Batch Switches and Descriptions

Specifies whether the capacity swapping algorithm will be applied prior to matching.

Runs that exist in both the template schedule (source for the match) and the live schedule (target for the match) and have no capacity type in the live schedule may be assigned a capacity type/vehicle type prior to the matching algorithm commencing for that run. (Note that runs that are only in the live schedule are ignored during matching).

For more information about capacity type swapping, see Capacity Type Swapping Switches.

The group optimizer will attempt to minimize the number of runs required to service each partial group. This feature can require significantly more computational time, however, depending on the number of partial groups.

Specifies whether cyclic redundancy checking (CRC) logging is enabled for detecting, analyzing, and debugging unexpected deviations in batch scheduling results. Specifically, if you run a batch schedule, return all trips to the state they were in before the batch (for example, unschedule all trips), and then run the batch again with the exact same parameters, one would expect the second batch to produce the exact same result as the first batch, assuming no other changes were made to the trips.

However, sometimes a batch may produce a different result than expected. Using CRC logging during batch scheduling records a CRC number for each booking in the batch that represents the solution chosen for that booking. The batch can then be re-run so that Schedule Server reads the CRC log, instead of writing to it, and compares the recorded CRC to the CRC calculated for each booking solution in the new batch. If the CRC numbers are different, it means that a different booking solution was chosen than the last time, which causes the batching process to stop, thereby leaving the offending booking unscheduled, and the offending booking details are traced to the log. These traces are used by a Trapeze developer to analyze or debug the solutions suggested for that booking.

• 0 - Log all solutions set differences.
• 1 - Log change in top insert’s run or position on run.

When the CRC Log Mode is set to 2, the batch will stop after it has scheduled this bookingId and this booking's solutions will be displayed in the log.

To log all booking IDs, set this value to 0 (default).

Specifies whether the sort order of the trips in the batch are dumped to a text file called batchorder.txt and located in the application's startup directory.

Specifies whether the alternate group optimizer sort order will be dumped to the log.

Specifies the maximum of number of bookings in a row that fail to be scheduled to the current run before the Group Optimizer moves on to the next run. This feature is useful for saving time when scheduling very large groups that cannot all fit on to one vehicle anyway. To disable this switch, set the value to 0.

Specifies whether the InfoFromDate and InfoToDate will be cross-checked against the schedule’s live date when matching from template schedules to live schedules. If the dates do not match, the match will fail for the trip and it will remain unscheduled.

Specifies how often the batch will save its results to the database each time it modifies this many runs since the last save. The default value is zero.

To allow the schedule server to auto-select the cycle size, set the value to 0 (default).

To disable this switch, set the “Periodic Save Rule” switch to 0.

Specifies how often to save batch results to the database.

Specify one of the following options:

• 0 - Off
• 1 - Always on
• 2 - Always on for same and future days
• 3 - Auto on. Same as (2), plus turns on for other schedules whenever their batch is interrupted.

To define the cycle size, see the “Periodic Save Cycle” switch.

Specifies whether trips that are bumped during the batching process will be automatically rescheduled. If they cannot be rescheduled, they will be unscheduled.

Specifies whether trips that are bumped during a batch will be automatically rescheduled. Any trips that cannot be rescheduled will be unscheduled.

Auto-groups are those that are not tagged with a group code, but are a group of people who happen to be travelling to and from the same coordinates at the same time. When enabled, this switch will see to it that the auto-groups are included in the group sorting for the batch sort order irrespective of whether or not the Group Optimizer is enabled. Works in tandem with the “Consider Partial Groups” switch.

Specifies whether a location, if within the Radius around group location setting, will be merged with the location with higher number of visits.

Specifies the size of the travel time period (in minutes) used by some of the batch sort orders.

To allow the batch to determine the ideal period size on its own, set this value to 0 (default).

Specifies whether to stop the batch after the specified number of bookings. For testing and analysis only.

To disable this switch, set the value to 0 (default).

For analysis purposes, you may wish to stop the batch just prior to the scheduling of a particular booking. This way, you may then schedule it in the schedule booking wizard to ascertain why a particular solution is chosen.

To disable this switch, set the value to 0 (default).

For testing only - the batch will search for solutions for each booking but not actually insert the solution. Can be used to identify bookings that cannot be scheduled.

Specifies whether to create a booking-by-booking performance output during a batch.

Specifies the trace level if tracing is enabled for the Group Optimizer.

Switch specifies the trace level for the batch-matching algorithm. For details on a booking-by-booking basis, set this switch to “Verbose.”

Specifies whether the statistics of each run at the end of the batch are also traced to the log file.

To use this switch, the “Trace Statistics” must also be set to “ON”.

Specifies whether information about the current batch plus the batch results will be traced to the log.