Water Quality Wire

Water and wastewater automation began as a way to keep equipment running. A contributed piece in Water Finance and Management, by Nan Johnson, opens with the same point: "Not long ago, automation was viewed primarily as a way to improve equipment operation." Pumps started and stopped automatically, tank levels were maintained, and treatment processes became more consistent. The article's title takes the next step, arguing that operational visibility has become just as important as equipment control. That is a reasonable reading of where many plants now direct their attention, though it raises a question the headline does not answer: who holds the record that visibility depends on?

The Record Is the Product

A screen shows the present. Visibility over time depends on a historian, the database or hosted service that logs tag values at set intervals, stores alarms and setpoint changes, and lets staff pull trends for a review. In an investigation, a permit question, a contractor dispute, or a board presentation, that record is often the evidence. It is also the component most likely to sit under someone else's account, configured by an integrator and billed through a subscription that may not appear on the utility's asset list.

The risk is rarely a sudden loss of data. It is quieter. A retention setting nobody reviewed, an export that drops alarm context, or a tag renamed during an upgrade can leave gaps that look normal until someone asks for a specific week. Operators who have worked a plant for years often know which trends matter, but that knowledge tends to live in their heads rather than in a document the next shift can use.

Four Questions Before the Next Renewal

Who holds export rights? Confirm the file format the platform produces, the time stamp convention, the units, and whether alarm states and operator acknowledgments come out with the trend values. A trend that exports without its alarm context is harder to read in a review, and an acknowledgment missing from the file can change the account of an event.

How long is the record kept? Retention is set by license terms, storage tiers, or contract language, and those settings are rarely read alongside the operating procedure. List the retention period for each data class, then compare it with the period over which your own records may be needed. The two periods are seldom the same, and the gap is easy to miss until an outside question arrives.

What happens when the vendor changes? A platform may be replaced, consolidated, or sold, and the terms of the original agreement decide whether history moves with the utility or stays behind. Ask for a written export plan before signing any renewal, and confirm that the plan has been tested on real tags rather than described in a brochure.

Who can edit the record? Tag renames, deleted points, and corrected values change what a future reader sees, even when the plant has not changed. Restrict edit rights to named roles, and log changes with the same care applied to operating commands.

Test the Export Before You Need It

A practical test takes an afternoon. Choose one pump station, pick a known event such as a level alarm and its operator acknowledgment, export the trend for that window, and open the file on a computer that is not signed into the vendor portal. If the time stamps, units, and alarm states can be read without help from the vendor, the record is usable. If the reading depends on the vendor's staff, the utility has learned the answer before a failure or dispute makes it urgent.

Equipment control still matters, and the article's framing does not argue otherwise. A pump that cannot be started remotely is a different problem from a trend that cannot be retrieved. Both belong in the asset register, each with a named owner, and both should be part of the same review when a platform is evaluated.

Where the Uncertainty Sits

A trade summary cannot tell a utility how any particular vendor handles export, retention, or transfer, and this article does not claim to know those terms for any product. Plant managers should read their own agreements, request written answers from vendors, and test those answers against a real event. Language about visibility is useful as a starting point for questions. It is not a description of what a given contract delivers.