Click here to go back to frontpage Industrial Digital Twin Association
Industrial Digital TwinAssociation

Home » Content Hub » Submodels

AAS Submodel Templates

Submodels constitute the content of the Asset Administration Shell. They describe content-related or functional aspects of an asset. Find the overview of the official IDTA submodel templates here.

IDTA SUBMODELS

Registered AAS Submodel Templates

You would like to develop your own submodel templates or collaborate in the development of the listed submodel templates?

Find the process described here. For further questions, contact us via email.

Number of our submodels:
Number of our submodels:
0
Status
Published
In Review
In Development
Proposal submitted
Select sorting
Sort by IDTA numbers
Sort by name
Submodel Template
IDTA Number
Version
Status
Downloads & Links
R-Strategy Decision Support System
02098
1.0
In Development
Coming soon

The focus of this submodel is to standardize the data model needed to take the decision which R-Strategy is the most fitting in the context of a circular economy (also called R-Grading or R-Strategy-Assist). Data is related to the use phase (instance) and the engineering phase (type) of an asset (component, machine, or just product). This SM is an input for algorithms, simulations, etc. that producers can use to decide which R-Strategy is the most suitable for their products.
R-Strategies, that are in focus of this tool, are reuse, repair, refurbish, remanufacture, repurpose and recycling.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Manufacturing Work Description
02100
1.0
In Development
Coming soon

The Submodel Manufacturing Work Description is aligned with the ISA‑95 Work Master concept and defines what is required to execute a manufacturing job at the Manufacturing Operations (Level 3) layer. It provides a structured and semantically described work definition covering parameter specifications and required personnel, equipment, physical assets, and material (including quantities and units). It is intended to complement technical process configuration models (e.g., Process Parameters submodel) by focusing on the work requirement package needed to prepare and run manufacturing operations.

Use Case:
Manufacturing job/work-package definition for MES → Provide a standardized work definition (required resources + parameter specs) used for detailed scheduling, dispatching, and shop-floor coordination.
Resource feasibility and selection →Expresses required personnel/equipment/material conditions so that planners and orchestration systems can select eligible resources.
Engineering-to-Operations handover →Transfer an approved “work master” definition from engineering/process planning to operations in a consistent, machine-readable form (to reduce interpretation errors and manual re-entry).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Maintenance Inspection Documentation
02101
1.0
In Development
Coming soon

The Submodel Maintenance Inspection Documentation addresses the domain of industrial maintenance and inspection. Its purpose is to provide a structured, machine-readable, and interoperable representation of maintenance and inspection documentation.

Inspection (Maintenance) reports often contain critical information for the operator, such as identified defects, regulatory requirements, or scheduling of the next inspection. These reports frequently require follow-up actions. To avoid manual extraction and entry of this information, the MaintenanceInspectionDocumentation captures it in a standardised and unambiguous format. This enables automated processing, such as task generation, deadline tracking, or integration into digital maintenance workflows.

The inspection report itself, along with any attachments, is referenced in the submodel HandoverDocumentation. For future inspections, the MaintenanceInspectionDocumentation is used to provide the necessary procedures and requirements.

This Submodel supports the creation of a consistent digital data space for the process industry and promotes interoperability between operators, inspection service providers, and authorities.

Use Case:
Smart Deadline and Schedule Management for Inspections and Maintenance
Transparent Defect Tracking and Decision Support
Automated Creation of Follow-up Actions
Seamless Integration into Digital Maintenance Workflows
Automated Processing of Maintenance and Inspection Results

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Product Passport – Part 1: Metadata
02099
1.0
In Review
Coming soon

This Submodel template aims to define the data points that are required for every Digital Product Passport conformant to the specification of CEN CENELC JTC24, prEN 18223:2025 [1].
Note: Many properties are also contained in the Submodel Template Specification “Digital Nameplate”. However, what is important to notice that for this Submodel Template only Value-Only Format of Digital Nameplate is compliant to prEN 18223:2025.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Additive Manufacturing with PBF-LB/M – AMProcessState
02033-6
1.0
In Development
Coming soon

The “AMProcessState 1.0” Submodel Template is part of the specification series for Additive Manufacturing with PBF-LB/M. This submodel instance is used to provide information about the process state.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Additive Manufacturing with PBF-LB/M – AMLayerInformation
02033-5
1.0
In Development
Coming soon

The “AMLayerInformation 1.0” Submodel Template is part of the specification series for Additive Manufacturing with PBF-LB/M. This submodel instance is used to provide layer information.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Additive Manufacturing with PBF-LB/M – AMMachineSensor
02033-4
1.0
In Development
Coming soon

The “AMMachineSensor 1.0” Submodel Template is part of the specification series for Additive Manufacturing with PBF-LB/M. This submodel instance is used to provide machine sensor data.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Additive Manufacturing with PBF-LB/M – BuildCycleFabrication
02033-3
1.0
In Development
Coming soon

The “BuildCycleFabrication 1.0” Submodel Template is part of the specification series for Additive Manufacturing with PBF-LB/M. The submodel instance BuildCycleFabrication is used to provide general information about the build cycle fabrication.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Additive Manufacturing with PBF-LB/M – BuildCycleSetup
02033-2
1.0
In Development
Coming soon

The ” Build cycle setup 1.0″ Submodel Template is part of the specification series for PBF-LB/M. The submodel instance Build cycle setup is used to provide static data about the Build cycle configuration.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Sensor 4.0 Part 2: Parameter
02029-2
1.0
In Development
Coming soon

Generic description of sensor parameters

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Safety instrumented system for the process industries
02097
1.0
In Development
Coming soon

Submodel for Safety instrumented system for the process industries which includes properties necessary for SIS specification and requirement. The proposal will be in alignment with IEC 61511.
The properties included in this new submodel can be aligned with and integrated into the IEC CDD. The submodel template will build on the work of two ongoing initiatives: 1) results from the Norwegian joint industry project named Automated process for follow-up of safety instrumented systems (APOS 2.0), including an UML model developed with basis in requirements and definitions in IEC 61511. 2) Results from the NAMUR WG1.3 on Information Management and Tool who is developing a similar UML model. Alignment activities have been carried out between NAMUR and the APOS 2.0 project, and we would like to involve persons from both organizations in preparing the details of the proposed new submodel templates.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Equipment under control for the process industries
02096
1.0
In Development
Coming soon

Submodel for Equipment under control which includes properties necessary to link the equipment to one or more safety instrumented functions as well as information about hazardous event related to the equipment. The proposal will be in alignment with IEC 61511 and IEC 61508.
The properties included in this new submodel can be aligned with and integrated into the IEC CDD. The submodel template will build on the work of two ongoing initiatives: 1) results from the Norwegian joint industry project named Automated process for follow-up of safety instrumented systems (APOS 2.0), including an UML model developed with basis in requirements and definitions in IEC 61511. 2) Results from the NAMUR WG1.3 on Information Management and Tool who is developing a similar UML model. Alignment activities have been carried out between NAMUR and the APOS 2.0 project, and we would like to involve persons from both organizations in preparing the details of the proposed new submodel templates.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
End-of-Life – Part 3: Circularity Information
02078-3
1.0
Coming soon

The submodel End-of-Life helps close the material loop effectively and efficiently, and triggers Manufacturers to improve End-of-Life-related concepts within the R-ladder, such as Re-Manufacturing, Re-Use, and Re-Purpose. The End-of-Life submodel enables End-of-Life actors to recognise, for a product, which materials, compounds, and/or data they are dealing with. Likewise, End-Users can obtain information about the environmental impact of their purchases.
Part 1: Management provides information on applying the R-strategies and advises on the most suitable for the asset. This information is targeted at both End-User and, later, End-of-Life actors.
Part 2: Material Composition gives details on the materials that compose the assets. This information is important for End-of-Life actors to know, for example, the specific material, its quality, or hazardous substances contained.
Part 3: Circularity Information exposes the asset circularity. It primarily targets End-Users and Regulators, informing them about the product’s circularity and its environmental impact.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
End-of-Life – Part 2: Material Composition
02078-2
1.0
In Development
Coming soon

The submodel End-of-Life helps close the material loop effectively and efficiently, and triggers Manufacturers to improve End-of-Life-related concepts within the R-ladder, such as Re-Manufacturing, Re-Use, and Re-Purpose. The End-of-Life submodel enables End-of-Life actors to recognise, for a product, which materials, compounds, and/or data they are dealing with. Likewise, End-Users can obtain information about the environmental impact of their purchases.
Part 1: Management provides information on applying the R-strategies and advises on the most suitable for the asset. This information is targeted at both End-User and, later, End-of-Life actors.
Part 2: Material Composition gives details on the materials that compose the assets. This information is important for End-of-Life actors to know, for example, the specific material, its quality, or hazardous substances contained.
Part 3: Circularity Information exposes the asset circularity. It primarily targets End-Users and Regulators, informing them about the product’s circularity and its environmental impact.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Nameplate
02006
4.0
In Development
Coming soon

This Submodel template aims at interoperable provision of information describing the nameplate of the asset of the respective Asset Administration Shell. Central element is the provision of properties, ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of submodels in such manner that information about assets and their nameplate can be exchanged in a meaningful way between partners in a value creation network. It targets equipment for process industry and factory automation by defining standardized meta data.
The intended use case is the provision of a standardized property structure within a digital nameplate, which enables the interoperability of digital nameplates from different manufacturers.
This concept can serve as a basis for standardizing the respective submodel. The conception is based on existing norms, directives and standards so that a far-reaching acceptance can be achieved.
Beside standardized submodel this template also introduces standardized SubmodelElementCollections (SMC) in order to improve the interoperability while modelling partial aspects within submodels. The standardized SMCs include address and asset product marking.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Asset Interfaces Mapping Configuration
02027
2.0
In Review
Coming soon

The Asset Interfaces Mapping Configuration (AIMC) Submodel version 2.0 supports two use cases:
1. Asset-to-AAS mapping
Together with the Asset Interface Description (AID) Submodel, AIMC specifies how data provided by
assets or asset-related services is mapped to target locations in an Asset Administration Shell (AAS). In
this scenario, AIMC functions as a configuration Submodel for northbound communication between an
asset and the enclosing AAS (for example, an application-specific Submodel for monitoring or logging).
2. AAS-to-AAS mapping
The AIMC can also specify mappings between locations within an AAS. For example, compute a singular
value from multiple existing elements.
In both cases, a mapping defines the relationship between a set of sources (input data) and a set of sinks
(output data) where results are written. An optional transformation step may be applied between sources and
sinks to convert or process the input data into the desired output format or value.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Energy Monitoring
02095
1.0
In Development
Coming soon

The Submodel provides a standardized description of energy flows of an asset during its operational phase. It is designed for general use with machines and components – from subcomponents to systems – that either receive or deliver energy.​
Energy connections at the asset’s interfaces are defined, enabling a uniform structure for the provision of energy-related data, including consumption, power, and efficiency. This data can later be integrated into higher-level energy monitoring systems and further processed in downstream applications – for example, documentation, benchmarking, or optimization of energy consumption.

