According to Section 6.6 of API 580 (2016), titled “Estimating Resources and Time Required,” it is clearly stated:

“The resources and time required to implement an RBI assessment will vary widely between organizations depending on a number of factors including the following:

a) implementation strategy/plans.

b) knowledge and training of implementers.

c) availability and quality of necessary data and information.

d) availability and cost of resources needed for implementation.

e) amount of equipment included in each level of RBI analysis.

f) degree of complexity of RBI analysis selected.

g) degree of precision required.”

This confirms the following are among the officially listed influencing factors:

A. Knowledge and training of implementers✔

C. The degree of precision required✔

D. Amount of equipment included✔

However:

B. Cost of mitigation activities —✘Not listed in Section 6.6 as a driver for time/resources during implementation.

E. Type of damage mechanisms involved —✘Relevant to PoF modeling, but not a direct listed factor for estimating time/resources needed to implement the RBI.

API 580, Section 4.2 defines risk reduction as:

“Risk reduction is the act of mitigating a known risk that is deemed to be too high to a lower, more acceptable level of risk with some form of risk reduction activity.”

Risk assessment and risk determination involve identifying and evaluating risk.

Risk management is the broader process that may or may not involve mitigation.

According to Section 7.3 of API 580:

“The data quality has a direct relation to the relative accuracy of the RBI analysis… Although the data requirements are quite different for the various types of RBI analysis, quality of input data is equally important no matter what approach to RBI is selected.”

This clearly establishes that regardless of whether a qualitative, semi-quantitative, or quantitative RBI method is chosen, the quality of data must remain consistently high to ensure meaningful risk assessments.

As indicated in API 580 Section 11.8:

"Reduction of some risks to a lower level may not be practical due to technology and cost constraints. An as low as reasonably practical (ALARP) approach to risk management may be necessary for these items."

Thus, technology limitations are explicitly cited as a reason why some risks cannot be feasibly reduced further.

According to API 580, Section 10.6.1:

“The consequences of releasing a hazardous material can be estimated in six steps…

a) estimate the release rate;

b) estimate total volume of fluid…

c) determine if the fluid disperses…”

Therefore, “Estimating the release rate” is the first step in the consequence evaluation process and is essential for modeling potential impact scenarios.

API 580, Section 12.4 and 12.6 emphasize that inspection should be optimized and risk-focused. Excessive inspections can increase exposure to damage mechanisms (such as mechanical or corrosion risks introduced during inspection activities), especially if not needed.

From Section 12.4:

“Organizations should be deliberate and systematic in assigning the level of risk management achieved through inspection and should be cautious not to assume that there is an unending capacity for risk management through inspection.”

Further, in risk-optimization contexts (Section 12.5):

“While there is a potential for reduction of inspection costs through utilization of RBI, increased equipment integrity and inspection cost optimization should remain the focus.”

Therefore, excess inspections may be:

Unjustified

Economically wasteful

Risk-enhancing (e.g., opening equipment unnecessarily may lead to deterioration)

Section 5.8 of API 580 states:

“The fact that some jurisdictions may have some prescriptive time-based rules on inspection intervals does not preclude the user from gaining significant benefits from the application of RBI as long as jurisdictional requirements are met and as long as the local regulations do not specifically prohibit the use of RBI planning.”

This confirms that unless explicitly prohibited, RBI may still be used effectively even in prescriptive jurisdictions.