Data Historians & ERP

download Data Historians & ERP

of 2

Transcript of Data Historians & ERP

  • 8/10/2019 Data Historians & ERP

    1/2

    Data Historians vs. ERP Systems

    See why both solutions play an integral role in manufacturing environmentsand areessential to optimizing process performance.

    Its easy to be confused as to what roles an Enterprise Resource Planning (ERP) system and a Data

    Historian play in a manufacturing environment. There are key features, functions, and benefits

    associated with each, and together they not only complement each otherbut bring greater value to

    today's process manufacturers.

    The Flexibility of the Data

    Historian

    As shown in Figure 1, the International

    Society of Automation (ISA) classifies the

    different systems used across a

    manufacturing organizationfrom the

    enterprise level down to the plant level. Data

    historians, like Aspen InfoPlus.21 (IP.21),

    reside as part of Level 3, but also extend into

    other areas due to their unique functionality.

    While they can communicate with all

    systems, the bulk of interaction is with Levels

    1 and 2. Historians can be configured to

    support either a single plant or the entire

    enterprise.

    ERP Functionality at the

    Enterprise Level

    Much like data historians, ERP systems vary in their

    degree and depth of functionality, but most are

    configured to support some or all of the key areas of

    business shown in Figure 2. Originally developed

    primarily to support Finance, ERP systems have

    grown over time to include functionality that

    supports Human Resources, Customer Orders,

    Inventory, and, in a limited capacity, Manufacturing.

    EnterpriseSystems

    Data historians providecurrent and historicalmanufacturing informationto plant and enterprisepersonnel

    PlantSystems

    ERPLevel 4

    Regulatory ControlSensors, Valves, DCS, PLC, SCADA

    Level 0, 1, 2

    ManufacturingExecution Systems

    Level 3

    Aspen IP.21

    Enterprise

    Systems

    ERP A Closer LookLevel 4

    CustomerOrders

    InvoicingFinancials

    HumanResources

    AccountsPayable

    CRM

    InventoryPurchasing Work Order

    Figure 1

    Figure 2

  • 8/10/2019 Data Historians & ERP

    2/2

    Contact AspenTech SMESales for Fast Response!

    North America

    phone: +1-855-882-7736

    Europe

    phone: +44-(0)-1189-226400

    Asia Pacific

    phone: +65-6395-3900

    Or email [email protected]

    Worldwide Headquarters

    Aspen Technology, Inc.

    200 Wheeler Road

    Burlington, MA 01803

    United States

    phone: +17812216400

    fax: +17812216410

    [email protected]

    For a complete list of offices, please vis

    www.aspentech.com/locations 2013 Aspen Technology, Inc. AspenTech, aspenONE, the Aspen leaf logo, the aspenONE logo, and OPTIMIZE are trademarks of Aspen

    Technology, Inc. All rights reserved. 11-4478-1013

    Closer Look at Historians

    Manufacturing Execution Systems (MES) can be further defined as shown in Figure 3. While

    some ERP software vendors claim to provide much of the MES functionality, it is not nearly as

    comprehensive as the offerings of a true MES vendorand does not provide the level of

    detail required by plant operations.

    Within the MES at Level 3, historian functionality is uniquely tailored toward Production DataCollection and Production Performance Analysis, collecting information to form a complete

    context of the manufacturing environment. (This is different than DCS or SCADA systems,

    which only have a view of information within their own system.) Historians then present

    actionable information back to the user in the form of trends, process graphics, and KPIs,

    which can be used for analytical purposes.

    Complementary Systems

    The strengths of ERP systems and historians actually complement one another. Historians

    gather data at the plant level so operators, engineers, and managers can effectively manage

    the day-to-day and month-to-month operation of a plant.

    ERPs pass the specific orders down to MES systems for processing. Historians then collect

    the relevant information from the actual product run and pass that data back to the ERP

    systemhelping the business make faster, smarter decisions.

    About AspenTech

    AspenTech is a leading supplier of

    software that optimizes process

    manufacturingfor energy,

    chemicals, pharmaceuticals,

    engineering and construction, and

    other industries that manufacture

    and produce products from a

    chemical process. With integrated

    aspenONE solutions, process

    manufacturers can implement best

    practices for optimizing their

    engineering, manufacturing, and

    supply chain operations. As a result,

    AspenTech customers are better able

    to increase capacity, improve

    margins, reduce costs, and become

    more energy efficient. To see how the

    worlds leading process

    manufacturers rely on AspenTech to

    achieve their operational excellence

    goals, visit www.aspentech.com .

    ProductDefinition

    ProductionCapability

    ProductionSchedule

    ProductionPerformance

    Level 0, 1, 2 Process Control

    Equipment & ProcessSpecific Production Rules

    OperationalCommands

    OperationalResponses

    Equipment & ProcessSpecific Data

    ProductionPerformance

    Analysis

    ProductionExecution

    DetailedProductionScheduling

    ProductionDispatching

    ProductDefinition

    Management

    ProductResource

    Management

    ProductionData

    Collection

    ProductionTracking

    MESLevel 3

    Aspen IP.21

    ERP HISTORIAN

    FundamentalPurpose

    Developed to support businesssystemsfinancial, sales, HR,

    etc.with limited manufacturingfunctionality for high-levelplanning/reporting. Not tactical.

    Developed to support plantmanagement. Collect information

    from a variety of systems (DCS,PLC, SCADA, instruments) to forma complete context ofmanufacturing environment.

    Architecture Geared toward "transactions" (e.g.,sale of products, payment ofinvoices). Typically structured as arelational database that handlestransactions well, but falls short insupporting real-time manufacturingprocesses.

    Architected to rapidly andefficiently gather plant data (e.g.,temperature, pressure, flows) anddeliver that information to users inthe form of trends, processgraphics, and KPIs for accurateanalysis.

    Figure 3

    http://localhost/var/www/apps/conversion/tmp/scratch_3/[email protected]://www.aspentech.com/locationshttp://localhost/var/www/apps/conversion/tmp/scratch_3/[email protected]://www.aspentech.com/locations