7 AutomationML Libraries OPC UA Model

7.1 General

The property ID of the ObjectType nodes describes a unique identifier.

The property Version of the ObjectType nodes consists of organizational information about the state of the version.

7.2 AutomationMLInterfaceClassLib

7.2.1 Instances

7.2.1.1 AutomationMLInterfaceClassLib

This Instance is a child of InterfaceClassLibs. It is defined in Table 27.

It consists of the Standard AutomationML Interface Class Library (Part 1). The content is extended with Part 3 and Part 4 of the AutomationML standard specification.

7.2.2 ObjectTypes

7.2.2.1 AutomationMLBaseInterface

7.2.2.1.1 General

The interface class “AutomationMLBaseInterface” is a base abstract interface type and shall be used as parent for the description of all AML interface classes.

7.2.2.1.2 ObjectType Definition

The AutomationMLBaseInterface is formally defined in Table 28.

7.2.2.2 AttachmentInterface

7.2.2.2.1 General

The interface class “AttachmentInterface” shall be used to denote a geometrical connection point of an AutomationML object.

7.2.2.2.2 ObjectType Definition

The AttachmentInterface is formally defined in Table 29.

7.2.2.3 Communication

7.2.2.3.1 General

The interface class “Communication” shall be used for the description of communication related interfaces.

7.2.2.3.2 ObjectType Definition

The Communication is formally defined in Table 30.

7.2.2.4 SignalInterface

7.2.2.4.1 General

The interface class “SignalInterface” shall be used for modelling signals.

7.2.2.4.2 ObjectType Definition

The SignalInterface is formally defined in Table 31.

7.2.2.5 ExternalDataConnector

7.2.2.5.1 General

The interface class “ExternalDataConnector” is a basic abstract interface type and shall be used for the description of connector interfaces referencing external docu¬ments. The classes “COLLADAInterface” and “PLCopenXMLInterface” are derived from this class. All existing and future connector classes shall be derived directly or indirectly from this class.

7.2.2.5.2 ObjectType Definition

The ExternalDataConnector is formally defined in Table 32.

7.2.2.5.3 ObjectType Description

7.2.2.5.3.1 refURI

The attribute “refURI” shall be used in order to store the path to the reference external document.

7.2.2.6 COLLADAInterface

7.2.2.6.1 General

The interface class “COLLADAInterface” shall be used in order to reference external COLLADA documents and to publish interfaces that are defined inside an external COLLADA document. Details are intended to be specified in IEC 62714-3.

7.2.2.6.2 ObjectType Definition

The COLLADAInterface is formally defined in Table 33.

7.2.2.6.3 ObjectType Description

7.2.2.7 PLCopenXMLInterface

7.2.2.7.1 General

The interface class “PLCopenXMLInterface” shall be used in order to reference external PLCOpenXML documents and to publish interfaces that are defined inside an external PLCOpenXML document. Details are intended to be specified in IEC 62714-3.

7.2.2.7.2 ObjectType Definition

The PLCopenXMLInterface is formally defined in Table 34.

7.2.2.8 LogicInterface

7.2.2.8.1 General

The interface class “LogicInterface” shall be used in order to reference a logic description within an external PLCopen XML document.

7.2.2.8.2 ObjectType Definition

The LogicInterface is formally defined in Table 35.

7.2.2.9 VariableInterface

7.2.2.9.1 General

The interface class “VariableInterface” shall be used in order to reference variables in external PLCopen XML document.

7.2.2.9.2 ObjectType Definition

The VariableInterface is formally defined in Table 36.

7.2.2.10 InterlockingVariableInterface

7.2.2.10.1 General

The interface class “InterlockingVariableInterface” shall be used in order to reference variables representing an interlocking condition in external PLCopen XML document.

7.2.2.10.2 ObjectType Definition

The InterlockingVariableInterface is formally defined in Table 37.

7.2.2.10.3 ObjectType Description

7.2.2.10.3.1 SafeConditionEquals

SafeConditionEquals indicates which value of the reference variable indicates a save state. Values are

“TRUE”: indicates that the value “TRUE” of the variable within the PLCopen XML description represents the safe state of the signal group.

“FALSE”: indicates that the value “FALSE” of the variable within the PLCopen XML description represents the safe state of the signal group.

Note: Use of the attribute is optional, default value is TRUE

7.2.2.11 InterlockingConnector

7.2.2.11.1 General

The interface class “InterlockingConnector” shall be used in order to model relations between signal groups and component groups.

7.2.2.11.2 ObjectType Definition

