Table 54 defines the corresponding ConformanceUnits for the OPC UA Information Model for Asset Management Basics.

Table 54 – Conformance Units for Asset Management Basics

Category

Title

Description

Server

AMB Asset Identification

All manageable assets provided by the server have the “ProductInstanceUri” and optionally additional identification Properties.

The Properties are either directly on the Object representing the asset or on the Identification Object grouping the Properties.

Server

AMB Configurable Asset Identification

All manageable assets provided by the server have the “AssetId” and optionally additional configurable identification Properties as writable Properties that store the configuration persistently, providing the written values also after a restart of the server.

Servers shall support at least 40 Unicode characters for the clients writing this value. This means clients can expect to be able to write strings with a length of 40 Unicode characters into that field.

The Properties are either directly on the Object representing the asset or on the Identification Object grouping the Properties.

Client

AMB Client Asset Identification

The client can make use of asset identification information and is capable to receive that information independent if it is provided per TypeDefinition, Interface or just as Properties on the instance or under the Identification Object and is able to deal with default values of the Properties.

Server

AMB Asset Discovery by ProductInstanceUri

All manageable assets are provided as AliasNames under to AssetsByProductInstanceUri using the ProductInstanceUri as AliasName. The AssetsByProductInstanceUri Object supports NodeVersion and ModelChangeEvents.

Server

AMB Asset Discovery by AssetId

All manageable assets supporting the AssetId Property are provided as AliasNames under to AssetsByAssetId using the AssetId as AliasName. The AssetsByProductInstanceUri Object supports NodeVersion and ModelChangeEvents.

Client

AMB Client Asset Discovery by ProductInstanceUri

The client can make use of the AssetsByProductInstanceUri discovery mechanism to discover the assets managed by the server or other, referenced servers. Whether the client uses the FindAlias method or browses the AliasNames is client-specific. The client is capable to manage Off-Server references in this discovery mechanism.

Client

AMB Client Asset Discovery by AssetId

The client can make use of the AssetsByAssetId discovery mechanism to discover the assets managed by the server or other, referenced servers. Whether the client uses the FindAlias method or browses the AliasNames is client-specific. The client is capable to manage Off-Server references in this discovery mechanism.

Server

AMB Asset Health Status Base

All manageable assets provided by the sever have the “DeviceHealth” variable.

Server

AMB Asset Health Status Alarms

All manageable assets provided by the server provide alarms with details of their fault indications.

Optionally, the alarms are provided as Objects in the DeviceHealthAlarms folder.

Server

AMB Asset Health Status Root Causes

All manageable assets provided by the server provide alarms with details of their fault indications. All those alarms implement the “IRootCauseIndicationType”.

Server

AMB Asset Health Status Alarm Categories

All manageable assets provided by the server provide alarms with a reasonable ConditionClassId.

Server

AMB Asset Health Tracking Overall Asset Status

All manageable assets provided by the sever having the “DeviceHealth” variable have the Historizing attribute of that variable set to true and the AccessLevel set to HistoricalRead.

Server

AMB Asset Health Tracking Events

The server supports access of the history of all alarms representing the details of fault indications of its assets.

Client

AMB Client Asset Health Status

The client can make use of the “DeviceHealth” variable and the alarms providing details on the fault indication.

Client

AMB Client Asset Health Tracking Status

The client can make use of the history of the “DeviceHealth” variable and the history of the alarms providing details on the fault indication.

Server

AMB Version Information

All manageable assets provided by the server have, depending on their nature, the Software- and or HardwareRevision Property and the RevisionCounter Property.

Server

AMB Operation Counters

At least one manageable asset provided by the server provides the OperationCounters Object and at least one operation counter.

Server

AMB DocumentationLinks Base

At least one manageable asset provided by the server provides the DocumentationLinks AddIn and have at least one link.

Server

AMB DocumentationLinks Edit Base

All manageable assets provided by the server provide the DocumentationLinks AddIn and have at least one link that can be edited by the user to provide user-specific links. The Browse- and DisplayName and the Description might be editable. The server supports links of a length of at least 255 chars.

Server

AMB DocumentationLinks Edit Advanced

All manageable assets provided by the server provide the DocumentationLinks AddIn and support the AddLink and RemoveLink methods. The server is capable to manage at least two links added via the AddLink method. The server supports links of a length of at least 255 chars.

Server

AMB Requirements

At least one manageable asset provided by the server provides the Requirements Object and at least one requirement.

Server

AMB Capabilities

At least one manageable asset provided by the server provides the Capabilities Object and at least one capability.

Server

AMB Classification

At least one manageable asset provides at least one HasDictionaryEntry reference to classify the asset.

Server

AMB Current and Future Maintenance Activities

All manageable assets provided by the server provide conditions with details of current or upcoming maintenance activities.

