Reshuffle is an action within the Gantt that allows rescheduling multiple service appointments at once based on predefined criteria such as emergency priority, travel time, or skills[209]. Reshuffle would allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work byrunning a reshuffle action that prioritizes emergency work and assigns it to the best available resources[210] . Defining a Global Optimization job to run hourly would not allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. 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[211]. Running a Global Optimization job hourly would not be responsive enough for emergency work identified throughout the day. Creating a custom Gantt action to call an Apex class to reschedule appointments would not be necessary for Universal Containers to dispatch emergency workidentified throughout the day that needs to be completed before lower-priority work. Custom Gantt actions are actions within the Gantt that can be customized using Apex code to perform specific tasks such as sending notifications or updating fields[212] .Creating a custom Gantt action would require additional development and maintenance and would not leverage the existing Reshuffle action. Writing a batch Apex class to unschedule low priority work orders would not allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Batch Apex is a way of processing large volumes of data asynchronously using Apex code[213]. Writing a batch Apex class would require additional development and maintenance and would not leverage the existing Reshuffle action. References: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_run.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_gantt_custom_actions_overview.htm & type=5https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_batch_interface.htm

This option allows tracking customer purchases of serialized components as assets and defining parent-child relationships between them. References:https://help.salesforce.com/s/articleView?id=sf.fs_asset_hierarchy.htm & type=5

These two troubleshooting steps should betaken to resolve the issue, as they could explain why the service appointment status is not updated correctly on the console. References:https://help.salesforce.com/s/articleView?id=sf.fs_mobile_troubleshooting.htm & type=5

This option reflects the sharing rules for Service Appointments, which grant access to the assigned resources, the owner of the record, and the members of the service territory associated with the record. References:https://help.salesforce.com/s/articleView?id=sf.fs_sharing_rules.htm & type=5

The Preventative Maintenance Gantt is a view within the Dispatcher Console that shows the scheduled service appointments for preventive maintenance work orders[217]. The Dispatcher Console Appointment list is a view within the Dispatcher Console that shows the listof service appointments with various details such as status, priority, or assigned resource[218] . Filtering is a feature that allows narrowing down the list of records based on specific criteria such as date, status, or territory[219]. Using the Preventative Maintenance Gantt and filter the list to show only desired work orders and using the Dispatcher Console Appointment list and filter the list to show only desired service appointments would allow Universal Containers’ Managers to monitor Preventative Maintenance work orders using the Dispatcher Console by showing them the preventive maintenance service appointments on a Gantt chart or a list view and allowing them to apply filters to see only the relevant records[220] . Using the Dispatcher Console Map and filter the list to show only desired service appointments would not allow Universal Containers’ Managers to monitor Preventative Maintenance work orders using the Dispatcher Console. The Dispatcher Console Map is a view within the Dispatcher Console thatshows the locations of service appointments and resources on a map[221]. Using the Dispatcher Work Order Polygon and filter the list to show only desired service appointments would not work because there is no such feature as Dispatcher Work Order Polygon. References: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_preventive_maintenance_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_appointment_list_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filter_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_preventive_maintenance_view.htm & type=5https://help.salesforce.com/s/articleView?id=sf.fs_gantt_map_overview.htm & type=5

Soft Boundariesand Customer First are two default scheduling policies that meet the requirement of committing preferred resources to accounts and providing prompt service. Soft Boundaries prioritize resources that are assigned to the same account or service territory asthe service appointment. Customer First prioritize resources that have the highest customer satisfaction rating.

This licensing will be required for the Field Service Schedule Optimization user, as it allows accessing Salesforce features and functionality such as optimization jobs and settings. References:https://help.salesforce.com/s/articleView?id=sf.fs_permission_sets.htm & type=5

Generation Horizon is a setting that defines how far in advance work orders should be generated from maintenance plans[126]. Defining a generation horizon of 14 days would allow Universal Containers to automatically generate Work Orders 14days before the next suggested maintenance date by creating work orders from maintenance plans within 14 days of their scheduled date[127] . Defining a generation timeframe of 14 days would not automatically generate Work Orders 14 days before the next suggested maintenance date. Generation Timeframe is a setting that defines how often work orders should be generated from maintenance plans[128]. Configuring Auto-generate Work Orders to True would not automatically generate Work Orders 14 days before the next suggested maintenance date. Auto-generate Work Orders is a setting that enables or disables the automatic generation of work orders from maintenance plans[129] . Defining a generation horizon of 20,160 minutes would not automatically generate Work Orders14 days before the next suggested maintenance date. Generation Horizon is measured in days, not minutes[130]. References: https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_horizon.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_timeframe.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_auto_generate_work_orders.htm & type=5https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm & type=5

Skills are records that define specific abilities orqualifications that service resources have[158].Skill Levels are fields on the skill object that indicate the proficiency or experience of a service resource in a skill[159] . Assigning Contractor 1 and 2 different Skill Levels for repair Work Type would allow Universal Containers to configure the Contractors’ experience by setting up criteria such as skill name equals repair and skill level equals high for Contractor 1 and low for Contractor 2. Assigning Contractor 1 as a Preferred Resource would not configure the Contractors’ experience. Preferred Resources are optimization criteria that prioritize assigning service appointments to resources who have previously completed similar work orders or who are preferred by customers[160]. Assigning Contractor 1 and2 different capacities for repair work would not configure the Contractors’ experience. Capacities are fields on the service resource object that indicate the number of hours available for work per day or week[161] . Assigning Contractor 2 as an Excluded Resource would not configure the Contractors’ experience. Excluded Resources are optimization criteria that prevent assigning service appointments to resources who are explicitly excluded by customers or dispatchers[162]. References: https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm & type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_skill_skilllevel.htm https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria_preferred_resources.htm & type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceresource_capacityhoursperday.htmhttps://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria_excluded_resources.htm & type=5

Arrival Window Start and Arrival Window End are fields on the Service Appointment that indicate when a technician is expected to arrive at a customer site based on travel time and service duration calculations. These fields can be shared with customersto set expectations around upcoming appointments. Scheduled End and Scheduled Start are fields on the Service Appointment that indicate when a technician is scheduled to start and end their service based on their availability and assigned time slots. These fields are not accurate indicators of when a technician will arrive at a customer site, as they do not account for travel time and service duration variations. References:https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm & type=5