The InterlockingConnector is formally defined in Table 38.

7.2.2.11.3 ObjectType Description

7.2.2.12 Order

7.2.2.12.1 General

The interface class “Order” is an abstract class that shall be used for the description of orders, e.g. a successor or a predecessor.

7.2.2.12.2 ObjectType Definition

The Order is formally defined in Table 39.

7.2.2.12.3 ObjectType Description

7.2.2.12.3.1 Direction

The attribute “Direction” shall be used in order to specify the direction. Permitted values are “In”, “Out” or “InOut”.

7.2.2.13 PortConnector

7.2.2.13.1 General

The interface class “PortConnector” shall be used in order to provide a high level relation between ports.

7.2.2.13.2 ObjectType Definition

The PortConnector is formally defined in Table 40.

7.2.2.14 PPRConnector

7.2.2.14.1 General

The interface class “PPRConnector” shall be used in order to provide a relation between resources, products and processes.

7.2.2.14.2 ObjectType Definition

The PPRConnector is formally defined in Table 41.

7.2.2.14.2.1 ObjectTypes

7.3 AutomationMLBaseRoleClassLib

7.3.1 Instances

7.3.1.1 AutomationMLBaseRoleClassLib

This Instance is a child of RoleClassLibs. It is defined in Table 42.

It consists of the Standard AutomationML Base Role Class Library (Part 1). The content is extended with Part 3 and Part 4 of the AutomationML standard specification.

7.3.2 ObjectTypes

7.3.2.1 AutomationMLBaseRoleClassLib

7.3.2.1.1 General

The role class “AutomationMLBaseRole” is a basic abstract role type and the base class for all standard or user-defined role classes.

7.3.2.1.2 ObjectType Definition

The AutomationMLBaseRole is formally defined in Table 43.

7.3.2.2 Group

7.3.2.2.1 General

The role class “Group” is a role type for objects that serve for the grouping of mirror objects that belong together from a certain engineering perspective. AML Group objects shall reference this role.

7.3.2.2.2 ObjectType Definition

The Group is formally defined in Table 44.

7.3.2.2.3 ObjectType Description

7.3.2.2.3.1 AssociatedFacet

The attribute “AssociatedFacet” shall be used for the definition of the name of the corresponding Facet. Example: AssociatedFacet = “PLCFacet”

7.3.2.3 Facet

7.3.2.3.1 General

The role class “Facet” is a role type for objects that serve as sub-view on attributes or interfaces of an AML object. AML Facet objects shall reference this role. Details and examples are specified in 8.3.

7.3.2.3.2 ObjectType Definition

The Facet is formally defined in Table 45

7.3.2.4 Port

7.3.2.4.1 General

The role class “Port” is a role type for objects that groups a number of interfaces and allows describing complex interfaces in this way. AML Port objects shall reference this role. Details and examples are specified in 8.2.

7.3.2.4.2 ObjectType Definition

The Port is formally defined in Table 46.

7.3.2.4.3 ObjectType Description

7.3.2.4.3.1 Cardinality

This attribute is a complex attribute which can describe MaxOccur or MinOccur.

7.3.2.4.3.2 Category

The category attribute describes the Port type. The value of this attribute is user-defined. Only ports with the same category value are allowed to be connected. Example: category = “MaterialFlow”

7.3.2.4.3.3 ConnectionPoint

This CAEX Interface allows connecting this Port with a number of other ports on an abstract level. The internal relations between single Port interfaces are not described in this way.

7.3.2.4.3.4 Direction

This attribute shall be used to describe the direction of the Port. Values shall be one of the following: “In” or “Out” or “InOut”. Ports with the direction “In” can only be connected to ports with the direction “Out” or “InOut” and ports with the direction “Out” can only be connected with ports with the direction “In” or “InOut”. Ports with the direction “InOut” can be connected to Ports of arbitrary direction. Examples: Direction =”Out” (e.g. a plug) Direction = “In” (e.g. a socket) Direction = “InOut” This information can be used e.g. in order to prove the validity of a connection.

7.3.2.5 Resource

7.3.2.5.1 General

The role class “Resource” is a basic abstract role type and the base class for all AML resource roles. It describes plants, equipment or other production resources. AML resource objects shall directly or indirectly reference this role.

7.3.2.5.2 ObjectType Definition

The Resource is formally defined in Table 47

7.3.2.6 Product

7.3.2.6.1 General

The role class “Product” is a 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. AML product objects shall directly or indirectly reference this role.

7.3.2.6.2 ObjectType Definition

The Product is formally defined in Table 48.

