Schedule Optimization travel estimate providers

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
  • Summarize
    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 is essential for efficiently allocating work order tasks to agents by accurately estimating travel time based on the locations of agents and tasks. It supports two travel estimate providers: Straight-line and Beans.AI, allowing administrators to select the appropriate method for their organization.

    Show full answer Show less

    Key Features

    • Straight-line Calculation: Administrators can configure straight-line travel estimates by setting speed limits and multipliers based on estimated travel time brackets. This serves as a fallback option if a map provider isn't chosen.
    • Beans.AI Integration: This map provider allows for precise travel time estimates. Administrators can create connections and limit the number of queried locations to optimize performance. A maximum of 300 location points is set by default, which can be adjusted according to organizational needs.

    Key Outcomes

    By utilizing these travel estimate providers, ServiceNow customers can expect:

    • Improved accuracy in scheduling tasks based on estimated travel times.
    • Flexibility to choose between a simple straight-line method or a more detailed mapping solution with Beans.AI.
    • Better resource allocation, leading to increased efficiency in field service operations.

    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 for more information on where the options are located.

    Straight-line

    To enter straight-line travel estimate configuration properties, an administrator can navigate to All > Schedule Optimization > Configuration > Scheduling 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 two or more, to increase the estimated travel time. If the travel time is greater than 15 minutes, multiply by 0.5 or less 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

    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 All > IntegrationHub > Connection and Credentials > Connection and Credentials Aliases.

    Travel estimates are obtained every time 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 number of locations queried exceeds the set value, the query defaults to straight-line. To change maximum number of location points allowed in a provider call, an administrator can navigate to All > Schedule Optimization > Configuration > > Properties > 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 toAll > Map Integrations for Field Service > Map Provider Configuration.

    By default, the Inputs field is set to Beans.AI. By default Decision table is setup as follows:
    Table 1. Fields in Beans.AI configuration for travel time estimates
    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]
    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.