White PaperIntegrity Assessment

Corrosion Reassessment Depends on Evidence Continuity

Author
Dr. Howard Ku
Year
2026
Version
1.3.0
DOI
10.5281/zenodo.22797411

Abstract

Pipeline corrosion is not a one-time finding. A wall-loss indication, a cathodic-protection reading or a historical corrosion-growth rate represents only part of a changing integrity condition. The credibility of a corrosion conclusion depends on whether the supporting evidence about corrosion mechanism, protection state, service conditions, inspection trends, mitigation effectiveness and uncertainty remains current.

This white paper presents a series-specific Corrosion Evidence Reassessment Cycle for maintaining continuity between corrosion observations, integrity interpretation, mitigation and subsequent reassessment.

The cycle links several connected evidence domains:

threat mechanism — what physical or electrochemical process is believed to be driving corrosion;

protection and service state — including coating condition, cathodic protection, interference, fluid composition, water, solids, chemistry, flow and inhibition;

inspection and monitoring evidence — including ILI, NDT, surveys, probes, coupons, sampling and operating history;

growth interpretation — how repeated observations, sizing uncertainty, feature matching and changing conditions affect corrosion-growth assumptions;

mitigation evidence — whether repair, coating work, CP adjustment, interference control, cleaning, dehydration, inhibition or other actions demonstrably changed the relevant condition; and

reassessment — when changing operating, environmental, protection or inspection evidence requires the corrosion conclusion to be revisited.

The analysis draws on publicly available material from AMPP, API, PHMSA, DNV and ROSEN, including AMPP guidance on cathodic protection, API RP 1160, PHMSA corrosion-control and integrity-management material, DNV-RP-F116, and attributed industry corrosion-management resources.

A central proposition is that a corrosion conclusion remains credible only while the evidence supporting its mechanism, growth behaviour and protection or mitigation state remains current. When those conditions—or the evidential basis for them—change, reassessment is required.

The paper distinguishes corrosion detection from corrosion-cause understanding. Similar wall-loss morphology may arise from different mechanisms. External corrosion can involve coating defects, cathodic-protection performance, shielding, current distribution, electrical interference, soil or environmental change and stray-current effects. Internal corrosion can depend on water, chemistry, corrosive species, deposits, microbiological activity, temperature, velocity, flow regime and inhibitor performance.

For external corrosion, coating and cathodic protection should be treated as interacting barriers rather than independent checks. A single CP measurement does not describe an entire protection system, and modifications to the pipeline or surrounding infrastructure can alter the interference environment over time.

For internal corrosion, inspection results should be interpreted alongside process and operating evidence. Historical absence of corrosion does not prove future immunity when service conditions change. Monitoring from coupons, probes, sampling, chemistry and operating indicators should therefore be triangulated against observed morphology and inspection results.

The paper also addresses corrosion-growth rates as conditional estimates rather than permanent asset properties. Growth estimates derived from repeated inspections can be affected by sizing uncertainty, feature matching, inspection technology and changing environmental or operating conditions. Both over-conservative and under-conservative conclusions can result when historical rates are treated as universally valid.

Mitigation is treated as an evidence-generating process. A closed work order demonstrates that an activity occurred; it does not by itself establish that the relevant corrosion mechanism has been controlled. Effective mitigation should therefore be followed by observable evidence appropriate to the threat, such as improved CP behaviour, stable monitoring indicators, reduced growth or verified repair condition.

The Corrosion Evidence Reassessment Cycle is a practitioner synthesis, not a new corrosion-management method, cathodic-protection criterion or universal corrosion-rate model. It does not replace AMPP, API, PHMSA, DNV, owner requirements, specialist corrosion judgement or project-specific engineering procedures.

The scope is deliberately limited to publicly discussable asset information, inspection, monitoring, analytical assurance and human engineering decision support. It does not specify proprietary mechanisms for authorising or executing consequential physical actions.

This paper forms No. 25 of the From Project to Live Asset — Independent Practitioner Research Series, Phase III, extending the wider steel-pipe lifecycle research programme from inspection-evidence reconciliation into continuing corrosion-state interpretation and reassessment.

Author-written abstract, reproduced from the authoritative Zenodo DOI record.

Why This Paper Exists

Examines why corrosion reassessment depends on the continuity of the underlying evidence.

Editorial orientation provided by DrKu.net. It is not part of the formal publication record; the authoritative abstract and metadata reside on the DOI record.

Lifecycle Position

Key Research Questions

  1. Has the asset condition changed?
  2. What evidence does this work contribute to the Integrity Assessment stage?

Derived cautiously from the verified paper content and its lifecycle position. They are not part of the formal publication record.

Applications

Citation

Howard, K. (2026). Corrosion Reassessment Depends on Evidence Continuity (Version 1.3.0). Zenodo. https://doi.org/10.5281/zenodo.22797411

Version Record

Current version
1.3.0
DOI
https://doi.org/10.5281/zenodo.22797411
Year
2026
Link to authoritative record

Boundary Note

This research does not replace applicable engineering codes, project specifications, regulatory requirements or competent engineering judgement.