API 2000 is the standard that tells you how much venting capacity an atmospheric or low-pressure storage tank needs so it neither ruptures from overpressure nor collapses from vacuum. A tank breathes as its contents heat and cool and as liquid is pumped in and out, and it can be exposed to fire, and each of these events pushes vapor in or out at some rate. API 2000 is the method for adding up those rates and sizing the vents to handle them safely.
API 2000 (tank venting) in one line: API 2000 is the standard for sizing the normal and emergency venting on atmospheric and low-pressure storage tanks. It defines how to calculate the venting required for thermal breathing, liquid movement, and fire exposure, and it is the basis for specifying conservation vents, breather valves, and emergency relief devices.
Normal venting handles the everyday demands a tank sees in routine service, and API 2000 splits these into two contributions that are added together. The first is thermal breathing: as ambient conditions warm the vapor space, the vapor expands and must be let out, and as the tank cools, the vapor contracts and outside air must be let in to prevent a vacuum. A tank that could not breathe thermally would balloon on a hot afternoon and buckle inward on a cold night.
The second contribution is liquid movement. Pumping liquid into a tank displaces vapor that has to leave, an out-breathing demand, and pumping liquid out draws vapor or air in to fill the space, an in-breathing demand. The faster the maximum fill and withdrawal rates, the more venting capacity these movements require, so the pumping rates are a direct input to the sizing.
API 2000 provides the method to quantify each of these in consistent units and sum them into a total normal in-breathing and out-breathing requirement. That total is what a conservation vent or breather valve must be able to pass at the tank's set pressure and vacuum without exceeding the tank's design limits. Size the vent below that requirement and the tank is at risk during ordinary operation.
Beyond normal breathing, a tank must survive an emergency, and the governing case is usually external fire. When flames impinge on a tank, heat boils the liquid and generates vapor far faster than any normal breathing event, and if that vapor cannot escape quickly enough the tank can overpressure and fail catastrophically. API 2000 provides the method to estimate this fire-driven vapor generation, based on the tank's wetted surface area exposed to fire, and to size emergency relief accordingly.
Because the emergency rate dwarfs normal venting, it is handled by dedicated emergency relief devices, larger vents, or hatches designed to open under the emergency condition, rather than by the normal breather alone. The normal conservation vent conserves vapor day to day; the emergency device exists solely to save the tank in a fire or other extreme upset.
The standard also accounts for the fact that certain design features can reduce the fire venting requirement, and it lets the analysis credit them where they apply. The essential output is the same either way: a demonstrated emergency venting capacity, provided by suitable devices, sufficient to keep a fire-exposed tank from exceeding its pressure rating.
It is worth being clear about what API 2000 is and is not. It is the sizing method, the calculation that tells you how much venting capacity a tank requires for normal and emergency service. The physical devices that provide that capacity, the conservation vents, pressure-vacuum breather valves, and emergency relief hatches, are the hardware you specify to meet the number. API 2000 sets the requirement; the vent hardware fulfills it.
A tank vent system sized to API 2000 works silently most of the time, which is exactly why the conditions that stress it, high fill rates, rapid temperature swings, and abnormal pressure in the vapor space, are worth monitoring. Level and, where fitted, vapor-space pressure on a tank tell an operator when the tank is breathing hardest and whether it is staying within its safe pressure and vacuum band.
On a cloud SCADA platform like Merobix, those readings become remote assurance that the tanks are behaving as designed. Trending fill rate against the vent's rated capacity, or watching vapor-space pressure during a fast transfer, lets an operator confirm the venting is keeping up and catch a plugged or frozen vent before it puts the tank at risk. For remote lease and terminal tanks, that visibility complements the physical vents rather than replacing them, since the vents remain the safety device and the monitoring is the early warning.
Normal venting covers routine service, the thermal breathing from heating and cooling plus the vapor displaced by pumping liquid in and out, and it is handled by conservation vents or breather valves. Emergency venting covers extreme events, chiefly external fire, which generates vapor far faster and requires dedicated emergency relief devices. API 2000 gives the method to size both.
It bases the fire-driven venting requirement on the tank's wetted surface area exposed to fire, because that heat input determines how fast liquid boils and generates vapor. The larger the exposed wetted area, the more vapor is produced and the more emergency relief capacity is needed. The standard also lets certain design features reduce the requirement where they apply.
No. API 2000 is the sizing standard that calculates how much venting a tank needs, while a breather valve, or conservation vent, is one piece of hardware that provides some of that venting capacity. You use API 2000 to determine the required capacity, then specify vent hardware, breather valves and emergency relief devices, that meets it. The standard defines the requirement; the hardware satisfies it.
Primary references from the standards bodies and regulators that define this topic:
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.