For each asset managed by an OPC UA Server the user wants to

Receive a globally unique identification of the asset that should be identical, even if the asset is managed by various OPC UA servers.

Receive standardized base identification information of the asset like serial number, manufacturer, and revision information.

Set and receive user-specific identification information that is tailored to the needs of the user, like a user-specific name or identification.

This allows the user to receive and manage asset information as base for various asset management use cases. The assets can be uniquely identified, even if managed by different applications, and the user gets information about the manufacturer of the asset etc. The user can set its own information into the identification information in order to follow a user-specific identification and naming schema.

The user wants to have a mechanism that allows access to information about all assets in an OPC UA Server with a minimum set of roundtrips (service calls).

The user wants to identify if new assets have been added to the OPC UA Server or assets have been removed. This requires a unique identification of the asset (see UC001).

For planning the usage of each asset, the user wants to receive information about:

general skills of an asset such as supported manufacturing processes, supported tools, …

products an asset can produce or transform

To use, position or reposition an asset managed by an OPC UA Server the user wants to get information about:

Connection Values such as electricity requirements (voltage, current, …) and media connection pressure if required

Connection and plug types

Required environmental conditions such as temperature and air pressure

Dimension and weight

The user wants to get version information of an asset. This information is needed for maintenance purposes and so on. Required are the following information:

Type or Hardware-Version

Firmware Version (if applicable)

Integrated Software and version of it

Current Patch Version (History)

Revision Counter

Supported OPC UA functionality

Operating time counter

Link to digital record (handbook / delivery status /usable skills and skill changes by upgrades)

Counter about using (e.g. Relay: Counter switching operation switch operations under load)

Standard Basic Error messages

For each asset managed by an OPC UA Server the user wants to

Receive a simple, common health status.

This includes (from Devices spec and NAMUR NE 107):

Normal – Asset functions normally

Failure – Malfunction of the asset

Check Function – Function checks are performed, like configuration checks, local operation, etc.

Off Spec – The asset is operating outside its specification (e.g. measuring or temperature range) or internal diagnoses indicate deviations

Maintenance required – Asset operates normally, the wear reserve is nearly exhausted or a function will soon be restricted due to operational conditions, e.g. build-up of deposits

Note: If an asset contains sub-assets, the health status of the sub-assets are of importance for the asset, however, how this is considered is an implementation detail (e.g. if you have redundant sub-assets, one might fail without the overall asset failing).

Receive asset specific information on failure or maintenance conditions. This information should include

Time of failure

Severity

A description, ideally containing cause of a failure and a proposed action, how to solve the failure (e.g. restarting the asset, changing the configuration, replacing asset, doing maintenance operations, etc.)

Once the user has investigated the cause, she wants the ability to mask and filter issues.

Information details about maintenance is covered in UC005-1.

The user wants to find the root cause of why the asset is not operating as expected.

Ideally the user may want to know how long the asset has been in its current common health status.

The user wants to get notified if an asset changes its health status.

Users want assets managed by an OPC UA Sever to have classified health indications. Proposed indications:

Critical Fault – Something has permanently failed.

Major Recoverable Fault – An asset can no longer perform its function. Intervention is required.

Minor Recoverable Fault – An asset has experienced a problem but is able to continue operation until intervention occurs.

Maintenance Needed – Service is required to keep the asset operating within its designed tolerances.

Limited Resource Capacity Near Limit – A limited resource met a threshold beyond which a more serious fault would occur.

Ideally users may want the ability to reassign indications to other categories based on their application.

Not all assets have the same capabilities, however if an asset can detect the following health conditions, users want them reported in a standardized way.

Standard Health Conditions:

One or more connections have failed

Over temperature

Calibration due

Self-Test has failed

Flash update in progress

Flash update has failed

Configuration is bad

OutOfResources issues and as specialisation OutOfMemory

For each asset managed by an OPC UA Server the user wants to

determine how long an asset has been in a specific health status and how often it changed over time.

get the information about asset specific information on failure or maintenance conditions over time.

be able to reset the tracked data (starting new from that point in time).

get the information when the tracked data have been reset / started to be tracked

The user wants to have access to the information regarding the maintenance activities of an asset. Through this information the user should be able to identify past and planned maintenance activities. This information should contain (if available):

Maintenance activity date

Estimated downtime (for planned events)

Actual downtime (for past events)

Notification for planned event (inactive/ days before / hours before)

Maintenance activity type (inspection, external check, servicing, repair, improvement)

Description of the maintenance activity

Maintenance supplier

Qualification of the personnel

Parts of the asset replaced

Parts of the asset serviced

Maintenance method (remote/local)

Configuration change (indicates whether the configuration has changed)

For any selected asset, the user shall be able to identify and browse the internal structure based on the hierarchy of sub-assets. The user shall be able to identify

1) all the exposed sub-assets directly linked to the asset in a parent-child-like relation and

2) other relations between sub-assets that are exposed to the asset.

Assets can be classified in many different ways, for example by the manufacturing process (see DIN 8580), by the type of physical asset (see ISA 95), ECLASS, IEC 61360, etc.

The user wants to access the classification information of each asset. An asset may be classified by different classification schemas. The user wants to access that information, including the used classification schema per classification.