Isa 95.00.01
Isa 95.00.01
Isa 95.00.01
ISBN: 978-1-936007-47-9
Copyright © 2010 by the International Society of Automation (ISA). All rights reserved. Not for
resale. Printed in the United States of America. No part of this publication may be reproduced,
stored in a retrieval system, or transmitted in any form or by any means (electronic mechanical,
photocopying, recording, or otherwise), without the prior written permission of the Publisher.
ISA
67 Alexander Drive
P.O. Box 12277
Research Triangle Park, North Carolina 27709
CONTENTS
1 SCOPE ............................................................................................................................ 13
2 NORMATIVE REFERENCES ............................................................................................ 13
3 TERMS, DEFINITIONS AND ABBREVIATIONS................................................................. 14
3.1 Terms and definitions .................................................................................................... 14
3.2 Abbreviations ................................................................................................................ 17
4 ENTERPRISE-CONTROL SYSTEM INTEGRATION OVERVIEW ....................................... 18
5 HIERARCHY MODELS ..................................................................................................... 19
5.1 Hierarchy model introduction ......................................................................................... 19
5.2 Functional hierarchy...................................................................................................... 20
5.3 Role based equipment hierarchy ................................................................................... 25
5.4 Physical asset equipment hierarchy............................................................................... 30
5.5 Decision hierarchy (Informative) .................................................................................... 31
6 FUNCTIONAL DATA FLOW MODEL ................................................................................. 32
6.1 Functional data flow model contents .............................................................................. 32
6.2 Functional data flow model notation............................................................................... 32
6.3 Functional model .......................................................................................................... 33
6.4 Functions...................................................................................................................... 33
6.5 Information flows........................................................................................................... 40
7 MANUFACTURING OPERATIONS ................................................................................... 47
7.1 Manufacturing operations management ......................................................................... 47
7.2 Manufacturing operations management categories......................................................... 47
7.3 Other activities within manufacturing operations management ........................................ 48
7.4 Manufacturing operations management resources ......................................................... 49
8 INFORMATION MODEL ................................................................................................... 49
8.1 Model explanation ......................................................................................................... 49
8.2 Manufacturing operations information ............................................................................ 49
8.3 Segment relationships................................................................................................... 50
8.4 Categories of production operations management information........................................ 51
9 COMPLETENESS, COMPLIANCE AND CONFORMANCE ................................................. 63
9.1 Completeness ............................................................................................................... 63
9.2 Compliance................................................................................................................... 63
9.3 Conformance ................................................................................................................ 63
ANNEX A (INFORMATIVE) OTHER ENTERPRISE ACTIVITIES AFFECTING MANUFACTURING
OPERATIONS ........................................................................................................................ 65
A.1 Other areas .................................................................................................................. 65
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Figures
Figure 1 – Outline of models in the standard ........................................................................... 18
Figure 2 – Enterprise-control system interface ........................................................................ 19
Figure 3 – Functional hierarchy............................................................................................... 21
Figure 4 – Role based equipment hierarchy ............................................................................ 26
Figure 5 – Example of defined types of work centers and work units ........................................ 28
Figure 6 – Example of a physical asset hierarchy related to role based equipment hierarchy .... 31
Figure 7 – Functional model ................................................................................................... 33
Figure 8 – Manufacturing operations management model ........................................................ 48
Figure 9 – Manufacturing operations information ..................................................................... 50
Figure 10 – Segment relationships .......................................................................................... 51
Figure 11 – Production operations management information .................................................... 52
Figure 12 – Areas of information exchange ............................................................................. 53
Figure 13 – Production capability information .......................................................................... 54
Figure 14 – Current and future capacities................................................................................ 55
Figure 15 – Future capacity confidence factor ......................................................................... 56
Figure 16 – Past capacity unused capacity reasons................................................................. 56
Figure 17 – Process segment capabilities ............................................................................... 58
Figure 18 – Production information definition........................................................................... 59
Figure 19 – Product segment relation to process segment ....................................................... 60
Figure 20 – Example of nested product segments ................................................................... 61
Figure 21 – Possible information overlaps ............................................................................... 61
Figure 22 – Production information ......................................................................................... 62
Figure A.1 – Other enterprise activities affecting manufacturing operations.............................. 65
Figure A.2 – Functions in management of regulatory compliance ............................................. 68
Figure C.1 – Multiple business and production processes ........................................................ 78
Tables
Table 1 – Storage zone and storage unit examples ................................................................. 30
Table 2 – Yourdon notation used ............................................................................................ 32
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
FOREWORD
This foreword, as well as all footnotes and annexes, is included for information purposes and is not part of
ANSI/ISA-95.00.01-2010 (IEC 62264-1 Mod).
This document has been prepared as part of the service of ISA, the International Society of Automation,
toward a goal of uniformity in the fields of instrumentation, systems and automation. To be of real value,
this document should not be static but should be subject to periodic review. Toward this end, the Society
welcomes all comments and criticisms and asks that they be addressed to the Secretary, Standards and
Practices Board; ISA; 67 Alexander Drive; P. O. Box 12277; Research Triangle Park, NC 27709;
Telephone (919) 549-8411; Fax (919) 549-8288; E-mail: [email protected].
The ISA Standards and Practices Department is aware of the growing need for attention to the metric
system of units in general, and the International System of Units (SI) in particular, in the preparation of
instrumentation standards. The Department is further aware of the benefits to USA users of ISA
standards of incorporating suitable references to the SI (and the metric system) in their business and
professional dealings with other countries. Toward this end, this Department will endeavor to introduce
SI-acceptable metric units in all new and revised standards, recommended practices, and technical
reports to the greatest extent possible. Standard for Use of the International System of Units (SI): The
Modern Metric System, published by the American Society for Testing & Materials as IEEE/ASTM SI 10-
97, and future revisions, will be the reference guide for definitions, symbols, abbreviations, and
conversion factors.
It is the policy of ISA to encourage and welcome the participation of all concerned individuals and
interests in the development of ISA standards, recommended practices, and technical reports.
Participation in the ISA standards-making process by an individual in no way constitutes endorsement by
the employer of that individual, of ISA, or of any of the standards, recommended practices, and technical
reports that ISA develops.
EVEN IF ISA IS UNAWARE OF ANY PATENT COVERING THIS STANDARD, THE USER IS
CAUTIONED THAT IMPLEMENTATION OF THE STANDARD MAY REQUIRE USE OF TECHNIQUES,
PROCESSES, OR MATERIALS COVERED BY PATENT RIGHTS. ISA TAKES NO POSITION ON THE
EXISTENCE OR VALIDITY OF ANY PATENT RIGHTS THAT MAY BE INVOLVED IN IMPLEMENTING
THE STANDARD. ISA IS NOT RESPONSIBLE FOR IDENTIFYING ALL PATENTS THAT MAY
REQUIRE A LICENSE BEFORE IMPLEMENTATION OF THE STANDARD OR FOR INVESTIGATING
THE VALIDITY OR SCOPE OF ANY PATENTS BROUGHT TO ITS ATTENTION. THE USER SHOULD
CAREFULLY INVESTIGATE RELEVANT PATENTS BEFORE USING THE STANDARD FOR THE
USER’S INTENDED APPLICATION.
HOWEVER, ISA ASKS THAT ANYONE REVIEWING THIS STANDARD WHO IS AWARE OF ANY
PATENTS THAT MAY IMPACT IMPLEMENTATION OF THE STANDARD NOTIFY THE ISA
STANDARDS AND PRACTICES DEPARTMENT OF THE PATENT AND ITS OWNER.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
This Part 1 standard is structured to follow IEC (International Electrotechnical Commission) guidelines.
This revised Part 1 replaces ANSI/ISA-95.00.01-2000.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
This document is Part 1 of a multi-part set of standards that defines the information exchange interface
between enterprise activities and control activities.
As currently envisioned, the ANSI/ISA-95 series will consist of the following parts under the general title,
Enterprise-Control System Integration:
INTRODUCTION
This is a revision of ISA-95.00.01-2000. The major changes made to this standard from the
previous version are:
1. The starting point for the update was IEC 62264-1 Enterprise-control system integration:
models and terminology. This is the IEC/ISO version of this standard. IEC 62264-1
includes a new section on the Decision Hierarchy in Clause 5.5.
2. The functional hierarchy in Clause 5.2 was extended using the definitions from
IEC 62264-3 Enterprise-control system integration - Part 3: Activity Models of
Manufacturing Operations Management.
3. The equipment hierarchy in Clause 5.3 was extended using the definitions from
IEC 62264-3.
4. A physical asset equipment model was added in Clause 5.3.
5. The generic model of manufacturing operations management categories in Clause 7 was
added using information from IEC 62264-3.
6. The formal UML models that were in Clause 7 were moved to the Part 2 standard in the
series and the remaining data definitions are now in Clause 8.
7. The capacity and capability model in Clause 8 was extended.
8. A new Annex A was moved from IEC 62264-3.
9. A new Annex B was moved from IEC 62264-3.
10. Clause 5.5 on the decision hierarchy was removed and a reference added to ISO 15704
which is now available.
11. Old Annex C, DISCUSSIONS OF MODELS, was moved to a Technical Report
12. Old Annex D, SELECTED ELEMENTS OF THE PURDUE REFERENCE MODEL, was
moved to a Technical Report.
13. Old Annex E, PRM CORRELATION TO MESA INTERNATIONAL MODEL AND ISA-95.01
MODELS, was moved to a Technical Report
This Part 1 standard is limited to describing the relevant functions in the enterprise and the manufacturing
and control domains and which information is normally exchanged between these domains. Subsequent
parts will address how this information can be exchanged in a robust, secure, and cost-effective manner
preserving the integrity of the complete system. For purposes of this standard the manufacturing and
control domain includes manufacturing operations management systems, manufacturing control systems,
and other associated systems and equipment associated with manufacturing. The terms “enterprise,”
“controls,” “process control,” and “manufacturing” are used in their most general sense and are held to be
applicable to a broad sector of industries.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
This Part 1 standard provides standard models and terminology for describing the interfaces
between the business systems of an enterprise and its manufacturing operations and control
systems. The models and terminology presented in this standard
a) emphasize good integration practices of control systems with enterprise systems during the
entire life cycle of the systems;
b) can be used to improve existing integration capabilities of manufacturing operations and
control systems with enterprise systems; and
c) can be applied regardless of the degree of automation.
Specifically, this standard provides a standard terminology and a consistent set of concepts and
models for integrating control systems with enterprise systems that will improve communications
between all parties involved. Some of the benefits produced will
a) reduce users' times to reach full production levels for new products;
b) enable vendors to supply appropriate tools for implementing integration of control systems to
enterprise systems;
c) enable users to better identify their needs;
d) reduce the costs of automating manufacturing processes;
e) optimize supply chains; and
f) reduce life-cycle engineering efforts.
b) responsible for specifying interfaces between manufacturing and process control systems and other
systems of the business enterprise; or
c) involved in designing, creating, marketing, and integrating automation products used to interface
manufacturing operations and business systems.
d) involved in specifying, designing or managing product creation, movement and storage within
manufacturing enterprises.
− suggest that there is only one way of implementing integration of control systems to
enterprise systems;
− force users to abandon their current methods of handling integration; or
− restrict development in the area of integration of control systems to enterprise systems.
This Part 1 standard discusses the interface content between manufacturing-control functions
and other enterprise functions, based upon the Purdue Reference Model for CIM (hierarchical
form) as published by ISA. This standard presents a partial model or reference model as defined
in ISO 15704. The first three clauses are normative and present the scope of the standard, normative
references, and definitions, in that order.
The scope of this part is limited to describing the relevant functions in the enterprise and the
manufacturing and control domain and which information is normally exchanged between these
domains. Subsequent parts will address how this information can be exchanged in a robust,
secure, and cost-effective manner preserving the integrity of the complete system.
Clause 4 is informative. The intent is to describe the context of the models in Clause 5 and
Clause 6. It gives the criteria used to determine the scope of the manufacturing operations and
control system domain. Clause 4, being informative, does not contain the formal definitions of the
models and terminology but describes the context to understand the other clauses.
Clause 5 is normative. The intent is to describe hierarchy models of the activities involved in
manufacturing-control enterprises. It presents in general terms the activities that are associated
with manufacturing operations and control and the activities that occur at the business logistics
level. It also gives an equipment hierarchy model of equipment associated with manufacturing
operations and control. Clause 5.5 is informative. Clause 5, being normative, contains format
definitions of the models and terminology.
Clause 6 is normative. The intent is to describe a general model of the functions within an
enterprise which are concerned with the integration of business and control. It defines, in detail,
an abstract model of control functions and, in less detail, the business functions that interface to
control. The purpose is to establish a common understanding for functions and data flows
involved in information exchange.
Clause 7 is normative. The intent is to define in detail the information that makes up the
information streams defined in Clause 6. The purpose is to establish a common terminology for the
elements of information exchanged. Clause 7, being normative, contains formal definitions of the models
and terminology. The attributes and properties are not formally defined in this clause of the standard.
Clause 8 is normative. It provides a description of the categories of information structures that are
exchanged between applications at Level 4 and those at Level 3. The clause also provides the
information categories that are exchanged between the applications within Level 3.
Annex A is informative. It defines the relationship of this standard with other related
standardization work in the manufacturing area.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Annex C is informative. It describes business drivers and key performance indicators that are the
reasons for the information exchange between business and control function.
1 Scope
This standard describes the interface content between manufacturing operations and control
functions and other enterprise functions. The interfaces considered are the interfaces between
Levels 3 and 4 of the hierarchical model defined by this standard. The goals are to increase
uniformity and consistency of interface terminology and reduce the risk, cost, and errors
associated with implementing these interfaces.
The standard can be used to reduce the effort associated with implementing new product
offerings. The goal is to have enterprise systems and control systems that inter-operate and
easily integrate.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
2 Normative references
The following referenced documents are indispensable for the application of this document. For
dated references, only the edition cited applies. For undated references, the latest edition of the
referenced document (including any amendments) applies.
For the purposes of this document, the following terms and definitions apply. Phrases in italic in
lines following the preferred term in bold are considered as synonyms.
3.1.1
area
physical, geographical or logical grouping of resources determined by the site
NOTE It can contain process cells, production units, production lines, and storage zones.
3.1.2
available capacity
portion of the production capacity that can be attained but is not committed to current or future
production
3.1.3
bill of lading
contract or receipt for goods that a carrier agrees to transport from one place to another and to
deliver to a designated person or that it assigns for compensation upon the conditions stated
therein
3.1.4
bill of material
listing of all the subassemblies, parts, and/or materials that are used in the production of
a product including the quantity of each material required to make a product
NOTE The term product may refer to a finished product or an intermediate product
3.1.5
bill of resources
listing of all resources and when in the production process they are needed to produce a product
NOTE It is also a listing of the key resources required to manufacture a product, organized as segments of
production and is often used to predict the impact of activity changes in the master production schedule
on the supply of resources.
3.1.6
capability
ability to perform actions, including attributes on qualifications and measures of the ability
as capacity
3.1.7
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
capacity
measure of the ability to take action, an aspect of a capability
EXAMPLE Measures of the production rates, flow rates, mass or volume.
3.1.8
certificate of analysis
certification of conformance to quality standards or specifications for products or materials
NOTE It can include a list or reference of analysis results and process information. It is often required for
custody transfer of materials.
3.1.9
committed capacity
portion of the production capacity that is currently in use or is scheduled for use
3.1.10
consumables
resources that are not normally included in bills of material or are not individually accounted for
in specific production requests or are not lot tracked
3.1.11
control domain
[see manufacturing operations and control domain]
3.1.12
enterprise
one or more organizations sharing a definite mission, goals and objectives to offer an output
such as a product or service
3.1.13
finished goods
final materials on which all processing and production is completed
3.1.14
finished good waivers
approvals for deviation from normal product specifications
3.1.15
in-process waiver requests
requests for waivers on normal production procedures due to deviations in materials, equipment,
or quality metrics, where normal product specifications are maintained
3.1.16
manufacturing operations management domain
domain that includes all the activities in Level 3 and information flows to and from levels 1, 2 and
4
NOTE The manufacturing operations management domain is a subset of the manufacturing operations and
control domain
3.1.17
manufacturing operations and control domain
control domain
domain that includes all the activities and information flows in Level 3, 2, and 1 and information
flows to and from Level 4.
3.1.18
process segment
business process segment
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
view of a collection of resources with specific capabilities needed for a segment of production,
independent of any particular product at the level of detail required to support business
processes that may also be independent of any particular product
NOTE 1 This may include material, energy, personnel, or equipment.
NOTE 2 The business process segment synonym is included to reflect the business process oriented aspects of
the process segment
3.1.19
product definition
collection of information about resources, production rules and scheduling required to create a
product. A product definition has an external reference to a bill of materials, a product production
rule, and a bill of resources
3.1.20
product segment
logical grouping of personnel resources, equipment resources, and material specifications
required of a process segment to complete a production step for a specific product
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
3.1.21
production capability
ability of resources to perform production in the enterprise. The production capability includes
the capacity of those resources and represents
a) the collection of personnel, equipment, material, and process segment capabilities;
b) the total of the current committed, available, and unattainable capacity of the production
facility;
c) the highest sustainable output rate that could be achieved for a given product mix, raw
materials, worker effort, plant, and equipment
3.1.22
production control
collection of functions that manages all production within a site or area
3.1.23
production line
work center that is a collection of equipment dedicated to the manufacture of a specific number
of products or product families
3.1.24
production rules
information used to instruct a manufacturing operation how to produce a product
3.1.25
production unit
work center that is a set of production equipment that converts, separates, or reacts one or more
feedstocks to produce intermediate or final products
3.1.26
physical asset
A physical object uniquely identified and tracked for maintenance and/or financial purposes.
NOTE: This standard addresses physical assets used in equipment roles. There are many other physical assets
in an enterprise.
3.1.27
resource
enterprise entity that provides some or all of the capabilities required by the execution of
an enterprise activity and/or business process (in the context of this standard, a collection
of personnel, equipment, and/or material)
3.1.28
site
a component of a manufacturing enterprise that is identified by physical, geographical, or logical
segmentation
3.1.29
storage unit
work unit within a storage zone that is a designated physical space and/or equipment dedicated
to the storage of materials and/or equipment
3.1.30
storage zone
work center that is a designated physical space and/or equipment dedicated to the storage of
materials and/or equipment
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
3.1.31
unattainable capacity
portion of the production capacity that cannot be attained
NOTE Typically due to factors such as equipment unavailability, sub-optimal scheduling, or resource limitations.
3.1.32
work cell
a work unit within a production line that consists of equipment grouped together to produce a
family of parts having similar manufacturing requirements
3.1.32
work center
an equipment element under an area in a role based equipment hierarchy that performs
production, storage, material movement, or any other Level 3 or Level 4 scheduled activity
3.1.33
work unit
an equipment element under a work center in a role based equipment hierarchy that performs
production, storage, material movement, or any other Level 3 or Level 4 scheduled activity
3.2 Abbreviations
For the purposes of this standard, the following abbreviations apply.
BOL Bill of lading
BOM Bill of material
CIM Computer integrated manufacturing
COA Certificate of analysis
MESA Manufacturing Enterprise Solutions Association
MO&C Manufacturing operations and control
Multiple models show the functions and integration associated with manufacturing operations
and control systems and enterprise systems.
a) Hierarchy models that describe the levels of functions and domains of control associated
within manufacturing organizations are presented in Clause 5. These models are based on
The Purdue Reference Model for CIM, referenced as PRM; the MESA International
Functional Model; and the equipment hierarchy model from IEC 61512-1. Detailed activity
models of the manufacturing operations domain are given in Part 3.
NOTE See the Bibliography for reference to the MESA white paper defining MES functionality.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
b) A data flow model that describes the functional and data flows within manufacturing
organizations is given in Clause 6. This model is also based on The Purdue Reference Model
for CIM.
c) An object model that describes the information that may cross the enterprise and control
system boundary is given in Part 2.
This standard provides models and information in multiple levels of detail and abstraction. These
levels are illustrated in Figure 1, which serves as a map to the rest of the document. Each model
and diagram increases the level of detail presented in the previous model.
The models start with a description of the domain of control systems and the domain of
enterprise systems. The domain discussion is contained in Clause 5.
Functions within the domains are presented in Clauses 5 and 6. Functions of interest that are
relevant to the standard are also given a detailed description in Clause 6. The information flows
of interest between the relevant functions are listed in 6.5.
The categories of information are given in Clause 8. The formal object model of the information
of interest is presented in Part 2.
The information that flows between functions identified as being within the MO&C domain
and those outside the MO&C domain describe the enterprise-control system boundary.
Information exchanged between functions within the MO&C domain and information exchanged
between functions outside the MO&C domain is outside the scope of this document. Figure 2
illustrates the enterprise-control system interface, as depicted in the data flow model, between
control and non-control functions; the shaded circles indicate functions that exchange
information and are described in the data flow model. Functions depicted as white circles and
data flows depicted as dashed lines are those considered as outside the scope of this standard.
Information flows of interest across the enterprise-control system boundary are given in Part 2
and Part 5. Some information flows within the manufacturing and operations domain are given in
Part 4 and Part 6.
Functions detailed
5 Hierarchy models
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Figure 3 depicts the different levels of a functional hierarchy model: business planning and
logistics, manufacturing operations and control, and batch, continuous, or discrete control. The
levels provide different functions and work in different timeframes. The interface addressed in
this standard is between Level 4 and Level 3 of the hierarchy model. This is generally the
interface between plant production scheduling and operation management and plant floor
coordination.
This standard specifies that each level shall provide the functions listed below and illustrated in
Figure 3.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Level 2 2 - Monitoring, supervisory control and
automated control of the production process
Time Frame
Batch Continuous Discrete Hours, minutes, seconds, subseconds
Control Control Control
Level 1 1 - Sensing the production process,
manipulating the production process
Level 0 0 - The actual production process
Levels 2, 1, and 0 present the cell or line supervision functions, operations functions, and
process control functions and are not addressed in this standard. The discussion and labeling of
levels is based on a historical description. Level 0 indicates the process, usually the
manufacturing or production process. Level 1 indicates manual sensing, sensors, and actuators
used to monitor and manipulate the process. Level 2 indicates the control activities, either
manual or automated, that keeps the process stable or under control. There are several different
models for the functions at these levels based on the actual production strategy used.
For purposes of this standard the terminology Manufacturing Operations Management (MOM)
defines the Level 3 activities and information flows, and Manufacturing Operations and Control
(MO&C) define Level 1, 2, and 3 activities and information flows. The standard assumes all
activities not explicitly presented as part of the MO&C domain to be part of the enterprise
domain.
The criterion for defining the activities to be included as a Level 3, 2, or 1 activity shall be that
the activity is directly involved in manufacturing and includes information about personnel,
equipment, or material and meets any of the following conditions.
EXAMPLE Maintaining regional, government and other agency compliance related to products and production.
NOTE 2 This includes such factors as safety, environmental and cGMP (current good manufacturing
practices) compliance.
NOTE 3 There are other criteria such as company policy and organizational structure, or the nature of the
operations that could expand the scope of manufacturing operations management. See Annex A.
NOTE 4 Such activities as personnel management of salaries and job titles may be important for running a
manufacturing business, but they are not considered part of manufacturing operations management.
5.2.3 Level 4
a) collecting and maintaining raw material and spare parts usage and available inventory, and
providing data for purchase of raw material and spare parts;
b) collecting and maintaining overall energy use and available inventory and providing data for
purchase of energy source;
c) collecting and maintaining overall goods in process and production inventory files;
d) collecting and maintaining quality control files as they relate to customer requirements;
e) collecting and maintaining machinery and equipment use and life history files necessary for
preventive and predictive maintenance planning;
f) collecting and maintaining manpower use data for transmittal to personnel and accounting;
g) establishing the basic plant production schedule;
h) modifying the basic plant production schedule for orders received, based on resource
availability changes, energy sources available, power demand levels, and maintenance
requirements;
i) developing optimum preventive maintenance and equipment renovation schedules in
coordination with the basic plant production schedule;
j) determining the optimum inventory levels of raw materials, energy sources, spare parts, and
goods in process at each storage point. These functions also include materials requirements
planning (MRP) and spare parts procurement;
k) modifying the basic plant production schedule as necessary whenever major production
interruptions occur;
l) planning production capacity, based on all of the above activities.
5.2.4 Level 3
a) reporting on area production including variable manufacturing costs based on the enterprise
standard cost model;
b) collecting and maintaining area data on production, inventory, manpower, raw materials,
product quality, spare parts and energy usage;
c) performing of data collection and off-line analysis as required by engineering functions. This
may include statistical quality analysis and related control functions;
d) performing needed personnel functions such as: work period statistics (for example, time,
task), vacation schedule, work force schedules, union line of progression, and in-house
training and personnel qualification;
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
e) establishing the immediate detailed production schedule for its own area including
maintenance, transportation and other production-related needs;
f) locally optimizing the costs for its individual production area while completing the production
schedule established by the Level 4 functions;
g) modifying production schedules to compensate for plant production interruptions that may
occur in its area of responsibility;
h) managing manufacturing operations;
i) managing maintenance on production equipment;
j) managing laboratory and quality testing of materials;
k) managing movement and storage of materials;
l) transforming the business oriented information used for Level 4-3 data exchanges into the
manufacturing operations management oriented information used within Levels 3 and below.
Descriptions of the major functionalities associated with these various Level 3 activities are given
in 5.2.4.2 through 5.2.4.13.
The MOM domain includes the functionality of managing resources directly associated with
control and manufacturing. The resources include machines, tools, labor skills, materials, other
equipment, documents, and other entities that are required for work to start and to be completed.
The management of these resources may include local resource reservation to meet production-
scheduling objectives.
The MOM domain also ensures that equipment is properly set up for processing, including any
allocation needed for set-up. The MOM domain is also responsible for providing real-time
statuses of the resources and a detailed history of resource use.
The MOM domain includes the functionality of managing the flow of production in the form of
jobs, orders, batches, lots, and work orders, by dispatching production to specific equipment and
personnel. Dispatch information is typically presented in the sequence in which the work needs
to be done and may change in real time as events occur on the factory floor.
The MOM domain may alter the prescribed schedules, within agreed limits, based on local
availability and current conditions. Dispatching of production includes the ability to control the
amount of work in process at any point through buffer management and management of rework
and salvage processes.
The MOM domain includes the functionality of obtaining the operational production and
parametric data that are associated with the production equipment and production processes.
The MOM domain also is responsible for providing real-time statuses of the production
equipment and production processes and a history of production and parametric data.
The MOM domain includes the functionality of providing real-time measurements collected from
manufacturing and analysis in order to assure proper product quality control and to identify
problems requiring attention. It may recommend actions to correct the problem, including
correlating the symptoms, actions and results to determine the cause.
The MOM domain includes the functionality of monitoring production processes and either
automatically corrects or provides decision support to operators for correcting and improving in-
process functions. These functions may be intra-operational and focus specifically on machines
or equipment being monitored and controlled within a single operation, as well as tracking a
production process from one operation to the next.
It may include alarm and event management to make sure personnel are aware of process
changes that may be outside acceptable tolerances.
The MOM domain includes the functionality of providing the status of production and the
disposition of work. Status information may include personnel assigned to the work; component
materials used in production; current production conditions; and any alarms, rework, or other
exceptions related to the product. The functionality includes the capability of recording the
production information to allow forward and backward traceability of components and their use
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
within each end product.
The MOM domain includes the functionality of providing up-to-the-minute reporting of actual
manufacturing operations results along with comparisons to past history and expected results.
Performance results include such measurements as resource utilization, resource availability,
product unit cycle time, conformance to schedule, and performance to standards. Performance
analysis may include SPC/SQC analysis and may draw from information gathered by different
control functions that measure operating parameters.
The MOM domain includes the functionality of providing the sequence and the timing of
operations based on priorities, attributes, characteristics, and production rules associated with
specific production equipment and specific product characteristics, such as shape, color
combinations or other requirements that, when scheduled properly in detail, will tend to minimize
set-up time and effort, or increase production throughput. Operations and detailed scheduling
take into account the finite capacity of resources and consider alternative and/or
overlapping/parallel operations when detailing the timing of equipment loading and the particular
adjustments to accommodate shift patterns.
The MOM domain includes some of the functionality of controlling records and forms that are
maintained with the production unit. The records and forms include work instructions, recipes,
drawings, standard operating procedures, part programs, batch records, engineering change
notices, shift-to-shift communication, as well as the ability to edit “as planned” and “as built”
information. It would also include the control and integrity of regulatory documentation,
environmental, health and safety regulations, and SOP information such as corrective action
procedures.
The MOM domain includes some of the functionality of maintaining equipment and tools. The
functions ensure the equipment and tools availability for manufacturing. They also may include
scheduling for periodic, preventive, or predictive maintenance as well as responding to
immediate problems. Maintenance management maintains a history of past events or problems
to aid in diagnosing problems, such as equipment performances, maintenance personnel
performances, or instrumentation reliabilities.
The MOM domain includes some of the functionality of managing and tracking the movement and
storage of materials, in-process items and finished products, as well as, the transfers between
and within work centers. In some instances, these functions may also include receipt of material,
certain types of material testing, processing or conversion and preparing material for shipment.
The assets of an enterprise involved in manufacturing are usually organized in a role based
hierarchical fashion as illustrated in Figure 4. Lower-level groupings are combined to form higher
levels in the role based hierarchy. In some cases, a grouping within one level may be
incorporated into another grouping at that same level.
NOTE 1 The term role based is applied to the equipment model to indicate that the hierarchy is defined in terms of
the Level 3 and 4 functions and activities that equipment entities may perform. The actual physical
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
location, composition, and relationships of the equipment entities are defined in a physical asset
equipment hierarchy.
This model shows the areas of responsibility for the different function levels defined in the
functional hierarchical model of Figure 3. The role based equipment hierarchy model additionally
describes some of the objects utilized in information exchange between functions.
1. Collapsing – Elements in the models may be omitted as long as the models remain consistent and the
functions of the elements combined or removed are taken into account.
2. Expanding – Elements may be added to, or divided within, the models. When they are added between
related elements, the integrity of the original relationship should be maintained. Elements may be
divided to separately manage the resulting smaller elements.
The UML role based equipment model defined in Part 2 of this standard is used to define the role
based equipment hierarchy information. The Part 2 UML model contains the rules used to
construct the hierarchical models used in different manufacturing operations management
scenarios.
AREA
AREA
AREA
Level 3 activities AREA
typically deal with Contains
these objects
WORK
WORK
WORK
CENTER
CENTER
WORK
CENTER
CENTER
Contains
WORK
WORK
WORK
UNIT
UNIT
WORK
UNIT
UNIT
Figure 4 – Role based equipment hierarchy
5.3.2 Enterprise
An enterprise is a collection of sites and areas and represents the top level of a role based
equipment hierarchy. The enterprise is responsible for determining what products will be
manufactured, at which sites they will be manufactured, and in general how they will be
manufactured.
Level 4 functions are generally concerned with the enterprise and site levels. However,
enterprise planning and scheduling may involve areas, work centers, or work units within an
area.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
5.3.3 Site
A geographical location and main production capability usually identifies a site. Sites generally
have well-defined manufacturing capabilities.
NOTE For example, site identifiers from various industries are Dallas Expressway Plant, Deer Park Olefins Plant
and Johnson City Manufacturing Facility. Sites are often used for rough-cut planning and scheduling.
5.3.4 Area
An area is a physical, geographical, or logical grouping determined by the site. It may contain
work centers such as process cells, production units, production lines, and storage zones. Most
Level 3 functions occur within the area. The main production capability and geographical location
within a site usually identify areas.
NOTE For example, area identifiers from various industries are CMOS Facility, North End Tank Farm and
Building 2 Electronic Assembly.
Areas generally have well-defined manufacturing capabilities and capacities. The capabilities
and capacities are used for Level 3 and Level 4 planning and scheduling.
An area is made up of lower-level elements that perform the manufacturing functions. An area
may have one or more of any of the lower-level elements depending upon the manufacturing
requirements.
EXAMPLE 1 Many areas will have a combination of production lines for the discrete operations, production units for
the continuous processes, and process cells for batch processes.
EXAMPLE 2 A beverage manufacturer may have an area with continuous mixing in a production unit, which feeds a
batch process cell for batch processing, feeding a bottling line for a discrete bottling process.
Depending on the planning and scheduling strategy selected, the Level 4 functions may stop at
the area level, or they may schedule the functions of the lower-level elements within the areas.
Work centers are elements of the equipment hierarchy under an area. The term work center may
be used when the specific type of the equipment element is not significant for the purpose of the
discussion.
For manufacturing operations management there are specific terms for work centers and work
units that apply to batch production, continuous production, discrete or repetitive production, and
for storage and movement of materials and equipment.
A work center is any equipment element subordinate to an area that may be defined by the user
in an extension to the role based equipment hierarchy model. See Figure 4. Types of work
centers specifically defined in this part are process cells, production units, production lines, or
storage zones, as shown in Figure 5.
The types of work centers may be extended when required for application specific role based
equipment hierarchies where the defined types do not apply. When a new type is added it shall
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
maintain the same relationship within the hierarchy as the defined work center types (within an
area and contains work units).
EXAMPLE 1 A new work center type represents a distinct grouping of work units (a single Work Unit cannot belong to
more than one Work Center).
EXAMPLE 2 Additional work center types are:
• Laboratory – used in quality operations
• Mobile Equipment Pool
• Unused Equipment Store – used in maintenance operations
• Transportation Center
NOTE 1 The role based equipment hierarchy is an expansion of the equipment hierarchy model described in
ANSI/ISA 88.01 and IEC 61512-1 and includes the definition of assets for discrete and continuous
manufacturing, and for material storage.
NOTE 2 Extended work center types are outside the scope of this standard and applications built using the
extensions may not be interoperable.
ENTERPRISE
SITE
AREA
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
CELL UNIT LINE ZONE CENTERS
NOTE 3 Material is also temporarily stored in process cells, production units and production lines. This material is
typically considered WIP and is usually distinct from inventory managed materials.
A work unit is any element of the equipment hierarchy under a work center. Work units are the
lowest form of elements in an equipment hierarchy that are typically scheduled by Level 3
functions. See Figure 5.
Work centers are typically the grouping of equipment scheduled by the Level 4 or Level 3
functions. Work centers have well-defined capabilities and capacities and these are used for
Level 3 functions. The capacities and capabilities are also often used as input to Level 4
business processes. Scheduling functions may identify specific work units.
Production units and units are the lowest level of equipment typically scheduled by the Level 4 or
Level 3 functions for continuous manufacturing processes. Production units are composed of
units and units are composed lower level elements, such as equipment modules, sensors, and
actuators, but definitions of these are outside the scope of this standard. A production unit
generally encompasses all of the equipment required for a segment of continuous production that
operates in a relatively autonomous manner. It generally converts, separates, or reacts one or
more feed stocks to produce intermediate or final products.
The major processing activity or product generated often identifies the production unit.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
NOTE For example, production unit identifiers from various industries are Catalytic Cracker #1, Steam Cracker
#59 and Alkylation Unit 2.
Production units and units have well-defined processing capabilities and throughput capacities
and these are used for Level 3 functions. The capacities and capabilities are also often used as
input to Level 4 scheduling, even if the units are not scheduled by the Level 4 functions.
Production lines and work cells are the lowest levels of equipment typically scheduled by the
Level 4 or Level 3 functions for discrete manufacturing processes. Work cells are usually only
identified when there is flexibility in the routing of work within a production line. Production lines
and work cells may be composed of lower-level elements, but definitions of these are outside the
scope of this document.
Production line and work cells have well-defined manufacturing capabilities and throughput
capacities and these are used for Level 3 functions. The capacities and capabilities are also
often used as input to Level 4 scheduling, even if the production lines and work cells are not
scheduled by the Level 4 functions.
Process cells and units are the lowest level of equipment typically scheduled by the Level 4 and
Level 3 functions for batch manufacturing processes. Units are usually only identified at Level 3
and 4 if there is flexibility in the routing of the product within a process cell. The definitions for
process cells and units are contained in IEC 61512-1.
The major processing capability or family of products produced often identifies the process cell.
NOTE For example, process cell identifiers from various industries are Mixing Line #5, West Side Glue Line and
Detergent Line 13.
Process cells and units have well-defined manufacturing capabilities and batch capacities and
these are used for Level 3 functions. The capacities and capabilities may also be used as input
data for Level 4 scheduling, even if the process cells or units are not scheduled by the Level 4
functions.
Storage zones and storage units are the lowest level of material movement equipment typically
scheduled by the Level 4 and Level 3 functions for discrete, batch and continuous manufacturing
processes. A storage zone is a type of work center and a storage unit is a type of work unit that
is organized as elements within an area. These are the lower-level elements of an equipment
hierarchy used in material storage and movement activities.
A storage zone typically has the capability needed for the receipt, storage, retrieval, movement
and shipment of materials. This may include the movement of materials from one work center to
another work center within or between enterprises.
NOTE Material is also temporarily stored in process cells, production units and production lines. This material is
typically considered WIP and is usually distinct from inventory managed materials.
Storage units are typically managed at a finer level of detail than a storage zone. The physical
location of a storage unit may change over time; for example, for goods in transit.
Storage units may be dedicated to a given material, group of materials, or method of storage.
Storage units can be further divided to address any hierarchical storage management scheme.
Table 1 lists examples of a hierarchy of storage zones and the associated storage units.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Ship terminal Ship, ship’s hold, container,
barrel, tank
Rail yard Railcar
Holding area Pallet, barrel
The physical assets of an enterprise involved in manufacturing are usually also organized in a
physical asset equipment hierarchy that may be related to financial or cost center control. Lower-
level groupings are combined to form higher levels in the physical asset hierarchy. In some
cases, a grouping within one level of the physical asset equipment hierarchy may be
incorporated into another grouping at that same level.
The UML formal physical asset equipment model defined in Part 2 of this standard is used to
define the physical asset equipment hierarchy information. The Part 2 UML model contains the
rules used to construct the hierarchical models used in different operational scenarios.
The physical asset hierarchy and the role based equipment hierarchy may overlap at any level;
however the physical asset hierarchy often contains additional levels that correspond to either a
cost center hierarchy or a physical assembly hierarchy, levels in the physical asset hierarchy
may also have different names than the role hierarchy, such as Site Asset, as illustrated in
Figure 6. Terminology for levels in the physical asset hierarchy is not defined in this Part.
NOTE 1 The physical asset equipment hierarchy usually has a reference to an accounting hierarchy in a chart of
accounts. A chart of accounts is a listing of accounts in a financial system and is used as the basis for
preparing financial reports from an accounting system.
NOTE 2 Single use equipment may be considered as equipment or material, which is consumed, depending upon
the application. For example load carriers such as containers and pallets may be single use equipment.
SITE
SITE SITE
SITE
SITE
SITE May correspond to SITE
SITE
Boston Boston
Contains
WORK CENTER
Line 52
May correspond to
WORK UNIT
Test Machine 12
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The functional data flow model shall identify and relate the following:
The enterprise-control interface is described using a data flow model. The model uses the
Yourdon-DeMarco notational methodology (see Bibliography).
Symbol Definition
A function is represented as a labeled ellipse. A function is a group of
tasks that are classified as having a common objective. Each function
can be further decomposed in terms of detailed functions, at a more
Function granular level. Functions at any level of decomposition are identified
(4.0) with a name and a level designation, for example, 3.1.3. The successive
numbers in a designation represent the depth of detail of an identified
function in the functional hierarchy level.
.
The functional model is depicted in Figure 7. The wide dotted line illustrates the boundary of the
enterprise-control interface. The line is equivalent to the Level 3/Level 4 interface presented in
5.1. The manufacturing operations and control side of the interface includes most of the
functions in production control and some of the activities in the other major functions. The
labeled lines indicate information flows of importance to manufacturing operations and control.
The wide dotted line intersects functions that have sub-functions that may fall into the MO&C
domain or the enterprise domain depending on organizational policies. This is a combination of a
function view and an information view of the enterprise, as defined in ISO 15704.
The model structure does not reflect an organizational structure within a company but an
organizational structure of functions. Different companies will place the functions in different
organizational groups.
The detailed information in the information flows is presented in Part 2.
Order
and
rial Processing
m ate ipt rs
ing rece de
om y Or (1.0) Product Cost Product
Inc energ ti on
uc
Pr
od ilit
y Accounting Shipping Admin
ab
ail (8.0) (9.0)
Av
Finished Goods Inventory
Production
Release to ship
Confirm to ship
t
Scheduling
os
od
(2.0)
an uctio
Fi
s
es t
an
r
Pr uc
tiv os
ent
Ma g Te
nis
od
uc tion
equ rgy
jec n C
he
rfo Prod
irem
Sc tio
n F Cap
ter
Lon
dG
Ob tio
he
rom ab
rm
du
uc
oo
le Pla ility
od
ds
n
Pe
Pr
qu
ire d Cu
En uirem
Pro Maintenance
Pr
Maintenance Standards
O
om
Re
Maintenance Requests
nfir
oc
Maintenance Responses
ts
me sto
teri
e
QA ess
du
sul
q
n ts m e
ing
ma
D
al a der
Re r
ct a uct a
Pro
and Methods
a
an
Re
su ta
tio
lts
dP
nd
Pro uct
r
d
nd nd P
QA
e
Feedback
ro d
Pro
du
Quality
ct a nd P
Procurement
ces oces
nd roc
Assurance
a
(5.0)
Technical
s T s In
r
Pro ess
ech form
M (6.0) St
an
Pu ain
ces
nic
d
r te
Re chas nan Re Cu ard
s K equ
qu sto s a
al F ation
q u e O ce ire me nd
ire
no irem
Req roces nd
QA me rder
ee
m r
nts
Re Maintenance
wH
en
P ct a
db eque
nts
uire s
sul
me
ts ts
ack
ow nts
Management
du
R
Marketing
Pro
e
(10.0)
& Sales
st
R&D (12.0)
and Engineering
(13.0)
6.4 Functions
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
There is generally no direct interface between the functions of order processing and the
manufacturing operations and control functions.
Production scheduling functions interface to the manufacturing operations and control system
functions through a production schedule, actual production information, and production capability
information. This information exchange is presented in the production control functions.
The production control functions encompass most of the functions associated with manufacturing
operations and control. The functions of production control typically include
a) controlling the transformation of raw materials into the end-product in accordance with the
production schedule and production standards;
b) performing plant engineering activities and updating of process plans;
c) issuing requirements for raw materials;
d) producing reports of performance and costs;
e) evaluating constraints to capacity and quality;
f) self-testing and diagnosis of production and control equipment;
g) creating production standards and instructions for SOPs (standard operating procedures),
recipes, and equipment handling for specific processing equipment.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The main functions in production control include process support engineering, operations control,
and operations planning.
The functions of process support engineering generate or modify the following information for
use in other control functions.
1) Minor equipment and process modifications; this may include new design drawings.
2) Instructions on how to handle equipment; this may include standard operating
procedures.
3) Instructions on how to make products; this includes production rules and the standard
materials, equipment, and other resources used.
4) Material safety data sheets (MSDS).
5) Instructions on how to install equipment; this may include vendor equipment.
6) Environmental and safety operating limits and constraints.
7) Engineering standards for process equipment design techniques and process operational
methods, and online operating instructions.
Production operations control is the collection of functions that manages all production within a
site or area.
The functions of production control typically generate or modify the following information for use
in other control functions.
The functions of production operations planning typically generate or modify the following
information for use in other control functions.
The functions of materials and energy control typically generate or modify the following
information for use in other control functions.
Some of the functions within material and energy control may be inside the MO&C domain,
based on local organizational structures. Therefore, selected data flows into and out of material
and energy control are presented because they may cross the enterprise-control system
boundary.
a) placing orders with suppliers for raw materials, supplies, spare parts, tools, equipment and
other required materials;
b) monitoring progress of purchases and reporting to requisitioners;
c) releasing incoming invoices for payment after arrival and approval of goods;
d) collecting and processing of unit requests for raw materials, spare parts, etc., for order
placement to vendors.
The functions of procurement typically generate or modify the expected material and energy
delivery schedules for use in other control functions.
The functions of quality assurance typically generate or modify the following information for use
in other control functions.
Some of the functions within quality assurance may be inside the MO&C domain, based on local
organizational structures; for example, quality assurance requests. Therefore, selected data
flows into and out of quality assurance are addressed because they may cross the enterprise-
control system boundary.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The functions of product inventory control typically generate or modify the following information
for use in other control functions.
Some of the functions within product inventory control may be inside the MO&C domain, based
on local organizational structures. Therefore, selected data flows into and out of product
inventory control are used because they may cross the enterprise-control system boundary.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
e) calculating and reporting on total production cost, reporting cost results to production for
adjustment;
f) setting cost objectives for materials and energy supply and distribution.
The functions of cost accounting typically generate or modify the following information for use in
other control functions.
a) organizing transport for product shipment in accordance with accepted orders requirements;
b) negotiating and placing orders with transport companies;
c) accepting freight items on site and releasing material for shipment;
d) preparing accompanying documents for shipment (BOL, customs clearance);
e) confirming shipment and releasing for invoicing to general accounting;
f) reporting on shipping costs to product cost accounting.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
6.4.10 Maintenance management (10.0)
The functions of maintenance management typically generate or modify the following information
for use in other control functions.
1) Maintenance schedules that specify the plan for future work orders.
2) Maintenance work orders that specify specific equipment to be taken out of service and
made available for maintenance functions.
3) Diagnostic and self-test requests to be performed on the equipment.
Some of the functions within maintenance management may be inside the MO&C domain, based
on local organizational structures. Therefore, selected data flows into and out of maintenance
management are shown because they may cross the enterprise-control system boundary.
The information flows between the functions that are labeled in Figure 7 are listed below.
6.5.2 Schedule
The schedule information flows from the production scheduling (2.0) functions to the production
control (3.0) functions.
This typically contains the information, to production, on what product is to be made, how much
is to be made, and when it is to be made. Details of the schedule information are defined in the
Part 2 object models.
The production-from-plan information flows from the production control (3.0) functions to the
production scheduling (2.0) functions.
This contains information about the current and completed production results from execution of
the plan. It typically contains what was made, how much was made, how it was made, and when
it was made. Details of the production-from-plan information are defined the Part 2 object
models.
The production capability information flows from the production control (3.0) functions to the
production scheduling (2.0) functions.
Production capability information is the current committed, available, and unattainable capacity
of the production facility. This typically includes materials, equipment, labor, and energy. Details
of the production capability information are defined in the Part 2 object models.
The material and energy order requirement information flows from the material and energy
control (4.0) functions to the procurement (5.0) functions.
Material and energy order requirements define future requirements for materials and energy
required to meet short-term and long-term requirements based on the current availability.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
There are no object models for the material and energy order requirements, but the information
may use the definitions relating to material and energy defined in the Part 2 object models.
The incoming order confirmation information flows from the material and energy control (4.0)
functions to the procurement (5.0) functions.
Incoming order confirmations are the notification that the material or energy has been received.
This information is not defined in the Part 2 object models because it does not cross the
interface between the enterprise and MO&C domains.
The long-term material and energy requirements information flows from the production
scheduling (2.0) functions to the material and energy control (4.0) functions.
The long-term material and energy requirements are typically time-sequenced definitions of
material and energy resources that will be needed for planned production.
There are no object models for the long-term material and energy requirements, but the
information may use the definitions relating to material and energy defined in the Part 2 object
models.
The short-term material and energy requirements information flows from the production control
(3.0) functions to the material and energy control (4.0) functions.
The short-term material and energy requirements are requirements for resources that are needed
for currently scheduled or executing production. These typically include
Material and energy requirements are defined in the Part 2 object models.
The material and energy inventory information flows from the material and energy control (4.0)
functions to the production control (3.0) functions.
The material and energy inventory information flows are the currently available material and
energy that is used for short-term planning and for production. This information typically deals
with raw materials. Material and energy inventory information is defined in the Part 2 object
models.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The production cost objectives information flows from the product cost accounting (8.0) functions
to the production control (3.0) functions.
Production cost objectives are the production performance targets in terms of resources. This
could be related to a product or to a process. This typically includes materials, labor hours,
energy, equipment usage, or actual costs. Elements of the production cost objectives are defined
in the Part 2 object models.
The production performance and costs information flows from the production control (3.0)
functions to the product cost accounting (8.0) functions.
Production performance and costs are the actual use and results associated with specific
production activities. This typically includes materials, labor hours, energy, and equipment
usage. Results are typically identified by products, by-products, co-products, and scrap. This
information would be in sufficient detail to identify all costs by product, co-products, and scrap.
Production performance is defined in the Part 2 object models.
The incoming material and energy receipt information flows from the material and energy control
(4.0) functions to the product cost accounting (8.0) functions.
Incoming material and energy receipt is the notification that the material or energy has been
received and additional information needed for cost accounting. This may include the BOL,
material safety data sheet (MSDS), and COA. This information is coordinated with the incoming
order confirmation (6.5.6) information flow.
This information is not detailed in the Part 2 object models because it generally does not cross
the interface between the enterprise and MO&C domains.
The quality assurance (QA) results information flows from the quality assurance (6.0) functions
to the product inventory control (7.0) functions, material and energy control (4.0) functions, and
the production control, operations control (3.2) functions.
Quality assurance results are typically the results from QA tests performed on raw materials, in-
process materials, or products. Quality assurance results may concern tests performed in the
product or in-process tests performed in a particular segment of production. Quality assurance
results may include granting of in-process waivers.
A positive QA result may be required before product inventory management may ship a product.
A positive QA result may be required before production control transfers product-to-product
inventory control.
Details of quality assurance results are defined in the Part 2 object models.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The standards and customer requirements information flows from the marketing and sales (12.0)
functions to the quality assurance (6.0) functions, and from quality assurance (6.0) to production
control (3.0).
Standards and customer requirements are the specific values for attributes of the product that
satisfy the customer needs. This typically includes specific processing specifications as well as
material properties. This information may result in changes in or additions to material,
equipment, and personnel properties and associated tests.
Details of standards and customer requirements are not defined in the Part 2 object models.
The product and process requirements information flows from the research, development and
engineering (RD&E) (13.0) functions to the production control (3.0) functions and the quality
assurance (6.0) functions.
The product and process requirements define how to make a product. These typically correspond
to general or site recipes in batch manufacturing, bills of materials, assembly instructions and
drawings in discrete manufacturing, and process descriptions in continuous manufacturing.
Information about specific equipment, personnel, and material requirements may be specified
according to the object models defined in Part 2.
Details of product and process requirements are defined in the Part 2 object models for product
definitions.
Finished goods waiver information flows from the order processing (1.0) functions to the quality
assurance (6.0) functions.
Finished goods waivers are approvals for deviation from normal product specifications. Finished
goods waivers may be negotiated customer deviations from specifications defined in the
standards and customer requirements (6.5.14).
Details of finished goods waiver are not defined in the Part 2 object models.
In-process waiver request information flows from production control (3.0) to the quality
assurance (6.0) functions.
In-process waiver requests are requests for waivers on normal production procedures due to
deviations in materials, equipment, or quality metrics, where normal product specifications are
maintained. The response to the request is in the quality assurance results.
Details of in-process waiver requests are not defined in the Part 2 object models.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The finished goods inventory information flows from the product inventory control (7.0) functions
to the production scheduling (2.0) functions.
The finished goods inventory is information on the current inventory of finished goods that is
maintained by product inventory control. This typically includes quantity, quality, and location
information that is used for the scheduling of new production, and as feedback on previously
scheduled production. This is the total finished product available for distribution or shipment.
Finished goods inventory is defined in the Part 2 object models.
The process data information flows from the production control (3.0) functions to the product
inventory control (7.0) functions and the quality assurance (6.0) functions.
Process data is information about production processes, as related to specific products and
production requests, and is described in the Part 2 object models. Typical uses of process data
are by quality assurance as part of the QA functions, and by product inventory control where this
information is needed as part of the finished product deliverables.
The pack-out schedule information flows from the production scheduling (2.0) functions to the
product inventory control (7.0) functions.
A pack-out schedule is the consolidation of produced items of one or more stock-keeping unit for
delivery to customers, inventory, or others.
Details of pack out schedules are defined in the Part 2 object models.
The product and process information request flows from the production control (3.0) functions to
the RD&E (13.0) functions.
A product and process information request is a request for new or modified product definitions
and process definitions.
Details of product and process information requests are defined in the Part 2 and Part 5 object
models.
The maintenance request information flows from the production control (3.0) functions to the
maintenance management (10.0) functions.
Maintenance requests are requests for a maintenance function. This may be a planned request
or an unplanned request due to an unplanned event, such as a lightning strike on a transformer.
Details of maintenance request information are defined in the Part 2 object models.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The maintenance response information flows from the maintenance management (10.0) functions
to the production control (3.0) functions.
Maintenance responses are the logged status or completion of routine, scheduled, or unplanned
maintenance.
Details of maintenance responses information are defined in the Part 2 object models.
Maintenance standards and methods information flows from the production control (3.0)
functions to the maintenance management (10.0) functions.
Maintenance standards and methods are typically accepted practices and procedures that
maintenance uses in performing its functions.
Details of maintenance standards and methods information are defined in the Part 2 object
models.
Maintenance technical feedback is typically information about the performance and reliability of
production equipment and may include reporting on performed maintenance. Reports on
maintenance may include scheduled, preventive, or predictive.
Details of maintenance technical feedback information are defined in the Part 2 object models.
Product and process technical feedback information flows from the production control (3.0)
functions to the RD&E (13.0) functions.
Product and process technical feedback is information about the performance of production
equipment and product. This information generally results from performance tests and study
requests to operations control.
Details of product and process technical feedback information are defined in the Part 2 object
models.
Maintenance purchase order requirements information flows from the maintenance management
(10.0) functions to the procurement (5.0) functions.
Maintenance purchase order requirements are information about materials and supplies required
to perform maintenance tasks.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Details of maintenance purchase order requirements information are not defined in the Part 2
object models.
Production order information flows from order processing (1.0) functions to production scheduling
(2.0) functions.
Production order is information about accepted customer orders that defines work for the plant.
Details of production order information are defined in the Part 2 object models.
6.5.29 Availability
Availability information flows from the production scheduling (2.0) functions to the order
processing (1.0) functions.
Release to ship information flows from the product shipping administration (9.0) functions to the
product inventory control (7.0) functions.
Details of release to ship information are defined in the Part 2 object models.
Confirm to ship information flows from the product inventory control (7.0) functions to the product
shipping administration (9.0).
Details of confirm to ship information are defined in the Part 2 object models.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
7 Manufacturing operations
The manufacturing operations management activities correspond to the activity set defined in
6.3. These are the activities contained within the heavy dotted line shown in Figure 8. The heavy
dotted line is equivalent to the Level 3/Level 4 interface defined in 5.2.1. Manufacturing
operations management shall be modeled using four categories: production operations
management, maintenance operations management, quality operations management and
inventory operations management, as shown in shaded areas in Figure 8.
NOTE 1 There are also other activities of a manufacturing facility, not shown in Figure 8, but described in
Annex A.
NOTE 2 The model structure and categories do not reflect a business organizational structure within a company
but is a model of activities. Different companies assign responsibilities for categories, activities or sub-
activities to different business organizational groups. Refer to Part 3 for a generic activity model which
can be applied to other categories of activities.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Order
Processing
(1.0) Product Cost Product
Accounting Shipping Admin
(8.0) (9.0)
Production
Scheduling
(2.0) PRODUCTION
OPERATIONS
MANAGEMENT
INVENTORY
Material and Production OPERATIONS Product
Energy Control Control MANAGEMENT
Inventory Control
(4.0) (3.0) (7.0)
INVENTORY
OPERATIONS QUALITY
MANAGEMENT OPERATIONS
MANAGEMENT
Procurement Quality
MAINTENANCE Assurance
(5.0)
OPERATIONS (6.0)
MANAGEMENT Marketing
& Sales
Maintenance
Management Research
(10.0) Development
and Engineering
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
These supporting activities include:
a) Management of security within manufacturing operations.
b) Management of information within manufacturing operations.
c) Management of configurations within manufacturing operations.
d) Management of documents within manufacturing operations.
e) Management of regulatory compliance within manufacturing operations.
f) Management of incidents and deviations within manufacturing operations.
The definition of the supporting activities is not in the scope of this standard, because they often
are enterprise wide, however requirements for the activities as they relate to manufacturing
operations are briefly described in Annex A.
8 Information model
Subclause 8.2 is an overview of the information contained in the object model and provides a
context for the object models. It includes the general categories of information formally defined in
Part 2.
The production schedule, production performance, product definition, and production capability
information for production operations management are defined in additional detail in Subclause
8.3 and later.
There are equivalent information structures for maintenance, quality test and inventory
operations management that are of importance for manufacturing operations and are defined in
Part 2 using a generic model.
The methods and activities associated with conversion and transformation within Level 3 of the
business representations to the Level 3 detailed work representations are defined in Part 3.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
There are four categories of manufacturing operations information that correspond to the four
categories of manufacturing operations activities. The information corresponds to four major
types of information as shown in Figure 9:
a) Schedule and request information – Information about requests to perform work within one or
more categories of activities.
b) Performance and response information – Information about work performed within one or
more categories of activities.
c) Capability information – Information about the capabilities to perform work within one or more
categories of activities.
d) Definition information – Information about the definition of work that could be performed
within one or more categories of activities.
Manufacturing
operations management
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Production Maintenance Quality Inventory
operations operations operations operations
management management management management
Product Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
definition definition definition definition capability capability capability capability
references C E A
B
E references
C E A
D C Production Parameters
Equipment Requirement
A Product Parameters Material Requirement
Equipment Specifications Personnel Requirement
Material Specifications
Parameters Personnel Specifications
Equipment Segment Actual
Material E
Personnel C A
reference
Production Data
Equipment Actual
Material Actual
Personnel Actual
Most of the production operations management information described in the Clause 6 model fall
into the following four main areas.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Production Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
schedule request request request performance response response response
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Production Maintenance Quality Inventory
operations operations operations operations
management management management management
Product Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
definition definition definition definition capability capability capability capability
Some information in each of these four areas is shared between the manufacturing operations
and control systems and the other business systems, as illustrated Figure 12. Venn diagrams
are used to illustrate the overlap of information. This standard is only concerned with the
overlapping information in the Venn diagrams, and with presenting a model and common
terminology for that information.
Manufacturing operations
management information
Production operations, maintenance
operations, quality operations, etc
There are three main areas of information about the production capability that have significant
overlap. The three areas of information are production capability information, maintenance
information, and capacity scheduling information. Figure 13 illustrates the overlapping
information.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Production Maintenance
Capability Information
Information
Scheduled Production equipment availability
Capacity
Scheduling
Information
Production Capacity
Figure 13 – Production capability information
For each site, area, and element within the area there is a presentation of the production
capability of the personnel, equipment, and materials.
The production capability information includes the current capacity, the future expected capacity
of the resource, and a history of capacity of the resource.
The collection of predicted or forecast available capacity, committed capacity, and unattainable
capacity shall be shown as production capacity, as depicted in Figure 14.
The production capacity is the theoretical maximum capability available for use in production.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Past capacity that represents actual use history shall be shown as used or unused capacity
EXAMPLE 1 Used capacity may be compared against predicted committed capacity to visualize time dependent
efficiencies.
Production Capacity
Unused Capacity Unattainable Capacity
Capacity
Available Capacity
Used Capacity
Committed Capacity
c) Committed capacity defines resources that are committed to future production or were
committed to past production, usually due to existing schedules and/or materials in
production.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Unattainable capacity defines resources that are not attainable for future production given the
equipment condition, equipment utilization, personnel availability, and material availability.
EXAMPLE 2 Unattainable equipment capacity due to equipment condition may occur because of equipment out of
service for maintenance
EXAMPLE 3 Unattainable equipment capacity due to equipment utilization may occur because 75 % of a vessel is
filled and the other 25 % is not available for other products
EXAMPLE 4 Unattainable personnel capacity may occur because of vacation schedules
Available capacity defines the resources that are available for additional future production and
not committed to production.
Capacities may have a confidence factor, as illustrated in Figure 15.
NOTE 2 Confidence factors may be used by planning and scheduling in the development of possible and
alternate schedules based on an acceptable level of risk.
Used Capacity is a historical value that defines the portion of the production capacity that was
used to make acceptable quality product.
Unused Capacity is a historical value that defines the portion of the production capacity that was
not used to make acceptable quality product. An unused capacity may have one or more
reasons for the unused capacity, as illustrated in Figure 16.
EXAMPLE 5 One portion of an unused capacity may be unused because of no scheduled production. Another
portion of the unused capacity may be unused because of production of unacceptable quality product.
Another portion may be unused because of equipment not available.
NOTE 3 Unused Capacity (no scheduled production) or Unused Capacity (Quality Unacceptable) may be a
concern for some entities and respective Key Performance Indicators may show resources available
but not utilized to manufacture a viable product.
Committed, Unattainable, and Available capacity may be defined for past times, as a history of
expected use, and for future times, as a prediction. Used and unused capacity may be defined
for past times.
Future Time
Figure 15 – Future capacity confidence factor
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Capacity
Used Capacity
Past Time
Figure 16 – Past capacity unused capacity reasons
For each site, area, and element within the area there is a listing of the equipment as required
for maintenance. This includes maintenance records and other information that is not part of the
production capability model.
The maintenance information includes the current maintenance state of the equipment.
The capacity scheduling information contains the process segments available for the production
unit, process cell, or production line.
For each site, area, and equipment element within the area there is a presentation of the
production capacity of the personnel, equipment, and materials needed for scheduling of
production.
Production equipment status is information derived from the capability information of the
equipment and the maintenance information. This includes the listing of the equipment, the
current status of the equipment, and the usage history of the equipment.
Production capacity is defined as the information derived from production capability information
and (product specific) capacity scheduling information. This includes the listing of the capacity
scheduling product definition information and current status and expected future status of the
personnel, equipment, and materials capabilities.
A capability may be given in terms of a process segment. Process segments show the business
view of a part of the manufacturing process. The capabilities may specify specific capabilities or
the class of capability (such as class of equipment) needed for the process segment. Figure 17
illustrates how capabilities relate to process segments.
– A manual process segment may define the class of materials and class of personnel needed
for production.
– A semi-automated process segment may define the class of materials, personnel, and
equipment needed.
– A non-material process segment, such as an equipment set-up segment, may define the
class of equipment and personnel used.
– An automated process segment may only define the material and equipment classes needed.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
There are three main areas of information required for the production of a specific product that
have significant overlap. The three areas are information for scheduling, material information,
and production rules. Figure 18 illustrates the overlapping information.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Production
Rules
Material information on a specific product, including
information not related to production (e.g. shipping
materials)
Bill Of
Scheduling information on a specific product,
Material including information that is not related to production
(e.g. material order lead times)
Bill Of
Resources
Product production rules are the information used to instruct a manufacturing operation how to
produce a product.
NOTE: Examples of product definition rules are a general site or master recipe (IEC 61512-1 definitions), product
data AP (application protocol) as defined in ISO 10303-1, standard operating procedure (SOP), standard
operating conditions (SOC), routing, or assembly steps based on the production strategy used.
The BOM is a list of all materials required to produce a product showing the quantity of each
required. These may be raw materials, intermediate materials, subassemblies, parts, and
consumables. This list does not contain the breakdown of where the materials are used or when
they are needed, but it may be organized in a hierarchical manner that maps to some of the
production steps. The bill of material often includes material that is not related to production of
the product, such as shipping materials or included documentation. The bill of material is a
subset of the bill of resources.
The manufacturing bill is the subset of the bill of material that is related to production.
The bill of resources is the list of all resources required to produce a product. Resources may
include materials, personnel, equipment, energy, and consumables. The bill of resources does
not contain the specific production steps, but it may be organized in a hierarchical manner that
maps to some of the production steps.
Product segment is the overlap of information between product production rules and the bill of
resources. It describes a job or task consisting of one or more work elements, usually carried out
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
essentially in one location. A product segment is the most detailed process view for the business
system to control material, labor, resource usage, cost, and quality in order to control the
production.
A product segment shall reference a process segment. This relationship is illustrated in Figure
19.
a) IEC 61512-1 process stages, process operations, unit procedures, or operations for batch
manufacturing;
b) production unit operations for continuous manufacturing;
c) assembly steps and assembly actions for discrete manufacturing;
d) other types of identifiable time spans for other types of manufacturing.
The example in Figure 20 illustrates nested product segments in a Gantt-type chart with time on
the horizontal axis and each box corresponding to a different product segment.
Production routing is the overlap of information between the product production rule information
and bill of resources information without the bill of material information. It represents all of the
non-material aspects of production such as equipment, labor, and energy. Production routings
include an ordered sequence of product segments.
Material routing is the overlap of information between the production rule information and the bill
of material information. It represents both the production material inputs and where they are
used in product segments.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Clean
Strawberries
Clean
Blueberries
Fill Bottles
Pack Bottles
Time Line
Figure 20 – Example of nested product segments
Figure 18 illustrates the overlap of information between different areas but is not meant to
represent the amount or importance of the information. Different manufacturing and business
strategies will have different amounts of information shared between the different areas. Figure
21 illustrates the amount of information in two examples. The left side of the figure shows an
example where the manufacturing systems maintain most of the information required for a
product. The right side of the figure shows an example where the business systems maintain
most of the information.
Product
Bill Of Product Bill Of
Production
Resources Production Resources
Rules
Rules
There are three main areas of information about actual production that have significant overlap.
These three areas are production history information, production resource information, and the
production scheduling information. Figure 22 shows the overlap between the areas of
information.
Production
Scheduling
Scheduling information on production
Production Information
Segment
Information
Production history information is all of the information recorded about the production of a
product. This may be called by many names, such as the batch journal, product log, or traveller.
Production resource information is all of the information about inventoried materials, equipment,
personnel, and other resources.
Typically, all consumed and produced materials are maintained in the production resource
information, and sometimes intermediates are maintained if they are needed for financial
evaluation. In some industries this may include energy information.
The scheduling model contains all of the information about the execution of scheduled
production runs.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The production resource history information is the part of the production history information that
contains information on resources that has been used in Production.
9.1 Completeness
9.2 Compliance
a) Any assessment of the degree of compliance of a specification shall be qualified by a
statement of the degree to which they then conform partially or totally to definitions.
b) In the event of partial compliance, areas of non-compliance shall be explicitly identified.
NOTE: This part of the standard does not enumerate compliance points sufficient to form a conformity
assessment scheme. Additional specifications are required to define specific compliance elements
needed to meet a specific technical regulation or directive.
9.3 Conformance
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Annex A
(informative)
In addition to the major activities already described, there are other activities that are used within
manufacturing operations, but are not necessarily unique to the manufacturing element of a
company. These supporting activities include, but are not limited to,
Figure A.1 illustrates the concept of the supporting activities and their relationship with the major
manufacturing operations activities. For example, there may be an aspect of management of
information used in production data collection, production resource management, production
tracking, production definition management, maintenance definition management and quality test
data collection.
Level 4
Level 3 Inventory
Operations
Management Management
Major Activities
of Information of Configuration
Maintenance Quality
Management Within Manufacturing
Management
Operations Operations of Security
of incidents and
deviations
Operations
Production Management Management
Operations of Documentation of Compliance
Management of security is an enterprise function and is not defined in this standard but does
impact manufacturing operations management. Security management functions include physical
(site and area) security, information security and computer security. The basic role of security in
manufacturing operations is to make sure that only authorized personnel may make changes or
affect manufacturing in allowed ways. This typically involves physical security to limit access to
facilities, control of information flows out of a facility to protect intellectual property and control of
communications to ensure that unauthorized remote access does not affect operations.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
NOTE Management of security is often combined with management of networks. The current recommend practice is
to ensure that networks used in production operations, especially those involved in physical control of
processes, are separate from non-real-time networks. This separation may be physical, through different
networks or network standards, or virtual through protocols, firewalls and routers. Real-time control requires
predictable network responsiveness and latency, which is best accomplished through the separation of
networks.
When policies and procedures for management of security do not exist on a company-wide basis,
then security control can be considered a manufacturing operations activity, for manufacturing
security.
Potentially relevant standards for security relating to communications and computer systems are
listed in Annex B.
Management of information is an enterprise function and not defined in this standard but does
impact manufacturing operations management. In fact, most of the manufacturing operations
activities consume and generate information as part of their function. Many functions must
exchange information with other functions that are not listed this standard.
When policies and procedures for management of information do not exist on a company-wide
basis, then information control can be considered a manufacturing operations activity, for
manufacturing information.
Management of configuration is often an enterprise function and is not defined in this standard
but does impact manufacturing operations management. Management of configuration includes
configuration management and change control procedures that should be considered in
manufacturing operations. This function may be required any place there is a semi-permanent
data storage and actions can be taken based on the stored data. Often audit trails and revision
management procedures are required.
EXAMPLE 1: This may include product definitions, work instruction, standard operating procedures, product and
process definitions, resource class definitions.
EXAMPLE 2: This may include management of Level 2 information such as PLC programs and DCS configurations.
When policies and procedures for management of configurations do not exist on a company-
wide basis, then configuration control can be considered a manufacturing operations activity, for
manufacturing configurations.
One aspect of configuration management involves the processes and procedures necessary to
implement changes to configuration elements that may comprise the production operations. This
includes identification, surveillance and control of changes to these configurable items. This
includes, but is not limited to,
One aspect of change control involves processes or procedures by which changes are initiated
and managed. These procedures often include the following:
Potentially relevant standards for management of configuration include are listed in Annex B.
Management of documents is often an enterprise function and is not defined in this standard but
does impact manufacturing operations management. Manufacturing operations need to manage
a wide range of documents. These include items such as SOPs, work instructions, recipes,
control system programmes, drawings, batch records, engineering change notices, alarm logs
and exception reports. Management of this information is often required for regulatory,
environmental, health and safety, or certification reasons. Generally companies have a set of
procedures, policies and software tools in place to manage all corporate documents.
When policies and procedures for management of documents do not exist on a company-wide
basis, then document control can be considered a manufacturing operations activity, for
manufacturing documentation.
after disasters so that operators can physically recreate production lines in the event of
unforeseen disasters.
The broad footprint of management of regulatory compliance means that many areas of the
enterprise can be significantly affected. Failures in regulatory compliance can stop production,
force product recalls and potentially cause safety problems. Where management of regulatory
compliance activities involves the quality and safety of production, then the activities are in the
scope of production operations.
When policies and procedures for management of regulatory compliance do not exist on a
company-wide basis, then compliance control can be considered a manufacturing operations
activity, for manufacturing compliance.
Figure A.2 illustrates some of the aspects of regulatory compliance and general activities
associated with each aspect.
Material Safety
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Employee
Data Sheet
Tracking
Chemical Authoring
Inventory and Labeling Facilities
Industrial Hygiene Air, Waste, and
Management Management Management Water Emissions
Trade & Shipping
Tracking
Hazardous Tracking and Equipment Safety
Occupational
Materials Compliance Incident Tracking
Health and
Safety Tracking and Prevention
Management of
Regulatory Compliance
Local Environmental
Environmental Regulatory Control
Regulatory Control
f) liability and management practices including civil and criminal liability and contaminated land
liability;
g) typical health and safety activities including
h) handling, classification, packaging and labelling of hazardous substances including safety
data sheets;
i) disaster planning including emergency planning and response and fire safety;
j) hazard communication in the form of warning signs, training and advice;
k) occupational health surveillance in the form of occupational exposure controls (including
chemical, physical, biological agents and noise);
l) medical surveillance of personnel;
m) process safety in the form of machinery safety, lifting equipment, pressure systems,
confined space entry/work permits/access control;
n) management of functional safety;
o) electrical safety;
p) ergonomics including office work, manual handling of loads and the like;
q) first aid.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Potentially relevant standards related to regulatory compliance are defined in Annex B.
Management of incidents: Maintaining plant operation often requires that unexpected events,
called incidents, are recorded and that the response to the incident is recorded. Incidents are
typically unexpected events related to maintaining plant operations, safety, regulatory
compliance, or security. Incident management typically involves investigation to determine the
root cause of the incident and may lead to preventive actions to prevent future incidents.
EXAMPLE 1: An unexpected release of a chemical into the environment may generate an incident and the incident
report may have to be sent to the appropriate regulatory agency, such as the US EPA.
EXAMPLE 2: An unexpected pump failure from a newly installed pump may generate an incident and the incident
response may be to investigate and potentially change the supplier.
Management of deviations: Maintaining plant operations often requires that deviations that have
been detected because of normal conditions are recorded and that the response to the deviation
is recorded. Deviations are typically measured differences between an observed value and an
expected or normal value, or an anomaly from a documented standard or process. Deviation
management typically involves determination of the root cause of the deviation and may lead to
corrective actions to remove the source of the deviation.
Management of corrective actions and preventive actions: Maintaining plant operations often
requires that corrective actions, typically in response to an incident, deviation, or failure, are
recorded and managed and that the results of the corrective action are recorded. Clear,
appropriate and implementable corrective actions should be identified at the conclusion of any
investigation. Tracking and follow-up should be managed to ensure that the corrective actions
are implemented and verified.
EXAMPLE 3: Corrective actions may include improving procedures, adding maintenance procedures for equipment, or
implementing retest or revalidation procedures.
Preventative actions are typically managed in a similar fashion, in order to prevent possible
future incidents or deviations.
EXAMPLE 4: Batch cycle times on a process cell may not meet the rated value and this is identified as a deviation;
then, a preventive action is created to reduce the batch cycle time.
Recommended actions are managed in a similar function. Recommended actions are predefined
sets of actions to occur in the event of an incident or deviation.
--`,,,,``,`,`,,`,```,
Annex B
(informative)
Associated standards
The following standards may apply to the common enterprise activities of management of
security.
The following standards may apply to the common enterprise activities of management of
configurations.
FDA 21 CFR Part 210, Current Good Manufacturing Practice in Manufacturing, Processing,
Packaging, or Holding of Drugs; General
The following standards may apply to the common enterprise activities of management of
documentation. Potentially relevant standards for document management include the following.
IEC 60417, Graphical symbols for use on equipment IEC 60617, Graphical symbols for diagrams
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
IEC 61175:2005, Industrial systems, installations and equipment and industrial products –
Designations for signals and connections
IEC 61286:2001, Information technology – Coded graphic character set for use in the preparation
of documents used in electrotechnology and for information interchange
IEC 61346-1:1996, Industrial systems, installations and equipment and industrial products –
Structuring principles and reference designations – Part 1: Basic rules
IEC 61346-4:1998, Industrial systems, installations and equipment and industrial products –
Structuring principles and reference designations – Part 4: Discussions of concept
IEC 61355:1997, Classification and designation of documents for plants, systems and equipment
IEC 61360-1:2002, Standard data element types with associated classification scheme for
electric components – Part 1: Definitions – Principles and methods
IEC 61360-2:2002, Standard data element types with associated classification scheme for
electric components – Part 2: EXPRESS dictionary schema
IEC 61360-4, Standard data element types with associated classification scheme for electric
components – Part 4: IEC reference collection of standard data element types and component
classes
IEC 61666:1997, Industrial systems, installations and equipment and industrial products –
Identification of terminals within a system
IEC 61734:2006, Application of symbols for binary logic and analogue elements
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
IEC 81714-2:2006, Design of graphical symbols for use in the technical documentation of
products – Part 2: Specification for graphical symbols in a computer sensitive form, including
graphical symbols for a reference library, and requirements for their interchange
IEC 81714-3:2004, Design of graphical symbols for use in the technical documentation of
products – Part 3: Classification of connect nodes, networks and their encoding
ISO 81714-1:1999, Design of graphical symbols for use in the technical documentation of
products – Part 1: Basic rules
The following standards may apply to the common enterprise activities of management of
regulatory compliance.
ISO 14001:2004, Environmental management systems – Requirements with guidance for use
ISO 14025:2006, Environmental labels and declarations – Type III environmental declarations –
Principles and procedures
ISO 14041:1998, Environmental management – Life cycle assessment – Goal and scope
definition and inventory analysis
ISO 14042:2000, Environmental management – Life cycle assessment – Life cycle impact
assessment
ISO 14043:2000, Environmental management – Life cycle assessment – Life cycle interpretation
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
ISO 19011:2002, Guidelines for quality and/or environmental management systems auditing
ISO 10006:2003, Quality management systems – Guidelines for quality management in projects
ISO 10014:2006, Quality management – Guidelines for realizing financial and economic benefits
ISO 19011:2002, Guidelines for quality and/or environmental management systems auditing
Annex C
(informative)
C.1 Purpose
This annex contains a collection of business drivers and key performance indicators (KPI) or
issues that have been defined, and used as the potential touch points into the business
processes of the users of the standard. These are also called Critical Success Factors. The
drivers were used to test the informational content included within the standards. They
determined if the communications model adequately addressed the business issue associated
with integration.
These business drivers are identified as being critical to the success of the operations of
manufacturing companies across a variety of industries. The drivers have been clarified and
validated with operating companies and vendors companies. The drivers provide users with the
basis from which to determine the usage of the standard based on their particular industry and
information system needs.
C.2 History
Key business drivers are the areas of performance that are most critical to an organization's
success. Key business driver is a term used in connection with strategic planning and related
goal setting. Key business drivers refer to principal organization-level requirements (similar to
Mission Essential Task List, or METL, in tactical units), derived from short- and long-term
strategic planning. They include customer-driven quality requirements and operational
requirements such as productivity, cycle time, deployment of new technology, strategic alliances,
supplier development, and research and development. In simplest terms, key business drivers
are those things the organization has to do well for its strategy to succeed (see Bibliography).
Business drivers, in a manufacturing facility, generate the need for information to flow between
the executive offices and the process or manufacturing floor. Enterprises focus on these
business drivers to meet competitive requirements in the marketplace. Business drivers
subsequently influence information sent to the production floor or are influenced by information
gathered from the production floor.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Business drivers and some information demands have been identified. Additional research and
work may be required to clarify the scope and definition of the drivers and information demands
for particular user requirements.
There is always some business process that needs information from production, or needs to
exercise control of production that drives the need for integration. Integration requires that the
production information can be mapped back to the business information.
Manufacturing enterprises are typically dynamic entities. There are continual changes in
business processes to meet changing business and legal environments. There are also usually
continual changes in production processes, as new technologies and advances in production
capabilities emerge. The purpose of this standard is to aid in the separation of the business
processes from the production processes. The standard describes information in a way that is
business-process independent and production-process independent. Figure E.1 illustrates this
concept of a common model that bridges the different business and production processes.
IEC 62264-1
PDXI
NAMUR IEC 61512 SME
Another value of the standard to business is the separation of exchanged information from
specific implementations of manufacturing operations and control systems and specific
implementations of business management systems. Manufacturing operations and control
systems change when the production processes change, when factories are bought or sold, or
when control equipment is updated or replaced. Likewise, business management systems
change due to corporate mergers, sell-offs, technology changes, or business or legal changes.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
Some terms or labels that describe such business drivers include the following.
Cycle time is defined as the time it takes to produce a product from the time the order is placed.
Cycle time refers to responsiveness and completion time measures – the time required to fulfill
commitments or to complete tasks (see Bibliography).
The reason that businesses concentrate on minimizing the total cycle time is generally to
increase inventory turns. This has the net result of increasing a business's ROA (return on
assets).
To reduce cycle time a business identifies areas where most of the delay and waiting occurs and
addresses them appropriately. In most cases, the time needed to plan and react to changes is
much longer than the time to build. Response time improvement requires all aspects of the
planning, scheduling and execution to be taken into account. Reducing the time to plan allows
more frequent analysis of forecasts and less dependence on forecasting data.
Asset efficiency is a focus on maximizing the effective and cost-effective use of assets in the
production of products. The information obtained from the production environment will deliver to
an enterprise realistic information on the production capabilities of the plant, train, unit, work cell,
etc. Asset efficiency is the desire to better utilize the assets of a company. It usually involves all
assets of a company, production, service, administration, support, sales, and marketing. Asset
efficiency improves a company's ROA.
Agile manufacturing is the ability to reconfigure production assets to meet market demand
quickly. This requires the ability to change production using existing plants and equipment.
Agile enterprises may be supported by a networked infrastructure that can link multi-company
teams into an integrated virtual corporation.
Agile manufacturing requires that production can quickly respond to changes in product definition
and sometimes even change product production processes in mid-stream.
The aim of supply chain management (SCM) is for each player in the supply chain to conduct
business with the latest and best information from everyone else in the chain, guiding supply and
demand into a more perfect balance. The purpose is to move product from the point of origin to
that of consumption in the least amount of time and at the smallest cost.
Supply chain management helps managers do such things as integrate retail channels with
manufacturing, drive demand from the point of sale, or eliminate inventory buffers in the
distribution chain. SCM extends beyond the walls of the enterprise to suppliers and distributors.
Supply chain management moves to supply chain optimization when the supply chain is used to
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
maximize the effectiveness of the whole, as well as maximizing the effectiveness of the
individual parts.
Supply chain optimization involves making complex tradeoffs to satisfy business objectives of
reducing operational costs and inventory, improving delivery reliability and response time, and
service to the customer.
Quality and traceability can be a business driver in some businesses. This may be required by
factors such as regulatory compliance, service cost measurement per product improvement,
reliability to customers, and human resources tracking of exposure to hazardous items.
Quality and traceability requires that information that is typically kept within a manufacturing
system be made available to other parts of an enterprise. This often requires integration of
production control and quality assurance, with a corporate quality system.
Empowerment: A condition whereby employees have the authority to make decisions and take
action in their work areas without prior approval. The act of vesting appropriate authority in the
hands of the people nearest the problems needs to be solved.
Improved planning is a key business driver for companies with expensive inventory, time-
consuming production but fast customer changes, and variable demand. Improved planning
requires access and use of information from throughout the corporation to move planning output
from production requests and closer to production schedules.
Improved planning requires continual feedback on actual production and material consumption,
as well as continual feedback on demand and inventories.
C.6.9 Summary
The business driver list is not all-inclusive. Any business driver that impacts cost, capacity,
compliance, time, or analysis could be added to the list. Additionally, informational components
of one business driver will also often be required when addressing other business drivers. The
example in Clause B.6 is a basic situation that may provide a starting point for various business
drivers.
An example of how business drivers and associated production functions generate the need for
information flow throughout the business enterprise is described as follows.
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
The first business driver, available to promise, is a basic business driver. We assume a
manufacturing business. In this business, there are certain functional steps that generate
information flow between the business enterprise (office) and the production floor (control
systems).
We will consider this business to be a general manufacturing facility. In a typical business day,
we have customers who are requesting to buy our product. Armed with information from our
sales personnel, we progress to the manufacturing floor. Here, information generation may be
outlined in the following steps.
h) Current state: Where are we right now? Every business requires knowledge of its current
manufacturing and business situation. This information is defined as production from plan
and production performance and costs in the standard's data flow model.
i) Target state: Where do we want to go? In the normal course of business, new orders may be
received, legal requirements change, and even the weather may have an informational
impact through the business. So, there is information that flows between the business
practices and manufacturing practices. This information is defined as schedule and pack- out
schedule in the standard's data flow model.
j) Transition state: Prior to a change, there is a significant amount of information generated to
anticipate how the changes will be managed. And when things actually change, there is
history gathering of how the changes actually occur. This information is defined as
production performance in the standard's object model.
k) Planning/Scheduling: For this business, the need for information regarding current state,
target state and transition environment may occur may times per week, day or operations
shift. The frequency of schedule update and the frequency of information uploads will depend
This is one method of describing steps that generate information flow between the business
offices and the production floor in an available-to-promise enterprise.
Regardless of the specific business driver and associated functions identified, some of the steps
described in the make-to-order example above are required to meet all business drivers. For
example, many business drivers require the business to know what the current state of its
business is.
C.8 Definitions
This clause presents terms sometimes used in describing key business drivers.
Current state reporting is a collection of information that characterizes the current activity and
conditions that exist in the manufacturing environment. This information is collected for the
purpose of decision support. This information allows you to understand where you are in relation
to current commitments. This information is described in the standard in the current production
capability information. Some other terms often used in current state reporting include
a) production request: information on the current production schedule with respect to the actual
product that has been requested for production;
b) production quantity: how much of the current production request has been completed
(cumulative versus request)?;
c) current rate: what is the instantaneous rate of production of the product requested?;
d) quality: measure of the effectiveness of production - this measurement of product quality,
yields data, waste, loss, yield, material, and energy balance);
e) physical equipment status: information on the maintenance state of the equipment, work
cells, trains, etc., to determine the current and future availability of that equipment for the
production of the next product;
f) predictive maintenance: a predictive determination of when equipment will need
maintenance, and a mechanism to perform maintenance on the equipment at or before its
expected error or failure time;
g) preventative maintenance: performing maintenance before an error or failure occurs, and a
mechanism to perform maintenance, usually on a fixed-time or run-time schedule;
h) inventory status: data on materials that will impact the decision to proceed with the next
product’s production.
Turnaround time is the time required to change a production mechanism for the purpose of
producing a different product or the same product with different characteristics. The information
that will determine the turnaround time includes
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
a) the current state of all items and current state of the production facility;
b) historical transition times, given the current state of the production facility;
c) standard operating procedures required for switchover;
d) resource requirements versus available (labor, material, equipment).
C.8.3 Campaigning
Campaigning is the planning of the execution of production based on the existing capacity, raw
material, resources and production request. A campaign is usually a limited run of product
through the production process. Campaigns can last from days to months depending on the
products, processes, and production requirements. Control strategy and physical process
changes may accompany campaigns.
One important aspect of campaigning is letting production know the sequence of events or
scheduled runs ahead of time.
Campaigns generally deal with a single product, or a set of products with compatible processing
or product requirements. Campaign planning has to also address previous product
characteristics to maximize the agility of the change.
New targets describe what to make in the next time sequence and when to start – mainly an
information demand that the control system places on the enterprise for a production order. New
targets are handled in the standard through the production parameters in a production request.
The type of information required for new targets depends on the industry. New targets can be
fixed numbers in a discrete environment and can be variable values, such as tables or functions,
in continuous environments.
Data reconciliation is a serious issue for enterprise-control integration. The data have to be valid
to be useful for the enterprise system. The data are often determined from physical
measurements that have associated error factors. This is usually converted into exact values for
the enterprise system. This conversion may require manual or intelligent reconciliation of the
converted values. Additional problems occur when the type of physical measurement, such as
volume, is used to calculate information based on a related value, such as weight. For example,
in the refining industry the operations floor changes the density of products, but measures by
volume, then uses inference to calculate density and weight.
Systems have to be set up to ensure that accurate data are sent to production and from
production. Inadvertent operator or clerical errors may result in too much production, too little
production, the wrong production, incorrect inventory, or missing inventory.
Annex D
(informative)
D.1 Introduction
This section contains notes about this standard, basically recorded as notes and emails between
committee members.
QUESTION:
What happened to the information on the Purdue Reference Model that was in the original part
one Annex?
ANSWER:
This annex was moved to a new ISA95 Technical Report that was in development at the time of
this publication.
QUESTION:
What exactly is the role based equipment and physical asset hierarchy? Is it different from how it
relates to the ISA88 equipment physical hierarchy? If so, how?
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
ANSWER:
The role based equipment hierarchy is just a new name for the equipment hierarchy. It is the
same as the ISA88 physical hierarchy. As we added the maintenance activities in Part 3, we
realized that there are two different aspects of equipment, one the control aspect, which is
basically the control role that the equipment performs, and the physical role, which is associated
with the maintenance of the physical equipment.
A lot of people were trying to use the ISA95 (and ISA88) equipment hierarchy in defining the
physical aspect of the equipment, and this resulted in a lot of confusion. For example, a pump
may be considered as a control module in ISA88 and part of a unit in ISA95. However, if the
physical pump was switched out with a different pump, the ISA88/95 equipment hierarchy did not
change (it performed the same role), but the serial number, maintenance record, etc. went with
the old pump.
Another way to think of the two identifiers is using your car as an example. Your car has a VIN
(Vehicle Identification Number) and performs a role (your means of transportation). If you sell
your car and get another, you still have a car performing a role, but the physical car is now
different. Your old car may still exist, and be performing a similar role for someone else.
We identified another hierarchy, the physical asset hierarchy, to handle identification, tracking,
and collections of physical equipment in the maintenance activities. The physical asset hierarchy
matches the hierarchy in the MIMOSA standard.
QUESTION:
How is the physical asset equipment hierarchy different from the ISA88 physical equipment
hierarchy?
ANSWER:
The ISA88 equipment hierarchy is a combination of equipment and control. The equipment is,
however, usually identified by role (for example: Tag Number), so it is the same as the ISA95
role based equipment hierarchy. The ISA95 physical asset hierarchy is identified by the actual
physical equipment (for example: equipment identified by serial number).
QUESTION:
What is the significance of the physical asset equipment hierarchy to the standard; is it related to
financial or cost control? Note 1 states that the physical asset equipment hierarchy usually has
a reference to an accounting hierarchy in a chart of accounts
ANSWER:
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
At one time we had a table of all of the different types of equipment hierarchies in an enterprise.
One of these was the allocation of a physical asset to an account (which department “owns” the
equipment) from a chart of accounts. The chart of accounts hierarchy was out of scope, but the
maintenance hierarchy was in scope.
QUESTION:
ANSWER:
The decision hierarchy was added by IEC in the IEC 62264-1 standard. After IEC/ISO 62264-1
was released, the decision hierarchy was defined in ISO 15704 Industrial automation systems —
Requirements for enterprise-reference architectures and methodologies. The ISA95 update was
based on the IEC 62264-1 standard. However, because there is now a complete standard on the
decision hierarchy it was removed from this standard, but a reference is now made to the ISO
15704 standard.
Bibliography
BALDRIGE, Malcolm, 1996 Award Criteria, National Institute of Standards and Technology, US
Department of Commerce.
BROWN, Mark Graham, How to Interpret the Malcolm Baldrige 1995 Award Criteria, Malcolm
Baldrige National Quality Award 1995 & 1996 Award Criteria, National Institute of Standards and
Technology, US Department of Commerce.
COX III, JAMES F., BLACKSTONE Jr., JOHN H., APICS Dictionary Ninth Edition, APICS – The
Educational Society for Resource Management, Alexandria VA. ISBN 1-55822-162-X (1998).
DEMARCO, T., Structured Analysis and System Specification, Prentice Hall Inc., Upper Saddle
River, NJ (1978).
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
MESA International, MES Functionality and MRP to MES Data Flow Possibilities – White Paper
Number 2 (1994).
MOTARD, R., BLAHA, M., BOOK, N., FIELDING, J., “Process Engineering Databases – from the
PDXI Perspective,” Foundations of Computer-Aided Process Design (FOCAPD), American
Institute of Chemical Engineers, New York, NY (1994).
PAMPEL, Albert, Information Flow Model of a Generic Production Facility, The Foxboro
Company, Foxboro, MA (1986).
PDXI – The Process Data eXchange Institute (PDXI) represents an initiative of the Computing
and Systems Technology (CAST) Division of the American Institute of Chemical Engineers, New
York, NY.
SITTON, O., MOTARD, R., BLAHA, M., GOLDSTEIN, B., HENDRICK, J., FIELDING, J., “The
Road To A Common Byte”, Chemical Engineering, September (1994). [Contains a list of
published references related to PDXI.]
VERNADAT, E.B., Enterprise Modelling and Integration, Chapman and Hall (1996).
WILLIAMS, T.J., The Purdue Enterprise Reference Architecture – A Technical Guide for CIM
Planning and Implementation, ISA, Research Triangle Park, NC (1992).
WILLIAMS, T.J. (Editor), A Reference Model for Computer Integrated Manufacturing (CIM),
A Description From the Viewpoint of Industrial Automation, Minutes, CIM Reference Model
Committee, International Purdue Workshop on Industrial Computer Systems, Purdue University,
West Lafayette, IN (1988) Instrument Society of American, Research Triangle Park, NC (1989).
While out of print at ISA, the complete document is available at:
http://www.pera.net/Pera/PeraReferenceModel/ReferenceModel.html
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---
ISA is an American National Standards Institute (ANSI) accredited organization. ISA administers
United States Technical Advisory Groups (USTAGs) and provides secretariat support for
International Electrotechnical Commission (IEC) and International Organization for
Standardization (ISO) committees that develop process measurement and control standards. To
obtain additional information on the Society’s standards program, please write:
ISA
Attn: Standards Department
67 Alexander Drive
P.O. Box 12277
Research Triangle Park, NC 27709
ISBN: 978-1-936007-47-9
--`,,,,``,`,`,,`,```,,``-`-``,```,,,`---