AAS Submodel Templates

Submodels (Teilmodelle) bilden den Inhalt der Asset Administration Shell. Sie beschreiben inhaltliche oder funktionale Aspekte eines Assets. Finden Sie hier die Übersicht der offiziellen IDTA Submodel-Templates.

IDTA TEILMODELLE

Registered AAS Submodel Templates

Sie möchten eigene Submodel Templates entwickeln oder bei der Entwicklung an einem der genannten Submodels Templates mitarbeiten?

Den Erstellungsprozess finden Sie hier. Bei weiteren Fragen nehmen Sie gerne Kontakt mit uns auf.

Anzahl unserer Teilmodelle:
Anzahl unserer Teilmodelle:
0
Submodel Template
IDTA Number
Version
Status
View on GitHub
Inclusion of Module Type Package (MTP) Data into Asset Administration Shell
02001
1.0
Published

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.

Contact Information
02002
1.0
Published

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.

Generic Frame for Technical Data for Industrial Equipment in Manufacturing
02003
1.2
Published

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.

Generic Frame for Technical Data for Industrial Equipment in Manufacturing
extern
1.1
Published

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.

Handover Documentation
02004
1.2
In Review
Coming soon

This Submodel template aims at interoperable provision of information, especially documentation, from manufacturers to operators of industrial equipment. It primarily targets process industry but is also suitable for equipment in factory automation by defining standardadized meta data and a classification for documents. The hereby provided documents contain information required for 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 CE declarations of conformity, ATEX certificates or material certificates. The transfer of this information to the IT systems of the plant operators is standardised in order to minimise the effort for manufacturers and operators.

This Submodel template specifies a basic set of SubmodelElements in order to bring about the necessary information according to VDI 2770-1.

Provision of simulation models
02005
1.0
In Development

This 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 sub-model 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, they are covered by another submodel, actually under development. 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 I want to provide a simulation model has an AAS. That is, if there are no AAS yet, I must first define the asset-ID and create an AAS. 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 a bill of material (BoM).

Digital Nameplate for Industrial Equipment
02006
2.0
Published

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.

Digital Nameplate for Industrial Equipment
extern
1.0
Published

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.

Software Nameplate
02007
1.0
In Development

In the context of Industrie 4.0, software as an asset becomes increasingly important. For an effective and efficient use and management of software in manufacturing value networks, in smart manufacturing, and in smart products, it is necessary to gather relevant information in a uniform representation, as a “nameplate for software”. This supports use cases like updates, patch management, license management, audits, etc.
This Submodel template specifies a basic set of SubmodelElements in order to describe the necessary information.

Time Series Data
02008
1.0
In Development
Coming soon

A time series is a series of data points in (regular or non-regular) time order over a period of time. Time Series can represent raw data with actual values, but can also represent main characteristics in a concise way. For example, two equal values within a time series can have different meanings, depending on whether they are in a rising or falling curve. In the same way, whole subsequences of a time series can be of importance, whereas intermediate sequences only represent unstructured data.

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. This Submodel template aims at an interoperable description of time series data in industrial automation for the complete asset lifecycle to fit time series into a big holistic picture and to obtain a better understanding of complex systems that produces and processes time series data.

The focus of this submodel template is on the semantic information about the time series and its storage within the asset administration shell, as many techniques, data formats and methods have already been developed to process, store and analyse time series data in external systems. The submodel claims to integrate time series data within the asset administration shell itself, but also from external data sources.

To enable the discovering of time series, every AAS that provides time series should have this submodel. In addition, elements of this submodel specification may be used or referenced in other submodels or submodel element collections.

OPC UA Server Data Sheet
02009
1.0
In Development
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.

Service Order Creation
02010
1.0
In Development
Coming soon

This Submodel template aims at interoperable provision of information, that can be used to generate a Service Order in an ERP System.

Hierachical Structures enabling Bills of Material
02011
1.0
In Review
Coming soon

