A connected factory is not automatically an interoperable factory. Machines may send data, platforms may display dashboards and suppliers may provide digital documentation—yet each source can still use different identifiers, formats and terminology. Integration then depends on one-off mappings that are expensive to create and fragile to maintain.
The Asset Administration Shell (AAS) addresses this problem at its foundation. It provides a standardised digital representation of an asset, with a defined metamodel, interfaces and semantic structures. The asset may be a machine, component, product, software service or even an abstract entity such as a process. Its shell gives other systems a consistent way to identify it and interact with its information.
A common structure without a monolithic platform
The AAS is sometimes described simply as a digital twin. That shorthand is useful, but incomplete. Its particular value lies in standardisation: it makes digital representations portable and understandable beyond the system in which they were created.
Information is organised into modular submodels. One submodel may describe technical data, another carbon footprint, another documentation, operational state, maintenance or nameplate information. Agreed submodel templates can give the same concepts the same structure and meaning across manufacturers and software products.
This does not require all industrial data to be copied into one central database. An AAS can expose information from distributed sources through standard interfaces. It can also be packaged for exchange when an offline handover is appropriate. The architecture can therefore remain federated while presenting a coherent digital view.
What interoperability requires in practice
A scalable industrial data ecosystem needs more than connectivity. It needs agreement at several levels:
— Technical interoperability: Systems can connect and exchange data through defined APIs and protocols.
— Syntactic interoperability: The structure and format of the exchanged data are understood.
— Semantic interoperability: A receiving system can interpret what a value means, including its unit, context and classification.
— Organisational interoperability: Responsibilities, access rights and lifecycle processes are clear across participating organisations.
The AAS specifications directly support the first three levels and provide building blocks for the fourth. Security, governance and commercial agreements still have to be designed for the use case; no technical standard removes that responsibility.
One digital thread across the asset lifecycle
Consider a production machine. During procurement, a standardised AAS can communicate technical capabilities and interface requirements. During commissioning, it can support configuration and documentation exchange. In operation, it can provide access to condition data and maintenance information. When the equipment is modified, relevant records can be updated without breaking its identity.
The same principle can connect product engineering, manufacturing and circularity use cases. AAS submodels can supply structured information to a Digital Product Passport, while operational data can support Industrial AI or a digital twin. Instead of building a separate data model for each project, organisations can reuse a common representation.
Adoption should be use-case-led
An AAS programme should not begin by modelling the entire factory. It should begin with a business or engineering interaction that is currently slow, manual or difficult to scale.
A focused demonstrator can follow six steps:
- Select one asset type and one cross-system exchange.
- Define the participating roles and decisions.
- Reuse an existing submodel template where possible.
- Connect the AAS to authoritative source data.
- Test the exchange with at least two independent systems or organisations.
- Measure integration effort, data quality and operational value.
This approach reveals whether identifiers, semantics, access control and ownership work under realistic conditions. It also produces a reference pattern that can be extended to additional assets and partners.
Asset Administration Shells are not a finished data ecosystem on their own. They are something more useful: a standard foundation on which ecosystems can be built without redefining every interface from the beginning.
EIRAS supports AAS architecture, submodel design and standards-based demonstrators. Contact us to identify a high-value interoperability use case in your product or production environment.