How to Choose AMI Software for a Water Utility

Choosing AMI software for a water utility is about more than collecting readings. The software determines how quickly large volumes of consumption data become information that billing teams, utility managers and field crews can use every day. Meters and communication networks are essential parts of smart metering, but the software determines how readings are validated, stored, analyzed and connected with the utility’s existing systems. According to the US Environmental Protection Agency’s WaterSense program, utilities are moving to advanced metering infrastructure to collect water usage data more easily, support customer billing and manage water more effectively. EPA also publishes a dedicated guide to working with AMI data, written for facility managers but useful as an introduction to what the data supports.

For utilities comparing AMI software, the most important questions concern compatibility, data quality, integration, scalability, water loss analysis, network visibility, security and the ability to migrate existing infrastructure gradually.

Key Takeaways

• AMI software should be selected for the meter estate and data volumes the utility expects to manage in the future, not only for the first deployment phase.
• Support for multiple meter manufacturers and communication technologies can reduce dependence on one hardware ecosystem and make future procurement more flexible.
• Meter data quality is as important as data collection. Utilities should understand how the platform validates readings, identifies missing data and prepares consumption records for billing.
• Water loss analysis is stronger when district data, consumption patterns and abnormal flow can be reviewed directly in the platform rather than assembled manually.
• Network and device monitoring can help operations teams identify communication problems before missing readings begin to affect billing or reporting.
• Security, API access, data export, vendor support and migration options should be evaluated alongside dashboards and analytics before a long term software decision is made.

AMI Software Evaluation Overview

Criteria	What to verify	Why it matters
Architecture	Which HES and MDM functions are included and how they interact	Clarifies which parts of the meter data process the platform actually manages
Meter compatibility	Supported manufacturers, device types and the specific communication technologies named, not described in general terms	Allows existing and future meters to operate within the same environment
Data quality	Validation, missing data detection, timestamps, estimation rules and audit history	Helps ensure that readings used for billing and analysis are reliable
Integration	API access and compatibility with billing, ERP and other utility systems	Reduces manual data transfer and supports existing business processes
Water loss analysis	DMA monitoring, balancing reports and abnormal consumption analysis	Helps teams identify areas that require further investigation
Network monitoring	Device status, communication quality, outages and network performance	Helps operations teams locate communication issues earlier
Scalability	Supported meter count, reading frequency, storage and processing capacity	Prevents the software from becoming a limitation as the AMI estate expands
Security and support	Certifications, hosting infrastructure, testing, access controls, software updates and support arrangements	Provides evidence that operational data and the platform are managed responsibly

What is AMI software for water utilities?

AMI software is the central data management layer within advanced metering infrastructure. It receives meter data over communication networks and makes it available for operational use.

A head end system, commonly called HES, handles communication with meters and network infrastructure. Meter data management, commonly called MDM, receives and processes the resulting data for activities such as validation, billing, reporting and analysis.

These functions may be supplied separately or within the same platform. Neither architecture is automatically better for every utility. A combined environment can reduce integration and supplier coordination, while separate systems may suit utilities that already operate established enterprise platforms.

The Mainlink Smart Metering Platform combines MDM and HES functions within one cloud native environment. Additionally IoT sensors, such as leakage detection, temperature and humidity sensors and other can be added into the monitoring of the property.

What should a utility check before choosing AMI software?

1. Can the platform work with more than one meter vendor?

Hardware independence can be important when a utility has inherited several types of meters or expects future meter purchases to remain open to competitive procurement.

Ask vendors which meter manufacturers and communication technologies are already operating in production environments. Mainlink’s platform is hardware agnostic and supports multiple meter brands, communication technologies and device types.

2. How does the platform manage meter data quality?

Collecting readings is only the beginning. Utilities should understand what happens when readings are missing, delayed or inconsistent.

A useful demonstration should show how the system validates incoming data, checks timestamps, identifies missing communication and prepares consumption information for billing. It should also make clear whether estimated or corrected values can be distinguished from original meter readings.

This area deserves particular attention because poor data quality can affect billing even when the communication network appears to be performing well.

3. Can the software support water loss analysis?

AMI software can provide more frequent consumption data, helping utilities investigate abnormal use and potential losses. However, software alone does not eliminate non revenue water.

NRW includes real losses such as leakage, apparent losses such as measurement or billing inaccuracies, and authorized consumption that is not billed. The World Bank also emphasizes that NRW management is a wider operational and financial challenge for utilities.

For utilities that use district metered areas, useful AMI software should enable comparison of network input with downstream consumption and investigation of areas where the difference warrants attention. Mainlink’s platform includes a balancing report for this purpose, comparing master meter consumption against individual submeter consumption, or DMA and DMZ data, for non revenue water detection. This supports NRW management, but it remains one part of a broader water loss program.

4. Does the platform monitor network and device health?

