Projected Load Handling
Projected Load Basics
In dispatch, each order is broken down into projected loads. A projected load record contains:
- Scheduled Date and Time to arrive on site
- Quantity to be delivered
- Alert Message
- Links to the Order
Once a delivery has started, the order will additionally have:
- Status Information where status 1 through 8 range from ticketed to returned
- Links to Ticket
- Target_Return_Offset
When an order is first created, all of the orders are scheduled based on the following factors:
- Original Scheduled Time
- Spacing
- Load Size
- Order Quantity
After the initial schedule is created, each load can be modified to change:
- Schedule Date/Time
- Load Size
- Alert Message
Depending on the change, following orders may be rescheduled.
Project Load Scheduling
Schedule: Begin and End Times
Projected load times are scheduled based on the begin and end times for an order. The begin and end times are based on:
- The plants open and close time of no begin and end time are setup for the order
- The order begin and end time
Roll Forward
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.
Project Load ReScheduling
Events that Trigger Rescheduling of Projected Loads
- Change in order quantity
- Change in spacing
- Change in load size
- Change in order delivery time
- Change in delivery time for specific load
- Delivery quantity varying from scheduled quantity
Active Load Handling
Target Return Offset
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.
Order Projected Load Offset
(Future) As actual status times change for active orders, the projected load offset will be used to track "soft" schedule changes for unscheduled loads.