Field-Service-Consultant Questions and Answers

Drip Feed Dispatching is a feature that allows dispatching groups of service appointments to technicians at regular intervals instead of all at once[56]. Enabling Drip Feed Dispatching in Field Service Settings allows turning on this feature for all service territories[57]. Setting the Number of Services to Drip Feed on the Service Territory allows specifying how many service appointments should be dispatched at a time for each service territory[58]. Setting the Service Appointment to Dispatch in Field Service Settings would not affect how many service appointments are dispatched at a time. Enabling Sharing of Dispatched Service Appointments would not affect how many service appointments are dispatched at a time. References: https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_enable.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_configure.htm &type=5

This option allows creating a record to request products from another inventory location and adding product request line items for each product requested. References:https://help.salesforce.com/s/articleView?id=sf.fs_product_requests_overview.htm &type=5

Work Orders are records that track customer requests for service such as repairs or maintenance[47].Work Order Line Items are records that track specific tasks or products related to a work order[48]. Service Appointments are records that track the date, time, duration, and assigned resource for a work order or work order line item[49]. Adding each Assetto a separate Work Order Line Item or a separate Work Order would allow handling the service associated with each container independently by creating different records for different containers. Creating a Service Appointment for each Line Item or each Work Order would allow scheduling and dispatching the service associated with each container independently by assigning different resources and time slots for different containers. Adding each Asset to a separate child Work Order would create an unnecessary hierarchy of Work Orders that could complicate reporting and scheduling. Creating a Service Appointment for the parent Work Order would not allow handling the service associated with each container independently by assigning one resource and time slot for all containers. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm &type=5

Work order line items are used to track individual products or services that are part of a work order. By creating a work order line item for each installed product that needs servicing, the system can track the status and completion of each product separately.

Crew Management is a feature that allows creating and managing crews of multiple service resources who share the same service appointments[163]. The Preferred Resource service objective is ignored for active Crew Members because it only applies to individual resources and not crews[164]. Capacity-based scheduling is not supported for Service Crews because crews do not have capacity limits and can be assigned unlimited service appointments[165]. A service resource can be a member of multiple crews and can switch between them depending on their availability and skills[166]. Salesforce Field Service does not consider the Recommended Crew Size when assigning appointments because it only considers the Required Crew Size which indicates the minimum number of crew members needed for a service appointment[167]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.fs_service_crews_create_edit_delete.htm&type=5https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_requiredcrewsize.htm

Service Appointments are records that trackthe date, time, duration, and assigned resource for a work order or work order line item[117]. Creating a new Service Appointment for each site visit would allow Universal Containers to track when Technicians need to visit a customer site multiple times toresolve an issue by creating different service appointments for the same work order and capturing notes and status updates for each service appointment. Creating a new Child Work Order for each site visit would create unnecessary records and complexity. Child Work Orders are work orders that are related to another work order as part of a hierarchy[118]. Creating a new Product Consumed for each site visit would not track the site visits. Products Consumed are records that track the products or parts that are used or installed during a service appointment[119]. Creating a new Work Order Line Item for each site visit would not track the site visits. Work Order Line Items are records that track specific tasks or products related to a work order[120]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.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_overview.htm&type=5https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5

Service Resources are records that represent the people or equipment that perform field service tasks[143]. Work Orders are records that track customer requests for service such as repairs or maintenance[144]. Resource Absences are records that mark resources as unavailable for work for specific time periods due to sickness, vacation, or other reasons[145]. If the Field Service Lightning User Territory feature is enabled, these three objects will be visible to users who are part of the User Territory by default[146]. Accounts are records that represent companies or individuals involved in business with an organization[147]. Work Types are records that define the standard tasks and duration for a specific type of work[148]. These two objects will not be visible to users who are part of the User Territory by default unless sharing rules are configured[149]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.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_resource_absences_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_user_territories_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.fs_work_types_overview.htm&type=5https://help.salesforce.com/s/articleView?id=sf.fs_user_territories_sharing_rules.htm &type=5

This option allows automatically dispatching a certain number of Service Appointments to a technician after they complete their current one, based on a predefined criteria. References:https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatch.htm &type=5

Multi-day service appointments are used when jobs can take longer than the available resources hours in a day or require consecutive days of work and can span over weekends. Jobs that need to be performed at the same site on the same day of the week or require multiple stages of workperformed by different resources can be handled by single-day service appointments with appropriate scheduling policies and optimization rules. References:https://help.salesforce.com/s/articleView?id=sf.fs_multiday_service_appointments_overview.htm &type=5

