On Nov. 3, Water Finance and Management reported that Badger Meter had acquired 37South, which the report describes as a Melbourne, Australia-based "utility technology and remote monitoring company." The notice places the deal in a recent string of acquisitions, with the earlier UDlive Limited purchase described as the most recent before it. A utility holding remote monitoring equipment will naturally ask about support contracts and service continuity. This piece asks a narrower question: what happens to the installed radio network, the data format, and the device credentials if the product line changes hands.
The source does not say how 37South's technology is built, licensed, or integrated with Badger Meter's existing products. Nothing below assumes otherwise. The points are general, and they apply to any remote monitoring purchase where ownership of hardware and ownership of the underlying system may diverge.
Ownership Is Layered
A remote monitoring installation usually has several layers: the meter register, the endpoint or transmitter, the radio protocol, the collector or gateway, the head-end software, and the export format used to move reads into billing or analytics. Each layer can have a different owner. An acquisition typically transfers the company, its catalog, and often its engineering staff. The protocol specification, the license terms on any patented radio method, and the cryptographic keys used to authenticate devices may not move in the same way, or may move under terms that the utility never reviewed.
That gap matters because a meter that transmits correctly today can become unreadable in a practical sense if the gateway can no longer be replaced, the firmware cannot be updated, or the decoding documentation stays with a former supplier.
Three Questions for the Procurement File
Before the next purchase or renewal, the procurement file should answer three questions in writing.
First, is the radio protocol published, licensed, or proprietary? If it is proprietary, the file should name who can grant a license if the owner changes, and what the contract says about that transfer.
Second, can the head-end export raw register reads and interval data in a documented format, on a schedule the utility controls? An export that exists only in a vendor dashboard is a report, not a record.
Third, who holds the keys for device authentication and firmware signing? The file should state what happens to a gateway or endpoint if the supplier stops issuing updates, and how long the contract commits to security patches.
Make Interoperability a Test
Contract language promising open data formats carries little weight until it is tested. A practical check has three parts. Export one month of reads and parse them with a neutral tool that the utility controls. Decode a sample of endpoints using only the documentation the vendor has supplied, without vendor software. Time a gateway swap inside a test zone, including reprovisioning and the first full day of reads afterward.
The mechanism behind this test is simple. If reads cannot be decoded without the vendor's tools, the utility's continuity depends on the vendor remaining in business and willing to support the product. An acquisition is a moment when that assumption is most likely to be revisited.
The Tradeoff
Proprietary stacks can offer tighter integration, mature battery management, and faster support. Published standards reduce lock-in, but they can lag on features, and a standard alone does not guarantee that a particular vendor's implementation is complete. Neither approach is automatically safer. The acquisition notice does not show a problem with any specific product, and the article cannot determine from the summary whether 37South's technology is proprietary. What the notice does establish is a reason to check, because the ownership question has changed.
What to Record Now
For each remote monitoring installation, the file should record the product family, the radio band and the protocol name as documented by the vendor, the license holder for that protocol, the export format and its version, the custodian of device keys, the firmware support window stated in the contract, and a named engineering contact at the supplier. Review the file whenever an acquisition is announced, not only at renewal. The point of the record is not to predict a vendor's future. It is to make sure the utility can still read its own meters if that future is different from the one the purchase assumed.