Can your existing meters be retrofitted?

Remote meter reading is often framed as a technology choice. Should the project use NB-IoT, LoRaWAN, or another network? Should the meters be replaced? Should the data go into a platform, an API, or an existing backend system? Which device can read which protocol? These are important questions. But in retrofit projects, they are not the first questions.

For utilities, building administrators, facility managers and system integrators, the first step is usually more practical: what is already installed, and can it be connected? In many buildings, technical rooms, utility networks and industrial sites, existing meters still work reliably. They measure water, heat, gas, electricity or other values. Some have M-Bus. Some use wireless M-Bus. Some provide pulse outputs. Some communicate through Modbus or other interfaces. Others are part of mixed environments with several meter types and manufacturers in use at the same time.

In these cases, full replacement may not be the only option, and it may not be the best first step. Before a suitable solution can be selected, the existing infrastructure needs to be assessed, and retrofitting existing meters into modern communication networks and data systems is often more practical.

Why retrofit-readiness matters

A remote reading project can fail before the first device is installed if the existing metering infrastructure is not understood properly.

The meter may have an interface, but the required data may not be available through it. The meter may support remote reading, but the installation environment may block radio communication. The requested reading interval may be technically possible, but unrealistic for long battery life. The customer may expect platform integration, but the data format or backend requirements may not be defined.

These are not unusual edge cases. They are common project questions, and they are also why retrofitting has become a distinct discipline rather than a shortcut. Many retrofit projects are also driven by regulatory requirements such as the Energy Efficiency Directive (EED), which pushes utilities toward more frequent and remotely accessible meter reading.

Retrofit-readiness means knowing whether existing meters can be connected, what connectivity is suitable, and what conditions must be considered before deployment. For larger organisations, this is not only a technical detail. It affects cost, rollout planning, installation time, device selection, data quality, long-term maintenance and the overall business case.

What meters are already installed?

The first step is to identify the existing metering infrastructure. This is the foundation for both Automated Meter Reading (AMR) projects, where consumption data is collected remotely without full Advanced Metering Infrastructure (AMI) capability, and fuller AMI rollouts with two-way communication and management. For a utility, this may mean a specific group of meters in a network. For a building administrator, it may mean a portfolio of apartment buildings or commercial properties. For a system integrator, it may mean a customer site with mixed devices from several manufacturers.

The basic information should include:

• utility type: water, heat, gas, electricity, or other
• meter manufacturer and model
• meter generation or year of installation, if known
• number of meters
• installation location
• available documentation
• meter accessibility
• expected remaining lifetime of the meter

‍

A remote reading solution cannot be selected properly without knowing what it needs to connect to. If the meter type and interface are unknown, the project starts with uncertainty. If the installed base is mixed, the solution may need to support more than one interface, protocol, or configuration. For larger deployments, it is worth building a meter inventory before choosing the connectivity architecture.

Which interface does the meter provide?

The next question is whether the meter has a usable output or communication interface. Common interfaces in retrofit metering projects include M-Bus, wireless M-Bus, pulse output including S0, Modbus/RS-485, optical interface, serial interface, and manufacturer-specific communication.

Each interface leads to a different type of solution. An M-Bus meter may need an M-Bus converter or gateway. A wireless M-Bus meter may need a concentrator that can receive radio telegrams. A pulse meter may need a pulse-input converter. A Modbus device may require protocol-specific configuration and data parsing.

It is also important to check whether the interface is physically available and usable in the installation. A meter may technically support M-Bus, but the terminals may not be wired. A pulse output may exist, but the pulse constant must be known. A wireless M-Bus meter may transmit data, but the telegram may be encrypted. A Modbus device may be readable, but the relevant register map must be available.

In retrofit projects, having an interface is only the beginning. The real question is whether it provides the needed data in a form that can actually be used.

What data is actually needed?

Not every remote reading project needs the same data. Some projects only need cumulative consumption once per day. Others need hourly or 15-minute interval readings. Some need alarms, status information, pressure, temperature, timestamps, diagnostic values, or historical data.

Examples of required data may include total consumption, interval consumption, meter status, alarms, tamper information, battery status, signal quality, pressure, temperature, flow, timestamped readings, and diagnostic values.

This matters because different meters and interfaces expose different data. A pulse output may be sufficient for consumption counting, but not for detailed diagnostics. M-Bus may provide richer data, but the exact values depend on the meter and telegram structure. Wireless M-Bus may suit frequent collection in buildings, but encryption and reception conditions need to be handled. A retrofit solution should be selected based on the required data, not just the meter type. The next step is to match the data requirement with the available meter output.

How often should the data be read?

Reading frequency directly affects the technical design and, depending on whether readings are taken daily, hourly, or every 15 minutes, it also affects power consumption, communication volume, data storage, and integration complexity. The right frequency should follow the business and operational need rather than a default setting. A closer look at the trade-offs between reading intervals and how they affect battery life and reporting is available in 15-minute vs daily meter readings frequency explained.

