Under API 653, an aboveground storage tank is inspected in two very different modes: while it is still in operation, and while it is emptied and taken out of service. The in-service side covers the external and routine inspections that can be done without removing the tank from duty - walking the shell, checking the roof, foundation, and appurtenances, and taking thickness readings from the outside - while the out-of-service side covers the internal inspection that requires the tank to be drained, cleaned, and entered to examine the bottom and lower shell. The interval between these inspections is not fixed; it is driven by measured corrosion rates, so a tank corroding quickly is looked at more often than one that is barely wasting away. Understanding the in-service regime, and how it relates to the internal one, is understanding how a tank is kept fit for service between the times it is opened up.
In-Service Inspection in one line: API 653 in-service inspection is the external and routine examination of a storage tank while it remains in operation, covering the shell, roof, foundation, and appurtenances and including external thickness measurements. It is distinct from the out-of-service internal inspection, which requires the tank to be emptied and entered, and the intervals for both are set by measured corrosion rates and the tank's fitness for service.
API 653 organizes tank inspection around whether the tank has to stop working to be examined. The routine, external inspections are in-service: an operator or inspector can look over the tank while it is full and running, checking the external condition of the shell and roof, the state of the foundation and anchor bolts, the condition of coatings, the appurtenances such as nozzles and stairways, and signs of settlement or leakage. External ultrasonic thickness readings can be taken on the shell from outside to track metal loss without emptying the tank. These checks catch the problems that are visible or measurable from the exterior.
The out-of-service inspection is a fundamentally deeper event because it reaches the parts of the tank the exterior view cannot. To perform it the tank is taken out of service, drained, cleaned, gas-freed, and entered so the bottom plates and the lower internal shell - the areas most exposed to water, sediment, and internal corrosion - can be inspected directly, commonly with bottom scanning and internal thickness surveys. The bottom in particular can only be properly assessed from inside, which is why a tank cannot be certified indefinitely on external inspection alone.
The two modes are complementary rather than alternatives. In-service inspections keep watch continuously between the major openings, catching external deterioration and shell thinning as it develops, while the out-of-service inspection periodically confirms the condition of the bottom and interior that only a full entry can reveal. A sound inspection program uses the frequent external and routine checks to manage risk in the years between the far less frequent, far more disruptive internal inspections.
The central idea in setting API 653 intervals is that the tank tells you how often to look at it, through how fast it is corroding. Thickness readings taken over time give a corrosion rate - metal loss per year - for the shell and, from internal inspections, for the bottom. Knowing the current thickness, the minimum thickness the component can safely tolerate, and the rate at which thickness is being lost, an inspector can calculate the remaining life of that component and set the next inspection so it happens well before the remaining life is used up. Fast corrosion means a short interval; slow corrosion allows a longer one.
This makes the interval a data-driven output rather than a fixed calendar rule. A newly measured corrosion rate can extend or shorten the time to the next inspection, and a component approaching its minimum thickness drives the interval down regardless of how long it has been since the last look. The consequence is that inspection intervals are not the same across tanks or even across time for one tank; they track the actual, measured condition, with maximum limits that the corrosion-rate calculation can only shorten, not exceed.
Fitness-for-service ties it all together. The point of measuring corrosion rate and setting intervals is to keep every tank demonstrably fit for continued service - thick enough, sound enough, and settled enough to hold its product safely until the next inspection. When a corrosion rate or a thickness measurement shows a component will not make it to the planned interval, the answer is to inspect or repair sooner, not to run to the calendar date. The regime is fundamentally about proving, on evidence, that the tank is safe to keep operating.
Periodic inspection, however well planned, is a snapshot: it tells you the tank's condition on the day it was inspected and infers the days in between from a corrosion rate. Continuous monitoring fills that gap by watching the tank between inspections, and much of what threatens a tank leaves a trace in data a SCADA system already collects. Level and temperature trends, fill rates, and the behavior of the tank's appurtenances can all reveal problems - a persistent bottom water layer accelerating internal corrosion, unusual movement suggesting settlement, or operating conditions the tank was not designed for - long before the next formal inspection would find them.
A cloud SCADA platform is naturally positioned to provide that continuous layer because it is already reading and historizing the tank's operating signals. When Merobix trends level, temperature, and related conditions over months, it turns slow developments into visible patterns: a rising interface indicating water sitting on the bottom, a settlement-related tilt showing up in level behavior, or repeated excursions outside safe operating conditions. These are exactly the kinds of trends that inform where inspectors should look hardest and whether an interval should be pulled in.
The relationship is supplementary, not a substitute. Continuous monitoring cannot measure shell thickness or enter a tank to scan its floor, so it does not replace the ultrasonic readings and internal inspections API 653 requires. What it does is make the periodic inspection smarter and the intervals between them safer - flagging conditions that warrant an earlier look, giving inspectors context about how the tank has actually been operated, and reducing the chance that a problem develops unseen in the years between openings. The formal inspection proves fitness for service; the continuous data helps ensure the tank stays fit in between.
In-service inspection is done while the tank keeps operating and covers the external and routine checks - the shell, roof, foundation, appurtenances, and external thickness readings that can be taken without emptying the tank. Out-of-service inspection requires the tank to be drained, cleaned, and entered so the bottom and lower internal shell, which the exterior view cannot reach, can be examined directly. The two are complementary, with frequent external checks managing risk between the far less frequent internal inspections.
It is driven by the tank's measured corrosion rate. Thickness readings over time give a rate of metal loss, and combined with the current thickness and the minimum safe thickness, that yields a remaining life for each component. The next inspection is set to occur well before that remaining life is used up, subject to maximum limits the standard allows. A fast-corroding tank gets a short interval; a slow-corroding one can go longer.
No. Continuous monitoring watches operating conditions and trends between inspections and can flag developing problems, but it cannot measure shell thickness or enter a tank to scan its floor, which the standard requires. Its role is supplementary - making periodic inspections smarter, informing where to look, and signaling when an interval should be shortened - while the formal external and internal inspections still provide the fitness-for-service evidence.
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.