InnerWeb
Skip to main content

Plant Alarm System: A Step-by-Step Guide

An alarm whose delivery cannot be proven is only a declaration in an audit. This guide shows how to organise alarm types, recipients and channels (email, SMS, phone, push) in an industrial plant so that every message leaves a trace that supports NIS2 compliance and the Polish Civil Protection Act.

24 h
deadline for the early warning of a significant incident
72 h
deadline for the notification of a significant incident

Why a plant needs structured alarming

An industrial plant usually has several independent ways of sending alarms: a siren, a radio, a board in the control room, a messenger group and a list of phone numbers in a binder. Each of them works, but none answers the questions an auditor or an accident investigation board will ask: who received the message, when, through which channel, and whether they acknowledged it.

Legal pressure is growing from two sides. For entities covered by the Polish National Cybersecurity System Act (KSC), the amendment implementing the NIS2 Directive requires an early warning without undue delay and no later than 24 hours after a significant incident is detected, and an incident notification within 72 hours. To meet those deadlines, the right people inside the plant must first be alerted within minutes. In turn, the Polish Act on Civil Protection and Civil Defence brings alarm sirens and public address devices held by businesses into the system of notification, warning and alarming (art. 71).

Step 1: define the alarm types

Start with a short list of event types. The fewer types you have, the easier they are to drill. In most plants five families are enough, and each gets its own message template and its own recipient group.

  • Fire alarm and evacuation: covers the whole workforce, contractors and visitors on site.
  • Process failure or substance release: covers operations management, maintenance, plant emergency services and neighbouring installations.
  • Lone worker alarm (SOS, no-motion): covers the duty officer, the supervisor and the rescue team.
  • IT and OT cybersecurity incident: covers the security team, management and the people who contact the CSIRT.
  • Organisational notice (power interruption, changed entrance, drills): covers selected groups, without alarm mode.

Reporting deadlines for a significant incident

Reporting deadlines for a significant incidentTwo bars: 24 hours for the early warning and 72 hours for the notification of a significant incident.020406080hoursEarly warning: 24 hours24 hoursEarly warningIncident notification: 72 hours72 hoursIncident notification
Source: (amendment to the KSC Act implementing the NIS2 Directive)

Step 2: assign recipients to roles, not to names

A list of people ages faster than a procedure. Define the recipient by role instead: duty operator, shift manager, HSE coordinator, NIS2 officer, contractor coordinator. A name and a phone number are only the assignment of a role to a person on a given day.

For each role set a deputy and a time after which a missing acknowledgement triggers escalation. For alarms that matter for life safety, the deputy should come from another shift, not from the same one that is already not answering.

Step 3: choose the channels and their order

No channel is fully reliable. Email is good for details and links, SMS for a short signal, and the phone for people who must react immediately. The InnerWeb system handles these channels in one place, which lets you build a sequence and avoid guessing who sent what.

Email

The message shows who generated it and has a valid reply address, so the recipient knows whom to contact. Email notifications have a full preview in the permit wizard. Email is not the channel for the first signal, because a mailbox can be overloaded.

SMS with a log

SMS messages are sent through the operator in the 7-bit standard, so they fit in one segment and stay on the phone. Every SMS sent is recorded in a log with the operator's order identifier, and SMS statistics are visible among the plant metrics.

Phone with a call log

The system can start phone calls (reminders and alarms) and records them in a call log. It calls the people named in the configuration, not public services, so calling the fire brigade remains a human decision under the plant procedure.

In-app push

Push reaches people who have the app on their phone and is the fastest route to a shift manager in the field. Treat it as the first signal, and SMS and phone as the supporting layer.

Step 4: do not allow critical alarms to be switched off

Each user can choose which email notifications they receive, which limits message fatigue. Notifications that matter for safety, however, stay mandatory and cannot be turned off. When designing recipient groups, use this: leave organisational notices optional, and mark the alarms from the list of types in step 1 as critical.

Step 5: build the audit evidence

Proof of alarming consists of three elements: the template text, the recipient list on the day of the event and the dispatch log. The SMS log and the call log provide an audit trail and channel usage statistics, and emails have an identifiable sender. From them you can reconstruct the event timeline in a few minutes, without searching mailboxes.

Such a set supports meeting the requirement to document incident response and business continuity procedures, but it does not replace legal assessment. The scope of obligations of a specific plant is decided by the analysis of the entity and its entry in the register, and the Civil Protection Act does not create a single catalogue of obligations for workplaces.

Step 6: test and repeat

The first test will show that some numbers are out of date and some people do not know how to acknowledge receipt. Plan a quarterly test with rotating roles and record the results. Detailed drill rules are in the material on crisis communication, and the rules for automatic alarm triggering in the description of if-then rules.

Video

Frequently asked questions

Is one alarm channel enough?

No. Every channel has weak points: a mailbox can be overloaded, a phone muted and the network uneven. At least two independent channels reduce the risk that a key person will not see the alarm.

Does the system call the fire brigade or an ambulance?

No. It notifies and calls the people named in the configuration. Calling public services remains a human decision under the plant procedure.

Can an employee switch off all notifications?

No. The user chooses email notifications, but notifications critical for safety stay mandatory.

What should I show the auditor?

The message template, the recipient list from the day of the event, and the SMS log and call log. Together they reconstruct the alarm timeline.

Sources

Let us talk about alarming in your plant

In a demo we will show how to arrange channels, recipients and proof of dispatch. Write to Marcin Worecki, CEO of InnerWeb, or book a conversation through the form.

Let's talk