Stormwater monitoring sensors must capture rapidly changing runoff while surviving dry periods, debris, sediment, oil films and variable water levels. Turbidity, suspended solids, oil-in-water, conductivity and pH can support event detection and sampler triggers, but the station must be designed around event hydraulics, sensor wetting, representative location, telemetry and safe maintenance.
Why Buyers Search for stormwater monitoring sensors
Industrial sites, municipalities and integrators search this topic because scheduled grab sampling can miss the first flush or a short illicit discharge. Their real concerns are choosing ranges that cover both clear baseflow and dirty events, preventing bottom sediment from dominating readings, keeping sensors wet or correctly detecting dry state, and obtaining reliable data during storms when access is limited.
The first engineering task is to define the event or process condition the station must detect, the available response time, acceptable uncertainty, maintenance resources and trusted reference method. This turns a broad industry search into a specification a supplier can review.
YEXsensor Options for stormwater monitoring sensors
YEX-S1-ZS provides turbidity ranges to 1000 NTU, YEX-S2-TSS-S measures 0–2000 mg/L, YEX-S1-OIL-A measures 0–40 ppm by UV fluorescence, YEX-S1-EC supplies conductivity ranges through 200 mS/cm, and YEX-S1-PH measures 0–14 pH. Modbus output supports an RTU or gateway that combines sensor values with rain, level and flow data.
Published values are configuration boundaries, not permission to ignore the matrix. Ask YEXsensor to confirm each ordered model, range, output, wetted material, cable, protocol and application limit on the quotation or attached datasheet.
Technical Parameters and Procurement Checks
| Measurement item | Official product specification | Procurement check |
|---|---|---|
| Turbidity ranges | 0–20.00, 0–200.0 or 0–1000.0 NTU | Compare turbidity ranges with normal and upset samples |
| Turbidity response | T90 <30 seconds | Record the selected turbidity response on the RFQ |
| TSS range | 0–2000 mg/L; 0.1 mg/L resolution | Compare tss range with normal and upset samples |
| TSS accuracy | ±5%, depending on homogeneity | Define reference method and acceptance for tss accuracy |
| Oil-in-water range | 0–40 ppm; 0.01 ppm resolution | Compare oil-in-water range with normal and upset samples |
| Oil method and accuracy | UV fluorescence; ±3% FS based on standard solution | Define reference method and acceptance for oil method and accuracy |
| Conductivity ranges | 0–20 μS/cm to 0–200 mS/cm configurations | Compare conductivity ranges with normal and upset samples |
| pH range | 0.00–14.00; ±0.1 pH | Compare ph range with normal and upset samples |
| Outputs | RS485 Modbus RTU; TSS page also lists 4–20 mA | State PLC inputs and protocol for outputs |
| Protection | IP68 sensor designs; installation still requires mechanical protection | Review compatibility and mechanical exposure for protection |
What the Parameters Mean in the Industry Project
First-flush turbidity or TSS may exceed dry-weather values by orders of magnitude. Select range from event samples, not baseflow alone.
Turbidity and TSS are related but not interchangeable. Particle type changes during an event and can alter their correlation.
UV fluorescence response to fuel, lubricant or other oil varies by product. Correlate with representative contaminants and the project method.
Conductivity and pH can flag an illicit or process-water discharge, but they do not identify the source chemical by themselves.
How to Build a Procurement-Ready Monitoring Scope
A list of parameters is not yet a monitoring design. Each value needs a location, expected range, operating decision, acceptance method and responsible owner. Normal production, start-up, cleaning, rainfall, shutdown and upset conditions can differ sharply. The selected range must cover the events the project intends to detect without sacrificing useful resolution during normal operation.
Separate the field probe from the complete measurement point. Power, surge protection, cable, waterproof junctions, bracket or flow cell, isolation, controller, gateway, telemetry, calibration materials, spare parts and service access may all affect delivered cost. Ask suppliers to list inclusions and exclusions so procurement compares equivalent systems.
Define data authority before automation. Operator trend, early warning, sampler trigger, chemical dosing, equipment protection and regulatory reporting have different validation requirements. Automatic actions need communication-timeout behavior, invalid-value checks, rate limits, interlocks and manual override. A fouled, dry or disconnected sensor must not become a false process command.
Assign lifecycle responsibilities before purchase. State who cleans and calibrates, who reviews alarms, who can change setpoints, which spares are held and how reference results are recorded. These operating details often determine data reliability more than a small difference between catalog specifications.
Develop the alarm matrix with operations before commissioning. Define warning, action, out-of-range, maintenance and communication-loss states separately. Add persistence time or rate-of-change logic where short spikes are common, but preserve raw data for investigation. Every automatic response should have a documented reset condition and a safe manual mode.
Review total ownership cost over the expected service period. Field visits, calibration standards, replacement caps or electrodes, cleaning tools, telemetry fees, spare sensors and staff time may outweigh the initial probe-price difference. A line-item lifecycle comparison makes maintenance assumptions visible and reduces the risk of purchasing equipment the site cannot support.
Plan data review and retention with the same care as the field hardware. Store engineering units, range, calibration status and maintenance events with the time series. Trend related parameters together and retain enough raw resolution to investigate short excursions. During handover, provide operators with a simple decision tree for checking the process, installation, reference result and communication status before declaring a sensor failure.
stormwater monitoring sensors: Selection Boundaries
Provide catchment type, baseflow and event data, maximum depth and velocity, sediment, debris, expected oil products, pH and conductivity range, dry-state behavior, mounting, power, telemetry, sampler interface and maintenance access. Define which thresholds trigger sampling, alarms or diversion and how false alarms will be reviewed.
A suitable solution stays within the official sensor limits, represents the process and remains safely accessible. An unsuitable point exposes the sensor to unreviewed pressure or chemistry, confuses one parameter with another, or produces data too late for the intended action.
Recommended Measurement Points and Use Cases
Industrial outfall
Use oil, conductivity and pH changes to trigger diversion, inspection or an automatic sampler.
Construction runoff
Use turbidity or TSS with rainfall and flow to evaluate controls while keeping the sensor above moving bed sediment.
Municipal drainage network
Deploy stations at prioritized catchments and use telemetry to identify event timing and anomalous discharges.
Retention pond outlet
Compare inlet and outlet solids trend to assess settling and maintenance needs across storms.
Document every point on the process drawing with stream name, location, depth or sample flow, nearby dosing and return lines, expected range and action. Where the matrix is variable, multiple points or a survey may provide more value than one sophisticated but unrepresentative station.
Installation and Integration Notes
Use a stable mount outside direct debris impact, above the bed unless bed-load measurement is intended, and within the wetted zone during monitored events. Protect cables from flow and vandalism. Add level or wet-state logic, local data buffering and communication-loss alarms. Commission during real storms before finalizing thresholds.
For RS485 Modbus RTU, confirm supply, polarity, A/B convention, address, baud rate, parity, stop bits and register map. Use suitable topology, shielding and termination. Store final settings and PLC tag definitions with commissioning records so future replacement does not require reverse engineering.
Commissioning should include mechanical inspection, wiring checks, stable-value confirmation, calibration or verification, reference comparison, alarm simulation and communication-loss testing. Record maintenance state so cleaning or dry exposure is not mistaken for a valid process event.
How to Request a Comparable Quotation
Send the process diagram, application, water sources, measurands and units, minimum/normal/maximum values, temperature, pressure, pH and major matrix components, mounting, cable, output, controller, power, quantity and destination. Add required drawings, certificates, inspection records, packing and delivery terms.
Ask for line-item pricing for sensors, mounting, flow cells, controller, gateway, power, telemetry, calibration materials, spares and commissioning. A clear quotation prevents a low probe price from hiding essential system scope and gives engineering a record of the exact configuration purchased.
Frequently Asked Questions About stormwater monitoring sensors
Should stormwater stations use turbidity or TSS?
Use turbidity for rapid optical trend and TSS when solids mass is the required decision. Event-specific correlation can support both, but it should be updated when particle sources change.
How can a station handle dry weather?
Add water-level or wet-state logic so exposed probes are not reported as valid water data. Define safe standby, wet-up checks and the event start condition in the controller.
Can an oil sensor identify the spilled product?
No. UV fluorescence can indicate oil-related trend, but response varies by fuel or lubricant and does not provide product identification. Trigger confirmation sampling and site inspection.
What belongs in a stormwater RFQ?
Send catchment, event ranges, depth and velocity, mounting, debris protection, cable, solar or mains power, telemetry, sampler interface, quantity and alarm logic.
Can stormwater monitoring sensors data connect to PLC or SCADA?
Yes. The listed YEXsensor products support RS485 Modbus RTU, with selected models also listing 4–20 mA. Confirm address, baud rate, parity, register map, cable distance, grounding and required analog scaling before ordering.
How should sensor ranges be selected?
Use minimum, normal, alarm and credible upset values from each measurement point. Select configurations by stream or process zone rather than ordering the widest range for every location.
How should calibration and verification be planned?
Use separate standards plus event-based correlation for turbidity, TSS, oil, conductivity and pH. Define standards, stabilization time, as-found and as-left records, paired samples and maintenance ownership. Frequency should follow drift and fouling history.
Can online sensors replace laboratory testing?
Online sensors support event detection and sampler control; pollutant identification and regulatory load calculations require flow data and approved analyses. Use continuous data for trend and response while retaining laboratory work required by permits, contracts and the quality plan.
What should the quotation identify?
Require model, exact range, output, wetted materials, cable, mounting, accessories, protocol, warranty, lead time, exclusions and line-item pricing. The offer should match the process diagram and RFQ, not only a product family name.
Summary
Effective stormwater monitoring sensors starts with process decisions, not a generic sensor list. Match each YEXsensor model and range to a defined stream, installation condition, reference method and response action. Treat integration, calibration, fouling, access and spares as part of the measurement point.
For a useful quotation, send the process drawing, ranges, matrix, mounting, cable, output, controller, quantity, documents and destination. YEXsensor can then confirm a deployable configuration instead of an ambiguous collection of probes.











