Alarm & notification workflows

Design useful, traceable alarms with thresholds, duration and priority.

The need and approach

Sending a notification for every threshold crossing can cause alarm fatigue. Define how the alarm closes, who evaluates it and what happens when there is no response, alongside the trigger itself.

Data flow

Valid measurement or event → rule evaluation → alarm record → notification → human assessment.

Hysteresis manages oscillation around a boundary; duration filters manage short transitions. Acknowledgement and return to normal are different events. Missing data can be its own alarm condition.

Illustrative workflow

A short cold-room door opening and a sustained temperature rise are treated differently. Thresholds and durations are validated against product and facility requirements.

Questions for discovery

  • Which events need actual intervention?
  • How long must a threshold be exceeded?
  • How are priority and ownership assigned?
  • What happens when the notification channel fails?
  • What are the repeat, mute and closure rules?

Limits and field conditions

A sent notification does not prove that someone read it or intervened. Critical safety functions require independent consideration.

Common questions

Can existing equipment be used?

Suitability depends on the device interface, manufacturer documentation, access permission and a field test. Start by sharing model details and the signals that are available.

Which data do you need to see? Which process could work better?

Tell us about your equipment and your requirements. Let's explore a suitable approach together.

Let's talk about your project