Badger Meter announced on Nov. 3 that it had acquired 37South, a Melbourne, Australia-based utility technology and remote monitoring company. The announcement is part of what the trade report describes as a "latest in a recent string of M&A activity" for Badger Meter. Water Finance and Management reported the acquisition, and the summary available for this piece does not describe terms, product plans, or customer effects. This article does not read that deal. It is a checklist for what any utility should record when the company behind its remote monitoring data changes hands, a situation that can arise with any vendor in this market.
Follow the Data Path, Not the Brochure
A remote monitoring system is a chain. An endpoint on the meter records consumption or pressure and transmits it over radio, cellular, or fixed network links to a collector or gateway. Head-end software receives those reads, checks them, and passes them to billing, leak alert, or customer portal systems. Each link can have a different owner. The hardware may come from one manufacturer, the firmware from another, the hosting from a cloud provider, and the alert rules from a software team in a different time zone.
When a company is acquired, the first question is which links change. Some acquisitions leave products untouched for years. Others consolidate onto a single platform, retire older endpoint models, or move hosting. None of these outcomes follows from an announcement alone. The utility's task is to know which link it depends on before anyone else has to explain it.
Contract Language That Matters After a Sale
Many utility software and service agreements contain a change-of-control clause, but many were drafted when the vendor's identity was not in question. Review four items: whether the contract survives a change of ownership with notice only or requires consent; whether the vendor must give advance notice before a product is discontinued or a data format changes; who holds the license to the firmware and head-end code, and whether escrow or a continuity commitment exists; and which party is responsible for security patches on endpoints and gateways that stay in the field for many years.
Patch responsibility deserves particular attention. A meter endpoint in service for a decade may outlast the engineering team that designed it. If an acquiring company adopts a new support policy, a utility can find that its installed devices are supported on paper but not in practice.
Export Rights Are a Records Question
Meter history is a legal and operational record. Billing disputes, leak claims, and regulatory reviews all draw on it. Confirm the format in which reads, timestamps, alarm events, and configuration changes can be exported, and test that export before it is needed. Ask whether the export includes raw interval data or only processed daily values, since the difference determines whether an analyst can reconstruct a usage pattern later. Record the retention period the vendor applies and whether it changes under new ownership.
Timestamps need careful handling. If a platform migration changes how time zones or daylight saving transitions are indexed, the historical series can show artifacts that look like consumption changes. Log migration dates in the utility's own records so that a later anomaly can be traced to a platform change rather than to the water system.
Interoperability Versus Lock-In
Integrated platforms reduce the work of connecting meters, billing, and alerts. They also concentrate dependence in one vendor. Documented interfaces make it easier to replace a head-end system or add a second data source, but they require the utility to maintain integration code and staff who understand it. An acquisition does not change this tradeoff, but it can change the price of the vendor relationship, and a utility that has never priced an exit will have little leverage at renewal.
Dealers and integrators sit between the manufacturer and the operator. Independent regional dealers such as Jones Air & Water often handle installation, replacement, and warranty claims, so they know which endpoint models remain stocked and which are being phased out. A utility should ask its dealer which platform versions it supports, what spare endpoints it keeps on hand, and how it expects a vendor change to affect service calls.
What to Write Down Now
Keep a one-page register of each remote monitoring component, listing its vendor, firmware version, hosting location, contract renewal date, and export format. Update the register when a vendor announces a deal, not when a problem appears. The register does not require knowledge of a transaction's terms. It requires only that the utility knows what it would need to replace, migrate, or verify if those terms turn out to matter.
Further reading: independent regional dealers such as Jones Air & Water.