The right alarm to the right person at the critical moment — without false positives or mail storms. Rule-based threshold tracking across energy, water, climate and LoRa sensor families, a cooldown mechanism and multiple notification channels.
The right alarm to the right person at the critical moment — without false positives or mail storms. Rule-based threshold tracking across energy, water, climate and LoRa sensor families, a cooldown mechanism and multiple notification channels.
When too many alarms arrive, operators start ignoring them. The genuinely critical event is lost in the noise.
If dozens of alarm e-mails a minute land for the same fault, the mailbox locks up and the alarm loses its effect.
A momentary measurement spike crossing the threshold triggers an unnecessary alarm; the team drives to site and finds nothing wrong.
When a device goes silent or a threshold is crossed, notification can lag by hours - and the damage grows.
In systems that rely on e-mail alone, no alarm arrives at all once the mail server goes down.
Energy/power (analyser, transformer, generator, UPS, CT polarity), water, climate (chiller faults and frozen telemetry, VRF faults and communication) and LoRa sensor (low battery, tamper, communication, CO₂) alarms - separate logic for each device type.
A minimum wait is defined between one triggered alarm and the next, so the same fault never produces a mail flood.
Microsoft Graph API with SMTP fallback - the notification still gets through even if the mail server is down.
Instant e-mail goes out only for critical alarms; warning-level alarms are gathered into a daily summary e-mail. Alarms arising from the same event are merged into one consolidated e-mail; your mailbox stays clean.
If a closed alarm reopens under the same condition, notification is sent again - nothing is silently dropped.
Every alarm event is recorded with its timestamp and remains accessible for SLA analysis and reporting.
For each device you define the category, the metric (kW, kVAr, battery %, fuel %), the threshold value, the duration and the recipient list from the web interface. Changes take effect immediately - no restart required.
Once an alarm with a cooldown period fires, it produces no new alarm for that rule for the configured period (for example 30 minutes). If the condition persists during that window, a single summary e-mail is sent in digest mode.
The silence threshold has two levels: by default a warning is raised after 30 minutes without data and a critical alarm after 120 minutes (60 / 240 minutes for water meters). If the whole field unit goes silent, per-device alarms are suppressed and a single consolidated outage notification is sent. The thresholds are configurable.
If an alarm is not resolved within a defined period, notification is sent automatically to a second recipient group (for example management). The escalation layer and its wait time can be defined separately for each rule.
| Alarm Families | Energy/power (analyser, transformer, generator, UPS), water, climate (chiller, VRF), LoRa sensor |
| Notification | Microsoft Graph API + SMTP fallback |
| Cooldown | Configurable per rule (recommended: 30 min) |
| Silence Threshold | Default 30 min warning / 120 min critical (water: 60 / 240 min), configurable |
| History Retention | 30 days |
Intelligent alarm management without missing critical events and without mail storms.
Request a Demo → info@6steknoloji.com