Playbook
How to Calculate Truck ETA and On-Time Verdicts.
When the plant, the carrier and the customer each compute ETA differently, every delay becomes an argument.
The problem
ETA promises built on maps that ignore how a particular truck actually moves.
The signal to watch
Pending km against the truck’s observed speed, and a written verdict rule against the promise date.
The playbook
- With no pings, assume 250 km per day.
- Once pings arrive, use the speed this truck has managed since billing, for example 600 km in 3 days = 200 km/day.
- ETA = pending km ÷ observed speed; for example 400 km ÷ 200 km/day = 2 days left.
- Verdict against the promise date in whole calendar days: ≤ 0 on time, +1 delay, +2 or more super delay.
- ATA, the contractual test: did the trip finish within 7 days of the promise, with no projection at all?
How to measure it
Report on-time, delay and super delay shares by carrier and lane, and the ATA success rate for customer audits.
In SCM for Manufacturers this runs on the same record as every other step from indent to settlement. Related: OTIF vs fill rate, GPS integration.
Questions
What is the difference between ETA and ATA?
ETA is the estimated arrival, projected from pending distance and speed. ATA is the actual arrival, used for the contractual test.
What default speed is used when a truck has no GPS?
SCM for Manufacturers assumes 250 km per day until pings arrive, then switches to the truck’s observed speed.
See it on your own data. SCM for Manufacturers puts the plant gate, carriers, RDC stock, cold chain and OTIF on one control tower. Book a 30-minute working session with an engineer.