AMI Procurement

Utility Procurement for AMI: How to Avoid Costly Mistakes

Why AMI procurement is more than buying meters—and how decisions made before deployment can shape cost, flexibility, integration, cybersecurity and long-term operations.

By Vincent Wong Yew Hon · 9 July 2026

Introduction

For many utilities, procurement is the first major step in an Advanced Metering Infrastructure (AMI) initiative.

It establishes the foundation for technology selection, project delivery, operational performance, and long-term scalability.

Yet many AMI challenges begin long before the first meter is installed.

They begin during procurement.

Procurement is often viewed as an administrative process focused on technical specifications, vendor evaluation, and commercial negotiations.

In reality, procurement decisions can influence a utility's operational flexibility, cybersecurity posture, integration capabilities, and total cost of ownership for the next 10–15 years.

Small mistakes made during procurement can become expensive problems later.

This is why successful AMI programs treat procurement as a strategic activity rather than simply a purchasing exercise.

Key Takeaways

AMI procurement is the procurement of an ecosystem, not simply meters.
Lowest upfront cost does not necessarily mean lowest lifecycle cost.
Business objectives should be established before technology requirements are defined.
Total Cost of Ownership should include communications, software, integration, support, cybersecurity and upgrades.
Integration requirements need to be addressed before contracts are finalized.
Interoperability and reasonable flexibility can reduce long-term vendor dependency.
Cybersecurity requirements should be incorporated from the beginning.
Service levels and vendor support responsibilities need clear contractual definition.
Vendor stability and long-term support capability matter for infrastructure with a 10–15 year lifecycle.
Procurement decisions should consider the complete operational lifecycle, not only deployment.

Why Procurement Matters More Than Many Utilities Realize

Smart metering projects are fundamentally different from purchasing standalone equipment.

An AMI deployment involves:

meters
communication networks
software platforms
data management systems
enterprise integrations
cybersecurity controls
long-term operational support

The procurement process determines how these components will work together throughout the system lifecycle.

A well-structured procurement process reduces risk and improves long-term flexibility.

A weak procurement process can create operational constraints that remain long after deployment is complete.

In many cases, procurement decisions influence project outcomes more than the technology itself.

Procurement Is About More Than Buying Meters

One of the most common misconceptions is that AMI procurement is primarily about selecting meters.

Meters are important.

However, utilities are actually procuring an ecosystem.

Questions that matter include:

How will data be managed?
How will systems integrate?
How will firmware be maintained?
How will cybersecurity be managed?
How will the solution evolve over time?
What happens if business requirements change?

Focusing exclusively on meter specifications can lead to important lifecycle considerations being overlooked.

Common Procurement Mistake #1: Focusing on Lowest Initial Cost

Cost is always important.

However, selecting a solution primarily because it offers the lowest upfront price can create challenges later.

A lower purchase price may be offset by:

higher integration costs
increased maintenance effort
limited scalability
higher communication costs
software licensing expenses
reduced operational flexibility

The cheapest proposal is not always the most economical solution over the life of the system.

Utilities should evaluate long-term value rather than only initial expenditure.

Common Procurement Mistake #2: Defining Technology Before Business Objectives

Procurement documents often begin with technical requirements.

While technical specifications are necessary, they should support clearly defined business objectives.

A utility should first ask:

What problems are we trying to solve?
What operational outcomes are expected?
What business value should the system deliver?

Examples may include:

reducing non-revenue water
improving billing accuracy
reducing manual meter reading costs
enhancing customer engagement
improving outage visibility

Once objectives are established, technology can be evaluated against those goals.

When procurement focuses on technology first, solutions may become disconnected from operational priorities.

Common Procurement Mistake #3: Ignoring Total Cost of Ownership

One of the most important procurement concepts is Total Cost of Ownership (TCO).

Unfortunately, it is also one of the most frequently underestimated.

The cost of an AMI system extends far beyond meter procurement.

TCO may include:

hardware
communication services
software licenses
implementation services
system integration
training
cybersecurity measures
maintenance and support
upgrades and enhancements

Over a 10–15 year lifecycle, operational costs can exceed initial procurement costs.

Utilities that focus only on capital expenditure may overlook significant long-term financial commitments.

Common Procurement Mistake #4: Underestimating Integration Requirements

AMI systems rarely operate in isolation.

Most utilities require integration with:

billing systems
GIS platforms
ERP systems
customer portals
analytics environments
outage management systems

Integration often proves more complex than anticipated.

Questions that should be addressed early include:

