AutomationML

Uses CAEX (IEC 62424) as the structural backbone to model the plant topology. This object-oriented data model represents the hierarchical structure of a manufacturing system—from the enterprise level down to individual sensors and actuators. CAEX defines System Unit Classes (templates) and Internal Elements (instances), establishing the semantic relationships and nesting of all physical and logical components.

Stores detailed 3D kinematic and visual geometry using COLLADA (ISO/PAS 17506). Unlike lightweight formats, COLLADA preserves the full kinematic chain, including joint axes, articulation limits, and mesh data. AutomationML links each geometry instance to its corresponding CAEX structural element, ensuring the visual representation is semantically tied to the plant hierarchy for accurate virtual commissioning and collision detection.

Represents control behavior and sequential logic using PLCopen XML (IEC 61131-10). This captures the full IEC 61131-3 programming model—including Ladder Diagram, Structured Text, and Sequential Function Chart—in an open XML schema. AutomationML links each Program Organization Unit (POU) to the specific CAEX element it controls, creating a direct, traceable relationship between software logic and physical equipment.

Defines reusable, vendor-neutral Role Classes that abstract the function of a component from its specific implementation. For example, a 'Motor' role defines the generic interface and behavior expected of any motor, while a specific manufacturer's part implements that role. This semantic abstraction layer enables multi-vendor engineering and simplifies the replacement of physical devices without rewriting the overarching control logic or plant model.

Employs a non-intrusive linking mechanism that references external documents rather than embedding them. CAEX elements contain ExternalReference nodes that point to COLLADA geometry files, PLCopen XML logic files, or any other engineering document via URI. This preserves the integrity of native tool formats, avoids data duplication, and allows domain experts to work in their preferred authoring tools while maintaining a single, coherent data backbone.

Provides AutomationML Interface Libraries that standardize the ports, signals, and data flow connections between components. These libraries define physical interfaces (e.g., electrical terminals, pneumatic ports) and logical interfaces (e.g., OPC UA variables, network signals). By formalizing how components connect and communicate, AutomationML enables automated consistency checks and seamless integration with Asset Administration Shells (AAS) for Industry 4.0 deployments.