Skip to content
DigiOS.
DigiWarehouse · Alarms and notifications

Alarms that reach the right person, and notices that never pretend to be alarms.

A cold room drifts, a conveyor jams, a dock door stays open. DigiOS raises each one once, with a priority and an owner, and walks up an escalation ladder until somebody answers. Shelving needs a reason and a time limit. Everything that is not an alarm is a notice, and notices are summarised.

One alarm, from raise to normal

  1. It is rationalised once.

    Every alarm has its cause, its consequence, the corrective action, the time to respond and a priority, written down before it ever sounds.

  2. It is raised once.

    Each alarm has one source: the PLC's own alarm, a device, or a rule over several readings. The same condition never raises two alarms.

  3. It is answered.

    Acknowledging logs your name and the time, and never clears the cause. First-out marks the alarm that started a trip, and a flood is counted and grouped instead of scrolling past.

  4. It is shelved, with a reason.

    A shelved alarm carries a reason and a time limit. It sits in its own list, and it comes back by itself when the time is up.

Alarm summarySee what is wrong in priority order, which alarm started it, who owns each one, what is shelved and until when, and who it goes to next if nobody acts.

Every alert has an owner, and a ladder.

If the owner doesn't answer, the next person is called, then the shift supervisor. The ladder is set per alarm and per shift, so a cold-room excursion at 3 a.m. goes to whoever holds the night.

  • An owner on every alarm, by role and by shift.
  • A next step and a time limit at each rung.
  • The path each alarm took is kept with the alarm.
An alarm goes to its owner, then the next person, then the supervisor, and it can be shelved on the side only with a reason and a time limit.

An alarm and a notice

What it is
An alarmSomething abnormal that needs a response now: a cold room out of range, a jam, a trip.
A noticeAn approval waiting, a dock appointment overdue, a thread, a late order.
Who is interrupted
An alarmIts owner, then up the ladder.
A noticeNobody, until the summary you chose.
How it is shown
An alarmOn the alarm summary, with its priority and its owner.
A noticeIn the periphery of the screen, and in a scheduled summary.
Can it be hidden
An alarmOnly by shelving, with a reason and a time limit.
A noticeYes: your team sets the summary and the quiet hours.

An alarm is never batched or hidden.

Nothing sits between a raise and the person who must act. Groupings and summaries only order and annotate what a person sees.

Alarm health, from the alarms themselves

The numbers a review needs, kept as the alarms happen.

Rate and floods.

How many alarms an operator gets in ten minutes, and how often a flood buries the screen.

Stale and chattering.

Alarms standing unanswered, and alarms that raise and clear again and again.

Top offenders.

The alarms that account for most of the noise, so you rationalise those first.

Where each part stands

Parts of alarms and notifications and where each stands
PartWhere it stands
Alarm management in the ISA-18.2 way
An owner and an escalation ladder on every alert
Notices summarised, never alarms
Alarm health measures

Questions

Can an alarm be silenced for a while?

Yes, by shelving it with a reason and a time limit. It is listed while it is shelved, and it returns on its own.

Do you replace the PLC's alarms?

No. A PLC alarm stays the one source, and DigiOS adds the priority, the owner and the ladder.

Where do approvals and late orders go?

They are notices, with a priority and an owner, summarised on the schedule your team picks.

Tell us about your last bad night.

We'll set up the alarm summary and the ladder for the equipment involved.

Book a working session