Explanation:

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 a setting 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 7 days 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 work orders from maintenance plans every 14 days within 14 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=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_timeframe.htm

Explanation:

This option allows recording the required work for each component separately, and tracking the status and progress of each Work Order Line Item.

References:

https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm&type=5

Explanation:

Capacity-Based Service Resources are service resources that have a limited number of hours available for work per day or week[150]. Setting the Contractor Manager as a Capacity-Based Service Resource would allow Universal Containers to outsource 100 hours of weekly maintenance to an external Contractor by setting up criteria such as capacity hours per week equals 100 and capacity type equals weekly[151]. Creating the individual Technicians as Service Crew Members would not work because Service Crew Members are service resources that belong to a crew and share the same service appointments[152]. Setting the individual Technicians as Capacity-Based Service Resources would not work because Universal Containers does not have visibility into the individual external technicians. Creating the Contractor Manager as a Crew Service Resource would not work because Crew Service Resources are service resources that act as leaders or managers of a crew and can assign crew members to service appointments[153].

References:

https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_capacity_based.htm& type=5

https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_capacity_based_crea te_edit.htm&type=5

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_create_edit_delete.htm&t ype=5

Explanation:

This question focuses on the process for a technician to order parts from an inventory location to their current location.

A Product Request is the master object that represents the entire request to transfer inventory from one location (e.g., a central warehouse) to another (e.g., the technician's van or a local depot). It contains header-level information like the source and destination locations.

Product Request Line Items are the child records of the Product Request. Each line item specifies the exact product and the quantity being requested. A single Product Request can contain multiple line items for different products.

This two-step process (create the header record, then add line items) is the standard and supported way to request parts in Salesforce Field Service inventory management.

🔴 Option A is incorrect: A Shipment is created to represent the fulfillment of a transfer or order (like a Product Request) once it is being acted upon, not the initial request itself.

🔴 Option B is incorrect: Product Consumed is used to record parts that have been used on a Work Order, reducing on-hand inventory. It is not used to request new parts.

🔴 Option D is incorrect: A Work Order Line Item defines a product needed to complete a job. While it can be the reason for a parts request, it is not the mechanism for creating the request itself. The request process is handled through the dedicated Product Request objects.

🔗 Reference:
Salesforce Help: "Request Inventory Using the Mobile App"
Key Concept: The Product Request object is the formal way to request a transfer of inventory, and it contains Product Request Line Items for the specific products needed.

Explanation:

Work Orders are records that track customer requests for service such as repairs or maintenance[87]. Work Order Line Items are records that track specific tasks or products related to a work order[88]. Service Appointments are records that track the date, time, duration, and assigned resource for a work order or work order line item[89]. Using this data model would allow Universal Containers’ technicians to follow a standard operating procedure while performing maintenance on an individual asset by creating different work order line items for different operations and capturing notes and status updates for each line item. It would also allow scheduling and dispatching one service appointment for one visit. Service appointment to represent preventative maintenance on the asset - work order line item to represent the different operations - work order to represent the visit would not work because service appointments cannot be related directly to assets. Work order line item represent preventative Maintenance on the asset - work order represent the different operations- service appointment to represent visit would not work because work order line items cannot be related directly to assets.

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=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm&type=5