RO Conductivity Monitoring for Reverse Osmosis Applications | Tenber

Measurement-point, conductivity-cell, controller and signal selection for reverse-osmosis feed, permeate, concentrate and product water.

MODEL SELECTION SUPPORT

Need help planning RO conductivity monitoring?

Tell us your water application, measuring range and output requirement. We will recommend a suitable model.

Request Model Selection

RO Conductivity Monitoring for Reverse Osmosis Applications

This application page covers how to configure conductivity measurement in an operating reverse osmosis project: where to measure, what operators should see, how alarms reach the PLC or SCADA system, and how the installation is handed over.

Assign each measurement point an operating decision

Point Application purpose Project data to confirm
Feed Track incoming water and pretreatment changes Normal/peak conductivity, pressure, temperature and pipe size
Permeate Monitor product-water quality and membrane trend Low-range resolution, sample flow and alarm response
Concentrate / reject Observe concentration and recovery-related changes Upper range, chemical exposure and safe access
Post-polishing Check quality after EDI, mixed bed or another polishing stage Required unit, reference temperature and downstream action

Each point should have a named owner and a defined response. Do not install beside a chemical-injection point, in a stagnant dead leg or where air can collect.

Plan alarms and operator response

Set alarm thresholds from the site’s baseline and process limits, not from a generic catalogue value. Define high, low, delay, hysteresis and sensor-fault behavior. Document what the operator checks first: sample result, temperature, flow, pressure, pretreatment, membrane condition or sensor cleanliness.

For a permeate alarm, the response may be to verify the sample and membrane trend before diverting water. For a feed or reject alarm, the response may involve pretreatment, recovery or concentration conditions. Keep the alarm cause and the operator action together in the control narrative.

Connect the loop to PLC or SCADA

Confirm whether the project uses 4–20 mA, RS485 Modbus RTU, relay contacts or a combination. For analogue integration, document the engineering range, scaling, decimal position and fail value. For Modbus, document the address, baud rate, parity, register map, byte order and update interval.

Define whether the PLC receives a compensated value, an uncompensated value, a temperature value, an alarm state and a sensor-fault state. Test normal, high, low, calibration and power-loss conditions before handover.

Choose the installation arrangement

Select a flow cell, bypass, insertion fitting or immersion assembly according to the pipe, tank, flow and maintenance plan. Provide isolation and drainage where practical. Keep the sensor wetted during measurement, prevent trapped air and leave enough access for cleaning, calibration and replacement.

Record the flow direction, sample conditioning, cable route, grounding, enclosure location and environmental conditions. The installation drawing should identify every measurement point and its corresponding controller channel.

Commissioning handoff

  1. Verify the tag, stream, point and controller channel.
  2. Check sensor installation, wiring, temperature input and grounding.
  3. Confirm units, compensation, analogue scaling and communication settings.
  4. Compare the online value with a suitable reference under stable flow.
  5. Test alarm, relay, PLC/SCADA and sensor-fault behavior.
  6. Record baseline, calibration method, cleaning interval and next inspection date.

What to include in a project quotation

Send the process flow diagram or point list, stream names, normal/minimum/maximum conductivity, temperature, pressure, chemistry, installation, cable length, signal, alarm logic, quantity, destination and documentation requirements. This lets the project team review the complete loop rather than only the display.

For the overall selection framework, use RO conductivity monitoring guide.

Frequently asked questions

Where should the PLC alarm be generated?

Generate it where the responsibility is clear. The controller may provide the local alarm while the PLC handles process interlocks; define the boundary in the control narrative.

Is a bypass always required?

No. It depends on the pipe, flow, access and maintenance plan. A bypass can simplify isolation and calibration when the process arrangement supports it.