Pumps, Energy & Controls

A water system is far more than pipes. Between the source and the outlet sits a set of working components, and understanding them is what turns "reuse the greywater" into a system that actually functions. Pumps are the heart: they move water against gravity and friction - lifting it to a storage tank on the roof, pushing it through treatment, delivering pressure to taps and irrigation. Tanks store water so that supply and demand need not match minute to minute - a rainwater cistern holding the monsoon for the dry months, a treated-greywater tank buffering flush demand, a header tank giving gravity pressure. Valves direct and control flow: isolating parts of the system for maintenance, switching between sources (reuse water when available, mains as backup), preventing backflow, and releasing or diverting water (a first-flush diverter throwing away the dirty first rain). Sensors measure what is happening - water level in a tank, flow rate, pressure, and increasingly quality indicators like turbidity - so the system can respond. And controls tie it together: the logic that decides when a pump runs, when a valve opens, when to draw from reuse versus mains, and when to raise an alarm.

Each of these is a real object that takes space, costs money, can fail, and - crucially - needs maintenance and, for the powered ones, energy. A rooftop tank needs structure to carry its weight. A pump needs power, a place, and eventual replacement. Sensors drift and need calibration. Controls need setting up and can misbehave. The elegance of a water diagram hides all of this; the discipline of a good design faces it. In particular, a system with many powered, complex, failure-prone components is not automatically better than a simpler one - it is more to buy, more to run, more to break and more to look after, which matters enormously for the maintenance discipline of the next lesson.

For the designer, the practical consequences are spatial and strategic. Tanks, pump rooms, plant space and service access have to be planned into the building, not squeezed in later. The choice of how many tanks, how much storage, how many pumps and how complex the controls is a design decision with lifelong energy and maintenance consequences. And the guiding instinct should be toward simplicity and robustness: the fewest moving parts that will do the job reliably, sized correctly, with the binding hydraulic and equipment decisions made by the water and services engineers under the codes. A water system you can understand and maintain beats a clever one you cannot.

Water is heavy - a cubic metre weighs a tonne - and moving it, especially lifting it and forcing it through fine filters or membranes, takes real energy. This is the crux of the water-energy nexus: water systems consume energy, and energy systems consume water, and the two cannot be optimised in isolation. In a regenerative water system, the energy shows up in three main places. Pumping: every metre of lift and every unit of pressure costs power, and a system that pumps water up, through treatment, back down and out again may pump the same water several times. Treatment: cleaning water to a usable standard can be energy-cheap (a constructed wetland, sedimentation, slow natural processes) or energy-expensive (membrane bioreactors, ultraviolet disinfection, and especially reverse osmosis, which forces water through a membrane at high pressure). Aeration and process loads: many biological treatment systems must be aerated, and blowers run continuously.

The honest and uncomfortable implication is that an on-site water system can be a net loss in carbon terms even while it saves water. A greywater recycling plant that relies on heavy pumping and energy-intensive treatment might consume more energy - and cause more emissions - than simply drawing more water from an efficient mains supply would have. "We recycle our water" is not automatically green; it depends entirely on how much energy the recycling costs. This is why the course insists on counting the energy, not just the water, and why demand reduction (Module 7) remains the first move: water you never use needs no pumping and no treatment, so it is free of both the water cost and the energy cost. Reuse should serve the demand that genuinely remains, and it should be designed to do so on as little energy as possible.

India sharpens this. Much electricity is still carbon-intensive, water pumping is already a large share of some regions' power use (groundwater irrigation especially), and power supply can be unreliable - so an energy-hungry water system may be both high-carbon and prone to failing when the power does. All the more reason to favour low-energy approaches. The binding energy and carbon accounting, like the hydraulics, should be done properly - modelled and verified, not assumed - but the design instinct is clear: treat every pump and every energy-intensive treatment step as a cost to be minimised, and reach for the lowest-energy way of achieving the needed water quality and delivery.

