10T Studios
← All solutions

Solutions

Systems for water utilities

Short answer

A water operator usually does not suffer from lacking a billing system. It suffers from what happens around it: a burst main that arrives by phone and ends up on a paper slip, meter readings typed in twice, work orders split between email, Excel and the dispatcher's memory. We build a custom system for that layer and connect it to what you already have, meaning billing, GIS and network monitoring. We do not recommend replacing the billing core as a first step. With organisations like this the audit gives the price, because it is driven by integrations and security requirements, not by the number of screens.

01What such a system holds

The objects of work are different from an office. They happen outdoors, to a deadline, with consequences for customers.

  • 01A fault or burst — taking the report, the location on the network, assignment to the on-call crew, shut-offs and notifying affected customers, closing it with a description of the intervention.
  • 02A field work order — a repair, meter replacement, connection or inspection; with the person responsible, materials, photos and a signature.
  • 03A meter reading — entered in the field, a photo of the dial, checked against the previous period, with unusual consumption flagged.
  • 04A customer request or complaint — with a reply deadline and the person handling it.
  • 05An asset register — network sections, manholes, hydrants, pumping stations, reservoirs, and for each the history of interventions, inspections and repairs.
  • 06Material for reports — what was done, where and how much, in a form from which a report can be assembled rather than retyped.

02Faults and field work orders

A fault is usually the most sensitive process. A customer calls, a report comes from the municipality, or monitoring picks up an alarm. The dispatcher needs to see in one place where it is, who is on call, what is already in progress and whose supply it affects. After the intervention it is written down what was found, what was repaired and what material was used, and it is written down in the field, not in the evening from memory.

The same holds for ordinary work orders. The technician has the day's list on their phone, a map, and the order with the history of the place. Where there is no signal they enter what is needed and the system sends it once the connection returns. The history then shows places that keep being repaired, which is more useful than any report.

The customer hears about progress however you already do it: an SMS or email for a fault, a reply for a request. The system only makes sure nothing drops off the list.

03Readings, billing and integrations

Readings and billing have two parts that need to be kept apart. Collecting readings is field work and belongs in a system you can use on a phone. The settlement itself, meaning advances, water and sewerage charges and invoices, is done by your current billing system and should stay there. We hand it the readings in an agreed format and do not recalculate them. Customers can submit their own reading through a simple page if you want that, and the system files it with the field readings.

GIS is the source of location and of what is in the network. The system reads from it the objects that belong to an order, and in the other direction returns the intervention history to the objects. How exactly depends on what your GIS offers, which is why it is found out in the audit.

We approach network monitoring (SCADA) with caution. Only what is needed is read, through an agreed interface, never by connecting into the control network, and the system writes nothing back to the technology. The aim is that an alarm from monitoring shows up in the fault queue, not that we control pumps.

Running on your infrastructure or in your data centre is possible. Access is by role, changes go into an audit log, and customer data is personal data with everything that implies.

04When you do not need this, and when not to pick us

If the organisation is small, say a municipality with its own water and two people in operations, a ready-made module for the billing system or a shared spreadsheet with a fixed procedure will probably do. A custom system starts to pay off when several separate lists run around billing and nobody can say which one is current.

Public procurement is another matter. A publicly owned operator usually cannot award a larger system informally, and the procurement cycle is long. That is a reasonable condition and we do not work around it. The audit and its output can serve as a basis for the specification even if someone else is finally chosen, and they do not tie you to us.

If the task is replacing the entire billing and customer core for tens of thousands of customers, it is not a project for a small studio and we will say so at the outset. A great deal can still be done around such a core.

05How it starts

With a fixed-price audit. We look at how a fault, a work order and a reading run today, what systems you already have and where data is retyped. You get a document with what can be simplified, what the integrations are and a price range. The document is yours even if you decide not to go on.

The first usable part is typically ready in a few weeks: work orders and faults for one depot, where the difference shows straight away. Further depots, readings and the network register are added piece by piece, without interrupting operations. The code and the data stay with you.

Frequently asked

Will you replace our billing system?
Not as a first step, and usually not at all. The billing core does the settlement and a lot is tied to it. Around it we deal with readings, faults, work orders and requests, and hand it data in an agreed format.
Can the system run on our own servers?
Yes. For network operators it is a common requirement and we plan for it from the start, along with roles and an audit log of changes. The exact deployment is agreed in the audit.
What about the regulator and reports?
The system does not fill in regulator forms for you. It keeps data on interventions, readings and assets so that a report can be assembled from what is already recorded. The specific report format is gone through in the audit with the responsible person on your side.
How much does it cost and how long does it take?
For a smaller operator a first part can come to between €2,000 and €10,000. For larger organisations it is more and depends on integrations and security requirements, which is why we give a price only after the audit. A first usable part takes a few weeks.

Where next