InnerWeb
Skip to main content

Recommendations: SOS response at a site without people

When an SOS comes from a site where, apart from the person calling, nobody is present, the dispatcher cannot count on a neighbour from the hall. Below are six recommendations for the order in which the central dispatcher should act, based on how an SOS from the watch actually behaves in the system.

3 s
SOS countdown with the option to cancel
Source: product documentation (card)
52 s
median time to close an alarm on site at a plant with staff
Source: production reference (card)
7 z 10
stops cancelled by the worker alone
Source: production reference (card)

Who these recommendations are for

For central dispatchers and shift leaders in organizations where technicians work alone at remote sites: stations, pumping stations and warehouses outside working hours. The order of actions matters, because without a person on site every minute of delay is time in which no one knows what happened.

The recommendations describe the dispatcher's procedure. They do not replace the risk assessment of the site or its safety instructions, and the system provides evidence of the course of events, not a guarantee of the outcome.

First, understand what the SOS is

SOS is triggered on the watch by a triple press or by holding the button, with a 3-second countdown that allows a mistake to be cancelled, also from the watch face. After the countdown, the SOS is an active and unconditional signal: it opens its own SOS permit, alerts supervisors with a notification and on the online map, and the worker's movement does not clear it. A person closes it.

This distinguishes SOS from the no-movement alarm. The server infers no movement from the pulses, and that alarm closes by itself when movement returns. SOS has no such automatic close and no dependence on no-movement settings, so the dispatcher should not treat the two events with the same procedure.

Time thresholds of events in the system

Time thresholds of events in the systemHorizontal bar chart: SOS countdown 3 seconds, warning 20, no-movement alarm 50, median close 52, response team notified up to 120 seconds.0255075100125sSOS countdownSOS countdown: 3 s3No-movement warningNo-movement warning: 20 s20No-movement alarmNo-movement alarm: 50 s50Median close on siteMedian close on site: 52 s52Response team notification(upper limit)Response team notification (upper limit): 120 s120
Source: Product documentation and parameters of a working production deployment; no-movement alarm = 20 s + 30 s

Six recommendations in order of action

The order follows the first minutes after the alarm.

1. Confirm receipt of the alarm immediately

The dispatcher's first move is to mark the alarm as accepted, so that other recipients of the notification do not duplicate actions. Assign one person as the lead of the event.

2. Check the last position on the online map

The SOS is visible on the map. The dispatcher immediately sees at which site, and in which place, the worker was last heard. If the worker went out of transmitter range, the platform substitutes the last known location, so the information about the place does not disappear.

3. Do not wait for the worker to respond

The worker's movement does not clear the SOS, so lack of movement or the worker's presence does not settle the situation. Since the alarm is unconditional, the dispatcher acts as if help is needed until a person closes the event.

4. Send the nearest person or the emergency services

At a site without staff, help has to travel. Name the nearest technician who knows how to reach the site, or call the emergency services straight away if the description of the event points to it. Record the decision on who was called in the event.

5. Keep communication going and repeat calls

In a working production deployment, an automatic dialer calls the designated people and repeats until someone answers. Apply the same principle manually: do not stop trying after the first unanswered call.

6. Close the event deliberately and record the course

A person closes the SOS. Closing should happen only after the worker's safety is confirmed, ideally by contact or presence on site. After the event the system generates a report with the time, the location and the course of the escalation, which is used for review.

Time thresholds for comparison

For orientation, here is how fast the process works. The SOS countdown lasts 3 s. In a working production deployment the no-movement alarm warns after 20 s without movement, after a further 30 s without a response it raises an alarm, and the time from detection to notifying the response team is under 2 minutes. In a production reference covering over 3,400 hours of watch time, the median time to close an alarm on site was 52 s, and workers cancelled 7 out of 10 stops themselves.

These figures come from a plant with staff. At a site without people, the travel time for help will be longer, which is exactly why a fast decision to call outside help matters more.

Mistakes to avoid

The most common errors are closing an SOS remotely without contact with the worker, treating an SOS as a no-movement event, and having no single person leading the event. Each of them can be eliminated with a short dispatcher instruction and a test alarm at a pilot site.

Video

Frequently asked questions

Does movement by the worker clear an SOS alarm?

No. SOS is an active and unconditional signal, so movement does not close it. A person closes it.

Does SOS depend on the no-movement settings?

No. SOS has no automatic close and no dependence on the no-movement settings, unlike the no-movement alarm.

What will the dispatcher see when the worker is out of transmitter range?

The last known location, because the platform substitutes it when the node does not hear any transmitter.

Set up an SOS procedure for sites without people

We will show the SOS alarm on the map and walk your dispatcher through the order of response for a chosen site.

Let's talk