AI in water management
We build models using your own measurement data from pumping stations, treatment plants and monitoring points, and put them into production, as we do in Waternet’s Datalab team.
Nitrous oxide emissions at the wastewater treatment plant: we developed a model for Waternet to minimise them
As part of Waternet’s Datalab team, we set up and maintain the MLOps workflow, including an MLflow model registry, CI/CD templates and the deployment of models to production. Now in development: a model to reduce the use of iron chloride when pre-treating river water for drinking water.
What can we do with all the data from pumping stations and treatment plants?
A process technologist checks aeration and nitrogen levels every day, and recently began monitoring nitrous oxide too. But the treatment plant still runs on fixed settings. A model that combines these measurements can suggest settings to reduce emissions. The operator decides.
Models for water treatment, drinking water and waterways that remain accurate after deployment
Fewer chemicals in pre-treatment
For Waternet, a model is being developed to reduce the use of iron chloride when pre-treating river water for drinking water.
Monitoring every model
For Rijkswaterstaat, we built a single general-purpose package that monitors models in production for data drift, prediction drift and outliers.
Waterway simulations
For Rijkswaterstaat, we used AIS data and a congestion model to simulate how an opening of the Botlekbrug affects road traffic jams.
Measurement data with shared terminology
We connect telemetry, laboratory measurements and Waterinfo, and follow Aquo terminology so you can continue to exchange your data with other water authorities.
One decision at a pumping station, weir or treatment plant determines which measurement series we retrieve first
-
Decision and measurement points
Which decision about water levels, dosing or aeration needs to improve, and which sensors, lab measurements and weather forecasts are relevant?
-
Prototype model using historical data
We train the model on previous years’ data, test it against a later period of high water or drought, and compare it with the current control rule.
-
Advice where the operator needs it
The forecast appears in the operator’s system, with drift monitoring in place. The technical specialist still makes the decision.
Are our water level or water quality measurement series good enough for a model?
A good fit if
You have years of measurements from pumping stations, weirs, treatment plants or monitoring points, and a recurring decision to make, such as pumping ahead of rainfall, adjusting chemical dosing or controlling aeration at a treatment plant.
Not a good fit if
The series have large gaps, sensors have been replaced without anyone recording the change, or a fixed control rule already works well. In that case, we start with the data or a dashboard—and we’ll tell you so.
What determines the scope
The number of monitoring points and sources, such as telemetry, laboratory data, Waterinfo and weather forecasts; how often a forecast is needed; whether it remains a prototype model; and who will manage the model afterwards.
Can a model help control operations?
We build it as an advisory tool: the operator or subject-matter specialist makes the decision. If you later want a model to control a pumping station or flood barrier automatically, first establish who will oversee it and how you’ll switch back to manual control.
Water level, water quality or treatment: where can a model deliver value first?
Water level and discharge
Choose this if you want to operate pumping stations and weirs earlier when rain or drought is forecast. You combine water levels, rainfall and the weather forecast; read more about forecasting.
Water quality
Choose this if you want to identify where readings at a monitoring point deviate, for example in relation to Water Framework Directive targets. Lab measurements are scarce, so expect limited historical data for each point.
Treatment and drinking water
Choose this if continuous measurements are already being taken, such as for aeration and nitrous oxide. Our advice: this is often where you’ll find the richest historical data, and the operator can use the results straight away.
Our work for Waternet and Rijkswaterstaat covered water treatment, drinking water and waterways
Data Science Lab has worked with data and AI from Amsterdam since 2016, as a Databricks and Microsoft partner. For Waternet and Rijkswaterstaat, we developed and monitored models for water treatment, drinking water and waterways.

