What process do I need to follow to confirm an equivalent inspection technique?

To confirm an equivalent inspection technique in a defensible way, you need a structured, auditable process, not a technical opinion. The goal is to demonstrate that the alternate method provides equal or better risk reduction for the specific damage scenario under your Mechanical Integrity (MI) or RBI program. Below is a practical process aligned with good practices as outlined in the American Petroleum Institute's guidance (notably API 580 and API 581).

Step-by-Step Process to Confirm Equivalency 

Step 1 — Define the inspection objective (don’t skip this)

Document exactly what the inspection must accomplish. The required elements for this step should be:

• Equipment and component scope
• Active and credible damage mechanisms
• Required detection threshold (e.g., remaining life basis)
• Required coverage (area/volume)
• RBI effectiveness category or inspection credit
• Decision supported (interval extension, fitness-for-service, etc.)

Why this matters:
You cannot judge equivalence without a clearly defined performance requirement.

Step 2 — Establish the baseline method performance

Document the current (accepted) inspection method in measurable terms. Include:

• POD vs. flaw size
• Minimum detectable flaw
• Coverage achieved in practice
• Sizing accuracy
• Known limitations
• Historical field performance
• Assumed effectiveness in the RBI model 

Deliverable: Baseline effectiveness profile. Unfortunately, POD is not published widely for various techniques.

Step 3 — Perform a physics-based applicability review

Evaluate whether the alternate technique is fundamentally capable of detecting the same damage. Confirm:

• Sensitivity to the specific damage morphology
• Material compatibility
• Temperature and surface condition limits
• Geometry limitations
• Access requirements
• Detection mode (volumetric vs. surface vs. screening)

If the physics do not support the detection of the credible damage mechanism, stop — the methods are not equivalent. 

Step 4 — Compare probability of detection (POD)

This is the technical core of equivalency. You need POD information that is:

• Damage-mechanism specific
• Representative of field conditions
• At relevant flaw sizes
• Statistically defensible (e.g., 90/95 POD when available)

Evaluate:

• POD curves
• False negative risk
• Sensitivity to small defects
• Repeatability

 Common mistake: Using a vendor brochure POD not tied to the actual application. Unfortunately, there are few industry practices/papers to help support this effort.

Step 5 — Evaluate coverage and inspection effectiveness

Determine whether the alternative method actually inspects the same population of damage. Assess:

• Percent surface/volume coverage
• Ability to detect localized damage
• Performance in high-risk locations (supports, dead legs, nozzles)
• Scan vs. spot measurement differences
• Human factor sensitivity
• Field execution complexity 

Remember, many techniques that look equivalent in theory lose effectiveness in real plant conditions.

Step 6 — Compare sizing and trending capability

For RBI and remaining life decisions, detection alone is insufficient. Confirm the alternate method can:

• Measure wall loss accurately
• Size cracks (depth/length as required)
• Support corrosion rate calculations
• Support fitness-for-service if needed
• Provide repeatable trending data

If sizing quality is materially worse, equivalence usually fails.

Step 7 — Validate with evidence (not opinion)

You need objective support proportional to risk. Acceptable evidence (ranked strongest to weakest):

1. Blind validation trials on representative samples
2. Industry POD studies
3. Qualified performance demonstration
4. Documented field case histories
5. Engineering technical justification
6. Vendor claims (weakest alone) 

High-risk services should demand stronger validation.

Step 8 — Recalculate RBI impact

Do not assume equivalence; prove it in the model. Update the RBI inputs:

• Inspection effectiveness
• Confidence factors
• Coverage assumptions
• Detection limits
• Degradation rates are affected

Then verify:

• Risk remains within target
• Inspection interval remains justified
• No hidden risk increase occurs

If risk rises when realistic effectiveness is used, the techniques are not equivalent.

Step 9 — Conduct an independent technical review

Best practice is a structured review by:

• MI/inspection SME
• RBI specialist
• Corrosion/materials engineer
• Operations representative and other roles as appropriate

Watch for bias when the same party benefits from reduced scope.

Step 10 — Document the technical basis (audit-ready)

Your equivalency package should include:

• Inspection objective definition
• Damage mechanism review
• POD comparison
• Coverage evaluation
• Limitations and uncertainties
• RBI sensitivity check
• Approval signatures
• MOC record

If it isn’t documented, regulators and auditors will treat it as unsupported.

Minimum Defensible Workflow (Quick Version) 

