Solution Parameters
Before you begin scheduling activities in the Schedule Booking Wizard, you should determine the number and types of solutions that the system produces.
Use the Set list in the Solution Parameters dialog box to choose a set of solution parameters. Review the Solution Parameters settings before performing any scheduling activity using the Schedule Booking Wizard.
| Parameters | Description |
|---|---|
| Set | Click a solution parameter set in the list. |
| SecGroupName | Click security group names in the list to restrict the solution parameter set to be available only to users who belong to these groups. |
| Early Win | The time used to expand the Requested Early Time (RE). For example, if the early window is set at 1hr and you are trying to schedule a booking with a request time of 10:00, then the scheduling algorithm searches for solutions as early as 9:00. Use this parameter only when you select the SearchW check box in the left-side filters in the Schedule Booking Wizard. |
| Late Win | The time used to expand the Requested Late Time (RL). For example, if you set the late window at 1 hr, the scheduling algorithm looks for solutions as late as one hour after the requested late time. You can pick up or drop off a client one hour after the requested late time and not incur a violation. Use this parameter only when the SearchW check box is selected in the left-side filters of the Schedule Booking Wizard. |
| Show All Run Variations |
If selected, the system returns different variations of solutions. For example, multiple solutions for Run 201 - the differences existing in schedule time and client position on the run. If unselected, only solutions with the best options for the route are generated. Note: Select this check box if you offer FLEX route service and want FLEX run
solutions included in your list.
|
| Try Taxi if no solutions found | When selected, the system (using the Schedule Booking Wizard or by batch
scheduling) generates taxi solutions if no other solutions are found. In this case, taxi solutions are suggested even if taxi run types were not initially selected in the Schedule Booking Wizard. If used in batch scheduling, the system tries to schedule a trip to a taxi if no other solutions were found. |
| Itin. Sol'ns Use Common Run | When selected, the system will search for solutions that ensure that both the
trip and return trip are scheduled on the same run itinerary. If the trips cannot be scheduled on the same run, no solutions will be shown. |
| Min Transfer Layover |
Defines the minimum amount of time that must occur between a transfer drop-off and the subsequent transfer pick-up. The default for this parameter is 0. If this parameter is violated (that is, the amount of time between transfer drop-off and pick-up is less than the minimum), a Transfer Layover (TL) violation will show. When searching for solutions, the Schedule Server considers this parameter and the Minimum Transfer Layover property (in , on the Profile tab, underPASS Scheduling) and uses the greater of the two values. Note: If TL violations are allowed, the degree of the allowed TL must be less than
the auto layover.
|
| Max Transfer Layover |
Defines the maximum amount of time allowed between transfer drop-off and subsequent transfer pick-up. When searching for solutions, the Schedule Server considers this parameter and the global Max Transfer Layover property (in , on the Profile tab, underPASS Scheduling) and then uses the lesser of the two values. Note: When no value is specified, the global Max Transfer
Layover property is used.
|
| Min Transfers |
The minimum number of transfers to be considered in the search for
solutions.
Note: This can be used to force a transfer solution. |
| Max Transfers |
The maximum number of transfers to be considered in the search for solutions. Note: This can be used to prevent excessive transfers.
|
| Max Walking Dist |
The maximum walking distance to a FLEX bus stop. When searching for solutions, the Schedule Server considers this parameter and the global Max Walking Distance property (in , on the Profile tab, underPASS Scheduling), and uses the lesser of the two values. Note: When no value is typed, the global Max Walking
Distance property is used.
|
| Exclude Last FX Trip | (For FLEX users) If this check box is selected, the search does not consider
the last trip on an FX run. When this check box is clear, the Schedule Server automatically includes the last trip on an FX run in the search for solutions. |
| Bump Rule |
(For sites using bump runs only) Choose one of the following options:
|
| Bulk - New Stop | For use with Location Programs in the UK. |
| Reset booking provider |
When selected, the system will attempt to schedule the selected trip booking, via batch or single insert schedule, to any provider if the user belongs to the provider's user security group. Once the booking has been scheduled, the system property (found in , on the Profile tab) determines how the
trip booking will be updated with the newly scheduled provider:
The Provider ID field in the trip booking will be updated only if the trip has been scheduled. If no scheduling solutions are found, the provider ID on the trip booking record will be left as-is. |
| Restrict first pickup window | Prevents the first trip on a run from being scheduled at the end of an
on-time window. For example, if the on-time window is 0–20, it is undesirable for the first pick-up to be scheduled at 15 minutes into the window because if the driver runs into traffic, the risk of starting the run out of the window will likely affect later on-time performance. The value represents the % of the scheduling window that is considered valid. (Setting the value to 100% turns off any restriction.) For example, if you set the value to 75% and you have a scheduling window of 20 mins (SchLate – SchEarly) where the SchLate time is 8:20 A.M. and the SchEarly time is 8:00 A.M., than the solution is only valid if the Est time falls before 8:15 A.M. (75% of a 20-minute scheduling window is 15 minutes). In this example, the last 5 minutes of the window or any time after the window are not considered valid. |
| Parameters | Description |
|---|---|
| Max. Sol | Determines the maximum number of solutions that the Schedule Booking Wizard
produces. These solutions are displayed in the Run Solutions view of Schedule Booking Wizard. For call takers, the maximum number of solutions should be between 3 and 5. For dispatchers and schedulers, the maximum is usually greater. |
| Add Srch Time | Indicates the additional search time required for finding solutions. If the search time-out is reached, scheduling uses this additional time before reporting that no solutions are found. Set to 2000 (milliseconds). |
| Srch Timeout | Shows the duration after which the wizard stops searching for
solutions. Set to 5000 (milliseconds). |
| FCost Depth | Determines the number of vehicles to re-cost using the Street Routing
method. It is typically set at 3. |
| Use Fast Costing | When selected, this property costs runs using the fast costing method (for example, triangulation) first, and then street routing. |
| Max Cost | Excludes solutions with a cost larger than this value. |
| Use Max Cost | If selected, then solutions are only generated in the Schedule Booking Wizard
that have a cost that is less than or equal to the value in the Max Cost field.
If used in batch scheduling, then the batch only saves solutions that are less than or equal to this cost weight. Max Cost is applied at the final recosted phase. |
| Batch Sort Order | Allows you to choose the order in which trips are batch scheduled. Choose one
of the following sort orders:
|