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.
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.
Table 27 - AutomationMLInterfaceClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLInterfaceClassLib |
FolderType |
The interface class “AutomationMLBaseInterface” is a base abstract interface type and shall be used as parent for the description of all AML interface classes.
The AutomationMLBaseInterface is formally defined in Table 28.
Table 28 - AutomationMLBaseInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
AutomationMLBaseInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the CAEXObjectType |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “AttachmentInterface” shall be used to denote a geometrical connection point of an AutomationML object.
The AttachmentInterface is formally defined in Table 29.
Table 29 - AttachmentInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
AttachmentInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “Communication” shall be used for the description of communication related interfaces.
The Communication is formally defined in Table 30.
Table 30 - Communication Definition
|
Attribute |
Value |
||||
|
BrowseName |
Communication |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “SignalInterface” shall be used for modelling signals.
The SignalInterface is formally defined in Table 31.
Table 31 - SignalInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
SignalInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Communication |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The ExternalDataConnector is formally defined in Table 32.
Table 32 - ExternalDataConnector Definition
|
Attribute |
Value |
||||
|
BrowseName |
ExternalDataConnector |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasComponent |
Variable |
refURI |
String |
BaseDataVariableType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The attribute “refURI” shall be used in order to store the path to the reference external document.
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.
The COLLADAInterface is formally defined in Table 33.
Table 33 - COLLADAInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
COLLADAInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ExternalDataConnector |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The PLCopenXMLInterface is formally defined in Table 34.
Table 34 - PLCopenXMLInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
PLCopenXMLInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ExternalDataConnector |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “LogicInterface” shall be used in order to reference a logic description within an external PLCopen XML document.
The LogicInterface is formally defined in Table 35.
Table 35 - LogicInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
LogicInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the PLCopenXMLInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “VariableInterface” shall be used in order to reference variables in external PLCopen XML document.
The VariableInterface is formally defined in Table 36.
Table 36 - VariableInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
VariableInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the PLCopenXMLInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “InterlockingVariableInterface” shall be used in order to reference variables representing an interlocking condition in external PLCopen XML document.
The InterlockingVariableInterface is formally defined in Table 37.
Table 37 - InterlockingVariableInterface Definition
|
Attribute |
Value |
||||
|
BrowseName |
InterlockingVariableInterface |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the VariableInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasComponent |
Variable |
SafeConditionEquals |
Boolean |
BaseDataVariableType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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
The interface class “InterlockingConnector” shall be used in order to model relations between signal groups and component groups.
The InterlockingConnector is formally defined in Table 38.
Table 38 - InterlockingConnector Definition
|
Attribute |
Value |
||||
|
BrowseName |
InterlockingConnector |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “Order” is an abstract class that shall be used for the description of orders, e.g. a successor or a predecessor.
The Order is formally defined in Table 39.
Table 39 - Order Definition
|
Attribute |
Value |
||||
|
BrowseName |
Order |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasComponent |
Variable |
Direction |
String |
BaseDataVariableType |
Optional |
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The attribute “Direction” shall be used in order to specify the direction. Permitted values are “In”, “Out” or “InOut”.
The interface class “PortConnector” shall be used in order to provide a high level relation between ports.
The PortConnector is formally defined in Table 40.
Table 40 - PortConnector Definition
|
Attribute |
Value |
||||
|
BrowseName |
PortConnector |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The interface class “PPRConnector” shall be used in order to provide a relation between resources, products and processes.
The PPRConnector is formally defined in Table 41.
Table 41 - PPRConnector Definition
|
Attribute |
Value |
||||
|
BrowseName |
PPRConnector |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseInterface |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
Table 42 - AutomationMLBaseRoleClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLBaseRoleClassLib |
FolderType |
The role class “AutomationMLBaseRole” is a basic abstract role type and the base class for all standard or user-defined role classes.
The AutomationMLBaseRole is formally defined in Table 43.
Table 43 - AutomationMLBaseRole Definition
|
Attribute |
Value |
||||
|
BrowseName |
AutomationMLBaseRole |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the CAEXObjectType |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Group is formally defined in Table 44.
Table 44 - Group Definition
|
Attribute |
Value |
||||
|
BrowseName |
Group |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasComponent |
Variable |
AssociatedFacet |
String |
BaseDataVariableType |
Optional |
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The attribute “AssociatedFacet” shall be used for the definition of the name of the corresponding Facet. Example: AssociatedFacet = “PLCFacet”
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.
The Facet is formally defined in Table 45
Table 45 - Facet Definition
|
Attribute |
Value |
||||
|
BrowseName |
Facet |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Port is formally defined in Table 46.
Table 46 - Port Definition
|
Attribute |
Value |
||||
|
BrowseName |
Port |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasComponent |
Variable |
Cardinality |
String |
BaseDataVariableType |
Optional |
|
HasComponent |
Variable |
Category |
String |
BaseDataVariableType |
Optional |
|
HasComponent |
Object |
ConnectionPoint |
|
PortConnector |
Optional |
|
HasComponent |
Variable |
Direction |
String |
BaseDataVariableType |
Optional |
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
This attribute is a complex attribute which can describe MaxOccur or MinOccur.
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”
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.
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.
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.
The Resource is formally defined in Table 47
Table 47 - Resource Definition
|
Attribute |
Value |
||||
|
BrowseName |
Resource |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Product is formally defined in Table 48.
Table 48 - Product Definition
|
Attribute |
Value |
||||
|
BrowseName |
Product |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Process is formally defined in Table 49.
Table 49 - Process Definition
|
Attribute |
Value |
||||
|
BrowseName |
Process |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Structure is formally defined in Table 50.
Table 50 - Structure Definition
|
Attribute |
Value |
||||
|
BrowseName |
Structure |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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
The ResourceStructure is formally defined in Table 51.
Table 51 - ResourceStructure Definition
|
Attribute |
Value |
||||
|
BrowseName |
ResourceStructure |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Structure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The ProductStructure is formally defined in Table 52.
Table 52 - ProductStructure Definition
|
Attribute |
Value |
||||
|
BrowseName |
ProductStructure |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Structure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The ProcessStructure is formally defined in Table 53.
Table 53 - ProcessStructure Definition
|
Attribute |
Value |
||||
|
BrowseName |
ProcessStructure |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Structure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Frame” denotes a distinct coordinate system. This coordinate system is explicitly accentuated for special usage.
The Frame is formally defined in Table 54.
Table 54 - Frame Definition
|
Attribute |
Value |
||||
|
BrowseName |
Frame |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The ComponentGroup is formally defined in Table 55.
Table 55 - ComponentGroup Definition
|
Attribute |
Value |
||||
|
BrowseName |
ComponentGroup |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Group |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The SignalGroup is formally defined in Table 56.
Table 56 - SignalGroup Definition
|
Attribute |
Value |
||||
|
BrowseName |
SignalGroup |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Group |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The PropertySet is formally defined in Table 57.
Table 57 - PropertySet Definition
|
Attribute |
Value |
||||
|
BrowseName |
PropertySet |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the AutomationMLBaseRole |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
This Instance is a child of RoleClassLibs. It is defined in Table 58.
It consists of the AutomationML Discrete Manufacturing Industry Role Class Library.
Table 58 - AutomationMLDMIRoleClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLDMIRoleClassLib |
FolderType |
The role class “DiscManufacturingEquipment” shall be used for equipment related to discrete manufacturing industries.
The DiscManufacturingEquipment is formally defined in Table 59.
Table 59 - DiscManufacturingEquipment Definition
|
Attribute |
Value |
||||
|
BrowseName |
DiscManufacturingEquipment |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Resource |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Transport” shall be used for equipment that performs transport processes to transfer items.
The Transport is formally defined in Table 60.
Table 60 - Transport Definition
|
Attribute |
Value |
||||
|
BrowseName |
Transport |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Storage is formally defined in Table 61.
Table 61 - Storage Definition
|
Attribute |
Value |
||||
|
BrowseName |
Storage |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Fixture” shall be used for equipment that reduces the degrees of freedom of an item.
The Fixture is formally defined in Table 62.
Table 62 - Fixture Definition
|
Attribute |
Value |
||||
|
BrowseName |
Fixture |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Gate” shall be used for equipment that can block or monitor an entrance, departure, or a passage way.
The Gate is formally defined in Table 63.
Table 63 - Gate Definition
|
Attribute |
Value |
||||
|
BrowseName |
Gate |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Robot” shall be used for robots.
The Robot is formally defined in Table 64.
Table 64 - Robot Definition
|
Attribute |
Value |
||||
|
BrowseName |
Robot |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Tool is formally defined in Table 65.
Table 65 - Tool Definition
|
Attribute |
Value |
||||
|
BrowseName |
Tool |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Carrier” shall be used for transport equipment that carries items.
The Carrier is formally defined in Table 66.
Table 66 - Carrier Definition
|
Attribute |
Value |
||||
|
BrowseName |
Carrier |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Machine is formally defined in Table 67.
Table 67 - Machine Definition
|
Attribute |
Value |
||||
|
BrowseName |
Machine |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “StaticObject” shall be used for passive, static items positioned in the production environment.
The StaticObject is formally defined in Table 68.
Table 68 - StaticObject Definition
|
Attribute |
Value |
||||
|
BrowseName |
StaticObject |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the DiscManufacturingEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
This Instance is a child of RoleClassLibs. It is defined in Table 69.
It consists of the AutomationML Continuous Manufacturing Industry Role Class Library.
Table 69 - AutomationMLCMIRoleClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLCMIRoleClassLib |
FolderType |
The role class “ContManufacturingEquipment” shall be used for equipment related to continuous manufacturing industries.
The ContManufacturingEquipment is formally defined in Table 70.
Table 70 - ContManufacturingEquipment Definition
|
Attribute |
Value |
||||
|
BrowseName |
ContManufacturingEquipment |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the CAEXObjectType |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
This Instance is a child of RoleClassLibs. It is defined in Table 71.
It consists of the AutomationML Batch Manufacturing Industry Role Class Library.
Table 71 - AutomationMLBMIRoleClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLBMIRoleClassLib |
FolderType |
The role class “BatchManufacturingEquipment” shall be used for equipment related to batch manufacturing industries.
The BatchManufacturingEquipment is formally defined in Table 72.
Table 72 - BatchManufacturingEquipment Definition
|
Attribute |
Value |
||||
|
BrowseName |
BatchManufacturingEquipment |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the CAEXObjectType |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
This Instance is a child of RoleClassLibs. It is defined in Table 73.
It consists of the AutomationML Control Industry Role Class Library.
Table 73 - AutomationMLCSRoleClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLCSRoleClassLib |
FolderType |
The role class “ControlEquipment” shall be used for equipment related to a control system. ControlEquipment can be used for every type of industry.
The ControlEquipment is formally defined in Table 74.
Table 74 - ControlEquipment Definition
|
Attribute |
Value |
||||
|
BrowseName |
ControlEquipment |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Resource |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The Communication is formally defined in Table 75.
Table 75 - Communication Definition
|
Attribute |
Value |
||||
|
BrowseName |
Communication |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “ControlHardware” shall be used for hardware that provides runtime environments.
The ControlHardware is formally defined in Table 76.
Table 76 - ControlHardware Definition
|
Attribute |
Value |
||||
|
BrowseName |
ControlHardware |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “PC” shall be used for any general-purpose computer that provides runtime environments for software being executed on it.
The PC is formally defined in Table 77.
Table 77 - PC Definition
|
Attribute |
Value |
||||
|
BrowseName |
PC |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlHardware |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The IPC is formally defined in Table 78.
Table 78 - IPC Definition
|
Attribute |
Value |
||||
|
BrowseName |
IPC |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlHardware |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Handheld” shall be used for any portable, programmable, electronic device with an own power supply for particular applications.
The Handheld is formally defined in Table 79.
Table 79 - Handheld Definition
|
Attribute |
Value |
||||
|
BrowseName |
Handheld |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlHardware |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The EmbeddedDevice is formally defined in Table 80.
Table 80 - EmbeddedDevice Definition
|
Attribute |
Value |
||||
|
BrowseName |
EmbeddedDevice |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlHardware |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Sensor” shall be used for sensors.
The Sensor is formally defined in Table 81.
Table 81 - Sensor Definition
|
Attribute |
Value |
||||
|
BrowseName |
Sensor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Actuator” shall be used for actuators.
The Actuator is formally defined in Table 82.
Table 82 - Actuator Definition
|
Attribute |
Value |
||||
|
BrowseName |
Actuator |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Controller is formally defined in Table 83.
Table 83 - Controller Definition
|
Attribute |
Value |
||||
|
BrowseName |
Controller |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “PLC” shall be used for programmable control functionality focusing the processing of signals.
The PLC is formally defined in Table 84.
Table 84 - PLC Definition
|
Attribute |
Value |
||||
|
BrowseName |
PLC |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Controller |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “NC” shall be used for programmable control functionality focusing the processing of numerical signals.
The NC is formally defined in Table 85.
Table 85 - NC Definition
|
Attribute |
Value |
||||
|
BrowseName |
NC |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Controller |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The RC is formally defined in Table 86.
Table 86 - RC Definition
|
Attribute |
Value |
||||
|
BrowseName |
RC |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Controller |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “PAC” shall be used for programmable automation functionality focusing on cross-domain functionality like binary, motion and continuous control.
The PAC is formally defined in Table 87.
Table 87 - PAC Definition
|
Attribute |
Value |
||||
|
BrowseName |
PAC |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Controller |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
Table 88 - AutomationMLExtendedRoleClassLib Instance Definition
|
Name |
TypeDefinition |
|
AutomationMLExtendedRoleClassLib |
FolderType |
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.
The PLCFacet is formally defined in Table 89.
Table 89 - PLCFacet Definition
|
Attribute |
Value |
||||
|
BrowseName |
PLCFacet |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Facet |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The HMIFacet is formally defined in Table 90.
Table 90 - HMIFacet Definition
|
Attribute |
Value |
||||
|
BrowseName |
HMIFacet |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Facet |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The Enterprise is formally defined in Table 91.
Table 91 - Enterprise Definition
|
Attribute |
Value |
||||
|
BrowseName |
Enterprise |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The Site is formally defined in Table 92.
Table 92 - Site Definition
|
Attribute |
Value |
||||
|
BrowseName |
Site |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The Area is formally defined in Table 93.
Table 93 - Area Definition
|
Attribute |
Value |
||||
|
BrowseName |
Area |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The ProductionLine is formally defined in Table 94.
Table 94 - ProductionLine Definition
|
Attribute |
Value |
||||
|
BrowseName |
ProductionLine |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The WorkCell is formally defined in Table 95.
Table 95 - WorkCell Definition
|
Attribute |
Value |
||||
|
BrowseName |
WorkCell |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The ProcessCell is formally defined in Table 96.
Table 96 - ProcessCell Definition
|
Attribute |
Value |
||||
|
BrowseName |
ProcessCell |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The Unit is formally defined in Table 97.
Table 97 - Unit Definition
|
Attribute |
Value |
||||
|
BrowseName |
Unit |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The ProductionUnit is formally defined in Table 98.
Table 98 - ProductionUnit Definition
|
Attribute |
Value |
||||
|
BrowseName |
ProductionUnit |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The StorageZone is formally defined in Table 99.
Table 99 - StorageZone Definition
|
Attribute |
Value |
||||
|
BrowseName |
StorageZone |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.”
The StorageUnit is formally defined in Table 100.
Table 100 - StorageUnit Definition
|
Attribute |
Value |
||||
|
BrowseName |
StorageUnit |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ResourceStructure |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Turntable” should be used for rotating transport equipment which changes the horizontal transport direction of a product and/or carrier.
The Turntable is formally defined in Table 101.
Table 101 - Turntable Definition
|
Attribute |
Value |
||||
|
BrowseName |
Turntable |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Conveyor” should be used for generic equipment which performs linear transport.
The Conveyor is formally defined in Table 102.
Table 102 - Conveyor Definition
|
Attribute |
Value |
||||
|
BrowseName |
Conveyor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “BeltConveyor” should be used for equipment which performs linear transport realized by one or more belts as transport platform.
The BeltConveyor is formally defined in Table 103.
Table 103 - BeltConveyor Definition
|
Attribute |
Value |
||||
|
BrowseName |
BeltConveyor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Conveyor |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “RollConveyor” should be used for equipment which performs linear transport realized by a sequence of rolls as transport platform.
The RollConveyor is formally defined in Table 104.
Table 104 - RollConveyor Definition
|
Attribute |
Value |
||||
|
BrowseName |
RollConveyor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Conveyor |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “ChainConeyor” should be used for equipment which performs linear transport driven by an endless chain as transport medium.
The ChainConveyor is formally defined in Table 105.
Table 105 - ChainConveyor Definition
|
Attribute |
Value |
||||
|
BrowseName |
ChainConveyor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Conveyor |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “PalletConveyor” should be used for equipment which is especially designed for linear transport of pallets.
The PalletConveyor is formally defined in Table 106.
Table 106 - PalletConveyor Definition
|
Attribute |
Value |
||||
|
BrowseName |
PalletConveyor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Conveyor |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “OverheadConveyor” should be used for equipment that performs overhead transport of hanging products or carriers.
The OverheadConveyor is formally defined in Table 107.
Table 107 - OverheadConveyor Definition
|
Attribute |
Value |
||||
|
BrowseName |
OverheadConveyor |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Conveyor |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The LiftingTable is formally defined in Table 108.
Table 108 - LiftingTable Definition
|
Attribute |
Value |
||||
|
BrowseName |
LiftingTable |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “AGV” should be used for equipment that performs automated transportation of discrete units independent of other transport equipment.
The AGV is formally defined in Table 109.
Table 109 - AGV Definition
|
Attribute |
Value |
||||
|
BrowseName |
AGV |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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).
The Transposer is formally defined in Table 110.
Table 110 - Transposer Definition
|
Attribute |
Value |
||||
|
BrowseName |
Transposer |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “CarrierHandlingSystem” should be used for equipment that performs an action to the carrier.
The CarrierHandlingSystem is formally defined in Table 111.
Table 111 - CarrierHandlingSystem Definition
|
Attribute |
Value |
||||
|
BrowseName |
CarrierHandlingSystem |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “BodyStore” should be used for buffering discrete products.
The BodyStore is formally defined in Table 112.
Table 112 - BodyStore Definition
|
Attribute |
Value |
||||
|
BrowseName |
BodyStore |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Storage |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Lift” should be used for equipment that performs discrete vertical transport. Normally used for larger heights.
The Lift is formally defined in Table 113.
Table 113 - Lift Definition
|
Attribute |
Value |
||||
|
BrowseName |
Lift |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Rollerbed” should be used for a sequence of rolls. None of these rolls are driven.
The Rollerbed is formally defined in Table 114.
Table 114 - Rollerbed Definition
|
Attribute |
Value |
||||
|
BrowseName |
Rollerbed |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Transport |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “StationaryTool” should be used for tools fixed at one place.
The StationaryTool is formally defined in Table 115.
Table 115 - StationaryTool Definition
|
Attribute |
Value |
||||
|
BrowseName |
StationaryTool |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Tool |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “MovableTool” should be used for tools which can be moved by equipment e.g. robots.
The MovableTool is formally defined in Table 116.
Table 116 - MovableTool Definition
|
Attribute |
Value |
||||
|
BrowseName |
MovableTool |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Tool |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “ControlCabinet” should be used for enclosed electrical and/or electronic assembly.
The ControlCabinet is formally defined in Table 117.
Table 117 - ControlCabinet Definition
|
Attribute |
Value |
||||
|
BrowseName |
ControlCabinet |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The IODevice is formally defined in Table 118.
Table 118 - IODevice Definition
|
Attribute |
Value |
||||
|
BrowseName |
IODevice |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The HMI is formally defined in Table 119.
Table 119 - HMI Definition
|
Attribute |
Value |
||||
|
BrowseName |
HMI |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The WarningEquipment is formally defined in Table 120.
Table 120 - WarningEquipment Definition
|
Attribute |
Value |
||||
|
BrowseName |
WarningEquipment |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the HMI |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “ActuatingDrive” should be used for physical unit used for driving mechanically actuated final controlling elements.
The ActuatingDrive is formally defined in Table 121.
Table 121 - ActuatingDrive Definition
|
Attribute |
Value |
||||
|
BrowseName |
ActuatingDrive |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Actuator |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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.
The MotionController is formally defined in Table 122.
Table 122 - MotionController Definition
|
Attribute |
Value |
||||
|
BrowseName |
MotionController |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlEquipment |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Panel” should be used for physical object providing one possibility for humans to interact with machines.
The Panel is formally defined in Table 123.
Table 123 - Panel Definition
|
Attribute |
Value |
||||
|
BrowseName |
Panel |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the ControlHardware |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
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”
The MeasuringEquipment is formally defined in Table 124.
Table 124 - MeasuringEquipment Definition
|
Attribute |
Value |
||||
|
BrowseName |
MeasuringEquipment |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Resource |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Clamp” should be used for equipment that performs fixation processes to hold items at one specific point.
The Clamp is formally defined in Table 125.
Table 125 - Clamp Definition
|
Attribute |
Value |
||||
|
BrowseName |
Clamp |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Fixture |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “ProcessController” should be used for the control of a specific tool or machine that performs process steps on a product.
The ProcessController is formally defined in Table 126.
Table 126 - ProcessController Definition
|
Attribute |
Value |
||||
|
BrowseName |
ProcessController |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Controller |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Loader” should be used for equipment to introduce products into the production process.
The Loader is formally defined in Table 127.
Table 127 - Loader Definition
|
Attribute |
Value |
||||
|
BrowseName |
Loader |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Storage |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |
The role class “Unloader” should be used for equipment to export products out of the production process.
The Unloader is formally defined in Table 128.
Table 128 - Unloader Definition
|
Attribute |
Value |
||||
|
BrowseName |
Unloader |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Inherit the components of the Storage |
|||||
|
|
|
|
|
|
|
|
HasProperty |
Variable |
ID |
BaseDataType |
PropertyType |
Optional |
|
HasProperty |
Variable |
Version |
BaseDataType |
PropertyType |
Optional |