---
sourceDocument: Yokohama Field Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/field-service-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Setting up a travel estimate provider

# Setting up a travel estimate provider {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Set up a travel estimate provider in Schedule Optimization for each of your technician groups to streamline and enhance the travel planning process.

## Travel estimate providers {#setting-up-a-travel-estimate-provider__section_lqr_dls_1yb}

Efficient allocation of work order tasks depends on accurately estimating travel time, considering both the technician's location and the task's location. The technician's starting location is determined using either their home
location or the location of their most recently completed task. Schedule Optimization uses travel estimate providers, which calculate distances between technicians and task and are assigned by admins to groups. The two supported travel estimate providers are straight-line or
Beans.ai.

* Straight-line: This default configuration serves as a backup when a primary configuration isn't available and a secondary configuration hasn't been selected. This provider can be modified but it can't be deleted.
* Beans.ai: This map provider provides more accurate travel time estimates. Locations that are deemed invalid through geocoding or aren't reachable by road are excluded from task assignments

{#setting-up-a-travel-estimate-provider__ul_e4b_sws_2fc}

For more information, see [Create a scheduling attribute for Schedule Optimization](https://servicenow-prod.fluidtopics.net/9hk10u57uKya5TsGewfXnw "Create the scheduling attributes to specify which tasks to optimize and define the rules to perform the optimization.").

## Map vendor call types {#setting-up-a-travel-estimate-provider__section_gly_tjv_zfc}

Property: map_vendor_call_types property  
* Sync: Default value.
* Async: Changing the default value to async can improve performance and may result in more outbound requests.
{#setting-up-a-travel-estimate-provider__ul_z5f_wjv_zfc}

For more information on properties, see [Schedule optimization properties](https://servicenow-prod.fluidtopics.net/JVNQhl4TnoLp5pG3aZUHLg "You can set parameters that control how optimization runs.").

## Travel band modifiers {#setting-up-a-travel-estimate-provider__section_ynz_hkv_zfc}

Travel band modifiers adjust travel times based on the time of day, such as during rush hour. You can add these modifiers to either straight-line or Beans.ai configurations. A multiplier is a number used in the configuration to
adjust travel time based on expected traffic conditions. When traffic is expected to be heavier than usual, a multiplier greater than 1 increases the travel time. For example, a multiplier of 1.2 adds extra time to account for
delays. When traffic is lighter, such as during off-peak hours, a multiplier less than 1 reduces the travel time. For instance, a multiplier of 0.8 shortens the estimated travel time to reflect faster travel.  
Travel band details:

* Range: 30 minutes to four hours.
* Can't overlap.
* Each travel band must have a different start and end time.  
  Note:  
  For example, to increase travel time during rush hour to simulate traffic not capture by the baseline values, you could set a travel band for your straight-line configuration between noon and 15:00 Monday through Friday with a multiplier of 1.2.
{#setting-up-a-travel-estimate-provider__ul_rzk_tkv_zfc}