Study guide

3.3 Team Decision Ownership, Review, and Approval Responsibilities

API 580 Risk Based Inspection Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Terms, Definitions, Acronyms, and RBI Scope

1.1 Fundamental RBI Terminology and Acronyms 1.2 Absolute vs. Relative Risk and Risk Acceptability Criteria 1.3 Scope, Objectives, and Integration with Fixed Equipment Mechanical Integrity (MI) Programs

2 Chapter 2: RBI Program Elements, Implementation, and Management

2.1 Essential Steps of an RBI Assessment and Implementation Plan 2.2 RBI Program Limitations, Assumptions, and Boundaries 2.3 Management of Change (MOC) Integration and Life-Cycle Sustainment

3 Chapter 3: Roles, Responsibilities, Training, and Qualifications

3.1 RBI Team Composition and Roles 3.2 Member Qualifications, Training, and Experience Requirements 3.3 Team Decision Ownership, Review, and Approval Responsibilities

4 Chapter 4: Data Collection, Quality, and Validation

4.1 Required Data Types: Design, Operating, Process, Maintenance, and Inspection Records 4.2 Data Completeness, Quality Assessment, and Handling Data Gaps 4.3 Validation and Evergreening of Physical and Operating Data

5 Chapter 5: Damage Mechanisms and Failure Modes

5.1 Credible Damage Mechanism Identification in Refineries and Petrochemical Plants 5.2 Thinning, Stress Corrosion Cracking (SCC), High-Temperature, and Environmental Degradation Modes 5.3 Failure Modes, Leak vs. Rupture Morbidities, and Degradation Rate Determination

6 Chapter 6: Probability of Failure (POF) Analysis

6.1 POF Methodologies: Qualitative, Semi-Quantitative, and Quantitative Modeling 6.2 Structural Damage Factors, Technical Modules, and Time-Dependent vs. Independent POF 6.3 Effect of Past Inspection Effectiveness (Categories A through E) on POF Determination

7 Chapter 7: Consequence of Failure (COF) Analysis

7.1 COF Dimensions: Safety, Environmental, Equipment Damage, and Business Interruption 7.2 Release Scenarios, Hole Sizes, Inventory Isolation, and Fluid Phase Behavior 7.3 Quantitative Consequence Areas (Flammable/Toxic) vs. Financial Cost Estimation

8 Chapter 8: Risk Assessment, Matrix Representation, and Plotting

8.1 Combining POF and COF: Risk Calculation and Risk Plotting 8.2 Qualitative and Quantitative Risk Matrix Structures (e.g., 5x5 Matrix) 8.3 Risk Uncertainty, Sensitivity Analysis, and Risk Acceptance Thresholds

9 Chapter 9: Risk Management and Inspection Planning

9.1 Risk-Driven Inspection Strategy: What, Where, When, and How to Inspect 9.2 Inspection Interval Determination and Non-Inspection Risk Mitigation 9.3 Risk Reduction Optimization and Cost-Benefit Analysis

10 Chapter 10: RBI Documentation, Reassessment, and Recordkeeping

10.1 Required Documentation, Audit Trails, and Rationale Tracking 10.2 Reassessment Triggers: Periodic Updates, MOC Events, Out-of-Limit Operations, and Inspection Results 10.3 Long-Term Record Retention and Reporting to Asset Integrity Management (AIM)

3.3 Team Decision Ownership, Review, and Approval Responsibilities

Key Takeaways Explain This Topic AI

API RP 580 Section 7 requires a formal, documented review and approval workflow for all RBI assessment results, risk rankings, and optimized inspection plans prior to field implementation.

Team decisions should be achieved through technical consensus; when technical disagreements arise (e.g., regarding corrosion rate estimations), the team must adopt conservative assumptions and document sensitivity analysis rationale.

Official sign-off and approval accountability must be provided by key team representatives, including the Equipment Inspector, Materials and Corrosion Specialist, Process/Operations Manager, and AIM/Maintenance Leadership.

Any changes to equipment physical configuration, process chemistry, feedstocks, or operating envelopes beyond Integrity Operating Window (IOW) limits automatically trigger Management of Change (MOC) review and RBI reassessment.

Evergreening ownership must be explicitly assigned to ensure periodic reassessments occur following turnarounds, major inspection findings, process modifications, or elapsed maximum calendar time limits.

Last updated: August 2026

3.3 Team Decision Ownership, Review, and Approval Responsibilities

API RP 580 Section 7 & 15 Governance: An RBI assessment is not complete upon generating software risk numbers or matrix plots. API RP 580 mandates a formal, documented review and approval process. Key team members and plant management must explicitly review, validate, and sign off on all risk rankings, damage mechanism assessments, and RBI-derived inspection plans prior to field implementation.

1. Consensus-Based Decision-Making Protocols

Because an RBI team comprises individuals with distinct technical backgrounds, differences of opinion frequently arise regarding degradation rates, cracking susceptibilities, or process upset severity. API RP 580 establishes that team decisions should be driven by technical consensus grounded in empirical data and sound engineering judgment.

A. Resolving Technical Disagreements

When team members disagree on key data inputs—such as whether a corrosion rate should be estimated at 5 mils per year (mpy) or 15 mpy:

Data Gathering & Re-examination: The team must first review available historical inspection records, metallurgical literature, API 571 guidance, and operating data.