Field Service Lightning Admin Permissions are required to set up new territories, define new schedule policies, and control settings onthe Gantt chart. These permissions allow users to access and modify field service settings and objects.

This feature shouldbe used to reduce travel time and increase technician productivity by automatically scheduling service appointments based on predefined criteria and objectives, such as minimizing travel distance or maximizing utilization. References:https://help.salesforce.com/s/articleView?id=sf.fs_optimizer_overview.htm &type=5

Frequency is a field on the Maintenance Plan objectthat defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[228]. Generation Timeframe is a field on the Maintenance Plan object that defines how many work orders should be generated from maintenance plans at a time such as 1, 2, or 12[229]. Auto-generate work orders is a field on the Maintenance Plan object that enables or disables the automatic generation of work orders from maintenance plans[230]. Setting Frequency to 1 Month; Generation Timeframe of 12; uncheck Auto-generate work orders would allow Universal Containers to offer customers a MaintenancePlan that provides 12 monthly checkups where the customer will call to schedule each visit by creating maintenance plans that generate one work order permonth for 12 months but do not generate them automatically until the customer calls[231]. Setting Frequency to 1 Month; Generation Timeframe of 1; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for one month and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 12; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for 12 months and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 1; uncheck Auto-generate work orders would not allow Universal Container

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

Customgantt filters are filters that allow dispatchers to view service appointments based on specific criteria such as status, priority, or custom fields[67]. Creating a custom gantt filter would allow providing a view of emergency work that is only visible to dispatchers by setting up criteria such as status equals emergency and sharing the filter with dispatchers only[68]. Custom lightning component is a component that allows developers to create custom user interfaces using Lightning Web Components or Aura Components[69]. Creating a custom lightning component would require coding and would not leverage the existing gantt chart functionality. Custom report in a private report folder is a report that allows users to view data based on specific criteria such as objects, fields, filters, or charts[70]. Creating a custom report in a private report folder would not provide a view of emergency work on the gantt chart and would not allow dispatchers to schedule or reschedule service appointments. Custom list view is a list view that allows users to view records based on specific criteria such as filters, fields, or sorting[71]. Creating a custom list view would not provide a view of emergency work on the gantt chart and would not allow dispatchers toschedule or reschedule service appointments. References: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filters.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filters_create.htm &type=5 https://developer.salesforce.com/docs/component-library/documentation/en/lwc https://help.salesforce.com/s/articleView?id=sf.reports_builder_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.customize_listviews.htm &type=5

Maintenance Plans are records that define the recurring service schedule for an asset or a product such as quarterly, monthly, or weekly[59]. Configuring a Maintenance Plan would allow creating quarterlyservice appointments for one of the products sold by Universal Containers automatically based on predefined criteria such as start date, end date, or generation method[60]. Defining a repeating Work Type would not create quarterly service appointments automatically. Work Types are templates that define the duration, skills, and products required for a work order or work order line item[61]. Implementing Path for Work Orders would not create quarterly service appointments automatically. Path is a feature that displays key fields and guidance for each stage of a work order process[62]. Building a Process for Service Appointments would not create quarterly service appointments automatically. Processes are automated workflows that execute actions based on specified criteria such as updating fields, sending emails, or creating tasks[63]. 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_create_edit_delete.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_types.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.path_overview.htm&type=5https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

A custom approval process on work orders is used to define the steps and criteria forapproving a work order before it can be closed. A custom validation rule on work orders is used to check the data entered on a work order and prevent it from being saved if it does not meet the specified conditions. By using these configurations, the system can prevent work orders from being closed until the customer service report is signed.

Work types can be used to assign associated articles to work orders, which can be accessed offline by technicians using the Field Service Mobile App. The Salesforce Mobile App does not have deep linking to the Field Service Mobile App. Creating a custom Mobile App that syncs articles based on service appointment assignments is not necessaryand would require additional development and maintenance. Writing a workflow that associates articles to work orders based on a picklist on thework order is not recommended and would not ensure offline access. References: https://help.salesforce.com/s/articleView? id=sf.fs_work_types.htm&type=5https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_overview.htm &type=5

Pinned statuses prevent service appointments from being rescheduled or unscheduled by scheduling and optimizationservices3. Status transitions define the valid status changes for service appointments based on business rules. References: 3 https://help.salesforce.com/s/articleView?id=sf.fs_pinned_statuses.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions.htm &type=5

