Isa 95.00.02-2010
Isa 95.00.02-2010
Isa 95.00.02-2010
ISBN: 978-1-936007-48-6
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
-3- ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
CONTENTS
INTRODUCTION ................................................................................................................ 11
1 Scope .......................................................................................................................... 13
2 Normative references ................................................................................................... 13
3 Terms, definitions and abbreviations............................................................................. 14
3.1 Terms and definitions .......................................................................................... 14
3.2 Abbreviations ...................................................................................................... 15
4 Production operations models and generic operations models ....................................... 15
4.1 Information models .............................................................................................. 15
4.2 General modeling information .............................................................................. 17
4.3 Extensibility of attributes through properties......................................................... 17
4.4 Object model structure ........................................................................................ 18
4.5 Explanation of tables ........................................................................................... 18
4.6 Relationship of models ........................................................................................ 21
4.7 Hierarchy scope .................................................................................................. 22
4.8 Value types ......................................................................................................... 23
5 Common object models ................................................................................................ 27
5.1 Personnel information ......................................................................................... 27
5.2 Role based equipment information ....................................................................... 33
5.3 Physical asset information ................................................................................... 40
5.4 Material information............................................................................................. 46
5.5 Process segment information............................................................................... 58
6 Operations management information ............................................................................ 69
6.1 Operations definition information ......................................................................... 69
6.2 Operations schedule information.......................................................................... 84
6.3 Operations performance information .................................................................. 100
6.4 Operations capability information ....................................................................... 116
6.5 Process segment capability information ............................................................. 128
7 Object model inter-relationships ................................................................................. 130
8 List of objects............................................................................................................. 134
9 Compliance ................................................................................................................ 138
Annex A (Normative) Production specific information......................................................... 139
Annex B (Informative) Use and examples .......................................................................... 147
Annex C (Informative) Example data sets.......................................................................... 157
Annex D (Informative) Questions and answers about object use ........................................ 165
Annex E (Informative) Logical information flows ................................................................ 181
Bibliography ..................................................................................................................... 184
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) -4-
Tables
Table 1 — UML notation used............................................................................................. 18
Table 2 — Example table.................................................................................................... 19
Table 3 — Attributes of hierarchy scope .............................................................................. 23
Table 4 — Attributes of personnel class .............................................................................. 28
Table 5 — Attributes of personnel class property................................................................. 29
Table 6 — Attributes of person ........................................................................................... 30
Table 7 — Attributes of person property .............................................................................. 31
Table 8 — Attributes of qualification test specification ......................................................... 32
Table 9 — Attributes of qualification test result.................................................................... 33
Table 10 — Attributes of equipment class ........................................................................... 35
Table 11 — Attributes of equipment class property .............................................................. 35
Table 12 — Attributes of equipment .................................................................................... 36
Table 13 — Attributes of equipment property....................................................................... 37
Table 14 — Attributes of equipment capability test specification .......................................... 38
Table 15 — Attributes of equipment capability test result ..................................................... 39
Table 16 — Attributes of physical asset .............................................................................. 42
Table 17 — Attributes of physical asset property ................................................................. 43
Table 18 — Attributes of physical asset class...................................................................... 43
Table 19 — Attributes of physical asset class property ........................................................ 44
Table 20 — Attributes of physical asset capability test specification..................................... 45
Table 21 — Attributes of physical asset capability test result ............................................... 45
Table 22 — Attributes of equipment asset mapping ............................................................. 46
Table 23 — Attributes of material class ............................................................................... 48
Table 24 — Attributes of material class property ................................................................. 49
Table 25 — Attributes of material definition ......................................................................... 50
Table 26 — Attributes of material definition property ........................................................... 51
Table 27 — Attributes of material lot ................................................................................... 52
Table 28 — Attributes of material lot property...................................................................... 54
Table 29 — Attributes of material sublot.............................................................................. 55
Table 30 — Attributes of material test specification ............................................................. 56
Table 31 — Attributes of material test result ........................................................................ 57
Table 32 — Attributes of process segment .......................................................................... 60
Table 33 — Attributes of personnel segment specification ................................................... 61
Table 34 — Attributes of personnel segment specification property...................................... 62
Table 35 — Attributes of equipment segment specification .................................................. 62
Table 36 — Attributes of equipment segment specification property..................................... 63
Table 37 — Attributes of material segment specification ...................................................... 64
Table 38 — Attributes of material segment specification property ........................................ 65
-5- ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Figures
Figure 1 – Production operations management information models ...................................... 16
Figure 2 – Operations information models for operations management ................................ 17
Figure 3 — Detailed resource relationship in models ........................................................... 21
Figure 4 — Hierarchy scope model ..................................................................................... 23
Figure 5 — Personnel model............................................................................................... 27
Figure 6 — Role based equipment model ............................................................................ 34
Figure 7 — Physical asset model ........................................................................................ 41
Figure 8 — Physical asset and equipment relationship ........................................................ 41
Figure 9 — Material model.................................................................................................. 47
Figure 10 — Example of a material with an assembly .......................................................... 58
Figure 11 — Process segment model .................................................................................. 59
Figure 12 – Segment dependency examples ....................................................................... 69
Figure 13 — Operations definition model............................................................................. 70
Figure 14 — Operations schedule model ............................................................................. 85
Figure 15 — Operations performance model ..................................................................... 101
Figure 16 — Operations capability Model .......................................................................... 117
Figure 17 — Process segment capability object model ...................................................... 129
-7- ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
FOREWORD
This standard is Part 2 of a multi-part set of standards that defines the interfaces between
enterprise activities and control activities. It follows ANSI/ISA-95.00.01-2010 (IEC 62264-1 Mod),
Enterprise-Control System Integration - Part 1: Models and Terminology.
The scope of this Part 2 standard is limited to defining the details of the interface content
between manufacturing control functions and other enterprise functions. The scope of this Part 2
standard is limited to the definition of object models and attributes for the information defined in
Part 1. The goal is to reduce the effort, cost, and errors associated with implementing these
interfaces.
The standard may be used to reduce the effort associated with implementing new product
offerings. The goal is to have enterprise systems and control systems that interoperate and
easily integrate.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2. Therefore,
the first three clauses present the scope of the standard, normative references, and definitions,
in that order.
Clause 4 is informative. It describes the general information about the object models and
examples defined in later clauses.
Clause 5 is normative. It defines the object models and attributes of common information defined
in Part 1.
Clause 6 is normative. It defines the object models and attributes of operations management
information defined in Part 1.
Clause 8 is informative. It lists the objects defined in the standard as an aid to documenting
conformance and compliance.
Annex A is normative. It defines the object models and attributes of production specific
information defined in Part 1.
Annex B is informative. It provides examples to illustrate how the models and attributes may be
used.
Annex D is informative. It contains questions and answers on the use and reason for elements in
the standard.
Annex E is informative. It discusses how the standard relates to logical information flows.
This page intentionally left blank.
- 11 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
INTRODUCTION
This Part 2 standard further defines formal object models for exchange information described in
ANSI/ISA-95.00.01-2010 (IEC 62264-1 Mod), Enterprise- Control System Integration - Part 1:
Models and Terminology (hereafter referred to as Part 1) using UML object models, tables of
attributes, and examples. The models and terminology defined in this part:
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 capability of manufacturing control systems with
enterprise systems; and
Specifically, this part provide 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. Benefits produced will
a) reduce the user’s time to reach full production levels for new products;
b) enable vendors to supply appropriate tools for implementing integration of control systems to
enterprise systems;
This standard may be used to reduce the effort associated with implementing new product
offerings. The goal is to have enterprise systems and control systems that interoperate and
easily integrate.
a) suggest that there is only one way of implementing integration of control systems to
enterprise systems;
This part of ISA95, in conjunction with ANSI/ISA-95.00.01-2010 (IEC 62264-1 Mod), Enterprise-
Control System Integration – Part 1: Models and Terminology, specifies generic interface content
between manufacturing control functions and other enterprise functions. The interface
considered is between Level 3 manufacturing systems and Level 4 business systems in the
hierarchical model defined in Part 1. The goal is to reduce the risk, cost, and errors associated
with implementing the interface.
Since this standard covers many domains, and there are many different standards in those
domains, the semantics of this standard are described at a level intended to enable the other
standards to be mapped to these semantics. To this end this standard defines a set of elements
contained in the generic interface, together with a mechanism for extending those elements for
implementations.
The scope of Part 2 is limited to the definition of object models and attributes of the exchanged
information defined in Part 1.
This Part 2 standard does not define attributes to represent the object relationships.
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.
ISO 10303-1, Industrial automation systems and integration – Product data representation and
exchange – Part 1: Overview and fundamental principles
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 14 -
For the purpose of this part the definitions given in Part 1 and the following apply.
3.1.1
equipment class
a grouping of role based equipment with similar characteristics
3.1.2
event
representation of a solicited or unsolicited fact indicating a state change in the enterprise
3.1.3
location
the scope of exchanged information as identified by an element of the equipment hierarchy
EXAMPLE There may be an agreement to only supply an “Area” name for exchanged information, because the site
and enterprise are implicitly defined through the messaging system
3.1.4
material class
a grouping of materials with similar characteristics
3.1.5
material lot
uniquely identifiable amount of a material
NOTE It describes the actual or planned total quantity or amount of material available, its current state, and its
specific property values.
3.1.6
material definition
definition of the properties for a substance
NOTE This includes material that may be identified as raw, intermediate, final material, or consumable
3.1.7
material sublot
uniquely identifiable subset of a material lot
3.1.8
personnel class
a grouping of persons with similar characteristics
- 15 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
3.1.9
product
the desired output or by-product of the processes of an enterprise
NOTE 1: A product may be an intermediate product or end product from a business perspective
NOTE 2: Also defined in ISO 10303 Part 1 as: a substance produced by a natural or artificial process
3.1.10
property
implementation specific characteristic of an entity
3.2 Abbreviations
Common objects used in information exchange that relate to personnel, equipment, physical
assets, and material are defined in Clause 5.
The information described in Part 1 for production operations management are represented in
the Production Schedule Model, the Production Performance Model, Product Definition Model,
and the Production Capability models, as shown in Figure 1. These objects are defined in
Annex A.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 16 -
Represented in the Production Schedule model Represented in the Production Performance model
Production Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
schedule request request request performance response response response
Product Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
definition definition definition definition capability capability capability capability
Represented in the Production Definition model Represented in the Production Capability model
A generic operations management information model is used to represent the information from
other operations management areas which may be exchanged when more than production
information is required. This is illustrated in Figure 2. These objects are defined in Clause 6.
- 17 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Represented in the Operations Schedule model Represented in the Operations Performance model
Production Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
schedule request request request performance response response response
Product Maintenance Quality Test Inventory Production Maintenance Quality Test Inventory
definition definition definition definition capability capability capability capability
Represented in the Operations Definition model Represented in the Operations Capability model
This clause describes the object models and attributes for information exchanged in enterprise-
control system integration. The attributes are part of the definition of terms.
In this standard, the word “Class” used as part of an object definition name is to be considered
as a category, not as a “Class” in the UML Class sense.
EXAMPLE “Personnel Class” is to be considered a “Personnel Category”, in the sense of distinguishing between
the kinds of personnel in the real world.
For particular applications the objects defined in the object models will need to be extended
through the addition of attributes to object class definitions. Accordingly this Standard provides
for attributes that are application or industry specific, to be modeled in terms of properties and
represented in property classes in the model. For example, the personnel class property would
be used to define application or industry specific attributes for personnel classes, and person
property would be used to contain instance values for the properties.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 18 -
The object models are depicted using the Unified Modeling Language (UML) notational
methodology, as defined in ISO/IEC 19501.
Symbol Definition
This subclause gives the meaning of the attribute tables. This includes a listing of the object
identification, data types, and presentation of the examples in the tables.
All attributes in the tables shall be considered optional, except where specified as required in the
attribute description.
- 19 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Many objects in the information model require unique identifications (IDs). These IDs shall be
unique within the scope of the exchanged information. This may require translations:
EXAMPLE A unit may be identified as “X6777” in the interface content, as resource “R100011” in the business
system, and as “East Side Reactor” in the control system.
The object IDs are used only to identify objects within related exchanged information sets. The
object ID attributes are not global object IDs or database index attributes.
Generally, objects that are elements of aggregations, and are not referenced elsewhere in the
model, do not require unique IDs.
The attributes presented are abstract representations, without any specific data type specified.
A specific implementation will show how the information is represented.
EXAMPLE 1 An attribute may be represented as a string in one implementation and as a numeric value in another
implementation.
EXAMPLE 2 A date/time value may be represented in ISO standard format in one implementation and in Julian
calendar format in another. Attributes for date or time may contain values for a date, a date and time or
a time value, the standard does not enforce the value semantics. Each implementation must negotiate
the value semantics.
EXAMPLE 3 An object or attribute relationship may be represented by key fields in data base tables, or by
parent/child elements in an XML by nested hierarchy.
Examples are included with each attribute given. Examples are presented for each of the main
operations categories defined in Part 3 of this standard. See Table Table 2 below for how the
example rows and columns are used.
When an example value is a set of values, or a member of a set of values, the set of values is
given within a set of braces, {}.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 20 -
The examples are purely fictional. They are provided to further describe attributes in the model.
No attempt was made to make the examples complete or representative of any manufacturing
enterprise.
NOTE 1 — Within a table the columns for Production, Maintenance, Quality and Inventory may or may not be examples
where the four operations management categories are coordinated or they may be separate examples. For example
when one system is coordinating multiple operations management categories the IDs used in each column may be the
same. When different systems coordinate multiple operations management categories the IDs may be different.
Example attributes are meant to be illustrative, and do not imply requirements.
NOTE 2 — Time and date attributes may illustrate a general or specific time horizon. For example a yearly or
quarterly plan may use general dates with no specific time, while a detailed schedule may include a specific time
stamp down to the minute.
NOTE 3 — Data resolution for the examples will be fit for purpose, which means that each implementation will
negotiate the appropriate resolution required for each attribute.
NOTE 4 — When (not applicable) is used as an example this is only illustrative that there is not a value for this
attribute in this example. It does not imply there can never be a value. This is also true when all four columns contain
(not applicable).
The models used to document a reference to a resource, in another package, using the class or
instance, with additional optional specification using properties, are not fully illustrated in the
object model figures. This relationship is not conformant to the Unified Modeling Language
(UML) modeling methodology, but was used to keep the diagrams simpler. Figure 3 below
illustrates how it is currently presented, on the left side, and how it could be more accurately
modeled in UML on the right side. UML was used in this standard as a visualization method and
not meant to describe implementations. The simplified relationship diagram method is used for
the following objects and their relationship to another package:
Personnel Capability Equipment Capability
Material Capability Personnel Segment Capability
Equipment Segment Capability Material Segment Capability
Physical Asset Capability Physical Asset Segment Capability
Personnel Segment Specification Equipment Segment Specification
Material Segment Specification Physical Asset Segment Specification
Personnel Specification Equipment Specification
Material Specification Physical Asset Specification
Personnel Requirement Equipment Requirement
Material Requirement Physical Asset Requirement
Personnel Actual Equipment Actual
Material Actual Physical Asset Actual
- 21 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Resource
Capability
to element in
Corresponds
to element in
Corresponds
0..n
Resource Resource
Capability Note: The
Capability correspondence
Property
relationship is
0..n 0..n defined through one
and only one of four
to element in
Corresponds
to element in
Corresponds
0..n relationships A, A and
Resource B, C, or C and D.
Capability A C
Property
Detailed Relationship
Model
The correspondence relationship is determined through one and only one of four possible
relationships: to the resource category definition; to the resource category definition and
resource category property; to the resource definition; or to the resource definition and resource
property.
In the model above the term resource category indicates: personnel class, equipment class,
physical asset class, material class, and material definitions. The term resource indicates:
person, equipment, physical asset, material lot, and material sublot. The term resource
capability indicates the use in the capability model, the process segment capability model, the
process segment model, the product definition model, the production schedule model, and the
production performance model.
This part does not define attributes to represent the object relationships.
NOTE Different implementations of the object models will have different methods for representing the object
relationships. While the relationships may be represented as additional attributes on one
implementation, such as a database, they could be represented as containment in another
implementation, such as an XML document.
The operations management information object models described in Clause 6 shall be used for
any manufacturing operations category, such as, Production, Maintenance, Quality, Inventory,
and Inventory Handling, as defined in Part 3. Although the generic object model can also be
used to describe operations management information models for user-defined operations
categories, conformance can be evaluated only if user-specific conformance testing scenarios
are available.
Also additional explanations to assist in applying these object definitions to describe the
interoperability among the following operations management categories are provided in Annex E:
- Production Operations;
- Maintenance Operations;
- Quality Operations;
- Inventory (Handling) Operations;`
- Mixed Operations;
- User-defined Operations.
The Production Information Models described in Annex A reproduce the models in earlier
versions of this standard in order to ensure the conformance of existing implementations of the
standard:
Hierarchy scope is an attribute used in many other objects. The hierarchy scope attribute
identifies where the exchanged information fits within the role based equipment hierarchy. It
defines the scope of the exchanged information, such as a site or area for which the information
is relevant. The hierarchy scope identifies the associated instance in the role based equipment
hierarchy.
NOTE The hierarchy scope attribute is optional and may not be needed if the context of the exchanged
information can be determined based on the exchange mechanism used.
EXAMPLE 1 A hierarchy scope may identify a SITE, such as WEST-END. A Production Performance may have a
Hierarchy Scope attribute that identifies the WEST-END site.
EXAMPLE 2 A hierarchy scope may identify an AREA within a SITE, such as WEST-END/HOLDING-AREA. A
Production Capability may have a Hierarchy Scope attribute that identifies the area.
EXAMPLE 3 A hierarchy scope may identify a WORK CENTER within an AREA or SITE, such as WEST-
END/HOLDING-AREA/CHIPPING-BIN #1.
EXAMPLE 4 A hierarchy scope may identify a WORK CENTER without an AREA or SITE identification because these
are already known due to the exchange mechanism, such as CHIPPING-BIN #1.
EXAMPLE 5 A hierarchy scope may identify a complete hierarchy of ENTERPRISE, SITE, AREA, WORK CENTER.
- 23 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
The hierarchy scope attribute may be modeled using the model illustrated in Figure 4 with
attributes for the Hierarchy Scope object defined in Table 3. Each Hierarchy Scope object
defines one element in the equipment hierarchy,
Hierarchy
Scope
0..1
May contain a
Value attributes are used in properties, parameters, and data to exchange actual values.
Value attributes are also used to exchange the allowed or expected values in properties and
parameters for Material Definitions, Material Classes, Equipment Classes, Personnel Classes,
Physical Asset Classes, Process Segments, Operations Definitions, and Product Definitions.
Value types thus represent actual single values, actual arrays of values, and ranges of possible
values, either as numerical or textual ranges or as sets of values.
The format for values in value attributes is not defined in this part and will be defined by
implementations of the standard.
The following syntax, defined in an EBNF notation from ISO 14977, may be used to represent
single element values, range specifications, arrays of values, and a set of allowed values as
delimited text strings.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 24 -
Simple value types may be derived from core component types that are compatible with the ISO-
15000-5 Core Component Technical Specification (CCTS). The CCTS types are a common set
of types that define specific terms with semantic meaning (e.g. the meaning of a quantity,
currency, amount, and identifier).
This standard defines attributes for value, quantity, and other units of measure. The unit of
measure was explicitly specified to ensure that it was not missed in information exchanges.
Implementations of this standard may represent the unit of measure in the manner appropriate
for the implementation.
Arrays of values may be represented following the syntax defined in the EBNF above.
EXAMPLE 1: A set of values for a single dimension array with 6 values would be represented as:
[ 1 , 2 , 3 , 4 , 5 , 6]
EXAMPLE 2: A set of values for a two dimension array of size 2x3 would be represented as:
[ [ 1 , 2] , [ 3 , 4 ] , [ 5 , 6 ] ]
Range specifications may be represented following the syntax defined in the EBNF above.
{ 0 .. 100 }
A specification defined as a set of allowed values may be represented following the syntax
defined in the EBNF above.
EXAMPLE 2: A series of values that define equipment hierarchy levels may be represented as:
Structured data elements may be represented in this standard’s property model by representing
the atomic elements of the structure in a flattened name space, or by using nested properties to
represent the data structure.
NOTE 1: The decision to use a flattened name space, nested properties, or a combination is determined by the
specific implementation.
A structure may be modeled by flattening the name space and having a single property for each
structure element.
NOTE 2: This standard specifies how to exchange information without regard to the specific exchange element’s
mapping. With structured elements there is no guarantee that the communicating entities would have
the same structure for the data. Therefore flattening the structure to its individual elements provides a
transportable format for structured data.
EXAMPLE 1: A structured element of data would be mapped to a flat name space as follows:
A structured data element may be represented by creating a property with no data value or unit
of measure and with nested child properties and an identification of the element.
Nested property objects are only shown in the Personnel, Equipment, Physical Asset, and
Material models. All property objects are also nested, as defined in the appropriate section in
the text, but are not shown in the model figures in order to reduce the complexity of the figures.
- 27 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
The personnel model shown in Figure 5 contains the information about specific personnel,
classes of personnel, and qualifications of personnel.
Qualification
Test
Specification
< Records the Qualification
0..n 0..n
execution of Test
Defines a Result
Is tested procedure for
0..n by a > obtaining a > 0..n
0..n 0..n
Personnel Person
Class Property < Maps to Property
0..n 0..n
< may contain nested < may contain nested
NOTE Examples of personnel classes are cook machine mechanics, slicing machine operators, cat-cracker
operator, and zipper line inspectors.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 28 -
EXAMPLE A personnel class may be associated to a qualification test specification without reference to a property,
such as a qualification test specification for a fork truck operator, in which the test determined if the
person is a member of the class of fork truck operators.
Properties of a personnel class shall be shown as personnel class properties. Each personnel
class shall have zero or more recognized properties. Table 5 lists the attributes of personnel
class property.
NOTE Examples of personnel class properties for the personnel class operators are class 1 certified, class 2
certified, night shift, and exposure hours.
Production requests may specify required personnel class property requirements for a product
segment.
A personnel class property may be tested by the execution of a qualification test specification.
5.1.4 Person
Properties of a person shall be listed as person properties. Each person shall have zero or more
person properties. These specify the current property values of the person for the associated
personnel class property. Table 7 lists the attributes of person property.
NOTE For example, a person property may be night shift and its value would be available, and a person
property may be exposure hours available and its value would be 4.
Person properties may include the current availability of a person and other current information,
such as location and assigned activity, and the unit of measure of the current information.
A person property may be tested by the execution of a qualification test specification with test
results exchanged in a qualification test result.
ID An identification of a test for Class 1 Widget Union LGC Model Fork Truck
certifying one or more values for Assembly Renewal 1003 Driving
one or more person properties. Certification Test Certificatio Test
Test n Test
For example, this may be the
name of a document that
describes or defines the
qualification test.
Description Additional information and Identifies the Renewal for Identifies Identifies
description about the qualification test for Class 1 union test for test for
test specification. Widget membership correct driving
assembly operation fork truck
certification – of LGC
returns a True Model
or False value 1003
for the Class 1
widget
assembly
certification
property
Version An identification of the version of V23 01 A 23C
the qualification test
specification.
The results from a qualification test for a specific person shall be given as a qualification test
result. Table 9 lists the attributes of qualification test result.
The role based equipment model shown in Figure 6 contains the information about specific
equipment, the classes of equipment, and equipment capability tests.
The formal UML role based equipment model object is used to define the role based equipment
hierarchy information that is defined in Part 1 of this standard. The model contains the
information that may be used to construct the hierarchical models used in manufacturing
scenarios. For purposes of corresponding to the Part 1 models, the defined equipment levels,
specified in the Equipment Level attributes, for role based equipment are: Enterprise, Site, Area,
Work Center, Work Unit, Process Cell, Unit, Production Line, Production Unit, Work Cell, Storage
Zone, and Storage Unit.
NOTE 1 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 Laboratory may be an extended equipment level that defines a Work Center that includes all equipment
in a test lab.
EXAMPLE 2 A Maintenance Storage Center may be an extended equipment level that defines a Work Center that
includes all equipment used by maintenance activities.
EXAMPLE 3 A Mobile Equipment Center may be a work center that includes all mobile equipment which may be used
at different work centers or areas at different points in time.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 34 -
Equipment 0..n
Equipment
Class 0..n < Defined by
0..n 0..n
Has Has
properties Is tested Is tested values for >
of > by an > by an >
0..n 0..n
Equipment
Capability Test
Specification
0..n 0..n < Records the Equipment
Defines a execution of Capability Test
Is tested procedure for Result
by an > obtaining an >
0..n 0..n
0..n 0..n
Equipment Equipment
Class Property Maps to Property
0..n 0..n
< may contain nested < may contain nested
NOTE Examples of equipment classes are reactor unit, bottling line, and horizontal drill press.
- 35 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Properties of an equipment class shall be listed as equipment class properties. Each may have
zero or more recognized properties. Table 11 lists the attributes of equipment class property. An
equipment class property may be tested by the execution of an equipment capability test
specification.
NOTE Examples of equipment class properties for the equipment class reactor unit may be lining material,
BTU extraction rate, and volume.
5.2.4 Equipment
A representation of the elements of the equipment hierarchy model shown in Part 1 shall be
known as equipment. Equipment may be a listing of sites, areas, production units, production
lines, work cells, process cells, units, storage zones or storage units. Table 12 lists the attributes
of equipment. Equipment may be tested by the execution of an equipment capability test
specification.
Equipment may be made up of other equipment, as presented in the equipment hierarchy model.
EXAMPLE 2 A reactor may be made up of sensors, valves, an agitator, and level switches.
Properties of equipment shall be listed as equipment properties. An equipment shall have zero or
more equipment properties. These specify the current property values of the equipment for the
associated equipment class property. Equipment properties may include a unit of measure. Table
13 lists the attributes of equipment property. An equipment property may be tested by the
execution of an equipment capability test specification with results exchanged in an equipment
capability test result.
NOTE: An equipment property may exist without an associated equipment class property, however all parties in
an exchange must have a common understanding of the equipment property.
EXAMPLE 1 An equipment class property may be volume with a value of {10000 – 50000} with a unit of measure of
liters, an equipment property may be volume with a value of 30.000 and a unit of measure of liters.
- 37 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
− maintenance status;
− performance values.
Description Additional information about the Widget making Capacity of Minimum Maximum
equipment property. average run the welder peak carrying
rate resolution weight for
the truck
Value The value, set of values, or range 59 {10-200} 0.05 1
of the property.
The value(s) is assumed to be
within the range or set of defined
values for the related equipment
property.
Value Unit of The unit of measure of the Widgets/Hour Amperes % Tons
Measure associated property value, if
applicable.
The results from an equipment capability test for a specific piece of equipment shall be shown as
an equipment capability test result. Table 15 lists the attributes of equipment capability test
result.
5.2.8 Containers
A container for material shall be represented as role based equipment, physical asset, or both of
type storage zone or storage unit.
EXAMPLE 1 In a refinery; bulk storage tanks would be represented as Storage Units and as containers for specific
materials.
EXAMPLE 2 In an automotive plant; assembly parts bins would be represented as Storage Units and as containers
for an assembly of parts.
EXAMPLE 3 In a pharmaceutical plant; portable tote bins or pallets that hold tablets would be represented as
Storage Units for a specific material lot or sublot.
EXAMPLE 4 Properties of containers would be represented as Equipment Class, Equipment, Physical Asset Class, or
Physical Asset properties, such as: Readiness, Transportability, Disposable, and Cleanness.
The association of material lots and sublots to containers is modeled as properties of the
material lot or sublot.
The association of containers to material lots and sublots is modeled as properties of the
container.
5.2.9 Tools
EXAMPLE 1 In a pharmaceutical plant; a tablet die used to compress and shape tablets would be represented as a
Work Unit. The tablet die work unit may have properties that identified the expected use time and the
actual use time.
EXAMPLE 2 In plastics parts manufacturing; an extruder die would be represented as a Work Unit. The extruder
machine could be represented as a Work Cell.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 40 -
EXAMPLE 3 In semiconductor manufacturing; a multi-platen multi-wafer CMP (Chemical Mechanical Polishing) tool
would be represented as a Work Cell.
EXAMPLE 4 A micrometer used for measuring sheet metal thickness in a general purpose machine shop may be
recorded as equipment but not tracked as a physical asset.
5.2.10 Software
NOTE Level 3 applications may have responsibility for keeping the actual software up to date. In the context of
this standard, information about the software may need to be specified, required, reported or
synchronized with Level 4 systems.
EXAMPLE 1 When a patch is applied to software the change may need to be known by Level 3 systems to allow
additional testing and Level 4 systems to update security settings.
EXAMPLE 2 When a physical asset is decommissioned and it contains licensed software, then a Level 4 system may
need the information to order software uninstalls, to order asset memory clearing or to know to cancel
the maintenance license fee.
The physical asset model contains information about the physical piece of equipment, usually
managed as a physical asset within the enterprise often utilizing a specific serial number. An
object in the equipment model defines a role for the equipment, and object in the asset model
defines the physical ID and properties of a piece of equipment.
EXAMPLE Equipment IDs can be represented as TAGs, which define a role such as TC184 for a temperature
controller, while the temperature controller is an asset and has a serial number
(TC_WED_9982002922).
The physical asset can be replaced (e.g. because it is broken) and in that case the TAG will not change,
but a new physical asset with a unique serial number will take the place of the old physical asset.
Therefore two separate ID’s are needed, one for the role (equipment ID) and one for the physical asset
(physical asset ID).
While assets have Level 4 significance, usually because they have an economic value, this part
of the standard focuses on the Level 3 significance of the asset. The asset model defines a
physical asset as a representation of a physical piece of equipment.
Definitions for hierarchy levels in the physical asset hierarchy are not defined in this Part,
however the role-based equipment hierarchy names should be used if they are equivalent.
Physical Asset
Capability Test
< records the
Specification
Physical Asset
testing of 0..n 0..n
Capability Test
Result Defines a
procedure for Is tested
0..n obtaining an < by an < 0..n
0..n 0..n
< may contain nested < may contain nested
The relationship between the physical asset information and the equipment information is shown
in Figure 8. There is a temporal relationship between the role of the equipment and the physical
asset. The physical asset performing the role may change over time and the equipment asset
mapping maintains the association.
< may contain nested < may contain nested < may contain nested < may contain nested
NOTE This model shown in Figure 8 is consistent with the MIMOSA data models, but with various name
differences due to their development history.
2. A MIMOSA Asset Utilization History element maps to an Equipment Asset Mapping object.
A physical asset represents a physical piece of equipment. Table 16 lists the attributes of a
physical asset. A physical asset may be tested by the execution of a physical asset capability
test specification.
Physical assets may be made up of other physical assets. For example, a packaging line may be
made up of conveyor sections, motors, and sensors.
NOTE 1 Implementations should consider the following rules concerning the use of IDs:
2. If an information exchange is required to handle assets across enterprises, then the ID should be a
GUID (Globally Unique ID).
3. Common local practices may require other identifications of physical assets and require additional
correlated identifications represented as properties.
NOTE 2 Materials used in maintenance operations may be represented in either the physical asset equipment
model, in the material model, or in both. When represented in both models the IDs used to identify the
material in both models (Material Lot and Physical Asset ID) should be the same.
Properties of physical assets shall be listed as physical asset properties. A physical asset shall
have zero or more physical asset properties. These specify the current property values of the
physical asset for the associated physical asset class property. Physical asset properties may
- 43 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
include a unit of measure. Table 17 lists the attributes of a physical asset property. A physical
asset property may be tested by the execution of a physical asset capability test specification
with results exchanged using a physical asset capability test result.
Description Additional information about the Name plate Vendor Indicates Indicates
asset property. date of assembly that the the state
production drawing ID physical of the
asset must physical
be signed asset
out and
tracked
Value The value, set of values, or range 2008 10 ACC08- <Tracked, <Assigned
of the property. 55642 Not , Issued,
Tracked,> Available>
The value(s) is assumed to be
within the range or set of defined
values for the related asset
property.
Value Unit of The unit of measure of the Date String Boolean Boolean
Measure associated property value, if
applicable.
Properties of a physical asset class shall be listed as physical asset class properties. Each may
have zero or more recognized properties. Table 19 lists the attributes of a physical asset class
property. A physical asset class property may be tested by the execution of a physical asset
capability test specification.
Physical asset class properties may contain nested physical asset class properties.
A representation of a capability test for a physical asset shall be represented as a physical asset
capability test specification. A physical asset capability test specification may be associated with
a physical asset property. This is typically used where a test is required to ensure that the
physical asset has the rated capability and capacity. A physical asset capability test specification
may test for one or more physical asset properties. Table 20 lists the attributes of a physical
asset capability test specification.
Description Additional information about the Test of Pump Test of Test of Test of
test specification. Throughput Maximum Average Hours to
speed of test rate recharge
welder truck
Version An identification of the version of 00 1 2 3
the capability test specification.
The results from a qualification test for a specific physical asset shall be represented as a
physical capability test result. Table 21 lists the attributes of a physical asset capability test
result.
Description Additional information about the the number of pH meter Hardness Cold box
test result. chrome plated calibration test of unit storage
widgets result test 878 temp.
produced per delta
hour
Date The date and time of the 1999-10-25 1999-10-25 1999-10- 1999-10-
capability test. 13:30 13:30 25 13:30 25 13:30
Result The result of the capability test. 48 7.0001 <Pass, 1.2
Fail>
o
Result Unit The unit of measure of the Widgets/Hour pH Boolean C
of Measure associated test result, if
applicable.
Expiration The date of the expiration of the 2000-10-25 2000-10-25 2000-10- 2000-10-
capability. 13:30 13:30 25 13:30 25 13:30
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 46 -
Description Additional information about the (not applicable) Installed (not (not
mapping element. under work applicable) applicable)
order 48423.
Removed
under work
order 93823
Start Time The starting time of the 1997-02-10 1997-02-10 2004-04- 2005-04-
association. 23 30
End Time The ending time of the 2004-12-10 2004-12-10 (not (not
association. applicable) applicable)
The material model shown in Figure 9 defines the actual materials, material definitions, and
information about classes of material definitions. Material information includes the inventory of
raw, finished, intermediate materials, and consumables. The information about planned or actual
material is contained in the material lot and material sublot information. Material classes are
defined to organize materials.
NOTE This corresponds to a resource model for material, as defined in ISO 10303.
- 47 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Is assembled from
0..n
Has Has Is tested Has
properties properties Is tested values for Has
by a > by a > values for
of Is tested of May be made up
by a > 0..n 0..n of sublots
0..n
Material Test
0..n Specification
Is tested Records the
0..n 0..n execution of
by a > Defines a QA Test
Is tested
by a > procedure Result
for
0..n 0..n 0..n obtaining a 0..n
Material Material 0..n 0..n 0..n
Material Lot
Class Definition
May Maps to Property
Property Property
map to
NOTE An example of a material class may be sweetener, with members of fructose, corn syrup, and sugar
cane syrup. Another example of a material class may be water, with members of city water, recycled
water, and spring water.
A material class may be defined as containing an assembly of material classes and as part of an
assembly of material classes:
Properties of a material class shall be presented as material class properties. A material class
shall be further characterized through zero or more material class properties. Table 24 lists the
attributes of material class property. A material class property may be tested by the execution of
a material test specification.
- 49 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
NOTE Examples of material class properties include density, pH factor, and material strength.
The material class properties often list the nominal, or standard, values for the material. A
material property does not have to match a material class property.
A representation of goods with similar name characteristics for the purpose of manufacturing
operations definition, scheduling, capability and performance shall be shown as a material
definition. Table 25 lists the attributes of material definition. A material definition may be tested
by the execution of a material test specification.
NOTE Examples of these may be city water, hydrochloric acid and grade B aluminum.
Table 26 lists the attributes of material definition property. A material definition property may be
tested by the execution of a material test specification.
NOTE Examples of material definition property include density, pH factor, or material strength.
Properties may present the nominal or standard values for the material.
A material lot may be made up of material sublots. Material lots and material sublots may be
used for traceability when they contain unique identifications.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 52 -
Status Status of the material lot. For In process approved blocked approved
example, released, approved,
blocked, in process, in quality
check.
Storage An identification of the storage Work Center Maintenance Work Bench Warehouse
Location location or a physical location 1 Shed 4S 10, Top 1
of the material lot. Shelf
Quantity The quantity of the material lot. 1200 20 1 41
Quantity Unit The unit of measure of the sheets Cans Liter Rolls
of Measure associated quantity, if
applicable.
NOTE 1 Representation of non-lot controlled items (for example consumable materials or bulk materials), may be
represented in the Material Lot model through the use of a unique IDs for each different Material
Definition. For example this could be the Material Definition ID or a system assigned ID,
- 53 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
NOTE 2 If non-lot controlled items must be maintained in multiple locations then the information may be
represented in the Material Sublot model through the use of unique sublot IDs for each different location
and Material Definition.
A material lot or a material sublot may be defined as containing an assembly of material lots or
material sublots and as part of an assembly of material lots or material sublots:
1. A material lot or a material sublot may define an assembly of zero or more material lots
or a material sublots.
2. A material lot or a material sublot may be an assembly element of zero or more material
lots or a material sublots.
EXAMPLE 1 A transient assembly could be a temporary collection of material maintained as a batch kit on a
pallet, the batch kit is identified with a unique identification and may contain specific
properties, such as a pallet identification, location, and related batch ID.
EXAMPLE 2 A permanent assembly of material may be an automobile. The automobile has a unique vehicle
identification number (VIN) and other properties. The automobile may contain an assembly of
an engine, transmission, chassis, and wheels, each with their own unique identification and
properties.
EXAMPLE 4 An unassembled collection of tractor components that are separately shipped is a logical
assembly of materials.
Each material can have unique values for zero or more material lot properties, such as a specific
pH value for the specific lot of material, or a specific density for the lot of material. A material lot
property may be tested by the execution of a material test specification with results exchanged in
a QA test specification result.
A material lot property is associated with either a material lot or a material sublot. When
associated with a material lot it specifies a property value for all sublots, when associated with a
material sublot it specifies a property value for a single sublot.
A material lot may be stored in separately identifiable quantities. Each separately identifiable
quantity of the same material lot shall be presented as a material sublot. All material sublots are
part of the same material lot, so they have the material lot’s property values. A material sublot
may be just a single item. Table 29 lists the attributes of material sublot. Material sublots may
have sublot specific properties.
EXAMPLE Sublot properties may be RFID tag IDs or other identification properties, such that each sublot of a lot
has a different property value.
Each material sublot shall contain the location of the sublot and the quantity or amount of
material available in the sublot.
NOTE For example, a sublot may be a pallet, each box on the pallet may also be a sublot, and each material
blister pack in the box may also be a sublot.
A representation of a material test shall be shown as a material test specification. A material test
specification shall be associated with one or more material definition properties. This is typically
used where a test is required to ensure that the material has the required property value. A
material test specification may identify a test for one or more material definition properties. Not
all properties need to have a defined material test specification. Table 30 lists the attributes of
material test specification.
Material test specifications may also be related to a production request. The same material may
have different specifications for different production requests, depending on specific customer
requirements.
A representation of the results from the execution of a quality assurance test shall be presented
as a material test result. A material test result records the results from a material test for a
specific material lot or material sublot. The following are some characteristics of material test
results. Table 31 lists the attributes of material test result.
a) They shall be related to a material lot or material sublot.
b) They may be related to a production request.
c) They may be associated with a specific production response.
d) They may be related to a specific process segment.
- 57 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
5.4.11 Assemblies
NOTE 1 Many assembly type industries, such as automobile manufacturing, airplane assembly, and furniture
manufacturing use the concept of assemblies. A produced material, with a unique identification and
properties, is made up of other materials with their own unique identification and properties.
EXAMPLE 1 An “automobile” is a material lot, with specific properties (color, VIN #, make, model, …) while it also
contains other chassis parts (engine, transmission, axles …) that also have their own unique
identification and properties.
EXAMPLE 2 A transaxle in an automobile has its own identification and also is an assembly of subcomponents, as
shown in Figure X, including seals, bearing, axle shaft, etc, as shown in Figure 10. There may be an
assembly which defines a specific model of transmission described in a Material Definition Assembly,
and there may be an assembly that defines a specific transmission described in a Material Assembly.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 58 -
EXAMPLE 3 A “batch kit” is an assembly that contains a collection of different materials that would be used in the
production of a batch, for example a batch kit for a soup may contain the seasonings that are used in
production of a single batch. There may be an assembly which defines the class of materials used in a
batch kit described in a Material Class Assembly, and there may be a batch specific assembly which
defines specific material lots or sublots described in a Material Assembly.
Axle Bearing
Material Definition
Axle Seal
Material Definition
Axle Shaft
Material Definition
Process segments are the smallest elements of manufacturing activities that are visible to
business processes. The process segment model is a hierarchical model, in which multiple
levels of abstraction of manufacturing processes may be defined because there may be multiple
business processes requiring visibility to manufacturing activities.
NOTE The term business process segment is a synonym for process segment and is used to reflect the
business process aspect of the process segment.
Process segments are also logical grouping of personnel resources, equipment resources, and
material required to perform a manufacturing operations step. A process segment defines the
needed classes of personnel, equipment, and material, and/or it may define specific resources,
such as specific equipment needed. A process segment may define the quantity of the resource
needed.
The manufacturing operations step may be a production operations step, inventory operations
step, maintenance operations step, and quality operations step.
Process 0..n
Segment
0..n Process
is a collection of Segment
May be made up of Dependency
A process segment lists the classes of personnel, equipment, physical assets, and material
needed, and/or it may present specific resources, such as specific equipment needed for the
process segment. A process segment may list the quantity of the resource needed.
A process segment is something that occurs or can occur during manufacturing operations.
Process segments may contain specifications of specific resources required by the Process
segment. Process segments may contain parameters that can be listed in specific operations
requests.
Duration Unit The units of measure of the Minutes (not minutes minutes
of Measure duration, if defined. applicable)
Personnel resources that are required for a process segment shall be presented as personnel
segment specifications.
Personnel Identifies the associated Milling Machine Type 2 Lab Tech Lift truck
Class personnel class or set of Operator Mechanic A operator
personnel classes specified
Specific properties that are required are specified in personnel segment specification properties.
Personnel segment specification properties may contain nested personnel segment specification
properties.
Table 34 defines the attributes for personnel segment specification property objects
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 62 -
Quantity Unit The unit of measure of the Hours / piece (not (not (not
of Measure associated quantity, if applicable. applicable) applicable) applicable)
Equipment resources that are required for a process segment shall be presented as equipment
segment specifications.
Equipment Identifies the associated (not applicable) 10 Ton Crane Reflectom 800 kg
Class equipment class or set of eter Fork Truck
equipment classes of the
capability.
Equipment* Identifies the associated Milling Machine (not (not (not
equipment or set of equipment of 001 applicable) applicable) applicable)
the capability.
Description Contains additional information Equipment Crane Measures Able to lift
and descriptions. needed for required to substrate two
widget milling remove thickness standard
process motor of wafer pallets
segment
Equipment Defines the expected use of the Part Milling Remove and Run Test Material
Use equipment class or equipment in Replace Movement
the context of the process Motor
segment.
Quantity Specifies the amount of 1.3 1 1 1
resources required, if applicable.
Quantity Unit The unit of measure of the Machine Hours Day Test Move
of Measure associated quantity, if applicable. / piece
Specific properties that are required are specified in equipment segment specification properties.
Table 36 defines the attributes for equipment segment specification property objects.
Quantity Unit The unit of measure of the Machine Hours / (not (not (not
of Measure associated quantity, if piece applicable) applicable) applicable)
applicable.
Material resources that are required for a process segment shall be listed as material segment
specifications.
Material Identifies the associated material Polymer sheet Motor Sample Pallet
Class class or set of material classes of stock 1001A Brushes Holder
the capability.*
Material Identifies the associated material Sheet stock #9949 Polyurethane Plastic
Definition definition or set of material 1443a sample holder Pallet
definitions of the capability. *
Description Contains additional information Defines the Brushes Disposable Pallet
and descriptions. polymer required sample holder used for
required for a during motor storage
widget milling maintenance
process
segment.
Assembly Optional: Defines the type of the Physical Physical Logical Physical
Type assembly. The defined types are:
Physical – The components of
the assembly are physically
connected or in the same area.
Logical – The components of the
assembly are not necessarily
physically connected or in the
same area.
Assembly Optional: Defines the type of the Permanent Transient Permanent Transient
Relationship relationships. The defined types
are:
Permanent – An assembly that is
not intended to be split during the
production process.
Transient – A temporary
assembly using during
production, such as a pallet of
different materials or a batch kit.
Material Use Defines the material use. Material Material Material Material
Consumed Consumed Consumed Consumed
For production defined values
are: Consumable, Material
Consumed, and Material
Produced
Quantity Specifies the amount of 0.35 6 1 (not
resources required. applicable)
Quantity Unit The unit of measure of the Sheets / piece Units Units (not
of Measure associated property value, if applicable)
applicable.
Specific properties that are required are specified in material segment specification properties.
Material segment specification properties may contain nested material segment specification
properties.
Table 38 defines the attributes for material segment specification property objects.
Quantity Unit The unit of measure of the Sheets / piece (not (not (not
of Measure associated property value, if applicable) applicable) applicable)
applicable.
Physical asset resources that are required for a process segment shall be presented as physical
asset segment specifications.
Table 39 defines the attributes for physical asset segment specification objects.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 66 -
Physical Identifies the associated physical Acme Super Easy bake Wafers R
SuperTote
Asset Class asset class or set of physical TT10 1969 Us RF 100 2000
asset classes of the capability.
Physical Identifies the associated physical TI-101 OV-1200 RF-140 Tote 12A
Asset asset or set of physical assets of
the capability.
Description Contains additional information Transmitter Oven with Measures Able to
and descriptions. with most minimum substrate store 200
recent 2000 hours thickness vials in 40
calibration date on run clock of wafer x 5 matrix
Physical Defines the expected use of the Temperature of Preventive Thickness Storage
Asset Use physical asset class or physical granulation maintenance measurem
asset in the context of the process ent
process segment.
Quantity Specifies the amount of 1 1 1 1
resources required, if applicable.
o
Quantity Unit The unit of measure of the K hours micron Cubic feet
of Measure associated quantity, if applicable.
Specific properties that are required are specified in physical asset segment specification
properties.
Physical asset segment specification properties may contain nested physical asset segment
specification properties.
Table 42 defines the attributes for physical asset segment specification property objects.
- 67 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Quantity Unit The unit of measure of the (not applicable) (not (not Count
of Measure associated quantity, if applicable. applicable) applicable)
Specific parameters required for a segment shall be shown as process segment parameters.
Table 42 defines the attributes for process segment dependency objects. The process segment
dependencies can be used to describe process dependencies that are independent of any
particular product or operations task.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 68 -
NOTE 1 For example, a process segment dependency may define that an testing segment must follow an
assembly segment.
EXAMPLE Using ‘A’ and ‘B’ to identify the process segments, or specific resources within the segments, and T to
identify the timing factor, as shown in Figure 12, the dependencies include:
⎯ Start B at A start
⎯ Start B after A start
Time Time
A A
T T
B B
NOTE 2 The associations to the A and B segments are not represented as attributes, as per 4.5.6.
Operations definition shall be used to specify the resources required to perform a specified
operation. The operations definition may apply to defining production, maintenance, quality test
and inventory operations. The actual definition of how to perform the operation is not included in
the object model. Figure 13 below is the common operations definition model.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 70 -
Bill of Bill of
Operations Work Definition
Resources Material
Definition (External)
(External) (External)
Has Has 1..1 may have a reference to >
associated > associated Has associated >
Operations instructions are defined as the information used to instruct a manufacturing operation
how to perform the operation. Production operations specific operations instructions may be
called a general, site or master recipe (IEC 61512-1 and ANSI/ISA-88.01-1995 definition),
standard operating procedure (SOP), standard operating conditions (SOC), master or product
routing, or assembly steps based on the production strategy used.
ID Uniquely identifies the operations Export Quality Medium Size Potency Tank
definition. Widget AC Motor Test Transfer
Overhaul Procedure Procedure
The ID shall be used in other
parts of the model when the
Operations definition needs to be
identified
Version An identification of the version of 1.0 1.4 1.1 1.1
the Operations definition.
In cases where there are multiple
versions of an Operations
definition, then the version
attribute shall contain the
additional identification
information to differentiate each
version.
Description Contains additional information Information For Test for Movement
and descriptions of the defining overhauls of potency of of material
Operations definition resources motors less product from one
required for than 200 HP. tank to
production of a another
single ‘Export
Quality
Widget’.
Operations Describes the category of Production Maintenance Quality Inventory
type operation
Required attribute
Defined values are: Production,
Maintenance, Quality, Inventory,
or Mixed.
“Mixed” shall be used when the
operations definition contains
several types of operations
requests and/or segment
requirements
Hierarchy Identifies where the exchanged East CNC Test Cell 4 Warehous
Scope information fits within the role Wing(AREA)/ Machine eB
Receiving
based equipment hierarchy. Manufacturing
Asset ID
Line #2(WORK
13465
CENTER)
Bill of Identification of the external Bill BOM9929 BOM9928 BOM9927 BOM9926
Material ID Of Material associated with this
Operation Definition
Work Identification of the external Work WD009 V0.23 WD008 V03 WD007 WD006
Definition ID Definition associated with this V1.3
Operations Definition
Bill of Identification of the external Bill BOR77782 V01 BOR77783 BOR77784 BOR77785
Resource ID Of Resource associated with this V11 V3.45
Operation Definition
NOTE 1 In the case of production, an Operations Definition ID may be the same ID as a Material Definition.
NOTE 2 A product definition, as defined in Part 1, is the equivalent of an Operations Definition for production.
NOTE 3 A MIMOSA Solution Package is the equivalent of an Operations Definition for maintenance.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 72 -
Table 45 defines the attributes for operations material bill objects. Operations material bill
objects define the collection of all material used in the operation independent of the segment the
material is used in.
Example: There may be one operations material bill for consumed materials and a second operations material bill
for produced materials.
Table 45 defines the attributes for operations material bill item objects. Operations material bill
item objects identify the items that make up the complete operations material bill.
- 73 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Material Identifies the associated material {Sheet stock {20 mm 10” 1000 lb
Definition definition or set of material 1443a , Rivet- Bearing, diameter Weight
definitions required. 10002} NLGI Grade circular load 4x4
2 Grease} chart pallet
paper
Use type Defines the use of the material. Consumed Consumed Consumed Consumed
Example 1: Consumed –
indicates that bill items are all
consumed material.
Example 2: Produced – indicates
that bill items are all produced
materials.
Assembly Optional: Defines the type of the Physical Physical Logical Physical
Type assembly. The defined types are:
Physical – The components of
the assembly are physically
connected or in the same area.
Logical – The components of the
assembly are not necessarily
physically connected or in the
same area.
Assembly Optional: Defines the type of the Permanent Transient Permanent Transient
Relationship relationships. The defined types
are:
Permanent – An assembly that is
not intended to be split during the
production process.
Transient – A temporary
assembly using during
production, such as a pallet of
different materials or a batch kit.
Quantity Specifies the amount of {1.0, 26} {2, 30} 5 100
resources required.
Quantity Unit The unit of measure of the {Sheets / piece , {piece, ml} Each Each
of Measure associated quantity, if applicable. Number /
piece}
An operations material bill item may be defined as containing an assembly of operations material
bill items and as part of an assembly of operations material bill items:
1. An operations material bill may define an assembly of zero or more operations material
bills.
2. An operations material bill may be an assembly element of zero or more operations
material bills.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 74 -
The information needed to quantify a segment for a specific operation shall be an operations
segment. An operations segment identifies, references, or corresponds to a process segment.
Hierarchy Identifies where the exchanged East Asset ID Test Cell 4 Warehouse
Scope information fits within the role Wing(AREA) 13465 B
based equipment hierarchy.
Duration Duration of segment, if known. 25 Minutes 4 15 30
Duration Unit The units of measure of the Minutes Hours Seconds Minutes
of Measure duration, if defined.
Process Identifies the associated Process Widget AC Motor Volt Meter Raw
segment segments. There may be multiple Polishing Disassemble Test Material
alternate process segments that Stage
could be used for the operations
segment.
Operations Describes the category of Production Maintenance Quality Inventory
type operation.
Required attribute.
Defined values are: Production,
Maintenance, Quality, Inventory,
or Mixed.
“Mixed” shall be used when the
operations segment contains
several types of operations
requests and/or segment
requirements.
Work Identification of the external Work WD009 V0.23 WD008 V03 WD007 WD006
Definition ID Definition associated with this V1.3
Operations Segment
NOTE 1 A MIMOSA ordered list is the equivalent of an operations segment for maintenance operations.
NOTE 2 A MIMOSA ordered list resource item is the equivalent of a single item personnel specification,
equipment specification, physical asset specification or material specification for a maintenance
operations segment.
- 75 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
NOTE 3 A product segment is the equivalent of an operations segment for production operations. See Annex A.
An operations segment may have an associated set of zero or more parameter specifications.
The parameter specification contains the names and types of the values that may be sent to the
Level 3 systems to parameterize the operation.
NOTE Examples of parameter specifications are pH of 3,5, pressure limit of 35 psi, and flange color = orange.
EXAMPLE Ranges may be alarm or quality ranges; tolerances for acceptable parameter values.
ID Identification of the parameter for Widget Torque Value Viscomete Cases per
a specific segment. roughness r spindle pallet
size
Description Contains additional information of Range of Maximum Spindle Number of
the parameter. acceptable torque value size for cases per
surface for fly wheel correct pallet
roughness to assembly viscosity
be range
manufactured.
Value The value, set of values, or range {80..2500} 35 2 124
of acceptable values
Value Unit of Unit of measure of the values, if Angstroms Nm cP Each
Measure applicable.
Specific elements associated with a personnel specification may be included in one or more
personnel specification properties.
NOTE Examples of personnel specification properties are training level required, specific skill required, and
exposure availability.
Specific elements associated with an equipment specification may be included in one or more
equipment specification properties.
NOTE Examples of equipment specification properties are material of construction, maximum material
capacity, and minimum heat extraction amount.
Equipment Defines the expected use of the Part finishing Assembly %VOC Raw
Use equipment class or equipment. setup Test result material
staging
Quantity Specifies the amount of 0.5 {shared 1 1 1
equipment resources required for between two
the parent segment, if applicable. segments}
Quantity Unit The unit of measure of the Each Each Each Each
of Measure associated quantity, if applicable.
Specific elements associated with an physical asset specification may be included in one or
more physical asset specification properties.
Physical Defines the expected use of the Polish Wrench Gas Raw
Asset Use physical asset class or physical required for Chromatog material
asset. proper raphy test staging
tightening of
motor head
Quantity Specifies the amount of physical 1.25 2 1 5000
asset resources required for the
parent segment, if applicable.
Quantity Unit The unit of measure of the Minutes / piece Each Each Each
of Measure associated quantity, if applicable.
Table 53 defines the attributes for physical asset specification property object.
Physical asset specification properties may contain nested physical asset specification
properties.
- 81 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Specific elements associated with a material specification may be included in one or more
material specification properties.
NOTE Examples of material specification properties are colour range, density tolerance, and maximum scrap
content.
Value The value, set of values, or range {1300..1500} 16-21 +/_ 500 304
for the associated property. Stainless
Steel
Value Unit of The unit of measure of the Grit Number Pitch ppb Grade
Measure associated property value, if
applicable.
Quantity Specifies the amount of material 5 (not (not (not
resources required for the parent applicable) applicable) applicable)
segment, if applicable.
Quantity Unit The unit of measure of the gm / piece (not (not (not
of Measure associated property value, if applicable) applicable) applicable)
applicable.
Table 56 defines the attributes for operations segment dependency objects. The operations
segment dependencies can be used to describe dependencies that are operation or product
specific.
EXAMPLE 2 Dependency type using A and B to identify the segments, or specific resources within the segments, and
T to identify the timing factor, as shown in Figure 12, include the following:
⎯ Start B at A start
NOTE The associations to the A and B segments are not represented as attributes, as per clause 4.5.6.
The operations schedule may apply to scheduling of Production, Maintenance, Quality Test and
Inventory.
Operations
Schedule
Is made up of
1..n
May correspond
Operations to an < Operations
Definition Request
Is made up of
Parameter
Specification or Personnel Equipment Physical Asset Material
Process Segment Model Model Model Model
Parameter
An operations schedule may be defined for any specific category of operations; production,
maintenance, quality, or inventory, or it may be defined for a combination of categories. When a
combination is selected, then the operations requests or segment requirement specifies the
category of the operation.
NOTE A MIMOSA Segment Request for Work and an Asset Request for Work are the equivalent of an
operations request for either equipment or for a physical asset. The table of Request for Work is the
equivalent of the Operations schedule.
A process segment and a production request shall be made up of one or more segment
requirements. Each segment requirement shall correspond to, or reference, an identified
operations segment or process segment. The segment requirement identifies or references the
segment capability to which the associated personnel, equipment, materials, and segment
parameters correspond.
The personnel requirement property, equipment requirement property and product parameter
shall align with the personnel property, equipment property, and product parameters sent as part
of a production request. If the scheduling function sends information that is not understood by
the receiving control function, then that information cannot be used within the control function.
Likewise the scheduling function has to be able to determine what information can be accepted
by the control function.
Latest End The expected latest ending time 10-28-2006 10-28-2006 10-28- 10-28-
Time of this segment requirement, if 10:00 UTC 2:15 UTC 2006 4:30 2006 6:30
applicable. UTC UTC
EXAMPLE There may are multiple segments defined. There is one master segment that applies to the entire
operations request. The master segment is made up of multiple nested segments for individually
specified and reported segments.
NOTE Information that applies across all segments of the operations request, such as a customer name, may
be represented as a segment parameter in the master segment. Information that applies to specific
segments may be specified as part of the segment.
- 91 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Information contained in the enterprise system that is required by the operation system for
correct manufacturing shall be known as segment parameters.
A segment parameter should include a set of limits that apply to any change to the value, such
as quality limits and safety limits.
The identification of the number, type, duration, and scheduling of specific certifications and job
classifications needed to support the current operations request shall be identified as a
personnel requirement. Properties of the personnel requirement shall be identified as personnel
requirement properties.
NOTE 1 Examples of job classification types include mechanics, operators, health and protection, and
inspectors.
NOTE 2 For example, there may be a requirement for one operator with a specified level of certification available
2 h after production starts. There would be one personnel requirement for the requirement for the
operator and two personnel requirement properties, one for the certification level and one for the time
requirement.
Specific elements associated with each personnel requirement may be included in one or more
personnel requirement properties.
NOTE Examples of personnel requirement property elements are training and certification, specific skill,
physical location, seniority level, exposure level, training certification, security level, experience level,
physical requirements, and overtime limitations and restrictions.
The identification of the number, type, duration, and scheduling of specific equipment and
equipment classifications or equipment constraints needed to support the current operations
request shall be used as an equipment requirement. Properties of the equipment requirement
shall be identified as equipment requirement properties. The operations request may include one
or more equipment requirements. Requirements can be as generic as materials of construction,
or as specific as a particular piece of equipment. Each of these requirements shall be an
instance of the equipment requirement class.
Each equipment requirement identifies a general class of equipment (such as reactor vessels), a
specific class of equipment (such as isothermal reactors), or a specific piece or set of equipment
(such as isothermal reactor #7). The specific requirements on the equipment, or equipment class
are listed as equipment requirement property objects.
Specific elements associated with each equipment requirement may be included in one or more
equipment requirement properties.
NOTE Examples of equipment requirement properties are material of construction and minimum equipment
capacity.
Equipment Identifies the associated Widget CNC Drill Micromete Bar code
Class equipment class or set of Polishing Press r scanner
equipment classes of the Machine
requirement for a specific
segment requirement.
Equipment Identifies the associated WPM-19 DP-1 (not (not
equipment set of equipment of applicable) applicable)
the requirement for a specific
segment requirement.
Typically either equipment class
or equipment is specified, but not
both.
Description Contains additional information Specifics the Automated Measurem Warehous
and descriptions of the expected drill press ent tool e bar code
equipment requirement machine to be scanner
used for this
operations
request.
Equipment Defines the expected use of the Production Repair Testing Transport
Use equipment class or equipment.
The identification of the number, type, duration, and scheduling of specific physical assets and
physical asset class constraints needed to support the current operations request shall be used
as a physical asset requirement.
Properties of the physical asset requirement shall be identified as physical asset requirement
properties. The operations request may include one or more physical asset requirements.
Requirements can be as generic as materials of construction, or as specific as a particular piece
of physical asset. Each of these requirements shall be an instance of the physical asset
requirement class.
Specific elements associated with each physical asset requirement may be included in one or
more physical asset requirement properties.
NOTE Examples of physical asset requirement properties are material of construction and minimum physical
asset capacity.
Physical Identifies the associated physical {not applicable} Model 105, {not {not
Asset Class asset model or set of physical XYZ Corp, applicable} applicable}
asset models of the requirement CNC Drill
for a specific segment Press
requirement.
Physical Identifies the associated physical {not applicable} Serial #: {not {not
Asset asset or set of physical assets of 5563442 applicable} applicable}
the requirement for a specific Asset ID:
segment requirement.
44Q56W
Typically either physical asset or
physical asset class is specified,
but not both.
Description Contains additional information {not applicable} Cameroon {not {not
and descriptions of the physical Drill Press applicable} applicable}
asset requirement.
Physical Defines the expected use of the {not applicable} Calibrate {not {not
Asset Use physical asset class or physical applicable} applicable}
asset.
Quantity Specifies the amount of {not applicable} 1 {not {not
equipment resources required for applicable} applicable}
the parent segment, if applicable.
Applies to each member of the
physical asset and physical asset
class sets.
Quantity Unit The unit of measure of the {not applicable} Machine {not {not
of Measure associated quantity, if applicable. applicable} applicable}
Equipment A level definition for the {not applicable} Work Center {not {not
Level associated element in the applicable} applicable}
hierarchy of the physical asset
model
EXAMPLE The following are maintenance examples for Physical Asset Use:
Repair Very frequent action. Take action – may or may not need spares/parts – to
return asset to its condition prior to the event that prompted the request. Does
not necessarily return to original design specs, but the condition immediately
prior to which it was withdrawn from service. Generally performed in place.
Action does not alter the value of the asset or its depreciation. Example: Pulley
belt has broken on an induced draft fan, and the belt needs to be replaced.
Remove Infrequent action. Remove of obsolete asset. Does not involve repair, does not
involve replacement. It is removed from active service, and
salvaged/scrapped/removed from an asset accounting perspective. Example: A
truck off-loading transfer pump – required with former trucking contractor – now
no longer needed as trucks are all pump-equipped to do their own transfer.
Replacement Frequent action, where the entire asset is removed and replaced with an equal
or like asset in terms of asset performance. Conditions are brought up to
original performance of the asset. Action does not alter the value of the asset or
its depreciation. Example: Remove and replace a 25 HP centrifugal transfer
pump.
- 97 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Calibrate Moderate frequency, but skilled action. The asset is calibrated and often
verified (tested/certified) for accuracy and precision. Often associated with field
instrumentation (sensors and valves). A related action is re-calibration or re-
ranging to a differing process requirement. Action does not alter the value of
the asset or its depreciation. Example: the RTD on tank 225 was re-ranged and
calibrated to 0 – 200 degrees F.
Modify/improve Relatively frequent. Often involving some elements of design, this involves
altering the original asset design to improve its usability and performance in
operations. This alters its design to make it perform better. Because of this, its
asset value has increased by the amount of capital invested to make this
improvement. Example: A rigid shaft coupling on a 50 hp centrifugal pump is
replaced with a flexible coupler to reduce the frequent bearing and/or seal
failures in the original design. A second (simple example) is to replace a failed
20 hp centrifugal pump with a 30 hp centrifugal pump: rather than replace like
for like, it us up-graded to higher horsepower. Again, its asset value has
increased by the amount of additional capital invested to make this improvement
(30 hp vs. 20 hp pump).
Table 66 defines the attributes for physical asset requirement property objects.
Physical asset requirement properties may contain nested physical asset requirement properties.
Assembly Optional: Defines the type of the Permanent Transient Permanent Transient
Relationship relationships. The defined types
are:
Permanent – An assembly that is
not intended to be split during the
production process.
Transient – A temporary
assembly using during
production, such as a pallet of
different materials or a batch kit.
Note 2 If material lots (or sublots)
are merged or absorbed (e.g.
blended), then this is a new material
lot, as defined in Part 1 of this
standard, not an assembly.
NOTE * Typically either a material class, material definition, material lot, or material sublot is specified.
Defined values for material use for production operations shall be: consumable, consumed,
produced.
Defined values for material use for maintenance operations shall be: consumable, replaced
asset, replacement asset
Defined values for quality operations shall be: consumable, sample, returned sample
Defined values for material use for inventory operations shall be: consumable, carrier, returned
carrier
Quantity Unit Identifies the unit of measure of Units {not {not {not
of Measure the quantity if applicable. applicable} applicable} applicable}
The identification of the information sent back as a result of the production request is a
requested segment response. This information is of the same form as a segment response, but
without actual values. (see the Clause 6.3.4)
A requested segment response may include required information, which presents information
reported on from production, such as the actual amount of material consumed.
A requested segment response may include optional information, which presents information that
may be reported on from production, such as operator-entered comments.
Operations
Performance
Is made up of
1..n
May correspond
May correspond to a >
Operations to an < Operations Operations
Definition Response Request
0..n 0..1
Is made up of
1..n
May correspond
to an <
Segment
Process Segment
Corresponds Response May contain
to a <
May contain 0..n
The responses from manufacturing that are associated with an operations request shall be used
as operations responses. There may be one or more operations responses for a single
operations request if the manufacturing facility needs to split the operations request into smaller
elements.
An operations response may include the status of the request, such as the percentage complete,
a finished status, or an aborted status.
NOTE 1 A response actual may contain information that defines if the response was required or optional when
the segment response is used as a requested segment response.
EXAMPLE There may be multiple segments defined. There may be one master segment = that applies to the
entire operations response. The master segment is made up of multiple nested segments for
individually reported segments =.
Information that applies across all segments of the operations response, such as a final material
produced, may be represented as a material produced in the master segment.
Information that applies to specific segments, such as widget polishing equipment actually used may be
reported as part of the polishing segment.
Other information related to the actual operations made shall be presented as segment data.
Personnel actuals shall include the identification of each resource used, usually identifying a
specific personnel capability or personnel class, such as end-point transmission assembly
operators, or personnel IDs such as Jean Smith or SS# 999-123-4567.
Specific information about personnel actuals shall be listed in personnel actual properties.
− the actual duration of use of the personnel during the product segment, such as 2 h; this information is often
needed for actual costing analysis;
− actual monitored exposure times by the personnel during the product segment;
− the location of the personnel after use in the product segment, such as area 51; this information is often used for
short-term scheduling of personnel resources.
Personnel Defines the actual use of the Allocated Certified {not {not
Use personnel class or person. applicable} applicable}
Equipment actual shall include the identification of the equipment used, usually identifying a
specific piece of equipment.
Specific information about equipment actuals shall be listed in equipment actual properties.
− the actual duration of use of the equipment during the product segment; this information is often needed for actual
costing analysis;
− the equipment condition, after use in the product segment, such as a status of available, out-of-service, or
cleaning; this information is often used for short-term scheduling of equipment resources;
− the equipment set-up procedures used for the product segment; this information is often needed for actual costing
analysis and scheduling feedback;
Value The value or set of values for the Dry 0 {not (not
associated property. For applicable} applicable)
example: Wet, Dry.
Value Unit of The unit of measure of the (not applicable) Number of {not (not
Measure associated property value, if Holes applicable} applicable)
applicable.
Quantity Specifies the amount of .05 2 {not (not
equipment resources used in applicable} applicable)
parent segment, if applicable
Quantity Unit Identifies the unit of measure of Machine Hours Tests {not (not
of Measure the quantity, if applicable. applicable} applicable)
An identification of a physical asset capability used during a specified segment shall be identified
as an physical asset actual. Operations functions often require physical asset as a resource to
carry out tasks.
Physical asset actual shall include the identification of the physical asset used, usually
identifying a specific piece of physical asset.
Specific information about physical asset actuals shall be listed in physical asset actual
properties.
Physical Identifies the associated physical {not applicable} CNC Drill {not {not
Asset Class asset class or set of physical Press applicable} applicable}
asset classes actually used for a >
specific segment response.
Physical Identifies the associated physical {not applicable} Serial #: {not {not
Asset asset or set of physical assts 5563442 applicable} applicable}
actually used for a specific
Asset ID:
segment response. 44Q56W
Typically either physical asset
class or physical asset is
specified, but not both.
Description Contains additional information {not applicable} Cameroon {not {not
and descriptions of the physical Drill Press applicable} applicable}
asset actual
Physical Defines the actual use of the {not applicable} Calibrated {not {not
Asset Use physical asset class or physical applicable} applicable}
asset.
Example for maintenance:
Repaired, Removed,
Replacement, Calibrated,
Modified/Improved
Quantity Specifies the amount of {not applicable} 1 {not {not
equipment resources used in applicable} applicable}
parent segment, if applicable.
Applies to each member of the
equipment and equipment class
sets.
Quantity Unit Identifies the unit of measure of {not applicable} Machine {not {not
of Measure the quantity, if applicable. applicable} applicable}
Table 78 defines the attributes for physical asset actual property objects.
Physical asset actual properties may contain nested physical asset actual properties.
- 113 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
An identification of a material that was used in the operations request shall be presented as a
material actual. Material actual contain definitions of materials that may have be consumed,
produced, replaced, sampled, or otherwise used in manufacturing.
Assembly Optional: Defines the type of the Physical Physical Logical Physical
Type assembly. The defined types are:
Physical – The components of
the assembly are physically
connected or in the same area.
Logical – The components of the
assembly are not necessarily
physically connected or in the
same area.
Assembly Optional: Defines the type of the Permanent Transient Permanent Transient
Relationship relationships. The defined types
are:
Permanent – An assembly that is
not intended to be split during the
production process.
Transient – A temporary
assembly using during
production, such as a pallet of
different materials or a batch kit.
NOTE * Typically either a material class, material definition, material lot, or material sublot is specified.
A material actual may be defined as containing an assembly of material actuals and as part of an
assembly of material actuals:
Operations capability information is the collection of information about all resources for
operations for selected future and past times. This is made up of information about equipment,
material, personnel, and process segments. Operations capability describes the names, terms,
statuses, and quantities of which the manufacturing control system has knowledge.
Figure 16 is the operations capability model that applies to production, maintenance, quality test
and inventory.
- 117 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Operations
Capability
Is a
1 collection of
Process
Segment Personnel Equipment Physical Asset Material
Capability Capability Capability Capability Capability 0..n
Is assembled
Has properties Has properties Has properties Has properties
from
of 1 of 1 of 1 of 1
Hierarchy Identifies where the exchanged Boston Widget CNC Test Cell 4 Warehous
Scope information fits within the role Company Machine eB
Receiving
based equipment hierarchy.
Asset ID
Zero or more as required to 13465
identify the specific scope of the
operations capability definition.
NOTE For example, 3 horizontal drill press operators available for the third shift on 2000-02-29.
Hierarchy Identifies where the exchanged South Shore CNC Test Cell 4 (not
Scope information fits within the role Work Plant Machine applicable)
Receiving
based equipment hierarchy.
Asset ID
If omitted, then the capability is 13465
associated to the parent
operations capability hierarchy
scope.
Zero or more as required to
identify the specific scope of the
operations capability definition.
Personnel Defines the expected capability (not applicable) (not (not (not
Use use of the personnel class or applicable) applicable) applicable)
person.
Start Time The starting time associated with 1999-12-30 10-28-2006 10-28- (not
the personnel capability. 11:59 2:00 UTC 2006 applicable)
00:00 UTC
If omitted, then the capability is
associated to the parent
operations capability start time.
End Time The ending time associated with 2000-01-01 10-28-2006 10-28- (not
the personnel capability. 12:00 2:15 UTC 2006 8:00 applicable)
UTC
If omitted, then the capability is
associated to the parent
operations capability end time.
Quantity Specifies the quantity of the 48 1 1 (not
personnel capability defined, if applicable)
applicable.
Quantity Unit The unit of measure of the Hours Full Time Full Time (not
of Measure associated quantity, if applicable. Equivalent Equivalent applicable)
- 121 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Where persons are members of multiple personnel classes then the personnel capability
information defined by personnel class should be used carefully because of possible double
counts, and personnel resources should be managed at the instance level.
Value Unit of The unit of measure of the (not applicable) Boolean Boolean (not
Measure associated property value, if applicable)
applicable.
Quantity Specifies the quantity of the 16 (not (not (not
personnel capability defined, if applicable) applicable) applicable)
applicable.
Quantity Unit The unit of measure of the Hours (not (not (not
of Measure associated quantity. applicable) applicable) applicable)
Specific equipment capabilities shall be used in equipment capability properties. The equipment
capability properties may include the quantity of the resource referenced.
Equipment Identifies the associated Widget Lathe CNC Drill Micromete (not
Class equipment class of the capability. Press r applicable)
Hierarchy Identifies where the exchanged South Shore CNC Test Cell 4 (not
Scope information fits within the role Work Plant Machine applicable)
Receiving
based equipment hierarchy.
Asset ID
If omitted, then the capability is 13465
associated to the parent
operations capability hierarchy
scope.
Zero or more as required to
identify the specific scope of the
operations capability definition.
Equipment Defines the expected capability (not applicable) (not (not (not
Use use of the equipment class or applicable) applicable) applicable)
equipment.
Start Time The starting time associated with 1999-12-30 10-28-2006 10-28- (not
the equipment capability. 11:59 2:00 UTC 2006 applicable)
00:00 UTC
If omitted, then the capability is
associated to the parent
operations capability start time.
End Time The ending time associated with 2000-01-01 10-28-2006 10-28- (not
the equipment capability. 12:00 2:15 UTC 2006 8:00 applicable)
UTC
If omitted, then the capability is
associated to the parent
operations capability end time.
Quantity Specifies the quantity of the 48 1 1 (not
equipment capability defined, if applicable)
applicable.
Quantity Unit The unit of measure of the Hours Machine Tool (not
of Measure associated quantity, if applicable. applicable)
Where equipment are members of multiple equipment classes then the equipment capability
information defined by equipment class should be used carefully because of possible double
counts, and equipment resources should be managed at the instance level.
- 123 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Value Unit of The unit of measure of the Liters Inches {not (not
Measure associated property value, if applicable} applicable)
applicable.
Quantity Specifies the quantity of the 12 {not 1 (not
equipment capability defined, if applicable} applicable)
applicable.
Quantity Unit The unit of measure of the Hours {not Each (not
of Measure associated quantity. applicable} applicable)
A representation of the capability of a physical asset of class of physical assets (physical asset
class) that is committed, available, or unattainable for a specific time shall be used as an
physical asset capability. Physical asset capability may contain references to either physical
asset or physical asset class.
Specific physical asset capabilities shall be used in physical asset capability properties. The
physical asset capability properties may include the quantity of the resource referenced.
Physical Identifies the associated physical Jones Model Model 105, {not (not
Asset Class asset class of the capability. 23 Lathe XYZ Corp, applicable} applicable)
CNC Drill
Press
Physical Identifies the associated physical Machine Serial #: {not (not
Asset asset of the capability. #99298 5563442 applicable} applicable)
Asset ID:
44Q56W
Description Contains additional information Widget Lathe Cameroon {not (not
and descriptions of the physical availability Drill Press applicable} applicable)
asset capability definition. over the 2000
New Year
boundary
Capability The capability type: Used, Unattainable Committed {not (not
Type Unused, Total, Available, applicable} applicable)
Unattainable, or Committed.
Reason Defines the reason for the Due to Y2K Scheduled {not (not
capability type. Non calibration applicable} applicable)
compliance
Confidence A measure of the confidence of 90% 100% {not (not
Factor the capacity value. applicable} applicable)
Hierarchy Identifies where the exchanged South Shore CNC {not (not
Scope information fits within the role Work Plant Machine applicable} applicable)
based equipment hierarchy.
Asset ID
If omitted, then the capability is 13465
associated to the parent
operations capability hierarchy
scope.
Zero or more as required to
identify the specific scope of the
operations capability definition.
Physical Defines the expected capability {not applicable} {not {not (not
Asset Use use of the physical asset class or applicable} applicable} applicable)
physical asset.
Start Time The starting time associated with 1999-12-30 10-28-2006 {not (not
the physical asset capability. 11:59 2:00 UTC applicable} applicable)
Table 85 defines the attributes for physical asset capability property objects.
Physical asset capability properties may contain nested physical asset capability properties.
Value Unit of The unit of measure of the Liters Inches {not (not
Measure associated property value, if applicable} applicable)
applicable.
Quantity Specifies the quantity of the 12 {not {not (not
physical asset capability defined, applicable} applicable} applicable)
if applicable.
Quantity Unit The unit of measure of the Hours {not {not (not
of Measure associated quantity. applicable} applicable} applicable)
Specific material capabilities shall be listed in material capability properties. The material
capability properties may include the quantity of the material referenced.
NOTE For example, 3 sublots in building 3 of material starch lot #12345 committed to production for 2000-02-29.
Material Identifies the associated material Lubricant Oil Aluminum {not (not
Class class of the capability.* applicable} applicable)
Material Identifies the associated material Lube Oil 8999 Aluminum {not (not
Definition definition of the capability.* sheet applicable} applicable)
Material Lot Identifies the associated material 8999LU-5G DW94 {not (not
lot of the capability.* applicable} applicable)
Description Contains additional information Lubricant oil Blank sheet {not (not
and descriptions of the material commitment to run test on applicable} applicable)
capability definition. over the 2000
New Year
boundary
Capability The capability type: Used, Committed Committed {not (not
Type Unused, Total, Available, applicable} applicable)
Unattainable, or Committed.
Reason Defines the reason for the Available for Scheduled {not (not
capability type. Work calibration applicable} applicable)
Hierarchy Identifies where the exchanged Work Line 15 CNC {not (not
Scope information fits within the role Machine applicable} applicable)
based equipment hierarchy.
Asset ID
If omitted, then the capability is 13465
associated to the parent
operations capability hierarchy
scope.
Zero or more as required to
identify the specific scope of the
operations capability definition.
Material Use Defines the expected capability Consumed Committed {not (not
use of the material. applicable} applicable)
Assembly Optional: Defines the type of the Physical Physical Logical Physical
Type assembly. The defined types are:
Physical – The components of
the assembly are physically
connected or in the same area.
Logical – The components of the
assembly are not necessarily
physically connected or in the
same area.
Assembly Optional: Defines the type of the Permanent Transient Permanent Transient
Relationship relationships. The defined types
are:
Permanent – An assembly that is
not intended to be split during the
production process.
Transient – A temporary
assembly using during
production, such as a pallet of
different materials or a batch kit.
NOTE 1 * Typically either a material class, material definition, material lot, or material sublot is specified.
Where materials are members of multiple material classes then the material capability
information defined by material class should be used carefully because of possible double
counts, and material resources should be managed at the instance level.
Value The value, set of values, or range 6.3 3x5 {not (not
of the property. applicable} applicable)
A process segment capability is related to a process segment that can occur during operations.
Is a collection of
Table 90 lists the attributes of process segment capability. Process segment capability has an
equivalent structure to the personnel, equipment and material structure of operations capability,
except the process segment capability is defined for a specific process segment.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 130 -
Process segment capabilities should be used carefully because of possible double counts of
resources.
EXAMPLE A resource may be shown as available in multiple process segments, but in actual fact may be available
for use in only a single process segment.
Figure 18 provides an informative illustration of how the object models inter-relate. The
operations information presents what was made and what was used. Its elements correspond to
information in operations scheduling that listed what to make and what to use. The operations
- 131 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
The slanted rectangles in Figure 18 represent any of the resources (personnel, equipment, or
material) or properties of the resources.
Operations Operations
Capability Information Information
What is available What to make and results
Operations Operations
to a
May correspond
Operations
to a
May correspond
to a
Must correspond
to a
Must correspond
to a
to a
May correspond
to a
May correspond
to a
May correspond
to a
May correspond
to a
May correspond
to a
May correspond
NOTE Both resource capability properties and operation segment’s operations specifications/properties map
their properties to the process segment’s resource specification/ properties. They may be subsets of
the process segment’s resource specification /properties where capability properties are used to
evaluate availability and product segment properties may be used to determine requirement specifics for
scheduling.
Table 91 provides a cross-reference between the elements of the information flows in the data
flow model and the corresponding clause describing the object model.
6.5.2 Schedule Production scheduling Production control (3.0) 6.2 and A.2
(2.0)
6.5.3 Production from Production control (3.0) Production scheduling 6.3 and A.3
plan (2.0)
6.5.4 Production Production control (3.0) Production scheduling 6.4 and A.4
capability (2.0)
6.5.5 Material and energy Material and energy Procurement (5.0) Described in terms of the
order requirements control (4.0) material model, 5.4.
6.5.6 Incoming order Material and energy Procurement (5.0) Described in terms of the
confirmation control (4.0) material model, 5.4.
6.5.7 Long-term material Production scheduling Material and energy Described in terms of the
and energy requirements (2.0) control (4.0) material model, 5.4.
6.5.8 Short-term material Production control (3.0) Material and energy Described in terms of the
and energy requirements control (4.0) material model, 5.4.
6.5.9 Material and energy Material and energy Production control (3.0) Described in terms of the
inventory control (4.0) material model, 5.4.
6.5.10 Production cost Product cost accounting Production control (3.0) 6.2 and A.2
objectives (8.0)
6.5.11 Production Production control (3.0) Product cost accounting 6.3 and A.3
performance and costs (8.0)
6.5.12 Incoming material Material and energy Product cost accounting <Not detailed in object
and energy receipt control (4.0) (8.0) model>
6.5.13 Quality assurance Quality assurance (6.0) Production control (3.0) 5.4 and 6.3
results
6.5.14 Standards and Marketing and sales Quality assurance (6.0) 6.1 and A.1
customer requirements
Quality assurance (6.0) Production control (3.0)
6.5.15 Product and Research, development, Quality assurance (6.0) 6.1 and A.1
process requirements and engineering
6.5.16 Finished goods Order processing (1.0) Quality assurance (6.0) <Not detailed in object
waiver model>
Typically unstructured
information handled on
an ad hoc basis
6.5.17 In-process waiver Production control (3.0) Quality assurance (6.0) Described in terms of the
request material model, 5.4.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 134 -
6.5.18 Finished goods Product inventory control Production scheduling Described in terms of the
inventory (7.0) (2.0) material model, 5.4.
6.5.19 Process data Production control (3.0) Quality assurance (6.0) 6.3 and A.3
6.5.20 Pack-out schedule Production scheduling Product inventory control 6.2 and A.2
(2.0) (7.0)
6.5.21 Product and Research, development, Production control (3.0) <Not detailed in object
process know-how and engineering model>
6.5.22 Product and Production control (3.0) Research, development, <Not detailed in object
process information and engineering model>
request
6.5.27 Product and Production control (3.0) Research, development, <Not detailed in object
process technical and engineering model>
feedback
6.5.29 Production order Order processing (1.0) Production scheduling <Not detailed in object
(2.0) model>
6.5.30 Availability Production scheduling Order processing (1.0) <Not detailed in object
(2.0) model>
6.5.31 Release to ship Product shipping Product inventory control <Not detailed in object
administration (9.0) (7.0) model>
6.5.32 Confirm to ship Product inventory control Product shipping <Not detailed in object
(7.0) administration (9.0) model>
8 List of objects
The following tables present a complete list of the objects discussed in this standard.
- 135 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Object Model
Object Model
9 Compliance
b) The object models supported (Personnel, Material, Equipment, Process Segment, Operations
Capability, Operations Definition, Operations Schedule, Operations Performance, Production
Capability, Process Segment Capability, Product Definition, Production Schedule, and
Production Performance)
Annex A
(Normative)
Production specific information
The production specific model is a specialized subset of the operations model with alternative
object names for purposes of backward compatibility. New implementations should use the
operations models.
The product definition is shown in Figure 19. It defines the shared information between product
production rule, bill of material, and bill of resources. These three external models are
represented by packages in Figure 19; their definitions are outside the scope of this standard.
Product production rules are defined as the information used to instruct a production operation
how to perform the operation. Product production rules are production specific operations
instructions. These may be called a general, site or master recipe (IEC 61512-1 and ANSI/ISA-
88.01-1995 definition), standard operating procedure (SOP), standard operating conditions
(SOC), routing, or assembly steps based on the production strategy used.
A product definition contains a listing of the exchanged information about a product. The
information is used in a set of product segments. A product definition has a reference to a bill of
materials, a product production rule, and a bill of resources.
The attributes of a product definition are the same as an operations definition, as defined in
Clause 6.1, except that Operations type is optional and if defined shall have the value
“Production”.
The identification of the material or material classes that are needed for production of the
product shall be known as a manufacturing bill. Manufacturing bill objects contain an
identification of materials that make up the items of a complete manufacturing bill.
The manufacturing bill includes all uses of the material in production of the product, while the
product segment material specification gives just the amount used in a segment of production.
NOTE For example, a manufacturing bill may identify 55 Type C left-threaded screws, where 20 are used in
one product segment, 20 in another product segment, and 15 in a third product segment.
The attributes of manufacturing bill are the same as the attributes for an operations material bill
defined in Table 44.
The attributes of a manufacturing bill item are the same as the attributes for an operations
material bill item defined in Table 45.
The values needed to quantify a segment for a specific product shall be a product segment. A
product segment identifies, references, or corresponds to a process segment. A product segment
is related to a specific product, while a process segment is product independent.
NOTE Examples include the requirement of a specific number of operators with specific qualifications.
The collection of product segments for a product gives the sequence and ordering of segments
required to manufacture a product in sufficient detail for production planning and scheduling. The
corresponding product production rule presents the additional detail required for actual
production.
A product segment shall use zero or more resources, which correspond to an equipment
specification, a personnel specification or a material specification. A product segment may have
parameter values for parameters specified in the corresponding process segment.
- 141 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
A product segment may have a reference to a product production rule that corresponds to the
rules required to implement the specific product segment when more granularity is needed than
one product production rule for the product definition.
EXAMPLE There may be a Master Recipe (IEC 61512) for each product segment.
The attributes of a product segment are the same as an operations segment, as defined in
Clause 6.1, except that operations type is optional and if defined shall have the value
“Production”.
The attributes for a product parameter are the same as the attributes for a parameter, as defined
in Clause 6.1.6
The attributes for a product segment dependency are the same as the attributes for a process
segment task dependency, as defined in Clause 6.1.15.
Production
Schedule
Is made up of
1..n
May correspond
Product
to a < Production
Production
Request
Rule
Is made up of
May be made up of
Corresponds 1..n 1..n 1..n 1..n
to Personnel Equipment Physical Asset Material
Requirement Requirement Requirement Requirement
Property Property Property Property
Parameter
Specification Personnel Equipment Physical Asset Material
Model Model Model Model
NOTE The previous version of this standard contained specific objects for each use type of materials. These
objects were removed from this version. The removed objects are: Material Produced Requirement,
Material Consumed Requirement, and Consumable Expected. An attribute of the Material Requirement
Property is to be used to determine the use of the material.
A request for production shall be listed as a production schedule. A production schedule shall be
made up of one or more production requests.
The attributes for production schedule are the same as operations schedule defined in Table 57,
except that the operations type attribute is optional, and if specified shall be “Production”.
A request for production for a single product identified by a product production rule shall be
shown as a production request. A production request contains the information required by manu-
facturing to fulfill scheduled production. This may be a subset of the business production order
information, or it may contain additional information not normally used by the business system.
- 143 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
A production request may identify or reference the associated product production rule. A
production request shall contain at least one segment requirement, even if it spans all production
of the product. If not uniquely given by the product production rule, then a segment requirement
shall contain at least one material produced requirement with the identification, quantity, and
units of measure of the material to be produced.
The attributes of a production request are the same as an operations request and are defined in
Table 58.
Information contained in the enterprise system that is required by the operation system for
correct production shall be known as production parameters.
Production parameters may be either product parameters that show some characteristics of the
product (such as paint color), or process parameters that present some characteristics of the
production process (such as bake time).
− quality limits;
− set points;
− targets;
− transportation information;
− other information not directly related to control (such as a customer order number required for labeling or
language for labels).
The attributes for a production parameter are the same as for a segment parameter and are
listed in Table 60.
Production
Performance
Is made up of
1..n
Production
Response
Is made up of
1..n
Corresponds
Product
to a < Segment
Segment or
Response May contain
Process Segment
NOTE The previous version of this standard contained specific objects for each use type of materials. These
objects were removed from this version. The removed objects are: Material Produced Actual, Material
Consumed Actual, and Consumable Actual. An attribute of the Material Requirement Property is to be
used to determine the use of the material.
The performance of the requested production requests shall be listed as production performance.
Production performance shall be a collection of production responses.
The attributes for production performance shall be the same as the attributes for operations
performance as defined in Table 69, except that the operations type attribute is optional and if
specified shall be “Production”.
The responses from manufacturing that are associated with a production request shall be used
as production responses. There may be one or more production responses for a single
production request if the production facility needs to split the production request into smaller
elements of reported production.
- 145 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
NOTE For example, a single production request for the production of 200 gears may be reported on by 10
production response objects of 20 gears each because of manufacturing restrictions.
Production responses contain the items reported back to the business system, at the end of
production or during production. The business system may need to know intermediate production
response statuses, rather than waiting for the final production response status, because of cost
accounting of material produced or intermediate materials.
The attributes for production response shall be the same as the attributes for operations
response as defined in Table 70, except that the operations type attribute is optional and if
specified shall be “Production”.
Other information related to the actual products made shall be presented as production data.
− specific commercial notes from operations related to the customer order, such as order complete, order
incomplete, or an anticipated completion date and time;
− quality information;
− certification of analysis;
− procedural deviations, such as an identification of an event used in another system and alarm information;
The attributes for production data shall be the same as the attributes of segment data, as defined
in Table 72.
The production capability model is shown in Figure 22. Production capability information is the
collection of information about all resources for production for selected times. This is made up of
information about equipment, material, personnel, and process segments. Production capability
describes the names, terms, statuses, and quantities of which the manufacturing control system
has knowledge.
Production
Capability
Is a
1 collection of
Process
Segment Personnel Equipment Physical Asset Material
Capability Capability Capability Capability Capability 0..n
The attributes of production capability are the same as operations capability as defined in
Table 81.
- 147 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Annex B
(Informative)
Use and examples
This standard is expected to be used in the specification of interfaces (at Level 3 and Level 4)
between new applications, between legacy applications, or between new applications and legacy
applications. That may facilitate the usage of packaged software in a legacy application context,
which may be the most powerful initial use of the standard.
Through the use of this standard the definition of the interface content may be provided faster
and more accurately. In addition the specification of interface content may be easily reused.
This will be facilitated by the correct use of compliance assessments that identify which object
models are supported by the interface content specification.
Part 1 defines the categories of information that should be exchanged between Business
Systems and Manufacturing Operations and Control Systems. Four (4) categories are defined;
• Product Definition
• Production Capability
• Production Schedule
• Production Performance Production Information
Each of these four (4) categories relies on the four (4) resources also defined in Part 1.
• Personnel
• Equipment
• Material
• Process Segment
Part 2 presents the corresponding UML models and attributes for the objects contained in the
UML models. The UML models are software independent descriptions of the data exchange
between Business Systems and the Manufacturing Operations and Control Systems.
UML relies on object-oriented methodology. Very briefly, this means that there are classes,
subclasses and instances (objects). A class can for example be Car, and the instances can be
“Mrs. Mine’s car” or “My car”. A class has attributes, and the instances have values on the
attributes, e.g., the class Car has an attribute “License plate” whereas the Instance “Mrs. Mine’s
car” has the attribute “license plate= ABC 123”.
Example - The following figure shows the UML model for Personnel.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 148 -
Qualification
Test
Specification
< Records the Qualification
0..n 0..n
execution of Test
Defines a Result
Is tested procedure for
0..n by a > obtaining a > 0..n
0..n 0..n
Personnel Person
Class Property < Maps to Property
0..n 0..n
< may contain nested < may contain nested
The model shown in Figure B-1, a copy of Figure 5, defines six (6) classes; person, personnel
class, Person Property, Personnel class property, Qualification test Specification and
Qualification Test Results.
Table B-1 shows the attributes for Person (a copy of Table 5).
This means that the class Person should have ID, Description and Name as attributes.
Figure B-2 shows the class Person with the attributes, and two instances e.g. John Smith and
Lou Brown.
- 149 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Person
ID:
Name:
Description:
A Person A Person
ID; 101 ID; 102
Description: employment number. Description: employment number.
Name; John Smith Name; Lou Brown
In the same manner there is a class for “Personnel Class” (Personnel Class should be thought of
as Personnel Group/Category), the instances used depends on the application but could be e.g.,
engineers, night-shift workers, drilling-machine-operators etc.
Of course certain attributes for Classes will depend on the application. To support application
specific attributes the “Property” should be used. The instances of the Properties will define the
attributes for the corresponding Class. The UML model says that there can be none, one or many
properties linked to the corresponding class as shown in Figure B-3.
Class
0..n
Class Property
This means that all the instances of “Property” will effectively describe attributes to the class.
Each instance of the class will contain values for the attributes.
EXAMPLE Certain attributes for Person as well as for Personnel Class depend on the application, e.g., it might be
useful to exchange info about a person’s date-of-birth in one application but not in another. To support
application specific attributes the “Person Property” or “Personnel Class Property” should be used. The
instances of the Properties will define the attributes for the Person/Personnel Class. The UML model says
that there can be none, one or many properties linked to Person/Personnel Class.
There is a class called Person Property. Each property is uniquely defined by its ID, Description,
Value and Value Unit of Measure, as shown in Figure B-4.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 150 -
Person
Property
ID:
Description:
Value:
Value Unit Of Measure:
The class can have for instances, two for the date of birth, one for John and one for Lou, and two
for shoe sizes, one for John and one for Lou, as shown in Figure B-5.
Person
Property
ID:
Description:
Value:
Value Unit Of Measure:
A Person Property
A Person Property
ID; shoe size
ID; shoe size
This means that each Person (instance) will have info about its properties, as shown in
Figure B-6.
Person
Person Property
0..n
ID: ID:
Name: Description:
Description: Value:
Value Unit Of Measure:
A Person Property
ID; shoe size
A Person
ID; 101 A Person Property
Description: employment number. ID; date of birth
Name; John Smith Description: when John Smith was born.
Value; 23 March 1945
Value Unit of Measure: --
A Person Property
ID; shoe size
A Person
ID; 102 A Person Property
Description: employment number. ID; date of birth
Name; Lou Brown Description: when Lou Brown was born.
Value; 12 June 1955
Value Unit of Measure: --
It is important to note that the classes must be defined within a product as well as support within
a product to create and manipulate instances. However, the specific instances created will
depend on the application.
When designing or creating a system that implements the standard, one must make sure that the
system supports the Classes needed (e.g. Person, Personnel Class, Person Property, Personnel
Class Property etc). To completely comply with the standard all classes defined in the standard
should be supported in the system.
Before the systems are put in execution mode it has to be decided what properties the classes
should have (i.e., what instances the Property Class should have). Of course, only the properties
that need to be exchanged between the systems have to be decided. The reasons this has to be
decided include:
• Due to the internal structure of databases, some databases cannot be enlarged during
execution mode, and therefore it needs to know in advance what properties should be
supported
• Different systems might have different constraints on the naming of the properties e.g., a
maximum length of property-name, the usage of upper and lower case letters.
• Different systems might be developed in different languages, e.g., in one system all
properties are presented in French, whereas in another one, the properties are presented in
English.
During execution, data regarding the instances can be exchanged. The data exchanged can be
implemented in many different forms. One possibility is through databases, another possibility is
through XML and XML schemas that have been developed in accordance with the models of this
standard.
If a database is used for data exchange, then there are many different ways of structuring the
database. Tables B-2 and B-3 are included as examples of a data base structure that can be
used to contain the data. The attribute “Key” indicates a unique value that may be required for
relational integrity.
TABLE: Person
ID Description Name
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 152 -
When the system is in execution the database could contain the information shown in Table B-4
and Table B-5.
TABLE: Person
ID Description Name
If a XML documents are used for data exchange, then there are many different ways of
structuring the documents. The structure for an XML document is defined in a “schema”. A
schema is the equivalent of a data base table definition.
Figure B-7 illustrates a possible XML schema for “Person”. The schema defines a place for ID,
Description, Name, the person properties, and a place to contain the list of Personnel Classes
the person belongs to. A Person (instance) is defined by its ID, Description, Name,
PersonProperty, and PersonnelClassID. The ID, Description and Name, correspond to the
attributes ID, Description and Name defined in this party.
PersonProperty is defined as a complex type that contains the property ID, description, and
value.
<xsd:simpleType name="PersonnelClassIDType">
<xsd:restriction base="xsd:string">
</xsd:restriction>
</xsd:simpleType>
During execution an XML document is created and the values of the attributes are filled in and
exchanged between the systems. Figure B-9 illustrates a sample XML document, matching the
schema above that contains person and person property information.
<PersonType>
<ID> 101</ID>
<Description>Employment Number</Description>
<Name>John Smith</Name >
<PersonProperty>
<ID>date-of-birth</ID>
<Description>indicates when a person is born
</Description>
<Value>1945-03-23</Value>
<Value Unit of Measure> YYYY-MM-DD
</Value Unit of Measure>
<ID>Shoe size</ID>
<Description>indicates the shoe size </Description>
<Value>43</Value>
</ PersonProperty >
<PersonnelClassID>{night-shift-operator, engineer}
</PersonnelClassID>
</PersonType>
The information about an instance (e.g., Product manager or Engineer) of PersonnelClass could
be exchanged in a separate XML schema, as shown in Figure B-10.
<PersonClassType>
<ID>Engineer</ID>
<Description> a registered professional engineer</Description>
<PersonnelClassPropertyType>
<ID>Engineer’s License Number</ID>
<Description>”The official engineer’s license number”
</Description>
</PersonnelClassPropertyType>
</PersonClassType>
Since the XML schemas or the objects and their attributes might not be implemented or called
the same thing inside different systems, it might be required to have an “adapter/translator”
inside the systems. This “adapter/translator” translates from the Part 1 terminology to the
terminology used within the different systems. Figure B-11 illustrates an adaptor that maps
property IDs and property types (date formats).
Person Person
ID: 101 ID: 101
Name: John Smith Name: John Smith
XML Data
Person
Ad Person Ad Person
ID: 101
ID: dob
Property ap Name: John Smith ap Property
ID: date-du-naissance
Description: Birthday ter ter Description: Birthday
Value: 23-03-1945 Value: 1945-03-23
Value Unit Of Measure: DD-MM-YYYY Value Unit Of Measure: YYYY-MM-DD
Person
Property
ID: date_of_birth
Description: Birthday
Value: 1945-03-23
Value Unit Of Measure: YYYY-MM-DD
Annex C
(Informative)
Example data sets
C.1 Introduction
The following sections contain example data sets, based on the Part 2 models and attributes.
This is a simplified example of material information that may be used in the food processing
industry. The example presents shared information about a material class (Pork), a material
definition (Pork 80% Lean), a material lot, and a material sublot. In a full example there may be
multiple material classes and material description information sets that are shared, with lot and
sublot dynamically shared. Indentation of objects is used to illustrate the relationship between
the objects.
Material Class
ID - Pork
Description -
Properties
ID - Lethal Heat
Description - Temperature to kill bacteria
Value - 160
Units of Measure - Degrees F
Material Definition
ID - Pork 80
Description - Boneless pork cut up with a target lean percentage of 80
Value -
Unit of Measure -
Properties
ID - Percentage Lean
Description -
Value - 80
Units of Measure – Percentage
QA Test Specification
ID - JackSpratTest1
Description - Test to determine percent of fat.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 158 -
Version - 1997-04-02
ID - Percentage Fat
Description -
Value - 20
Units of Measure - Percentage
Material Lot
ID - 20000115091345
Description -
Status approved
Properties
ID - Delivery Temperature
Description - Temperature at delivery
Value - 37.5
Units of Measure - Degrees F
QA Test Result
ID - 2000-01-16-4930-TEMP
Description - Internal temperature of pork
Date - 2000-01-16
Result - Failed
Expiration - None
ID - Cut
Description - Cut Date
Value - 2000-01-14
Units of Measure -
ID - Expiration
Description - Expiration Date
Value - 2000-01-17
Units of Measure -
ID - Fat
Description - Actual Percent Fat
Value - 20
Units of Measure – Percent
QA Test Result
ID - 2000-01-16-4930-SPRAT
Description -
Date - 2000-01-16
Result - Pass
Expiration – None
ID - Lean
Description - Actual Percent Lean
Value - 80
Units of Measure – Percent
QA Test Result
ID - 2000-01-16-4930-SPRAT
Description -
Date - 2000-01-16
Result - Pass
Expiration - None
Material SubLot
ID - 20000115091345-1
Description -
Storage Location - Tote 392, Level 3, Rack 49
Value - 200
Unit of Measure - Pounds
- 159 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
ID - 20000115091345-2
Description -
Storage Location - Tote 852, Level 3, Rack 50
Value - 300
Unit of Measure – Pounds
Paper Producer
Deep Woods River Integrated Paper
Site Mill Complex
Wood
Preparation
Plant
Rail Yard Storage
Saw Mill Continuous
Slasher Deck
Splitting
Conveyor
Wood Room
Debarking
Chippers
Screend
Chip Conveyors
Chip Bins/Silos Storage
Grinders
Wood Yard Storage
Pile A
Pile B
Pile C
Steam Plant
Boiler Room
Furnace #1
Stack
ESP Environmental
Controls -
Electrostatic
Precipitator
Boiler #1
Gauges &
Instruments
Pulp Mill -- Batch (product) /
Chemical pulp Continuous
-- Kraft (machine operation)
process
Cooking &
Washing --
wood chips
Chip Storage Storage
White Liquor Storage
Storage
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 160 -
Digester
Blow Tank
Washers
Acid Plant Chemical Recovery
System
Black Liquor Storage
Storage
Evaporators
Recovery
Furnace
Dissolving Tank
Green Liquor Storage
Storage
Slaker
Clarifier
Lime Mud
Washer
White Liquor Storage
Storage
Lime Kiln
Steam Plant
Refuse Boilers
ByProducts Storage
Pulp Processing
Bleaching
Washer Vacuum
Centrifugal
Screening
Pressure
Screening
Pulp Press
Paper Mill Batch (product) /
Continuous
(machine operation)
Beater Room
Beating Engine
#1
Machine Room
Paper Machine West End
#2
Screens
Head Box
Wire Pit
Press
Wet End
Paper machine Dry End
#2
Drying Section
Calendar Stack #1
Calendar Stack #2
Reeeler
Winder
Machine Dri ve
Roll
Handler/Conveyor
Roll Storage Storage
- 161 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Finishing Discrete
Coating
Coater # 1
Coater Mix
Coater
Dryer
Supercalendar #
1
Coater # 2
Supercalendar #
2
Slitting -- Reels
Slitter # 1
Knife Set
Kickup
Conveyor
Sheeting
Sheeter
Stacker
Bundler
Shipping Warehouse Storage
Lumber Mill Lumber / board
Semiconductor Manufacturing
Etch Tools
Furnace Tools
Repeat the above steps over and
over until the wafer of devices is built
Back
End
Passivation Preparation for pad bonding
Bonding
Dicing
Packaging
Test
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 162 -
This is a simplified example of personnel information that might be used in the petrochemical
processing industry. The example lists shared information about personnel classes and persons,
including qualification test information.
Personnel Class
ID - Operator Level A
Description - Top level operator certification for petrochemical plant
ID - Operator Level B
Description - Basic level operator certification for petrochemical plant
ID - Operator
Description - Operators for petrochemical plant
Properties
ID - PC-MTBE-992828
Description - Test to determine level of MTBE certification.
Version - 1997-04-02
ID - Push-Up Certification
Description - Operator is temporarily able to perform the higher up function
Value - TRUE, FALSE
Units of Measure -
Person
ID - 999-63-8161
Description -
Name - John Doe
Properties
ID - PC-MTBE-992828-2000-10-12
Description - Test to determine level of MTBE certification.
Result - Passed
Expiration - 2000-12-15
ID - Push-Up Certification
- 163 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Personnel Classes
ID - Operator
ID - Operator Level B
ID - Fire Team Qualified
This is a simplified example of production capability information for a crude oil pipeline shipment
system. This example illustrates the future committed definition of the capability of a crude oil
pipeline segment, using a specific segment of time.
Production Capability
Material Capability
ID - Viscosity
Value - 104
Unit of Measure - cp (centipoise)
ID - Entry Temperature
Value - 30
Unit of Measure - Deg C
ID - Ground Temperature
Value - 18
Unit of Measure - Deg C
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 164 -
This is a simplified example of production performance information for a crude oil pipeline
shipment system. This example illustrates an example of a day of production for crude oil
pipeline segment.
Production Performance
Production Response
ID - Daily Production
Start Time - August 1,2001 - 6:00
End Time - August 2,2001 - 6:00
Segment Response
ID - Daily Production
Production Data
ID - Average Viscosity
Value - 103
Unit of Measure - cp (centipoise)
ID - Entry Temperature
Value - 32.3
Unit of Measure - Deg C
- 165 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Annex D
(Informative)
Questions and answers about object use
D.1 Introduction
This section contains notes about the expected use of the object models, basically recorded as
notes between committee members.
QUESTION:
In many continuous production facilities the material inflow into the process is an important
element of shared information. Does the product segment present the material inflow into
production, or can it be presented in the product production rule?
ANSWER:
There are no attributes in the product segment - material specification, or the process segment -
material segment specification that detail if the material is produced or consumed.
To be consistent with the rest of the models we should be able to specify the inflow (consumed)
material in either the process segment
or in the product segment (producing a material also consumes a material). This information is
needed for scheduling, so it should be included in the exchanged information. The information
should probably be recorded as a property of either the product segment - material specification
or of the process segment - material segment specification, depending on the industry needs.
QUESTION:
In many continuous and batch industries a single process segment may produce multiple
products. What describes the whole picture that multiple product segments are associated with
a certain process segment?
EXAMPLE In a system where materials A, B and C are used to produce products X and Y at a certain equipment in
a single batch, where Y could be a by-product.
ANSWER:
This part of 62264 does not model the object relationships in IEC 62264-1, so this is a matter of
implementation. The most common approach to this problem seems to be to list a process
segment for the process of consuming (A,B,C) and generating (X,Y).
The process segment - material segment specifications would contain the appropriate ratios
(assuming they are constant), such as [50% A, 30% B, 20% C] to produce [75% X, 25% Y].
There would be product segments for X and Y, but they would not maintain the inflow
(consumed) information in the product segments.
Since the exact relationship between the amounts of material may also be equipment specific,
the most common approach would be to create multiple process segments that show the
consumed and produced materials in the ratios appropriate for each set of unique equipment.
In petrochemical refining and chemical production it is even more complicated, since the ratio of
produced material can vary based on production parameters (such as temperatures of trays in
distillation columns) and on the specific properties of the consumed materials (such as the sulfur
content of the oil). In those cases, if the information needed to be exchanged on a regular basis,
the most common approach would be to extend the process segment - material segment
specifications to include the mathematical relationships, such as an equation, tables, or LP, or a
reference to an LP, equation, or table.
QUESTION:
ANSWER:
A process segment presents a production activity and what resources are needed to execute the
activity, at the level of detail required for business processes, such as planning or costing.
Business segment is a synonym for process segment.
EXAMPLE Making a bicycle frame requires an assembly jig, a bending machine, and an assembler for 30 minutes.
The same resources may be associated with more than one process segment.
A product segment lists what resources are needed to make a specific product, at the level of
detail required for planning or costing.
EXAMPLE What is needed to make a 27-inch bicycle; 2 27-inch wheels, 1 27-inch frame, 1 seat, 15 screws, 1 hour
of a tall test cyclist, etc.
Any specific implementation may require more than one product segment, more than one
process segment, or a combination of both to fully describe a planning or costing view of
production.
The concept of “process segment” is a planning view of production describing the resources
needed for production. In the continuous industries, this usually corresponds to
scheduled/planned operations within production units.
- 167 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
EXAMPLE A process segment in an oil refinery would be the material flowing through a catalytic cracker. The
“segment” of production would be the use of the catalytic cracker. The scheduled element would be
either the flow rate through the cracker, or the total amount of material through the cracker during a
period of time.
In addition, when multiple products are produced from the same process, then process segments
are generally considered a better description of production.
EXAMPLE A distillation process segment (associated with a distillation column) could process many product
segments (one per outflow).
The “product segment” is a planning view of production where the product definition is more
descriptive than the process definition.
EXAMPLE There may be many products made using a “semiconductor chip insertion process”, but the product
definition is the key determination of the product produced, not the process itself.
Process segments are generally considered a sufficient description when the processes are
relatively generic and do not themselves define products. Product segments are important in
flexible-discrete and batch manufacturing, where the ability to include specific characteristics for
each product is possible.
QUESTION:
ANSWER:
Either, and this ambiguity was used on purpose, because the specifying committee had
examples for both cases.
EXAMPLE A production parameter may be a paint color to be used, this could be defined as being in either the
product segment (if each product can be painted a different color in the same production step) or in the
process segment (if all products going through the production step must be painted the same color).
D.6 How class name and property IDs are used to identify elements
QUESTION:
The object models all follow the same pattern of class name, with an optional property ID. How
is that used to identify elements?
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 168 -
ANSWER:
While properties can be used to contain information about resources, they can also be used to
identify subsets of resources.
Resources can sometimes be described using a class name, such as “Operators,” or as class
names plus some differencing property, such as “Operators” with ranking of “Master,” “Standard”
or “Junior.” In the models where a “quantity” is needed, the models all follow the same pattern.
There is always a reference to a class (such as Personnel Capability) that may have an optional
quantity.
EXAMPLE 1 It may require 10 man-hours of operator time available for a shift. If the element described is a subset of
the class, such as only “Master” operators, then a property object is used to contain the discriminating
information, and the quantity information.
EXAMPLE 2 Personnel Property Capability would define 4 man-hours of “Master” operator time available for a shift.
This model allows significant flexibility by allowing a single class definition (e.g., Operators),
without a quantity listing, and multiple property descriptions (e.g., Master, Standard, and Junior
operators) each with their own property definition. The left part of Figure D-1 illustrates how a
Personnel Capability would describe a capability of 8 operators. The right part illustrates how
the capability of different ranking of operators would be defined. The Personnel Capability
Property, Ranking, is used to differentiate the capability of different types of operators.
QUESTION:
ANSWER:
The statements, such as: Where persons are members of multiple personnel classes, then the
personnel capability information presented by personnel class should be used carefully because
of possible double counts, and personnel resources should be managed at the instance level,
are given because when a property is used to show overlapping subsets of a capability, then the
same capability may be double scheduled unless this situation is recognized. Figure D-2 shows
an example where a property of ReactorType presents how many reactors are available. The
total amount of capability is 5, but the sum of all reactors subsets is 6, because 1 reactor can be
qualified as a heating and a mixing type. In this situation the mixing and heating resources
should be scheduled at the instance level in order not to overuse the available resources.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 170 -
Equipment Capability
- Equipment Class = Reactor
- Quantity = 5
QUESTION:
How are routing information and processing capabilities represented in the models?
ANSWER:
In some industries the routing is product specific, such as the route shown in Figure D-3. The left
side of the figure illustrates the assembly of a specific electronic product, with multiple assembly
operations (at G and H). The routing, for a single product (or class of products), is represented
by the product segment dependencies illustrated in the center of Figure D-3. The capability of
the system, for a specific product, can be represented in a set of product segment dependencies,
as illustrated on the right side of Figure D-3.
In this example there could be multiple product routings given, one for each class of products.
A scheduling system would use the product demand, product routing, and process segment
capabilities to generate production schedules.
- 171 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
In some industries, such as continuous production with byproducts, the routing may be
dependent on the processes. In Figure D-4 the routing contains material dependencies
information. The routing information is then used for scheduling. The route in the left side of
Figure D-4 can be represented in a set of process segment definitions (center table in Figure
D-4) and process segment dependency definitions (right table in Figure D-4). The process
segment definitions contain the material production and consumption information. The
consumption and production information within the process segments present additional
constraints and dependencies required for scheduling of material B1, C1, and F1.
QUESTION:
How is the information represented for complex scheduling problems, such as where there is a
complex relationship between equipment and products? An example of this is a paint plant,
where particular products can only be manufactured on specific equipment and yield varies
based on product and equipment.
ANSWER:
There can be a mapping of equipment to process segments. The example shown in Figure D-5
shows sets of equipment A, B, C, and D that correspond to process segments. There might be
multiple elements of equipment (process cells, production lines, production units) associated with
each process segment, or it could correspond to a single piece of equipment.
In this example there can be specific rules for each product, or rules for classes of products.
The product segments for each product would show which process segments are valid. The
capability of each process segment and product combination can be represented in process
segment capability objects. This information can then be used to fill in the information needed
by a scheduling system, such as in a cost/throughput matrix illustrated in the lower right of
Figure D-5. The costing information, and demand information required to determine the optimal
throughput, do not cross the boundary addressed by this standard, but the capacity information
does.
A B C D
Process Segment Capabilities $XA $XB $XC $XD
X 500 450 325 600
500 Kg of Product Class X on Process Segment A
450 Kg of Product Class X on Process Segment B $YA $YB $YC $YD
325 Kg of Product Class X on Process Segment C
Y 0 467 0 0
600 Kg of Product Class X on Process Segment D $ZA $ZB $ZC $ZD
467 Kg of Product Class Y on Process Segment B Z 0 330 521 0
330 Kg of Product Class Z on Process Segment B
$WA $WB $WC $WD
521 Kg of Product Class Z on Process Segment C W
489 Kg of Product Class W on Process Segment D 0 0 0 489
QUESTION:
ANSWER:
The dependency type attribute in the process segment dependency and the product segment
dependency objects may be used to show the dependency. These may be simple dependencies,
such as:
a) One segment follows another segment.
b) One segment cannot follow another segment.
c) Two segments may run in parallel.
d) One segment starts when another segment starts.
e) One segment starts when another segment ends.
f) One segment starts any time after another segment starts.
g) One segment starts any time after another segment ends.
These dependencies may include physical constraints (because of production line layout), or
constraints based on safety (such as prohibiting a “water add” after an “acid fill”), or constraints
based on the chemical or physical processing required to make a product (bicycle wheels must
be assembled before the bicycle final assembly).
More complicated constraints based on timing or other dependencies may also be defined using
the dependency factor attribute.
EXAMPLE 1 The longer a semiconductor wafer is kept unprocessed the more defects are introduced, so there is a
maximum delay allowed between segments of production.
EXAMPLE 2 A material (like cheese or wine) must age between processing segments so there is a minimum time
allowed between segments of production.
Figure D-6 illustrates some of the possible dependencies using timing constraints associated
with product segment dependencies or process segment dependencies. The left side of Figure
D-6 illustrates possible dependencies where overlapped execution of the segment is allowed or
required. The right side of Figure D-6 illustrates dependencies where non-overlapped execution
is allowed or required.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 174 -
Time Time
A A
T T
B B
The dependency type may not only be related to time, but also to other unit of measures. For
example, in Discrete Industry it may be common to specify a dependency between two work task
segments that is based on the amount of product produced rather than on the time elapsed. The
idea is to be able to express a dependency like “Start B after A has started and at least 50% of
product quantity has been produced.”
QUESTION:
Why are there two different models for representing the material produced and material
consumed, as attributes in some objects (production capability model and product definition
model), and as separate objects in the production schedule and production performance models?
ANSWER:
In the production schedule and production performance model, typical implementations had used
these as separate objects, and this information was of major importance. In the other models the
material information usually refers to material consumed, and only rarely seems to be used to
represent produced material. The attribute model was used in these cases so that the object
models would be less complex.
QUESTION:
ANSWER:
In some processes, there are materials that are produced as a side effect of production, such as
wastewater, or recycled materials. These materials may be used in other parts of production, and
their availability may have to be considered in schedules.
- 175 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
QUESTION:
How is a material transfer handled? It is not a request for production, just a request to move
material from one location to another.
ANSWER:
A material transfer can be handled using the production schedule and production performance
models. There are multiple methods; one is to have a process segment defined for a
“TRANSFER.” The material to be transferred could be identified in the material consumed
requirement object. The actual amount of material transferred could be identified in a material
produced actual object. In some processes the two amounts may differ due to losses during
transfer. The material locations for the movements could be identified in the material consumed
sublot and material produced sublot information.
If the movement of material is initiated from the manufacturing operations level but must be
known by the logistics level, then a production response could be generated that defined a
“TRANSFER” segment. There is no requirement in this standard that there must be a production
request for a production response, but corresponding business processes must support the
exchange of information.
Properties are the standard method for extensions, however, where required information cannot
be added using the property model, additional information, including industry- and application-
specific information, may have to be added as non-standard attributes and objects. However, in
order to achieve integration, these extensions have to be documented and explicitly shared
among interoperating partners. A documentation method should be to define a new industry or
application specific standard, referencing this Part and documenting the extensions.
QUESTION:
ANSWER:
Depending on the purpose of the tool, a tool can be modelled as either equipment or as
materials. Tools may be used in different ways, for example tools used in the process of
manufacturing versus tools included in the assembly of the product. Tools that can be consumed
or must be lot traceable would be modelled as material. Other tools could be modelled as
equipment. Some examples:
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 176 -
Equipment Material
Hammer Nail
QUESTION:
Does there need to be a one-to-one relationship between physical asset and equipment?
ANSWER:
There are cases of one-to-one relationships, and one-to-many relationships in each direction.
One item that is scheduled as a single piece of equipment may be tracked as multiple physical
assets for maintenance purposes. Likewise a single physical asset may be scheduled as
multiple pieces of equipment. The relationship with these many to many roles is accomplished
using the mapping of the role based equipment hierarchy to the physical asset hierarchy. One
element in the equipment role hierarchy is a collection of assets in the physical asset hierarchy.
Labeller
Conveyer
Servo Motor
QUESTION:
ANSWER:
There are different types of dependencies (resource availability, customer priority, process
dependency, and other)
For example, an MRP/ERP at level 4 can generate separate requests for subassemblies or a
single request for the final assembly of a given finished product and for the manufacturing of the
intermediate materials that are the subassemblies to be assembled. Of course, there is a work
process dependency relationship and final assembly may start only after all subassemblies have
been manufactured. This is handled in an implementation where a production or work request
states the start time and/or end time and then the associated segment requests specify the
earliest start time, latest end time and duration for each segment. The algorithm for the actual
dispatching of work can be implemented at level 4 or level 3, but represented in the production
schedule or production/operations schedule request.
QUESTION:
ANSWER:
The operation schedule model can handle mixed types of operations. The operation schedule,
operation request and segment requirement can be specialized or mixed:
• A “mixed” operation schedule can hold mixed or specialized operation requests.
• A “mixed” operation request can hold mixed or specialized segment requirements.
• A “mixed” segment requirement can handle multiple resource specifications that would
normally appear in specialized segment.
In the figure, the segment requirement specifies
• the material movements needed to fulfill the corresponding operation (inventory operation
category);
• the resources for the production; the material information should include the dispensed
material and other material those transfer would not need to be specified (liquid substance
available from fixed pipes);
• the quality related resources that are involved during or at the end of the production
operation.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 178 -
Operation Schedule
mixed
Operation Request
mixed
Segment Requirement
Mixed
Material Spec Equipment Spec Material Spec Material Spec Material Spec
Material Spec
Being Moved To Contributing Being Consumed Being Produced Being Tested
Being moved from Being moved to Production Consumed Produced Tested material
D.19 What is the relationship between this standard and WBF’s B2MML
QUESTION:
ANSWER:
B2MML is an implementation of the standard that is based on XML technology and was
developed by and is the property of WBF (ref: www.wbf.org). B2MML includes a compliance
statement (as defined in Clause 9.)
The B2MML implementation includes additional information (elements) than are defined in this
standard, usually for consistency of type definitions or to make use of the implementation easier
when using standard programming languages.
B2MML is not the only way to implement this standard, but B2MML may be used as a reference
implementation of the standard.
The committee developing the B2MML standard also sends comments on this standard to the
committee developing this standard.
QUESTION:
ANSWER:
The standard presents each of these objects with a unique namespace to clarify to the reader of
the standard that these objects represent specific tests and test results, dependent on the
context of usage within each resource model. Representing the models in this way clearly
conveys to the reader the purpose and usage of each of the models within the standard.
Modern data modeling tools can yield multiple levels of optimization; however, these abstracted
data models are not helpful to convey an understanding of how this standard represents
information in this specific problem space. The models have been developed along the lines of
other standards, such as OAGIS and EDI standards, which have proven to be useful standards
for similar reasons.
While the committee members recognize that the models may be represented with a more
optimized view, the purpose of this standard is not to present the most optimized data model. By
further optimizing the data models represented in the standard, the committee feels that the
meaning of these data models and their significance to the standard will be lost leading to
misunderstandings or impractical implementations of the standard. The committee members
also realize that implementations of this standard may employ advanced data modeling
techniques that seek to optimize the representation of certain objects (i.e. using a common
resource model in XML with an element to distinguish its type and maintain its unique
namespace).
This page intentionally left blank.
- 181 - ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod)
Annex E
(Informative)
Logical information flows
E.1 Summary
The personnel model, equipment model, material model, and process segment model are
collectively referred to as the resource models.
Systems communicating using the product capability, product definition, production schedule,
and production performance models have to agree on the meaning of data values.
The objects in the resource models document the agreed upon values.
The assumption is that the resource model information is shared among communicating systems.
The resource model information may be embedded as part of an information flow for other
objects, may be exchanged as separate objects, or may be part of a common or distributed data
store.
The Part 1 object model does not assume a one-to-one relationship between enterprise systems
and manufacturing control systems. These may be one-to-many, many-to-one, or many-to-many
relationships.
EXAMPLE Examples of the exchanges include contract manufacturing being performed for multiple customers
(many-to-one), and a single company with multiple different manufacturing control systems (one-to-
many).
Figure E-1 illustrates some possible logical information flows between enterprise systems and
manufacturing control systems.
ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod) - 182 -
Company 1
with manufacturing
Manufacturing
Enterprise
Control
System 1
System 1
Manufacturing
Control
System 2
Manufacturing
Enterprise
Control
System 2
System 3
Company 2 Company 3
with no manufacturing contract manufacturer
The information in this Part 2 standard is independent of any communication protocol. Part 2
makes no assumptions about the agents that create the information and the agents that use the
information. Different implementations of the information model may describe different
communication protocols and will often require additional attributes and objects.
EXAMPLE An SQL implementation will have to identify primary keys and may identify index attributes.
Additionally, the information model does not assume a one-to-one relationship between external
systems and manufacturing control systems. There may be one-to-many, many-to-one, or many-
to-many relationships.
EXAMPLE Examples of the many-to-many exchanges include multiple maintenance systems or quality systems.
Manufacturing
Scheduling Maintenance
Control
System System 1
System 1
Manufacturing
Maintenance
Control
System 2
System 2
Manufacturing Quality
Costing
Control System
System
System 3
Bibliography
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-48-6