A Sensor Trend Is Not a Verdict: What Wastewater Analytics Can and Cannot Tell a Small Town

Somewhere under a Midwest street, a small sensor sits in a manhole or inside a lift station and keeps a running record of what moves through the pipe. Flow, depth, and sometimes other readings build up month after month. Software companies now offer to read those records and flag anything unusual, with the promise that a town hears about a problem before a basement does.

Water Finance and Management's report on the StormHarvester board appointment describes a wastewater analytics company that has added Colby Manwaring, an international water technology executive and former CEO of Innovyze, as a board advisor. The company framed the move as part of plans to "accelerate its growth" in the United States and abroad. That is corporate news. It tells a reader about the company's direction and its people. It does not tell a town whether any monitoring tool will catch a real break, and a city council should keep those two questions apart.

What an alert is measuring

A monitoring platform does not see a broken pipe. It sees numbers. A meter records how much water is moving and how fast, and the software compares that record against a baseline it has learned. An alert means the new reading departed from that baseline. Whether the departure means a leak, an illegal connection, a stuck float, or a rainy week depends on how the baseline was built. A few months of data from a dry season can make a wet spring look like a crisis. A meter placed in the wrong spot can report flows that do not represent the neighborhood at all.

Rainfall is the most common source of confusion. Storm water can enter older sewers through cracked joints and open lids, raising flows in ways that look like a fault in one section and a normal event in another. A good system separates those cases, but only if it receives accurate rainfall records and reflects the local pattern. Ask the vendor how the tool handles wet weather before the first alert arrives, not after.

Questions to answer before the contract is signed

Start with the record. How many months of data exist for your system, and does the baseline cover a full year? Who installs the meters, who calibrates them, and who replaces them when they drift? Who receives an alert, at what hour, and who decides whether a crew goes out? A flag that lands in an inbox nobody checks is not monitoring.

Then look at the paperwork. Who owns the raw readings if the town ends the contract? Can the town export its history in a format a future engineer can read? What happens to support if the company changes leadership or ownership? A board appointment like the one in the trade report is a sign of corporate direction, and direction can change. The contract should protect the town's records regardless.

Turning a flag into a fact

An alert is the start of a work order, not the end of a question. A sound process sends a crew to the flagged section, records what they find, and feeds that outcome back into the software so future alerts can be judged against real results. Over time, that log tells the council whether the tool is worth its cost. Ask for the figures: how many alerts led to a confirmed problem, how many turned out to be weather or equipment, and how long a crew took to respond. If the vendor or staff cannot produce those numbers, the tool is still an experiment.

Councils should also ask what the system does not cover. Analytics can point toward a stretch of line. They do not replace a camera inspection, a smoke test, or a manhole check by someone who knows the street. They also do not pay for the repair the data reveals. A chart can show a pattern that has been forming for years, but someone still has to fund the fix.

The short version

A wastewater trend is a reason to look, not a verdict on the pipe. Read trade news for what it is, a picture of a company and its plans. Read monitoring data for what it is, a set of readings that need context. Keep the decision in public view, where the people who pay for the system can see what the flags were, what crews found, and what changed as a result.

Related coverage: St. Charles Water Ratings.