Situation: issuing devices for a shift
The scenario concerns a plant where worn devices (watches, active cards, locators) are issued for a shift from an issuing point and return to multi-chargers after the shift. The dispatcher or storekeeper handles dozens of devices within a short window between shifts.
The case is a scenario modelled on the function documentation, without pointing to any specific plant. We describe the mechanism and illustrative figures, not the result of a single implementation.
Problem: the device does not signal that it is charging
Worn devices rarely report their real charging status. The heartbeat contains the battery level, but not always reliable information about whether the device is connected to power. Without this, a storekeeper cannot tell a charged device from one lying on a shelf with a flat battery.
In practice, the effect is issuing a device with a low battery to an employee, or long manual checks of every unit before a shift.
Time spent checking devices before a shift
Solution: inference from trend and location
The system combines two pieces of information: the location of the device and the trend of its battery level. When the device is at the location of a multi-charger and the battery is rising, the system concludes that it is charging. When the battery is falling, it concludes that the device has been taken off the charger.
The heartbeat from which the battery level comes is the cyclic message of the device: the beacons heard, signal strength, battery level and status. A beacon next to the charger acts as a reference point, saying that the device is in the charging place.
What the dispatcher sees on screen
A list of devices with their battery level and state: charging, taken off the charger, in use. This way, before a shift, devices are issued starting from the highest level, not the first ones to hand.
Limitations to be aware of
The inference is based on the trend, so it needs several successive heartbeats. Right after a device is connected, the state may still be out of date. The issuing procedure should therefore include a short waiting window, rather than a decision based on a single reading.
Effect: illustrative calculation
Assume 60 devices and 2 minutes of manual checking per device before a shift. That is 120 minutes of work. If the status list reduces the check to a review of the screen and a manual check of only 10 devices with a low battery (20 minutes), the saving is 100 minutes per shift. These are illustrative assumptions, and each plant should measure its own times during the pilot.
Conclusion: the charging status does not have to come from the device if the system knows its location and battery trend. The condition is a correctly recorded location of the multi-charger.
A practical implementation note concerns the placement of charging points. If the multi-chargers stand in one room, one location and a beacon nearby are enough. If they are spread across several issuing points, each of them should have its own entry, so that the system does not confuse a device lying on a shelf with one connected to power. When the room layout changes, the entry must be updated in the same way as the location of any other transmitter.
Checklist
Video
Frequently asked questions
Why does a device not report charging on its own?
Many worn devices rarely pass on a reliable charging status. That is why the system infers it from the battery trend and the location.
What if the charger stands in a place without a beacon?
The inference requires the device to be at the location of a multi-charger. Without a correct location entry, the charging status will not be reliable.
Does the list replace a visual check?
Not fully. The list shortens the check and points to the devices to inspect, but the issuing procedure should still allow a manual check.
See the device fleet status on screen
We will show the list of devices with their battery level and inferred charging status, and help you set the locations of the multi-chargers.
Let's talk