RBI Is Not a Software Purchase

Every year, operators spend serious money on RBI software licenses and end up, eighteen months later, with exactly what they started with: a time-based inspection program — now with more expensive record-keeping. The tool was real. The implementation wasn't.

Risk Based Inspection, done properly to API 580 and 581, is an engineering methodology. It concentrates inspection effort where the combination of probability and consequence of failure justifies it. The software only calculates; the risk picture it calculates from has to be built by people who understand the plant.

What the software cannot do for you

It cannot define your corrosion loops — grouping equipment that shares process conditions and degradation behavior. It cannot run a damage mechanism review, where materials and corrosion engineers decide which mechanisms are credible, at what rates, in which circuits. It cannot judge whether your inspection history is trustworthy enough to lower a probability of failure. And it certainly cannot maintain itself when the process changes: feed slate shifts, operating temperatures creep, injection points move. Without an evergreening process, an RBI assessment is a photograph that ages badly.

What a real implementation looks like

The sequence matters: data consolidation and corrosion loop definition first, damage mechanism reviews second, risk assessment third, inspection planning fourth — and the management system around it (roles, competencies, reassessment triggers, deviation handling) built in parallel, not bolted on. When the turnaround scope drops by twenty percent, you need to be able to show a regulator precisely why that is safe. That defense lives in the methodology, not the license.