InnerWeb
Skip to main content

Working Alone at a Station: Stillness Window and Escalation

A service worker has scanned in at a station and works alone for several hours. If they fall, nobody sees it, and the gate scan only says that they entered. Below are best practices for the head of technical services: how to set the stillness window, who receives the question, when escalation starts and how to write it into the procedure.

< 2 min
from stillness to team notification with location
Source: offer card: stillness with escalation
1 s
system reaction to the alarm
Source: offer card: stillness with escalation

Why the entry scan is not enough

The entry scan at a station records that a person entered and with what permissions. It says nothing about what happens after an hour. Working alone at a station, in a switchgear or in a boiler house is a classic risk: a fall, an electric shock, fainting. The time from the event to help determines the consequences, and without a system it lasts as long as the next planned check.

The head of technical services should therefore complement access control with a second mechanism that starts working from the moment of entry: stillness detection with escalation.

How stillness with escalation works

BLE transmitters register the lack of movement, the application asks the employee whether everything is all right, and the lack of a response within a configurable window starts the next stage. The notification to the response team with the location on the map follows in under 2 minutes, and the system's reaction to the alarm takes 1 second.

The heartbeat of a beacon or tag carries signals from the transmitters received, the signal strength, the battery and the status. From these the system calculates the employee's position in real time and drives stillness detection, so the dispatcher sees not only the alarm but also the place.

Time to team notification: planned check versus stillness

Time to team notification: planned check versus stillnessComparison of an average 30-minute wait for a planned check with under 2 minutes to notification with stillness detection0102030minPlanned check every 60 min (sample calculation, average): Time to detection: 30 min30 minPlanned check every 60 min (samplecalculation, average)Stillness with escalation (upper limit): Time to detection: 2 min2 minStillness with escalation (upper limit)
Source: Sample calculation: assumed planned check every 60 minutes, on average half of the period; 2 min value from the offer card

Practice 1: match the stillness window to the type of work

The window is configurable and it is worth differentiating it. Work at a closed switchgear, where the service worker crouches by a cabinet, has a different natural rhythm than a round along the galleries. A window that is too short generates false questions and teaches people to ignore them; one that is too long loses its purpose.

Reasoning: the head of technical services knows the rhythm of their crews. Set the window based on the longest typical pause in movement for a given task, not on the default value. After the first month review the number of false alarms and correct.

Practice 2: first a question to the person, then escalation

The first stage is a question in the application to the employee. Most cases end with an answer, because the service worker is standing and reading a diagram. Only the lack of a response within the window starts the next stage: a notification to the response team with the location on the map.

Reasoning: direct escalation without a question wears out the response team. A question first is cheap, and if the person does not respond, the alarm is credible.

Practice 3: describe who does what after an alarm

The system delivers the notification and the location, and the procedure says who goes, who calls the person and who informs the dispatcher. Write roles by job title, not by name, and keep substitutes. An alarm at three in the morning must have an owner who is not on leave.

Reasoning: the under-2-minute time from stillness to the team notification makes no sense if the team does not know that the role is theirs.

Practice 4: check connectivity where there is no Wi-Fi

Switchgear, cable basement, boiler house: places where the phone application has no coverage. There the signal is carried by an active LoRa card, and the pulses reach the same stillness mechanism as the data from the application. A LoRa bridge translates the frames to the existing API, so a watch or card works without Wi-Fi.

Reasoning: a stillness system that works only where the phone has coverage protects the easiest places. Our solution for places without coverage is described on the page about stillness in a switchgear without Wi-Fi.

Practice 5: evidence for the audit

Record alarms, questions and reactions. When an auditor asks how you protect work done alone, you show the window configuration, the register of questions and the time from alarm to notification. The system provides the evidence, and the assessment of compliance stays with the plant.

Checklist

Video

Frequently asked questions

How quickly will the team learn about a stillness event?

The notification to the response team with the location on the map follows in under 2 minutes from the start of escalation, and the system's own reaction to the alarm takes 1 second.

Does stillness detection work where there is no phone coverage?

Yes, when the employee has an active card or a LoRa watch. The LoRa bridge translates the frames to the existing API, and the pulses reach the same stillness mechanism.

Can the stillness window be changed?

The window is configurable. We recommend setting it based on the longest typical pause in movement for the task and correcting it after a month.

Let's set stillness for your stations

We will go through the time windows, the roles after an alarm and the places without coverage using one station as an example.

Let's talk