AMP8 automation: what £104bn of water investment means for PLC, SCADA and telemetry

AMP8 automation is the control-systems share of the water industry's 2025 to 2030 investment cycle: new PLCs and SCADA at treatment works, replacement telemetry at pumping stations and overflows, and the instrumentation that proves performance to regulators. Ofwat approved £104 billion of spending for April 2025 to March 2030, 77% more than AMP7, according to Causeway's AMP8 summary. A large slice of that money passes through a control panel somewhere.

If you run controls for a water company or a tier-one contractor, the question is not whether the work is coming. It is whether you have the engineering hours, standards and test discipline to deliver it without tying up your own team for five years.

Where the AMP8 automation scope comes from

Most AMP8 control work traces back to three drivers. Each one creates a different kind of package, so it helps to recognise them early.

• Storm overflows and environmental performance. Causeway lists a target to cut storm overflow spills by 45% by 2030 and £12 billion for overflow infrastructure. Storage tanks, screens and pumping upgrades all need new control logic, interlocks and telemetry.
• Pollution incidents. The Environment Agency's environmental performance report for 2024 recorded 2,801 pollution incidents, up 29% on 2023, with 693 at pumping stations. Better alarms, standby logic and remote monitoring are a direct response.
• Monitoring and reporting. Since 1 January 2025 companies must publish storm overflow starts and stops within an hour, under the storm overflows policy and guidance. That puts data quality from the outstation to the website in scope.

What a typical AMP8 control package looks like

On a wastewater treatment works upgrade, the control package usually includes a new or extended PLC, a SCADA or HMI update, MCC interfaces, instrument integration and telemetry back to the regional control centre. On a network scheme it may be a single pumping station panel and outstation. The engineering effort is less about the size of the asset and more about how many interfaces you have to prove.

The skills problem behind AMP8 automation

Causeway's piece is blunt about it: skills will be the biggest challenge of AMP8, with around 100,000 new workers needed to deliver the programme and replace retirements. Controls engineering is one of the tightest corners of that gap, because water companies each have their own engineering standards, preferred PLC platforms and SCADA conventions, and new engineers take time to learn them.

Water companies now expect integrated, digital-ready supply chains.

In practice that means contractors are being asked for consistent tag naming, clean I/O schedules, test records that can be audited and software that matches the client's templates first time. Those are documentation and discipline problems as much as programming problems.

How to plan AMP8 control work so it does not stall

1. Lock the standard early. Get the water company's current engineering standard, PLC template and SCADA style guide before design starts. Old revisions cause more rework than any other single issue.
2. Write the functional design specification first. Agree duty, standby, alarm and failure behaviour on paper before anyone opens a programming tool.
3. Test against a simulated plant. Run the PLC and SCADA against a process simulation so factory acceptance testing finds the logic faults, not the commissioning team on a wet night.
4. Plan the telemetry cutover. Decide how old and new outstations will run in parallel and how the control centre will see both during changeover.
5. Hand over documents the operator will use. As-built I/O lists, cause-and-effect tables and alarm lists are what keep the site running in year three.

Mistakes we see on AMP8 control packages

Most delays on water control packages are avoidable. They come from assumptions that nobody wrote down, rather than from difficult engineering. These are the ones that cost the most time:

• Programming against an I/O list that changes weekly because the mechanical design is still moving.
• Treating telemetry as an afterthought, so the outstation point list is written on site.
• Copying logic from a sister site without checking that the process, instruments or MCC are the same.
• Leaving alarm priorities to the programmer, which produces a SCADA that alarms on everything.
• No agreed test record format, so FAT evidence has to be rewritten for the client's audit.

None of these need new technology. They need a short design stage with sign-off, and a team that has done water work before and knows what the client's assessor will ask for.

Where outside engineering capacity fits

Many contractors keep site leadership, commissioning and client relationships in house and buy in PLC, SCADA and documentation work as fixed packages. That is the model we use in the UK: a Milton Keynes contact and engineering from our India centre. Commissioning is carried out by your team or a local partner, with our engineers joining remotely.

If telemetry is a big part of your AMP8 scope, read our guide to telemetry outstation replacement before the PSTN switch-off. For overflow monitoring, see event duration monitoring explained.

Next step

Send us the I/O schedule or functional spec for one AMP8 package and we will return a written scope, programme and price. Our water and wastewater controls service covers PLC, SCADA and telemetry, and the UK market briefing explains how we work. Or go straight to contact.