Use Cases:
Energy consumption of production machines for e.g. PCF calculation of a production line
Energy distribution within complex systems
Monitoring of energy sources, energy generation or energy conversion

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Product Energy Consumption
02094
1.0
In Development
Coming soon

The submodel provides a standardized description of energy consumption during the production phase of an asset (focus on production of single parts, subcomponents and components). It is designed for general use with assets produced via energy-consuming manufacturing processes. In the submodel, production steps are defined and linked to production machines. Users define KPIs such as total energy consumed or energy per unit.
The submodel integrates with higher-level systems for cost analysis, sustainability reporting, and process optimization, while providing foundational energy data to support the Product Carbon Footprint (PCF) Submodel. It explicitly links to the Energy Monitoring Submodel of the producing machine.

Use Cases:
Energy consumption as basis for future PCF calculations
Energy consumption to analyze the production process

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Environmental Product Declaration (EPD) Type III
02093
1.0
In Development
Coming soon

The proposed submodel enables the integration of verified Environmental Product Declarations (EPDs, Type III according to ISO 14025) into the Asset Administration Shell (AAS). An EPD provides objective, transparent, and third-party verified information about the environmental performance of a product throughout its life cycle. It is based on a Life Cycle Assessment (LCA) in accordance with ISO 14040/44 and product category rules (PCRs).

The submodel represents the structure and metadata of an EPD in a machine-readable format, including information on:
Program operator (e.g., International EPD System, PEP ecopassport, IBU, EPD Norway/EPD-Global)
Registration and validity data• Declared product (product name, declared unit, functional unit)
Underlying PCRs (e.g., EN 15804 for construction products, EN 50693 for electrical and HVAC products)
Key LCA result indicators (e.g., global warming potenti al, resource use, waste generation)

Verification and reviewer details.
The AAS integration enables manufacturers, planners, and authorities to digitally exchange EPD data, use it within Digital Product Passports, and perform automated sustainability and compliance checks. Primary application domains include the construction and building materials sector, the electrical/electronic and HVAC industries, and general industrial and consumer goods.

Use Cases:
Digital integration of verified EPD documents in AAS
Automated verification and compliance checks
Data exchange for Digital Product Passports (DPP)
Linking EPDs to product identifiers and nameplate submodels
Machine-readable representation of Type III environmental declarations

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Human Worker Assignment Data
02092
1.0
In Development
Coming soon

This submodel will serve as the counterpart to the already published SMT “Worker Workstation Matching Data”. The latter specifies, among other things, the skill and qualification demands from a worker for a workstation. The proposed SMT will provide the skill and qualification offerings by a worker to be compared to the demands of a workstation.
The ultimate goal is that in the combination of the two SMTs, the automatic assignment of a human workforce to a set of workstations becomes possible. As such, the SMT shall contain information of the particular qualifications and skills of a human worker, including personal preferences and impairments (if necessary/wanted).
The SMT should also provide information on the ergonomic load on different body parts accumulated by the worker due to being assigned to several workstations over a period of time. This information can be used to optimize the distribution of a set of workers to a set of workstations from the point of view of balancing and minimizing the total ergonomic strain on a set of workers.

Use cases:
Automated worker-workstation matching for shift management
Optimizing / minimizing the physical strain of a workforce over several shifts
Tracking the skill pool of the workforce to inform needed hires

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Worker Profile
02091
1.0
In Development
Coming soon

The proposed submodel serves as the counterpart of the “Digital Nameplate for Industrial Equipment” for human worker assets. The “Digital Nameplate” SMT is fully focused on capturing information of machines and cannot be re-used to any significant degree for a human worker. Hence, a new SMT is necessary to provide a standardized way of handling human worker asset data.
The submodel will include general information about a human worker that allow the general management of human assets and can be used to store information ranging from IDs and key dates and values pertaining to a worker to information such as language proficiencies or work clothes/equipment sizes.

Use Cases:
General bookkeeping of human assets
Keeping track of need to provide information in a specific language
Managing needed work equipment/clothes for workforce

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Standard Data Model for Asset Inventory of Operational Technology
02090
1.0
In Development
Coming soon

Knowledge about the type of installed control system components, their number and location is key for a many critical processes in running an industrial production facility. Life-Cycle Management, Maintenance Management as well as Safety- and Cyber Security Management all require an asset inventory with high data quality and completeness. End users of operational technology (OT) commonly utilize various software tools for collecting and updating the asset inventory, which are provided by control system vendors and third parties. However, collecting, pooling and exchanging of asset information across multiple platforms is often per-formed via file exports and manual processing steps because every platform employs separate often incompatible data models to represent asset information. The goal of this submodel is to bridge these gaps and serve as a common data model for compatibility across platforms and the use cases named above.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Supply Chain Event Data Collection
02089
1.0
In Development
Coming soon

The proposed Submodel focuses on representing product related supply chain events throughout the entire life cycle. Its goal is to provide a comprehensive lifecycle record of a product by enabling the tracing of raw materials, the tracking of production and logistics steps, and the logging of events during the usage phase, such as product operation or maintenance activities. With this approach, the Submodel enhances supply chain transparency and plays a key role in implementing the Digital Product Passport (DPP).

Use-Cases:
Asset-Management
Regulatory Compliance Documentation
Track & Trace Applications
Digital Product Passport

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Product Material Compliance
02088
1.0
In Development
Coming soon

The proposed submodel focuses on Product Material Compliance, addressing essential regulatory requirements such as SCIP, REACH, and RoHS. Its goal is to ensure and monitor the material compliance of products to meet both legal mandates and sustainability objectives. This model is crucial for the implementation of the Digital Product Passport (DPP) and contributes to transparency within the domain of material compliance. It supports efforts to promote a sustainable supply chain and enforce unified standards across the industry.

Use Cases:
Regulatory Compliance Documentation
Captures and proves adherence to regulations such as SCIP, REACH, and RoHS, especially for plastic-based products
Support for Audits and Certifications
Provides structured data for internal audits or external validation via programs like EPD International 1.
Supply Chain Transparency
Tracks material origin and composition to assess risks and sustainability across the value chain 1.
Support for the Digital Product Passport
Contributes to harmonization with EU regulations such as ESPR and CPR, enabling standardized environmental and compliance data

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Plastic and Rubber Moulds Part 2: Engineering Data
02038-2
1.0
In Review
Coming soon

This Submodel specifies the design‑time engineering information of plastics and rubber moulds. Its purpose is to capture the assumptions and artefacts from the design and development phase and the resulting engineered characteristics of the mould. Typical contents include:
• Process definition and assumptions: the intended manufacturing process such as injection or compression moulding, assumed operating envelopes and constraints considered during design, and the design intent regarding cycle sequence.
• Target equipment assumptions: intended machine category and class, and assumed capabilities of the injection or compression machine and peripheral devices like hot‑runner controllers, temperature control units, valve‑gate controllers, robots and EOAT, and dosing or mixing equipment. These assumptions are represented in first‑level SubmodelElementCollections (SMCs) such as MachineData and HotRunners.
• Article definition for which the mould was engineered: identifiers and names, references to 2D drawings and 3D geometry, and materials and colorants that were considered and verified during design. This information is grouped under the SMC Article with further structure for Materials and MaterialColors.
• Engineered mould characteristics (design result): descriptors such as number of cavities, gating or hot‑runner concept and nozzle types, ejector concept, core‑pull or slide units, and other properties that characterize the engineering outcome, encapsulated in the SMC MouldDescription. Cavity‑level information aligns with OPC 40082‑5 to enable an unambiguous mapping to OPC UA implementations where applicable.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 7: Circularity
02035-7
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations.
The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 7: Circularity (IDTA_02035-7).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 6: Material Composition
02035-6
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations.
The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 6: Material Composition (IDTA_02035-6).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 5: Product Condition
02035-5
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations.
The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 5: Product Condition (IDTA_02035-5).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 4: Technical Data
02035-4
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations.
The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 4: Technical Data (IDTA-02035-4).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 3: Product Carbon Footprint
02035-3
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations.
The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 3: Product Carbon Footprint 1.0 (IDTA-02035-3).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 2: Handover Documentation
02035-2
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations.
The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 2: Handover Documentation 1.0 (IDTA-02035-2).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Battery Passport – Part 1: Digital Nameplate
02035-1
1.0
Published
Download
GitHub

This Submodel template aims to define the dynamic data points of a Battery Passport conformant to DIN
DKE SPEC 99100 and the corresponding EU regulations. The battery passport consists of the following 7 parts:
Digital Battery Passport – Part 1: Digital Nameplate (IDTA-02035-1)
Digital Battery Passport – Part 2: Handover Documentation (IDTA-02035-2)
Digital Battery Passport – Part 3: Product Carbon Footprint (IDTA-02035-3)
Digital Battery Passport – Part 4: Technical Data (IDTA-02035-4)
Digital Battery Passport – Part 5: Product Condition (IDTA-02035-5)
Digital Battery Passport – Part 6: Material Composition (IDTA-02035-6)
Digital Battery Passport – Part 7: Circularity (IDTA-02035-7)
This specification is Part 1: Digital Nameplate 1.0 (IDTA-02035-1).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Company Carbon Footprint
02087
1.0
In Development
Coming soon

This data model captures and structures key information related to a company’s carbon footprint. It includes data on direct (Scope 1), indirect energy-related (Scope 2), and other indirect (Scope 3) greenhouse gas emissions, categorized by source and activity. The model supports tracking of emissions over time, across business units, and by emission type, enabling consistent reporting, benchmarking, and compliance with sustainability frameworks such as the GHG Protocol.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Characteristic curves
02086
1.0
In Development
Coming soon

This Submodel is used for the standardized description of characteristic curves and multidimensional characteristic maps, as well as corresponding approximation descriptions.
This information is used in a variety of ways:
– For parameterization of simulation models
– As a basis for control system development
– For simple calculations
– As a basis for decision-making in the engineering process

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Requirement model for Assets and Entities
02085
1.0
In Development
Coming soon

This Submodel templates allows assigning functional and non-functional requirements to assets and entities of Asset Administration Shells. It allows specifying such requirements at early stages of the life-cycle, tracking and refining them over the course of the life-cycle, in order to provide test criteria.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Asset Interfaces Description
02017
1.1
In Review
Coming soon

This Submodel specifies an information model and a common representation for describing the interface(s) of an asset service or asset related service. Based on this information, it is possible to initiate a connection to such kind of service and start to request or subscribe to served datapoints, and/or perform operations. Such datapoints of a system service can be, for example, various sensor and/or status values, and an operation can trigger an actuator, such as switching a motor “on” or “off”.
The Asset Interfaces Description (AID) in version 1.1 supports the description of interfaces based on following specific protocols:
• Modbus
• HTTP
• MQTT
• OPC UA
• BACnet

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Process Parameters Type
02031-1
1.0
Published
Download
GitHub

