Use Remaining Life Assessment (RLA) when the decision is mainly about a time or cycle horizon. Use Fitness-for-Service (FFS) when known damage or a flaw must be evaluated for defined operating conditions. Use Risk-Based Inspection (RBI) when the question is which equipment should be inspected first, when and with what focus. These methods can support one another, but they are not substitutes.
The right starting point is therefore not the acronym. It is the decision the asset owner needs, the condition of the equipment and the evidence available. A fleet may be screened through RBI, a damaged item may then require FFS, and a mechanism-specific remaining-life estimate may help set the next intervention or reassessment point.
This guide explains how to select and sequence those routes for pressure equipment. It supports the broader pressure equipment integrity and life-extension process, but it does not replace the applicable code, project specification, jurisdictional requirements or engineering review.
Key Takeaways
• RLA asks how much time or how many cycles may remain before a defined limit is reached; the method depends on the damage mechanism.
• FFS asks whether equipment with known damage is acceptable for a defined operating case and what restrictions or actions may be required.
• RBI asks where inspection effort should be focused by combining probability and consequence of failure.
• An FFS assessment may include a remaining-life projection, but RLA and FFS are not automatic synonyms.
• Known flaws, uncertain data and mixed equipment populations often require a sequence of methods rather than one isolated study.
The Three Questions Are Related – but Not Interchangeable
RLA, FFS and RBI sit within the same integrity-management system, which is why they are often discussed together. Confusion begins when they are treated as three names for the same task. Each starts from a different management question and produces a different type of output.
| Assessment routePrimary questionTypical scaleMain outputWhat it does not prove by itself | ||||
|---|---|---|---|---|
| Remaining Life Assessment | How long or how many cycles until a defined limit may be reached? | A component, location or degradation mechanism | A time- or cycle-based estimate with assumptions and review triggers | That a known flaw is acceptable under every relevant failure mode |
| Fitness-for-Service | Is equipment with known damage acceptable for defined operating conditions? | A damaged component or specific flaw | Acceptability, operating limits and run / monitor / repair / rerate / replace options | Which items across a fleet should receive inspection priority |
| Risk-Based Inspection | Which equipment should be inspected first, when and with what effectiveness? | A population, unit, circuit or equipment programme | Risk ranking and an inspection plan based on probability and consequence | Direct structural acceptability of a measured flaw |
The boundaries are practical rather than administrative. RBI may identify an item that needs closer examination. Inspection may reveal a flaw. FFS may establish whether that flaw is tolerable under a defined case. A remaining-life evaluation may then help set a monitoring, inspection or intervention date. The results should feed back into the integrity plan.
What Remaining Life Assessment Actually Answers
Remaining-life assessment estimates a time or cycle horizon to a defined technical limit. It is a broad objective, not one universal calculation method. The required model, data and uncertainty treatment depend on how the equipment is degrading.
The phrase remaining life is therefore incomplete unless four points are clear: the damage mechanism, the limit being projected, the future operating case and the assumptions used. A number without those conditions can look precise while giving the decision-maker little reliable guidance.
Corrosion-based remaining life
For a corrosion-controlled case, the team may review measured thickness, the relevant minimum basis, historical trends and expected future conditions. The result can support an estimate of when another review, inspection or intervention may be needed. A simple trend can be useful when the measurements represent the same location and condition, but it should not be treated as a universal life model. Changes in process, corrosion mechanism, coverage or measurement uncertainty may alter the projection.
When an FFS scope is being prepared, the input package should make those trends and gaps visible. See what data is required for an FFS assessment once the supporting article is live.
Fatigue, creep and crack-growth life
Fatigue life depends on loading cycles, stress ranges, geometry and the relevant fatigue model. Creep life depends on time at elevated temperature, material condition and the applicable creep assessment approach. Crack-growth life requires suitable flaw characterization, loading and fracture or growth data. These are not interchangeable with a corrosion-rate projection.
This is why RLA should be described by the mechanism and decision, not sold as a single calculation. The estimate should state its basis, uncertainty, operating envelope and trigger for review. If the evidence cannot support a time-dependent conclusion, the correct output may be a data gap or a more conservative action rather than an artificial life number.
What Fitness-for-Service Answers
FFS evaluates whether equipment with known damage can meet a defined integrity requirement under stated operating conditions. It is the main route when the decision is about flaw acceptability rather than only inspection priority or elapsed time.
API 579-1 / ASME FFS-1 provides assessment procedures for in-service equipment with damage. ASME describes the scope as covering both the current integrity of a component and projected remaining life. The overlap matters: an FFS assessment may include a remaining-life projection when the damage mechanism, data and future service case support one. That does not make every remaining-life study an FFS assessment, or every FFS conclusion a life prediction.
A practical FFS scope normally connects:
• a defined component and flaw location;
• inspection evidence suitable for the damage mechanism;
• geometry, material and design information relevant to the assessment;
• current and intended pressure, temperature, loads and environment;
• the decision required, such as continued operation, monitoring, repair, rerating or replacement.
The exact assessment route and input requirements must be checked against the applicable edition and project specification. A website comparison cannot select an assessment level or establish acceptance.
For NWE’s commercial scope, see Fitness-for-Service engineering services. For a separate explanation of assessment escalation, see API 579 FFS Levels 1-3.
What Risk-Based Inspection Answers
RBI prioritizes inspection by considering the probability and consequence of failure. It is used to direct inspection resources toward the equipment, damage mechanisms and locations that matter most to risk.
API RP 580 identifies the basic elements for developing, implementing and maintaining an RBI programme. API RP 581 documents a quantitative approach to RBI using probability of failure and consequence of failure. In practice, the output may include risk ranking, inspection priorities, techniques, coverage and reassessment timing.
RBI does not directly demonstrate that a measured crack, wall-loss area or deformation is structurally acceptable. It may identify the item as important and define the inspection need. Once a specific flaw is known, an appropriate defect assessment such as FFS may still be required. Likewise, a low risk rank is not proof that degradation is absent; consequence, uncertainty and inspection effectiveness remain part of the programme.
Review NWE’s Risk-Based Inspection service for the planning route. Detailed input requirements are covered separately in RBI data requirements, while RBI vs time-based inspection explains the inspection-planning distinction.
How RLA, FFS and RBI Can Work in Sequence
Many integrity problems do not require a choice of only one method. They require a controlled sequence in which the output of one activity becomes the input to the next.
1. Define the decision. State whether the immediate need is inspection priority, flaw acceptability, a time horizon or a combination of these.
2. Check evidence readiness. Confirm equipment identity, operating case, likely damage mechanism, inspection traceability and critical gaps.
3. Prioritize where needed. Use RBI when a fleet, unit or circuit must be ranked and the inspection plan needs to be focused.
4. Characterize the condition. Perform the inspection or data-gap work needed to establish the flaw, degradation or uncertainty.
5. Assess known damage. Use FFS when the equipment contains a defined flaw or damage condition that needs an engineering acceptability decision.
6. Project time or cycles where justified. Use a mechanism-specific remaining-life evaluation to establish a review, monitoring or intervention horizon.
7. Feed the result back. Update the RBI model, inspection plan, operating limits, maintenance actions and reassessment triggers.
The sequence is not always linear. An FFS conclusion may reveal that additional inspection is needed. A remaining-life estimate may change the risk ranking. An operating change may invalidate a previous projection and trigger a new assessment. The programme remains defensible only when these feedback points are documented.
Decision Tool Selection Matrix
Use the matrix below to define an initial route. It is a scope-selection aid, not an engineering conclusion or a substitute for the applicable standards.
| Asset condition or management questionPrimary routeSupporting routeExpected outputCritical caveat | ||||
|---|---|---|---|---|
| Known flaw or measured damage: Is it acceptable at defined conditions? | FFS | Targeted inspection or material verification | Acceptability, limits and action options | RBI ranking alone cannot prove flaw acceptability |
| How long until a thickness, fatigue, creep or crack-growth limit may be reached? | Mechanism-specific RLA | Often FFS or another code-based evaluation | Time or cycles with assumptions and review triggers | Do not apply one corrosion-rate approach to every mechanism |
| Which equipment should be inspected first, when and with what effectiveness? | RBI | Damage-mechanism review and inspection data | Risk ranking and inspection plan | RBI quality depends on data, consequence model and governance |
| Fleet has mixed age and a limited inspection budget | RBI screening | Escalate selected items to FFS or RLA | Prioritized programme and exception list | Low risk does not mean no degradation |
| RBI identifies a high-risk item with known degradation | FFS and/or RLA | Update RBI after assessment | Operating decision plus revised inspection plan | Sequence and feedback must be documented |
| Inspection found wall loss but location or extent is uncertain | Data-gap closure first | Then FFS or RLA as applicable | Assessment-ready evidence | Do not force a precise life estimate from weak data |
| Operating conditions changed or an excursion occurred | Basis review; possible FFS | Update RBI and life estimate | Revalidated operating basis | The future case must be defined before projecting life |
| Scope principle – Do not choose the acronym first. Start with the decision: flaw acceptability, remaining time or inspection priority. If a known flaw needs an engineering decision, review the FFS scope. If the challenge is fleet or circuit prioritization, review the RBI scope. |
|---|
Common Selection Mistakes and Missing Inputs
The wrong study is often commissioned because the problem statement is too broad. Phrases such as “calculate remaining life” or “perform RBI” do not identify the equipment condition, decision deadline or evidence gap.
| Selection mistakeWhy it failsBetter correction | ||
|---|---|---|
| Using RBI to approve a known flaw | RBI ranks risk and plans inspection; it does not directly establish structural acceptability | Define the flaw and operating case, then review whether FFS is required |
| Treating a corrosion-rate result as total remaining life | Other mechanisms, changing service and measurement uncertainty may control the decision | Name the mechanism, limit, data basis and future conditions |
| Starting FFS with an untraceable inspection finding | A precise calculation cannot correct the wrong component, location or extent | Close identity, location, sizing and coverage gaps first |
| Requesting a precise RLA when the future operating case is unknown | The projection has no defined load, temperature, environment or duty basis | Define the intended future case and review triggers |
| Assuming every ageing item needs all three studies | This creates cost and duplicate work without a clear decision path | Use the management question and asset scale to select the first route |
| Treating a previous study as permanently valid | New damage, operating changes or revised evidence may invalidate the basis | Review assumptions, limitations and reassessment triggers |
Before commissioning a study, the owner should be able to state what is known, what is uncertain and which decision cannot be made with the current evidence. The next action may be targeted inspection, record retrieval, material verification or a scope review – not necessarily a full calculation.
When a Combined Scope Is Justified
A combined scope is justified when the programme must answer more than one decision at different scales. It should still be staged so that each method receives the evidence it needs and produces a clear handover to the next step.
| ScenarioWhy methods are combinedPossible sequence | ||
|---|---|---|
| Ageing facility with many pressure vessels | The owner must prioritize the population and assess selected damaged items | RBI screening -> targeted inspection -> FFS/RLA -> updated RBI plan |
| Known anomaly in a high-consequence item | The flaw needs acceptability review and the result may change risk and inspection timing | FFS -> remaining-life projection if justified -> RBI update |
| Process change or operating excursion | The previous operating basis and degradation assumptions may no longer be valid | Basis review -> FFS/RLA as needed -> revised inspection plan |
| Limited or inconsistent inspection data | No method can produce a defensible output until critical uncertainty is reduced | Data-gap review -> targeted inspection -> selected assessment route |
The combined programme should not hide method boundaries. Each report should state the question answered, data used, assumptions, limitations, responsible review and the action that follows. This prevents an RBI ranking from being read as an FFS conclusion, or a remaining-life number from being treated as unconditional permission to operate.
Does Reaching Original Design Life Select the Method?
No. Reaching an original design-life milestone is a trigger for review, not an automatic instruction to replace the equipment or perform one specific study. The required route depends on jurisdiction, the design and operating basis, current condition, degradation mechanisms, inspection evidence and the decision the owner needs.
A population-level life-extension programme may use RBI to prioritize work, FFS for identified damage and mechanism-specific life evaluation for future planning. Another item may need record reconstruction or inspection before any of those routes can be used reliably. A dedicated NWE article will address the beyond-design-life decision in more detail.
Define the Decision Before Choosing the Method
A useful scope discussion starts with five questions. These are more valuable than selecting RLA, FFS or RBI from the service name alone.
1. Which asset, component, circuit or equipment population is involved?
2. What decision must be made: inspection priority, flaw acceptability, time horizon, repair planning or life extension?
3. What inspection finding, degradation concern or operating change triggered the review?
4. What current and intended operating conditions should the assessment represent?
5. Which records are available, which are uncertain, and when is the decision required?
If the issue is a known flaw or damage condition, share the evidence with NWE’s FFS team to define the engineering assessment route. If the challenge is prioritizing a fleet, unit or circuit, review the RBI scope. The first conversation can begin before every record is available, provided the gaps are visible.
Known damage or flaw: discuss a Fitness-for-Service scope. Fleet or inspection-priority problem: review NWE’s Risk-Based Inspection scope. The final method, inputs and conclusions remain subject to the applicable requirements, verified evidence and responsible engineering review.
Frequently Asked Questions
Is Remaining Life Assessment the same as Fitness-for-Service?
No. RLA estimates a mechanism-specific time or cycle horizon to a defined limit. FFS evaluates whether equipment with known damage is acceptable for stated operating conditions. An FFS assessment may include projected remaining life when the evidence, mechanism and future case support it, but the terms are not interchangeable.
Can RBI prove that a damaged pressure vessel is fit for service?
No. RBI prioritizes inspection using risk. It can identify an important item, damage mechanism or inspection need, but it does not directly establish the structural acceptability of a measured flaw. A suitable engineering assessment such as FFS may still be required.
Can an FFS assessment provide remaining life?
It may. ASME describes FFS procedures as covering present integrity and projected remaining life. A useful projection still requires a defined damage mechanism, suitable data, future operating conditions and clear assumptions. Some FFS questions may support an acceptability decision without a defensible long-term life estimate.
Does an RBI study replace remaining-life calculations?
No. RBI uses condition, degradation, probability and consequence information to plan inspection. A mechanism-specific life evaluation may still be needed to establish when a limit, intervention or reassessment point may be reached. The life result can then be fed back into the RBI programme.
Which method is needed after wall loss is found?
First confirm the equipment, location, extent, measurement quality and likely damage mechanism. FFS commonly addresses whether the wall-loss condition is acceptable. A corrosion-based remaining-life estimate may support timing, and RBI may be updated to reflect the new condition and inspection need.
Do ageing facilities need all three methods?
Not automatically. A combined scope is useful when the owner must prioritize a population, assess specific damaged items and plan future inspection or intervention. If only one decision is required, one route may be sufficient after the evidence is checked.
What if the inspection data is incomplete?
Close the gaps that materially affect the decision before demanding a precise result. The next step may be targeted inspection, material verification, operating-data review or record reconstruction. A scope review can begin with incomplete records when the uncertainties are clearly identified.
Does reaching original design life make RLA mandatory?
No. It triggers an integrity review, not one universal assessment. The route depends on the applicable requirements, design basis, actual condition, degradation mechanisms, operating history and the decision the owner needs to make.
