ID

UC001

Name

Identification of Asset

Objective

The user wants to identify the assets managed by an OPC UA Server in a globally unique manner, receive standardized identification information about the asset and set user-specific information in order to simplify its usage.

Description

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.

Addressed in section

7

ID

UC002

Name

Discovery of Assets

Objective

The user wants to easily access all assets managed in an OPC UA Server.

Description

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).

Required Use Cases

UC001

Addressed in section

8

ID

UC0003-1

Name

Skills / Capabilities

Objective

The user wants to plan the usage of an asset managed by an OPC UA Server.

Description

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

Required Use Cases

UC001

Addressed in section

10.7

ID

UC003-2

Name

Requirements

Objective

The user wants to use, position or reposition assets managed by an OPC UA Server.

Description

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

Required Use Cases

UC001

Addressed in section

10.6

ID

UC003-3

Name

Version information

Objective

The user wants to get Version information of an asset managed by an OPC UA Server.

Description

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

Required Use Cases

UC001

Addressed in section

10.2, 10.3, 10.4, 10.5

ID

UC004

Name

Health Status

Objective

The user wants to get information about the current health status of an asset managed by an OPC UA Server. This includes a simple, common overview on each asset as well as detailed information on failure conditions.

Description

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.

Required Use Cases

UC001

Addressed in section

9

ID

UC004-1

Name

Health Categories

Objective

Users want health indications of assets managed by an OPC UA Server to be categorized by importance.

Description

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.

Required Use Cases

UC001, UC004

Addressed in section

9.3

ID

UC004-2

Name

Specific Health Conditions

Objective

Users want health indications of assets managed by an OPC UA Server to be reported in a harmonized way.

Description

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

Required Use Cases

UC001, UC004, UC004-1

Addressed in section

9.5

ID

UC004-3

Name

Tracking of Health Information

Objective

Users want to get information on the health information of an asset managed by an OPC UA Server over time.

Description

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

Required Use Cases

UC001, UC004, UC004-1, UC004-2

Addressed in section

9.6

ID

UC005-2

Name

Log of maintenance records

Objective

The user wants to access the information concerning the maintenance activities of an asset managed by an OPC UA Server.

Description

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)

Required Use Cases

CU001

Addressed in section

12

ID

UC007-3

Name

Hierarchical Location

Objective

The user needs knowledge about the hierarchical location of assets managed by an OPC UA Server.

Description

The user needs detailed information concerning the hierarchical location of each asset to be able to apply actions or receive information only from a specific part inside his plant, e.g. all assets within a specific line or emergency area. Examples for standardized hierarchies can be IEC 62264 (ISA 95), IEC 61512 (ISA 88), or IEC PAS 63088:2017 (Smart Manufacturing/Industry 4.0).

Required Use Cases

UC001

Addressed in section

13.3

ID

UC007-4

Name

Time / Local Time Location

Objective

The user needs knowledge about the time/local-time location of assets managed by an OPC UA Server.

Description

The user needs detailed information concerning the time/local-time location of each asset to be able to apply configuration changes related to a time zone, e.g. reconfiguration of an NTP server or applying a specific maintenance plan.

Required Use Cases

UC001

Addressed in section

13.2

ID

UC007-6

Name

Digital Location

Objective

The user needs knowledge about the digital location of digital assets managed in an OPC UA Server.

Description

The user needs detailed information concerning the digital location of each digital asset. The digital location can be a URI e.g. in case of a file asset.

Required Use Cases

UC001

Addressed in section

13.5

ID

UC007-7

Name

Operational Location

Objective

The user needs knowledge about the operational location of assets managed in an OPC UA Server.

Description

The user needs information about the operational location of each asset. An operational location represents a logical or physical location in which assets are located for operation. An operational location can for example be a stainless-steel tote, maintenance shed, work bench shelf and warehouse. Operational locations may be made up of smaller operational locations.

Required Use Cases

UC001

Addressed in section

13.4

ID

UC008-1

Name

Identifying the Structure of Assets

Objective

The user wants to identify the internal structure of an asset managed by an OPC UA Server, based on its sub-assets.

Description

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.

Required Use Cases

UC001

Addressed in section

14

ID

UC009

Name

Asset Classification

Objective

The user wants to access classification information of assets managed in an OPC UA Server.

Description

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.

Required Use Cases

CU001

Addressed in section

10.6