Execution Scheduling

Execution Scheduling refers to a method of scheduling that considers in-transit activity reported against a load. In this mode, scheduling identifies the last reported location/date/time for the load and then projects the schedule from that point forward. All elapsed time up to that point will be categorized (as best as possible) as driving, loading, unloading, waiting, off-duty, etc., and can be viewed separately from the planned elapsed timings.

Scheduling in this mode will not fail for a load even if it appears that shipment pick-up dates, shipment delivery dates, appointments or dock commitments cannot be honored. “Best case” ETAs will be captured, regardless of the fact that scheduling will have “failed”. A violation alert will be triggered for the load. The expectation is that the alert will prompt the shipper to take some form of corrective or reactive action which could include one or more of the following:

  • Re-sequence remaining delivery stops to ensure that critical freight is not delivered late
  • Adjust staffing at locations to accommodate late arriving freight
  • Divert freight to another location
  • Modify an appointment or dock commitment
  • Notify stakeholders that freight will be late

Execution scheduling considers the same Hours of Service (HOS) constraints that scheduling uses during planning. This includes meal breaks, if these have been configured.

The most recent sets of scheduling results in both planning/confirmation and execution modes will be retained in the load schedule table.

Time based rating will be possible using durations computed in planning or execution modes.

When scheduling has been disabled for a load, UI and API users will now be able to override both planning and execution values when working with Load Scheduling Overrides.

To enable, execution scheduling, set the Scheduling Mode field in Global Settings to Execution. See Scheduling Controls.

Planning scheduling mode will always be used when operational status for the load is Open, Planned, Tendered or Tender Rejected.

Execution scheduling mode will always be used when operational status for the load is Picked Up, In Transit or Completed.

If operational status for the load is Tender Accepted or Confirming, then Execution mode will be used only if at least one of these events has been reported for the load, else Planning mode will be used:

  • Driver Check-In at the first pick-up stop (Note: If Driver Check-Out has been performed, then load will have advanced to In Transit operational status)
  • Driver Check-In and/or Driver Check-Out at a separate Tractor or Trailer Domicile
  • Carrier ETA with current location
  • Carrier ETD at the first stop, Tractor Domicile, or Trailer Domicile
  • Carrier current location update

For trips, evaluation of status eligibility will be based on the first load of the trip itinerary.

For bookings, evaluation of status eligibility will be based on any load attached to the booking.

Loads scheduled using a tariff service that has a “Scheduling Mode” of Delivery Schedule will qualify for execution mode scheduling.

Loads and trips where financial status is Voucher Created or greater will not be eligible for execution scheduling if the tariff /service combination previously assigned to the transaction (i.e. by an earlier RR&S call) has any tariff charges where the “Time Based Rating Units Source” is Execution. A control in the A/P Voucher Versions table will allow voucher generation to be delayed until all operational activity is complete. You can use the voucher version control when you need to use execution times as the basis for rating. If a load or trip is not eligible for RR&S due to the condition described above, a severe RR&S error condition will be generated. In this case, the “Execution Scheduling Status” for the load will be Financial Status Restrictions. This scenario will be identified in TM and if applicable, scheduling will not be performed.