The right technician, the right part, the first time.
Dynamics 365 Field Service from work order to completed job: scheduling, the technicians' mobile app and the integrations that make planning smarter.
Mobile app
Work order
Sound familiar?
Planners schedule jobs on a whiteboard or in Excel, and every change means a round of phone calls.
Technicians arrive without the right part or the history of the asset they're repairing.
Work orders are closed on paper and typed in again at the office, days later.
Standard where it works. Specialists where it counts.
Field Service handles work orders, scheduling and the mobile app out of the box. Where planning or diagnosis needs more, I connect specialist services through plugins and Azure Functions, so the technician still works in one app.
Where the work comes from
Customer Service cases
Escalated to a work order
IoT alerts
From connected assets
Maintenance agreements
Recurring work orders
What I implement
Plugin framework and Azure Functions
Dynamics 365 Field Service
Specialist services
Solvice
Route optimization
Vintecc
AI image recognition
ERP
Inventory and invoicing
Your own system
via API
Azure Integration Services · Microsoft Entra ID · monitoring
What I deliver
Work orders that drive the job
Incident types, service tasks and assets modeled so a work order carries everything the technician needs.
Smarter scheduling
The schedule board, plus route optimization and external planning engines when the standard isn't enough.
A mobile app technicians like
The Field Service mobile app with offline profiles, and PCF controls where the standard forms fall short.
Integrations in the field
Connections to external services such as AI image recognition, inventory and ERP, built on Azure.
Where I've done this
On my current project at Savaco I'm the technical lead on Dynamics 365 Field Service, including integrations with Vintecc for AI image recognition and Solvice for route optimization.
More about meHow I work
01
Discover
Understand your processes, data and goals before a single line of code is written.
02
Design
Architect a solution that fits the platform: configuration first, code where it counts.
03
Build
Deliver in short iterations with automated tests and source-controlled solutions.
04
Deliver
Ship through CI/CD pipelines, document, and hand over a solution your team can own.
Go deeper
The technical guides behind this solution.