Where the jumps come from
A navigation beacon recorded in the system in the wrong location, for example inside a warehouse instead of by the road, causes a route jump on the map: a spike to the side and a return. The second typical reason is two physical devices with the same identifier. Moving the entry in the database then moves the error to another place instead of removing it, so the physical duplicate has to be removed.
How the dispatcher loses time
Every jump requires a check. The diagnosis is made by comparing the route point with the previous and the next point of the same vehicle: the previous point shows where the device really hangs. The comparison itself takes a short time, but the events repeat, because a faulty beacon triggers a jump every time a vehicle passes it.
Dispatcher time on jumps: before and after the correction
Assumptions of the example calculation
We assume a plant where the dispatcher reports or checks 15 jumps a week, and each check, comparison of points and note takes 16 minutes. Together this is 15 x 16 = 240 minutes, that is 4 hours a week. We assume a cost of the dispatcher's hour of PLN 70 (an example assumption).
The annual time is 4 x 52 = 208 hours, and the example cost is 208 x 70 = PLN 14,560 a year. These values result only from the assumptions, not from data of a specific plant.
What the correction returns
If the correction of a few incorrectly recorded beacons and the removal of identifier duplicates reduces the number of jumps by 80 percent (an assumption), 3 jumps a week remain. The time drops to 3 x 16 = 48 minutes, that is 0.8 hours a week. The recovered time is 3.2 hours a week, about 166 hours a year, which at PLN 70 an hour gives about PLN 11,650 a year.
The cost of the correction is mainly the service technician's time and possibly the replacement or removal of the physical duplicate. The calculation does not assign an amount to it, because it depends on the number of beacons and the access to the mounting places.
Hidden costs that we do not price
Jumps lower the trust in the map: a dispatcher who has repeatedly seen a faulty spike starts to question the position during an alarm. This cost is real but hard to count, so it is not included in the calculation. Similarly, we do not count the time spent on conversations with drivers who ask why the system shows them in the wrong place.
- Incorrect beacon records in the wrong location.
- Duplicate device identifiers.
- No procedure for reporting and correcting jumps.
How to start the correction
Collect from one week a list of jumps with the place and the time. For each one, compare the route point with the previous and the next. You correct the location of the beacon indicated as faulty, and for an identifier duplicate you remove the physical duplicate. After a week, count the jumps again and compare them with the database.
Dispatcher time on route jumps
| Parameter | Value |
|---|---|
| Jumps to check | 15 a week |
| Time of one check | 16 min |
| Cost of the dispatcher's hour | 70 PLN |
| Reduction of jumps after correction | 80 % |
Result: Before: 240 min a week (4 h, about PLN 14,560 a year). After: 48 min a week. Recovered about 3.2 h a week (about PLN 11,650 a year).
Note: Example calculation on assumptions; these are not data from a specific plant. Put in your own values.
Video
Frequently asked questions
Do these numbers come from a real plant?
No. It is an example calculation on explicit assumptions: 15 jumps, 16 minutes, PLN 70 an hour. Put your own values into the same formula.
Why does moving the entry of a duplicate not help?
Because it moves the error to another place instead of removing it. The physical duplicate has to be removed.
How quickly can a jump be diagnosed?
Compare the route point with the previous and the next point of the same vehicle. The previous point shows where the device really hangs.
Let's talk about the beacon layout at your plant
We will show the map, the readings and the configuration on your site plan. Book a short conversation with the InnerWeb team.
Let's talk