Many RBI programs are technically strong at the time they are created, but can become outdated if process conditions change and the RBI model is not updated. Integrity Operating Windows (IOWs) help bridge the gap between operations and integrity management by identifying the operating variables that control damage mechanisms.
A well-designed RBI program at commissioning may become unreliable over years of operation if process changes โ in chemistry, temperature, water content, or flow regime โ quietly invalidate the original damage mechanism assumptions.
What Are Integrity Operating Windows?
IOWs are defined ranges or limits for process variables that, if exceeded, may affect equipment integrity by changing damage mechanism susceptibility, corrosion rate, cracking risk, fouling, thermal cycling, pressure protection risk, or other integrity-related behaviour.
IOWs are different from routine process control limits. Process alarms may focus on production stability or safety trips, while IOWs focus on long-term equipment integrity and degradation control.
Why RBI Needs IOWs
RBI is built on assumptions about process chemistry, temperature, pressure, flow regime, water content, contaminants, corrosive species, inhibitor performance, operating duty, start-up/shutdown frequency, and relief scenarios. When these assumptions change, PoF and inspection planning may no longer be valid.
Examples of IOW Variables
- Water cut or free water presence โ changes from dry to wet service dramatically affects corrosion risk
- pH โ controls H2S corrosion, amine corrosion, and carbonate cracking susceptibility
- H2S and CO2 partial pressures โ affect SOHIC, HIC, SSC, and wet corrosion rates
- Chloride concentration โ affects stainless steel SCC risk and carbon steel pitting
- Temperature โ affects CUI susceptibility ranges, creep, HTHA, and coating performance
- Flow velocity โ affects erosion-corrosion risk at elbows, injection points, and tees
- Oxygen ingress โ affects MIC and general corrosion rates in water-containing systems
- Inhibitor residual โ affects corrosion rate protection in corrosive service
- Operating pressure โ affects PSV set pressure margin, relief demand, and fatigue
IOW Exceedance Response
When an IOW limit is approached or exceeded, a defined engineering response should be triggered: review of the damage mechanism assumptions in the RBI model, update of corrosion rate estimates, review of the inspection plan and intervals, acceleration of specific inspections where risk may have increased, process correction or mitigation, and formal management of change documentation where operating conditions change permanently.
IOWs and CUI Management
For CUI programs, operating temperature changes, shutdown frequency, and insulation system condition directly affect CUI susceptibility. Facilities that increase shutdown/start-up frequency or extend ambient temperature exposure may require updated CUI risk ranking even if no significant equipment changes have occurred.
Integration with RBI Evergreening
IOWs should be formally linked to the RBI evergreening process. When IOW exceedances are recorded, the RBI model should be reviewed and updated. This ensures the integrity management program remains defensible as operating conditions evolve.
TES Canada integrates IOW development into RBI and integrity program design. We help clients identify which operating variables control active damage mechanisms and define appropriate IOW limits, monitoring requirements, and response protocols.
Standards & References
- API RP 580 โ Risk-Based Inspection โ Integrity Operating Windows
- API RP 581 โ Risk-Based Inspection Methodology
- API 571 โ Damage Mechanisms Affecting Fixed Equipment
- API 584 โ Integrity Operating Windows
- API 570 โ Piping Inspection Code
Need support with this type of technical challenge?
TES Canada can help you assess the issue, select the right inspection or engineering approach, and develop a practical integrity management solution.
Contact TES Canada โ