InnerWeb
Skip to main content

Driver location tag pool: depleted devices at the delivery gate

A driver receives a location tag at the gate and drives into the yard, and a few minutes later the device stops reporting because it was flat. This scenario shows how the service tab for security displays devices that are offline or have a battery at or below 5 percent, before they reach the drivers' hands.

5%
battery threshold in the service tab
Source: feature sheet
30
tags in the pool in the example calculation
Source: example calculation

Situation: several drivers, several dead devices

This is a concept scenario, built on the behaviour of the deliveries and prior notice module, not a report from a specific plant. A duty guard works at the delivery gate. Every driver entering the yard receives a BLE location tag, which lets the dispatcher see the vehicle on an online map and guide the driver by voice to the correct dock. During the morning peak several drivers in a row receive devices that did not have time to charge after the previous shift.

The effects are twofold. The driver has no navigation, so he wanders around the yard, and the dispatcher does not see him on the map. In addition, the duty officer spends time establishing whether the lack of signal is the fault of the device, the driver or the coverage of the yard transmitters. A pool of tags whose condition nobody checks becomes the source of complaints that cannot be resolved.

Pool limited to the gate's transmitters

The driver receives a BLE location tag at the gate, and the tag pool is limited to the gate's transmitters. This arrangement clarifies responsibility: the drivers' devices are assigned to a specific issuing point, rather than scattered across the whole plant. When a driver returns from the yard, the duty officer knows which units to look for.

The position of a tag in the yard comes from the signals of several BLE transmitters averaged on the map, without GPS. Plant roads are covered with transmitters roughly every 100 m. This means the quality of the position depends both on the layout of the transmitters and on the state of the tag's battery, which is why the first check whenever visibility is poor is always the condition of the device.

Tag pool in the example calculation

Tag pool in the example calculationBar chart: a base of 24 tags, a reserve of 6 units, 30 units in the pool in total.0102030pcsBase (12 deliveries x 2): 24 pcs24 pcsBase (12 deliveries x 2)Reserve 25%: 6 pcs6 pcsReserve 25%Total in the pool: 30 pcs30 pcsTotal in the pool
Source: Example calculation based on the assumptions in the tag pool section

Service tab for security

The service tab shows devices that are offline and those with a battery at or below 5 percent, together with a recommendation to charge them. The duty officer does not have to check each tag one by one: he opens a single list and sees which units to take out of issue. This changes the nature of the work from reactive control to preventive control.

It is worth scheduling the review of the list. It is best done at the start of the shift, before the first delivery peak, and again after a large group of vehicles has returned. In the post instructions one sentence is enough: a device with a battery at or below 5 percent, or offline, is not issued to a driver; it goes to charging and returns to the pool after a check.

Why a 5 percent threshold helps

The battery threshold of 5 percent is not guesswork but a fixed rule visible on the list, so it does not depend on the duty officer's eyeball assessment. A tag below the threshold can switch off during a delivery, and then the parking stop and the driver's route preview are interrupted.

Example calculation: how many tags to keep in the pool

We assume example figures, not a result from a deployment: 12 deliveries on the yard at the same time, 2 tags per delivery because one truck may carry two drivers, and a 25 percent reserve for charging. The base is 24 tags, the reserve is 6 units, giving a total of 30.

The reserve is what allows devices flagged in the service tab to be taken out of circulation without stopping issuing. With too small a pool the duty officer faces a choice: give the driver a device on the edge of discharge, or halt entry. Both choices cost more than a few extra units in the pool.

Conclusions for the head of security

Battery condition is a matter of organisation, not of equipment. If the service list is checked at the start of the shift, a flat device does not reach the driver. If it is not, every report that a driver got lost in the yard has to be settled by guesswork.

It is also worth writing down who charges the devices, where, and after how long a unit returns to issue. The system does not manage the chargers, but it shows a status on which responsibility can rest, and that is usually enough to close the matter.

Video

Frequently asked questions

Where does the duty officer see which location tags are depleted?

In the service tab of the security panel. It shows devices that are offline or have a battery at or below 5 percent, with a recommendation to charge.

Is the location tag pool shared across the whole plant?

No. The pool is limited to the transmitters of the gate where the driver collects the device, which makes it easier to know which units to look for after a delivery is finished.

How does the system know where a driver with a location tag is in the yard?

The position comes from the signals of several BLE transmitters averaged on the map, without GPS. Plant roads are covered with transmitters roughly every 100 m.

Let us plan the tag pool for your gate

We will show the service tab in a demo and work out together the pool for your yard based on the number of simultaneous deliveries.

Let's talk