Scheduling/Overrides (Employee)

This screen displays detailed load and scheduling information.

Scheduling failure and overrides

Most of the rateable entities are scheduled as well as rated. In certain circumstances, especially when building complex loads with multiple stops, scheduling might fail, in turn causing routing and rating to fail.

It may be difficult for a user to know why scheduling has failed and what they need to change for scheduling to succeed. To address this, users have the option to override the scheduling for a load. When scheduling is overridden, routing and rating will be performed but scheduling results will not be returned.

Disable scheduling

In Load Properties, the Scheduling Active flag allows the user to disable scheduling for a load. This can be done at any stage during the load build process, even before rating.

Users can select carrier and service combinations that failed scheduling. This will disable the Scheduling Active flag and any subsequent rates for that load will be performed without invoking scheduling.

Note: Disable scheduling is not allowed for loads assigned to a booking or using booking service without hard committed primary schedule.

Scheduling information

If scheduling overrides are used there will be loads that have routed and rated successfully but have no scheduling information. This has implications for tendering loads, MBOL documents, and similar concerns. These concerns will be addressed:

• if scheduling data is available, it will be used
• if appointment data is available, it will be used
• if dock commitment data is available, it will be used
• the Scheduling Results / Time Overrides screen displays scheduling results in a read only format if scheduling was successful. If no scheduling results are available, then you can enter information here - note that all fields are optional.

  Note: The Scheduling Results section is not displayed for loads assigned to a booking and loads that are eligible for booking.

The information will be used as Input Values for time units for Time as a Rateable Entity and as the start date (pick at first stop) and end date (final drop) for the load in Load Tenders, MBOLs and Outbound 204s.

If required, these start and end dates can be outside the shipment pickup and delivery windows. If so, the pickup and delivery windows on the shipment will remain unchanged so that performance and on-time delivery can be monitored.

Note: Loads that have scheduling inactive will not be eligible for the CST process or eligible for being consolidated onto trips by the Optimizer.