Alignment of ISA-95 and AutomationML

AutomationML is an neutral XML-based standard targeting the modeling of production environments. It was developed by an industrial-academic consurtium including the companies Daimler, ABB, Siemens, Rockwell, Kuka, Zühlke, netAllied and the universities of Magdeburg and Karlsruhe and was published by the International Electronic Commission, released as IEC 62714.
AutomationML enables data exchange between manufacturing engineering tools and therefore supports the interoperability between them.
Various extensions were developed e.g. with the help of annotations of AML models geometry and kinematics of machines as well as their internal behavior can be enriched.

AutomationML is based on the \textit{Computer Aided Engineering Data-Exchange-Metamodel} (CAEX), a XML dialect standardized in IEC 62424. CAEX is a neutral data format for model hierarchical object information. With CAEX can e.g. the hierarchical plant structure be mapped, which consists of coupled and parameterized modules and components at a certain level of abstraction.
CAEX allows you to save these modules and components using the Object Approach. It explicitly supports concepts such as encapsulation, classes, class libraries, instances, instance hierarchies, inheritance, relations, attributes, and interfaces. CAEX is based on XML and is defined as an XML schema.
AutomationML adds a set of instance elements as well as rules and restrictions to CAEX, which results in computer-readable semantics and simplify modeling of automated production systems.

There are several entities, which are redundantly defined in both standards of IEC 62264-2 and AutomationML.

In order to transform actual models, the semantics of the appropriate meta models have to be aligned.
First the entities are semantically coupled to the CAEX-specific entities Attributes, Role Class, System Unit, Role Class and Internal Elements, which is visualized in figure on the left side:
(i) All properties of all resources can be mapped to Attribute. Both metamodels support subattributes/subproperties.
(ii) System Units are vendor-specific reusable entities, which can be represented through
Physical Asset Classes. Material Defintions can also be seen as vendor-specific of raw material (e.g. coating powder).
(iii) Role Class are classifications of Internal Elements and System Unit Classes, which can mapped to either Personnel Class, Equipment Class or Material Class.
(iv) All other entities can be mapped to Internal Elements.
(v) References between IEC 62264-2 Elements, which can not mapped to super or sub classifications can be realized with External Interface and Internal Link.

Diagram shows on the right the mapping of ISA-95 entities categorized in the lower granular concepts of AutomationML Libraries:Product, Process (Structure) Resources (PPR) and AutomationMLBaseRoleClass:
(i) Equipment, Equipment Class, Physical Asset and Physical Asset Class can be mapped to Resource.
(ii) Material Definition, Material Class, Material Lot, Material Sublot are Products.
(iii) Operation Segment, Process Segment are Processes – Operations Definition can be mapped to Process Structure.
(iv) All Personnel related and all specification entities can be mapped to AutomationMLBaseRoleClass.