Figure1_

Figure3_

Figure4_

Figure5_

     OPC UA Companion Specification

OPC 30270

 

OPC UA for Asset Administration Shell (AAS)

 

 

 

 

Release 1.00

2021-06-04

 

 

 

 

 

 


 

Standard Type:

Industry Standard Specification

Comments:

 

 

 

 

Title:

OPC UA for Asset Administration Shell (AAS)

Date:

2021-06-04

 

 

 

 

Version:

Release 1.00

Software:

MS-Word

Editors:

 

Source:

OPC 30270 - UA Companion Specification for AAS 1.00.docx

 

 

 

 

 

Owner:

 

Status:

Release

 

 

 

 


 

 

CONTENTS

Page

 

Figures......................................................................................................... vi

Tables......................................................................................................... vii

1       Scope........................................................................................................ 1

2       Normative references..................................................................................... 1

3       Terms, definitions and conventions.................................................................... 1

3.1            Overview......................................................................................... 1

3.2            OPC UA for Asset Administration Shell terms........................................... 2

3.3            Abbreviations and symbols.................................................................. 2

3.4            Conventions used in this document........................................................ 2

3.4.1             Conventions for Node descriptions.......................................... 2

3.4.2             NodeIds and BrowseNames................................................... 3

3.4.2.1     NodeIds......................................................................... 3

3.4.2.2     BrowseNames................................................................. 3

3.4.3             Common Attributes.............................................................. 4

3.4.3.1     General......................................................................... 4

3.4.3.2     Objects.......................................................................... 4

3.4.3.3     Variables........................................................................ 4

3.4.3.4     VariableTypes................................................................. 5

3.4.3.5     Methods......................................................................... 5

4       General information on the Asset Administration Shell and OPC UA.......................... 5

4.1            Introduction to the Asset Administration Shell........................................... 5

4.1.1             Motivation......................................................................... 5

4.1.2             AAS metamodel overview...................................................... 6

4.2            Introduction to OPC Unified Architecture................................................. 7

4.2.1             What is OPC UA?................................................................ 7

4.2.2             Basics of OPC UA............................................................... 7

4.2.3             Information modelling in OPC UA............................................ 8

4.2.3.1     Concepts....................................................................... 8

4.2.3.2     Namespaces................................................................. 11

4.2.3.3     Companion Specifications................................................. 11

5       AAS metamodel representation in the OPC UA information model........................... 11

5.1            General rules for the mapping of the AAS metamodel to the OPC UA information model................................................................................................... 11

5.2            Overview of AAS in the OPC UA information model.................................. 15

5.3            Overview of AAS types which are directly inherited from OPC UA types........ 15

5.4            Handling of Dictionary Entries............................................................. 16

6       OPC UA ObjectTypes................................................................................... 17

6.1            General remark............................................................................... 17

6.2            AAS root ObjectTypes....................................................................... 17

6.3            AASReferenceType.......................................................................... 17

6.4            Referable and Identifiable.................................................................. 19

6.4.1             IAASReferableType............................................................ 21

6.4.2             IAASIdentifiableType.......................................................... 21

6.4.3             AASAdministrativeInformationType........................................ 22

6.5            AASIdentifierType............................................................................ 22

6.6            AASAssetType................................................................................ 23

6.7            AASSubmodelType........................................................................... 24

6.8            SubmodelElementType specialization................................................... 25

6.8.1             AASSubmodelElementType common attributes......................... 27

6.8.2             AASSubmodelElementCollectionType..................................... 28

6.8.3             AASOrderedSubmodelElementCollectionType.......................... 28

6.8.4             AASMultiLanguagePropertyType........................................... 30

6.8.5             AASPropertyType.............................................................. 31

6.8.6             AASCapabilityType............................................................ 31

6.8.7             AASOperationType............................................................ 32

6.8.8             AASBlobType................................................................... 33

6.8.9             AASFileType.................................................................... 33

6.8.10          AASRelationshipElementType............................................... 35

6.8.11          AASReferenceElementType................................................. 37

6.8.12          AASEventType.................................................................. 38

6.8.13          AASEntityType.................................................................. 39

6.8.14          AASRangeType................................................................. 39

6.9            Concept description.......................................................................... 40

6.9.1             AASIrdiConceptDescriptionType............................................ 41

6.9.2             AASIriConceptDescriptionType............................................. 41

6.9.3             AASCustomConceptDescriptionType...................................... 42

6.10         AAS Data Specification Templates....................................................... 42

6.10.1          AASDataSpecificationType.................................................. 42

6.10.2          AASDataSpecificationIEC61360Type...................................... 44

6.10.3          AASDataSpecificationType.................................................. 45

6.11         AAS Qualifiers................................................................................. 46

6.11.1          AASQualifierType.............................................................. 46

6.11.2          AASQualifier usage............................................................ 47

6.12         AASViewType................................................................................. 48

7       OPC UA DataTypes..................................................................................... 49

7.1            AASIdentifierTypeDataType enum value definition................................... 49

7.2            AASModelingKindDataType................................................................ 49

7.3            AASAssetKindDataType.................................................................... 50

7.4            AASKey data types........................................................................... 50

7.4.1             AASKeyDataType.............................................................. 50

7.4.2             AASKeyElementsDataType.................................................. 50

7.5            AASKeyTypeDataType...................................................................... 51

7.6            AASCategoryDataType...................................................................... 51

7.7            AASValueTypeDataType.................................................................... 51

7.8            AASPathDataType........................................................................... 52

7.9            AASMimeDataType.......................................................................... 52

7.10         AASEntityTypeDataType.................................................................... 52

7.11         AASDataTypeIEC61360DataType........................................................ 53

7.12         AASLevelTypeDataType.................................................................... 53

8       Profiles and ConformanceUnits....................................................................... 54

8.1            Conformance Units........................................................................... 54

8.2            Profiles.......................................................................................... 54

8.2.1             Profile list........................................................................ 54

8.2.2             Server Facets................................................................... 54

8.2.2.1     Overview...................................................................... 54

8.2.2.2     I4AAS BaseFunction Server Server Facet............................. 54

9       Namespaces.............................................................................................. 55

9.1            Namespace Metadata....................................................................... 55

9.2            Handling of OPC UA Namespaces........................................................ 56

Annex A (normative)  OPC UA for AAS Namespace and mappings................................ 57

Annex B (informative)       Pick and Place station Information Model example.................... 58

 


 

Figures

 

Figure 1 – Smart manufacturing component – I4.0-component....................................... 6

Figure 2 – AAS Metamodel overview........................................................................ 6

Figure 3 – The Scope of OPC UA within an Enterprise................................................. 7

Figure 4 – A Basic Object in an OPC UA Address Space.............................................. 8

Figure 5 – The Relationship between Type Definitions and Instances............................... 9

Figure 6 – Examples of References between Objects................................................. 10

Figure 7 – The OPC UA Information Model Notation................................................... 10

Figure 8 – Overview of the AAS OPC UA core information model.................................. 15

Figure 9 – AASReference type.............................................................................. 18

Figure 10 – Identification concepts for AAS.............................................................. 19

Figure 11 – OPC UA mapping of the identification concept.......................................... 20

Figure 12 – AASAssetType graphical overview......................................................... 23

Figure 13 – AASSubmodelType graphical overview.................................................... 24

Figure 14 – SubmodelElement Subtypes................................................................. 26

Figure 15 – AASSubmodelElementType graphical overview......................................... 27

Figure 16 – AASSubmodelElementCollectionType graphical overview............................ 28

Figure 17 – AASOrderedSubmodelElementCollectionType graphical overview.................. 29

Figure 18 – AASMultiLanguagePropertyType graphical overview................................... 30

Figure 19 – AASPropertyType graphical overview...................................................... 31

Figure 20 – AASOperationType graphical overview.................................................... 32

Figure 21 – AASBlobType graphical overview........................................................... 33

Figure 22 – AASFileType graphical overview............................................................ 34

Figure 23 – AASRelationElementType graphical overview........................................... 35

Figure 24 – AASReferenceElementType graphical overview......................................... 37

Figure 25 – AASEventType graphical overview......................................................... 38

Figure 26 – AASEntityType graphical overview......................................................... 39

Figure 27 – Concept description and data specification OPC UA graphical model.............. 41

Figure 28 – AASDataSpecificationIEC61360Type graphical overview............................. 44

Figure 29 – Structure of the object AASQualifierType................................................. 46

Figure 30 – Primitive AAS data types..................................................................... 49

Figure 31 – Example pick and place station with subcomponents boring and honing.......... 58

Figure 32 – Example pick and place station – submodel honing.................................... 59

Figure 33 – Example pick and place station – property with concept description reference.. 59

Figure 34 – Example pick and place station – concept description elements..................... 60

Figure 35 – Example pick and place station – data specification of concept description...... 60

Figure 36 – Example pick and place station – package explorer view............................. 61

 


Tables

Table 1 – Examples of DataTypes 2

Table 2 – Type Definition Table. 3

Table 3 – Common Node Attributes 4

Table 4 – Common Object Attributes 4

Table 5 – Common Variable Attributes 5

Table 6 – Common VariableType Attributes 5

Table 7 – Common Method Attributes 5

Table 8 – Basic ObjectTypes of the asset administration shell 15

Table 9 – Basic ReferenceTypes of the asset administration shell 16

Table 10 – Basic data types of the asset administration shell 16

Table 11 – AASAssetAdministrationShellType Definition. 17

Table 12 – AASAssetAdministrationShellType Additional References 17

Table 13 – AASReferenceType Definition. 18

Table 14 – AASReferenceType Additional References 18

Table 15 – IAASReferableType Definition. 21

Table 16 – IAASReferableType Additional References 21

Table 17 – IAASIdentifiableType Definition. 21

Table 18 – IAASIdentifiableType Additional References 21

Table 19 – AASAdministrativeInformationType Definition. 22

Table 20 – AASAdministrativeInformationType Additional References 22

Table 21 – AASIdentifierType. 22

Table 22 – AASIdentifierType Additional References. 22

Table 23 – AASAssetType Definition. 23

Table 24 – AASAssetType Additional References 23

Table 25 – AASSubmodelType Definition. 24

Table 26 – AASSubmodelType Additional References 25

Table 27 – AASSubmodelElementType Definition. 27

Table 28 – AASSubmodelElementType Additional References 28

Table 29 – AASSubmodelElementCollectionType Definition. 28

Table 30 – AASSubmodelElementCollectionType Additional References 28

Table 31 – AASOrderedSubmodelElementCollectionType Definition. 29

Table 32 – AASOrderedSubmodelElementCollectionType Additional References 30

Table 33 – AASMultiLanguagePropertyType Definition 30

Table 34 – AASMultiLanguagePropertyType Additional References 30

Table 35 – AASPropertyType Definition. 31

Table 36 – AASPropertyType Additional References 31

Table 37 – AASCapabilityType Definition. 32

Table 38 – AASOperationType Definition. 32

Table 39 – AASBlobType Definition. 33

Table 40 – AASBlobType Additional References 33

Table 41 – AASFileType Definition. 34

Table 42 – AASFileType Additional References 34

Table 43 – AASRelationshipElementType Definition. 35

Table 44 – AASRelationshipElementType Additional References 36

Table 45 – AASAnnotatedRelationshipElementType Definition. 36

Table 46 – AASAnnotatedRelationshipElementType Additional References 36

Table 47 – AASReferenceElementType Definition. 38

Table 48 – AASReferenceElementType Additional References 38

