9.1 Flow Monitoring, Flow Meters & Sensor Calibration

9.1 Flow Monitoring, Flow Meters & Sensor Calibration

Exam Focus: Perform adjustments on… flow monitoring, monitor flow sensors, and collect and document data from charts, gauges, and other instrumentation are three separate criteria tasks that all rest on the same skill set.

---

Why Flow Monitoring Exists

Flow data answers questions the utility cannot answer any other way:

• I/I quantification. Comparing wet-weather to dry-weather flow by basin identifies which sub-basins deserve rehabilitation money.
• Capacity assessment. Confirming whether an interceptor can carry projected growth plus peak wet weather.
• SSO investigation. Reconstructing what the system was doing before and during an overflow.
• Model calibration. A hydraulic model is only as good as the monitored flows used to calibrate it.
• Permit and billing compliance. Reporting to the regulator, and inter-agency billing where one utility conveys another's flow.

---

Site Selection

A monitoring site is chosen for hydraulic quality, not convenience:

• Straight, uniform pipe with at least several diameters of undisturbed approach; avoid drop connections, junctions, and bends immediately upstream.
• Free-flowing conditions where possible, so depth relates predictably to flow.
• No sediment or debris at the sensor location.
• Adequate depth — very shallow flow gives poor velocity resolution.
• Safe access — the site is a permit-required confined space, and it will be revisited repeatedly.

Sensing Depth and Velocity

Depth is measured by a submerged pressure transducer, by downward-looking ultrasonic from the crown, or by an upward-looking ultrasonic sensor in the band. Pressure transducers need their vent tube desiccant maintained (Section 2.3). Ultrasonic sensors are non-contact and stay clean, but foam, condensation, and heavy turbulence disturb the echo.

Velocity is measured by Doppler (reflecting sound off particles and bubbles and reading the frequency shift) or by electromagnetic sensors. Doppler reads a sample of the flow near the sensor, not the true mean velocity across the section, which is a systematic source of error the meter's firmware corrects with a profile factor.

Flow is then computed from continuity:

$Q = A \\times V$

where the area $A$ is derived from measured depth and the known pipe geometry. This is why an incorrect pipe diameter entered at setup corrupts every reading the site ever produces — the meter computes area from the diameter it was told.

---

Reading the Data

The Hydrograph

Flow plotted against time shows the diurnal pattern — the morning and evening peaks of domestic use — and the wet-weather response. The shape of the storm response separates inflow from infiltration: a fast, sharp peak coincident with rainfall is inflow; a slow rise with a long recession tail extending days past the storm is infiltration (Section 4.1).

The Scattergraph

The scattergraph plots velocity on one axis against depth on the other, one point per reading interval. It is the single most diagnostic display in flow monitoring, because a healthy free-flowing pipe produces a tight, predictable curve, and departures from that curve identify specific hydraulic problems:

• Points falling below the expected curve — lower velocity than the depth should produce — indicate backwater or a downstream restriction: the pipe is deeper than it should be for the flow it is carrying.
• A cluster at high depth with collapsing velocity indicates surcharging.
• Scatter that drifts over weeks usually means sensor fouling, not a change in the sewer.

A hydrograph alone cannot distinguish "more flow" from "same flow, backing up." A scattergraph can.

---

Verification and Calibration

Field instruments are verified, not assumed.

• Manual depth check. Measure the actual liquid depth with a chalked rod or a folding rule and compare it to the recorded depth. This is the fastest and most valuable single check, and it should be recorded at every site visit.
• Independent velocity check. Take a velocity profile with a handheld meter and compare it to the recorded velocity.
• Pump runtime cross-check. At a lift station, multiply verified pump capacity by accumulated runtime hours and compare to metered volume for the same period. This uses the station itself as the reference and is the strongest independent verification available. Pump capacity itself is verified by a drawdown test (Section 6.2).
• Zero and span. Ultrasonic sensors are zeroed against a known distance; pressure transducers are zeroed in air or at a known submergence.
• Cleaning. Grease and rag material accumulating on the sensor band is the dominant cause of drift in collection systems. Clean the sensor at every visit and record that you did — a "sensor drift" that was actually a grease coating will otherwise be misread as a real hydraulic change.

Adjusting a sensor is not the same as correcting data. Note the as-found reading before adjusting, so that the record shows when the drift began and the historical data can be corrected or flagged.

---

Documenting the Data

The criteria call for collecting and documenting data. Practical requirements:

• Record the as-found condition, the as-left condition, and every adjustment, with date, time, and the operator's name.
• Record site conditions — sediment depth, surcharge marks, grease, unusual odor, anything that would explain an anomaly months later.
• Keep the raw data, not only the processed output. Regulators and consultants will ask for it.
• Note rainfall from a co-located or nearby gauge; wet-weather flow data without matched rainfall data cannot be interpreted.
• Flag suspect periods rather than silently deleting them. Deleted data with no explanation destroys the credibility of the whole dataset.