Skip to content

Updates answer idgh42 (best practices for creating a system of AAS) #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Updates answer idgh42 (best practices for creating a system of AAS) #138

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
60ecf94
Fixes duplicate link id #id42
seicke Aug 25, 2025
e988629
Updates answer idgh42
seicke Aug 25, 2025
558ffe2
Fix
seicke Aug 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Please address discussions and proposals via issues and pull requests in the git
- [How to define the relationship between asset instance and asset type wrt. corresponding submodels?](#idgh13)

### Asset Administration Shell
- [What are best practices for creating a system of Asset Administration Shells?](#id42)
- [What are best practices for creating a system of Asset Administration Shells?](#idgh42)
- [Where are examples of AAS available?](#id16)
- [Can RDF be used as an interchange format?](#idgh59)
- [Values for externalSubjectId within SpecificAssetId?](#idgh78)
Expand Down Expand Up @@ -111,23 +111,23 @@ As of now, references ignore versioning information. In case versioning is essen

[This AAS example](https://admin-shell-io.github.io/questions-and-answers/Examples/isCaseOf_Examples.aasx) contains a template of "Technical Data" submodel with two properties indicating how alterantive semantic IDs can be used in AAS modeling. For example, the "ManufacturerName" property, has a semantic ID "https://admin-shell.io/sandbox/SG2/TechnicalData/ManufacturerName/1/1" and two isCaseOf references to a ECLASS and a CDD IRDIs (the references are within the ConceptDescription).

**[What are best practices for creating a system of Asset Administration Shells?](#id42)** <a id="id42"></a><!-- ID: 42 -->
**[What are best practices for creating a system of Asset Administration Shells?](#idgh42)** <a id="idgh42"></a><!-- ID: 42 -->

There are currently two ways to create/reference further AAS:
1) Using a BOM (Bill of Material) submodel, a dedicated submodel with self- or co-managed assets
There are currently two ways to create/reference AAS:
1) Creating a submodel by using the [submodel template "Hierarchical Structures enabling Bills of Material" (BOM)](https://github.com/admin-shell-io/submodel-templates/tree/main/published/Hierarchical%20Structures%20enabling%20Bills%20of%20Material)

> Note: Scope of the BOM submodel are relations between *assets* and not *AASs*. BOM submodel defined “isPartOf” and “isIdentical” relation types between assets.
> Note: Scope of the BOM submodel are relations between *assets* and not *Asset Administration Shells*. The submodel defines "SameAs", "IsPartOf" and "HasPart" relationships between assets.

* Self-managed assets have own asset ID which can be used in AAS infrastructure (e.g., a registry) to query available AAS.
* Co-managed assets have no asset ID and own AAS.
* Self-managed assets have their own `globalAssetId` which can be used in an AAS infrastructure (AAS Discovery Service, AAS registry & AAS repository) to query available AAS.
* Co-managed assets do not have an `globalAssetId` and do not have an own AAS.

&nbsp;&nbsp;&nbsp;&nbsp;*Advantages*: BOM-AAS is self-contained and has no “external” dependencies such as references to AAS, probably will be used as blueprint for further submodels.
&nbsp;&nbsp;&nbsp;&nbsp;*Advantages*: Asset Administration Shells with BOM submodel are self-contained and have no "external" dependencies such as references to AAS. They can be used as blueprint for further AAS resp. submodels.

&nbsp;&nbsp;&nbsp;&nbsp;*Disadvantages*: AAS infrastructure for resolution of asset ID to AAS is needed.
&nbsp;&nbsp;&nbsp;&nbsp;*Disadvantages*: AAS infrastructure (AAS Discovery Service, AAS registry & AAS repository) for resolving of `globalAssetIds` to an AAS is needed (cf. [Specification of the Asset Administration Shell Part 2: Application Programming Interfaces](https://industrialdigitaltwin.io/aas-specifications/index/home/index.html)).

2) Direct references to external AAS or Submodels using ReferenceElements or RelationshipElements. We currently do not recommend this method in case of lacking generalizability and creation of tight couplings between AAS (by taking over the “resolution” part).
2) Direct references to (external) AAS or submodels using submodel elements like `ReferenceElement` or `RelationshipElement`. This is not recommend cause of lacking generalizability and creation of tight couplings between AAS.

(Answered: 2021-06-28)
(Answered: 2021-06-28 | Updated: 2025-08-25 | AAS Metamodel v3)

**[How shall a link to a website be entered in an AAS, as File or as ReferenceElement object?](#id2)** <a id="id2"></a><!-- ID: 2 -->

Expand Down