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
The Competition
FedEx Discussions
Peak 2017
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="59 Dano" data-source="post: 3201962" data-attributes="member: 23516"><p>There are ways around that. The easiest is to use an ad hoc route number, though it will cause time card/on-road problems. However, they wouldn't really be an issue since on-road productivity isn't tracked so strictly during peak. Proper notations would have to be made at some point in the process.</p><p></p><p>What you said would also work, again with proper notations being made. The issue of programming PPADs to work in the configuration you mention (route 123a works as a slave to route 123) gets brought up from time to time, only to end up behind something that's more important.</p><p></p><p></p><p></p><p></p><p>A runner works well when, as you said, the stop density justifies it. The goal is to avoid WDLs and have all Christmas freight delivered in time. If a station doesn't have the threat of rollover freight then there's no reason to have runners. If a courier stays on the truck and has the runner do all the running, then there's no need for a runner.</p><p></p><p>The only real benefit to having runners is that it's better to be safe than sorry from a perspective of getting freight off by the due date. If the density isn't there then the "proper" use of a runner is that he and the courier split up the legwork on a route to delay the onset of fatigue. Runners are expensive but a decent insurance policy against rollover WDL freight.</p></blockquote><p></p>
[QUOTE="59 Dano, post: 3201962, member: 23516"] There are ways around that. The easiest is to use an ad hoc route number, though it will cause time card/on-road problems. However, they wouldn't really be an issue since on-road productivity isn't tracked so strictly during peak. Proper notations would have to be made at some point in the process. What you said would also work, again with proper notations being made. The issue of programming PPADs to work in the configuration you mention (route 123a works as a slave to route 123) gets brought up from time to time, only to end up behind something that's more important. A runner works well when, as you said, the stop density justifies it. The goal is to avoid WDLs and have all Christmas freight delivered in time. If a station doesn't have the threat of rollover freight then there's no reason to have runners. If a courier stays on the truck and has the runner do all the running, then there's no need for a runner. The only real benefit to having runners is that it's better to be safe than sorry from a perspective of getting freight off by the due date. If the density isn't there then the "proper" use of a runner is that he and the courier split up the legwork on a route to delay the onset of fatigue. Runners are expensive but a decent insurance policy against rollover WDL freight. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
The Competition
FedEx Discussions
Peak 2017
Top