OptimalIntegrity Studio™ Wiki / RBI to API 580/581
Method and tool
Risk-based inspection
RBI ranks equipment by the risk of failure and puts the inspection effort where that risk is highest, instead of inspecting everything on the same fixed calendar. API 580 sets out the concepts, API 581 gives the quantitative calculation.
What RBI is
API RP 580 defines the recommended practice for risk-based inspection: the principles, the process and what a credible programme must contain. API RP 581 provides the quantitative methodology behind it, the equations for probability and consequence of failure. RBI is not a way to inspect less for its own sake, it is a way to inspect the right items, at the right time, with the right technique, and to justify running the rest longer.
Risk = PoF × CoF
Risk = Probability of failure × Consequence of failure
In API 581 the probability of failure is the generic failure frequency for the item, adjusted by a damage factor that captures the active damage mechanism, its rate and how effective past inspection has been, and by a management-systems factor. The consequence of failure is modelled from the fluid, the inventory and the conditions as a flammable, toxic, environmental and business-interruption outcome, expressed as an affected area or a cost. Multiply the two and you have risk, in a form you can rank and set a target against.
Qualitative, semi-quantitative, quantitative
| Qualitative | Expert judgement places each item in a probability and consequence band. Fast, good for screening a whole site. |
|---|---|
| Semi-quantitative | Simplified models and scoring, a practical middle ground where some data is thin. |
| Quantitative | The full API 581 calculation with failure frequencies, damage factors and consequence modelling. The most defensible, and the basis for ISO risk lines and financial risk targets. |
The RBI process
An RBI assessment runs as a loop, kept evergreen as new data arrives:
- Collect the equipment data, materials, process conditions and inspection history.
- Screen the credible damage mechanisms for each item in its service.
- Assess probability of failure from the damage factor, and consequence of failure from the fluid and inventory.
- Rank the items by risk on the matrix, against the risk target.
- Plan the inspection: date, coverage and technique, sized to reduce the risk that matters.
- Reassess after inspection and on change, so the plan stays live.
From risk to inspection plan
Risk sets the inspection, not the calendar. A higher-risk item is inspected sooner, more thoroughly and with a more effective technique; a low-risk item earns a longer interval. API 581 grades inspection effectiveness from A, highly effective to E, ineffective, because an inspection that cannot see the expected damage does not reduce the risk however often it is done. The run-length interval follows from the risk target and the rate of damage.
Try it: the risk matrix
Set the probability and consequence of failure to see where an item lands and how its risk is classified. This is the 5×5 that an RBI programme ranks the whole estate on.
PoF comes from the damage factor, the mechanism and its rate against inspection effectiveness. CoF blends safety, environmental and business loss. An illustrative 5×5 in the API 581 style.
Risk = PoF × CoF
Rows probability, columns consequence. Risk here is High · PoF 4 × CoF 4
Where OptimalIntegrity Studio™ fits
OptimalIntegrity Studio™ runs qualitative, semi-quantitative and fully quantitative RBI to API 581, screens the damage mechanisms automatically from materials and process conditions, imports thickness data and predicts corrosion growth, and turns the ranked risk into a run-length inspection plan. It carries the assessment as a living model, so the risk and the plan move when the plant does.