API RP 580

Covers — the required elements of a risk-based inspection (RBI) program: data collection, damage-mechanism identification, probability-of-failure and consequence-of-failure assessment, risk ranking, inspection planning/effectiveness, reassessment, management of change, and roles/qualifications.

Does NOT cover (exclusions) — the following are governed elsewhere:

• The quantitative POF/COF calculation methodology → API RP 581.
• Damage-mechanism descriptions → API RP 571.
• The baseline inspection code (interval caps, rerating) → API 570 / 510.

RP 580 defines what an RBI program must contain; RP 581 provides one quantitative way to calculate the risk.

RP 580 sets the program elements for RBI:

• Data & Damage Mechanisms — collect equipment data and identify credible damage mechanisms (per RP 571).
• Risk Assessment — evaluate probability and consequence of failure and rank risk.
• Inspection Planning — set inspection scope, method, and interval by risk and inspection effectiveness.
• Reassessment & Roles — update on change/new data, with defined roles and qualified personnel.

API RP 580 defines the elements a risk-based inspection (RBI) program must contain: data, damage-mechanism identification, probability and consequence of failure, risk ranking, risk-driven inspection planning, reassessment, and qualified roles. It directs inspection resources by risk — more effort on high-risk equipment, less on low-risk — rather than by fixed intervals alone.

It is deliberately methodology-neutral: RP 580 says what a credible program must include, while the quantitative POF/COF calculation is provided by API RP 581. RBI plans made under 580/581 can replace the default fixed intervals of API 570/510.

Engineering Note: An RBI program is only credible if its damage-mechanism identification (RP 571) is complete — missing a credible mechanism produces a falsely low risk ranking and an inspection plan that never looks for the threat that actually fails the equipment.