- General
Asset Administration Shell and ECLASS: What your PIM must deliver for digital twins and product passports
At a glance:
- The Asset Administration Shell (AAS) is the Industry 4.0 standard for digital twins. It structures product data into standardised submodels such as nameplate, technical data and documentation.
- ECLASS defines what this data means: each property receives a unique identifier (IRDI) that machines can interpret without further clarification. Many AAS submodels use ECLASS as their core semantic framework.
- Since July 2026, harmonised European standards for the Digital Product Passport (EN 18216 and EN 18219 to EN 18223) and an EU registry have been in place. An AAS is not automatically a product passport, but a product passport can be derived from an AAS.
- The next firm deadlines: the Machinery Regulation applies from 20 January 2027, and the battery passport from 18 February 2027. For iron and steel, the first product-specific legal act under the Ecodesign Regulation has been announced for the end of 2026.
- The PIM supplies type-level data: properties with ECLASS identifiers, units, documents and environmental metrics for each product model. Data about individual units, such as serial numbers or condition, comes from ERP, MES or the device itself.
In our article on the Packaging and Packaging Waste Regulation (PPWR), we described how mandatory information becomes new master data. The Asset Administration Shell takes this a step further: product data must not only be complete, but also available in a format that machines, customers and authorities can read without translation. For manufacturers in mechanical engineering, electrical engineering and automation, this has been a topic for years. The Digital Product Passport is making it relevant to other industries too.
This article explains what AAS and ECLASS are, how they relate to the product passport and what responsibilities this creates for the PIM.
What is the Asset Administration Shell?
The Asset Administration Shell is the standardised digital representation of a product or industrial asset. It was developed within Plattform Industrie 4.0, and its specifications are now maintained by the Industrial Digital Twin Association (IDTA). Its structure is also standardised internationally (IEC 63278-1). The metamodel is available in version 3.2, with version 3.3 in development.
An AAS consists of submodels. Each submodel describes one aspect of the product using a defined template. The IDTA publishes these as Submodel Templates. The following are particularly important for PIM:
| Submodel | IDTA number and version | Content | Typical source |
|---|---|---|---|
| Digital Nameplate | 02006, version 3.0.1 | Manufacturer, product designation, type, markings | PIM (type-level data), ERP or manufacturing (serial number, year of manufacture) |
| Technical Data | 02003, version 2.0 | Technical properties, organised by classification | PIM |
| Handover Documentation | 02004, version 2.0 | Operating instructions, certificates and data sheets with metadata in accordance with VDI 2770 | DAM or document management, linked in the PIM |
| Carbon Footprint | 02023, version 1.0 | Product CO2 values by life cycle stage | Life cycle assessment tool, maintained per model in the PIM |
| Digital Battery Passport | Series 02035, parts 1 to 7, version 1.0 | Nameplate, documentation, carbon footprint, technical data, condition, material composition, circularity | PIM for model-level data, battery management and ERP for condition and individual battery data |
| Digital Product Passport, Part 1: Metadata | 02099-1, version 1.0.1 | Mandatory information for every product passport, such as identifiers and granularity | PIM and ERP |
The table highlights an important point: no submodel draws all its data from a single system. The PIM is responsible for type-level data, meaning everything that is the same for every unit of a product model.
The role of ECLASS
A submodel defines where a value belongs. Semantics define what that value means. This is where ECLASS comes in. Each ECLASS property has a globally unique identifier, the IRDI, for example 0173-1#02-AAC895#008. In the Asset Administration Shell, this identifier is attached to the data element as its semantic ID. The associated dictionary, containing the name, unit, data type and definition, follows IEC 61360.
ECLASS itself states that many submodels use ECLASS as their core semantic framework, including Handover Documentation and Technical Data. Companies that classify their products according to ECLASS today have therefore already done much of the work required for the Asset Administration Shell. However, this only applies if the properties in the PIM are maintained with their IRDI and the correct unit, not just a descriptive name.
ECLASS continues to evolve. Version 16.0 was released on 28 November 2025 with 995 new classes and 1,253 new properties. Around 23,300 class definitions were created using AI and are labelled as machine-generated. Work on version 17.0 has been underway since May 2026, including a new segment for waste and residual materials. For PIM, this means that version upgrades are part of ongoing operations and require a migration strategy.
And what about ETIM? In electrical wholesaling and building services, ETIM is the more important standard. Many manufacturers therefore maintain both classifications. For the Asset Administration Shell, mapping accurately to ECLASS properties makes sense because the widely used submodels are based on them.
Asset Administration Shell and Digital Product Passport
The Digital Product Passport (DPP) is being introduced through the Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) and product-specific rules such as the Batteries Regulation. Its technical framework has been defined since July 2026:
- Standards: Implementing Decision (EU) 2026/1736 of 14 July 2026 published the harmonised standards for the product passport in the Official Journal. The series of standards covers unique identifiers (EN 18219), data carriers such as QR codes (EN 18220), storage (EN 18221), interfaces (EN 18222), interoperability (EN 18223) and data exchange (EN 18216), among other aspects.
- Registry: Implementing Regulation (EU) 2026/1778 of 16 July 2026 governs the EU registry in which product passports are registered.
The IDTA makes it clear: an Asset Administration Shell alone is not a product passport as defined by these standards. However, a product passport can be derived from an existing AAS if it contains the required submodels as well as the metadata submodel IDTA 02099. For manufacturers already generating Asset Administration Shells, this is the shortest route to a product passport. Companies without an AAS do not necessarily have to adopt one, as the standards are technology-neutral. However, the AAS is the route that the Industry 4.0 community has prepared for the product passport.
Read more about the product passport itself in our guide to the Digital Product Passport and in the PIM Wiki.
Key dates through to 2029
| Date | What applies | Implications for product data |
|---|---|---|
| End of 2026 (announced) | First product-specific delegated act under the Ecodesign for Sustainable Products Regulation: iron and steel | First specific product passport requirements for a product group |
| 20 January 2027 | Machinery Regulation (EU) 2023/1230 applies | Operating instructions may be provided digitally; they must remain accessible online for the lifetime of the machine, and for at least ten years. Paper copies must be provided free of charge on request. |
| 18 February 2027 | Battery passport under Article 77 of the Batteries Regulation (EU) 2023/1542 | Mandatory for light means of transport batteries, industrial batteries above 2 kWh and electric vehicle batteries, accessible via QR code; from the same date, all batteries must carry a QR code. Details in the article Battery passport and PIM |
| 2027 to 2029 (working plan) | Further acts under the 2025 to 2030 working plan: textiles and tyres in 2027, furniture and aluminium in 2028, mattresses in 2029 | Product passports for additional product groups, each with a transition period following the relevant act |
The years in the Commission’s working plan are indicative dates for the adoption of the acts. The obligations only apply after a transition period. For manufacturers of machinery and components, 2027 is nevertheless the crucial year, as the Machinery Regulation and battery passport requirements take effect four weeks apart.
What the PIM system needs to deliver
Most manufacturers already have the data for an Asset Administration Shell, but it is scattered across systems and lacks semantics. We recommend six steps:
- Clarify the obligations for each product group: Which products fall under the Batteries Regulation, the Machinery Regulation or a future act under the Ecodesign for Sustainable Products Regulation? Which customers are already asking for Asset Administration Shells?
- Separate type and instance data: Define which data is held in the PIM for each product model and which comes from ERP, MES or the device for each individual instance. This boundary determines the architecture.
- Maintain classification with identifiers: Store the ECLASS class and properties with their IRDI, version and unit. If ETIM is your primary standard, maintain a mapping to ECLASS.
- Link documents: Operating instructions, declarations of conformity and data sheets need document classes in accordance with VDI 2770, a language and a version. The files are usually stored in the DAM, while their links to products are maintained in the PIM.
- Include environmental metrics: Carbon footprint and material composition data usually come from life cycle assessment tools. The PIM holds the verified values for each model, together with their source and reference date.
- Generate and deliver AAS: The PIM either exports AASX or JSON files based on the IDTA metamodel or supplies an AAS server via an interface. Open-source components such as Eclipse BaSyx are widely used. The product passport also requires an identifier in accordance with EN 18219, a QR code and registration.
The third step usually requires the most effort. If you currently maintain properties as free text or use your own names, you will need to map them properly to ECLASS once. This is worthwhile even without a product passport, as the same data can better support catalogues, dealers and marketplaces.
Questions to ask your PIM vendor
- Can properties carry an ECLASS IRDI, version and unit, and how does a migration from ECLASS 15 to 16 or 17 work?
- Does the system generate Asset Administration Shells based on the IDTA metamodel 3.x, as AASX files, as JSON or via an interface to an AAS server?
- Which submodels are available out of the box, such as Digital Nameplate, Technical Data, Handover Documentation and Carbon Footprint?
- How are documents from the DAM assigned using document classes in accordance with VDI 2770?
- How do you connect type data from the PIM with instance data from ERP or MES?
- Which customers in our industry are already using the system to generate Asset Administration Shells or product passports?
For an overview of PIM systems for manufacturers, see our comparisons for mechanical engineering and the electrical industry, as well as our PIM vendor directory.
Frequently asked questions
Is the Asset Administration Shell the same as the Digital Product Passport?
No. The Asset Administration Shell is a standard for digital twins, while the product passport is a legal requirement with its own standards. A product passport can be derived from an Asset Administration Shell if it contains the required submodels and the IDTA 02099 metadata submodel.
Is the Asset Administration Shell required by law?
No. The European standards for the product passport are technology-neutral. However, the IDTA has published submodels for the product passport and battery passport, making the Asset Administration Shell a suitable technical foundation.
Do I need ECLASS if I use ETIM?
Not necessarily, but it helps. Widely used submodels such as Technical Data and Handover Documentation use ECLASS as their core semantic framework. If ETIM is your primary standard, you should establish a mapping to ECLASS properties.
Which data comes from the PIM?
All type data, meaning information that is identical for every instance of a product model: technical properties, nameplate data without the serial number, documents and environmental metrics for each model. The serial number, year of manufacture, condition and usage data come from ERP, MES or the device.
Your next step
Want to know whether your PIM is ready for the Asset Administration Shell and product passport? We provide a vendor-neutral review of your data model, classification and interfaces, and identify the gaps you should close by 2027. The initial consultation is free: Book an appointment.
As of October 2026. Dates are based on legislation and the Commission’s working plan; indicative timelines may change.
Sources
- IDTA: Specification of the Asset Administration Shell, Part 1 Metamodel v3.2, Annex Digital Product Passport
- IDTA 02099-1: Digital Product Passport, Part 1: Metadata, Version 1.0.1 (July 2026)
- IDTA: AAS Submodel Templates (overview)
- IDTA: 3 Questions to Oliver Hillermeier on the Submodel Handover Documentation (30.03.2023)
- IEC 63278-1: Asset Administration Shell for industrial applications, Part 1: Structure
- ECLASS: ECLASS in the AAS (24.03.2025)
- IDTA and ECLASS: Semantic Transport, ECLASS in AAS (October 2024)
- ECLASS: Release 16.0 now available (28.11.2025)
- ECLASS: Development of Release 17.0 started (05.05.2026)
- EUR-Lex: Implementing Decision (EU) 2026/1736 on harmonised standards for the digital product passport
- EUR-Lex: Implementing Regulation (EU) 2026/1778 on the registry for digital product passports
- WIoT: CEN-CENELEC publishes six EU DPP standards (EN 18216, EN 18219 to EN 18223)
- European Commission: Digital Product Passport, Iron and Steel
- One Click LCA: The first ESPR working plan 2025 to 2030
- Regulation (EU) 2023/1542, Article 77 (battery passport)
- WEKA: Operating instructions under the new Machinery Regulation, fact check
- Produktion: Machinery Regulation, what changes from 2027
Request vendor-neutral advice
Want to know whether your PIM is ready for the Asset Administration Shell, ECLASS and product passport? We provide a vendor-neutral review of your data model, classification and interfaces.
PIM Market Update newsletter
Acquisitions, new vendors and practical tips: by email every six to eight weeks
Concise and vendor-neutral: what is changing in the PIM market and what it means for your selection process. Unsubscribe at any time.
More PIM insights
News & Blog

PIM in Austria: systems, integrators and local requirements 2026
Austrian manufacturers and retailers typically sell throughout the DACH region and comply with the same EU rules as companies in Germany. Some requirements, however, are

PIM and DAM: choose one vendor or separate systems?
Product images, data sheets, certificates and videos are all part of a product’s information. That is why many PIM vendors offer their own DAM module,

PIM in Corporate Groups: What Matters with Multiple ERP Systems
In large enterprises, product data rarely comes from a single ERP system. Acquisitions, national subsidiaries and production sites bring their own systems, often with different

PIM for Small Businesses: Systems and Costs on a Tight Budget
Small businesses rarely need an enterprise PIM, but often need more than a spreadsheet and their online store’s product management features. Once the same product

Multilingual product data: German, French and Italian in PIM
Which languages Swiss regulations require for product information, how a PIM handles German, French and Italian, and which questions you should ask vendors.

Battery passport from February 2027: What data your PIM must provide
From 18 February 2027, battery passports will be mandatory for LMT, industrial and electric vehicle batteries, with QR codes required on all batteries. Find out which data comes from PIM, ERP and battery management systems.
