Exercise set
Water and Wastewater Pump Station Reliability, Standby, Monitoring, and Release Exercises
Solved pump-station reliability exercises for standby availability, common support, runtime balance, leakage trends, alarms and release evidence.
These exercises practise pump-station reliability decisions for water and wastewater systems: series availability, standby pumps, common support, runtime balance, seal leakage trends, alarm response, checklist closure, proof tests, maintenance backlog and release gates.
The goal is to prove that the station can keep service when components fail or conditions drift. Hydraulic duty may pass while reliability fails because standby logic, alarms, common power, maintenance evidence or surge-control tests are incomplete.
Assume simplified reliability screens unless stated otherwise. Field release should use operating logs, runtime records, alarm history, maintenance work orders, generator tests, wet-well trends, pump alternation evidence and post-maintenance validation records.
How to use these exercises
Use the set as a pump-station reliability release review. Exercises 1 to 6 test availability, standby logic, common support, generator tests and standby-start success. Exercises 7 to 11 use monitoring trends to catch unequal wear, leakage growth and delayed alarm response. Exercises 12 to 17 connect maintenance backlog, temporary controls, proof-test coverage, checklist closure and residual risk. Exercise 18 then applies the hard release gate.
Keep the required service function visible: normal duty, peak wet-weather flow, overflow prevention, permit compliance, dewatering or treatment continuity. A station can meet hydraulic duty in a short test and still fail release if the standby path, alarm response, common controller or proof-test evidence is weak.
Release Evidence Notes
Reliability evidence should state the required function, outage consequence, operating mode, redundant equipment, common support systems and failure definition.
Standby evidence should include pump availability, controls, power, suction conditions, automatic alternation, starts, check valves and successful demand tests.
Monitoring evidence should include leak trends, vibration, motor current, runtime balance, alarm delay, wet-well levels and response records.
Release evidence should close hydraulic, electrical, control, surge, maintenance and operator handover gates.
The evidence package should identify common-cause exposures explicitly: shared power, shared controls, common suction blockage, common discharge valve, shared wet-well instrumentation, flood exposure, generator fuel, telemetry loss and operator response. Redundant pumps are not redundant service if one unresolved support failure can disable both units.
Engineering Boundary Notes
This page covers reliability, standby and release evidence. Pump power, NPSH and VFD limits belong in the pump-duty exercise set. Pipe headloss, valves and surge pressure belong in the pipe/transient exercise set.
Real release decisions also need site-specific duty curves, wet-well storage, inflow hydrographs, emergency storage, overflow consequence, electrical coordination, generator load tests, check-valve behavior, air entrainment, debris, confined-space access, telemetry, maintenance access and documented operating procedures. Use these exercises to locate reliability evidence gaps before calling a station available.
Common Release Mistakes
Common mistakes include claiming redundancy while sharing one vulnerable controller, ignoring failed standby starts, accepting runtime imbalance as normal, planning maintenance only after alarm threshold, treating alarm acknowledgement delay as a minor operations issue, closing release with missing proof-test cases, and accepting hydraulic performance while reliability gates fail.
Other failures include proving duty flow with the lead pump only, omitting generator fuel or automatic transfer evidence, treating historical availability as current after maintenance changes, accepting alarm acknowledgement without response completion, and releasing a station when maintenance backlog has no owner or due date.
Scenario Map
| Scenario | Exercises | Primary check | Engineering decision |
|---|---|---|---|
| Availability and standby | 1-6 | series availability, parallel standby and common support | Decide whether redundancy is credible. |
| Monitoring trends | 7-11 | runtime balance, leakage, alarm delay and current drift | Trigger maintenance or controls review. |
| Evidence closure | 12-16 | proof tests, checklist completion and backlog risk | Hold or release station. |
| Reliability release | 17-18 | hard gates and residual risk | Release, restrict or retest. |
Exercise 1: Series Availability
A pumping function requires pump availability:
and power supply availability:
in series. Find function availability.
Solution
Series availability:
So:
Engineering Comment
The common power supply lowers total availability even when the pump itself is good.
Plausibility Check
The result must be lower than either series component.
Exercise 2: Parallel Standby Pump Availability
Two pumps each have availability:
At least one is required. Assume independent failures. Find availability.
Solution
Both fail:
Availability:
Engineering Comment
Independence is a strong assumption. Shared suction blockage, common controls or power failure can reduce benefit.
Plausibility Check
Standby availability should be much higher than one pump alone.
Exercise 3: Standby with Common Controller
Standby pump-pair availability is:
Controller availability is:
Find station availability.
Solution
Controller is in series:
Engineering Comment
The controller caps availability. Redundant pumps do not protect against a common control failure.
Plausibility Check
The result is close to controller availability because pump-pair availability is near one.
Exercise 4: Generator Test Availability
Generator monthly test success is:
successes out of:
tests. Find pass rate.
Solution
Pass rate:
Engineering Comment
Backup power reliability should be investigated if tests fail, especially for overflow-sensitive stations.
Plausibility Check
One miss in twelve is about eight percent failed.
Exercise 5: Standby Start Success
Standby pump starts successfully:
times out of:
demands. Find demand success rate.
Solution
Success rate:
Engineering Comment
Demand tests should distinguish electrical start failure, valve failure, air binding and control logic failure.
Plausibility Check
Three failed starts in fifty gives six percent failure.
Exercise 6: Standby Release Gate
Required standby start success is:
Measured success is:
Check gate.
Solution
Since:
the standby start gate fails.
Engineering Comment
The station should not claim high standby reliability until start failures are corrected and retested.
Plausibility Check
Measured performance is four percentage points below the requirement.
Exercise 7: Runtime Balance
Pump A runtime is:
Pump B runtime is:
Find imbalance relative to average.
Solution
Average:
Difference:
Relative imbalance:
Engineering Comment
Runtime imbalance can indicate alternation logic, availability differences or manual override.
Plausibility Check
Two hundred hours out of about one thousand is near twenty percent.
Exercise 8: Runtime Balance Gate
Runtime imbalance is:
The rule allows at most:
Check gate.
Solution
Since:
the runtime-balance gate fails.
Engineering Comment
Alternation should be reviewed before one pump accumulates disproportionate wear.
Plausibility Check
The measured imbalance is almost double the limit.
Exercise 9: Seal Leakage Trend
Seal leakage increases from:
to:
over 60 days. Find rate.
Solution
Rate:
Engineering Comment
Leakage trend is useful maintenance evidence when tied to seal type, solids load and operating hours.
Plausibility Check
A 0.12 increase over sixty days gives 0.002 per day.
Exercise 10: Days to Leakage Alarm
Current leakage is:
Alarm threshold is:
Trend is:
Find days to alarm.
Solution
Remaining increase:
Time:
Engineering Comment
Maintenance should be planned before the alarm if the station is critical.
Plausibility Check
The remaining increase is slightly less than the previous sixty-day increase, so about fifty days is reasonable.
Exercise 11: Alarm Response Delay
High-level alarm occurred at:
operator acknowledgement occurred at:
The response rule is at most 10 minutes. Check.
Solution
Delay:
Since:
the alarm response gate fails.
Engineering Comment
Alarm delay can turn a pump fault into an overflow or permit event.
Plausibility Check
The acknowledgement came fourteen minutes after the alarm.
Exercise 12: Maintenance Backlog Risk
A deferred pump repair has:
Compute risk priority.
Solution
Priority:
Engineering Comment
Backlog risk should have an owner, due date and temporary control.
Plausibility Check
The product of the three integer scores is under one hundred.
Exercise 13: Temporary Control Reduction
A temporary inspection reduces likelihood from:
to:
while C=8 and D=3. Find new priority.
Solution
New priority:
Engineering Comment
The control halves the score, but it does not eliminate high consequence.
Plausibility Check
Only likelihood halves, so the score halves.
Exercise 14: Proof-Test Coverage
A pump-station interlock has:
required proof-test cases. Completed cases:
Find coverage.
Solution
Coverage:
Engineering Comment
Interlock proof tests should map to actual failure modes and response actions.
Plausibility Check
Two missing out of eighteen is about eleven percent missing.
Exercise 15: Proof-Test Gate
Coverage is:
Requirement is:
Check release.
Solution
Since:
the gate fails.
Engineering Comment
Latent interlock gaps should block release until tested or justified.
Plausibility Check
The coverage is more than six percentage points below the threshold.
Exercise 16: Checklist Closure
A station release checklist has:
required records. Accepted records:
All records are required. Check.
Solution
Closure:
The package fails because one required record is missing.
Engineering Comment
Missing surge, control or standby evidence can be a release blocker.
Plausibility Check
One missing record gives high percentage completion but not full closure.
Exercise 17: Residual Reliability Score
A station residual risk score is:
The release rule requires:
Check gate.
Solution
Since:
the residual risk gate fails.
Engineering Comment
Risk reduction should target the dominant failure modes, not only documentation closure.
Plausibility Check
The score is above the release threshold.
Exercise 18: Pump Station Reliability Release Gate
A station reliability package has:
| Gate | Requirement | Current result |
|---|---|---|
| standby start success | at least 98\% | 94\% |
| runtime imbalance | at most 10\% | 18.5\% |
| proof-test coverage | at least 95\% | 88.9\% |
| checklist closure | 100\% | 90.9\% |
Decide whether to release.
Solution
All four gates fail:
The reliability package is not releasable.
Engineering Comment
Hydraulic performance cannot compensate for failed standby, monitoring and proof-test evidence.
Plausibility Check
Multiple hard gates fail, so release must be held or restricted.
Validation Package Checklist
A strong pump-station reliability solution should check:
- whether required function and outage consequence are explicit;
- whether standby availability includes common power and control systems;
- whether standby starts and generator tests are successful enough for release;
- whether runtime balance supports equal wear and alternation logic;
- whether leakage, current, vibration and alarm trends are reviewed;
- whether maintenance backlog risk has owner and due date;
- whether interlock proof tests and release records are complete.
- whether generator, telemetry, transfer switch and operator response evidence match the same operating mode;
- whether surge, wet-well level and overflow consequence are considered before release;
- whether temporary controls have expiry, owner and retest requirements;
- whether the final decision is release, restricted operation, standby retest, maintenance hold or derated service.
The final acceptance question is whether the station can keep the required service after the first credible equipment or support failure. If the answer relies on an untested standby start, shared controller, delayed alarm response or undocumented maintenance action, the station is not release-ready.