Execution Scheduling

This section describes the criteria used to determine the effective scheduling mode when the Scheduling Mode field is set to Execution in the Global Settings page. 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 that are scheduled using a tariff service that has a “Scheduling Mode” of Delivery Schedule will qualify for execution mode scheduling.

While most loads that require execution scheduling will be in the In Transit operational status, the process will also be triggered for loads in other operational statuses:

  • Carriers can optionally supply an ETA for the first pick-up stop when accepting a tender, or when revising a previously accepted tender that is still active. Therefore, execution scheduling will be invoked for loads in Tender Accepted operational status.
  • For domicile-based loads, to be able to incorporate driver check-in and driver check-out activity at separate domiciles prior to driver check-out being reported for the first pick-up stop, execution scheduling will be triggered for loads in the Tender Accepted or Confirming operational status.
  • For any load, to be able to accommodate loads where driver check-in has been reported for the first stop but driver check-out has not been provided, Execution scheduling needs to be triggered for loads in the Tender Accepted or Confirming operational status.
  • While a round-trip load or trip will advance to the Completed operational status once pick-up and delivery has been reported at all stops, the driver will still log additional driving time while returning to the origin domicile or location. This means that a driver check-in event will be reported at the original starting location so that execution scheduling can fully represent all actual driving activity.
  • When a load moves to the Completed operational status, there could still be related loads that might be impacted (for example, other loads on a trip, web scheduling scenarios).

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. 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.