Standards
Reading API 653 as an owner, not an inspector
The standard governs inspection, repair and reconstruction. What it really sets is the clock on your tank — and cleaning is what stops that clock being wasted.
API 653 is written for inspectors, but the people whose decisions it constrains are owners. It sets inspection intervals, it defines what counts as a finding, and it determines when a tank can go back into service.
The part that catches operators out is preparation. An inspection cannot start until the tank is clean, gas-free and accessible. If the cleaning runs long, the inspection window slips, and the outage that was scheduled around it stretches with it.
This is why cleaning should be planned against the inspection date rather than the other way round. The relevant question is not how quickly a tank can be emptied, but how quickly it can be brought to inspection-ready condition with a gas-free certificate in hand.
API 2015 governs that second part — safe entry and cleaning — and API 2016 covers entry itself. Between them they describe the state a tank has to reach before an API 653 inspector is of any use to you.
Read together, the three standards are less a compliance burden than a schedule. The operators who treat them that way lose fewer days per turnaround.