Report Segmented ACFM Indications Without Double Counting

An ACFM file or segment is an acquisition record, not automatically one physical indication. A long feature can appear in several records, and one record can contain more than one reviewed observation. Begin the report with separate identifiers for acquisition segments and interpreted indications. Connect them through the actual technical review. This prevents the number of files or screenshots from becoming the reported number of conditions on the component simply because each export occupies a separate table row.

The register documents evidence relationships after the examination. It does not prescribe scanning, classify crack interactions or establish a sizing algorithm. The responsible technical process determines which records represent the same physical feature and what dimensions are supported. Preserve that decision, including any uncertainty. A report preparer should not join signals because they look similar or split one reviewed indication because the acquisition was interrupted and restarted in another file.

Record the component, weld identifier and the specific region addressed by the acquisition. A weld toe, cap or adjacent surface needs a clear physical reference where those distinctions matter to the result. Define the origin and direction used for locations. Do not assume that a distance along a weld identifies which side or surface was examined. A recipient planning follow-up should be able to distinguish the actual feature without guessing from a filename or the orientation of a selected screenshot.

If a local datum was used for a segment, preserve its relationship to the project datum. An acquisition may begin at zero after repositioning without starting at the physical weld origin. Keep that offset or crosswalk in the source record and report reference. Where the relationship is uncertain, identify the affected interval rather than forcing all segments into a continuous-looking coordinate table. The precision of a displayed value does not establish the accuracy of its physical placement.

Identify the actual probe, setup and examination event supporting each segment. Do not use a generic ACFM equipment description as evidence of the configuration used on the component. If the probe or arrangement changed, mark the affected record boundary. A later reviewer may need that context to understand why adjacent segments differ in presentation or available information. The register can reference a detailed setup record without reproducing operating instructions or unverified settings in the report.

Eddyfi’s ACFM probe catalog distinguishes several probe arrangements, including single-probe and array applications. That product context supports preserving the real configuration rather than assuming every ACFM record has the same acquisition geometry. It does not establish that a particular probe is suitable for the job. The responsible technical basis and event evidence determine what the reported segments support.

Different passes or selected records may serve different purposes within the actual examination process. Identify the role of each segment in the reported conclusion. A record that locates an area of interest is not necessarily the record supporting a final dimension. Do not attach a sizing value to the nearest convenient screenshot without preserving the actual analysis relationship. The recipient should understand which evidence supports location, characterization and the stated size, even when those roles involve related acquisitions.

Eddyfi’s ACFM technology explanation describes field-response interpretation and model-based sizing context. This is a general method explanation, not a universal result for another component. For reporting, retain the actual reviewed analysis and its supporting records. Do not infer depth from a displayed color or signal magnitude, and do not treat the application’s ability to produce a number as independent proof that the value is valid for the specific feature.

Record the segment’s start, end and direction using the source convention, then connect that extent to the component reference. Preserve units and any limitation on the location. A segment boundary may reflect file management or repositioning rather than the endpoint of a physical indication. Do not report the whole acquisition interval as the indication length unless the technical record establishes that relationship. Keep examination extent and interpreted feature extent in separate fields where they differ.

If several records overlap, identify the common physical region through the actual correlation evidence. Do not add their lengths to calculate a larger indication or a larger examined area. Repeated coverage can provide useful supporting information without representing another physical interval. The worksheet does not prescribe overlap or determine whether it is technically sufficient. It records the actual relationship so the report’s quantities and location statements remain consistent with the reviewed examination.

An indicated endpoint should be linked to the actual analysis and location evidence. If acquisition stops while the feature continues beyond the available record, preserve that limitation rather than treating the stop as a confirmed endpoint. The report may need a qualified extent or an unresolved boundary supplied by the technical review. Do not silently use the last recorded coordinate to produce a complete-looking length. That would turn an acquisition limit into an unsupported statement about the physical feature.

Where another segment establishes the continuation or endpoint, document the correlation and controlling analysis. A similar response in an adjacent file is not enough on its own to prove continuity. The responsible reviewer determines whether the records represent one feature, several features or an unresolved relationship. Preserve that decision and its basis so the final report can explain why a particular length or indication count was used without relying on the report preparer’s visual guess.

An unrecorded or inadequately assessed interval between segments should remain a separate scope question. Do not bridge it by drawing one continuous line across the final map unless the actual technical evidence supports that representation. A schematic can help communicate location, but its legend must distinguish confirmed extent from an unresolved relationship. The recipient should not mistake a graphic connection added during layout for a technical conclusion that the feature continues through the intervening region.

If access, geometry or another condition prevented completion, record the actual physical boundary and responsible follow-up. Keep the reason for the gap separate from the interpretation of the adjacent signals. A gap does not prove that the feature stops, and it does not prove that it continues. The register’s value is to preserve the question precisely enough that further examination or review can address it, rather than hide it inside an apparently complete numerical result.

In a fictional weld examination, segments S1 and S2 overlap and both contain records associated with reviewed indication I4. The draft summary counts two indications and adds the two segment lengths. The reviewer returns to the physical datum and actual interpretation record. The overlap represents repeated acquisition of part of the same region, while the technical review provides the supported I4 extent. The final report lists one indication with two supporting segment references rather than two independent conditions.