This Submodel template aims at interoperable provision of hierarchical entities and relations which are applicable for industrial equipment. 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 sub systems down to material and component level, described on type or instance level and can include produced products.
The AAS models assets thoughout their lifecycle. Already in the design phase, assets are composed and aggregated into hierarchical structures. As some assets are parts of larger assets, they may each have their own AAS. Since nesting of AAS and Submodels is forbidden by the meta-model, this Submodel shall describe the internal structure of an asset. It shall allow the consumer to identify components and find their respective AAS if they exist. The Submodel serves as an index pointing to Assets 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 topological structure within an AAS during all lifecycle phases. Complementing information about each component and their own lifecycle phase shall be made discoverable into the n-th tier, depending on the design of the Submodel Instance.

DEXPI
02012
1.0
In Development

Proposal for AAS-submodel to package and transfer P&I-Diagrams packaged according to the DEXPI-Standard.

Reliability
02013
1.0
Published

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.

Functional Safety
02014
1.0
Published

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.

Control Component Type
02015
1.0
In Development

Actuators, sensors and their composition into operating equipment for industrial production usually require automated guidance. The associated control functionality can be encapsulated in components. These control components show similar interfaces to the outside across different application domains and hierarchy levels and similar behavior when interacting with these interfaces.

The ControlComponentType and ControlComponentInstance submodels enable a simple, uniform description of these components for their use in or for setting up process control (orchestration). Therefore they describe mainly
– which interfaces are available and how they can be reached,
– which modes (operation modes, services, procedures, skills, depending on the context) the components offer at the interface
– and which errors can occur in these modes.
The submodels thus make it possible in the future to compile the operating modes of the leading components according to different standards (e.g. a mixing service in an MTP module and the filling of a PackML machine) in engineering to form a machine-supported sequence or to assign these to required capabilities in the sequence. In doing so, the driving modes can be semantically annotated via additional capabilities submodels. At the same time, the compensation of errors and the establishment of communication links can be provided for. Finally, the sequences can be implemented automatically in the plant.

Control Component Instance
02016
1.0
In Development

Actuators, sensors and their composition into operating equipment for industrial production usually require automated guidance. The associated control functionality can be encapsulated in components. These control components show similar interfaces to the outside across different application domains and hierarchy levels and similar behavior when interacting with these interfaces.

The ControlComponentType and ControlComponentInstance submodels enable a simple, uniform description of these components for their use in or for setting up process control (orchestration). Therefore they describe mainly
– which interfaces are available and how they can be reached,
– which modes (operation modes, services, procedures, skills, depending on the context) the components offer at the interface
– and which errors can occur in these modes.
The submodels thus make it possible in the future to compile the operating modes of the leading components according to different standards (e.g. a mixing service in an MTP module and the filling of a PackML machine) in engineering to form a machine-supported sequence or to assign these to required capabilities in the sequence. In doing so, the driving modes can be semantically annotated via additional capabilities submodels. At the same time, the compensation of errors and the establishment of communication links can be provided for. Finally, the sequences can be implemented automatically in the plant.

Asset Interface Description
02017
1.0
In Development

Standardization of the structure and semantics required to interact with an asset or service, e.g., to request/subscribe to specific data points or to perform operations based on communication protocols such as Modbus, OPC UA, HTTP, and MQTT. The W3C Web of Things Thing Description is considered to have a base line for content and structure for submodule definition.

Maintenance
02018
1.0
In Development

Submodel for the transfer of all relevant information regarding maintenance (maintenance instructions/maintenance steps, required maintenance materials, maintenance intervals, …) for integration into various higher-level maintenance software/systems. Standardization of the transfer of maintenance information to plant or machine manufacturers, or to plant operators and service organizations.

Plant Asset Management
02019
1.0
In Development
Coming soon

The submodel describes the plant asset management aspects of production plants in the process industry. It refers to the condition and criticality of assets in production processes, as well as to functions and methods for providing all relevant information to asset managers. It also forms the basis for the development of PAM methods.

Capability
02020
1.0
In Development