7.3.2.7 Process

7.3.2.7.1 General

The role class “Process” is a basic abstract role type and the base class for all AML process roles. It describes production related processes. AML process objects shall directly or indirectly reference this role.

7.3.2.7.2 ObjectType Definition

The Process is formally defined in Table 49.

7.3.2.8 Structure

7.3.2.8.1 General

The role class “Structure” is a 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. AML structure objects shall directly or indirectly reference this role.

7.3.2.8.2 ObjectType Definition

The Structure is formally defined in Table 50.

7.3.2.9 ResourceStructure

7.3.2.9.1 General

The role class “ResourceStructure” is an abstract role type for a resource oriented object hierarchy. AML resource structure objects shall directly or indirectly reference this role

7.3.2.9.2 ObjectType Definition

The ResourceStructure is formally defined in Table 51.

7.3.2.10 ProductStructure

7.3.2.10.1 General

The role class “ProductStructure” is an abstract role type for a product oriented object hierarchy. AML product structure objects shall directly or indirectly reference this role.

7.3.2.10.2 ObjectType Definition

The ProductStructure is formally defined in Table 52.

7.3.2.11 ProcessStructure

7.3.2.11.1 General

The role class “ProcessStructure” is an abstract role type for a process oriented object hierarchy. AML process structure objects shall directly or indirectly reference this role.

7.3.2.11.2 ObjectType Definition

The ProcessStructure is formally defined in Table 53.

7.3.2.12 Frame

7.3.2.12.1 General

The role class “Frame” denotes a distinct coordinate system. This coordinate system is explicitly accentuated for special usage.

7.3.2.12.2 ObjectType Definition

The Frame is formally defined in Table 54.

7.3.2.13 ComponentGroup

7.3.2.13.1 General

The role class “ComponentGroup” is a role type for objects that group objects belonging to one component group according to the interlocking definition of AutomationML.

7.3.2.13.2 ObjectType Definition

The ComponentGroup is formally defined in Table 55.

7.3.2.14 SignalGroup

7.3.2.14.1 General

The role class “SignalGroup” is a role type for objects that group objects belonging to one signal group according to the interlocking definition of AutomationML.

7.3.2.14.2 ObjectType Definition

The SignalGroup is formally defined in Table 56.

7.3.2.15 PropertySet

7.3.2.15.1 General

The role class “PropertySet” is an abstract role type that serves for the definition of sets of properties corresponding to a certain engineering aspect. AML property set objects shall directly or indirectly reference this role.

7.3.2.15.2 ObjectType Definition

The PropertySet is formally defined in Table 57.

7.4 AutomationMLDMIRoleClassLib

7.4.1 Instances

7.4.1.1 AutomationMLDMIRoleClassLib

This Instance is a child of RoleClassLibs. It is defined in Table 58.

It consists of the AutomationML Discrete Manufacturing Industry Role Class Library.

7.4.2 ObjectTypes

7.4.2.1 DiscManufacturingEquipment

7.4.2.1.1 General

The role class “DiscManufacturingEquipment” shall be used for equipment related to discrete manufacturing industries.

7.4.2.1.2 ObjectType Definition

The DiscManufacturingEquipment is formally defined in Table 59.

7.4.2.2 Transport

7.4.2.2.1 General

The role class “Transport” shall be used for equipment that performs transport processes to transfer items.

7.4.2.2.2 ObjectType Definition

The Transport is formally defined in Table 60.

7.4.2.3 Storage

7.4.2.3.1 General

The role class “Storage” shall be used for 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.

7.4.2.3.2 ObjectType Definition

The Storage is formally defined in Table 61.

7.4.2.4 Fixture

7.4.2.4.1 General

The role class “Fixture” shall be used for equipment that reduces the degrees of freedom of an item.

7.4.2.4.2 ObjectType Definition

The Fixture is formally defined in Table 62.

7.4.2.5 Gate

7.4.2.5.1 General

The role class “Gate” shall be used for equipment that can block or monitor an entrance, departure, or a passage way.

7.4.2.5.2 ObjectType Definition

The Gate is formally defined in Table 63.

7.4.2.6 Robot

7.4.2.6.1 General

The role class “Robot” shall be used for robots.

7.4.2.6.2 ObjectType Definition

The Robot is formally defined in Table 64.

7.4.2.7 Tool

7.4.2.7.1 General

The role class “Tool” shall be used for equipment used by resources that is necessary to or aids in the performance of an operation on the product.

7.4.2.7.2 ObjectType Definition

