Admin ServiceOptimizer System Configuration Travel Matrix
- Paul Hindle
- Andrew Hill (Deactivated)
Inter-Region Travel Times/Profiles
The Travel Matrix data for any given pair of regions are overridden if there is an entry in the database table sp014_travel_overrides in which the columns region_no1 and region_no2 contain the numbers of the two Regions in question. The travel time and the travel profile for that journey in the Travel Matrix are overridden by the values in the fields travel_time and travel_profile, respectively.
Intra-Region Travel Times/Profiles
The intra-region travel times and profile are held in the travel matrix but are overridden for any given region by any non-NULL value in the fields Database sp057_regions.internal_travel_time and sp057_regions.internal_journey_type, respectively, in the record corresponding to that region.
Same Post Code Travel Times
The same postcode (or zipcode) travel times are not held in the Travel Matrix at all. Instead there is a default value set in the sp083_system_parameters parameter with the name 'same_postcode_travel' (see following section).
This default value can be overridden for any region by any non-NULL value in sp057.internal_travel_time2 in the record corresponding to that region. However, the global default should be sufficient for most users.
There is no profile associated with any journeys of this type.
Relevant System Parameters in SP083_SYSTEM_PARAMETERS
This section lists the main system parameters relating to travel and the calculation of travel times. The values of these parameters are entered into the database directly.
Parameter | Significance |
travel_overhead | Fixed addition in minutes for all travel values used in the system. |
travel_multiplier | Multiplier for all travel values used in the system. |
internal_travel_multiplier | Multiplier for intra-region travel. |
same_postcode_travel | Default value for same postcode travel. |
The values of these parameters are used to calculate travel times as described below.
| Value | Formula |
|---|---|
| travel between different regions | ( value_from_matrix_file + travel_overhead ) * travel_multiplier |
| travel within the same region (intra-region travel) | ( ( value_from_matrix_file * internal_travel_multiplier ) + travel_overhead ) * travel_multiplier |
These formulas are not used when the value is obtained from a travel override (sp014_travel_overrides or sp057_regions). The idea is that a travel override has been set explicitly by the user, so that value should be used directly.
The value of the same postcode travel is derived directly from the same_postcode_travel parameter, or from the relevant value in sp057_regions as specified in the preceding section.
Postcode Travel Matrix (using RJServer)
Additional to the above, the system can be configured to use a further travel matrix that is built up on the fly as the system runs and which calculates and stores the actual point to point travel times using Routing J Server®. These times will be used instead of the times retrieved from the standard travel matrix, and all subsequent processing will continue as described above.
In order to make use of this functionality further sp083_system_parameters need to be set as follows (where applicable, these may also be set in sp213_optimizer parameters on a per-FRU basis):
Parameter | Significance | FRU? |
postcode_matrix_directory | The directory/folder where FRU postcode matrix files reside. Files will be automatically created as <FRU name>.tm2 if they do not already exist. |
|
postcode_tm_lookup | Switch to enable use of postcode look up matrix | Y |
postcode_tm_scan_interval | Time, in seconds, between update scans. Mandatory if postcode matrix is enabled. | Y |
postcode_tm_server | url for RJS Server. Mandatory if postcode matrix is enabled. | Y |
postcode_tm_server_trigger_level | Number of route updates needed to trigger scan. Mandatory if postcode matrix is enabled. | Y |
rjs_retry_count | Number of retries allowed to the RJS Server. Mandatory if postcode matrix is enabled. | Y |