A Work Order can have only one Price Book associated with it, which is determined by the Price Book selected on the Work Type. To use products from different Price Books on the same Work Order, the price on Work Order Line Items for products on other Price Books can be overridden manually or by using automation tools such as Process Builder or Apex triggers. Creating one Work Order for each Price Book or using Work Types to assign Price Books to each Work Order Line Item would not allow using products from different Price Books on thesame Work Order. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_types.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5

Products consumed are records that track the products used during a service appointment[32]. A custom installation date field on products consumed would allow reporting on the volume of products installed within a specific timeframe by filtering on the installation date field values[33]. A work order related list on asset would show the work orders associated with an asset, but not the products installed. Field history tracking on asset would track field changes on an asset, but not the products installed. The standard installation date field on asset would show when an asset was installed, but not the products installed. References: https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed.htm &type=5https://help.salesforce.com/s/articleView?id=sf.reports_filter_date_fields.htm &type=5

These two objects are required when configuring an optimization job, as they define the scope and the criteria for the optimization process. References:https://help.salesforce.com/s/articleView?id=sf.fs_optimizer_overview.htm &type=5

The In Jeopardy field on the Service Appointment is a checkbox that indicates whether a service appointment is at risk of late completion based on travel time and service duration calculations. Technicians can update this field using the Field Service Mobile App to alert dispatchers and managers of potential issues. Posting to the Service Appointment Chatter feed, changing the Status field on the Service Appointment, or adjusting the Scheduled End field on the Service Appointment would not indicate that a service appointment is in jeopardy, but would communicate otherinformation such as comments, progress, or rescheduling. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_overview.htm &type=5

A custom lightning component that displays work order progress can be created using Lightning Web Components or Aura Components and deployed to technicians through the Field Service Mobile App using Mobile App Extensions. Adding the work order line items related list to the work order page layout would not show the work progress on the work order line-item card in the Field Service Mobile App. Creating a custom visual force page or a report chart would not be compatible with the Field Service Mobile App user interface. References: https://developer.salesforce.com/docs/component-library/documentation/en/lwc https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_extensions.htm &type=5

This option allows capturing multiple signatures on a service report by creating different signature types (such as customer approval or technician verification) and adding themto the service report template. References:https://help.salesforce.com/s/articleView?id=sf.fs_signature_types.htm &type=5

This configuration can be used to brand the Salesforce Field Service mobile app by uploading a custom logo image that appears on the app’s login screen and navigation bar. References:https://help.salesforce.com/s/articleView?id=sf.fs_mobile_branding.htm &type=5

Service Resources are records that represent the people or equipment that perform field service tasks[53]. Permission Set Licenses are licenses that grant users access to specific features such as Field Service Dispatcher Console or Field Service Mobile App[54]. Creating one service resource and assigning the relevant permission set license would allow an employee at Universal Containers to perform both dispatcher and technician roles using one record and one license. Creating two skills records and assigning them to service resources record would not affect their roles or accessto features. Skills are records that define specific abilities or qualifications that service resources have[55]. Creating two service resources and assigning them to the employee would create duplicate records and require two licenses for one employee. Creating one service resource and assigning the technician and dispatcher role would not work because roles are not fields on the service resource object. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_permission_set_licenses_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm &type=5

