Itron Water Meter Selection: A Field Guide for People Who've Already Been Burned

There's no 'best' Itron water meter — only the right one for your situation

I started handling metering orders in 2017. Or rather, I was given the title in 2017; I didn't fully understand the metering ecosystem until 2018. By the end of that year, I had cost my utility about $9,000 — maybe $8,700, I'd have to check the old POs — in restock fees, wrong protocol modules, and one very awkward phone call to a contractor. Now I keep our team's pre-order checklist, and I'm writing down what I wish someone had told me before I bought 250 registers that didn't speak to our router.

Here's the thing: if you ask a manufacturer rep 'which Itron water meter should I use?' they'll usually say 'it depends.' That's not an evasion. It's true. The right choice depends on what you're replacing, how your network is built, and — if you're honest — how fast you need it.

Before I list scenarios, two caveats:

• My experience is based on mid-sized municipal utilities, mostly residential and small commercial endpoints. If you're running a rural district with 500 meters or a metro system with 400,000, your constraints are different.
• I don't have hard data on industry-wide first-installation failure rates. Based on six years of our own orders, my sense is that 8–12% of first deliveries have some issue — wrong endpoint, wrong register orientation, wrong sensor depth. That's an anecdote, not a statistic.

With that out of the way, here are the four scenarios I see most often.

Scenario 1: You're replacing an existing meter population, meter by meter

This is the most common situation, and the one where I made my biggest mistake.

In 2017, we were replacing old residential water meters with new smart endpoints. I found a deal on a batch of meters with a different communications module. The price was $2,800 less than the quote from our Itron distributor. 'Same spec, cheaper,' I told my boss. It wasn't. The modules didn't talk to our existing fixed-network collector. We had to send back 250 units, pay restocking, and still ended up buying the correct meters. Total wasted budget: roughly $3,100 plus a two-week delay.

What I'd do now:

• Before you buy any Itron water meter, confirm the endpoint protocol matches your collector. Don't assume 'Itron-compatible' means 'your-system-compatible.'
• Check the register orientation and reading format. A digital register that faces the wrong direction in a pit can be read with a handheld, but it's a pain forever.
• If you're going with the Itron Intelis water meter line, use the pre-order compatibility documentation. The Intelis is a good residential endpoint — remote-readable, compact, no separate pulse cable to lose — but only if your network supports it.

Reference: Itron Intelis installation documentation, available on itron.com. The compatibility section will tell you which endpoint modules fit which collectors. I ignored a similar reference once; my mistake wasn't the meter, it was not reading the manual.

One tool that saved us: a cheap depth micrometer. We now use one to verify pit depth and sensor insertion depth before ordering a new flow sensor. It sounds overly simple, but a mismatched pit depth changes which meter tailpiece you need.

Scenario 2: You're designing a new development or district metered area

New construction is the rare case where you can get everything right the first time.

I wish I'd tracked how much time we wasted fixing meter pits on old subdivisions. With new construction, the question is not 'what can we retrofit?' It's 'where should the flow sensor sit, and what data do we actually need?'

For a new DMA, my recommendation to my own team has been:

• Use a flow sensor on the inlet and key branches, not just at the master meter. You'll get better data on night flows and leak location.
• Spec the Itron Intelis water meter if you're deploying AMI. It gives you remote reads without a separate register box, and it sits well in a standard residential pit.
• Use a depth micrometer during installation to verify the minimum cover on meter boxes and the insertion depth of any insertion-style flow sensor. The sensor's manufacturer will give you a depth range; in September 2022, we skipped that step and installed a flow sensor 2 inches too shallow. It read fine for three weeks. Then a water-loss audit showed a 12% gap. The depth micrometer would have caught it in five minutes.

A note on price: 'New development' also means you have time to compare vendors. It's tempting to go with the first bid. But you're not buying a meter; you're buying a data system. Spend the extra time on protocol sheets, not just price per unit.

Scenario 3: You need a meter or flow sensor right now

This is where I stopped being clever and started being honest with my budget.

In March 2024, a fire-flow meter failed two weeks before a compliance audit. The 'budget' replacement was $320 cheaper, lead time 3 weeks. The rush option was $400 more, guaranteed 3 days. I almost chose the budget one because 'we can explain the delay.' Then I did the math: the audit penalty and re-testing would have cost $15,000. We paid the $400.

That $400 wasn't for speed. It was for certainty.

This applies beyond emergency orders:

• If a utility deadline is fixed — a rate case, a regulatory filing, a mandatory conservation report — paying extra for a confirmed ship date is often the rational move.
• If a vendor says 'probably next week,' treat 'probably' as 'late.' Not because they're dishonest, but because unpredictability is the real cost of a non-guaranteed promise.
• After getting burned twice by 'should be fine' lead times, we now add guaranteed delivery into the project budget from the start.

To be fair, the budget tier has a place: non-critical spares, slow projects, seasonal work. I'm not saying you should rush everything. I'm saying that when the deadline is real, the cheapest option is rarely the least expensive one.

Let me rephrase that: people think rush orders cost more because they're harder. Actually, they cost more because they're unpredictable and disrupt planned workflows.

Scenario 4: You have a mixed fleet and need to read a Sensus digital water meter

I know this article is about Itron. But people ask 'how to read a Sensus digital water meter' often enough that I'd rather cover it than pretend no one else is in that boat.

Some of our sister utilities run Sensus meters alongside Itron meters. I'm not going to tell you Sensus is bad — they're a solid metering company. We just don't stock them in our area. But if you end up with one on a route, the reading procedure is generally straightforward:

1. Locate the digital display on the meter body or register lid. Sensus digital meters usually cycle through screens automatically.
2. Wait for the screen that shows a row of digits. Write down all the digits from left to right.
3. If there's a red digit, or a decimal, that's a fraction — you can record it for leak checks, but for a standard billing read, only the main digits matter.
4. Look at the label next to the digits. It will say gallons, cubic feet, or cubic meters. Don't assume — that's the kind of detail that makes a 1,000-gallon read look like a 100,000-gallon error.
5. If the screen is blank, check the meter's internal battery, if it's user-accessible, or call the vendor. Some Sensus meters with AMI modules may not show anything on the screen until they're interrogated over the radio.

Why do I know this? Because in 2022, I had to explain to a summer intern why she was reading every Sensus meter in one subdivision backward. We sorted it out. The meter was fine. The process wasn't.

If you're in a mixed fleet, keep a cheat sheet with a screen photo. One photo in your phone is worth three pages of spec sheet.

How to tell which scenario you're in

If you're still unsure, here's my annoying but practical answer:

• Are you replacing meters one at a time? Scenario 1. Spend your time on compatibility before price.
• Are you starting from zero on a new site? Scenario 2. Spend your time on sensor placement and data architecture.
• Does the meter have to be working by a date on a calendar? Scenario 3. Budget for certainty.
• Do you just need to know what a number on a screen means? Scenario 4. Get a photo, take a breath, write it down right.

That last one is maybe the most common. I've been burned enough times to know that the simplest-sounding question — 'how do I read this meter?' — is exactly where expensive mistakes hide.