The Tool is formally defined in Table 65.

7.4.2.8 Carrier

7.4.2.8.1 General

The role class “Carrier” shall be used for transport equipment that carries items.

7.4.2.8.2 ObjectType Definition

The Carrier is formally defined in Table 66.

7.4.2.9 Machine

7.4.2.9.1 General

The role class “Machine” shall be used for mechanic or mechatronic equipment that creates added value on products and is designed expressly to perform specific tasks.

7.4.2.9.2 ObjectType Definition

The Machine is formally defined in Table 67.

7.4.2.10 StaticObject

7.4.2.10.1 General

The role class “StaticObject” shall be used for passive, static items positioned in the production environment.

7.4.2.10.2 ObjectType Definition

The StaticObject is formally defined in Table 68.

7.5 AutomationMLCMIRoleClassLib

7.5.1 Instances

7.5.1.1 AutomationMLCMIRoleClassLib

This Instance is a child of RoleClassLibs. It is defined in Table 69.

It consists of the AutomationML Continuous Manufacturing Industry Role Class Library.

7.5.2 ObjectTypes

7.5.2.1 ContManufacturingEquipment

7.5.2.1.1 General

The role class “ContManufacturingEquipment” shall be used for equipment related to continuous manufacturing industries.

7.5.2.1.2 ObjectType Definition

The ContManufacturingEquipment is formally defined in Table 70.

7.6 AutomationMLBMIRoleClassLib

7.6.1 Instances

7.6.1.1 AutomationMLBMIRoleClassLib

This Instance is a child of RoleClassLibs. It is defined in Table 71.

It consists of the AutomationML Batch Manufacturing Industry Role Class Library.

7.6.2 ObjectTypes

7.6.2.1 BatchManufacturingEquipment

7.6.2.1.1 General

The role class “BatchManufacturingEquipment” shall be used for equipment related to batch manufacturing industries.

7.6.2.1.2 ObjectType Definition

The BatchManufacturingEquipment is formally defined in Table 72.

7.7 AutomationMLCSRoleClassLib

7.7.1 Instances

7.7.1.1 AutomationMLCSRoleClassLib

This Instance is a child of RoleClassLibs. It is defined in Table 73.

It consists of the AutomationML Control Industry Role Class Library.

7.7.2 ObjectTypes

7.7.2.1 ControlEquipment

7.7.2.1.1 General

The role class “ControlEquipment” shall be used for equipment related to a control system. ControlEquipment can be used for every type of industry.

7.7.2.1.2 ObjectType Definition

The ControlEquipment is formally defined in Table 74.

7.7.2.2 Communication

7.7.2.2.1 General

7.7.2.2.2 ObjectType Definition

The Communication is formally defined in Table 75.

7.7.2.3 ControlHardware

7.7.2.3.1 General

The role class “ControlHardware” shall be used for hardware that provides runtime environments.

7.7.2.3.2 ObjectType Definition

The ControlHardware is formally defined in Table 76.

7.7.2.4 PC

7.7.2.4.1 General

The role class “PC” shall be used for any general-purpose computer that provides runtime environments for software being executed on it.

7.7.2.4.2 ObjectType Definition

The PC is formally defined in Table 77.

7.7.2.5 IPC

7.7.2.5.1 General

The role class “IPC” shall be used for any PC-based computing platform for industrial applications that provides runtime environments for software being executed on it.

7.7.2.5.2 ObjectType Definition

The IPC is formally defined in Table 78.

7.7.2.6 Handheld

7.7.2.6.1 General

The role class “Handheld” shall be used for any portable, programmable, electronic device with an own power supply for particular applications.

7.7.2.6.2 ObjectType Definition

The Handheld is formally defined in Table 79.

7.7.2.7 EmbeddedDevice

7.7.2.7.1 General

The role class “EmbeddedDevice” shall be used for any device designed to perform one or a few dedicated software functions. It is embedded as part of a complete device often including hardware and mechanical parts.

7.7.2.7.2 ObjectType Definition

The EmbeddedDevice is formally defined in Table 80.

7.7.2.8 Sensor

7.7.2.8.1 General

The role class “Sensor” shall be used for sensors.

7.7.2.8.2 ObjectType Definition

The Sensor is formally defined in Table 81.

7.7.2.9 Actuator

7.7.2.9.1 General

The role class “Actuator” shall be used for actuators.

7.7.2.9.2 ObjectType Definition

The Actuator is formally defined in Table 82.

7.7.2.10 Controller

7.7.2.10.1 General

