rdAlarm

A recipient drowning in alarms stops opening any of them, and the alerting set-up becomes decorative; to sort, native routing forces you to multiply alarm classes that nobody understands three years later.

rdAlarm enriches a Niagara station's alarm routing: a recipient receives only the alarms that satisfy conditions on any of the alarm's information — priority, class, source, state, message content. Conditions combine, are configured with no development, and add to existing routing without touching what triggers alarms.

• Each recipient receives only what concerns them, and so keeps reading their alarms.
• Sorting works on any of the alarm's information, including message content.
• Fewer alarm classes created to work around routing, so a station that is easier to take over.
• No development: when the on-call rule changes, you reconfigure.
• Native routing stays in place: what works keeps working.

• Night on-call: forward only what justifies waking someone up.
• Multi-tenant portfolio: each operator receives their own scope.
• Subcontracting by package: HVAC to HVAC, electrical to the electrician.
• Cutting a flow that became unreadable without risking a missed real event.

Niagara ≥ 4.13.x

0.7.2

on request

rdAlarm

See the range