The Asset Administration Shell (AAS, standardised internationally as IEC 63278) is one of the most important industrial data standards of the past decade. Developed by the Industrial Digital Twin Association (IDTA) and backed by ZVEI, VDMA, and Bitkom, it does something genuinely hard well: it gives a physical asset a precise, machine-readable digital twin, organised into submodels, each one a self-contained, standardised description of one facet of the product. This is not a critique of AAS. AAS is excellent, and this post is about how well it lines up with something built beside it.
Same vision, different output
The AAS and the EU Digital Product Passport (DPP) chase the same idea: structure product data, make it machine-readable, make it portable across a supply chain. They arrive at that idea from different directions, and they produce different outputs. The interesting part is how close the two actually sit.
The European Commission has not treated AAS as a rival. It actively references AAS submodels as a technical foundation for DPP data structures, notably the Digital Nameplate submodel and the Carbon Footprint submodel. That is a strong signal about where the convergence is heading.
The Digital Nameplate is already half a passport
Look at what the Digital Nameplate submodel already carries: manufacturer and product designation, serial number, production date, article number, base technical data, certifications, and declarations of conformity. That list is close to the minimum a DPP has to expose. A manufacturer who has maintained a Digital Nameplate submodel has, without setting out to, already done roughly half the work of a Digital Product Passport.
What AAS does not produce on its own
Here is the honest gap. Structured submodel data is necessary for a DPP. It is not sufficient. On its own, AAS does not produce four things the EU regulation requires as its published output:
- a GS1 Digital Link, the URI standard the DPP uses as its identifier surface, so a scanner resolves to the right passport;
- a cryptographic signature that an authority or an auditor can independently verify, rather than trust on assertion;
- a consumer-facing QR code channel printed on the physical product;
- the packaging labelling the PPWR packaging regulation will require.
Call those four the regulatory output layer. They are the difference between structured industrial data and a passport that a regulator, a recycler, and a consumer can each actually pick up and use.
Where Transpareo fits: as the output layer, not a second twin
That output layer is precisely what Transpareo is, and the arrangement is complementary by design. The AAS stays the single point of truth. AAS submodel data flows via REST API into Transpareo. Transpareo produces the EU-compliant DPP as output: signed, GS1-Digital-Link-addressed, QR-reachable, and register-ready. The signed version history is rendered by the Transpareo Time Machine, a browser-verifiable, cryptographically signed record of every version, released as open source under GPL v3 so its verification does not depend on trusting Transpareo.
No second data-maintenance system. No parallel model to keep in sync. No double work. Your submodel stays where it lives; the passport is generated from it.
All of this is available today, without waiting for the mandate. When the DPP obligation arrives for your segment, the remaining step is the link to the EU register.
The bridge is the opportunity
The convergence of AAS and DPP is the part worth watching, and it is underway right now, with the EU citing AAS submodels as the technical basis. The bridge from a structured AAS submodel to a published, signed, QR-linked DPP is an opening for the AAS community, not a competing ecosystem trying to replace it. If you want to see why that output layer builds on open, resolvable semantics in the first place, the reasoning is in our post on EN 18223.
So a genuine question to the people running AAS in production: how does your AAS connect, or how do you plan to connect it, to your DPP obligations? Which submodels do you expect to map cleanly, and where do you see the seams? We would rather hear how you are thinking about it than assume.