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
Latest Flavor of the Month: Send Agains
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="pretzel_man" data-source="post: 768502" data-attributes="member: 927"><p>Dill,</p><p> </p><p>Again, I don't know your situation but I think I need to stick ot my point....</p><p> </p><p>Sounds like in your case the problem is the dispatch, right? They needed to break up a route and picked one that generated more work than the original route? They created a poor dispatch, right?</p><p> </p><p>Changing the number of routes needs to be done right. Doing it wrong creates a pocket dispatch. That pocket dispatch generates a lot of additional miles.</p><p> </p><p>The dispatch is absolutely the responsibility of the local operation. I wonder if the PDS knows how to dispatch per loop concepts? Do the loops make sense? Is the trace right?</p><p> </p><p>I know that you don't know this and its not your job. It is the job of local management though. When the SPC target is made, it assumes that the dispatch can be adjusted per the CD methods. If that is not true, SPC will be very difficult to attain. Again, back to the original cause, management that knows how to create a dispatch...</p><p> </p><p>You do bring up a very good point however. The biggest variable is miles and the systems do not help there. The PDS is not warned if a pocket dispatch is going to create excess miles. </p><p> </p><p>Of course, there is another metric for this. It looks at stops per sequence break.... We can hold off discussing that metric for a while.</p><p> </p><p>P-Man </p><p> </p><p>(I guess we will see if paragraphs work this time)</p></blockquote><p></p>
[QUOTE="pretzel_man, post: 768502, member: 927"] Dill, Again, I don't know your situation but I think I need to stick ot my point.... Sounds like in your case the problem is the dispatch, right? They needed to break up a route and picked one that generated more work than the original route? They created a poor dispatch, right? Changing the number of routes needs to be done right. Doing it wrong creates a pocket dispatch. That pocket dispatch generates a lot of additional miles. The dispatch is absolutely the responsibility of the local operation. I wonder if the PDS knows how to dispatch per loop concepts? Do the loops make sense? Is the trace right? I know that you don't know this and its not your job. It is the job of local management though. When the SPC target is made, it assumes that the dispatch can be adjusted per the CD methods. If that is not true, SPC will be very difficult to attain. Again, back to the original cause, management that knows how to create a dispatch... You do bring up a very good point however. The biggest variable is miles and the systems do not help there. The PDS is not warned if a pocket dispatch is going to create excess miles. Of course, there is another metric for this. It looks at stops per sequence break.... We can hold off discussing that metric for a while. P-Man (I guess we will see if paragraphs work this time) [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
Latest Flavor of the Month: Send Agains
Top