3.3 Team Decision Ownership, Review, and Approval Responsibilities

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:

1. Data Gathering & Re-examination: The team must first review available historical inspection records, metallurgical literature, API 571 guidance, and operating data.
2. 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.
3. Sensitivity Analysis: The Risk Analyst executes sensitivity runs to evaluate whether varying the disputed input significantly alters the final risk category or inspection interval.
4. 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.

---

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:

1. 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.
2. 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.
3. MOC Events & Process Excursions: Significant process changes or sustained IOW exceedances require immediate model updating.
4. 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.