How to leverage SAMM Aspect Models for Submodel Templates in the Asset Administration Shell

Imprint

Joint publication of Industrial Digital Twin Association (IDTA) and Catena-X e.V.

Publisher

Industrial Digital Twin Association
Lyoner Strasse 18
60528 Frankfurt am Main
Germany
https://www.industrialdigitaltwin.org/

Catena-X Automotive Network e.V.
c/o beyond Quartier Heidestrasse
Heidestraße 34, 10557 Berlin
https://www.catena-x.net/

Version history

Date Version Comment

June 2026

V1.0

First version. Result of joint expert group between Industrial Digital Twin Association (IDTA) and Catena-X e.V.

How to Get in Contact

Contact: IDTA

Sources: GitHub

Feedback:

Editorial Notes

This document is the result of a joint expert group between Industrial Digital Twin Association (IDTA) and Catena-X e.V.

Versioning

This specification is versioned using Semantic Versioning 2.0.0 (semver) and follows the semver specification [36] with the following deviations:

  • patch releases are bugfix releases and are not necessarily backward compatible. They shall be used.

Conformance

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC2119 RFC8174[1]:

  • MUST word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.

  • MUST NOT This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.

  • SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

  • SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

  • MAY This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)