Resource Utilization Metrics now appear on the Scheduler Calendar to allow dispatchers to assign Resources based on capacity. Dispatchers can enable or disable this functionality as needed. Productive time can be configured to include travel times, event types, and shift segments, and configurable emojis represent user-definable capacity thresholds. Metrics are calculated based on the selected date, duration, and interval, with support for intervals of up to 6 weeks.

Full utilization metrics for Resources, Service Teams, and Territories are calculated for the currently selected scheduling horizon and expressed as both percentages and the number of hours. Total amounts of time are calculated based on all hours in Shifts and Shift Exceptions that have user-configurable shift types. Productive time calculations and charts are broken down by user-defined option fields in Job objects, such as Order Type. Nonproductive time is not used to calculate Resource utilization metrics, and travel time is used for calculation if enabled.

Guardrails can now be enabled for API-based optimization. Optimization for Schedule Proposals for Jobs and Project Tasks can be stopped in cases where too many related events are in the payload, or too many routes are submitted. Guardrails are supported for Appointment Proposals only when the Enable Appointment Proposals Policies Selection setting is enabled. Additional guardrails are supported, but might not be activated or enforced. This functionality makes it possible to warn dispatchers of likely issues before proposals are submitted, which reduces the risk of expensive executions and increases processing capacity.

Schedule Proposals can now be generated only for the current day. Additional capabilities from the Proposal API are used for this automation, including travel adjustment controls and skilled labor handling. Users can choose to optimize Appointment rescheduling or to fill open time slots in the schedule. Lead-time capabilities are available to give technicians time to react to schedule changes. Job qualification for optimization is simplified, and advanced options are available to allow specific Resource selection based on qualified Jobs.

On the Scheduler Calendar, new icons and tooltips indicate when Jobs are submitted for Current-Day Optimization, and highlight historical issues with selected Jobs to allow dispatchers to take corrective action or manually assign Resources. These capabilities enable dispatchers to focus on more unique scheduling use cases or handle other responsibilities.

When the optimization engine finds conflicting or overlapping Events and Appointments in Current-Day Optimization payloads, processing fails and notification icons with tooltips appear on the related Job Cards, Appointments, and Events to inform users to make manual adjustments. Additionally, dispatchers are notified in cases where Optimized Rescheduling can resolve conflicts without manual intervention.

ServiceMax AI is now available for scheduling use cases within Service Board. Out of the box default capabilities include creation of AI actions that allow users to schedule Jobs by using generative AI. This feature is designed to minimize dispatcher effort in manual scheduling, and is not intended for route optimization. AI Actions can be combined with follow up options that may, for example, require users to identify nearby Jobs. Admins can also create custom AI Actions, such as Job summarization. To use this feature, a separate ServiceMax AI license is required.

Configurable minimum and maximum thresholds for the Resource Recommendation Star option are added in this release. Dispatchers can now set minimum and maximum score percentages to define which recommended Resources are highlighted with a star in the Resource List. Resources with scores within and inclusive of the specified range are started and sorted at the top of the list. Default behavior is unchanged unless the new maximum threshold value is configured.

This release includes an upgrade to React 18. This upgrade has been thoroughly tested for compatibility. Please report any unexpected UI behavior to Customer Support.