For the identification of an asset, this specification mainly uses Propertiesdefined in OPC 10000-100. In order to support already released companion specifications and products as well as the different options provided by OPC 10000-100, this specification does not define or require a specific ObjectTypeor Interface, but ConformanceUnitsand Profilesreferencing mandatory and optional Propertiesas defined in OPC 10000-100.

The Propertiesdefined in OPC 10000-100for identification can either be implemented directly on the Objectrepresenting the asset, or in a grouping Objectcalled 2:Identification, also defined in OPC 10000-100.

This leads to the following options, as shown in Figure 1:

  1. Usage of 2:ComponentTypeor 2:DeviceType. An Objectrepresenting an asset can have the TypeDefinition2:ComponentType, 2:DeviceType, or a subtype of one of those ObjectTypesand thus containing the identification Propertiesdefined in OPC 10000-100.
  2. Usage of 2:IVendorNameplateTypeand 2:ITagNameplateType. An Objectrepresenting an asset can either directly implement those interfaces, or has a TypeDefinitiondirectly or indirectly implementing the interfaces.
  3. Usage of 2:Identification Object. An Objectrepresenting an asset provides the 2:Identification Object, and the 2:Identification Objectprovides the Properties, either by implementing the 2:IVendorNameplateTypeand 2:ITagNameplateTypeor by just providing the Properties.

image004.png

Figure 1– Different Options for Identification of Asset

The 2:Identification Objectshall have the BrowseName2:Identificationand shall be referenced with a hierarchical Referencefrom the Objectrepresenting an asset. The ObjectTypeof the 2:Identification Objectshall be 2:FunctionalGroupTypeor a subtype of 2:FunctionalGroupType.

The preferred and recommended approach is to use the 2:Identification Object. However, Clientsshall be aware of the other approaches and consider those for the identification of an asset as well.

OPC 10000-100defines most of the Propertiesas mandatory on the 2:DeviceType, with default values when the value cannot be provided. The 2:ComponentTypeand the Interfacesdefine the Propertiesas optional, i.e., they should be omitted when the information cannot be provided. The preferred and recommended approach is to omit Propertiesif the information is not available. However, Clientsshall be aware that there are default values and shall consider those.

In order to allow a globally unique identification of an asset, the 2:ProductInstanceUrishall be provided (see ConformanceUnitAMB Asset Identification in 15.1). It shall be either a Propertyof the Objectrepresenting the asset or referenced with a hierarchical Referencefrom the 2:Identification Object. The Propertyvalue shall not be an empty String.

All other Propertiesof 2:IVendorNameplateTypeshould be provided if the information is available. Other companion specifications will define additional, domain-specific identification information and vendors may add information as well. This additional information should preferably be put on the 2:Identification Object. A specialisation of 2:IVendorNameplateType can also be used to identify this additional information is identification information.

If the 2:AssetIdof the 2:ITagNameplateTypeis provided it shall be writable to allow a configurable identification of the asset (see ConformanceUnitAMB Configurable Asset Identification in 15.1). Other Properties of 2:ITagNameplateType and additional configurable Properties may be provided as well.

Older versions of OPC 10000-100did not define the 2:IVendorNameplateTypeand 2:ITagNameplateTypeand thus Clientsshall not expect that the 2:IVendorNameplateTypeand 2:ITagNameplateTypeare explicitly implemented on the TypeDefinition.