10.2 Reassessment Triggers: Periodic Updates, MOC Events, Out-of-Limit Operations, and Inspection Results
Key Takeaways
- API RP 580 mandates that RBI assessments are dynamic 'evergreen' processes requiring formal reassessment at defined maximum time intervals (typically every 3-5 years in industry practice; within 10 years when RBI extends API 510/570 code inspection intervals) or immediately upon critical triggering events.
- Inspection results serve as a primary reassessment trigger, where newly acquired field thickness data, cracking findings, or non-destructive examination (NDE) effectiveness updates drive Bayesian updating of Damage Factors (Df) and Probability of Failure (PoF).
- Management of Change (MOC) workflows must directly interface with the RBI system to trigger reassessments whenever equipment design, process chemistry, metallurgy, or operating envelopes are altered.
- Out-of-limit process operations, including excursions beyond Integrity Operating Windows (IOWs per API RP 584) or unexpected fluid contamination, require immediate RBI re-evaluation to adjust corrosion rates and damage susceptibility.
- Post-incident investigations, physical equipment repairs/alterations, or unexpected damage discovery on duplicate equipment lines automatically mandate unit-wide RBI reassessment to prevent systemic failure.
10.2 Reassessment Triggers: Periodic Updates, MOC Events, Out-of-Limit Operations, and Inspection Results
A Risk-Based Inspection (RBI) assessment is not a static, one-time study; it is an iterative, dynamic process known as Evergreening. Under API RP 580 (4th Edition, Section 15), an RBI evaluation reflects equipment risk at a specific snapshot in time based on known operating conditions, historical inspection findings, and damage mechanism assumptions. Over time, process units age, operating parameters fluctuate, feedstocks change, equipment undergoes repairs, and field inspections generate new physical data. Failing to update an RBI model as conditions evolve renders the risk rankings obsolete and can lead to unmitigated safety hazards or unnecessary inspection expenditures.
API RP 580 Section 15 mandates that plant management establish formal procedures defining when and how RBI assessments must be updated. Reassessment triggers fall into four primary categories: Periodic (Time-Based) Reviews, Inspection & NDE Feedback, Management of Change (MOC) Events, and Out-of-Limit Process Excursions (IOW Triggers).
Categorization of Reassessment Triggers
+-----------------------------------------------------------------------------------+
| API RP 580 REASSESSMENT TRIGGERS |
+------------------------------------+----------------------------------------------+
| Trigger Category | Specific Operational Event / Criteria |
+------------------------------------+----------------------------------------------+
| 1. Periodic (Time-Based) | Typical 3-5 year review cycle; 10-year code |
| | revalidation cap when RBI extends intervals |
| 2. Inspection & NDE Feedback | Field NDE completion (wall loss / cracking) |
| | Bayesian revision of PoF & Damage Factor Df |
| 3. Management of Change (MOC) | Feedstock change (high sulfur / crude acid) |
| | Physical alteration, piping rerun, re-lining |
| 4. Operational Excursions (IOWs) | Critical / Standard IOW limit breach |
| | Chemical contamination (chloride / amine) |
+------------------------------------+----------------------------------------------+
1. Periodic (Time-Based) Reassessment Rules
API RP 580 Section 15 states that even in the absence of obvious operational changes or inspection findings, an RBI assessment must undergo a comprehensive periodic review. Over time, gradual degradation, atmospheric exposure, and subtle operational creep accumulate.
- Code Revalidation Cap: When an RBI assessment is used to extend inspection intervals beyond code defaults, API 510 and API 570 require the RBI assessment to be reviewed and revalidated at intervals not exceeding 10 years, or more often if warranted by process, equipment, or consequence changes. In industry practice, most owner-users schedule comprehensive RBI reviews every 3 to 5 years, aligned with major turnaround cycles and jurisdictional requirements.
- Turnaround Cycle Alignment: In practice, process plants schedule major RBI reassessments 12 to 18 months prior to a scheduled major unit turnaround (TA). This timing ensures that updated risk rankings directly inform the turnaround inspection work scope.
2. Inspection Feedback and Bayesian Updating
Field inspection results represent the single most important empirical validation of an RBI model. API RP 580 Section 15 mandates that whenever a field inspection is executed, the resulting NDE data must be fed back into the RBI software to perform Bayesian Updating of the time-dependent Damage Factor ($D_f$) and Probability of Failure ($ ext{PoF}$).
Mathematical Principles of Bayesian Revision
Before an inspection, the probability distribution of damage is based on historical models (Prior PoF). When NDE is performed with a known effectiveness category (API 581 Category A, B, C, D, or E), Bayes' Theorem updates the probability distribution to yield a Posterior PoF:
- Confirmation of Low Damage (Positive Feedback): If a Category A (Highly Effective) ultrasonic grid scan reveals negligible metal loss, Bayesian updating reduces the uncertainty factor in the corrosion rate model, significantly lowering the Damage Factor ($D_f$) and extending the Next Inspection Date (NID).
- Discovery of Unexpected Damage (Negative Feedback): If inspection uncovers localized pitting, micro-cracking, or corrosion rates exceeding baseline predictions, $D_f$ increases immediately, causing an upward spike in risk and accelerating future inspection deadlines.
- Null Results in Cracking Inspections: Finding no cracks using a Category A NDE method (e.g., PAUT for Wet $\text{H}_2\text{S}$ cracking) reduces the cracking Damage Factor by validating the effectiveness of environmental controls.
3. Management of Change (MOC) Events
Process safety regulations require plants to maintain a Management of Change (MOC) workflow for all physical, chemical, metallurgical, and organizational alterations. API RP 580 Section 15 mandates that the MOC procedure must include a mandatory screening checkpoint requiring sign-off from the RBI team prior to implementing changes.
Key MOC events that automatically trigger an immediate RBI reassessment include:
- Feedstock & Chemical Shift: Introduction of high-naphthenic acid crudes, higher sulfur gas oil feeds, increased chloride concentrations in reformer feeds, or oxygen ingress into amine systems.
- Operating Envelope Alterations: Increases in operating pressure, temperature increases bringing carbon steel into the High-Temperature Hydrogen Attack (HTHA) range ($>400^\circ\text{F}$ in $\text{H}_2$ service per Nelson curves), or flow velocity increases causing Flow-Assisted Corrosion (FAC).
- Metallurgical & Physical Modifications: Replacement of carbon steel piping with 316L stainless steel (which eliminates sulfidic corrosion but introduces Chloride SCC susceptibility), installation of internal strip lining, or removal of thermal insulation.
4. Operational Excursions and Integrity Operating Windows (IOWs)
Under API RP 584 (Integrity Operating Windows), process parameters critical to asset integrity are bounded by established operating limits (Critical, Standard, and Informational IOWs). Operating outside these limits accelerates physical degradation.
When a process excursion breaches an established IOW limit, an Out-of-Limit Operational Trigger is activated. The table below highlights how specific IOW excursions alter damage mechanisms and necessitate RBI reassessments:
| Process Variable | IOW Limit Type | Excursion Event | Impact on RBI Risk Model | Required Reassessment Action |
|---|---|---|---|---|
| Desalter Salt Outlet | Critical IOW | Chloride content exceeds $10\text{ ptb}$ for $>48\text{ hours}$ | Accelerated $\text{HCl}$ dew-point corrosion in crude column overhead piping | Re-calculate thinning corrosion rate; update PoF; shorten NID |
| Amine Solution Temperature | Standard IOW | Temperature exceeds $160^\circ\text{F}$ in un-PWHT piping | Initiates Amine Stress Corrosion Cracking (ASCC) mechanism | Activate ASCC cracking module; schedule PAUT / WFMT inspection |
| Hydrotreater Bed Temp | Critical IOW | Temperature spike $>800^\circ\text{F}$ during reactor runaway | Accelerates hydrogen embrittlement and creep strain damage | Conduct high-temperature creep & HTHA damage factor re-evaluation |
| Wash-Water Injection Flow | Critical IOW | Water injection rate drops below $5\text{ gpm}$ minimum | Ammonium bisulfide ($\text{NH}_4\text{HS}$) salt crystallization and severe localized erosion-corrosion | Re-assess localized thinning DF; inspect injection point mixing tees |
Worked Technical Example: Reassessment Triggered by IOW Chloride Excursion
Baseline Conditions
A 304L stainless steel overhead condenser piping circuit in a hydrocracker fractionator unit was assessed in 2024. The baseline operating temperature was $140^\circ\text{F}$ with zero water phase condensation. Chloride SCC was screened as Inactive, resulting in a low probability of failure ($\text{PoF} = 1.2 \times 10^{-4} / \text{year}$) and a scheduled NID of 2032 (8-year interval).
Trigger Event & Reassessment Execution
In March 2026, an upstream wash-water pump failed, causing a 72-hour process excursion where water condensed in the overhead circuit containing $150\text{ ppm}$ soluble chlorides (breaching the Critical IOW limit of $<10\text{ ppm}$ chlorides).
- MOC / IOW Trigger: The plant IOW monitoring system automatically flagged the excursion and notified the RBI team.
- Damage Mechanism Re-Screening (API RP 571): Chloride Stress Corrosion Cracking (Cl-SCC) was re-classified from Inactive to Active & Severe due to the combination of tensile residual stress, austenitic stainless steel metallurgy, $140^\circ\text{F}$ temperature, and liquid water with high chlorides.
- Model Re-run: The Cl-SCC Damage Factor increased from $D_f = 1$ to $D_f = 120$. Mitigated PoF spiked from $1.2 \times 10^{-4}$ to $1.4 \times 10^{-2} / \text{year}$. Total financial risk jumped to $$185,000 / \text{year}$, breaching the company's risk limit of $$50,000 / \text{year}$.
- Revised Inspection Plan: The NID was immediately updated from 2032 to Q3 2026, specifying 100% Pulsed Eddy Current (PEC) screening and Dye Penetrant (PT) examination at all circumferential welds.
When an RBI assessment is used to extend equipment inspection intervals beyond API 510/570 code defaults, what is the maximum time interval at which the RBI assessment must be formally reviewed and revalidated?
How does newly acquired field inspection data act as a reassessment trigger under API RP 580?
What role do Integrity Operating Windows (IOWs), as defined in API RP 584, play in triggering an RBI reassessment?