Schedule optimization properties
You can set parameters that control how optimization runs.
Field Service Schedule Optimization properties
Schedule Optimization properties
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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. Changing the default value of sync to async can improve performance and may result in more outbound requests. Beans.AI is the map provider that Schedule Optimization supports for travel time estimates. For more information, see Schedule Optimization travel estimate providers.
|
Performance-related Schedule Optimization 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| sn_schedule_optim.data_processor_number_of_queues | Number of queues for data processing Enables performance improvement for end to end optimization.
|
| 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.
|
| 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."
|
| 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.
|
| 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.
|