Solution
Smart Alarm Engine
The right alert to the right person at the critical moment — without false positives or mail storms. Rule-based threshold monitoring across 5 categories, a cooldown mechanism and multiple notification channels.
The right alert to the right person at the critical moment — without false positives or mail storms. Rule-based threshold monitoring across 5 categories, a cooldown mechanism and multiple notification channels.
When too many alarms come in, operators start ignoring the alerts. A real critical event gets lost in the noise.
If dozens of alarm emails for the same fault arrive every minute, the mailbox locks up and the alarm loses its impact.
When instantaneous measurement spikes exceed the threshold, an unnecessary alarm is triggered; the team heads to the site but there is no problem.
When a device goes silent or a threshold is exceeded, notification delays can reach hours — and the damage grows.
In systems that rely on email only, if the mail server goes down no alarm gets through.
Customizable threshold rules across the Energy, Transformer, Generator, UPS and Water categories — separate logic for each device type.
A minimum waiting period is defined before a triggered alarm fires again; no mail flood for the same fault.
Microsoft Graph API + SMTP fallback — notifications are delivered even if the mail server goes down.
High-frequency alarms are summarized and sent as a single email; your mailbox stays clean.
If a closed alarm reopens under the same condition, a notification is sent again; it is never lost.
Every alarm event is recorded with a timestamp; it is accessible for SLA analysis and reporting.
From the web interface, you define a category, metric (kW, kVAr, battery%, fuel%), threshold value, duration and recipient list for each device. Changes take effect immediately, with no restart required.
Every alarm that has a cooldown period defined will not generate a new alarm for the same rule for the specified duration (e.g. 30 minutes) after it is triggered. If the condition persists during that period, a single summary email is sent in digest mode.
If no data arrives from a device for 3 times its expected poll period, a silence alarm is generated. For example, with a 15-minute poll interval, a 45-minute data outage triggers an alarm. This threshold is configurable.
If an alarm is not resolved within a certain time, a notification is automatically sent to a second recipient group (e.g. a manager). The escalation tier and waiting period can be defined separately per rule.
| Rule Categories | Energy, Transformer, Generator, UPS, Water |
| Notification | Microsoft Graph API + SMTP fallback |
| Cooldown | Configurable per rule (recommended: 30 min) |
| Silence Threshold | Poll × 3 (e.g. 15 min poll → 45 min silence) |
| History Retention | 30 days (np_alarm_gecmisi) |
Smart alarm management — without missing critical events and without mail storms.
Request a Demo → info@nevacontrol.com