Drinking Water & Purification System Online Monitoring: How to Combine Conductivity, TDS, UV254, Turbidity, and Filter Status

Why This Industry Needs Continuous, Interpretable Water Quality Data

The monitoring object of drinking water and purification is not a static sample, but a process that continuously changes with flow, temperature, raw water, weather, equipment status, and human operations. Traditional sampling and laboratory analysis are irreplaceable, but they only cover the sampling moment. For household water purifiers, commercial water dispensers, central water treatment, pure water equipment, bottled water production, and small water supply systems, the real challenge is what happens between two samplings, how long changes last, whether they synchronize with a process action, and when to trigger a review. The first value of continuous sensors is to fill these gaps into time series.

The goal of this approach is to allow raw water variations, membrane separation effects, filter load, storage contamination risks, and end-user experience to be interpreted separately by sensors at different locations, rather than summarizing all water quality with a single TDS value. Therefore, a project should not start with "which probe to buy," but should begin with the decision problem, acceptable response time, data usage, and evidence level. Data for alarms, operations optimization, customer display, and regulatory reporting require different calibration, redundancy, and review procedures. Define the purpose first to avoid using expensive equipment to generate large amounts of unused data.

Step 1: Write Monitoring Goals as Verifiable Engineering Problems

An actionable goal should include the object, location, time scale, acceptable risk, and follow-up actions. For example, "When key trends in conductivity, TDS, temperature, UV254, turbidity, color, and organic load deviate from the normal baseline and persist for a certain period, the system issues graded alarms; operators inspect the process and site status, and retain reference samples if necessary." This statement is more valuable than "real-time water quality monitoring" because it simultaneously constrains points, sampling period, thresholds, review, and responsible persons.

• Trend goals: Identify baselines, daily cycles, seasonal variations, startup and shutdown processes.
• Event goals: Capture sudden increases, decreases, continuous drifts, and unreasonable combinations between parameters.
• Control goals: Provide input for aeration, blowdown, flushing, bypass switching, filter management, or process adjustments.
• Quality goals: Preserve raw values, status codes, cleaning and calibration records, and manual notes to enable data traceability.
• Commercial goals: Use continuous evidence to demonstrate product, process, or service value while clearly defining measurement boundaries.

At project initiation, it is recommended to create a one-page "Measurement Task Sheet": list the normal range, minimum meaningful change, expected response time, maximum acceptable missing duration, reference method, maintenance resources, and output recipients. The task sheet is not a one-time document but should be updated after commissioning, seasonal changes, and process modifications.

Parameter Combination: Different Measurement Mechanisms Should Explain Each Other, Not Simply Stack

Conductivity reflects the ionic conductive ability of water; TDS is usually estimated from conductivity using a conversion factor. The conversion factor varies with different ionic compositions, so TDS is more suitable for trends and product display rather than treating any converted value as a complete chemical analysis. UV254 and turbidity provide another type of optical information, but they cannot replace microbiology, specific toxic substances, or regulatory laboratory testing.

Correspondence with AtomBit Product Capabilities

Dual-channel or three-channel BA series ASICs are suitable for comparing conductivity/TDS changes between raw water, post-membrane water, and different purification stages, supporting temperature compensation, digital output, and embedded product development. NSDD-Lite3 is suitable for commercial water and relatively clean water bodies to add TOC, COD, UV254, and temperature trends, supplementing organic changes that cannot be explained by ionic indicators alone.

The core products involved in this article are BA012, BA022, BA112, BAT3U multi-channel ASICs and the NSDD-Lite3 compact optical sensor. Selection must be based on the latest datasheet, target water sample, range, temperature, pressure, material, interface, and installation conditions. This website article provides engineering logic and does not replace item-by-item technical confirmation. For new water bodies or cross-industry applications, AtomBit can cooperate in sample evaluation, interface confirmation, trial installation, and model validation.

System Architecture: From Probe to Actionable Information Requires a Complete Data Chain

A reliable system typically includes five layers: the measurement layer is responsible for stable acquisition of raw signals; the edge layer handles power supply, communication, time synchronization, and status collection; the platform layer is responsible for storage, unit conversion, quality marking, and permissions; the analysis layer handles baselines, rates of change, correlations, and event rules; the business layer delivers results to operations, quality, after-sales, or customer interfaces. If any layer is missing, a seemingly online system may lose practical value.

RS485/Modbus RTU is suitable for multi-device buses in industrial sites. Engineers should unify address, baud rate, parity, register type, data length, byte order, unit, and scaling factor; the master polling should set reasonable timeout and retry, and communication failures should not be automatically written as zero. Each record should ideally include device time, platform reception time, quality status, maintenance status, and raw register snapshot for problem tracing.

Data Frequency: Faster Is Not Always Better

The sampling period should be shorter than the change time of the target event, but also consider sensor response, flow cell replacement, network bandwidth, and storage. Second-level acquisition is suitable for equipment diagnostics, minute-level averages are commonly used for operation screens, and hourly or daily statistics are suitable for management reports. It is recommended to save high-frequency raw data and then generate derived data at different time scales to avoid losing the ability to review transients after only storing averages.

