Think Big, Start Small, Scale up!

How to get started with the Asset Administration Shell

Digital Twins are the digital repesentation of an asset, where asset is anything that has an added value to organisations. The AAS is the standardized digital representation of this asset.

The AAS consists of Submodels and can be addressed by unique identifier. Submodels are groups of data based on aspect of an asset, for example a digital nameplate. In addition to this, the semantic definitions, for example based on ECLASS, IEC CDD, can be used to provide unambigious meaning to this data.

23 04 25 IDTA Infografiken Screencast 01
Figure 1. Data groupped in different Submodels of an AAS

Want to learn more about the AAS and Submodels? Have a look at the specifications for the AAS provided by IDTA (Metamodel, API, Data Specification and AASX Package File Format). Additionally, detailed information on different Submodels can be found in IDTA’s Submodel overview.

qr code AASSpec
qr code Submodels

This document considers two different cases: The user is a data provider or a data consumer. In the end, the document also covers a software tools landscape for AAS to ease implementation.

Start for Data Provider

Steps to be followed by data provider:

Step 1

Choose an asset, for instance, a product type from one product class.
🎥 Watch screencast on step 1 and step 2

Step 2

Choose a use case and corresponding Submodel template. We recommend starting with a simple use case of the Digital Nameplate.

Step 3

Model the AAS and the chosen Submodel with the help of a modelling tool (for instance, AASX Package Explorer).
🎥 Watch screencast on step 3

Step 4

Validate the modelled AAS with the AAS-Validators (for instance, AAS test engine).
🎥 Watch screencast on step 4

Step 5

Choose an AAS Server from available open source or proprietary solutions to deploy the modelled AAS. Please refer to the software tools landscape section of this document for more information.
🎥 Watch screencast on step 5

Step 6

Register the AAS with its endpoint into the AAS-Registry to make it discoverable.
🎥 Watch screencast on step 6

Step 7

Repeat for other product types and instances, add more Submodels to the AAS.

DataProviderSteps
Figure 2. Providing Asset-related Information by AAS and Submodels

The result may look as below:

DataProviderResult
Figure 3. Example AAS with Digital Nameplate using AASX Package Explorer

Start for Data Consumer

If you are a consumer and want to access the data from the AAS, you can use the AAS Client to connect and retrieve the information from the AAS-Registry, AAS-Discovery and the AAS-/Submodel-Repositories.

  • Registry (AAS/SM): Directories in which AAS IDs and Submodel IDs are stored together with the associated endpoints.

  • Discovery: Supports fast search and only stores copies of the essential information, i.e. key-value pairs to find IDs based on other IDs.

  • Repositories (AAS/SM): Stores data from the AAS, Submodels and concept descriptions.

Steps to be followed by data consumer:

Step 1

Retrieve an AssetId, for instance from a QR code on the asset, RFID for the asset, firmware of the asset, or an asset database.
🎥 Watch screencast on step 1 to step 4

Step 2

Retrieve the related AAS-Id with AssetId via Discovery Interface ("GetAllAssetAdministrationShellIdsByAssetLink")

Step 3

Retrieve the AAS descriptor with the AAS-Id from step 2 using AAS Registry Interface ("GetAssetAdministrationShellDescriptorById"). This descriptor consists of AAS-Endpoint (typically a URL-path into a repository or to a single AAS).

Step 4

Use the AAS-Endpoint retrieved in step 3 to query the AAS. This AAS consists of all the Submodel-references of the AAS.

Step 5

Choose a Submodel-reference to be used for further steps. For instance, if you want to retrieve the data related to Digital Nameplate, choose the Submodel-reference which consists of the Submodel-Id of Digital Nameplate. The Submodel-Id can be found at key/value in a Submodel-reference.
🎥 Watch screencast on step 5 to step 7

Step 6

Use this Submodel-Id to Submodel Registry Interface to retrieve Submodel-Endpoint ("GetSubmodelDescriptorById").

Step 7

Retrieve the Submodel using the Submodel-Endpoint.

DataConsumerSteps
Figure 4. Retrieval of Asset-related Information by AAS and Submodels

AAS Software Landscape

This section provides information about the AAS tools/solutions based on the level/phase of AAS-implementation.

IDTA fosters the development of reference implementations for the AAS through collaborative open source initiative at Eclipse Foundation called Eclipse Digital Twin Top-Level Project. In addition to the open source tools and Software Development Kits (SDK) mentioned above, there are some proprietary solutions as well. These can be found at IDTA’s Solution-Hub.

241108 IDTA QuickStartGuide Grafik grey
Figure 5. AAS Software Landscape