Submodel to express capability definitions of a production resource, allowing to connect capability definitions and their properties from ontologies/catalouges to executable skills and their parameters.

Engineering of Power Drive Trains
02021
1.0
In Development
Coming soon

The objective of the drive design is to select suitable components based on movement patterns and system requirements. Major components that are described: Sizing Project: Identifying characteristics of the sizing project with reference to the sizing project file. Customer Requirements: • Motion and load profile: The specified motion sequence and the calculated motion, taking into account the workload and customer specifications. • Environmental: Environmental conditions in which the drive train is to be operated. • System Requirements: The features required by the customer in the selection of individual components and in the consideration of the overall system. Transformation mechanisms: Mechanisms for transmitting the force in the drive task, such as belt or rack and pinion applications. Sizing Results: Bill of Material: Simple list for ordering the individual components. Utilization Rates: Technical data of the drive components and their utilization rates in relation to the requirements in the motion profile.

Wireless Communication
02022
1.0
In Development
Coming soon

A crucial part of highly interconnected I4.0 systems is the wireless communication system (WCS). Therefore, it has to cope with the level of adaptability required by I4.0 and, should not be planned and installed for worst-case scenarios as in the traditional systems. It means that if changes are necessary, the WCS and/or its use of the medium should be adapted accordingly. It includes changes due to the production process requirements or changes due to external disturbances, for example, interferences. For that, WCS should be capable of self-configuration to adjust itself to the possible changes.
To reach this capability, a collaboration between the production system and WCS is necessary. To enable this collaboration between the parties, it is proposed a digital twin approach. In this approach, data exchange between the production system and the WCS in the digital domain is required. For that it is necessary that the relevant parameters of WCS are also considered when developing the AAS of assets. The AAS must have a submodel that contain all relevant information related with wireless communication. This information will be used in the digital domain to manage communication resources.
Among the submodels and properties proposed, there is the submodel TransceiverFunction. Two submodels element collection are defined within this submodel element: Transmiter and Receiver. Under these two elements are properties as bitrate, modulation type and receiver sensitivity. A management system can use information from the AAS related to the wireless signal as RSSI and RSRP to monitor the conditions of the radio channel. The management system can take actions based on these values.

Carbon Footprint
02023
1.0
In Development
Coming soon

Due to new regulations, carbon pricing and increasing requirements for the sustainability of manufactured products, the need for a way to determine the carbon footprint of manufactured products (PCF) as well as the provision of information about the carbon footprint over the entire supply chain is also increasing. The goal is to create a sub-model to enable sharing and low-effort retrieval of carbon footprint information per product across the entire supply chain. Existing standards are to be taken into account.

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.

Batch Process
02025
1.0
In Development
Coming soon

The objective is to propose a model for the definition of AAS for industry-specific assets of batch-manufactured products based on the ISA 88 standard, which makes it possible to digitally represent information related to the production recipe, as a step towards the digitization of the product life cycle. The ultimate goal is use the data obtained by the AAS to execute blockchain-based smart contracts that validate compliance with the technical specifications of the product.

3D CAD
02026
1.0
Proposal submitted
Coming soon

This AAS Submodel Template „3D CAD“ aims to provide fully functional 3D CAD files (either directly embedded or referenced) and 3D CAD related properties in a software vendor independent way.
The intended use case is, that an industrial equipment manufacturer can fully integrate 3D CAD files and properties of product types or instances of an asset in the format required by his specific tool landscape, without loss of information, performance and features, like it’s the case with formats like STEP (ISO 10303).

Security Engineering
In Development
Coming soon

Modeling of the information needed for the security engineering of process automation plants.

Platform Resources
Proposal submitted
Coming soon

Model structure for the (runtime) representation of platform (device) resources such as memory and CPU capacities, available communication infrastructure, etc.

The platform resources submodel enables a uniform representation of the platform resources for different use cases. For example, this information is required to analyze the real-time capability of a deployment as part of a “what-if” analysis.

Sensor
Proposal submitted
Coming soon