Condition Management¶

Overview¶

The Condition Management functionality allows users to open and manage a condition for an asset. Conditions can be automatically opened by a Rule or manually be created by a user. All conditions are tied to a Condition Policy which can provide context to the situation and offer recommended actions. Condition Policies can be standardized and used across many assets. A condition is associated to an Asset. When created by a Rule, the rule, signal are also associated.

Conditions support 'comments' by users, which can be used to provide updates and information such as actions taken, any troubleshooting details, etc.

Condition States¶

The following lifecycle states are supported for a condition.

Condition Priorities¶

Condition Policies specify the priority, this is a decision by users who define the policies.

• Minor
• Major
• Critical
• Blocker

These priorities have no further definition and is up to the user to determine how to apply the levels to their processes

Condition Lifecycle Flow¶

sequenceDiagram
  autonumber
  participant Signal Data
  participant Rule
  participant Condition Policy
  participant Condition 
  actor User
  Signal Data -->>Rule: New Values
  activate Rule
  rect rgba(255, 0, 0,.1)
  Rule->>Rule: Detect Condition
  deactivate Rule
  Note right of Rule: Rule Critical or Warning State Change!
  end
  Rule-->>Condition Policy: Condition Detected
  Condition Policy-->>Condition Policy: Is there an open Condition?
  Condition Policy->>Condition: No, Create New
  activate Condition
  Note right of Condition: New Condition<br>Unacknowledged
  User->>Condition: Acknowledge
  Note right of Condition:  Acknowledged

  Signal Data -->>Rule: New Values
  activate Rule
  rect rgba(0, 255, 0,.1)
  Rule->>Rule: Detect Condition
  deactivate Rule
  Note right of Rule: Rule Back to Ok State.
  end

  User->>Condition: Assign
  Note right of Condition:  Assigned

  Signal Data -->>Rule: New Values
  activate Rule
  rect rgba(255, 0, 0,.1)
  Rule->>Rule: Detect Condition
  deactivate Rule
  Note right of Rule: Rule Critical or Warning State Change!
  end
  Rule-->>Condition Policy: Condition Detected
  Condition Policy-->>Condition Policy: Is there an open Condition?
  Note right of Condition Policy: Yes, No action<br>(Condition Exists)

  User->>User: Take recommended actions.
  User->>Condition: Close
  Note right of Condition:  Closed
  deactivate Condition

Condition Management¶

The Conditions page can be found using the left navigation menu. This page will show a list of conditions for user roles with Condition Read-Only or Condition User permissions, filtered by default to not show closed conditions. User Roles with the Condition Policy Management permission will also see the Condition Policy tab to manage policies.

Conditions and Signal Rules¶

To associate a Signal Rule in your asset to a Condition Policy, use the Asset Configuration page to Add/Edit Actions for the specific Rule.

Here, the Condition Policy Action is available to choose from the available Condition Policies.

Once this is setup for the rule, when the Rule state changes to warning and/or critical (this is specified by the Administrator) a new condition will be created if there is currently not an open condition. If there is already an open condition, it will stay open.

Manually Create a Condition¶

Using the (+) button on the Conditions list page you can manually add a new Condition. When creating a condition, an Asset and Condition Policy are required. You may also add a description of why the Condition is being created and choose a priority. The condition can be assigned or left unassigned.

Condition Policies¶

A condition policy specifies a type of condition with descriptive information and details for corrective action. These are fully defined by an operator or manager role with the permission. At least one Policy must be set up to use Conditions.

It's recommended to create a default 'general' policy for use when a condition needs to be manually tracked that may not have a specific policy in place.

The policy description format is in Markdown syntax

The Condition Policy ID is used only once, when setting up the default policy as a Rule Action.

Condition Action Setup¶

The Condition feature can be though of as a type of Rule Action. To use Conditions with Rules, an Administrator must first set up an Action type. This is a one time setup. The default policy ID is used here.