http://in.compucrete.com/index.php?action=history&feed=atom&title=Projected_Load_Handling 2026-05-15T17:00:35Z Revision history for this page on the wiki MediaWiki 1.40.0 http://in.compucrete.com/index.php?title=Projected_Load_Handling&diff=520&oldid=prev 2023-07-14T13:00:35Z

<p>1 revision imported</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 13:00, 14 July 2023</td> </tr> <!-- diff cache key my_wiki:diff::1.12:old-519:rev-520 --> </table>

WikiAdmin http://in.compucrete.com/index.php?title=Projected_Load_Handling&diff=519&oldid=prev 2017-01-10T00:02:10Z

<p>1 revision imported</p> <p><b>New page</b></p><div>==Projected Load Basics==<br /> In dispatch, each order is broken down into projected loads. <br /> A projected load record contains:<br /> *Scheduled Date and Time to arrive on site<br /> *Quantity to be delivered<br /> *Alert Message<br /> *Links to the Order<br /> <br /> Once a delivery has started, the order will additionally have:<br /> *Status Information where status 1 through 8 range from ticketed to returned<br /> *Links to Ticket<br /> *Target_Return_Offset<br /> <br /> When an order is first created, all of the orders are scheduled based on the following factors:<br /> *Original Scheduled Time<br /> *Spacing<br /> *Load Size<br /> *Order Quantity<br /> <br /> After the initial schedule is created, each load can be modified to change:<br /> *Schedule Date/Time<br /> *Load Size<br /> *Alert Message<br /> <br /> Depending on the change, following orders may be rescheduled.<br /> <br /> ==Project Load Scheduling==<br /> <br /> ===Schedule: Begin and End Times===<br /> Projected load times are scheduled based on the begin and end times for an order.<br /> The begin and end times are based on:<br /> *The plants open and close time of no begin and end time are setup for the order<br /> *The order begin and end time<br /> <br /> ===Roll Forward===<br /> When the roll forward flag is set, the End of Day (Begin of Day?) procedure will reset all unscheduled loads based on the order begin and end times.<br /> <br /> ==Project Load ReScheduling==<br /> <br /> ===Events that Trigger Rescheduling of Projected Loads===<br /> *Change in order quantity<br /> *Change in spacing<br /> *Change in load size<br /> *Change in order delivery time<br /> *Change in delivery time for specific load<br /> *Delivery quantity varying from scheduled quantity<br /> <br /> ==Active Load Handling==<br /> <br /> ===Target Return Offset===<br /> As each status changes, the app server updates the Target Return Offset field by comparing the actual vs target time. This is used to update the projected return time of the truck and to update the demand graph.<br /> <br /> ===Order Projected Load Offset===<br /> (Future) As actual status times change for active orders, the projected load offset will be used to track &quot;soft&quot; schedule changes for unscheduled loads.</div>

Intra>User