Subscribe to Our Newsletter

API RBI Software

The API RBI Software Difference

Developed by subject matter experts from top multinational refiners, and backed by the American Petroleum Institute (API), the technology behind API RBI software reflects industry best practices and the expertise of the best minds in the industry.

API consensus process for technology
The technology was developed through an ANSI-approved consensus process, and all technology enhancements continue to be reviewed and balloted by owner/user companies through an API committee. Once approved, the technology is programmed into the software and a field test is conducted for validation. Periodically these results are compared to known incidents to check the answer against industry experience.

Technical basis documentation
The technology is thoroughly documented and updated in API 581, available for purchase from API. The software is a validation of solid technology, as its output is tested against this documentation for accuracy.

Quantitative vs. qualitative
A truly quantitative tool calculates risk over time, that is, risk due to an increasing Probability of Failure (PoF) as in-service damage potentially occurs. API RBI is the only RBI tool that provides metrics and calculates PoF due to ongoing damage. This PoF will generate a location in the Risk Matrix that could move (increase) over time, depending on the impact of damage rate on equipment integrity.

Risk-based cost benefit and decision-making
Because a discreet risk is calculated and can change with time, a cost benefit approach can be used to determine the date where inspection is required. The ability to generate cost benefit (in terms of risk reduction/$ spent) leads to more information for risk management and budgeting.

Risk-based to recommend inspection intervals
API RBI technology uses a true risk-based interval. The methodology offers the option to set a maximum interval (in practice 20 to 25 years) and recommends re-evaluation of the RBI study and basis at a minimum of every 10 years (shorter if operating conditions change). That is, the decision logic generating a recommended inspection is not limited by or based on half-life calculations or prescriptive interval approaches. Credit is earned for knowledge and capitalized on in the risk analysis. Half-life calculations or prescriptive interval approaches do not enter into the inspection recommendations - only risk. The impact of this approach is MORE emphasis on high risk equipment (increasing inspection costs) and LESS emphasis on low risk equipment (decreasing inspection costs). The net result is usually a reduction of overall costs, while still reducing risk.

Various companies have developed RBI approaches based on API 580, which is a qualitative versus quantitative approach. Most tend to be “black-box” or they are too generic to accurately define an auditable inspection/ maintenance plan providing measures of inspection program improvement. The primary goal API RBI is sound technology that produces PoF, CoF and risk numbers you can trust.