Damage mechanisms
API 571: damage mechanisms, explained
API 571 is the American Petroleum Institute's recommended practice cataloguing the damage mechanisms that affect fixed equipment in the refining and petrochemical industries. For each mechanism it describes the affected materials, the critical process factors, the appearance of the damage, prevention and mitigation, inspection and monitoring methods, and related mechanisms. It is a reference, not an inspection code: it tells you what can happen and where to look, while API 510, 570, 653 and 580 decide the intervals and the program.
What the standard requires
Mechanism identification
For each item of equipment, the credible mechanisms are identified from material, process conditions and history using the API 571 descriptions. The mechanism list is the starting input to CML selection, inspection method choice and the probability side of RBI.
Critical factors
Each mechanism carries the process variables that control it, such as temperature thresholds, concentration, velocity, pH or water presence. Recording those factors per equipment item is how a mechanism moves from possible to credible.
Appearance and morphology
API 571 describes what the damage looks like, from general thinning to pitting, cracking, blistering or metallurgical change. That description tells the inspector which examination method can actually detect the mechanism, because a thickness gauge will not find a crack.
Inspection and monitoring methods
For every mechanism the practice lists the effective inspection and monitoring techniques. The inspection plan should cite the mechanism it is looking for and use a method that can find it; coverage without that link is not evidence.
Recording the mechanism with the finding
A defensible record ties each finding, each CML and each inspection to the mechanism that motivated it, and updates the mechanism list when a new one is found or a process change removes one.
What the record must carry
- Equipment identification, material of construction and process service
- Each credible damage mechanism named as API 571 names it
- The critical factors present that make the mechanism credible
- Expected morphology and the inspection method chosen to detect it
- CMLs and inspection tasks linked to the mechanism they address
- Findings attributed to a mechanism, with photos or readings
- Review history: who assigned the mechanism, when, and why it changed
How intelliSPEC handles it
Damage mechanisms are first-class records in intelliINTEGRITY, not a free-text field, so each mechanism is attached to the equipment with its critical factors and linked to the CMLs, inspection tasks and findings that address it. Those mechanism records feed the probability side of the API 580/581 semi-quantitative scoring, and the CUI wizard family in intelliINSPECT handles the mechanism API 571 treats as one of the most common: visual, suspect area, insulation removal, NDE UT, advanced NDE, repairs and recoat. Every assignment and change is signed and recorded in the hash-chained audit trail.
Answers
API 571 questions
What is API 571 used for?
API 571 is the reference for the damage mechanisms that affect refinery and petrochemical fixed equipment. Integrity engineers use it to decide which mechanisms are credible for each piece of equipment, which then sets where CMLs go, which inspection method is used, and what feeds the probability side of an RBI assessment.
Is API 571 an inspection code?
No. It is a recommended practice that describes mechanisms, their causes, appearance and detection methods. Intervals, qualifications and record requirements come from API 510, 570, 653 and 580. API 571 tells those programs what to look for.
How should damage mechanisms be recorded in an inspection system?
As structured records attached to the equipment, naming the mechanism as API 571 does, the critical factors present, and the inspection method chosen to detect it. Each CML, task and finding should link to the mechanism it addresses. A comment field that says 'possible CUI' cannot be queried, ranked or audited.
How does API 571 connect to RBI under API 580 and 581?
The probability of failure in an RBI assessment is built from the credible damage mechanisms and their rates or susceptibility. API 571 is where those mechanisms and their critical factors are defined, so the mechanism list per equipment item is the first input to the probability score.