PLC or Bespoke Controller: What Belongs in Your Water Treatment Control Panel
The Panel That Could Run A Car Factory
Open the control panel on almost any water treatment plant and look at what is doing the thinking. There is a fair chance you will find a controller with enough capability to run a bottling line, a paper mill or a section of a car assembly plant. It is wired to a couple of pumps, a few valves, a level probe and a dosing line.
It works. It works very well, which is why nobody asks the awkward question: how much did the plant pay for the capability it will never actually use?
That question sits underneath one of the more consequential decisions in water treatment plant automation, and it usually gets settled by habit rather than by engineering. It is worth slowing down and understanding the options.
First, What The Water Treatment Control Panel Actually Does
The water treatment control system is what turns a pile of equipment into a plant. On a typical site, it will:
Start, stop and alternate pumps, and drive variable speed drives to hold a setpoint
Sequence valves through filtration, backwash and clean-in-place cycles
Read level, flow, pressure, turbidity, pH and conductivity, and act on what it reads
Pace chemical dosing against actual flow rather than guesswork
Trip equipment before it damages itself
Keep a record of run hours, volumes and alarms that proves the plant did what it should
Process design sets the ceiling on plant performance. The control system decides how close you get to it. There are two routes to it. One is the conventional PLC control system. The other is a bespoke controller built for water treatment. Both are good engineering, but they are good at different things.
The PLC Arrives Knowing Nothing About Water
That sounds like a criticism. It is closer to a compliment, and it certainly hits the design brief.
A programmable logic controller (PLC) is a ruggedised industrial computer with one purpose: read inputs, solve logic, write outputs, thousands of times an hour, for twenty years, in a hot panel next to a motor starter. It is deliberately general. It will run a water treatment plant, a bakery oven or a gantry crane with equal enthusiasm, because everything specific to the job is added afterwards by whoever programs it.
It is also modular. A processor and power supply sit on a rail in the water treatment control panel, then I/O cards are added for float switches, contactors, 4-20 mA instruments and modulating valves, along with communications cards to reach drives, analysers and SCADA over Modbus, PROFIBUS or Ethernet/IP. Programming follows the international IEC 61131-3 standard, most often in ladder logic, which is drawn to resemble the relay wiring diagrams it replaced.
The result is a platform that anybody in the industry can pick up. In PLC water treatment applications, the hardware is certified, spares are global, and any competent integrator can open the logic and work out what is going on. On a municipal works, or on any site with an automation standard to match, that counts for more than anything else on this page.
The trade is that the plant buys the whole general-purpose capability and then pays an engineer to teach it about water. On every project. From the top.
The Bespoke Controller Turns Up Already Knowing the Job
A bespoke water treatment controller is hardware and firmware designed for one family of applications instead of all of them.
The I/O count, the input electronics, the communications and the control logic are chosen around what water treatment plants actually do. Flow-paced dosing, backwash sequencing, duty and standby rotation, sensor scaling and alarm handling are not rebuilt from scratch on each site. They are tested firmware, and they arrive with the box.
One caution, because the word bespoke makes some people nervous. A serious bespoke control system is a properly engineered product, with a defined I/O specification, industrial communications, electrical protection suited to a plant environment, documentation and version-controlled firmware. It is narrower than a PLC. Narrow is the feature.
The Comparison
Factor | PLC | Bespoke Controller |
Flexibility | High, and suits almost any process | Designed specifically for the application |
Initial development | Lower, because the platform already exists | Higher, because the platform must be developed |
Hardware cost per unit | Can be higher, particularly at small I/O counts | Usually lower for a purpose-built system |
Engineering per project | Repeated on every plant | Largely done once, then reused |
Scalability | Strong, by adding I/O modules | Depends on the design and its expansion path |
Fit to the process | General capability, configured for the plant | Capability matched to the plant from the outset |
Integration and data | Native drivers and broad protocol support | Open protocols such as Modbus TCP let SCADA and telemetry read it directly |
Maintenance | Widely understood, and serviceable by third parties | Supported by the developer, who knows the plant and the process |
Spares and obsolescence | Global supply, though subject to vendor phase-out and migration cycles | Controlled by the developer, who owns the roadmap |
Industry familiarity | Very high | Narrower, though the operator interface is built around the plant |
Water-treatment-specific features | Must be programmed or configured each time | Designed around them and delivered as standard |
The pattern in the table is really about when you pay. A PLC costs almost nothing to adopt and then charges engineering time on every project. A bespoke controller charges up front and asks for very little afterwards.
Whether that is a good trade depends on how many plants you intend to build.
Which One Belongs on Your Plant?
Reach for a PLC control system when:
The plant is large or complex, with high I/O counts and interacting process streams
A tender, consultant or client standard names the platform
The site's automation standard sets a tag structure or toolchain that must be matched
The process is unusual, or will keep changing
Third-party servicing anywhere in the country is contractual
A bespoke controller usually wins when:
Similar plants and skids get built repeatably
The I/O requirement is modest and well understood
A full PLC, HMI and the associated licences would cost a serious fraction of the plant itself
One set of treatment logic must behave identically across a fleet of sites
Most operations of any size run both, and we are no exception. What has changed is the balance. A great deal of industrial water treatment automation now happens on packaged plants and containerised skids, and those sit squarely in the second list.
Why Greenchain Group Built Its Own
Because we kept paying twice.
Our plants are, at the control level, usually variations on one theme: some pumps, some valves, a handful of instruments, a dosing regime and a sequence. On each one we were buying general-purpose hardware carrying capability the plant would never use, and then paying engineering time to rewrite dosing, backwash and pump logic we had already proven on the site down the road.
On a large municipal works, that is a reasonable price for flexibility. On a containerised
reuse skid, it is not.
Because of this, we built OneBoard, Greenchain's own water treatment controller:
8 digital inputs, 8 relay outputs and 4 analogue inputs switchable per channel between 4-20 mA and 0-10 V.
RS485 Modbus RTU for drives, meters and analysers.
Modbus TCP, so a site's SCADA or telemetry can interrogate it directly.
A touchscreen HMI built for operators rather than programmers, and an expansion module for sites that need more I/O or analogue outputs.
What that buys, in practice:
Water treatment functions ship as tested firmware, so there is less new code on each plant and fewer places for a commissioning error to hide
The control layer costs a sensible fraction of the plant instead of an alarming one
Every site behaves the same way, so an operator who knows one knows all of them, and an improvement made once lands everywhere
Open protocols keep the plant visible to whatever SCADA, telemetry or reporting the client already runs
We own the roadmap, so nothing goes obsolete on somebody else's schedule
We are equally clear about the other side of that decision. Building your own controller makes you the support route, so OneBoard runs on a standard 24 V DC supply with conventional terminals, and it is documented for the people who will maintain it. Where a client standard or the scale of a plant calls for a conventional PLC, that is what we design and install.
The Short Version
A PLC will do anything you ask of it, but needs to be told everything, every time. A bespoke controller does one job and arrives already knowing how to do it.
For very large plants and unusual processes, the PLC still wins. For the packaged plants, skids and mid-sized works that make up most of the market, a bespoke controller is becoming harder to argue against.
The right water treatment control system is the one that fits the plant it is bolted to, at a
price that fits what the plant is worth.
Ready to put the right solution in place?
Every plant has different control requirements. Book a meeting with Greenchain Group to discuss your application, operational needs and the capabilities your system requires. Our team can assess your application and help you identify the right approach for your operation.
FEATURED PROJECT
INDUSTRIAL WASTEWATER TREATMENT
Advanced Membrane Bioreactor (MBR) system for a macadamia processing facility in Nelspruit, South Africa, treating industrial wastewater and sewerage to support compliance, sustainability and future water reuse.
Comments