AutomationML - Provisioning for MES and ERP · 2019. 1. 7. · Application Recommendation Provisioning for MES and ERP – Support for IEC 62264 and B2MML Release Date: November 7,

Application Recommendation Provisioning for MES and ERP – Support for

IEC 62264 and B2MML

Release Date: November 7, 2018

ID: AR-MES-ERP

Version: 1.1.0

Compatibility: AutomationML 2.0 (CAEX 2.15)

AR-MES-ERP 1.1.0 2

Provisioning for MES and ERP

Author: Bernhard Wally [email protected] Business Informatics Group, CDL-MINT, TU Wien

mailto:[email protected]

https://www.big.tuwien.ac.at/

https://www.tuwien.ac.at/

AR-MES-ERP 1.1.0 3


Table of Content

Table of Content .............................................................................................................................................. 3

List of Figures .................................................................................................................................................. 6

List of Tables .................................................................................................................................................... 7

List of Code Listings ..................................................................................................................................... 11

Provided Libraries .................................................................................................................. 12

I.1 Role Class Libraries ............................................................................................................................ 12

I.2 Interface Class Libraries ..................................................................................................................... 12

Referenced Libraries .............................................................................................................. 12

II.1 Role Class Libraries ............................................................................................................................ 12

II.2 Interface Class Libraries ..................................................................................................................... 12

Referenced Documents ......................................................................................................... 13

1 Introduction ................................................................................................................................................ 14

1.1 Provisioning for ERP and MES ........................................................................................................... 14

1.2 IEC 62264 ........................................................................................................................................... 15

1.2.1 Personnel .................................................................................................................................... 15

1.2.2 Equipment ................................................................................................................................... 15

1.2.3 Physical Asset ............................................................................................................................. 16

1.2.4 Material ........................................................................................................................................ 16

1.2.5 Process Segment ........................................................................................................................ 16

1.3 Structure of this Document ................................................................................................................. 16

2 Terms, Definitions and Abbreviations ..................................................................................................... 17

2.1 Terms and Definitions ......................................................................................................................... 17

2.2 Abbreviations ...................................................................................................................................... 17

2.3 Conformity ........................................................................................................................................... 17

3 Mapping of IEC 62264-2 to AutomationML .............................................................................................. 18

3.1 IEC 62264-2 Common Object Models ................................................................................................ 18

3.1.1 Hierarchy Scope .......................................................................................................................... 18

3.1.2 Personnel .................................................................................................................................... 19

3.1.3 Equipment ................................................................................................................................... 20

3.1.4 Physical Asset ............................................................................................................................. 21

3.1.5 Material ........................................................................................................................................ 23

3.1.6 Process Segment ........................................................................................................................ 25

3.2 IEC 62264-2 Operations Management Information ............................................................................ 27

3.2.1 Operations Definition ................................................................................................................... 27

3.2.2 Operations Schedule ................................................................................................................... 29

3.2.3 Operations Performance ............................................................................................................. 31

3.2.4 Operations Capability .................................................................................................................. 33

AR-MES-ERP 1.1.0 4


3.2.5 Process Segment Capability ....................................................................................................... 35

3.3 Visualization of the Mapping ............................................................................................................... 36

4 Related AutomationML Libraries .............................................................................................................. 37

4.1 AutomationML Interface Class Libraries ............................................................................................. 37

4.1.1 AutomationMLInterfaceClassLib ................................................................................................. 37

4.1.2 AutomationMLBPRInterfaceClassLib .......................................................................................... 37

4.2 AutomationML Role Class Libraries ................................................................................................... 38

4.2.1 AutomationMLBaseRoleClassLib................................................................................................ 38

4.2.2 AutomationMLBMIRoleClassLib ................................................................................................. 39

4.2.3 AutomationMLCMIRoleClassLib ................................................................................................. 39

4.2.4 AutomationMLDMIRoleClassLib ................................................................................................. 40

4.2.5 AutomationMLCSRoleClassLib ................................................................................................... 41

4.2.6 AutomationML Extended RoleClass Library (non-normative) ..................................................... 42

4.2.7 AutomationMLBPRRoleClassLib (non-normative) ...................................................................... 43

4.3 Alignment of IEC 62264-2 and AutomationML ................................................................................... 43

4.3.1 Alignment of IEC 62264-2 and AutomationMLBaseRoleClassLib .............................................. 43

4.3.2 Alignment of IEC 62264-2 and Detailed Normative AutomationML Role Class Libraries .......... 46

4.3.3 Alignment of IEC 62264-2 and AutomationMLExtendedRoleClassLib ....................................... 47

5 AML Libraries for Supporting IEC 62264 ................................................................................................. 48

5.1 Interface Class Library AutomationMLIEC62264InterfaceClassLib ................................................... 48

5.2 Role Class Library AutomationMLB2MMLRoleClassLib .................................................................... 51

5.3 Role Class Library AutomationMLIEC62264RoleClassLib ................................................................. 52

5.3.1 Hierarchy Scope .......................................................................................................................... 55

5.3.2 Personnel .................................................................................................................................... 55

5.3.3 Equipment ................................................................................................................................... 59

5.3.4 Physical Asset ............................................................................................................................. 62

5.3.5 Material ........................................................................................................................................ 66

5.3.6 Process Segment ........................................................................................................................ 74

5.3.7 Operations Definition ................................................................................................................... 81

5.3.8 Operations Schedule ................................................................................................................... 90

5.3.9 Operations Performance ........................................................................................................... 100

5.3.10 Operations Capability ................................................................................................................ 109

5.3.11 Process Segment Capability ..................................................................................................... 119

6 Referencing B2MML Files ....................................................................................................................... 120

7 Relation to OPC Unified Architecture .................................................................................................... 121

8 Notes regarding the Examples in the Appendices ............................................................................... 123

References.... ............................................................................................................................................... 124

Appendix A AutomationMLIEC62264InterfaceClassLib ........................................................................ 125

Appendix B AutomationMLIEC62264RoleClassLib ............................................................................... 126

AR-MES-ERP 1.1.0 5


Appendix C AutomationMLB2MMLRoleClassLib ................................................................................... 153

Appendix D Examples for Referencing External B2MML Documents ................................................. 154

D.1 Referencing a B2MML Document from AML .................................................................................... 154

D.2 Referencing a Specific Element within a B2MML Document from AML ........................................... 155

D.3 Process-Product-Resource (PPR) .................................................................................................... 157

Appendix E Example for Modeling IEC 62264 Information within AML Documents .......................... 177

AR-MES-ERP 1.1.0 6


List of Figures

Figure 1: Overview of the engineering data exchange format AML. ............................................................ 14

Figure 2: Typical expanded equipment hierarchy (from [IEC 62264-1], graphically adapted). .................... 15

Figure 3: Hierarchy scope model (from [IEC 62264-2], graphically adapted)............................................... 18

Figure 4: Personnel model (from [IEC 62264-2], graphically adapted). ....................................................... 19

Figure 5: Equipment model (from [IEC 62264-2], graphically adapted). ...................................................... 20

Figure 6: Physical asset model (from [IEC 62264-2], graphically adapted). ................................................. 21

Figure 7: Relationship between equipment information and physical asset information (from [IEC 62264-2], graphically adapted). ..................................................................................................................... 22

Figure 8: Material model (from [IEC 62264-2], graphically adapted). ........................................................... 23

Figure 9: Process segment model (from [IEC 62264-2], graphically adapted). ............................................ 25

Figure 10: Operations definition model (from [IEC 62264-2], graphically adapted). ...................................... 27

Figure 11: Operations schedule model (from [IEC 62264-2], graphically adapted). ...................................... 29

Figure 12: Operations performance model (from [IEC 62264-2], graphically adapted). ................................. 31

Figure 13: Operations capability model (from [IEC 62264-2], graphically adapted). ...................................... 33

Figure 14: Process segment capability model (from [IEC 62264-2], graphically adapted). ............................ 35

Figure 15: Visualization of the mapping from IEC 62264-2 to the CAEX metamodel (left) and to existing AutomationML elements of the AutomationMLBaseRoleClassLib (right). .................................... 36

Figure 16: Usage example for interface class HierarchyScopeConnector. .................................................... 48

Figure 17: Usage example for interface class ResourceConnector. .............................................................. 49

Figure 18: Usage example of interface class EquipmentAssetConnector...................................................... 49

Figure 19: Usage example of interface class DependencyConnector. ........................................................... 50

Figure 20: Usage example for interface class TestConnector. ....................................................................... 50

Figure 21: Composition of transformation/alignment functions: ≠ . ..................................................... 121

Figure 22: Excerpt of the basic information model for AutomationML-based models (cf. [DIN 16592-12]). 121

Figure 23: Excerpt of the basic information model for IEC 62264-based models (cf. [OPC-IEC62264]). .... 121

Figure 24: Referencing corresponding elelements from IEC 62264 and AutomationML in OPC UA. ......... 122

Figure 25: Visualization of the PPR example (from IEC 62714-1). .............................................................. 157

Figure 26: Internal links of the PPR example (from IEC 62714-1). .............................................................. 158

AR-MES-ERP 1.1.0 7


List of Tables

Table 1: Template for the mapping of IEC 62264-2 concepts to AutomationML elements. ........................ 18

Table 2: Mapping of the IEC 62264-2 hierarchy scope model to AML. ....................................................... 18

Table 3: Mapping of the IEC 62264-2 personnel model to AML. ................................................................ 20

Table 4: Mapping of the IEC 62264-2 equipment model to AML. ............................................................... 21

Table 5: Mapping of the IEC 62264-2 physical asset model to AML. .......................................................... 22

Table 6: Mapping of the IEC 62264-2 relationship between equipment information and physical asset information. .................................................................................................................................... 22

Table 7: Mapping of the IEC 62264-2 material model to AML. ................................................................... 24

Table 8: Mapping of the IEC 62264-2 process segment model to AML. ..................................................... 26

Table 9: Mapping of the IEC 62264-2 operations definition model to AML. ................................................ 28

Table 10: Mapping of the IEC 62264-2 operations schedule model to AML. ................................................ 30

Table 11: Mapping of the IEC 62264-2 operations performance model to AML. .......................................... 32

Table 12: Mapping of the IEC 62264-2 operations capability model to AML. ............................................... 34

Table 13: Mapping of the IEC 62264-2 process segment capability model to AML. ..................................... 35

Table 14: InterfaceClasses of the AutomationMLInterfaceClassLib. ............................................................. 37

Table 15: InterfaceClass of the AutomationMLBPRInterfaceClassLib. ......................................................... 37

Table 16: Selected RoleClasses of the AutomationMLBaseRoleClassLib.................................................... 38

Table 17: RoleClass of the AutomationMLBMIRoleClassLib. ....................................................................... 39

Table 18: RoleClass of the AutomationMLCMIRoleClassLib. ....................................................................... 39

Table 19: RoleClasses of the AutomationMLDMIRoleClassLib. ................................................................... 40

Table 20: RoleClasses of the AutomationMLCSRoleClassLib. ..................................................................... 41

Table 21: RoleClasses of the AutomationMLExtendedRoleClassLib. ........................................................... 42

Table 22: RoleClass of the AutomationMLBPRRoleClassLib. ...................................................................... 43

Table 23: Alignment of IEC 62264-2 with AML base role classes. ................................................................ 45

Table 24: Alignment of IEC 62264-2 with more detailed normative AML role classes. ................................. 46

Table 25: Alignment of IEC 62264-2 with the (non-normative) AML extended role class lib. ....................... 47

Table 26: InterfaceClasses needed for supporting concepts of IEC 62264, subsumed in the AutomationMLIEC62264InterfaceClassLib. ................................................................................... 48

Table 27: InterfaceClass HierarchyScopeConnector. ................................................................................... 48

Table 28: InterfaceClass ResourceConnector. .............................................................................................. 49

Table 29: InterfaceClass EquipmentAssetConnector. ................................................................................... 49

Table 30: InterfaceClass DependencyConnector. ......................................................................................... 50

Table 31: InterfaceClass TestConnector. ...................................................................................................... 50

Table 32: RoleClass “B2mmlData” needed for referencing a specific B2MML document, encapsulated in the AutomationMLB2MMLRoleClassLib. ............................................................................................. 51

Table 33: RoleClass B2mmlData. .................................................................................................................. 51

Table 34: RoleClasses needed for supporting concepts from IEC 62264, subsumed in the AutomationMLIEC62264RoleClassLib. ......................................................................................... 54

AR-MES-ERP 1.1.0 8


Table 35: Role class HierarchyScope. ........................................................................................................... 55

Table 36: Role class PersonnelModel. .......................................................................................................... 55

Table 37: Role class PersonnelClass. ........................................................................................................... 56

Table 38: Attribute type PersonnelClassProperty. ......................................................................................... 56

Table 39: Role class Person. ......................................................................................................................... 57

Table 40: Attribute type PersonProperty. ...................................................................................................... 57

Table 41: Role class QualificationTestSpecification. ..................................................................................... 58

Table 42: Role class QualificationTestResult. ............................................................................................... 58

Table 43: Role class EquipmentModel. ......................................................................................................... 59

Table 44: Role class EquipmentClass. .......................................................................................................... 59

Table 45: Attribute type EquipmentClassProperty. ........................................................................................ 60

Table 46: Role class Equipment. ................................................................................................................... 60

Table 47: Attribute type EquipmentProperty. ................................................................................................. 60

Table 48: Role class EquipmentCapabilityTestSpecification......................................................................... 61

Table 49: Attribute type EquipmentCapabilityTestResult. ............................................................................. 62

Table 50: Role class PhysicalAssetModel. .................................................................................................... 62

Table 51: Role class PhysicalAssetClass. ..................................................................................................... 63

Table 52: Attribute type PhysicalAssetClassProperty. .................................................................................. 63

Table 53: Role class PhysicalAsset. .............................................................................................................. 64

Table 54: Attribute type PhysicalAssetProperty. ........................................................................................... 64

Table 55: Role class PhysicalAssetCapabilityTestSpecification. .................................................................. 65

Table 56: Attribute type PhysicalAssetCapabilityTestResult. ........................................................................ 65

Table 57: RoleClass EquipmentAssetMapping. ............................................................................................ 66

Table 58: Role class MaterialModel. .............................................................................................................. 66

Table 59: Role class MaterialClass. .............................................................................................................. 67

Table 60: Attribute type MaterialClassProperty. ............................................................................................ 67

Table 61: Role class MaterialDefinition. ........................................................................................................ 68

Table 62: Attribute type MaterialDefinitionProperty. ...................................................................................... 68

Table 63: Role class MaterialLot. .................................................................................................................. 69

Table 64: Attribute type MaterialLotProperty. ................................................................................................ 70

Table 65: Role class MaterialSublot. ............................................................................................................. 71

Table 66: Role class MaterialTestSpecification. ............................................................................................ 72

Table 67: Attribute type MaterialTestResult. ................................................................................................. 73

Table 68: Role class MaterialAssembly. ........................................................................................................ 73

Table 69: Role class ProcessSegmentModel. ............................................................................................... 74

Table 70: Role class ProcessSegment. ......................................................................................................... 74

Table 71: Attribute type ProcessSegmentParameter. ................................................................................... 75

Table 72: Role class PersonnelSegmentSpecification. ................................................................................. 75

Table 73: Attribute type PersonnelSegmentSpecificationProperty. ............................................................... 76

AR-MES-ERP 1.1.0 9


Table 74: Role class EquipmentSegmentSpecification. ................................................................................ 76

Table 75: Attribute type EquipmentSegmentSpecificationProperty. .............................................................. 77

Table 76: Role class PhysicalAssetSegmentSpecification. ........................................................................... 77

Table 77: Attribute type PhysicalAssetSegmentSpecificationProperty. ........................................................ 78

Table 78: Role class MaterialSegmentSpecification. .................................................................................... 79

Table 79: Attribute type MaterialSegmentSpecificationProperty. .................................................................. 80

Table 80: Role class ProcessSegmentDependency. .................................................................................... 80

Table 81: Role class OperationsDefinitionModel. .......................................................................................... 81

Table 82: Role class OperationsDefinition. ................................................................................................... 81

Table 83: Role class OperationsMaterialBill. ................................................................................................. 82

Table 84: Role class OperationsMaterialBillItem. .......................................................................................... 83

Table 85: Role class OperationsSegment. .................................................................................................... 84

Table 86: Attribute type ParameterSpecification. .......................................................................................... 84

Table 87: Role class PersonnelSpecification. ............................................................................................... 85

Table 88: Attribute type PersonnelSpecificationProperty. ............................................................................. 85

Table 89: Role class EquipmentSpecification. .............................................................................................. 86

Table 90: Attribute type EquipmentSpecificationProperty. ............................................................................ 86

Table 91: Role class PhysicalAssetSpecification. ......................................................................................... 87

Table 92: Attribute type PhysicalAssetSpecificationProperty. ....................................................................... 87

Table 93: Role class MaterialSpecification. ................................................................................................... 88

Table 94: Attribute type MaterialSpecificationProperty. ................................................................................. 89

Table 95: Role class OperationsSegmentDependency. ................................................................................ 89

Table 96: Role class OperationsScheduleModel. .......................................................................................... 90

Table 97: Role class OperationsSchedule. ................................................................................................... 91

Table 98: Role class OperationsRequest. ..................................................................................................... 92

Table 99: Role class SegmentRequirement. ................................................................................................. 93

Table 100: Attribute type SegmentParameter. ................................................................................................ 94

Table 101: Role class PersonnelRequirement. ............................................................................................... 94

Table 102: Attribute type PersonnelRequirementProperty. ............................................................................. 95

Table 103: Role class EquipmentRequirement. .............................................................................................. 95

Table 104: Attribute type EquipmentRequirementProperty. ............................................................................ 96

Table 105: Role class PhysicalAssetRequirement. ......................................................................................... 96

Table 106: Attribute type PhysicalAssetRequirementProperty. ....................................................................... 97

Table 107: Role class MaterialRequirement. ................................................................................................... 98

Table 108: Attribute type MaterialRequirementProperty. ................................................................................ 99

Table 109: Role class RequestedSegmentResponse. .................................................................................. 100

Table 110: Role class OperationsPerformanceModel. .................................................................................. 100

Table 111: Role class OperationsPerformance. ............................................................................................ 101

Table 112: Role class OperationsResponse. ................................................................................................ 102

AR-MES-ERP 1.1.0 10


Table 113: Role class SegmentResponse. ................................................................................................... 103

Table 114: Attribute type SegmentData......................................................................................................... 104

Table 115: Role class PersonnelActual. ........................................................................................................ 104

Table 116: Attribute type PersonnelActualProperty. ...................................................................................... 105

Table 117: Role class EquipmentActual. ....................................................................................................... 105

Table 118: Attribute type EquipmentActualProperty. ..................................................................................... 106

Table 119: Role class PhysicalAssetActual. .................................................................................................. 106

Table 120: Attribute type PhysicalAssetActualProperty. ............................................................................... 107

Table 121: Role class MaterialActual. ........................................................................................................... 108

Table 122: Attribute type MaterialActualProperty. ......................................................................................... 109

Table 123: Role class OperationsCapabilityModel. ....................................................................................... 109

Table 124: Role class OperationsCapability. ................................................................................................. 110

Table 125: Role class PersonnelCapability. .................................................................................................. 111

Table 126: Attribute type PersonnelCapabilityProperty. ................................................................................ 112

Table 127: Role class EquipmentCapability. ................................................................................................. 113

Table 128: Attribute type EquipmentCapabilityProperty. ............................................................................... 114

Table 129: Role class PhysicalAssetCapability. ............................................................................................ 115

Table 130: Attribute type PhysicalAssetCapabilityProperty........................................................................... 116

Table 131: Role class MaterialCapability....................................................................................................... 117

Table 132: Attribute type MaterialCapabilityProperty. ................................................................................... 118

Table 133: Role class ProcessSegmentCapability. ....................................................................................... 119

Table 134: HasAMLIEC62264UAReference ReferenceType. ...................................................................... 122

Table 135: Substitutions in use in Listings 4, 6, 8, and 13. ........................................................................... 123

Table 136: Setup of the PPR example (from IEC 62714-1). ......................................................................... 157

AR-MES-ERP 1.1.0 11


List of Code Listings

Listing 1: AutomationML IEC 62264 interface class library......................................................................... 125

Listing 2: AutomationML IEC 62264 role class library. ............................................................................... 126

Listing 3: AutomationML B2MML role class library. .................................................................................... 153

Listing 4: InstanceHierarchy excerpt of document Example-01-B2MML-Document.aml. .......................... 154

Listing 5: Contents of document Turntable.b2mml. .................................................................................... 154

Listing 6: InstanceHierarchy excerpt of document Example-02-B2MML-Element.aml. .............................. 155

Listing 7: Contents of document Equipment.b2mml. .................................................................................. 156

Listing 8: InstanceHierarchy, RoleClassLib, and SystemUnitClassLib excerpts of document Example-03-B2MML-PPR.aml. ........................................................................................................................ 158

Listing 9: Contents of document PPR-Equipment.b2mml. .......................................................................... 169

Listing 10: Contents of document PPR-PhysicalAssets.b2mml. ................................................................... 170

Listing 11: Contents of document PPR-Material.b2mml. .............................................................................. 172

Listing 12: Contents of document PPR-ProcessSegments.b2mml. .............................................................. 173

Listing 13: InstanceHierarchy, SystemUnitClassLib, and RoleClassLib excerpt of document Example-04-IEC62264-PPR.aml. .................................................................................................................... 177

AR-MES-ERP 1.1.0 12


Provided Libraries

I.1 Role Class Libraries

Role Class Library Name Version Comment

AutomationMLB2MMLRoleClassLib 1.0.0 B2MML Role Class Library

AutomationMLIEC62264RoleClassLib 1.1.0 IEC 62264 Role Class Library

I.2 Interface Class Libraries

Interface Class Library Name Version Comment

AutomationMLIEC62264InterfaceClassLib 1.0.0 IEC 62264 Interface Class Library

Referenced Libraries

II.1 Role Class Libraries

Role Class Library Name Version Comment

AutomationMLBaseRoleClassLib 2.2.2 AML Base Role Class Library

AutomationMLExtendedRoleClassLib 2.7.0 AML Extended Role Class Library (non-normative)

AutomationMLBMIRoleClassLib 1.1.0 AML Batch Manufacturing Industry Role Class Library

AutomationMLCMIRoleClassLib 1.1.0 AML Continuous Manufacturing Industry Role Class Library

AutomationMLDMIRoleClassLib 2.4.0 AML Discrete Manufacturing Industry Role Class Library

AutomationMLCSRoleClassLib 2.3.0 AML Control Industry Role Class Library

AutomationMLBPRRoleClassLib 1.0.0 Best Practice Recommendation: External Data Reference

II.2 Interface Class Libraries

Interface Class Library Name Version Comment

AutomationMLInterfaceClassLib 2.2.2 Standard AML Interface Class Library

AutomationMLBPRInterfaceClassLib 1.0.0 Best Practice Recommendation: External Data Reference

AR-MES-ERP 1.1.0 13


Referenced Documents

Document-ID Version Comment

WP-Part1 2.0.0 AML Whitepaper Part 1: Architecture and General Requirements

WP-Part2 2.0.0 AML Whitepaper Part 2: Role Class Libraries

BPR-EDR 1.0.0 Best Practice Recommendation: External Data Reference

AR-MES-ERP 1.1.0 14


1 Introduction

AutomationML1 (AML) is a standard published by the International Electronic Commission2 (IEC) for the exchange of information between automation engineering tools, released as IEC 62714. It is based on the Computer Aided Engineering Exchange (CAEX) standard (IEC 62424), which defines a neutral data format for the storage of object hierarchies and object relations, encoded in Extendable Markup Language (XML). Its original application scenario is the description of the static structure of a plant’s shop floor. AML introduces a distributed document architecture where different documents can be linked together from a central AML document (cf. Figure 1).

The focus of AML so far has been in the description of the shop floor, i.e. the definition of machines, their terminals and communication links, and how they are all wired together. Geometric and kinematic information can be linked to AML objects through the Collaborative Design Activity3 (COLLADA) file format, which is also XML based. Logic descriptions for the programming of automated machines can be referenced through documents stored in the PLCopen4 XML data format.

Figure 1: Overview of the engineering data exchange format AML.

1.1 Provisioning for ERP and MES

In a fully integrated system, business and manufacturing functions are aligned in order to foster an efficient data flow. For the data exchange between Enterprise Resource Planning (ERP) systems and Manufacturing Execution Systems (MES) a data standard has been specified in the IEC 62264 series, based on a standard that has been standardized by the American National Standards Institute5 (ANSI) and the International Society of Automation6 (ISA): ANSI/ISA-95. A complete XML implementation of IEC 62264 has been published as the Business To Manufacturing Markup Language (B2MML) by the Manufacturing Enterprise Solutions Association (MESA) International7.

After IEC 62264 enables the linking of the business layer (ERP and supply chain management) to the manufacturing layer, linking objects from AML to elements of IEC 62264 further fosters the integration of manufacturing layers.

1 https://www.automationml.org/ 2 http://www.iec.ch/ 3 https://www.khronos.org/collada/ 4 http://www.plcopen.org/ 5 https://www.ansi.org/ 6 https://www.isa.org/ 7 http://www.mesa.org/

https://www.automationml.org/

http://www.iec.ch/

https://www.khronos.org/collada/

http://www.plcopen.org/

https://www.ansi.org/

https://www.isa.org/

http://www.mesa.org/

AR-MES-ERP 1.1.0 15


1.2 IEC 62264

IEC 62264 comprises five parts that deal with various aspects of enterprise control system integration. In cases where references to these documents are written without revision information (year of publication), the following default revisions apply:

IEC 62264-1:2013 models and terminology

IEC 62264-2:2013 objects and attributes for enterprise-control system integration

IEC 62264-3:2007 activity models of manufacturing operations management

IEC 62264-4:2015 object model attributes for manufacturing operations management integration

IEC 62264-5:2011 business to manufacturing transactions

AutomationML as an object oriented data format mainly overlaps or is related to IEC 62264-2, where core objects and relationships that are relevant in the context of data exchange between the office floor and the shop floor are depicted. Specifically, IEC 62264-2 defines five types of resources that are briefly described in Clauses 1.2.1 to 1.2.5 (an exhaustive mapping of IEC 62264-2 concepts to AML is given in Clause 3). Together, they form the fundament for further modeling steps, such as operations planning, operations performance, etc.

NOTE: This document describes the integration of part 2 if IEC 62264, IEC 62264-2, with AML. Integration of other parts will be realized in future versions of this document.

1.2.1 Personnel

Personnel comprises the actors that are required to operate manufacturing processes. AML is not focused on the definition of human resources, however if required, they could be modeled in AML as well.

1.2.2 Equipment

Equipment represents the equipment of an organization in form of a role based model. One example is the business structure of an organization with regards to physical, geographical or logical features, such as the enterprise and its sites, areas, process cells, production units, production lines, storage zones, units, work cells, and storage units (cf. Figure 2). More specific examples include welders, titration testers, lift trucks, reactors, etc. Equipment may define a hierarchy.

NOTE: Concerning the AutomationMLBaseRoleClassLib, equipment corresponds to the “Resource” or “ResourceStructure” role classes.

Figure 2: Typical expanded equipment hierarchy (from [IEC 62264-1], graphically adapted).

AR-MES-ERP 1.1.0 16


1.2.3 Physical Asset

Physical assets represent the physical pieces of equipment, i.e. while equipment defines the roles for certain items, a physical asset is the real physical item that implements that role. Physical assets have an impact on the ERP layer, as they are usually of value and need to be tracked financially. Machines for instance have a unique serial number, as such the serial number of a machine resembles a valid value for a physical asset’s ID. A dedicated equipment asset mapping represents the relationship between a physical asset and an equipment. It records the time frame in which a physical asset was associated with an equipment.

1.2.4 Material

Material represents raw, finished, and intermediate materials, as well as consumables. A uniquely identified amount of material is referred to as material lot.

NOTE: Concerning the AutomationMLBaseRoleClassLib, material corresponds to the “Product” or “ProductStructure” role classes.

1.2.5 Process Segment

Process segments resemble the smallest elements of manufacturing activities that are visible to business processes. Process segments describe a hierarchical model in which multiple levels of abstraction may be defined. Process segments are also a logical grouping of personnel, equipment, physical asset, and material required for a specific manufacturing operation.

NOTE: Concerning the AutomationMLBaseRoleClassLib, process segment corresponds to the “Process” or “ProcessStructure” role classes.

1.3 Structure of this Document The remainder of this document is structured as follows:

Clause 2 lists (or refers to documents that in turn list) terms, definitions and abbreviations in use in this document.

Clause 3 describes a mapping of IEC 62264-2 elements to AML modeling elements, i.e., it is a mapping of the IEC 62264-2 and CAEX metamodels.

Clause 4 depicts the relation of IEC 62264-2 elements to concepts already declared in the AML environment.

Clause 5 is a set of modeling rules for the modeling of IEC 62264-2 elements within AML documents.

Clause 6 defines the mechanism for referencing IEC 62264-2 information that resides outside AML documents but can be referred from AML documents.

Clause 7 describes potential conflicts between IEC 62264-2, AML and OPC UA; and how to resolve them.

Appendix A lists the IEC 62264 interface class library defined in this document.

Appendix B lists the IEC 62264 role class library defined in this document.

Appendix C lists the B2MML role class library defined in this document.

Appendix D provides examples for the referencing of external B2MML documents from AML documents with different levels of complexity.

Appendix E translates the example of Appendix D.3 to a version where all information is modeled within a single AML document and no references to external B2MML documents are required.

AR-MES-ERP 1.1.0 17


2 Terms, Definitions and Abbreviations

2.1 Terms and Definitions For the purpose of this document, the terms and definitions of IEC 62714-1:2014 and of IEC 62714-2:2015 apply.

2.2 Abbreviations

For the purpose of this document, the abbreviations of IEC 62714-1:2014 and of IEC 62714-2:2015 apply.

2.3 Conformity

In the scope of AML, a B2MML document shall conform to the specification of B2MML version 6.0 (V0600) released in March 2013.

AR-MES-ERP 1.1.0 18


3 Mapping of IEC 62264-2 to AutomationML

IEC 62264-2 defines (i) basic resources that depict the static definitions of an enterprise with regards to its production facilities, such as personnel and material (cf. Clause 3.1) and (ii) operations management information that resembles operational data such as schedules and logs (cf. Clause 3.2).

The following Clauses each (i) describes a sub model of IEC 62264-2, (ii) shows its Unified Modeling Language8 (UML) class diagram, and (iii) provides a table comprising a mapping of each IEC 62264-2 concept to one or more corresponding AutomationML element(s). The tables follow the template depicted in Table 1: the first column “IEC 62264-2” identifies the IEC 62264-2 concept (usually a UML class name), the second column “AutomationML” shows the possible AutomationML elements the concept might be realized with, and the third column gives a brief description of the concept in question, usually taken from [IEC 62264-2].

IEC 62264-2 AutomationML Comment

«IEC 62264-2 Concept» e.g. Person.

«AutomationML Concept» e.g. InternalElement.

NOTE: Multiple AML elements are specified in case several AML concepts fit the given IEC 62264-2 concept or are required

(One-to-Many Mapping).

«A brief description of the concept in question, usually taken from [IEC 62264-2].»

Table 1: Template for the mapping of IEC 62264-2 concepts to AutomationML elements.

3.1 IEC 62264-2 Common Object Models

3.1.1 Hierarchy Scope

One often used concept in IEC 62264-2 is that of levels and scopes in a hierarchy. To account for that a simple helper class “HierarchyScope” has been defined in IEC 62264-2 (cf. Figure 3) that can be used to define an equipment hierarchy. A hierarchy scope refers to a piece of equipment and defines an equipment level for that equipment based on the principles defined in Clause 1.2.2. A mapping of the hierarchy scope model to AML is given in Table 2.

Figure 3: Hierarchy scope model (from [IEC 62264-2], graphically adapted).


Hierarchy Scope InternalElement 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.

Table 2: Mapping of the IEC 62264-2 hierarchy scope model to AML.

8 http://www.omg.org/spec/UML/

http://www.omg.org/spec/UML/

AR-MES-ERP 1.1.0 19


3.1.2 Personnel

The IEC 62264-2 personnel model (cf. Figure 4) enables the modeling of classes of personnel, specific personnel, and qualifications of personnel [IEC 62264-2]. Personnel classes and individual persons may define properties. A mapping of the personnel model to AML is given in Table 3. Personnel entities have not been explicitly considered in IEC 62714 parts 1 to 4, because of its focus on the physical setup of manufacturing systems. While the modeling of specific persons might be out of scope for many AML models, the specification of personnel classes might be useful for a more detailed view on the manufacturing process.

Persons are modeled as internal elements, while personnel classes are modeled as role classes. With this setup a person can implement multiple personnel classes and a personnel class can be implemented by multiple person elements, which corresponds to the IEC 62264-2 model. A personnel class can be instantiated once (singleton pattern) as an internal element, in order to make it available in an instance hierarchy for e.g., linking.

A person must directly or indirectly refer to the generic “Person” role class defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib), while a person class must inherit from the “PersonClass” role class. The singleton instance of a personnel class (if existing) must not refer to the “Person” role class, but refer to the personnel class role class it represents. The singleton instance is used e.g., when referencing a personnel class from a process segment.

Figure 4: Personnel model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 20



Personnel Class RoleClass (mandatory) - and - InternalElement (optional)

Representation of a grouping of persons with similar characteristics for a definite purpose such as manufacturing operations definition, scheduling, capability, and performance.

Personnel Class Property Attribute Each personnel class shall have zero or more recognized properties.

Person InternalElement Representation of a specifically identified individual. A person may be a member of zero or more personnel classes.

Person Property Attribute Each person shall have zero or more person properties. These specify the current property values of the person for the associated personnel class property.

Qualification Test Specification

InternalElement Representation of a qualification test. Can be associated with a personnel class, personnel class property, person, or person property.

Qualification Test Result InternalElement Results from a qualification test for a specific person.

Table 3: Mapping of the IEC 62264-2 personnel model to AML.

3.1.3 Equipment

IEC 62264-2 role based equipment information (cf. Figure 5) resembles information about classes of equipment, specific equipment, and equipment capability tests [IEC 62264-2]. Equipment classes and specific equipment may define properties. A mapping of the equipment model to AML is given in Table 4.

The mapping is realized following the arguments of the personnel model, i.e., a person is implemented as an internal element in AML and an equipoment class as a role class. Similar to the personnel model, an equipment class may be instantiated once as an internal element.

An equipment must directly or indirectly refer to the generic “Equipment” role class defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib), while an equipment class must inherit from the “EquipmentClass” role class. The singleton instance of an equipment class (if existing) must not refer to the “Equipment” role class, but refer to the equipment class role class it represents. The singleton instance is used e.g., when referencing an equipment class from a process segment.

Figure 5: Equipment model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 21



Equipment Class RoleClass (mandatory) - and - InternalElement (optional)

Representation of a grouping of equipment with similar characteristics.

Equipment Class Property Attribute Each equipment class may have zero or more recognized properties.

Equipment InternalElement Representation of the elements of the equipment hierarchy model.

Equipment Property Attribute An equipment shall have zero or more equipment properties. These may include a unit of measure.

Equipment Capability Test Specification

InternalElement Representation of a capability test. May be associated with an equipment class, equipment class property, equipment or equipment property.

Equipment Capability Test Result

InternalElement Results from an equipment capability test for a specific piece of equipment.

Table 4: Mapping of the IEC 62264-2 equipment model to AML.


The IEC 62264-2 physical asset model (cf. Figures 6 and 7) contains information about physical pieces of equipment [IEC 62264-2]. Physical asset classes and physical assets may define properties. A mapping of the physical asset model to AML is given in Tables 5 and 6.

The physical asset model has different cardinalities between the object element (physical asset) and the type element (physical asset class) than the personnel and the equipment models. Still, similar to the other models, a physical asset is instantiated as an internal element, but this time with a required reference to a system unit class representing a physical asset class. Further, a physical asset class is modeled as a system unit class that can be instantiated by any number of physical assets (1:n mapping).

A physical asset must directly or indirectly refer to the generic “PhysicalAsset” role class defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib), while a physical asset class must inherit from the “PhysicalAssetClass” role class. The singleton instance of a physical asset class (if existing) must not refer to the “PhysicalAsset” role class, but refer to the physical asset class role class it represents. The singleton instance is used e.g., when referencing a physical asset class from a process segment.

Figure 6: Physical asset model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 22



Physical Asset Class SystemUnitClass (mandatory) - and - InternalElement (optional)

A representation of a grouping of physical assets with similar characteristics for purposes of repair and replacement.

Physical Asset Class Property

Attribute Each physical asset class may have zero or more recognized properties.

Physical Asset InternalElement A physical piece of equipment shall be presented as a physical asset. Any physical asset shall be a member of one physical asset class.

Physical Asset Property Attribute A physical asset shall have zero or more physical asset properties.

Physical Asset Capability Test Specification

InternalElement Representation of a capability test. May be associated with a physical asset property.

Physical Asset Capability Test Result

InternalElement Results from a qualification test for a specific physical asset.

Table 5: Mapping of the IEC 62264-2 physical asset model to AML.

Figure 7: Relationship between equipment information and physical asset information (from [IEC 62264-2], graphically adapted).


Equipment Asset Mapping InternalElement Relationship between a physical asset and an equipment. It records the period when one equipment entity and one physical asset entity were associated.

Table 6: Mapping of the IEC 62264-2 relationship between equipment information and physical asset information.

AR-MES-ERP 1.1.0 23


3.1.5 Material

The IEC 62264-2 material model (cf. Figure 8) defines information about classes of material, material definitions, and actual materials [IEC 62264-2]. Material classes, material definitions, and actual material may define properties. A mapping of the material model to AML is given in Table 7.

Material classes are implemented in AML as role classes that can be implemented by multiple material definitions that in turn are implemented as system unit classes. Material lots and sublots are implemented as internal elements with the sublots modeled as child elements of their parent lots or sublots.

A material lot or sublot must directly or indirectly refer to the generic “MateriaLot” or “MaterialSublot” role class defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib), while a material definition must refer to the “MaterialDefinition” role class and a material class must inherit from the “MaterialClass” role class. The singleton instance of a material class or material definition (if existing) must not refer to the “MaterialLot” or “MaterialSublot” role class, but refer to the material class role class or material definition system unit class it represents. The singleton instance is used e.g., when referencing a material class or material definition from a process segment.

Figure 8: Material model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 24



Material Class RoleClass (mandatory) - and - InternalElement (optional)

Representation of groupings of material definitions for a definite purpose such as manufacturing operations definition, scheduling, capability and performance.

Material Class Property Attribute A material class may define zero or more material class properties.

Material Definition SystemUnitClass (mandatory) - and - InternalElement (optional)

Representation of goods with similar name characteristics for the purpose of manufacturing definition, scheduling, capability and performance.

Material Definition Property Attribute A material definition may define zero or more material definition properties.

Material Lot InternalElement Uniquely identified specific amount of material, either countable or weighable. A material lot describes the planned or actual total quantity or amount of material available, its current state, and its specific property values.

Material Lot Property Attribute Each material can have unique values for zero or more material lot properties, such as a specific pH value for the specific material lot, or a specific density for the material lot.

Material Sublot InternalElement Separately identifiable quantity of the same material lot.

Material Test Specification InternalElement Representation of a material test. Shall be associated with one or more material definition properties.

Material Test Result InternalElement Results from the execution of a quality assurance test. Records the results from a material test for a specific material lot or material sublot.

Table 7: Mapping of the IEC 62264-2 material model to AML.

AR-MES-ERP 1.1.0 25



IEC 62264-2 process segments are the smallest elements of manufacturing activities that are visible to business processes. The process segment model is a hierarchical model that reflects a logical grouping of personnel, equipment, physical assets, and material (cf. Figure 9) [IEC 62264-2]. A mapping of the process segment model to AML is given in Table 8.

A process segment is modeled as an internal element with its diverse specifications modeled as children internal elements. Process segments must refer to role class “ProcessSegment” that is defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib). The same (but with their corresponding classes) applies to the other internal elements listed in this mapping.

Figure 9: Process segment model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 26



Process Segment InternalElement 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.

Process Segment Parameter Attribute Specific parameters required for a process segment.

Process Segment Dependency

InternalElement Process dependencies that are independent of any particular product or operations task.

Personnel Segment Specification

InternalElement Personnel resources that are required for a process segment.

Personnel Segment Specification Property

Attribute Specific properties that are required for personnel segment specifications.

Equipment Segment Specification

InternalElement Equipment resources that are required for a process segment.

Equipment Segment Specification Property

Attribute Specific properties that are required for equipment segment specifications.

Physical Asset Segment Specification

InternalElement Physical asset resources that are required for a process segment.

Physical Asset Segment Specification Property

Attribute Specific properties that are required for physical asset segment specifications.

Material Segment Specification

InternalElement Material resources that are required for a process segment.

Material Segment Specification Property

Attribute Specific properties that are required for material segment specifications.

Table 8: Mapping of the IEC 62264-2 process segment model to AML.

AR-MES-ERP 1.1.0 27


3.2 IEC 62264-2 Operations Management Information

Operations management information is information that resembles runtime data from manufacturing – be it specific manufacturing schedules, the produced goods of a production run, or the available personnel in a certain period. While the common object models presented in Clause 3.1 correspond closely to concepts of AML, operations management information is typically not modeled in AML. However, there might be uses cases that require the recording of operations management information, and for these use cases the following alignment is provided.

3.2.1 Operations Definition

An operations definition defines the resources required to perform a specified operation. The operations definition may apply to defining production, maintenance, quality test, and inventory [IEC 62264-2].

An operations definition is modeled as an internal element with its diverse specifications modeled as children internal elements. Operations definitions must refer to role class “OperationsDefinition” that is defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib). The same (but with their corresponding classes) applies to the other internal elements listed in this mapping.

Figure 10: Operations definition model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 28



Operations Definition InternalElement Resources required to perform a specified operation.

Operations Material Bill InternalElement Collection of all material used in the operation, independent of the process segment the material is used in. There may be multiple operations material bills, with different uses.

Operations Material Bill Item InternalElement Items that make up the complete operations material bill.

Operations Segment InternalElement Information needed to quantify a segment for a specific operation. It identifies, references, or corresponds to a process segment.

Parameter Specification Attribute Specific parameters required for an operations segment. There may be an associated set of zero or more parameter specifications.

Personnel Specification InternalElement An identification, reference, or correspondence to a personnel capability. A personnel specification usually specifies a personnel class, but may specify a person.

Personnel Specification Property

Attribute Specific properties that are required for personnel specifications.

Equipment Specification InternalElement An identification, reference, or correspondence to an equipment capability. An equipment specification may specify either an equipment class or a piece of equipment.

Equipment Specification Property

Attribute Specific properties that are required for equipment specifications.

Physical Asset Specification InternalElement An identification, reference, or correspondence to a physical asset capability. A physical asset specification may specify either a physical asset class or a physical asset.

Physical Asset Specification Property

Attribute Specific properties that are required for physical asset specifications.

Material Specification InternalElement An identification or correspondence to a material capability. A material specification specifies a material definition or a material class.

Material Specification Property

Attribute Specific properties that are required for material specifications.

Operations Segment Dependency

InternalElement Operations dependencies that are operation or product specific.

Table 9: Mapping of the IEC 62264-2 operations definition model to AML.

AR-MES-ERP 1.1.0 29


3.2.2 Operations Schedule

A request for operations to be performed is an operations schedule. The schedule may apply to scheduling of production, maintenance, quality test, and inventory operations [IEC 62264-2].

An operations schedule is modeled as an internal element with its diverse requirements modeled as children internal elements. Operations schedules must refer to role class “OperationsSchedule” that is defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib). The same (but with their corresponding classes) applies to the other internal elements listed in this mapping.

Figure 11: Operations schedule model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 30



Operations Schedule InternalElement Request for operations to be performed. An operations schedule shall be made up of one or more operations requests.

Operations Request InternalElement Request for an element of an operations schedule. Contains the information required by manufacturing to fulfill the scheduled operation.

Segment Requirement InternalElement An operations 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.

Segment Parameter InternalElement Specific parameters required for a segment requirement.

Personnel Requirement InternalElement Identification of the number, type, duration, and scheduling of specific certifications and job classifications needed to support the current operations request.

Personnel Requirement Property

Attribute Specific properties that are required for personnel requirements.

Equipment Requirement InternalElement Identification of the number, type, duration, and scheduling of specific equipment and equipment classifications needed to support the current operations request.

Equipment Requirement Property

Attribute Specific properties that are required for equipment requirements.

Physical Asset Requirement InternalElement Identification of the number, type, duration, and scheduling of specific physical assets and physical asset class constraints needed to support the current operations request.

Physical Asset Requirement Property

Attribute Specific properties that are required for physical asset requirements.

Material Requirement InternalElement Identification of a material that is expected to be used in the operations request. Material requirements contain definitions of materials that may be consumed, produced, replaced, sampled, or otherwise used in manufacturing

Material Requirement Property

Attribute Properties of a material requirement.

Requested Segment Response

InternalElement Identification of the information sent back as a result of the production request. This information is of the same form as a segment response, but without actual values.

Table 10: Mapping of the IEC 62264-2 operations schedule model to AML.

AR-MES-ERP 1.1.0 31


3.2.3 Operations Performance

Operations performance is a report on requested manufacturing and is a collection of operations responses. Operations responses are responses from manufacturing that may be associated with an operations request. 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 [IEC 62264-2].

An operations performance is modeled as an internal element with its diverse actuals modeled as children internal elements. Operations performances must refer to role class “OperationsPerformance” that is defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib). The same (but with their corresponding classes) applies to the other internal elements listed in this mapping.

Figure 12: Operations performance model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 32



Operations Performance InternalElement Performance of the requested manufacturing requests. Operations performance shall be a collection of operations responses.

Operations Response InternalElement Responses from manufacturing that are associated with an operations request. There may be one or more operations responses for a single operations request.

Segment Response InternalElement Information on a segment of an operations response. A segment response shall be made up of zero or more sets of information on segment data, personnel actual, equipment actual, and material actual

Segment Data InternalElement Other information related to the actual operations made.

Personnel Actual InternalElement Identification of a personnel capability used during a specified segment response.

Personnel Actual Property Attribute Specific properties that are required for a personnel actual.

Equipment Actual InternalElement Identification of an equipment capability used during a specified segment.

Equipment Actual Property Attribute Specific properties that are required for an equipment actual.

Physical Asset Actual InternalElement Identification of a physical asset capability used during a specified segment.

Physical Asset Actual Property

Attribute Specific properties that are required for a physical asset actual.

Material Actual InternalElement Identification of a material that was used in the operations request. Material actuals contain definitions of materials that may have been consumed, produced, replaced, sampled, or otherwise used in manufacturing.

Material Actual Property Attribute Specific properties that are required for a material actual.

Table 11: Mapping of the IEC 62264-2 operations performance model to AML.

AR-MES-ERP 1.1.0 33


3.2.4 Operations Capability

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, physical assets, material, personnel, and process segments. Operations capability describes the names, terms, statuses, and quantities of which the manufacturing control system has knowledge [IEC 62264-2]. The process segment capability element is described in detail in Clause 3.2.5.

An operations capability is modeled as an internal element with its diverse capabilities modeled as children internal elements. Operations capabilities must refer to role class “OperationsCapability” that is defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib). The same (but with their corresponding classes) applies to the other internal elements listed in this mapping.

Figure 13: Operations capability model (from [IEC 62264-2], graphically adapted).

AR-MES-ERP 1.1.0 34



Operations Capability InternalElement Collection of personnel capabilities, equipment capabilities, physical asset capabilities, material capabilities, and process segment capabilities, for a given slice of time (past, current, or future).

Personnel Capability InternalElement Capability of persons or personnel classes that is committed, available, or unattainable for a defined time.

Personnel Capability Property

Attribute Specific properties that are required for personnel capabilities.

Equipment Capability InternalElement Representation of the capability of equipment or equipment classes that is committed, available, or unattainable for a specific time.

Equipment Capability Property

Attribute Specific properties that are required for equipment capabilities.

Physical Asset Capability InternalElement Representation of the capability of a physical asset or physical asset class that is committed, available, or unattainable for a specific time.

Physical Asset Capability Property

Attribute Specific properties that are required for physical asset capabilities.

Material Capability InternalElement Representation of the capability of material that is committed, available, or unattainable for a specific time. Material capability is used for material lots and material sublots.

Material Capability Property Attribute Specific properties that are required for material capabilities.

Table 12: Mapping of the IEC 62264-2 operations capability model to AML.

AR-MES-ERP 1.1.0 35


3.2.5 Process Segment Capability

Representation of logical grouping of personnel resources, equipment resources, physical asset resources, and material that is committed, available, or unavailable for a defined process segment for a specific time. The model’s structure is equivalent to the one of operations capability, except that a process segment capability is defined for a specific process segment. As such, the various capabilities and capability properties described in Table 12 (Clause 3.2.4) provide the same semantics and structure as the ones required for process segment capabilities. A duplication of the mapping is therefore omitted.

A process segment capability is modeled as an internal element with its diverse capabilities modeled as children internal elements. Process segment capabilities must refer to role class “ProcessSegmentCapability” that is defined in the accompanying role class library (AutomationMLIEC62264RoleClassLib). The same (but with their corresponding classes) applies to the other internal elements listed in this mapping.

Figure 14: Process segment capability model (from [IEC 62264-2], graphically adapted).


Process Segment Capability InternalElement Representation of a logical grouping of personnel resources, equipment resources, physical asset resources, and material that is committed, available, or unavailable for a given process segment for a specific time.

Table 13: Mapping of the IEC 62264-2 process segment capability model to AML.

AR-MES-ERP 1.1.0 36


3.3 Visualization of the Mapping

Figure 15 depicts a visual approach to the mapping of IEC 62264-2 metamodel elements (i) to CAEX metamodel elements and (ii) to existing AutomationML elements of the AutomationMLBaseRoleClassLib. IEC 62264-2 elements are located in the center column.

Mappings to the left have the following semantics: “An instance of type <X> of the IEC 62264-2 metamodel is modeled as an instance of type <Y> of the CAEX metamodel”.

Mappings to the right have the following semantics: “A role class that resembles type <X> of the IEC 62264-2 metamodel is a subclass of <Y> of the AutomationML base role class library”. These mappings are complemented by Clause 4.3.1.

Figure 15: Visualization of the mapping from IEC 62264-2 to the CAEX metamodel (left) and to existing AutomationML elements of the AutomationMLBaseRoleClassLib (right).

NOTE: Not all IEC 62264-2 elements have been regarded in Figure 15, but a representative selection.

AR-MES-ERP 1.1.0 37


4 Related AutomationML Libraries

4.1 AutomationML Interface Class Libraries

4.1.1 AutomationMLInterfaceClassLib

Table 14 depicts the interface classes defined in AML parts 1 and 2. With the “ExternalDataConnector” AML defines the basic abstract interface type for referencing external documents. “COLLADAInterface” and “PLCopenXMLInterface” are two standardized interface classes for referencing elements from COLLADA and PLCopen XML files, respectively.

InterfaceClass Library InterfaceClass Description

AutomationMLInterfaceClassLib

AutomationMLBaseInterface

Order

PortConnector

InterlockingConnector

PPRConnector

ExternalDataConnector

COLLADAInterface

PLCopenXMLInterface

Communication

SignalInterface

AutomationMLBaseInterface Basic abstract interface type, to be used as parent for the description of all AML interface classes.

ExternalDataConnector Basic abstract interface type, to be used for the description of connector interfaces referencing external documents. All existing and future connector classes shall be derived directly or indirectly from this class.

Table 14: InterfaceClasses of the AutomationMLInterfaceClassLib.

4.1.2 AutomationMLBPRInterfaceClassLib

Table 15 displays the content of AutomationMLBPRInterfaceClassLib, that deals with the referencing of data outside the scope of AML. Interface class “ExternalDataReference” is a direct successor to the previously stated interface class “ExternalDataConnector”. It contains two attributes: “refURI” (inherited from ExternalDataConnector) gives the URI to the external data file, while “MIMEtype” provides information about the type of content stored in that location [AML-B-EDR]. This interface class is required for the referencing of externally stored data in B2MML documents (cf. Clause 6).

InterfaceClass Library InterfaceClass Description

AutomationMLBPRInterfaceClassLib

ExternalDataReference

ExternalDataReference Shall be used in order to reference external documents out of the scope of AutomationML.

Table 15: InterfaceClass of the AutomationMLBPRInterfaceClassLib.

AR-MES-ERP 1.1.0 38


4.2 AutomationML Role Class Libraries

4.2.1 AutomationMLBaseRoleClassLib

AutomationMLBaseRoleClassLib (cf. Table 16) defines entities that resemble abstractions of concepts defined in IEC 62264, subsumed under the term “Process-Product-Resource” (PPR). It defines abstract role types for non-hierarchical elements (“Process”, “Product”, and “Resource”), as well as for hierarchical elements (“ProcessStructure”, “ProductStructure”, and “ResourceStructure”) [IEC 62714-1]. This is the most generic definition of AML role classes with respect to IEC 62264-2, and as such a corresponding role class defined in this library are used as the super role class of IEC 62264-2 related role classes, if applicable. A mapping of elements from IEC 62264-2 to PPR is given in Clause 4.3.1, a more detailed implementation in AML follows in Clause D.3.

RoleClass Library RoleClass Description

AutomationMLBaseRoleClassLib

AutomationMLBaseRole

Group

Facet

Port

Port-Interfaces

ConnectionPoint

Resource

Product

Process

Structure

ProductStructure

ProcessStructure

ResourceStructure

PropertySet

AutomationMLBaseRole Basic abstract role type and the base class for all standard or user-defined role classes.

Resource Basic abstract role type and the base class for all AML resource roles. It describes plants, equipment, workers or other production resources.

Product Basic abstract role type and the base class for all AML product roles. It describes products, product parts or product related materials that are processed in the described plant.

Process Basic abstract role class and the base class for all AML process roles. It describes production related processes.

Structure Basic abstract role type for objects that serve as structure elements in the plant hierarchy, e.g. a folder, a site or a manufacturing line.

ProductStructure Abstract role type for a product oriented object hierarchy.

ProcessStructure Abstract role type for a process oriented object hierarchy.

ResourceStructure Abstract role type for a resource oriented object hierarchy.

Table 16: Selected RoleClasses of the AutomationMLBaseRoleClassLib.

NOTE: Role class “Resource” is the (indirect) base class for elements described in the AutomationMLBMIRoleClassLib, AutomationMLCMIRoleClassLib, AutomationMLDMIRoleClassLib, and the AutomationMLCSRoleClassLib. It is also the (indirect) base class for non-hierarchical elements in the (non-normative) AutomationMLExtendedRoleClassLib other than “PLCFacet” and “HMIFacet”.

NOTE: Role class “ResourceStructure” is the (indirect) base class for hierarchical elements in the (non-normative) AutomationMLExtendedRoleClassLib.

AR-MES-ERP 1.1.0 39


4.2.2 AutomationMLBMIRoleClassLib

Table 17 depicts a base role class related to batch manufacturing. The role class “BatchManufacturingEquipment” inherits from AML base role “Resource” and could be used as an additional supported role class for internal elements representing equipment or physical asset items.


AutomationMLBMIRoleClassLib

BatchManufacturingEquipment BatchManufacturingEquipment Equipment related to batch

manufacturing.

Table 17: RoleClass of the AutomationMLBMIRoleClassLib.

4.2.3 AutomationMLCMIRoleClassLib

Table 18 depicts a base role class related to continuous manufacturing. The role class “ContManufacturingEquipment” inherits from AML base role “Resource” and could be used as an additional supported role class for internal elements representing equipment or physical asset items.


AutomationMLCMIRoleClassLib

ContManufacturingEquipment

ContManufacturingEquipment Equipment related to continuous manufacturing.

Table 18: RoleClass of the AutomationMLCMIRoleClassLib.

AR-MES-ERP 1.1.0 40


4.2.4 AutomationMLDMIRoleClassLib

Table 19 lists role classes related to discrete manufacturing. The top-level role class “DiscManufacturingEquipment” (from which the other role classes of this library directly inherit) inherits from AML base role “Resource” and could be used as an additional supported role class for internal elements representing equipment or physical asset items.


AutomationMLDMIRoleClassLib

DiscManufacturingEquipment

Transport

Storage

Fixture

Gate

Robot

Tool

Carrier

Machine

StaticObject

DiscManufacturingEquipment Equipment related to discrete manufacturing industries.

Transport Equipment that performs transport processes to transfer items.

Storage Equipment that is used to buffer products or material temporarily within the plant. It can also be used to feed products or materials into the production process or to export products or materials out of the production process.

Fixture Equipment that reduces the degrees of freedom of an item.

Gate Equipment that can block or monitor an entrance, departure, or passage way.

Robot Role class used for robots.

Tool Equipment used by resources that is necessary for or aids in the performance of an operation on the product.

Carrier Transport equipment that carries items.

Machine Mechanic or mechatronic equipment that creates added value on products and is designed expressly to perform specific tasks.

StaticObject Passive, static items positioned in the production environment.

Table 19: RoleClasses of the AutomationMLDMIRoleClassLib.

AR-MES-ERP 1.1.0 41


4.2.5 AutomationMLCSRoleClassLib

Table 20 lists role classes related to control system equipment (applicable to batch, continuous, and discrete manufacturing). The top-level role class “ControlEquipment” (from which the other role classes of this library directly or indirectly inherit) inherits from AML base role “Resource” and could be used as an additional supported role class for internal elements representing equipment or physical asset items.


AutomationMLCSRoleClassLib

ControlEquipment

Communication

ControlHardware

PC

IPC

EmbeddedDevice

Handheld

Sensor

Actuator

Controller

PLC

NC

RC

PAC

ControlEquipment Equipment related to a control system. ControlEquipment can be used for every type of industry.

Communication Items dedicated to communications.

ControlHardware Hardware that provides runtime environments.

PC Any general-purpose computer that provides runtime environments for software being executed on it.

IPC Any PC-based computing platform for industrial applications that provides runtime environments for software being executed on it.

EmbeddedDevice Any device designed to perform one or a few dedicated software functions. It is embedded as part of another device often including hardware and mechanical parts.

Handheld Any portable, programmable, electronic device with an own power supply for particular applications.

Sensor Role class used for sensors.

Actuator Role class used for actuators.

Controller Self-acting functionalities that process signals according to a predefined logic and generate output signals in order to reach an intended behavior of technical processes.

PLC Programmable Logic Controller: Programmable control functionality focusing on the processing of signals.

NC Numerical Control: Programmable control functionality focusing on the processing of numerical signals.

RC Programmable control functionality driving robots in order to reach an intended behavior of the robot kinematic system and corresponding connected periphery.

PAC Programmable Automation Controller: Programmable automation functionality focusing on cross-domain functionality like binary, motion, and continuous control.

Table 20: RoleClasses of the AutomationMLCSRoleClassLib.

AR-MES-ERP 1.1.0 42


4.2.6 AutomationML Extended RoleClass Library (non-normative)

Table 21 lists more specific role classes that are extending corresponding role classes of the previously discussed role class libraries (cf. Clauses 4.2.1 to 4.2.5). All listed role classes (except for “PLCFacet” and “HMIFacet”) inherit directly or indirectly from AML base role “Resource” and could be used as an additional supported role class for internal elements representing equipment or physical asset items. In Table 21 only role classes that are specifically relevant for this recommendation are explicitly named and commented: an AML object that resembles an an IEC 62264 element of type equipment or equipment class that has the equipment level “Enterprise” shall be associated with the role class “Enterprise” from the AutomationMLExtendedRoleClassLib (e.g. through the addition of a “supported role class”). The same rule shall apply to the other hierarchical elements of the role based equipment model correspondingly (“Site”, “Area”, “ProductionLine”, …).


AutomationMLExtendedRoleClassLib

PLCFacet

HMIFacet

Enterprise

Site

Area

ProductionLine

WorkCell

ProcessCell

Unit

ProductionUnit

StorageZone

StorageUnit

Turntable

Conveyor

BeltConveyor

RollConveyor

ChainConveyor

PalletConveyor

OverheadConveyor

LiftingTable

AGV

Transposer

CarrierHandlingSystem

BodyStore

Lift

Rollerbed

StationaryTool

MovableTool

ControlCabinet

IODevice

HMI

WarningEquipment

ActuatingDrive

MotionController

Panel

MeasuringEquipment

Clamp

ProcessController

Loader

Unloader

Enterprise Role class used for business structures.

Site Physical, geographical, or logical grouping determined by the enterprise. It may contain areas, production lines, process cells, and production units.

Area Physical, geographical, or logical grouping determined by the site. It may contain work centers such as production lines, process cells, production units, and storage zones.

ProductionLine Equipment for discrete manufacturing at the production line level.

WorkCell Equipment for discrete manufacturing at the work cell level.

ProcessCell Equipment for batch manufacturing at the process cell level.

Unit Linked chained production plants in batch manufacturing.

ProductionUnit Lowest level of equipment for continuous manufacturing processes.

StorageZone Work center for material movement equipment.

StorageUnit Work unit for material movement equipment.

Table 21: RoleClasses of the AutomationMLExtendedRoleClassLib.

AR-MES-ERP 1.1.0 43


NOTE: Some of the elements in the (non-normative) AML extended role class library are roles that have been derived from IEC 62264-1 (role classes “Site” to “StorageUnit”), but there are two issues with those elements: (i) in the current implementation of the extended role class library it is that the work unit “Unit” is included only with reference to batch manufacturing – however, in IEC 62264-1 “Unit” is the name for work units in batch and in continuous production, and (ii) role classes for generic work cells and work units should be provided (not only the more specific ones: “ProductionLine”, “ProcessCell”, “ProductionUnit”, “StorageZone”, “WorkCell”, “Unit”, and “StorageUnit”), as this is proposed in IEC 62264-1. As such, a corresponding revision of the extended role class library is proposed and might be implemented in future versions of AutomationMLExtendedRoleClassLib (this is out of scope of this recommendation).

4.2.7 AutomationMLBPRRoleClassLib (non-normative)

Table 22 lists the role class related to the referencing of external documents, as specified in [AML-B-EDR]. This role class serves as the base role class for the role class specifying external B2MML documents. This role class is declared in a dedicated role class library (cf. Clause 5.2).


AutomationMLBPRRoleClassLib

ExternalData

ExternalData Tagging role class for the referencing of external documents.

Table 22: RoleClass of the AutomationMLBPRRoleClassLib.

4.3 Alignment of IEC 62264-2 and AutomationML An alignment of IEC 62264-2 with generic PPR role classes is given in Clause 4.3.1, while an alignment with more detailed AutomationML role classes is depicted in Clause 4.3.2. It depends on the implementer’s domain knowledge at which detail he/she wants to annotate his/her elements.

4.3.1 Alignment of IEC 62264-2 and AutomationMLBaseRoleClassLib

Role classes “Resource”, “Product”, “Process”, “ProductStructure”, “ProcessStructure”, and “ResourceStructure”, which are defined in the AutomationMLBaseRoleClassLib of IEC 62714-1 (cf. Clause 4.2.1), are related to concepts in IEC 62264-2 (cf. Clause 4.2).

A mapping of related concepts from IEC 62264-2 and AML base role classes is given in Table 23 (“AutomationMLBaseRoleClassLib/AutomationMLBaseRole” is abbreviated as “BR” for better readability). The other concepts of IEC 62264-2 are not directly related to any of the existing base roles of AML – they are therefore not listed here. The mappings listed here correspond to the inheritance relation of IEC 62264-2 role classes that are defined in Clause 5.3, e.g., role class “BR/Resource” is the super role class of the newly defined IEC 62264 role class “Equipment”.

NOTE: Some of the mappings are also visualized in Figure 15.

AR-MES-ERP 1.1.0 44


IEC 62264-2 AutomationML Base Role Class

Comment

Person BR/Resource Representation of a specifically identified individual. A person may be a member of zero or more personnel classes.

Personnel Class BR/Resource Representation of a grouping of persons with similar characteristics for a definite purpose such as manufacturing operations definition, scheduling, capability, and performance.

Equipment BR/Resource Representation of the elements of the equipment hierarchy model.

Equipment Class BR/Resource Representation of a grouping of equipment with similar characteristics.

Physical Asset BR/Resource A physical piece of equipment shall be presented as a physical asset. Any physical asset shall be a member of one physical asset class.

Physical Asset Class

BR/Resource A representation of a grouping of physical assets with similar characteristics for purposes of repair and replacement.

Material Definition

BR/Product Representation of goods with similar name characteristics for the purpose of manufacturing definition, scheduling, capability and performance.

Material Class BR/Product Representation of groupings of material definitions for a definite purpose such as manufacturing operations definition, scheduling, capability and performance.

Material Lot BR/Product Uniquely identified specific amount of material, either countable or weighable. A material lot describes the planned or actual total quantity or amount of material available, its current state, and its specific property values.

Material Sublot BR/Product Separately identifiable quantity of the same material lot.

Process Segment BR/Process 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.

Operations Definition

BR/Structure/ProcessStructure

Resources required to perform a specified operation.

Operations Segment

BR/Process Information needed to quantify a segment for a specific operation. An operations segment identifies, references, or corresponds to a process segment.

Operations Schedule


Request for operations to be performed. An operations request shall be made up of one or more operations requests.

Operations Request


Request for an element of an operation schedule. An operations request contains the information required by manufacturing to fulfill the scheduled operation.

Segment Requirement

BR/Process An operations request shall be made up of one ore more segment requirements. Each segment requirement shall correspond to or reference an identified operations segment or process segment.

Requested Segment Response

BR/Process Identification of the information sent back as a result of the operations request.

AR-MES-ERP 1.1.0 45


IEC 62264-2 AutomationML Base Role Class

Comment

Operations Performance


Performance of the requested operations.

Operations Response


Response from manufacturing that is associated with an operations request. 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.

Segment Response

BR/Process Information on a segment of an operations response.

Operations Capability

BR/Process Collection of personnel capabilities, equipment capabilities, physical asset capabilities, material capabilities, and process segment capabilities, for a given slice of time (past, current, or future) and defined as committed, available, and unattainable.

Process Segment Capability

BR/Process Representation of a logical grouping of personnel resources, equipment resources, physical asset resources, and material that is committed, available, or unavailable for a defined process segment for a specific time.

Table 23: Alignment of IEC 62264-2 with AML base role classes.

AR-MES-ERP 1.1.0 46


4.3.2 Alignment of IEC 62264-2 and Detailed Normative AutomationML Role Class Libraries

In addition to the generic role classes discussed in Clause 4.3.1, more detailed role classes are defined in IEC 62714-2 in the role class libraries “AutomationMLBMIRoleClassLib”, “AutomationMLCMIRoleClassLib”, “AutomationMLDMIRoleClassLib”, and “AutomationMLCSRoleClassLib” (cf. Clauses 4.2.2 - 4.2.5).

All the role classes defined in these libraries inherit directly or indirectly from the base role class (cf. Clause 4.2.1) “AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Resource” and can be applied to any of the IEC 62264-2 concepts listed in Table 24. Application of any of these role classes can be realized as additional “supported role class”.

IEC 62264-2 AutomationML

Equipment

Equipment Class

Physical Asset


AutomationMLCSRoleClassLib/ControlEquipment

AutomationMLCSRoleClassLib/ControlEquipment/Communication

AutomationMLCSRoleClassLib/ControlEquipment/ControlHardware

AutomationMLCSRoleClassLib/ControlEquipment/ControlHardware/PC

AutomationMLCSRoleClassLib/ControlEquipment/ControlHardware/IPC

AutomationMLCSRoleClassLib/ControlEquipment/ControlHardware/EmbeddedDevice

AutomationMLCSRoleClassLib/ControlEquipment/ControlHardware/Handheld

AutomationMLCSRoleClassLib/ControlEquipment/Sensor

AutomationMLCSRoleClassLib/ControlEquipment/Actuator

AutomationMLCSRoleClassLib/ControlEquipment/Controller

AutomationMLCSRoleClassLib/ControlEquipment/Controller/PLC

AutomationMLCSRoleClassLib/ControlEquipment/Controller/NC

AutomationMLCSRoleClassLib/ControlEquipment/Controller/RC

AutomationMLCSRoleClassLib/ControlEquipment/Controller/PAC

AutomationMLBMIRoleClassLib/BatchManufacturingEquipment

AutomationMLCMIRoleClassLib/ContManufacturingEquipment

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Transport

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Storage

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Fixture

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Gate

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Robot

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Tool

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Carrier

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/Machine

AutomationMLDMIRoleClassLib/DiscManufacturingEquipment/StaticObject

Table 24: Alignment of IEC 62264-2 with more detailed normative AML role classes.

AR-MES-ERP 1.1.0 47


4.3.3 Alignment of IEC 62264-2 and AutomationMLExtendedRoleClassLib

Even more detailed role classes are defined in IEC 62714-2 in the “AutomationMLExtendedRoleClassLib” role class library (cf. Clause 4.2.6). All the role classes defined in this library (except for the two “Facets”) inherit directly or indirectly from role class “AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Resource” (cf. Clause 4.2.1) and can be applied to any of the IEC 62264-2 concepts listed in Table 25. Application of any of these role classes can be realized as additional “supported role class”.

IEC 62264-2 AutomationML

Equipment

Equipment Class

Physical Asset


AutomationMLExtendedRoleClassLib/Enterprise

AutomationMLExtendedRoleClassLib/Site

AutomationMLExtendedRoleClassLib/Area

AutomationMLExtendedRoleClassLib/ProductionLine

AutomationMLExtendedRoleClassLib/WorkCell

AutomationMLExtendedRoleClassLib/ProcessCell

AutomationMLExtendedRoleClassLib/Unit

AutomationMLExtendedRoleClassLib/ProductionUnit

AutomationMLExtendedRoleClassLib/StorageZone

AutomationMLExtendedRoleClassLib/StorageUnit

AutomationMLExtendedRoleClassLib/Turntable

AutomationMLExtendedRoleClassLib/Conveyor

AutomationMLExtendedRoleClassLib/Conveyor/BeltConveyor

AutomationMLExtendedRoleClassLib/Conveyor/RollConveyor

AutomationMLExtendedRoleClassLib/Conveyor/ChainConveyor

AutomationMLExtendedRoleClassLib/Conveyor/PalletConveyor

AutomationMLExtendedRoleClassLib/Conveyor/OverheadConveyor

AutomationMLExtendedRoleClassLib/LiftingTable

AutomationMLExtendedRoleClassLib/AGV

AutomationMLExtendedRoleClassLib/Transposer

AutomationMLExtendedRoleClassLib/CarrierHandlingSystem

AutomationMLExtendedRoleClassLib/BodyStore

AutomationMLExtendedRoleClassLib/Lift

AutomationMLExtendedRoleClassLib/Rollerbed

AutomationMLExtendedRoleClassLib/StationaryTool

AutomationMLExtendedRoleClassLib/MovableTool

AutomationMLExtendedRoleClassLib/ControlCabinet

AutomationMLExtendedRoleClassLib/IODevice

AutomationMLExtendedRoleClassLib/HMI

AutomationMLExtendedRoleClassLib/HMI/WarningEquipment

AutomationMLExtendedRoleClassLib/ActuatingDrive

AutomationMLExtendedRoleClassLib/MotionController

AutomationMLExtendedRoleClassLib/Panel

AutomationMLExtendedRoleClassLib/MeasuringEquipment

AutomationMLExtendedRoleClassLib/Clamp

AutomationMLExtendedRoleClassLib/ProcessController

AutomationMLExtendedRoleClassLib/Loader

AutomationMLExtendedRoleClassLib/Unloader

Table 25: Alignment of IEC 62264-2 with the (non-normative) AML extended role class lib.

AR-MES-ERP 1.1.0 48


5 AML Libraries for Supporting IEC 62264

5.1 Interface Class Library AutomationMLIEC62264InterfaceClassLib Interface class library AutomationMLIEC62264InterfaceClassLib (cf. Table 26) specifies a number of interface classes required for the modeling of IEC 62264 information with AML by enabling required cross-references.

InterfaceClass Library RoleClass Description

AutomationMLIEC62264InterfaceClassLib

HierarchyScopeConnector

ResourceConnector

EquipmentAssetConnector

DependencyConnector

TestConnector

HierarchyScopeConnector HierarchyScopeConnector shall be used in order to reference hierarchy scope elements from other entities such as e.g., process segments.

ResourceConnector ResourceConnector shall be used in order to reference basic or complex resources from complex entities such as e.g., a person or personnel class from a personnel segment specification of a process segment.

EquipmentAssetConnector EquipmentAssetConnector shall be used in order to link equipment and physical assets to equipment asset mappings.

DependencyConnector DependencyConnector shall be used in order to link process or operations segments to process or operations segment dependencies, respectively.

TestConnector TestConnector shall be used in order to link resources and resource types to test specifications and test results.

Table 26: InterfaceClasses needed for supporting concepts of IEC 62264, subsumed in the AutomationMLIEC62264InterfaceClassLib.

InterfaceClass “HierarchyScopeConnector” shall be used as specified in Table 27: one instance of this interface class is to be bound to an element of type “HierarchyScope” (cf. Clause 5.3.1), while another instance of this interface class is to be instantiated at a “scopable” IEC 62264 element. Then, an internal link is to be created, thus reifying the relation (cf. Figure 16).

Class Name HierarchyScopeConnector

Description The InterfaceClass “HierarchyScopeConnector” shall be used in order to reference hierarchy scope elements from other entities such as e.g., process segments.

Parent Class AutomationMLInterfaceClassLib/AutomationMLBaseInterface

Path for Element Reference

AutomationMLIEC62264InterfaceClassLib/HierarchyScopeConnector

Table 27: InterfaceClass HierarchyScopeConnector.

Figure 16: Usage example for interface class HierarchyScopeConnector.

AR-MES-ERP 1.1.0 49


InterfaceClass “ResourceConnector” shall be used as specified in Table 28: one instance of this interface class is to be bound to an element of any of the basic resource types (e.g., equipment or equipment class), while another instance of this interface class is to be instantiated at a “referring” IEC 62264 element (e.g., equipment segment specification). Then, an internal link is to be created, thus reifying the relation (cf. Figure 17). Another use case is the referencing of complex structures, e.g., for expressing the relation of an operations segment to a process segment.

Class Name ResourceConnector

Description The InterfaceClass “ResourceConnector” shall be used in order to reference basic resources from complex entities such as e.g., a personnel segment specification of a process segment referring to a person or personnel class.



AutomationMLIEC62264InterfaceClassLib/ResourceConnector

Table 28: InterfaceClass ResourceConnector.

Figure 17: Usage example for interface class ResourceConnector.

InterfaceClass “EquipmentAssetConnector” shall be used as specified in Table 29: one instance of this interface class is bound to an equipment, while the other is bound to an equipment asset mapping. At the same time, another instance of this interface class is bound to a physical asset. Then, two internal links are created that interlink (i) the equipment with the equipment asset mapping and (ii) the physical asset with the equipment asset mapping (cf. Figure 18).

Class Name EquipmentAssetConnector

Description The InterfaceClass “EquipmentAssetConnector” shall be used in order to link Equipment and PhysicalAssets to EquipmentAssetMappings.



AutomationMLIEC62264InterfaceClassLib/EquipmentAssetConnector

Table 29: InterfaceClass EquipmentAssetConnector.

Figure 18: Usage example of interface class EquipmentAssetConnector.

AR-MES-ERP 1.1.0 50


InterfaceClass “DependencyConnector” shall be used as specified in Table 30: one instance of this interface class is bound to a process segment or operations segment, while the other is bound to a process segment dependency or operations segment dependency, respectively. At the same time, another instance of this interface class is bound to another process segment or operations segment. Then, two internal links are created that interlink the process segments or operations segments with the process segment dependency or the operations segment dependency, respectively (cf. Figure 19).

Class Name DependencyConnector

Description The InterfaceClass “DependencyConnector” shall be used in order to link ProcessSegments and OperationsSegments to Process/OperationsSegmentDependencies.



AutomationMLIEC62264InterfaceClassLib/DependencyConnector

Table 30: InterfaceClass DependencyConnector.

Figure 19: Usage example of interface class DependencyConnector.

InterfaceClass “TestConnector” shall be used as specified in Table 31: one instance of this interface class is bound to a resource or resource type (e.g., person, personnel class, equipment, equipment class), while the other is bound to a test specification or test result. Then, internal links are created to interlink the resource or resource type with the test specification or test result, as well as the test result with the test specification (cf. Figure 20). If the test specification needs to specify a resource property or resource type property, it shall instantiate an attribute with the same name as the one referring to, but prefixed with “ts:”. If the test result needs to specify a resource property or resource type property, it shall instantiate an attribute with the same name as the one referring to, but prefixed with “tr:”.

Class Name TestConnector

Description The InterfaceClass “TestConnector” shall be used in order to link ProcessSegments and OperationsSegments to Process/OperationsSegmentDependencies.



AutomationMLIEC62264InterfaceClassLib/TestConnector

Table 31: InterfaceClass TestConnector.

Figure 20: Usage example for interface class TestConnector.

AR-MES-ERP 1.1.0 51


5.2 Role Class Library AutomationMLB2MMLRoleClassLib

Role class library “AutomationMLB2MMLRoleClassLib”, as depicted in Table 32, is encapsulating role classes that are required for the use of externally linked B2MML documents. It is not required in case all IEC 62264 information is modeled within AML


AutomationMLB2MMLRoleClassLib

B2mmlData

B2mmlData References external B2MML documents.

Table 32: RoleClass “B2mmlData” needed for referencing a specific B2MML document, encapsulated in the AutomationMLB2MMLRoleClassLib.

NOTE: IEC 62264 elements such as Personnel Class and Equipment Class that are normally modeled as instances of type RoleClass in AML documents cannot hold instances of type InternalElement that represent external documents. Therefore, they shall be instantiated additionally as an internal element that refers to the correct IEC 62264 role class and this internal element holds another internal element representing an external document [AML-B-EDR].

RoleClass “B2mmlData” shall be used as specified in Table 33, and as further specified in Clause 6. It corresponds to the specification given in [AML-B-EDR], as it is used to tag an AML element as representing an external document. This role class is to be referenced by AML elements that should reference external files through the external interfaces of interface class “ExternalDataReference”.

Class Name B2mmlData

Description The RoleClass “B2mmlData” shall be used in order to reference external B2MML documents, using the mechanism defined in BPR External Data Reference.

Parent Class AutomationMLBPRRoleClassLib/ExternalData


AutomationMLB2MMLRoleClassLib/B2mmlData

Attributes None

Table 33: RoleClass B2mmlData.

AR-MES-ERP 1.1.0 52


5.3 Role Class Library AutomationMLIEC62264RoleClassLib


AutomationMLIEC62264RoleClassLib

HierarchyScope

PersonnelModel

PersonnelClass

Person

QualificationTestSpecification

QualificationTestResult

EquipmentModel

EquipmentClass

Equipment

EquipmentCapabilityTest Specification

EquipmentCapabilityTestResult

PhysicalAssetModel

PhysicalAssetClass

PhysicalAsset

PhysicalAssetCapabilityTest Specification

PhysicalAssetCapabilityTestResult

EquipmentAssetMapping

MaterialModel

MaterialClass

MaterialDefinition

MaterialLot

MaterialSublot

MaterialTestSpecification

MaterialTestResult

MaterialAssembly

ProcessSegmentModel

ProcessSegment

PersonnelSegmentSpecification

EquipmentSegmentSpecification

PhysicalAssetSegmentSpecification

MaterialSegmentSpecification

ProcessSegmentDependency

OperationsDefinitionModel

OperationsDefinition

OperationsMaterialBill

OperationsMaterialBillItem

OperationsSegment

PersonnelSpecification

EquipmentSpecification

PhysicalAssetSpecification

MaterialSpecification

OperationsSegmentDependency

OperationsScheduleModel

OperationsSchedule

OperationsRequest

SegmentRequirement

PersonnelRequirement

EquipmentRequirement

PhysicalAssetRequirement

HierarchyScope Role class used for hierarchy scopes.

PersonnelModel Abstract role class used for structuring personnel roles.

PersonnelClass Role class used for personnel classes.

Person Role class used for persons.

QualificationTest Specification

Role class used for qualification test specifications.

QualificationTestResult Role class used for qualification test results.

EquipmentModel Abstract role class used for structuring equipment roles.

EquipmentClass Role class used for equipment classes.

Equipment Role class used for equipment.

EquipmentCapabilityTest Specification

Role class used for equipment capability test specifications.

EquipmentCapabilityTestResult

Role class used for equipment capability test results.

PhysicalAssetModel Abstract role class for structuring physical asset roles.

PhysicalAssetClass Role class used for physical asset classes.

PhysicalAsset Role class used for physical assets.

PhysicalAssetCapability TestSpecification

Role class used for physical asset capability test specifications.

PhysicalAssetCapability TestResult

Role class used for physical asset capability test results.

EquipmentAssetMapping EquipmentAssetMapping is used to link physical assets to equipment.

MaterialModel Abstract role class for structuring material roles.

MaterialClass Role class used for material classes.

MaterialDefinition Role class used for material definitions.

MaterialLot Role class used for material lots.

MaterialSublot Role class used for material sublots.

MaterialTestSpecification Role class used for material test specifications.

MaterialTestResult Role class used for material test results.

MaterialAssembly Role class used for specifying material assemblies.

AR-MES-ERP 1.1.0 53



MaterialRequirement

RequestedSegmentResponse

OperationsPerformanceModel

OperationsPerformance

OperationsResponse

SegmentResponse

PersonnelActual

EquipmentActual

PhysicalAssetActual

MaterialActual

OperationsCapabilityModel

OperationsCapability

PersonnelCapability

EquipmentCapability

PhysicalAssetCapability

MaterialCapability

ProcessSegmentCapability

ProcessSegmentModel Abstract role class for structuring process segment roles.

ProcessSegment Role class used for process segments.

PersonnelSegment Specification

Role class used for personnel segment specifications.

EquipmentSegment Specification

Role class used for equipment segment specifications.

PhysicalAssetSegment Specification

Role class used for physical asset segment specifications.

MaterialSegment Specification

Role class used for material segment specifications.

ProcessSegment Dependency

Role class used for process segment dependencies.

OperationsDefinition Model

Abstract role class used for structuring operations definition roles.

OperationsDefinition Role class used for operations definitions.

OperationsMaterialBill Role class used for operations material bills.

OperationsMaterialBill Item

Role class used for operations material bill items.

OperationsSegment Role class used for operations segments.

PersonnelSpecification Role class used for personnel specifications.

EquipmentSpecification Role class used for equipment specifications.

PhysicalAsset Specification

Role class used for physical asset specifications.

MaterialSpecification Role class used for material specifications.

OperationsSegment Dependency

Role class used for operations segment dependencies.

OperationsSchedule Model

Abstract role class used for structuring operations schedule roles.

OperationsSchedule Role class used for operations schedules.

OperationsRequest Role class used for operations requests.

SegmentRequirement Role class used for segment requirements.

PersonnelRequirement Role class used for personnel requirements.

AR-MES-ERP 1.1.0 54



EquipmentRequirement Role class used for equipment requirements.

PhysicalAsset Requirement

Role class used for physical asset requirements.

MaterialRequirement Role class used for material requirements.

RequestedSegment Response

Role class used for requested segment responses.

OperationsPerformance Model

Abstract role class used for structuring operations performance roles.

OperationsPerformance Role class used for operations performances.

OperationsResponse Role class used for operations responses.

SegmentResponse Role class used for segment responses.

PersonnelActual Role class used for personnel actual.

EquipmentActual Role class used for equipment actual.

PhysicalAssetActual Role class used for physical asset actual.

MaterialActual Role class used for material actual.

OperationsCapability Model

Abstract role class used for structuring operations capability roles.

OperationsCapability Role class used for operations capabilities.

PersonnelCapability Role class used for personnel capabilities.

EquipmentCapability Role class used for equipment capabilities.

PhysicalAssetCapability Role class used for physical asset capabilities.

MaterialCapability Role class used for material capabilities.

ProcessSegment Capability

Role class used for process segment capabilities.

Table 34: RoleClasses needed for supporting concepts from IEC 62264, subsumed in the AutomationMLIEC62264RoleClassLib.

Some role classes that are defined in Clauses 5.3.1 to 5.3.11 declare attributes; these attributes have been derived from IEC 62264. All these attributes are optional (it is not required to duplicate information that is stored in other documents) – however, if any of these attributes is used in an AML document its value(s) shall be equal to the value(s) in the referenced B2MML document.

AR-MES-ERP 1.1.0 55


5.3.1 Hierarchy Scope

RoleClass “HierarchyScope” shall be used as specified in Table 35. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “HierarchyScope” as a supported role class or role requirement. The relation to a piece of equipment is realized by adding a mirror object of this equipment as a child internal element to this hierarchy scope. Further, a hierarchy scope may contain other hierarchy scope elements as child internal elements.

Class Name HierarchyScope

Description Role class used for hierarchy scopes.

Parent Class AutomationMLBaseRoleClassLib/AutomationMLBaseRole


AutomationMLIEC62264RoleClassLib/HierarchyScope

Attributes

(optional)

equipmentElementLevel (type=“xs:string”) Identification of the equipment level if the equipment element is defined.

Table 35: Role class HierarchyScope.

5.3.2 Personnel

RoleClass “PersonnelModel” shall be used as specified in Table 36. It is the base structuring role class for all personnel roles, without specific semantics on its own. In the context of IEC 62264, one of the concrete sub roles (or any user defined sub role thereof) of PersonnelModel shall be used as a starting point for AML models.

Class Name PersonnelModel

Description Abstract role class used for structuring personnel roles.



AutomationMLIEC62264RoleClassLib/PersonnelModel

Attributes None

Table 36: Role class PersonnelModel.

AR-MES-ERP 1.1.0 56


RoleClass “PersonnelClass” shall be used as specified in Table 37. Instances of this role class shall be realized as role classes, specifying “PersonnelClass” as parent class. Personnel class instances can be realized as internal elements following a singleton pattern, i.e., only up to one internal element can be created for each personnel class. This internal element can be used e.g., for linking within instance hierarchies, or for referencing external data. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name PersonnelClass

Description Role class used for personnel classes.

Parent Class AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Resource


AutomationMLIEC62264RoleClassLib/PersonnelModel/PersonnelClass

Attributes

(optional)

id (type=“xs:string”) Unique identification of a specific personnel class. These are not necessarily job titles, but identify classes that are referenced in other parts of the model.

Table 37: Role class PersonnelClass.

User defined attributes for personnel classes (“PersonnelClassProperty”) shall be defined as complex attributes as specified in Table 38. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for personnel classes. May be tested by the execution of a qualification test specification.

Host Class AutomationMLIEC62264RoleClassLib/PersonnelModel/PersonnelClass

Attributes id (type=“xs:string”) An identification of the specific property, unique under the scope of the parent personnel class object.

Table 38: Attribute type PersonnelClassProperty.

AR-MES-ERP 1.1.0 57


RoleClass “Person” shall be used as specified in Table 39. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “Person” as a supported role class or role requirement. The (optional) relation to one or more personnel classes is realized by referencing these personnel classes as supported role classes. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name Person

Description Role class used for persons.



AutomationMLIEC62264RoleClassLib/PersonnelModel/Person

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific person, within the scope of the information exchanged (e.g. production capability, production schedule, and production performance).

name (type=“xs:string”) The name of the individual.

Table 39: Role class Person.

User defined attributes for persons (“PersonProperty”) shall be defined as complex attributes as specified in Table 40. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for persons. May be tested by the execution of a qualification test specification.

Host Class AutomationMLIEC62264RoleClassLib/PersonnelModel/Person

Attributes id (type=“xs:string”) An identification of the specific property.

Table 40: Attribute type PersonProperty.

AR-MES-ERP 1.1.0 58


RoleClass “QualificationTestSpecification” shall be used as specified in Table 41. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “QualificationTestSpecification” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

An external interface of type “TestConnector” has to be instantiated on a test specification and on a person or personnel class internal element; then, these external interfaces need to be interlinked. That way, the test specification is linked to that resource or resource type. If the test specification needs to specify a resource property or resource type property, it shall instantiate an attribute with the same name as the one to be referred, but prefixed with “ts:” (cf. Clause 5.1).

Class Name QualificationTestSpecification

Description Role class used for qualification test specifications.



AutomationMLIEC62264RoleClassLib/PersonnelModel/QualificationTestSpecification

Attributes

(optional)

id (type=“xs:string”) An identification of a test for certifying one or more values for one or more person properties.

version (type=“xs:string”) An identification of the version of the qualification test specification.

Table 41: Role class QualificationTestSpecification.

RoleClass “QualificationTestResult” shall be used as specified in Table 42. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “QualificationTestSpecification” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Usually, it represents a specific test result for a resource property. If the test result needs to specify such a resource property, it shall instantiate an attribute with the same name as the one to be referred, but prefixed with “tr:” (cf. Clause 5.1).

Class Name QualificationTestResult

Description Role class used for qualification test results.



AutomationMLIEC62264RoleClassLib/PersonnelModel/QualificationTestResult

Attributes

(optional)

id (type=“xs:string”) A unique instance identification that records the results from the execution of a test identified in a qualification test specification for a specific person.

date (type=“xs:dateTime”) The date and time of the qualification test.

result (type=“xs:string”) The result of the qualification test. The unit of measure of the associated test result, is to be specified as the “Unit” attribute, if applicable.

expiration (type=“xs:dateTime”) The date of the expiration of the qualification.

Table 42: Role class QualificationTestResult.

AR-MES-ERP 1.1.0 59


5.3.3 Equipment

RoleClass “EquipmentModel” shall be used as specified in Table 43. It is the base structuring role class for all equipment roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of EquipmentModel shall be used as a starting point for AML models.

Class Name EquipmentModel

Description Abstract role class used for structuring equipment roles.



AutomationMLIEC62264RoleClassLib/EquipmentModel

Attributes None

Table 43: Role class EquipmentModel.

RoleClass “EquipmentClass” shall be used as specified in Table 44. Instances of this role class shall be realized as role classes, specifying “EquipmentClass” as parent class. Equipment class instances can be realized as internal elements following a singleton pattern, i.e., only up to one internal element can be created for each equipment class. This internal element can be used e.g., for linking within instance hierarchies, or for referencing external data. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name EquipmentClass

Description Role class used for equipment classes.



AutomationMLIEC62264RoleClassLib/EquipmentModel/EquipmentClass

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific equipment class, within the scope of the information exchanged (e.g. production capability, production schedule, production performance).

equipmentLevel (type=“xs:string”) An identification of the level in the role based equipment hierarchy. One of (nominal scaled constraint): “Enterprise”, “Site”, “Area”, “Work Center”, “Process Cell”, “Production Unit”, “Production Line”, “Storage Zone”, “Work Unit”, “Unit”, “Work Cell”, “Storage Unit”.

Table 44: Role class EquipmentClass.

AR-MES-ERP 1.1.0 60


User defined attributes for equipment classes (“EquipmentClassProperty”) shall be defined as complex attributes as specified in Table 45. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for equipment classes. May be tested by the execution of an equipment capability test specification.

Host Class AutomationMLIEC62264RoleClassLib/EquipmentModel/EquipmentClass


Table 45: Attribute type EquipmentClassProperty.

RoleClass “Equipment” shall be used as specified in Table 46. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “Equipment” as a supported role class or role requirement. The (optional) relation to one or more equipment classes is realized by referencing these classes as supported role classes. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name Equipment

Description Role class used for equipment.



AutomationMLIEC62264RoleClassLib/EquipmentModel/Equipment

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific piece of equipment, within the scope of the information exchanged (manufacturing operations definition, scheduling, capability and performance).

equipmentLevel (type=“xs:string”) An identification of the level in the role based equipment hierarchy. One of (nominal scaled constraint): “Enterprise”, “Site”, “Area”, “Work Center”, “Process Cell”, “Production Unit”, “Production Line”, “Storage Zone”, “Work Unit”, “Unit”, “Work Cell”, “Storage Unit”.

Table 46: Role class Equipment.

User defined attributes for equipment (“EquipmentProperty”) shall be defined as complex attributes as specified in Table 47. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for equipment. May be tested by the execution of an equipment capability test specification.

Host Class AutomationMLIEC62264RoleClassLib/EquipmentModel/Equipment


Table 47: Attribute type EquipmentProperty.

AR-MES-ERP 1.1.0 61


RoleClass “EquipmentCapabilityTestSpecification” shall be used as specified in Table 48. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “EquipmentCapabilityTestSpecification” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

An external interface of type “TestConnector” has to be instantiated on a test specification and on an equipment or equipment class internal element; then, these external interfaces need to be interlinked. That way, the test specification is linked to that resource or resource type. If the test specification needs to specify a resource property or resource type property, it shall instantiate an attribute with the same name as the one to be referred, but prefixed with “ts:” (cf. Clause 5.1).

Class Name EquipmentCapabilityTestSpecification

Description Role class used for equipment capability test specifications.



AutomationMLIEC62264RoleClassLib/EquipmentModel/ EquipmentCapabilityTestSpecification

Attributes

(optional)

id (type=“xs:string”) An identification of a test for certifying one or more values for one or more equipment properties.

version (type=“xs:string”) An identification of the version of the capability test specification.

Table 48: Role class EquipmentCapabilityTestSpecification.

AR-MES-ERP 1.1.0 62


RoleClass “EquipmentCapabilityTestResult” shall be used as specified in Table 49. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “EquipmentCapabilityTestResult” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.


Class Name EquipmentCapabilityTestResult

Description Role class used for equipment capability test results.



AutomationMLIEC62264RoleClassLib/EquipmentModel/ EquipmentCapabilityTestResult

Attributes

(optional)

id (type=“xs:string”) A unique instance identification that records the results from the execution of a test identified in a capability test specification for a specific piece of equipment.

date (type=“xs:dateTime”) The date and time of the capability test.

result (type=“xs:string”) The result of the capability test. The unit of measure of the associated test result, is to be specified as the “Unit” attribute, if applicable.

expiration (type=“xs:dateTime”) The date of the expiration of the capability.

Table 49: Attribute type EquipmentCapabilityTestResult.


RoleClass “PhysicalAssetModel” shall be used as specified in Table 50. It is the base structuring role class for all physical asset roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of PhysicalAssetModel shall be used as a starting point for AML models.

Class Name PhysicalAssetModel

Description Abstract role class used for structuring physical asset roles.



AutomationMLIEC62264RoleClassLib/PhysicalAssetModel

Attributes None

Table 50: Role class PhysicalAssetModel.

AR-MES-ERP 1.1.0 63


RoleClass “PhysicalAssetClass” shall be used as specified in Table 51. Instances of this role class shall be realized as system unit classes, specifying “PhysicalAssetClass” as a supported role class. Physical asset class instances can be realized as internal elements following a singleton pattern, i.e., only up to one internal element can be created for each physical asset class. This internal element can be used e.g., for linking within instance hierarchies. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name PhysicalAssetClass

Description Role class used for physical asset classes.



AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAssetClass

Attributes

(optional)

manufacturer (type=”xs:string”) An identification of the manufacturer.

id (type=“xs:string”) The manufacturer’s identification of the specific physical asset class.

description (type=“xs:string”) Additional information about the physical asset class.

Table 51: Role class PhysicalAssetClass.

User defined attributes for physical asset classes (“PhysicalAssetClassProperty”) shall be defined as complex attributes as specified in Table 52. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for physical asset classes. May be tested by the execution of a physical asset capability test specification.

Host Class AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAssetClass


Table 52: Attribute type PhysicalAssetClassProperty.

AR-MES-ERP 1.1.0 64


RoleClass “PhysicalAsset” shall be used as specified in Table 53. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “PhysicalAsset” as a supported role class or role requirement. The relation to the physical asset class is realized by specifying the RefBaseSystemUnitPath with the path to the corresponding system unit class. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name PhysicalAsset

Description Role class used for physical assets.



AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset

Attributes

(optional)

id (type=“xs:string”) Defines a unique identification of a physical asset.

physicalLocation (type=“xs:string”) Actual physical location of the physical asset.

fixedAssetId (type=“xs:string”) Contains a unique identification for financial tracking as required by laws or regulations.

vendorId (type=“xs:string”) Contains a vendor’s serial number.

Table 53: Role class PhysicalAsset.

User defined attributes for physical assets (“PhysicalAssetProperty”) shall be defined as complex attributes as specified in Table 54. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for physical assets. May be tested by the execution of a physical asset capability test specification.

Host Class AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset


Table 54: Attribute type PhysicalAssetProperty.

AR-MES-ERP 1.1.0 65


RoleClass “PhysicalAssetCapabilityTestSpecification” shall be used as specified in Table 55. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “PhysicalAssetCapabilityTestSpecification” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

An external interface of type “TestConnector” has to be instantiated on a test specification and on a physical asset or physical asset class internal element; then, these external interfaces need to be interlinked. That way, the test specification is linked to that resource or resource type. If the test specification needs to specify a resource property or resource type property, it shall instantiate an attribute with the same name as the one to be referred, but prefixed with “ts:” (cf. Clause 5.1).

Class Name PhysicalAssetCapabilityTestSpecification

Description Role class used for physical asset capability test specifications.



AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/ PhysicalAssetCapabilityTestSpecification

Attributes

(optional)

id (type=“xs:string”) An identification of the specific physical asset capability test specification.

version (type=“xs:string”) An identification of the version of the capability test specification.

Table 55: Role class PhysicalAssetCapabilityTestSpecification.

RoleClass “PhysicalAssetCapabilityTestResult” shall be used as specified in Table 56. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “PhysicalAssetCapabilityTestResult” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.


Class Name PhysicalAssetCapabilityTestResult

Description Role class used for physical asset capability test results.



AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/ PhysicalAssetCapabilityTestResult

Attributes

(optional)

id (type=“xs:string”) An identification of the specific physical asset capability test result.

date (type=“xs:dateTime”) The date and time of the capability test.

result (type=“xs:string”) The result of the capability test. The unit of measure of the associated test result, is to be specified as the “Unit” attribute, if applicable.

expiration (type=“xs:dateTime”) The date of the expiration of the capability.

Table 56: Attribute type PhysicalAssetCapabilityTestResult.

AR-MES-ERP 1.1.0 66


RoleClass “EquipmentAssetMapping” shall be used as specified in Table 57: an instance of this class is instantiated as an internal element somewhere in the instance hierarchy (could be realized in a dedicated EquipmentAssetMapping “folder”). The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

External interfaces of type “EquipmentAssetConnector” have to be instantiated on (i) an equipment and a physical asset and (ii) on an equipment asset mapping; then, these external interfaces need to be interlinked. That way, the physical asset is linked to an equipment through a reified equipment asset mapping relation (cf. Clause 5.1).

Class Name EquipmentAssetMapping

Description RoleClass “EquipmentAssetMapping” shall be used to link physical assets to equipment.



AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/EquipmentAssetMapping

Attributes

(optional)

id (type=“xs:string”) An identification of the specific equipment asset mapping.

startTime (type=“xs:dateTime”) The starting time of the association.

endTime (type=“xs:dateTime”) The ending time of the association.

Table 57: RoleClass EquipmentAssetMapping.

5.3.5 Material

RoleClass “MaterialModel” shall be used as specified in Table 58. It is the base structuring role class for all material roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of MaterialModel shall be used as a starting point for AML models.

Class Name MaterialModel

Description Abstract role class used for structuring material roles.



AutomationMLIEC62264RoleClassLib/MaterialModel

Attributes None

Table 58: Role class MaterialModel.

AR-MES-ERP 1.1.0 67


RoleClass “MaterialClass” shall be used as specified in Table 59. Instances of this role class shall be realized as role classes, specifying “MaterialClass” as parent class. Material class instances can be realized as internal elements following a singleton pattern, i.e., only up to one internal element can be created for each material class. This internal element can be used e.g., for linking within instance hierarchies, or for referencing external data. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name MaterialClass

Description Role class used for material classes.

Parent Class AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Product


AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialClass

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific material class, within the scope of the information exchanged (e.g. production capability, production schedule, production performance)

assemblyType (type=“xs:string”) Defines the type of the assembly. One of (nominal scaled constraint) “Physical” or “Logical”.

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.

assemblyRelationship (type=“xs:string”) Defines the type of the relationships. One of (nominal scaled constraint) “Permanent” or “Transient”.

Permanent: an assembly that is not intended to be split during the production process.

Transient: a temporary assembly used during production, such as a pallet of different materials or a batch kit.

Table 59: Role class MaterialClass.

User defined attributes for material classes (“MaterialClassProperty”) shall be defined as complex attributes as specified in Table 60. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for material classes. May be tested by the execution of a material test specification.

Host Class AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialClass

Attributes id (type=“xs:string”) An identification of a specific material class property.

Table 60: Attribute type MaterialClassProperty.

AR-MES-ERP 1.1.0 68


RoleClass “MaterialDefinition” shall be used as specified in Table 61. Instances of this role class shall be realized as system unit classes, specifying “MaterialDefinition” as a supported role class. The (optional) relation to one or more material classes is realized by referencing the material classes as supported role classes. Material definition instances can be realized as internal elements following a singleton pattern, i.e., only up to one internal element can be created for each material definition. This internal element can be used e.g., for linking within instance hierarchies. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name MaterialDefinition

Description Role class used for material definitions.



AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialDefinition

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific material definition, within the scope of the information exchanged (e.g. operations capability, operations schedule, operations performance).







Table 61: Role class MaterialDefinition.

User defined attributes for material definitions (“MaterialDefinitionProperty”) shall be defined as complex attributes as specified in Table 62. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for material definitions. May be tested by the execution of a material test specification.

Host Class AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialDefinition

Attributes id (type=“xs:string”) An identification of the specific material definition property.

Table 62: Attribute type MaterialDefinitionProperty.

AR-MES-ERP 1.1.0 69


RoleClass “MaterialLot” shall be used as specified in Table 63. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “MaterialLot” as a supported role class or role requirement. The relation to the material definition is realized by specifying the RefBaseSystemUnitPath pointing to the corresponding system unit class. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name MaterialLot

Description Role class used for material lots – a uniquely identified specific amount of material, either countable or weighable. A material lot describes the planned or actual total quantity or amount of material available, its current state, and its specific property values.



AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialLot

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific material lot, within the scope of the information exchanged (e.g. operations capability, operations schedule, operations performance).







status (type=“xs:string”) Status of the material lot, e.g. “released”, “approved”, “blocked”, “in process”, “in quality check”.

storageLocation (type=“xs:string”) An identification of the storage location or a physical location of the material lot.

quantity (type=“xs:string”) The quantity of the material lot. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 63: Role class MaterialLot.

NOTE: If material lots are merged or absorbed (e.g. blended), then this is a new material lot [IEC 62264-2].

AR-MES-ERP 1.1.0 70


NOTE: Representation of non-lot controlled items (for example consumable materials or bulk materials), can be represented in the material lot model through the use of a unique ID for each different material definition [IEC 62264-2].

NOTE: If non-lot controlled items are maintained in multiple locations then the information can be represented in the material sublot model through the use of a unique sublot ID for each different location and material definition [IEC 62264-2].

User defined attributes for material lots and sublots (“MaterialLotProperty”) shall be defined as complex attributes as specified in Table 64. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the property.

Description User defined attributes for material lots and sublots. May be tested by the execution of a material test specification.

Host Class AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialLot

- or -

AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialSublot

Attributes id (type=“xs:string”) An identification of the specific material lot property.

Table 64: Attribute type MaterialLotProperty.

AR-MES-ERP 1.1.0 71


RoleClass “MaterialSublot” shall be used as specified in Table 65. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “MaterialSublot” as a supported role class or role requirement. The relation to the parent material (sub)lot is realized by inserting the material sublot as a child element of a material (sub)lot internal element. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name MaterialSublot

Description Role class used for material sublots – a separately identifiable quantity of the same material lot. A material lot may be stored in separately identifiable quantities. 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.



AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialSublot

Attributes

(optional)

id (type=“xs:string”) A unique identification of a specific material sublot, within the scope of the information exchanged (e.g. production capability, production schedule, production performance).







status (type=“xs:string”) Status of the material sublot, e.g. “released”, “approved”, “blocked”, “in process”, “in quality check”.

storageLocation (type=“xs:string”) An identification of the storage location or a physical location of the material sublot.

quantity (type=“xs:string”) The quantity of the material sublot. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 65: Role class MaterialSublot.

NOTE: If material sublots are merged or absorbed (e.g. blended), then this is a new material sublot [IEC 62264-2].

AR-MES-ERP 1.1.0 72


NOTE: Assemblies are collections or sets of related elements. Assemblies are represented as relationships between elements and attributes of the elements. Each assembly element has its own identity and properties, such as a material lot which has its own identity and properties. An object with an assembly (material lot, material sublot, material class, and material definition) shall contain the list of other elements that make up the assembly. 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 [IEC 62264-2].

RoleClass “MaterialTestSpecification” shall be used as specified in Table 66. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “MaterialTestSpecification” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

An external interface of type “TestConnector” has to be instantiated on a test specification and on a material class, material definition, or material lot internal element; then, these external interfaces need to be interlinked. That way, the test specification is linked to that resource or resource type. If the test specification needs to specify a resource property or resource type property, it shall instantiate an attribute with the same name as the one to be referred, but prefixed with “ts:” (cf. Clause 5.1).

Class Name MaterialTestSpecification

Description Role class used for material test specifications.



AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialTestSpecification

Attributes

(optional)

id (type=“xs:string”) An identification of a test for certifying one or more values for one or more material properties.

version (type=“xs:string”) An identification of the version of the maerial test specification.

Table 66: Role class MaterialTestSpecification.

AR-MES-ERP 1.1.0 73


RoleClass “MaterialTestResult” shall be used as specified in Table 67. It can be instantiated anywhere in the instance hierarchy as an internal element specifying “MaterialTestResult” as supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Usually, it represents a specific test result for a material lot property. If the test result needs to specify such a material lot property, it shall instantiate an attribute with the same name as the one to be referred, but prefixed with “tr:” (cf. Clause 5.1).

Class Name MaterialTestResult

Description Role class used for material test results.



AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialTestResult

Attributes

(optional)

id (type=“xs:string”) A unique instance identification that records the results from the execution of a test identified in a material test specification for a lot or sublot.

date (type=“xs:dateTime”) The date and time of the material test.

result (type=“xs:string”) The value or list of values returned from the performance of the material test. The unit of measure of the associated test result, is to be specified as the “Unit” attribute, if applicable.

expiration (type=“xs:dateTime”) The date of the expiration of the test results.

Table 67: Attribute type MaterialTestResult.

RoleClass “MaterialAssembly” shall be used as specified in Table 68. It holds internal elements of either material class, material definition, material lot, or material sublot type (often, but not exclusively, in terms of mirror objects). Instances of this role class shall be realized as a child internal element of the material type that defines an asembly, specifying “MaterialAssembly” as a supported role class or role requirement. A material assembly of a material class might only contain other material classes, a material definition assembly might only contain material definitions. A material assembly of a material lot or sublot might each contain instances of both material lots and material sublots.

The “MaterialAssembly” role class is also used to specify assembly relationships of the following entities: Material Segment Specification (cf. Clause 5.3.6), Material Specification and Operations Material Bill Item (cf. Clause 5.3.7), Material Requirement (cf. Clause 5.3.8), Material Actual (cf. Clause 5.3.9), and Material Capability (cf. Clause 5.3.10).

Class Name MaterialAssembly

Description Role class used for specifying material class and material definition assemblies.



AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialAssembly

Attributes None

Table 68: Role class MaterialAssembly.

AR-MES-ERP 1.1.0 74



RoleClass “ProcessSegmentModel” shall be used as specified in Table 69. It is the base structuring role class for all process segment roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of ProcessSegmentModel shall be used as a starting point for AML models.

Class Name ProcessSegmentModel

Description Abstract role class used for structuring process segment roles.



AutomationMLIEC62264RoleClassLib/ProcessSegmentModel

Attributes None

Table 69: Role class ProcessSegmentModel.

RoleClass “ProcessSegment” shall be used as specified in Table 70. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “ProcessSegment” as a supported role class or role requirement. Nested process segments can be modeled directly as child internal elements or they can be defined as child internal element in terms of a mirror object.

The hierarchy scope of this element is defined by a relation to a “HierarchyScope” internal element. The relation is defined as follows: this element needs to define an external interface of type “HierarchyScopeConnector” that is linked via an internal link to another “HierarchyScopeConnector” external interface that is bound to a “HierarchyScope” internal element. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name ProcessSegment

Description Role class used for process segment classes.

Parent Class AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Process


AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ProcessSegment

Attributes

(optional)

id (type=“xs:string”) A unique identification of a process segment, within the scope of the information exchanged (e.g. operations capability, operations schedule, operations performance).

operationsType (type=“xs:string”) Describes the category of the activity. One of (nominal scaled constraint) “Production”, “Maintenance”, “Quality”, “Inventory”, or “Mixed”.

“Mixed” shall be used when the activity contains several categories of process segments.

duration (type=“xs:decimal”) Duration of process segment, if known. The unit of measure of the duration, is to be specified as the “Unit” attribute, if defined.

Table 70: Role class ProcessSegment.

AR-MES-ERP 1.1.0 75


Parameters for process segments (“ProcessSegmentParameter”) shall be defined as complex attributes as specified in Table 71. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the parameter.

Description Process segment parameters for process segments.

Host Class AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ProcessSegment

Attributes id (type=“xs:string”) Identification of the process segment parameter.

Table 71: Attribute type ProcessSegmentParameter.

RoleClass “PersonnelSegmentSpecification” shall be used as specified in Table 72. Instances of this role class shall be realized as child internal elements of a “ProcessSegment” internal element in an instance hierarchy, specifying “PersonnelSegmentSpecification” as a supported role class or role requirement. Its purpose is the specification of the personnel class or person that is involved in the given process segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.

The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name PersonnelSegmentSpecification

Description Role class used for personnel segment specification classes – personnel resources that are required for a process segment.



AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ PersonnelSegmentSpecification

Attributes

(optional)

personnelUse (type=“xs:string”) Defines the expected use of the personnel class or person, e.g. “Allocated” or “Certified”.

quantity (type=“xs:decimal”) Specifies the personnel resource required for the parent process segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 72: Role class PersonnelSegmentSpecification.

AR-MES-ERP 1.1.0 76


User defined attributes for personnel segment specifications (“PersonnelSegmentSpecificationProperty”) shall be defined as complex attributes as specified in Table 73. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the resources required and its unit of measure, if applicable.

Description User defined attributes for personnel segment specifications.

Host Class AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ PersonnelSegmentSpecification

Attributes id (type=“xs:string”) An identification of a property of the associated person property or personnel class property.

quantity (type=“xs:decimal”) Specifies the personnel resource required, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 73: Attribute type PersonnelSegmentSpecificationProperty.

RoleClass “EquipmentSegmentSpecification” shall be used as specified in Table 74. Instances of this role class shall be realized as child internal elements of a “ProcessSegment” internal element in an instance hierarchy, specifying “EquipmentSegmentSpecification” as a supported role class or role requirement. Its purpose is the specification of the equipment class or equipment that is involved in the given process segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name EquipmentSegmentSpecification

Description Role class used for equipment segment specification classes – equipment resources that are required for a process segment.



AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ EquipmentSegmentSpecification

Attributes

(optional)

equipmentUse (type=“xs:string”) Defines the expected use of the equipment class or equipment in the context of the process segment, e.g. “Part Milling”, “Remove Motor”, “Run Test”, and “Material Movement”.

quantity (type=“xs:decimal”) Specifies the amount of resources required, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 74: Role class EquipmentSegmentSpecification.

AR-MES-ERP 1.1.0 77


User defined attributes for equipment segment specifications (“EquipmentSegmentSpecificationProperty”) shall be defined as complex attributes as specified in Table 75. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the resources required and its unit of measure, if applicable.

Description User defined attributes for equipment segment specifications.

Host Class AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ EquipmentSegmentSpecification

Attributes id (type=“xs:string”) An identification of a property of the associated equipment property or equipment class property.

quantity (type=“xs:decimal”) Specifies the amount of resources required. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 75: Attribute type EquipmentSegmentSpecificationProperty.

RoleClass “PhysicalAssetSegmentSpecification” shall be used as specified in Table 76. Instances of this role class shall be realized as child internal elements of a “ProcessSegment” internal element in an instance hierarchy, specifying “PhysicalAssetSegmentSpecification” as a supported role class or role requirement. Its purpose is the specification of the physical asset class or physical asset that is involved in the given process segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name PhysicalAssetSegmentSpecification

Description Role class used for physical asset segment specification classes – physical asset resources that are required for a process segment.



AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ PhysicalAssetSegmentSpecification

Attributes

(optional)

physicalAssetUse (type=“xs:string”) Defines the expected use of the physical asset class or physical asset in the context of the process segment.


Table 76: Role class PhysicalAssetSegmentSpecification.

AR-MES-ERP 1.1.0 78


User defined attributes for physical asset segment specifications (“PhysicalAssetSegmentSpecificationProperty”) shall be defined as complex attributes as specified in Table 77. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the resources required and its unit of measure, if applicable.

Description User defined attributes for physical asset segment specifications.

Host Class AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ PhysicalAssetSegmentSpecification

Attributes id (type=“xs:string”) An identification of a property of the associated physical asset property or physical asset class property.


Table 77: Attribute type PhysicalAssetSegmentSpecificationProperty.

AR-MES-ERP 1.1.0 79


RoleClass “MaterialSegmentSpecification” shall be used as specified in Table 78. Instances of this role class shall be realized as child internal elements of a “ProcessSegment” internal element in an instance hierarchy, specifying “MaterialSegmentSpecification” as a supported role class or role requirement. Its purpose is the specification of the material class or material definition that is involved in the given process segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name MaterialSegmentSpecification

Description Role class used for material segment specification classes – material resources that are required for a process segment.



AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ MaterialSegmentSpecification

Attributes

(optional)







materialUse (type=“xs:string”) Defines the material use. One of (nominal scaled constraint): “Consumable”, “Material Consumed”, and “Material Produced”.


Table 78: Role class MaterialSegmentSpecification.

AR-MES-ERP 1.1.0 80


User defined attributes for material segment specifications (“MaterialSegmentSpecificationProperty”) shall be defined as complex attributes as specified in Table 79. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the resources required and its unit of measure, if applicable.

Description User defined attributes for material segment specifications.

Host Class AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ MaterialSegmentSpecification

Attributes id (type=“xs:string”) An identification of a property of the associated material definition property or material class property.


Table 79: Attribute type MaterialSegmentSpecificationProperty.

RoleClass “ProcessSegmentDependency” shall be used as specified in Table 80. Its purpose is the specification of a process segment dependency that is relevant for the given process segment. Instances of this role class shall be realized as internal elements anywhere in the instance hierarchy, specifying “ProcessSegmentDependency” as a supported role class or role requirement. The referenced process segment is specified through internal linking, by adding an instance of interface class “DependencyConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “DependencyConnector” is already existing, it can be reused.


Class Name ProcessSegmentDependency

Description Role class used for process segment dependency classes – process dependencies that are independent of any particular product or operations task.



AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ ProcessSegmentDependency

Attributes

(optional)

id (type=“xs:string”) The identification of the unique instance of the process segment dependency.

dependencyType (type=“xs:string”) Defines the execution dependency constraints of one segment by another segment.

dependencyFactor (type=“xs:decimal”) Factor used by dependency. The unit of measure of the dependency factor, is to be specified as the “Unit” attribute, if defined.

Table 80: Role class ProcessSegmentDependency.

AR-MES-ERP 1.1.0 81


5.3.7 Operations Definition

RoleClass “OperationsDefinitionModel” shall be used as specified in Table 81. It is the base structuring role class for all operations definition roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of OperationsDefinitionModel shall be used as a starting point for AML models.

Class Name OperationsDefinitionModel

Description Abstract role class used for structuring operations definition roles.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel

Attributes None

Table 81: Role class OperationsDefinitionModel.

RoleClass “OperationsDefinition” shall be used as specified in Table 82. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “OperationsDefinition” as a supported role class or role requirement. Operations definitions usually hold child internal elements of type “OperationsMaterialBill” and “OperationsSegment”. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

The hierarchy scope of this element is defined by a relation to a “HierarchyScope” internal element. The relation is defined as follows: this element needs to define an external interface of type “HierarchyScopeConnector” that is linked via an internal link to another “HierarchyScopeConnector” external interface that is bound to a “HierarchyScope” internal element.

Class Name OperationsDefinition

Description Role class used for operations definition classes.

Parent Class AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Structure/ProcessStructure


AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/OperationsDefinition

Attributes

(optional)

id (type=“xs:string”) Uniquely identifies the operations definition.

version (type=“xs:string”) An identification of the version of the operations definition.

operationsType (type=“xs:string”) Describes the category of operation. One of (nominal scaled constraint) “Production”, “Maintenance”, “Quality”, “Inventory”, or “Mixed”.

“Mixed” shall be used when the operations definition contains several types of operations requests and/or segment requirements.

workDefinitionId (type=“xs:string”) Identification of the external work definition associated with this operations definition.

billOfResourceId (type=“xs:string”) Identification of the external bill of resources associated with this operations definition.

Table 82: Role class OperationsDefinition.

AR-MES-ERP 1.1.0 82


RoleClass “OperationsMaterialBill” shall be used as specified in Table 83. Instances of this role class shall be realized as child internal elements of an “OperationsDefinition” internal element in an instance hierarchy, specifying “OperationsMaterialBill” as a supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name OperationsMaterialBill

Description Role class used for operations material bill classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ OperationsMaterialBill

Attributes

(optional)

id (type=“xs:string”) Unique identification of a manufacturing bill.

Table 83: Role class OperationsMaterialBill.

AR-MES-ERP 1.1.0 83


RoleClass “OperationsMaterialBillItem” shall be used as specified in Table 84. Instances of this role class shall be realized as child internal elements of an “OperationsMaterialBill” internal element in an instance hierarchy, specifying “OperationsMaterialBillItem” as a supported role class or role requirement. Operations material bill items may be made up of further operations material bill items (often in terms of mirror child objects). In addition, an operations material bill item shall hold a mirror child internal element of type “MaterialSpecification” in order to specify the concrete material resource represented by this operations material bill item. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Class Name OperationsMaterialBillItem

Description Role class used for operations material bill item classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ OperationsMaterialBillItem

Attributes

(optional)

id (type=“xs:string”) Unique identification of a bill item.

useType (type=“xs:string”) Defines the use of the material. One of (nominal scaled constraint): “Consumed” or “Produced”.

Consumed: Indicates that bill items are all consumed materials.

Produced: Indicates that bill items are all produced materials.








Table 84: Role class OperationsMaterialBillItem.

AR-MES-ERP 1.1.0 84


RoleClass “OperationsSegment” shall be used as specified in Table 85. Instances of this role class shall be realized as child internal elements of an “OperationsDefinition” internal element in an instance hierarchy, specifying “OperationsSegment” as a supported role class or role requirement. Nested operations segments can be modeled directly as child internal elements or they can be defined as child internal element in terms of a mirror object. Usually, operations segment hold child internal elements for resource specification or of type “OperationsSegmentDependency”. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

Related process segments are specified through internal linking, by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name OperationsSegment

Description Role class used for operations segment classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/OperationsSegment

Attributes

(optional)

id (type=“xs:string”) Unique identification of a specific segment.

duration (type=“xs:string”) Duration of segment, if known. The unit of measure of the duration, is to be specified as the “Unit” attribute, if defined.


“Mixed” shall be used when the operations segment contains several types of operations requests and/or segment requirements.

workDefinitionId (type=“xs:string”) Identification of the external work definition associated with this operations segment.

Table 85: Role class OperationsSegment.

Parameter specifications for operations segments (“ParameterSpecification”) shall be defined as complex attributes as specified in Table 86. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the parameter.

Description Parameter specification for operations segments.

Host Class AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/OperationsSegment

Attributes id (type=“xs:string”) Identification of the parameter for a specific segment.

Table 86: Attribute type ParameterSpecification.

AR-MES-ERP 1.1.0 85


RoleClass “PersonnelSpecification” shall be used as specified in Table 87. Instances of this role class shall be realized as child internal elements of an “OperationsSegment” internal element in an instance hierarchy, specifying “PersonnelSpecification” as a supported role class or role requirement. Its purpose is the specification of the personnel class or person that is involved in the given operations segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name PersonnelSpecification

Description Role class used for personnel specification classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ PersonnelSpecification

Attributes

(optional)

personnelUse (type=“xs:string”) Defines the expected use of the personnel class or person.

quantity (type=“xs:decimal”) Specifies the amount of personnel resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 87: Role class PersonnelSpecification.

Properties for personnel specifications (“PersonnelSpecificationProperty”) shall be defined as complex attributes as specified in Table 88. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Parameter specification for personnel specifications.

Host Class AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ PersonnelSpecification

Attributes id (type=“xs:string”) Identification of a property of the associated person property or personnel class property for a specific segment.

quantity (type=“xs:decimal”) Specifies the amount of personnel resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 88: Attribute type PersonnelSpecificationProperty.

AR-MES-ERP 1.1.0 86


RoleClass “EquipmentSpecification” shall be used as specified in Table 89. Instances of this role class shall be realized as child internal elements of an “OperationsSegment” internal element in an instance hierarchy, specifying “EquipmentSpecification” as a supported role class or role requirement. Its purpose is the specification of the equipment class or equipment that is involved in the given operations segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name EquipmentSpecification

Description Role class used for equipment specification classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ EquipmentSpecification

Attributes

(optional)

equipmentUse (type=“xs:string”) Defines the expected use of the equipment class or equipment.

quantity (type=“xs:decimal”) Specifies the amount of equipment resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 89: Role class EquipmentSpecification.

Properties for equipment specifications (“EquipmentSpecificationProperty”) shall be defined as complex attributes as specified in Table 90. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Parameter specification for equipment specifications.

Host Class AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ EquipmentSpecification

Attributes id (type=“xs:string”) Identification of a property of the associated equipment property or equipment class property for a specific segment.

quantity (type=“xs:decimal”) Specifies the amount of equipment resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 90: Attribute type EquipmentSpecificationProperty.

AR-MES-ERP 1.1.0 87


RoleClass “PhysicalAssetSpecification” shall be used as specified in Table 91. Instances of this role class shall be realized as child internal elements of an “OperationsSegment” internal element in an instance hierarchy, specifying “PhysicalAssetSpecification” as a supported role class or role requirement. Its purpose is the specification of the physical asset class or physical asset that is involved in the given operations segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name PhysicalAssetSpecification

Description Role class used for physical asset specification classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ PhysicalAssetSpecification

Attributes

(optional)

physicalAssetUse (type=“xs:string”) Defines the expected use of the physical asset class or physical asset.

quantity (type=“xs:decimal”) Specifies the amount of physical asset resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 91: Role class PhysicalAssetSpecification.

Properties for physical asset specifications (“PhysicalAssetSpecificationProperty”) shall be defined as complex attributes as specified in Table 92. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Parameter specification for physical asset specifications.

Host Class AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ PhysicalAssetSpecification

Attributes id (type=“xs:string”) Identification of a property of the associated physical asset property or physical asset class property for a specific segment.

quantity (type=“xs:decimal”) Specifies the amount of physical asset resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 92: Attribute type PhysicalAssetSpecificationProperty.

AR-MES-ERP 1.1.0 88


RoleClass “MaterialSpecification” shall be used as specified in Table 93. Instances of this role class shall be realized as child internal elements of an “OperationsSegment” internal element in an instance hierarchy, specifying “MaterialSpecification” as a supported role class or role requirement. Its purpose is the specification of the material class or material definition that is involved in the given operations segment. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either a material class or material definition is specified [IEC 62264-2].

Class Name MaterialSpecification

Description Role class used for material specification classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ MaterialSpecification

Attributes

(optional)

materialUse (type=“xs:string”) Defines the expected material use. One of (nominal scaled constraint) “Material Consumed”, “Material Produced”, or “Consumable”.

quantity (type=“xs:decimal”) Specifies the amount of material resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.







Table 93: Role class MaterialSpecification.

AR-MES-ERP 1.1.0 89


Properties for material specifications (“MaterialSpecificationProperty”) shall be defined as complex attributes as specified in Table 94. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Parameter specification for material specifications.

Host Class AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ MaterialSpecification

Attributes id (type=“xs:string”) Identification of the associated material property for a specific segment.

quantity (type=“xs:decimal”) Specifies the amount of material resources required for the parent segment, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 94: Attribute type MaterialSpecificationProperty.

RoleClass “OperationsSegmentDependency” shall be used as specified in Table 95. Instances of this role class shall be realized as child internal elements of an “OperationsSegment” internal element in an instance hierarchy, specifying “OperationsSegmentDependency” as a supported role class or role requirement. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

The referenced operations segment is specified through internal linking, by adding an instance of interface class “DependencyConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “DependencyConnector” is already existing, it can be reused.

Class Name OperationsSegmentDependency

Description Role class used for operations segment dependency classes.



AutomationMLIEC62264RoleClassLib/OperationsDefinitionModel/ OperationsSegmentDependency

Attributes

(optional)

id (type=“xs:string”) Identification of the unique instance of the operations segment dependency.

dependencyType (type=“xs:string”) Defines the execution dependency constraints of one segment by another segment.

dependencyFactor (type=“xs:string”) Factor used by dependency. The unit of measure of the dependency factor, is to be specified as the “Unit” attribute, if defined.

Table 95: Role class OperationsSegmentDependency.

AR-MES-ERP 1.1.0 90


5.3.8 Operations Schedule

RoleClass “OperationsScheduleModel” shall be used as specified in Table 96. It is the base structuring role class for all operations schedule roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of OperationsScheduleModel shall be used as a starting point for AML models.

Class Name OperationsScheduleModel

Description Abstract role class used for structuring operations schedule roles.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel

Attributes None

Table 96: Role class OperationsScheduleModel.

AR-MES-ERP 1.1.0 91


RoleClass “OperationsSchedule” shall be used as specified in Table 97. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “OperationsSchedule” as a supported role class or role requirement. Child internal elements include mainly elements of type “OperationsRequest”. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.


Class Name OperationsSchedule

Description Role class used for operations schedule classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ OperationsSchedule

Attributes

(optional)

id (type=“xs:string”) Uniquely identifies the operations schedule and could include version and revision identification.



startTime (type=“xs:dateTime”) The starting time for the associated operations schedule, if applicable.

endTime (type=“xs:dateTime”) The ending time for the associated operations schedule, if applicable.

publishedDate (type=“xs:dateTime”) The date and time on which the operations schedule was published or generated.

scheduledState (type=“xs:string”) Indicates the state of the operations schedule. One of (nominal scaled constraint) “Forecast” or “Released”.

Forecast: the requirements have not been released for use.

Released: the requirements have been released for use.

Table 97: Role class OperationsSchedule.

AR-MES-ERP 1.1.0 92


RoleClass “OperationsRequest” shall be used as specified in Table 98. Instances of this role class shall be realized as child internal elements of an “OperationsSchedule” internal element in an instance hierarchy, specifying “OperationsRequest” as a supported role class or role requirement. Operations requests usually hold child internal elements of type “SegmentRequirement”. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

A related operations definition is specified through internal linking, by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name OperationsRequest

Description Role class used for operations request classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/OperationsRequest

Attributes

(optional)

id (type=“xs:string”) Unique identification of the operations request.

operationsType (type=“xs:string”) Describes the category of operations. One of (nominal scaled constraint) “Production”, “Maintenance”, “Quality”, “Inventory”, or “Mixed”.


startTime (type=“xs:dateTime”) When operation is to be started operations schedule, if applicable.

endTime (type=“xs:dateTime”) When operation is to be completed, if applicable.

priority (type=“xs:string”) The priority of the request, if applicable.

requestState (type=“xs:string”) Indicates the state of the operations request. One of (nominal scaled constraint) “Forecast” or “Released”.



Table 98: Role class OperationsRequest.

AR-MES-ERP 1.1.0 93


RoleClass “SegmentRequirement” shall be used as specified in Table 99. Instances of this role class shall be realized as child internal elements of an “OperationsRequest” internal element in an instance hierarchy, specifying “SegmentRequirement” as a supported role class or role requirement. Nested segment requirements can be modeled directly as child internal elements or they can be defined as child internal element in terms of a mirror object. Typical child internal elements of segment requirements are the resource requirement classes specified below. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

A related operations segment or process segment is specified through internal linking, by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name SegmentRequirement

Description Role class used for segment requirement classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ SegmentRequirement

Attributes

(optional)

id (type=“xs:string”) Unique identification of the segment requirement.



earliestStartTime (type=“xs:dateTime”) The expected earliest start time of this segment requirement, if applicable.

latestEndTime (type=“xs:dateTime”) The expected latest ending time of this segment requirement, if applicable.

duration (type=“xs:decimal”) The expected duration of this segment requirement, if applicable. Note: this should match the associated segment duration. The unit of measure of the duration, is to be specified as the “Unit” attribute, if applicable.

segmentState (type=“xs:string”) Indicates the state of the segment request. One of (nominal scaled constraint) “Forecast” or “Released”.



Table 99: Role class SegmentRequirement.

AR-MES-ERP 1.1.0 94


Parameters for segment requirements (“SegmentParameter”) shall be defined as complex attributes as specified in Table 100. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the parameter.

Description Parameter specification for segment requirements.

Host Class AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ SegmentRequirement

Attributes id (type=“xs:string”) Identification of the segment parameter.

Table 100: Attribute type SegmentParameter.

RoleClass “PersonnelRequirement” shall be used as specified in Table 101. Instances of this role class shall be realized as child internal elements of a “SegmentRequirement” internal element in an instance hierarchy, specifying “PersonnelRequirement” as a supported role class or role requirement. Its purpose is the specification of the personnel class or person that is involved in the given segment requirement. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either personnel class or person is specified, but not both [IEC 62264-2].

Class Name PersonnelRequirement

Description Role class used for personnel requirement classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ PersonnelRequirement

Attributes

(optional)

personnelUse (type=“xs:string”) Defines the expected use of the personnel class or person.

quantity (type=“xs:decimal”) Specifies the amount of personnel resources required for the parent segment, if applicable. Applies to each member of the person and personnel class sets. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 101: Role class PersonnelRequirement.

AR-MES-ERP 1.1.0 95


Properties for personnel requirements (“PersonnelRequirementProperty”) shall be defined as complex attributes as specified in Table 102. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for personnel requirements.

Host Class AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ PersonnelRequirement

Attributes id (type=“xs:string”) Identification of the associated person property or personnel class property for a specific segment requirement.

quantity (type=“xs:decimal”) Specifies the amount of the property required for the parent personnel requirement, if applicable. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 102: Attribute type PersonnelRequirementProperty.

RoleClass “EquipmentRequirement” shall be used as specified in Table 103. Instances of this role class shall be realized as child internal elements of a “SegmentRequirement” internal element in an instance hierarchy, specifying “EquipmentRequirement” as a supported role class or role requirement. Its purpose is the specification of the equipment class or equipment that is involved in the given segment requirement. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either equipment class or equipment is specified, but not both [IEC 62264-2].

Class Name EquipmentRequirement

Description Role class used for equipment requirement classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ EquipmentRequirement

Attributes

(optional)

equipmentUse (type=“xs:string”) Defines the expected use of the equipment class or equipment.

quantity (type=“xs:decimal”) Specifies the amount of equipment resources required for the parent segment, if applicable. Applies to each member of the equipment and equipment class sets. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

equipmentLevel (type=“xs:string”) A definition of the level of the associated element of the equipment model.

Table 103: Role class EquipmentRequirement.

AR-MES-ERP 1.1.0 96


Properties for equipment requirements (“EquipmentRequirementProperty”) shall be defined as complex attributes as specified in Table 104. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for equipment requirements.

Host Class AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ EquipmentRequirement

Attributes id (type=“xs:string”) Identification of the associated equipment property or equipment class property for a specific segment requirement.

quantity (type=“xs:decimal”) Specifies the amount of equipment property required for the parent equipment requirement, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 104: Attribute type EquipmentRequirementProperty.

RoleClass “PhysicalAssetRequirement” shall be used as specified in Table 105. Instances of this role class shall be realized as child internal elements of a “SegmentRequirement” internal element in an instance hierarchy, specifying “PhysicalAssetRequirement” as a supported role class or role requirement. Its purpose is the specification of the physical asset class or physical asset that is involved in the given segment requirement. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either physical asset class or physical asset is specified, but not both [IEC 62264-2].

Class Name PhysicalAssetRequirement

Description Role class used for physical asset requirement classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ PhysicalAssetRequirement

Attributes

(optional)

physicalAssetUse (type=“xs:string”) Defines the expected use of the physical asset class or physical asset.

quantity (type=“xs:decimal”) Specifies the amount of physical asset resources required for the parent segment, if applicable. Applies to each member of the physical asset and physical asset class sets. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

equipmentLevel (type=“xs:string”) A level definition for the associated element in the hierarchy of the physical asset model.

Table 105: Role class PhysicalAssetRequirement.

AR-MES-ERP 1.1.0 97


Properties for physical asset requirements (“PhysicalAssetRequirementProperty”) shall be defined as complex attributes as specified in Table 106. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for physical asset requirements.

Host Class AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ PhysicalAssetRequirement

Attributes id (type=“xs:string”) Identification of the associated physical asset property or physical asset class property for a specific segment requirement.

quantity (type=“xs:decimal”) Specifies the amount of physical asset property required for the parent physical asset requirement, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 106: Attribute type PhysicalAssetRequirementProperty.

AR-MES-ERP 1.1.0 98


RoleClass “MaterialRequirement” shall be used as specified in Table 107. Instances of this role class shall be realized as child internal elements of a “SegmentRequirement” internal element in an instance hierarchy, specifying “MaterialRequirement” as a supported role class or role requirement. Its purpose is the specification of the material class, material definition, material lot, or material sublot that is involved in the given segment requirement. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either material class, material definition, material lot, or material sublot is specified [IEC 62264-2].

NOTE: If material lots (or sublots) are merged or absorbed (e.g. blended), then this is a new material lot [IEC 62264-2].

Class Name MaterialRequirement

Description Role class used for material requirement classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ MaterialRequirement

Attributes

(optional)

materialUse (type=“xs:string”) Identifies the use of the material.

storageLocation (type=“xs:string”) Identifies the proposed location of the material, if applicable.

quantity (type=“xs:decimal”) Specifies the amount of material to be used, if applicable. Applies to each member of the material lot, material definition, or material class sets. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.







Table 107: Role class MaterialRequirement.

AR-MES-ERP 1.1.0 99


Properties for material requirements (“MaterialRequirementProperty”) shall be defined as complex attributes as specified in Table 108. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for material requirements.

Host Class AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ MaterialRequirement

Attributes id (type=“xs:string”) Identification of a property of the associated material definition property or material class property for a specific segment requirement.

quantity (type=“xs:decimal”) Specifies the amount of material to be produced, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 108: Attribute type MaterialRequirementProperty.

AR-MES-ERP 1.1.0 100


RoleClass “RequestedSegmentResponse” shall be used as specified in Table 109. Instances of this role class shall be realized as child internal elements of an “OperationsRequest” internal element in an instance hierarchy, specifying “RequestedSegmentResponse” as a supported role class or role requirement. Requested segment responses may hold a child internal element (typically a mirror element) of type “ProcessSegment” specifying the corresponding process segment. The same concept applies to associated elements of type “OperationsDefinition”.



Class Name RequestedSegmentResponse

Description Role class used for requested segment response classes.



AutomationMLIEC62264RoleClassLib/OperationsScheduleModel/ RequestedSegmentResponse

Attributes

(optional)

id (type=“xs:string”) Uniquely identifies the instance of a process segment executed.


“Mixed” shall be used when the operations response contains several categories of segment responses.

actualStartTime (type=“xs:dateTime”) The actual start time of this segment response.

actualEndTime (type=“xs:dateTime”) The actual end time of this segment response.

segmentState (type=“xs:string”)

Table 109: Role class RequestedSegmentResponse.

5.3.9 Operations Performance

RoleClass “OperationsPerformanceModel” shall be used as specified in Table 110. It is the base structuring role class for all operations performance roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of OperationsPerformanceModel shall be used as a starting point for AML models.

Class Name OperationsPerformanceModel

Description Abstract role class used for structuring operations performance roles.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel

Attributes None

Table 110: Role class OperationsPerformanceModel.



RoleClass “OperationsPerformance” shall be used as specified in Table 111. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “OperationsPerformance” as a supported role class or role requirement. An element of type “OperationsPerformance” may define a child internal element of type “OperationsSchedule” (typically as mirror object) in orer to relate the associated operations schedule. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.


Class Name OperationsPerformance

Description Role class used for operations performance classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ OperationsPerformance

Attributes

(optional)

id (type=“xs:string”) Uniquely identifies the operations performance and could include version and revision identification.


“Mixed” shall be used when the operations performance contains several categories of operations responses and/or segment responses.

startTime (type=“xs:dateTime”) The starting time for the associated operations performance, if applicable.

endTime (type=“xs:dateTime”) The ending time for the associated operations performance, if applicable.

performanceState (type=“xs:string”) Indicates the state of the operations performance. One of (nominal scaled constraint) “Ready”, “Completed”, “Aborted”, or “Holding”.

publishedDate (type=“xs:dateTime”) The date and time on which the operations performance was published or generated.

Table 111: Role class OperationsPerformance.



RoleClass “OperationsResponse” shall be used as specified in Table 112. Instances of this role class shall be realized as child internal elements of an “OperationsPerformance” internal element in an instance hierarchy, specifying “OperationsResponse” as a supported role class or role requirement. An operations response typically holds child elements of type “SegmentResponse”. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

A related operations request or operations definition is specified through internal linking, by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


Class Name OperationsResponse

Description Role class used for operations response classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ OperationsResponse

Attributes

(optional)

id (type=“xs:string”) Uniquely identifies the operations response.



startTime (type=“xs:dateTime”) The starting time of this operations response.

endTime (type=“xs:dateTime”) The ending time of this operations response.

responseState (type=“xs:string”) Indicates the state of the operations response. One of (nominal scaled constraint) “Ready”, “Completed”, “Aborted”, or “Holding”.

Table 112: Role class OperationsResponse.



RoleClass “SegmentResponse” shall be used as specified in Table 113. Instances of this role class shall be realized as child internal elements of an “OperationsResponse” internal element in an instance hierarchy, specifying “SegmentResponse” as a supported role class or role requirement. Nested segment responses can be modeled directly as child internal elements or they can be defined as child internal element in terms of a mirror object. The “description” property is to be instantiated as a “Description” header-attribute of the internal element.

A related segment requirement, operations segment or process segment is specified through internal linking, by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: The same process segment can be referenced multiple times in a segment response [IEC 62264-2].

Class Name SegmentResponse

Description Role class used for segment response classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ SegmentResponse

Attributes

(optional)

id (type=“xs:string”) Uniquely identifies the instance of a process segment executed.



actualStartTime (type=“xs:dateTime”) The actual start time of this segment response.

actualEndTime (type=“xs:dateTime”) The actual end time of this segment response.

segmentState (type=“xs:string”) Indicates the state of the segment response. One of (nominal scaled constraint) “Ready”, “Completed”, “Aborted”, or “Holding”.

Table 113: Role class SegmentResponse.



Data for segment responses (“SegmentData”) shall be defined as complex attributes as specified in Table 114. The top-level attribute holds the description, the value and its unit of measure, if applicable. A sub-attribute holds the IEC 62264 ID of the data.

Description Data specification for segment responses.

Host Class AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ SegmentResponse

Attributes

(optional)

id (type=“xs:string”) Identification of the segment data.

Table 114: Attribute type SegmentData.

RoleClass “PersonnelActual” shall be used as specified in Table 114. Instances of this role class shall be realized as child internal elements of a “SegmentResponse” internal element in an instance hierarchy, specifying “PersonnelActual” as a supported role class or role requirement. Its purpose is the specification of the personnel class or person that is involved in the given segment response. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either personnel class or person is specified, but not both [IEC 62264-2].

Class Name PersonnelActual

Description Role class used for personnel actual classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/PersonnelActual

Attributes

(optional)

personnelUse (type=“xs:string”) Defines the actual use of the personnel class or person.

quantity (type=“xs:decimal”) Specifies the amount of personnel resources used in the parent segment, if applicable. Applies to each member of the person or personnel class sets. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 115: Role class PersonnelActual.



Properties for personnel actuals (“PersonnelActualProperty”) shall be defined as complex attributes as specified in Table 116. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for personnel actuals.

Host Class AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/PersonnelActual

Attributes id (type=“xs:string”) Identification of the associated person property or personnel class property for a specific segment response.

quantity (type=“xs:decimal”) Specifies the amount of personnel resources used in the parent segment, if applicable. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 116: Attribute type PersonnelActualProperty.

RoleClass “EquipmentActual” shall be used as specified in Table 117. Instances of this role class shall be realized as child internal elements of a “SegmentResponse” internal element in an instance hierarchy, specifying “EquipmentActual” as a supported role class or role requirement. Its purpose is the specification of the equipment class or equipment that is involved in the given segment response. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either equipment class or equipment is specified, but not both [IEC 62264-2].

Class Name EquipmentActual

Description Role class used for equipment actual classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ EquipmentActual

Attributes

(optional)

equipmentUse (type=“xs:string”) Defines the actual use of the equipment class or equipment.

quantity (type=“xs:decimal”) Specifies the amount of equipment resources used in the parent segment, if applicable. Applies to each member of the equipment or equipment class sets. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 117: Role class EquipmentActual.



Properties for equipment actuals (“EquipmentActualProperty”) shall be defined as complex attributes as specified in Table 118. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for equipment actuals.

Host Class AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ EquipmentActual

Attributes id (type=“xs:string”) Identification of the associated equipment property or equipment class property for a specific segment response.

quantity (type=“xs:decimal”) Specifies the amount of equipment resources used in the parent segment, if applicable. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 118: Attribute type EquipmentActualProperty.

RoleClass “PhysicalAssetActual” shall be used as specified in Table 119. Instances of this role class shall be realized as child internal elements of a “SegmentResponse” internal element in an instance hierarchy, specifying “PhysicalAssetActual” as a supported role class or role requirement. Its purpose is the specification of the physical asset class or physical asset that is involved in the given segment response. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either physical asset class or physical asset is specified, but not both [IEC 62264-2].

Class Name PhysicalAssetActual

Description Role class used for physical asset actual classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ PhysicalAssetActual

Attributes

(optional)

physicalAssetUse (type=“xs:string”) Defines the actual use of the physical asset class or physical asset. Example for maintenance: Repaired, Removed, Replacement, Calibrated, Modified/Improved.

quantity (type=“xs:decimal”) Specifies the amount of physical asset resources used in the parent segment, if applicable. Applies to each member of the physical asset or physical asset class sets. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 119: Role class PhysicalAssetActual.



Properties for physical asset actuals (“PhysicalAssetActualProperty”) shall be defined as complex attributes as specified in Table 120. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for physical asset actuals.

Host Class AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/ PhysicalAssetActual

Attributes id (type=“xs:string”) Identification of the associated physical asset property or physical asset class property for a specific segment response.

quantity (type=“xs:decimal”) Specifies the amount of physical asset resources used in the parent segment, if applicable. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 120: Attribute type PhysicalAssetActualProperty.

RoleClass “MaterialActual” shall be used as specified in Table 121. Instances of this role class shall be realized as child internal elements of a “SegmentResponse” internal element in an instance hierarchy, specifying “MaterialActual” as a supported role class or role requirement. Its purpose is the specification of the material class, material definition, material lot, or material sublot that is involved in the given segment response. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.


NOTE: Typically, either a material class, material definition, material lot, or material sublot is specified [IEC 62264-2].



Class Name MaterialActual

Description Role class used for material actual classes.



AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/MaterialActual

Attributes

(optional)

materialUse (type=“xs:string”) Defines the actual use of the material. One of (nominal scaled constraint) “Consumable”, “Consumed”, “Produced”, “Replaced Asset”, “Replacement Asset”, “Sample”, “Returned Sample”, “Carrier”, “Returned Carrier”.

Defined values for production operations: Consumable, Consumed, Produced.

Defined values for maintenance operations: Consumable, Replaced Asset, Replacement Asset.

Defined values for quality operations: Consumable, Sample, Returned Sample.

Defined values for inventory operations: Consumable, Carrier, Returned Carrier.

storageLocation (type=“xs:string”) Identifies the actual location of the produced material, if applicable.

quantity (type=“xs:decimal”) Specifies the amount of material produced by the parent segment. Applies to each member of the material lot, material definition, or material class sets. The unit of measure of the quantity, is to be spec. as the “Unit” attribute, if applicable.


Physical: components of the assembly are physically connected or in the same area.

Logical: components of the assembly are not necessarily physically connected or in the same area.




Table 121: Role class MaterialActual.



Properties for material actuals (“MaterialActualProperty”) shall be defined as complex attributes as specified in Table 122. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for material actuals.

Host Class AutomationMLIEC62264RoleClassLib/OperationsPerformanceModel/MaterialActual

Attributes id (type=“xs:string”) Identification of the associated material definition property or material class property for a specific segment response.

quantity (type=“xs:decimal”) Specifies the amount of material produced by the parent segment. Applies to each member of the material lot, material definition, or material class sets. The unit of measure of the quantity, is to be specified as the “Unit” attribute, if applicable.

Table 122: Attribute type MaterialActualProperty.

5.3.10 Operations Capability

RoleClass “OperationsCapabilityModel” shall be used as specified in Table 123. It is the base structuring role class for all operations capability roles. In the context of IEC 62264, one of the concrete child roles (or any user defined sub role thereof) of OperationsCapabilityModel shall be used as a starting point for AML models.

Class Name OperationsCapabilityModel

Description Abstract role class used for structuring operations capability roles.



AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel

Attributes None

Table 123: Role class OperationsCapabilityModel.



RoleClass “OperationsCapability” shall be used as specified in Table 124. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “OperationsCapability” as a supported role class or role requirement. Besides the entities specified below, also entities of type “ProcessSegmentCapability” might be added to an operations capability by means of a child internal element (be it explicitly modeled or a mirror object). The “description” property is to be instantiated as a “Description” header-attribute of the internal element.


Class Name OperationsCapability

Description Role class used for operations capability classes.



AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ OperationsCapability

Attributes

(optional)

id (type=“xs:string”) Defines a unique instance of an operations capability for a specified element of the equipment hierarchy model (enterprise, site, area, work center, or work unit).

capacityType (type=“xs:string”) The capacity type. One of (nominal scaled constraint) “Used”, “Unused”, “Total”, “Available”, “Unattainable”, or “Committed”.

reason (type=“xs:string”) Defines the reason for the capability type.

confidenceFactor (type=“xs:string”) A measure of the confidence of the capacity value.

startTime (type=“xs:dateTime”) The starting date and time of the operations capability.

endTime (type=“xs:dateTime”) The ending date and time of the operations capability.

publishedDate (type=“xs:dateTime”) The date and time on which the operations capability was published or generated.

Table 124: Role class OperationsCapability.



RoleClass “PersonnelCapability” shall be used as specified in Table 125. Instances of this role class shall be realized as child internal elements of an “OperationsCapability” or a “ProcessSegmentCapability” internal element in an instance hierarchy, specifying “PersonnelCapability” as a supported role class or role requirement. Its purpose is the specification of the personnel class or person that is involved in the given operations capability or process segment capability. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.



Class Name PersonnelCapability

Description Role class used for personnel capability classes.



AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ PersonnelCapability

Attributes

(optional)

capabilityType (type=“xs:string”) The capability type. One of (nominal scaled constraint) “Used”, “Unused”, “Total”, “Available”, “Unattainable”, or “Committed”.



personnelUse (type=“xs:string”) Defines the expected capability use of the personnel class or person.

startTime (type=“xs:dateTime”) The starting time associated with the personnel capability.

endTime (type=“xs:dateTime”) The ending time associated with the personnel capability.

quantity (type=“xs:decimal”) Specifies the quantity of the personnel capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 125: Role class PersonnelCapability.



Properties for personnel capabilities (“PersonnelCapabilityProperty”) shall be defined as complex attributes as specified in Table 126. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for personnel capabilities.

Host Class AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ PersonnelCapability

Attributes id (type=“xs:string”) Identification of the associated person property or personnel class property.

quantity (type=“xs:decimal”) Specifies the quantity of the personnel capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 126: Attribute type PersonnelCapabilityProperty.



RoleClass “EquipmentCapability” shall be used as specified in Table 127. Instances of this role class shall be realized as child internal elements of an “OperationsCapability” or a “ProcessSegmentCapability” internal element in an instance hierarchy, specifying “EquipmentCapability” as a supported role class or role requirement. Its purpose is the specification of the equipment class or equipment that is involved in the given operations capability or process segment capability. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.



Class Name EquipmentCapability

Description Role class used for equipment capability classes.



AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ EquipmentCapability

Attributes

(optional)




equipmentUse (type=“xs:string”) Defines the expected capability use of the equipment class or equipment.

startTime (type=“xs:dateTime”) The starting time associated with the equipment capability.

endTime (type=“xs:dateTime”) The ending time associated with the equipment capability.

quantity (type=“xs:decimal”) Specifies the quantity of the equipment capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 127: Role class EquipmentCapability.



Properties for equipment capabilities (“EquipmentCapabilityProperty”) shall be defined as complex attributes as specified in Table 128. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for equipment capabilities.

Host Class AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ EquipmentCapability

Attributes id (type=“xs:string”) Identification of the associated equipment property or equipment class property.

quantity (type=“xs:decimal”) Specifies the quantity of the equipment capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 128: Attribute type EquipmentCapabilityProperty.



RoleClass “PhysicalAssetCapability” shall be used as specified in Table 129. Instances of this role class shall be realized as child internal elements of an “OperationsCapability” or a “ProcessSegmentCapability” internal element in an instance hierarchy, specifying “PhysicalAssetCapability” as a supported role class or role requirement. Its purpose is the specification of the physical asset class or physical asset that is involved in the given operations capability or process segment capability. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.



Class Name PhysicalAssetCapability

Description Role class used for physical asset capability classes.



AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ PhysicalAssetCapability

Attributes

(optional)




physicalAssetUse (type=“xs:string”) Defines the expected capability use of the physical asset class or physical asset.

startTime (type=“xs:dateTime”) The starting time associated with the physical asset capability.

endTime (type=“xs:dateTime”) The ending time associated with the physical asset capability.

quantity (type=“xs:decimal”) Specifies the quantity of the physical asset capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 129: Role class PhysicalAssetCapability.



Properties for physical asset capabilities (“PhysicalAssetCapabilityProperty”) shall be defined as complex attributes as specified in Table 130. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for physical asset capabilities.

Host Class AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/ PhysicalAssetCapability

Attributes id (type=“xs:string”) Identification of the associated physical asset property or physical asset class property.

quantity (type=“xs:decimal”) Specifies the quantity of the physical asset capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 130: Attribute type PhysicalAssetCapabilityProperty.

RoleClass “MaterialCapability” shall be used as specified in Table 131. Instances of this role class shall be realized as child internal elements of an “OperationsCapability” or a “ProcessSegmentCapability” internal element in an instance hierarchy, specifying “MaterialCapability” as a supported role class or role requirement. Its purpose is the specification of the material class, material definition, material lot, or material sublot that is involved in the given operations capability or process segment capability. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.





Class Name MaterialCapability

Description Role class used for material capability classes.



AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/MaterialCapability

Attributes

(optional)




materialUse (type=“xs:string”) Defines the expected capability use of the material.

startTime (type=“xs:dateTime”) The starting time associated with the material capability.

endTime (type=“xs:dateTime”) The ending time associated with the material capability.

quantity (type=“xs:decimal”) Specifies the quantity of the material capability defined, if applicable. The unit of measure of the material quantity, is to be specified as the “Unit” attribute, if applicable.







Table 131: Role class MaterialCapability.



Properties for material capabilities (“MaterialCapabilityProperty”) shall be defined as complex attributes as specified in Table 132. The top-level attribute holds the description, the value and its unit of measure, if applicable. One sub-attribute holds the IEC 62264 ID of the property, while another one (“quantity”) holds the amount of resources required and its unit of measure, if applicable.

Description Property specification for material capabilities.

Host Class AutomationMLIEC62264RoleClassLib/OperationsCapabilityModel/MaterialCapability

Attributes id (type=“xs:string”) Identification of the associated material property or equipment class property.

quantity (type=“xs:decimal”) Specifies the quantity of the material capability defined, if applicable. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.

Table 132: Attribute type MaterialCapabilityProperty.



5.3.11 Process Segment Capability

RoleClass “ProcessSegmentCapability” shall be used as specified in Table 133. Instances of this role class shall be realized as internal elements in an instance hierarchy, specifying “ProcessSegmentCapability” as a supported role class or role requirement. Its purpose is the specification of the process segment that is involved in the given operations capability or process segment capability. This is realized by adding an instance of interface class “ResourceConnector” (cf. Clause 5.1) to this entity (in form of an external interface) as well as to the resource it is linked to. If a “ResourceConnector” is already existing, it can be reused.



NOTE: Process segment capabilities should be used carefully because of possible double counts of resources [IEC 62264-2].

Class Name ProcessSegmentCapability

Description Role class used for process segment capability classes.



AutomationMLIEC62264RoleClassLib/ProcessSegmentCapability

Attributes

(optional)

id (type=“xs:string”) Defines a unique instance of a process segment capability for a specified element of the equipment hierarchy model (enterprise, site, area, work center, or work unit).

capacityType (type=“xs:string”) The capacity type. One of (nominal scaled constraint) “Available”, “Unattainable”, or “Committed”.

reason (type=“xs:string”) Gives the reason for the capacity type.

startTime (type=“xs:dateTime”) The starting time of the time span defining the capacity type.

endTime (type=“xs:dateTime”) The ending time of the time span defining the capacity type.

Table 133: Role class ProcessSegmentCapability.



6 Referencing B2MML Files

Regarding referencing B2MML files, the following provisions apply:

An AML object that references a B2MML document shall hold a child internal element (resembling the document) that references role class “B2mmlData” as defined in Clause 5.2.

A reference from this “document object” to a B2MML file shall be modelled by means of a CAEX external interface of interface class “ExternalDataReference” as described in Clause 4.1.2.

The B2MML file shall be referenced by its URI within the attribute “refURI” of this external interface. If no fragment part is defined in the URI, then the root element is implicitly referenced.

The B2MML file shall be referenced with a specific MIME type defined in the “MIMEtype” attribute of this external interface. The MIME type shall be “application/x.b2mml+xml”, in conformance with [RFC 6838].

Referencing elements within a B2MML file shall be modeled by applying the global ID of the respective element to the fragment part of the URI, separated by a hash (#). It is to be noted that B2MML does not support the common XML notation of an “id” attribute, but instead uses an “ID” element of type “normalizedString” as a child of the element to be referenced.

Referencing multiple B2MML files from a single AML object is allowed and shall be modeled by using multiple “document objects” as child internal elements.

If a B2MML document is to be referenced from a role class entity, then a singleton instance of this role class shall be instantiated as an internal element, that in turn holds a “document object”, as described before. The unit of measure of the associated quantity, is to be specified as the “Unit” attribute, if applicable.



7 Relation to OPC Unified Architecture

OPC Unified Architecture (UA) is an industry standard brought forward by the OPC Foundation; it defines a modern, object- and service-oriented communication stack and modeling paradigm for industrial automation [IEC 62541-1]. Its versatility allows the mapping of various domain-specific models into OPC UA equivalent information models, such as AutomationML and IEC 62264 models.

The definitions in this recommendation are (through OPC UA) closely related to two other specifications: (i) the alignment of IEC 62264 with OPC UA [OPC-IEC62264] and (ii) the alignment of AutomationML with OPC UA [DIN 16592-12]. The relations are visualized in Figure 21 and resemble transformation rules for the

conversion of information from one metamodel into information of another metamodel: (i) function describes

how to transform AutomationML models into the OPC UA space, (ii) function describes the transformation

from IEC 62264 to OPC UA, and (iii) function provides a transformation from IEC 62264 to AutomationML. It

would be benefitial for a number of stakeholders if the provision would hold, i.e., IEC 62264 models

that are mapped directly into the OPC UA space via function have an identical representation there as if they

would be first be transformed into AutomationML (via ) and only then be mapped into the OPC UA space

(via ).

Figure 21: Composition of transformation/alignment functions: ≠ .

The two already defined transformation specifications (“IEC 62264 to OPC UA” [OPC-IEC62264] and “AutomationML to OPC UA” [DIN 16592-12]) each define a basic OPC UA information model that provides the base structures for domain specific information models (depicted in Figure 22 and Figure 23). Therefore, an internal element that implements the role class “PhysicalAsset”, as defined in this specification, would be instantiated as an OPC UA object with a type definition pointing to a subtype of the OPC UA object type “CAEXObjectType”. A physical asset instance of IEC 62264 would be instantiated as an OPC UA object with a type definition pointing to the OPC UA object type “PhysicalAssetType”.

Figure 22: Excerpt of the basic information model for AutomationML-based models (cf. [DIN 16592-12]).

Figure 23: Excerpt of the basic information model for IEC 62264-based models (cf. [OPC-IEC62264]).

Since an OPC UA object is allowed only one type definition, it is not possible to provide a fully compatible mapping from IEC 62264 to AutomationML. However, it is possible (and has been realized in this



recommendation) to map IEC 62264 elements to AutomationML elements in a way that the corresponding metamodel elements of OPC UA conform to each other. This has been achieved for all main concepts, except for resource test results (e.g., QualificationTestResult and EquipmentCapabilityTestResult): in [OPC-IEC62264], these entities are istances of OPC UA variable types (and thus correspond to attributes), while in this specification they are instances of type internal element and not realized as attributes. This decision has been taken in order to keep referential integrity within the AML document while relying on standard AML referencing schemes.

In a setting where both the IEC 62264 model and the AutomationML model are injected into an OPC UA server, these two model co-exist in parallel. To clarify and make explicit that two distinct OPC UA nodes describe an identical asset [DIN 16592-12] provides the reference type “HasAMLUAReference”. References of this reference type point from an AutomationML node to a corresponding IEC 62264 node (cf. Figure 24). Currently, this is realized by following the external data reference, as specified in Clause 6, i.e., it is only supported in an environment where an external B2MML file is referenced.

Figure 24: Referencing corresponding elelements from IEC 62264 and AutomationML in OPC UA.

In order to overcome this issue and provide a semantically similar solution to AutomationML, models that have been modeled without references to B2MML documents, the following approach is provided: internal elements and system unit classes that have been modeled with the definitions provided in this recommendation can be matched with IEC 62264 elements via their “ID” attribute. After transforming the IEC 62264 aware AutomationML model into an OPC UA information model, a second processing step could search the IEC 62264 based OPC UA space (if there is one) for elements whose ID matches that of an AutomationML based element. In that case, a reference of type “HasAMLIEC62264UAReference” shall be created, pointing from the AutomationML element to the IEC 62264 element.

Reference type “HasAMLIEC62264UAReference” is defined as a subtype of “HasAMLUAReference” and represented in the OPC UA address space as specified in Table 134.

Attributes Value

BrowseName HasAMLIEC62264UAReference

InverseName IsAMLIEC62264ReferenceOf

Symmetric False

IsAbstract False

References NodeClass BrowseName Comment

Subtype of HasAMLUAReference ReferenceType, defined in [DIN 16592-12].

Table 134: HasAMLIEC62264UAReference ReferenceType.

The SourceNode of this ReferenceType is an OPC UA Node of type Object, ObjectType, or Variable which is part of a transformed AML model and that represents an element of IEC 62264.

The TargetNode of this ReferenceType is an OPC UA Node of any type that represents a corresponding element of IEC 62264, such as one created by applying the transformation rules defined in [OPC-IEC62264].



8 Notes regarding the Examples in the Appendices

For the sake of better comprehendability, in the code listings in Appendix D and Appendix E, the UUIDs of AML elements have been replaced by human readable or otherwise shortened strings (e.g., the value of a corresponding “name” attribute, if applicable). Furthermore, in all appendices some often-used CAEX path definitions are substituted by shorter strings, as depicted in Table 135.

Original Substitution

AutomationMLInterfaceClassLib/AutomationMLBaseInterface/PPRConnector PPRConnector

AutomationMLBaseRoleClassLib/AutomationMLBaseRole BR

AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Process Process

AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Product Product

AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Resource Resource

AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Structure/ ProcessStructure

ProcessStructure

AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Structure/ ProductStructure

ProductStructure

AutomationMLBaseRoleClassLib/AutomationMLBaseRole/Structure/ ResourceStructure

ResourceStructure

AutomationMLExtendedRoleClassLib/Site Site

AutomationMLExtendedRoleClassLib/Area Area

AutomationMLExtendedRoleClassLib/ProductionLine ProductionLine

AutomationMLExtendedRoleClassLib/WorkCell WorkCell

AutomationMLBPRInterfaceClassLib/ExternalDataReference EDR

AutomationMLIEC62264RoleClassLib/EquipmentModel/EquipmentClass EquipmentClass

AutomationMLIEC62264RoleClassLib/EquipmentModel/Equipment Equipment

AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAssetClass PhysicalAssetClass

AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset PhysicalAsset

AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialClass MaterialClass

AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialDefinition MaterialDefinition

AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ ProcessSegmentDependency

ProcessSegmentDependency

AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ProcessSegment ProcessSegment

AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/ EquipmentSegmentSpecification

EquipmentSegmentSpecification

AutomationMLIEC62264RoleClassLib/ProcessSegmentModel/MaterialSegmentSpecification

MaterialSegmentSpecification

AutomationMLIEC62264InterfaceClassLib/ResourceConnector RC

AutomationMLIEC62264InterfaceClassLib/EquipmentAssetConnector EAC

AutomationMLIEC62264InterfaceClassLib/DependencyConnector DC

AutomationMLB2MMLRoleClassLib/B2mmlData B2mmlData

Table 135: Substitutions in use in Listings 2, 4, 6, 8, and 13.



References....

[IEC 62264-1] IEC, Enterprise-control system integration – Part 1: Models and terminology, International Electrotechnical Commission (IEC), Standard, Rev. ISO/IEC 62264-1:2013, May 2013.

[IEC 62264-2] IEC, Enterprise-control system integration – Part 2: Objects and attributes for enterprise-control system integration, International Electrotechnical Commission (IEC), Standard, Rev. ISO/IEC 62264-2:2013, June 2013.

[IEC 62714-1] IEC, Engineering data exchange format for use in industrial automation systems engineering – Automation markup language – Part 1: Architecture and general requirements, International Electrotechnical Commission (IEC), Standard, Rev. ISO/IEC 62714-1:2014, June 2014.

[IEC 62714-2] IEC, Engineering data exchange format for use in industrial automation systems engineering – Automation markup language – Part 2: Role class libraries, International Electrotechnical Commission (IEC), Standard, Rev. ISO/IEC 62714-2:2015, March 2015.

[AML-B-EDR] AutomationML Consortium, AutomationML Best Practice Recommendation – External Data Reference, July 2016.

[RFC 6838] N. Freed, J. Klensin, and T. Hansen, Media Type Specifications and Registration Procedures, Internet Engineering Task Force (IETF) Best Current Practice, January 2013.

[IEC 62541-1] IEC, OPC Unified Architecture – Part 1: Overview and Concepts, International Electrotechnical Commission (IEC), Standard, Rev. IEC 62541-1:2010, February 2010.

[DIN 16592-12] DIN, Combining OPC Unified Architecture and Automation Markup Language, DIN Standard, DIN 16592:2016-12, December 2016.

[OPC-IEC62264] OPC Foundation, OPC Unified Architecture for ISA-95 Common Object Model, Companion Specification, Rev. 1.00, October 2013.



Appendix A AutomationMLIEC62264InterfaceClassLib

Listing 1 depicts the complete source code of the AutomationMLIEC62264InterfaceClassLib. Conceptually, the AutomationMLIEC62264InterfaceClassLib works in conjunction with the AutomationMLIEC62264RoleClassLib.

Listing 1: AutomationML IEC 62264 interface class library.

1 <InterfaceClassLib Name="AutomationMLIEC62264InterfaceClassLib">

2 <Description>IEC 62264 Interface Class Library</Description>

3 <Version>1.0.0</Version>

4 <InterfaceClass Name="HierarchyScopeConnector"

5 RefBaseClassPath="AutomationMLInterfaceClassLib/AutomationMLBaseInterface">

6 <Description>

7 HierarchyScopeConnector shall be used in order to reference hierarchy scope

8 elements from other entities such as e.g., process segments.

9 </Description>

10 </InterfaceClass>

11 <InterfaceClass Name="ResourceConnector"


13 <Description>

14 ResourceConnector shall be used in order to reference basic or complex

15 resources from complex entities such as, e.g., a person or personnel

16 class from a personnel segment requirement of a process segment.

17 </Description>


19 <InterfaceClass Name="EquipmentAssetConnector"


21 <Description>

22 EquipmentAssetConnector shall be used in order to link equipment and

23 physical assets to equipment asset mappings.

24 </Description>


26 <InterfaceClass Name="DependencyConnector"


28 <Description>

29 DependencyConnector shall be used in order to link process and operations

30 segments to process and operations segment dependencies, respectively.

31 </Description>


33 <InterfaceClass Name="TestConnector"


35 <Description>

36 TestConnector shall be used in order to link resources and resource types to

37 test specifications and test results.

38 </Description>


40 </InterfaceClassLib>



Appendix B AutomationMLIEC62264RoleClassLib

Listing 2 depicts the complete source code of the AutomationMLIEC62264RoleClassLib. Conceptually, the AutomationMLIEC62264RoleClassLib can be used without using references to external B2MML documents and thus it is independent of, but interoperable with, the AutomationMLB2MMLRoleClassLib.

Listing 2: AutomationML IEC 62264 role class library.

1 <RoleClassLib Name="AutomationMLIEC62264RoleClassLib">

2 <Description>IEC 62264 Role Class Library</Description>


4 <RoleClass Name="HierarchyScope" RefBaseClassPath="BR">

5 <Attribute Name="equipmentElementLevel" AttributeDataType="xs:string">

6 <Description>

7 Identification of the equipment level if the equipment element is

8 defined.

9 </Description>

10 </Attribute>

11 </RoleClass>

12 <RoleClass Name="PersonnelModel" RefBaseClassPath="BR">

13 <Description>

14 Abstract role class used for structuring personnel roles.

15 </Description>

16 <RoleClass Name="PersonnelClass" RefBaseClassPath="Resource">

17 <Description>Role class used for personnel classes.</Description>

18 <Attribute Name="id" AttributeDataType="xs:string">

19 <Description>

20 Unique identification of a specific personnel class. These are not

21 necessarily job titles, but identify classes that are

22 referenced in other parts of the model.

23 </Description>

24 </Attribute>

25 </RoleClass>

26 <RoleClass Name="Person" RefBaseClassPath="Resource">

27 <Description>Role class used for persons.</Description>


29 <Description>

30 A unique identification of a specific person, within the scope of

31 the information exchanged (e.g. production capability,

32 production schedule, and production performance).

33 </Description>

34 </Attribute>

35 <Attribute Name="name" AttributeDataType="xs:string">

36 <Description>The name of the individual.</Description>

37 </Attribute>

38 </RoleClass>

39 <RoleClass Name="QualificationTestSpecification" RefBaseClassPath="BR">

40 <Description>

41 Role class used for qualification test specifications.

42 </Description>


44 <Description>

45 An identification of a test for certifying one or more values for

46 one or more person properties.

47 </Description>

48 </Attribute>

49 <Attribute Name="version" AttributeDataType="xs:string">

50 <Description>

51 An identification of the version of the qualification test

52 specification.

53 </Description>

54 </Attribute>

55 </RoleClass>

56 <RoleClass Name="QualificationTestResult" RefBaseClassPath="BR">

57 <Description>Role class used for qualification test results.</Description>



58 </RoleClass>

59 </RoleClass>

60 <RoleClass Name="EquipmentModel" RefBaseClassPath="BR">

61 <Description>

62 Abstract role class used for structuring equipment roles.

63 </Description>

64 <RoleClass Name="EquipmentClass" RefBaseClassPath="Resource">

65 <Description>Role class used for equipment classes.</Description>


67 <Description>

68 A unique identification of a specific equipment class, within the

69 scope of the information exchanged (e.g. production

70 capability, production schedule, production performance).

71 </Description>

72 </Attribute>

73 <Attribute Name="equipmentLevel" AttributeDataType="xs:string">

74 <Description>An identification of the level in the role based equipment

75 hierarchy. One of (nominal scaled constraint): "Enterprise",

76 "Site", "Area", "Work Center", "Process Cell", "Production Unit",

77 "Production Line", "Storage Zone", "Work Unit", "Unit", "Work

78 Cell", "Storage Unit".</Description>

79 <Constraint Name="equipmentLevel">

80 <NominalScaledType>

81 <RequiredValue>Enterprise</RequiredValue>

82 <RequiredValue>Site</RequiredValue>

83 <RequiredValue>Area</RequiredValue>

84 <RequiredValue>Work Center</RequiredValue>

85 <RequiredValue>Process Cell</RequiredValue>

86 <RequiredValue>Production Unit</RequiredValue>

87 <RequiredValue>Production Line</RequiredValue>

88 <RequiredValue>Storage Zone</RequiredValue>

89 <RequiredValue>Work Unit</RequiredValue>

90 <RequiredValue>Unit</RequiredValue>

91 <RequiredValue>Work Cell</RequiredValue>

92 <RequiredValue>Storage Unit</RequiredValue>

93 </NominalScaledType>

94 </Constraint>

95 </Attribute>

96 </RoleClass>

97 <RoleClass Name="Equipment" RefBaseClassPath="Resource">

98 <Description>Role class used for equipment.</Description>


100 <Description> 101 A unique identification of a specific piece of equipment, within the 102 scope of the information exchanged (manufacturing operations 103 definition, scheduling, capability and performance). 104 </Description> 105 </Attribute> 106 <Attribute Name="equipmentLevel" AttributeDataType="xs:string"> 107 <Description>An identification of the level in the role based equipment 108 hierarchy. One of (nominal scaled constraint): "Enterprise", 109 "Site", "Area", "Work Center", "Process Cell", "Production Unit", 110 "Production Line", "Storage Zone", "Work Unit", "Unit", "Work 111 Cell", "Storage Unit".</Description> 112 <Constraint Name="equipmentLevel"> 113 <NominalScaledType> 114 <RequiredValue>Enterprise</RequiredValue> 115 <RequiredValue>Site</RequiredValue> 116 <RequiredValue>Area</RequiredValue> 117 <RequiredValue>Work Center</RequiredValue> 118 <RequiredValue>Process Cell</RequiredValue> 119 <RequiredValue>Production Unit</RequiredValue> 120 <RequiredValue>Production Line</RequiredValue> 121 <RequiredValue>Storage Zone</RequiredValue> 122 <RequiredValue>Work Unit</RequiredValue> 123 <RequiredValue>Unit</RequiredValue>



124 <RequiredValue>Work Cell</RequiredValue> 125 <RequiredValue>Storage Unit</RequiredValue> 126 </NominalScaledType> 127 </Constraint> 128 </Attribute> 129 </RoleClass> 130 <RoleClass Name="EquipmentCapabilityTestSpecification" RefBaseClassPath="BR"> 131 <Description> 132 Role class used for equipment capability test specifications. 133 </Description> 134 <Attribute Name="id" AttributeDataType="xs:string"> 135 <Description> 136 An identification of a test for certifying one or more values for 137 one or more equipment properties. 138 </Description> 139 </Attribute> 140 <Attribute Name="version" AttributeDataType="xs:string"> 141 <Description> 142 An identification of the version of the capability test 143 specification. 144 </Description> 145 </Attribute> 146 </RoleClass> 147 <RoleClass Name="EquipmentCapabilityTestResult" RefBaseClassPath="BR"> 148 <Description> 149 Role class used for equipment capability test results. 150 </Description> 151 </RoleClass> 152 </RoleClass> 153 <RoleClass Name="PhysicalAssetModel" RefBaseClassPath="BR"> 154 <Description> 155 Abstract role class for structuring physical asset roles. 156 </Description> 157 <RoleClass Name="PhysicalAssetClass" RefBaseClassPath="Resource"> 158 <Description>Role class used for physical asset classes.</Description> 159 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 160 <Description>An identification of the manufacturer.</Description> 161 </Attribute> 162 <Attribute Name="id" AttributeDataType="xs:string"> 163 <Description>The manufacturer's identification of the specific physical 164 asset class.</Description> 165 </Attribute> 166 </RoleClass> 167 <RoleClass Name="PhysicalAsset" RefBaseClassPath="Resource"> 168 <Description>Role class used for physical assets.</Description> 169 <Attribute Name="id" AttributeDataType="xs:string"> 170 <Description> 171 Defines a unique identification of a physical asset. 172 </Description> 173 </Attribute> 174 <Attribute Name="physicalLocation" AttributeDataType="xs:string"> 175 <Description> 176 Actual physical location of the physical asset. 177 </Description> 178 </Attribute> 179 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 180 <Description> 181 Contains a unique identification for financial tracking as required 182 by laws or regulations. 183 </Description> 184 </Attribute> 185 <Attribute Name="vendorId" AttributeDataType="xs:string"> 186 <Description>Contains a vendor's serial number.</Description> 187 </Attribute> 188 </RoleClass> 189 <RoleClass Name="PhysicalAssetCapabilityTestSpecification"



190 RefBaseClassPath="BR"> 191 <Description> 192 Role class used for physical asset capability test specifications. 193 </Description> 194 <Attribute Name="id" AttributeDataType="xs:string"> 195 <Description> 196 An identification of the specific physical asset capability test 197 specification. 198 </Description> 199 </Attribute> 200 <Attribute Name="version" AttributeDataType="xs:string"> 201 <Description> 202 An identification of the version of the capability test 203 specification. 204 </Description> 205 </Attribute> 206 </RoleClass> 207 <RoleClass Name="PhysicalAssetCapabilityTestResult" RefBaseClassPath="BR"> 208 <Description> 209 Role class used for physical asset capability test results. 210 </Description> 211 </RoleClass> 212 <RoleClass Name="EquipmentAssetMapping" RefBaseClassPath="BR"> 213 <Description> 214 EquipmentAssetMapping shall be used to link physical assets to 215 equipment. 216 </Description> 217 <Attribute Name="id" AttributeDataType="xs:string"> 218 <Description> 219 An identification of the specific equipment asset mapping. 220 </Description> 221 </Attribute> 222 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 223 <Description>The starting time of the association.</Description> 224 </Attribute> 225 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 226 <Description>The ending time of the association.</Description> 227 </Attribute> 228 </RoleClass> 229 </RoleClass> 230 <RoleClass Name="MaterialModel" RefBaseClassPath="BR"> 231 <Description> 232 Abstract role class for structuring material roles. 233 </Description> 234 <RoleClass Name="MaterialClass" RefBaseClassPath="Product"> 235 <Description>Role class used for material classes.</Description> 236 <Attribute Name="id" AttributeDataType="xs:string"> 237 <Description> 238 A unique identification of a specific material class, within the 239 scope of the information exchanged (e.g. production 240 capability, production schedule, production performance) 241 </Description> 242 </Attribute> 243 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 244 <Description>Defines the type of the assembly. One of (nominal scaled 245 constraint) "Physical" or "Logical". Physical: the components of 246 the assembly are physically connected or in the same area. 247 Logical: the components of the assembly are not necessarily 248 physically connected or in the same area.</Description> 249 <Constraint Name="assemblyType"> 250 <NominalScaledType> 251 <RequiredValue>Physical</RequiredValue> 252 <RequiredValue>Logical</RequiredValue> 253 </NominalScaledType> 254 </Constraint> 255 </Attribute>



256 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 257 <Description>Defines the type of the relationships. One of (nominal 258 scaled constraint) "Permanent" or "Transient". Permanent: an 259 assembly that is not intended to be split during the production 260 process. Transient: a temporary assembly used during production, 261 such as a pallet of different materials or a batch 262 kit.</Description> 263 <Constraint Name="assemblyRelationship"> 264 <NominalScaledType> 265 <RequiredValue>Permanent</RequiredValue> 266 <RequiredValue>Transient</RequiredValue> 267 </NominalScaledType> 268 </Constraint> 269 </Attribute> 270 </RoleClass> 271 <RoleClass Name="MaterialDefinition" RefBaseClassPath="Product"> 272 <Description>Role class used for material definitions.</Description> 273 <Attribute Name="id" AttributeDataType="xs:string"> 274 <Description> 275 A unique identification of a specific material definition, within 276 the scope of the information exchanged (e.g. operations 277 capability, operations schedule, operations performance). 278 </Description> 279 </Attribute> 280 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 281 <Description>Defines the type of the assembly. One of (nominal scaled 282 constraint) "Physical" or "Logical". Physical: the components of 283 the assembly are physically connected or in the same area. 284 Logical: the components of the assembly are not necessarily 285 physically connected or in the same area.</Description> 286 <Constraint Name="assemblyType"> 287 <NominalScaledType> 288 <RequiredValue>Physical</RequiredValue> 289 <RequiredValue>Logical</RequiredValue> 290 </NominalScaledType> 291 </Constraint> 292 </Attribute> 293 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 294 <Description>Defines the type of the relationships. One of (nominal 295 scaled constraint) "Permanent" or "Transient". Permanent: an 296 assembly that is not intended to be split during the production 297 process. Transient: a temporary assembly used during production, 298 such as a pallet of different materials or a batch 299 kit.</Description> 300 <Constraint Name="assemblyRelationship"> 301 <NominalScaledType> 302 <RequiredValue>Permanent</RequiredValue> 303 <RequiredValue>Transient</RequiredValue> 304 </NominalScaledType> 305 </Constraint> 306 </Attribute> 307 </RoleClass> 308 <RoleClass Name="MaterialLot" RefBaseClassPath="Product"> 309 <Description>Role class used for material lots.</Description> 310 <Attribute Name="id" AttributeDataType="xs:string"> 311 <Description> 312 A unique identification of a specific material lot, within the scope 313 of the information exchanged (e.g. operations capability, 314 operations schedule, operations performance). 315 </Description> 316 </Attribute> 317 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 318 <Description>Defines the type of the assembly. One of (nominal scaled 319 constraint) "Physical" or "Logical". Physical: the components of 320 the assembly are physically connected or in the same area. 321 Logical: the components of the assembly are not necessarily



322 physically connected or in the same area.</Description> 323 <Constraint Name="assemblyType"> 324 <NominalScaledType> 325 <RequiredValue>Physical</RequiredValue> 326 <RequiredValue>Logical</RequiredValue> 327 </NominalScaledType> 328 </Constraint> 329 </Attribute> 330 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 331 <Description>Defines the type of the relationships. One of (nominal 332 scaled constraint) "Permanent" or "Transient". Permanent: an 333 assembly that is not intended to be split during the production 334 process. Transient: a temporary assembly used during production, 335 such as a pallet of different materials or a batch 336 kit.</Description> 337 <Constraint Name="assemblyRelationship"> 338 <NominalScaledType> 339 <RequiredValue>Permanent</RequiredValue> 340 <RequiredValue>Transient</RequiredValue> 341 </NominalScaledType> 342 </Constraint> 343 </Attribute> 344 <Attribute Name="status" AttributeDataType="xs:string"> 345 <Description>Status of the material lot, e.g. "released", "approved", 346 "blocked", "in process", "in quality check".</Description> 347 </Attribute> 348 <Attribute Name="storageLocation" AttributeDataType="xs:string"> 349 <Description> 350 An identification of the storage location or a physical location of 351 the material lot. 352 </Description> 353 </Attribute> 354 <Attribute Name="quantity" AttributeDataType="xs:string"> 355 <Description>The quantity of the material lot.</Description> 356 </Attribute> 357 </RoleClass> 358 <RoleClass Name="MaterialSublot" RefBaseClassPath="Product"> 359 <Description>Role class used for material sublots.</Description> 360 <Attribute Name="id" AttributeDataType="xs:string"> 361 <Description> 362 A unique identification of a specific material sublot, within the 363 scope of the information exchanged (e.g. production 364 capability, production schedule, production performance). 365 </Description> 366 </Attribute> 367 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 368 <Description>Defines the type of the assembly. One of (nominal scaled 369 constraint) "Physical" or "Logical". Physical: the components of 370 the assembly are physically connected or in the same area. 371 Logical: the components of the assembly are not necessarily 372 physically connected or in the same area.</Description> 373 <Constraint Name="assemblyType"> 374 <NominalScaledType> 375 <RequiredValue>Physical</RequiredValue> 376 <RequiredValue>Logical</RequiredValue> 377 </NominalScaledType> 378 </Constraint> 379 </Attribute> 380 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 381 <Description>Defines the type of the relationships. One of (nominal 382 scaled constraint) "Permanent" or "Transient". Permanent: an 383 assembly that is not intended to be split during the production 384 process. Transient: a temporary assembly used during production, 385 such as a pallet of different materials or a batch 386 kit.</Description> 387 <Constraint Name="assemblyRelationship">



388 <NominalScaledType> 389 <RequiredValue>Permanent</RequiredValue> 390 <RequiredValue>Transient</RequiredValue> 391 </NominalScaledType> 392 </Constraint> 393 </Attribute> 394 <Attribute Name="status" AttributeDataType="xs:string"> 395 <Description>Status of the material sublot, e.g. "released", 396 "approved", "blocked", "in process", "in quality 397 check".</Description> 398 </Attribute> 399 <Attribute Name="storageLocation" AttributeDataType="xs:string"> 400 <Description> 401 An identification of the storage location or a physical location of 402 the material sublot. 403 </Description> 404 </Attribute> 405 <Attribute Name="quantity" AttributeDataType="xs:string"> 406 <Description>The quantity of the material sublot.</Description> 407 </Attribute> 408 </RoleClass> 409 <RoleClass Name="MaterialTestSpecification" RefBaseClassPath="BR"> 410 <Description> 411 Role class used for material test specifications. 412 </Description> 413 <Attribute Name="id" AttributeDataType="xs:string"> 414 <Description> 415 An identification of a test for certifying one or more values for 416 one or more material properties. 417 </Description> 418 </Attribute> 419 <Attribute Name="version" AttributeDataType="xs:string"> 420 <Description> 421 An identification of the version of the maerial test specification. 422 </Description> 423 </Attribute> 424 </RoleClass> 425 <RoleClass Name="MaterialTestResult" RefBaseClassPath="BR"> 426 <Description>Role class used for material test results.</Description> 427 </RoleClass> 428 <RoleClass Name="MaterialAssembly" RefBaseClassPath="BR"> 429 <Description> 430 Role class used for specifying material assemblies. 431 </Description> 432 </RoleClass> 433 </RoleClass> 434 <RoleClass Name="ProcessSegmentModel" RefBaseClassPath="BR"> 435 <Description> 436 Abstract role class for structuring process segment roles. 437 </Description> 438 <RoleClass Name="ProcessSegment" RefBaseClassPath="Process"> 439 <Description>Role class used for process segments.</Description> 440 <Attribute Name="id" AttributeDataType="xs:string"> 441 <Description> 442 A unique identification of a process segment, within the scope of 443 the information exchanged (e.g. operations capability, 444 operations schedule, operations performance). 445 </Description> 446 </Attribute> 447 <Attribute Name="operationsType" AttributeDataType="xs:string"> 448 <Description>Describes the category of the activity. One of (nominal 449 scaled constraint) "Production", "Maintenance", "Quality", 450 "Inventory", or "Mixed". "Mixed" shall be used when the activity 451 contains several categories of process segments.</Description> 452 <Constraint Name="operationsType"> 453 <NominalScaledType>



454 <RequiredValue>Production</RequiredValue> 455 <RequiredValue>Maintenance</RequiredValue> 456 <RequiredValue>Quality</RequiredValue> 457 <RequiredValue>Inventory</RequiredValue> 458 <RequiredValue>Mixed</RequiredValue> 459 </NominalScaledType> 460 </Constraint> 461 </Attribute> 462 <Attribute Name="duration" AttributeDataType="xs:decimal"> 463 <Description>Duration of process segment, if known.</Description> 464 </Attribute> 465 </RoleClass> 466 <RoleClass Name="PersonnelSegmentSpecification" RefBaseClassPath="BR"> 467 <Description> 468 Role class used for personnel segment specifications. 469 </Description> 470 <Attribute Name="personnelUse" AttributeDataType="xs:string"> 471 <Description>Defines the expected use of the personnel class or person, 472 e.g. "Allocated" or "Certified".</Description> 473 </Attribute> 474 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 475 <Description> 476 Specifies the personnel resource required for the parent process 477 segment, if applicable. 478 </Description> 479 </Attribute> 480 </RoleClass> 481 <RoleClass Name="EquipmentSegmentSpecification" RefBaseClassPath="BR"> 482 <Description> 483 Role class used for equipment segment specifications. 484 </Description> 485 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 486 <Description>Defines the expected use of the equipment class or 487 equipment in the context of the process segment, e.g. "Part 488 Milling", "Remove Motor", "Run Test", and "Material 489 Movement".</Description> 490 </Attribute> 491 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 492 <Description> 493 Specifies the amount of resources required, if applicable. 494 </Description> 495 </Attribute> 496 </RoleClass> 497 <RoleClass Name="PhysicalAssetSegmentSpecification" RefBaseClassPath="BR"> 498 <Description> 499 Role class used for physical asset segment specifications. 500 </Description> 501 <Attribute Name="physicalAssetUse" AttributeDataType="xs:string"> 502 <Description> 503 Defines the expected use of the physical asset class or physical 504 asset in the context of the process segment. 505 </Description> 506 </Attribute> 507 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 508 <Description> 509 Specifies the amount of resources required, if applicable. 510 </Description> 511 </Attribute> 512 </RoleClass> 513 <RoleClass Name="MaterialSegmentSpecification" RefBaseClassPath="BR"> 514 <Description> 515 Role class used for material segment specifications. 516 </Description> 517 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 518 <Description>Defines the type of the assembly. One of (nominal scaled 519 constraint) "Physical" or "Logical". Physical: the components of



520 the assembly are physically connected or in the same area. 521 Logical: the components of the assembly are not necessarily 522 physically connected or in the same area.</Description> 523 <Constraint Name="assemblyType"> 524 <NominalScaledType> 525 <RequiredValue>Physical</RequiredValue> 526 <RequiredValue>Logical</RequiredValue> 527 </NominalScaledType> 528 </Constraint> 529 </Attribute> 530 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 531 <Description>Defines the type of the relationships. One of (nominal 532 scaled constraint) "Permanent" or "Transient". Permanent: an 533 assembly that is not intended to be split during the production 534 process. Transient: a temporary assembly used during production, 535 such as a pallet of different materials or a batch 536 kit.</Description> 537 <Constraint Name="assemblyRelationship"> 538 <NominalScaledType> 539 <RequiredValue>Permanent</RequiredValue> 540 <RequiredValue>Transient</RequiredValue> 541 </NominalScaledType> 542 </Constraint> 543 </Attribute> 544 <Attribute Name="materialUse" AttributeDataType="xs:string"> 545 <Description>Defines the material use. One of (nominal scaled 546 constraint): "Consumable", "Material Consumed", and "Material 547 Produced".</Description> 548 <Constraint Name="materialUse"> 549 <NominalScaledType> 550 <RequiredValue>Consumable</RequiredValue> 551 <RequiredValue>Material Consumed</RequiredValue> 552 <RequiredValue>Material Produced</RequiredValue> 553 </NominalScaledType> 554 </Constraint> 555 </Attribute> 556 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 557 <Description>Specifies the amount of resources required.</Description> 558 </Attribute> 559 </RoleClass> 560 <RoleClass Name="ProcessSegmentDependency" RefBaseClassPath="BR"> 561 <Description> 562 Role class used for process segment dependencies. 563 </Description> 564 <Attribute Name="id" AttributeDataType="xs:string"> 565 <Description> 566 The identification of the unique instance of the process segment 567 dependency. 568 </Description> 569 </Attribute> 570 <Attribute Name="dependencyType" AttributeDataType="xs:string"> 571 <Description> 572 Defines the execution dependency constraints of one segment by 573 another segment. 574 </Description> 575 </Attribute> 576 <Attribute Name="dependencyFactor" AttributeDataType="xs:decimal"> 577 <Description>Factor used by dependency.</Description> 578 </Attribute> 579 </RoleClass> 580 </RoleClass> 581 <RoleClass Name="OperationsDefinitionModel" RefBaseClassPath="BR"> 582 <Description> 583 Abstract role class used for structuring operations definition roles. 584 </Description> 585 <RoleClass Name="OperationsDefinition" RefBaseClassPath="ProcessStructure">



586 <Description>Role class used for operations definitions.</Description> 587 <Attribute Name="id" AttributeDataType="xs:string"> 588 <Description> 589 Uniquely identifies the operations definition. 590 </Description> 591 </Attribute> 592 <Attribute Name="version" AttributeDataType="xs:string"> 593 <Description> 594 An identification of the version of the operations definition. 595 </Description> 596 </Attribute> 597 <Attribute Name="operationsType" AttributeDataType="xs:string"> 598 <Description>Describes the category of operation. One of (nominal 599 scaled constraint) "Production", "Maintenance", "Quality", 600 "Inventory", or "Mixed". "Mixed" shall be used when the 601 operations definition contains several types of operations 602 requests and/or segment requirements.</Description> 603 <Constraint Name="operationsType"> 604 <NominalScaledType> 605 <RequiredValue>Production</RequiredValue> 606 <RequiredValue>Maintenance</RequiredValue> 607 <RequiredValue>Quality</RequiredValue> 608 <RequiredValue>Inventory</RequiredValue> 609 <RequiredValue>Mixed</RequiredValue> 610 </NominalScaledType> 611 </Constraint> 612 </Attribute> 613 <Attribute Name="workDefinitionId" AttributeDataType="xs:string"> 614 <Description> 615 Identification of the external work definition associated with this 616 operations definition. 617 </Description> 618 </Attribute> 619 <Attribute Name="billOfResourceId" AttributeDataType="xs:string"> 620 <Description> 621 Identification of the external bill of resources associated with 622 this operations definition. 623 </Description> 624 </Attribute> 625 </RoleClass> 626 <RoleClass Name="OperationsMaterialBill" RefBaseClassPath="BR"> 627 <Description>Role class used for operations material bills.</Description> 628 <Attribute Name="id" AttributeDataType="xs:string"> 629 <Description> 630 Unique identification of a manufacturing bill. 631 </Description> 632 </Attribute> 633 </RoleClass> 634 <RoleClass Name="OperationsMaterialBillItem" RefBaseClassPath="BR"> 635 <Description> 636 Role class used for operations material bill items. 637 </Description> 638 <Attribute Name="id" AttributeDataType="xs:string"> 639 <Description>Unique identification of a bill item.</Description> 640 </Attribute> 641 <Attribute Name="useType" AttributeDataType="xs:string"> 642 <Description>Defines the use of the material. One of (nominal scaled 643 constraint): "Consumed" or "Produced". Consumed: Indicates that 644 bill items are all consumed materials. Produced: Indicates that 645 bill items are all produced materials.</Description> 646 <Constraint Name="useType"> 647 <NominalScaledType> 648 <RequiredValue>Consumed</RequiredValue> 649 <RequiredValue>Produced</RequiredValue> 650 </NominalScaledType> 651 </Constraint>



652 </Attribute> 653 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 654 <Description>Defines the type of the assembly. One of (nominal scaled 655 constraint) "Physical" or "Logical". Physical: the components of 656 the assembly are physically connected or in the same area. 657 Logical: the components of the assembly are not necessarily 658 physically connected or in the same area.</Description> 659 <Constraint Name="assemblyType"> 660 <NominalScaledType> 661 <RequiredValue>Physical</RequiredValue> 662 <RequiredValue>Logical</RequiredValue> 663 </NominalScaledType> 664 </Constraint> 665 </Attribute> 666 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 667 <Description>Defines the type of the relationships. One of (nominal 668 scaled constraint) "Permanent" or "Transient". Permanent: an 669 assembly that is not intended to be split during the production 670 process. Transient: a temporary assembly used during production, 671 such as a pallet of different materials or a batch 672 kit.</Description> 673 <Constraint Name="assemblyRelationship"> 674 <NominalScaledType> 675 <RequiredValue>Permanent</RequiredValue> 676 <RequiredValue>Transient</RequiredValue> 677 </NominalScaledType> 678 </Constraint> 679 </Attribute> 680 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 681 <Description>Specifies the amount of resources required.</Description> 682 </Attribute> 683 </RoleClass> 684 <RoleClass Name="OperationsSegment" RefBaseClassPath="Process"> 685 <Description>Role class used for operations segments.</Description> 686 <Attribute Name="id" AttributeDataType="xs:string"> 687 <Description>Unique identification of a specific segment.</Description> 688 </Attribute> 689 <Attribute Name="descriptions" AttributeDataType="xs:string"> 690 <Description> 691 Contains additional information about the segment. 692 </Description> 693 </Attribute> 694 <Attribute Name="duration" AttributeDataType="xs:string"> 695 <Description>Duration of segment, if known.</Description> 696 </Attribute> 697 <Attribute Name="operationsType" AttributeDataType="xs:string"> 698 <Description>Describes the category of operation. One of (nominal 699 scaled constraint) "Production", "Maintenance", "Quality", 700 "Inventory", or "Mixed". "Mixed" shall be used when the 701 operations segment contains several types of operations requests 702 and/or segment requirements.</Description> 703 <Constraint Name="operationsType"> 704 <NominalScaledType> 705 <RequiredValue>Production</RequiredValue> 706 <RequiredValue>Maintenance</RequiredValue> 707 <RequiredValue>Quality</RequiredValue> 708 <RequiredValue>Inventory</RequiredValue> 709 <RequiredValue>Mixed</RequiredValue> 710 </NominalScaledType> 711 </Constraint> 712 </Attribute> 713 <Attribute Name="workDefinitionId" AttributeDataType="xs:string"> 714 <Description> 715 Identification of the external work definition associated with this 716 operations segment. 717 </Description>



718 </Attribute> 719 </RoleClass> 720 <RoleClass Name="PersonnelSpecification" RefBaseClassPath="BR"> 721 <Description>Role class used for personnel specifications.</Description> 722 <Attribute Name="personnelUse" AttributeDataType="xs:string"> 723 <Description> 724 Defines the expected use of the personnel class or person. 725 </Description> 726 </Attribute> 727 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 728 <Description> 729 Specifies the amount of personnel resources required for the parent 730 segment, if applicable. 731 </Description> 732 </Attribute> 733 </RoleClass> 734 <RoleClass Name="EquipmentSpecification" RefBaseClassPath="BR"> 735 <Description>Role class used for equipment specifications.</Description> 736 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 737 <Description> 738 Defines the expected use of the equipment class or equipment. 739 </Description> 740 </Attribute> 741 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 742 <Description> 743 Specifies the amount of equipment resources required for the parent 744 segment, if applicable. 745 </Description> 746 </Attribute> 747 </RoleClass> 748 <RoleClass Name="PhysicalAssetSpecification" RefBaseClassPath="BR"> 749 <Description> 750 Role class used for physical asset specifications. 751 </Description> 752 <Attribute Name="physicalAssetUse" AttributeDataType="xs:string"> 753 <Description> 754 Defines the expected use of the physical asset class or physical 755 asset. 756 </Description> 757 </Attribute> 758 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 759 <Description> 760 Specifies the amount of physical asset resources required for the 761 parent segment, if applicable. 762 </Description> 763 </Attribute> 764 </RoleClass> 765 <RoleClass Name="MaterialSpecification" RefBaseClassPath="BR"> 766 <Description>Role class used for material specifications.</Description> 767 <Attribute Name="materialUse" AttributeDataType="xs:string"> 768 <Description>Defines the expected material use. One of (nominal scaled 769 constraint) "Material Consumed", "Material Produced", or 770 "Consumable".</Description> 771 <Constraint Name="materialUse"> 772 <NominalScaledType> 773 <RequiredValue>Material Consumed</RequiredValue> 774 <RequiredValue>Material Produced</RequiredValue> 775 <RequiredValue>Consumable</RequiredValue> 776 </NominalScaledType> 777 </Constraint> 778 </Attribute> 779 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 780 <Description> 781 Specifies the amount of material resources required for the parent 782 segment, if applicable. 783 </Description>



784 </Attribute> 785 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 786 <Description>Defines the type of the assembly. One of (nominal scaled 787 constraint) "Physical" or "Logical". Physical: the components of 788 the assembly are physically connected or in the same area. 789 Logical: the components of the assembly are not necessarily 790 physically connected or in the same area.</Description> 791 <Constraint Name="assemblyType"> 792 <NominalScaledType> 793 <RequiredValue>Physical</RequiredValue> 794 <RequiredValue>Logical</RequiredValue> 795 </NominalScaledType> 796 </Constraint> 797 </Attribute> 798 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 799 <Description>Defines the type of the relationships. One of (nominal 800 scaled constraint) "Permanent" or "Transient". Permanent: an 801 assembly that is not intended to be split during the production 802 process. Transient: a temporary assembly used during production, 803 such as a pallet of different materials or a batch 804 kit.</Description> 805 <Constraint Name="assemblyRelationship"> 806 <NominalScaledType> 807 <RequiredValue>Permanent</RequiredValue> 808 <RequiredValue>Transient</RequiredValue> 809 </NominalScaledType> 810 </Constraint> 811 </Attribute> 812 </RoleClass> 813 <RoleClass Name="OperationsSegmentDependency" RefBaseClassPath="BR"> 814 <Description> 815 Role class used for operations segment dependencies. 816 </Description> 817 <Attribute Name="id" AttributeDataType="xs:string"> 818 <Description> 819 Identification of the unique instance of the operations segment 820 dependency. 821 </Description> 822 </Attribute> 823 <Attribute Name="dependencyType" AttributeDataType="xs:string"> 824 <Description> 825 Defines the execution dependency constraints of one segment by 826 another segment. 827 </Description> 828 </Attribute> 829 <Attribute Name="dependencyFactor" AttributeDataType="xs:string"> 830 <Description>Factor used by dependency.</Description> 831 </Attribute> 832 </RoleClass> 833 </RoleClass> 834 <RoleClass Name="OperationsScheduleModel" RefBaseClassPath="BR"> 835 <Description> 836 Abstract role class used for structuring operations schedule roles. 837 </Description> 838 <RoleClass Name="OperationsSchedule" RefBaseClassPath="ProcessStructure"> 839 <Description>Role class used for operations schedules.</Description> 840 <Attribute Name="id" AttributeDataType="xs:string"> 841 <Description> 842 Uniquely identifies the operations schedule and could include 843 version and revision identification. 844 </Description> 845 </Attribute> 846 <Attribute Name="operationsType" AttributeDataType="xs:string"> 847 <Description>Describes the category of operation. One of (nominal 848 scaled constraint) "Production", "Maintenance", "Quality", 849 "Inventory", or "Mixed". "Mixed" shall be used when the



850 operations definition contains several types of operations 851 requests and/or segment requirements.</Description> 852 <Constraint Name="operationsType"> 853 <NominalScaledType> 854 <RequiredValue>Production</RequiredValue> 855 <RequiredValue>Maintenance</RequiredValue> 856 <RequiredValue>Quality</RequiredValue> 857 <RequiredValue>Inventory</RequiredValue> 858 <RequiredValue>Mixed</RequiredValue> 859 </NominalScaledType> 860 </Constraint> 861 </Attribute> 862 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 863 <Description> 864 The starting time for the associated operations schedule, if 865 applicable. 866 </Description> 867 </Attribute> 868 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 869 <Description> 870 The ending time for the associated operations schedule, if 871 applicable. 872 </Description> 873 </Attribute> 874 <Attribute Name="publishedDate" AttributeDataType="xs:dateTime"> 875 <Description> 876 The date and time on which the operations schedule was published or 877 generated. 878 </Description> 879 </Attribute> 880 <Attribute Name="scheduledState" AttributeDataType="xs:string"> 881 <Description>Indicates the state of the operations schedule. One of 882 (nominal scaled constraint) "Forecast" or "Released". Forecast: 883 the requirements have not been released for use. Released: the 884 requirements have been released for use.</Description> 885 <Constraint Name="scheduledState"> 886 <NominalScaledType> 887 <RequiredValue>Forecast</RequiredValue> 888 <RequiredValue>Released</RequiredValue> 889 </NominalScaledType> 890 </Constraint> 891 </Attribute> 892 </RoleClass> 893 <RoleClass Name="OperationsRequest" RefBaseClassPath="ProcessStructure"> 894 <Description>Role class used for operations requests.</Description> 895 <Attribute Name="id" AttributeDataType="xs:string"> 896 <Description> 897 Unique identification of the operations request. 898 </Description> 899 </Attribute> 900 <Attribute Name="operationsType" AttributeDataType="xs:string"> 901 <Description>Describes the category of operations. One of (nominal 902 scaled constraint) "Production", "Maintenance", "Quality", 903 "Inventory", or "Mixed". "Mixed" shall be used when the 904 operations definition contains several types of operations 905 requests and/or segment requirements.</Description> 906 <Constraint Name="operationsType"> 907 <NominalScaledType> 908 <RequiredValue>Production</RequiredValue> 909 <RequiredValue>Maintenance</RequiredValue> 910 <RequiredValue>Quality</RequiredValue> 911 <RequiredValue>Inventory</RequiredValue> 912 <RequiredValue>Mixed</RequiredValue> 913 </NominalScaledType> 914 </Constraint> 915 </Attribute>



916 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 917 <Description> 918 When operation is to be started operations schedule, if applicable. 919 </Description> 920 </Attribute> 921 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 922 <Description> 923 When operation is to be completed, if applicable. 924 </Description> 925 </Attribute> 926 <Attribute Name="priority" AttributeDataType="xs:string"> 927 <Description>The priority of the request, if applicable.</Description> 928 </Attribute> 929 <Attribute Name="scheduledState" AttributeDataType="xs:string"> 930 <Description>Indicates the state of the operations request. One of 931 (nominal scaled constraint) "Forecast" or "Released". Forecast: 932 the requirements have not been released for use. Released: the 933 requirements have been released for use.</Description> 934 <Constraint Name="scheduledState"> 935 <NominalScaledType> 936 <RequiredValue>Forecast</RequiredValue> 937 <RequiredValue>Released</RequiredValue> 938 </NominalScaledType> 939 </Constraint> 940 </Attribute> 941 </RoleClass> 942 <RoleClass Name="SegmentRequirement" RefBaseClassPath="Process"> 943 <Description>Role class used for segment requirements.</Description> 944 <Attribute Name="id" AttributeDataType="xs:string"> 945 <Description> 946 Unique identification of the segment requirement. 947 </Description> 948 </Attribute> 949 <Attribute Name="operationsType" AttributeDataType="xs:string"> 950 <Description>Describes the category of operation. One of (nominal 951 scaled constraint) "Production", "Maintenance", "Quality", 952 "Inventory", or "Mixed". "Mixed" shall be used when the 953 operations definition contains several types of operations 954 requests and/or segment requirements.</Description> 955 <Constraint Name="operationsType"> 956 <NominalScaledType> 957 <RequiredValue>Production</RequiredValue> 958 <RequiredValue>Maintenance</RequiredValue> 959 <RequiredValue>Quality</RequiredValue> 960 <RequiredValue>Inventory</RequiredValue> 961 <RequiredValue>Mixed</RequiredValue> 962 </NominalScaledType> 963 </Constraint> 964 </Attribute> 965 <Attribute Name="earliestStartTime" AttributeDataType="xs:dateTime"> 966 <Description> 967 The expected earliest start time of this segment requirement, if 968 applicable. 969 </Description> 970 </Attribute> 971 <Attribute Name="latestEndTime" AttributeDataType="xs:dateTime"> 972 <Description> 973 The expected latest ending time of this segment requirement, if 974 applicable. 975 </Description> 976 </Attribute> 977 <Attribute Name="duration" AttributeDataType="xs:decimal"> 978 <Description> 979 The expected duration of this segment requirement, if applicable. 980 Note: this should match the associated segment duration. 981 </Description>



982 </Attribute> 983 <Attribute Name="segmentState" AttributeDataType="xs:string"> 984 <Description>Indicates the state of the segment request. One of 985 (nominal scaled constraint) "Forecast" or "Released". Forecast: 986 the requirements have not been released for use. Released: the 987 requirements have been released for use.</Description> 988 <Constraint Name="segmentState"> 989 <NominalScaledType> 990 <RequiredValue>Forecast</RequiredValue> 991 <RequiredValue>Released</RequiredValue> 992 </NominalScaledType> 993 </Constraint> 994 </Attribute> 995 </RoleClass> 996 <RoleClass Name="PersonnelRequirement" RefBaseClassPath="BR"> 997 <Description>Role class used for personnel requirements.</Description> 998 <Attribute Name="personnelUse" AttributeDataType="xs:string"> 999 <Description> 1000 Defines the expected use of the personnel class or person. 1001 </Description> 1002 </Attribute> 1003 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1004 <Description> 1005 Specifies the amount of personnel resources required for the parent 1006 segment, if applicable. Applies to each member of the person 1007 and personnel class sets. 1008 </Description> 1009 </Attribute> 1010 </RoleClass> 1011 <RoleClass Name="EquipmentRequirement" RefBaseClassPath="BR"> 1012 <Description>Role class used for equipment requirements.</Description> 1013 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 1014 <Description> 1015 Defines the expected use of the equipment class or equipment. 1016 </Description> 1017 </Attribute> 1018 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1019 <Description> 1020 Specifies the amount of equipment resources required for the parent 1021 segment, if applicable. Applies to each member of the 1022 equipment and equipment class sets. 1023 </Description> 1024 </Attribute> 1025 <Attribute Name="equipmentLevel" AttributeDataType="xs:string"> 1026 <Description> 1027 A definition of the level of the associated element of the equipment 1028 model. 1029 </Description> 1030 </Attribute> 1031 </RoleClass> 1032 <RoleClass Name="PhysicalAssetRequirement" RefBaseClassPath="BR"> 1033 <Description> 1034 Role class used for physical asset requirements. 1035 </Description> 1036 <Attribute Name="physicalAssetUse" AttributeDataType="xs:string"> 1037 <Description> 1038 Defines the expected use of the physical asset class or physical 1039 asset. 1040 </Description> 1041 </Attribute> 1042 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1043 <Description> 1044 Specifies the amount of physical asset resources required for the 1045 parent segment, if applicable. Applies to each member of the 1046 physical asset and physical asset class sets. 1047 </Description>



1048 </Attribute> 1049 <Attribute Name="equipmentLevel" AttributeDataType="xs:string"> 1050 <Description> 1051 A level definition for the associated element in the hierarchy of 1052 the physical asset model. 1053 </Description> 1054 </Attribute> 1055 </RoleClass> 1056 <RoleClass Name="MaterialRequirement" RefBaseClassPath="BR"> 1057 <Description>Role class used for material requirements.</Description> 1058 <Attribute Name="materialUse" AttributeDataType="xs:string"> 1059 <Description>Identifies the use of the material.</Description> 1060 </Attribute> 1061 <Attribute Name="storageLocation" AttributeDataType="xs:string"> 1062 <Description> 1063 Identifies the proposed location of the material, if applicable. 1064 </Description> 1065 </Attribute> 1066 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1067 <Description> 1068 Specifies the amount of material to be used, if applicable. Applies 1069 to each member of the material lot, material definition, or 1070 material class sets. 1071 </Description> 1072 </Attribute> 1073 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 1074 <Description>Defines the type of the assembly. One of (nominal scaled 1075 constraint) "Physical" or "Logical". Physical: the components of 1076 the assembly are physically connected or in the same area. 1077 Logical: the components of the assembly are not necessarily 1078 physically connected or in the same area.</Description> 1079 <Constraint Name="assemblyType"> 1080 <NominalScaledType> 1081 <RequiredValue>Physical</RequiredValue> 1082 <RequiredValue>Logical</RequiredValue> 1083 </NominalScaledType> 1084 </Constraint> 1085 </Attribute> 1086 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 1087 <Description>Defines the type of the relationships. One of (nominal 1088 scaled constraint) "Permanent" or "Transient". Permanent: an 1089 assembly that is not intended to be split during the production 1090 process. Transient: a temporary assembly used during production, 1091 such as a pallet of different materials or a batch 1092 kit.</Description> 1093 <Constraint Name="assemblyRelationship"> 1094 <NominalScaledType> 1095 <RequiredValue>Permanent</RequiredValue> 1096 <RequiredValue>Transient</RequiredValue> 1097 </NominalScaledType> 1098 </Constraint> 1099 </Attribute> 1100 </RoleClass> 1101 <RoleClass Name="RequestedSegmentResponse" RefBaseClassPath="Process"> 1102 <Description> 1103 Role class used for requested segment responses. 1104 </Description> 1105 <Attribute Name="id" AttributeDataType="xs:string"> 1106 <Description> 1107 Uniquely identifies the instance of a process segment executed. 1108 </Description> 1109 </Attribute> 1110 <Attribute Name="operationsType" AttributeDataType="xs:string"> 1111 <Description>Describes the category of operations. One of (nominal 1112 scaled constraint) "Production", "Maintenance", "Quality", 1113 "Inventory", or "Mixed". "Mixed" shall be used when the



1114 operations response contains several categories of segment 1115 responses.</Description> 1116 <Constraint Name="operationsType"> 1117 <NominalScaledType> 1118 <RequiredValue>Production</RequiredValue> 1119 <RequiredValue>Maintenance</RequiredValue> 1120 <RequiredValue>Quality</RequiredValue> 1121 <RequiredValue>Inventory</RequiredValue> 1122 <RequiredValue>Mixed</RequiredValue> 1123 </NominalScaledType> 1124 </Constraint> 1125 </Attribute> 1126 <Attribute Name="actualStartTime" AttributeDataType="xs:dateTime"> 1127 <Description> 1128 The actual start time of this segment response. 1129 </Description> 1130 </Attribute> 1131 <Attribute Name="actualEndTime" AttributeDataType="xs:dateTime"> 1132 <Description> 1133 The actual end time of this segment response. 1134 </Description> 1135 </Attribute> 1136 <Attribute Name="segmentState" AttributeDataType="xs:string"> 1137 <Description>Indicates the state of the segment response. One of 1138 (nominal scaled constraint) "Ready", "Completed", "Aborted", or 1139 "Holding".</Description> 1140 </Attribute> 1141 </RoleClass> 1142 </RoleClass> 1143 <RoleClass Name="OperationsPerformanceModel" RefBaseClassPath="BR"> 1144 <Description> 1145 Abstract role class used for structuring operations performance roles. 1146 </Description> 1147 <RoleClass Name="OperationsPerformance" RefBaseClassPath="ProcessStructure"> 1148 <Description>Role class used for operations performances.</Description> 1149 <Attribute Name="id" AttributeDataType="xs:string"> 1150 <Description> 1151 Uniquely identifies the operations performance and could include 1152 version and revision identification. 1153 </Description> 1154 </Attribute> 1155 <Attribute Name="operationsType" AttributeDataType="xs:string"> 1156 <Description>Describes the category of operation. One of (nominal 1157 scaled constraint) "Production", "Maintenance", "Quality", 1158 "Inventory", or "Mixed". "Mixed" shall be used when the 1159 operations performance contains several categories of operations 1160 responses and/or segment responses.</Description> 1161 <Constraint Name="operationsType"> 1162 <NominalScaledType> 1163 <RequiredValue>Production</RequiredValue> 1164 <RequiredValue>Maintenance</RequiredValue> 1165 <RequiredValue>Quality</RequiredValue> 1166 <RequiredValue>Inventory</RequiredValue> 1167 <RequiredValue>Mixed</RequiredValue> 1168 </NominalScaledType> 1169 </Constraint> 1170 </Attribute> 1171 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1172 <Description> 1173 The starting time for the associated operations performance, if 1174 applicable. 1175 </Description> 1176 </Attribute> 1177 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1178 <Description> 1179 The ending time for the associated operations performance, if



1180 applicable. 1181 </Description> 1182 </Attribute> 1183 <Attribute Name="performanceState" AttributeDataType="xs:string"> 1184 <Description>Indicates the state of the operations performance. One of 1185 (nominal scaled constraint) "Ready", "Completed", "Aborted", or 1186 "Holding".</Description> 1187 <Constraint Name="performanceState"> 1188 <NominalScaledType> 1189 <RequiredValue>Ready</RequiredValue> 1190 <RequiredValue>Completed</RequiredValue> 1191 <RequiredValue>Aborted</RequiredValue> 1192 <RequiredValue>Holding</RequiredValue> 1193 </NominalScaledType> 1194 </Constraint> 1195 </Attribute> 1196 <Attribute Name="publishedDate" AttributeDataType="xs:dateTime"> 1197 <Description> 1198 The date and time on which the operations performance was published 1199 or generated. 1200 </Description> 1201 </Attribute> 1202 </RoleClass> 1203 <RoleClass Name="OperationsResponse" RefBaseClassPath="ProcessStructure"> 1204 <Description>Role class used for operations responses.</Description> 1205 <Attribute Name="id" AttributeDataType="xs:string"> 1206 <Description>Uniquely identifies the operations response.</Description> 1207 </Attribute> 1208 <Attribute Name="operationsType" AttributeDataType="xs:string"> 1209 <Description>Describes the category of operation. One of (nominal 1210 scaled constraint) "Production", "Maintenance", "Quality", 1211 "Inventory", or "Mixed". "Mixed" shall be used when the 1212 operations response contains several categories of segment 1213 responses.</Description> 1214 <Constraint Name="operationsType"> 1215 <NominalScaledType> 1216 <RequiredValue>Production</RequiredValue> 1217 <RequiredValue>Maintenance</RequiredValue> 1218 <RequiredValue>Quality</RequiredValue> 1219 <RequiredValue>Inventory</RequiredValue> 1220 <RequiredValue>Mixed</RequiredValue> 1221 </NominalScaledType> 1222 </Constraint> 1223 </Attribute> 1224 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1225 <Description> 1226 The starting time of this operations response. 1227 </Description> 1228 </Attribute> 1229 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1230 <Description>The ending time of this operations response.</Description> 1231 </Attribute> 1232 <Attribute Name="responseState" AttributeDataType="xs:string"> 1233 <Description>Indicates the state of the operations response. One of 1234 (nominal scaled constraint) "Ready", "Completed", "Aborted", or 1235 "Holding".</Description> 1236 <Constraint Name="responseState"> 1237 <NominalScaledType> 1238 <RequiredValue>Ready</RequiredValue> 1239 <RequiredValue>Completed</RequiredValue> 1240 <RequiredValue>Aborted</RequiredValue> 1241 <RequiredValue>Holding</RequiredValue> 1242 </NominalScaledType> 1243 </Constraint> 1244 </Attribute> 1245 </RoleClass>



1246 <RoleClass Name="SegmentResponse" RefBaseClassPath="Process"> 1247 <Description>Role class used for segment responses.</Description> 1248 <Attribute Name="id" AttributeDataType="xs:string"> 1249 <Description> 1250 Uniquely identifies the instance of a process segment executed. 1251 </Description> 1252 </Attribute> 1253 <Attribute Name="operationsType" AttributeDataType="xs:string"> 1254 <Description>Describes the category of operations. One of (nominal 1255 scaled constraint) "Production", "Maintenance", "Quality", 1256 "Inventory", or "Mixed". "Mixed" shall be used when the 1257 operations response contains several categories of segment 1258 responses.</Description> 1259 <Constraint Name="operationsType"> 1260 <NominalScaledType> 1261 <RequiredValue>Production</RequiredValue> 1262 <RequiredValue>Maintenance</RequiredValue> 1263 <RequiredValue>Quality</RequiredValue> 1264 <RequiredValue>Inventory</RequiredValue> 1265 <RequiredValue>Mixed</RequiredValue> 1266 </NominalScaledType> 1267 </Constraint> 1268 </Attribute> 1269 <Attribute Name="actualStartTime" AttributeDataType="xs:dateTime"> 1270 <Description> 1271 The actual start time of this segment response. 1272 </Description> 1273 </Attribute> 1274 <Attribute Name="actualEndTime" AttributeDataType="xs:dateTime"> 1275 <Description> 1276 The actual end time of this segment response. 1277 </Description> 1278 </Attribute> 1279 <Attribute Name="segmentState" AttributeDataType="xs:string"> 1280 <Description>Indicates the state of the segment response. One of 1281 (nominal scaled constraint) "Ready", "Completed", "Aborted", or 1282 "Holding".</Description> 1283 <Constraint Name="segmentState"> 1284 <NominalScaledType> 1285 <RequiredValue>Ready</RequiredValue> 1286 <RequiredValue>Completed</RequiredValue> 1287 <RequiredValue>Aborted</RequiredValue> 1288 <RequiredValue>Holding</RequiredValue> 1289 </NominalScaledType> 1290 </Constraint> 1291 </Attribute> 1292 </RoleClass> 1293 <RoleClass Name="PersonnelActual" RefBaseClassPath="BR"> 1294 <Description>Role class used for personnel actual.</Description> 1295 <Attribute Name="personnelUse" AttributeDataType="xs:string"> 1296 <Description> 1297 Defines the actual use of the personnel class or person. 1298 </Description> 1299 </Attribute> 1300 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1301 <Description> 1302 Specifies the amount of personnel resources used in the parent 1303 segment, if applicable. Applies to each member of the person 1304 or personnel class sets. 1305 </Description> 1306 </Attribute> 1307 </RoleClass> 1308 <RoleClass Name="EquipmentActual" RefBaseClassPath="BR"> 1309 <Description>Role class used for equipment actual.</Description> 1310 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 1311 <Description>



1312 Defines the actual use of the equipment class or equipment. 1313 </Description> 1314 </Attribute> 1315 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1316 <Description> 1317 Specifies the amount of equipment resources used in the parent 1318 segment, if applicable. Applies to each member of the 1319 equipment or equipment class sets. 1320 </Description> 1321 </Attribute> 1322 </RoleClass> 1323 <RoleClass Name="PhysicalAssetActual" RefBaseClassPath="BR"> 1324 <Description>Role class used for physical asset actual.</Description> 1325 <Attribute Name="physicalAssetUse" AttributeDataType="xs:string"> 1326 <Description>Defines the actual use of the physical asset class or 1327 physical asset. Example for maintenance: Repaired, Removed, 1328 Replacement, Calibrated, Modified/Improved.</Description> 1329 </Attribute> 1330 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1331 <Description> 1332 Specifies the amount of physical asset resources used in the parent 1333 segment, if applicable. Applies to each member of the physical 1334 asset or physical asset class sets. 1335 </Description> 1336 </Attribute> 1337 </RoleClass> 1338 <RoleClass Name="MaterialActual" RefBaseClassPath="BR"> 1339 <Description>Role class used for material actual.</Description> 1340 <Attribute Name="materialUse" AttributeDataType="xs:string"> 1341 <Description>Defines the actual use of the material. One of (nominal 1342 scaled constraint) "Consumable", "Consumed", "Produced", 1343 "Replaced Asset", "Replacement Asset", "Sample", "Returned 1344 Sample", "Carrier", "Returned Carrier". Defined values for 1345 production operations: Consumable, Consumed, Produced. Defined 1346 values for maintenance operations: Consumable, Replaced Asset, 1347 Replacement Asset. Defined values for quality operations: 1348 Consumable, Sample, Returned Sample. Defined values for inventory 1349 operations: Consumable, Carrier, Returned Carrier.</Description> 1350 <Constraint Name="materialUse"> 1351 <NominalScaledType> 1352 <RequiredValue>Consumable</RequiredValue> 1353 <RequiredValue>Consumed</RequiredValue> 1354 <RequiredValue>Produced</RequiredValue> 1355 <RequiredValue>Replaced Asset</RequiredValue> 1356 <RequiredValue>Sample</RequiredValue> 1357 <RequiredValue>Returned Sample</RequiredValue> 1358 <RequiredValue>Carrier</RequiredValue> 1359 <RequiredValue>Returned Carrier</RequiredValue> 1360 </NominalScaledType> 1361 </Constraint> 1362 </Attribute> 1363 <Attribute Name="storageLocation" AttributeDataType="xs:string"> 1364 <Description> 1365 Identifies the actual location of the produced material, if 1366 applicable. 1367 </Description> 1368 </Attribute> 1369 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1370 <Description> 1371 Specifies the amount of material produced by the parent segment. 1372 Applies to each member of the material lot, material 1373 definition, or material class sets. 1374 </Description> 1375 </Attribute> 1376 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 1377 <Description>Defines the type of the assembly. One of (nominal scaled



1378 constraint) "Physical" or "Logical". Physical: components of the 1379 assembly are physically connected or in the same area. Logical: 1380 components of the assembly are not necessarily physically 1381 connected or in the same area.</Description> 1382 <Constraint Name="assemblyType"> 1383 <NominalScaledType> 1384 <RequiredValue>Physical</RequiredValue> 1385 <RequiredValue>Logical</RequiredValue> 1386 </NominalScaledType> 1387 </Constraint> 1388 </Attribute> 1389 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 1390 <Description>Defines the type of the relationships. One of (nominal 1391 scaled constraint) "Permanent" or "Transient". Permanent: an 1392 assembly that is not intended to be split during the production 1393 process. Transient: a temporary assembly used during production, 1394 such as a pallet of different materials or a batch 1395 kit.</Description> 1396 <Constraint Name="assemblyRelationship"> 1397 <NominalScaledType> 1398 <RequiredValue>Permanent</RequiredValue> 1399 <RequiredValue>Transient</RequiredValue> 1400 </NominalScaledType> 1401 </Constraint> 1402 </Attribute> 1403 </RoleClass> 1404 </RoleClass> 1405 <RoleClass Name="OperationsCapabilityModel" RefBaseClassPath="BR"> 1406 <Description> 1407 Abstract role class used for structuring operations capability roles. 1408 </Description> 1409 <RoleClass Name="OperationsCapability" RefBaseClassPath="Process"> 1410 <Description>Role class used for operations capabilities.</Description> 1411 <Attribute Name="id" AttributeDataType="xs:string"> 1412 <Description> 1413 Defines a unique instance of an operations capability for a 1414 specified element of the equipment hierarchy model 1415 (enterprise, site, area, work center, or work unit). 1416 </Description> 1417 </Attribute> 1418 <Attribute Name="capacityType" AttributeDataType="xs:string"> 1419 <Description>The capacity type. One of (nominal scaled constraint) 1420 "Used", "Unused", "Total", "Available", "Unattainable", or 1421 "Committed".</Description> 1422 <Constraint Name="capacityType"> 1423 <NominalScaledType> 1424 <RequiredValue>Used</RequiredValue> 1425 <RequiredValue>Unused</RequiredValue> 1426 <RequiredValue>Total</RequiredValue> 1427 <RequiredValue>Available</RequiredValue> 1428 <RequiredValue>Unattainable</RequiredValue> 1429 <RequiredValue>Committed</RequiredValue> 1430 </NominalScaledType> 1431 </Constraint> 1432 </Attribute> 1433 <Attribute Name="reason" AttributeDataType="xs:string"> 1434 <Description>Defines the reason for the capability type.</Description> 1435 </Attribute> 1436 <Attribute Name="confidenceFactor" AttributeDataType="xs:string"> 1437 <Description> 1438 A measure of the confidence of the capacity value. 1439 </Description> 1440 </Attribute> 1441 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1442 <Description> 1443 The starting date and time of the operations capability.



1444 </Description> 1445 </Attribute> 1446 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1447 <Description> 1448 The ending date and time of the operations capability. 1449 </Description> 1450 </Attribute> 1451 <Attribute Name="publishedDate" AttributeDataType="xs:dateTime"> 1452 <Description> 1453 The date and time on which the operations capability was published 1454 or generated. 1455 </Description> 1456 </Attribute> 1457 </RoleClass> 1458 <RoleClass Name="PersonnelCapability" RefBaseClassPath="BR"> 1459 <Description>Role class used for personnel capabilities.</Description> 1460 <Attribute Name="capabilityType" AttributeDataType="xs:string"> 1461 <Description>The capability type. One of (nominal scaled constraint) 1462 "Used", "Unused", "Total", "Available", "Unattainable", or 1463 "Committed".</Description> 1464 <Constraint Name="capabilityType"> 1465 <NominalScaledType> 1466 <RequiredValue>Used</RequiredValue> 1467 <RequiredValue>Unused</RequiredValue> 1468 <RequiredValue>Total</RequiredValue> 1469 <RequiredValue>Available</RequiredValue> 1470 <RequiredValue>Unattainable</RequiredValue> 1471 <RequiredValue>Committed</RequiredValue> 1472 </NominalScaledType> 1473 </Constraint> 1474 </Attribute> 1475 <Attribute Name="reason" AttributeDataType="xs:string"> 1476 <Description>Defines the reason for the capability type.</Description> 1477 </Attribute> 1478 <Attribute Name="confidenceFactor" AttributeDataType="xs:string"> 1479 <Description> 1480 A measure of the confidence of the capacity value. 1481 </Description> 1482 </Attribute> 1483 <Attribute Name="personnelUse" AttributeDataType="xs:string"> 1484 <Description> 1485 Defines the expected capability use of the personnel class or 1486 person. 1487 </Description> 1488 </Attribute> 1489 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1490 <Description> 1491 The starting time associated with the personnel capability. 1492 </Description> 1493 </Attribute> 1494 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1495 <Description> 1496 The ending time associated with the personnel capability. 1497 </Description> 1498 </Attribute> 1499 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1500 <Description> 1501 Specifies the quantity of the personnel capability defined, if 1502 applicable. 1503 </Description> 1504 </Attribute> 1505 </RoleClass> 1506 <RoleClass Name="EquipmentCapability" RefBaseClassPath="BR"> 1507 <Description>Role class used for equipment capabilities.</Description> 1508 <Attribute Name="capabilityType" AttributeDataType="xs:string"> 1509 <Description>The capability type. One of (nominal scaled constraint)



1510 "Used", "Unused", "Total", "Available", "Unattainable", or 1511 "Committed".</Description> 1512 <Constraint Name="capabilityType"> 1513 <NominalScaledType> 1514 <RequiredValue>Used</RequiredValue> 1515 <RequiredValue>Unused</RequiredValue> 1516 <RequiredValue>Total</RequiredValue> 1517 <RequiredValue>Available</RequiredValue> 1518 <RequiredValue>Unattainable</RequiredValue> 1519 <RequiredValue>Committed</RequiredValue> 1520 </NominalScaledType> 1521 </Constraint> 1522 </Attribute> 1523 <Attribute Name="reason" AttributeDataType="xs:string"> 1524 <Description>Defines the reason for the capability type.</Description> 1525 </Attribute> 1526 <Attribute Name="confidenceFactor" AttributeDataType="xs:string"> 1527 <Description> 1528 A measure of the confidence of the capacity value. 1529 </Description> 1530 </Attribute> 1531 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 1532 <Description> 1533 Defines the expected capability use of the equipment class or 1534 equipment. 1535 </Description> 1536 </Attribute> 1537 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1538 <Description> 1539 The starting time associated with the equipment capability. 1540 </Description> 1541 </Attribute> 1542 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1543 <Description> 1544 The ending time associated with the equipment capability. 1545 </Description> 1546 </Attribute> 1547 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1548 <Description> 1549 Specifies the quantity of the equipment capability defined, if 1550 applicable. 1551 </Description> 1552 </Attribute> 1553 </RoleClass> 1554 <RoleClass Name="PhysicalAssetCapability" RefBaseClassPath="BR"> 1555 <Description> 1556 Role class used for physical asset capabilities. 1557 </Description> 1558 <Attribute Name="capabilityType" AttributeDataType="xs:string"> 1559 <Description>The capability type. One of (nominal scaled constraint) 1560 "Used", "Unused", "Total", "Available", "Unattainable", or 1561 "Committed".</Description> 1562 <Constraint Name="capabilityType"> 1563 <NominalScaledType> 1564 <RequiredValue>Used</RequiredValue> 1565 <RequiredValue>Unused</RequiredValue> 1566 <RequiredValue>Total</RequiredValue> 1567 <RequiredValue>Available</RequiredValue> 1568 <RequiredValue>Unattainable</RequiredValue> 1569 <RequiredValue>Committed</RequiredValue> 1570 </NominalScaledType> 1571 </Constraint> 1572 </Attribute> 1573 <Attribute Name="reason" AttributeDataType="xs:string"> 1574 <Description>Defines the reason for the capability type.</Description> 1575 </Attribute>



1576 <Attribute Name="confidenceFactor" AttributeDataType="xs:string"> 1577 <Description> 1578 A measure of the confidence of the capacity value. 1579 </Description> 1580 </Attribute> 1581 <Attribute Name="physicalAssetUse" AttributeDataType="xs:string"> 1582 <Description> 1583 Defines the expected capability use of the physical asset class or 1584 physical asset. 1585 </Description> 1586 </Attribute> 1587 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1588 <Description> 1589 The starting time associated with the physical asset capability. 1590 </Description> 1591 </Attribute> 1592 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1593 <Description> 1594 The ending time associated with the physical asset capability. 1595 </Description> 1596 </Attribute> 1597 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1598 <Description> 1599 Specifies the quantity of the physical asset capability defined, if 1600 applicable. 1601 </Description> 1602 </Attribute> 1603 </RoleClass> 1604 <RoleClass Name="MaterialCapability" RefBaseClassPath="BR"> 1605 <Description>Role class used for material capabilities.</Description> 1606 <Attribute Name="capabilityType" AttributeDataType="xs:string"> 1607 <Description>The capability type. One of (nominal scaled constraint) 1608 "Used", "Unused", "Total", "Available", "Unattainable", or 1609 "Committed".</Description> 1610 <Constraint Name="capabilityType"> 1611 <NominalScaledType> 1612 <RequiredValue>Used</RequiredValue> 1613 <RequiredValue>Unused</RequiredValue> 1614 <RequiredValue>Total</RequiredValue> 1615 <RequiredValue>Available</RequiredValue> 1616 <RequiredValue>Unattainable</RequiredValue> 1617 <RequiredValue>Committed</RequiredValue> 1618 </NominalScaledType> 1619 </Constraint> 1620 </Attribute> 1621 <Attribute Name="reason" AttributeDataType="xs:string"> 1622 <Description>Defines the reason for the capability type.</Description> 1623 </Attribute> 1624 <Attribute Name="confidenceFactor" AttributeDataType="xs:string"> 1625 <Description> 1626 A measure of the confidence of the capacity value. 1627 </Description> 1628 </Attribute> 1629 <Attribute Name="materialUse" AttributeDataType="xs:string"> 1630 <Description> 1631 Defines the expected capability use of the material. 1632 </Description> 1633 </Attribute> 1634 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1635 <Description> 1636 The starting time associated with the material capability. 1637 </Description> 1638 </Attribute> 1639 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 1640 <Description> 1641 The ending time associated with the material capability.



1642 </Description> 1643 </Attribute> 1644 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 1645 <Description> 1646 Specifies the quantity of the material capability defined, if 1647 applicable. 1648 </Description> 1649 </Attribute> 1650 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 1651 <Description>Defines the type of the assembly. One of (nominal scaled 1652 constraint) "Physical" or "Logical". Physical: the components of 1653 the assembly are physically connected or in the same area. 1654 Logical: the components of the assembly are not necessarily 1655 physically connected or in the same area.</Description> 1656 <Constraint Name="assemblyType"> 1657 <NominalScaledType> 1658 <RequiredValue>Physical</RequiredValue> 1659 <RequiredValue>Logical</RequiredValue> 1660 </NominalScaledType> 1661 </Constraint> 1662 </Attribute> 1663 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 1664 <Description>Defines the type of the relationships. One of (nominal 1665 scaled constraint) "Permanent" or "Transient". Permanent: an 1666 assembly that is not intended to be split during the production 1667 process. Transient: a temporary assembly used during production, 1668 such as a pallet of different materials or a batch 1669 kit.</Description> 1670 <Constraint Name="assemblyRelationship"> 1671 <NominalScaledType> 1672 <RequiredValue>Permanent</RequiredValue> 1673 <RequiredValue>Transient</RequiredValue> 1674 </NominalScaledType> 1675 </Constraint> 1676 </Attribute> 1677 </RoleClass> 1678 </RoleClass> 1679 <RoleClass Name="ProcessSegmentCapability" RefBaseClassPath="Process"> 1680 <Description>Role class used for process segment capabilities.</Description> 1681 <Attribute Name="id" AttributeDataType="xs:string"> 1682 <Description> 1683 Defines a unique instance of a process segment capability for a 1684 specified element of the equipment hierarchy model (enterprise, 1685 site, area, work center, or work unit). 1686 </Description> 1687 </Attribute> 1688 <Attribute Name="capacityType" AttributeDataType="xs:string"> 1689 <Description>The capacity type. One of (nominal scaled constraint) 1690 "Available", "Unattainable", or "Committed".</Description> 1691 <Constraint Name="capacityType"> 1692 <NominalScaledType> 1693 <RequiredValue>Available</RequiredValue> 1694 <RequiredValue>Unattainable</RequiredValue> 1695 <RequiredValue>Committed</RequiredValue> 1696 </NominalScaledType> 1697 </Constraint> 1698 </Attribute> 1699 <Attribute Name="reason" AttributeDataType="xs:string"> 1700 <Description>Gives the reason for the capacity type.</Description> 1701 </Attribute> 1702 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 1703 <Description> 1704 The starting time of the time span defining the capacity type. 1705 </Description> 1706 </Attribute> 1707 <Attribute Name="endTime" AttributeDataType="xs:dateTime">



1708 <Description> 1709 The ending time of the time span defining the capacity type. 1710 </Description> 1711 </Attribute> 1712 </RoleClass> 1713 </RoleClassLib>



Appendix C AutomationMLB2MMLRoleClassLib

Listing 3 depicts the complete source code of the AutomationMLB2MMLRoleClassLib.

Listing 3: AutomationML B2MML role class library.

1 <RoleClassLib Name="AutomationMLB2MMLRoleClassLib">

2 <Description>B2MML Role Class Library</Description>


4 <RoleClass Name="B2mmlData"

5 RefBaseClassPath="AutomationMLBPRRoleClassLib/ExternalData">

6 <Description>

7 B2mmlData shall be used in order to reference external B2MML documents,

8 using the mechanism defined in BPR External Data Reference.

9 </Description>

10 </RoleClass>

11 </RoleClassLib>



Appendix D Examples for Referencing External B2MML Documents

Clauses D.1 and D.2 exemplify the two distinct ways of referencing B2MML data from AML, while Clause D.2 depicts a more complex example taken from IEC 62714-1.

D.1 Referencing a B2MML Document from AML

In this example, an internal element inside an AML document references an element from B2MML by specifying the complete document as the reference target. Listing 4 shows the relevant excerpt (the instance hierarchy) of the AML document that contains an internal element “Turntable”. A child internal element is added to this turntable, representing a B2MML document. By applying an external interface of type ExternalDataReference it references the B2MML document “Turntable.b2mml” through the refURI attribute. As the given URI does not contain a fragment part, the root element of the B2MML document is implicitly referenced – in this example an equiment with the ID “Turntable” (cf. Listing 5).

Listing 4: InstanceHierarchy excerpt of document Example-01-B2MML-Document.aml.

1 <InstanceHierarchy Name="B2mmlDocument">

2 <Description>

3 Example for referencing an IEC 62264 element represented by a B2MML document.

4 </Description>


6 <InternalElement Name="Turntable" ID="Turntable">

7 <InternalElement Name="TurntableB2mmlDocument" ID="TurntableB2mmlDocument">

8 <ExternalInterface Name="B2mml" ID="B2mml" RefBaseClassPath="EDR">

9 <Attribute Name="MIMEType" AttributeDataType="xs:string">

10 <Value>application/x.b2mml+xml</Value>

11 </Attribute>

12 <Attribute Name="refURI" AttributeDataType="xs:anyURI">

13 <Value>./Turntable.b2mml</Value>

14 </Attribute>

15 </ExternalInterface>

16 <RoleRequirements RefBaseRoleClassPath="B2mmlData" />

17 </InternalElement>

18 <SupportedRoleClass RefRoleClassPath="WorkCell" />

19 <RoleRequirements RefBaseRoleClassPath="Equipment" />


21 </InstanceHierarchy>

NOTE: By omitting the fragment part of the URI, the root element of the given document is referenced.

NOTE: Turntable specifies role class “Equipment” – the referenced B2MML element must be of type “Equipment” as well.

NOTE: As the internal element specifies role class “Equipment”, it must also specify the equipment level by assigning one of the corresponding role classes of the extended role class hierarchy, in this case “WorkCell” is chosen.

Listing 5 depicts a B2MML document that contains only one element of type equipment identified by the term “Turntable”, exhibiting the minimum set of B2MML attributes: ID, Description, and EquipmentLevel.

Listing 5: Contents of document Turntable.b2mml.

1 <Equipment xmlns="http://www.mesa.org/xml/B2MML-V0600">

2 <ID>Turntable</ID>

3 <Description>

4 Turns products towards distinct work cells for further production.

5 </Description>

6 <EquipmentLevel>

7 <EquipmentElementLevel>WorkCell</EquipmentElementLevel>

8 </EquipmentLevel>

9 </Equipment>



D.2 Referencing a Specific Element within a B2MML Document from AML

In this example, a specific element of a more complex B2MML document is referenced from an AML document with a very simple instance hierarchy containing an internal element named “Turntable”. A child internal element within this “Turntable” element resembles a B2MML document, as clarified with the role class B2mmlData. It specifies an ExternalDataReference referencing the element with ID “Turntable” from the B2MML document “Equipment.b2mml”, by declaring “./Equipment.b2mml#Turntable” as refURI (cf. Listing 6). The fragment part “Turntable” is the unique ID of an element within the equipment catalog given in Listing 7.

Listing 6: InstanceHierarchy excerpt of document Example-02-B2MML-Element.aml.

1 <InstanceHierarchy Name="B2mmlElement">

2 <Description>

3 Example for referencing an IEC 62264 element that is one of many elements

4 within a B2MML document.

5 </Description>



8 <InternalElement Name="TurntableB2mmlDocument" ID="TurntableB2mmlDocument">

9 <ExternalInterface Name="B2mml" ID="B2mml" RefBaseClassPath="EDR">



12 </Attribute>


14 <Value>./Equipment.b2mml#Turntable</Value>

15 </Attribute>


17 <RoleRequirements RefBaseRoleClassPath="B2mmlData" />





22 </InstanceHierarchy>

NOTE: By providing a fragment part in the URI, the corresponding (sub) element of the given document is referenced.



Listing 7 depicts a slightly more complex B2MML document “Equipment.b2mml” that contains a sequence of equipment elements within an equipment information root element. Each of the equipment elements provides a unique ID, a Description, and an EquipmentLevel sub element. The string content of the ID sub element is used to reference a specific equipment element.

Listing 7: Contents of document Equipment.b2mml.

1 <EquipmentInformation xmlns="http://www.mesa.org/xml/B2MML-V0600">

2 <Equipment>

3 <ID>Conveyer</ID>

4 <Description>Delivers products from one work cell to another.</Description>

5 <EquipmentLevel>


7 </EquipmentLevel>

8 </Equipment>

9 <Equipment>


11 <Description>

12 Turns products towards distinct work cells for further production.

13 </Description>

14 <EquipmentLevel>


16 </EquipmentLevel>

17 </Equipment>

18 <Equipment>

19 <ID>Robot</ID>

20 <Description>Assembles products from intermediate products.</Description>

21 <EquipmentLevel>



24 </Equipment>

25 </EquipmentInformation>



D.3 Process-Product-Resource (PPR)

The following instance builds upon the example given in Clause A.2.6 of IEC 62714-1. The setup is explained in Table 136 and in Figures 25 and 26. The AutomationML document is presented in Listing 8. The relevant B2MML documents are depicted in Listings 9 to 12, resembling respectively Equipment, Physical Assets, Material, and Process Segments.

Product

Wheel A wheel that is to be attached to a car.

Car-without-Wheels A car that has no wheels attached.

Car-with-Wheels A car with wheels attached.

Resource

Conveyer-1 Delivers cars without wheels from the product source to the turntable.

Conveyer-2 Delivers cars without wheels from the turntable to the product drain for finished products.

Turntable Turns cars without wheels either towards the product drain for unfinished products or towards Conveyor-2.

Robot Assembles wheels to cars without wheels.

Process

Transport-1 Transport-1 is accomplished with Conveyer-1. Cars without wheels are delivered from the product source to the turntable.

Transport-2 Transport-2 is accomplished with Conveyer-2. Cars without wheels are delivered from the turntable to the robot.

Transport-3 Transport-3 is accomplished with Conveyer-2. Cars with wheels are delivered from the robot to the product drain for finished products.

Turn Turning is accomplished by the turntable that might hold a Car-without-Wheels. Cars without wheels that should be assembled are turned towards Conveyer-2, the ones that should not be further processed are turned towards the product drain for unfinished products.

Assemble Assembling is accomplished by the robot, which attaches Wheels to Cars-without-Wheels in order to transform them into Cars-with-Wheels.

Table 136: Setup of the PPR example (from IEC 62714-1).

Figure 25 resembles a shop floor setup, showing the flow of products (material) through the resources. Processes are represented as arrows and indicate the direction of material flow. In Figures 25 and 26 dark gray trapezoid elements depict resources, and light gray stadiums depict products (in Figure 26, additionally, white rectangles depict processes). In Figure 25 white trapezoids resemble resources that are not regarded in detail in this scenario.

Figure 25: Visualization of the PPR example (from IEC 62714-1).

Figure 26 depicts the complete set of internal links defined for the given scenario. Solid lines connect processes to resources, dotted lines connect processes to products, and dashed lines connect resources to products.



Figure 26: Internal links of the PPR example (from IEC 62714-1).

Listing 8 resembles (i) the InstanceHierarchy, (ii) the RoleClassLib (for material and equipment classes), and (iii) the SystemUnitClassLib (for the material definitions) excerpt of the AutomationML document for the PPR example. It references various elements from different B2MML documents, e.g. the InternalElement with the ID “ID-Conveyer-1” (line 9) references an IEC 62264 equipment encoded in B2MML through an ExternalInterface of type ExternalDataReference (line 13). In lines 17-19, the attribute “refURI” refers to “./PPR-Equipment.b2mml#Conveyer-1”, which resolves to the file “PPR-Equipment.b2mml” and the element with ID “Conveyer-1” (cf. Listing 9). In addition, since the equipment in question is of equipment level “WorkCell”, in line 24 the corresponding role class “AutomationMLExtendedRoleClassLib/WorkCell” is specified for the InternalElement. The conveyer “Conveyer-1” itself is marked as implementing role class “Equipment” of the AutomationMLIEC62264RoleClassLib. Also, it refers to its equipment class through a supported role class in lines 25-26

Listing 8: InstanceHierarchy, RoleClassLib, and SystemUnitClassLib excerpts of document Example-03-B2MML-PPR.aml.

1 <InstanceHierarchy Name="B2MML-PPR-IH">

2 <Description>

3 Example for referencing multiple IEC 62264 elements that reside in multiple

4 B2MML documents that hold multiple B2MML elements. Additionally, AML

5 objects are aligned with PPR roles.

6 </Description>


8 <InternalElement Name="Equipment" ID="Equipment">

9 <InternalElement Name="Conveyer-1" ID="Conveyer-1">

10 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-11" />

11 <InternalElement Name="Conveyer-1-B2MML-Document"

12 ID="Conveyer-1-B2MML-Document">

13 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-11">



16 </Attribute>


18 <Value>./PPR-Equipment.b2mml#Conveyer-1</Value>

19 </Attribute>


21 <RoleRequirements

22 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" />





25 <SupportedRoleClass

26 RefRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Conveyer-Class" />

27 <InternalLink Name="C1_CWOW" RefPartnerSideA="Conveyer-1:PPR"

28 RefPartnerSideB="Car-without-Wheels-Instance:PPR" />





33 <InternalElement Name="Turntable-B2MML-Document"

34 ID="Turntable-B2MML-Document">




38 </Attribute>


40 <Value>./PPR-Equipment.b2mml#Turntable</Value>

41 </Attribute>







48 RefRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Turntable-Class" />

49 <InternalLink Name="TT_CWOW" RefPartnerSideA="Turntable:PPR"






55 <InternalElement Name="Conveyer-2-B2MML-Document"

56 ID="Conveyer-2-B2MML-Document">




60 </Attribute>


62 <Value>./PPR-Equipment.b2mml#Conveyer-2</Value>

63 </Attribute>







70 RefRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Conveyer-Class" />

71 <InternalLink Name="C2_CWOW" RefPartnerSideA="Conveyer-2:PPR"


73 <InternalLink Name="C2_CWW" RefPartnerSideA="Conveyer-2:PPR"

74 RefPartnerSideB="Car-with-Wheel-Instance:PPR" />



77 <InternalElement Name="Robot" ID="Robot">


79 <InternalElement Name="Robot-B2MML-Document" ID="Robot-B2MML-Document">




83 </Attribute>


85 <Value>./PPR-Equipment.b2mml#Robot</Value>

86 </Attribute>









93 RefRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Robot-Class" />

94 <InternalLink Name="R_CWOW" RefPartnerSideA="Robot:PPR"


96 <InternalLink Name="R_W" RefPartnerSideA="Robot:PPR"

97 RefPartnerSideB="Wheel-Instance:PPR" />

98 <InternalLink Name="R_CWW" RefPartnerSideA="Robot:PPR"

99 RefPartnerSideB="Car-with-Wheel-Instance:PPR" />

100 <RoleRequirements RefBaseRoleClassPath="Equipment" /> 101 </InternalElement> 102 <RoleRequirements RefBaseRoleClassPath="ResourceStructure" /> 103 </InternalElement> 104 <InternalElement Name="EquipmentClasses" ID="EquipmentClasses"> 105 <Description>IH representations of "Equipment Class" role 106 classes.</Description> 107 <InternalElement Name="Conveyer-Class" ID="Conveyer-Class"> 108 <InternalElement Name="Conveyer-Class-Document" 109 ID="Conveyer-Class-Document"> 110 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-20"> 111 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 112 <Value>application/x.b2mml+xml</Value> 113 </Attribute> 114 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 115 <Value>./PPR-Equipment.b2mml#Conveyer-Class</Value> 116 </Attribute> 117 </ExternalInterface> 118 <RoleRequirements 119 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 120 </InternalElement> 121 <RoleRequirements 122 RefBaseRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Conveyer-Class" 123 /> 124 </InternalElement> 125 <InternalElement Name="Turntable-Class" ID="Turntable-Class"> 126 <InternalElement Name="Turntable-Class-Document" 127 ID="Turntable-Class-Document"> 128 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-21"> 129 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 130 <Value>application/x.b2mml+xml</Value> 131 </Attribute> 132 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 133 <Value>./PPR-Equipment.b2mml#Turntable-Class</Value> 134 </Attribute> 135 </ExternalInterface> 136 <RoleRequirements 137 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 138 </InternalElement> 139 <RoleRequirements 140 RefBaseRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Turntable-Class" 141 /> 142 </InternalElement> 143 <InternalElement Name="Robot-Class" ID="Robot-Class"> 144 <InternalElement Name="Robot-Class-Document" ID="Robot-Class-Document"> 145 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-22"> 146 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 147 <Value>application/x.b2mml+xml</Value> 148 </Attribute> 149 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 150 <Value>./PPR-Equipment.b2mml#Robot-Class</Value> 151 </Attribute> 152 </ExternalInterface> 153 <RoleRequirements 154 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 155 </InternalElement> 156 <RoleRequirements



157 RefBaseRoleClassPath="B2MML-PPR-RCL/EquipmentClasses/Robot-Class" /> 158 </InternalElement> 159 <RoleRequirements RefBaseRoleClassPath="ResourceStructure" /> 160 </InternalElement> 161 <InternalElement Name="PhysicalAssets" ID="PhysicalAssets"> 162 <InternalElement Name="Conveyer-1-PA" ID="Conveyer-1-PA" 163 RefBaseSystemUnitPath= 164 "B2MML-PPR-SUC/PhysicalAssetClasses/Short-Conveyer-PA-Class"> 165 <Description> 166 Delivers cars without wheels from the product source to the turntable. 167 </Description> 168 <Attribute Name="id" AttributeDataType="xs:string"> 169 <Value>Conveyer-1-PA</Value> 170 </Attribute> 171 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 172 <Value>001</Value> 173 </Attribute> 174 <Attribute Name="vendorId" AttributeDataType="xs:string"> 175 <Value>CM12345</Value> 176 </Attribute> 177 <InternalElement Name="Conveyer-1-PA-B2MML-Document" 178 ID="Conveyer-1-PA-B2MML-Document"> 179 <ExternalInterface Name="B2MML" ID="B2MML-29" RefBaseClassPath="EDR"> 180 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 181 <Value>application/x.b2mml+xml</Value> 182 </Attribute> 183 <Attribute Name="refURI" AttributeDataType="xs:string"> 184 <Value>./PPR-PhysicalAssets.b2mml#Conveyer-1-PA</Value> 185 </Attribute> 186 </ExternalInterface> 187 <RoleRequirements 188 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 189 </InternalElement> 190 <RoleRequirements 191 RefBaseRoleClassPath= 192 "AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset" /> 193 </InternalElement> 194 <InternalElement Name="Turntable-PA" ID="Turntable-PA" 195 RefBaseSystemUnitPath= 196 "B2MML-PPR-SUC/PhysicalAssetClasses/Turntable-PA-Class"> 197 <Description> 198 Turns cars without wheels either towards the product drain for unfinished 199 products or towards Conveyor-2. 200 </Description> 201 <Attribute Name="id" AttributeDataType="xs:string"> 202 <Value>Turntable-PA</Value> 203 </Attribute> 204 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 205 <Value>003</Value> 206 </Attribute> 207 <Attribute Name="vendorId" AttributeDataType="xs:string"> 208 <Value>TM123</Value> 209 </Attribute> 210 <InternalElement Name="Turntable-PA-B2MML-Document" 211 ID="Turntable-PA-B2MML-Document"> 212 <ExternalInterface Name="B2MML" ID="B2MML-26" RefBaseClassPath="EDR"> 213 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 214 <Value>application/x.b2mml+xml</Value> 215 </Attribute> 216 <Attribute Name="refURI" AttributeDataType="xs:string"> 217 <Value>./PPR-PhysicalAssets.b2mml#Turntable-PA</Value> 218 </Attribute> 219 </ExternalInterface> 220 <RoleRequirements 221 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 222 </InternalElement>



223 <RoleRequirements 224 RefBaseRoleClassPath= 225 "AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset" /> 226 </InternalElement> 227 <InternalElement Name="Conveyer-2-PA" ID="Conveyer-2-PA" 228 RefBaseSystemUnitPath= 229 "B2MML-PPR-SUC/PhysicalAssetClasses/Long-Conveyer-PA-Class"> 230 <Description> 231 Delivers cars without wheels from the turntable to the product drain for 232 finished products. 233 </Description> 234 <Attribute Name="id" AttributeDataType="xs:string"> 235 <Value>Conveyer-2-PA</Value> 236 </Attribute> 237 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 238 <Value>002</Value> 239 </Attribute> 240 <Attribute Name="vendorId" AttributeDataType="xs:string"> 241 <Value>CM54321</Value> 242 </Attribute> 243 <InternalElement Name="Conveyer-2-PA-B2MML-Document" 244 ID="Conveyer-2-PA-B2MML-Document"> 245 <ExternalInterface Name="B2MML" ID="B2MML-28" RefBaseClassPath="EDR"> 246 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 247 <Value>application/x.b2mml+xml</Value> 248 </Attribute> 249 <Attribute Name="refURI" AttributeDataType="xs:string"> 250 <Value>./PPR-PhysicalAssets.b2mml#Conveyer-2-PA</Value> 251 </Attribute> 252 </ExternalInterface> 253 <RoleRequirements 254 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 255 </InternalElement> 256 <RoleRequirements 257 RefBaseRoleClassPath= 258 "AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset" /> 259 </InternalElement> 260 <InternalElement Name="Robot-PA" ID="Robot-PA" 261 RefBaseSystemUnitPath= 262 "B2MML-PPR-SUC/PhysicalAssetClasses/Robot-PA-Class"> 263 <Description>Assembles wheels to cars without wheels.</Description> 264 <Attribute Name="id" AttributeDataType="xs:string"> 265 <Value>Robot-PA</Value> 266 </Attribute> 267 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 268 <Value>004</Value> 269 </Attribute> 270 <Attribute Name="vendorId" AttributeDataType="xs:string"> 271 <Value>RM321</Value> 272 </Attribute> 273 <InternalElement Name="Robot-PA-B2MML-Document" 274 ID="Robot-PA-B2MML-Document"> 275 <ExternalInterface Name="B2MML" ID="B2MML-27" RefBaseClassPath="EDR"> 276 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 277 <Value>application/x.b2mml+xml</Value> 278 </Attribute> 279 <Attribute Name="refURI" AttributeDataType="xs:string"> 280 <Value>./PPR-PhysicalAssets.b2mml#Robot-PA</Value> 281 </Attribute> 282 </ExternalInterface> 283 <RoleRequirements 284 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 285 </InternalElement> 286 <RoleRequirements 287 RefBaseRoleClassPath= 288 "AutomationMLIEC62264RoleClassLib/PhysicalAssetModel/PhysicalAsset" />



289 </InternalElement> 290 <RoleRequirements RefBaseRoleClassPath="ResourceStructure" /> 291 </InternalElement> 292 <InternalElement Name="MaterialDefinitions" ID="MaterialDefinitions"> 293 <Description>IH representations of "Material Definition" system unit 294 classes.</Description> 295 <InternalElement Name="Wheel" ID="Wheel-Instance" 296 RefBaseSystemUnitPath="B2MML-PPR-SUC/MaterialDefinitions/Wheel"> 297 <ExternalInterface Name="PPR" ID="PPR-20" RefBaseClassPath="PPRConnector" /> 298 <RoleRequirements RefBaseRoleClassPath="MaterialDefinition" /> 299 </InternalElement> 300 <InternalElement Name="Car-without-Wheels" ID="Car-without-Wheels-Instance" 301 RefBaseSystemUnitPath= 302 "B2MML-PPR-SUC/MaterialDefinitions/Car-without-Wheels"> 303 <ExternalInterface Name="PPR" ID="PPR-21" RefBaseClassPath="PPRConnector" /> 304 <RoleRequirements RefBaseRoleClassPath="MaterialDefinition" /> 305 </InternalElement> 306 <InternalElement Name="Car-with-Wheels" ID="Car-with-Wheel-Instance" 307 RefBaseSystemUnitPath= 308 "B2MML-PPR-SUC/MaterialDefinitions/Car-with-Wheels"> 309 <ExternalInterface Name="PPR" ID="PPR-22" RefBaseClassPath="PPRConnector" /> 310 <RoleRequirements RefBaseRoleClassPath="MaterialDefinition" /> 311 </InternalElement> 312 <RoleRequirements RefBaseRoleClassPath="ProductStructure" /> 313 </InternalElement> 314 <InternalElement Name="MaterialClasses" ID="MaterialClasses"> 315 <Description>IH representations of "Material Class" role classes.</Description> 316 <InternalElement Name="Car-without-Wheels-Class" ID="Car-without-Wheels-Class"> 317 <InternalElement Name="Car-without-Wheels-Class-Document" 318 ID="Car-without-Wheels-Class-Document"> 319 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-23"> 320 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 321 <Value>application/x.b2mml+xml</Value> 322 </Attribute> 323 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 324 <Value>./PPR-Material.b2mml#Car-without-Wheels-Class</Value> 325 </Attribute> 326 </ExternalInterface> 327 <RoleRequirements 328 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 329 </InternalElement> 330 <RoleRequirements 331 RefBaseRoleClassPath= 332 "B2MML-PPR-RCL/MaterialClasses/Car-without-Wheels-Class" /> 333 </InternalElement> 334 <InternalElement Name="Wheel-Class" ID="Wheel-Class"> 335 <InternalElement Name="Wheel-Class-Document" ID="Wheel-Class-Document"> 336 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-24"> 337 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 338 <Value>application/x.b2mml+xml</Value> 339 </Attribute> 340 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 341 <Value>./PPR-Material.b2mml#Wheel-Class</Value> 342 </Attribute> 343 </ExternalInterface> 344 <RoleRequirements 345 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 346 </InternalElement> 347 <RoleRequirements 348 RefBaseRoleClassPath="B2MML-PPR-RCL/MaterialClasses/Wheel-Class" /> 349 </InternalElement> 350 <InternalElement Name="Car-with-Wheels-Class" ID="Car-with-Wheels-Class"> 351 <InternalElement Name="Car-with-Wheels-Class-Document" 352 ID="Car-with-Wheels-Class-Document"> 353 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-25"> 354 <Attribute Name="MIMEType" AttributeDataType="xs:string">



355 <Value>application/x.b2mml+xml</Value> 356 </Attribute> 357 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 358 <Value>./PPR-Material.b2mml#Car-with-Wheels-Class</Value> 359 </Attribute> 360 </ExternalInterface> 361 <RoleRequirements 362 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 363 </InternalElement> 364 <RoleRequirements 365 RefBaseRoleClassPath= 366 "B2MML-PPR-RCL/MaterialClasses/Car-with-Wheels-Class" /> 367 </InternalElement> 368 <RoleRequirements RefBaseRoleClassPath="ProductStructure" /> 369 </InternalElement> 370 <InternalElement Name="ProcessSegments" ID="ProcessSegments"> 371 <InternalElement Name="Transport-1" ID="Transport-1"> 372 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-15" /> 373 <InternalElement Name="Transport-1-B2MML-Document" 374 ID="Transport-1-B2MML-Document3"> 375 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-15"> 376 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 377 <Value>application/x.b2mml+xml</Value> 378 </Attribute> 379 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 380 <Value>./PPR-ProcessSegments.b2mml#Transport-1</Value> 381 </Attribute> 382 </ExternalInterface> 383 <RoleRequirements 384 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 385 </InternalElement> 386 <InternalLink Name="T1_C1" RefPartnerSideA="Transport-1:PPR" 387 RefPartnerSideB="Conveyer-1:PPR" /> 388 <InternalLink Name="T1_CWOW" RefPartnerSideA="Transport-1:PPR" 389 RefPartnerSideB="Car-without-Wheels-Instance:PPR" /> 390 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 391 </InternalElement> 392 <InternalElement Name="Turn" ID="Turn"> 393 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-16" /> 394 <InternalElement Name="Turn-B2MML-Document" ID="Turn-B2MML-Document"> 395 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-16"> 396 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 397 <Value>application/x.b2mml+xml</Value> 398 </Attribute> 399 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 400 <Value>./PPR-ProcessSegments.b2mml#Turn</Value> 401 </Attribute> 402 </ExternalInterface> 403 <RoleRequirements 404 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 405 </InternalElement> 406 <InternalLink Name="T_TT" RefPartnerSideA="Turn:PPR" 407 RefPartnerSideB="Turntable:PPR" /> 408 <InternalLink Name="T_CWOW" RefPartnerSideA="Turn:PPR" 409 RefPartnerSideB="Car-without-Wheels-Instance:PPR" /> 410 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 411 </InternalElement> 412 <InternalElement Name="Transport-2" ID="Transport-2"> 413 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-17" /> 414 <InternalElement Name="Transport-2-B2MML-Document" 415 ID="Transport-2-B2MML-Document"> 416 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-17"> 417 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 418 <Value>application/x.b2mml+xml</Value> 419 </Attribute> 420 <Attribute Name="refURI" AttributeDataType="xs:anyURI">



421 <Value>./PPR-ProcessSegments.b2mml#Transport-2</Value> 422 </Attribute> 423 </ExternalInterface> 424 <RoleRequirements 425 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 426 </InternalElement> 427 <InternalLink Name="T2_C2" RefPartnerSideA="Transport-2:PPR" 428 RefPartnerSideB="Conveyer-2:PPR" /> 429 <InternalLink Name="T2_CWOW" RefPartnerSideA="Transport-2:PPR" 430 RefPartnerSideB="Car-without-Wheels-Instance:PPR" /> 431 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 432 </InternalElement> 433 <InternalElement Name="Assemble" ID="Assemble"> 434 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-18" /> 435 <InternalElement Name="Assemble-B2MML-Document" 436 ID="Assemble-B2MML-Document"> 437 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-18"> 438 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 439 <Value>application/x.b2mml+xml</Value> 440 </Attribute> 441 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 442 <Value>./PPR-ProcessSegments.b2mml#Assemble</Value> 443 </Attribute> 444 </ExternalInterface> 445 <RoleRequirements 446 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 447 </InternalElement> 448 <InternalLink Name="A_R" RefPartnerSideA="Assemble:PPR" 449 RefPartnerSideB="Robot:PPR" /> 450 <InternalLink Name="A_CWOW" RefPartnerSideA="Assemble:PPR" 451 RefPartnerSideB="Car-without-Wheels-Instance:PPR" /> 452 <InternalLink Name="A_W" RefPartnerSideA="Assemble:PPR" 453 RefPartnerSideB="Wheel-Instance:PPR" /> 454 <InternalLink Name="A_CWW" RefPartnerSideA="Assemble:PPR" 455 RefPartnerSideB="Car-with-Wheel-Instance:PPR" /> 456 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 457 </InternalElement> 458 <InternalElement Name="Transport-3" ID="Transport-3"> 459 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-19" /> 460 <InternalElement Name="Transport-3-B2MML-Document" 461 ID="Transport-3-B2MML-Document"> 462 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-19"> 463 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 464 <Value>application/x.b2mml+xml</Value> 465 </Attribute> 466 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 467 <Value>./PPR-ProcessSegments.b2mml#Transport-3</Value> 468 </Attribute> 469 </ExternalInterface> 470 <RoleRequirements 471 RefBaseRoleClassPath="AutomationMLB2MMLRoleClassLib/B2mmlData" /> 472 </InternalElement> 473 <InternalLink Name="T3_C2" RefPartnerSideA="Transport-3:PPR" 474 RefPartnerSideB="Conveyer-2:PPR" /> 475 <InternalLink Name="T3_CWW" RefPartnerSideA="Transport-3:PPR" 476 RefPartnerSideB="Car-with-Wheel-Instance:PPR" /> 477 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 478 </InternalElement> 479 <RoleRequirements RefBaseRoleClassPath="ProcessStructure" /> 480 </InternalElement> 481 </InstanceHierarchy> 482 <RoleClassLib Name="B2MML-PPR-RCL"> 483 <Description>Modeling of IEC 62264 information.</Description> 484 <Version>1.0.0</Version> 485 <RoleClass Name="EquipmentClasses" RefBaseClassPath="ResourceStructure"> 486 <RoleClass Name="Conveyer-Class"



487 RefBaseClassPath= 488 "AutomationMLIEC62264RoleClassLib/EquipmentModel/EquipmentClass"> 489 <Description> 490 Conveyers of all kind belong to the Conveyer equipment class. 491 </Description> 492 <Attribute Name="id" AttributeDataType="xs:string"> 493 <Value>Conveyer-Class</Value> 494 </Attribute> 495 </RoleClass> 496 <RoleClass Name="Turntable-Class" 497 RefBaseClassPath= 498 "AutomationMLIEC62264RoleClassLib/EquipmentModel/EquipmentClass"> 499 <Description> 500 Turntables of all kind belong to the Turntable equipment class. 501 </Description> 502 <Attribute Name="id" AttributeDataType="xs:string"> 503 <Value>Turntable-Class</Value> 504 </Attribute> 505 </RoleClass> 506 <RoleClass Name="Robot-Class" 507 RefBaseClassPath= 508 "AutomationMLIEC62264RoleClassLib/EquipmentModel/EquipmentClass"> 509 <Description> 510 Robots of all kind belong to the Robot equipment class. 511 </Description> 512 <Attribute Name="id" AttributeDataType="xs:string"> 513 <Value>Robot-Class</Value> 514 </Attribute> 515 </RoleClass> 516 </RoleClass> 517 <RoleClass Name="MaterialClasses" RefBaseClassPath="ProductStructure"> 518 <RoleClass Name="Car-without-Wheels-Class" 519 RefBaseClassPath= 520 "AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialClass"> 521 <Description> 522 Cars without wheels of all kind belong to the Car-without-Wheels material 523 class. 524 </Description> 525 <Attribute Name="id" AttributeDataType="xs:string"> 526 <Value>Car-without-Wheels-Class</Value> 527 </Attribute> 528 </RoleClass> 529 <RoleClass Name="Wheel-Class" 530 RefBaseClassPath= 531 "AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialClass"> 532 <Description> 533 Wheels of all kind belong to the Wheel material class. 534 </Description> 535 <Attribute Name="id" AttributeDataType="xs:string"> 536 <Value>Wheel-Class</Value> 537 </Attribute> 538 </RoleClass> 539 <RoleClass Name="Car-with-Wheels-Class" 540 RefBaseClassPath= 541 "AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialClass"> 542 <Description> 543 Cars with wheels of all kind belong to the Car-with-Wheels material 544 class. 545 </Description> 546 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 547 <Value>Physical</Value> 548 </Attribute> 549 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 550 <Value>Permanent</Value> 551 </Attribute> 552 <Attribute Name="id" AttributeDataType="xs:string">



553 <Value>Car-with-Wheels-Class</Value> 554 </Attribute> 555 </RoleClass> 556 </RoleClass> 557 </RoleClassLib> 558 <SystemUnitClassLib Name="B2MML-PPR-SUC"> 559 <Description> 560 Integration of IEC 62264 information by referencing B2MML documents. 561 </Description> 562 <Version>1.0.0</Version> 563 <SystemUnitClass Name="PhysicalAssetClasses"> 564 <SupportedRoleClass RefRoleClassPath="ResourceStructure" /> 565 <SystemUnitClass Name="Short-Conveyer-PA-Class" ID="Short-Conveyer-PA-Class"> 566 <Description>The short conveyer of Conveyer Manufacturer.</Description> 567 <Attribute Name="id" AttributeDataType="xs:string"> 568 <Value>Short-Conveyer-PA-Class</Value> 569 </Attribute> 570 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 571 <Value>Conveyer Manufacturer</Value> 572 </Attribute> 573 <InternalElement Name="Short-Conveyer-PA-Class-B2MML-Document" 574 ID="Short-Conveyer-PA-Class-B2MML-Document"> 575 <ExternalInterface Name="B2MML" ID="B2MML-07" RefBaseClassPath="EDR"> 576 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 577 <Value>application/x.b2mml+xml</Value> 578 </Attribute> 579 <Attribute Name="refURI" AttributeDataType="xs:string"> 580 <Value>./PPR-PhysicalAssets.b2mml#Short-Conveyer-PA-Class</Value> 581 </Attribute> 582 </ExternalInterface> 583 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 584 </InternalElement> 585 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 586 </SystemUnitClass> 587 <SystemUnitClass Name="Long-Conveyer-PA-Class" ID="Long-Conveyer-PA-Class"> 588 <Description>The long conveyer of Conveyer Manufacturer.</Description> 589 <Attribute Name="id" AttributeDataType="xs:string"> 590 <Value>Long-Conveyer-PA-Class</Value> 591 </Attribute> 592 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 593 <Value>Conveyer Manufacturer</Value> 594 </Attribute> 595 <InternalElement Name="Long-Conveyer-PA-Class-B2MML-Document" 596 ID="Long-Conveyer-PA-Class-B2MML-Document"> 597 <ExternalInterface Name="B2MML" ID="B2MML-04" RefBaseClassPath="EDR"> 598 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 599 <Value>application/x.b2mml+xml</Value> 600 </Attribute> 601 <Attribute Name="refURI" AttributeDataType="xs:string"> 602 <Value>./PPR-PhysicalAssets.b2mml#Long-Conveyer-PA-Class</Value> 603 </Attribute> 604 </ExternalInterface> 605 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 606 </InternalElement> 607 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 608 </SystemUnitClass> 609 <SystemUnitClass Name="Turntable-PA-Class" ID="Turntable-PA-Class"> 610 <Description>The high end turntable of Turntable Manufacturer.</Description> 611 <Attribute Name="id" AttributeDataType="xs:string"> 612 <Value>Turntable-PA-Class</Value> 613 </Attribute> 614 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 615 <Value>Turntable Manufacturer</Value> 616 </Attribute> 617 <InternalElement Name="Turntable-PA-Class-B2MML-Document" 618 ID="Turntable-PA-Class-B2MML-Document">



619 <ExternalInterface Name="B2MML" ID="B2MML-05" RefBaseClassPath="EDR"> 620 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 621 <Value>application/x.b2mml+xml</Value> 622 </Attribute> 623 <Attribute Name="refURI" AttributeDataType="xs:string"> 624 <Value>./PPR-PhysicalAssets.b2mml#Turntable-PA-Class</Value> 625 </Attribute> 626 </ExternalInterface> 627 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 628 </InternalElement> 629 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 630 </SystemUnitClass> 631 <SystemUnitClass Name="Robot-PA-Class" ID="Robot-PA-Class"> 632 <Description>The only robot of Robot Manufacturer.</Description> 633 <Attribute Name="id" AttributeDataType="xs:string"> 634 <Value>Robot-PA-Class</Value> 635 </Attribute> 636 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 637 <Value>Robot Manufacturer</Value> 638 </Attribute> 639 <InternalElement Name="Robot-PA-Class-B2MML-Document" 640 ID="Robot-PA-Class-B2MML-Document"> 641 <ExternalInterface Name="B2MML" ID="B2MML-06" RefBaseClassPath="EDR"> 642 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 643 <Value>application/x.b2mml+xml</Value> 644 </Attribute> 645 <Attribute Name="refURI" AttributeDataType="xs:string"> 646 <Value>./PPR-PhysicalAssets.b2mml#Robot-PA-Class</Value> 647 </Attribute> 648 </ExternalInterface> 649 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 650 </InternalElement> 651 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 652 </SystemUnitClass> 653 </SystemUnitClass> 654 <SystemUnitClass Name="MaterialDefinitions"> 655 <SupportedRoleClass RefRoleClassPath="ProductStructure" /> 656 <SystemUnitClass Name="Wheel" ID="Wheel"> 657 <InternalElement Name="Wheel-B2MML-Document" ID="Wheel-B2MML-Document"> 658 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-01"> 659 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 660 <Value>application/x.b2mml+xml</Value> 661 </Attribute> 662 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 663 <Value>./PPR-Material.b2mml#Wheel</Value> 664 </Attribute> 665 </ExternalInterface> 666 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 667 </InternalElement> 668 <SupportedRoleClass 669 RefRoleClassPath="B2MML-PPR-RCL/MaterialClasses/Wheel-Class" /> 670 <SupportedRoleClass RefRoleClassPath="MaterialDefinition" /> 671 </SystemUnitClass> 672 <SystemUnitClass Name="Car-without-Wheels" ID="Car-without-Wheels"> 673 <InternalElement Name="Car-without-Wheels-B2MML-Document" 674 ID="Car-without-Wheels-B2MML-Document"> 675 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-02"> 676 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 677 <Value>application/x.b2mml+xml</Value> 678 </Attribute> 679 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 680 <Value>./PPR-Material.b2mml#Car-without-Wheels</Value> 681 </Attribute> 682 </ExternalInterface> 683 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 684 </InternalElement>



685 <SupportedRoleClass 686 RefRoleClassPath= 687 "B2MML-PPR-RCL/MaterialClasses/Car-without-Wheels-Class" /> 688 <SupportedRoleClass RefRoleClassPath="MaterialDefinition" /> 689 </SystemUnitClass> 690 <SystemUnitClass Name="Car-with-Wheels" ID="Car-with-Wheels"> 691 <InternalElement Name="Car-with-Wheels-B2MML-Document" 692 ID="Car-with-Wheels-B2MML-Document"> 693 <ExternalInterface Name="B2MML" RefBaseClassPath="EDR" ID="B2MML-03"> 694 <Attribute Name="MIMEType" AttributeDataType="xs:string"> 695 <Value>application/x.b2mml+xml</Value> 696 </Attribute> 697 <Attribute Name="refURI" AttributeDataType="xs:anyURI"> 698 <Value>./PPR-Material.b2mml#Car-with-Wheels</Value> 699 </Attribute> 700 </ExternalInterface> 701 <RoleRequirements RefBaseRoleClassPath="B2mmlData" /> 702 </InternalElement> 703 <SupportedRoleClass 704 RefRoleClassPath="B2MML-PPR-RCL/MaterialClasses/Car-with-Wheels-Class" 705 /> 706 <SupportedRoleClass RefRoleClassPath="MaterialDefinition" /> 707 </SystemUnitClass> 708 </SystemUnitClass> 709 </SystemUnitClassLib>

Listing 9 depicts the IEC 62264 equipment information encoded in B2MML. Equipment is one of two possible IEC 62264 counterparts of AML resources (the other one being physical assets). In order to list several pieces of equipment in one document, the root element EquipmentInformation is to be used. In this case, three equipment classes are specified: “Conveyer-Class”, “Turntable-Class”, and “Robot-Class”. Each of the classes specifies a list of equipment that is defined by this equipment class in a sequence of EquipmentID elements. Equipment elements in turn define through the EquipmentClassID element to which equipment class they belong to.

Listing 9: Contents of document PPR-Equipment.b2mml.

1 <EquipmentInformation xmlns="http://www.mesa.org/xml/B2MML-V0600">

2 <Equipment>

3 <ID>Conveyer-1</ID>

4 <Description>

5 Delivers cars without wheels from the product source to the turntable.

6 </Description>

7 <EquipmentLevel>


9 </EquipmentLevel>

10 <EquipmentClassID>Conveyer-Class</EquipmentClassID>

11 </Equipment>

12 <Equipment>

13 <ID>Conveyer-2</ID>

14 <Description>

15 Delivers cars without wheels from the turntable to the product drain for

16 finished products.

17 </Description>

18 <EquipmentLevel>



21 <EquipmentClassID>Conveyer-Class</EquipmentClassID>

22 </Equipment>

23 <Equipment>


25 <Description>

26 Turns cars without wheels either towards the product drain for unfinished

27 products or towards Conveyor2.

28 </Description>



29 <EquipmentLevel>



32 <EquipmentClassID>Turntable-Class</EquipmentClassID>

33 </Equipment>

34 <Equipment>

35 <ID>Robot</ID>

36 <Description>Assembles wheels to cars without wheels.</Description>

37 <EquipmentLevel>



40 <EquipmentClassID>Robot-Class</EquipmentClassID>

41 </Equipment>

42 <EquipmentClass>

43 <ID>Conveyer-Class</ID>

44 <Description>

45 Conveyers of all kind belong to the Conveyer equipment class.

46 </Description>

47 <EquipmentLevel>



50 <EquipmentID>Conveyer-1</EquipmentID>


52 </EquipmentClass>

53 <EquipmentClass>

54 <ID>Turntable-Class</ID>

55 <Description>

56 Turntables of all kind belong to the Turntable equipment class.

57 </Description>

58 <EquipmentLevel>



61 <EquipmentID>Turntable</EquipmentID>


63 <EquipmentClass>

64 <ID>Robot-Class</ID>

65 <Description>

66 Robots of all kind belong to the Robot equipment class.

67 </Description>

68 <EquipmentLevel>



71 <EquipmentID>Robot</EquipmentID>


73 </EquipmentInformation>

Listing 10 depicts the IEC 62264 physical asset information encoded in B2MML. Physical assets are one of two possible IEC 62264 counterparts of AML resources (the other one being equipment). In order to list several physical assets in one document, the root element PhysicalAssetModel is to be used. Here, four physical asset classes are defined: one for each equipment class presented in Listing 9 except for the Conveyer-Class, where two physical asset classes are defined, one for long conveyers, and one for short conveyers. The reason for that is the logics defined in IEC 62264: a physical asset class corresponds to a certain product model of a supplier. The four physical assets correspond to the required resources for the PPR example – in IEC 62264 physical assets correspond to a specific instance of a product model, i.e. something that yields a unique serial number.

Listing 10: Contents of document PPR-PhysicalAssets.b2mml.

1 <PhysicalAssetInformation xmlns="http://www.mesa.org/xml/B2MML-V0600">

2 <PhysicalAsset>

3 <ID>Conveyer-1-PA</ID>

4 <Description>

5 Delivers cars without wheels from the product source to the turntable.

6 </Description>



7 <PhysicalLocation>Area 1, Hall 1</PhysicalLocation>

8 <FixedAssetID>001</FixedAssetID>

9 <VendorID>CM12345</VendorID>

10 <EquipmentAssetMapping>


12 <PhysicalAssetID>Conveyer-1-PA</PhysicalAssetID>

13 <StartTime>2016-06-01</StartTime>

14 </EquipmentAssetMapping>

15 <PhysicalAssetClassID>Short-Conveyer-PA-Class</PhysicalAssetClassID>

16 </PhysicalAsset>

17 <PhysicalAsset>

18 <ID>Conveyer-2-PA</ID>

19 <Description>

20 Delivers cars without wheels from the turntable to the product drain for

21 finished products.

22 </Description>



25 <VendorID>CM54321</VendorID>






31 <PhysicalAssetClassID>Long- Conveyer-PA-Class</PhysicalAssetClassID>

32 </PhysicalAsset>

33 <PhysicalAsset>

34 <ID>Turntable-PA</ID>

35 <Description>

36 Turns cars without wheels either towards the product drain for unfinished

37 products or towards Conveyor 2.

38 </Description>



41 <VendorID>TM123</VendorID>


43 <EquipmentID>Turntable</EquipmentID>

44 <PhysicalAssetID>Turntable-PA</PhysicalAssetID>



47 <PhysicalAssetClassID>Turntable-PA-Class</PhysicalAssetClassID>

48 </PhysicalAsset>

49 <PhysicalAsset>

50 <ID>Robot-PA</ID>

51 <Description>Assembles wheels to cars without wheels.</Description>



54 <VendorID>RM321</VendorID>


56 <EquipmentID>Robot</EquipmentID>

57 <PhysicalAssetID>Robot-PA</PhysicalAssetID>



60 <PhysicalAssetClassID>Robot-PA-Class</PhysicalAssetClassID>

61 </PhysicalAsset>

62 <PhysicalAssetClass>

63 <ID>Short-Conveyer-PA-Class</ID>

64 <Description>The short conveyer of Conveyer Manufacturer.</Description>

65 <Manufacturer>Conveyer Manufacturer</Manufacturer>


67 </PhysicalAssetClass>


69 <ID>Long-Conveyer-PA-Class</ID>

70 <Description>The long conveyer of Conveyer Manufacturer.</Description>

71 <Manufacturer>Conveyer Manufacturer</Manufacturer>






75 <ID>Turntable-PA-Class</ID>

76 <Description>The high end turntable of Turntable Manufacturer.</Description>

77 <Manufacturer>Turntable Manufacturer</Manufacturer>

78 <PhysicalAssetID>Turntable-PA</PhysicalAssetID>



81 <ID>Robot-PA-Class</ID>

82 <Description>The only robot of Robot Manufacturer.</Description>

83 <Manufacturer>Robot Manufacturer</Manufacturer>

84 <PhysicalAssetID>Robot-PA</PhysicalAssetID>


86 </PhysicalAssetInformation>

Listing 11 depicts the IEC 62264 material information encoded in B2MML. Material is the IEC 62264 equivalent of AML products. In order to list several types of material in one document, the root element MaterialInformation is to be used. In this example three material classes and three material definitions are defined: cars without wheels, wheels, and cars with wheels. Material may represent an assembly, which can be defined on material class and/or material definition level. In this case, it is defined on both levels, stating that a car with wheels is a physical (the other option would be logical) and permanent (that is, it is not teared apart during production again) assembly of (i) a car without wheels and (ii) wheels.

Listing 11: Contents of document PPR-Material.b2mml.

1 <MaterialInformation xmlns="http://www.mesa.org/xml/B2MML-V0600">

2 <MaterialClass>

3 <ID>Car-without-Wheels-Class</ID>

4 <Description>

5 Cars without Wheels of all kind belong to the Car-without-Wheels material

6 class.

7 </Description>

8 <MaterialDefinitionID>Car-without-Wheels</MaterialDefinitionID>

9 </MaterialClass>

10 <MaterialClass>

11 <ID>Wheel-Class</ID>

12 <Description>

13 Wheels of all kind belong to the Wheel material class.

14 </Description>

15 <MaterialDefinitionID>Wheel</MaterialDefinitionID>

16 </MaterialClass>

17 <MaterialClass>

18 <ID>Car-with-Wheels-Class</ID>

19 <Description>

20 Cars with Wheels of all kind belong to the Car-with-Wheels material class.

21 </Description>

22 <MaterialDefinitionID>Car-with-Wheels</MaterialDefinitionID>

23 <AssemblyClassID>Car-without-Wheels-Class</AssemblyClassID>

24 <AssemblyClassID>Wheel-Class</AssemblyClassID>

25 <AssemblyType>Physical</AssemblyType>

26 <AssemblyRelationship>Permanent</AssemblyRelationship>

27 </MaterialClass>

28 <MaterialDefinition>

29 <ID>Car-without-Wheels</ID>

30 <Description>A car that has no wheels attached.</Description>

31 <MaterialClassID>Car-without-Wheels-Class</MaterialClassID>

32 </MaterialDefinition>


34 <ID>Wheel</ID>

35 <Description>A wheel that is to be attached to a car.</Description>

36 <MaterialClassID>Wheel-Class</MaterialClassID>



39 <ID>Car-with-Wheels</ID>



40 <Description>A car with wheels attached.</Description>

41 <MaterialClassID>Car-with-Wheels-Class</MaterialClassID>

42 <AssemblyDefinitionID>Car-without-Wheels</AssemblyDefinitionID>

43 <AssemblyDefinitionID>Wheel</AssemblyDefinitionID>

44 <AssemblyType>Physical</AssemblyType>

45 <AssemblyRelationship>Permanent</AssemblyRelationship>


47 </MaterialInformation>

Listing 12 depicts the IEC 62264 process segment information encoded in B2MML. Process segments are the IEC 62264 equivalent of AML processes. In order to list several process segments in one document, the root element ProcessSegmentInformation is to be used. In this example five process segments are defined, corresponding to the processes of the PPR-setup. From the B2MML code given in Listing 12 a lot of information can be extracted that might be of use in the context of AutomationML. This information could be used to enrich the referencing AML document (and thus duplicate information, which might resemble a problem with regards to document maintenance), or it could be used by tools that understand AML and B2MML to infer knowledge for advanced tasks (such as simulation). The information provided in Listing 12 includes:

1. the process itself is assigned to an equipment level (e.g. Transport-1 takes place on the work cell level),

2. the duration of a process (e.g. Transport-1 takes 30 seconds: “PT30S”),

3. the equipment and material required for the process (this information should correspond to information encoded in AML using the PPR method),

4. a quantity for the involved equipment (e.g. 30 machine seconds per piece for Conveyer-1),

5. a quantity for the required material (e.g. 1 unit of cars without wheels for Transport-1),

6. the role of the involved material: is it consumed, produced, or moved (e.g. in the Assemble process segment, the materials Wheel and Car-without-Wheels are consumed, while the material Car-with-Wheels is produced)? This kind of information is not commonly defined in the PPR method,

7. segment dependencies define how two process segments are depending on each other (e.g. “Start Turn after Transport-1 end”, which resembles a time constraint that the turn process must not start earlier than after Transport-1 has finished).

Listing 12: Contents of document PPR-ProcessSegments.b2mml.

1 <ProcessSegmentInformation xmlns="http://www.mesa.org/xml/B2MML-V0600">

2 <ProcessSegment>

3 <ID>Transport-1</ID>

4 <Description>

5 Transport 1 is accomplished with Conveyer 1. Cars without wheels are

6 delivered from the product source to the turntable.

7 </Description>

8 <OperationsType>Production</OperationsType>

9 <HierarchyScope>

10 <EquipmentElementLevel OtherValue="">WorkCell</EquipmentElementLevel>

11 </HierarchyScope>

12 <Duration>PT30S</Duration>

13 <EquipmentSegmentSpecification>


15 <Description>

16 Conveyer needed for transporting cars without wheels to the turntable.

17 </Description>

18 <EquipmentUse>Material Movement</EquipmentUse>

19 <Quantity>

20 <QuantityString>30</QuantityString>

21 <UnitOfMeasure>Machine Seconds / Piece</UnitOfMeasure>

22 </Quantity>

23 </EquipmentSegmentSpecification>

24 <MaterialSegmentSpecification>


26 <Description>

27 The cars without wheels that are to be transported.



28 </Description>

29 <MaterialUse>Material Moved</MaterialUse>

30 <Quantity>


32 <UnitOfMeasure>Units</UnitOfMeasure>

33 </Quantity>

34 </MaterialSegmentSpecification>

35 </ProcessSegment>

36 <ProcessSegment>


38 <Description>

39 Transport 2 is accomplished with Conveyer 2. Cars without wheels are

40 delivered from the turntable to the robot.

41 </Description>


43 <HierarchyScope>






49 <Description>

50 Conveyer needed for transporting cars without wheels from the turntable

51 to the robot.

52 </Description>


54 <Quantity>



57 </Quantity>


59 <MaterialSegmentSpecification>


61 <Description>

62 The cars without wheels that are to be transported.

63 </Description>

64 <MaterialUse>Material Moved</MaterialUse>

65 <Quantity>


67 <UnitOfMeasure>Units</UnitOfMeasure>

68 </Quantity>

69 </MaterialSegmentSpecification>

70 <SegmentDependency>

71 <ID>Transport-2-after-Turn</ID>

72 <Description>Transport 2 after Turn</Description>

73 <Dependency>Start Transport 2 after Turn end</Dependency>

74 <ProcessSegmentID>Turn</ProcessSegmentID>

75 </SegmentDependency>

76 </ProcessSegment>

77 <ProcessSegment>


79 <Description>

80 Transport 3 is accomplished with Conveyer 2. Cars with wheels are delivered

81 from the robot to the product drain for finished products.

82 </Description>


84 <HierarchyScope>






90 <Description>

91 Conveyer needed for transporting cars with wheels from the robot to the

92 product drain.

93 </Description>




95 <Quantity>



98 </Quantity>


100 <MaterialSegmentSpecification> 101 <MaterialDefinitionID>Car-with-Wheels</MaterialDefinitionID> 102 <Description>The cars with wheels that are to be transported.</Description> 103 <MaterialUse>Material Moved</MaterialUse> 104 <Quantity> 105 <QuantityString>1</QuantityString> 106 <UnitOfMeasure>Units</UnitOfMeasure> 107 </Quantity> 108 </MaterialSegmentSpecification> 109 <SegmentDependency> 110 <ID>Transport-3-after-Assemble</ID> 111 <Description>Transport 3 after Assemble</Description> 112 <Dependency>Start Transport 3 after Assemble end</Dependency> 113 <ProcessSegmentID>Assemble</ProcessSegmentID> 114 </SegmentDependency> 115 </ProcessSegment> 116 <ProcessSegment> 117 <ID>Turn</ID> 118 <Description> 119 Turning is accomplished by the turntable that might hold a car without 120 wheels. Cars without wheels that should be assembled are turned 121 towards Conveyer 2, the ones that should not be further processed are 122 turned towards the product drain for unfinished products. 123 </Description> 124 <OperationsType>Production</OperationsType> 125 <HierarchyScope> 126 <EquipmentElementLevel OtherValue="">WorkCell</EquipmentElementLevel> 127 </HierarchyScope> 128 <Duration>PT15S</Duration> 129 <EquipmentSegmentSpecification> 130 <EquipmentID>Turntable</EquipmentID> 131 <Description> 132 Turntable needed for turning cars to either Conveyer 2 or to the product 133 drain for unfinished products. 134 </Description> 135 <EquipmentUse>Material Movement</EquipmentUse> 136 <Quantity> 137 <QuantityString>15</QuantityString> 138 <UnitOfMeasure>Machine Seconds / Piece</UnitOfMeasure> 139 </Quantity> 140 </EquipmentSegmentSpecification> 141 <MaterialSegmentSpecification> 142 <MaterialDefinitionID>Car-without-Wheels</MaterialDefinitionID> 143 <Description>The cars without wheels that are to be turned.</Description> 144 <MaterialUse>Material Moved</MaterialUse> 145 <Quantity> 146 <QuantityString>1</QuantityString> 147 <UnitOfMeasure>Units</UnitOfMeasure> 148 </Quantity> 149 </MaterialSegmentSpecification> 150 <SegmentDependency> 151 <ID>Turn-after-Transport-1</ID> 152 <Description>Turn after Transport 1</Description> 153 <Dependency>Start Turn after Transport 1 end</Dependency> 154 <ProcessSegmentID>Transport-1</ProcessSegmentID> 155 </SegmentDependency> 156 </ProcessSegment> 157 <ProcessSegment> 158 <ID>Assemble</ID> 159 <Description>



160 Assembling is accomplished by the robot, which attaches wheels to cars 161 without wheels in order to transform them into cars with wheels. 162 </Description> 163 <OperationsType>Production</OperationsType> 164 <HierarchyScope> 165 <EquipmentElementLevel OtherValue="">WorkCell</EquipmentElementLevel> 166 </HierarchyScope> 167 <Duration>PT2M</Duration> 168 <EquipmentSegmentSpecification> 169 <EquipmentID>Robot</EquipmentID> 170 <Description> 171 Robot needed for attaching wheels to cars without wheels. 172 </Description> 173 <EquipmentUse>Attach Wheels</EquipmentUse> 174 <Quantity> 175 <QuantityString>2</QuantityString> 176 <UnitOfMeasure>Machine Minutes / Piece</UnitOfMeasure> 177 </Quantity> 178 </EquipmentSegmentSpecification> 179 <MaterialSegmentSpecification> 180 <MaterialDefinitionID>Car-without-Wheels</MaterialDefinitionID> 181 <Description>The cars without wheels that are to be refined.</Description> 182 <MaterialUse>Material Consumed</MaterialUse> 183 <Quantity> 184 <QuantityString>1</QuantityString> 185 <UnitOfMeasure>Units</UnitOfMeasure> 186 </Quantity> 187 </MaterialSegmentSpecification> 188 <MaterialSegmentSpecification> 189 <MaterialDefinitionID>Wheel</MaterialDefinitionID> 190 <Description>The wheels that are to be attached.</Description> 191 <MaterialUse>Material Consumed</MaterialUse> 192 <Quantity> 193 <QuantityString>4</QuantityString> 194 <UnitOfMeasure>Units</UnitOfMeasure> 195 </Quantity> 196 </MaterialSegmentSpecification> 197 <MaterialSegmentSpecification> 198 <MaterialDefinitionID>Car-with-Wheels</MaterialDefinitionID> 199 <Description>The cars with wheels that are produced.</Description> 200 <MaterialUse>Material Produced</MaterialUse> 201 <Quantity> 202 <QuantityString>1</QuantityString> 203 <UnitOfMeasure>Units</UnitOfMeasure> 204 </Quantity> 205 </MaterialSegmentSpecification> 206 <SegmentDependency> 207 <ID>Assemble-after-Transport-2</ID> 208 <Description>Assemble after Transport 2</Description> 209 <Dependency>Start Assemble after Transport 2 end</Dependency> 210 <ProcessSegmentID>Transport-2</ProcessSegmentID> 211 </SegmentDependency> 212 </ProcessSegment> 213 </ProcessSegmentInformation>



Appendix E Example for Modeling IEC 62264 Information within AML Documents

Listing 13 resembles the InstanceHierarchy, RoleClassLib and SystemUnitClassLib of the AutomationML document for the IEC 62264 PPR example, again based on the application scenario depicted in Figures 25 and 26. Instead of referencing various elements from different B2MML documents, it models IEC 62264 information within AML, by making use of the AutomationMLIEC62264RoleClassLib. Again, the substitutions as depicted in Table 135 have been conducted.

There are no references to external B2MML documents modeled here, but B2MML documents could be partly generated from the information stored in this AML document.

Listing 13: InstanceHierarchy, SystemUnitClassLib, and RoleClassLib excerpt of document Example-04-IEC62264-PPR.aml.

1 <InstanceHierarchy Name="IEC62264-PPR-IH">

2 <Description>

3 Example for modeling IEC 62264 elements without reference to B2MML documents.

4 The IEC 62264 logic is modeled by means of AML concepts. Additionally,

5 AML objects are aligned with PPR roles.

6 </Description>


8 <InternalElement Name="Equipment" ID="Equipment">

9 <InternalElement Name="Site-1" ID="Site-1">

10 <InternalElement Name="Hall-1" ID="Hall-1">

11 <InternalElement Name="Production-Line-1" ID="Production-Line-1">

12 <InternalElement Name="Robot" ID="Robot">

13 <Description>

14 Assembles wheels to cars without wheels.

15 </Description>


17 <Value>Robot</Value>

18 </Attribute>

19 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector"

20 ID="PPR-14" />

21 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-01" />

22 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-01">


24 <Description>

25 An identification of the specific equipment asset

26 mapping.

27 </Description>

28 </Attribute>

29 <Attribute Name="description" AttributeDataType="xs:string">

30 <Description>

31 Additional information about the mapping element.

32 </Description>

33 </Attribute>

34 <Attribute Name="startTime" AttributeDataType="xs:dateTime">

35 <Description>

36 The starting time of the association.

37 </Description>

38 </Attribute>

39 <Attribute Name="endTime" AttributeDataType="xs:dateTime">

40 <Description>

41 The ending time of the association.

42 </Description>

43 </Attribute>




47 RefRoleClassPath=

48 "IEC62264-PPR-RCL/EquipmentClasses/Robot-Class" />






52 <Description>

53 Delivers cars without wheels from the turntable to the product

54 drain for finished products.

55 </Description>


57 <Value>Conveyer-2</Value>

58 </Attribute>


60 ID="PPR-13" />

61 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-02" />

62 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-02">


64 <Description>

65 An identification of the specific equipment asset

66 mapping.

67 </Description>

68 </Attribute>

69 <Attribute Name="description" AttributeDataType="xs:string">

70 <Description>

71 Additional information about the mapping element.

72 </Description>

73 </Attribute>

74 <Attribute Name="startTime" AttributeDataType="xs:dateTime">

75 <Description>

76 The starting time of the association.

77 </Description>

78 </Attribute>

79 <Attribute Name="endTime" AttributeDataType="xs:dateTime">

80 <Description>

81 The ending time of the association.

82 </Description>

83 </Attribute>




87 RefRoleClassPath=

88 "IEC62264-PPR-RCL/EquipmentClasses/Conveyer-Class" />




92 <Description>

93 Turns cars without wheels either towards the product drain for

94 unfinished products or towards Conveyor-2.

95 </Description>


97 <Value>Turntable</Value>

98 </Attribute>


100 ID="PPR-12" /> 101 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-03" /> 102 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-03"> 103 <Attribute Name="id" AttributeDataType="xs:string"> 104 <Description> 105 An identification of the specific equipment asset 106 mapping. 107 </Description> 108 </Attribute> 109 <Attribute Name="description" AttributeDataType="xs:string"> 110 <Description> 111 Additional information about the mapping element. 112 </Description> 113 </Attribute> 114 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 115 <Description>



116 The starting time of the association. 117 </Description> 118 </Attribute> 119 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 120 <Description> 121 The ending time of the association. 122 </Description> 123 </Attribute> 124 </ExternalInterface> 125 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 126 <SupportedRoleClass 127 RefRoleClassPath= 128 "IEC62264-PPR-RCL/EquipmentClasses/Turntable-Class" /> 129 <RoleRequirements RefBaseRoleClassPath="Equipment" /> 130 </InternalElement> 131 <InternalElement Name="Conveyer-1" ID="Conveyer-1"> 132 <Description> 133 Delivers cars without wheels from the product source to the 134 turntable. 135 </Description> 136 <Attribute Name="id" AttributeDataType="xs:string"> 137 <Value>Conveyer-1</Value> 138 </Attribute> 139 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" 140 ID="PPR-11" /> 141 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-04" /> 142 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-04"> 143 <Attribute Name="id" AttributeDataType="xs:string"> 144 <Description> 145 An identification of the specific equipment asset 146 mapping. 147 </Description> 148 </Attribute> 149 <Attribute Name="description" AttributeDataType="xs:string"> 150 <Description> 151 Additional information about the mapping element. 152 </Description> 153 </Attribute> 154 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 155 <Description> 156 The starting time of the association. 157 </Description> 158 </Attribute> 159 <Attribute Name="endTime" AttributeDataType="xs:dateTime"> 160 <Description> 161 The ending time of the association. 162 </Description> 163 </Attribute> 164 </ExternalInterface> 165 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 166 <SupportedRoleClass 167 RefRoleClassPath= 168 "IEC62264-PPR-RCL/EquipmentClasses/Conveyer-Class" /> 169 <RoleRequirements RefBaseRoleClassPath="Equipment" /> 170 </InternalElement> 171 <SupportedRoleClass RefRoleClassPath="Equipment" /> 172 <RoleRequirements RefBaseRoleClassPath="ProductionLine" /> 173 </InternalElement> 174 <SupportedRoleClass RefRoleClassPath="Equipment" /> 175 <RoleRequirements RefBaseRoleClassPath="Area" /> 176 </InternalElement> 177 <SupportedRoleClass RefRoleClassPath="Equipment" /> 178 <RoleRequirements RefBaseRoleClassPath="Site" /> 179 </InternalElement> 180 <RoleRequirements RefBaseRoleClassPath="ResourceStructure" /> 181 </InternalElement>



182 <InternalElement Name="PhysicalAssets" ID="PhysicalAssets"> 183 <InternalElement Name="Conveyer-1-PA" ID="Conveyer-1-PA" 184 RefBaseSystemUnitPath= 185 "IEC62264-PPR-SUC/PhysicalAssetClasses/Short-Conveyer-PA-Class"> 186 <Description> 187 Delivers cars without wheels from the product source to the turntable. 188 </Description> 189 <Attribute Name="id" AttributeDataType="xs:string"> 190 <Value>Conveyer-1-PA</Value> 191 </Attribute> 192 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 193 <Value>001</Value> 194 </Attribute> 195 <Attribute Name="vendorId" AttributeDataType="xs:string"> 196 <Value>CM12345</Value> 197 </Attribute> 198 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-05" /> 199 <RoleRequirements RefBaseRoleClassPath="PhysicalAsset" /> 200 </InternalElement> 201 <InternalElement Name="Turntable-PA" ID="Turntable-PA" 202 RefBaseSystemUnitPath= 203 "IEC62264-PPR-SUC/PhysicalAssetClasses/Turntable-PA-Class"> 204 <Description> 205 Turns cars without wheels either towards the product drain for 206 unfinished products or towards Conveyor-2. 207 </Description> 208 <Attribute Name="id" AttributeDataType="xs:string"> 209 <Value>Turntable-PA</Value> 210 </Attribute> 211 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 212 <Value>003</Value> 213 </Attribute> 214 <Attribute Name="vendorId" AttributeDataType="xs:string"> 215 <Value>TM123</Value> 216 </Attribute> 217 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-06" /> 218 <RoleRequirements RefBaseRoleClassPath="PhysicalAsset" /> 219 </InternalElement> 220 <InternalElement Name="Conveyer-2-PA" ID="Conveyer-2-PA" 221 RefBaseSystemUnitPath= 222 "IEC62264-PPR-SUC/PhysicalAssetClasses/Long-Conveyer-PA-Class"> 223 <Description> 224 Delivers cars without wheels from the turntable to the product drain 225 for finished products. 226 </Description> 227 <Attribute Name="id" AttributeDataType="xs:string"> 228 <Value>Conveyer-2-PA</Value> 229 </Attribute> 230 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 231 <Value>002</Value> 232 </Attribute> 233 <Attribute Name="vendorId" AttributeDataType="xs:string"> 234 <Value>CM54321</Value> 235 </Attribute> 236 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-07" /> 237 <RoleRequirements RefBaseRoleClassPath="PhysicalAsset" /> 238 </InternalElement> 239 <InternalElement Name="Robot-PA" ID="Robot-PA" 240 RefBaseSystemUnitPath= 241 "IEC62264-PPR-SUC/PhysicalAssetClasses/Robot-PA-Class"> 242 <Description>Assembles wheels to cars without wheels.</Description> 243 <Attribute Name="id" AttributeDataType="xs:string"> 244 <Value>Robot-PA</Value> 245 </Attribute> 246 <Attribute Name="fixedAssetId" AttributeDataType="xs:string"> 247 <Value>004</Value>



248 </Attribute> 249 <Attribute Name="vendorId" AttributeDataType="xs:string"> 250 <Value>RM321</Value> 251 </Attribute> 252 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-08" /> 253 <RoleRequirements RefBaseRoleClassPath="PhysicalAsset" /> 254 </InternalElement> 255 <RoleRequirements RefBaseRoleClassPath="ResourceStructure" /> 256 </InternalElement> 257 <InternalElement Name="MaterialDefinitions" ID="MaterialDefinitions"> 258 <InternalElement Name="Car-without-Wheels" ID="Car-without-Wheels" 259 RefBaseSystemUnitPath= 260 "IEC62264-PPR-SUC/MaterialDefinitions/Car-without-Wheels"> 261 <ExternalInterface Name="PPR" ID="PPR-20" RefBaseClassPath="PPRConnector" 262 /> 263 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-05" /> 264 <RoleRequirements RefBaseRoleClassPath="MaterialDefinition" /> 265 </InternalElement> 266 <InternalElement Name="Wheel" ID="Wheel" 267 RefBaseSystemUnitPath="IEC62264-PPR-SUC/MaterialDefinitions/Wheel"> 268 <ExternalInterface Name="PPR" ID="PPR-21" RefBaseClassPath="PPRConnector" 269 /> 270 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-06" /> 271 <RoleRequirements RefBaseRoleClassPath="MaterialDefinition" /> 272 </InternalElement> 273 <InternalElement Name="Car-with-Wheels" ID="Car-with-Wheels" 274 RefBaseSystemUnitPath= 275 "IEC62264-PPR-SUC/MaterialDefinitions/Car-with-Wheels"> 276 <ExternalInterface Name="PPR" ID="PPR-22" RefBaseClassPath="PPRConnector" 277 /> 278 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-07" /> 279 <InternalElement Name="Assembly" ID="Assembly-01"> 280 <InternalElement Name="Wheel" ID="Wheel-01" 281 RefBaseSystemUnitPath="Wheel"></InternalElement> 282 <InternalElement Name="Car-without-Wheels" ID="Car-without-Wheels-01" 283 RefBaseSystemUnitPath="Car-without-Wheels"></InternalElement> 284 <RoleRequirements 285 RefBaseRoleClassPath= 286 "AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialAssembly" 287 /> 288 </InternalElement> 289 <RoleRequirements RefBaseRoleClassPath="MaterialDefinition" /> 290 </InternalElement> 291 <RoleRequirements RefBaseRoleClassPath="ProductStructure" /> 292 </InternalElement> 293 <InternalElement Name="MaterialClasses" ID="MaterialClasses"> 294 <InternalElement Name="Car-without-Wheels-Class" 295 ID="Car-without-Wheels-Class"> 296 <RoleRequirements 297 RefBaseRoleClassPath= 298 "IEC62264-PPR-RCL/MaterialClasses/Car-without-Wheels-Class" /> 299 </InternalElement> 300 <InternalElement Name="Wheel-Class" ID="Wheel-Class-02"> 301 <RoleRequirements 302 RefBaseRoleClassPath="IEC62264-PPR-RCL/MaterialClasses/Wheel-Class" 303 /> 304 </InternalElement> 305 <InternalElement Name="Car-with-Wheels-Class" ID="Car-with-Wheels-Class"> 306 <InternalElement Name="Assembly" ID="Assembly"> 307 <InternalElement Name="Wheel-Class" ID="Wheel-Class-01" 308 RefBaseSystemUnitPath="Wheel-Class-02"></InternalElement> 309 <InternalElement Name="Car-without-Wheels-Class" 310 ID="Car-without-Wheels-Class-01" 311 RefBaseSystemUnitPath="Car-without-Wheels-Class"> 312 </InternalElement> 313 <RoleRequirements



314 RefBaseRoleClassPath= 315 "AutomationMLIEC62264RoleClassLib/MaterialModel/MaterialAssembly" 316 /> 317 </InternalElement> 318 <RoleRequirements 319 RefBaseRoleClassPath= 320 "IEC62264-PPR-RCL/MaterialClasses/Car-with-Wheels-Class" /> 321 </InternalElement> 322 <RoleRequirements RefBaseRoleClassPath="ProductStructure" /> 323 </InternalElement> 324 <InternalElement Name="ProcessSegments" ID="ProcessSegments"> 325 <InternalElement Name="Transport-1" ID="Transport-1"> 326 <Description> 327 Transport-1 is accomplished with Conveyer-1. Cars without wheels are 328 delivered from the product source to the turntable. 329 </Description> 330 <Attribute Name="id" AttributeDataType="xs:string"> 331 <Value>Transport-1</Value> 332 </Attribute> 333 <Attribute Name="operationsType" AttributeDataType="xs:string"> 334 <Value>Production</Value> 335 </Attribute> 336 <Attribute Name="duration" AttributeDataType="xs:decimal"> 337 <Value>30</Value> 338 </Attribute> 339 <Attribute Name="durationUnitOfMeasure" AttributeDataType="xs:string"> 340 <Value>seconds</Value> 341 </Attribute> 342 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-15" 343 /> 344 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-01" /> 345 <InternalElement Name="Conveyer-1-Specification" 346 ID="Conveyer-1-Specification"> 347 <Description> 348 Conveyer needed for transporting cars without wheels to the 349 turntable. 350 </Description> 351 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 352 <Value>Material Movement</Value> 353 </Attribute> 354 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 355 <Value>30</Value> 356 </Attribute> 357 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 358 <Value>machine seconds / piece</Value> 359 </Attribute> 360 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-08" /> 361 <InternalLink Name="t1_c1" 362 RefPartnerSideA="Conveyer-1-Specification:RC" 363 RefPartnerSideB="Conveyer-1:RC" /> 364 <RoleRequirements RefBaseRoleClassPath="EquipmentSegmentSpecification" 365 /> 366 </InternalElement> 367 <InternalElement Name="Car-without-Wheels-Specification" 368 ID="Car-without-Wheels-Specification"> 369 <Description> 370 The cars without wheels that are to be transported. 371 </Description> 372 <Attribute Name="materialUse" AttributeDataType="xs:string"> 373 <Value>Material Moved</Value> 374 </Attribute> 375 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 376 <Value>1</Value> 377 </Attribute> 378 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 379 <Value>units</Value>



380 </Attribute> 381 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-09" /> 382 <InternalLink Name="t1_cwow" 383 RefPartnerSideA="Car-without-Wheels-Specification:RC" 384 RefPartnerSideB="Car-without-Wheels:RC" /> 385 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 386 /> 387 </InternalElement> 388 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 389 <InternalLink Name="T1_C1" RefPartnerSideA="Transport-1:PPR" 390 RefPartnerSideB="Conveyer-1:PPR" /> 391 <InternalLink Name="T1_CWOW" RefPartnerSideA="Transport-1:PPR" 392 RefPartnerSideB="Car-without-Wheels:PPR" /> 393 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 394 </InternalElement> 395 <InternalElement Name="Turn" ID="Turn"> 396 <Description> 397 Turning is accomplished by the turntable that might hold a 398 Car-without-Wheels. Cars without wheels that should be assembled 399 are turned towards Conveyer-2, the ones that should not be 400 further processed are turned towards the product drain for 401 unfinished products. 402 </Description> 403 <Attribute Name="id" AttributeDataType="xs:string"> 404 <Value>Turn</Value> 405 </Attribute> 406 <Attribute Name="operationsType" AttributeDataType="xs:string"> 407 <Value>Production</Value> 408 </Attribute> 409 <Attribute Name="duration" AttributeDataType="xs:decimal"> 410 <Value>15</Value> 411 </Attribute> 412 <Attribute Name="durationUnitOfMeasure" AttributeDataType="xs:string"> 413 <Value>seconds</Value> 414 </Attribute> 415 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-16" 416 /> 417 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-02" /> 418 <InternalElement Name="Turntable-Specification" 419 ID="Turntable-Specification"> 420 <Description> 421 Turntable needed for turning cars to either Conveyer-2 or to the 422 product drain for unfinished products. 423 </Description> 424 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 425 <Value>Material Movement</Value> 426 </Attribute> 427 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 428 <Value>15</Value> 429 </Attribute> 430 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 431 <Value>machine seconds / piece</Value> 432 </Attribute> 433 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-10" /> 434 <InternalLink Name="t_tt" RefPartnerSideA="Turntable-Specification:RC" 435 RefPartnerSideB="Turntable:RC" /> 436 <RoleRequirements RefBaseRoleClassPath="EquipmentSegmentSpecification" 437 /> 438 </InternalElement> 439 <InternalElement Name="Car-without-Wheels-Specification" 440 ID="Car-without-Wheels-Specification"> 441 <Description> 442 The cars without wheels that are to be turned. 443 </Description> 444 <Attribute Name="materialUse" AttributeDataType="xs:string"> 445 <Value>Material Moved</Value>



446 </Attribute> 447 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 448 <Value>1</Value> 449 </Attribute> 450 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 451 <Value>units</Value> 452 </Attribute> 453 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-11" /> 454 <InternalLink Name="t_cwow" 455 RefPartnerSideA="Car-without-Wheels-Specification:RC" 456 RefPartnerSideB="Car-without-Wheels:RC" /> 457 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 458 /> 459 </InternalElement> 460 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 461 <InternalLink Name="T_TT" RefPartnerSideA="Turn:PPR" 462 RefPartnerSideB="Turntable:PPR" /> 463 <InternalLink Name="T_CWOW" RefPartnerSideA="Turn:PPR" 464 RefPartnerSideB="Car-without-Wheels:PPR" /> 465 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 466 </InternalElement> 467 <InternalElement Name="Transport-2" ID="Transport-2"> 468 <Description> 469 Transport-2 is accomplished with Conveyer-2. Cars without wheels are 470 delivered from the turntable to the robot. 471 </Description> 472 <Attribute Name="id" AttributeDataType="xs:string"> 473 <Value>Transport-2</Value> 474 </Attribute> 475 <Attribute Name="operationsType" AttributeDataType="xs:string"> 476 <Value>Production</Value> 477 </Attribute> 478 <Attribute Name="duration" AttributeDataType="xs:decimal"> 479 <Value>10</Value> 480 </Attribute> 481 <Attribute Name="durationUnitOfMeasure" AttributeDataType="xs:string"> 482 <Value>seconds</Value> 483 </Attribute> 484 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-17" 485 /> 486 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-03" /> 487 <InternalElement Name="Conveyer-2-Specification" 488 ID="Transport-2-Specification"> 489 <Description> 490 Conveyer needed for transporting cars without wheels from the 491 turntable to the robot. 492 </Description> 493 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 494 <Value>Material Movement</Value> 495 </Attribute> 496 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 497 <Value>10</Value> 498 </Attribute> 499 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 500 <Value>machine seconds / piece</Value> 501 </Attribute> 502 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-12" /> 503 <InternalLink Name="t2_c2" 504 RefPartnerSideA="Transport-2-Specification:RC" 505 RefPartnerSideB="Conveyer-2:RC" /> 506 <RoleRequirements RefBaseRoleClassPath="EquipmentSegmentSpecification" 507 /> 508 </InternalElement> 509 <InternalElement Name="Car-without-Wheels-Specification" 510 ID="Car-without-Wheels-Specification"> 511 <Description>



512 The cars without wheels that are to be transported. 513 </Description> 514 <Attribute Name="materialUse" AttributeDataType="xs:string"> 515 <Value>Material Moved</Value> 516 </Attribute> 517 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 518 <Value>1</Value> 519 </Attribute> 520 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 521 <Value>units</Value> 522 </Attribute> 523 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-13" /> 524 <InternalLink Name="t2_cwow" 525 RefPartnerSideA="Car-without-Wheels-Specification:RC" 526 RefPartnerSideB="Car-without-Wheels:RC" /> 527 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 528 /> 529 </InternalElement> 530 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 531 <InternalLink Name="T2_C2" RefPartnerSideA="Transport-2:PPR" 532 RefPartnerSideB="Conveyer-2:PPR" /> 533 <InternalLink Name="T2_CWOW" RefPartnerSideA="Transport-2:PPR" 534 RefPartnerSideB="Car-without-Wheels:PPR" /> 535 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 536 </InternalElement> 537 <InternalElement Name="Assemble" ID="Assemble"> 538 <Description> 539 Assembling is accomplished by the robot, which attaches wheels to cars 540 without wheels in order to transform them into cars with wheels. 541 </Description> 542 <Attribute Name="id" AttributeDataType="xs:string"> 543 <Value>Assemble</Value> 544 </Attribute> 545 <Attribute Name="operationsType" AttributeDataType="xs:string"> 546 <Value>Production</Value> 547 </Attribute> 548 <Attribute Name="duration" AttributeDataType="xs:decimal"> 549 <Value>2</Value> 550 </Attribute> 551 <Attribute Name="durationUnitOfMeasure" AttributeDataType="xs:string"> 552 <Value>minutes</Value> 553 </Attribute> 554 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-18" 555 /> 556 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-04" /> 557 <InternalElement Name="Robot-Specification" ID="Robot-Specification"> 558 <Description> 559 Robot needed for attaching wheels to cars without wheels. 560 </Description> 561 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 562 <Value>Attach Wheels</Value> 563 </Attribute> 564 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 565 <Value>2</Value> 566 </Attribute> 567 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 568 <Value>machine minutes / piece</Value> 569 </Attribute> 570 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-14" /> 571 <InternalLink Name="a_r" RefPartnerSideA="Robot-Specification:RC" 572 RefPartnerSideB="Robot:RC" /> 573 <RoleRequirements RefBaseRoleClassPath="EquipmentSegmentSpecification" 574 /> 575 </InternalElement> 576 <InternalElement Name="Car-without-Wheels-Specification" 577 ID="Car-without-Wheels-Specification">



578 <Description> 579 The cars without wheels that are to be refined. 580 </Description> 581 <Attribute Name="materialUse" AttributeDataType="xs:string"> 582 <Value>Material Consumed</Value> 583 </Attribute> 584 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 585 <Value>1</Value> 586 </Attribute> 587 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 588 <Value>units</Value> 589 </Attribute> 590 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-15" /> 591 <InternalLink Name="a_cwow" 592 RefPartnerSideA="Car-without-Wheels-Specification:RC" 593 RefPartnerSideB="Car-without-Wheels:RC" /> 594 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 595 /> 596 </InternalElement> 597 <InternalElement Name="Wheel-Specification" ID="Wheel-Specification"> 598 <Description>The wheels that are to be attached.</Description> 599 <Attribute Name="materialUse" AttributeDataType="xs:string"> 600 <Value>Material Consumed</Value> 601 </Attribute> 602 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 603 <Value>4</Value> 604 </Attribute> 605 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 606 <Value>units</Value> 607 </Attribute> 608 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-16" /> 609 <InternalLink Name="a_w" RefPartnerSideA="Wheel-Specification:RC" 610 RefPartnerSideB="Wheel:RC" /> 611 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 612 /> 613 </InternalElement> 614 <InternalElement Name="Car-with-Wheels-Specification" 615 ID="Car-with-Wheels-Specification"> 616 <Description>The cars with wheels that are produced.</Description> 617 <Attribute Name="materialUse" AttributeDataType="xs:string"> 618 <Value>Material Produced</Value> 619 </Attribute> 620 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 621 <Value>1</Value> 622 </Attribute> 623 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 624 <Value>units</Value> 625 </Attribute> 626 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-17" /> 627 <InternalLink Name="a_cww" 628 RefPartnerSideA="Car-with-Wheels-Specification:RC" 629 RefPartnerSideB="Car-with-Wheels:RC" /> 630 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 631 /> 632 </InternalElement> 633 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 634 <InternalLink Name="A_R" RefPartnerSideA="Assemble:PPR" 635 RefPartnerSideB="Robot:PPR" /> 636 <InternalLink Name="A_CWOW" RefPartnerSideA="Assemble:PPR" 637 RefPartnerSideB="Car-without-Wheels:PPR" /> 638 <InternalLink Name="A_W" RefPartnerSideA="Assemble:PPR" 639 RefPartnerSideB="Wheel:PPR" /> 640 <InternalLink Name="A_CWW" RefPartnerSideA="Assemble:PPR" 641 RefPartnerSideB="Car-with-Wheels:PPR" /> 642 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 643 </InternalElement>



644 <InternalElement Name="Transport-3" ID="Transport-3"> 645 <Description> 646 Transport-3 is accomplished with Conveyer-2. Cars with wheels are 647 delivered from the robot to the product drain for finished 648 products. 649 </Description> 650 <Attribute Name="id" AttributeDataType="xs:string"> 651 <Value>Transport-3</Value> 652 </Attribute> 653 <Attribute Name="operationsType" AttributeDataType="xs:string"> 654 <Value>Production</Value> 655 </Attribute> 656 <Attribute Name="duration" AttributeDataType="xs:decimal"> 657 <Value>10</Value> 658 </Attribute> 659 <Attribute Name="durationUnitOfMeasure" AttributeDataType="xs:string"> 660 <Value>seconds</Value> 661 </Attribute> 662 <ExternalInterface Name="PPR" RefBaseClassPath="PPRConnector" ID="PPR-19" 663 /> 664 <ExternalInterface Name="DC" ID="DC-05" RefBaseClassPath="DC" /> 665 <InternalElement Name="Conveyer-2-Specification" 666 ID="Conveyer-2-Specification"> 667 <Description> 668 Conveyer needed for transporting cars with wheels from the robot to 669 the product drain. 670 </Description> 671 <Attribute Name="equipmentUse" AttributeDataType="xs:string"> 672 <Value>Material Movement</Value> 673 </Attribute> 674 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 675 <Value>10</Value> 676 </Attribute> 677 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 678 <Value>machine seconds / piece</Value> 679 </Attribute> 680 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-18" /> 681 <InternalLink Name="t3_c2" 682 RefPartnerSideA="Conveyer-2-Specification:RC" 683 RefPartnerSideB="Conveyer-2:RC" /> 684 <RoleRequirements RefBaseRoleClassPath="EquipmentSegmentSpecification" 685 /> 686 </InternalElement> 687 <InternalElement Name="Car-with-Wheels-Specification" 688 ID="Car-with-Wheels-Specification"> 689 <Description> 690 The cars with wheels that are to be transported. 691 </Description> 692 <Attribute Name="materialUse" AttributeDataType="xs:string"> 693 <Value>Material Moved</Value> 694 </Attribute> 695 <Attribute Name="quantity" AttributeDataType="xs:decimal"> 696 <Value>1</Value> 697 </Attribute> 698 <Attribute Name="quantityUnitOfMeasure" AttributeDataType="xs:string"> 699 <Value>units</Value> 700 </Attribute> 701 <ExternalInterface Name="RC" RefBaseClassPath="RC" ID="RC-19" /> 702 <InternalLink Name="t3_cww" 703 RefPartnerSideA="Car-with-Wheels-Specification:RC" 704 RefPartnerSideB="Car-with-Wheels:RC" /> 705 <RoleRequirements RefBaseRoleClassPath="MaterialSegmentSpecification" 706 /> 707 </InternalElement> 708 <SupportedRoleClass RefRoleClassPath="WorkCell" /> 709 <InternalLink Name="T3_C2" RefPartnerSideA="Transport-3:PPR"



710 RefPartnerSideB="Conveyer-2:PPR" /> 711 <InternalLink Name="T3_CWW" RefPartnerSideA="Transport-3:PPR" 712 RefPartnerSideB="Car-with-Wheels:PPR" /> 713 <RoleRequirements RefBaseRoleClassPath="ProcessSegment" /> 714 </InternalElement> 715 <RoleRequirements RefBaseRoleClassPath="ProcessStructure" /> 716 </InternalElement> 717 <InternalElement Name="EquipmentAssetMappings" ID="EquipmentAssetMappings"> 718 <InternalElement Name="EAM1" ID="EAM-01"> 719 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 720 <Description>The starting time of the association.</Description> 721 <Value>2017-01-01</Value> 722 </Attribute> 723 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-09" /> 724 <InternalLink Name="eam1_c1pa" RefPartnerSideB="EAM-01:EAC" 725 RefPartnerSideA="Conveyer-1-PA:EAC" /> 726 <InternalLink Name="eam1_c1" RefPartnerSideB="Conveyer-1:EAC" 727 RefPartnerSideA="EAM-01:EAC" /> 728 <RoleRequirements RefBaseRoleClassPath="EquipmentAssetMapping" /> 729 </InternalElement> 730 <InternalElement Name="EAM2" ID="EAM-02"> 731 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 732 <Description>The starting time of the association.</Description> 733 <Value>2017-01-03</Value> 734 </Attribute> 735 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-10" /> 736 <InternalLink Name="eam2_ttpa" RefPartnerSideB="EAM-02:EAC" 737 RefPartnerSideA="Turntable-PA:EAC" /> 738 <InternalLink Name="eam2_tt" RefPartnerSideB="Turntable:EAC" 739 RefPartnerSideA="EAM-02:EAC" /> 740 <RoleRequirements RefBaseRoleClassPath="EquipmentAssetMapping" /> 741 </InternalElement> 742 <InternalElement Name="EAM3" ID="EAM-03"> 743 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 744 <Description>The starting time of the association.</Description> 745 <Value>2017-01-02</Value> 746 </Attribute> 747 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-11" /> 748 <InternalLink Name="eam3_c2pa" RefPartnerSideB="EAM-03:EAC" 749 RefPartnerSideA="Conveyer-2-PA:EAC" /> 750 <InternalLink Name="eam3_c2" RefPartnerSideB="Conveyer-2:EAC" 751 RefPartnerSideA="EAM-03:EAC" /> 752 <RoleRequirements RefBaseRoleClassPath="EquipmentAssetMapping" /> 753 </InternalElement> 754 <InternalElement Name="EAM4" ID="EAM-04"> 755 <Attribute Name="startTime" AttributeDataType="xs:dateTime"> 756 <Description>The starting time of the association.</Description> 757 <Value>2017-01-04</Value> 758 </Attribute> 759 <ExternalInterface Name="EAC" RefBaseClassPath="EAC" ID="EAC-12" /> 760 <InternalLink Name="eam4_rpa" RefPartnerSideB="EAM-04:EAC" 761 RefPartnerSideA="Robot-PA:EAC" /> 762 <InternalLink Name="eam4_r" RefPartnerSideB="Robot:EAC" 763 RefPartnerSideA="EAM-04:EAC" /> 764 <RoleRequirements RefBaseRoleClassPath="EquipmentAssetMapping" /> 765 </InternalElement> 766 <RoleRequirements RefBaseRoleClassPath="BR" /> 767 </InternalElement> 768 <InternalElement Name="ProcessSegmentDependencies" 769 ID="ProcessSegmentDependencies"> 770 <InternalElement Name="Turn-after-Transport-1" 771 ID="Turn-after-Transport-1-Dependency"> 772 <Description>Turn after Transport-1</Description> 773 <Attribute Name="dependency" AttributeDataType="xs:string"> 774 <Value>Start Turn after Transport-1 end</Value> 775 </Attribute>



776 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-06" /> 777 <InternalLink Name="dc_t1" 778 RefPartnerSideA="Turn-after-Transport-1-Dependency:DC" 779 RefPartnerSideB="Transport-1:DC" /> 780 <InternalLink Name="dc_t" 781 RefPartnerSideA="Turn-after-Transport-1-Dependency:DC" 782 RefPartnerSideB="Turn:DC" /> 783 <RoleRequirements RefBaseRoleClassPath="ProcessSegmentDependency" /> 784 </InternalElement> 785 <InternalElement Name="Transport-2-after-Turn" ID="Transport-2-after-Turn"> 786 <Description>Transport-2 after Turn</Description> 787 <Attribute Name="dependency" AttributeDataType="xs:string"> 788 <Value>Start Transport-2 after Turn end</Value> 789 </Attribute> 790 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-07" /> 791 <InternalLink Name="dc_t" RefPartnerSideA="Transport-2-after-Turn:DC" 792 RefPartnerSideB="Turn:DC" /> 793 <InternalLink Name="dc_t2" RefPartnerSideA="Transport-2-after-Turn:DC" 794 RefPartnerSideB="Transport-2:DC" /> 795 <RoleRequirements RefBaseRoleClassPath="ProcessSegmentDependency" /> 796 </InternalElement> 797 <InternalElement Name="Assemble-after-Transport-2" 798 ID="Assemble-after-Transport-2"> 799 <Description>Assemble after Transport-2</Description> 800 <Attribute Name="dependency" AttributeDataType="xs:string"> 801 <Value>Start Assemble after Transport-2 end</Value> 802 </Attribute> 803 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-08" /> 804 <InternalLink Name="dc_t2" RefPartnerSideA="Assemble-after-Transport-2:DC" 805 RefPartnerSideB="Transport-2:DC" /> 806 <InternalLink Name="dc_a" RefPartnerSideA="Assemble-after-Transport-2:DC" 807 RefPartnerSideB="Assemble:DC" /> 808 <RoleRequirements RefBaseRoleClassPath="ProcessSegmentDependency" /> 809 </InternalElement> 810 <InternalElement Name="Transport-3-after-Assemble" 811 ID="Transport-3-after-Assemble"> 812 <Description>Transport-3 after Assemble</Description> 813 <Attribute Name="dependency" AttributeDataType="xs:string"> 814 <Value>Start Transport-3 after Assemble end</Value> 815 </Attribute> 816 <ExternalInterface Name="DC" RefBaseClassPath="DC" ID="DC-09" /> 817 <InternalLink Name="dc_a" RefPartnerSideA="Transport-3-after-Assemble:DC" 818 RefPartnerSideB="Assemble:DC" /> 819 <InternalLink Name="dc_t3" RefPartnerSideA="Transport-3-after-Assemble:DC" 820 RefPartnerSideB="Transport-3:DC" /> 821 <RoleRequirements RefBaseRoleClassPath="ProcessSegmentDependency" /> 822 </InternalElement> 823 <RoleRequirements RefBaseRoleClassPath="BR" /> 824 </InternalElement> 825 </InstanceHierarchy> 826 <RoleClassLib Name="IEC62264-PPR-RCL"> 827 <Version>1.0.0</Version> 828 <RoleClass Name="EquipmentClasses" RefBaseClassPath="ResourceStructure"> 829 <RoleClass Name="Conveyer-Class" RefBaseClassPath="EquipmentClass"> 830 <Description> 831 Conveyers of all kind belong to the Conveyer equipment class. 832 </Description> 833 <Attribute Name="id" AttributeDataType="xs:string"> 834 <Value>Conveyer-Class</Value> 835 </Attribute> 836 </RoleClass> 837 <RoleClass Name="Turntable-Class" RefBaseClassPath="EquipmentClass"> 838 <Description> 839 Turntables of all kind belong to the Turntable equipment class. 840 </Description> 841 <Attribute Name="id" AttributeDataType="xs:string">



842 <Value>Turntable-Class</Value> 843 </Attribute> 844 </RoleClass> 845 <RoleClass Name="Robot-Class" RefBaseClassPath="EquipmentClass"> 846 <Description> 847 Robots of all kind belong to the Robot equipment class. 848 </Description> 849 <Attribute Name="id" AttributeDataType="xs:string"> 850 <Value>Robot-Class</Value> 851 </Attribute> 852 </RoleClass> 853 </RoleClass> 854 <RoleClass Name="MaterialClasses" RefBaseClassPath="ProductStructure"> 855 <RoleClass Name="Car-without-Wheels-Class" RefBaseClassPath="MaterialClass"> 856 <Description> 857 Cars without wheels of all kind belong to the Car-without-Wheels 858 material class. 859 </Description> 860 <Attribute Name="id" AttributeDataType="xs:string"> 861 <Value>Car-without-Wheels-Class</Value> 862 </Attribute> 863 </RoleClass> 864 <RoleClass Name="Wheel-Class" RefBaseClassPath="MaterialClass"> 865 <Description> 866 Wheels of all kind belong to the Wheel material class. 867 </Description> 868 <Attribute Name="id" AttributeDataType="xs:string"> 869 <Value>Wheel-Class</Value> 870 </Attribute> 871 </RoleClass> 872 <RoleClass Name="Car-with-Wheels-Class" RefBaseClassPath="MaterialClass"> 873 <Description> 874 Cars with wheels of all kind belong to the Car-with-Wheels material 875 class. 876 </Description> 877 <Attribute Name="id" AttributeDataType="xs:string"> 878 <Value>Car-with-Wheels-Class</Value> 879 </Attribute> 880 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 881 <Value>Physical</Value> 882 </Attribute> 883 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 884 <Value>Permanent</Value> 885 </Attribute> 886 </RoleClass> 887 </RoleClass> 888 </RoleClassLib> 889 <SystemUnitClassLib Name="IEC62264-PPR-SUC"> 890 <Description> 891 Integration of IEC 62264 information by modeling complete IEC 62264 892 structures within AML. 893 </Description> 894 <Version>1.0.0</Version> 895 <SystemUnitClass Name="PhysicalAssetClasses"> 896 <SupportedRoleClass RefRoleClassPath="ResourceStructure" /> 897 <SystemUnitClass Name="Short-Conveyer-PA-Class"> 898 <Description>The short conveyer of Conveyer Manufacturer.</Description> 899 <Attribute Name="id" AttributeDataType="xs:string"> 900 <Value>Short-Conveyer-PA-Class</Value> 901 </Attribute> 902 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 903 <Value>Conveyer Manufacturer</Value> 904 </Attribute> 905 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 906 </SystemUnitClass> 907 <SystemUnitClass Name="Long-Conveyer-PA-Class">



908 <Description>The long conveyer of Conveyer Manufacturer.</Description> 909 <Attribute Name="id" AttributeDataType="xs:string"> 910 <Value>Long-Conveyer-PA-Class</Value> 911 </Attribute> 912 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 913 <Value>Conveyer Manufacturer</Value> 914 </Attribute> 915 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 916 </SystemUnitClass> 917 <SystemUnitClass Name="Turntable-PA-Class"> 918 <Description> 919 The high end turntable of Turntable Manufacturer. 920 </Description> 921 <Attribute Name="id" AttributeDataType="xs:string"> 922 <Value>Turntable-PA-Class</Value> 923 </Attribute> 924 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 925 <Value>Turntable Manufacturer</Value> 926 </Attribute> 927 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 928 </SystemUnitClass> 929 <SystemUnitClass Name="Robot-PA-Class"> 930 <Description>The only robot of Robot Manufacturer.</Description> 931 <Attribute Name="id" AttributeDataType="xs:string"> 932 <Value>Robot-PA-Class</Value> 933 </Attribute> 934 <Attribute Name="manufacturer" AttributeDataType="xs:string"> 935 <Value>Robot Manufacturer</Value> 936 </Attribute> 937 <SupportedRoleClass RefRoleClassPath="PhysicalAssetClass" /> 938 </SystemUnitClass> 939 </SystemUnitClass> 940 <SystemUnitClass Name="MaterialDefinitions"> 941 <SupportedRoleClass RefRoleClassPath="ProductStructure" /> 942 <SystemUnitClass Name="Car-without-Wheels" ID="Car-without-Wheels"> 943 <Description>A car that has no wheels attached.</Description> 944 <Attribute Name="id" AttributeDataType="xs:string"> 945 <Value>Car-without-Wheels</Value> 946 </Attribute> 947 <SupportedRoleClass RefRoleClassPath="MaterialDefinition" /> 948 <SupportedRoleClass 949 RefRoleClassPath= 950 "IEC62264-PPR-RCL/MaterialClasses/Car-without-Wheels-Class" /> 951 </SystemUnitClass> 952 <SystemUnitClass Name="Wheel" ID="Wheel"> 953 <Description>A wheel that is to be attached to a car.</Description> 954 <Attribute Name="id" AttributeDataType="xs:string"> 955 <Value>Wheel</Value> 956 </Attribute> 957 <SupportedRoleClass RefRoleClassPath="MaterialDefinition" /> 958 <SupportedRoleClass 959 RefRoleClassPath="IEC62264-PPR-RCL/MaterialClasses/Wheel-Class" /> 960 </SystemUnitClass> 961 <SystemUnitClass Name="Car-with-Wheels" ID="Car-with-Wheels"> 962 <Description>A car with wheels attached.</Description> 963 <Attribute Name="id" AttributeDataType="xs:string"> 964 <Value>Car-with-Wheels</Value> 965 </Attribute> 966 <Attribute Name="assemblyType" AttributeDataType="xs:string"> 967 <Value>Physical</Value> 968 </Attribute> 969 <Attribute Name="assemblyRelationship" AttributeDataType="xs:string"> 970 <Value>Permanent</Value> 971 </Attribute> 972 <SupportedRoleClass RefRoleClassPath="MaterialDefinition" /> 973 <SupportedRoleClass



974 RefRoleClassPath= 975 "IEC62264-PPR-RCL/MaterialClasses/Car-with-Wheels-Class" /> 976 </SystemUnitClass> 977 </SystemUnitClass> 978 </SystemUnitClassLib>