The role class “Controller” shall be used for self-acting functionalities that process signals according to a predefined logic and generate output signals in order to reach an intended behaviour of technical processes.

7.7.2.10.2 ObjectType Definition

The Controller is formally defined in Table 83.

7.7.2.11 PLC

7.7.2.11.1 General

The role class “PLC” shall be used for programmable control functionality focusing the processing of signals.

7.7.2.11.2 ObjectType Definition

The PLC is formally defined in Table 84.

7.7.2.12 NC

7.7.2.12.1 General

The role class “NC” shall be used for programmable control functionality focusing the processing of numerical signals.

7.7.2.12.2 ObjectType Definition

The NC is formally defined in Table 85.

7.7.2.13 RC

7.7.2.13.1 General

The role class “RC” shall be used for programmable control functionality driving robots in order to reach an intended behaviour of the robot kinematic system and corresponding connected periphery.

7.7.2.13.2 ObjectType Definition

The RC is formally defined in Table 86.

7.7.2.14 PAC

7.7.2.14.1 General

The role class “PAC” shall be used for programmable automation functionality focusing on cross-domain functionality like binary, motion and continuous control.

7.7.2.14.2 ObjectType Definition

The PAC is formally defined in Table 87.

7.8 AutomationMLExtendedRoleClassLib

7.8.1 Instances

7.8.1.1 AutomationMLExtendedRoleClassLib

This Instance is a child of RoleClassLibs. It is defined in Table 88.

The AutomationMLExtendedRoleClassLibrary is a recommended extension of the AutomationMLBaseRoleClassLib and the AutomationMLDMIRoleClassLib and covers a wide area of typical roles of the discrete manufacturing industry.

7.8.2 ObjectTypes

7.8.2.1 PLCFacet

7.8.2.1.1 General

The role class “PLCFacet” should be used for the view concerning everything involved in PLC control code generators: PLC view on AML objects which points to information concerning PLC.

7.8.2.1.2 ObjectType Definition

The PLCFacet is formally defined in Table 89.

7.8.2.2 HMIFacet

7.8.2.2.1 General

The role class “HMIFacet” should be used for the view concerning everything involved in HMI: HMI view on AML objects which points to information concerning HMI.

7.8.2.2.2 ObjectType Definition

The HMIFacet is formally defined in Table 90.

7.8.2.3 Enterprise

7.8.2.3.1 General

The role class “Enterprise” should be used for business structures. The definition of an “Enterprise” is given in IEC 62264-1:2013, 5.3.2: “An enterprise is a collection of sites and areas and represents the top level of a role based equipment hierarchy. The enterprise is responsible for determining what products will be manufactured, at which sites they will be manufactured, and in general how they will be manufactured. Level 4 functions are generally concerned with the enterprise and site levels. However, enterprise planning and scheduling may involve areas, work centers, or work units within an area.”

7.8.2.3.2 ObjectType Definition

The Enterprise is formally defined in Table 91.

7.8.2.4 Site

7.8.2.4.1 General

The role class “Site” should be used for localisation. It is also used for hierarchical organization. The definition of a “Site” is given in IEC 62264-1:2013, 5.3.3: “A site is a physical, geographical, or logical grouping determined by the enterprise. It may contain areas, production lines, process cells, and production units. Site planning and scheduling may involve cells, lines, or units within the areas. A geographical location and main production capability usually identifies a site. Examples of site identifications are ‘Deer Park Olefins Plant’ and ‘Johnson City Manufacturing Facility’. Sites are often used for rough-cut planning and scheduling. Sites generally have well-defined manufacturing capabilities.

7.8.2.4.2 ObjectType Definition

The Site is formally defined in Table 92.

7.8.2.5 Area

7.8.2.5.1 General

The role class “Area” should be used for production buildings and their subdivisions (structure/hall), used for hierarchical organization. The definition of an “Area” is given in IEC 62264-1:2013, 5.3.4: “An area is a physical, geographical, or logical grouping determined by the site. It may contain process cells, production units, and production lines. The main production capability and geographical location within a site usually identify areas. Examples of area identifications are ‘North End Tank Farm’ and ‘Building 2 Electronic Assembly’. Areas generally have well-defined manufacturing capabilities and capacities. The capabilities and capacities are used for planning and scheduling. An area is made up of lower-level elements that perform the manufacturing functions. There are three types of elements defined that correspond to continuous manufacturing models, discrete (repetitive and nonrepetitive) manufacturing models, and batch manufacturing models. An area may have one or more of any of the lower-level elements depending upon the manufacturing requirements. Many areas will have a combination of production lines for the discrete operations, production units for the continuous processes, and process cells for batch processes. For example, a beverage manufacturer may have an area with continuous mixing in a production unit, which feeds a batch process cell for batch processing, feeding a bottling line for a discrete bottling process.”

