Any oil and gas facility storing more than 1,320 gallons of oil above ground falls under the EPA's SPCC rule, and that same site almost always carries a separate stormwater permit obligation running in parallel, two regulatory programs that frequently get managed with two different inspection routines and two different paper trails. Secondary containment freeboard, oil-water separator performance, and retention pond capacity all shift with every storm event, yet most facilities still confirm compliance through a monthly walk-down and a clipboard rather than continuous measurement. The gap between those manual checks is exactly where a missed freeboard exceedance or a separator discharging above the oil and grease benchmark tends to surface, usually during an inspection rather than before one. AI software built around SPCC and stormwater requirements closes that gap by tracking containment capacity and discharge quality continuously instead of on a fixed schedule. Facilities can see how that maps to their own site by reaching out to iFactory support.
A Monthly Walk-Down Only Catches What's Wrong That Day. Storms Don't Wait for the Schedule.
iFactory's AI tracks secondary containment freeboard, separator performance, and stormwater discharge quality continuously across your site, flagging a developing compliance gap before the next storm event turns it into a reportable discharge.
Two Regulations, One Site, and Very Little Overlap in How They're Tracked
SPCC and stormwater compliance protect against the same basic outcome, oil reaching a waterway, but they're built as separate regulatory programs with separate documentation requirements, and most facilities end up managing them that way operationally too.
SPCC: Spill Prevention, Control, and Countermeasure
Governs bulk oil storage above 1,320 gallons above ground or 42,000 gallons underground, requiring secondary containment sized to the largest container plus precipitation freeboard, a facility diagram, and a written plan reviewed on a five-year engineering cycle.
Stormwater: Multi-Sector General Permit
Covers stormwater discharge quality leaving the site, requiring benchmark monitoring for oil and gas extraction facilities, visual inspections, and corrective action when a discharge exceeds a pollutant threshold.
How Secondary Containment Capacity Is Actually Calculated
The 110% rule sounds simple, but the number that matters shifts depending on how many containers share a containment area, and precipitation eats into that margin every time it rains before the containment is drained.
| Containment Scenario | Capacity Requirement | What Reduces Available Margin |
|---|---|---|
| Single Container | 110% of that container's full volume | Accumulated rainwater not yet drained from the containment area |
| Multiple Containers, Shared Area | 110% of the largest single container, or sufficient capacity for the group, whichever is greater | Sediment buildup reducing effective containment volume over time |
| Bulk Storage Freeboard | Sized to hold a 25-year, 24-hour storm event on top of full container volume | Undersized drainage that can't clear water fast enough between storms |
See Your Containment Margin Modeled Against Real Storm Data
iFactory can walk through how your site's containment capacity and separator performance would have tracked through last year's storm events.
Stormwater Benchmark Exceedances and What Happens Next
The EPA's Multi-Sector General Permit added benchmark monitoring specifically for oil and gas extraction facilities, and an exceedance doesn't just mean a bad sample, it triggers a tiered corrective action process called Additional Implementation Measures.
First Exceedance
Requires the facility to conduct an inspection to identify the cause of the exceedance and document corrective steps taken.
Repeat Exceedance
Escalates to a more detailed evaluation of control measures and may require physical changes to stormwater management infrastructure.
Continued Exceedance
The most serious tier, typically requiring engineering-level redesign of containment or treatment systems and closer regulatory scrutiny going forward.
Monthly Walk-Downs vs. Continuous AI Compliance Tracking
| Capability | Manual Monthly Walk-Down | AI-Driven Continuous Monitoring |
|---|---|---|
| Containment freeboard visibility | Confirmed once per scheduled inspection | Tracked continuously against live precipitation and tank level data |
| Separator performance | Sampled quarterly per permit schedule | Trended continuously, with drift toward the benchmark flagged early |
| Storm event response | Reactive, assessed after the storm has passed | Forecasted, with containment status checked ahead of predicted rainfall |
| Documentation for audits | Paper logs and periodic reports compiled manually | Continuous digital record available on demand for inspection |
What the AI Model Actually Tracks Across Your Site
Secondary Containment Capacity
Live tank level and containment volume data are reconciled continuously against the 110% requirement, factoring in accumulated rainwater that hasn't yet been drained.
Oil-Water Separator Trending
Effluent quality trends are tracked between scheduled sampling events, catching drift toward the oil and grease benchmark before a quarterly sample confirms it.
Storm-Event Freeboard Forecasting
Weather forecast data is layered against current containment and retention pond capacity to flag sites that need pre-storm attention before rainfall arrives.
Continuous Compliance Documentation
Every reading feeds a running digital record that stands in for manual log entries, ready to produce during an SPCC review or stormwater audit.
A Composite Scenario: The Separator Trend Caught Before the Sample
A mid-size upstream facility ran quarterly oil and grease sampling on its stormwater separator, consistent with its MSGP permit schedule, and had passed every sample for two years running. After connecting separator flow and turbidity data to a continuous monitoring model, the system flagged a gradual upward trend in effluent quality indicators roughly three weeks before the next scheduled sample, tracing back to sediment accumulation reducing the separator's effective retention time.
The facility scheduled a separator cleanout during a routine maintenance window instead of waiting for the quarterly sample to confirm a problem. When that sample was eventually taken, the reading came back at 4.1 mg/L, well under the 10 mg/L benchmark, instead of the exceedance the unaddressed trend would very likely have produced.
Rolling AI Compliance Monitoring Out Across a Facility
Map SPCC and Stormwater Assets Together
Tank farms, separators, and retention infrastructure are catalogued as one connected system rather than two separate compliance programs.
Connect Existing Level and Flow Instrumentation
Tank level sensors, separator flow meters, and available weather data feed the model directly without requiring a new instrumentation layer.
Validate Against a Real Storm Event
Predicted freeboard and separator trends are checked against actual performance during the next significant rainfall before the team relies on the model operationally.
Expand to Full-Site Continuous Documentation
Once validated, every tank, separator, and containment area across the site feeds a single continuous compliance record ready for audit.
Common Mistakes Facilities Make With SPCC and Stormwater Compliance
Managing SPCC and Stormwater as Unrelated Programs
Splitting oversight between separate teams means a containment issue and a discharge quality issue on the same tank farm can go unconnected until both show up independently.
Ignoring Accumulated Rainwater in Containment
Freeboard calculated once at design time doesn't account for water sitting in containment between drainage events, quietly eroding the available spill capacity.
Treating Quarterly Sampling as the Only Signal
A separator can drift toward a benchmark exceedance for weeks between scheduled samples, and a passing result today says nothing about next week's trend.
Reacting to Storms Instead of Preparing for Them
Assessing containment and drainage capacity only after a major storm has passed misses the window where a pre-storm drawdown could have prevented an exceedance entirely.
Frequently Asked Questions
What triggers an SPCC plan requirement for an oil and gas facility?
A facility needs a written SPCC plan once it stores more than 1,320 gallons of oil in aboveground containers, or more than 42,000 gallons underground, and operates in a way that could reasonably discharge oil into navigable waters. The plan must include a facility diagram, spill risk analysis, and engineered secondary containment sized to at least 110% of the largest container onsite. Facilities can review how their own tank configuration maps to these requirements by contacting iFactory support.
Is stormwater permitting a separate requirement from SPCC, or does one cover the other?
They are separate regulatory programs under different sections of the Clean Water Act. SPCC governs bulk oil storage and spill prevention, while stormwater permitting under the Multi-Sector General Permit governs the quality of water actually leaving the site during rain events. A facility with bulk oil storage typically needs both an SPCC plan and stormwater permit coverage, and the two are usually tracked with separate inspection and monitoring schedules even though they protect against the same basic risk.
What happens if a stormwater sample exceeds the oil and grease benchmark?
An exceedance triggers a tiered corrective action process known as Additional Implementation Measures, starting with a required inspection to identify the cause after the first exceedance. Repeat exceedances escalate to more significant control measure evaluations, and continued exceedances can require engineering-level redesign of treatment or containment systems. A discharge monitoring report showing oil and grease above roughly 10 mg/L commonly triggers a notice of violation within about 30 days.
Do we need to replace our existing tank level sensors and separator instrumentation to use this?
No, most facilities already have tank level sensors and separator flow instrumentation in place, and that existing data is what the predictive model uses as its primary input. Weather forecast data is layered on top to support storm-event freeboard forecasting, and new instrumentation is typically only added where a specific monitoring gap is identified. Book a demo to see how a rollout maps to your current instrumentation.
How often does an SPCC plan need to be reviewed once it's in place?
SPCC plans require a formal engineering review at least every five years to confirm the plan still reflects current site conditions and equipment. Beyond that formal review, many regulated sites also perform monthly tank integrity walks, and facilities frequently combine that inspection with fuel inventory reconciliation so the same visit covers both requirements. Continuous monitoring doesn't replace the five-year engineering review, but it does give a much clearer, ongoing picture of how the site is actually performing between those formal reviews.
Stop Confirming Compliance With a Clipboard Once a Month
iFactory tracks secondary containment capacity, separator performance, and stormwater discharge quality continuously, turning SPCC and stormwater compliance into a live operating picture instead of a scheduled walk-down.
