PM Connector

Overview

The PM connector ensures that Planned Maintenance (PM) data in NEXUS reflects PM data within a CMMS environment and that the data in both systems is kept accurate and up-to-date without having to enter data into both systems.

By automating the synchronisation process and ensuring data consistency, the connector enhances the efficiency and reliability of PM management within the organisation.

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

NEXUS provides an Asset Information Group (AIG) form, which stores PM data, including the following key fields:

  • PM Number

  • Function fields (used to calculate RBI interval and next inspection date)

  • CMMS Start Date

  • CMMS Interval

Additional fields can be mapped to NEXUS as needed as part of the configuration process.

The connector operates by identifying PM records where:

  • The PM Number is blank, or

  • The Next PM Date and Interval fields in NEXUS do not match the CMMS Start Date and CMMS Interval fields.

For each PM that meets these criteria, the connector sends a request to the CMMS system, including the unique Sub-AIG Row ID. Once the PM is created or updated in the CMMS, a payload is returned to NEXUS containing:

  • The unique PM ID

  • The CMMS Start Date

  • The CMMS Interval

This data is then used to update the corresponding PM record in NEXUS.

The following diagram summarises the standard example workflow:


_images/integration.pm.connector.png

  1. NEXUS periodically checks for PMs that either lack a PM Number or have mismatched start dates or intervals compared to the CMMS.

  2. The connector sends the Sub-AIG Row ID to the CMMS system, where a new PM will be created.

  3. Upon receiving a response from the CMMS, NEXUS updates the PM Number, CMMS Start Date, and CMMS Interval fields accordingly.

  4. If an existing PM has changes to its interval or start date in NEXUS, the connector detects the discrepancy and pushes the update to the CMMS.

  5. If PM details are modified in the CMMS, these changes are automatically pushed back to NEXUS.