Our first conversation focuses on one pumping station, monitoring point or treatment plant
Stef Stoelwinder
Business DevelopmentStef is your first point of contact. In our first conversation, we’ll discuss one decision about water levels, water quality or treatment, along with the relevant measurement data.
E-mail info@datasciencelab.nl
Phone +31 (0)20 3636 724
Which measurement time series would you like us to forecast first?
Describe the decision and the measurement time series you already have. We’ll reply by email or arrange an initial conversation.
Message sent
Thanks for your message. We’ll be in touch as soon as possible.
Frequently asked questions
AI in water management means training a model on measurements that water authorities already have: water levels, flows, rainfall, lab results and treatment plant process data. You can use it to predict a water level or flow, identify an anomalous measurement or suggest a treatment plant setting. These are among the AI applications we build, often for the public sector.
Water also features on our regional pages: bridges and waterways in Rotterdam, national water authorities in Utrecht, and networks and water in Groningen.
With a model that combines measured flow, rainfall, forecast rainfall and evaporation. Waterschap Limburg has published such a model for the flow of the River Roer in the Algorithm Register: a linear regression that provides hourly forecasts to support decisions. A specialist interprets the result and makes the decision.
Rijkswaterstaat uses Delft-FEWS, a system developed by Deltares, to forecast conditions along the Rhine and Meuse. A custom model can supplement that system where it falls short locally. The challenge is that high water levels are rare, so there are few examples of the situation that matters most. Read more about forecasting.
Usually more than they use: telemetry from pumping stations and weirs, monitoring wells, water quality lab results and treatment plant process data. Through Waterinfo, Rijkswaterstaat publishes current, forecast and historical measurements for national waters, including water levels, wave heights, flow data and water quality.
For data exchange, there is the Aquo standard, maintained by Informatiehuis Water, a partnership between provinces, Rijkswaterstaat and water authorities. Using its definitions makes it easier to combine data series from different databases. To learn where these sources come together, see our data and AI platform page.
A treatment plant collects measurements continuously, making it well suited to a model. For Waternet, we developed a machine learning model to minimise nitrous oxide emissions at a wastewater treatment plant. We are now developing a model to reduce the use of iron chloride in the pretreatment of river water for drinking water.
Water authorities are paying considerable attention to nitrous oxide. STOWA has published a handbook on monitoring nitrous oxide at municipal treatment plants, and the Lachgas Versnellingsprogramma is bringing continuous measurement to more facilities. Those measurements provide the historical data a model can learn from.
By monitoring it. A replacement sensor, a pumping station operating differently or a wetter winter changes the input, making forecasts less accurate. This is called drift. For Rijkswaterstaat, we built a generic package that monitors all its models in production for data drift, prediction drift and outliers.
Decide in advance who receives an alert and who approves a new version. You can read how this works technically on our MLOps page. Management can sit with your team or with us through management and continuous improvement.
The Water Framework Directive is the European directive on clean and healthy surface water and groundwater. Member states agreed to achieve good status by 2027 at the latest, with progress tracked through water quality measurements.
A model does not make water cleaner, but it can help identify an anomalous measurement or show which measure appears to have an effect. Lab samples are only taken occasionally, so the historical record at each monitoring point is often limited. Start by asking which decision about monitoring or measures needs to improve.
Annex III of the AI Act lists AI used as a safety component in the supply of water, gas, heating or electricity as high-risk. According to the European Commission, those obligations will apply from 2 December 2027. Your legal or compliance team must assess whether a model for a pumping station or treatment plant falls within that category; we can help you take stock of your models.
Public authorities publish their algorithms in the Algorithm Register, including the model for the flow of the River Roer. Read about how to do this responsibly on our Responsible AI and AI Act pages.
When a fixed rule in the pumping station controls already works well, when the decision rarely arises or when insights from the measurements are enough. In those cases, a Power BI dashboard using the telemetry is more useful than a model.
If the data series have gaps or no one knows when a sensor was replaced, start with the data foundation. If a simpler solution is a better fit, we will say so.
Want to read more about government, forecasting or model management?
- Data and AI for governmentHow we help policymakers and operational teams work from the same information.
- Forecasting and predictive modelsHow a model uses historical data and expectations to forecast, and when a simple rule works better.
- MLOpsHow models in production are monitored, retrained and released.