Record RFT Tube Features and Review Exceptions

An RFT record can contain references to tubesheets, supports, bends and other physical features as well as evaluated indications. They do not all represent the same kind of result. Give each entry a defined role in the report: location landmark, geometry context, interpreted condition or unresolved question. Do not convert a feature label into a defect category merely because it appears in the same exported table. The recipient needs to understand why the entry is present and what decision it supports.

The feature register documents the actual examination and review. It does not teach signal interpretation, prescribe a probe arrangement or establish acceptance criteria. The responsible analyst and technical process supply those decisions. A clear register preserves their evidence relationships so another reviewer can locate the relevant record and understand its context. Where the available evidence does not establish whether a response is associated with geometry or a condition requiring evaluation, retain that uncertainty rather than choosing a convenient category.

Record the exchanger identity, tubesheet map revision and individual tube reference used by the acquisition. Include the viewing end or numbering convention where it affects physical identification. A support label without a confirmed tube relationship is not enough to locate a feature in the bundle. Keep the actual acquisition event distinct from earlier campaigns or later follow-up. This prevents a familiar support sequence from being attached to a different tube simply because the files use similar names.

Where a tube has been replaced or its map label changed, preserve the actual history and crosswalk. A tubesheet position can remain the same while the physical tube changes. Do not carry a previous feature or condition record forward as if it necessarily describes the current component. The report should identify which event and physical item the observation belongs to, then use any historical comparison only where the responsible review establishes a valid relationship.

Identify the probe and setup reference used for the reported acquisition. A generic RFT label does not describe every configuration or the evidence supporting a particular region. Keep the event-specific source record retrievable rather than substituting a product brochure or a current equipment inventory entry. If the arrangement changed during the examination, identify the affected tubes or segments and the technical record that explains the change. The report should describe the work actually performed.

Eddyfi’s remote-field testing explanation describes the indirect magnetic-field path through and outside the tube wall. This provides context for retaining the surrounding physical-feature relationship in an RFT record. It does not establish a universal response interpretation or coverage guarantee. Use the actual technical basis and review evidence for the component, rather than transferring a general method description into a claim that a particular region was fully assessed.

Record the landmark identifiers and their physical meanings from the actual source map or reviewed analysis. A sequence labeled SP1, SP2 and SP3 needs a defined starting end and direction. Do not assume every tube or every campaign numbers supports in the same order. If a landmark was inferred during analysis rather than directly correlated with a drawing, preserve that basis and any uncertainty. The register should distinguish a known physical reference from an analyst’s provisional location aid.

Keep the source drawing and analysis landmark relationship visible when they differ. A missing expected feature or an additional response should become a specific review question, not an automatic renumbering of every later entry. Record the actual resolution and which records it affects. This is especially useful when the final report is prepared from a summary export that no longer displays the source signal context needed to understand why a landmark was assigned or questioned.

State the origin, direction and units used for reported locations. Identify whether a value refers to a reviewed physical feature position, an acquisition coordinate or another source convention. Do not assume those representations are interchangeable. Preserve any documented offset or conversion relationship required to place the entry on the component. A number can be transcribed correctly yet point to the wrong physical location if the report silently changes its datum or treats a setup reference as a component coordinate.

Where the source location is approximate or bounded, retain that qualification. Avoid adding decimal places that imply a positional precision not established by the record. If a support-associated region is described by an interval, preserve the actual interval and its basis rather than replacing it with one point for convenience. The worksheet does not calculate probe offsets or determine positional accuracy. It records the location relationship supplied by the responsible examination and analysis process.

If the analyst identifies a limitation near a support or tubesheet, name the affected feature and region and reference the actual assessment. Do not apply one generic excluded distance to every support or claim that all support regions were fully assessed without evidence. The configuration, component and technical process determine what the examination supports. A precise description of the question is more useful than a broad note saying support interference, especially when only selected locations need follow-up.

Evident’s remote-field probe documentation distinguishes probe designs and describes support-vicinity performance as a design consideration. That is not proof of capability for an individual examination. For the report, retain the actual probe configuration and reviewer’s limitation statement. Do not convert a manufacturer’s comparative capability description into a guarantee that no relevant condition could be missed near a support in the current dataset.

Identify the physical context of the reported location rather than treating the entire tube length as one uniform region. A tubesheet transition, bend or other geometry change may have a different analysis relationship from a free-span location. Preserve the actual feature map and the responsible interpretation. The report preparer should not classify a response solely from its proximity to a named feature, nor assume that a feature-associated response is automatically harmless.

Where the examination record identifies a specific unassessed or limited region, retain its boundary in the scope summary. Do not include that region in a favorable condition category simply because the result table has no separate status for it. Use a clear limitation entry and link any subsequent examination that addresses the question. The register should make the technical boundary visible without supplying an invented exclusion length or prescribing a replacement method for every geometric transition.

A review exception should identify the source file, tube and relevant location or analysis reference. A note saying check support is too vague when several supports and acquisitions exist. Preserve the exact question: uncertain landmark identity, limited assessment, possible condition requiring review or another documented issue. The responsible analyst can then locate the evidence and make the appropriate decision without guessing which signal or exported row prompted the request.