This Submodel defines type-specific information of Process Parameters and provides a framework to describe the input parameters for processes of industrial equipment. This Submodel does not require any knowledge about how a process is executed and in which order. It is solely focused on the structured provision of data necessary for process execution.
The need for a dedicated Process Parameters Submodel is to enable the interoperable description and transfer of data between assets. The concept is based on process knowledge from various organizations in the automotive wire harness industry. Although the associated use cases are from the value chain of wire harness manufacturing, the aim of the working group is to develop a generalized Submodel that can be used for a wide variety of products and industries.
This Submodel is intended for the description of input parameters of a process and should be used in combination with the Hierarchical Structures Submodel to define the sequence of process execution and hierarchical requirements.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
PCE Request – Process data according NE 159
02083
1.0
In Development
Coming soon

The NE 159 contains a formal description of the properties of a PCE request which are exchanged between process and automation engineering. There is also a modeling in CAEX standardized in VDI/VDE 3697 part 2.
However, for an AAS-based Use Case to order devices from a vendor, these properties need to be exchanged between owner operator, engineering contractor and device vendor. With the help of these properties, a part of the role AAS is defined.
The NE 159 contains two different main objects, the PCE Loop and the PCE Request. For both objects, different AAS with different submodel content is needed.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
PCE Request – P&ID Information according IEC 62424
02084
1.0
In Development
Coming soon

The IEC 62424 contains a formal description of the properties of a PCE request which are depicted on a P&ID diagram. There is also a modeling in CAEX standardized.
However, for an AAS-based Use Case to order devices from a vendor, these properties need to be exchanged between owner operator, engineering contractor and device vendor. With the help of these properties, a part of the role AAS is defined.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Unmanned aerial vehicle (Drone)
02081
1.0
In Development
Coming soon

• The submodel should contain relevant parameters of the drones like classification of wings, payload capacity and wind resistance.
• This standardized representation will increase the autonomy and intelligence of UAV systems paving the way for seamless integration across multiple domains, including logistics and agriculture.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
SIS device for the process industries
02079
1.0
In Development
Coming soon

The main goal is to propose submodels consisting of safety list of properties (SLOPs) of a SIS (safety instrumented system) Device) in alignment with IEC 61511 and IEC 61508. This proposal is one out of two submodels for functional safety for the process industry (the other being submodel for SIF already in development).
The SLOP included in this new submodel can then be aligned with and integrated into the IEC CDD. The submodel template will build on the work of two ongoing initiatives: 1) results from the Norwegian joint industry project named Automated process for follow-up of safety instrumented systems (APOS 2.0), including an UML model developed with basis in requirements and definitions in IEC 61511. 2) Results from the NAMUR WG1.3 on Information Management and Tool who is developing a similar UML model. Alignment activities have been carried out between NAMUR and the APOS 2.0 project, and we would like to involve persons from both organizations in preparing the details of the proposed new submodel templates.
Although this specific proposal pertains particularly to establishing the submodel for SIS Device), it is tightly connected with another relevant submodel under the domain of ‘functional safety for process industries’, namely:
-Submodel for SIF (safety instrumented function)

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Resilience Assessment in Industrial Production
02082
1.0
In Development
Coming soon

The Resilience Submodel provides a framework for assessing resilience in industrial production environments. It encompasses relevant operational levels, including machine, shopfloor, and supply chain. The model contains data elements necessary for established resilience assessment methodologies while incorporating four innovative methods developed within the EU-wide Flex4Res project.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
End-of-Life – Part 1: Management
02078-1
1.0
In Development
Coming soon

The submodel End-of-Life helps close the material loop effectively and efficiently, and triggers Manufacturers to improve End-of-Life-related concepts within the R-ladder, such as Re-Manufacturing, Re-Use, and Re-Purpose. The End-of-Life submodel enables End-of-Life actors to recognise, for a product, which materials, compounds, and/or data they are dealing with. Likewise, End-Users can obtain information about the environmental impact of their purchases.
Part 1: Management provides information on applying the R-strategies and advises on the most suitable for the asset. This information is targeted at both End-User and, later, End-of-Life actors.
Part 2: Material Composition gives details on the materials that compose the assets. This information is important for End-of-Life actors to know, for example, the specific material, its quality, or hazardous substances contained.
Part 3: Circularity Information exposes the asset circularity. It primarily targets End-Users and Regulators, informing them about the product’s circularity and its environmental impact.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Material Data for the Characterization of Plastic Waste Feedstocks and Recycled Plastics
02080
1.0
Published
Download
GitHub

The Submodel template “Material Data for the Characterization of Plastic Waste Feedstocks and Recycled Plastics” aims at the interoperable provision of information describing prioritized physical and chemical characteristics of plastics materials. At its core, this Submodel is modelled after EN 18065 [8], and in particular with the intent to provide all necessary data elements and a template structure to support automated designation of data sets (in individual Submodel instances) as specified therein. This document makes the necessary specifications of elements such that stakeholders along the value chain and life cycle of plastics materials can aggregate and exchange data about such materials.
Anticipated use cases have an asset view on such materials and and associate them with one or more AASs comprised of instances of this and other Submodels. Sharing (access) to these AAS can facilitate • market- and match-making for digital trading of materials;
• integration of electronic, machine-readable, batch-specific product data sheets into business software and manufacturing processes;
• implementations of ‘digital product passport’-like (‘DPP’-like) data sets as specified in EN 18065, supporting, for example, automated greenhouse gas asset accounting and reporting, automated verification and audits, end-to-end traceability of materials, and AI-powered data analytics.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Hierarchical Structures enabling Bills of Material- Extension based on IEC 81346
02011-1
1.0
Published
Download
GitHub

The structuring of machines, plants or systems is an essential task in engineering to make the complexity of a technical system manageable. IEC 81346 standardises a concept of structuring based on various aspects that an object (asset) can have. In this sense, a system always consists of several objects, which means that the system (composite asset) also has corresponding aspects. Figure 1 shows three of the aspects as examples. The standard describes a total of five aspects:
• What an object is supposed to do or what it actually does – Function aspect (=)
• The means by which an object does what it is supposed to do – Product aspect (-)
• Planned or actual location of the object – Location aspect (+)
• Group of objects that have the same properties – Type aspect (%)
• A freely definable aspect that must be specified by the creator – Other aspect (#)

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Handover Documentation
02004
2.0
Published
Download
GitHub

The Submodel Handover Specification defines a standardized exchange format for information or documentation for a specific asset. The scope of this Submodel is to increase the interoperability between the parties that are exchanging asset documentation. These parties can be manufacturers of components or complete machines, or operators using these components or machines. In case a machine manufacturer sells a machine to a customer (operator), the manufacturer hands over the machine and its documentation in form of an AAS with the Submodel “Handover Documentation”. The documents provided can contain information required for e.g. correct design, installation, commissioning, spare parts stocking, operation, cleaning, inspection, maintenance, and repair. In addition, there are legal regulations that stipulate the existence of certain manufacturer documents, such as Communauté Européenne (CE) declarations of conformity, Atmosphères Explosives (ATEX) certificates, or material certificates. Besides the structure of a Submodel and the exchange format of an AAS, this Submodel standardizes the meta data that comes with the asset documentation and the classes that classify the type of the document. With these standardized meta data and classes, the asset documentation can be automatically integrated in the customer’s document management system, backend system, or any other system. The meta data as well as the classification classes of this Submodel are based on the VDI Guideline VDI 2770 Blatt 1 “Operation of process engineering plants – Minimum requirements for digital manufacturer information for the process industry” [7]. While the classification of documents according to VDI 2770 is mandatory, additional classification classes can be added.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Generic Frame for Technical Data for Industrial Equipment in Manufacturing
02003
2.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of technical data describing the asset of the respective Asset Administration Shell. Central element is the provision of properties, ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common data dictionary).
The intended use-case is, that a manufacturer of industrial equipment describes assets (type or instance), which are provided to the market, by the means of technical data (properties), which are interoperable and unambiguously understood by the other market participants, such as system integrators or operators of industrial equipment. For providing individual industrial equipments to the market, also a supplier is covered by the use-case (for this purpose seen as functioning as manufacturer).
This Submodel template specifies a basic set of SubmodelElements in order to bring about the necessary information according to this use-case.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Control Component Type
02015
2.0
Published
Download
GitHub

The scope of this Submodel is the definition of type-specific information of a Control Component (CC) into an AAS. Together with its counterpart, the CCInstance Submodel (IDTA 02016), both Submodels aim to establish templates to ensure a uniform structure. The use of these templates allows the development of manufacturer- and domain-independent control concepts and facilitates the exchange of process information with other Submodels. Additionally, it allows the use of standardized call and monitoring sequences, as well as standardized description of its services, endpoints, error-codes, etc.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Control Component Instance
02016
2.0
Published
Download
GitHub

The scope of this Submodel is the definition of instance-specific information of a Control Component (CC) into an AAS. Together with its counterpart, the CCType Submodel (IDTA 02015), both Submodels aim to establish templates to ensure a uniform structure. The use of these templates allows the development of manufacturer- and domain-independent control concepts and facilitates the exchange of process information with other Submodels. Additionally, it allows the use of standardized call and monitoring sequences, as well as standardized description of its services, endpoints, error-codes, etc.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Carbon Footprint
02023
1.0
Published
Download
GitHub

