Schedule Optimization properties

  • Release version: Zurich
  • Updated July 31, 2025
  • 9 minutes to read

    • You can set parameters that control how optimization runs.

    Field Service Schedule Optimization properties

    Schedule Optimization general properties

    Table 1. General
    Property Description
    Exit buffer time Amount of time (in minutes) to add between the end of a task and the travel start of the next. An example of a valid time value is 10.
    • Type: Integer
    • Default value: 0
    • Location: All > Field Service > Administration > Properties
    Qualifier type for schedule optimization The qualifier type for schedule optimization determines the criteria used to optimize schedules. There are two qualifier types available: "Assignment group" and "Territory."

    When the Field Service Territory model is enabled, the qualifier type automatically switches to "Territory" and remains fixed. This means that when the Territory model is active, the optimization process focuses on territories instead of assignment groups. For more information, see Enable the Field Service territory model.

    • Type: String
    • Default value: Assignment group
    • Location: All > Field Service > Schedule Optimization > Administration > Properties
    Number of seconds used for task scheduling resolution Specifies the acceptable interval for scheduling a task.

    For example, if the value is set to 300 seconds, Schedule Optimization will schedule tasks and the associated travel time, such as task start time, travel start time, or estimated end, to the nearest 5-minute start or end time.

    • Type: Integer
    • Default value: 300
    • Location: All > Field Service > Schedule Optimization > Administration > Properties
    Maximum number of overlapping qualifiers in a qualifier set Numeric value set to determine the maximum number of overlapping qualifiers that can be applied to a single qualifier set.
    • Type: Integer
    • Default value: 30
    • Location: All > Field Service > Schedule Optimization > Administration > Properties
    Logging level The logging level will determine the type of information displayed in the results of an optimization log entry, providing details about the Schedule optimization run. There are four options available: Error, Warning, Info, and Debug.
    • Type: Choice
    • Default value: Error
    • Location: All > Field Service > Schedule Optimization > Administration > Properties

    Schedule Optimization travel time estimate properties

    Table 2. Travel Time Estimates
    Property Description
    Maximum number of location points allowed in a map vendor call Numeric value set to determine the maximum number of location points allowed in a map provider call.

    Beans.AI is the map provider that Schedule Optimization supports for travel time estimates. For more information, see Schedule Optimization travel estimate providers.

    • Type: Integer
    • Default value: 300
    • Location:All > Field Service > Schedule Optimization > Administration > Properties

    Schedule Optimization system properties

    The following properties support the prioritized event mode for intraday optimization.

    Table 3. Schedule Optimization system properties for Field Service Management
    Property Description
    sn_schedule_optim.prioritized_event_assignment_horizon_offset Number of minutes that will be adjusted to the Window start time of a task, only for GraphQL processing. This will be used by Schedule Optimization to prevent the Schedule Start and Schedule Travel Start from being scheduled in the past for prioritized events.
    • Type: non-zero integer (in minutes)
    • Default value: 1 minute

    • Location: System Properties list [sys_properties] table
    sn_schedule_optim.prioritized_event_max_agent_count Maximum number of technicians to be considered for prioritized event optimization.
    • Type: non-zero integer
    • Default value: 20

    • Location: System Properties list [sys_properties] table

      Note:

      If the data for a prioritized intraday job exceeds these limits, the job will not run, and no assignments will be received.

      The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes.
    sn_schedule_optim.prioritized_event_max_task_count Maximum number of tasks to be considered for prioritized event optimization.
    • Type: non-zero integer
    • Default value: 100

    • Location: System Properties list [sys_properties] table

      Note:

      If the data for a prioritized intraday job exceeds these limits, the job will not run, and no assignments will be received.

      The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes.
    sn_schedule_optim.max_priority_events Maximum number of prioritized event types that can be configured to trigger optimization.
    • Type: non-zero integer
    • Default value: 3

    • Location: System Properties list [sys_properties] table

      Note:
      The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes.
    sn_schedule_optim.prioritized_optimization_delay_buffer Time (in seconds) to wait before initiating the optimization process for prioritized events.
    • Type: non-zero integer (in seconds 60-900)
    • Default value: 180 seconds (3 minutes)

    • Location: System Properties list [sys_properties] table

    Performance-related Schedule Optimization properties

    The following is the list of solution processing properties that are available with the Schedule Optimization plugin. To access these properties, navigate to All > System Properties > All Properties.
    Table 4. Schedule Optimization solution processing properties
    Property Description
    com.glide.event_manager.sn_schedule_optim.data_queue_1.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_1.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_1
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_2.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_2.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_2
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_3.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_3.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_3
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_4.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_4.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_4
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_5.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_5.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_5
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_6.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_6.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_6
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_7.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_7.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_7
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.data_queue_8.claim_limit This property controls the number of Data Processing events that are captured and processed in a single background transaction. If the property is set to 100, the event handler will grab and process the first 100 Data Processing events from the queue in one background transaction.
    • Type: Integer
    • Default value: 100
    com.glide.event_manager.sn_schedule_optim.data_queue_8.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.data_queue_8
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_1.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_1.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_1.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_2.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_2.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_2.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_3.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_3.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_3.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_4.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_4.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_4.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_5.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_5.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_5.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_6.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_6.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_6.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_7.claim_limit Controls how many Solution Processing events are grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_7.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_7.
    • Type: true/false
    • Default value: false
    com.glide.event_manager.sn_schedule_optim.event_queue_8.claim_limit Controls the number of Solution Processing events grabbed by its event handler and processed in a single background transaction.
    • Type: Integer
    • Default value: 500
    com.glide.event_manager.sn_schedule_optim.event_queue_8.even.load.distribution.enabled Controls balanced events load distribution for custom queue sn_schedule_optim.event_queue_8.
    • Type: true/false
    • Default value: false
    sn_schedule_optim.data_processor_number_of_queues

    Number of queues for data processing

    Enables performance improvement for end to end optimization.
    • Type: Integer
    • Default value: 4
    sn_schedule_optim.solution_processor_number_of_queues Number of queues for solution processing (task updates).
    Increases the number of custom queues (up to 8) for processing optimization solution and speeding up optimization by allowing more parallel processing during solution processing flow.
    • Type: Integer
    • Default value: 4
    sn_schedule_optim.solution_processor_packet_size Packet size to group events for solution processing (task updates).

    Sets the packet size for grouping events in solution processing, defining the capacity of each custom queue. It aims to distribute solution processing as widely as possible across the available custom queues specified in sn_schedule_optim.solution_processor_number_of_queues."

    • Type: Integer
    • Default value: 10
    sn_schedule_optim.map_vendor_call_types Controls whether a synchronous or asynchronous call type is made to the map vendor. Changing the default value of sync to async can improve performance and may result in more outbound requests.
    • Type: String
    • Default value: "beans": "sync"
    sn_fsm_map_integr.logging.verbosity Captures additional logs for troubleshooting purposes. It is used for integration calls to map providers such as Beans.ai or Google, providing detailed insights to help diagnose and resolve issues.
    • Type: Choice
    • Default value: info
    sn_schedule_optim.qualifier_data_agent_entity_split Indicates how many sets of agents will be processed simultaneously in an optimization run, improving performance.
    • Type: non-zero integer
    • Default value: 2
    Note:
    The 'maint' role is required to edit any performance-related properties. This role is exclusive to internal users. Contact support to make changes.