Alarm fatigue is a safety issue, not just an annoyance

When the alarm list is always full, the alarm that matters gets missed. Why alarm floods are a risk, and how to start cleaning one up.

On many existing buildings the BMS alarm list is never empty. Hundreds of alarms sit there, some for months. The people who are meant to watch it have learned, quite reasonably, to ignore it.

That is usually treated as an annoyance. It is more serious than that. An alarm system exists to tell someone, quickly, that something needs attention - a frost risk, a plant room flood, a failed pump on a critical system. If the important alarm arrives in the middle of four hundred unimportant ones, it may as well not arrive at all.

How it happens

What good looks like

The process industries have long-established guidance on alarm management, such as EEMUA 191 and IEC 62682. Buildings are different, but the principles transfer: every alarm should need a response, be understandable, arrive at a manageable rate and reach the person who can act on it.

Where to start

Export a month of alarm history and count alarms by source. In most flooded systems a small number of points create a large share of the noise. Fix the causes of the top ten - repairs, limits, delays - before touching anything else. Then agree a simple priority scheme, route alarms by role and add a short alarm summary to every service report.

The reward is not just a tidier screen. When the list is short and every alarm means something, people start reading it again - and the alarm that matters gets dealt with.

Our article Alarm rationalisation sets out a full clean-up plan, from measuring the problem to monthly alarm figures.

Read the alarm rationalisation guide

More news from 3EC

3EC logo