Midwest Water News

Covering the water that covers the Midwest

Infrastructure

The Alarm Rings Somewhere Else: Who Answers a Remote Monitoring Alert at a Small Midwest Water System

A tank level or pump trip can now reach a phone far from the plant, so the question worth asking is who is supposed to act on it and how that route is written down.

By Staff ·

Midwest Water News

A water tower can report its condition without anyone climbing the ladder. A level sensor reports how full it is, a pressure transmitter at a booster station reports whether the line is holding, and a control panel at a well house reports whether the pump is running or has tripped. In many systems those readings no longer stay on a gauge at the site. They travel to a screen somewhere else, often one run by a vendor. Remote monitoring is common enough now that it deserves a plain question at the next council or board meeting: when a reading crosses a line at 2 a.m., who is supposed to act on it?

Trade news this week shows how much of this equipment and software is changing hands. Water Finance and Management reported that Badger Meter acquired Melbourne-based 37South, which the report describes as a "utility technology and remote monitoring company." The announcement was made on Nov. 3, and the report places the deal in a recent string of acquisitions by Badger Meter. The summary does not describe what any Midwest utility would need to change, and that gap is useful. A purchase changes the company behind a product. It does not, by itself, change who answers the phone when a tank drops.

Three Places an Alarm Can Land

Most small systems route alarms in one of three ways, and many use more than one at the same time. The first is a person on call, whether a certified operator, a contract operator, or a city employee with a personal phone. This route is only as good as the schedule behind it. The second is the vendor's monitoring desk, which may watch the feed around the clock. A desk like that can see the reading, but it may not have authority to send a crew, change a setpoint, or decide that a low reading is a sensor fault rather than a real loss of water. The third is a shared inbox, which receives the message and waits for someone to read it, sometimes on Monday.

Each route fails differently. A personal phone fails when the operator is asleep, traveling, or has changed numbers. A vendor desk fails when the call list is out of date or when the desk is waiting for the utility to say what counts as an emergency. An inbox fails quietly, because nothing about an unread message looks like a problem until water is missing from the tank.

Write the Route Down

A utility does not need special software to answer the basic questions. It needs a written page that names the first contact, a backup, the hours each one covers, and the threshold that turns a reading into a phone call. The page should also say who can silence an alarm, who can restart a pump, and whether anyone outside the utility is allowed to reset equipment from a distance. A remote restart is a decision that should be authorized on paper before it happens, not discovered after a storm.

Board members can ask for three things at a regular meeting: the current call list with dates, a copy of the vendor agreement section that describes response times, and a short statement of which alarms go to people and which go only to a dashboard. None of these requests requires technical training. They require that the answers be written where a future board can find them.

What a Vendor Change Should Trigger

When a monitoring company is bought, the practical questions are ordinary ones. Does the support phone number change? Do alarm thresholds carry over exactly, or were some set by a technician who has since left? Who holds the administrator login, and is there a way to export the historical readings if the contract ends? The announcement does not answer any of these for a particular town, so a utility should not assume the answers are unchanged or changed. It should ask the vendor in writing and file the reply with the contract.

The Same Logic at a Home Well

Rural households with a well, a pressure tank, and a pump face a smaller version of the same problem. A pump that fails at night can leave a house without water before anyone notices. A homeowner can write down who gets a text, who is the backup, and which readings matter, and can check whether the alarm options they already have cover the pump at all. Readers who are sorting out that coverage can look at coverage for home systems and appliances as one place to compare the paperwork before they buy anything.

Read the Headline for What It Says

The Badger Meter announcement is a business story about a company, and it should be read that way. It does not say that rates will rise, that service will change, or that any town's data will be handled differently. Those would be separate questions, and they belong with the utility, not the trade press. The useful lesson for a Midwest reader is simpler: before a sensor reaches a screen, someone should be able to say who receives its message, who acts on it, and what happens when they do not answer. If that answer is not written down, the first step is to ask for it at the next public meeting.