What the cost of wandering consists of
Driver wandering is not only the driver's time. The first component is the working time of the vehicle and the driver: every minute spent looking for the ramp is a minute missing from the delivery window schedule. The second is the queue behind it: if the ramp is waiting, the next vehicle waits on the yard. The third is risk: a driver searching for the way usually drives more slowly, but also brakes harshly, turns back and enters zones where they should not be.
The fourth component is hidden: the time of security and logistics staff who answer calls and walk out to the yard to show the way. Such a contact takes a few minutes, but it happens many times a day and rarely appears in any record.
The calculation below covers only the first component, because it can be measured from data the plant already has: the number of deliveries and the working hours of the ramps. The other components are worth adding as a note, without assigning them amounts.
Example calculation step by step
Starting assumption: 100 deliveries a day and 10 minutes of unnecessary ramp searching per delivery. Multiplying 100 by 10 gives 1000 minutes a day. Dividing by 60 gives about 16.7 hours a day consumed by vehicles and drivers who should be standing at the ramp or already leaving.
To translate this into money, multiply the hours by the hourly rate of a vehicle with its driver, which the transport department knows. We do not give an amount here, because it depends on whether the vehicles belong to the plant or to carriers, and on the contracts. The result in hours, however, does not depend on the rate, so it is convenient to start the discussion about purchasing from it.
Consider the spread as well: with deliveries from abroad and new drivers, wandering is longer than with regular carriers, so it is worth calculating several variants, for example 5, 10 and 15 minutes.
Hours spent searching for the ramp per day at 100 deliveries
What voice navigation changes in this calculation
Voice navigation affects one variable: the number of minutes spent searching per delivery. The BLE locator detects the driver position from signals of several transmitters, and messages at junctions give the direction, without GPS and without live routing. The effect depends on the quality of the decision matrix and on whether the driver hears the message in a language they understand.
We do not promise a specific reduction in time without measurement at your plant. A sensible method is a before-and-after measurement: the operator isolates an active delivery on the map and sees the route from the entry, the stops longer than one minute and the pin of the declared destination. From this data the actual time to reach the ramp can be calculated before and after deployment.
- measure the time from the gate to the ramp for a trial of several dozen deliveries
- compare it with the time in the first week after messages are switched on
- exclude deliveries under special supervision from the comparison
- count drivers with navigation in a language other than Polish separately
How to collect data for your own calculation
The number of deliveries per day can be found in the appointment system or in the gate log. If the appointment system is integrated, the system fetches the data of the planned delivery from the appointment card code and pre-fills the form, so you have both the number of deliveries and the planned ramp at the same time.
Wandering time is best determined from the difference between the time of entry and the time of arrival at the ramp, less the time needed for direct driving. You know the latter from test drives with an experienced driver. Stops longer than one minute, visible in the delivery route, will show the places where drivers most often get lost.
Record the results in a table: deliveries per day, minutes of searching, hours per day, hours per month for the assumed number of working days. Such a table is a clear attachment to an investment request.
Driver wandering time per day
| Parameter | Value |
|---|---|
| Deliveries per day | 100 deliveries |
| Unnecessary ramp searching per delivery | 10 minutes |
| Conversion | 60 min/h |
Result: 1000 minutes a day, or about 16.7 hours of vehicle and driver time.
Note: Example calculation on the assumptions above. It is not data from any plant; insert your own number of deliveries, searching time and hourly rate.
Video
Frequently asked questions
Does the calculation need an hourly rate?
Not at the start. The result in hours is enough for comparisons, and the transport department adds the rate, since it knows the cost of a vehicle with its driver.
Where do I get the ramp searching time?
From the difference between entry and arrival at the ramp, less the time of direct driving. A delivery route with stops helps to show where drivers got lost.
Does the system promise a specific time reduction?
No. The effect has to be measured at a given plant by comparing the time to the ramp before and after voice navigation is switched on.
Let us calculate it on your figures
Bring the number of deliveries and an estimate of the ramp searching time, and we will prepare a calculation sheet with your assumptions.
Let's talk