Updating the Resource as not available allows marking a resource as unavailable for a specific time period due to sickness, vacation, or other reasons[27. Selecting the affected Service Appointments and pressing “Schedule” allows rescheduling multiple service appointments at once based on predefined criteria such as travel time or priority[28. Dragging and dropping the Service Appointments to other available Resources and running Optimization would reschedule service appointments manually and then run an optimization process that could override the manual changes[29. Asking the Customer Service Rep to call the customers and manually re-schedule for another day would not use the scheduling features of Field Service and could result in customer dissatisfactionor missed service level agreements. Changing the Scheduling Policy to “High Intensity” and activating the Background Optimization process would change the optimization criteria for all service appointments and run an optimization process in the backgroundthat could take a long time to complete[30. References: https://help.salesforce.com/s/articleView?id=sf.fs_resource_absences_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_schedule_service_appointments.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_global_optimization_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_background_optimization_overview.htm &type=5

Sort by Average Utilization is an option on the Resources Tab of the Gantt chart that allows sorting resources by their average utilization percentage[239]. Utilization is a metric that measures how much time a resource spends on service appointments compared to their total working hours[240]. Selecting Sort by Average Utilization on the ResourcesTab would allow Universal Containers to identify which resources need more or fewer appointments by showing them how busy each resource is based on their utilization percentage[241]. Selecting Date Resolution on the Hours Tab would not allow Universal Containers to identify which resources need more or fewer appointments. Date Resolution is an option on the Hours Tab of the Gantt chart that allows changing how many hours are shown per column such as 1 hour, 2 hours, or 4 hours[242]. Selecting Travel Time and Breaks as skills on the Skills Tab would not allow Universal Containers to identify which resources need more or fewer appointments. Skills are records that define specific abilities orqualifications that resources have[243]. Travel Time and Breaks arenot skills but fields on the Resource object that define how much time a resource spends traveling between service appointments and how much time they take for breaks[244]. Selecting Hours, Absences and Overtime on

The Exclude Technician from Geolocation Tracking permission allows disabling geolocation tracking for specific service resources by assigning them a permission set with this permission. Setting the Geolocation Update Frequency field tozero for contractors would not disable geolocation tracking, but would make it update less frequently. Unchecking the Geocoding field on the Contractor’s profile or the Collect Service Resource Geolocation History field in Field Service Mobile Settings would not affect geolocation tracking, as these are not related settings. References: https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_permissions.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_settings.htm &type=5

A custom Price Book allows different prices for the same products in different markets. A standard Price Book has the same prices for all markets. Pricing rules arenot available for Field Service Lightning. References: https://help.salesforce.com/s/articleView?id=sf.pricebook_custom.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.pricebook_standard.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_pricing.htm &type=5

Service Territory Location is a junction object that links Service Territory and Location objects[236]. Related Lists are components on page layouts that show records that are related to a record through a lookup or master-detail relationship[237]. Adding the Service Territory Location Related List on the Service Territory page layout and adding the Service Territory Location Related List on the Location page layout would allow Universal Containers to show howLocations are associated to Territories by displaying a list of Service Territory Locations on each record[238]. Creating the Service Territory Location as a Service Territory lookup field or creating the Service Territory Location as a Location lookup field would not work because they are not valid fields on either object. References: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceterritorylocation.htm https://help.salesforce.com/s/articleView?id=sf.customize_related_lists.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_service_territory_locations_overview.htm &type=5

This option allows tracking individual tasks completed as work order line items, including parts consumed and pricing details, and scheduling one or multiple tasks to different technicians as needed using service appointments. References:https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5

This option allows the Resource Skill to expire when the certification expires, and prevents the resource from being scheduled for jobs that require that skill. References:https://help.salesforce.com/s/articleView?id=sf.fs_resource_skills.htm &type=5

These three options are available to the dispatcher to schedule service appointments from the dispatch console while taking the scheduling policy into consideration. References:https://help.salesforce.com/s/articleView?id=sf.fs_dispatch_console_schedule_appointments.htm &type=5

Scheduling, dispatching, and knowledge base are three field service processes that can help reduce the mean-time-to-service. Scheduling is the process of assigning service appointments to resources based on their availability, skills, and location. Dispatching is the process of sending service appointments to resources and tracking their status and location. Knowledge base is a repository of articles that provide information and solutions for common issues and questions.

Excluded Resources are used to prevent certain service resources from being assigned to specific accounts or locations based on customer feedback or preferences. Assigning theTechnician to a new Service Territory would affect all their service appointments, not just those for that Customer. Removing the Technician as a Preferred Resource would not prevent them from being assigned to that Customer, but would lower their priority. Creating a new Work Order Validation Rule would not affect the scheduling or optimization of service appointments, but would only validate data entry on work orders. References: https://help.salesforce.com/s/articleView?id=sf.fs_excluded_resources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_territories.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_preferred_resources.htm &type=5

Earliest Start Permitted is a field on the Service Appointment object that defines the earliest date and time that a service appointment can start[222]. Due Date is a field on the Service Appointment object that defines the latest date and time that a service appointment must be completed by[223]. Using Earliest Start Permitted and Due Date fields on Service Appointments would help ensure that they are completed within the agreed upon Service Level Agreement (SLA) with Universal Containers’ customers by setting the boundaries for when a service appointment can start and finish according to the SLA terms[224]. Actual Start andActual End are fields on the Service Appointment object that capture the actual date and time that a service appointment started and ended[225]. Using Actual Start and Actual End fields on Service Appointments would not help ensure that they are completedwithin the agreed upon SLA with Universal Containers’ customers because they are recorded after the service appointment is performed and do not enforce any SLA terms. Arrival Window Start and Arrival Window End are fields on the Service Appointment objectthat define the expected date and time range that a resource will arrive at a service appointment[226]. Using Arrival Window Start and Arrival Window End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate when a resource will arrive and do not enforce any SLA terms. Scheduled Start and Scheduled End are fields on the Service Appointment object that define the planned date and time range thata service appointment will take place[227]. Using Scheduled Start and Scheduled End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate whena service appointment is scheduled and do not enforce any SLA terms. References: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment.htmhttps://help.salesforce.com/s/articleView?id=sf.fs_sla_overview.htm &type=5

Street Level Routing is a feature that calculates travel time between service appointments based on actual road distance and traffic conditions[131]. DefaultTravel Speed is a setting that defines the average speed of resources when traveling between service appointments[132]. Using Street Level Routing and Default Travel Speed would allow improving travel time accuracy by taking into account real-time road conditions and resource speed. Minimum Grade, Default Operating Hour would not affect travel time accuracy. Minimum Grade is a setting that defines the minimum skill level required for resources to be matched with service appointments[133]. Default OperatingHour is a record that defines the default working hours for resources[134]. Estimated Travel Time, Minimize Travel would not affect travel time accuracy. Estimated Travel Time is a field on the service appointment object that shows the expected travel timefor the assigned resource[135]. Minimize Travel is an optimization criterion that prioritizes reducing travel time when scheduling service appointments[136]. Travel Speed Unit, Actual Travel Time would not affect travel time accuracy. Travel Speed Unit isa setting that defines the unit of measurement for travel speed such as miles per hour or kilometers per hour[137]. Actual Travel Time is a field on the service appointment object that shows the actual travel time recorded by the resource[138]. References: https://help.salesforce.com/s/articleView?id=sf.fs_street_level_routing_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_default_travel_speed.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_minimum_grade.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_default_operating_hours_overview.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_estimatedtraveltime.htm https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_travel_speed_unit.htm &type=5https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_actualtraveltime.htm

Maintenance Plans are records that define recurring work orders for preventive maintenance such as inspections or tune-ups[188]. Auto-generate Work Orders is a setting that enables or disables the automatic generation of work orders from maintenance plans[189]. Generation Timeframe is asetting that defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[190]. Generation Horizon is a setting that defines how far in advance work orders should be generated from maintenance plans such as 7days or 30 days[191]. Auto-generating Work Orders with a 14 day Generation Timeframe and a 14 day Generation Horizon would allow Universal Containers to automatically generate Work Orders 14 days before the next suggested maintenance date by creating workorders from maintenance plans every 14 days within14 days of their scheduled date. Associating a Required Skill called Site Visit to a Maintenance Plan would not affect how far in advance work orders are generated from maintenance plans. Required Skills are fields on the maintenance plan object that indicate which skills are needed for performing preventive maintenance[192]. Associating a Work Type called Site Visit to a Maintenance Plan would not affect how far in advance work orders are generated from maintenance plans. Work Types are records that define the standard tasks and duration for a specific type of work[193]. 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_auto_generate_work_orders.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_timeframe.htm

Service Resources are records that represent thepeople or equipment that perform field service tasks[199]. Permission Set Licenses are records that grant users access to specific features or apps such as Salesforce Field Service[200]. Creating one Service Resource and assigning the relevant Permission Set Licenses would allow Universal Containers to configure Salesforce Field Service to support an employee who performs the role of a Dispatcher and a Technician by creating a service resource record for the employee and assigning them the Salesforce FieldService Dispatcher and Mobile permission set licenses[201]. Creating two Service Resources and assigning them to the employee would not work because an employee can only be associated with one service resource record[202]. Creating one Service Resource andassigning the Technician and Dispatcher role would not work because roles are records that define the level of access users have to data in an organization hierarchy[203]. Creating two Skills records and assign them to the Service Resource record would not work because skills are records that define specific abilities or qualifications that service resources have and do not affect their access to features or apps[204]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.perm_sets_license_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_perm_sets_license_assign.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_create_edit_delete.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.roles.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm &type=5

The book appointment action is used to schedule a service appointment based on service objectives and resource availability. Theaction displays a list of potential time slots with service objective scores for each slot. The higher the score, the better the slot meets the service objectives.

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 variouscriteria 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 thetravel time between locations if a different travel speed is not specified for the resource.

These two considerations impact the scheduled timeframe of multi-day work, as they affect the availability and capacity of the resource assigned to the work. References:https://help.salesforce.com/s/articleView?id=sf.fs_multi_day_work.htm &type=5