The Guardian reported that the US south-west faced more storms after the Four Corners region had endured "days of rain," with another round of heavy showers and thunderstorms expected in the forecast (The Guardian's report on renewed storms in the Four Corners region). The story is about weather and its immediate effects. For a utility, though, a prolonged wet period is also a stress test of the monitoring network, and that test often reveals more about the instruments than about the source water.
What the sensors actually measure
Most storm-period telemetry comes from a small set of instruments: turbidity at intakes and reservoirs, flow and level at pumping stations, chlorine residual and pH at treatment and distribution points, and sometimes conductivity. Each reading has a physical pathway between the water and the sensor. A turbidity probe responds to suspended solids in its optical path, so a sharp rise can reflect sediment arriving in the source, debris pressed against the housing, a film on the lens, or air trapped near the window. The reading is accurate in the narrow sense that the probe registered something. The cause is a separate question, and the data does not answer it on its own.
Where storm data goes wrong
Four failure patterns recur. The first is fouling. Cleaning intervals set for dry-weather conditions can fall behind when sediment and organic debris load the sensor faster than expected, and a drifting baseline can look like a real change in water quality. The second is power and communications loss. When telemetry drops, the historian may hold the last value, so a flat line during a storm can look like stable conditions when it is actually a missing record. Treat unexplained flatness as a warning sign. The third is coverage. A single station at one point in a system will miss a localized runoff plume that enters elsewhere, and a network that looks dense on a map may have only one station in the drainage that matters during a given event. The fourth is calibration drift. Probes exposed to temperature swings and sediment loads move away from their calibration, and the error is often largest exactly when operators most need the reading to be right.
Alarm thresholds add a fifth problem. Thresholds set against normal operating ranges either generate a stream of alerts during a storm, which trains operators to ignore them, or stay silent when an event is real because the value never crosses a line designed for other conditions. Neither outcome is a fault in the instrument. Both are a fault in how the alarm was specified.
Build a verification step before action
Pair continuous readings with grab samples taken at the same time-stamped moment, and treat each pair as a calibration check as well as a water quality record. Log cleaning, calibration, and maintenance dates alongside the data, so an operator can tell whether a spike coincides with a documented sensor history or with an undocumented gap. Record which sites lost communication and for how long. Where a reading is about to drive an operational step, such as adjusting treatment chemistry, changing a pumping schedule, or isolating a zone, confirm it with a second method first. A reading that cannot be confirmed should be labeled as unverified in the operating record, not silently accepted.
The sequence matters. Verification should come before the response, and the record of how the reading was checked should exist before anyone has to explain the decision later. Storm events compress the time available for both, which is why the verification steps belong in the procedure before the next wet period arrives.
What this means for buyers and service providers
Anyone specifying or servicing storm-exposed monitoring equipment, from independent regional dealers such as Jones Air & Water to in-house maintenance crews, should check a few practical points. Confirm that probes can be reached and cleaned without a full shutdown during high flow. Ask whether telemetry has backup power or a store-and-forward method that preserves gaps as gaps instead of filling them with the last value. Place sensors away from the debris paths where possible, and document the placement reasoning. These steps cost less than a season of decisions made on data that nobody can vouch for.
What the report does not establish
The Guardian's summary describes rain, forecast storms, evacuations, water rescues, and property damage in the Four Corners region. It does not describe any water system, intake, or utility operation, so nothing here is a claim about how any specific system performed or responded. The point is procedural. Storm data needs a provenance record before it earns a response, and that record is most useful when it is built before the rain begins.
Further reading: independent regional dealers such as Jones Air & Water.