All Things API: The Standards Behind Mechanical Integrity
A field guide to the API inspection standards that govern pressure vessels, piping, tanks, and risk programs — and why connected facility data decides how well any of them actually get applied.
In the process industries, few organizations have shaped inspection, maintenance, and mechanical integrity practice as extensively as the American Petroleum Institute. API standards influence how facilities inspect pressure vessels, piping systems, storage tanks, and relief devices — establishing what should be inspected, how often, how damage should be evaluated, and when equipment can safely remain in service.
For owners and operators, understanding API requirements is only part of the challenge. The harder task is applying those requirements consistently across thousands of assets, years of inspection history, changing operating conditions, and records scattered across multiple systems.
That is where mechanical integrity programs either become reliable operating systems or remain collections of disconnected documents.
What Are API Standards?
API develops technical standards, recommended practices, and inspection codes for the oil, gas, petrochemical, refining, and broader process industries. These documents provide a common framework for managing equipment throughout its lifecycle. Depending on the asset and application, a standard may address equipment design and construction, in-service inspection requirements, damage mechanisms, remaining-life calculations, risk-based inspection, repair and alteration practices, inspector qualifications, fitness-for-service evaluations, and recordkeeping.
These are not reference manuals that sit on a shelf. They shape inspection plans, turnaround scopes, corrosion monitoring programs, engineering decisions, and maintenance priorities across a facility.
The Standards Most Mechanical Integrity Teams Encounter
A mature MI program may reference dozens of API documents, but a handful appear repeatedly across refining, chemical processing, terminals, and midstream operations.
| Standard | Covers | Typical assets |
|---|---|---|
| API 510 | In-service inspection, rating, repair, alteration | Pressure vessels |
| API 570 | Inspection, rating, repair, alteration | In-service metallic piping |
| API 653 | Inspection, repair, alteration, reconstruction | Aboveground storage tanks |
| API 580 | Risk-based inspection framework | Program-level RBI |
| API 581 | Quantitative RBI methodology | Risk calculations |
| API 579 | Fitness-for-service assessment | Flawed or damaged equipment |
Pressure Vessel Inspection
API 510 provides requirements for the in-service inspection, rating, repair, and alteration of pressure vessels. Vessels operate under conditions that introduce corrosion, cracking, erosion, and fatigue, and the standard helps inspection teams set intervals, evaluate thickness readings, document repairs, and confirm continued suitability for service.
Managing these assets requires more than storing the latest inspection report. Teams must maintain a complete record of vessel components, materials, design conditions, corrosion rates, minimum required thicknesses, repairs, alterations, and open recommendations. When that information is scattered across spreadsheets, PDFs, drawings, and maintenance systems, even routine decisions become difficult to verify.
Piping Inspection
API 570 covers the inspection, rating, repair, and alteration of in-service metallic piping. Piping is often the largest and most complex asset population in a facility — a single site may contain thousands of circuits, lines, components, and monitoring locations.
Effective piping programs depend on maintaining accurate relationships between circuits, process services, damage mechanisms, inspection locations, thickness readings, and drawings. This is where intelligent P&IDs and connected asset data earn their keep: an inspector should be able to identify a circuit on a drawing, review its inspection history, locate the associated CMLs, understand the process service, and reach supporting records without hopping between disconnected systems.
Storage Tank Inspection
API 653 addresses the inspection, repair, alteration, and reconstruction of aboveground storage tanks. Tank integrity programs monitor shells, roofs, floors, foundations, nozzles, and settlement — and each inspection generates large volumes of information, from floor scans and settlement surveys to repair records and engineering calculations.
Every inspection becomes more valuable when it can be compared against prior conditions and connected to the tank's complete operating history. A strong tank program gives teams a clear view of current condition, historical deterioration, upcoming requirements, and unresolved recommendations.
Risk-Based Inspection
API 580 provides the framework for developing and maintaining an RBI program, while API 581 supplies quantitative methodologies to support risk calculations. Where traditional programs rely on fixed intervals, risk-based inspection weighs both the probability and the consequence of failure, letting organizations focus resources on the equipment that presents the greatest risk.
RBI lives or dies on data quality.
Risk calculations draw on equipment design, materials, process conditions, damage mechanisms, inspection effectiveness, fluid properties, and corrosion rates. When that information is incomplete or stale, the output can look precise while resting on weak assumptions.
RBI cannot compensate for poor facility data — the strongest programs treat it as part of a larger mechanical integrity system rather than an isolated calculation tool.
Fitness-for-Service
API 579 (jointly published as ASME FFS-1) governs fitness-for-service assessments: engineering evaluations that determine whether equipment containing flaws or damage can continue operating safely. Assessments cover conditions such as general metal loss, localized corrosion, pitting, crack-like flaws, dents and gouges, fire damage, creep, and brittle fracture concerns.
The quality of an FFS assessment is directly connected to the quality of the underlying record. When equipment history and inspection findings are hard to locate, engineers spend significant time reconstructing information before the evaluation can even begin.
The Standards Are Connected
One of the most common weaknesses in MI programs is treating each standard as a separate administrative requirement. In practice, they overlap constantly. A piping system managed under API 570 may feed a vessel governed by API 510. Both assets may sit inside an RBI program aligned with API 580 and API 581. A significant finding may trigger an API 579 assessment. Repairs generate work orders, engineering reviews, drawing updates, and future inspection recommendations.
The real challenge is not managing each standard independently — it is maintaining the relationships between assets, inspections, calculations, findings, drawings, repairs, and operating decisions.
Mechanical integrity is a connected discipline, and the systems supporting it should reflect that.
The Data Problem Behind Compliance
Most facilities already possess the information their API programs require. The problem is that it is rarely organized into a single, trusted environment. Inspection reports live in document repositories. Thickness readings live in spreadsheets. Asset hierarchies live in a CMMS. P&IDs are stored as static PDFs. Risk calculations sit in separate RBI software. Recommendations are tracked through email.
Each system holds part of the truth, but no single system presents the complete condition of the asset. Inspectors search for prior records, engineers work from incomplete histories, intervals become hard to verify, recommendations linger without owners, and drawings drift out of sync with field conditions. Compliance may still be achieved — but it requires unnecessary effort and leaves more room for uncertainty.
Turning Requirements Into Digital Workflows
Modern programs need more than electronic storage; they need structured workflows that translate requirements into repeatable actions. A piping workflow should connect the circuit to its process service, inspection locations, thickness readings, corrosion rate, remaining life, interval, damage mechanisms, recommendations, work history, and associated drawings. A vessel workflow should connect the asset to its components, design conditions, inspection methods, calculated minimum thickness, repairs, and next inspection date. A tank workflow should provide a complete record across shells, roofs, floors, settlement data, and historical inspections.
The objective is not to replace engineering judgment. It is to give inspectors, engineers, and operations the information they need to apply that judgment consistently.
The Role of Intelligent Drawings
P&IDs remain one of the most important reference points in a process facility — they show how equipment, piping, valves, instruments, and process systems relate. Yet most remain disconnected from the inspection and asset records behind them.
An intelligent drawing platform changes that relationship. Instead of treating the drawing as a static image, teams use it as an interface into the MI program: selecting a vessel, line, valve, or tag provides direct access to inspection history, asset records, documents, recommendations, and work activity. Users begin with the physical process relationship they already understand, and the drawing carries them into the data. Intelligent drawings also support redlining, drawing updates, flow-path tracking, circuit visualization, and validation between field conditions and facility records.
Preparing for an Audit
Audit readiness should not begin when an audit is announced. A mature program can answer basic questions at any time:
- Which assets are governed by each inspection code
- When each asset was last inspected, and by what methods
- Which damage mechanisms are being monitored
- What corrosion rate was calculated and what remaining life is projected
- Which recommendations remain open, and who owns them
- Whether the drawings reflect current field conditions
When those answers require days of searching, the issue is not audit preparation. It is a sign the program lacks a reliable operating layer.
Beyond Compliance
API standards establish an essential foundation, but the strongest programs do more than meet minimum requirements. They use inspection data to identify deterioration earlier, connect findings to maintenance planning, prioritize work based on risk, and give operations, inspection, engineering, and leadership a shared understanding of asset condition. Compliance becomes the baseline rather than the objective.
API standards provide the framework for mechanical integrity. The systems around those standards determine how effectively that framework gets applied.
Frequently Asked Questions
What is the difference between API 510, API 570, and API 653?
All three govern in-service inspection, but for different asset classes: API 510 covers pressure vessels, API 570 covers metallic piping systems, and API 653 covers aboveground storage tanks. Each defines inspection intervals, evaluation methods, and repair and alteration requirements for its asset type.
What is the difference between API 580 and API 581?
API 580 defines the framework and minimum requirements for a risk-based inspection program. API 581 provides the quantitative methodology — the calculation procedures used to evaluate probability and consequence of failure within that framework.
Is API 579 the same as ASME FFS-1?
Yes. API 579 is jointly published with ASME as API 579-1/ASME FFS-1. It provides the assessment procedures used to determine whether equipment containing flaws or damage is fit for continued service.
Do API standards require specific software?
No. The standards define requirements, not tools. But applying them consistently across thousands of assets depends on complete, connected records — which is why most mature programs move from spreadsheets and disconnected files to a dedicated mechanical integrity platform.
How do intelligent P&IDs support API compliance?
They connect the drawing to the records behind it. Selecting a vessel, line, or tag on the P&ID provides direct access to inspection history, thickness data, recommendations, and work activity — reducing the time spent assembling information from separate systems.
Put your API program on a connected operating layer.
VisualAIM’s Mechanical Integrity Suite brings asset information, inspection history, corrosion monitoring, recommendations, risk calculations, and supporting documents into one connected environment — while the Intelligent Drawing Platform extends that record into the P&IDs themselves.
Explore the MI Suite