7.8.2.5.2 ObjectType Definition

The Area is formally defined in Table 93.

7.8.2.6 ProductionLine

7.8.2.6.1 General

The role class “ProductionLine” should be used for defining the role based equipment hierarchy defined in IEC 62264-1:2013, 5.3.7, for discrete manufacturing at the work cell level: “Production lines and work cells are the lowest level of equipment. Work cells are usually only identified when there is flexibility in the routing of work within a production line. Production lines and work cells may be composed of lower-level elements, but definitions of these are outside the scope of this document. The major processing activity often identifies the production line. Examples of production line identifications are ‘Bottling Line #1’, ‘Capping Line #15’, and ‘Water Pump Assembly Line #4’. Production line and work cells have well-defined manufacturing capabilities and throughput capacities.”

7.8.2.6.2 ObjectType Definition

The ProductionLine is formally defined in Table 94.

7.8.2.7 WorkCell

7.8.2.7.1 General

The role class “WorkCell” should be used for defining the role based equipment hierarchy defined in IEC 62264-1:2013 at the work cell level: for sub units/sub production steps of units/production lines, station, processes single component, cycle, location in which the production step takes place. It is used for hierarchization. The definition of a “WorkCell” is given in IEC 62264-1:2013, 5.3.7: “Production lines and work cells are the lowest level of equipment. Work cells are usually only identified when there is flexibility in the routing of work within a production line. Production lines and work cells may be composed of lower-level elements, but definitions of these are outside the scope of this document. The major processing activity often identifies the production line. Examples of production line identifications are ‘Bottling Line #1’, ‘Capping Line #15’, and ‘Water Pump Assembly Line #4’. Production line and work cells have well-defined manufacturing capabilities and throughput capacities.”

7.8.2.7.2 ObjectType Definition

The WorkCell is formally defined in Table 95.

7.8.2.8 ProcessCell

7.8.2.8.1 General

The role class “ProcessCell” should be used for sub units/sub production steps of units/production lines, station, processes single component, cycle, location in which the production step takes place. It is used for hierarchization. The definition of a “ProcessCell” is given in IEC 62264-1:2013, 5.3.8: “Process cells and units are the lowest level of equipment for batch manufacturing processes. Units are usually only identified if there is flexibility in the routing of product within a process cell. The definitions for process cells and units are contained in the IEC 61512-1 standard. The major processing capability or family of products produced often identifies the process cell. Examples of process cell identifications are ‘Mixing Line #5’ and ‘Detergent Line 13’. Process cells and units have well-defined manufacturing capabilities and batch capacities.”

7.8.2.8.2 ObjectType Definition

The ProcessCell is formally defined in Table 96.

7.8.2.9 Unit

7.8.2.9.1 General

The role class “Unit” should be used for linked chained production plants. It is used for hierarchization. The definition of a “Unit” is given in IEC 62264-1:2013, 5.3.8: “Process cells and units are the lowest level of equipment for batch manufacturing processes. Units are usually only identified if there is flexibility in the routing of product within a process cell. The definitions for process cells and units are contained in the IEC 61512-1 standard. The major processing capability or family of products produced often identifies the process cell. Examples of process cell identifications are ‘Mixing Line #5’ and ‘Detergent Line 13’. Process cells and units have well-defined manufacturing capabilities and batch capacities.”

7.8.2.9.2 ObjectType Definition

The Unit is formally defined in Table 97.

7.8.2.10 ProductionUnit

7.8.2.10.1 General

The role class “ProductionUnit” should be used for sub units/sub production steps of units/production lines, station, processes single component, cycle, location in which the production step takes place. It is used for hierarchization. The definition of a “ProductionUnit” is given in IEC 62264-1:2013, 5.3.6: “Production units are the lowest level of equipment for continuous manufacturing processes. Production units are composed of lower level elements, such as equipment modules, sensors, and actuators, but definitions of these are outside the scope of the IEC 62714 series. A production unit generally encompasses all of the equipment required for a segment of continuous production that operates in a relatively autonomous manner. It generally converts, separates, or reacts to one or more feedstocks to produce intermediate or final products. The major processing activity or product generated often identifies the production unit. Examples of production unit identifications are ‘Catalytic Cracker #1’ and ‘Alkylation Unit 2’. Production units have well-defined processing capabilities and throughput capacities.”

