Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 63097 — Smart Manufacturing Reference Architecture Model for Industry 4.0
Technical Report on Smart Manufacturing Architecture
1. Overview and Scope of IEC TR 63097
IEC TR 63097 provides a reference architecture model for smart manufacturing within the Industry 4.0 framework. Published as a technical report, this document establishes a structured architectural blueprint that integrates the physical production environment with digital information systems, enabling interoperability, data-driven decision-making, and adaptive manufacturing processes across diverse industrial domains.
IEC TR 63097 aligns closely with the RAMI 4.0 (Reference Architectural Model Industrie 4.0) standard IEC PAS 62832 and the Industrial Internet Reference Architecture (IIRA). It serves as a harmonisation layer that maps concepts between these frameworks, making it an essential reference for multi-vendor smart factory integration projects.
The standard addresses the fundamental challenge of Industry 4.0: how to create a cohesive system architecture from heterogeneous components spanning multiple vendors, communication protocols, and data formats. It defines a three-dimensional architectural space comprising the life cycle dimension (product design to recycling), the hierarchy dimension (field device to enterprise), and the functional dimension (data acquisition to business analytics). This layered approach ensures that every aspect of smart manufacturing is captured in a consistent, traceable manner.
| Architecture Dimension | Layers / Levels | Key Focus Areas |
|---|---|---|
| Life Cycle & Value Stream | Development, Production, Maintenance, End-of-Life | Digital twin, PLM, traceability, circular economy |
| Hierarchy Levels | Field Device → Control → Station → Work Center → Enterprise → Connected World | ISA-95/IEC 62264 alignment, scalability, legacy integration |
| Functional Layers | Asset → Integration → Communication → Information → Functional → Business | OPC UA, AAS, data modelling, analytics, decision support |
2. Core Architectural Components and Interoperability
The reference architecture model is built around the concept of the Asset Administration Shell (AAS), a standardised digital representation of a physical or logical asset. Each AAS contains sub-models that describe the asset’s properties, capabilities, states, and interfaces. IEC TR 63097 specifies the minimum required sub-models for interoperability: identification, nameplate, technical data, communication parameters, and health condition. Manufacturers can extend these with domain-specific sub-models as needed.
A critical implementation pitfall is treating the AAS as a static data repository rather than a live digital twin. The standard emphasises that the administration shell must be continuously synchronised with the physical asset through real-time data streams. AAS instances that are updated only during commissioning quickly become outdated and lose their decision-support value.
Interoperability in the IEC TR 63097 architecture is achieved through three complementary mechanisms: semantic interoperability via standardised information models (OPC UA companion specifications, AutomationML, eCl@ss), syntactic interoperability through defined communication protocols (MQTT, OPC UA binary, RESTful APIs), and transport interoperability using TCP/IP, TSN, and 5G networks. The standard provides explicit mapping tables between these mechanism layers and the functional architecture levels, enabling engineers to select appropriate technology stacks for each integration point.
Companies that implement the full AAS-based architecture as described in IEC TR 63097 report 40-60% reductions in engineering effort for factory integration projects. The standardised sub-models eliminate the need for point-to-point interface definitions between each pair of systems, replacing them with a unified information bus.
3. Engineering Design Insights for Smart Manufacturing Deployments
From a practical engineering standpoint, several critical design considerations emerge from IEC TR 63097. First, the selection of communication infrastructure must account for both time-sensitive networking (TSN) for deterministic control loops and best-effort IP networking for analytics and reporting. A converged network architecture using IEEE 802.1 TSN standards can carry both real-time control traffic and non-critical data on the same physical infrastructure, significantly reducing cabling and switch costs.
Second, data modelling consistency is paramount. The standard recommends establishing a company-wide semantic dictionary based on eCl@ss or IEC CDD (Common Data Dictionary) before any integration work begins. Without a shared semantic foundation, data from different production cells cannot be meaningfully aggregated at the enterprise level. Third, edge computing nodes should be deployed with sufficient local storage and processing capability to maintain autonomous operation for at least 72 hours in the event of central system or cloud connectivity loss. This “graceful degradation” requirement is often underestimated during the design phase.
For brownfield factories with existing PLC-based automation, IEC TR 63097 recommends deploying OPC UA gateway appliances that translate legacy fieldbus protocols (Profinet, EtherNet/IP, Modbus TCP) into the standardised information model. These gateways should be specified with sufficient processing headroom to handle protocol translation at full line speed without introducing latency spikes.
The standard also addresses cybersecurity architecture, recommending defence-in-depth aligned with IEC 62443. The key principle is network segmentation: OT networks (control level and below) must be separated from IT networks (operations and above) by industrial firewalls with deep packet inspection capable of understanding industrial protocols. Unidirectional data diodes are recommended for connections from OT to IT zones where real-time bidirectional communication is not required.
4. Frequently Asked Questions
Q: How does IEC TR 63097 differ from RAMI 4.0?
A: IEC TR 63097 is the international standardisation of the RAMI 4.0 concept. While the original RAMI 4.0 model was developed by German industry association Plattform Industrie 4.0, IEC TR 63097 broadens the scope to include global alignment with IIRA (Industrial Internet Consortium) and other regional smart manufacturing initiatives.
A: IEC TR 63097 is the international standardisation of the RAMI 4.0 concept. While the original RAMI 4.0 model was developed by German industry association Plattform Industrie 4.0, IEC TR 63097 broadens the scope to include global alignment with IIRA (Industrial Internet Consortium) and other regional smart manufacturing initiatives.
Q: What is the recommended approach for migrating legacy PLC systems to the reference architecture?
A: The standard recommends a phased migration: first deploy OPC UA gateways for data access, then gradually replace legacy controllers with TSN-capable devices during scheduled upgrade cycles, and finally implement the AAS framework as a software layer above the existing control infrastructure.
A: The standard recommends a phased migration: first deploy OPC UA gateways for data access, then gradually replace legacy controllers with TSN-capable devices during scheduled upgrade cycles, and finally implement the AAS framework as a software layer above the existing control infrastructure.
Q: Is IEC TR 63097 applicable to small and medium-sized enterprises?
A: Yes. The standard explicitly acknowledges that SMEs may not have the resources for a full implementation. It defines a minimal viable architecture (MVA) profile that strips the framework to its essential components — basic AAS, OPC UA connectivity, and a single-level hierarchy mapping — which can be scaled up as the organisation grows.
A: Yes. The standard explicitly acknowledges that SMEs may not have the resources for a full implementation. It defines a minimal viable architecture (MVA) profile that strips the framework to its essential components — basic AAS, OPC UA connectivity, and a single-level hierarchy mapping — which can be scaled up as the organisation grows.
Q: What role does artificial intelligence play in the reference architecture?
A: IEC TR 63097 situates AI/ML capabilities in the functional layer’s analytics sub-layer. The standard recommends that AI models be deployed as AAS sub-models of the production asset they monitor, with data pipelines defined using the standardised communication interfaces to ensure model portability and reusability across production lines.
A: IEC TR 63097 situates AI/ML capabilities in the functional layer’s analytics sub-layer. The standard recommends that AI models be deployed as AAS sub-models of the production asset they monitor, with data pipelines defined using the standardised communication interfaces to ensure model portability and reusability across production lines.
