Every wastewater capital request eventually meets the same skeptical question from a finance director, a council member, or a rate commission: what happens if we do nothing. A maintenance team that has been running calendar-based PM can describe the risk in general terms, but describing a risk and pricing it are different exercises, and only one of them survives budget review. Building an avoided-cost case means turning sensor trends, failure predictions, and closed work orders into a running ledger that ties predictive maintenance directly to NPDES violation exposure and consent decree risk. Get Started to see how a CMMS turns maintenance history into evidence finance and engineering can both stand behind.
Can you show a rate commission what would have failed if you had done nothing?
Predictive maintenance only pays for itself on paper if every avoided failure is logged with a timestamp, a sensor reading, and a dollar figure before the failure happens — not reconstructed from memory after the budget hearing is scheduled.
Most utilities can describe a risk. Few can price it.
A predictive maintenance program generates value in two forms: failures that never happen, and failures that happen on a planned schedule instead of an emergency one. Both are easy to feel operationally and hard to defend financially, because the evidence has to exist before the counterfactual event, not after.
"This avoided cost is speculative."
The most common objection a rate case or capital request receives, and the correct response when a prediction was never logged with a timestamp before the asset was repaired.
"Show us the counterfactual."
Commission staff and council finance committees are trained to discount anecdotes. A sensor trend, a work order, and a completion date logged in sequence is not an anecdote.
"Why does this need to be capital, not operating?"
Sensor and CMMS spend often gets miscategorized as a soft operating cost instead of the risk-reduction capital investment it actually is, weakening the case before it is even filed.
Three pillars of a defensible avoided-cost figure
Asset criticality
What does this pump, blower, or clarifier drive mean downstream. A RAS pump failure that risks a permit violation carries a different weight than a redundant sump pump, and the case should reflect that weighting explicitly.
Failure probability
Vibration trend, amperage drift, or dissolved oxygen instability logged over weeks, not a single alarm event, is what gives a predicted failure date enough credibility to withstand cross-examination.
Cost consequence
Emergency parts markup, overtime labor, discharge violation exposure, and reputational cost all belong in the consequence figure, priced separately from the cost of the planned repair that replaced them.
What a running ledger entry actually looks like
Rather than a narrative summary written after the fact, an avoided-cost ledger is a chronological record: a prediction logged, a work order raised, a repair completed, and a dollar range attached to each stage.
| Date Logged | Asset & Signal | Predicted Failure Mode | Action Taken | Avoided Cost Basis |
|---|---|---|---|---|
| Day 0 | Influent pump 2 — rising vibration | Bearing failure within 10-14 days | Planned bearing replacement, next shift change | Emergency callout, overtime, and bypass pump rental avoided |
| Day 0 | Blower 1 — amperage drift +12% | Impeller fouling reducing DO transfer | Scheduled cleaning during low-flow window | Nitrification upset and potential permit exceedance avoided |
| Day 0 | RAS pump — DP trend and cycle shortening | Seal failure leading to dry-run trip | Seal kit replaced during planned outage | Unplanned SSO risk and full pump replacement avoided |
Each row in a CMMS-generated ledger carries its own audit trail — the sensor reading that triggered the alert, the technician who closed the work order, and the date each step occurred — which is what turns the ledger from a claim into evidence.
Where PdM ROI and NPDES risk actually meet
Civil penalties under the Clean Water Act are assessed per day, per violation, and inflation-adjusted annually, which means the exposure figure in a risk case should be current, not a number pulled from an old presentation.
Maximum per-violation administrative penalty under CWA Section 309(g), current federal figure
Maximum per-day-per-violation civil judicial penalty under CWA Section 309(d), current federal figure
A single undetected equipment failure can generate a violation that continues to accrue daily until corrected and reported
State-level penalty schedules and consent decree stipulated penalties are frequently set independently of the federal figures above and can be higher for utilities already under a decree — always confirm current numbers against your own permit and any active order.
From sensor alert to a filed exhibit: four stages
Instrument the critical few
Start with the pumps, blowers, and process assets whose failure carries the highest permit or public-health consequence, not the full asset list at once.
Log every prediction before the fix
A prediction only counts as evidence if it is timestamped before the corrective work order closes, not written up afterward.
Attach a defensible cost range
Use documented emergency repair costs from your own history, plus a conservative NPDES exposure range, rather than a single speculative figure.
Export the ledger as an exhibit
A CMMS report that finance, legal, and engineering all pull from the same underlying data closes the gap between operations testimony and the numbers in the filing.
Why most avoided-cost cases stall before they reach a hearing
- Avoided failures written up weeks or months after the repair
- No sensor trend attached, so the prediction date is unverifiable
- Cost figures estimated from memory rather than actual invoices
- Engineering, finance, and legal each maintain separate versions
- Case rebuilt from scratch for every new filing cycle
- Every prediction timestamped at the moment the threshold is crossed
- Sensor reading, work order, and completion date linked automatically
- Cost figures tied to logged parts, labor, and contractor invoices
- One running record shared across engineering, finance, and legal
- New filings pull the latest ledger instead of starting over
Start the ledger before you need it, not during discovery
Every prediction your maintenance team makes today is next year's avoided-cost evidence — if it is logged now.
PdM ROI and NPDES risk cases, answered
What actually counts as evidence of an avoided cost?
A prediction logged before the repair, tied to a specific sensor reading and asset, followed by a work order and completion record. A narrative written after the repair is testimony, not documentation.
How is this different from a general reliability KPI dashboard?
A reliability dashboard shows uptime and PM completion trends. An avoided-cost ledger is narrower and more specific: it links individual predictions to individual dollar figures for use in a financial or regulatory filing.
Do we need every asset instrumented before we can build a case?
No. Most utilities start with the handful of assets whose failure carries the highest NPDES or public-health consequence, then expand the ledger as more sensors come online.
Can a CMMS export this ledger directly for a rate case filing?
Yes, when predictions, work orders, and costs are all logged in the same system. Book a Demo to see a sample export format.
How current should the NPDES penalty figures in our case be?
Federal civil penalty maximums under the Clean Water Act are adjusted for inflation annually, so a case should always cite the current year's figures alongside any state-specific or consent decree penalty schedule that applies to your utility.
The next commission hearing will ask what you avoided. Have the ledger ready.
Turn sensor trends and work order history into a running avoided-cost record your finance, legal, and engineering teams can all stand behind.
