How a French water treatment company structured its scheduling in less than six weeks
Already equipped with field service management software and an ERP, this company was not looking for another tool. It wanted to automate, optimize and govern its scheduling — with an internal objective of redeploying 2 to 3 planner FTEs.
An implementation designed to meet the deadline thanks to a scope defined from the pre-sales stage, workstreams run in parallel and a single Nomadia point of contact.
This case study was written during final integration, before go-live. Post-deployment gains will be updated six months after go-live, with the client’s approval.
The company services industrial and domestic equipment across several business subsidiaries. The initial project scope covers 30 field technicians and 3 full-time planning assistants.
The real issue was not the tool
The client already had software components in place. What was missing was an optimization and governance framework capable of turning individual practices into a managed operating model.
Fragmented scheduling
Each planner built daily schedules in their own way, without an engine to arbitrate resource allocation. Technicians were already completing 4 to 5 appointments a day in assigned territories, so the main opportunity was not mileage reduction.
The real lever was elsewhere: automate scheduling, standardize operations and free up time for higher-value work.
An ambition driven by leadership
A change in operations leadership created the momentum. The objective was clear: make scheduling a managed business asset, rather than a collection of individual practices.
The internal target: save the equivalent of 2 to 3 planner FTEs, which can be redeployed to other activities.
Define the scope before launch
To prevent scope creep, Nomadia separated requests from the pre-sales stage. This discipline is essential to meet a short deadline without turning the project into a custom development programme.
Lot 1 · Included foundation
The essential scope for launch, covered by Nomadia’s pre-configuration and methodology.
Lot 2 · Priced option
Additional requests are identified, separated and priced independently.
Lot 3 · Out of scope
Anything not required for launch is excluded or scheduled for a later phase, with no ambiguity.
Two structuring decisions
Hotel nights: the topic was accepted on the condition that Nomadia’s methodology would be applied instead of reproducing the client’s historical practice. Guidance replaced custom development.
Quotes and invoicing: requests based on consumed parts were excluded. The scope is limited to viewing unit prices, with no inventory management or invoicing.
The selected setup
36 subscriptions · 50 service days · Nomadia hosting
The project is led by Bruno Renimel, Nomadia project manager and the client’s single point of contact.
Run workstreams in parallel, not sequentially
The client had an internal IT team capable of developing the integration APIs. The Express deployment methodology builds on this capability: Nomadia exposes its APIs and documents the platform while the client develops its connectors.
A jointly built schedule
Each party commits to its own deadlines: the client for the APIs, Nomadia for the configured engine.
Workstreams run in parallel
Requirements modelling, unit testing, configuration and integration development move forward without downtime.
An orchestrated final connection
Integration is not postponed to a separate phase: it joins a configuration that is already prepared.
What this should change for the client
Within the initial scope of 30 technicians and 3 planners, the expected benefits after 12 months focus on four operational levers.
-
Automate scheduling
Move from fragmented operations to scheduling supported by the Nomadia engine, with an internal objective of redeploying 2 to 3 planner FTEs.
-
Modernize field execution
Standardize practices through the technician mobile app, digitized service reports and a complete offline mode.
-
Give customers more autonomy
Enable contracting parties and end customers to book appointments through a portal using the client’s visual identity.
-
Prepare a scalable architecture
Connect inventory management via API and prepare a phased rollout to the parent company, a direct subsidiary and then other entities.
Why the methodology works here
The difference does not come from shortcuts taken during the project. It comes from the way the project is structured from the moment it is signed.
✓ Favourable conditions
- An operations leadership team that clearly owns the ambition
- A client IT team that is available and able to develop the APIs
- An initial scope covered by pre-configuration and kept under control
- A client lead and a Nomadia contact able to make decisions quickly
⚠ Points to watch
- A project that would depend entirely on custom development
- A scope that continued to expand after signature
- Insufficient client availability for APIs and testing
- No sponsor or fast decision-making for key trade-offs
Starting a Field Service Management project?
In 30 minutes, review your current setup, identify the conditions for success and estimate the potential of your own scope.
About Nomadia. Nomadia is a European field operations optimization provider, with more than 200,000 users in 95 countries. Nomadia Field Service Management structures, schedules and manages field interventions.
