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.