Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62714-2: AutomationML Role Class Libraries for Manufacturing
Key Insight: IEC 62714-2:2015 is the second part of the AutomationML (Automation Markup Language) standard suite. It defines standardized role class libraries that enable semantically consistent exchange of engineering data across heterogeneous software tools in factory automation, process engineering, and control system design. This standard is a cornerstone of Industry 4.0 digital twin implementations.
1. Introduction to AutomationML and Part 2
AutomationML (AML) is an open, XML-based data exchange format designed to interconnect engineering tools across the entire lifecycle of production systems. The IEC 62714 series provides the formal standardization of AML, with Part 1 defining the overall architecture, Part 2 (this document) specifying role class libraries, and subsequent parts covering specific application areas. The core concept is that engineering data — from mechanical CAD through electrical design to PLC programming — can be represented in a unified format using standardized semantics.
The role class library defined in IEC 62714-2 provides a semantic vocabulary for describing the functional role of components within a production system. Each role class defines what a component does, not what it is physically — enabling separation of function from implementation. This abstraction layer is critical for tool interoperability and digital twin modeling.
Industry Impact: AutomationML is widely adopted across automotive manufacturing, process industries, and machine building. Major engineering software vendors including Siemens, Dassault, and Autodesk provide AML import/export capabilities, making IEC 62714-2 a de facto standard for engineering data exchange in discrete and continuous manufacturing.
2. Role Class Library Architecture
2.1 Manufacturing Industry Libraries
The standard defines four primary role class libraries, each tailored to a specific manufacturing paradigm. Table 1 summarizes the libraries and their key role classes.
| Library Name | Applicable Industry | Key Role Classes | Use Case |
|---|---|---|---|
| AutomationMLDMIRoleClassLib | Discrete Manufacturing | Robot, Machine, Transport, Storage, Fixture, Gate, Tool, Carrier | Automotive assembly, electronics production, mechanical fabrication |
| AutomationMLCMIRoleClassLib | Continuous Manufacturing | ContManufacturingEquipment, various process equipment types | Chemical processing, oil and gas, pharmaceutical continuous production |
| AutomationMLBMIRoleClassLib | Batch Manufacturing | BatchManufacturingEquipment, process cell components | Food and beverage, specialty chemicals, biotech batch processing |
| AutomationMLCSRoleClassLib | Control Systems | ControlEquipment, PLC, NC, RC, PAC, Sensor, Actuator, Controller, IPC, HMI | Automation architecture design, control network planning |
The discrete manufacturing library (AutomationMLDMIRoleClassLib) is the most detailed, reflecting the origins of AML in automotive production. The DiscManufacturingEquipment role class serves as the top-level container, with specialized subclasses covering the full range of production equipment found on a factory floor. The Transport role class encompasses conveyors (belt, roll, chain, pallet, overhead), AGVs, lifting tables, and transposers. The Storage role class covers body stores, storage zones, and storage units.
2.2 Control Systems Role Class Library
The AutomationMLCSRoleClassLib is particularly important for automation engineers. It provides a comprehensive taxonomy of control equipment that bridges the gap between physical hardware and software functions. Table 2 shows the control system hierarchy.
| Role Class | Parent Class | Description | Example Equipment |
|---|---|---|---|
| ControlEquipment | Root | Top-level class for all control devices | Any automation controller |
| Controller | ControlEquipment | Device that executes control logic | Programmable logic controllers |
| PLC | Controller | Programmable Logic Controller | Siemens S7, Allen-Bradley ControlLogix |
| NC | Controller | Numerical Controller | CNC machine controllers |
| RC | Controller | Robot Controller | ABB IRC5, KUKA KR C4 |
| PAC | Controller | Programmable Automation Controller | Beckhoff CX series, National Instruments cRIO |
| Sensor | ControlHardware | Device that measures physical quantity | Proximity sensors, temperature sensors, vision systems |
| Actuator | ControlHardware | Device that produces physical motion or action | Motors, valves, solenoids, cylinders |
| Communication | ControlEquipment | Network and communication infrastructure | Ethernet switches, fieldbus gateways |
| HMI | IPC / EmbeddedDevice | Human-Machine Interface | Touch panels, operator terminals |
Engineering Design Insight: The separation of control hardware into distinct role classes (PLC vs. PAC vs. IPC) reflects real engineering practice where these devices have fundamentally different programming paradigms, real-time characteristics, and reliability profiles. Using the correct role class ensures that downstream engineering tools can apply appropriate validation rules and generate correct configuration code.
3. Extended Role Class Library (Annex A)
Annex A of the standard provides an informative (non-normative) extended role class library that offers finer granularity for complex production systems. This includes specialized facet role classes such as PLCFacet (describing PLC-specific characteristics like cycle time, memory capacity, supported programming languages per IEC 61131-3) and HMIFacet (describing display properties, resolution, and touch capabilities).
The enterprise hierarchy facet classes — Enterprise, Site, Area, ProductionLine, WorkCell, ProcessCell, Unit, and ProductionUnit — align with the ISA-95 / IEC 62264 functional hierarchy model. This alignment is intentionally designed to bridge the gap between enterprise resource planning (ERP) systems and shop-floor automation, enabling vertical integration from Level 4 (business planning) down to Level 1 (sensing and actuation).
Implementation Consideration: While the extended role class library is informative (non-mandatory), its adoption is strongly recommended for projects requiring detailed semantic modeling. Many AML-compatible engineering tools provide built-in support for these extended role classes, and their use significantly improves the quality of automated data exchange.
4. Engineering Design Insights
For engineers implementing AutomationML-based data exchange, several key insights from IEC 62714-2 are critical. First, the choice of role class determines how engineering data will be interpreted by downstream tools — a component classified as “PLC” will be treated differently than one classified as “IPC” even if both are physically similar. Second, the standard’s alignment with ISA-95 (IEC 62264) makes it suitable for both brownfield and greenfield projects, as legacy equipment can be mapped to appropriate role classes regardless of physical form factor. Third, the facet mechanism (Annex A) allows role classes to be composed, enabling a single device to express multiple functional roles simultaneously — a powerful feature for modeling complex multi-function automation components.
Digital Twin Readiness: IEC 62714-2 role classes form the semantic foundation for digital twin models in manufacturing. By standardizing how equipment functions are described, the standard enables consistent simulation, virtual commissioning, and performance optimization across the entire production system lifecycle.
5. Frequently Asked Questions
Q1: How does IEC 62714-2 relate to other parts of the AutomationML standard?
A: Part 1 defines the overall AML architecture and top-level model. Part 2 (this standard) defines role class libraries with standardized semantics for describing equipment functions. Part 3 specifies geometry and kinematics data exchange, and subsequent parts cover additional domain-specific extensions.
A: Part 1 defines the overall AML architecture and top-level model. Part 2 (this standard) defines role class libraries with standardized semantics for describing equipment functions. Part 3 specifies geometry and kinematics data exchange, and subsequent parts cover additional domain-specific extensions.
Q2: Can IEC 62714-2 role classes be extended for proprietary equipment?
A: Yes. The role class hierarchy is designed for extensibility. Users can create proprietary subclasses of standard role classes to capture equipment-specific characteristics while maintaining compatibility with the base classification. The standard recommends using the XML namespace mechanism to avoid naming conflicts.
A: Yes. The role class hierarchy is designed for extensibility. Users can create proprietary subclasses of standard role classes to capture equipment-specific characteristics while maintaining compatibility with the base classification. The standard recommends using the XML namespace mechanism to avoid naming conflicts.
Q3: What is the relationship between IEC 62714-2 role classes and IEC 61131-3 programming languages?
A: The PLC role class in IEC 62714-2 can include facet information about which IEC 61131-3 programming languages (Ladder Diagram, Function Block Diagram, Structured Text, etc.) the controller supports. This enables engineering tools to generate appropriate code targeting specific controller capabilities.
A: The PLC role class in IEC 62714-2 can include facet information about which IEC 61131-3 programming languages (Ladder Diagram, Function Block Diagram, Structured Text, etc.) the controller supports. This enables engineering tools to generate appropriate code targeting specific controller capabilities.
Q4: Is IEC 62714-2 applicable outside of discrete manufacturing?
A: Absolutely. While the standard originated in automotive discrete manufacturing, the role class libraries support continuous manufacturing (AutomationMLCMIRoleClassLib) and batch manufacturing (AutomationMLBMIRoleClassLib), making it applicable across process industries, food and beverage, pharmaceuticals, and many other sectors.
A: Absolutely. While the standard originated in automotive discrete manufacturing, the role class libraries support continuous manufacturing (AutomationMLCMIRoleClassLib) and batch manufacturing (AutomationMLBMIRoleClassLib), making it applicable across process industries, food and beverage, pharmaceuticals, and many other sectors.
