Alarming Devices
This page provides a real-time overview of devices in alarm state and their associated messages in the project.
- Total number of devices currently under alarm.
- Statistics for devices currently under alarm: count of pending alarms and total number of all alarm messages.
- Statistics for devices currently under alarm: alarm message urgency, prioritized into High (Level 5), Medium (Level 3/4), and Low (Level 1/2).
- More Filters: Filter alarms based on thing model and device name keywords.
- Clear search criteria and refresh the page.
- The three status texts from top to bottom are: Resolved, To Be Resolved, Acknowledged.
- Acknowledge/Cancel acknowledge alarms.
Alarm Message Details Page
The platform features a standard alarm handling process, offering automatic triggering (recommended) and manual triggering: Automatic triggering requires pre-configuration in the rules engine, executing actions like dispatching tasks, sending notifications, or device control automatically upon alarm. Manual triggering allows administrators to perform actions like recording inspections, dispatching orders, or acknowledging alarms in real-time based on the situation. The alarm handling progress is tracked through three statuses: To Be Resolved (unhandled alarm), Acknowledged (being handled, can set silent mode for no disturbance), and Resolved (manually marked after completing at least one handling action, does not prevent the device from alarming again due to rules).
-
Basic Alarm Information: Includes the time the alarm was triggered, the device's location, etc.
-
Device location information and playback video or screenshots (if available).
-
Device 3D Model (if available): Shows the location of the alarming device in the Digital Twins scene; when present in multiple scenes, click the arrow to view all scene lists.
-
Alarm Acknowledgment Log: Clicking "Acknowledged" indicates the alarm is known and being handled; click again to unacknowledge. When acknowledging, a silence duration can be set; during this period, even if the device continues to alarm, the platform will not repeat reminders, but you can still view the record in the alarm list.
-
Displays the alarm message status, with the following three states:
(1) To Be Resolved: Newly generated alarm, not yet handled.
(2) Acknowledged: User clicked the Acknowledge button (Indicates the alarm is known and being handled; click again to cancel acknowledge.)
(3) Resolved: User clicked the Resolve button (Indicates the alarm has been handled; requires completing at least one operation before clicking, such as filling inspection results, creating and closing a task, or sending a third-party notification)
Note: Messages in the Resolved status can be reopened, reverting them to Acknowledged/To Be Resolved status.
-
Alarm Handling Process: Includes filling inspection records, dispatching tasks, and sending external notifications.
(1) Fill Inspection Record:
After submitting the inspection record, users can re-edit and view/download attachments.
(2) Dispatch Task:
Note, a work order is considered completed for the purpose of this workflow only when its status is one of those shown below. If multiple work orders exist, all must be completed before the alarm can be resolved.
(3) Send External Notification:
Note, on the alarm message details page, third-party notifications can only be sent via "WhatsApp". To send via E-mail or Teams, configure automatic triggers using pre-built handling templates in the Device Alarm Rules Platform.
-
Click to download a report detailing this specific alarm and its handling log.