What Is API 650?

Field-Erected Tanks and Shell-Course Design

The tanks API 650 covers are field-erected, meaning they are too large to fabricate elsewhere and are instead built on their foundation from steel plates welded together on site. This is the defining characteristic that separates API 650 tanks from small shop-built tanks: the scale of a field-erected tank drives everything about how it is designed and constructed, from the way plates are joined to the way the finished tank is tested before it goes into service. A production tank battery's largest vessels and a terminal's bulk storage are typical API 650 tanks.

The shell of such a tank - its cylindrical wall - is built from horizontal rings called courses, and API 650's shell design reflects a simple physical fact: the liquid pressure on the wall is greatest at the bottom and decreases with height. The standard therefore allows the shell to be thickest in the lowest course, where it bears the most pressure, and progressively thinner in the courses above, where the liquid head is less. This tapering is why a tall storage tank's wall is not a uniform thickness but a stack of courses sized for the pressure each one carries.

Designing the shell is fundamentally about ensuring each course can safely resist the hoop stress the liquid imposes at that elevation, with appropriate margin. The standard provides the methods for determining the required plate thickness at each course from the tank's diameter, the height of liquid above that course, and the density of the stored product. The result is a wall engineered to hold the liquid load efficiently - strong where the pressure is high and no heavier than it needs to be higher up.

Bottoms, Roofs, and Low Design Pressure

Beyond the shell, API 650 addresses the tank bottom and the roof, each of which has its own design considerations. The bottom is the plate floor the tank sits on, welded together and resting on a prepared foundation; its design has to keep the stored liquid contained and manage the way the tank settles and drains. The roof is where API 650 offers real variety, because different service needs call for different roof types. A fixed roof is a permanent top over the tank, while a floating roof rides on the liquid surface and rises and falls with the level, an arrangement used to reduce vapor space and the evaporation losses and emissions that come with it.

The choice between roof types is not cosmetic; it is driven by what the tank stores and by emissions considerations. A floating roof, whether an external floating roof open at the top or an internal floating roof beneath a fixed roof, minimizes the vapor space above a volatile product, which reduces both product loss and vapor emissions. A fixed roof is simpler and suits products where vapor space is less of a concern. API 650 accommodates these configurations because a storage tank's roof has to match its service rather than being one-size-fits-all.

A crucial characteristic running through API 650 is that these are atmospheric, low-pressure tanks. They are designed for internal pressures very close to atmospheric, not for the substantial pressures a pressure vessel handles. This is fundamental to understanding what an API 650 tank is and is not: it is built to hold a liquid at essentially ambient pressure, with its venting arranged to keep internal pressure and vacuum within the small range the design allows. Exceeding that range - by overpressuring or by pulling a vacuum as liquid is drawn out - is dangerous precisely because the tank is not built to be a pressure vessel, which is why proper venting is integral to the design.

Where API 650 Sits Among the Tank Standards, and the SCADA Picture

API 650 is the new-construction standard for large field-erected welded tanks, and understanding it is easier by contrast with its neighbors. It governs how such a tank is designed and built in the first place. A separate standard covers the in-service side - the inspection, repair, alteration, and reconstruction of tanks once they are operating - and yet another covers small, shop-fabricated tanks that are built in a shop and delivered whole. API 650's lane is specifically the design and construction of the large field-erected welded tank, and knowing that boundary keeps it from being confused with the inspection or small-tank standards.

Because API 650 is about how a tank is built rather than how it is operated day to day, a cloud SCADA platform such as Merobix does not intersect the construction standard directly; a monitoring system does not design a shell course or select a roof. Where monitoring matters is in operating an API 650 tank within the limits its design assumes. The tank is engineered for a specific product, a maximum liquid level, and a narrow band of internal pressure, and staying inside those bounds is an operational responsibility that continuous monitoring supports.

That operational role is real and worth stating precisely. An API 650 tank's atmospheric design means level and the integrity of its venting matter constantly: overfilling stresses a tank never meant to be run past its design level, and a venting problem can push internal pressure or vacuum outside the small range the shell and roof were built for. Cloud monitoring of tank level and abnormal conditions helps operators keep a tank inside the envelope its API 650 design defined, and on remote or unmanned sites it delivers that awareness to someone who can act. The standard builds a tank to safely hold its contents; monitoring helps ensure it is never asked to do more than it was designed to.

Frequently Asked Questions