Situation at a logistics site
The case described is a scenario modelled on typical service reports at warehouse facilities, without pointing to any specific plant. The dispatcher sees the routes of forklifts and vehicles on the map. On one of them a spike appears: the route points jump into the interior of the warehouse, and the next point returns to the road.
For the dispatcher it looks like a vehicle fault or theft, for the service like a system error. Both conclusions can be wrong: a typical source is the configuration entry of a single beacon.
First cause: a beacon recorded in the wrong place
A navigation beacon recorded in the system in the wrong location, for example inside the warehouse instead of by the road, produces a so-called route jump on the map: a spike to the side and a return. The system calculates the position from the signal correctly, but assumes the transmitter hangs where it was entered.
The display name of a beacon comes from the location assigned to it, and a location name has a limit of 30 characters. This matters, because service often tells apart beacons by name, and with a shortened name it is easy to confuse two similar entries.
How to diagnose it
A jump is diagnosed 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: if the vehicle was earlier by the road, the beacon entry that appeared in the spike is in the wrong place.
- open the vehicle's route and find the spike point
- check the previous and the next point of the same vehicle
- read the name of the beacon at the spike point
- compare the physical mounting place with the entry in the system
- correct the beacon location and check the next pass
Example number of false spikes per week
Second cause: two devices with the same identifier
If after correcting the entry the jump disappears in one place but appears in another, suspect a duplicate. When two physical devices transmit the same identifier, changing the entry in the database moves the error to another place instead of removing it. The system sees one identifier, but the signal arrives from two points.
The fix is to remove the physical duplicate: find the two beacons with the same number and switch off or reprogram one of them. Changing the database entry will not solve the problem, because it only changes where the error is visible.
How to tell the two causes apart
After correcting the location, check the route over the next passes. If the spike has disappeared, it was the first cause. If the spike has moved to another place or appears cyclically in two places, it is a duplicate identifier.
Effect and cost of the error
After the cause is removed, the vehicle route becomes continuous again. The dispatcher stops analysing false events, and service has a clear rule to follow. Example calculation: if 12 false spikes appear in a week, and analysing each takes the dispatcher 5 minutes, this is 60 minutes of work per week. These are illustrative assumptions, not data from a specific plant.
A conclusion for logistics sites: whenever a new beacon is mounted, it is worth making a control pass and checking whether the route is continuous, and recording the identifiers in a register to avoid a duplicate.
It is also worth writing one rule into the dispatcher's instructions: a route spike is reported to service with the vehicle number, the time and the name of the beacon visible at the jump point. Such a report lets service start with diagnosis instead of collecting information. After the cause is removed, it is good to review the routes from previous days, because the same faulty entry may have distorted earlier passes and affected the reports on stops.
Checklist
Video
Frequently asked questions
Does a jump mean a vehicle fault?
Usually not. Most often it is an incorrect beacon location entry or a duplicate identifier, not a fault in the device on the vehicle.
Why did changing the database entry not help?
With a duplicate, two physical devices transmit the same number. Changing the entry moves the error, and one of the transmitters has to be removed physically.
How can such errors be prevented?
Make a control pass with each new beacon, keep a register of identifiers and check location names for mistakes.
Let's plan a control pass of the beacons
We will help prepare a register of identifiers and a control pass procedure, so that location errors do not reach the dispatcher's map.
Let's talk