2.3 Management of Change (MOC) Integration and Life-Cycle Sustainment

Key Takeaways

  • API RP 580 mandates that RBI programs integrate directly with the facility Management of Change (MOC) system to evaluate physical, operational, and feedstock changes prior to execution.
  • MOC triggers for RBI reassessment include crude slate modifications, material substitution, injection point additions, inhibitor dosing changes, and operating parameter shifts.
  • RBI evergreening requires continuous life-cycle updating through both scheduled periodic reviews (typically every 3–5 years) and out-of-cycle event-driven reassessments.
  • Out-of-cycle reassessment triggers include NDE findings of unexpected degradation, IOW excursions, equipment leaks, and updates to inspection codes or industry damage standards.
Last updated: August 2026

2.3 Management of Change (MOC) Integration and Life-Cycle Sustainment

A Risk-Based Inspection (RBI) assessment is not a one-time engineering deliverable; it is a dynamic, living asset integrity program. Under API RP 580 Section 15 and Section 16, maintaining long-term program validity requires seamless integration with the facility's Management of Change (MOC) process and an ongoing life-cycle sustainment strategy known as evergreening. Without robust MOC integration and structured reassessments, an RBI program rapidly degenerates into an obsolete document, creating unmitigated process safety risks and regulatory compliance vulnerabilities.


Integration of Management of Change (MOC) with RBI

Process safety management regulations (e.g., OSHA 29 CFR 1910.119) mandate that facilities control physical, operational, and organizational changes through a formal MOC process. API RP 580 requires that the RBI management system be fully embedded into the plant MOC workflow. Any proposed modification capable of altering equipment degradation rates, damage mechanism susceptibility, or release consequences must undergo an RBI MOC review prior to engineering approval and field implementation.

Physical and Design MOC Triggers

Physical modifications directly alter equipment stress states, flow dynamics, or local corrosion environments:

  • Material of Construction (MOC) Substitutions: Substituting specified alloys (e.g., installing carbon steel components in place of 316L stainless steel due to procurement delays) can introduce severe un-monitored corrosion or environmental cracking risks.
  • Piping Modifications and Tie-Ins: Adding new process piping circuits, hot taps, bypass lines, or deadlegs alters flow regimes and creates localized degradation traps.
  • Injection Point Additions: Installing new chemical injection points (e.g., wash water, neutralizer, or corrosion inhibitor quenches) introduces extreme localized corrosion potential, requiring immediate creation of dedicated piping inspection circuits.
  • Insulation Modifications: Adding, removing, or changing insulation systems impacts operating temperatures and introduces potential Corrosion Under Insulation (CUI) hazards.

Process and Operational MOC Triggers

Process variations frequently alter fluid corrosivity without changing physical equipment geometry:

  • Feedstock and Crude Slate Changes: Processing higher-sulfur crudes, high Total Acid Number (TAN) Opportunity Crudes, or feeds with elevated organic chlorides accelerates sulfidation and naphthenic acid corrosion.
  • Throughput Expansions and Debottlenecking: Increasing flow velocities elevates erosion-corrosion and liquid droplet impingement risks while shortening fluid retention times in wash systems.
  • Chemical Treatment Alterations: Changing inhibitor formulations, altering neutralising amine dosing, or suspending water wash systems directly impacts corrosion rates.
  • Operating Envelope Parameter Shifts: Permanently elevating operating temperatures into the High-Temperature Hydrogen Attack (HTHA) or creep regime, or lowering operating temperatures below ductile-to-brittle transition thresholds.

Life-Cycle Sustainment and "Evergreening" Workflows

API RP 580 defines evergreening as the continuous, iterative updating of the RBI assessment throughout the asset life cycle. Evergreening ensures that the inspection plan continuously reflects current mechanical condition, recent operational history, and updated risk modeling algorithms.

Scheduled Periodic Reassessments

API RP 580 mandates routine periodic RBI reassessments at defined intervals. Facilities typically conduct comprehensive RBI reviews:

  • Every 3 to 5 years, aligning with plant risk management cycles.
  • Prior to Major Turnarounds (TAR), ensuring turnarounds focus NDE work packs exclusively on high-risk assets requiring internal inspection or non-intrusive advanced NDE.

Event-Driven Out-of-Cycle Reassessments

In addition to scheduled reviews, specific operational or inspection events mandate immediate, out-of-cycle RBI reassessments:

  1. Inspection and NDE Findings: When NDE during turnarounds or routine monitoring reveals corrosion rates significantly exceeding predictions, localized pitting, or environmental cracking (e.g., wet H2S cracking), the RBI model must be updated immediately. The revised corrosion rate recalculates the Probability of Failure (POF), while past inspection effectiveness ratings are updated to reflect the new NDE data.
  2. Process Excursions and IOW Breaches: Sustained or severe parameter breaches beyond Critical Integrity Operating Windows (IOWs)—such as thermal excursions or acid dew point condensation—require an out-of-cycle risk assessment to evaluate potential cumulative damage.
  3. Equipment Leaks, Failures, or Industry Incidents: Any containment loss event within the unit, sister facilities, or industry alerts (e.g., API safety bulletins regarding HTHA or ammonium bisulfide corrosion) requires immediate review of similar equipment circuits.
  4. Equipment Repairs, Rerating, or Replacement: Post-turnaround physical repairs, weld overlays, or component replacements alter baseline damage factors and reset inspection timers.

Re-Evaluating Inspection Effectiveness and Audit Trail Documentation

A vital component of evergreening is updating the Inspection Effectiveness levels (Categories A through E under API RP 581) based on newly completed NDE:

  • Category A (Highly Effective): Performing thorough, high-coverage NDE (e.g., 100% Phased Array UT or intrusive visual inspection by certified API inspectors) confirms damage presence/absence with high statistical confidence, significantly reducing structural damage factor uncertainty in POF calculations.
  • Category E (Ineffective): Inadequate NDE methods or insufficient surface preparation provide no confidence, preventing POF reduction.

Maintaining Audit Trail Documentation

API RP 580 Section 16 mandates that all RBI reassessments, MOC evaluations, risk adjustments, and inspection plan modifications maintain a clear, audit-ready technical rationale. Documentation must be archived in a centralized Asset Integrity Management (AIM) database including:

  • Approved RBI team member sign-offs and meeting minutes.
  • Updated POF/COF calculation sheets and risk matrix plots.
  • Documented technical justification for inspection interval extensions, deferrals, or non-inspection mitigation decisions.
  • Comprehensive audit records proving regulatory compliance during API 510/570/653 facility audits.
Test Your Knowledge

Which event represents an operational change that MUST trigger an immediate MOC-driven RBI reassessment under API RP 580 guidelines?

A
B
C
D
Test Your Knowledge

What term describes the continuous, iterative life-cycle process of updating RBI risk models with new inspection findings, process data, and MOC records?

A
B
C
D
Test Your Knowledge

How should an RBI team respond when NDE during a scheduled turnaround reveals wall thinning significantly exceeding the predicted corrosion rate?

A
B
C
D