Point Selection and Installation: Representativeness Is Often More Important Than Nominal Accuracy

The raw water point is used to establish the input baseline; the pre-membrane point can identify pretreatment changes; the post-membrane point observes rejection efficiency; the storage and terminal points judge secondary changes. Multi-point design must also consider water circuit dead ends, stagnation during shutdown, temperature changes, flushing processes, and sampling timing.

Immersion installation should keep the sensing surface continuously submerged, avoid direct impact and cable stress, and reserve space for lifting, cleaning, and replacement. Flow-through installation should ensure sample representativeness, stable flow, bubble removal, and supporting shut-off, bypass, drain, and flushing structures. High pressure, high temperature, corrosive, or food contact scenarios also require separate confirmation of seals, materials, and hygiene requirements.

• Survey the actual minimum and maximum water level, flow, temperature, pressure, and pollution load.
• Use portable instruments or sampling to compare candidate points and confirm spatial representativeness.
• Check for bubbles, sediment, floating matter, sunlight, vibration, electromagnetic interference, and maintenance safety.
• Record installation depth, orientation, flow cell volume, pipe length, and photos, and include them in the site archive.
• During trial operation, retain reference samples to verify point selection and response time before finalizing the design.

Calibration, Verification, and Data Quality: Establish a "Pre-Clean – Post-Clean – Post-Check" Evidence Chain

Quality control for continuous sensors cannot be reduced to just a calibration date. Each maintenance should first record the stable value before cleaning and site status, then complete cleaning and record the value after cleaning, and finally perform verification with a reference solution, portable reference instrument, or representative sample. These three sets of data can distinguish contamination effects, calibration drift, and real water body changes. If only the final normal value is retained, the basis for judging whether historical data can be used is lost.

Laboratory comparisons must ensure that samples correspond in time and space to sensor readings, and record sampling, preservation, transport, method, and uncertainty. For spectral proxy quantities, normal, low, high, and typical abnormal ranges of the target water body should be covered. Model evaluation should not only look at correlation coefficients but also observe residuals, low-end bias, high-end saturation, seasonal stability, and cross-point applicability. When the water matrix changes significantly, revalidation should be performed.

The data platform should use quality flags rather than simply deleting anomalies. It is recommended to distinguish at least: valid, under maintenance, cleaning recovery, under verification, communication failure, out of range, suspected bubble, suspected contamination, and pending review. Customer-facing charts can hide invalid segments, but the internal database must retain raw values, causes, and processing records.

Alarm Design: Threshold, Rate of Change, Duration, and Parameter Correlation Are All Essential

A single fixed threshold is easily affected by seasons, formulations, raw water, and operating conditions. More robust rules can combine absolute thresholds, relative baselines, rates of change, durations, consistency among multiple parameters, and equipment status. For example, if turbidity spikes but flow, UV254, and organic trends do not respond, it may be bubbles or local particles; if multiple related parameters change synchronously and persist, it is more worthy of triggering sample retention and manual inspection.

Alarms must be bound to a handling process: who receives, how long to confirm, which status to check first, whether to re-measure, when to keep a sample, when to escalate, and when to close. Unverified automatic control should set upper and lower limits, hysteresis, minimum run time, interlocks, and manual override to prevent a brief sensor anomaly from directly driving critical equipment.

Common Failure Modes and Prevention Measures

• Promoting low TDS directly as safe or healthy
• Using a fixed TDS conversion factor for all raw water types
• Probes installed in dead-end branches causing lagging readings
• Filter life calculated only by time, ignoring water usage and raw water changes
• Ignoring normal transients during startup flushing and shutdown stagnation

The common feature of these problems is that the equipment itself may not be damaged, but the data has lost representativeness or interpretability. Prevention strategies should cover site structure, communication, algorithms, personnel, and files, rather than attributing all problems to "recalibration." When anomalies occur, first check status codes, raw signals, adjacent parameters, maintenance records, and site events before deciding to clean, recalibrate, remodel, or replace components.

How to Calculate Total Cost of Ownership and Project Benefits

Provide interpretable water quality display, filter management, and remote service basis for water purification equipment, and embed sensing capabilities into mass-produced products at lower volume and cost through multi-channel chips.

The cost model should at least include sensors and accessories, installation structure, power supply and communication, platform, reference samples, consumables, labor, inspection transport, downtime, spare parts, and data review. Benefits can be measured by anomaly advance warning, reduced manual sampling, avoided downtime or quality loss, chemical and energy optimization, reduced false alarms, and customer service efficiency. For reagent-free solutions, reagent procurement, storage, waste liquid, and pump/valve maintenance should also be compared with traditional solutions over the full lifecycle.

Do not rush to promise large-scale savings during the pilot phase. First select a point with a clear pain point and access to reference samples, run a cycle covering typical conditions, and statistically quantify data availability, maintenance time, event discovery count, false alarm rate, and relationship with reference methods. Only when a verifiable pilot report is formed can scaled replication have a reliable basis.

Phased Implementation Roadmap