A high read rate is useful, but it does not explain why communication deteriorates.

Look for visibility into devices that stop reporting, gateway performance, communication quality and network outages. These functions help teams identify where a problem is occurring before missing data becomes a billing issue.

The goal is not for software to automatically diagnose every technical fault. It is to give field teams enough information to narrow the investigation.

5. How does it connect with existing utility systems?

AMI software rarely operates alone. Billing platforms, ERP systems, customer applications and analytics tools may all require access to meter data.

Ask what can be accessed through an API, which data can be exported automatically and what happens if the utility changes software providers in the future.

Documented APIs and standard data exports can reduce the cost and complexity of integration and future migration.

6. Can existing AMR infrastructure be migrated gradually?

Many utilities cannot replace an entire meter estate at once. Existing AMR equipment and new AMI devices may therefore need to operate at the same time.

The practical objective is to avoid creating separate databases and reconciliation processes during a multiyear migration. A platform that already supports legacy meter types alongside new ones eliminates the primary technical reason to run two systems in parallel.

7. What evidence supports the vendor’s security claims?

Security evaluation should go beyond a statement that the platform is hosted in the cloud.

Utilities should review relevant certifications, access controls, hosting arrangements, data protection processes, software update procedures and security testing.

Mainlink has ISO 9001:2015 for quality management and ISO/IEC 27001:2022 for information security management.

How do AMI software approaches differ?

Some AMI platforms are closely connected to one manufacturer’s meters and communication network. This can simplify accountability and system compatibility when a utility plans to standardize on one ecosystem.

Other platforms focus primarily on bringing existing meters online quickly. This can suit utilities that need remote reading without immediately introducing more extensive analytics.

Vendor agnostic platforms are designed for environments where multiple meter types or communication technologies need to coexist. They can provide greater procurement flexibility, although utilities should still confirm the level of integration work required for each device and protocol.

The correct choice depends on the existing estate, procurement strategy, internal IT capabilities and long term metering plan.

Five warning signs during an AMI software demonstration

1. The vendor only demonstrates perfect sample data and cannot show how missing or inconsistent readings are handled.
2. Water loss analysis is limited to a static dashboard with no ability to review individual districts or time periods.
3. The vendor cannot identify meter manufacturers or communication technologies already running on the platform.
4. Security answers focus only on cloud hosting without supporting certifications, named hosting infrastructure or testing information.
5. Consumption data can only be downloaded manually, with no scheduled export and no clear route for system integration.

Where does Mainlink fit?

Mainlink is most relevant to water utilities that want flexibility across meter technologies or need to modernize infrastructure in stages.

Its platform combines MDM and HES functions, supports multiple meter vendors and communication technologies, validates incoming data, provides balancing reports, monitors device and network status and connects with external systems through API integrations.

A practical utility example is the Bernkastel-Kues deployment in Germany. Mainlink reports that 1,500 NB IoT ultrasonic meters have been installed, with approximately 4,000 planned by the end of 2026. The utility previously relied on wM-Bus meters mainly for annual billing. Mainlink reports that the newer system has supported more efficient billing, earlier leak identification in public buildings and faster responses to customer inquiries.

Frequently Asked Questions

What is the difference between HES and MDM software?

A head end system communicates with meters and the communication network. Meter data management receives, validates, stores and processes the readings for billing, reporting and analysis. Some AMI platforms combine both functions.

Does a utility have to replace every meter when moving from AMR to AMI?

Not necessarily. Some platforms allow existing meters to continue operating while newer AMI devices are introduced gradually. Compatibility should be confirmed for the utility’s specific meter estate.

How can AMI software help reduce non revenue water?

AMI software provides more frequent consumption data, supports district comparison and can identify abnormal or continuous flow patterns. These insights help utilities prioritize investigation, but NRW reduction also depends on meter accuracy, leak detection, repairs, pressure management and commercial loss control.

Can a single AMI platform support multiple meter manufacturers?

Yes, if the platform has been designed for multiple vendors. Utilities should ask which manufacturers are already integrated and whether additional development is required for new devices.

What determines the cost of AMI software?

Most vendors price by meter count, reading frequency and data retention period rather than by feature list, which means the same platform can carry very different costs depending on how the utility intends to use it.

What should a utility test before selecting AMI software?

Use real utility data where possible. Test meter compatibility, missing data handling, validation, billing export, API integration, user permissions, network monitoring and reporting. Also review support procedures and security documentation before making a long term commitment.

Next Step

The most useful way to compare AMI software is to begin with the utility’s existing meter inventory, communication infrastructure, billing systems and future deployment plan.

For Mainlink, this means testing how much of the current estate can connect to the platform, which equipment can remain in service and how new AMI devices can be added over time. A demonstration based on real infrastructure will reveal more about long term suitability than a standard feature list.