Consulting for Damage Mechanism Screening Per API 571

Damage Mechanism Screening Is the Step Most Inspection Plans Skip — and API 571 Is the Reference That Catches It

Ask most inspection departments how they decide what to inspect and how often, and the honest answer is usually some version of "the same way we did it last turnaround, plus whatever the last incident taught us." API 571, Damage Mechanisms Affecting Fixed Equipment in the Refining Industry, exists to replace that instinct-driven approach with a structured screening process: for every piece of equipment, systematically identify which of the roughly 60-plus damage mechanisms catalogued in the standard are actually credible given the metallurgy, process environment, and operating history, and use that list — not habit — to drive NDT method selection and inspection interval.

This matters because different damage mechanisms require fundamentally different inspection approaches, and picking the wrong one doesn't just waste a turnaround day, it can mean walking past active damage. Sulfidation and wet H2S cracking don't look the same, don't behave the same, and don't get found by the same NDT technique. A screening process that lumps "corrosion" into one generic bucket and applies one generic UT thickness survey will miss the mechanisms that don't manifest as uniform wall loss — which is most of the dangerous ones.

What Damage Mechanism Screening Actually Involves

A proper API 571 screening exercise starts with a materials and process review for each equipment item: base metal and weld metal composition, operating temperature and pressure ranges (including upset conditions, not just normal operation), process stream composition (sulfur content, hydrogen partial pressure, chloride content, presence of naphthenic acids, amine concentration, and so on), and equipment history including any prior repairs, weld overlays, or metallurgical changes. That data gets cross-referenced against API 571's mechanism tables to build a credible damage mechanism list per equipment item — typically three to eight mechanisms are credible for any given vessel or piping circuit, out of the much larger universe the standard describes.

Why "corrosion" is not a damage mechanism

One of the most consistent gaps we find in consulting engagements is inspection scopes written against generic categories — "internal corrosion," "external corrosion" — rather than named mechanisms with known behavior. API 571 forces specificity: is it high-temperature sulfidation (Section 4.1 mechanisms, governed by sulfur content and temperature, typically becoming significant above roughly 500°F/260°C depending on alloy), is it naphthenic acid corrosion (highly velocity- and temperature-dependent, concentrated in specific piping geometries like elbows and reducers), is it amine cracking in a sour water stripper overhead system, or is it CO2/H2S wet corrosion in a sour water system operating below the dew point? Each of these has a different inspection signature, a different set of susceptible locations on the equipment, and a different NDT technique that actually detects it reliably.

Matching NDT Technique to Damage Mechanism

This is where damage mechanism screening earns its keep operationally — it directly drives which method gets used where, instead of a default UT thickness survey applied uniformly:

• High-temperature hydrogen attack (HTHA): conventional UT thickness gauging won't reliably detect early-stage HTHA because it doesn't cause measurable wall loss until advanced — advanced UT backscatter techniques or wet fluorescent MT after grinding, combined with API 941 Nelson curve review of operating temperature/hydrogen partial pressure, are the appropriate screen.
• Wet H2S cracking (SSC, HIC, SOHIC): wet fluorescent MT for surface-breaking cracking, and angle-beam UT or phased array specifically configured for HIC/SOHIC detection (not standard thickness-gauging UT setups) for subsurface stepwise cracking in susceptible carbon steel.
• Sulfidation thinning: conventional UT thickness gauging is appropriate, but CML placement must target high-velocity and high-turbulence locations (elbows, tees, reducers) where sulfidation accelerates, not just straight-run pipe.
• Caustic stress corrosion cracking: wet fluorescent MT or PT at known susceptible locations — typically at or near welds in caustic service without adequate post-weld heat treatment — rather than general UT survey.
• Chloride stress corrosion cracking (austenitic stainless steel): PT is the standard surface method, but insulated stainless piping needs the same CUI-style risk-zone thinking layered in, since chloride SCC frequently initiates under wet insulation.
• Creep damage in high-temperature piping and headers: replication metallography combined with dimensional/diameter surveys to detect bulging, rather than UT thickness alone, since creep damage manifests as microstructural void formation before measurable wall change.

