Home
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
Orion Forcing
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="35years" data-source="post: 2336900" data-attributes="member: 60822"><p>I didn't miss your point.</p><p>There were mileage estimates before ORION and even before RDO/EDD.</p><p>Every aspect of the job has been time and motion studied for decades.</p><p>Before ORION you had to be able to explain why you "broke trace" if it cost you miles.</p><p>Drivers with experience could always find ways (and were expected to do so) to cut miles by <strong>not</strong> following DOL, then later EDD/RDO.</p><p></p><p>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.</p><p></p><p>Management has always fiddled with the numbers to pressure drivers into running faster to make their production quotas.</p><p>Now they fiddle with ORION to try to make the drivers cut miles. Left bldg time is just one technique.</p><p>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.</p><p></p><p>Some management teams are now fiddling with ORION to project <strong>more miles</strong> 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.</p></blockquote><p></p>
[QUOTE="35years, post: 2336900, member: 60822"] 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 [B]not[/B] 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 [B]more miles[/B] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
Orion Forcing
Top