What is the Asset Administration Shell?
The Asset Administration Shell (AAS, German: Verwaltungsschale) is the standardised digital representation of a physical or logical asset, exposing all of that asset’s information and functions in machine-readable submodels so that systems from different vendors can exchange it without custom integration. The AAS originated in Germany’s Industry 4.0 programme and is often called “the digital twin of Industrie 4.0”. Its structure is defined internationally in IEC 63278-1, while the Industrial Digital Twin Association (IDTA) maintains the technical specifications and submodel templates.
🎯 Why does industry need an Asset Administration Shell?
A pump, variable-speed drive or complete machine arrives with dozens of documents and datasets: datasheets, manuals, certificates, CAD models, maintenance instructions and process data. Every supplier delivers them in its own format, and every customer re-keys them by hand into its ERP, asset management system or engineering tool. That is slow and error-prone.
The AAS replaces this with one agreed structure:
- One identity per asset — every asset and every AAS gets a globally unique identifier, usually an IRI
- Fixed building blocks — information lives in standardised submodels such as the nameplate or technical data
- Unambiguous meaning — each data element points via a semantic ID to a definition in a dictionary such as ECLASS or IEC CDD
- The whole lifecycle — from design and engineering through operation and maintenance to recycling, in line with lifecycle management
🧠 How does an Asset Administration Shell work?
An AAS is a “shell” wrapped around the asset. Together, asset and shell form an Industrie 4.0 component, as described in the RAMI 4.0 reference model (DIN SPEC 91345). The shell does not hold free-form data but follows a fixed metamodel:
| Building block | Purpose | Example |
|---|---|---|
| Asset information | Links the AAS to the asset and states whether it describes a type or an instance | globalAssetId, serial number |
| Submodel | One well-defined aspect of the asset, with its own semantic ID | Digital Nameplate, Technical Data, Carbon Footprint |
| Submodel element | The actual data item or function inside a submodel | Property, Range, File, Operation, Entity |
| Semantic ID | Reference to the meaning of an element | ECLASS property following IEC 61360 |
| Concept description | Definition of a concept within the AAS itself, for example taken from a dictionary | Unit, data type, definition |
The distinction between type and instance matters. The manufacturer supplies a type AAS describing the product model; each delivered unit gets an instance AAS holding its serial number, calibration data and maintenance history.
📚 What types of AAS are there?
The specifications distinguish three forms, in increasing order of interactivity:
| Type | Form | Exchange | Typical use |
|---|---|---|---|
| Passive (type 1) | File: AASX, JSON or XML | Download or email | Handing over product data at delivery |
| Reactive (type 2) | Server with an API | HTTP/REST or OPC UA | Querying and updating during operation |
| Proactive (type 3) | Autonomous software agent | Industrie 4.0 language (VDI/VDE 2193) | Negotiating production orders; mostly research |
The AASX format is a ZIP package based on the Open Packaging Conventions (ISO/IEC 29500-2), the same foundation as Office files. It contains the AAS models plus attachments such as PDF manuals and images. For type 2, the API specification describes, among other things, a registry (where is which AAS?), a repository (the AAS and submodels themselves) and a discovery service that finds the right AAS for a given asset ID.
🕰️ How did the AAS emerge and become a standard?
| Year | Milestone |
|---|---|
| 2016 | Plattform Industrie 4.0 publishes Struktur der Verwaltungsschale; RAMI 4.0 appears as DIN SPEC 91345 |
| 2020 | IDTA founded on 23 September by VDMA, ZVEI, Bitkom and twenty companies including ABB, Bosch, Festo, SAP, Schneider Electric and Siemens |
| 2021 | OPC 30270, the OPC UA mapping of the AAS, is published by a joint working group of the OPC Foundation, ZVEI and VDMA |
| 2023 | IDTA releases version 3.0 of the specifications; IEC 63278-1 is published in December |
| 2024 | Adopted in Europe as EN IEC 63278-1 |
| 2025 | IDTA publishes Part 4: Security, with an access rule model |
The IDTA specifications are split into parts: Part 1 (metamodel), Part 2 (APIs), Part 3 (data specifications, including IEC 61360), Part 4 (security) and Part 5 (AASX). Within IEC TC 65, IEC 63278-2 (information metamodel, at DIS stage in 2026) and IEC 63278-3 (security provisions) are still under development.
🔄 How does the AAS relate to OPC UA, ISA-95 and the Unified Namespace?
The AAS does not compete with existing OT standards; it complements them with a different focus:
| Standard | Focus | Relationship with the AAS |
|---|---|---|
| Digital Twin | General concept | The AAS is a concrete, standardised implementation of it |
| OPC UA | Real-time communication and information models | Transport layer for a reactive AAS via OPC 30270 |
| ISA-95 | Hierarchy and functions from ERP to MES and control | The AAS describes a single asset; ISA-95 the organisation around it |
| Unified Namespace | Live process data via a broker such as MQTT | Enriched with static context from the AAS |
| Module Type Package | Connecting process modules to an orchestration layer | The MTP file can travel inside an AAS as an attachment or submodel |
Put simply: OPC UA and the Unified Namespace tell you what a machine is doing now; the AAS tells you what the machine is and what you need to know about it.
🏭 What is the Asset Administration Shell used for?
The IDTA maintains a catalogue of standardised submodel templates. Some of the most widely used:
- Digital Nameplate (IDTA 02006) — the digital rating plate with manufacturer, type, serial number and markings. A QR code following IEC 61406 on the device can link straight to the AAS.
- Handover Documentation (IDTA 02004) — structured handover of manuals and certificates following VDI 2770
- Carbon Footprint (IDTA 02023) — the carbon footprint of the product and its transport, used in supply-chain reporting
- Technical Data — technical properties, linked to ECLASS
- Digital Battery Passport (IDTA 02035) — a series of seven submodels developed together with the automotive data ecosystem Catena-X
That last one touches European law. The Ecodesign for Sustainable Products Regulation (EU) 2024/1781 (ESPR), in force since 18 July 2024, introduces the Digital Product Passport, which becomes mandatory product group by product group through delegated acts. The Battery Regulation (EU) 2023/1542 requires a battery passport from 18 February 2027 for, among others, EV batteries and industrial batteries above 2 kWh. The AAS is frequently cited as a technical foundation for such passports.
🔧 How do you get started with the Asset Administration Shell?
For an asset owner or machine builder, a step-by-step approach works best:
- Start with procurement — ask suppliers of new components for an AASX containing at least the Digital Nameplate and Handover Documentation
- Pick a small use case — for example automatically populating the asset register or the maintenance system at handover
- Use open-source tools — the AASX Package Explorer to view and create packages, Eclipse BaSyx for an AAS server
- Connect existing systems — let the AAS server supply master data to ERP, MES or a predictive maintenance application
- Fix the semantics — use existing IDTA templates and ECLASS properties instead of your own field names
- Build in security from day one — see the next section
Machine builders who will supply digital instructions under the Machinery Regulation from 2027 can publish them through the same AAS.
🔐 How do you secure an Asset Administration Shell?
An AAS holds valuable and sometimes sensitive information: configurations, firmware versions, network addresses and intellectual property. A reactive AAS with write access is also a route into the asset itself. Key measures:
- Access rules — IDTA Part 4 uses attribute-based access control (ABAC) down to the level of a single submodel element
- Strong authentication — tokens via OAuth 2.0 or OpenID Connect, connections over TLS only
- Integrity — AASX packages can be digitally signed with X.509 certificates under the Open Packaging Conventions; organise proper certificate management for this
- Segmentation — place AAS servers not in the control network but in a DMZ or at level 3, following the zones and conduits of IEC 62443
- Read-only where possible — allow write access to process parameters through the AAS only after an explicit risk assessment
❓ Frequently asked questions
What is the difference between an AAS and a digital twin?
A digital twin is the general concept of a digital counterpart of a physical object. The Asset Administration Shell is a concrete, internationally standardised implementation of that concept, with a fixed metamodel, submodels and APIs. Thanks to the AAS, digital twins from different vendors can work together.
Is the Asset Administration Shell an official standard?
Yes, the structure of the Asset Administration Shell is defined in IEC 63278-1:2023 and adopted in Europe as EN IEC 63278-1. The detailed technical specifications, such as the metamodel, the APIs and the AASX format, are maintained by the Industrial Digital Twin Association. Parts 2 and 3 of IEC 63278 are still under development.
What is an AASX file?
An AASX file is the package format of the Asset Administration Shell, based on the Open Packaging Conventions. It bundles the AAS, its submodels and attachments such as manuals into a single file. You can open an AASX file with the free AASX Package Explorer.
What is a submodel in the AAS?
A submodel is a self-contained part of the Asset Administration Shell that describes one aspect of an asset, such as the nameplate, the technical data or the carbon footprint. The IDTA publishes standard submodel templates so that every supplier uses the same structure and meaning.
Does the AAS use OPC UA?
The Asset Administration Shell can be exposed through OPC UA following the companion specification OPC 30270, but this is not mandatory. An AAS can also be offered as a file (AASX, JSON or XML) or through an HTTP/REST API. In practice, REST APIs are widely used for master data.
Do you need the AAS for the Digital Product Passport?
European legislation does not prescribe a specific technology for the Digital Product Passport. The Asset Administration Shell is, however, a frequently cited technical foundation, because submodels such as Digital Nameplate, Carbon Footprint and Digital Battery Passport already exist.
📌 In summary
The Asset Administration Shell is the standardised digital twin of Industry 4.0: one identity, fixed submodels and unambiguous semantics per asset, defined in IEC 63278 and maintained by the IDTA. Organisations that require AASX files in procurement today and secure their AAS servers properly lay the groundwork for efficient handover, maintenance and the coming Digital Product Passport.