Service · Web development

Custom water technology software development.

Custom software for pumping and distribution installations, drinking water production, water treatment and irrigation. Real-time telemetry from float switches and pressure, flow and quality sensors, connected to your PLCs via OPC UA, Modbus or Profinet — with an operator layer your water technicians understand.

PLC & SCADA integrationOPC UAMobile operator appDrinking water compliance

What water engineering software typically needs to do.

Water engineering is an umbrella term for everything that transports, treats or doses water: drinking water production and distribution at Vitens, Brabant Water, PWN, Evides, WMD and Waternet, municipal wastewater and sewage pumping stations, water boards handling regional water system management, industrial process water installations at food and chemical companies, cooling towers, swimming pool and recreational water, irrigation in horticulture and agriculture, and onboard water systems on ships.

Functionally, much of the software in this sector follows the same pattern: pumps, valves and frequency controllers are controlled from the PLC, sensors deliver real-time data (float switches, pressure gauges, flow meters, pH, conductivity, turbidity, free chlorine), and operators want to see that data at the right level — at the installation, in a central control room, or on a tablet on the move. On top of that come alarm management, trending, recipe or setpoint management for different water quality targets, and compliance reporting to regulators.

In the Purdue reference model for industrial automation, a typical water installation is structured as follows: level 1 is the PLC with motor control and safety loops, level 2 is the local HMI at the station, level 3 is SCADA for supervisory monitoring across multiple sites and pumping pits, and level 4 is your information and compliance system (reporting to the ILT, water boards or Vitens quality management). We mainly build at levels 2, 3 and 4 — the operator, supervisory and information layers — and integrate with your PLCs and existing SCADA environment via OPC UA, Modbus TCP, MQTT or Profinet.

We build custom software when a standard SCADA package is not the right fit: because you want a single information layer across multiple PLC brands, because you want to give field operators a mobile HMI or control app, or because you need deep integrations with your maintenance system, energy monitoring or asset register. For maintenance on pumps and frequency controllers, we often work with an integration to a CMMS maintenance system, and for energy consumption per pumping station or treatment step we link to energy monitoring.

Three flavours of water engineering software.

Depending on where in the stack you need custom software: at the installation, across your sites or stations, or as an information layer for compliance and management.

Compact project · fixed sprint budget

Local operator and monitoring app

A web- or tablet-based control interface for a single installation: pumping or lift station, treatment line, drinking water pump or cooling tower. Real-time data from float switches, pressure sensors and flow meters, prioritised alarm handling, basic trends and operator login with role management. Suitable as a modernisation of an outdated proprietary HMI or as an additional mobile layer alongside your existing SCADA.

OPC UA clientReal-time trendsAlarm managementTablet- and touch-ready
Mid-sized project · fixed sprint budget

Multi-site monitoring & mobile control

A platform that brings dozens to hundreds of pumping wells, lift stations, booster stations or treatment lines into a single overview. A unified data layer via OPC UA and MQTT, push notifications for critical alarms, and role-based access per region or asset cluster. Operators and on-call staff see what is happening on their phone or tablet, without being tied to a PC in the central control room.

Multi-site overviewMQTT pub/subPush notificationsOn-call roles
Larger project · fixed sprint budget

Information and compliance layer on top of SCADA

A custom information layer on top of your existing Wonderware, WinCC, Ignition or FactoryTalk environment. Quality reporting for the Dutch Drinking Water Act, BTO contributions, HACCP records for process water, integrations with your asset register and CMMS, and dashboards for management and regulators. Deep horizontal integration with ERP, GIS and maintenance systems.

Where the focus is on drainage rather than treatment, different standards and a different kind of record apply. Our page on sewer management software with an inspection register covers that.

SCADA tap via OPC UACompliance reportingGIS & asset registerHistorian integration

What you get at the end.

A production-ready water engineering layer, plus the documentation and integrations to manage and extend it yourself.

  • The water engineering software itselfProduction and staging, running on an industrial-grade PC, edge device or in your cloud, depending on what the OT network allows and what segmentation your security team prescribes.
  • OPC UA, Modbus and Profinet integrationsConfigured for your specific PLC brands (Siemens, Rockwell, Beckhoff, Schneider, Wago), with tag mapping, a watchdog for dropped connections and a gateway for legacy protocols where needed.
  • Codebase and architecture documentationFull source, build instructions, deployment runbook and an architecture overview in which your OT and IT teams can find the choices made around network segmentation, redundancy and data flow.
  • Operator and administration manualWritten for the people who work with it every day: how to adjust a setpoint, how to acknowledge an alarm, how to configure a new operator role or a new station.
  • Compliance and validation documentationAudit log specification, data quality checks and, where applicable, a traceable link between quality measurements and the reports sent to regulators.
  • Maintenance contract (optional)Monitoring, security patches, ongoing development, and keeping up with PLC firmware updates that change tag names or types. Fixed monthly price, with four response-time levels for on-call scenarios.

