AMPP ICS common mistakes
AMPP ICS · Understand the traps and how to avoid them.
Treating CO2 corrosion as a single mechanism and predicting corrosion rate from partial pressure alone, ignoring the effect of in-situ pH, temperature, and protective iron carbonate scale formation.
Candidates memorize simple CO2 partial pressure rules of thumb and apply them without checking whether conditions favor or prevent FeCO3 scale, which dominates real field behavior.
What to do instead
For each CO2 case, explicitly work through pH, temperature, flow regime, and scale tendency before selecting a corrosion rate or mitigation; state whether conditions are scale-forming or scale-destructive.
Conflating H2S-related mechanisms (sour corrosion, sulfide stress cracking, hydrogen-induced cracking) and applying the wrong damage morphology or mitigation.
All three are grouped under 'sour service', so candidates apply a generic sour answer rather than distinguishing general metal loss from cracking mechanisms that require different controls.
What to do instead
Classify the threat first: uniform/localized metal loss (sour corrosion) versus cracking (SSC/HIC/SOHIC), then match mitigation and inspection method to the specific mechanism.
Assuming higher flow always means higher corrosion, or ignoring flow regime and velocity when assessing erosion-corrosion and under-deposit attack.
Velocity effects are nonlinear: low flow promotes deposition and under-deposit corrosion while high flow removes scales and causes erosion-corrosion, so a monotonic assumption produces wrong predictions.
What to do instead
Evaluate the actual flow regime and identify whether the system is in a deposition-prone or scale-removal/erosion-prone velocity range before predicting damage location and rate.
Ignoring the interaction of operating variables (temperature, pressure, water cut, gas composition, oxygen ingress) and analyzing each in isolation.
Corrosion is driven by combined conditions; candidates assess one variable at a time and miss synergistic effects like oxygen ingress accelerating CO2 attack or water dropout at low spots.
What to do instead
Build a combined operating-condition picture for each location and explicitly assess interactions, especially where water accumulates and where oxygen or other contaminants can enter.
Underestimating field safety hazards such as H2S exposure, oxygen deficiency, and confined-space entry during monitoring and sampling activities.
Candidates focus on the corrosion mechanism and treat field activities as routine, neglecting toxic-gas and atmospheric hazards that drive personnel risk.
What to do instead
For any field activity, identify the specific hazards (H2S toxicity, oxygen deficiency, LEL, pressure) and state the controls: gas monitoring, permits, PPE, rescue provisions, and buddy systems.
Reading corrosion monitoring data (coupons, probes, UT) as a direct measure of wall-loss rate without accounting for probe sensitivity, response time, and representativeness.
Candidates accept a single data stream as ground truth, missing that ER/LPR probes have limitations and that coupons integrate over time while probes give instantaneous trends.
What to do instead
Cross-check multiple monitoring methods, account for each technique's response characteristics and limitations, and verify trends against inspection data before drawing conclusions.
Selecting a mitigation strategy (inhibitor, biocide, coating, material upgrade, dehydration) without matching it to the specific mechanism and environment.
Candidates default to a familiar option like inhibitor injection rather than mapping the control to the dominant mechanism, fluid chemistry, and operating envelope.
What to do instead
State the dominant mechanism first, then justify why the chosen mitigation addresses it, including compatibility, dosage/coverage, and any failure modes of the mitigation itself.
Proposing monitoring or design alternatives without addressing their limitations, coverage gaps, or the need for redundancy and verification.
Candidates treat an alternative design or monitoring tool as a complete solution and skip the assessment of what it cannot detect or where it fails.
What to do instead
For each alternative, describe coverage, blind spots, and how it will be verified or supplemented so the overall program still detects the target damage.
Jumping to a root cause (e.g., 'inhibitor failed') from a single observation without gathering and correlating evidence such as failure morphology, operating history, and monitoring records.
Candidates shortcut the failure analysis process and anchor on the first plausible explanation instead of systematically testing hypotheses.
What to do instead
Follow a structured process: characterize damage morphology, reconstruct operating history, compare against monitoring/inspection data, and rule out alternative mechanisms before concluding.
Treating the corrosion control program as static, omitting periodic review, record retention, and documentation that supports regulatory and legal compliance.
Candidates focus on technical measures and overlook program management elements like review cycles, change management, and auditable records required for compliance.
What to do instead
Include explicit program-management elements: defined review intervals, triggers for reassessment, record retention, and documentation that demonstrates compliance and supports decisions.