Scenario: a foreign driver at the plant gate
The production plant receives several dozen deliveries a day from carriers from several countries. The driver arrives after an overnight trip, has a pre-arrival notice for a specific warehouse, but sees the internal roads for the first time. The signs are in Polish, and security at the gate has a few dozen seconds for the check-in, because another vehicle is waiting behind.
Until now this ended in one of two ways: the driver followed a random vehicle, or security handed over the route on a sheet of paper. In both cases nobody could be sure that the truck would not turn into a zone it was not allowed to enter. The scenario below shows how a locator with voice navigation closes this gap.
What security sets when issuing the locator
When the locator is issued, security records three decisions for each device: whether the driver wants voice navigation, in which language, and whether the delivery is under special supervision. This is one action at the barrier, done on the same screen where security registers the issue anyway.
There are 10 languages available: Polish, Ukrainian, English, Russian, Romanian, Bulgarian, Slovak, Czech, German and Hungarian. Polish is the default. The security dispatcher can therefore ask the driver for the language with one question and point to the right position on the list, instead of explaining the route with gestures.
- switching navigation on saves it together with the chosen language,
- switching navigation off clears the chosen language,
- switching navigation on without a language choice sets Polish,
- a delivery under special supervision is a separate flag, independent of the language.
Unnecessary ramp searching with 100 deliveries a day (example)
What the driver hears at intersections
On plant grounds, the driver with a BLE locator hears the prompts 'left', 'right', 'straight ahead' and 'turn back', played by the locator application in the chosen language. The instruction is not a built-in route: it comes from a decision matrix in which the plant administrator has described what to say at which intersection for a given warehouse.
The 'left' or 'right' direction is calculated by the system from the driver's actual approach segment relative to the recorded absolute direction. As a result the same intersection works correctly regardless of the arm from which the vehicle approaches. Each intersection speaks at most once during a single delivery, so the driver does not hear the same instruction twice.
Why the prompt is reliable and when the system stays silent
A prompt at an intersection is triggered by a transmitter on the approach, confirmed in two consecutive location readings. A single distant signal is rejected, so the driver does not get a prompt for an intersection they have not yet reached. The position comes from the signals of many BLE transmitters averaged on the map, and it works without GPS.
When the system cannot establish which side the driver approached the intersection from, it stays silent and records this in the log. A wrong direction is worse than no prompt, because it leads the vehicle into the wrong zone. The voice prompt is sent as a push message valid for 55 seconds: if it does not arrive in that time, it expires and does not sound a few minutes later, when the phone regains coverage.
Effect: less searching for the ramp and a visible vehicle on the map
The security dispatcher sees the vehicle on the online map. A vehicle with navigation in a language other than Polish is red, so it is immediately clear which trucks the system guides and which need a question. A vehicle under special supervision is black and takes colour precedence.
A sample calculation shows the scale of the problem: 100 deliveries a day with 10 minutes of unnecessary ramp searching each give 1000 minutes, or about 16.7 hours of vehicle and driver time per day. Every minute saved means fewer foreign vehicles on roads used by pedestrians and forklifts.
Conclusions for the plant
Two elements matter most: setting the language when the locator is issued, and a well-described intersection matrix. The first takes security a few seconds, and the second is prepared once by the plant administrator and tuned in the panel without deployment and without a restart.
Where drivers change every day, the value lies in the fact that nobody needs to know the plant. The knowledge of the roads sits in the matrix, not in the head of the security guard who happens to be on shift.
Time spent on unnecessary ramp searching
| Parameter | Value |
|---|---|
| Deliveries | 100 deliveries a day |
| Unnecessary ramp searching | 10 min per delivery |
Result: 1000 minutes, or about 16.7 hours of vehicle and driver time per day.
Note: Example calculation on the assumptions in the table; in a specific plant the values should be measured on its own deliveries.
Video
Frequently asked questions
Does the driver have to install their own application?
In this scenario the prompts are played by the locator application issued at the gate. Security saves the settings per device, so the driver configures nothing themselves.
What if the driver only speaks a language outside the list of 10?
Security leaves navigation switched off or chooses the closest language. Switching navigation off clears the language, and the delivery is still visible on the map.
Does the system replace road signs in the plant?
No. It supplements them with voice prompts and vehicle visibility on the map. The road markings stay unchanged.
Do transmitters have to be placed in the middle of the intersection?
No. The intersection is a geometric point, and the prompt is triggered by transmitters on the approach, whose signal carries tens of metres.
Want to test navigation on your deliveries?
Describe your road layout and the number of deliveries a day. We will show how to set up the intersection matrix and the prompt language for your plant.
Let's talk