Control Travel Time Through the Routing Plan

You can control travel time through the Routing Plan. With improved Travel time section of the routing plan settings, you can choose the optimization type and set distance limits.

To control Travel time through the routing plan, specify:

1. Avoid long travel segments to minimize summary travel

   You can minimize summary travel if some specific activities are getting long travel or if some activities are left unassigned and summary travel might increase. This enables you to limit the amount of travel time or distance a resource can spend travelling for any one activity. This results in fewer assigned activities and less optimal routes, but eliminates any travel that's beyond the specified amount of time or distance.

   Specify values for Travel segment limit, minutes and Travel segment limit, kilometers. If no value is specified for these fields, the default values of 240 minutes and 200 kilometers would apply.

   Note: Routing might prioritize longer travel with higher accuracy over slightly shorter travel with lower accuracy. When evaluating the most probable activity location areas, less accurate travel estimates might result in significantly longer distances than initially expected.
2. Use SLR

   Street Level Routing (SLR) maps the best path for a vehicle traveling from Point A to Point B, then estimates the travel time. It computes the distance on roads, considering turn-by-turn directions; this means it's based on actual road speed and the expected speed based on the type of road.

   SLR in Routing requires a subscription to Oracle Fusion Field Service Enterprise and Oracle Fusion Field Service Standard Map Service either with Google Maps or Baidu Maps.

   Select Use SLR to enable Street Level Routing. This feature can be used when the Run schedule is set to Manually, Once a Day, Recurrently, Sequentially, or Continuous Improvement; it isn't available for Immediate routing runs. To improve the quality of the routing run with SLR, configure the plan with adequate time to gather enough SLR data. We recommend that you allocate a minimum of ten minutes for Once a Day and Manual routing plans. This time might vary depending on your business and the number of activities to be optimized. You might increase the time if needed.

   Note: Sometimes, when routing’s evaluation must end due to a time limit, it consumes slightly more time than configured. This is because termination can only occur after completing the current block of computations.

   • Daily travel limit, kilometers

     Routing might limit total travel distance per day per route. This option is particularly useful for electric vehicles or similar fleet types with limited range.

     Note: If one or both locations have low or medium accuracy, SLR travel might still be calculated as long as the areas don't intersect. If they do intersect, travel calculations will rely on airline distance between locations. To improve accuracy for airline distances between low or medium accuracy locations, travel calculations use an average distance between points within those areas, instead of the airline distance between their coordinates.
   • SLR Time Limit, %

     Choose which part of the total routing plan runtime might be spent on obtaining SLR data. The recommended value is 70%. The routing runtime includes both gathering SLR data and using that data to run routing. To use SLR, routing runs must run at least 10 seconds, as such runs need at least 5 seconds for routing and 5 seconds for SLR.

     In some situations, when there are several pending activities, every point-to-point travel combination can’t be obtained within the allotted time period. When this occurs, routing will use SLR data and learning travel data to optimize the routes. This ensures routes are optimized quickly with the best combination of travel data.
     For more information, see:

     • Set the SLR Time Limit
     • Optimize Route for Fleet with Limited Range
3. Prefer fastest routes, even if it means the increase of a total travel distance

   Indicates that activities might require lengthy travel, but the total travel time for the entire bucket is optimal. This option is the default and results in the most optimized routes.

4. Prefer shortest routes, even if it means the increase of a total travel time

   Indicates that activities might require a longer travel time, but the total distance travelled will be optimal.

   Note: Preassigned activities that weren't moved during a routing run are no longer counted as non-assigned in the Routing Report. The non-assignment reason, "6032 – Travel statistics for specified travel keys are missing", applies to travel-enabled activities when their coordinates aren't geolocated, and statistics for their travel keys are missing.