industry
Assets on a cycle, customers on an appointment.
Water and wastewater, gas networks, generation and metering, spread wide enough that travel is a real cost in the plan.
what is different here
Two kinds of work, one region.
-
An inspection round is not an appointment
Treatment works and pump stations are planned around the asset and the route. A metering or connection visit is planned around a customer being in.
in Etaprise → asset-driven rounds and booked windows on the same schedule
-
A reading without an asset and a time is not evidence
Samples, readings and consumables get written down, then attached to the wrong site or dated by memory when the report is compiled weeks later.
in Etaprise → captured against the asset, at the time, on the visit
-
The regulator asks for a period, not a document
The request is every inspection on a class of asset over a quarter. Answering it from folders and spreadsheets is a project each time.
in Etaprise → queried across the period, with the record behind each line
On site
the setup
The modules that carry most of the weight here.
The other eleven are still there. Sector setup changes which forms attach to a job, which certifications gate an assignment, and what a closed job has to prove, not which software you are running.
what a rollout looks like
In order, and with honest timings.
Inspection cycles are the backbone and customer appointments are the constraint. This sequence loads the recurring asset work first, then adds the visits where a person has to be at home.
-
weeks 1–3
Inspection cycles and rounds
Treatment works, pump stations and network points with their visit frequencies and routes, so the recurring programme is running before anything else changes.
-
weeks 2–5
Readings, samples and forms
Build the capture the operation already uses on paper, with mandatory fields and units, so a reading is tied to an asset and a timestamp the moment it is taken.
-
weeks 4–8
Metering and connection appointments
Customer-premises work booked into windows, with access notes and the travel legs planned against the same crews already committed to asset rounds.
-
ongoing
Environmental and regulatory reporting
Once the capture is consistent, a period can be queried rather than assembled: what was inspected, by whom, what was recorded, and what was raised as a result.
questions from this sector
The objections we hear, answered plainly.
Yes, and that is the point of putting them together. A booked customer window is a hard constraint the schedule works around; an inspection round is flexible within its cycle. Held apart, the two plans quietly double-book the same crew.
Common on remote plant and rural network points. The app holds the job, its forms and its asset history offline, captures readings and photographs on site, and syncs when the vehicle is back in coverage.
Then travel is part of the plan rather than an afterthought. Rounds are sequenced geographically and a same-day insertion shows what it costs in driving before it is committed, not after.
No. Those systems tell you the state of the network. This one carries the work that follows: raising the job, sending the right person, capturing what they found, and holding the evidence against the asset afterwards.
further reading
Further reading
Bring us a week of your jobs.
One inspection round and one day of appointments. We will schedule them together.
Book a demoother industries