7.8.2.10.2 ObjectType Definition

The ProductionUnit is formally defined in Table 98.

7.8.2.11 StorageZone

7.8.2.11.1 General

The role class “StorageZone” should be used defining the role based equipment hierarchy defined in IEC 62264-1:2013 at the storage zone level: The definition of an “StorageZone” is given in IEC 62264-1: 2013, 5.3.9: “Storage zones and storage units are the lowest level of material movement equipment typically scheduled by the Level 4 and Level 3 functions for discrete, batch and continuous manufacturing processes. A storage zone is a type of work center and a storage unit is a type of work unit that is organized as elements within an area. These are the lower-level elements of an equipment hierarchy used in material storage and movement activities. A storage zone typically has the capability needed for the receipt, storage, retrieval, movement and shipment of materials. This may include the movement of materials from one work center to another work center within or between enterprises.”

7.8.2.11.2 ObjectType Definition

The StorageZone is formally defined in Table 99.

7.8.2.12 StorageUnit

7.8.2.12.1 General

The role class “StorageUnit” should be used defining the role based equipment hierarchy defined in IEC 62264-1:2013 at the storage unit level: The definition of an “StorageUnit” is given in IEC 62264-1: 2013, 5.3.9: “Storage zones and storage units are the lowest level of material movement equipment typically scheduled by the Level 4 and Level 3 functions for discrete, batch and continuous manufacturing processes. Storage units are typically managed at a finer level of detail than a storage zone. The physical location of a storage unit may change over time; for example, for goods in transit. Storage units may be dedicated to a given material, group of materials, or method of storage. Storage units can be further divided to address any hierarchical storage management scheme.”

7.8.2.12.2 ObjectType Definition

The StorageUnit is formally defined in Table 100.

7.8.2.13 Turntable

7.8.2.13.1 General

The role class “Turntable” should be used for rotating transport equipment which changes the horizontal transport direction of a product and/or carrier.

7.8.2.13.2 ObjectType Definition

The Turntable is formally defined in Table 101.

7.8.2.14 Conveyor

7.8.2.14.1 General

The role class “Conveyor” should be used for generic equipment which performs linear transport.

7.8.2.14.2 ObjectType Definition

The Conveyor is formally defined in Table 102.

7.8.2.15 BeltConveyor

7.8.2.15.1 General

The role class “BeltConveyor” should be used for equipment which performs linear transport realized by one or more belts as transport platform.

7.8.2.15.2 ObjectType Definition

The BeltConveyor is formally defined in Table 103.

7.8.2.16 RollConveyor

7.8.2.16.1 General

The role class “RollConveyor” should be used for equipment which performs linear transport realized by a sequence of rolls as transport platform.

7.8.2.16.2 ObjectType Definition

The RollConveyor is formally defined in Table 104.

7.8.2.17 ChainConveyor

7.8.2.17.1 General

The role class “ChainConeyor” should be used for equipment which performs linear transport driven by an endless chain as transport medium.

7.8.2.17.2 ObjectType Definition

The ChainConveyor is formally defined in Table 105.

7.8.2.18 PalletConveyor

7.8.2.18.1 General

The role class “PalletConveyor” should be used for equipment which is especially designed for linear transport of pallets.

7.8.2.18.2 ObjectType Definition

The PalletConveyor is formally defined in Table 106.

7.8.2.19 OverheadConveyor

7.8.2.19.1 General

The role class “OverheadConveyor” should be used for equipment that performs overhead transport of hanging products or carriers.

7.8.2.19.2 ObjectType Definition

The OverheadConveyor is formally defined in Table 107.

7.8.2.20 LiftingTable

7.8.2.20.1 General

The role class “LiftingTable” should be used for equipment that performs discrete vertical transport. The transport medium is also lifted. Normally used for minor heights.

7.8.2.20.2 ObjectType Definition

The LiftingTable is formally defined in Table 108.

7.8.2.21 AGV

7.8.2.21.1 General

The role class “AGV” should be used for equipment that performs automated transportation of discrete units independent of other transport equipment.

7.8.2.21.2 ObjectType Definition

The AGV is formally defined in Table 109.

7.8.2.22 Transposer

7.8.2.22.1 General

The role class “Transposer” should be used for transport equipment that performs the change of the transport medium. Changes the classification or relation of product to the carrier (one to another).

7.8.2.22.2 ObjectType Definition

The Transposer is formally defined in Table 110.

7.8.2.23 CarrierHandlingSystem

7.8.2.23.1 General

