Missed my point.
When you say UPS used to go after guys more before Orion for running up miles, how did they really know unless it was excessive? There wasn't a mileage solution for the day before Orion, was there? Just asking. Was there a mileage estimate based on running regular EDD?
I didn't miss your point.
There were mileage estimates before ORION and even before RDO/EDD.
Every aspect of the job has been time and motion studied for decades.
Before ORION you had to be able to explain why you "broke trace" if it cost you miles.
Drivers with experience could always find ways (and were expected to do so) to cut miles by
not following DOL, then later EDD/RDO.
The only difference is now, by following ORION, you are doing the route less efficiently (as far as miles go) if you are an experienced driver, who knows how to adapt on a daily basis based on a myriad of factors. Now if they ask why you did it inefficiently, you just have to respond that you are following ORION.
Management has always fiddled with the numbers to pressure drivers into running faster to make their production quotas.
Now they fiddle with ORION to try to make the drivers cut miles. Left bldg time is just one technique.
The problem is that projecting unrealistic mileage numbers becomes counterproductive because drivers can't just skip break or run faster to make the mileage quotas like they can for the production quotas. So if drivers face harassment/intimidation/discipline over miles they will just follow ORION trace and break off for service failures, which is VERY inefficient and adds miles.
Some management teams are now fiddling with ORION to project
more miles so that the driver is at least close to the ORION solution/projection. ORION could have been a useful tool if it had been implemented as an alternative, rather than setting up hard and fast (85%) imperatives. I would have thought they learned their lesson with hard and fast (90%) EDD compliance when it was rolled out, which was later abandoned.