Table 49 – AASEventType Definition. 38

Table 50 – AASEntityType Definition. 39

Table 51 – AASEntityType Additional References 39

Table 52 – AASRangeType Definition. 40

Table 53 – AASRangeType Additional References 40

Table 54 – AASIrdiConceptDescriptionType Definition. 41

Table 55 – AASIrdiConceptDescriptionType Additional References. 41

Table 56 – AASIriConceptDescriptionType Definition. 42

Table 57 – AASIriConceptDescriptionType Additional References 42

Table 58 – AASCustomConceptDescriptionType Definition 42

Table 59 – AASCustomConceptDescriptionType Additional References 42

Table 60 – AASDataSpecificationType Definition. 43

Table 61 – AASDataSpecificationIEC61360Type Definition. 45

Table 62 – AASDataSpecificationIEC61360Type Additional References 45

Table 63 – AASQualifierType Definition. 46

Table 64 – AASQualifierType Additional References. 47

Table 65 – AASViewType Definition 48

Table 66 – AASViewType Additional References 48

Table 67 – AASIdentifierTypeDataType Definition. 49

Table 68 – AASModelingKindDataType enum value Definition. 49

Table 69 – AASAssetKindDataType enum value Definition. 50

Table 70 – AASKeyDataType. 50

Table 71 – AASKeyElementsDataType enum value Definition. 50

Table 72 – AASKeyTypeDataType. 51

Table 73 – AASCategoryDataType enum Definition. 51

Table 74 – AASValueTypeDataType enum Definition. 51

Table 75 – AASPathDataType Definition. 52

Table 76 – AASMimeDataType Definition. 52

Table 77 – AASEntityTypeDataType Definition. 52

Table 78 – AASEntityTypeDataType Definition. 52

Table 79 – AASDataTypeIEC61360DataType Definition. 53

Table 80 – AASDataTypeIEC61360DataType Definition. 53

Table 81 – AASLevelTypeDataType Definition. 53

Table 82 – AASLevelTypeDataType enum value Definition 53

Table 83 – I4AAS Conformance Units Definition. 54

Table 84 – Profile URIs for I4AAS. 54

Table 85 – I4AAS BaseFunction Server Facet Definition. 55

Table 86 – NamespaceMetadata Object for this companion specification. 55

Table 87 – Namespaces used in a I4AAS Server 56

Table 88 – Namespaces used in this companion specification. 56

 


 

 

OPC Foundation, ZVEI, VDMA

____________

AGREEMENT OF USE

COPYRIGHT RESTRICTIONS

·       This document is provided "as is" by the OPC Foundation, ZVEI, and VDMA.

·       Right of use for this companion specification is restricted to this companion specification and does not grant rights of use for referred documents.

·       Right of use for this companion specification will be granted without cost.

·       This document may be distributed through computer systems, printed or copied as long as the content remains unchanged and the document is not modified.

·       OPC Foundation, ZVEI, and VDMA do not guarantee usability for any purpose and shall not be made liable for any case using the content of this document.

·       The user of the document agrees to indemnify OPC Foundation, ZVEI, and VDMA and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this companion specification.

·       The document shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

·       The intellectual property and copyright is solely owned by the OPC Foundation, ZVEI, and VDMA.

 

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC Foundation, ZVEI, or VDMA  specifications may require use of an invention covered by patent rights. OPC Foundation, ZVEI, or VDMA shall not be responsible for identifying patents for which a license may be required by any OPC Foundation, ZVEI, or VDMA specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC Foundation, ZVEI, or VDMA specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION NOR ZVEI NOR VDMA MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION NOR ZVEI NOR VDMA BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this companion specification is borne by you.

RESTRICTED RIGHTS LEGEND

This companion specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830

COMPLIANCE

The combination of ZVEI, VDMA, and OPC Foundation shall at all times be the sole entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials as specified within this document. Products developed using this companion specification may claim compliance or conformance with this companion specification if and only if the software satisfactorily meets the certification requirements set by ZVEI NOR VDMA, or the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this companion specification and must not claim compliance or conformance with this companion specification.

Trademarks

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of Germany.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this companion specification.

 

 


 


1     Scope

The companion specification presented in this document is an extension of the overall OPC Unified Architecture standards and defines an information model that conforms to the Industrie 4.0 Asset Administration Shell (AAS) metamodel defined in the Plattform Industrie 4.0 document “Details of the Asset Administration Shell” (see Section 2).

The aim of the AAS metamodel is to enable partners in a value creation network to exchange meaningful information by conforming to a specified set of standardized information elements.

This companion specification describes the mapping of the AAS metamodel specified in “Details of the Asset Administration Shell - Part 1” (see Section 2) to the OPC UA information model in order to represent AAS and their submodels in the address space of OPC UA servers.

 

2     Normative references

The following referenced documents are indispensable for the application of this companion specification. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

Details of the Asset Administration Shell - Part 1 - The exchange of information between partners in the value chain of Industrie 4.0 (Version 2.0.1).

https://www.plattform-i40.de/PI40/Redaktion/EN/Downloads/Publikation/Details_of_the_Asset_Administration_Shell_Part1_V2.html

OPC 10000-1 - OPC UA Specification: Part 1 – Concepts

http://www.opcfoundation.org/UA/Part1/

OPC 10000-2 - OPC UA Specification: Part 2 – Security Model

http://www.opcfoundation.org/UA/Part2/

OPC 10000-3 - OPC UA Specification: Part 3 – Address Space Model

http://www.opcfoundation.org/UA/Part3/

OPC 10000-4 - OPC UA Specification: Part 4 – Services

http://www.opcfoundation.org/UA/Part4/

OPC 10000-5 - OPC UA Specification: Part 5 – Information Model

http://www.opcfoundation.org/UA/Part5/

OPC 10000-6 - OPC UA Specification: Part 6 – Mappings

http://www.opcfoundation.org/UA/Part6/

OPC 10000-7 - OPC UA Specification: Part 7 – Profiles

http://www.opcfoundation.org/UA/Part7/

OPC 10000-19 – OPC UA Specification: Part 19 – Dictionary Reference

http://www.opcfoundation.org/UA/Part19/

 

3     Terms, definitions and conventions

3.1     Overview

It is assumed that basic concepts of OPC UA information modelling and metamodel of the AAS are understood in this companion specification. This companion specification will use these concepts to describe the AAS Information Model. For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-7 and “Details of the Asset Administration Shell – Part 1” V2.0 (see section 2) as well as the following apply.

Note that OPC UA terms and terms defined in this companion specification are italicized in the specification.

 

3.2     OPC UA for Asset Administration Shell terms

The terms defined in “Details of the Asset Administration Shell - Part 1” (see section 2) are valid for this companion specification. 

 

3.3     Abbreviations and symbols

 

AAS            Asset Administration Shell

 

3.4     Conventions used in this document

3.4.1    Conventions for Node descriptions

Node definitions are specified using tables (see Table 2).

Attributes are defined by providing the Attribute name and a value, or a description of the value.

References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass.

·      If the TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table.