Are APIs available?
Are industry standards supported?
What integration tools are required?
Who owns integration responsibilities?

Failure to address integration requirements during procurement can create delays and unexpected costs during implementation.

Common Procurement Mistake #5: Creating Vendor Lock-In

Utilities typically expect AMI systems to remain operational for more than a decade.

Over that period, technologies evolve, vendors change, and business requirements develop.

Vendor lock-in occurs when future flexibility becomes limited because systems rely heavily on proprietary technologies or interfaces.

Potential risks include:

limited interoperability
reduced competitive options
higher upgrade costs
dependency on a single supplier

While no solution is entirely vendor-independent, procurement should seek reasonable flexibility wherever possible.

Open standards and well-documented interfaces can reduce future constraints.

Common Procurement Mistake #6: Treating Cybersecurity as a Later Phase

Cybersecurity is sometimes addressed only after technology selection has been completed.

This approach introduces unnecessary risk.

Cybersecurity requirements should be incorporated into procurement from the beginning.

Areas to consider include:

authentication mechanisms
encryption capabilities
firmware security
access control management
security monitoring
vulnerability management processes

Security features are often much easier to implement when included in procurement requirements than when added later.

Common Procurement Mistake #7: Weak Service Level Agreements

Technical specifications receive significant attention during procurement.

Operational support requirements sometimes receive less scrutiny.

However, long-term success often depends on support quality.

Important considerations include:

response times
resolution targets
escalation procedures
software support commitments
firmware maintenance responsibilities
performance reporting

A technically capable solution can still create operational challenges if support expectations are unclear.

Common Procurement Mistake #8: Failing to Evaluate Vendor Stability

AMI systems often remain in operation for many years.

A vendor's ability to support the solution throughout its lifecycle is therefore important.

Utilities should assess factors such as:

financial stability
market presence
deployment experience
product roadmap
local support capabilities

This is not about selecting the largest vendor.

It is about understanding whether the vendor can realistically support long-term operational requirements.

Questions Utilities Should Ask During Procurement

Strong procurement processes focus on asking the right questions.

Examples include:

How does the solution support future scalability?
What interoperability standards are supported?
How are firmware updates managed?
What cybersecurity controls are included?
How is data ownership handled?
What integration capabilities exist?
How will the system evolve over the next decade?
What operational support is provided?

The quality of these discussions often reveals more than technical datasheets.

Why Procurement Should Consider the Entire Lifecycle

Many procurement exercises focus primarily on deployment.

However, deployment is only the beginning.

Once systems become operational, utilities must manage:

firmware updates
battery performance
cybersecurity risks
technology evolution
communication network changes
software upgrades

Lifecycle considerations should influence procurement decisions from the outset.

A solution that appears attractive during deployment may create challenges later if lifecycle requirements are not adequately considered.

What Successful Utilities Do Differently

They Start With Business Outcomes

Technology requirements are derived from operational objectives rather than the other way around.

They Evaluate Total Cost of Ownership

Long-term financial impact receives as much attention as upfront costs.

They Prioritize Interoperability

Future flexibility is considered during technology selection.

They Include Operations Teams Early

Procurement decisions reflect operational realities rather than purely technical preferences.

They Plan Beyond Deployment

Support, maintenance, upgrades, and lifecycle management are considered before contracts are signed.

Field Notes from Real Deployments

Across many smart metering projects, some of the most expensive problems are not caused by technology failures.

They originate from procurement decisions that failed to consider long-term operational realities.

A communication solution selected primarily on cost may create coverage challenges.

A software platform chosen without integration planning may increase implementation effort.

A contract that lacks clear support obligations may create operational uncertainty.

These issues often become visible only after deployment begins.

By then, they are significantly more difficult and expensive to address.

The strongest procurement processes recognize that AMI is not a short-term technology purchase.

It is a long-term operational investment.

Conclusion

Procurement is one of the most influential phases of any AMI program.

The decisions made before deployment begins can affect operational performance, flexibility, cybersecurity, integration complexity, and lifecycle costs for years to come.

Successful utilities recognize that procurement is not simply about comparing products and prices.

It is about selecting technologies, partners, and commercial frameworks that support long-term business objectives.

A well-structured procurement process reduces risk, improves adaptability, and increases the likelihood of achieving expected outcomes.

In smart metering, some of the most important project decisions are made long before the first meter is installed.

Read the Full Article on Medium

This article was originally published on Medium, where the full discussion examines the procurement decisions that can shape AMI cost, flexibility, integration, cybersecurity and long-term operational performance.

Read the Full Article on Medium →

Publications