Getting this match wrong is the single most common finding in our damage mechanism screening consulting engagements: technically competent NDT technicians running the wrong technique for the mechanism actually present, because the inspection plan was built around equipment type and general corrosion assumptions rather than a documented mechanism screen.

The upset-condition blind spot

Screening based purely on normal operating parameters misses a recurring failure pattern: a process unit that experienced a temperature or contaminant excursion — a feedstock change that temporarily raised sulfur content, an amine system upset that concentrated corrosive species, a startup/shutdown cycle that passed equipment through a susceptible temperature window it doesn't normally see — can introduce or accelerate a damage mechanism that wasn't credible under steady-state operating conditions. A rigorous API 571 screen reviews operating history and known upsets, not just the design basis and current normal operating envelope, specifically because the design basis often understates what the equipment has actually been exposed to over its service life.

Who Should Actually Perform the Screening

API 571 assumes the screening exercise is performed or reviewed by someone with genuine metallurgical and process background — not necessarily a metallurgist by title on every engagement, but someone who understands why a given alloy behaves differently under a given process condition, and who can read a corrosion loop diagram and process flow data with enough fluency to catch inconsistencies. In practice, we see three staffing models across the industry: a dedicated in-house materials/corrosion engineer who owns the screening for the whole facility (most common at larger integrated refineries), a rotating responsibility split across inspection and reliability engineers with metallurgy backgrounds (common at mid-size facilities), and, more often than either of those, screening that was performed once by a contractor during initial RBI program implementation years ago and has effectively had no dedicated owner since. That third pattern is the one that produces the stale, unrefreshed mechanism lists we most often find during consulting reviews.

The Level III's role versus the metallurgist's role

It's worth being precise about where an ASNT Level III's expertise fits into this process versus where a metallurgist's does. A Level III brings deep knowledge of NDT method capability and limitation — exactly which technique can and cannot reliably detect a given mechanism, at what sensitivity, under what access constraints — which is the piece that translates a metallurgist's mechanism list into an actual, executable inspection plan. The metallurgist or corrosion engineer brings the process chemistry and materials science judgment that identifies which mechanisms are credible in the first place. A screening engagement that has only one of those two perspectives tends to produce either a technically sound mechanism list that never gets translated into a workable inspection technique matrix, or an inspection plan built around techniques that are readily available rather than techniques actually capable of finding the mechanism in play. Combining both perspectives is where a consulting engagement adds the most value over either discipline working in isolation.

Integrating Damage Mechanism Screening Into RBI

Damage mechanism identification is the direct input to the probability-of-failure side of an API 580/581 risk-based inspection program — you cannot build a defensible RBI ranking without first knowing which mechanisms are credible for each equipment item, because probability of failure calculations are mechanism-specific (a generalized corrosion model produces a completely different risk profile than a stress corrosion cracking model applied to the same vessel). Facilities that skip formal damage mechanism screening and go straight to assigning RBI risk categories based on equipment type and age are building their entire inspection interval structure on an unverified assumption about what's actually attacking the metal.

We consistently find this gap during consulting engagements: an RBI program that's been running for years, technically compliant with API 580 process steps on paper, but where the underlying damage mechanism assignments were done once during initial implementation and never revisited as process conditions, feedstocks, or catalysts changed. Refining feedstock slates in particular can shift meaningfully over a five-to-ten-year window — increased opportunity crude processing, for example, often means higher and more variable sulfur and naphthenic acid content than the original design basis assumed — and a damage mechanism screen that isn't refreshed against current feed data is quietly drifting out of date.

Building a Defensible Screening Record

