Risk-Based Inspection (RBI) Program Design

Defensible plant-wide RBI programs per API 580 framework + API 581 quantitative methodology — designed by ASNT Level III consultants who have sat in front of API auditors, PHMSA inspectors and corporate AI-Bs across four continents.

Most plants still inspect on a calendar. Every five years a pressure vessel gets externally examined, every ten years it gets internally examined — whether or not the damage mechanisms have changed, whether or not the failure consequence has changed, whether or not the inspection adds any actual risk-reduction value. The result is over-inspection of low-risk equipment, under-inspection of high-risk equipment, and inspection budgets that grow faster than the assets they protect.

Done correctly, RBI typically cuts inspection spend 30-50% while improving asset reliability and audit defence. Done badly — as a one-off Excel exercise that nobody maintains — it produces compliance risk and disillusioned management. Atlantis NDT delivers the former.

UT, RT, MT, PT, VT, ET — full method coverage for any inspection-effectiveness review API 581 Annex 2 requires.

API 510, API 570, API 653 — the certifications that let us sign inspection plans the regulator and AI body will recognise.

Hands-on experience configuring Meridium APM, PCMS, Inspectioneering RBI Inspect and Visions RBI across 40+ refinery and petrochemical sites.

Anonymised results from recent RBI engagements. Reference letters available on NDA-bound request.

Most engagements start with a 60-minute scoping call — free, no obligation, NDA available on request. We will tell you whether your plant is RBI-ready, what data we need, and what timeline looks like for your equipment population. Pricing varies by region and scope — contact us for a tailored quote.

What this page covers

From fixed-interval inspection to defensible risk-ranked plans
What you get
Methodology — how we build the program
ASNT Level III credentials backing every output
Industries served
Sample client outcomes
Engagement model
Frequently asked questions
Ready to build a defensible RBI program?

Key points covered

Plant-wide damage mechanism review per API 571 with screening of all 60+ recognized mechanisms against your equipment, materials of construction, and process conditions.
Process-driven corrosion-loop diagrams that group equipment by shared damage exposure — the foundation for any defensible RBI program.
Quantitative LoF per API 581 Annex 2 — generic failure frequency × damage factor (DF) × management systems factor (FMS), documented for audit defence.
Financial + safety + environmental CoF per API 581 Part 3, including release-rate modelling, isolation effectiveness and detection credits.
5×5 risk matrix output, ranked equipment inventory, and code-defensible inspection plan with NDT method, extent, interval and effectiveness category for every item.
Configuration of your RBI tool of choice — Meridium APM, PCMS, Inspectioneering / RBI Inspect, Visions or in-house — so the outputs are sustainable, not one-off.
RBI working procedure, MoC trigger matrix, re-assessment protocol and operator/inspector training package so the program survives staff turnover.
Equipment population, regulatory drivers (API 510/570/653, PESO, OISD, PED, ABSA), and target risk-acceptance criteria are agreed in a kick-off workshop.
P&IDs, equipment registers, inspection history, process variables (T, P, H2S, water content, chloride, velocity, pH) and material-of-construction data are collected and validated.
API 571 mechanisms are screened against operating envelope. Output: a documented DM matrix per equipment item.
Equipment is grouped into corrosion loops based on common DM exposure. P&ID overlays mark loop boundaries.
Quantitative LoF + CoF per API 581 Parts 2 + 3, with inspection effectiveness credit per API 581 Annex 2.C.
Code-defensible plans per API 510 / 570 / 653 with method, location, extent, interval and effectiveness category.
Software configured, working procedure issued, owner/operator training delivered. Re-assessment trigger schedule agreed.
Reduction in inspection spend year-over-year (Gulf Coast refinery, ~600 equipment items)
PHMSA / OSHA / regulator inspection findings during 3-year post-RBI audit window
Typical engagement duration for a 1,000-item plant (Eastern Province GCC refinery)
Avoided unplanned downtime (Asia-Pacific cracker, after first re-assessment cycle)
API 580 is the recommended practice describing what an RBI program must contain — minimum elements, documentation, personnel qualifications, re-assessment triggers. API 581 is the quantitative methodology — the equations, damage factors and consequence models you actually use to compute risk. Most defensible programs cite API 580 for the framework and API 581 for the math.
For a single refinery unit (100-200 equipment items) we deliver in 6-8 weeks. A full refinery (1,000+ items) typically runs 12-20 weeks. A multi-unit petrochemical complex can take 24-36 weeks. The pacing constraint is almost always data quality, not analysis time.
Yes — both API 510 (vessels), 570 (piping) and 653 (tanks) explicitly allow RBI-based inspection intervals as an alternative to fixed-interval defaults, provided the program meets API 580 minimums. We design programs that satisfy each code's specific RBI requirements.
Both. We are tool-agnostic and have configured Meridium APM, GE APM, PCMS, Inspectioneering RBI Inspect, Visions RBI, Antea and bespoke Excel/Access programs. If you already have a license, we work in it. If you do not, we recommend an option matched to your equipment count and team capability.
Yes — our consulting team holds ASNT Level III in UT, RT, MT, PT, VT and ET, plus API 510, 570, 653 certifications. RBI outputs are signed by a Level III with relevant API authorized inspector credentials.
What about damage mechanisms we cannot quantify (e.g., HTHA, brittle fracture)?
API 581 handles most mechanisms quantitatively. For HTHA we layer in API RP 941 Nelson Curves. For brittle fracture we use API 579-1 Part 3. For mechanisms outside the quantitative scope (e.g., reformer tube creep, FCC erosion) we use semi-quantitative ranking with documented engineering judgement.
API 580 requires re-assessment when (a) significant process changes occur, (b) damage mechanisms change, (c) major repairs or replacements occur, or (d) on a scheduled cycle — typically 5 years for high-risk equipment, 10 years for medium-risk. We build the trigger matrix during program design.
Yes, if the program meets API 580 minimums and the inputs and judgements are documented. We deliver full audit-defence packs — DM screening, corrosion-loop diagrams, LoF/CoF worksheets, inspection-effectiveness justification, MoC trigger logs — so every output traces back to a documented source.