Editor’s Note: AI, Statistics, and the RBI Journey

RBI programs have proven their value for many, as evidenced by their ongoing use.  Why would so many owner/operators continue investing in API RP 580? It has been a great “what to do” document. It has kept us between the lanes, so to speak. It represents the minimum requirements for a credible RBI program by addressing what the consensus group believes to represent minimum credible practices for an RBI program (i.e., essential and recommended practices). It is methodology-neutral and presents basic RBI requirements that many governmental jurisdictions and companies reference.

There are various RBI methodologies, each with its own algorithms. One popular methodology that some software manufacturers use for RBI calculations is API RP 581. One important requirement of API RP 580 is that, whatever RBI software is used, the basis must be documented. This is for many reasons, one being that the licensee should review the basis to make sure it is in alignment with, in the US at least, OSHA requirements and recognized and generally accepted good engineering practices (RAGAGEP). This is important. In fact, OSHA requires this type of sound engineering basis for the PSM rule. Whatever is used to make equipment inspection and run/repair/replace decisions must be based on RAGAGEP. Our decisions should be and, in some cases, must be technically defensible.

The hardworking volunteer owner/operators, consultants, advisors, and contractors at API, and other organizations like ASME, etc., have continued to supply us with very useful standards, codes, and practices for decades. Most of these are industry consensus documents, often under the auspices of organizations like ANSI, that represent RAGAGEP when applied properly.

New and evolving technologies bring the hope and promise of enabling increased success on our risk management journey. This includes artificial intelligence, statistics, digital twins, contextualization tools, etc.  Many of us believe that, when used responsibly, these new tools promise improved safety and reliability, decision-making, and overall business performance.

So, what does that mean, for instance, if I am using a tool like API RBI, based on API RP 581 (which is a specific RBI methodology)? Can I use AI, statistics, etc., and still be compliant with API RP 580?

No matter what steps you take, sublime or more gradually evolving as you become comfortable with the technologies and ROIs on your MI and reliability journeys, you have options. Will you go slow and evolve or make a drastic change? Remember to think about the sustainability of your programs with the changes, what burden might be placed on the organization to achieve the benefits, and ALWAYS make sure what you use and do is technically defensible for safety, reliability, and ROI reasons. Make sure “the juice is worth the squeeze!”

As we add AI, statistical, and other emerging capabilities, please remember to comply with API RP 580 or a similar standard, as appropriate, to ensure we continuously improve our safety and business performance. Potentially powerful tools and capabilities are emerging. Many bright professionals are discovering ways to use them to improve quality, efficiency, and productivity. It is incumbent on us to make sure we are using tools, models, and making decisions that are defensible, 720º around (safety, reliability, optimization)! Guard the Gate while participating in business success!