API 570 Piping Classes and Intervals
API 570 does not inspect every line on the same clock - it classifies piping by the consequence of failure and lets condition drive the interval. This page explains the piping classification concept and how thickness measurement locations and corrosion rate combine to set intervals, for the engineer scheduling a piping program. It focuses on the classification and interval logic rather than a full code walkthrough.
API 570 Piping Classes in one line: API 570 classifies piping by the consequence of a failure - higher-consequence services in higher classes get more attention - and sets inspection intervals from the corrosion rate measured at thickness measurement locations, capped by not-to-exceed ceilings. A fast-corroding, high-consequence line is inspected far more often than a benign, low-consequence one.
Classifying Piping by Consequence
The first move in an API 570 program is grouping piping into classes by what a leak would do - toxicity, flammability, proximity to people, and environmental impact all raise the class. Higher-consequence services warrant tighter inspection; low-consequence utility lines warrant less. This is consequence-based prioritization, the same instinct behind a high consequence area in pipeline regulation.
Classification is not a one-time label. When a line changes service, or a plant reassesses hazards, the class can move, and the inspection plan moves with it. Getting the class wrong under-inspects a dangerous line or wastes effort on a harmless one, so it is worth an engineering review rather than a default assignment.
Thickness Locations and Corrosion Rate
Within each circuit, inspectors establish thickness measurement locations - specific points measured repeatedly so a trend, and therefore a corrosion rate, can be computed. Condition monitoring locations target the spots most likely to thin: elbows, tees, injection points, dead legs, and the underside of insulated lines prone to corrosion under insulation.
The corrosion rate from those trends, against the remaining thickness margin, sets the interval - the same condition-driven logic that governs tanks under API 653 inspection intervals. A not-to-exceed ceiling caps the interval so no line goes indefinitely uninspected even if its measured rate is very low.
Class and Interval at a Glance
The structure below shows how class and condition combine. The actual maximum intervals and class definitions come from the code and your facility's service classification - use this to understand the logic, not to schedule a real line.
| Piping class | Consequence | Inspection attention |
|---|---|---|
| Higher class (e.g. Class 1) | Severe if it leaks | Shortest intervals, most TMLs |
| Middle class | Moderate | Longer intervals |
| Lower class | Low, e.g. many utilities | Longest intervals, fewest TMLs |
Common Misconceptions
A common mistake is inspecting every line to the same interval for simplicity. That either over-inspects benign utilities or, worse, under-inspects high-consequence lines. The classification exists precisely to put effort where a failure matters most.
Another is placing thickness locations only where access is easy. Corrosion concentrates at elbows, injection points, and dead legs - often the awkward spots. A program that measures only convenient straight runs will trend the wrong locations and miss the thinning that actually causes leaks.
Frequently Asked Questions
How does API 570 classify piping?
By the consequence of a failure - toxicity, flammability, and proximity to people or the environment. Higher-consequence services fall in higher classes and get shorter inspection intervals and more thickness measurement locations.
What is a thickness measurement location in API 570?
A specific point on a piping circuit measured repeatedly so a thickness trend and corrosion rate can be established. Condition monitoring locations target the spots most prone to thinning, such as elbows, tees, injection points, and dead legs.
Does every line get the same inspection interval?
No. Intervals are set per circuit from its corrosion rate and its class, capped by a not-to-exceed ceiling. A high-consequence corroding line is inspected far more often than a low-consequence stable one.
Sources and verification
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- API 653, Tank Inspection, Repair, Alteration, and Reconstruction - American Petroleum Institute
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.