Skip to main content
Skip table of contents

Alerts Report

The alerts report is a record of all actions taken to resolve an alert.

Click here to watch a video on the alerts report.

Report headings will appear:

  • red if the alert has not been actioned

  • amber if the alert has been acknowledged

  • grey if the alert has been cleared

If an alert was cleared in bulk using the Clear all button, the Action taken field will read: ‘Alert cleared using the Clear all function’.

Types of Alerts Reports

There are four types of alerts reports each containing different types of information. See below for full details.

CWM Alerts Reports

Check Alert Report

A check alert report is a record of all actions taken to resolve a check alert (an alert triggered when a member of staff uncovers an issue while completing work on the CWM app).

Image 1: Check alert report

A check alert report specifies:

  • when the alert was raised (recorded in the local time of the location where the alert was raised)

  • the work schedule

  • the check that triggered the alert

  • the team responsible for the work

  • the user that triggered the alert on the app

  • the delayed check ID and cancellation reason (if the check alert was triggered by the cancellation of a time-delayed check)

  • when the alert was actioned (recorded in the local time of the location where the alert was raised)

  • the user(s) that actioned the alert

  • how the alert was actioned:

    • acknowledged

    • cleared

  • the delay between the alert being triggered and actioned

  • details of the action taken

Overdue Alert Report

An overdue alert report is a record of all actions taken to resolve an overdue alert (an alert triggered because work was not completed in time).

Image 2: Overdue alert report

An overdue alert report specifies:

  • when the alert was raised (recorded in the local time of the location where the alert was raised)

  • the work schedule

  • the work that triggered the alert

  • the team responsible for the work

  • the delayed check ID (if the overdue alert was triggered by late completion of a time-delayed check)

  • when the alert was actioned (recorded in the local time of the location where the alert was raised)

  • the user(s) that actioned the alert

  • how the alert was actioned:

    • acknowledged

    • cleared

  • the delay between the alert being triggered and actioned

  • details of the action taken

If you have completed work on the CWM app in time but your device was offline, the overdue alert will be cleared automatically when your device comes back online.

The Action taken field will read: ‘Automatically cleared as Job was completed in time by another user’.

CAM Alerts Reports

Sensor Alert Report

A sensor alert report is a record of all actions taken to resolve a sensor alert (an alert triggered when a sensor is operating outside of its defined parameters).

Image 3: Sensor alert report

A sensor alert report specifies:

  • when the alert was raised (recorded in the local time of the location where the alert was raised)

  • the sensor that triggered the alert

  • the rule assigned to the sensor

  • the team assigned to the sensor

  • the sensor reading that triggered the alert

  • the acceptable range

  • when the alert was actioned (recorded in the local time of the location where the alert was raised)

  • the user(s) that actioned the alert

  • how the alert was actioned:

    • acknowledged

    • cleared

  • the delay between the alert being triggered and actioned

  • details of the action taken

Click on the sensor to view a graph showing when the alert occurred. Click the back button on your browser to return to the report. See image 4.

Sensor alert report hyperlink.gif

Image 4: View when an alert occurred

Service Alert Report

A service alert report is a record of all actions taken to resolve a service alert (an alert triggered when a sensor, Repeater, or Hub is offline or has low battery).

Image 5: Service alert report

A service alert report specifies:

  • when the alert was generated (recorded in the local time of the location where the alert was raised)

  • the sensor/Repeater/Hub that generated the alert

  • the type of service alert:

    • device offline

    • low battery

  • when the alert was actioned (recorded in the local time of the location where the alert was raised)

  • the user(s) that actioned the alert

  • how the alert was actioned:

    • acknowledged

    • cleared

  • the delay between the alert being triggered and actioned

  • details of the action taken

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.