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 |