Asset Administration Shell meets OPC UA: Why Both Matter
Administration shell meets OPC UA: Why both are important using the example of the CO₂ footprint (Product Carbon Footprint, PCF)
When it comes to reliable and digital information in the industrial sector, two terms frequently come up:
- Asset Administration Shell (AAS) and
- Open Platform Communications Unified Architecture (OPC UA).
Both have partly different tasks – but complement each other perfectly. Especially when the goal is not only to transmit data, but also to provide it in a way that is understandable, standardized, and reusable.
A great example: the product’s carbon footprint.
What is OPC UA?
OPC UA (Open Platform Communications Unified Architecture) is a widely used standard for communication between machines, sensors, and systems.
It enables data to be transmitted independently of manufacturers, securely, and in a structured format – in real time.
OPC UA is designed specifically for fast and reliable data transport at the operational level (OT): high-frequency, robust, and standardized.
You can think of OPC UA as a stable and standardized transport network for machine data.
Focus: How data is transmitted – standardized, fast, secure, and on the shop floor (OT).
What is the Asset Administration Shell (AAS)?
The Asset Administration Shell (AAS) is the digital twin of a physical or virtual object – such as a machine, a product, or even software.
It describes all relevant information about that asset in a standardized, structured, and machine-readable format – from technical specifications and condition data to usage history.
Think of the AAS as a digital profile – containing characteristics, conditions, capabilities, and historical data.
How do OPC UA and AAS work together?
The Asset Administration Shell is not designed for real-time data, but to structure information and make it reusable, for example by other systems or business partners.
Using so-called AAS connectors, OPC UA data can be transferred directly into the AAS.
Focus:
Cross-domain standard (IT + OT) for the structured description, provision, and use of information – with an emphasis on data meaning and context.
Example: Product Carbon Footprint
A component passes through a production machine. Its carbon footprint should be automatically calculated and stored. For this, the following is needed:
- Real-time data from the machine (via OPC UA):
- e.g., power consumption, operating time, material usage.
- Structure and context (via AAS):
- In a submodel called “Carbon Footprint,” documentation is provided on how the CO₂ value was calculated, which data sources were used, and under which assumptions.
- The result:
- The CO₂ value is not just a number, but traceable, machine-readable, and reusable – for example, in a Digital Product Passport (DPP).
Summary
Together, they enable transparency, automation, and standardized interfaces for applications such as sustainability verification or product passports.
Ready to unlock the full potential of AAS and OPC UA?
Discover how our Neoception® Digital Twin Infrastructure enables the seamless integration of real-time OPC UA data into standardized AAS models – fully aligned with DPP 4.0 requirements and future-ready for your digital transformation.
Let’s bridge the gap between IT and OT – together.