Optionally, the conditions are provided as Objects in the DeviceHealthAlarms folder.

The ConditionTypes used as maintenance activities implement the IMaintenanceEventType.

Server

AMB Past Maintenance Activities

The server provides capability to read the history of events and for all manageable assets provided by the server the history of all maintenance activities is provided.

The ConditionTypes used as maintenance activities implement the IMaintenanceEventType.

Client

AMB Client Current and Future Maintenance Activities

The client can make use of the conditions provided as maintenance activities providing details on current and planned maintenance activities.

Client

AMB Client Past Maintenance Activities

The client can make use of the history of the conditions provided as maintenance activities providing details on the past maintenance activities.

Server

AMB Local Time

At least one manageable asset provided by the server provides the LocalTime Property.

Server

AMB Hierarchical Location Property

At least one manageable asset provided by the server provides the Location Property.

Server

AMB Hierarchical Location Objects

The HierarchicalLocations Object is provided with at least one location hierarchy and at least one manageable asset is referenced from that hierarchy with the HierarchicalContains Reference or a subtype.

Server

AMB Operational Location Property

At least one manageable asset provided by the server provides the OperationalLocation Property.

Server

AMB Operational Location Objects

The OperationalLocations Object is provided with at least one operational location and at least one manageable asset is referenced from that location with the OperationalContains Reference or a subtype.

Server

AMB Digital Location

At least one manageable asset provided by the server provides the DigitalLocation Property.

Server

AMB Sub-assets

At least one manageable asset provided by the server exposes at least one sub-asset as manageable asset. The sub-assets may be managed in another server.

Client

AMB Client sub-assets

The client can make use of the sub-asset hierarchy provided by the server and is capably to identify all sub-assets of an asset managed in the same server.

Client

AMB Client sub-assets remote

The client can make use of the sub-asset hierarchy provided by the server and is capably to identify all sub-assets of an asset managed in multiple servers.

Server

AMB Asset relations

At least one manageable asset provided by the server exposes a relation to another manageable asset other than containment (sub-asset). The referenced asset may be managed in another server.

Table 55 lists all Profiles defined in this document and defines their URIs.

Table 55 – Profile URIs for Asset Management Basics

Profile

URI

AMB Base Asset Management Server Facet

http://opcfoundation.org/UA-Profile/AMB/Server/BaseServer

AMB Base Asset Management Client Facet

http://opcfoundation.org/UA-Profile/AMB/Client/BaseClient

The following sections specify the Facets available for Servers that implement the Asset Management Basics companion specification. Each section defines and describes a Facet or Profile.

Table 56 defines a Profile that describes the base characteristics for all OPC UA Servers that make use of this companion specification.

Table 56 – AMB Base Asset Management Server Facet

Group

Conformance Unit / Profile Title

Mandatory / Optional

Server

AMB Asset Identification

M

Server

AMB Configurable Asset Identification

O

Server

AMB Asset Discovery by ProductInstanceUri

O

Server

AMB Asset Discovery by AssetId

O

Server

AMB Asset Health Status Base

O

Server

AMB Asset Health Status Alarms

O

Server

AMB Asset Health Status Root Causes

O

Server

AMB Asset Health Status Alarm Categories

O

Server

AMB Asset Health Tracking Overall Asset Status

O

Server

AMB Asset Health Tracking Events

O

Server

AMB Version Information

O

Server

AMB Operation Counters

O

Server

AMB DocumentationLinks Base

O

Server

AMB DocumentationLinks Edit Base

O

Server

AMB DocumentationLinks Edit Advanced

O

Server

AMB Requirements

O

Server

AMB Capabilities

O

Server

AMB Classification

O

Server

AMB Current and Future Maintenance Activities

O

Server

AMB Past Maintenance Activities

O

Server

AMB Local Time

O

Server

AMB Hierarchical Location Property

O

Server

AMB Hierarchical Location Objects

O

Server

AMB Operational Location Property

O

Server

AMB Operational Location Objects

O

Server

AMB Digital Location

O

Server

AMB Sub-assets

O

Server

AMB Asset relations

O

The following tables specify the Facets available for Clients that implement the Asset Management Basics companion specification.

Table 57 defines a Facet that describes the base characteristics for all OPC UA Clients that make use of this companion specification.

Table 57 – AMB Base Asset Management Client Facet

Group

Conformance Unit / Profile Title

Mandatory / Optional

Client

AMB Client Asset Identification

M

Client

AMB Client Asset Discovery by ProductInstanceUri

O

Client

AMB Client Asset Discovery by AssetId

O

Client

AMB Client Asset Health Status

O

Client

AMB Client Asset Health Tracking Status

O

Client

AMB Client Current and Future Maintenance Activities

O

Client

AMB Client Past Maintenance Activities

O

Client

AMB Client sub-assets

O

Client

AMB Client sub-assets remote

O