WATER SERVICE PROVIDERS · GUIDE 01
A definition for water and sanitation service providers, and what the system has to hold.
A water utility management information system is the connected set of records a service provider uses to run a service: the customers it serves, the infrastructure it operates, the work it carries out on that infrastructure, and the money it bills and collects. It is often shortened to utility MIS. What separates it from a billing package is that the customer, the meter, the connection, and the pipe are one linked record seen from different sides, rather than four separate lists that have to be reconciled by hand.
A provider with a utility MIS can start from a leaking pipe and reach the households that will lose supply, the bills they were sent last month, and the technician who last worked on that section. A provider without one can answer each of those questions separately, from a different file, and cannot answer them together.
Four points settle what the category is before the detail that follows.
Most service providers already hold every piece of information a utility MIS contains. It sits in a customer ledger, a meter reading book, an asset inventory drawn up for a past project, and a maintenance log. Each is accurate on its own terms. None of them agree with each other, because nothing forces them to.
The cost of that separation shows up as specific, recurring failures. A connection built last year never reaches the customer register, so it is never billed. A meter reader records a reading against a customer who moved out. A repair is completed but the fault stays open because the technician reported it by phone. A board asks for collection efficiency and three staff produce three different answers.
Connecting the records removes the reconciliation work rather than automating it. When the meter reading attaches to the customer account, and the account attaches to the physical connection, and the connection sits on the network, a reading entered in the field updates the bill, the consumption figure, and the map at the same time.
Eight record types account for almost everything a water or sanitation provider needs to hold. Each entry below names the record and what it carries.
A provider does not need all eight on the first day. It does need to decide early which records are authoritative, because a record that two systems both claim to own becomes a record neither system maintains.
The connections between records are what turn a set of lists into a system. Three of them carry most of the value.
Each connection also creates a check. A connection with no account is either a new customer or lost revenue. An account with no reading this month is either inactive or a missed route. The system does not have to find these for a manager to act on them, but it has to make them visible.
The same model carries a small scheme and a city utility. What changes is how much of it is switched on.
The order matters more than the scale. Providers that start with the customer register and the connection record can add accounting later. Providers that start with accounting alone tend to discover that the ledger describes customers nobody can locate.
The record types translate directly to sanitation, with the service chain in place of the distribution network. Containment assets replace connections, emptying and transport jobs replace meter reading rounds, and treatment sites replace sources.
The part that usually needs deciding first is what counts as the asset. A pit latrine, a septic tank, and a connection to a sewer are all containment, and a provider that records them consistently can report on a whole service area rather than on the customers it happens to serve. mWater publishes the Sanitation Asset Standard as a public good so that providers, regulators, and partners can record containment the same way and combine the results.
It is not a billing package. Billing is one output of the system, and a provider that buys billing alone still has no asset register, no fault history, and no way to find the connections that are missing from the ledger.
It is not a geographic information system. Mapping matters, and a map of assets is part of the system, but a map without a customer register cannot tell a manager which failure costs the most revenue.
It is not a spreadsheet with more columns. Spreadsheets hold data well and connect it badly. The moment two people need to update the same record from different places, the spreadsheet stops being the record and becomes a copy of it.
Finally, it does not fix a provider on its own. The system makes the gaps visible. Closing them is management work, and the World Bank sets out how that work is sequenced in its Water Utility Turnaround Framework, which treats commercial and technical operations as two of five areas a utility has to improve together.
mWater provides all eight record types on one platform, free to use, with unlimited users and no license fee. Providers can set up a water system, import an existing customer list, configure tariffs, record meter readings offline in the field, generate bills, and see arrears and collection rate on a customer overview page.
This guide defines the category. The rest of the series covers choosing a system, designing the records, recovering lost revenue, and the first month of operation.
A water utility management information system is the linked record of a provider's customers, infrastructure, work, and money, maintained by the people who operate the service. Its value is not the volume of data it stores. It is whether a manager can start from any one record and reach every other record that depends on it, and act before the next billing cycle closes.
mWater · Water service provider series