Keep selected displays and source acquisition distinguishable. A cropped view may help explain a feature but omit the wider context needed for interpretation. Reference the native data and analysis session through the actual technical package. The report worksheet does not inspect that data or establish whether the response is geometric. Its role is to preserve a retrievable path from the reported exception to the evidence and the actual responsible resolution.

In a fictional tube report, an export contains a support landmark labeled SP3 and a separate unresolved evaluation near that location. The reporting template places both rows into a defect table, making the landmark appear to be another evaluated condition. A reviewer separates the physical feature from the interpretation question. SP3 remains a location reference, while the unresolved entry retains its own source data, scope and required technical review. The final report no longer counts one context marker as a second condition.

If a later examination provides evidence for the unresolved region, the register links that event to the specific question and preserves the responsible conclusion. This scenario is hypothetical and defines no RFT acceptance threshold or support exclusion zone. Its useful outcome is a clear distinction between where the analysis is located, what was actually interpreted and what remains uncertain. Those distinctions help the client use the report without treating every feature symbol as a defect or every support label as a completed evaluation.

A tube may have a reviewed condition at one location and a limitation at another. Preserve both rather than forcing the tube into one status that hides the distinction. The final summary can use the project’s agreed aggregation rule, but its relationship to the detailed record must remain retrievable. A favorable evaluation of one indication does not resolve a separate support-associated question, and a limitation does not by itself establish a particular physical condition in the unassessed region.

Define the legend so the recipient can distinguish feature references, evaluated results and incomplete assessment. Avoid color-only explanations that become ambiguous when the map is printed or viewed without its key. Keep the same definitions in the map, table and narrative. If the source software uses abbreviations that differ from the client’s reporting convention, preserve the approved crosswalk and do not simplify away a technical distinction merely to fit a smaller legend.

When another examination is performed, identify the actual tube, region and event it addresses. Preserve the correlation between the original RFT location and the follow-up location. Do not assume that a later result anywhere on the same tube resolves the original question. The responsible technical process determines the significance of the additional evidence. Record whether it confirms a condition, changes the interpretation, narrows the limitation or leaves part of the question unresolved.

Keep different methods’ results in their own defined terms. A local thickness measurement, another electromagnetic acquisition and an internal visual record may provide different evidence. The report should not average unlike quantities or present one as a direct replacement without a supported basis. The feature register can connect the records and their actual reviewed conclusion while preserving what each examination established. This makes the follow-up useful without overstating its physical extent or technical equivalence.

A later campaign may use revised numbering, a different acquisition direction or improved physical documentation. Record the crosswalk before comparing locations or condition categories. Do not interpret a shifted feature label as a moved support or a new indication without checking the source convention. Preserve the actual map revision and the responsible correlation. Where the available history is insufficient, report the current examination accurately and qualify the historical comparison rather than manufacturing continuity.

If the equipment configuration or analysis approach changed, retain the relevant context for the comparison. A difference in report detail can reflect a different supported view of the component rather than a physical change. The technical reviewer determines what can be concluded. The worksheet does not calculate degradation or remaining service life; it keeps the source relationships clear enough for that separate assessment and prevents a map-format change from becoming an unsupported engineering trend.

Use the digital reporting tool for a reviewed feature and exception table with explanatory notes. Supported DOCX and XLSX tables can be imported after preview. The application does not parse native RFT data, identify support signals or generate a technical tube map from acquisition files. Keep those records in the appropriate analysis workflow and reference them accurately. Its company and client image controls are logo fields, not attachments for examination displays.

The equipment tracker can organize probe and instrument references. The procedure draft tool can help structure proposed reporting responsibilities for technical review. Neither establishes the interpretation of a feature-related response. The tube-platform configuration guide addresses broader system planning, while this worksheet documents the actual event. Use the tools to organize real evidence without implying that a record entry independently validates the examination.

A landmark missing from a summary export can mean that it was not assigned, was excluded by an export rule or remains unresolved in the analysis. It does not automatically mean the probe never passed that region. Conversely, the presence of an expected landmark label does not prove that all data needed for the surrounding assessment is usable. Preserve the actual acquisition and analysis evidence before assigning either conclusion. The feature register should name the missing relationship precisely, so the next reviewer knows whether to investigate source data, landmark assignment or report extraction instead of repeating an examination without understanding the question.

Trace one physical landmark from the source map into the feature register and final report. Then trace one unresolved question to its data reference and actual disposition or follow-up. Check that the legend distinguishes those roles consistently. A table can be technically accurate while a map uses a misleading color or the summary claims full assessment. Review the delivered package as a whole so the recipient receives the same scope and meaning in every representation.

Use the buyer-review guide for wider closeout checks and replace the fictional worksheet row with actual reviewed records. The finished register should explain where a feature is, why it matters to the reported analysis and what evidence supports the stated result or limitation. It makes the examination usable for later review while preserving the separate responsibility for signal interpretation, technical acceptance and any asset-integrity decision based on the report.