Spill containment is the set of physical barriers and systems designed to catch and hold leaks, drips, and spills before they reach soil, groundwater, or surface water. At oil and gas sites it is a required line of defense around tanks, vessels, and loading areas.
Spill Containment in one line: Spill containment, most often secondary containment, is a barrier, such as a bermed and lined area, dike, or basin, built around tanks and equipment to capture any liquid that escapes the primary vessel. It is sized to hold the volume of the largest container plus a margin for rain, giving operators time to recover the spill before it spreads to the environment.
Containment is layered. Primary containment is the vessel that normally holds the fluid, a tank, pipe, or drum. Secondary containment is the backup barrier around it that catches whatever the primary containment fails to hold. The classic example is a lined earthen berm or concrete dike surrounding a tank battery, forming a basin that would hold the oil, produced water, or chemicals if a tank leaked or ruptured.
Because a single containment area often surrounds several tanks, sizing rules are conservative. A common standard is that the containment must hold the volume of the largest single tank plus freeboard for precipitation, so that a full-tank failure plus a rain event does not overtop the barrier. Liners of clay or synthetic membrane prevent the caught fluid from soaking into the ground.
Secondary containment appears wherever a significant liquid inventory is stored or transferred: tank batteries, chemical totes and drums, truck loading and unloading areas, and around pumps and manifolds prone to leaks. Smaller forms include drip pans, spill pallets under drums, and curbing around equipment. The goal everywhere is to turn an uncontrolled release into a captured, recoverable one.
Rainwater is the operational complication. Containment basins collect precipitation that must be drained, but only after it is inspected to confirm it is not contaminated with oil. Manual or valved drains, sometimes with a normally-closed valve and an operator check, are used so clean rainwater can be released while any oily water is retained for proper disposal.
In the United States, spill containment for oil is driven largely by the Spill Prevention, Control, and Countermeasure (SPCC) rule under 40 CFR Part 112, which applies to facilities that store oil above threshold quantities and could discharge to navigable waters. SPCC requires a written plan, appropriate secondary containment, inspections, and specific sizing and integrity provisions. State agencies add their own tank and containment requirements.
Beyond formal secondary containment, the SPCC framework also recognizes general site drainage control and countermeasures, so that even areas without a full berm have a plan to contain and clean up a release. The overarching principle is prevention plus preparedness: build barriers that catch spills, and have the plan and equipment ready to recover them quickly.
A common requirement is that containment hold the volume of the largest single tank within it, plus freeboard to account for rainfall so a full-tank failure during a storm does not overtop the barrier. Exact sizing follows the applicable rule, such as SPCC, and state tank regulations.
Because the same barrier that catches spills also collects precipitation, which must be removed to preserve capacity. It can only be drained after inspection confirms it is not contaminated with oil; oily water must be retained and disposed of properly, so drains are typically kept closed and released only after a check.
Yes. Where containment areas have level sensors or leak detection, those signals can be brought into a cloud SCADA platform like Merobix over Modbus or MQTT, so rising liquid in a containment basin or a leak-detection alarm reaches operators quickly, complementing the physical inspections that regulations require.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.