Multistate Status

Some integrated system assets can be in multiple states at once. A multistate status can be defined to show that an asset is in a specific combination of states. The multistate status requires all added statuses for the asset to resolve to that state.

While multistate assets can be configured to use single state statuses, you will need to configure the priority to ensure the correct state is displayed. When the highest priority state is active, any lower priority states will not be shown. Creating a multistate status allows the Runtime operator to have awareness of the multiple active states. For example, if a door could be open or closed, as well as locked or unlocked, and the locked/unlocked statuses were highest priority, the Runtime operator would never be aware if the door was open or closed.

It is not recommended to use multistate statuses for single state assets, as they will never resolve to multiple statuses at once.

Creating a Multistate Status

In this example, we will be setting up a multistate status for a door system. A door can be opened (unsecure) or closed (secure), as well as locked or unlocked. We will configure a status for when the door is both secure and locked in the following steps.

In the integrated system door status table:

  1. Click Add to create a new status.
  2. In the Description, label the status Secure + Locked.
  3. In the State drop-down, select the - Multistate - option.
  4. Add the Secure and Locked states.
    1. Select Secure from the Available States list and click >.
    2. Select Locked from the Available States list and click >.
    Multistate status with secure and locked states selected

Runtime Behavior

When multiple multistate statuses exist in a status table, the system considers the following conditions when resolving which status to display:

  1. The total number of matching system states
  2. The priority of the status
Note: If multiple multistate statuses contain the same or overlapping states, you may see unexpected or unintended behavior during resolution.

Example:

  1. Status 1: Door Open + Unlocked + REX Disabled

    • Multistate includes:

      • Open

      • Unlock

      • REX Disabled

    • Priority: 10

  2. Status 2: Door Open + Unlocked

    • Multistate includes:

      • Open

      • Unlock

    • Priority: 20

  3. Evaluate the resolved status for the scenario

    If the physical door is Open, Unlocked, and REX is enabled, the system will still resolve to Status 1.

    This occurs because both Status 1 and Status 2 have two matching states (Open and Unlock). Since the total number of matching states is equal, Runtime uses Priority to determine which to display. In this case, Status 1 (Priority 10) is higher, so it is shown.

  4. Resolve conflicts when multiple statuses are valid
    • Adjust Priorities:

      • Increase the priority of Status 2 above Status 1 so the status manager selects Status 2 when both are valid.

    • Refine Multistate Definitions
      • Add REX Enabled (or another relevant state) to Status 2’s multistate list so it has more matching states when REX is enabled, allowing it to take precedence over Status 1.