Part 3a: Data Specification Template IEC 61360 (IDTA-01003-a)

Specification of the Asset Administration Shell

This specification is part of the Asset Administration Shell Specification series.

Version

This is version 3.1 of the specification IDTA-01003-a.

Previous version: 3.0.2

Notice

Publisher and Copyright: Industrial Digital Twin Association e.V. (IDTA)

IDTA Document Number: IDTA-01003-a-3-1

This work is licensed under a Creative Commons Attribution 4.0 International License.

SPDX-License-Identifier: CC-BY-4.0

How to Get in Contact

Contact: IDTA

Sources: GitHub

Feedback:

Editorial Notes

This document, version 3.1, was produced from Dec. 2022 on by the Workstream "Asset Administration Shell Specifications" of the working group o "Open Technology" of the Industrial Digital Twin Association (IDTA).

The document "Details of the Asset Administration Shell – Part 1 – The exchange of information between partners in the value chain of Industrie 4.0, V3.0RC02" was split into several parts. One of them is this document, which represents Part 3a and describes a data specification that is defined to be used with the core model as specified in Part 1. This is also why versioning now starts with V3.0: it is only valid in combination with V3.0 of Part 1.

Version 3.0 of this document was produced from June 2022 to November 2022 by the sub working group "Asset Administration Shell" of the joint working group of the Plattform Industrie 4.0 working group "Reference Architectures, Standards and Norms" and the "Open Technology" working group of the Industrial Digital Twin Association (IDTA). It is the first release published by the IDTA.

For a complete history, please refer to Part 1 of the document series " Specification of the Asset Administration Shell: Part 1 Metamodel".

Versioning

This specification is versioned using Semantic Versioning 2.0.0 (semver) and follows the semver specification [13].

Conformance

The key words "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.)