NFPA 30 is the Flammable and Combustible Liquids Code, the standard that sets the rules for how hazardous liquids are classified, stored, and handled. It starts by putting liquids into classes based on how easily they give off ignitable vapor, then uses those classes to drive requirements for tank spacing, containment, and fire protection. For crude oil and condensate storage, NFPA 30 is the governing code behind the layout of a tank battery - why tanks sit a certain distance apart, why they are surrounded by a dike, and how much liquid that dike has to be able to hold. It is the code that turns the flammability of a liquid into concrete facility design.
NFPA 30 (flammable liquids) in one line: NFPA 30 is the Flammable and Combustible Liquids Code, which classifies liquids by their flash point and boiling point and sets requirements for their storage and handling. It drives storage-tank spacing, secondary containment such as dikes and remote impounding, and the sizing of that containment, so a leak or spill of crude, condensate, or refined product is contained rather than allowed to spread.
The foundation of NFPA 30 is its classification of liquids, because how a liquid is stored depends first on how dangerous it is. The code separates flammable liquids from combustible liquids using flash point - the temperature at which a liquid gives off enough vapor to form an ignitable mixture with air. A liquid with a low flash point releases ignitable vapor at ordinary temperatures and is treated as flammable; a liquid with a higher flash point does not become a vapor hazard until heated and is treated as combustible. The lower the flash point, the more readily the liquid can be ignited, and the more stringent the storage requirements become.
Within these broad groups, NFPA 30 defines subclasses that refine the picture using flash point together with boiling point, so that liquids are sorted by both how easily they vaporize and how volatile they are once vaporized. This layered classification is what lets the code apply proportionate rules: the most volatile products get the tightest controls, while less hazardous liquids are handled under lighter requirements. In upstream oil and gas, this matters directly because crude oil and condensate span a range of volatilities, and where a given stream falls in the classification affects how its storage must be designed.
Classification is not an academic exercise; it is the input to nearly every other requirement in the code. The class of a liquid influences allowable tank arrangements, the separation distances between tanks and to property lines and buildings, and the fire protection provisions. Getting the classification right is therefore the first step in designing compliant storage, because an underestimate of a liquid's hazard would ripple into spacing and containment that are inadequate for what is actually in the tank.
One of the most visible outcomes of NFPA 30 is the spacing between storage tanks and their distance from other features. The code sets separation requirements so that a fire or failure at one tank is less likely to spread to its neighbors, and so that emergency responders have room to work. These distances relate to tank size and to the class of liquid stored, and they are part of why a tank battery is laid out the way it is rather than packed as tightly as the pad would allow. Spacing is a passive safety measure - it buys distance and time without any active system having to function.
The other cornerstone is containment of a spill or release, and NFPA 30 addresses this through methods such as diking around tanks or draining to a remote impounding area. Secondary containment is the barrier that catches liquid if a tank or its piping fails, keeping a release inside a defined area instead of letting it run across the site or reach a waterway. A dike, or firewall, is the earthen or concrete wall built around a tank or group of tanks to serve exactly this purpose, and it is the feature most people picture when they think of tank containment.
The code does not just require containment; it addresses how large it must be. The containment volume has to be sized to hold a meaningful release - the failure of the largest tank within it - so a dike that is too shallow or too small would let liquid overtop and defeat the purpose. This is where NFPA 30 connects to the hardware most operators already know: the secondary-containment structures around a tank battery exist because the code requires them, and their dimensions are driven by the code's sizing rules. The code is the reason the containment is there and the reason it is as big as it is.
NFPA 30 shapes storage-tank operation, but the code's requirements are largely physical and procedural - classification, layout, containment, and fire protection - rather than something a monitoring system enforces directly. It is important to be clear that a SCADA platform does not make a tank battery NFPA 30 compliant; the spacing, the dike, and the containment sizing are engineering and construction decisions. Where cloud monitoring contributes is in operating that storage safely day to day and in reducing the chance that a release ever tests the containment in the first place.
Level monitoring is the most direct connection. NFPA 30's containment exists to catch a release, but the better outcome is not to have one, and continuous visibility into tank levels helps operators avoid the overfills and abnormal conditions that lead to spills. A cloud SCADA platform such as Merobix reads tank levels across a battery, trends them, and alarms on high levels and abnormal rates of change, so an operator sees a tank approaching trouble before liquid ever reaches a relief path or a seam. That is prevention working upstream of the code's last line of defense.
Monitoring also helps when a containment structure is actually doing its job. Water and liquid accumulation inside a dike, whether from rainfall or from a small leak, has to be managed, and a release into containment needs a fast response before it can escape or evaporate into a vapor hazard. Remote monitoring of level and, where instrumented, of the containment area itself lets an operator at a distant, unmanned site know quickly that something has changed. NFPA 30 provides the passive protection - the spacing and the dike that hold a release; cloud monitoring provides the awareness that keeps normal operation from getting to that point and shortens the response when it does.
NFPA 30 separates liquids using flash point, the temperature at which a liquid gives off enough vapor to form an ignitable mixture with air. Liquids with low flash points that release ignitable vapor at ordinary temperatures are treated as flammable, while those with higher flash points that only become a vapor hazard when heated are treated as combustible. The code then defines subclasses using flash point together with boiling point, so more volatile liquids get more stringent storage requirements.
Dikes, sometimes called firewalls, provide secondary containment that catches liquid if a tank or its piping fails, keeping a release inside a defined area instead of spreading across the site or reaching a waterway. NFPA 30 requires this containment and addresses how large it must be, so that it can hold a meaningful release such as the failure of the largest tank within it. A dike that is too small or too shallow would let liquid overtop and defeat the purpose, which is why the code's sizing rules drive its dimensions.
Yes, NFPA 30 governs the storage of flammable and combustible liquids, which includes crude oil and condensate at production and gathering sites. Because these streams span a range of volatilities, where a given liquid falls in the code's classification affects how its storage must be designed, including spacing and containment. The code is a major reason a tank battery is laid out with separation between tanks and a sized dike around them.
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.