This Submodel template provides the means to exchange an asset`s Carbon Footprint (CF) between the partners along a value chain. The aim of this Submodel is to increase the interoperability between the parties, who are interested in documenting, exchanging, evaluating, or optimizing the environmental footprint of their assets. These parties can for example be manufacturers, users/consumers, or logistic partners. The CF might be part of larger initiatives, such as the Digital Product Passport (DPP) or the Product Environmental Footprint. It is not the scope of this Submodel template to substitute the relevant certificates. Use cases with increasing complexity are described in the following section. Version 1.0 of this document will focus on Use Cases 1,2, and 3. Additional use cases will be supported in future versions.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Energy Flexibility Data Model
02076
1.0
Published
Download
GitHub

The proposed submodel template designed to enable an optimally energy-flexible operation across systems within industrial enterprises and to facilitate the communication of energy flexibility between industrial companies and energy market-related services.
The model provides a generic description of energy flexibility, focusing on a minimal set of parameters and metrics, but encompassing technically and energetically relevant information necessary to describe energy flexibility. It serves as a central foundation for communication within a company unit as well as externally with software applications (services) mediated via a marketplace platform. It does not aim to create a digital twin as a virtual and fully realistic representation of energy flexibility. This approach limits the complexity and volume of exchanged information while avoiding the exchange of sensitive production and process data.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Nameplate for industrial equipment
02006
3.0.1
Published
Download
GitHub

This Submodel template aims to provide asset nameplate information to the respective Asset Administration Shells in an interoperable manner. Central element is the provision of properties [7], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets and their nameplate can be exchanged in a meaningful way between partners in a value creation network. It targets equipment for process industry and factory automation by defining standardized meta data.
The intended use case is the provision of a standardized property structure within a digital nameplate, which enables the interoperability of digital nameplates from different manufacturers.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, directives and standards so that a far-reaching acceptance can be achieved.
Beside standardized Submodel this template also introduces standardized SubmodelElementCollections (SMC) in order to improve the interoperability while modelling partial aspects within Submodels. The standardized SMCs include address and asset product marking.
In addition to the general information for Industrial Equipment listed in this document, it may be necessary to supplement the digital nameplate with additional information for specific areas of application, e.g. for explosion safety or radio. Information for the digital nameplate for additional areas of application are defined in supplementary Submodel templates.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Provision of Company Data
02068
1.0
Published
Download
GitHub

Companies collect data/information from their suppliers and must provide data/information to their customers for whom they are suppliers. The information must then be maintained in the course of supplier qualification.
The following information is required:
– Contact details
– Business figures, from the annual reports
– Account data
– Identification numbers, e.g. for taxes
– logo
– Certificates and declarations and their metadata

All companies that have suppliers that need to be qualified and/or have customers that qualify and maintain their suppliers are affected.

As the information can relate to groups of companies, but also to locations, e.g. for production and sales, the mapping of the entities for which a submodel can be specified and how these can be related must also be described.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Production Calendar
02067
1.0
Published
Download
GitHub

• The submodel should contain a template to store one or more production calendars of mimeType iCalendar (RFC 5545).
• The iCal format is very abstract and isn’t enough specified for industry requirements. For this, necessary variables, describing the content of the production calendar, will be specified by the working group.
• A Management Execution System and a value chain simulation can use the calendar submodel to exchange information like the shift schedule of a machine and execute operations on it.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Process Variables for Manufacturing Key Performance Indicators
02066
1.0
In Review
Coming soon

In industrial production environments normally heterogeneous landscapes of production systems exist, furthermore named as machines. These landscapes facilitate high flexibility in production processes due to varied production capabilities that can be combined in a modular way. However, the control and optimization of the production flow by Manufacturing Operations Management (MOM) and its subsystem, the Manufacturing Execution System (MES), gets complicated if heterogeneous machinery is used. However, Manufacturing Key Performance Indicators (KPIs), like Overall Equipment Effectiveness (OEE), play a crucial role in assessing and optimizing the MOM. To calculate the KPI, defined process variables for all available machines are required, which in turn can be derived from the combination of user-defined machine signals.
Such important process variables can be, if the machine is producing, in error mode or in idle. This process variables result from the logical combination of multiple machine signals, which is custom for every machine type. For one machine it could be the combination of the signals
– automatic mode is active together with
– override 0 and
– program is running and
– start cycle
For another machine it could be the combination of the signals
– automatic mode is active together with
– program is running and
– override = 100% and
– spindle drive = 100% and
– NC ready
MES vendors must analyze every machine type regarding the communication interface, the meaning of the signals and the communication protocol with which the signals will be transferred to the MES to derive the typical process variables, which are defined and standardized in the ISO 22400-2. After deriving the process variables for single machines, the OEE can be calculated. The process described often requires collaboration between the MES vendor, the operator, and the machine manufacturer, which leads to complex coordination and a need for consultation due to different departments with their own terminology and concepts, as well as the fact that the customer may be entering new territory when integrating into an MES for the first time.
The Submodel “Process Variables for Manufacturing KPI Calculation” (PVM) defines an initial set of specified process variables, based on ISO 22400-2, which are required by the MES. The current values of the process variables should be provided via the Submodel, so that other applications can use them, e.g., to automatically compute Manufacturing KPIs for heterogeneous machinery. The Submodel is intended to be used as a standalone Submodel as well as in combination with already published Submodels, specifically the Asset Interface Description [7] and Asset Interface Mapping Configuration Submodel [8]. The developed solution considers the existence of different communication protocols and PLCs but provides a standardized information model for process variables a MES or other systems require. Furthermore, this Submodel is designed to be extensible and to serve as a foundation for computing Manufacturing KPIs beyond its initial scope.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Safety instrumented functions (SIF) for the process industries
02064
1.0
In Development
Coming soon

The main goal is to propose submodels consisting of safety list of properties (SLOPs) of safety instrumented functions (SIF) in alignment with IEC 61511.
The SLOP included in this new submodel can then be aligned with and integrated into the IEC CDD. The submodel template will build on the work of two ongoing initiatives: 1) results from the Norwegian joint industry project named Automated process for follow-up of safety instrumented systems (APOS 2.0), including an UML model developed with basis in requirements and definitions in IEC 61511. 2) Results from the NAMUR WG1.3 on Information Management and Tool who is developing a similar UML model. Alignment activities have been carried out between NAMUR and the APOS 2.0 project, and we would like to involve persons from both organizations in preparing the details of the proposed new submodel templates.
Although this specific proposal pertains particularly to establishing thesubmodel for safety instrumented function (SIF), we recognize the need for expanding our scope to establish a set of relevant submodels under the domain of ‘functional safety for process industries’, for example:
-Submodel for safety instrumented system (SIS) components
– Submodel for SIS subsystems
– Submodel for Safety requirement specification (SRS)
– Submodel for data collection in SIF operation.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Interface Connectors
02062
1.0
In Development
Coming soon

Information model that describes the interfaces of an asset that are planned or integrated as part of the engineering process of production systems. This includes all kind of connections including: electrical, mechanic, pneumatic etc.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Explosion Protection
02057
1.0
In Development
Coming soon

Interoperable representation of all explosion protection features and markings regardless of the certification system.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Data Retention Policies
02056
1.0
Published
Download
GitHub

This Submodel describes a common representation of data retention policies that can be applied to elements in the Asset Administration Shell via semantic identifiers. Based on this information, it is possible to automate the reduction, archiving, or removal of data stored in the Asset Administration Shell. Such data can be, for example, raw sensor data, large images, sensitive data, or any data that becomes obsolete over time.
A data retention policy defines how long data must be stored before it may be deleted. It also provides information about the policy provider, the specific requirement or law that enforces the policy, and the timeframe between which the policy is in effect. Additionally, the authorship of each policy can be traced through an audit log, in which all changes to the policy are documented. Based on this information, an automated service can apply and validate each policy against the data stored in the Asset Administration Shell and reduce, archive, or remove the data as necessary.
This Submodel allows a set of policies to inherit from another set of policies so that an existing policy can be extended or adjusted to more specific use cases. For example, business policies may be overridden or extended by contracts with more specific policies or longer retention periods.
The enforcement of data retention policies described by this Submodel are outside the scope of this document.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Spare parts and consumables lists
02040
1.0
Proposal submitted
Coming soon

The submodel represents an interoperable list of spare and consumable parts of an asset that are required for the repair, maintenance or regular operation of a specific product, device or system. The purpose of this list is to provide a clear overview of available spare parts and consumables to ensure the smooth running of repairs and maintenance operations.

The benefit of such a list is that it enables technicians, maintenance personnel or even end users to quickly identify and procure the required parts. This contributes to efficiency by minimizing downtime and ensuring effective maintenance. The list also supports stock management by enabling accurate inventory control and timely reordering.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Replacement and successor product
02041
1.0
Proposal submitted
Coming soon

The replacement and successor product submodel refers to a new product that either replaces or improves the obsolete asset or asset that is no longer available. It is intended to inform the user of a suitable replacement or successor product depending on the discontinuation status of the existing product.

Possible content:
– Discontinuation status of the current product, incl. last order and repair date
– AssetId, product name and model number of the replacement and successor product
– Comparison with predecessor product (improvements, …)

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Handover information for engineering authoring systems
02039
1.0
Proposal submitted
Coming soon

This Submodel template aims at interoperable provision of information models for engineering authoring systems for the handover of industrial components. These industrial components are typically provided by manufacturers and suppliers, including dealers, and used by industrial users, e.g. original equipment manufacturers (OEMs), system integrators and producing enterprises (industrial end users). Industrial components can be described on type or instance level.
The aim of this Submodel is to digitialize and interoperably convey sets of information to faciliate and ease engineering tasks using such industrial components. Engineering authoring systems are considered all systems concerned with selecting, dimensioning, simulating, constructing and sketching industrial systems. For the time being, this document focuses on electrical and fluidic engineering.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Plastic and Rubber Moulds Part 1: Identification
02038-1
1.0
Published
Download
GitHub

This specification applies to moulds used in plastics and rubber production machines. The Submodel is part of the mould’s digital twin, offering detailed information for mould identification, as these components often require additional information compared to machines or devices. This document is a part of the specification series IDTA 02038 (identical to EUROMAP 101 series) describing plastics and rubber moulds. This series consist of the following Submodel templates, of which some may still be under development (further specifications are possible):
– Part 1: Identification of plastic and rubber moulds
– Part 2: Engineering data of plastic and rubber moulds
– Part 3: Plastic and rubber mould configuration data
– Part 4: Plastic and rubber mould production parameters
– Part 5: Plastic and rubber mould collaborative condition monitoring
– Identification
– Engineering Data from the development process
– Configuration Data
– Process Optimization Data
– Collaborative Condition Monitoring
– Maintenance

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Automation Engineering
02037
1.0
In Development
Coming soon

In the submodel Automation Engineering, information of engineering in the area of electrics, hydraulics, pneumatics and control (general automation engineering) is to be covered. Components of automation engineering are selected, structured, placed and connected in engineering tools. The model consistently continues the concepts of the AAS and transfers them to the engineering of plants and systems. As a link between the requirements definition of a resource and the actually used component and its installed instance, it makes a significant contribution. The objective is to make the existing information available to other software systems in a formally standardised form. This brings considerable added value to a large number of use cases over the life cycle if they are semantically processed. Among other things, collaborative engineering, derivations for production, maintenance and documentation are taken into account. The model will be based on relevant standards such as IEC 81346 and IEC 61355 as well as existing submodels such as Hierarchical Structures enabling Bills of Material and Generic Frame for Technical Data for Industrial Equipment in Manufacturing.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Product Change Notifications for Industrial product types and items in manufacturing
02036
1.0
In Review
Coming soon

This Submodel template aims at interoperable provision of product change notifications between suppliers and users of industrial product types and items, particularly industrial components. These industrial product types and items are typically provided by manufacturers and suppliers, including dealers, and used by industrial users, e.g. original equipment manufacturers (OEMs), system integrators and producing enterprises (industrial end users). The product types are typically used to provide more than one product instance, however special cases such as mass-customization and engineer-to-order are applicable.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Factory automation data for plant planning
02075
1.0
In Review
Coming soon

The Submodel „Factory Automation Data for Plant Planning” defines the scope and boundaries of the standardized representation of all engineering building services (TGA) data in the context of digital factory and plant planning. It is specifically designed for OEM planning tools as well as BIM/CAD systems that capture, transmit, and integrate this data as part of an Asset Adminstration Shell (AAS) and integrate it into further planning projects. To address the growing complexity, speed, and flexibility of production environments, the Submodel ensures that all relevant engineering building services data circulates seamlessly along the entire planning chain and enables automated workflows without the need for manual post-processing.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Creation and classification of materials in an ERP, PDM/PLM and PIM system
02034
1.0
Published
Download
GitHub

The Submodel “Creation and classification of materials in an ERP, PDM/PLM and PIM system” has been designed to provide a standardized interface for the creation and classification of materials across various system environments. Its aim is to ensure a consistent and efficient process for the creation and classification of material data within Enterprise Resource Planning (ERP), Product Information Management (PIM), and Product Lifecycle Management (PLM) / Product Data Management (PDM) systems. A Material Master must exist as an object so that Classifications to this Material can be assigned correspondingly.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Additive Manufacturing with PBF-LB/M – AMMachine
02033-1
1.0
In Development
Coming soon

The “AMMachine 1.0” Submodel Template is part of the specification series for Additive Manufacturing with PBF-LB/M. The submodel instance AMMachine is used to provide static data about the used hard- and software configuration of a PBF-LB/M machine.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Inspection Documents of Steel Products
02032
1.0
Published
Download
GitHub

This Submodel template aims to standardize the representation and storage of inspection data for steel products within the steel manufacturing and supply industry, specifically adhering to the DIN EN 10204:2004 and DIN EN 10168:2004 standards. DIN EN 10204:2004 defines the various types of inspection documents supplied to the customer, while DIN EN 10168:2004 specifies the required document content for inspection documents of metallic products. This template is designed for stakeholders such as steel manufacturers, suppliers, and customers, to facilitate seamless exchange and direct usability of inspection data. It covers the lifecycle of steel products from production to delivery, ensuring consistency and reliability in data handling. The Submodel will manage comprehensive inspection documents, including detailed information about the manufacturer and customer, order data, product specifications, mechanical test results, chemical analysis, and validation information. By providing a uniform structure for data related to steel product inspections, this Submodel enhances traceability, data interoperability, and compliance across the supply chain, ensuring added value and efficiency for both suppliers and customers.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Technical Data for Fiber Optic Microduct Cabling for Broadband Expansion
02061
1.0
In Development
Coming soon

Developed in cooperation with InterOpera.
The objective of the submodel “Technical Data for Fiber Optic Microduct Cabling for Broadband Expansion” is to standardize the technical characteristics of micro tubes and their composites. This is due to the fact that although the planning and documentation of fiber optic lines is carried out digitally, the properties of the pipe assemblies into which fiber optic cables are blown after professional installation are not uniformly defined. This has so far prevented, for example, the comparability of their specifications across manufacturer boundaries and integration in planning according to the Building Information Model (BIM). Since the characteristics belong to the technical specifications, they are standardized in an extended submodel using the IDTA submodel “Generic Frame for Technical Data for Industrial Equipment in Manufacturing” (IDTA number: 02003, version: 1.2) as a base. The standards DIN EN 60794-5-10, DIN EN 60794-5-20, DIN EN 50411-2-4 and DIN 47609 are taken into account.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Technical Data for Automated Guided Vehicles in Intralogistics
02047
1.0
Published
Download
GitHub

The material flow in the factory will increasingly be driverless and autonomously controlled. With the growing penetration of production with AGVs, these will also take on very specific transport, handling and, with the right setup, possibly also assembly or manufacturing tasks.
Suppliers of AGVs will continue to develop specific capabilities and features for their vehicles and possible attachments. This will inevitably lead to the situation where different types of vehicles and vehicles from different manufacturers have to be operated in one production environment. These mixed fleets have to be integrated in the overall driverless transportation system and controlled via a central or decentral control system. In most cases this control system will be linked to the ERP or MES system where it is receiving the transportation orders from. Control systems can be proprietary systems of the vehicle supplier or manufacturer-independent systems. With increasingly mixed fleets in operation manufacturer-independent control systems will be more widespread on the market.
Against this background, a digital twin in the form of an AAS for the vehicles is to form the data basis for the integration of the individual vehicles into an overall system. The Submodel “Technical Data for Automated Guided Vehicles in Intralogistics” aims to identify the necessary information for integration and standardize it with an AAS Submodel specification. In addition to the integration aspect in an overall system during the engineering phase, the Submodel should also take into account technical data needs for commissioning, operation and maintenance.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Purchase Order
02050
1.0
Published
Download
GitHub

The Purchase Order Submodel is designed to enable the interoperable provisioning of information related to
a purchase order issued by a buyer / customer to a seller / supplier concerning a specific asset, in alignment
with the Asset Administration Shell (AAS) framework. A key element of this submodel is the inclusion of
properties [7], ideally enhanced by semantic interoperability through the use of standardized dictionaries such
as ECLASS and the IEC Common Data Dictionary (CDD).
The purpose of this document is to specify submodels that allow for the meaningful exchange of asset- related
information between partners across the supply chain. It focuses specifically on purchase order processes and
the data exchanged during these transactions.
The intended use case is the provision of a standardized data structure for purchase orders. This structure
enables the interoperable and unambiguous exchange of essential information, starting from a purchase
request, progressing through a quotation, and culminating in the issuance of a formal purchase order.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Quality Control for Machining
02049
1.0
Published
Download
GitHub

The Submodel “Quality Control for Machining” aims at an interoperable description of the quality control relevant data in the field of machining, which provides a comprehensive, structured and standardized data basis for the subsequent tasks of data analysis. On the one hand, the information and data relevant to quality control is presented in a structured manner, whereby the data structure and the required administrative data is summarized as general as possible, independent of specialist areas. On the other hand, the option to specify domain-specific features is included in order to provide the meta-information of specific standards as well as the test parameters and to allow the definition of other characteristics specific to the machining process.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Control configuration and parametrization for NC/CNC machines
02053
1.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of information describing the “Control configuration and parametrization for NC/CNC machines” in regard to the asset of the respective AAS. The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network. It targets people who are commissioning or integrate Computerized Numerical Control (CNC) machines. Therefore, they need data to parametrize the CNC control.
The intended use-case is the provision of a standardized property structure for Control configuration and parametrization for NC/CNC machines, which enables an easy access of data, which is needed to configure or parametrize a CNC controller.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, studies of common practices at enterprises, directives and standards so that a far-reaching acceptance can be achieved.
Beside standardized Submodel this template also introduces standardized SubmodelElementCollections (SMC) in order to improve the interoperability while modelling aspects of Control configuration and parametrization for NC/CNC machines within other Submodels.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Computing Platform Resources
02030
1.0
In Development
Coming soon

The objective of the submodel “Computing Platform Resources” is to represent platform (device) resources that are required for (re)deployment of the software. In the context of convertible production, different products can thus be manufactured on the same production line. The submodel supports the dynamic addition and removal of capabilities and devices in the production line and enables automated deployment of services/applications to be executed on available and suitable resources. The affected software services can be moved accordingly. To perform the reconfiguration and redeployment of the device-related software, the available platform resources are taken into account. Among other things, the following properties are described: CPU clock, number of CPU cores, RAM, hard disk space, real-time capability, OS, available technologies (virtual machines, containers, etc.).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Workstation Worker Matching Data
02046
1.0
Published
Download
GitHub

The focus of the Submodel “Workstation Worker Matching Planning” is on the employee scheduling and operational deployment of employees who carry out manual activities in production. The activities performed can include, for example, the processing of products, their assembly, the operation of machines and systems, as well as their loading and set-up, transportation, quality inspections, maintenance, servicing and much more. With the high level of automation and increasing digitalization and autonomation of production the requirements for the planning and management of employees are changing. In future, employees will have to be deployed in a more situational and targeted manner according to their qualifications and skills. The fixed assignment of an employee to a workstation for an entire shift, in which the employee covers all the skills potentially required at the workstation, will no longer be the norm.
In an Industry 4.0 production environment, different requirements are placed on employee scheduling than in a traditional production system, in which employees are manually assigned, usually by the group leader. In Industry 4.0 production, employees and the (autonomous) automation system will have to work together synergistically and employees with the appropriate qualifications or skills will have to be scheduled and managed according to the situation. When qualified personnel resources are scarce, the optimal allocation of qualifications and skills is particularly important.
The current approach of employee scheduling (shift planning) and operative employee deployment by the group leader will reach its limits in future Industry 4.0 production. The classic qualification matrix for planning the necessary qualifications and skills will also no longer be sufficient. The manual creation and maintenance of the matrix will get at its limits and is not interoperable.
The “Workstation Worker Matching Data” Submodel is used to map the general-, ad hoc- and order-dependent demand of a workstation for qualifications and skills. In addition, further information will be provided by the Submodel that are relevant for operative worker deployment and employee scheduling.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Data Model for Asset Location
02045
1.0
Published
Download
GitHub

The location of static or mobile objects (assets / goods / trackables) and, if applicable, the origin and destination of transport processes are naturally the most important information in transport and internal logistics. In the past, the postal address or a simple location description (e.g., hall B, aisle 3) or a GNSS coordinate (Global Navigation Satellite System, like GPS) was sufficient as location information for controlling logistics processes. With the increasing propagation of localization technologies such as Ultra-Wideband (UWB), BLE (Bluetooth Low Energy), RFID (Radio-Frequency Identification) and others, the continuous and precise tracking of objects becomes possible at reasonable costs. This opens up new possibilities for the automation, monitoring and analysis of goods flows and internal transportation tasks. It is also possible to measure masses of localization data for short distances within buildings, which is why the integration of a localization solution into warehouse systems or production lines is becoming increasingly popular. The systems for localization are usually referred to as real-time location systems (RTLS). Automated guided vehicles (AGVs) and autonomous transport robots with free navigation (AGVs) are also increasingly being used for internal transportation tasks. These are another driver for the use of localization technologies in companies. Location data for assets are determined by different localization systems during the life cycle and even at the same point in time more than one system can deliver a location information. Today location data originate from a variety of non-interoperable systems, for which the data model for the localization information is not standardized. Since asset location data are generated and used by different systems, for different use cases, in different life cycle phases and by different organizations it makes particular sense to manage the location data in the AAS of an asset in the form of a standardized Submodel.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Technical Data for Injection Molding
02044
1.0
In Review
Coming soon

This Submodel template aims at the interoperable provision of information describing an injection molding machine (IMM) regarding to the asset of the respective Asset Administration Shell. The central element is the provision of properties [7], ideally interoperable by means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this Submodel is to enhance the already published IDTA specification “Generic Frame for Technical Data for Industrial Equipment in Manufacturing” (02003-1-2) with specific properties of an injection molding machine. The focus of this document is the standardized description of relevant properties that represent the technical master data of an IMM. Master data in this context characterize the IMM capabilities, usually expressed in minimum, maximum, or boolean values, e.g., the maximum possible clamping force, minimal required mold height, or if the IMM has a centering groove. Typically, this master data is unalterable or fixed for a certain period.
This Submodel targets order management, production planning and control, and can be used for predictive maintenance. In order management, comparing the technical requirements of a plastic part to be produced from a customer with the technical capabilities of the manufacturer’s machinery is possible, e.g., for subcontracting. In a production planning scenario, performing a capability check to find suitable IMM for producing a plastic part in-house is conceivable [8]. Moreover, for production control, this Submodel enables resilience by allowing an accelerated rescheduling of jobs after a disturbance occurs, e.g., machine breakdown, by finding suitable alternative machinery. Lastly, the Submodel can be used for predictive maintenance by providing nominal values of single properties relevant for calculations, e.g., of the remaining useful life. This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, studies of common practices at enterprises, directives, and standards to achieve far-reaching acceptance.
Besides the standardized Submodel, this template also introduces standardized SubmodelElementCollections (SMC) in order to improve interoperability while modeling aspects of IMM within other Submodels, e.g., the injection mold or periphery.
Scope of the document is a common injection moulding machine. Special designs will be considered in later revisions.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Quality Document Part 1: Core Elements
02065-1
1.0
Published
Download
GitHub

This Submodel template addresses the need to handle documentation, certificates and reports about the conformity of an asset to relevant requirements. These kinds of requirements are usually related to the quality infrastructure (metrology, accreditation, conformity assessment, standards, market surveillance) and the corresponding documents are for the purpose of simplicity called “quality documents” here.
The Submodel aims to provide a Digital Quality Document (DQD) model that can be transferred across an asset lifecycle. A quality document in the sense of this specification is a (usually machine-readable) document that contains information about quality properties about an asset, with this specification focusing on conformity statements. In general, one asset may have several conformity statements related to different domains and application purposes. For instance, for a measuring instrument there can be statements about calibration (based on ISO/IEC 17025) and about the compliance with explosion protection (ATEX/IECEx). Each instance of the DQD Submodel is then related to one document for each such statement. That is, several instances of the DQD Submodel can exist for one asset at the same time. Moreover, some conformity statements may relate to the product type rather than the individual asset. This is the case, for instance, for type approval in a conformity assessment based on ISO/IEC 17065.
The information contained in the Submodel is inspired by the already developed XML schema for Digital Calibration Certificates (DCC) [7]. This XML schema meets the requirements of ISO/IEC 17025 and can be cryptographically signed. There is an ongoing international harmonization of DCCs, and an increasing number of certificates and reports in other domains than calibration are being developed in a similar way.
Information described in this DQD Submodel regarding the assets of the respective Asset Administration Shell is semantically identified by means of the DCC namespace and dictionaries such as ECLASS and IEC CDD (Common Data Dictionary).
Part 1 of this Submodel initially focuses on general information expected to be relevant for all types of quality documents, especially with documents related to the ISO/IEC 170xx series in mind. Subsequent versions of this Submodel will extend the general specifications to more specific ones for various domains, such as conformity assessment, testing, and verification.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Process Parameters Instance
02031-2
1.0
Published
Download
GitHub

This Submodel defines instance-specific information of Process Parameters and provides a framework to describe the output parameters for processes of industrial equipment. This Submodel does not require any knowledge about how a process is executed and in which order. It is solely focused on the structured description of data reported by a process.
The need for a dedicated Process Parameters Submodel is to enable the interoperable description and transfer of data between assets. The concept is based on process knowledge from various organizations in the automotive wire harness industry. Although the associated use cases are from the value chain of wire harness manufacturing, the aim of the working group is to develop a generalized Submodel that can be used for a wide variety of products and industries.
This Submodel is intended for the description of output parameters of a process and should be used in combination with the Hierarchical Structures Submodel to define the sequence of process execution and hierarchical requirements.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Predictive Maintenance
02048
1.0
Published
Download
GitHub

The Submodel Predictive Maintenance aims to standardize metadata and information from various sub-systems within highly automated production lines, that are required for developing and deploying predictive maintenance solutions (PdM solutions). This facilitates integration and interoperability of sub-systems of production lines into PdM solutions. In addition, their data can be evaluated in a more targeted manner in the context of the PdM application in order to reduce unplanned machine downtimes. Accordingly, the PdM solutions can in turn provide maintenance-relevant information via the AAS, e.g., on predicted remaining lifetime and/or the probability of failure.
In general PdM aims to predict the end of useful life of a specific device or component (asset). The remaining useful life (RUL) is the duration until this end of life is reached, and the asset must be replaced or a maintenance action must be performed. RUL can be measured in time or other wear relevant units such as a distance/length or numbers of process cycles. The scope of the Submodel is mainly on data related to PdM, not on the prediction model itself.
Thus, this submodel does not contain the implementation details data-driven and AI-boosted models for PdM,. As a matter of fact, this submodel is merely structuring the data attained from an algorithm or model (physical or mathematical) for better utilization in planning and maintaining physical assets in a shopfloor.
The Submodel Predictive Maintenance aims at interoperable provision of information describing PdM topics in regard to an asset. Central element is the provision of properties [7], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network. It targets components of machines or plant sections which are themselves sub-systems of factories or plants and predictive maintenance applications for these components and sub-systems.
The conception is based on existing norms, studies of common practices at enterprises, directives and standards so that a far-reaching acceptance can be achieved (see also section 1.3).
In the context of maintenance, it is important to understand that PdM for industrial applications is a niche but rapidly growing segment within the much broader field of maintenance use cases. Therefore, only functionalities which are directly enabled because of PdM, namely predicted remaining useful lifetime of an asset, are the main focus of this submodel. Topics out of the scope of this submodel are maintenance instructions and preparation, corrective maintenance, predetermined or condition-based maintenance. Figure 1 shows a schematic overview on types of maintenance adapted from DIN EN 13306. Appendix B provides a future vision for the embedding of PdM Submodel in the context of maintenance as a whole and its connections to other existing and potential Submodels
Furthermore, it is important to understand that the aforementioned predicted useful lifetime of an asset in the sense of predictive maintenance is not static. Rather it depends on the concrete use of the asset in a specific process environment. In that regard, this prediction is impacted by the constant changes of the process values, which cause wear and tear to the asset.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Artificial Intelligence Model Nameplate
02060
1.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of information describing Artificial Intelligence (AI) model information in regard to the asset of the respective Asset Administration Shell. Central element is the provision of properties [7], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network. It targets to assist the AI model documentation and helps to manage an AI lifecycle.
The intended use-case is the provision of a standardized property structure for documenting AI models, which enables an efficient management of the different models and helps to reuse already trained models. On top of that it contains information about the responsible person for the model and helps to gain additional information of the model from him.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, studies of common practices at enterprises, directives and standards so that a far-reaching acceptance can be achieved.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Artificial Intelligence Deployment
02059
1.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of information describing deployment of Artificial Intelligence (AI) models in regard to the asset of the respective Asset Administration Shell. Central element is the provision of properties [7], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network. It targets the assistance of deployment of AI models in a standardized way. Currently the focus is on an industrial environment.
The intended use-case is the provision of a standardized property structure for deploying AI, which enables an easier usage of AI in an industrial environment. With the assistance of two other AI Submodels (AI Dataset and AI ModelNameplate), it provides an overview of the whole AI lifecycle and allows an easier management of it.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, studies of common practices at enterprises, directives and standards so that a far-reaching acceptance can be achieved.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Artificial Intelligence Dataset
02058
1.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of information describing a dataset and meta information about it in regard to the asset of the respective Asset Administration Shell. Central element is the provision of properties [7], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network. It aims to provide detailed information about a dataset used in AI context. This includes additional service information (the person responsible for the dataset).
The intended use-case is the provision of a standardized property structure for datasets used to train AI, which enables a standardized way to describe datasets.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, studies of common practices at enterprises, directives and standards so that a far-reaching acceptance can be achieved.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Software Bill of Materials
02042
1.0
In Development
Coming soon

The submodel “Software Bills of Material” represents a formal, machine-readable inventory of software components and their dependencies, as well as information about these components and their hierarchical relationships. The mandatory features of the submodel enable unambiguous identification of the individual software components. Optional features are defined to support extended use cases. The current standardised formats for interoperable exchange of the Software Bill of Material are taken into account in the development of the submodel. The submodel is based on the results of the IDTA submodel “Hierarchical Structures enabling Bills of Material”.   
The submodel offers numerous advantages for the use cases in the collaborative value chains, e.g. in software development, supply chain management, vulnerability management, asset management, procurement, etc.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Vulnerability Management
02043
1.0
In Development
Coming soon

The aim of the submodel “Vulnerability Management” is to establish a clear assignment between vulnerabilities, safety instructions and components used in an industrial plant. In doing so, the CSAF standard can be applied to avoiding duplicate structures. For instance, the submodel may contain the meta-information, the uniform data structure and the information about the vulnerabilities and safety instructions specified by the component manufacturers.
Note: The vulnerability assessment follows the CVSS standard and refers to the corresponding entries in the public registers, such as National Vulnerability Database and VDE CERT. As a rule, the security advisories are created in the open JSON-based CSAF format. Existing references for information exchange of vulnerabilities and security advisories are taken into account, such as Common Security Advisory Framework.  
The submodel “Vulnerability Management” has a wide range of applications; in particular, it enables the resource-saving identification and the unambiguous, machine-readable description of security-relevant vulnerabilities and the corresponding countermeasures for industrial plants. This can significantly increase IT security.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Intelligent Information for Use
02063
1.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of information describing the provisioning of “Intelligent Information for Use”, i.e. information of the Technical Documentation enriched by metadata based on the iiRDS (Intelligent Information Retrieval and Delivery Standard, see Table 2) Standard v1.2 with respect of the asset of the respective Asset Administration Shell. Central element is the provisioning of properties [5], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network.
Target is the cross-manufacturer exchange of technical documentation as information for use. The technical documentation should be transferable as intelligent information, i.e., the content should be modular, semantically rich, and exchangeable in different media formats as well as in media-specific compilations.
Compared to the conventional document-based exchange of technical documentation, the aim is to enable dynamic, structured, and intelligent transmission that can provide content for users in a user-oriented form. This includes usage scenarios in Industry 4.0, websites, mobile apps, portal applications and display on HMIs. The relevant information should be able to be displayed to the user at the right time, in the right context, in the right format, and on the right end device.
The intended use-case is the provisioning of a standardized property structure to exchange and integrate intelligent information between companies, the departments of a company and information from different sources in general.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, studies of common practices at enterprises, directives and standards so that a far-reaching acceptance can be achieved.
Beside standardized Submodel this template also introduces standardized SubmodelElementCollections (SMC) in order to improve the interoperability while modelling aspects and properties of intelligent information within other Submodels.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Asset Interfaces Mapping Configuration
02027
1.0
Published
Download
GitHub

This Asset Interfaces Mapping Configuration (AIMC) Submodel specifies an information model and a common representation for describing the mapping of interface(s) of an asset service or asset-related service already described in an Asset Interfaces Description (AID) Submodel. It can be understood as a configuration Submodel for south-bound communication between AAS and asset. Based on this information in the AIMC Submodel, it is possible to configure and initiate a connection to an asset service and map payloads to intended locations in an AAS automatically, and vice versa.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Provision of 3D Models
02026
1.0
Published
Download
GitHub

The general Scope of the specification IDTA SMT 020026 “Provision of 3D Models” with the Submodel “Models3D” aims to provide enough meta data to find the right file, to integrate the file in the right way and to do plausibility checks. The file can be either provided within the Submodel itself or, as recommended, with a link to an online file source. This Submodel should complement the existing 3D model file formats and is not meant to replace or redefine them. Nevertheless, meta data that is seen as relevant during the exchange (provision, search, integration) of 3D models but is not harmonized across the various 3D formats will be in the scope of this Submodel. Based on the experience of different stakeholders of the working group “Provision of 3D Models”, for various reasons, there is still the demand for different 3D file formats, be it based on standards like ISO 10303 or proprietary software formats. The scope is based on the implemented use cases and might be extended in future versions of the AAS Submodel Template “Provision of 3D Models”. The [SM] “Models 3D” is suitable for Asset Administration Shells (AAS) of the kind type and instance.
In short: the scope of the SubmodelTemplate IDTA 020026 “Provision of 3D Models” with the Submodel “Models3D” is the provision of 3D Models by complementing and not redefining the existing 3D Model formats themselves.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Material Integration
02024
1.0
In Development
Coming soon

Generic integration of material and product information as an ontology to provide a uniform data model on needed usage levels in different steps.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Wireless Communication
02022
1.0
Published
Download
GitHub

This document is intended to address aspects of wireless communication. The structure of this Submodel is expressed through diagrams and UML tables, clarifying its constituent elements. In addition, potential assets and usage scenarios that can benefit from the adoption of this Submodel are identified. The main objective of this Submodel is to integrate wireless industrial communication in the context of the Industry 4.0 (I4.0) framework. The approach is based on the design of a Submodel that encompasses the parameters associated with an asset with wireless communication characteristics. Such a Submodel model is configured to create a fundamental set of Submodel elements that digitally represent relevant information about the different parts that make up a wireless communication system. This Submodel incorporates parameters relevant to various wireless communication technologies and assets. The underlying idea is that the Submodel has a generic character, allowing its application to different technologies and different types of assets. Therefore, some Submodel parameters may be more or less relevant depending on the technology and asset that will be modelled. In order to make the Submodel more specific, the user has the possibility to expand it by adding additional parameters at the time of AAS implementation. Other Submodels targeting specific communication technologies can be standardized later based on this Submodel. The Submodel focuses on layers 1 and 2 of the ISO-OSI model. The description of aspects from layer 3 upwards are not considered in this document and should be described for other submodels, as they do not depend on the type of technology, be it wireless or wired.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Capabilties for Industrial Appliances
02020
1.0
In Review
Coming soon

The Capability Description submodel is used to model process or product requirements (i.e., required capabilities) and resource capabilities (i.e., provided capabilities) in a specified way. Thus, a reliable comparison between required and provided capabilities can be made, enabling efficient planning and orchestration of production processes.
The submodel is based on the definition from [8], [9] where a capability is an “implementation-independent specification of a function in industrial production to achieve an effect in the physical or virtual world”. From [8] it can be seen that the capability class has three central relationships. It is restricted by constraints, specified by properties and realized by skills.
Properties specify the capability in more detail (e.g., maximum speed, allowed tolerances, or temperature range).
Constraints are divided into two types which further restrict the capability:
Property constraints: These refer to properties of a capability (e.g., temperature) and can be used as preconditions, invariants or postconditions.
Transition constraints: Refer to relationships between multiple capabilities to determine their sequence or parallel flow (e.g., transport must occur before tempering).
Skills, on the other hand, implement a capability in the form of technical or software-based solution modules.
Overall, the Capability Description submodel provides is a base for defining the required capabilities in a production process and matching them with the provided capabilities of available resources. It is intended to be used by production planners, machine manufacturers and plant operators.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Control Component Instance
02016
1.0
Published
Download
GitHub

The scope of this Submodel is the definition of instance-specific information of a Control Component (CC) into an AAS. Together with its counterpart, the CCType Submodel (IDTA 02015), both Submodels aim to establish templates to ensure a uniform structure. The use of these templates allows the development of manufacturer- and domain-independent control concepts and facilitates the exchange of process information with other Submodels. Additionally, it allows the use of standardized call and monitoring sequences, as well as standardized description of its services, endpoints, error-codes, etc.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Functional Safety
02014
1.0
Published
Download
GitHub

The submodel shall specify the functional safety and reliability data model descriptions for devices to be used by engineering tools for the design of safety related control systems according to IEC 62061, IEC 61508-2 or ISO 13849-1 or for dependability analysis of electrotechnical systems. This submodel is used to facilitate the exchange between computers of data characterizing safety relevant devices in particular. The data models described in this document is based on the definition in the IEC/CDD 62683-1 DB.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Reliability
02013
1.0
Published
Download
GitHub

The submodel shall specify the functional safety and reliability data model descriptions for devices to be used by engineering tools for the design of safety related control systems according to IEC 62061, IEC 61508-2 or ISO 13849-1 or for dependability analysis of electrotechnical systems. This submodel is used to facilitate the exchange between computers of data characterizing safety relevant devices in particular. The data models described in this document is based on the definition in the IEC/CDD 62683-1 DB.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Inclusion of Module Type Package (MTP) Data into Asset Administration Shell
02001
1.0
Published
Download
GitHub

Within the modular production, module instances are called Process Equipment Assembly (PEA). Module Type Package (MTP) is the integration technology for production modules within the modular production. MTP definies the communication interface towards the PEA and the representation of these interfaces within an MTP file. Per definition this file exclusively contains type-specific module information.
The submodels defined in this document describe the integration of PEA (instance) and MTP (type) information into an AAS. The models do not intend to cover asset aspects addressed by further submodel definitions like technical data or digital nameplate. Therefore, introduced models should be used along with mentioned ones to complete the AAS of the respective asset.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Contact Information
02002
1.0
Published
Download
GitHub

This Submodel template aims at interoperable provision of contact information in regard to the asset of the respective Asset Administration Shell. Central element is the provision of properties, ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). The purpose of this document is to make selected specifications of Submodels in such manner that information about assets can be exchanged in a meaningful way between partners in a value creation network. It targets equipment for process industry and factory automation by defining standardized meta data.
The intended use-case is the provision of a standardized property structure for contact information, which can effectively accelerate the preperation for asset maintenance.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on studies of common practices at enterprises.
Beside standardized Submodel this template also introduces standardized SubmodelElementCollections (SMC) in order to improve the interoperability while modelling aspects of contact information within other Submodels.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Generic Frame for Technical Data for Industrial Equipment in Manufacturing
02003
1.2
Published
Download
GitHub

This Submodel template aims at interoperable provision of technical data describing the asset of the respective Asset Administration Shell. Central element is the provision of properties, ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common data dictionary).
The intended use-case is, that a manufacturer of industrial equipment describes assets (type or instance), which are provided to the market, by the means of technical data (properties), which are interoperable and unambiguously understood by the other market participants, such as system integrators or operators of industrial equipment. For providing individual industrial equipments to the market, also a supplier is covered by the use-case (for this purpose seen as functioning as manufacturer).
This Submodel template specifies a basic set of SubmodelElements in order to bring about the necessary information according to this use-case.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Provision of Simulation Models
02005
1.1
Published
Download
GitHub

The presented Submodel allows the interoperable provision of simulation model files for an asset via the asset administration shell. The Submodel enables this for a wide range of simulation model types and simulation purposes. It contains information about the type of model, how to use the model, and the areas of application.
The main underlying class of models for this Submodel are DAEs, models described by differential algebraic equations. However, models of other types, such as CAD, FMEA, etc., can also be described. FEM type models are not considered explicitly, they will be covered by another Submodel by interest. The models described by this Submodel may be provided in ASCII or binary form to be used with a specific simulation software (e.g. Matlab/Simulink, Virtuos, etc.), as source code (e.g. C, Modelica, etc.), or in a model exchange format such as FMI.
It describes rudimentarily the content of the model.
Assets, where you can provide simulation models via AAS, can be passive parts, active devices, subsystems, machines or even production plants. When using this Submodel template, it is requiered that the asset for which a simulation model should beprovided has an AAS. That is, if there are no AAS yet, first an asset-ID needs to be defined and an AAS created. A Submodel can then be added to this AAS.
In the first step, the Submodel supports searching and finding, as well as requesting simulation model files from manufacturers or distributors.
In further steps, the Submodel will also support the automatic integration of a model into a specific simulation environment, up to an automatic generation of an overall simulation based on structural descriptions of a system containing different components. As it is possible with e.g., the Submodel candidate for hierarchical structures enabling “Bills of Material” (BoM).

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Digital Nameplate for Industrial Equipment
02006
2.0
Published
Download
GitHub

This Submodel template aims to provide asset nameplate information to the respective Asset Administration Shells in an interoperable manner. Central element is the provision of properties [7], ideally interoperable by the means of dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). While in the current version an IRI is provided for a small quantity of the specified properties as their semantic identifier, a complete harmonization of all properties is planned for the subsequent version 2.1. The purpose of this document is to make selected specifications of Submodels in such manner that information about assets and their nameplate can be exchanged in a meaningful way between partners in a value creation network. It targets equipment for process industry and factory automation by defining standardized meta data.
The intended use case is the provision of a standardized property structure within a digital nameplate, which enables the interoperability of digital nameplates from different manufacturers.
This concept can serve as a basis for standardizing the respective Submodel. The conception is based on existing norms, directives and standards so that a far-reaching acceptance can be achieved.
Beside standardized Submodel this template also introduces standardized SubmodelElementCollections (SMC) in order to improve the interoperability while modelling partial aspects within Submodels. The standardized SMCs include address and asset product marking.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Nameplate for Software in Manufacturing
02007
1.0
Published
Download
GitHub

Software becomes more and more an essential part in manufacturing value networks, in smart manufacturing, and in smart products. For an effective and efficient use and management of such software, it is necessary to gather relevant information in a uniform representation. Use cases like updates, patch management, license management, audits, etc. rely on information regarding identification, sources and features of software. This information shall be provided in a consistent manner in form of a “nameplate for software”, derived and specialized from a common digital nameplate.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Maintenance Instructions
02018
1.0
Published
Download
GitHub

Definition maintenance:
The process of preserving a condition or situation or the state of being preserved.
Distinction between predictive and preventive maintenance:
The main difference between both maintenance concepts is that preventive maintenance is scheduled at
regular intervals while predictive maintenance is scheduled as needed (based on asset conditions).
This Submodel template is focused on the handover of preventive maintenance instructions.
Within the product life cycle of components, machines and production facilities (see Figure 1), maintenance
is an essential part of maintaining productivity. Preventive maintenance can be planned and is usually
carried out at set intervals. For planned maintenance, appropriate preparation for planning and execution is
necessary. For this purpose, information is provided by the manufacturer. In reality, this information is often
provided in the form of a PDF containing all the necessary information on maintenance, which is then passed
on. Component manufacturers pass on their information to the machine/plant builder, who then has the task
of creating the maintenance instructions for the machine/plant based on all the information.
The disadvantage of the current solutions: maintenance information often has to be collected manually from
various sources/documents and transferred by copy & paste, e.g. into a maintenance software. This process
is very resource-intensive and offers room for mistakes.
The intended use case starts here and aims at providing an interoperable Submodel on the topic of
maintenance. All required information on maintenance is to be passed on – ideally with the help of
dictionaries such as ECLASS and IEC CDD (Common Data Dictionary). While in the current version most of
the specified properties have an IRI as semantic identifier, a complete harmonisation of all properties is
aimed at for a successor version if possible. The structure by means of SubmodelElementCollections (SMC)
is intended to simplify the evaluation and use of the information, especially the spare parts, consumables and
tool lists.
This Submodel is not intended for calibrations, or the documentation of maintenance work carried out or
calibration values from measurements. However, it can be used as a basis for this.
Important Note:
This Submodel is not suitable for unplanned repair tasks!

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Carbon Footprint
02023
0.9
Published
Download
GitHub

This Submodel template provides the means to exchange an asset`s Carbon Footprint (CF) between the partners along a value chain. The aim of this Submodel is to increase the interoperability between the parties, who are interested in documenting, exchanging, evaluating, or optimizing the environmental footprint of their assets. These parties can for example be manufacturers, users/consumers, or logistic partners. The CF might be part of larger initiatives such as the Digital Product Passport or the Product Environmental Footprint. It is not the scope of this Submodel template to substitute the relevant certificates. Use cases with increasing complexity are described in the following section. The first version of this document will focus on Use Case 1 and 2 only. Additional use cases will be supported in future versions.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Sensor 4.0 Part1: Measurement Value
02029-1
1.0
Published
Download
GitHub

