Drag and Drop Question A heating and cooling company uses many disparate systems to track technicians and the work performed at customer sites. A dispatcher wants to implement Dynamics 365 Field…

Question

Answer Area

Explanation

This question tests knowledge of the Dynamics 365 Field Service lifecycle and which stage maps to each operational requirement a dispatcher might encounter when transitioning from legacy systems.

Approach. The three requirements map to the middle stages of the Field Service lifecycle: (1) 'Work order' is the core record that captures what work needs to be done, the location, required skills, and parts - it is created before any scheduling occurs. (2) 'Schedule' is the stage where a technician with matching skills and availability is booked to the work order, typically using the Schedule Board or Resource Scheduling Optimization (RSO). (3) 'Service' is the stage where the field technician is on-site performing the actual work, logging time, parts consumed, and task completions - often via the Field Service mobile app. The other lifecycle stages (Case, Dispatch, Review/Approval) are valid stages but do not match the specific requirements presented in this scenario, which focuses on work documentation, resource booking, and on-site execution.

Concept tested. Dynamics 365 Field Service end-to-end lifecycle: understanding the sequential stages (Case -> Work Order -> Schedule -> Dispatch -> Service -> Review/Approval) and which operational activities belong to each stage, particularly Work Order creation, Schedule Board assignment, and on-site Service execution.

Reference. Microsoft Learn - Dynamics 365 Field Service: Work order lifecycle and statuses (https://learn.microsoft.com/en-us/dynamics365/field-service/work-order-status-booking-status)

No community discussion yet for this question.