Where are the meters installed?

The installation environment can decide whether a retrofit project is straightforward or technically demanding. Meters may sit in basements, technical rooms, shafts, meter cabinets, apartment buildings, industrial halls, outdoor boxes, underground spaces, metal enclosures, remote sites, ATEX zones or locations with limited access, and each of these creates different requirements for radio coverage, antenna placement, IP rating or certification. Installation photos and site information are valuable during project preparation, and for larger rollouts the environment should not be treated as a minor detail. Why proper antenna tuning specifically makes or breaks reception in these environments is covered in Why a device without an antenna fails.

Is power available?

Power supply is one of the most practical questions in retrofit smart metering. Some installations can use external power. Others require battery-powered devices, since mains power is often unavailable near the meter or would add installation complexity. The project should clarify whether external power is available, whether battery operation is required, expected battery lifetime, reading and transmission frequency, environmental conditions, access for battery replacement and service interval expectations.

Battery lifetime is not a fixed number independent of the project. It depends on the communication technology, reading interval, transmission interval, signal quality, payload size, temperature and device behaviour. For building administrators and utilities, this has operational consequences. A technically working solution may still be unsuitable if it requires frequent maintenance across many sites.

Which communication network fits the project?

Once the meter interface, data requirements and installation environment are understood, the communication network can be selected. Common options include NB-IoT, LoRaWAN, LTE-M or other project-specific paths, and the right choice depends on coverage, network ownership, data volume, power consumption, indoor or underground penetration, roaming or operator availability, customer IT requirements and the long-term operating model.

There is no universal answer, and the network should be chosen according to field conditions and target operating model rather than preference alone. A practical comparison of these options for utility deployments is available in Choosing a remote reading system for water utilities.

Where should the data go?

Remote reading is not complete when the data leaves the meter. Before integration begins, the project must define where the data should be delivered and in what form. Possible destinations include a utility backend, billing system, customer platform, energy management system, building management system, cloud dashboard, API endpoint, CSV or scheduled export, data lake, integration middleware or partner platform.

A simple dashboard may be enough for a pilot or small deployment. A larger utility or building portfolio may require API integration, structured data formats, authentication, device management and operational monitoring. It is also important to define who is responsible for the data after transmission, since the device supplier, system integrator, platform provider and customer may each own different parts of the data path. A good retrofit project defines the destination and integration requirements early.

Who controls configuration and security?

Security and configuration should be part of the project design, not an afterthought. Retrofit devices may need secure communication, device authentication, encryption, key management, remote firmware updates, downlinks, access control and configuration logs, particularly since metering data can support billing, operational monitoring, reporting and customer-facing services.

Who owns the encryption keys, and what that means for long-term control if the customer later changes platform, is explored in Not your keys, not your hardware.

What information should be prepared before asking for a solution?

The quality of the initial information has a direct impact on the quality of the proposed solution. Before contacting a supplier or integrator, utilities and building administrators should prepare as much of the following as possible:

• meter manufacturer and model
• number of meters
• utility type
• meter interface, if known
• photos of the meter and terminals
• installation location and indoor/outdoor conditions
• availability of external power
• required reading frequency and data values
• expected battery lifetime
• communication network preference, if any
• platform or backend destination
• security requirements
• rollout size and timeline
• access limitations
• existing documentation or meter passports

‍

Not every project will have all this information at the beginning. But even partial information helps narrow down the right connectivity path, and for larger deployments this list can also serve as the basis for a site survey or pilot preparation.

When retrofit is not the right answer, and where ACRIOS fits

Retrofit connectivity is not suitable for every project. A full meter replacement may be the better route when existing meters are end-of-life, do not provide usable outputs, cannot deliver the required data, are physically inaccessible, or when the customer wants one vendor for a complete, certified meter fleet. Retrofitting is a practical option when existing meters are still valuable and can provide the data needed, not a universal replacement for smart meter rollout.

ACRIOS focuses on this narrower role: connecting existing working meters and mixed metering infrastructure to modern communication networks and data systems, rather than delivering complete meter fleets and end-to-end national rollouts. A fuller look at when a focused converter supplier fits better than a large vendor, and when it does not, is available in Focused supplier or large vendor? Depends on the project.

Before replacing meters, understand what can be connected

Remote meter reading does not always start with new meters. For many utilities, building administrators and system integrators, the starting point is existing infrastructure that already works. The challenge is to connect it reliably, securely and in a way that delivers usable data.

Before selecting a converter, gateway, network or platform, the project should answer practical questions: what meters are installed, which interfaces are available, what data is needed, how often it should be read, where the devices sit and where the data should go. The better the input, the faster the right connectivity path can be defined.

The findings in this checklist are general guidance based on common retrofit scenarios. Every site has its own combination of meters, environment and requirements, so a project-specific assessment is recommended before committing to a particular converter, network or rollout plan.

For organisations planning remote reading across existing infrastructure, the question is often not what to replace, but what can be connected, and what needs to be known before connecting it.