When custom is the right choice.

We don't replace Siemens WinCC, AVEVA/Wonderware System Platform, Inductive Automation Ignition or Rockwell FactoryTalk for enterprise SCADA on a large installation. They are good at that. Custom development is worth considering in these situations.

Multi-vendor PLC

Different PLC brands in one layer

You have Siemens PLCs at pumping stations alongside Rockwell on a treatment line, or Beckhoff on modern installations alongside Wago or Schneider at older wells. A single-vendor SCADA forces everything into its own ecosystem. A custom layer talks to all of them via OPC UA and gives your people a single user interface.

Mobile on-call

Operators in the field

The on-call team isn't sitting in a central room but out on the road. A browser-based operator app fits on a tablet and phone, without you having to manage three different interfaces. Push notifications for overflows, critically low levels or overpressure land straight on the right device.

Deep integration

Beyond the plant floor

The software needs to push maintenance notifications to the CMMS, write quality data to the laboratory LIMS, and link energy consumption per station to your energy monitoring. That kind of horizontal integration is not part of standard vendor SCADA packages.

Compliance and reporting

Drinking water or HACCP reporting

You need to demonstrate compliance with the Dutch Drinking Water Act, contribute to BTO research, or keep HACCP records on process water in a food business. A custom information layer on top of your SCADA makes reporting traceable and repeatable, without building spreadsheets by hand every month.

OPC UA, Modbus and the PLC landscape in water technology.

In recent years, OPC UA (Open Platform Communications Unified Architecture) has become the dominant way to communicate with a PLC in the water sector too. It is vendor-independent: an OPC UA client talks to a Siemens PLC just as well as to a Rockwell, Beckhoff or Wago, provided the PLC publishes a UA server. For modern PLCs this is built in as standard; for older Modicon or Wago installations, we build a gateway that translates Modbus TCP, Profinet or a manufacturer-specific protocol into OPC UA. For your information layer, that means one protocol, one tag model and one security layer, instead of maintaining six different PLC driver libraries.

For multi-site water installations — think of a water board with dozens of pumping stations, or a drinking water company with hundreds of distribution stations — we also work with MQTT as a pub/sub layer. MQTT is light on bandwidth (useful on 4G/LTE connections or legacy copper), keeps connections open from behind NAT, and lets multiple consumers listen in on the same stream (operator app, multi-site dashboard, historian, lab integration) without each setting up its own connection to the PLC. At field level, Modbus TCP is still regularly needed for smaller sensor modules or legacy PLCs where OPC UA is overkill or unavailable.

The tech stack of a typical custom layer for water technology looks like this: a web front end in React or Vue for the operator interface and multi-site dashboards, a Node.js or Python back end that handles PLC and SCADA communication and normalises data, a time-series database (InfluxDB or TimescaleDB) for historical trending of flow rates, pressure and quality, and WebSocket or Server-Sent Events for real-time push to the browser. For on-call staff and engineers, we often link the information layer to an IoT app that shows the same data on a phone or tablet, with push notifications for overflows, level alarms or a failed pump.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Standard SCADA packages and when they fit.

The Dutch water technology landscape relies largely on a handful of SCADA packages: AVEVA/Wonderware System Platform (formerly InTouch, widely used at water boards and drinking water companies), Siemens WinCC and WinCC OA (strong in industrial process water environments and at larger treatment plants), Inductive Automation Ignition (vendor-independent, web-based, on the rise), and Rockwell FactoryTalk View (on Allen-Bradley installations, more common in the food industry). These packages are mature, well documented and, in many cases, the right choice for the SCADA layer itself.

We deliberately do not replace those enterprise SCADA environments. Where we come in is the operator layer at the installation (close to the PLC), the mobile layer for on-call staff and engineers, and above all the information and compliance layer on top of SCADA. That layer is slightly different in every water organisation: your reporting requirements, your asset register, your maintenance process, your integration with ERP and GIS. Making a packaged SCADA do that information layer as well almost always leads to vendor lock-in, high per-user licence costs and rigid reports that do not keep pace with regulation.

A specific example where custom wins: you are a water board with around ten treatment plants on Wonderware System Platform and hundreds of pumping stations on various PLCs, some with local telemetry. You want a single dashboard that on-call staff, asset management and the board can all follow, with push notifications on overflows and automatic reports to Rijkswaterstaat and the province. In that case, our layer taps into the Wonderware historian and the PLCs via OPC UA, normalises tags across the installations, and delivers a single web interface that works on the dike reeve's phone. For industrial water installations, such as a food factory with HACCP requirements on its CIP water, we work in a similar way: WinCC or FactoryTalk stays, and the compliance reporting is built on top.

If you manage drinking water installations at priority institutions, fixed legionella prevention requirements apply: a management plan, a logbook and six-monthly sampling. See legionella management plan software.

