[object Object]

A facilities manager wants to know why the same HVAC unit has been serviced four times this quarter and the parts cost is climbing. The answer lives in Field Service, but only if the work orders, assets, and parts are linked correctly. A field service deployment without these links produces lots of activity reporting and almost no insight.

Work Order Lifecycle

Work order to scheduled to dispatched to in progress to completed to invoiced. Connects to case management (service events) and asset records (what is serviced). The work order is the core entity; everything else hangs off it. Get the work order schema right and the rest of the configuration follows.

Work order linkages:
- Customer (account or contact)
- Service account (where the work happens)
- Asset (what is serviced)
- Originating case (if from customer service)
- Bookable resource booking (the technician assignment)
- Parts and services (what was used)

The asset link is the one most teams skip during initial rollout. Without it, you cannot ask “how often does this unit fail.”

Universal Resource Scheduling

URS is the scheduling engine. Considers skills, location, availability, customer priority. Schedule Board gives dispatchers a visual view; Schedule Assistant suggests optimal assignments. The scheduling engine works on constraints; the more constraints you model, the better the suggestions.

Scheduling constraints:
- Required characteristics (skills, certifications)
- Territory match
- Working hours
- Travel time from previous booking
- SLA on the work order
- Customer preference for specific resource

The travel time calculation requires Bing Maps integration; without it, the scheduler picks the resource without considering distance.

Field Service Mobile

The mobile app is where the technician works. Offline-capable, shows work orders, parts, knowledge, forms. Customize mobile forms per job type for fastest completion. The mobile form is not the same as the desktop form; build a slim version that the technician can complete in under two minutes.

Mobile work order form essentials:
- Customer name and contact
- Service address with map link
- Asset details with QR scan
- Required tasks checklist
- Parts used capture
- Customer signature
- Photos (before, during, after)

Test the form on the actual phone the technicians use. Field reality is harsh on UI choices.

Connected Field Service

IoT integration triggers work orders automatically when sensors report anomalies. Predictive maintenance use cases — value depends on your IoT investment and data quality. The integration uses Azure IoT Hub or Event Grid to deliver telemetry; the rule engine on the Dataverse side decides when to create a work order.

IoT trigger flow:
1. Sensor reports anomaly to IoT Hub
2. Stream Analytics or Function classifies severity
3. Event creates a Dataverse alert record
4. Alert rule converts to a work order if criteria match
5. Scheduler assigns based on URS

The classification step is critical. Without it, every minor anomaly creates a work order and the technician queue floods.

Asset Hierarchy

Assets nest. A building contains floors, floors contain HVAC systems, HVAC systems contain compressors. Modeling the hierarchy lets you ask questions at any level. Compressor failure rate by manufacturer, building service cost, system uptime. Without the hierarchy, every asset is a flat record and the questions stop at “what failed.”

Reporting

KPIs to track: first-time fix rate, travel time, utilization, customer satisfaction. Field service margin depends on these. The first-time fix rate is the most actionable metric; a drop usually means parts shortages or skill mismatches.

<fetch aggregate="true">
  <entity name="msdyn_workorder">
    <attribute name="msdyn_workorderid" aggregate="count" alias="total" />
    <attribute name="msdyn_firsttimefix" aggregate="countcolumn" alias="ftf" />
    <filter>
      <condition attribute="msdyn_systemstatus" operator="eq" value="690970004" />
      <condition attribute="msdyn_completedon" operator="last-x-days" value="30" />
    </filter>
  </entity>
</fetch>

Track this weekly. Below 80 percent first-time fix is a margin problem.

Inventory Awareness

Field Service integrates with the warehouse and truck inventory tables. A technician dispatched without the right part on the truck wastes the trip. Build a check into the work order creation that validates parts availability before scheduling.

What to do this week

Audit your work orders for asset linkage and fix the orphans. Build the first-time fix dashboard and review with the dispatch team weekly. If you have IoT integration, validate the classification step is filtering noise before creating work orders.

[object Object]
Share