A Fitness-for-Service (FFS) assessment normally needs evidence from five connected areas: the equipment and design basis, operating history and intended future service, inspection and flaw data, material information, and repair or alteration history. The exact package is not fixed. It changes with the equipment, damage mechanism, flaw type, assessment route and decision the owner needs to make.
A recent thickness report may be useful, but it is rarely the complete basis by itself. The assessor must be able to connect each finding to the correct component and location, understand the measurement limits, identify the relevant operating case and see which facts are verified, assumed or still missing.
This guide explains how to prepare a practical data handover before requesting a Fitness-for-Service assessment. It is a scope-preparation guide, not a substitute for API 579-1 / ASME FFS-1, the applicable project edition or engineering review.
Key Takeaways
• There is no universal FFS input list that is sufficient for every flaw or damage mechanism.
• The data pack must identify the equipment, the assessed location, the operating decision required and the intended future service.
• Inspection data must be traceable and suitable for the relevant assessment route; file volume alone does not create assessment readiness.
• Unknown material, geometry or operating information should be visible as a controlled gap, not silently replaced with an assumption.
• Early scope review can prevent unnecessary re-inspection by identifying which additional evidence is decision-relevant.
Why FFS Quality Cannot Exceed Input Quality
An assessment cannot be more specific than the evidence and assumptions supporting it. API describes FFS as a quantitative engineering evaluation for in-service pressurised components with flaws, damage or operating conditions that may affect structural integrity. That evaluation needs a defined component, condition and service case—not an isolated measurement.
Weak inputs usually create one or more practical consequences:
• The engineer must request clarification because the equipment, drawing revision or flaw location is ambiguous.
• The assessment uses conservative assumptions because a critical input cannot be verified.
• Targeted inspection or record reconstruction is needed before a final conclusion can be supported.
This does not mean every document must be available before the first conversation. An incomplete package can still support a scope review when the known gaps are clearly listed. It does mean that missing or conflicting evidence should not be hidden behind a label such as “data complete.”
The Required Data Depends on the Damage Mechanism and Assessment Route
Common data groups exist, but corrosion, crack-like flaws, distortion and time-dependent damage do not ask the same engineering question. The relevant Part and assessment level within API 579-1 / ASME FFS-1 must be confirmed against the applicable edition and project specification.
The examples below show why the input package changes. They are not universal minimum requirements.
| Condition being evaluatedData that may become especially importantWhy it matters | ||
|---|---|---|
| General or local metal loss | Thickness distribution, location, component geometry, operating pressure and temperature, corrosion history | The assessment must relate the measured loss to the correct geometry and operating case. |
| Crack-like flaw | Flaw dimensions and orientation, location, loading or stress information, material properties and relevant environment | Crack assessment can be sensitive to geometry, material behaviour, loading and flaw characterization. |
| Distortion or deformation | Measured shape or profile, reference geometry, loads, restraints and relevant fabrication or operating history | The engineering model must represent the actual deformation and its context. |
| High-temperature or time-dependent damage | Time-temperature history, excursions, material condition, service duration and relevant inspection evidence | Future operation depends on both accumulated exposure and the intended service case. |
For a high-level explanation of assessment escalation, see API 579 FFS Levels 1–3. The assessment level should not be selected from a website checklist alone; data quality, flaw complexity and project context still require engineering review.
Equipment Identity, Design Basis and Construction Records
The assessor must know exactly which equipment item, component and location the finding belongs to. A correct calculation applied to the wrong drawing revision or component geometry is still the wrong assessment.
Depending on the case, the starting package may include:
• equipment tag, asset hierarchy reference and component name;
• general arrangement, fabrication or as-built drawings with revision status;
• construction code and edition, when verified;
• design pressure and temperature, dimensions and documented allowances;
• datasheets, calculation records or manufacturer information relevant to the component;
• material records and weld, nozzle or seam information where they affect the assessment;
• previous rating, rerating or design-change records.
A fabrication or manufacturing dossier can provide much of this history, but acceptance documentation and in-service FFS serve different purposes. NWE’s pressure equipment documentation review explains the construction-record side of that boundary.
When drawings conflict, identify the conflict and the source of each revision. Do not choose the most convenient drawing without verification. Field measurement or as-built validation may be needed when critical geometry cannot be confirmed from records.
Operating History and the Intended Future Operating Case
Design values provide the original reference, while actual and intended service define the condition being assessed. The engineer needs to understand both. A vessel that has operated steadily below design limits presents a different history from one that has experienced repeated excursions, cycling or a process change.
| Actual service historyIntended future service | |
|---|---|
| Normal pressure and temperature ranges | Proposed pressure and temperature range |
| Relevant start-up, shutdown and operating cycles | Expected future cycles or service duration |
| Recorded excursions, upsets or abnormal events | Planned process, feed, environment or duty changes |
| Process chemistry and external environment relevant to damage | Any rerating, restriction or changed operating envelope being considered |
| Inspection trends and available degradation-rate history | The decision period or operating question the assessment must address |
Provide source dates and note where history is estimated rather than measured. If the planned future case has not been defined, the assessor may be unable to establish what period or conditions the conclusion is intended to cover.
Inspection Data, Defect Location and Sizing
Inspection data is useful for FFS only when it is traceable to the assessed component and suitable for the relevant damage mechanism. A report title such as “UT inspection completed” does not show whether the coverage, coordinate system or measurement detail supports the engineering question.
A practical handover should make the following fields easy to find:
| Handover fieldWhat should be clear | |
|---|---|
| Report identity | Report number, date, revision and responsible inspection party |
| Equipment and location | Tag, component, drawing reference and a repeatable location system |
| Method and scope | Technique, procedure reference, inspection area and stated limitations |
| Finding description | Flaw type or indication description without overstating the damage mechanism |
| Dimensions and orientation | Recorded size, direction, extent and units, with uncertainty or limitations where known |
| Supporting evidence | Raw readings, maps, scans, images or attachments needed to interpret the result |
| Trend information | Previous comparable data and dates, when genuinely comparable |
NWE’s guide on how to read an NDT report provides a broader review of indications, acceptance references and inspection evidence. Detailed rules for thickness mapping, location control, coverage and traceability belong in the dedicated inspection-data-quality scope, not in a universal FFS checklist.
Material Properties and Uncertainty
Unknown material information must be identified and managed; it should not be silently guessed. The relevant material inputs may include grade, product form, strength data, weld or heat-treatment condition, and toughness- or creep-related information where the selected assessment route is sensitive to them.
When a critical property is missing, the next step depends on the method and project context. The assessor may be able to use verified records, a permitted conservative basis, targeted material verification or testing, or a different assessment route. In other cases, the gap may prevent a final conclusion until it is closed.
Record three things clearly: what is known, the source of that information, and what remains uncertain. This is more useful than presenting an unverified value as fact.
Damage-Mechanism Context
The damage mechanism influences what must be measured and which assessment route may apply. “Corrosion” is often too broad a description. General thinning, localized metal loss, pitting, erosion-corrosion, environmental cracking, hydrogen-related damage, creep and mechanical deformation create different evidence needs.
The handover should therefore include the relevant process and environmental context, the basis for the suspected mechanism, whether the condition appears active or historical, and whether more than one mechanism may interact. A final damage-mechanism determination remains an engineering and materials task; inspection terminology alone should not be treated as proof.
Repair, Alteration and Previous Assessment History
Previous repairs and alterations may change geometry, material condition, loads, residual stress or the assumptions used in an earlier assessment. They may also explain why current drawings no longer match the installed equipment.
Provide records for relevant permanent or temporary repairs, weld overlays, replacements, alterations, post-weld heat treatment, rerating, management-of-change actions and previous FFS or remaining-life assessments. Include the date, location, procedure or drawing reference, inspection after the work and any conditions that were carried forward.
An older assessment should not be supplied as a conclusion without its inputs and limitations. The new operating case or inspection evidence may differ from the basis used previously.
What to Do When Records Are Incomplete
A scope review can often begin with incomplete records, but a final assessment may require targeted gap closure. Data readiness is not simply complete or incomplete. The useful question is whether the uncertainty is visible and whether the selected assessment can manage it.
Use the following matrix to prepare the conversation with the FFS engineer. It is a scope tool, not an acceptance criterion.
| Data groupReady for scope and assessor reviewUsable with documented assumptionsGap closure likely required | |||
|---|---|---|---|
| Equipment identity and geometry | Tag, component, location and drawing revision align | Critical geometry reconstructed from verified field data | Equipment, location or revision remains ambiguous |
| Design basis | Relevant design conditions, dimensions and basis are traceable | A controlled, conservative basis may be defined by the assessor | Critical design or geometry input is unknown and unverified |
| Operating history | Actual history, relevant excursions and future case are defined | History can be bounded and the owner confirms the scenario | Future case or significant excursions cannot be defined |
| Inspection and flaw data | Method, date, location, dimensions and attachments are traceable | Known sizing limits are documented and can be evaluated | Location, extent or sizing is unreliable for the selected route |
| Material information | Relevant grade and properties are traceable | A permitted basis or verified testing may support the route | A critical property is unknown and the assessment is sensitive to it |
| Damage context | Credible mechanism and environment are described | More than one mechanism remains possible and screening is planned | The observed condition is inconsistent or the mechanism has not been evaluated |
| Repair or alteration history | Relevant changes and prior assessments are traceable | Partial history is carried as a controlled uncertainty | An unrecorded change may affect geometry, loads or material condition |
When a gap is identified, record it before deciding the action. The next step may be document retrieval, field verification, as-built measurement, targeted NDT, material testing, a controlled assumption or a pause in the assessment. The correct route depends on how sensitive the engineering conclusion is to the missing input.
For geometry and drawing conflicts, as-built preparation and validation can support record reconstruction. A later NWE article will address missing pressure-equipment records as a dedicated integrity-basis problem.
Client-Ready FFS Data Handover Checklist
Send an indexed, revision-controlled package with a one-page case summary and an explicit gap list. The objective is not to create the largest possible folder. It is to let the assessor understand the equipment, finding, source evidence and decision need without reconstructing the case from disconnected files.
| Package elementRecommended content | |
|---|---|
| 1. One-page case summary | Equipment tag and component; finding and location; current status; required decision; owner contacts |
| 2. File index | File name, document number, revision, date, source and brief relevance note |
| 3. Design and construction folder | Relevant drawings, datasheets, calculations, material and fabrication records |
| 4. Operating folder | Actual pressure/temperature history, excursions, cycles, environment and intended future case |
| 5. Inspection folder | Current and previous reports, maps, scans, photographs, raw data and location references |
| 6. Repair and change folder | Repair/alteration records, MOC, rerating and previous assessments |
| 7. Known-gap register | Missing, conflicting or uncertain inputs; who owns each action; planned verification |
| 8. Revision control | A clear issue date and change log so the assessor knows which package is current |
Do not rename files so aggressively that their original document identity is lost. A simple index is often better than a new folder structure that separates reports from the drawings and location references needed to interpret them.
Define the Scope Before Collecting More Data
Do not automatically order more inspection before asking for an FFS scope review. First define the damage question and the operating decision. Early coordination between the owner, inspector and FFS engineer can identify which additional evidence will change the decision and which activity would add cost without resolving the uncertainty.
1. State the decision required: continued operation, monitoring, repair planning, rerating or another defined question.
2. Share the one-page case summary, current file index and known-gap register.
3. Ask the FFS engineer to identify the likely assessment route and the inputs to which the result is most sensitive.
4. Use the inspection specialist to plan targeted evidence gathering with repeatable location control and suitable methods.
5. Issue the updated data pack under revision control before the assessment basis is finalized.
NWE provides separate in-service inspection and FFS engineering support. Where complex geometry or a specific flaw requires additional characterization, the inspection scope can then be selected for that decision rather than from a generic test list.
Prepare the Available Evidence, Then Request a Scope Review
You do not need to pretend the data pack is complete before starting the discussion. Prepare the equipment identity, finding summary, available design and operating records, intended future case and known gaps. That is enough to make the first scope conversation productive.
Share the current package and the decision you need with NWE’s Fitness-for-Service team to define the assessment scope and any targeted data-gap actions. The assessment outcome will still depend on the applicable method, verified evidence, operating conditions, project governance and responsible engineering review.
Frequently Asked Questions
Is a recent thickness report enough to start an FFS assessment?
It may be enough for an initial scope discussion, but it is not usually the complete assessment basis. Its value depends on equipment and location traceability, coverage, the suspected damage mechanism, design information and the operating case.
Can an FFS assessment be performed without original drawings?
A scope review may still begin. Critical geometry or design gaps may then require verified field measurement, record reconstruction, testing or controlled assumptions permitted by the applicable assessment route. In some cases, the gap must be closed before a final conclusion can be supported.
Do data requirements change between corrosion and crack-like flaws?
Yes. The equipment identity, design basis and operating case may overlap, but flaw characterization, material information, loading and environmental data can differ substantially. The relevant assessment procedures must be checked in the applicable edition.
What operating data should be provided?
Provide actual pressure and temperature history, relevant excursions and cycles, process or environmental information, and the intended future operating case. State where information is estimated or incomplete.
What if the material grade or toughness is unknown?
Make the gap explicit. Depending on the selected method, the assessor may need verified records, a permitted conservative basis, material verification or testing, or a different assessment route. The value should not be silently guessed.
Should we perform more NDT before contacting an FFS engineer?
Not automatically. Early scope review can identify which additional measurements are decision-relevant and avoid inspection that does not resolve the assessment uncertainty.
How should files be organized for handover?
Use an indexed, revision-controlled package with a one-page case summary. Keep equipment identifiers and original document numbers visible, connect findings to repeatable locations, and include a known-gap register.
Does a well-prepared data pack guarantee acceptance for continued operation?
No. It supports a clearer and more efficient engineering assessment. The conclusion still depends on the applicable method, verified inputs, assumptions, operating conditions, jurisdiction, owner governance and the responsible engineering decision.
