Customer case study
Microsoft Dynamics 365 Field Service Staffing at Ridgeway Utilities
Engagement summary
Ridgeway Utilities added one full-time Microsoft Dynamics 365 Field Service consultant from MS Dynamics Guys from March to September 2024 to configure work orders, scheduling and technician mobile workflows for 240 field engineers. Dispatch supervisors signed off on 13 September. Ridgeway’s field service analytics recorded 21.7 jobs completed per engineer per week in the 60 days after rollout, up from 18.2.
Engagement Facts
| Field | Detail |
|---|---|
| Client | Ridgeway Utilities, 1,900 employees |
| Industry | Utilities |
| Client and delivery locations | Cardiff, UK / Lisbon |
| Product | Microsoft Dynamics 365 Field Service |
| Roles | 1 D365 Field Service consultant (full-time) |
| Engagement dates | 4 Mar – 20 Sept 2024 |
| Overlap | 7 hours GMT |
| Reporting line | Client Field Operations Manager |
Why the Client Added Capacity
Ridgeway was replacing a legacy scheduling system. Its internal team knew the utility’s field operations and needed a Microsoft Dynamics 365 specialist to configure those workflows for dispatchers and engineers.
Decision Rights
| Decision | Owner |
|---|---|
| Workflow design | Consultant proposes; Field Ops Manager approves |
| Scheduling policy | Dispatch supervisors |
| UAT acceptance | Field Ops Manager |
| Release authorisation | Programme Director |
Work Delivered
The consultant configured 48 service territories, seven scheduling policies and 12 work types. The mobile workflow covered parts consumption and customer signatures so the dispatch team could test a complete work order. Dispatch supervisors set scheduling policy and reviewed the workflows, the Field Operations Manager approved them, and the Programme Director authorised release.
| Role | Assignment | Accepted output | Reviewer | Approver |
|---|---|---|---|---|
| Field Service consultant | Work-order and scheduling | 48 service territories, 7 scheduling policies, 12 work types | Dispatch supervisors | Field Ops Manager |
| Field Service consultant | Technician mobile | Mobile work-order flow with parts consumption and customer signature; 6 scenarios tested | Dispatch supervisors | Field Ops Manager |
Outcomes
The user acceptance record shows six of six work-order scenarios signed. The programme log records that the planned 16 September rollout date was met.
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Jobs per engineer per week | 18.2 | 21.7 | 60 days post-rollout | Field service analytics |
| Work-order scenarios signed | — | 6 of 6 | Sept 2024 | UAT record |
| Rollout date | Planned 16 Sept | Met | — | Programme log |
| Dispatch supervisor sign-off | — | Signed 13 Sept 2024 | — | Acceptance record |
| First accepted configuration | — | 10 business days | Mar 2024 | Client ticket record |
Client perspective
“Our dispatchers tested it, not the project board. That's how we knew it would work on a Monday morning.”
Your next step
Discuss the capacity your team needs
Share the application, workstream and specialist allocation you need. Your team can define its own backlog, acceptance and release responsibilities.