The short version: Many installations were manually maintained, with too little insight and intervention happening too late. Barberry delivered the full path—industrial-grade sensors, connectivity, cloud platform, dashboards, Telegram alerting, calibration support and technician training—so operators could see hourly behaviour, respond to abnormalities and plan from actual usage.
The operational difference
A sensor feed is not an operating model
At smaller sites, manual checking can leave a long gap between a change in water quality, flow, tank level or pump condition and the moment someone notices. At larger installations, SCADA may exist but still be expensive or hard to translate into a clear next action. The goal was not monitoring theatre: it was an affordable, industrial-grade operating view that teams could trust.
What was delivered
| Layer | Operational purpose |
|---|---|
| Devices and sensors | Measure raw water, product water, volume, levels and relevant quality conditions. |
| Connectivity | Use LPWAN, Wi-Fi or another suitable approach where difficult connectivity made ordinary deployments unreliable. |
| Cloud platform and dashboards | Make hourly trends, device state and usage visible to operators. |
| Rules and alerting | Route useful exceptions to the people who can act, including Telegram notification patterns. |
| Field workflow and training | Support checklists, technician training, manual testing and app workflows where the engagement required them. |
For some larger installations, the approach replaced costly SCADA arrangements with lower-cost industrial-grade sensors and devices. It is a delivery pattern, not a claim that every system should be replaced.
Calibration is part of trustworthy data
Not every measurement can be “fixed in software.” In the documented work, tank levels could commonly be calibrated through the dashboard, while water-quality sensors needed physical buffer calibration on site. Field teams retained that responsibility, supported by checklists and training aligned to the relevant water-quality requirements, including SANS 241-informed practices where appropriate.
What changes for operations
- Teams can see when a pump stops or a measurement becomes abnormal, rather than discovering it only at the next manual test.
- Hourly patterns reveal actual consumption and help operators plan plant capacity and billing from observed usage.
- Water-quality and dosage context supports earlier intervention where reliability matters.
- Technicians work from a clearer operating view while physical checks and calibration remain accountable field work.
No final response-time, downtime or revenue figure is claimed here. The documented outcome is earlier, more informed action and less reactive rushed execution.
Bring one real operational signal
If your team has one alert, spreadsheet, device-data sample or recurring field problem that deserves a clearer response path, start there. A focused pilot can connect the signal, operating context and accountable action before a broader rollout.
Bring a telemetry or field-workflow example
Related: PoolSense · IoT and telemetry systems · guided technical support