An auditor or a corporate reliability review doesn't just want to see the final mechanism list — they want to see the reasoning trail: what process data was reviewed, which API 571 sections were consulted, why mechanisms were included or excluded, and who (ideally a metallurgist or Level III-qualified reviewer with damage mechanism expertise) signed off. A mechanism list with no documented reasoning is functionally the same as no screening at all from an audit-defensibility standpoint, even if the list itself happens to be correct.

Part of what a consulting engagement delivers here is that documentation structure — a repeatable template for how mechanism screening gets performed, recorded, and refreshed, rather than a one-time exercise that becomes stale the moment operating conditions shift. For facilities running this across dozens or hundreds of equipment items, keeping the mechanism list, the linked NDT technique assignment, and the CML history connected to the same asset record — rather than scattered across an RBI software export, a metallurgist's memo, and an inspection contractor's report — is exactly the kind of consolidation a system like Atlantis NDT ERP is built to handle, tying damage mechanism data directly to the inspection scheduling and technician assignment for that equipment.

Where Screening Errors Actually Cost Facilities

The financial and safety cost of a damage mechanism screening gap rarely shows up as an immediate incident — it shows up as either over-inspection (spending turnaround time and budget on UT surveys for mechanisms that aren't actually credible, because nobody ever screened them out) or under-inspection (missing the mechanism that's actually active because the inspection plan defaulted to generic corrosion assumptions). Both are expensive in different ways: the first wastes turnaround time that's almost always the tightest constraint in a planning cycle, and the second creates the kind of exposure that turns into an incident investigation. A facility running a sizable RBI-managed equipment population can easily be carrying a mechanism screening gap on a meaningful share of that population without anyone having explicitly verified it — not because the inspection team is careless, but because nobody assigned ownership of keeping the screen current against evolving process data.

Revalidating a Screen After a Repair or Metallurgical Change

A screen that was accurate the day it was built can become wrong the moment a repair changes the equipment's metallurgy without anyone updating the mechanism list to match. A common scenario: a vessel originally fabricated in carbon steel receives a weld overlay of a corrosion-resistant alloy in a localized area after an earlier thinning finding, but the damage mechanism screen and the associated NDT technique matrix are never revisited to reflect that the overlay zone now has a different — and in some cases new — set of credible mechanisms (dissimilar metal weld cracking at the overlay-to-base-metal transition, for instance, is not a mechanism the original carbon steel screen would have flagged). The inspection plan continues treating the entire vessel as if it were still homogeneous carbon steel, which means the overlay zone, arguably now the highest-attention area on the vessel, gets the same generic technique as everywhere else.

The same logic applies to process changes that fall short of a full unit revamp: a new catalyst formulation, a debottlenecking project that shifts flow velocities and therefore erosion-corrosion risk at specific geometries, or a change in crude slate that alters sulfur and chloride loading. None of these show up automatically in an existing RBI risk ranking unless someone explicitly re-runs the damage mechanism screen against the new operating reality. Building a trigger list — repairs, metallurgical changes, process changes, and a maximum revalidation interval regardless of whether anything obviously changed — into the facility's management of change (MOC) procedure is the most reliable way we've seen to keep screening current without relying on someone remembering to flag it.

What a Damage Mechanism Screening Engagement Delivers

A structured engagement produces a documented, mechanism-specific screen for each equipment item or logical grouping, cross-referenced against current (not historical) process data; a technique-matching matrix connecting each credible mechanism to the appropriate NDT method and inspection location; identification of any equipment where current inspection practice doesn't match the mechanisms actually present; and a refresh protocol so the screen gets revisited when feedstock, catalyst, or operating envelope changes rather than sitting static for a decade. Combined with a properly scoped ASNT Level III consulting review of the NDT procedures themselves, this closes the loop between "we know what's attacking the metal" and "we're actually looking for it with a technique capable of finding it" — which is the entire point of API 571 existing as a standard in the first place.

Atlantis NDT Products & Services

Atlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.