EXPLAINER · 8 MIN READ

What is an Asset Administration Shell?

The Asset Administration Shell (AAS) is the international standard for creating a structured digital identity for any industrial asset — from a single sensor to an entire production line. Here is everything you need to know in plain language.

The 30-second version

Every physical asset in a factory — a robot arm, a motor, a valve — has datasheets, certificates, maintenance logs, and configuration data scattered across PDFs, Excel files, and ERP systems. The AAS puts all of that data into a single, machine-readable file that any system can consume without custom integration work.

The standard is defined by the Industrial Digital Twin Association (IDTA) and published as IEC 63278. It is the technical foundation for the EU Digital Product Passport and CATENA-X supply chain programs.

AAS structure at a glance

Asset
The physical thing — a motor, a battery, a machine. The AAS describes it but does not replace it.
Submodels
Self-contained data sections. Each covers one topic: Nameplate, Technical Data, Carbon Footprint, Safety Documentation. You pick which submodels you need.
Properties
Inside each submodel are properties — typed key-value pairs like ManufacturerName (string), NominalVoltage (decimal), ManufacturingDate (date).
Semantic IDs
Every property can carry a semantic ID (an IRDI or URI) that links it to an international dictionary like eCLASS or IEC CDD. This is what makes data interoperable.

Why does AAS exist?

Before AAS, integrating two systems in a factory meant writing a custom connector. Multiply that by hundreds of machines from dozens of vendors and you get the system integration hell that has consumed industrial IT budgets for decades.

AAS is the answer: agree on a common data model once, and every vendor who implements it becomes automatically interoperable with every other vendor who does the same. It is the same idea as HTML for web browsers — one format everyone agrees on.

AAS and EU compliance

Jan 20, 2027
EU Machinery Regulation 2023/1230
Technical file must be machine-readable. AAS is the preferred format for digital technical documentation.
Early 2027
EU Battery Regulation 2023/1542
Battery Passport mandatory for EV & industrial batteries. AAS provides the data structure for the DPP.
From 2028
EU Ecodesign Regulation 2024/1781
Digital Product Passport for all product categories by 2030. AAS is the underlying format.
Active now
CATENA-X
Automotive supply chain data exchange network. OEM onboarding requires AAS-formatted submodels.

Frequently asked questions

Is AAS the same as a digital twin?
They overlap. An AAS is a standardized, interoperable digital twin — defined by the IDTA (Industrial Digital Twin Association) and ISO/IEC 63278. A 'digital twin' is any digital representation; an AAS follows a specific schema that makes it machine-readable across vendors.
Do I need to know XML or JSON to create an AAS?
No. AAS Studio's guided wizard and AI extraction let you create valid AAS files without touching XML directly. The editor is there for engineers who want full control.
What's the difference between AAS Type and AAS Instance?
A Type AAS describes a product model — the blueprint. An Instance AAS describes one specific physical item with its serial number, manufacturing date, and actual measured values.
How does AAS relate to the Digital Product Passport?
The EU Digital Product Passport (DPP) is a regulatory requirement. AAS is the technical format used to implement it. When the DPP regulation says you must provide a digital product file, AAS is how you structure that file.
What is a submodel?
A submodel is a self-contained section of an AAS, representing one aspect of an asset (e.g. Nameplate, Technical Data, Carbon Footprint). The IDTA publishes standardized submodel templates so that different companies produce compatible data.

Ready to create your first AAS file?

AAS Studio generates valid AAS files in minutes — no XML expertise required.

Open AAS Studio — free

Command palette

Navigate + run actions