The situation: a chemical plant and lone working
The case is generic and pseudonymised: a chemical plant in an international group, an essential entity under NIS2, about 2,000 employees, and a dozen or so external firms in maintenance. Operators and mechanics walk tank farms, pump stations and pipelines, often alone, also on the night shift.
The plant has a competent control room and a procedure, but the procedure assumes that the injured person will reach for a radio or phone themselves. In a faint, a fall from height or inhalation of vapours, that assumed action does not happen. That is why the plant wants a way of calling for help that takes a single gesture, and a second one that works when the person is unable to do anything.
The problem: who finds out first and after how long
In the old scheme the dispatcher learns about the event from a witness or from the lack of a reply to a radio call. Then he or she calls in turn the shift manager, the OHS coordinator, the rescue team and the head of maintenance. Each call takes several dozen seconds, and the list is dialled sequentially.
The second problem is evidence. After an event it is necessary to reconstruct who was notified and at what time, which for an entity covered by the national cybersecurity system and business continuity management is part of the documentation of response procedures.
Time to notify 12 people: manual and automatic
The solution: a rescue chain started from the watch
The worker wears a watch integrated with the InnerWeb system. The watch is integrated hardware, and InnerWeb supplies the software that handles the alarm and notifications.
SOS with one gesture and the option to cancel
The worker calls for help with a gesture on the watch button: a triple click or a long press. A three-second countdown follows, during which a mistake can be cancelled. This limits false alarms without losing speed.
Its own permit and the notification chain
An SOS always creates its own permit and starts the rescue chain: a notification to the team channel in the messenger and automatic PBX calls to the people specified in the configuration. The calls do not go to public services, so summoning the fire brigade or ambulance remains with the duty officer in accordance with the plant's procedure.
The alarm lasts until a person closes it. The worker's movement does not clear the SOS, because someone may have moved in panic or been carried.
The second track: the no-motion alarm
When the worker cannot press the button, the no-motion alarm operates. After a threshold is exceeded, the system sends push and e-mail notifications to the responsible people, creates an alarm permit from the ALARM template, marks the alarm on the location map and can trigger an external webhook, for example a call to the duty person. When the worker moves again, this alarm permit closes by itself.
Effect: an illustrative calculation of notification time
An illustrative calculation on these assumptions: the rescue chain has 12 recipients (dispatcher, shift manager, OHS coordinator, rescue team, maintenance, management). The dispatcher calls manually one after another, and each call takes 45 seconds on average including dialling and passing on the information. Result: 12 times 45 s = 540 s, that is 9 minutes until the last person is notified, not counting unanswered calls.
In the automatic variant, push and the team channel message reach everyone at the same moment, and PBX calls are made in parallel on four lines of about 25 seconds each. For 12 recipients that is 3 rounds of 25 s, so 75 s, about 1.3 minutes. To this is added 3 seconds of countdown on the worker's side. The difference in this calculation is about 7.7 minutes in favour of the automatic variant.
- Assumption 1: 12 recipients in the chain.
- Assumption 2: manually 45 s per recipient, in sequence.
- Assumption 3: automatically 4 lines in parallel, 25 s per call.
- Assumption 4: the time to decide to call the services and the rescue team's travel time are left out.
Lessons for the plant director and the OHS manager
First lesson: the SOS gesture must be simple and cancelling a mistake must be possible, otherwise workers will stop using it. Second: the no-motion alarm is needed as a backup track, not a substitute for SOS. Third: the chain should end with a person who closes the alarm, not with movement or the passage of time.
The fourth lesson concerns coverage. The alarm works where there is a network and location; in places without coverage a coverage solution and a test on site are needed. A full discussion of motion detection can be found in a separate article, and the alarming guide describes the channels and registers on which audit evidence rests.
Video
Frequently asked questions
Does SOS work outside network coverage?
We do not promise this without a coverage solution. In places without coverage an additional piece of infrastructure and a test on the plant site are needed.
Does the worker's movement clear the SOS?
No. An SOS alarm lasts until a person closes it. Only the alarm permit after a no-motion alarm closes by itself, when the worker moves again.
Who do the PBX calls go to?
To the people specified in the configuration, for example the duty officer, the shift manager and the rescue team. Calling public services remains a human decision.
Sources
Let us talk about alarming in your plant
We will show in a demo how to arrange channels, recipients and proof of dispatch. Write to Marcin Worecki, president of InnerWeb, or book a conversation through the form.
Let's talk