Conservative Bounding Assumptions: If data gaps or uncertainty persist, API RP 580 directs the team to adopt conservative assumptions (e.g., applying the higher estimated corrosion rate of 15 mpy) to ensure equipment integrity is not compromised.

Sensitivity Analysis: The Risk Analyst executes sensitivity runs to evaluate whether varying the disputed input significantly alters the final risk category or inspection interval.

Documenting Dissent & Rationale: The team must document the consensus rationale, the sensitivity results, and any dissenting technical opinions in the official RBI record.

2. Formal Review and Verification Workflows

Before an RBI assessment is submitted for management approval, it must undergo a multi-stage review process to verify data integrity and logical consistency. +-------------------------------------------------------------------+

  • | DRAFT ASSESSMENT CREATION |
  • | - Data collection (Process, Inspection, Metallurgy, Design) |
  • | - Initial POF / COF software runs & risk matrix plotting |
  • +-------------------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------------------+
  • | STAGE 1: TEAM DATA CHECK |
  • | - Inspector verifies thickness readings & past effectiveness |
  • | - Corrosion Specialist validates API 571 damage mechanisms |
  • | - Process Specialist validates stream compositions & IOW limits |
  • +-------------------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------------------+
  • | STAGE 2: TECHNICAL CONSENSUS MEETING |
  • | - Multidisciplinary team reviews risk matrix positions |
  • | - Evaluates risk drivers (POF dominant vs. COF dominant) |
  • | - Formulates risk-mitigating inspection plans & strategies |
  • +-------------------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------------------+
  • | STAGE 3: INDEPENDENT PEER REVIEW (OPTIONAL) |
  • | - Senior independent specialists audit high-risk item logic |
  • | - Verifies methodology compliance & boundary consistency |
  • +-------------------------------------------------------------------+
  • |
  • v
  • +-------------------------------------------------------------------+
  • | STAGE 4: FORMAL MANAGEMENT SIGN-OFF |
  • | - Equipment Inspector, Corrosion Specialist, Process Manager |
  • | - Asset Integrity / Operations Plant Leadership written sign-off |
  • +-------------------------------------------------------------------+
  • 3. Formal Approval Accountabilities by Role

API RP 580 requires explicit sign-offs from key discipline leaders to establish clear accountability.

Approver Role Primary Approval Accountability Key Questions Addressed Before Sign-Off

Equipment Inspector Inspection Intervals, NDE Methods, Baseline Data Are proposed inspection techniques capable of detecting identified damage? Are intervals practical under API 510/570 caps?

Corrosion Specialist Damage Mechanisms, Degradation Rates, IOW Limits Are all credible API 571 mechanisms identified? Are corrosion rate overrides technically justified? Are IOW boundaries correct?

Process / Operations Manager Operating Envelopes, Fluid Compositions, Isolation Do process stream compositions reflect actual operations? Can operations maintain conditions within defined IOW limits?

Asset Integrity / Plant Manager Risk Acceptance, Mitigation Budget, Resource Plan Does residual risk meet corporate ALARP criteria? Are capital resources approved for high-risk equipment mitigation?

4. Integration with Management of Change (MOC)

An RBI assessment represents a snapshot of risk based on specific operating and physical conditions. Changes to process chemistry, metallurgy, equipment configuration, or operating envelopes can instantly invalidate RBI results.

API RP 580 Section 15 mandates tight integration between the RBI program and the facility Management of Change (MOC) system:

MOC Triggers for RBI Reassessment:

Process Chemistry Changes: Alterations in crude oil slates (e.g., higher naphthenic acid or total acid number [TAN]), feed gas composition changes, or chemical neutralizer injection changes.

Operating Envelope Excursions: Operating outside established Integrity Operating Windows (IOWs) in temperature, pressure, or water dew point for extended durations.

Equipment Physical Modifications: Piping rerouting, vessel nozzle additions, alloy claddings, or installation of internal sleeves.

Service Re-assignment: Changing an equipment item from non-corrosive service to sour or corrosive service.

MOC Governance Rule: The MOC procedure must mandate that any process or physical change affecting an RBI-assessed unit requires formal notification to the RBI Team Leader and Corrosion Specialist for immediate risk reassessment prior to implementing the change.

5. Evergreening Ownership and Life-Cycle Sustainment

Evergreening is the continuous process of updating an RBI assessment as new inspection data, process changes, or equipment history become available.

A. Ownership of Evergreening

The owner-user organization must assign explicit long-term ownership for evergreening. Typically, the Asset Integrity Manager or Plant Inspection Supervisor is designated as the RBI Owner.

B. Mandatory Reassessment Triggers

API RP 580 specifies four mandatory triggers that require updating an RBI assessment:

Post-Turnaround / Inspection Results: Following a plant turnaround or major inspection campaign, new wall thickness measurements, crack inspection results, and updated damage findings must be incorporated into the RBI model to update POF values.

Elapsed Calendar Time: Even in stable units, RBI assessments must undergo periodic updates (typically every 3 to 5 years) to account for cumulative corrosion, aging, and minor operational drift.

MOC Events & Process Excursions: Significant process changes or sustained IOW exceedances require immediate model updating.

Equipment Failure or Near-Miss Events: Any unexpected leak, rupture, or accelerated degradation event within the facility or similar industry units triggers an immediate review of damage mechanism assumptions across all affected equipment circuits.