Most outage NDE programs still size themselves the same way regardless of what the last three outages actually found: inspect a fixed percentage of welds, run the same technique mix on every circuit, and hope the sampling happens to land on the component that's actually degrading. That approach isn't wrong so much as blind to its own history, since every outage generates failure data that could reshape next year's scope but rarely does. A risk-based approach starts from the opposite direction, using condition history, criticality, and prior findings to decide where inspection hours actually belong before the outage window opens. A short session with our team can show what a risk-ranked inspection scope looks like against your own outage history.
Outage Planning · NDE Scope Optimization
NDE Inspection Scope Optimization for Outage Planning
Turn historical failure data, criticality ranking, and prior inspection findings into an inspection scope that puts crew hours and NDE technology where degradation is actually likely, instead of spreading a fixed percentage evenly across every circuit regardless of condition.
Inspection Hour Allocation
Weighted by criticality and prior finding history, not evenly split across the circuit list
3+ Cycles
of prior finding history most programs never feed back into scope
4
core NDE techniques competing for the same crew hours
Fixed %
is still how most outage scopes are sized, regardless of condition
The Scope Problem
Why a Fixed Inspection Percentage Stops Matching Actual Risk After the First Outage Cycle
A fixed inspection percentage is easy to plan and easy to defend during budget review, which is exactly why so many outage NDE scopes are still built that way. The trouble is that it treats every weld, tube, and circuit as an equally likely candidate for degradation, when in practice a small subset of components accounts for most of the findings across any real inspection history. A boiler tube circuit with two prior wall-loss findings and a header weld with a clean twenty-year history are not the same inspection priority, but a fixed-percentage scope samples them at the same rate. Over several outage cycles, that mismatch compounds: crews spend inspection hours confirming that low-risk components are still fine while a genuinely degrading component sits outside the sample and only gets caught once it fails or triggers an unplanned outage. The fix isn't more inspection hours, it's routing the hours that already exist toward where the condition history says they're actually needed.
Where Fixed Scopes Fall Short
Four Ways a Non-Risk-Based Inspection Scope Misallocates Crew Hours
Even Sampling Across Unequal Risk
A fixed sampling percentage applies the same inspection rate to a circuit with a documented wall-loss trend as to one with no findings across multiple prior outages.
Crew Sizing Set by Scope, Not Risk
Crew size and shift count are planned against total point count rather than against how many of those points actually carry elevated risk, leaving high-risk points rushed.
Findings Data Fragmented Across Outages
Prior outage findings live in separate reports by contractor and by cycle, making it hard to see a multi-cycle degradation trend on a specific component before scope is finalized.
Technique Selected by Habit, Not Fit
The same technique mix is specified regardless of the failure mode actually suspected, adding inspection hours without necessarily adding detection confidence.
Matching Technique to Failure Mode
Four Core NDE Techniques and When Each One Actually Earns Its Inspection Hours
Technique selection is one of the highest-leverage decisions in scope planning, since the wrong technique on the right component still misses the failure mode it was meant to catch.
| Technique | Best Suited For | What It Can Miss |
|---|---|---|
| Ultrasonic Testing (UT) | Wall thickness loss, internal flaws, weld volumetric defects | Very tight or tightly closed surface cracks without the right probe angle |
| Radiographic Testing (RT) | Volumetric weld defects, porosity, internal geometry verification | Planar defects oriented parallel to the radiation beam |
| Penetrant / Magnetic Particle (PT/MT) | Surface-breaking cracks and linear indications on accessible surfaces | Any subsurface flaw, since both techniques are surface-limited by design |
| Eddy Current Testing (ECT) | Tube-to-tube comparison, near-surface cracking, conductive material sorting | Deep subsurface flaws in thicker-wall components |
See Your Circuit List Ranked by Actual Inspection Risk
Most outage teams have never seen their full inspection point list sorted by criticality and finding history in one place. A short session shows what that ranked scope looks like for your own network.
Building a Risk-Based Scope
Five Steps From Historical Data to a Dispatchable Inspection Scope
1
Consolidate Historical Finding Data
Prior outage reports across contractors and cycles are pulled into one record so a multi-cycle trend on a specific component is visible before scope is planned.
2
Rank Components by Criticality and History
Each point is scored against consequence of failure and prior finding trend, producing a ranked list rather than a flat percentage target.
3
Match Technique to Suspected Failure Mode
Technique selection follows the failure mode most likely at each ranked point, rather than a single default mix applied across the whole scope.
4
Size Crews Against Risk-Weighted Hours
Crew count and shift length are planned against where inspection hours are actually concentrated, so high-risk points aren't rushed to cover low-risk ones.
5
Document Findings Back Into the Same Record
Results feed back into the same historical record used to build the scope, so the next outage starts from an updated risk picture instead of the same fixed percentage.
Fixed Percentage vs Manual Risk Review vs Automated Risk-Based Scoping
Three Ways Outage NDE Scope Actually Gets Built
Fixed Percentage
Simple to plan and budget, but samples every component at roughly the same rate regardless of actual condition history.
Manual Risk Review
An engineer applies judgment to prioritize known problem components, but the review depends on that person's recall of past outage reports.
Automated Risk-Based Scoping
Historical findings, criticality, and technique fit are combined into a ranked scope that updates as each outage adds new data.
Where Scoping Goes Wrong
Four Mistakes That Undermine a Risk-Based Scope Before It Starts
Scoring Criticality Once, Never Updating
A criticality score set years ago stays in place even after the component's operating context or duty cycle has changed.
Losing Contractor Findings Between Outages
Each outage's contractor delivers a standalone report that never gets reconciled against the last one, erasing the trend that risk-based scoping depends on.
Defaulting to the Same Technique Mix
The same UT/PT combination is specified across every circuit regardless of the suspected failure mode at each point.
Sizing Crews to the Point Count, Not the Risk
Crew hours are divided evenly across the point list instead of concentrated where the ranked risk actually sits.
Applied Example
How a Reprioritized Scope Caught a Wall-Loss Trend Two Outages Earlier
A economizer tube circuit had shown a minor wall-thickness reading below nominal on two consecutive outages, but each report was filed separately by a different inspection contractor and never directly compared. Under the site's fixed-percentage scope, that circuit was sampled at the same rate as every other tube bank, so the trend went unnoticed. When historical findings were consolidated and ranked by criticality, the two prior readings surfaced as a clear downward trend, moving the circuit into the high-risk allocation for the next outage. A targeted UT scan with a higher point density confirmed accelerating wall loss consistent with localized erosion, and the affected tube section was replaced during the planned outage rather than failing between outages and forcing an unplanned shutdown.
Getting Started Guidance
What to Confirm Before Moving to a Risk-Based Inspection Scope
A short readiness review shows how quickly your existing inspection history can be turned into a ranked scope.
| Question | Why It Matters |
|---|---|
| Are prior outage findings stored in one place across contractors and cycles? | Determines how much consolidation work is needed before a trend can be ranked |
| Is criticality currently scored per component or applied uniformly? | Shows whether a ranked scope can be built from existing data or needs a scoring pass first |
| How is technique currently selected for each inspection point? | Identifies whether technique fit is already matched to failure mode or defaulted |
| Who owns updating the risk ranking after each outage closes? | Defines the workflow that keeps the ranked scope current between outage cycles |
Common Questions
NDE Inspection Scope Optimization — Frequently Asked
These are the questions outage planning teams tend to ask first before shifting from a fixed-percentage scope to a risk-based one.
Does risk-based scoping mean fewer total inspection hours?
Not necessarily fewer hours, but a different allocation of the hours already planned, moving time away from low-risk components with a clean history and toward components with an active finding trend or high consequence of failure. Some programs do reduce total hours once low-risk sampling is trimmed, but the primary gain is better-targeted coverage rather than a smaller budget. Book a demo to see how allocation shifts against your own scope.
How many outage cycles of history are needed to build a useful ranking?
A single cycle of consolidated findings can already surface obvious high-consequence components, but a trend like gradual wall loss becomes far more reliable once at least two or three cycles of data are compared side by side. Programs starting from scratch typically see the ranking sharpen noticeably after their second cycle. Contact support to review what your existing history can support.
Can this work if different contractors run each outage?
Yes, the consolidation step is built specifically for that situation, since most sites do rotate or mix contractors across outage cycles. Findings are normalized into one record regardless of which contractor generated the original report, so the ranking isn't dependent on continuity of the inspection vendor. Book a session to see how multi-contractor history gets consolidated.
Does this replace engineering judgment on technique selection?
No, technique recommendations are meant to support the inspection engineer's decision, not override it, since local access constraints and equipment configuration still require an engineer's final call on what's actually achievable in the field. The ranking narrows the starting point rather than removing the review step. Ask our team about how technique recommendations fit into existing review processes.
Is this only relevant for boiler and pressure vessel components?
No, the same risk-ranking approach applies to any component with a repeatable inspection history, including piping circuits, structural welds, and rotating equipment shafts, as long as prior findings and criticality data exist to rank against. The technique table changes by component type, but the scoping logic stays the same. Book a call to discuss scope optimization across your full asset list.
Turn Your Outage History Into a Risk-Ranked Inspection Scope
iFactory consolidates prior findings, criticality data, and technique fit into one ranked scope, so inspection hours go where the condition history says they're actually needed.
.png)