Gate 1: Physics supports detection
Gate 2: Comparable POD at relevant flaw size
Gate 3: Comparable coverage in real conditions
Gate 4: Comparable sizing accuracy
Gate 5: RBI risk remains acceptable
Gate 6: Independent review completed
Gate 7: Fully documented under MOC

Miss any gate and the techniques are not equivalent.

Where most organizations get this wrong

In post-incident reviews, the failures usually involve:

• Assuming that if inspection is performed, the degradation is detectable
• Over-crediting inspection effectiveness
• Using generic POD values
• Ignoring localized damage risk
• Treating screening methods as quantitative methods
• Skipping RBI recalculation
• Allowing cost savings to drive the decision

Bottom line

Confirming equivalency is a structured risk validation exercise, not a technology comparison. The alternate method must demonstrably deliver equal confidence in detecting the credible damage at the required stage under real plant conditions and within your RBI risk targets.

Bibliography 

• American Petroleum Institute. API Recommended Practice 580: Risk-Based Inspection. Latest edition.
• American Petroleum Institute. API Recommended Practice 581: Risk-Based Inspection Methodology. Latest edition.
• American Petroleum Institute. API Recommended Practice 571: Damage Mechanisms Affecting Fixed Equipment in the Refining Industry. Latest edition.
• American Society for Nondestructive Testing. Nondestructive Testing Handbook, Third Edition.
• American Society for Testing and Materials. Relevant NDT standards (e.g., E317, E797, E164, E273, E1067) as applicable.
• European Federation for Non-Destructive Testing. Probability of Detection (POD) Handbook — Recommended Practice.
• Center for Chemical Process Safety. Guidelines for Mechanical Integrity Systems.
• UK Health and Safety Executive. Best Practice for Risk-Based Inspection as Part of Plant Integrity Management.

Mechanical Integrity (MI) Inspection Equivalency — One-Page Audit Checklist 

Purpose: Verify that an alternate inspection technique provides equivalent or better risk reduction than the baseline method.

Use for: RBI reviews, MOC evaluations, deferral justification, and internal audits.

References: API 580, API 581, American Society for Nondestructive Testing guidance.

Asset & Review Information

• Equipment / Tag: ______________________________
• Service / Unit: ______________________________
• Damage Mechanism(s): ______________________________
• Baseline Method: ______________________________
• Proposed Alternate Method: ______________________________
• Review Type: ☐ RBI ☐ MOC ☐ Deferral ☐ Other
• Risk Category: ☐ Low ☐ Medium ☐ High ☐ Critical
• Reviewer(s): ______________________________
• Date: ______________________________

Gate 1 — Inspection Objective Defined

Requirement: Performance expectations are explicit and measurable.

Gate Decision: ☐ Pass ☐ Fail

Gate 2 — Physics Applicability

Requirement: An alternate method can detect credible damage.

Gate Decision: ☐ Pass ☐ Fail

Gate 3 — Probability of Detection (POD)

Requirement: Comparable POD at relevant flaw size.

Gate Decision: ☐ Pass ☐ Fail

Gate 4 — Coverage & Effectiveness

Requirement: The same damage population is effectively inspected.

Gate Decision: ☐ Pass ☐ Fail

Gate 5 — Sizing & Trending Capability

Requirement: Supports integrity and life decisions.

Gate Decision: ☐ Pass ☐ Fail

Gate 6 — Evidence Quality

Requirement: Equivalency supported by objective data.

Evidence strength adequate for risk level: ☐ Yes ☐ No
Gate Decision: ☐ Pass ☐ Fail

Gate 7 — RBI Impact Verified

Requirement: Risk remains acceptable using realistic effectiveness.

Gate Decision: ☐ Pass ☐ Fail

Gate 8 — Independence & Bias Review

Requirement: Decision free of commercial bias.

Gate Decision: ☐ Pass ☐ Fail

Final Determination

Equivalency Status:
☐ Equivalent — Approved
☐ Conditionally Equivalent — Restrictions apply
☐ Not Equivalent — Reject

Conditions / Restrictions (if any):

Approvals

• MI/Inspection Authority: __________________ Date: ______
• Corrosion/Materials: __________________ Date: ______
• RBI Authority (if applicable): __________________ Date: ______
• Operations (if required): __________________ Date: ______

Auditor’s Reminder

If any gate fails, the techniques are not equivalent unless risk controls or scope are adjusted and re-evaluated.

Be the first to comment

There are no comments for this article.