If you work on the refrigerant circuit of cooling or climate installations, the F-gas Regulation applies and you must work from a STEK-certified company. How to keep that logbook is covered on STEK dossier.

How a water technology project runs.

1

Introduction and site visit

A conversation in which we learn which installations you have, which PLC brands they run on, which SCADA you use and which compliance requirements apply (Drinking Water Act, BTO, HACCP, EHEDG). Ideally, we walk a station or treatment plant with you — seeing the inside of a pumping station tells you more than a diagram in an office.

2

Tag inventory and wireframes

We draw up an inventory of the OPC UA, Modbus or SCADA tags the software needs, and sketch the first screen flow with your operator, process and asset engineers. At the end, you have a scope, a schedule and a clickable prototype your people can test.

3

Building in sprints

Every two weeks, a working build you can try out on a staging PLC, a SCADA tap or a PLC simulator. Operators test from the first sprint — an interface that looks good in the meeting can still turn out to be awkward in the waiting room or on a tablet on the move.

4

Rollout and maintenance

A phased go-live at one station or treatment plant, then rollout to the rest. Operator training, a short video tutorial and a runbook for your IT and OT teams. After that, ongoing maintenance for security patches, PLC firmware changes and further development.

Frequently asked questions.

What clients in the water sector usually want to know before we start on a custom project.

Who do you build water technology software for?
For organisations that transport, treat or dose water: water boards, drinking water companies (Vitens, Brabant Water, PWN, Evides, WMD, Waternet), municipal wastewater organisations, industrial process water environments in food and chemicals, cooling tower operators, swimming pool and leisure water, irrigation in horticulture and agriculture, and onboard water on ships. The technical patterns are more alike than many people think — pumps, valves, sensors, alarms.
How do you handle PLC control of pumps, valves and level meters?
The PLC itself remains in control of pumps, frequency controllers, valves, float switches and level sensors — that is where the safety loops sit and what a certified controller is meant to do. Our software is the operator, monitoring and information layer that talks to the PLC via OPC UA, Modbus TCP, Profinet or MQTT. Setpoints, recipes and operation go through the PLC, not around it.
How does an OPC UA integration between PLC and SCADA or HMI work?
OPC UA is the modern industry-standard protocol for PLC communication and is built into virtually every new Siemens, Rockwell, Beckhoff or Schneider PLC. We build OPC UA clients into our layer that talk directly to the PLC or the SCADA server, with tag mapping, a watchdog for dropped connections and certificates for authentication and encryption. For legacy installations without UA, we build a gateway that abstracts Modbus TCP or Profinet, so the information layer only needs to know one protocol.
Do you replace Siemens WinCC or AVEVA System Platform?
For enterprise SCADA on a large installation: no. Those packages are mature and well documented, and the licensing and knowledge base at water boards and drinking water companies is broad. We mainly build the operator layer at the installation, the mobile layer for on-call staff, and the information and compliance layer on top of SCADA — that is typically where the real vendor lock-in and the heavy per-user licence costs sit.
Can operators and on-call staff operate the installation remotely?
For monitoring and alarm acknowledgement on a tablet or phone: standard. Push notifications for overflows, critically low levels, overpressure or a failed pump go straight to the on-call operator's device. For remote control of pumps or valves, we assess each case against your OT security policy and, where required, build role-based control with double confirmation, an audit log and a fallback to local control if the connection is lost.
What about the Dutch Drinking Water Act, BTO, HACCP and EHEDG?
For drinking water production and distribution, we build in audit logging, data quality checks and traceability from the first sprint, rather than bolting them on afterwards. We can automate BTO contributions (the sector's joint research programme) and reporting to ILT (the Dutch inspectorate) and the province, based on your existing dataset. For industrial process water with HACCP requirements, we provide CCP logging and quality registration. EHEDG applies to hardware and hygienic design, not software, but our choices around cleaning cycles and CIP recipes stay consistent with it.
What determines the cost of a custom project?
Mainly four things: how many different PLC brands and SCADA systems we need to integrate, how many installations or stations it covers, whether integration with CMMS, LIMS, GIS, ERP or energy monitoring is involved, and which compliance requirements apply. A local operator app for a single pumping station is a different project from a multi-site information layer with Drinking Water Act reporting. After the discovery sprint, we give you a substantiated estimate rather than an open-ended list price.
How long until we can go live?
A local operator app for a single station with a limited tag set can be up and running on a staging PLC or SCADA tap within a few sprints. A multi-site monitoring platform with a mobile on-call function and compliance reporting is a project spanning several sprints, phased by region or asset cluster. We always work with interim demos on real data, so you never see what has been built only at the end.

Talk to us about your water technology software.

A no-obligation introductory call of half an hour. We listen to your installation portfolio, your PLC and SCADA landscape and your on-call workflow, and give you direction you can actually use. This is often followed by a short walk-through at a station or treatment plant, because nothing tells you as much as the real working environment.

Edit content