Global optimization is a feature that allows rescheduling multiple service appointments at once based on predefined criteria such as emergency priority, travel time, or skills[194]. Global optimization would allow Universal Containers to realign available resources with open work by running an optimization job that prioritizes emergency work and assigns it to the best available resources[195]. Resource Schedule Optimization is a feature that allows scheduling service appointments for individual resources based on their availability and preferences[196]. Resource Schedule Optimization would not allow Universal Containers to realign available resources with open work because it does not consider multiple resources or service appointments at once. Emergency scheduling is a feature that allows creating and assigning emergency service appointments to the best available resources[197]. Emergency scheduling would not allow Universal Containers to realign available resources with open work because it does not reschedule existing service appointments. Customer First scheduling is a feature that allows prioritizing customer preferences and satisfaction when scheduling service appointments[198]. Customer First scheduling would not allow Universal Containers to realign available resources with open work because it does not prioritize emergency work or reschedule existing service appointments. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_optimization_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_optimization_global_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_resource_schedule_optimization_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_emergency_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_customer_first_overview.htm&type=5

These are three factors that should be considered when configuring routing. Routing is the process of finding the best resource for a service appointment based on various criteria and constraints. A schedule policy is used to define the routing preferences and rules for a service territory or operating hours. A work rule is used to define a scheduling constraint or preference for a service appointment or a resource. A service objective is used to define a scheduling goal or metric for a service appointment. The Resource Availability work rule is used to calculate travel time and breaks as part of the resource's availability. The Default Travel Speed is used to estimate the travel time between locations if a different travel speed is not specified for the resource.

This feature should be configured to meet this requirement, as it allows creating a group of service resources that can perform periodic maintenance on complex products together. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_crew_management.htm&type=5

Field History Tracking on Assets allows tracking location and status changes in the lifecycle of a specific component in a customer's install base by recording the date, time, nature, and user of each change. A Work Order related list on Assets would show the work orders associated with an asset, but not the location and status changes of the asset. A custom installation date field on Products Consumed would show when a product was installed, but not the subsequent changes in the asset lifecycle. A Product related list on Assets would show the products related to an asset, but not the location and status changes of the asset. Reference: https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_products.htm&type=5

This scheduling policy prioritizes customer service preferences over other factors, such as travel time or resource availability. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies.htm&type=5