The 5-Step TCO Checklist for Smart Metering Procurement

If you’re managing procurement for a water, gas, or electric utility, you’ve probably seen a smart metering RFP that looks simple on paper. Vendor A quotes a great per-unit price on meters. Vendor B comes in slightly higher but includes “free” software. Your team leans toward the lower upfront cost. I’ve been there—more times than I’d like to admit.

Over the past 6 years of tracking invoices and negotiating with metering vendors, I’ve built a simple 5-step checklist that helps us avoid the hidden costs that eat into budgets. It’s not rocket science, but it’s saved us roughly 15-20% on total project costs compared to our earlier naïve approach. Here’s the checklist we use whenever we evaluate a new metering solution—including our recent deep dive into Itron’s smart metering platform.

Step 1: Map Out the Data Infrastructure Costs

People think the meter cost is the biggest line item. For a project with 10,000 Itron smart water meters, the hardware might be $250-400 per unit. But that’s just the beginning. The real cost driver is often the data infrastructure—the head-end system, the communication network, and the software licenses needed to actually use the data.

What to check in the quote:

• Does the price include the head-end software or data collection platform?
• Is there a recurring annual license fee for the software? (surprise, surprise—this is often buried in the fine print)
• What about the communication modules? For Itron’s intelis water meter, for example, the communication module (like an RF module or cellular endpoint) can add another $50-150 per meter.

Checkpoint: I ask vendors to split their quote into hardware, software, and communication costs. If they can’t or won’t, that’s a red flag. In our Q2 2024 vendor switch evaluation, two out of four vendors couldn’t provide this breakdown—and their “all-in” prices turned out to be incomplete when we dug deeper.

Step 2: Ask About the Integration Quotient

This is the step most people skip, and it’s probably where we’ve made our biggest mistakes. A smart meter is useless if its data doesn’t flow into your existing billing, customer information, and analytics systems. I’ve seen utilities buy great meters—only to spend 6 months and an extra $50,000 on integration middleware.

What to check:

• Does the vendor offer pre-built APIs or integration modules for common utility systems (like Oracle, SAP, or custom CIS platforms)?
• What is the cost of professional services for integration setup? Is it hourly or fixed price?
• Are there any ongoing integration maintenance fees?

With Itron’s platform, they offer a suite of open APIs and pre-built connectors. But I’ve learned to ask specifically: “Is that integration included in the base quote, or is it an add-on?” Because the standard “Yes, we can integrate” often means “Yes, for an additional $X.”

Checkpoint: Get a written statement on what integration support is included. I add a line item in my procurement spreadsheet labeled “Integration contingency (15% of base quote)” until I have a firm fixed-price quote for this work.

Step 3: Calculate the Deployment Logistics (Don’t Forget the Truck Roll)

The cost of installing meters is often higher than the meters themselves—especially if you’re replacing existing meters in occupied homes or businesses. For a typical residential installation, the total cost can be $150-300 per meter when you factor in labor, truck rolls, customer communication, and potential rework.

What to check:

• Does the vendor offer installation support or training? If you’re using internal crews, what is the training cost and time? (note to self: we underestimated this by 40% in our 2023 pilot project)
• Are there any “obstruction fees” for difficult installations? Some vendors charge extra for installations that require special tools or extra time.
• What is the warranty coverage on installation? If a meter is damaged during installation, who bears the cost?

Checkpoint: I now require a sample installation audit: the vendor or our team installs 20-50 meters in diverse settings (basements, outdoor pits, high-rise buildings) and we track actual time and cost. This pilot data has been invaluable for budgeting the full rollout.

Step 4: Evaluate the Data Continuity and Analytics Tiers

This is the step I wish I’d known about 3 years ago. Smart meters generate a firehose of data—hourly or even sub-hourly reads from thousands of meters. But what do you actually need? And what tier of analytics are you paying for?

The assumption is that more data is always better. Actually, the cost of data storage, processing, and analytics scales with volume. If you’re just doing monthly billing, you might not need 15-minute interval data for every meter. I’ve seen utilities overpay for premium analytics tiers when a basic tier would have covered 90% of their needs.

What to check:

• What are the available data tiers? (e.g., daily reads vs. hourly vs. 15-minute intervals)
• Is there a cost ceiling for data storage? Some vendors charge extra beyond a certain number of reads or storage volume.
• What analytics features are included in the base platform vs. premium add-ons? For Itron’s analytics suite, I’ve found that the base tier covers leak detection and basic consumption patterns, but advanced forecasting or pressure monitoring costs extra.

Checkpoint: We now do a “data needs assessment” before selecting a tier. I map out exactly which reports and alerts we need for the first 12 months. Often, we start with the basic tier and only upgrade later if the data shows we need more. This approach saved us about $12,000 annually on our last smart metering project.

Step 5: Build in a Contingency for the “Unexpected” (And Yes, It Will Happen)

Every project has surprises. A construction delay means you need to reschedule 200 installations. A firmware update breaks your data integration. A new regulatory requirement means you need to report data differently. I budget 15-20% contingency on the total project cost for these unknowns. Some call it pessimistic. I call it realistic based on tracking 6 years of project overruns.

What to check:

• What is the vendor’s change order process? How much does a mid-project change cost?
• Are there any penalties or fees for project delays caused by the customer side? (Yes, some vendors charge this.)
• Does the vendor offer a fixed-price option for the initial rollout, or is it time-and-materials?

Checkpoint: I always ask the vendor for their “typical change order log” from similar-sized projects. They won’t share client names (understandably), but I’ve gotten honest ballpark estimates: “For a 10,000-meter project, expect 3-5 change orders averaging $5,000-15,000 each.” Now I budget for that.

Common Mistakes to Avoid

• Focusing only on meter unit price. This was true 10 years ago when meters were standalone devices. Today, the software and integration costs often exceed the hardware. Ignore the unit price war and look at TCO.
• Assuming all “smart” features are needed. Not every deployment needs real-time pressure monitoring. Pick the features that solve your specific problems, not the vendor’s most comprehensive package.
• Not accounting for training and change management. I budget at least 5% of the project cost for training field crews, customer service teams, and data analysts. A smart meter is only smart if people know how to use its data.
• Skipping the pilot. We tried to save time by skipping the pilot on a 5,000-meter project. It cost us more in rework than the pilot would have. Now, I insist on a pilot with realistic conditions—without exception.

A personal note: After comparing 8 vendors over 3 months using this checklist for our 2024 project, we chose a solution that wasn’t the cheapest upfront. But the TCO was 12% lower than the cheapest option when we factored in integration costs, data tiers, and contingencies. And we haven’t had a single budget overrun surprise. That’s the real goal.