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.

6.8.1 AASSubmodelElementType common attributes

Figure 15 shows an overview about the AASSubmodelElement ObjectType.

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.

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.

6.8.2 AASSubmodelElementCollectionType

Figure 16 shows an overview about the AASSubmodelElementCollection ObjectType.

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

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

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.

Table 31 defines the AASOrderedSubmodelElementCollection ObjectType.

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

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

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

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

6.8.5 AASPropertyType

Figure 19 shows an overview about the AASProperty ObjectType.

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

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

6.8.6 AASCapabilityType

Table 37 defines the AASCapability ObjectType.

6.8.7 AASOperationType

Figure 20 shows an overview about the AASOperation ObjectType.

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.

An example of a method definition is:

Signature

Method_xy_name (

)

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.

Table 39 defines the AASBlob ObjectType.

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

6.8.9 AASFileType

Figure 22 shows an overview about the AASFile ObjectType.

Table 41 defines the AASFile ObjectType.

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

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.

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

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 45 defines the AASAnnotatedRelationshipElement ObjectType.

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

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.

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.

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.

6.8.12 AASEventType

Figure 25 shows an overview about the AASEvent ObjectType.

Table 49 defines the AASEvent ObjectType.

6.8.13 AASEntityType

Figure 26 shows an overview about the AASEntity ObjectType.

Table 50 defines the AASEntity ObjectType.

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

6.8.14 AASRangeType

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

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.