Alarms and notifications
When a reading goes out of range, the platform opens an alarm, notifies the right people and records who handled it and when.
How an alarm is raised
Each device type has its alarm rules: an upper and a lower limit, a delay so that a brief door opening does not trigger an alert, or a condition that must repeat before it fires. Rules can vary by time of day or by device, and thresholds can be taken from each site's data.
The sensor takes part too: if a reading crosses its threshold, the logger does not wait for the next scheduled transmission and sends at once, so that the alarm arrives in time.
Severity and life cycle
Alarms are classed by severity, from warning to critical, and an alarm that gets worse moves up a level without being duplicated. Each one has a status (active or cleared, acknowledged or not), an assignee and a comment thread. Everything is recorded: what happened, when, who acknowledged it and what was done.
Alerts and escalation
Notifications arrive by email and within the platform. If nobody acknowledges an alarm, it is escalated to a second list of recipients after the delay that has been set. An alarm on a device can also be seen on the site that contains it, so that the site manager sees it without looking for it.
Designed for audits
Complete record
Every alarm keeps its history: start, end, acknowledgement and comments.
Documented excursions
The period out of range stays in the data and in the reports.
Clear ownership
Each alarm is assigned to a person, and their response is recorded.
A question about your measurement
A specialist replies with the solution, the instrument and the service that fit.