The role class “CarrierHandlingSystem” should be used for equipment that performs an action to the carrier.

7.8.2.23.2 ObjectType Definition

The CarrierHandlingSystem is formally defined in Table 111.

7.8.2.24 BodyStore

7.8.2.24.1 General

The role class “BodyStore” should be used for buffering discrete products.

7.8.2.24.2 ObjectType Definition

The BodyStore is formally defined in Table 112.

7.8.2.25 Lift

7.8.2.25.1 General

The role class “Lift” should be used for equipment that performs discrete vertical transport. Normally used for larger heights.

7.8.2.25.2 ObjectType Definition

The Lift is formally defined in Table 113.

7.8.2.26 Rollerbed

7.8.2.26.1 General

The role class “Rollerbed” should be used for a sequence of rolls. None of these rolls are driven.

7.8.2.26.2 ObjectType Definition

The Rollerbed is formally defined in Table 114.

7.8.2.27 StationaryTool

7.8.2.27.1 General

The role class “StationaryTool” should be used for tools fixed at one place.

7.8.2.27.2 ObjectType Definition

The StationaryTool is formally defined in Table 115.

7.8.2.28 MovableTool

7.8.2.28.1 General

The role class “MovableTool” should be used for tools which can be moved by equipment e.g. robots.

7.8.2.28.2 ObjectType Definition

The MovableTool is formally defined in Table 116.

7.8.2.29 ControlCabinet

7.8.2.29.1 General

The role class “ControlCabinet” should be used for enclosed electrical and/or electronic assembly.

7.8.2.29.2 ObjectType Definition

The ControlCabinet is formally defined in Table 117.

7.8.2.30 IODevice

7.8.2.30.1 General

The role class “IODevice” should be used for devices providing the functionality to connect sensors or actuators with an automation system. IODevice can consist of different modules.

7.8.2.30.2 ObjectType Definition

The IODevice is formally defined in Table 118.

7.8.2.31 HMI

7.8.2.31.1 General

The role class “HMI” should be used for the functionality to visualize an industrial control and monitoring system for the effective operation and control of the machine by humans.

7.8.2.31.2 ObjectType Definition

The HMI is formally defined in Table 119.

7.8.2.32 WarningEquipment

7.8.2.32.1 General

The role class “WarningEquipment” should be used for equipment providing warning functionality. NOTE The functionality can be realized in auditive, visual, haptic or other way.

7.8.2.32.2 ObjectType Definition

The WarningEquipment is formally defined in Table 120.

7.8.2.33 ActuatingDrive

7.8.2.33.1 General

The role class “ActuatingDrive” should be used for physical unit used for driving mechanically actuated final controlling elements.

7.8.2.33.2 ObjectType Definition

The ActuatingDrive is formally defined in Table 121.

7.8.2.34 MotionController

7.8.2.34.1 General

The role class “MotionController” should be used for logic to generate set points (the desired output or motion profile) and close a position or velocity feedback loop.

7.8.2.34.2 ObjectType Definition

The MotionController is formally defined in Table 122.

7.8.2.35 Panel

7.8.2.35.1 General

The role class “Panel” should be used for physical object providing one possibility for humans to interact with machines.

7.8.2.35.2 ObjectType Definition

The Panel is formally defined in Table 123.

7.8.2.36 MeasuringEquipment

7.8.2.36.1 General

The role class “MeasuringEquipment” should be used for defining equipment defined in IEC60050-311:2001, 311-03-05: “assembly of measuring instruments intended for specified measurement purposes”

7.8.2.36.2 ObjectType Definition

The MeasuringEquipment is formally defined in Table 124.

7.8.2.37 Clamp

7.8.2.37.1 General

The role class “Clamp” should be used for equipment that performs fixation processes to hold items at one specific point.

7.8.2.37.2 ObjectType Definition

The Clamp is formally defined in Table 125.

7.8.2.38 ProcessController

7.8.2.38.1 General

The role class “ProcessController” should be used for the control of a specific tool or machine that performs process steps on a product.

7.8.2.38.2 ObjectType Definition

The ProcessController is formally defined in Table 126.

7.8.2.39 Loader

7.8.2.39.1 General

The role class “Loader” should be used for equipment to introduce products into the production process.

7.8.2.39.2 ObjectType Definition

The Loader is formally defined in Table 127.

7.8.2.40 Unloader

7.8.2.40.1 General

The role class “Unloader” should be used for equipment to export products out of the production process.

7.8.2.40.2 ObjectType Definition

The Unloader is formally defined in Table 128.