INFRASTRUCTURE RESILIENCE
Building Resilient Water Infrastructure for an Uncertain Future
Water systems are expected to run every hour of every day. Storms, power loss, aging equipment, staff turnover and cyber threats challenge that expectation. Resilience is how a system responds on its hardest day.
Resilience is not a single upgrade
No one product makes a plant or lift station resilient. Resilience comes from coordinated layers of power, local control, communications, recovery resources and trained people. Each layer should reduce the consequences when another becomes unavailable.
Start with a practical question: if this part of the system fails, what happens next? The answer should guide the design, documentation and testing.
Start with power
Every control system depends on power. Ask what happens when the utility feed drops: does the station ride through, restart cleanly, or require operator intervention? Generator transfer, UPS-backed controls and restart logic all need to match the process. A station that returns in the wrong state can create a second problem after the outage.
Check: Document the expected sequence for power loss, transfer and restoration, then verify it under an approved test plan.
Keep local control working
Design essential station control to operate without a remote server or SCADA connection. Pump alternation, backup level inputs and local alarm logic should be evaluated at the controller level. Loss of supervisory communications should not remove the local functions needed to operate safely.
Check: Define which functions continue locally and how operators recognize a communications failure.
Plan for a device failure
A resilient control design assumes a sensor or controller component may fail. Redundant level sensing, hard-wired backups and manual modes can provide additional layers when their independence and failure behavior are considered. A second sensor alone does not guarantee that a bad reading will be detected.
Check: Review sensor disagreement, backup operation and manual control while preserving required protective functions.
Give communications a backup plan
Radio, cellular and fiber links can all become unavailable. Consider more than one alarm path where the application warrants it, and examine whether those paths share power or infrastructure. Keep local control working while the link is out, and make loss of communication clear to operators.
Check: Identify who receives a lost-site alarm and what action follows.
Treat cybersecurity as another layer
Segmented networks, firewalls, controlled vendor access and tested backups each contribute to protection. Give vendors access only when needed, through a segregated path and for the authorized session. Design each layer with the assumption that another may fail.
Check: Review remote access arrangements and confirm that recovery copies are available when normal systems are unavailable.
Keep system knowledge available
Maintain current drawings, controller and HMI program backups, and network diagrams. Keep protected copies off-site and update them as systems change. Clear panel, wire and device labels help the next person troubleshoot. When experienced staff leave, the knowledge should stay with the utility.
Check: Confirm that another qualified team member can locate and understand the latest documentation.
Keep spares and test recovery
A spare is useful only if it works and fits the application. Identify critical controllers, power supplies, communication modules and HMI components, then choose spares based on operational risk and replacement lead time. Track obsolete parts and their replacement paths. Test backups and restores before an emergency.
Check: Verify that spare hardware, firmware, software and saved configurations support the planned recovery.
Modernize in stages
Replacing everything at once is rarely practical. Start with the highest-risk equipment and single points of failure. Standardize on platforms the team can support, and plan each stage to fit the next one. Temporary arrangements during an upgrade deserve the same attention as the final system.
Check: Connect each proposed upgrade to a specific failure scenario and a practical implementation sequence.
Train the people
Operators need clear procedures for abnormal conditions and manual operation. Practice outage response and recovery through planned drills suited to the site. Technology supports the response, but people must understand what the system is doing and when to intervene.
Check: Walk through responsibilities, escalation contacts and the return to normal operation.
How can BEA help?
BEA designs and supports PLC and SCADA controls for water and wastewater systems. We assess existing lift stations and plants for single points of failure, help utilities plan staged upgrades around real budgets, and document systems so the team can maintain them with confidence.
If you want a second set of eyes on your system, give us a call. Start with one station or one failure scenario, then build a practical improvement plan.