A separate segment S3 is near I4 but has an unresolved location relationship. It remains a distinct review question instead of being automatically joined to I4. This hypothetical scenario defines no minimum gap, interaction rule or sizing tolerance. It demonstrates why the source file count, scan length and reviewed physical indication are different quantities. The correct report relationship comes from the actual technical assessment, not from adding rows or choosing whichever calculation produces the most complete-looking result.

Record the actual reviewed dimensions and identify the analysis reference supporting each. A reported maximum depth may relate to a particular location within a longer feature, while its length describes another extent. Preserve that relationship rather than placing a depth value beside an unrelated segment endpoint. Do not add depth values from separate records or average them to create a compromise dimension. The responsible technical process determines which result and qualifications belong in the report.

If the review identifies several branches or interacting features, retain the actual representation and decision basis. The worksheet does not determine whether to treat them as one crack or multiple cracks, nor does it apply an engineering interaction rule. Avoid simplifying a complex result into one unqualified number merely to fit the table. Use notes or linked technical records so the recipient can understand the actual dimensions, their physical references and any limitations that affect subsequent assessment.

A repeat pass may confirm a location, improve the available evidence or answer a specific review question. Identify its purpose and relationship to the earlier event. Do not treat every repeat as another physical indication, and do not discard an earlier record simply because the later display appears clearer. The responsible review determines how the evidence is used. Preserve the controlling result and the supporting history so a recipient can understand why more acquisition records exist than reported indications.

If the repeat occurred after cleaning, coating removal, repair or another physical change, record that condition boundary. It may be a new examination of a changed surface rather than a repetition under the same conditions. The report should not merge the records into one event without explanation. Keep the applicable setup, dates and technical decisions connected to the correct state of the component. That history matters when the result is later used to plan repair or compare examinations.

A segment can have available data whose interpretation remains unresolved, or it can lack the acquisition needed for the intended assessment. Those are different questions. Identify the actual issue and the evidence required next. A vague pending note makes it difficult to decide whether the next action is technical review, data retrieval or additional field work. The register should preserve the specific uncertainty and responsible action rather than assigning the same general status to every incomplete record.

When the question is resolved, retain the supporting decision and the affected indication or scope statement. Do not merely change the cell to complete. The recipient should be able to understand whether a location was corrected, two records were correlated, an endpoint was established or further examination changed the available evidence. That distinction makes later report revisions explainable and reduces the risk that a closed administrative task is mistaken for an unrestricted technical conclusion.

Count physical indications using the actual reviewed identifiers and the project’s stated summary basis. Keep acquisition-segment count, examination length and indication count separate. A report can include all three where useful, but label their units clearly. Check that a map symbol, a result-table row and a narrative reference point to the same reviewed indication. This is particularly important when one physical feature has several supporting views or when a long weld is divided into many acquisition files.

Preserve unresolved correlation questions in the summary where they affect its meaning. Do not force an exact count if the responsible review has not established whether adjacent records represent one or several features. Use the actual qualified statement and maintain the evidence references. The worksheet does not decide how the client should assess component fitness or prioritize repairs. It ensures that the numerical summary accurately represents the examination and interpretation that were actually completed.

Identify the native acquisition files, selected views and analysis records used for the report. Keep their actual names or stable package references connected to the segment and indication identifiers. Do not rely on a screenshot caption that omits the source file or physical datum. A reviewer should be able to locate the supporting record without opening every file and guessing which one matches the report image. Preserve any software or setup reference required by the actual technical handover.

The digital reporting workspace can hold the reviewed segment register and narrative, including supported DOCX and XLSX imports. It does not read native ACFM data, perform sizing or attach examination images through its logo fields. Deliver those records through the agreed external process and describe the relationship accurately. The generated PDF organizes supplied evidence; it does not independently verify signal correlation, calculate crack dimensions or provide technical approval.

The equipment tracker can organize instrument and probe records associated with the examination. It does not establish the configuration used for every segment. The procedure draft workspace can help organize proposed reporting fields and responsibilities for review, but it cannot approve a sizing approach or supply missing acquisition evidence. Keep the actual source setup and technical decision linked to the reported result.

The ACFM instrument and probe buyer guide addresses broader procurement questions. This register concerns the specific physical relationships in a completed examination. Do not substitute product claims about detection or through-coating capability for the actual supported scope. A useful report identifies what was acquired, interpreted and left unresolved on the component, including the conditions and event boundaries that matter to the result.

Trace a reviewed indication through all supporting segments, the physical location map and the reported dimensions. Confirm that overlapping records have not been counted twice and that acquisition boundaries have not become unsupported feature endpoints. Then check an unresolved correlation or access question to ensure its qualification remains visible in the final package. These checks focus on evidence relationships rather than the visual neatness of a map or the number of populated rows.

Use the buyer-review guide for broader closeout checks and replace the fictional worksheet row with real reviewed references. The finished register should explain why the report contains a particular indication count, location and dimension set. It preserves the relationship between segmented acquisition and professional interpretation while avoiding unsupported arithmetic, automatic signal joining or claims that a reporting application has independently validated the examination.