Smart utility metering for water, gas and power
Meters report themselves, charges land on the maintenance bill as readings rather than estimates, and abnormal usage raises an alert before it becomes a dispute or a flooded basement.
Smart utility metering reads water, gas and energy meters automatically and bills each flat for actual consumption on the maintenance invoice. Abnormal usage and suspected leaks raise alerts, and a prepaid mode lets residents recharge in advance instead of being billed in arrears.
Bill for what is used, not what is guessed
Most societies divide the water bill equally per flat, because reading four hundred meters by hand every month is not a job anyone will do reliably. The consequence is that a two-person household subsidises an eight-person one, and the households that know this raise it at every AGM.
Where manual reading is attempted, it introduces its own problems. Readings are taken over several days and treated as if simultaneous, transcription errors produce bills that are obviously wrong, and a meter that has stopped is usually discovered months later when somebody notices a flat consuming nothing.
Automatic reading removes both the labour and the argument. Every meter reports on the same schedule, the charge on the bill is a reading with a date rather than a share of a total, and a member who disputes it can be shown their own consumption graph. The disputes do not become easier to win; they stop happening.
- Equal division is a cross-subsidy. And the households paying it are the ones who raise it at every general body meeting.
- Manual reading does not scale. Four hundred meters read by hand is several days of work and a stack of transcription errors.
- Failed meters hide for months. Nobody notices a stopped meter when the bill is a flat share.
Which meters connect, and how readings arrive
Smart water, gas and energy meters
KeyMatrix works with the smart meter families commonly deployed in Indian residential projects rather than supplying hardware. Meters report over the network the installation uses — typically LoRaWAN or NB-IoT for water and gas, and RS-485 or a similar bus for energy — into a gateway that forwards readings.
Which meter and which network is a decision for whoever warrants the installation. What we specify is that readings arrive with a meter identity, a timestamp and a value, and that the meter can be mapped to a flat.
Automatic meter reading
Readings arrive on a schedule — commonly daily, sometimes hourly for energy — without anyone visiting a meter. The billing reading is taken at the same moment across every flat, which is what makes the resulting charges comparable.
Missed readings are visible as missed readings rather than as a flat that consumed nothing. A meter that stops reporting raises a maintenance flag, so a failed device is a work order within days instead of a billing anomaly discovered at year end.
Consumption-based billing on the maintenance invoice
Consumption is converted to a charge on the maintenance bill using the tariff the general body approved — flat rate per unit, or slab-based where the society wants to price heavy use differently. Common-area consumption is apportioned separately rather than being buried in the per-flat rate.
The bill shows opening reading, closing reading, consumption and rate. That transparency is what makes consumption billing survive its first AGM: a member can check the arithmetic themselves.
Because metering is wired straight into billing rather than exported to it, the consumption charge is simply another head on the invoice. It posts to the ledger like any other head and appears on the member’s statement with its readings attached.
Where metering pays for itself: leaks and unaccounted-for water
The payback case rests mostly on leak detection, not on behaviour change.
Leak and abnormal usage alerts
Continuous non-zero flow overnight is the classic signature of a leaking tank or a running toilet, and it is invisible under monthly manual reading. An alert on that pattern reaches the resident and the maintenance team within a day, and raises a work order against the meter or the plumbing so the response is a scheduled repair rather than an argument about a bill.
A single leaking overhead tank can waste more water in a month than the metering saves in a year of behaviour change, and the only way to catch it early is to be watching the pattern rather than the monthly total.
Consumption analytics per flat
Residents see their own consumption over time and against the anonymised distribution for comparable flats. That comparison is what changes behaviour: a household that learns it uses twice the median for its size usually investigates before the committee has to raise it.
For the committee, the aggregate view shows total supply against the sum of flat consumption, which is how unaccounted-for water — leaks in the common line, unmetered draw — becomes a number rather than a suspicion.
Prepaid recharge, and the cut-off question
Where a society opts for it, residents recharge a utility balance in advance and consumption draws it down, with low-balance warnings before it runs out. This is common in student housing, co-living and PG operations, and increasingly in rented stock.
Prepaid needs to be set up carefully. Cut-off policy is a general body decision, not a software default, and any deployment should carry a grace balance and clear warnings — the failure mode is a household losing water supply at 11pm over a small balance, which no committee wants to defend.