
- API 510 covers pressure vessels, API 570 covers process piping and API 653 covers aboveground storage tanks.
- Intervals are driven by measured corrosion rate and remaining life, within limits set by the governing code and edition.
- Each code needs its own API-certified authorised inspector, so one certification does not cover all three.
- Repairs, alterations and records need defined approvals and a permanent, progressive equipment file kept by the owner-user.
Most plants in the region run equipment that falls under at least one of three API inspection codes, and often all three. A refinery unit may have pressure vessels covered by API 510, interconnecting lines under API 570 and a tank farm governed by API 653. Each code has its own language, its own inspector certification and its own expectations for records, which makes it easy for a maintenance or integrity team to treat them as one vague obligation.
That vagueness causes real problems. Intervals get set by habit rather than data, repairs go ahead without the right approvals, and records end up scattered across contractors and spreadsheets. When an auditor or regulator asks how the next inspection date was set, the answer should come from the code and your own data, not from what was done last time.
What each code covers
API 510 is the Pressure Vessel Inspection Code. It covers the in-service inspection, repair, alteration and rerating of pressure vessels and their pressure-relieving devices once they are in service. It assumes the vessel was built to a recognised construction code, most often ASME Section VIII, and picks up where construction ends.
API 570 is the Piping Inspection Code for in-service metallic piping systems. It covers process piping and associated components, and it uses ideas such as circuits, condition monitoring locations and injection points to focus attention on the parts of a system most likely to degrade.
API 653 covers the inspection, repair, alteration and reconstruction of aboveground storage tanks, mainly those built to API 650 or its predecessor API 12C. Its attention is on the shell, bottom, roof and foundation, and on whether a tank remains suitable for continued service.
How intervals are set
None of the three codes asks you to inspect simply because a calendar date has arrived. The principle is the same across all of them: measure how fast metal is being lost, compare current thickness with the minimum required thickness, and work out how much life remains. The next inspection is then set as a fraction of that remaining life, subject to maximum limits that the code defines.
Those limits, and the factors applied to remaining life, differ between codes, equipment types and editions. Local regulations and owner-user standards can tighten them further. Rather than relying on a figure remembered from training, check the edition you are working to and your jurisdiction's requirements. The codes also allow risk-based inspection, under defined conditions, to adjust intervals where the data supports it.
The practical consequence is that interval quality depends on data quality. A corrosion rate built from a handful of inconsistent readings taken at shifting locations will produce an interval you cannot defend.
An inspection interval is only as good as the thickness data behind it.
The certified inspector's role
Each code relies on an authorised inspector holding the relevant API individual certification. These are separate certifications: an API 510 inspector is not automatically qualified to sign off API 570 or API 653 work. The inspector is responsible for confirming that inspections, examinations and tests have been carried out and evaluated as the code requires, and for accepting repairs and alterations.
The inspector works alongside other roles the codes define. Being clear about who does what matters, particularly when several contractors are on site.
- Owner-user: holds overall responsibility for the inspection programme, the records and compliance with the code.
- Authorised inspector: plans and evaluates inspections, accepts repairs and confirms next inspection dates.
- Engineer: handles design calculations, fitness-for-service assessments and approval of alterations and rerating.
- Examiner: performs NDT to qualified procedures and reports results to the inspector.
- Repair organisation: carries out repairs and alterations under the inspector's authorisation.
Repairs and alterations
The codes distinguish between a repair, which restores equipment to a condition suitable for its existing design, and an alteration, which changes the design itself. The distinction matters because alterations usually need engineering involvement, broader approval and more extensive testing. Rerating, where design pressure or temperature changes, carries its own conditions.
A sensible routine for any repair or alteration looks like this:
- Confirm whether the work is a repair or an alteration under the governing code.
- Obtain the authorised inspector's authorisation before work starts, and engineering approval where required.
- Use qualified welding procedures and welders, and specify the NDT and pressure testing needed.
- Have the inspector accept the completed work against the agreed requirements.
- Update the equipment file, including drawings, calculations and nameplate or stamping where the code requires it.
Records that hold up
All three codes expect the owner-user to keep permanent, progressive records. In practice that means design and construction data, inspection history, thickness readings tied to fixed locations, corrosion rate and remaining life calculations, repair and alteration records, and any fitness-for-service assessments. A new engineer should be able to open the file and understand the equipment's condition and how its next inspection date was reached.
The common weaknesses are familiar: readings that cannot be traced to a location, reports held by the contractor rather than the owner, and repairs recorded in work orders but never reaching the equipment file. Closing these gaps is usually cheaper than another round of inspection.
A practical first step
Pick one unit and review a sample of equipment across all three codes. Is the scope clear, is each interval traceable to a calculated remaining life, and is the repair history complete? The gaps you find will show where to start. If an independent view would help, KARR's API inspection team can review records with you or support the work on site.
API 510, API 570, API 653


