Schedule Optimization properties

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

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

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

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.

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.

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.

Sets the level of detail captured in Schedule Optimization logs for each run. The choices are info, debug, warn, and error.- Type: Choice list - Default value: Error - 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.

Maximum number of ML solutions that can run simultaneously. When workload distribution is enabled with multiple jobs or multiple optimization modes run concurrently, increase this value.- 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.

Determines which optimization modes use split qualifiers to distribute workloads across parallel jobs. Choices:

• None – No distribution; all qualifiers processed in a single job.
• Only Batch – Distribute qualifiers only for batch optimization runs.
• Only Intraday – Distribute qualifiers only for intraday optimization runs.
• Both – Distribute qualifiers for both batch and intraday optimization runs.

Note: Split qualifiers work with batch, intraday, and prioritized optimization but not on-demand optimization.

• Type: choice
• Default value:none
• Location: System Properties list [sys_properties] table

Number of splits to distribute qualifiers across parallel optimization jobs for each batch or intraday configuration. Higher split counts reduce processing time per job but require more ML capacity.If running multiple optimization modes simultaneously adjust sn_schedule_optim.so_max_solution_threshold to accommodate the total number of concurrent ML solutions needed.

• Type: Integer
• Default value: 1
• 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.