---
sourceDocument: Australia Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/field-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Schedule Optimization travel estimate providers

# Schedule Optimization travel estimate providers {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Schedule Optimization Travel Estimate Providers

Schedule Optimization enhances the efficiency of work order task allocation by utilizing precise travel time estimations based on agent and task locations.
It supports two travel estimate providers: Straight-line and Beans.AI.
An administrator must select a provider for each qualifier-level group to ensure accurate estimations.
Show full answer Show less  

## Key Features

* **Straight-line:** This option allows administrators to configure travel estimates based on straight-line distance. In the configuration, speed limits can be set, and multipliers can be defined to adjust estimates based on the travel time bracket.
* **Beans.AI:** This provider offers map-based travel time estimates. Administrators can set up a connection to Beans.AI and limit the number of locations queried to optimize performance. If the limit is exceeded, the system defaults to straight-line calculations.

## Key Outcomes

By implementing the appropriate travel estimate provider, ServiceNow customers can enhance the accuracy of travel time calculations, leading to better allocation of tasks to agents. This results in improved operational efficiency and customer satisfaction as agents can reach their tasks more effectively.  
Travel estimate providers used by Schedule Optimization.
Efficient allocation of work order tasks to agents depends on accurate estimation of travel time, taking into account both the agent's location and the task's location. Schedule Optimization supports two options to calculate distances between agents and task, Straight-line and Beans.AI. An administrator is required to select a travel estimate provider for all qualifier-level
groups. See, [Create a scheduling attribute for Schedule Optimization](https://www.servicenow.com/docs/81xNM0itm8aRQDkiML0QKw "Create scheduling attributes to specify which tasks to optimize and define the rules to perform the optimization. You can create different scheduling attributes configurations for each policy.") for more information on where the options are located.

## Straight-line {#schedule-optimization-travel-estimate-providers__section_s1m_htw_1yb}

To enter straight-line travel estimate configuration properties, an administrator can navigate to AllSchedule OptimizationConfigurationScheduling Attributes and open the travel estimate configuration record.

In the General tab, you can add the speed limit for the region in the speed multiplier field.

In the Multipliers tab, the multipliers defined in the straight-line calculation are the values that the estimated straight-line travel time is multiplied by, depending on the time bracket the estimate falls
in. If the travel time is less than 15 minutes, multiply by a value greater than 1, to increase the estimated travel time. If the travel time is greater than 15 minutes, multiply by a positive value smaller than 1 to decrease the
estimated travel time.  
Note:  
Straight-line distance calculation is a fallback logic in case a customer doesn't want to choose a map provider for travel time estimates.

## Beans.AI {#schedule-optimization-travel-estimate-providers__section_unh_3tw_1yb}

Beans.AI is the map provider that Schedule Optimization supports for travel time estimates.

To create a connection and credential record for Beans.AI, an administrator can navigate to AllIntegrationHubConnection and CredentialsConnection and Credentials Aliases.

Travel estimates are obtained every time Schedule Optimization runs. An administrator can limit the number of locations that are queried from Beans.AI. For example, if optimization runs for two agents and two tasks, a 4x4 matrix is sent to Beans.AI to find
the shortest distance to the new location. A 4x4 matrix sends 16 location elements to Beans.AI. If the number of locations queried exceeds the set value, the query defaults to straight-line. To change the maximum number of location
points allowed in a provider call, an administrator can navigate to AllSchedule OptimizationConfigurationProperties and change the value in the Travel Time Estimates field. The default value is set to 300.

To change the configurations for Beans.AI, an administrator can navigate to AllMap Integrations for Field ServiceMap Provider Configuration.  
By default, the Inputs field is set to Beans.AI. By default Decision table is set up as indicated in the table.{#schedule-optimization-travel-estimate-providers__table_zc4_kw3_cyb__entry__2}

| Field | Value |
|-|-|
| Request Threshold Limit | 5000 \[considering 50 runs a day with 100 groups in each run\] |
| Max Location Element Count | 250,000 \[considering 500 x500 matrix support per Map Provider call\] |
[Table 1. Fields in Beans.AI configuration for travel time estimates]

{#schedule-optimization-travel-estimate-providers__table_zc4_kw3_cyb}  
Note:  
Straight-line distance calculation is a fallback logic in case a customer doesn't want to choose a map provider for travel time estimates.

*[\>]: and then