1. Requirements definition: Determine business problem, parameters, candidate points, data usage, reference methods, and responsible persons.
2. Sample and interface assessment: Verify water sample range, environmental conditions, power supply, communication, materials, and main controller interface.
3. Small-scale pilot: Establish installation archive, baseline, maintenance cycle, reference samples, and quality flags.
4. Model and alarm validation: Check error, residual, seasonal stability, and alarm handling effectiveness using independent data.
5. Scale deployment: Replicate verified structures, address planning, parameter tables, O&M forms, and spare parts strategy.
6. Continuous improvement: Review data availability, maintenance costs, event value, and model version monthly or quarterly.

At each stage, retain an "exit condition": if the point is not representative, the target change is less than system uncertainty, maintenance resources are insufficient, or the data has no clear user, modify the plan rather than continue adding equipment. For new industries not previously covered by AtomBit, the customer's process knowledge combined with our sensing, interface, and engineering verification capabilities can jointly define new application boundaries.

Procurement and Technical Review Checklist

• Is the target water body, parameters, range, temperature, pressure, material, and expected response time documented?
• Do sensors, probes, cables, cleaning devices, flow cells, brackets, gateways, and power supplies form a complete BOM?
• Are communication protocol, registers, byte order, address, baud rate, status codes, and anomaly values debugged together?
• Are calibration solutions, reference instruments, laboratory methods, sampling plan, and acceptance criteria clear?
• Are responsibilities for automatic cleaning, manual maintenance, spare parts, training, remote support, and data divided?
• Do all promotions, alarms, and reports accurately describe the boundaries of trends, proxies, screening, and compliance results?

Engineering Appendix: Review Method from a Single Reading to Credible Conclusions

When reviewing a segment of data, first check completeness: whether time is continuous, whether the device clock jumps, whether communication failures are written as zero, and whether maintenance periods are correctly flagged. Second, check physical reasonableness: whether temperature and range are reasonable, whether the rate of change is possible, and whether related parameters show exactly the same or completely opposite anomalies. Third, check site evidence: whether pump, valve, aeration, feeding, rainfall, discharge, cleaning, and sampling records correspond to the curve.

Fourth, compare. First compare with the historical baseline of the same device, then compare with adjacent points, other measurement mechanisms, and reference samples. When comparing, unify time, unit, temperature conditions, and sampling position. Disagreement between two methods does not automatically mean the online sensor is wrong; it may stem from sample inconsistency, preservation changes, laboratory uncertainty, or different measurement objects of the two methods. The difference itself is important information for understanding the water body.

Fifth, form a conclusion hierarchy. Conclusions can be classified into "trend changes with normal equipment status," "suspicious events requiring site verification," "water quality changes confirmed by reference samples," and "invalid data affected by contamination or drift." This grading is more suitable for continuous monitoring than simple pass/fail, and allows operations, engineering, and management to communicate based on the same evidence.

For cross-industry new applications, it is recommended to establish a joint verification sample library: each sample stores time, point, operating conditions, sensor raw and output values, lab results, and remarks. The sample library is not only for one-time calibration but also for regression testing of firmware, model, and hardware version upgrades. As customers accumulate data, technical capabilities can continuously expand to new water bodies and decision problems on a fixed sensing principle.

Conclusion: Technology Platform Fixed, Application Value Defined Jointly by Field Problems

BA012, BA022, BA112, BAT3U multi-channel ASICs and the NSDD-Lite3 compact optical sensor provide integrable and verifiable sensing and interface capabilities; the ultimate value comes from the customer's understanding of industry processes, correct point selection, reference methods, data quality, and clear actions. Typical applications are only a part that has been validated. For new water bodies, equipment, or business models, AtomBit can collaborate from sample, selection, interface, trial installation, calibration, data interpretation to mass production, helping partners turn unknown applications into deliverable solutions.

References and Further Reading

• WHO Guidelines for Drinking-water Quality: Framework for risk management and operational monitoring
• USGS materials on conductivity and TDS proxy relationships and their applicability boundaries
• AtomBit BA series ASIC, probe, and NSDD-Lite3 product documentation

This article summarizes engineering application methods, original compilation based on publicly available agency guidelines and AtomBit product information. Specific projects should comply with local regulations, industry standards, and safety requirements; conclusions involving compliance, health, or trade release should be confirmed by qualified laboratories and responsible agencies.

Supplementary Note: Project Documentation and Long-Term Maintenance Mechanisms

It is recommended to establish for each project: equipment list, site description, wiring diagram, register table, calibration records, reference sample records, maintenance records, alarm handling records, and version change records. Documents should be linked to equipment serial numbers and point IDs to prevent knowledge loss when personnel changes. When modifying range, coefficient, threshold, and model on the platform, record the modifier, reason, time, and impact scope, and retain rollback capability.

Long-term operation should also set indicators such as data availability, maintenance hours, verification pass rate, communication success rate, alarm confirmation time, and effective event ratio. Indicators are not for blame but to detect systemic problems: if maintenance hours at a site are consistently high, the installation structure may need adjustment; if false alarms concentrate during rainy periods, the seasonal baseline should be improved; if reference sample coverage is persistently insufficient, sampling resources should be rearranged.