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.
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 11 – AASAssetAdministrationShellType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASAssetAdministrationShellType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 12 – AASAssetAdministrationShellType 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 |
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.
The details of the AASReferenceType are defined in Table 13.
Table 13 – AASReferenceType Definition
|
Attribute |
Value |
||||
|
BrowseName |
AASReferenceType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
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 14 – AASReferenceType 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
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.
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.
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).
Table 15 defines the AASReferable ObjectType.
Table 15 – IAASReferableType Definition
|
Attribute |
Value |
||||
|
BrowseName |
IAASReferableType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
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 |
Table 17 defines the IAASIdentifiable ObjectType.
Table 17 – IAASIdentifiableType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
IAASIdentifiableType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 |
The AdministrativeInformationType is a subtype of the BaseObjectType. Table 19 defines the AASAdministrationInformation ObjectType.
Table 19 – AASAdministrativeInformationType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASAdministrativeInformationType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 |
Table 21 defines the AASIdentifier ObjectType. It is used to uniquely identify an entity.
|
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 |
Figure 12 shows an overview about the AASAsset ObjectType.
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 |
NodeClass |
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 24 – AASAssetType 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 |
Figure 13 shows an overview about the AASSubmodel ObjectType.
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 |
NodeClass |
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 26 – AASSubmodelType 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 |
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.
Figure 14 – SubmodelElement Subtypes
Figure 15 shows an overview about the AASSubmodelElement ObjectType.
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 |
NodeClass |
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 28 – AASSubmodelElementType 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 |
Figure 16 shows an overview about the AASSubmodelElementCollection ObjectType.
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 |
NodeClass |
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 30 – AASSubmodelElementCollectionType 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).
Figure 17 shows an overview about the AASOrderedSubmodelElementCollection ObjectType.
Figure 17 – AASOrderedSubmodelElementCollectionType graphical overview
Table 31 defines the AASOrderedSubmodelElementCollection ObjectType.
Table 31 – AASOrderedSubmodelElementCollectionType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASOrderedSubmodelElementCollectionType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 32 – AASOrderedSubmodelElementCollectionType 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).
Figure 18 shows an overview about the AASMultiLanguageProperty ObjectType
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 |
NodeClass |
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 34 – AASMultiLanguagePropertyType 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 |
Figure 19 shows an overview about the AASProperty ObjectType.
Figure 19 – AASPropertyType graphical overview
The valueId attribute references a DictionaryEntry. Table 35 defines the AASProperty ObjectType.
Table 35 – AASPropertyType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASPropertyType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 36 – AASPropertyType 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 |
Table 37 defines the AASCapability ObjectType.
Table 37 – AASCapabilityType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASCapabilityType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 |
|
|
Figure 20 shows an overview about the AASOperation ObjectType.
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 |
NodeClass |
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.
Figure 21 shows an overview about the AASBlob ObjectType.
Figure 21 – AASBlobType graphical overview
Table 39 defines the AASBlob ObjectType.
Table 39 – AASBlobType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASBlobType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 40 – AASBlobType Additional References
|
Source Path |
Reference Type |
Is Forward |
Target Path |
|
File |
0:HasDictionaryEntry |
True |
Admin-shell.io/aas/2/0/Blob/value |
Figure 22 shows an overview about the AASFile ObjectType.
Figure 22 – AASFileType graphical overview
Table 41 defines the AASFile ObjectType.
Table 41 – AASFileType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASFileType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 42 – AASFileType 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.
Figure 23 shows an overview about the AASRelationElement ObjectType.
Figure 23 – AASRelationElementType graphical overview
A relationship element is used to define a relationship between two referable elements (Table 43).
Table 43 – AASRelationshipElementType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASRelationshipElementType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 44 – AASRelationshipElementType 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 45 – AASAnnotatedRelationshipElementType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASAnnotatedRelationshipElementType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 46 – AASAnnotatedRelationshipElementType 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
Figure 24 shows an overview about the AASReferenceElement ObjectType.
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 |
NodeClass |
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 48 – AASReferenceElementType Additional References
|
Source Path |
Reference Type |
Is Forward |
Target Path |
|
Value |
0:HasDictionaryEntry |
True |
Admin-shell.io/aas/2/0/ReferenceElement/value |
Figure 25 shows an overview about the AASEvent ObjectType.
Figure 25 – AASEventType graphical overview
Table 49 defines the AASEvent ObjectType.
Table 49 – AASEventType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASEventType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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. |
||||||
Figure 26 shows an overview about the AASEntity ObjectType.
Figure 26 – AASEntityType graphical overview
Table 50 defines the AASEntity ObjectType.
Table 50 – AASEntityType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASEntityType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 51 – AASEntityType 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 |
If Min missing then negative open range infinitely, if max missing the open range infinitely.
Table 52 – AASRangeType Definition
|
Attribute |
Value |
||||
|
BrowseName |
AASRangeType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
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 53 – AASRangeType 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 |
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.
Figure 27 – Concept description and data specification OPC UA graphical model
Table 54 defines the AASIrdiConceptDescription ObjectType.
Table 54 – AASIrdiConceptDescriptionType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASIrdiConceptDescriptionType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 55 – AASIrdiConceptDescriptionType 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 |
Table 56 defines the AASIriConceptDescription ObjectType.
Table 56 – AASIriConceptDescriptionType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASIriConceptDescriptionType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 57 – AASIriConceptDescriptionType 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 |
Table 58 defines the AASCustomConceptDescription ObjectType.
Table 58 – AASCustomConceptDescriptionType Definition
|
Attribute |
Value |
||||
|
BrowseName |
AASCustomConceptDescriptionType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
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 59 – AASCustomConceptDescriptionType 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 |
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 |
NodeClass |
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 |
|
Figure 28 shows an overview about the AASDataSpecificationIEC61360 ObjectType.
Figure 28 – AASDataSpecificationIEC61360Type graphical overview
Table 61 defines the AASDataSpecificationIEC61360 ObjectType.
Table 61 – AASDataSpecificationIEC61360Type Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASDataSpecificationIEC61360Type |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 |
|
|
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 |
Figure 29 shows an overview about the AASQualifier ObjectType.
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 64 – AASQualifierType 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 |
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"
}
]
},
Table 65 defines the AASView ObjectType.
Table 65 – AASViewType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
AASViewType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
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 |