The idea of Submodel Sensor 4.0 is to provide a common representation of all data around industrial sensors, including data that is generated by sensors as well as data that describes the sensor itself and its integration. Submodel Sensor 4.0 is intended as a series of Submodel templates for different aspects of sensor usage. This document as part 1 of the Submodel Sensor 4.0 series is named “Measurement Value” because it focusses on the operation of sensors as data generating devices. It provides a data model for a generic access to sensor data completely independent from the sensor’s functional and interface technology.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
OPC UA Server Data Sheet
02009
1.0
In Review
Coming soon

Content describes data of an OPC UA Server (provided with an asset).

This includes information to find and access the OPC UA server and information about the content implemented in the OPC UA server (used Namespaces, implemented Profiles/Facets/CUs, …) and information about other sources where descriptions are available.

Content could be updated while provisioning and installation.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Time Series Data
02008
1.1
Published
Download
GitHub

In Industrie 4.0, the ubiquity of data sources and sensors and low costs of storage has resulted in increasing amounts of time series data being captured – not only during the operational phase of an asset. A time series is a series of data points in time order over a period of time. Time Series can represent raw data, but can also represent main characteristics, textual descriptions or events in a concise way. This Submodel template aims at an interoperable description of time series data in industrial automation for the complete asset lifecycle. The focus of this Submodel template is on the semantic information of time series data. The Submodel claims to integrate time series data within the AAS itself, but also from external data sources. Figure 1 shows the use cases, such as sensor data from real and virtual sensors, and their technical storage options inside or outside the AAS that were taken into account in the creation of this specification.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Service Request Notification
02010
1.0
Published
Download
GitHub

