Companion specification · Tier 2

I4AAS / AAS

Version5.0.0
Published2021-06-04
Namespacehttp://opcfoundation.org/UA/I4AAS/
SectorDigital twin

A mapping of the Asset Administration Shell into OPC UA. The AAS is the Industrie 4.0 digital twin container, and this nodeset - at version 5.0.0 from 2021 - lets an OPC UA server expose AAS structure.

Where it sits in the stack

Built on the core information model. The AAS itself is specified elsewhere and evolves on its own schedule, which is the main thing to understand about this mapping.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the type inventory of this mapping.

Using it on a real machine

  1. Understand what an AAS is forIt is a standardised container for everything known about an asset across its lifecycle - documentation, capabilities, runtime data - not a machine data model.
  2. Check the version relationshipThe nodeset is from 2021 while the AAS specification has continued to develop. Establish which AAS version a given implementation targets.
  3. Do not expect it to replace a machine modelAn AAS may reference runtime data, but your state and counts still come from Machinery or a sector model.

What it gives you for OEE

No direct contribution. The AAS is a lifecycle and documentation container. It can reference the runtime data that feeds OEE, but it does not provide it.

Try it free: No free public server exposes this model as far as we know. To see it you need a machine that implements it or a vendor demo. If you find a public endpoint, tell us and we will add it.

Gotchas

  • The nodeset is from 2021 while the AAS specification has moved on. Version alignment is the main risk.
  • Lifecycle and documentation container, not a runtime data model. A very common misunderstanding.
  • Substantial ecosystem activity around AAS generally, less around this specific OPC UA mapping.
Verify before you rely on this: The relationship between this 2021 nodeset and current AAS specification versions is not something we have verified, and it is the most important question about this model. The type inventory on this page is deliberately short. We list only type names we are confident of and would rather publish five correct ones than twelve with four wrong. Browse a real server or the released nodeset for the complete list.
Related models

Once the machine speaks a companion spec, the OEE mapping is portable across vendors, which is the point at which analytics stops being a per-machine project.

See Jemba →

Last verified 7 September 2026 against OPC UA 1.05.07. Version and publication date read from the released nodeset. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.

Free download
OPC UA Machine Data → OEE Mapping Kit
Which nodes to subscribe to, how they become Availability, Performance and Quality, and which companion specification already gives you the answer, so you stop inventing tags.
Get the free mapping kit →
Free, no course, no login