5 Use cases ToC Previous Next

5.5 Health Status (UC004) ToC Previous Next

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

Previous Next