This Submodel template aims to standardize the description of a Service Request Notification that can be used to create a Service Request Notification for industrial assets, or the asset creates it via his Asset Administration Shell (AAS). These industrial assets, such as production lines, modules, infrastructure elements, and subsystems, are provided by value chain partners such as suppliers, equipment manufacturers, and system integrators. They are utilized in specific applications by industrial operators and end users.
A Service Request Notification is a request for a service to be performed, such as a maintenance, an inspection, or a return. The notification entry can be made by Asset Administration Shell (AAS), via a service dashboard, service portal or even through the customer service department by phone.
The Service Request Notification can be considered as a “call for help”, which, if the business partner responds to it, triggers the further service process.
The objective of the Submodel template is to define and standardize the Service Request Notification, including its content (properties, operations, etc.) and structure. Additionally, service types are defined.
The objective of this Submodel is to enable the interoperable exchange of these notifications between Asset Administration Shells, and the IT systems of various value creation partners.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Hierarchical Structures enabling Bills of Material
02011
1.1
Published
Download
GitHub

This Submodel Template aims to provide hierarchical structures applicable to industrial equipment in an interoperable manner. For this primarily Entities and Relationship Elements of the AAS Metamodel are used.
This industrial equipment, for example production lines, modules and sub systems, are provided by partners in the value chain, such as suppliers, equipment manufacturers and systems integrators and used in specific applications by industrial operators and end users, both in factory as also process automation. Industrial equipment can be composed of subsystems down to material and component level, can include produced products and can be described on type or instance level.
The AAS contains Submodels that cover aspects of the assets among their life cycle. Already in the design phase, assets are composed and aggregated into newly created hierarchical structures.
Typically, assets have their own AAS (Entity with entityType “SelfManagedEntity”), but it is possible that an Asset has no AAS and is represented by a co-managed Entity.
Since nesting of AAS and Submodels is forbidden by the metamodel, this Submodel is intended to provide a description of the internal structure of an asset. It shall allow the consumer of an AAS to identify assets and their corresponding entities and find their respective AAS if they exist. The Submodel serves as an index, pointing to Assets (described as co- or self-managed entities) and AAS in a distributed network capable of transcending the limits of a single organization.
Instances of this Submodel Template shall be the authoritative source for hierarchical structures within an AAS during all lifecycle phases. Complementing information about each asset and their own lifecycle phase is enabled to be discoverable into the n-th level of the hierarchy and across the whole supply chain depending on the design of the Submodel Instance.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Plant Asset Management
02019
1.0
Published
Download
GitHub