If energy is the hidden cost, then the design goal is to need as little of it as possible while still delivering water safely and reliably. The first and best move is gravity. Water falls for free, so a system arranged to let water flow downhill under its own weight - collecting rain high, storing it in an elevated tank, letting it feed outlets and irrigation by gravity - can move water with little or no pumping. The classic header-tank arrangement, where water is pumped up once (or arrives high naturally) and then gravity-fed to everything below, minimises pumping. Landscapes can be graded so that captured stormwater and treated water flow to where they are needed without power. Gravity is the lowest rung of the energy ladder, and a design that exploits site levels and building height can lean on it heavily.

Where pumping is unavoidable, make it efficient: correctly sized pumps (an oversized pump wastes energy continuously), variable-speed drives that match pumping to actual demand rather than running flat out, minimal lift and pressure, smooth pipe runs that reduce friction losses, and pumps chosen for efficiency at their real operating point. For treatment, prefer the lowest-energy process that reaches the required quality - natural and biological systems (constructed wetlands, reed beds) over energy-intensive membranes and reverse osmosis wherever the water quality target allows, reserving the heavy processes for where they are genuinely necessary. And consider powering what pumping remains with on-site renewable energy - solar pumping, for instance - so that the energy cost of water carries a lower carbon burden, though renewables do not excuse an inefficient system.

Controls contribute too. Smart, simple controls can cut energy by pumping when demand or tariffs are favourable, avoiding unnecessary cycling, and shutting things down when not needed - though complexity is a trade-off, since every added control is another thing to set up, maintain and troubleshoot. The overarching principle mirrors the whole course: reduce, then be efficient, then supply. Reduce the demand (less water to move and treat), design to move what remains by gravity as far as possible, make any pumping and treatment as efficient and low-energy as the quality target allows, and only then reach for powered complexity. The binding pump selection, hydraulic design and energy modelling belong to the water and services engineers under the codes - but the low-energy, gravity-first strategy is the designer's to set.

Controls are the nervous system of a water system - the sensors, logic and actuators that decide when to pump, which source to draw from, when to switch to mains backup, and when something is wrong. Done well, controls make a system efficient and safe: they draw reuse water when it is available and clean, fall back to mains when it is not, run pumps only when needed, detect leaks and faults early, and alert an operator before a small problem becomes a big one. Done badly, they become a source of failure themselves - a stuck sensor, a mis-set threshold, a controller that keeps a pump running dry or a valve open when it should be shut. Because controls sit at the point where the system makes decisions, they carry a special responsibility: they must fail safe.

The fail-safe principle means designing the control logic so that when something goes wrong - a sensor fails, power is lost, water quality drifts, a component breaks - the system moves to its safest state, not its most dangerous one. For a reuse system, the safest state is usually to stop supplying non-potable water and fall back to the mains (potable) supply, and to raise an alarm, rather than to keep pushing possibly-substandard reuse water into use. A control system should never be arranged so that a failure results in untreated or unverified water reaching an outlet, or in a cross-connection scenario. If in doubt, shut the reuse valve. This is the health discipline expressed in logic: safety is not traded for continuity of supply.

Controls also serve the monitoring and maintenance that the next lesson is about. Sensors that log water levels, flows, pressures and quality indicators give the operator the information needed to run the system, spot deterioration, and prove it is working - and alarms turn a silent, creeping failure into a noticed one. But controls are only as good as their upkeep: sensors drift and need calibration, thresholds need reviewing, and a control system nobody understands or maintains will eventually mislead. So the same instinct applies here as everywhere in this module - prefer controls that are as simple as the job allows, that fail safe, that are documented and understandable, and that a real operator can actually look after. The detailed control design, the safety interlocks and the water-quality thresholds are set by the engineers under the codes; the designer's contribution is to insist that the system fails toward safety, that it is monitored, and that it stays simple enough to be maintained.