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.

image033.png

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