Water Quality Monitoring

The problem

pH, turbidity and chlorine are checked by grab samples, so a quality event between samples is found late and records for the regulator are incomplete.

Solution overview

MILESGO gateways collect data from water quality analysers (pH, turbidity, chlorine, DO), 4–20 mA / 0–10 V transmitters, flow meters over Modbus RTU / Modbus TCP, and deliver it to SCADA, a historian / database (MySQL, SQL Server, InfluxDB), SMS, email and messaging alarms as MQTT / OPC UA / Modbus TCP. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

water quality analysers (pH, turbidity, chlorine, DO)
4–20 mA / 0–10 V transmitters
flow meters

Protocol path

Modbus RTU / Modbus TCP → MQTT / OPC UA / Modbus TCP

Implementation checklist for the project manager

Keep sensor calibration certificates on file and plan recalibration intervals.
Confirm the authority’s reporting requirements and data formats at the start of the project.
Agree data retention and the report format needed for audits with the quality team at the start.
For hard-wired signals, list each DI/DO/AI/AO with its type (dry contact, 4–20 mA, 0–10 V, PT1000) and choose I/O modules accordingly.
Define an alarm matrix (priority, recipient, escalation) and test every alarm end to end at SAT.
Confirm local storage so data survives network outages, and define the retention period.

Project deliverables

Signed point table and protocol mapping
Gateway configuration files and backups
IP address plan and network drawing
FAT and SAT test records
As-built documentation and operator training

System architecture

Field layer: water quality analysers (pH, turbidity, chlorine, DO), 4–20 mA / 0–10 V transmitters, flow meters, connected over Modbus RTU / Modbus TCP. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: SCADA, a historian / database (MySQL, SQL Server, InfluxDB), SMS, email and messaging alarms, which receives the data as MQTT / OPC UA / Modbus TCP. Remote access for maintenance runs over VPN rather than open internet ports.

System composition

Field devices: water quality analysers (pH, turbidity, chlorine, DO), 4–20 mA / 0–10 V transmitters, flow meters
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: SCADA, a historian / database (MySQL, SQL Server, InfluxDB), SMS, email and messaging alarms (MQTT / OPC UA / Modbus TCP)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Software and AI capabilities

Anomaly detection on trend dataRoadmap
Automatic report drafting from collected dataRoadmap

Delivery steps

1
Site survey and point list
Inventory devices, protocols, register maps, panel space, power and network paths.
2
Design and point table sign-off
Map every point to the target protocol and system; agree it with the client and the upper-system contractor.
3
Configuration and FAT
Build the gateway configuration off site, simulate it and test against the signed point table.
4
Installation and wiring
Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.
5
SAT and alarm tests
Verify values against local readings, test every alarm and command end to end.
6
Handover and support
Hand over configuration backups, point table and as-built documents; train operators.

Customer value

Timestamped records for compliance and reporting
Abnormal conditions seen early, before they become failures
Alarms reach the right person by SMS, email or messaging apps
Reliable trend data for optimisation and fault diagnosis

Tell us about your project

Send the protocols, point count and target system. A sales and engineering pair reviews every submission.

Discuss Your Project