The AAS Submodel “Plant Asset Management Specification Sheet” is a crucial tool for the procurement and documentation of Plant Asset Management (PAM) functions in industrial settings. Its scope includes establishing a clear contractual basis and documenting PAM functions. These functions can range from special control system functions to add-on parts on production equipment or enabled functions within the equipment. The Submodel ensures a well-defined contractual basis during procurement, minimizing misunderstandings and improving efficiency. It standardizes requirements, specifications, and expectations related to PAM functions, allowing all stakeholders, such as producers, control system manufacturers, and equipment manufacturers, to have a shared understanding.
Furthermore, the Submodel serves as documentation for PAM functions, capturing vital information. It includes detailed descriptions of function blocks, sensors, and monitoring devices, ensuring a comprehensive record of PAM functionalities. This documentation facilitates troubleshooting, maintenance, and modifications. In addition, the Submodel supports the engineering process, which often involves multiple stakeholders and departments. It acts as a central reference, aligning efforts and fostering collaboration between departments such as procurement, operation, maintenance, sales, and engineering. The Submodel promotes transparency and manages dependencies in engineering PAM functions.
The Submodel also aids decision-making throughout the PAM functions’ lifecycle. It provides information for informed decisions regarding maintenance, upgrades, and component replacement. It also assists in evaluating compatibility and integration of new PAM functions into existing systems. This is crucial for managing complex industrial environments with interconnected systems.
The management of online and historical data for a specific PAM function is not within the scope of this Submodel. This is because such data may contain highly detailed and specific information that is beyond the level of specification covered here. Additionally, the management of this data may be better suited for a separate AAS Submodel focused on general condition monitoring, which is not addressed in this particular Submodel. The primary focus of this Submodel is to establish a contractual basis, document PAM functions, and support the engineering process, rather than delving into the intricacies of online and historical data management.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Control Component Type
02015
1.0
Published
Download
GitHub

