Water and wastewater facilities are expected to operate for decades, and they will inevitably face conditions that were not part of normal operation. Power gets lost. Communications fail. Equipment becomes inaccessible. Flooding and severe weather can disrupt even a well-designed facility.

The question in those situations is not just whether individual pieces of equipment still work. It is whether the facility can continue protecting the process, give operators the control they need, and ultimately return to normal operation. Those decisions are much easier to make during design than after it.

Resilience starts with understanding what could realistically go wrong, deciding how the facility should respond, and getting the right people involved while there is still time to influence the design.

Start with the Required Outcomes

Most project teams spend a great deal of time defining normal operation: design flows, equipment capacities, operating sequences, and performance requirements. Failure conditions do not always receive the same level of attention.

What needs to remain operational during a power loss? What can shut down safely? How long does backup power need to last? What does an operator still need to be able to control? And once the immediate problem is over, how does the facility get back to normal?

Those questions should come before the solution. When they are addressed early, the project team still has flexibility. Equipment selections, layouts, controls, and specifications can all be developed around the required operating philosophy. When they come up late, what sounds like a small change can ripple through the design. A new emergency operating requirement might affect electrical service, controls, equipment dimensions, structural supports, access, or available space. Defining the outcome first gives the team room to evaluate the best way to achieve it.

Look Beyond Individual Equipment

Resilience is a system-level issue. Having standby power, for example, does not necessarily mean every process should continue operating normally during an outage. Controls may remain available while a mechanical component cannot move. Equipment may be designed for emergency operation but become inaccessible during a flood. A system may handle the first few minutes of a failure exactly as intended but not have enough stored energy or capacity if the condition lasts longer.

That is why the entire sequence matters: What causes the failure? What happens next? What can operators still control? What needs to happen before the facility can return to normal operation?

Once those questions are answered, individual equipment requirements become much clearer. A pump may need backup power or a controlled shutdown. A control system may need local operating capability if communications are lost. A gate or valve may need to move to a predetermined position, remain where it is, or still be available for operation using stored energy.

There is no universal answer. The right response depends on the process and what happens if that process or equipment is unavailable.

Match the Solution to the Risk

Resilient design does not mean adding the most sophisticated backup system everywhere. It means understanding the risk and designing an appropriate response.

Some processes may justify redundancy because an interruption has significant consequences; others may not. Additional environmental protection can provide real life cycle value for equipment exposed to flooding but add little in a protected indoor installation. Stored energy may be important where equipment must operate after power is lost, while allowing equipment to remain in its last position may be perfectly acceptable somewhere else.

The point is not to design for every possible scenario. It is to identify the failures that are credible, understand what they mean for the facility, and decide intentionally how the system should respond. That also gives owners a better way to evaluate cost. Initial price still matters, but it can be considered alongside reliability, maintenance, downtime, recovery, and long-term performance.

Get the Right People Involved Early

Different members of the project team see different parts of the problem. Owners and operators know the process, emergency procedures, and what losing a system actually means at the facility. Engineers understand how systems interact and how operating requirements translate into design. Contractors bring practical knowledge about installation, access, constructability, and schedule. Equipment manufacturers and specialists understand the capabilities and limitations of the technologies being considered.

Collaborative delivery creates a good environment for those conversations, but the delivery method itself does not guarantee they will happen. Timing matters. Bringing equipment specialists into the conversation early should not be about steering the project toward a particular product. Their value is in helping the team understand technical constraints, compare approaches, and develop requirements around what the owner actually needs the system to do.

Make Resilience Part of the Design

Resilience is ultimately about what happens when normal operation is no longer available. Can the facility protect the process? Can operators still make the decisions and take the actions they need to? And can the system recover once the failure has passed?

Those questions deserve the same attention as normal operating conditions, and they need to be asked while the design is still flexible enough to do something with the answers.

When owners, operators, engineers, contractors, and equipment specialists work through those scenarios together early in the project, resilience becomes part of the design rather than something the team tries to add later.