5 Use cases

The use cases defined below are applicable to one or more roles described. It is not intended to be a complete list. The example roles in each plant or factory who is interested in the given data are given below:

Service technician, plant manager, quality engineer, machine integrator, factory planner, IT manager.

5.1 Asset Management

Name

Asset Management – Overview of System, Identification and Lifecycle Management of Assets. Tightening System can contain multiple assets.

Objective

To provide detailed information of the different assets in a system. It includes a standard organized way of accessing list of assets from a given system.

Description

For each asset managed in each system, it should be possible to:

  • Get a list of assets in standard way from a given system.
  • Receive a globally unique identification of the asset.
  • Receive a standardized base identification information of the asset like serial number, manufacturer, product code, and revision information, etc.
  • Set and receive specific identification information that is tailored to the needs, like a user-specific name or identification.
5.2 Condition Monitoring

Name

Condition Monitoring – Basic Health Information of the asset.

Objective

To provide regular or permanent recording of the machine condition by measuring and analyzing physical quantities, e.g. vibrations, temperatures, position/approximation.

Description

For each asset, managed in each system, it should be possible to:

  • Get basic condition and health information like temperature, uptime, error, service information etc.
5.3 Result Management

Name

Result Management – Standard result structure and interface to access the result data.

Objective

To provide standard content for result and standard methods, events, to access the result from a given system.

Description

For every operation from the system, the result information should be:

  • Exposed as standard data structure. To get the process values in different levels of detail. This starts at the basic level with OK / NOT_OK up to values of each step and traces.
  • Standard interface to access the result data.
  • Flexible result model to generalize across joining techniques and other domains.
5.4 Event Management

Name

Event Management

Objective

To provide system events in a standard way.

Description

For any event, error, or any occurrence in a system, the information should be:

  • Possible to send using standard event model.
  • Signals the existence of a new result.