About Bump Runs and Rescheduling

Depending on how BTL is configured, some trips can be rescheduled and others may be moved directly to a bump run.

If the BTL Reschedule switch is set to ON, it immediately reschedules the trips that score more than the value specified for the BTL Reschedule Cost switch . Setting it to OFF moves the trips directly to a bump run, which is a temporary holding place for these trips until a more suitable trip can be found. Trips on a bump run must also score more than the value specified for the Bump Cost switch.

For example, if the BTL Reschedule Cost is 1000, but a trip scores only 950, the trip will remain scheduled on the same run. If the Bump Cost switch is set to 3000 and a trip scores 3500, it will be moved to the bump run to be rescheduled during the next Re-evaluate Interval, which requires the Re-evaluate Trigger switch be set to ON.

Bump runs can only hold the maximum number of trips defined in the Bump Run Trips Max switch. As a safeguard, the Bump Run Trips Over switch allows some extra runs to be added in case the maximum number of bumped runs has already been reached.

If provider costing is used (when providers are reimbursed for the trips they perform), runs may be moved to the bump run depending on the Bump Run PC Max and Bump Run PC Over switches.

Note: Refer to the PASS-CT System Administrator and User Guide for more information about providers.

Because some sites and clients may have trip notifications and reminders set up, the time window during which trips can be bumped needs to be defined. The Window > Date Offset switch specifies the scheduling window when trips can start to be bumped (e.g., today, tomorrow, the day after), while the Window > Days switch specifies how many days a trip can remain on a bump run. For example, trips may be bumped starting the day it is scheduled and left on the bump run for up to 3 days.

The Bump Window Cut off For Next Day switch specifies the cut off time to prevent the Bump Manager from proceeding beyond this time on the day before the schedule.

For example, a site uses the Window > Date Offset switch to schedule trips to be bumped starting from the day it is scheduled. If they print next day's run manifests the night before, they may wish to use Bump Window Cutoff For Next Day to ensure that the schedule doesn't change (due to bumping) after this time.