·      The DataType is only specified for Variables; “[<number>]” indicates a single-dimensional array, for multi-dimensional arrays the expression is repeated for each dimension (e.g. [2][3] for a two-dimensional array). For all arrays the ArrayDimensions is set as identified by <number> values. If no <number> is set, the corresponding dimension is set to 0, indicating an unknown size. If no number is provided at all the ArrayDimensions can be omitted. If no brackets are provided, it identifies a scalar DataType and the ValueRank is set to the corresponding value (see OPC 10000-3). In addition, ArrayDimensions is set to null or is omitted. If it can be Any or ScalarOrOneDimension, the value is put into “{<value>}”, so either “{Any}” or “{ScalarOrOneDimension}” and the ValueRank is set to the corresponding value (see OPC 10000-3 and the ArrayDimensions is set to null or is omitted. Examples are given in Table 1.

Table 1 – Examples of DataTypes

Notation

Data­Type

Value­Rank

Array­Dimensions

Description

Int32

Int32

-1

omitted or null

A scalar Int32.

Int32[]

Int32

1

omitted or {0}

Single-dimensional array of Int32 with an unknown size.

Int32[][]

Int32

2

omitted or {0,0}

Two-dimensional array of Int32 with unknown sizes for both dimensions.

Int32[3][]

Int32

2

{3,0}

Two-dimensional array of Int32 with a size of 3 for the first dimension and an unknown size for the second dimension.

Int32[5][3]

Int32

2

{5,3}

Two-dimensional array of Int32 with a size of 5 for the first dimension and a size of 3 for the second dimension.

Int32{Any}

Int32

-2

omitted or null

An Int32 where it is unknown if it is scalar or array with any number of dimensions.

Int32{ScalarOrOneDimension}

Int32

-3

omitted or null

An Int32 where it is either a single-dimensional array or a scalar.

 

·      The TypeDefinition is specified for Objects and Variables.

·      The TypeDefinition column specifies a symbolic name for a NodeId, i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node.

·      The ModellingRule of the referenced component is provided by specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace, the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object.

If the NodeId of a DataType is provided, the symbolic name of the Node representing the DataType shall be used.

Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType, their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition.

Table 2 illustrates the Type Definition Table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point to the Node definition.

Table 2 – Type Definition Table

Attribute

Value

Attribute name

Attribute value. If it is an optional Attribute that is not set “—” will be used.

 

 

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

ReferenceType name

NodeClass of the TargetNode.

BrowseName of the target Node. If the Reference is to be instantiated by the server, then the value of the target Node’s BrowseName is “—”.

DataType of the referenced Node, only applicable for Variables.

TypeDefinition of the referenced Node, only applicable for Variables and Objects.

Referenced ModellingRule of the referenced Object.

NOTE Notes referencing footnotes of the table content.

 

Components of Nodes can be complex and contain components by themselves. The TypeDefinition, NodeClass, DataType and ModellingRule can be derived from the type definitions, and the symbolic name can be created as defined in 3.4. Therefore, those contained components are not explicitly specified; they are implicitly specified by the type definitions.

3.4.2    NodeIds and BrowseNames

3.4.2.1    NodeIds

The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.

The symbolic name of each Node defined in this companion specification is its BrowseName, or, when it is part of another Node, the combination of the BrowseName of the other Node, a “.” and the BrowseName of itself. In this case “part of” means that the whole has a 0:HasProperty or 0:HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique name in this companion specification, the symbolic name is unique.

The NamespaceUri for all NodeIds defined in this companion specification is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table.

Note that this companion specification not only defines concrete Nodes, but also requires that some Nodes shall be generated, for example one for each Session running on the Server. The NodeIds of those Nodes are Server-specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this companion specification, because they are not defined by this companion specification but generated by the Server.

3.4.2.2    BrowseNames

The text part of the BrowseNames for all Nodes defined in this companion specification is specified in the tables defining the Nodes. The NamespaceUri for all BrowseNames defined in this companion specification is defined in Annex A.

If the BrowseName is not defined by this companion specification, a namespace index prefix like ‘0:EngineeringUnits’ or ‘2:DeviceRevision’ is added to the BrowseName. This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this companion specification. Table 88 provides a list of namespaces and their indexes as used in this companion specification.

3.4.3    Common Attributes

3.4.3.1    General

The Attributes of Nodes, their DataTypes and descriptions are defined in OPC 10000-3. Attributes not marked as optional are mandatory and shall be provided by a Server. The following tables define if the Attribute value is defined by this companion specification or if it is server-specific.

For all Nodes specified in this companion specification, the Attributes named in Table 3 shall be set as specified in the table.

Table 3 – Common Node Attributes

Attribute

Value

DisplayName

The DisplayName is a LocalizedText. Each server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId “en”. Whether the server provides translated names for other LocaleIds is server-specific.

Description

Optionally a server-specific description is provided.

NodeClass

Shall reflect the NodeClass of the Node.

NodeId

The NodeId is described by BrowseNames as defined in 3.4.2.1.

WriteMask

Optionally the WriteMask Attribute can be provided. If the WriteMask Attribute is provided, it shall set all non-server-specific Attributes to not writable. For example, the Description Attribute may be set to writable since a Server may provide a server-specific description for the Node. The NodeId shall not be writable, because it is defined for each Node in this companion specification.

UserWriteMask

Optionally the UserWriteMask Attribute can be provided. The same rules as for the WriteMask Attribute apply.

RolePermissions

Optionally server-specific role permissions can be provided.

UserRolePermissions

Optionally the role permissions of the current Session can be provided. The value is server-specific and depends on the RolePermissions Attribute (if provided) and the current Session.

AccessRestrictions

Optionally server-specific access restrictions can be provided.

 

3.4.3.2    Objects

For all Objects specified in this companion specification, the Attributes named in Table 4 shall be set as specified in the Table 4. The definitions for the Attributes can be found in OPC 10000-3.

Table 4 – Common Object Attributes

Attribute

Value

EventNotifier

Whether the Node can be used to subscribe to Events or not is server-specific.

 

3.4.3.3    Variables

For all Variables specified in this companion specification, the Attributes named in Table 5 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

Table 5 – Common Variable Attributes

Attribute

Value

MinimumSamplingInterval

Optionally, a server-specific minimum sampling interval is provided.

AccessLevel

The access level for Variables used for type definitions is server-specific, for all other Variables defined in this companion specification, the access level shall allow reading; other settings are server-specific.

UserAccessLevel

The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least one user.

Value

For Variables used as InstanceDeclarations, the value is server-specific; otherwise it shall represent the value described in the text.

ArrayDimensions

If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific.

If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the Variable.

Historizing

The value for the Historizing Attribute is server-specific.

AccessLevelEx

If the AccessLevelEx Attribute is provided, it shall have the bits 8, 9, and 10 set to 0, meaning that read and write operations on an individual Variable are atomic, and arrays can be partly written.

 

3.4.3.4    VariableTypes

For all VariableTypes specified in this companion specification, the Attributes named in Table 6 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

Table 6 – Common VariableType Attributes

Attributes

Value

Value

Optionally a server-specific default value can be provided.

ArrayDimensions

If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific.

If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType.

3.4.3.5    Methods

For all Methods specified in this companion specification, the Attributes named in Table 7 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

Table 7 – Common Method Attributes

Attributes

Value

Executable

All Methods defined in this companion specification shall be executable (Executable Attribute set to “True”), unless it is defined differently in the Method definition.

UserExecutable

The value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user.

 

 

4     General information on the Asset Administration Shell and OPC UA

4.1     Introduction to the Asset Administration Shell

4.1.1    Motivation

The Asset Administration Shell[1] (AAS) is the standardized digital representation of an asset, the corner stone for the interoperability of Industrie 4.0 components organized in Industrie 4.0 systems. The Industrie 4.0 component is the combination of the asset and its digital representation, the AAS, as illustrated in Figure 1. The AAS may be the logical representation of a simple component, a machine or a plant at any level of the equipment hierarchy. The manufacturer provides the standardized digital representation to his customers, creating both an AAS for the asset type and for each asset instance. The system designers, the asset users, the applications, the processes and the asset itself update the information of the AAS during the lifetime of the asset until its disposal. From the manufacturer’s point of view the asset is a product. The manufacturer manages different asset types that have a history with different versions. In parallel, he produces instances of these different types and versions.

Figure6_

Figure 1 – Smart manufacturing component – I4.0-component

4.1.2    AAS metamodel overview

The AAS metamodel stipulates structural principles of the AAS in a formal manner (UML) in order to enable an exchange of information between AASs. The main parts of AAS model elements describe the represented asset as well as its submodels (see Figure 2). Optionally, dictionaries and views may be part of an AAS. A dictionary contains so-called concept descriptions. Views define a set of elements selected for a specific stakeholder, e.g. for a machine operator. An AAS represents exactly one asset.

Figure7_

Figure 2 – AAS Metamodel overview

4.2     Introduction to OPC Unified Architecture

4.2.1    What is OPC UA?

OPC UA is an open and royalty free set of standards designed as an interoperability framework. While there are numerous communication solutions available, OPC UA has key advantages:

·      A state-of-the-art security model (see OPC 10000-2).

·      Multiple fault-tolerant communication protocols.

·      An information modelling framework that allows application developers to represent their data in an object-oriented way.

OPC UA has a broad scope which offers economies of scale for application developers. This means that a larger number of high-quality applications at a reasonable cost is available. When combined with semantic models such as Asset Administration Shell, OPC UA makes it easier for end users to access data via generic commercial applications.

The OPC UA model is scalable from small devices to ERP systems. OPC UA Servers process information locally and then provide that data in a consistent format to any application requesting data -- ERP, MES, PMS, Maintenance Systems, HMI, Smartphone or a standard Browser, for example. For a more complete overview see OPC 10000-1.

4.2.2    Basics of OPC UA

As an open standard, OPC UA is based on standard internet technologies, like TCP/IP, HTTP, Web Sockets.

As an extensible standard, OPC UA provides a set of Services (see OPC 10000-4) and a basic information model framework. This framework provides an easy method for creating and exposing vendor defined information in a standard way. Moreover, OPC UA Clients are able to discover and use vendor-defined information. This means OPC UA users can benefit from the economies of scale that come with generic visualization and historian applications. This companion specification is an example of an OPC UA Information Model designed to meet the needs of a specific group of developers and users.

OPC UA Clients can be any consumer of data from another device on the network to browser based thin clients and ERP systems. The full scope of OPC UA applications is shown in Figure 3.

Figure8_

Figure 3 – The Scope of OPC UA within an Enterprise

OPC UA provides a robust and reliable communication infrastructure having mechanisms for handling lost messages, failover, heartbeat, etc. With its binary encoded data, it offers a high-performing, secure data exchange solution.

4.2.3    Information modelling in OPC UA

4.2.3.1    Concepts

OPC UA provides a framework that can be used to represent complex information as Objects in an AddressSpace which can be accessed with standard services. These Objects consist of Nodes connected by References. Different classes of Nodes convey different semantics. For example, a Variable Node represents a value that can be read or written. The Variable Node has an associated DataType that can define the type of the actual value, such as a string, float, structure etc. It can also describe the Variable value as a variant. A Method Node represents a function that can be called. Every Node has a number of Attributes including a unique identifier called NodeId and a non-localized name called BrowseName. An Object representing a ‘Reservation’ is shown in Figure 4.

Figure9_

Figure 4 – A Basic Object in an OPC UA Address Space

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 5 illustrates the relationship between an instance and its TypeDefinition.

The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 5 the PersonType ObjectType defines two children: First Name and Last Name. All instances of PersonType are expected to have the same children with the same BrowseNames. Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed to search for children based on the BrowseNames from the type instead of NodeIds. This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers implement.

OPC UA also supports the concept of subtyping. This allows a modeller to take an existing type and extend it. There are rules regarding subtyping defined in OPC 10000-3, but in general they allow the extension of a given type or the restriction of a DataType. For example, the modeller may decide that the existing ObjectType in some cases needs an additional Variable. The modeller can create a subtype of the ObjectType and add the Variable. A Client that is expecting the parent type can treat the new type as if it was of the parent type. Regarding DataTypes, subtypes can only restrict. If a Variable is defined to have a numeric value, a sub type could restrict it to a float.

 

Figure10_ 

Figure 5 – The Relationship between Type Definitions and Instances

References allow Nodes to be connected in ways that describe their relationships. All References have a ReferenceType that specifies the semantics of the relationship. References can be hierarchical or non-hierarchical. Hierarchical references are used to create the structure of Objects and Variables. Non-hierarchical are used to create arbitrary associations. Applications can define their own ReferenceType by creating subtypes of an existing ReferenceType. Subtypes inherit the semantics of the parent but may add additional restrictions. Figure 6 depicts several References, connecting different Objects.

Figure11_

Figure 6 – Examples of References between Objects

The figures above use a notation that was developed for the OPC UA specification. The notation is summarized in Figure 7. UML representations can also be used; however, the OPC UA notation is less ambiguous because there is a direct mapping from the elements in the figures to Nodes in the AddressSpace of an OPC UA Server.

Figure12_

Figure 7 – The OPC UA Information Model Notation

A complete description of the different types of Nodes and References can be found in OPC 10000-3 and the base structure is described in OPC 10000-5.

OPC UA specification defines a very wide range of functionality in its basic information model. It is not expected that all Clients or Servers support all functionality in the OPC UA specifications. OPC UA includes the concept of Profiles, which segment the functionality into testable certifiable units. This allows the definition of functional subsets (that are expected to be implemented) within a companion specification. The Profiles do not restrict functionality, but generate requirements for a minimum set of functionalities (see OPC 10000-7).

4.2.3.2    Namespaces

OPC UA allows information from many different sources to be combined into a single coherent AddressSpace. Namespaces are used to make this possible by eliminating naming and ID conflicts between information from different sources. Namespaces in OPC UA have a globally unique string called a NamespaceUri and a locally unique integer called a NamespaceIndex. The NamespaceIndex is only unique within the context of a Session between an OPC UA Client and an OPC UA Server. The Services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values.

There are two types of values in OPC UA that are qualified with Namespaces: NodeIds and QualifiedNames. NodeIds are globally unique identifiers for Nodes. This means the same Node with the same NodeId can appear in many Servers. This, in turn, means Clients can have built-in knowledge of some Nodes. OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model.

QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames; however, instances do not have that restriction.

4.2.3.3    Companion Specifications

An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes, VariableTypes, DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects as entry points into the AddressSpace.

 

5     AAS metamodel representation in the OPC UA information model

5.1     General rules for the mapping of the AAS metamodel to the OPC UA information model

This Companion Specification maps AAS information model elements from “Details of the Asset Administration Shell – Part 1” (see section 2) expressed in UML class diagrams, to OPC UA information model elements. This mapping has to be used in order to implement Industrie 4.0 conformant digital twins based on OPC UA as implementation technology.

General rules for mapping the AAS information model to OPC UA are given in the following section. In subsequent sections examples for these rules are given.

 

General Rules:

 

1.   For all class elements of the metamodel, an ObjectType with the same name + suffix “Type” + prefix “AAS” is added. Example: AASAssetType for Asset, AASSubmodelElementType for SubmodelElement and AASQualifierType for Qualifier. These Types are derived from OPC UA’s BaseObjectType. Exception: ConceptDescriptions and Referables (see below).

2.   For all types in an AAS that cannot directly be mapped to OPC UA primitive types, a data type is created with the same name + suffix “DataType” + prefix “AAS”. Example: AASKeyElementDataType for KeyElement. Exception: LangStringSet is mapped to the predefined OPC UA type 0:LocalizedText.

3.   Attributes of classes in an AAS that have a simple data type are mapped to 0:HasProperty references within the ObjectType. The BrowseName corresponds to the name in the AAS UML model but is starting with a capital letter. Example: AASAdministrativeInformationType contains a property with BrowseName Version and data type String. Exception: The name of the attribute “Kind” was extended with the prefixes “Modelling” and “Asset”.

4.   The cardinality of an association or aggregation is specified via OPC UA modelling rules. The OPC UA modelling rule “Optional” is used, if the cardinality is 0 or 1. The OPC UA modelling rule “Mandatory” is used, if the cardinality is 1. The OPC UA modelling rule “OptionalPlaceholder” is used, if the cardinality is 0, one or more than one element. The OPC UA modelling rule “MandatoryPlaceholder” is used, if the cardinality is 1 or more than 1 element.

5.   Aggregation and composition attributes of classes in AAS are mapped to 0:HasComponent References within the ObjectType. In case of cardinality 0 .. 1 or 1 the BrowseName corresponds to the name in the AAS UML model but is starting with capital letter. Example: Objects of type “AASAssetType” have a component with browse name “AssetIdentificationModel”. In case of cardinality > 1 the BrowseName corresponds to the idShort in the AAS UML model. Example: AASSubmodelType has OPC UA components with OPC UA TypeDefinition AASSubmodelElementType. A submodel element may have the idShort “MaxRotationSpeed”. Then the BrowseName of the component is “MaxRotationSpeed” as well.

6.   Since OPC UA does not support multiple inheritance abstract classes, e.g. needed for the AAS classes “Qualifiable” or “Identifiable”, these are not modelled via subtype reference in OPC UA. The corresponding attributes, aggregations and compositions are modelled as part of the inheriting class. For details see rules below.

 

Rules for SubmodelElements:

7.   Specific for the Blob SubmodelElement type (AASBlobType) the predefined OPC UA type definition FileType is used for the value. References of type FileType are components of the ObjectType. The BrowseName is not “value”, but “File”. The mime type is part of the OPC UA FileType and therefore not added. In contrast to the OPC UA FileType, the mime type is mandatory for the AAS information model.

8.   Specific for the File SubmodelElement type (AASFileType) the value attribute is mapped to an OPC UA property with BrowseName “FileReference”. Additionally, an object of type “FileType” with browse name “File” can be added similar as for the Blob. Since this is optional, the mime type is modelled as OPC UA property. In case both are present, then the mime types need to be the same.

9.   SubmodelElementCollection can be either ordered or not ordered. In case of an ordered collection “SubmodelElementCollection” is realized as AASOrderedSubmodelElementCollectionType and the relationship between collection and submodel elements is realized via the predefined OPC UA “HasOrderedComponent” reference type. Otherwise a AASSubmodelElementCollectionType is used.

10. For Operations first an AASOperationType is defined but then the OPC UA Method is used for describing the operation. The name of the method is “Operation”. Hint: The OPC UA Specification “Amendment 2: Method Metadata” allows to add meta information to individual arguments (HasArgumentDescription). This is used to realize a semanticId by using the OPC UA reference type 0:HasDictionaryEntry. For AAS references as used in ReferenceElement of RelationshipElement see rule for referencing.

11. For AAS submodel elements of type “Event”, the ObjectType “AASEventType” references an OPC UA event via the reference type “GenerateEvent”.

 

Rules for Referables and Identifiables:

 

12. For Referable and Identifiable separate OPC UA ObjectTypes are defined that are referenced from the corresponding ObjectTypes representing the concrete referables and identifiables via the OPC UA 0:HasInterface reference type. The naming convention for this is as follows: “IAAS<AAS UML class name>”. Example: IAASIdentifiableType.

13. In case of referenced referables with modelling rule “OptionalPlaceholder” or “MandatoryPlaceholder” the attribute idShort of AAS Referables is represented by the browse name of an element. Since there are cases like for AssetAdministrationShell/asset where the browse name is “Asset” but the asset has an idShort as well, idShort is modelled additionally. In cases with no predefined BrowseName The BrowseName and the idShort shall be identical.

14. DisplayName has prefix "Asset:", "AAS:", "Submodel:" and "View:" for Instances of AASAssetType, AASAssetAdministrationShellType, AASSubmodelType and AASViewType. Although DisplayName is of type LocalizedText, the prefix will not be translated.

15. The parent attribute of Referables is not explicitly modelled because OPC UA supports native navigation.

16. In case of referenced referables with modelling rule “Optional” or “Mandatory” the browse name is identical to the AAS attribute name and the display name shall be identical to the idShort.

 

 

Rules for Qualifiables:

 

17. Qualifiers of an element are modelled via the 0:HasComponent reference. Since qualifiers are not referable, they do not have a BrowseName that corresponds to an AAS attribute. Instead the name should be generated as follows: qualifier:<value of AAS:Qualifier/qualiferType>=<value of Qualifier/qualifierValue>.

 

Rules for semanticId and Concept Descriptions:

18. A concept description is inheriting from the predefined OPC UA IrdiDictionaryEntry or UriDictionaryEntry. This is why there are both ObjectTypes: “AASIrdiConceptDescriptionType” or “AASUriConceptDescriptionType” and not only one like for the other AAS classes. Additionally for “idType = Custom” a new Type “AASCustomConceptDescriptionType” is created inheriting directly from “DictionaryEntryType”.

19. Concept descriptions are added to a folder on the server side. The “Dictionaries” folder defined in OPC 10000-19 shall be the top-level folder. Below additional subfolders can be created.

20. semanticId is modelled by using the predefined OPC UA reference type HasDictionaryEntry and is either referencing an object of type “AASIrdiConceptDescriptionType” or of type “AASUriConceptDescriptionType” or of type “AASCustomConceptDescriptionType”.

21. A concept description has at least one Add-In to allow the usage of the IEC61360 data specification template (see rules for data specifications).

Rules for Data Specifications:

 

22. Concrete data specifications are inheriting from the AAS ObjectType “AASDataSpecificationType”.

23. There is no need in OPC UA to distinguish between the data specification properties and the data specification content defining the properties that shall be added to the ObjectType that uses the data specification. The AAS attributes of DataSpecification are modelled as OPC UA properties or components (rules as above) of the AASDataSpecificationType but are not instantiated. This is always the case in OPC UA if there are no modelling rules attached to a property or component.

24. The concept of embedded data specifications is used. The element that is using the data specification uses the OPC UA reference type 0:HasComponent. This Add-In uses pairs of elements: one property being the global external reference to a data specification, the other one being the data specification content.

25. For AAS references as used in ReferenceElement of RelationshipElement a new non-hierarchial Reference Type “AASReference” is introduced. For AAS, however, also global external references are possible – to elements in other AAS on other OPC UA Servers or to entities completely outside the scope of the AAS. The object with type “AASReferenceType” is holding the unique key chain to the referenced elements and optionally can reference the “real” element via “AASReference” reference. There is no special rule for the BrowseName in this case. The display name should be the same as the idShort of the referenced element.

26. The Keys of a reference are implemented in form of an array. Every single Key is serialized as described in Section 5.2.1. of Details of the Asset Administration Shell – Part 1” V2.0.

 

 

Rules for Semantics of Metamodel Elements

27. The 0:HasDictionaryEntry reference type of OPC UA is not only used to describe the semantics of objects but also of ObjectTypes. For doing so, the rules for creating identifiers as defined in Section 5.2.2 of Details of the Asset Administration Shell – Part 1” V2.0 are used.

 

5.2     Overview of AAS in the OPC UA information model

Figure 8 gives a general overview about the AAS root (left upper structure), the asset type description (left lower structure), the submodel type (right upper structure) and the submodel element types (right lower structure). The detailed specification is part of the following sections.

 

Figure13_

Legend: green – defined in OPC UA, red – type/instance relation, brown – Identification elements, black – main AAS model definitions

 

Figure 8 – Overview of the AAS OPC UA core information model

 

 

5.3     Overview of AAS types which are directly inherited from OPC UA types

Table 8 collects all AAS ObjectTypes that are directly derived from OPC UA types.

 

 

Table 8 – Basic ObjectTypes of the asset administration shell

AASiD Element

Parent OPC UA type

AASAssetAdministrationShellType

 BaseObjectType

AASAssetType

 BaseObjectType

AASSubmodelType

 BaseObjectType

AASSubmodelElementType

 BaseObjectType

AASAdministrativeInformationType

 BaseObjectType

AASReferenceType

 BaseObjectType

AASIriConceptDescriptionType

 UriDictionaryEntryType

AASIrdiConceptDescriptionType

 IrdiDictionaryEntryType

AASCostumConceptDescriptionType

 DictionaryEntryType

AASViewType

 BaseObjectType

AASQualifierType

 BaseObjectType

 

 

Table 9 collects all Asset Administration Shell ReferenceTypes which are OPC UA types.

 

 

Table 9 – Basic ReferenceTypes of the asset administration shell

AASiD Element

Parent OPC UA type

IAASReferableType

 BaseInterfaceType

AASReference

  NonHierarchicalReference

 

 

Table 10 collects all AAS data types that are directly derived from OPC UA data types.

 

Table 10 – Basic data types of the asset administration shell

AASiD Element

Parent OPC UA type

AASAssetKindDataType

 Enumeration

AASModelingKindDataType

 Enumeration

AASIdentifierTypeDataType

 Enumeration

AASEntityTypeDataType

 Enumeration

AASCategoryDataType

 Enumeration

AASDataTypeIEC61360DataType

 Enumeration

AASLevelTypeDataType

 Enumeration

AASKeyElementsDataType

 Enumeration

AASKeyTypeDataType

 Enumeration

AASValueTypeDataType

 Enumeration

AASMimeDataType

 String

AASPathDataType

 String

AASPropertyValueDataType

 String

AASQualifierDataType

 String

AASKeyDataType

 Structure

 

 

 

 

-

 

5.4     Handling of Dictionary Entries

The ObjectTypes in this specification define dictionary entries (using the HasDictionaryEntry References) in various places either directly on the ObjectType or the InstanceDeclarations. By the nature of this non-hierarchical Reference this only defines the dictionary entry for the corresponding Node. It does not require, from the OPC UA modelling concepts, that instances of the ObjectType or instances based on InstanceDeclarations have to have the same dictionary entries. However, this is the intention in this specification. Therefore, all Objects that are instance of an ObjectType defined in this specification shall have the same HasDictionaryEntry References to the same dictionary entries as the ObjectType. The same is true for the InstanceDeclarations. Instances based on InstanceDeclarations shall have References to the same dictionary entries as their InstanceDeclarations. In both cases it is allowed, that instances have additional References to other DictionaryEntries.

 

6     OPC UA ObjectTypes

6.1     General remark

The AAS metamodel contains model elements representing security aspects. These are not part of this version of the companion specification and a matter of the next revision.

6.2     AAS root ObjectTypes

 

 

Table 11 defines the root class AASAssetAdministrationShellType of the OPC UA Asset Administration Shell.

Note: For a single submodel either a <Submodel> component or a <SubmodelReference> component is created. Submodel references are used in case that the submodel is deployed on a different OPC UA Server, i.e. it is not located in the address space. Otherwise the submodel can be directly added.

Table 11AASAssetAdministrationShellType Definition

Attribute

Value

BrowseName

AASAssetAdministrationShellType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasComponent

Object

Asset

-

AASAssetType

M

0:HasComponent

Object

<Submodel>

-

AASSubmodelType

OP

0:HasComponent

Object

<SubmodelReference>

-

AASReferenceType

OP

0:HasComponent

Object

<ConceptDictionary>

-

AASConceptDictionaryType

OP

0:HasComponent

Object

<View>

-

AASViewType

OP

0:HasComponent

Object

DerivedFrom

-

AASReferenceType

O  

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/AssetAdministrationShell

 

AASIriConceptDescriptionType

 

 

The components of the AASAssetAdministrationShellType have additional references which are defined in Table 12.

Table 12AASAssetAdministrationShellType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/hasDataSpecification/dataSpecification

Asset

 

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AssetAdministrationShell/asset

<Submodel>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AssetAdministrationShell/submodels

<SubmodelReference>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AssetAdministrationShell/submodels

<ConceptDictionary>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AssetAdministrationShell/conceptDictionaries

<View>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AssetAdministrationShell/views

DerivedFrom

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AssetAdministrationShell/derivedFrom

 

 

 

6.3     AASReferenceType

For AAS references as used in ReferenceElement of RelationshipElement a new non-hierarchial ReferenceType “AASReference” is introduced (Figure 9). The OPC UA ReferenceType 0:HasComponent is not directly used to reference an element because OPC UA references can only reference elements in the same address space. For more details please see rule 24 in section 5.1.

 

Figure14_

 

Figure 9 – AASReference type

 

The details of the AASReferenceType are defined in Table 13.

Table 13AASReferenceType Definition

Attribute

Value

BrowseName

AASReferenceType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

Keys

AASKeyDataType []

0:PropertyType

M

AASReference

Object

<Referable>

-

0:BaseObjectType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Reference

 

AASIriConceptDescriptionType

 

 

The components of the AASReferenceType have additional references which are defined inTable 14.

Table 14AASReferenceType Additional References

Source Path

Reference Type

Is Forward

Target Path

Keys

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Reference/keys

 

 

The AASReference to a Referable does not have a counterpart in the metamodel of the asset administration shell. It was added to this specification to allow a direct link to an OPC Object if available that corresponds to the one specified via the keys.

 

 

Objects of the AASReferenceType can reference another referable node instance. Instances of the following ObjectTypes can be referenced:

·      AASAccessPermissionRuleType

·      AASAnnotatedRelationshipElementType

·      AASAssetAdministrationShellType

·      AASAssetType

·      0:BaseEventType

·      AASBlobType

·      AASCapabilityType

·      AASConceptDictionaryType

·      AASCustomConceptDescriptionType

·      AASFileType

·      AASEntityType

·      AASEventType

·      AASIrdiConceptDescriptionType

·      AASIriConceptDescriptionType

·      AASMultiLanguagePropertyType

·      AASOperationType

·      AASPropertyType

·      AASRangeType

·      AASReferenceElementType

·      AASRelationshipElementType

·      AASSubmodelType

·      AASSubmodelElementType

·      AASSubmodelElementCollectionType

·      AASViewType

 

6.4     Referable and Identifiable

The identification concept serves to clearly identify all AAS elements. In principle, a distinction can be made between the following partial identification concepts, which differ in their validity area (Figure 10).

• Globally unique identification, e.g. IRDI or URI - this is called "Identifiable"

• Locally unique identification (instance-related ID valid only in the inner context of an AAS) - this is called "Referable"

• semantic referencing (reference to a conceptual library (dictionary / repository))

In Figure 10 these are shown. The light blue backed rectangles are each AASs. The attributes of the AAS named in the upper section (AAS - Asset Administration Shell, Asset and Submodel) have a globally valid identifier. In addition to the identifier itself, the identifier is also given its type, which can be URI, IRDI or Custom (manufacturer-specific). The identifiers of these AAS elements are thus unique. This is necessary because it is the entry point into the AAS. If this is compared with an OPC UA Server URI, then the same applies since the validity in the namespace of the OPC UA server must also be unique.

Figure15_

Figure 10 – Identification concepts for AAS

The middle section of Figure 10 shows AAS elements that have locally unique identifiers. This allows for e.g. the same properties can be present several times and also submodels can be used again and again. The validity of this identification concept is only in its context (namespace), i.e. along the composition from the globally unique identifiers until the individual instances. An example of idShort is "MaxTemp" and for the composition in the identification: "urn: PROFIBUS: PROFIBUS-PA: V3-02: Parameter: 1: 1: MaxTemp # 0002".

With these two concepts, the identification of an AAS, i.e. the addressing is clearly possible. However, as with the example of the PROFIBUS PA profile, the name MaxTemp is unique only in this profile. In the planning documents of the plants there are also specifications for the maximum temperature, as well as in the manual of the transmitter. All three parameters correspond to the same understanding, but they are not automatically interconvertible by machine. This is where the third identification concept of AAS comes in. The lower part of Figure 10 shows the semantic references that refer to dictionaries, which are feature catalogs that store the understanding of the properties and important attributes (data type, unit of measurement, ...). From selected AAS elements e.g. submodel and property can be checked if the same thing is meant despite different naming. It is possible to specify only the semantic reference and it is expected that the user can interpret this. However, it is also possible to embed the corresponding dictionary in the AAS.

For these three identification principles, there are corresponding model elements in the AAS metamodel. It is also possible that an element e.g. a submodel has both a local identifier and a semantic reference. The reserved word "keys" encapsulates each of the attributes of the identifier. The attribute "local" allows elements to be located outside the AAS where it is identifiable. Local = "TRUE" means the identifier value "Value" refers to the same AAS, Local = "FALSE" means the identifier value "Value" refers to an external location. The “Local” variable is defined in AASKeyDataType (Table 70).

Figure 11 shows an overview about the IAASReferableType ObjectType.

Figure16_

 

Figure 11 – OPC UA mapping of the identification concept

 

For the identification concept, a mapping to the OPC UA information model is shown in (Figure 11). It can be seen that "Identifiable" is a specialization of "Referable". The identifiable identification contains not only the identifier but also the type and optionally a version and revision. The Category for the Referable Identifier are inherited. What is striking is that in OPC UA modelling at this level, the formal idShort designation is not visible. idShort is always mapped to the browsing name of an OPC UA node by the generally valid rule (see). In this way, the locally valid identification customary in OPC UA can be used.

Overall, this AAS identification concept is an extension of the OPC UA BrowseName Identification (valid in the namespace of the OPC UA Server).

 

6.4.1    IAASReferableType

Table 15 defines the AASReferable ObjectType.

 

Table 15 – IAASReferableType Definition

Attribute

Value

BrowseName

IAASReferableType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseInterfaceType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

Category

0:String

0:PropertyType

M

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Referable

 

AASIriConceptDescriptionType

 

 

The OPC UA node attribute “description” is used for the IAASReferableType instances.

 

The components of the IAASReferableType have additional references which are defined in Table 16.

Table 16 – IAASReferableType Additional References

Source Path

Reference Type

Is Forward

Target Path

Category

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Referable/category

 

 

6.4.2    IAASIdentifiableType

Table 17 defines the IAASIdentifiable ObjectType.

Table 17 – IAASIdentifiableType Definition

Attribute

Value

BrowseName

IAASIdentifiableType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the IAASReferableType defined in OPC 10000-19, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

Identification

 

AASIdentifierType

M

0:HasComponent

Object

Administration

 

AASAdministrativeInformationType

M

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Identifiable

 

AASIriConceptDescriptionType

 

 

The components of the IAASReferableType have additional references which are defined in Table 18.

Table 18 – IAASIdentifiableType Additional References

Source Path

Reference Type

Is Forward

Target Path

Identification

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Identifiable/identification

Administration

0:HasDictionaryEntry

True

 Admin-shell.io/aas/2/0/Identifiable/administration

 

 

 

6.4.3    AASAdministrativeInformationType

The AdministrativeInformationType is a subtype of the BaseObjectType. Table 19 defines the AASAdministrationInformation ObjectType.

Table 19AASAdministrativeInformationType Definition

Attribute

Value

BrowseName

AASAdministrativeInformationType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

Version

0:String

0:PropertyType

O

0:HasProperty

Variable

Revision

0:String

0:PropertyType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/AdministrativeInformation

 

AASIriConceptDescriptionType

 

 

The components of the AASAdministrativeInformationType have additional references which are defined in Table 20.

Table 20 – AASAdministrativeInformationType Additional References

Source Path

Reference Type

Is Forward

Target Path

Version

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AdministrativeInformation/version

Revision

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AdministrativeInformation/revision

 

 

6.5     AASIdentifierType

Table 21 defines the AASIdentifier ObjectType. It is used to uniquely identify an entity.

Table 21 – AASIdentifierType

Attribute

Value

BrowseName

AASIdentifierType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasProperty

Variable

Id

String

0:PropertyType

M

0:HasProperty

Variable

IdType

AASIdentifierTypeDataType

0:PropertyType

M

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Identifier

 

AASIriConceptDescriptionType

 

 

 

The components of the AASIdentifierType have additional references which are defined in Table 22.

Table 22 – AASIdentifierType Additional References

Source Path

Reference Type

Is Forward

Target Path

Id

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Identifier/id

IdType

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Identifier/idType

 

 

 

6.6     AASAssetType

Figure 12 shows an overview about the AASAsset ObjectType.

Figure17_

Figure 12 – AASAssetType graphical overview

 

The Asset Type describes meta data of an asset that is represented by an AAS. The asset has a globally unique identifier (I4AASIdentifiableType) plus – if needed – additional domain specific (proprietary) identifiers (Table 23). Optionally it can refer to a list of submodels.

Table 23 – AASAssetType Definition

Attribute

Value

BrowseName

AASAssetType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasProperty

Variable

AssetKind

AASAssetKindDataType

0:PropertyType

M

0:HasComponent

Object

AssetIdentificationModel

-

AASReferenceType

O

0:HasComponent

Object

BillOfMaterial

-

AASReferenceType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Asset

 

AASIriConceptDescriptionType

 

 

The components of the AASAssetType have additional references which are defined in Table 24.

Table 24AASAssetType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Asset/dataSpecifications

AssetKind

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Asset/assetKind

AssetIdentificationModel

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Asset/assetIdentificationModel

BillOfMaterial

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Asset/billOfMaterial

 

 

6.7     AASSubmodelType

Figure 13 shows an overview about the AASSubmodel ObjectType.

Figure18_

Figure 13 – AASSubmodelType graphical overview

A Submodel defines a specific aspect of the asset represented by the AAS and is defined in Table 25.

A submodel is used to structure the information model of an AAS representing the technical functionality of the underlying asset into distinguishable parts. Each submodel refers to a well-defined domain or subject matter. Submodels can become standardized and thus become submodel templates. Submodels can have different life-cycles.

Note: The concept of template and instance applies to properties.

 

Table 25 – AASSubmodelType Definition

Attribute

Value

BrowseName

AASSubmodelType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasProperty

Variable

ModelingKind

AASModelingKindDataType

0:PropertyType

M

0:HasComponent

Object

<Qualifier>

 

AASQualifierType

OP

0:HasComponent

Object

<SubmodelElement>

 

AASSubmodelElementType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Submodel

 

AASIriConceptDescriptionType

 

 

The default value of the variable “ModelingKind” is “Instance”.

For each AASSubmodelType instance the semanticId is mapped to the OPC UA HasDictionaryEntry reference. This is why the semanticId refers to the instance of the submodel element. This is equivalent to the DictionaryEntry which refers to the concept dictionary element which describes the individual instance not the submodel type.

The components of the AASSubmodelType have additional references which are defined in Table 26.

Table 26AASSubmodelType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Asset/dataSpecifications

ModelingKind

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/HasKind/kind

<Qualifier>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Submodel/qualifiers

<SubmodelElement>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Submodel/submodelElements

 

6.8     SubmodelElementType specialization

To meet the range of aspects of the assets which have to be described in the AAS a set of submodel element types are defined. Each submodel element type represents one of these aspects. Figure 14 provides a general overview.

Figure19_

Figure 14 – SubmodelElement Subtypes

 

6.8.1    AASSubmodelElementType common attributes

Figure 15 shows an overview about the AASSubmodelElement ObjectType.

 

Figure20_

Figure 15 – AASSubmodelElementType graphical overview

 

A data element is a submodel element that is not further composed of other submodel elements (Table 27). A data element is a submodel element that has a value. The type of value may differ for different data elements.

Table 27 – AASSubmodelElementType Definition

Attribute

Value

BrowseName

AASSubmodelElementType

IsAbstract

True

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasInterface

ObjectType

IAASReferableType

 

-

-

0:HasProperty

Variable

ModelingKind

AASModelingKindDataType

0:PropertyType

M

0:HasComponent

Object

<Qualifier>

 

AASQualifierType

OP

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasDictionaryEntry

Object

<IRDI_or_IRI_or_Custom_concept_description_entry>

 

AASIriConceptDescriptionType

 

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/SubmodelElement

 

AASIriConceptDescriptionType

 

Applied from IAASReferableType

0:HasProperty

Variable

Category

0:String

0:PropertyType

M

 

The default value of the variable “ModelingKind” is “Instance”.

For each AASSubmodelElementType instance the semanticId is mapped to the OPC UA HasDictionaryEntry. This is at instance level because the DictionaryEntry refers to the concept dictionary element, which describes the individual instance and not the submodel element type.

The components of the AASSubmodelElementType have additional references which are defined in Table 28.

Table 28AASSubmodelElementType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/hasDataSpecification/dataSpecification

ModelingKind

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/SubmodelElement/kind

<Qualifier>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/SubmodelElement/qualifiers

 

6.8.2    AASSubmodelElementCollectionType

Figure 16 shows an overview about the AASSubmodelElementCollection ObjectType.

 

Figure21_

Figure 16 – AASSubmodelElementCollectionType graphical overview

 

A submodel element collection is a set or list of submodel elements. The AASSubmodelElementCollectionType is defined in Table 29

 

Table 29 – AASSubmodelElementCollectionType Definition

Attribute

Value

BrowseName

AASSubmodelElementCollectionType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<SubmodelElement>

 

AASSubmodelElementType

OP

0:HasProperty

Variable

AllowDuplicates

0:Boolean

0:PropertyType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/SubmodelElementCollection

 

AASIriConceptDescriptionType

 

 

The components of the AASSubmodelElementCollectionType have additional references which are defined in Table 30.

Table 30AASSubmodelElementCollectionType Additional References

Source Path

Reference Type

Is Forward

Target Path

<SubmodelElement>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/SubmodelElementCollection/values

AllowDuplicates

0:HasDictionaryEntry

True

 Admin-shell.io/aas/2/0/SubmodelElementCollection/allowDuplicates

The value elements in this collection are not ordered (i.e. http://Admin-shell.io/aas/2/0/ SubmodelElementCollection/ordered == False).

 

6.8.3    AASOrderedSubmodelElementCollectionType

Figure 17 shows an overview about the AASOrderedSubmodelElementCollection ObjectType.

 

Figure22_

 

Figure 17 – AASOrderedSubmodelElementCollectionType graphical overview

 

Table 31 defines the AASOrderedSubmodelElementCollection ObjectType.

Table 31 – AASOrderedSubmodelElementCollectionType Definition

Attribute

Value

BrowseName

AASOrderedSubmodelElementCollectionType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementCollectionType defined in Table 29 and Table 30 i.e. inheriting the InstanceDeclarations of that Node.

0:HasOrderedComponent

Object

<SubmodelElement>

 

AASSubmodelElementType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/SubmodelElementCollection

 

AASIriConceptDescriptionType

 

 

The components of the AASOrderedSubmodelElementCollectionType have additional references which are defined in Table 32.

Table 32AASOrderedSubmodelElementCollectionType Additional References

Source Path

Reference Type

Is Forward

Target Path

<SubmodelElement>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/SubmodelElementCollection/values

 

 

 

 

The value elements in this collection are ordered (i.e. http://Admin-shell.io/aas/2/0/ SubmodelElementCollection/ordered == True).

 

6.8.4    AASMultiLanguagePropertyType

Figure 18 shows an overview about the AASMultiLanguageProperty ObjectType

Figure23_

Figure 18 – AASMultiLanguagePropertyType graphical overview

 

This submodel element type is used for properties with a value that can be provided in multiple languages (see Table 33).

 

Table 33 – AASMultiLanguagePropertyType Definition

Attribute

Value

BrowseName

AASMultiLanguagePropertyType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node

0:HasComponent

Object

ValueId

 

AASReferenceType

O

0:HasProperty

Variable

Value

0:LocalizedText[]

0:PropertyType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/MultiLanguageProperty

 

AASIriConceptDescriptionType

 

 

The components of the AASMultiLanguagePropertyType have additional references which are defined in Table 34.

Table 34AASMultiLanguagePropertyType Additional References

Source Path

Reference Type

Is Forward

Target Path

ValueId

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/MultiLanguageProperty/valueId

Value

0:HasDictionaryEntry

True

 Admin-shell.io/aas/2/0/MultiLanguageProperty/value

 

 

6.8.5    AASPropertyType

Figure 19 shows an overview about the AASProperty ObjectType.

Figure24_

Figure 19 – AASPropertyType graphical overview

 

The valueId attribute references a DictionaryEntry. Table 35 defines the AASProperty ObjectType.

 

Table 35AASPropertyType Definition

Attribute

Value

BrowseName

AASPropertyType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

Value

0:BaseDataType

0:PropertyType

O

0:HasProperty

Variable

ValueType

AASValueTypeDataType

0:PropertyType

M

0:HasComponent

Object

ValueId

-

AASReferenceType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Property

 

AASIriConceptDescriptionType

 

 

The components of the AASPropertyType have additional references which are defined in Table 36.

Table 36AASPropertyType Additional References

Source Path

Reference Type

Is Forward

Target Path

Value

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Property/value

ValueType

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Property/valueType

ValueId

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Property/valueId

 

6.8.6    AASCapabilityType

Table 37 defines the AASCapability ObjectType.

Table 37 – AASCapabilityType Definition

Attribute

Value

BrowseName

AASCapabilityType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Property

 

AASIriConceptDescriptionType

 

 

 

6.8.7    AASOperationType

Figure 20 shows an overview about the AASOperation ObjectType.

Figure25_

Figure 20 – AASOperationType graphical overview

 

AASOperationType is defined in Table 38. It encapsulates the standard OPC UA Method “Operation”. All rules for the OPC UA Method NodeClass declaration apply. “Operation” is defined without Arguments but with the OptionalPlaceholder ModellingRule. As defined in OPC 10000-3, this rule allows the inclusion of Arguments to this Method on sub-types or on instances.

 

Table 38 – AASOperationType Definition

Attribute

Value

BrowseName

AASOperationType

IsAbstract

False

References

Node
Class

BrowseName

Data

Type

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Method

Operation

 

 

MP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Operation

 

AASIriConceptDescriptionType

 

 

 

An example of a method definition is:

 

Signature

 

Method_xy_name (

          [InputArgument]

0:PropertyType                  BrowseNameA

0:PropertyType                  BrowseNameB

                   …

 

          [OutputArgument]

0:PropertyType                  BrowseNameK

0:PropertyType                  BrowseNameL

                   …

)

 

 

Each individual element of the InputArgument and OutputArgument has to be referenced by a 0:HasDictionaryEntry to its semantic definition.

 

 

6.8.8    AASBlobType

Figure 21 shows an overview about the AASBlob ObjectType.

 

Figure26_

Figure 21 – AASBlobType graphical overview

 

Table 39 defines the AASBlob ObjectType.

Table 39AASBlobType Definition

Attribute

Value

BrowseName

AASBlobType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

File

 

0:FileType

M

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Blob

 

AASIriConceptDescriptionType

 

 

The components of the AASBlobType have additional references which are defined in Table 40.

Table 40AASBlobType Additional References

Source Path

Reference Type

Is Forward

Target Path

File

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Blob/value

 

 

6.8.9    AASFileType

Figure 22 shows an overview about the AASFile ObjectType.

Figure27_

Figure 22 – AASFileType graphical overview

Table 41 defines the AASFile ObjectType.

Table 41AASFileType Definition

Attribute

Value

BrowseName

AASFileType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

Value

0:String

0:PropertyType

M

0:HasProperty

Variable

MimeType

AASMimeDataType

0:PropertyType

M

0:HasComponent

Object

File

 

0:FileType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/File

 

AASIriConceptDescriptionType

 

 

The components of the AASFileType have additional references which are defined in Table 42.

Table 42AASFileType Additional References

Source Path

Reference Type

Is Forward

Target Path

File

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/File/value

MimeType

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/File/mimeType

 

The additional reference to the real file of type 0:FileType is optional and not specified as such in the asset administration shell metamodel.

 

6.8.10  AASRelationshipElementType

Figure 23 shows an overview about the AASRelationElement ObjectType.

Figure28_

Figure 23 – AASRelationElementType graphical overview

 

A relationship element is used to define a relationship between two referable elements (Table 43).

Table 43AASRelationshipElementType Definition

Attribute

Value

BrowseName

AASRelationshipElementType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

First

 

AASReferenceType

M

0:HasComponent

Object

Second

 

AASReferenceType

M

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/RelationshipElement

 

AASIriConceptDescriptionType

 

 

Objects which have the AASReferenceType shall reference another type. According to Table 43 these are the following references:

 

·      the “First” node shall reference the Referable Type instance having the role of the subject

·      the “Second” node shall reference the Referable Type instance having the role of the object

 

The components of the AASRelationshipType have additional references defined in Table 44.

Table 44AASRelationshipElementType Additional References

Source Path

Reference Type

Is Forward

Target Path

First

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/RelationshipElement/first

Second

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/RelationshipElement/second

 

Table 45 defines the AASAnnotatedRelationshipElement ObjectType.

Table 45AASAnnotatedRelationshipElementType Definition

Attribute

Value

BrowseName

AASAnnotatedRelationshipElementType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASRelationshipElementType defined in Table 45, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<DataElement>

 

AASSubmodelElementType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/AnnotatedRelationshipElement

 

AASIriConceptDescriptionType

 

 

The components of the AASAnnotatedRelationshipElementType have additional references which are defined in Table 46.

Table 46AASAnnotatedRelationshipElementType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataElement>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/AnnotatedRelationshipElement/annotations

 

 

The following SubmodelElement objects are allowed for AASAnnotatedRelationshipElementType:

·      AASProperty

·      AASMultiLanguageProperty

·      AASRangeType

·      AASReferenceElementType

·      AASFileType

·      AASBlobType

 

 

 

6.8.11  AASReferenceElementType

Figure 24 shows an overview about the AASReferenceElement ObjectType.

Figure29_

Figure30_

Figure 24 – AASReferenceElementType graphical overview

 

An AASReferenceElement has a Reference as value (Table 47). This reference has an aggregation of keys (see Table 47) which represents a key chain. The resolved key chain points to an element.

 

Table 47 – AASReferenceElementType Definition

Attribute

Value

BrowseName

AASReferenceElementType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

Value

 

AASReferenceType

M

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/ReferenceElement

 

AASIriConceptDescriptionType

 

 

The Object which has the AASReferenceType shall reference another type. According to Table 47 the “Value” can contain the allowed subtypes of AASSubmodelElementTypes as defined in chapter 6.3.

 

The components of the AASReferenceElementType have additional references which are defined in Table 48.

Table 48AASReferenceElementType Additional References

Source Path

Reference Type

Is Forward

Target Path

Value

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/ReferenceElement/value

 

 

6.8.12  AASEventType

Figure 25 shows an overview about the AASEvent ObjectType.

 

 

Figure31_

Figure 25 – AASEventType graphical overview

 

Table 49 defines the AASEvent ObjectType.

Table 49 – AASEventType Definition

Attribute

Value

BrowseName

AASEventType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

The attribute “observed” of the BasicEvent submodel element in the AAS metamodel is mapped to the OPC UA eventing mechanism using GeneratesEvent-references pointing from instances of this AASEventType to ObjectTypeNodes of type BaseEventType or its customized subclasses.

 

 

6.8.13  AASEntityType

Figure 26 shows an overview about the AASEntity ObjectType.

Figure32_

Figure 26 – AASEntityType graphical overview

 

Table 50 defines the AASEntity ObjectType.

Table 50 – AASEntityType Definition

Attribute

Value

BrowseName

AASEntityType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<SubmodelElement>

-

AASSubmodelElementType

OP

0:HasProperty

Variable

EntityType

AASEntityTypeDataType

0:PropertyType

M

0:HasComponent

Object

Asset

-

AASReferenceType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Entity

 

AASIriConceptDescriptionType

 

 

The components of the AASEntityType have additional references which are defined in Table 51.

Table 51AASEntityType Additional References

Source Path

Reference Type

Is Forward

Target Path

<SubmodelElement>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Entity/statements

EntityType

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Entity/entityType

Asset

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Entity/asset

 

 

6.8.14  AASRangeType

If Min missing then negative open range infinitely, if max missing the open range infinitely.

 

Table 52AASRangeType Definition

Attribute

Value

BrowseName

AASRangeType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASSubmodelElementType defined 6.8.1, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

ValueType

AASValueTypeDataType

0:PropertyType

M

0:HasProperty

Variable

Min

0:BaseDataType

0:PropertyType

O

0:HasProperty

Variable

Max

0:BaseDataType

0:PropertyType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Range

 

AASIriConceptDescriptionType

 

 

Only simple data type of the OPC UA specification are allowed.

The components of the AASRangeType have additional references which are defined in Table 53.

Table 53AASRangeType Additional References

Source Path

Reference Type

Is Forward

Target Path

ValueType

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Range/valueType

Min

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Range/min

Max

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Range/max

 

 

 

6.9     Concept description

The AAS can define its own dictionary that contains semantic definitions of its submodel elements. These semantic definitions are called concept descriptions (ConceptDescription). It is optional whether an AAS defines its own concept dictionary (ConceptDescription) or not.

A concept description is inheriting from the predefined OPC UA IrdiDictionaryEntry or UriDictionaryEntry (Figure 27). This is why there are both ObjectTypes: “AASIrdiConceptDescriptionType” or “AASIriConceptDescriptionType” and not only one like for the other AAS classes. Additionally, for user specific dictionaries the “AASCustomConceptDescriptionType” is derived from the general OPC UA DictionaryEntryType. The semanticId is modelled by using the predefined OPC UA ReferenceType HasDictionaryEntry and is either referencing an object of type “AASIrdiConceptDescriptionType” and of type “AASUriConceptDescriptionType” or “AASCustomConceptDescriptionType”. Additionally, a concept description has at least one Add-In to allow the usage of the IEC61360 data specification template (see rules for data specifications in section 5.1 and section 6.10).

The ConceptDescription types are located under the standard OPC UA folder Dictionaries.

 

Figure33_

Figure 27 – Concept description and data specification OPC UA graphical model

 

6.9.1    AASIrdiConceptDescriptionType

Table 54 defines the AASIrdiConceptDescription ObjectType.

Table 54 – AASIrdiConceptDescriptionType Definition

Attribute

Value

BrowseName

AASIrdiConceptDescriptionType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the IrdiDictionaryEntryType defined in OPC 10000-19, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasComponent

Object

<ConceptDescription>

 

AASReferenceType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/ConceptDescription

 

AASIriConceptDescriptionType

 

 

The components of the AASIrdiConceptDescriptionType have additional references which are defined in Table 55.

Table 55AASIrdiConceptDescriptionType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/hasDataSpecification/dataSpecification

<ConceptDescription>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/ConceptDescription/IsCaseOf

 

6.9.2    AASIriConceptDescriptionType

 

Table 56 defines the AASIriConceptDescription ObjectType.

Table 56 – AASIriConceptDescriptionType Definition

Attribute

Value

BrowseName

AASIriConceptDescriptionType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the UriDictionaryEntryType defined in OPC 10000-19, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasComponent

Object

<ConceptDescription>

 

AASReferenceType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/ConceptDescription

 

AASIriConceptDescriptionType

 

 

The components of the AASIriConceptDescriptionType have additional references which are defined in Table 57.

Table 57AASIriConceptDescriptionType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/hasDataSpecification/dataSpecification

<ConceptDescription>

0:HasDictionaryEntry

True

 Admin-shell.io/aas/2/0/ConceptDescription/IsCaseOf

 

 

6.9.3    AASCustomConceptDescriptionType

Table 58 defines the AASCustomConceptDescription ObjectType.

Table 58 – AASCustomConceptDescriptionType Definition

Attribute

Value

BrowseName

AASCustomConceptDescriptionType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the DictionaryEntryType defined in OPC 10000-19, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasComponent

Object

<ConceptDescription>

 

AASReferenceType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/ConceptDescription

 

AASIriConceptDescriptionType

 

 

The components of the AASCustomConceptDescriptionType have additional references which are defined in Table 59.

Table 59AASCustomConceptDescriptionType Additional References

Source Path

Reference Type

Is Forward

Target Path

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/hasDataSpecification/dataSpecification

<ConceptDescription>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/ConceptDescription/IsCaseOf

 

 

6.10   AAS Data Specification Templates

6.10.1  AASDataSpecificationType

Concrete data specifications are inheriting from the AAS ObjectType “AASDataSpecificationType”. The AAS attributes of DataSpecification are modelled as properties of the AASDataSpecificationType but are not instantiated. This is always the case in OPC UA if there are no modelling rules attached to a property (Table 60).

The concept of embedded data specifications is used. The element that is using the data specification uses the OPC ReferenceType “HasComponent”. This Add-In uses pairs of elements: one property being the global external reference to a data specification, the other one the data specification.

Table 60 – AASDataSpecificationType Definition

Attribute

Value

BrowseName

AASDataSpecificationType

IsAbstract

True

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasInterface

ObjectType

IAASIdentifiableType

-

-

-

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/DataSpecification

 

AASIriConceptDescriptionType

 

 

6.10.2  AASDataSpecificationIEC61360Type

Figure 28 shows an overview about the AASDataSpecificationIEC61360 ObjectType.

 

Figure34_

Figure 28 – AASDataSpecificationIEC61360Type graphical overview

Table 61 defines the AASDataSpecificationIEC61360 ObjectType.

Table 61 – AASDataSpecificationIEC61360Type Definition

Attribute

Value

BrowseName

AASDataSpecificationIEC61360Type

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the AASDataSpecificationType defined in Table 60, i.e. inheriting the InstanceDeclarations of that Node.

0:HasProperty

Variable

0:DefaultInstanceBrowseName

String

0:PropertyType

 M

0:HasProperty

Variable

Category

AASCategoryDataType

0:PropertyType

O

0:HasComponent

Object

Identification

 

AASIdentifierType

M

0:HasComponent

Object

Administration

 

AASAdministrativeInformationType

M

0:HasProperty

Variable

DataType

AASDataTypeIEC61360DataType

0:PropertyType

O

0:HasProperty

Variable

Definition

0:LocalizedText

0:PropertyType

O

0:HasProperty

Variable

PreferredName

0:LocalizedText

0:PropertyType

M

0:HasProperty

Variable

ShortName

0:LocalizedText

0:PropertyType

O

0:HasProperty

Variable

SourceOfDefinition

0:String

0:PropertyType

O

0:HasProperty

Variable

Symbol

0:String

0:PropertyType

O

0:HasProperty

Variable

Unit

0:String

0:PropertyType

O

0:HasComponent

Object

UnitId

 

AASReferenceType

O

0:HasProperty

Variable

ValueFormat

0:String

0:PropertyType

O

0:HasComponent

Object

ValueList

 

ValueListType

O

0:HasProperty

Variable

Value

0:BaseDataType

0:PropertyType

O

0:HasComponent

Object

ValueId

-

AASReferenceType

O

0:HasProperty

Variable

LevelType

AASLevelTypeDataType

 

O

0:HasDictionaryEntry

Object

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0

 

AASIriConceptDescriptionType

 

 

 

6.10.3  AASDataSpecificationType

The components of the AASDataSpecificationType have additional references which are defined in Table 62.

Table 62 – AASDataSpecificationIEC61360Type Additional References

Source Path

Reference Type

Is Forward

Target Path

Category

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecification/category

Identification

0:HasDictionaryEntry

True

 Admin-shell.io/DataSpecification/identification

Administration

0:HasDictionaryEntry

True

 Admin-shell.io/DataSpecification/administration

DataType

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/dataType

Definition

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/definition

PreferredName

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/preferredName

ShortName

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/shortName

SourceOfDefinition

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/sourceOfDefinition

Symbol

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/symbol

Unit

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/unit

UnitId

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/unitId

ValueFormat

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/valueFormat

ValueList

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0/valueList

Value

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/value

ValueId

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/valueId

LevelType

0:HasDictionaryEntry

True

Admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0//DataSpecificationIEC61360/levelType

 

 

6.11   AAS Qualifiers

6.11.1  AASQualifierType 

Figure 29 shows an overview about the AASQualifier ObjectType.

Figure35_

Figure 29 – Structure of the object AASQualifierType

 

Table 63 defines the AASQualifier ObjectType.

Table 63 – AASQualifierType Definition

Attribute

Value

BrowseName

AASQualifierType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasProperty

Variable

Type

0:String

0:PropertyType

M

0:HasProperty

Variable

ValueType

AASValueTypeDataType

0:PropertyType

M

0:HasProperty

Variable

Value

0:BaseDataType

0:PropertyType

O

0:HasComponent

Object

ValueId

 

AASReferenceType

O

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/Qualifier

 

AASIriConceptDescriptionType

 

 

*Note: Constraint AASd-006: if both, the value and the valueId are present then the value needs to be identical to the value of the referenced

coded value in Qualifier/valueId.

 

The components of the AASQualifierType have additional references which are defined in Table 64.

Table 64AASQualifierType Additional References

Source Path

Reference Type

Is Forward

Target Path

Type

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Qualifier/type

ValueType

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Qualifier/valueType

Value

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/Qualifier/value

 

6.11.2  AASQualifier usage

The HasDictionaryEntity of Table 63 is denoted by the complete qualifier. The ValueId of Table 63 is referencing the individual value instantiated in the Value of the AASQualifier instance. There are multiple qualifier value depending on the application domain and the application case. While the semanticId of the qualifier is fixed the semanticId of the ValueId is instance dependent. A JSON example is shown below. The “semanticId” references the AASQualifier instance itself. The "DinSpec29000QualifierType" ValueId Keys value references the “required” value semantic coming from the DIN-SEC 29000.

 

Note: the IRI for defining the unique semantic ids of the qualifier and its values are only examples.

 

 

"qualifiers": [

        {

          "semanticId": {

            "keys": [

              {

                "type": "GlobalReference",

                "local": false,

                "value": "http://DINSPEC/29000/PropertyValueStatement/ExpressionSemantic",

                "index": 0,

                "idType": "IRI"

              }

            ]

          },

          "type": "ExpressionSemantic",

          "value": "REQUIREMENT_0",

          "valueId": {

            "keys": [

              {

                "type": "GlobalReference",

                "local": false,

                "value": " http://DINSPEC/29000/PropertyValueStatement/ExpressionSemantic/Requirement",

                "index": 0,

                "idType": "IRI"

              }

            ]

          },

 

 

6.12    AASViewType

Table 65 defines the AASView ObjectType.

Table 65 – AASViewType Definition

Attribute

Value

BrowseName

AASViewType

IsAbstract

False

References

Node
Class

BrowseName

DataType

TypeDefinition

Others

Subtype of the FolderType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node.

0:HasComponent

Object

<Referable>

 

AASReferenceType

OP

0:HasComponent

Object

<DataSpecification>

 

AASReferenceType

OP

0:HasDictionaryEntry

Object

Admin-shell.io/aas/2/0/View

 

AASIriConceptDescriptionType

 

 

 

For each AASViewType instance the semanticId is mapped to the OPC UA DictionaryEntryType. This is at instance level because the DictionaryEntry refers to the concept dictionary element which describes the individual instance not the AASView type.

 

The components of the AASViewType have additional references which are defined in Table 66.

Table 66 – AASViewType Additional References

SourceBrowsePath

Reference Type

Is Forward

Target Path

<Referable>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/View/containedElements

<DataSpecification>

0:HasDictionaryEntry

True

Admin-shell.io/aas/2/0/View/dataSpecifications

 

 

7     OPC UA DataTypes

Figure 30 shows the AAS data types which are directly derived from OPC UA data types enumeration and string. The details are defined in the following sub-sections of this chapter.

 

Figure36_

Figure 30 – Primitive AAS data types

 

7.1     AASIdentifierTypeDataType enum value definition

Table 67 defines the AASIdentifierType data type.

Table 67 – AASIdentifierTypeDataType Definition

Name

Value

Description

IRDI

0

IRDI according to ISO29002-5 as an Identifier scheme for properties and classifications

IRI

1

Internationalized Resource Identifier according to RFC3305

Custom

2

Custom identifiers like GUIDs (globally unique Identifiers)

 

7.2     AASModelingKindDataType

Table 68 defines the AASModelingKindDataType data type.

Table 68 – AASModelingKindDataType enum value Definition

Name

Value

Description

Template

0

Hardware or software element which specifies the common attributes shared by all instances of the type

[SOURCE: IEC TR 62390:2005-01, 3.1.25]

Instance

1

Concrete, clearly identifiable component of a certain template.

 

Note: It becomes an individual entity of a template, for example a device model, by defining specific property values.

Note: In an object oriented view, an instance denotes an object of a template (class).

 

[SOURCE: IEC 62890:2016, 3.1.16 65/617/CDV] modified

 

7.3     AASAssetKindDataType

Table 69 defines the AASAssetKindDataType data type.

Table 69 – AASAssetKindDataType enum value Definition

Name

Value

Description

Type

0

Hardware or software element which specifies the common attributes shared by all instances of the type

[SOURCE: IEC TR 62390:2005-01, 3.1.25]

Instance

1

Concrete, clearly identifiable component of a certain type

 

Note: It becomes an individual entity of a type, for example a device, by defining specific property values.

Note: In an object-oriented view, an instance denotes an object of a class (of a type).

 

[SOURCE: IEC 62890:2016, 3.1.16 65/617/CDV]

 

7.4     AASKey data types

The AAS metamodel knows different ways of referencing which have to be specified in the “Keys” variable used in the AASReferenceType (6.3). The “Keys” Variable is of the data type AASKeyDataType which is a structure defined in Table 70. It indicates to which type of AAS element it is referring to (AASKeyElementDataType - Table 71), if the reference refers to a local or remote element (Local), the type of the identifier of the referred element and the identifier value. The IdType is of data type AASKeyTypeDataType (Table 72).

 

 

7.4.1    AASKeyDataType

The AASKeyDataType is defined in Table 70.

Table 70 – AASKeyDataType

 

Name

Type

Description

AASKeyDataType

Structure

This structure represents an AAS key.

   Type

AASKeyElementsDataType

Type of element which is referenced

   Local

Boolean

Indicates if target of reference is within own AAS (=true) or outside (=false)

   Value

String

Key to identify the target of reference

   IdType

AASKeyTypeDataType

Kind of identifier (Value)

 

7.4.2    AASKeyElementsDataType

The AASKeyElementsDataType is defined in Table 71.

Table 71 – AASKeyElementsDataType enum value Definition[2]

Name

Value

Description

AccessPermissionRule

0

"AccessPermissionRule"

AnnotatedRelationshipElement

1

“AnnotatedRelationshipElement”

Asset

2

"Asset"

AssetAdministrationShell

3

"AssetAdministrationShell"

Blob

4

"Blob"

Capability

5

“Capability”

ConceptDescription

6

"ConceptDescription"

ConceptDictionary

7

"ConceptDictionary"

DataElement

8

"DataElement"

Entity

9

“Entity”

Event

10

"Event"

File

11

"File"

FragmentReference

12

“FragmentReference”

GlobalReference

13

"GlobalReference"

MultiLanguageProperty

14

“MultiLanguageProperty”

Operation

15

"Operation"

Property

16

"Property"

Range

17

“Range”

ReferenceElement

18

"ReferenceElement"

RelationshipElement

19

"RelationshipElement"

Submodel

20

"Submodel"

SubmodelElement

21

"SubmodelElement"

SubmodelElementCollection

22

"SubmodelElementCollection"

View

23

"View"

 

7.5     AASKeyTypeDataType

The AASKeyTypeDataType is defined in Table 72.

Table 72 – AASKeyTypeDataType

 

Name

Value

Description

IdShort

0

Identification of the element itself. Provides a unique identification for a possible event flow scheduling.

FragmentId

1

Identifier of a fragment within a file

Custom

2

Identifier is customer specific

IRDI

3

International Registration Data Identifier) is based on the international standards ISO/IEC 11179-6, ISO 29002 and ISO 6532

IRI

4

Internationalized Resource Identifier (IRI) is the international format of Uniform Resource Identifier (URI). It is defined in RFC 3987.

 

7.6     AASCategoryDataType

The CategoryDataType is defined in Table 73.

Table 73 – AASCategoryDataType enum Definition

Name

Value

Description

CONSTANT

0

Values does not change over time

PARAMETER

1

Typically once value is set, it will not change over time

VARIABLE

2

Value is calculated or changed during runtime

RELATIONSHIP

3

Relationship

 

 

 

7.7     AASValueTypeDataType

The AASValueTypeDataType is defined in Table 74.

Table 74 – AASValueTypeDataType enum Definition

Name

Value

Description

Boolean

0

A two-state logical value (true or false).

SByte

1

An integer value between -128 and 127.

Byte

2

An integer value between 0 and 255.

Int16

3

An integer value between -32 768 and 32 767.

UInt16

4

An integer value between 0 and 65 535.

Int32

5

An integer value between -2 147 483 648 and 2 147 483 647.

UInt32

6

An integer value between 0 and 4 294 967 295.

Int64

7

An integer value between -9 223 372 036 854 775 808 and 9 223 372 036 854 775 807.

UInt64

8

An integer value between 0 and 18 446 744 073 709 551 615.

Float

9

An IEEE single precision (32 bit) floating point value.

Double

10

An IEEE double precision (64 bit) floating point value.

String

11

A sequence of Unicode characters. Strings are just an array of UA_Byte.

DateTime

12

An instance in time. A DateTime value is encoded as a 64-bit signed integer which represents the number of 100 nanosecond intervals since January 1, 1601 (UTC).

ByteString

13

A sequence of octets.

LocalizedText

14

Human readable text with an optional locale identifier.

UtcTime

15

A date/time value specified in Universal Coordinated Time (UTC).

 

7.8     AASPathDataType

The AASPath data type is a sub type of string and defined in Table 75.

Table 75 – AASPathDataType Definition

Attribute

Value

BrowseName

AASPathDataType                                                                     

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of String Type defined in OPC 10000-3

 

7.9     AASMimeDataType

The enumeration of the AASMime is defined in Table 76.

Table 76 – AASMimeDataType Definition

Attribute

Value

BrowseName

AASMimeDataType                                                                   

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of String Type defined in OPC 10000-3

 

7.10   AASEntityTypeDataType

The AASEntityTypeDataType is defined in Table 77.

Table 77 – AASEntityTypeDataType Definition

Attribute

Value

BrowseName

AASEntityTypeDataType                                                           

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of Enumeration data type defined in OPC 10000-3

0:HasProperty

Variable

0:EnumValues

0:EnumValueType[]

0:PropertyType

 

 

 

The enumeration of the AASEntityType is defined in Table 78.

Table 78 – AASEntityTypeDataType Definition

Name

Value

Description

CoManagedEntity

0

Self-Managed Entities have their own AAS. This is why a reference to this asset is specified as well (Entity/asset). Additionally, further property statements (compare to [15]) can be added to the asset that are not specified in the AAS of the asset itself because they are specified in relation to the composite I4.0 Component only.

SelfManagedEntity

1

For co-managed entities there is no separate AAS. The relationships and property statements of such entities are managed within the AAS of the composite I4.0 Component.

 

7.11   AASDataTypeIEC61360DataType

The AASDataTypeIEC61360DataType is defined in Table 79.

Table 79 – AASDataTypeIEC61360DataType Definition

Attribute

Value

BrowseName

AASDataTypeIEC61360DataType                                             

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of Enumeration data type defined in OPC 10000-3

0:HasProperty

Variable

0:EnumStrings

0:LocalizedText []

0:PropertyType

 

 

The enumeration of the AASDataTypeIEC61360 is defined in Table 80.

Table 80 – AASDataTypeIEC61360DataType Definition

Name

Value

Description

BOOLEAN

0

Date type according to IEC61360

DATE

1

Date type according to IEC61360

RATIONAL

2

Date type according to IEC61360

RATIONAL_MEASURE

3

Date type according to IEC61360

REAL_COUNT

4

Date type according to IEC61360

REAL_CURRENCY

5

Date type according to IEC61360

REAL_MEASURE

6

Date type according to IEC61360

STRING

7

Date type according to IEC61360

STRING_TRANSLATABLE

8

Date type according to IEC61360

TIME

9

Date type according to IEC61360

TIME_STAMP

10

Date type according to IEC61360

URL

11

Date type according to IEC61360

INTEGER

12

Date type according to IEC61360

INTEGER_COUNT

13

Date type according to IEC61360

INTEGER_CURRENCY

14

Date type according to IEC61360

 

7.12    AASLevelTypeDataType

The AASLevelTypeDataType is defined in Table 81.

Table 81 – AASLevelTypeDataType Definition

Attribute

Value

BrowseName

AASLevelTypeDataType                                                            

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Subtype of Enumeration data type defined in OPC 10000-3

0:HasProperty

Variable

0:EnumValues

0:EnumValueType[]

0:PropertyType