US NPDES and SSO reporting
An overflow is one physical event, but the two regimes count it differently, and a report built for the wrong rulebook is not much use in a permit conversation.
Open Operations & reports ▸ Spill register (CSO events) and set Reporting under.
What actually differs
Section titled “What actually differs”| UK · EA / EDM | US · NPDES / CWA | |
|---|---|---|
| Counting | spills block-counted over 12-24 h | every activation is a discrete event |
| Headline | counted spills per year, banded by SOAF | events, volume and violations per outfall |
| Volume | m³ | gallons and MG |
| Cadence | annual return | monthly DMR, rolling into an annual summary |
| Identity | CSO structure and permit | NPDES permit no., permitted outfall no., permittee, receiving water |
The regime defaults from the model: a model in CFS, GPM or MGD is being built by someone who reports to a US regulator, so it opens on NPDES. You can switch it, and the choice is saved with the project.
The part that matters most: dry-weather overflows
Section titled “The part that matters most: dry-weather overflows”This is what the tool does that you cannot eyeball from a hydrograph. Each event is classified by cause, wet weather or dry weather, from the rainfall in the 24 hours before it started. Then:
- In a separate sanitary system, every overflow is an SSO, and every SSO is prohibited, wet or dry.
- In a combined system, a wet-weather activation is a permitted CSO. A dry-weather overflow is a violation under the fourth of the Nine Minimum Controls, which requires their elimination.
The summary therefore reports violations as a separate figure, which is the number a US regulator reads first.
Permit identity
Section titled “Permit identity”Per outfall, record the NPDES permit number, the permitted outfall number, the permittee or facility and the receiving water. Typed once, saved with the project, and reused by every report thereafter, so the identifying details on a DMR are not retyped each month.
The report
Section titled “The report”Regulator report (PDF) generates the document from the run: events per outfall worst first, volumes in gallons and MG, durations, monthly totals for the DMR cadence, and the violation count called out rather than buried.
Requires a Pro plan.
Related
Section titled “Related”- Water balance and the spill register
- Worked example: Oldham & Royton for the UK consent and river-class route