Anomaly Action Connector

Overview

The Anomaly Action Connector enables the automatic creation of notification requests in a CMMS system when an anomaly action is raised in NEXUS with the action type set to a specified value. It also supports updates to anomaly actions in NEXUS when corresponding notifications are modified in the CMMS, ensuring both systems remain synchronised.

Note

The functionality described below reflects the standard behaviour of the connector. However, workflows and features can be highly customised to meet specific client requirements.

Functionality

The connector operates on a scheduled basis and retrieves anomaly actions from NEXUS where:

  • Action Type is set to a specified value (for example, “Notification Request”)

  • Completed At and Reference Number fields are empty

For each matching anomaly action, a notification request is created in the CMMS.

Any updates made to the notification request in the CMMS are sent back to NEXUS, updating the corresponding anomaly action. This ensures NEXUS mirrors the current state of the notification in the CMMS.

The following diagram summarises the standard workflow:


_images/integration.anomaly.action.png

  1. On a scheduled interval, the connector identifies anomaly actions in NEXUS where:

    • Action Type = “Notification Request”`

    • Completed At is empty

    • Reference Number is empty

  2. For each identified anomaly action, the connector sends a notification request to the CMMS.

  3. Users manage and update the notification in the CMMS to track progress and resolution.

  4. Updates from the CMMS are sent back to NEXUS, ensuring the anomaly action reflects the current state of the notification. No manual action is required in NEXUS during this process.