What the dispatcher sees when an employee disappears from the map
Loss of an employee signal is a situation in which the system stops receiving periodic reports from the employee's device. For the dispatcher it is the hardest moment, because the same picture, namely no update on the map, can mean two different things: an employee without connectivity or a device that has stopped working. This page describes how to tell them apart and what follows from a missing heartbeat.
The heartbeat is the periodic report from the device: it contains the list of heard transmitters, the signal strength, the battery status and the device status. It feeds the view of who is on site, the automatic joining and leaving of permits, and safety signals, including no-movement detection. When the heartbeat stream stops, most of the information about the employee stops with it.
The first question: connectivity loss or a fault
The dispatcher has three sources of clues. The first is the last heartbeat: if it reported a low battery, a power failure is the most likely cause. The second is the last position: if the employee was near the exit of the hall or in a zone without coverage at the last reading, the silence may simply come from leaving the range. The third is the watch event log, which after connectivity returns arrives in batches and lets you check what the device was doing during the silence.
The difference between the device time and the time the server received the entry shows how long the silence lasted once connectivity came back. If entries from the gap arrived later, the device was working and recording events, it just had no way to send them. If there are no entries from that time at all, and the device came back after a battery swap or charging, the most likely cause was a fault or a discharged battery.
An important practical rule: the dispatcher should not wait for the diagnosis before acting. The procedure should assume that a missing heartbeat in a high-risk zone is a reason to check on the employee, while the technical diagnosis runs in parallel.
Time scale of a signal loss
What a missing heartbeat means for other functions
A missing heartbeat does not only switch off the position on the map. It also halts the automatic joining and leaving of permits and no-movement detection, because these functions rely on the same stream. An employee who is actually lying motionless but whose device has no connectivity will not generate a no-movement signal in the system until connectivity returns. That is why a signal loss must be treated as a separate type of alarm, not as an absence of events.
On the server side, writing the heartbeat is protected by error handling, so that a fault in permission coordination does not interrupt the acceptance of positions. This means a problem with one function does not drown out the whole stream. It matters for diagnosis: if positions keep flowing but permissions do not update, the problem lies in permission coordination, not in the devices.
The diagnostic window and the limits of storage
The event log queue on the watch holds 89 entries, so a device offline for longer than about 2 hours loses the beginning of its own failure. This is a window, not an archive. The dispatcher and the service technician should know that the longer the silence, the fewer details the device keeps, which is why the first minutes after a loss of signal are the most valuable for reconstructing the cause.
In a live system there was a case in which a watch vibrated and operated for 26 minutes without sending anything to the server. Without a durable record of events, the sequence could not be reconstructed. Since then the log has been a permanent feature, and the dispatcher's procedure should use it as a second source alongside the map.
A simple procedure for the dispatcher
A sample layout of the procedure can be written in a few steps. Step one: check the battery level in the last heartbeat. Step two: check the last position and whether the employee was in a zone with coverage. Step three: contact the employee by radio or through their supervisor. Step four: if there is no contact within the time set in the instruction, send a person to the last known position. Step five: once the device is back in connectivity, read the log and record the cause in the service report.
The time limit in step four is set by the plant on the basis of a risk assessment. The system does not impose a single value, and the decision on the threshold should be taken by the health and safety manager together with security. It is worth setting a shorter threshold for a high-risk zone than for the office.
Video
Frequently asked questions
Does a missing heartbeat always mean a device fault?
No. It can mean leaving the coverage area, a discharged battery or a fault. The last battery level, the last position and the log after return decide.
Does no-movement detection work during the silence?
No, because it relies on the heartbeat stream. A signal loss is treated as a separate alarm.
How do you check whether the device was working during the gap?
Compare the device time with the time the log entries were received. Delayed entries mean the device worked without connectivity.
Who sets the response time threshold?
The plant, based on a risk assessment: usually the health and safety manager with security. The system does not impose a single value.
Let us plan the signal loss procedure
We will help you set the time thresholds and the escalation path for the dispatcher at your plant.
Let's talk