New guide: assessing organisational readiness for Microsoft 365 Copilot. Read the guide

Industrial Manufacturing Group ยท Manufacturing

Field service scheduling and asset history for a manufacturer

Work order management, mobile capture with intermittent connectivity, and a consolidated asset service history.

20 January 2026 Manufacturing

Technologies

  • Dynamics 365 Field Service
  • Power Apps
  • Dataverse
  • Power BI
  • Microsoft Azure

Outcome themes

  • Scheduling visibility
  • Asset history
  • Offline capability

Client context

A manufacturer maintains installed equipment at customer sites. Work is scheduled by regional coordinators using spreadsheets and telephone calls. Engineers record work on paper forms that are keyed in later, sometimes days after the visit.

The challenge

Customer sites frequently have poor connectivity, so a purely online mobile experience will not work. Asset history is fragmented across paper records and several systems, making preventive maintenance planning impossible. Parts availability is not visible at the point of scheduling.

Objectives

  • One scheduling view across regions with skills and parts visibility
  • Mobile capture that works reliably without connectivity
  • A consolidated service history per asset
  • Preventive maintenance planning based on actual service records
  • Reduced delay between visit and recorded work

The solution

Work orders, assets, skills and parts are modelled in Dynamics 365 Field Service, with scheduling visibility across regions. Engineers use the mobile experience with offline capability, capturing work, parts consumed, photographs and customer sign-off, synchronising when connectivity returns. Asset records consolidate service history, enabling preventive maintenance scheduling based on actual intervals. Reporting covers scheduling efficiency, first-time fix and parts consumption.

Architecture

  • Dynamics 365 Field Service for work order, asset, resource and scheduling management
  • Field Service mobile with offline profiles scoped to the engineer assigned work
  • Dataverse as system of record for assets, work orders and service history
  • Integration to the ERP for parts inventory and customer master data
  • Power BI reporting on scheduling, first-time fix and consumption
  • Azure integration services for scheduled and event-based ERP synchronisation

Delivery approach

How the work ran

  1. Discover

    Field observation with engineers and coordinators to capture real working conditions, including connectivity.

    Process maps Connectivity assessment Data inventory
  2. Design

    Work order model, offline profile scope, scheduling rules and ERP integration design.

    Solution architecture Offline design Integration specification
  3. Build

    Configuration, mobile experience, integrations and asset history migration.

    Configured solution Mobile experience Migration output
  4. Validate

    Field testing in genuinely low-connectivity locations, not simulated conditions.

    Field test evidence Defect log Sign-off
  5. Adopt

    Regional rollout with engineer coaching and coordinator enablement.

    Training material Rollout plan Hypercare log

Outcomes

What changed

Cross-region scheduling visibility

Coordinators schedule against skills, location and parts availability in one view.

Reliable capture without connectivity

Work is recorded at the point of service and synchronised on reconnection.

Consolidated asset history

Service records accumulate against the asset, enabling preventive planning.

Shorter recording delay

Work reaches the system on the day it is performed rather than days later.

Lessons learned

What we would tell the next organisation

Every engagement produces something worth carrying forward. These are the points that mattered most in this one.

  • Offline profiles must be scoped tightly. Broad profiles cause synchronisation times engineers will not tolerate.
  • Field testing has to happen in real low-connectivity locations. Simulated testing misses the failure modes that matter.
  • Engineer input during design determines whether the mobile experience is used as intended.

More customer stories

Next step

Start with the problem, not the platform

The first conversation is about what is not working today. Product selection comes later, and sometimes the answer is that you do not need a new one.

Talk to an expert Solutions