Flow, metering and water loss

What is the difference between AMR and AMI water metering?

• AMR is one way. The meter reports out. Nothing is sent back to it.
• AMI is two way. Read intervals, thresholds and firmware can be changed remotely.
• Frequency is the real difference. Monthly totals cannot show a leak. Hourly or better can.
• Only AMI supports alarming. Continuous overnight flow is invisible in a single monthly figure.

The distinction that actually matters

The two terms are often used loosely, and the marketing distinction between them is less useful than the operational one. What matters is how often the data arrives and whether anything can be sent back to the device.

AMR was designed to solve a labour problem. Instead of sending someone to read a dial, the meter transmits its total, whether that is to a handheld unit walked past, a receiver in a passing vehicle, or a fixed collector. The reading is still essentially the same reading a person would have taken, just collected without the visit. Communication runs one way only.

AMI was designed to solve a data problem. A permanent two way network connects the meter, so it reports at short intervals, and the operator can also send instructions to it: change the reporting interval, set an alarm threshold, update firmware, request a reading on demand. The output is a time series rather than a periodic total.

Why interval frequency decides what you can detect

This is the point that determines whether a metering upgrade pays for itself, and it is worth stating plainly. A leak is only visible if the measurement interval is short enough to isolate it from genuine consumption.

Consider a continuously running overflow on a site that also has real daytime demand. In a monthly total it is a slightly larger number, indistinguishable from a busy month, and it will run until the bill arrives and someone questions it. In hourly interval data it is unmistakable, because consumption never returns to zero overnight. The flat overnight floor is the leak, and its height is the leak rate.

That single analysis, the minimum overnight flow, is the foundation of most water loss work, and it simply is not available from infrequent totalised reads. It is the clearest argument for interval data over more frequent billing reads.

What each is good for

AMR remains perfectly reasonable where the goal is accurate billing without site visits, particularly across many low consumption points where the cost of a richer system is hard to justify. It removes estimated bills and access problems, which is a real benefit.

AMI is what you need if the meter is expected to do anything beyond billing: detect leaks, support a water balance across a site, verify that a plant shutdown actually stopped consumption, or raise an alarm when flow appears where it should not. Anything involving an alarm requires the two way capability, because a threshold has to be set and a message has to get out.

There is a middle route worth knowing about. Many existing mechanical meters already have a pulse output, and a data logger fitted to that output produces interval data without replacing the meter at all.