The scope of this Submodel is the definition of type-specific information of a Control Component (CC) into an AAS. Together with its counterpart, the CCInstance Submodel (IDTA 02016), both Submodels aim to establish templates to ensure a uniform structure. The use of these templates allows the development of manufacturer- and domain-independent control concepts and facilitates the exchange of process information with other Submodels. Additionally, it allows the use of standardized call and monitoring sequences, as well as standardized description of its services, endpoints, error-codes, etc.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Information Model for P&I Diagrams based on DEXPI Standard
02012
1.0
Published
Download
GitHub

The engineering of a process plant is a complex multi-disciplinary and multi-organizational process involving exchange of a vast number of (semi-)standardized artifacts like diagrams, drawings, tables, certificates, and other documents.
One core artifact which is created and extended during the engineering process is the Piping & Instrumentation Diagram (P&ID) providing among others a good balance of abstraction between the physical layout of the plant (i.e., used equipment and piping connections) and its representation within the automation domain (i.e., signal types, tag names, logical connections between sensor and actuators). Due to this fact P&IDs are long-living artifacts which are frequently used during the whole plant’s lifecycle beyond the engineering phase [7].
Even though most engineering artifacts are created digitally, they are not necessarily exchanged in a machine-readable format. The lack of a machine-readable representation of engineering artifacts (including P&IDs) hinders the digital transformation and can be a show-stoper for digital use-cases due to high costs of creation of a machine-readable P&ID representation.
Efforts to create a standardized machine-readable exchange format for P&ID are made by the DEXPI working group of DECHEMA including of operators from multiple verticals, engineering companies, software tool vendors and research institutes. DEXPI [8] is an UML-Model implemented using an XML-based P&ID exchange format including multiple aspects of plant design like piping topology and its graphical representation, instrumentation structure, tag names. DEXPI is an open industrial standard aiming for a broad usage across industrial domains.
Due to the paramount role of P&ID during whole plant’s lifecycle, the importance of DEXPI has been identified by the Industry 4.0 community. Inclusion of DEXPI models into a standardized lifecycle information container – the Industry 4.0 Asset Administration Shell (AAS) – would facilitate links between different disciplines, organizations and industry domains. Mapping of DEXPI models to the AAS by defining an AAS Submodel template is governed by Industrial Digital Twin Association (IDTA) where a respective working group was founded in 2022. The group consists of representatives of the DEXPI working group, oil and gas industry, engineering and procurement companies, automation equipment suppliers, and research institutes.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Sizing of power drive trains
02021
1.1
Published
Download
GitHub

The Submodel template aims at interoperable provision of information, especially information for sizing
electrical drive systems in industrial automation. For this purpose, the essential components drive, motor,
gearbox, transformation as well as their additional components are described and the parameters necessary
for the calculation are considered. Mechanical and electrical aspects are considered in the drive design. The
Submodel specification addresses machine and plant manufacturers, manufacturers of drive compontents
and developers of sizing tools that exchange information for the use case of drive design. The objective of
the drive design is to select suitable components based on movement patterns and system requirements.

Submodel Template
IDTA Number
Version
Status
Downloads & Links
Asset Interfaces Description
02017
1.0
Published
Download
GitHub

This Submodel specifies an information model and a common representation for describing the interface(s) of an asset service or asset related service. Based on this information, it is possible to initiate a connection to such kind of service and start to request or subscribe to served datapoints, and/or perform operations. Such datapoints of a system service can be, for example, various sensor and/or status values, and an operation can trigger an actuator, such as switching a motor “on” or “off”.
The Asset Interfaces Description (AID) in version 1.1 supports the description of interfaces based on following specific protocols:
• Modbus
• HTTP
• MQTT
• OPC UA
• BACnet