Explain ECA Channel and Surface Maps in Reports

An ECA display arranges recorded responses into a view that helps analysis. The report still needs to explain how that view relates to the component. Identify the acquisition, probe arrangement, scan direction and physical datum supporting the selected map. Do not assume that a rectangular color image is a scale drawing of the entire examined surface. A reader needs the actual axis meanings and scope relationship before using the image to locate an observation or infer coverage.

This worksheet documents a reviewed examination rather than configuring an array or interpreting signals. The responsible technical process supplies the valid mapping and result. Preserve that relationship accurately, including any unresolved position or coverage question. A report can use a selected map effectively without claiming that every displayed pixel represents an independently measured physical property or that a visually continuous image proves uninterrupted acquisition across the intended surface.

Record the probe identifier and the relevant configuration or channel-map reference for the acquisition. A probe family name may not establish which arrangement was used on the job. Keep the actual source setup retrievable, particularly where the system supports different configurations or the analysis uses selected channels. The report preparer should not reconstruct channel order from an illustration in a catalog or assume that every channel number corresponds directly to one evenly spaced physical strip.

Eddyfi’s ECA explanation describes multiple elements and sequenced coil activation. That context supports retaining the actual channel arrangement rather than treating the display as self-explanatory. It does not establish a universal mapping for every probe. Use the configuration and reviewed technical basis belonging to the examination, and preserve the distinction between the physical sensor arrangement, the acquired channels and the selected presentation in the final report.

State what the scan and index axes represent in the delivered view. One axis may relate to movement along the component while the other reflects the array arrangement or another software representation. Preserve the actual units and origin. Do not relabel a channel index as a physical distance unless the source mapping supports that conversion. If an axis is time-based, keep that meaning visible rather than presenting it as an encoded position without evidence.

A selected image can lose axis labels when cropped for the report. Keep the missing context in a caption or linked record if the view remains useful, and verify that the recipient can still locate the displayed region. The worksheet does not calculate a position from acquisition timing or assumed scan speed. It records the actual relationship supplied by the examination process, including any qualification on the location values used in the report.

Identify the physical mark, drawing coordinate or feature used as the scan reference. An acquisition zero is not necessarily the component’s reporting origin. Preserve any documented offset and direction relationship. If the origin was reset between passes, record the event boundary and the corresponding source file. Do not join separate acquisitions by numerical position alone when each begins at zero. Their relationship needs actual physical evidence, not a convenient spreadsheet ordering convention.

Keep the source coordinate and the reported physical location distinguishable where a transformation is used. This allows the reviewer to trace a reported observation back to the original data without reverse-engineering an undocumented shift. If the mapping remains uncertain, retain that uncertainty and identify the affected scope. A precise-looking coordinate can be misleading when the datum relationship is missing, even if the number was copied exactly from the instrument display.

Record the orientation of the probe relative to the component and the direction of each relevant pass. A return pass can reverse the relationship between screen direction and physical direction, depending on the acquisition and display setup. Do not mirror a map for page layout without preserving the resulting orientation. A recipient should be able to identify which edge of the displayed view corresponds to the actual component reference used by the examination team.

If a probe was rotated or a different arrangement used to address another region, identify the affected file or segment and its map relationship. Do not assume the same channel-to-surface convention applies across every pass. The responsible technical review determines how the views correlate. The report should retain that decision rather than making an attractive composite image whose physical orientation changes silently from one section to another.

Identify the quantity or processed signal representation shown by the color scale through the actual analysis record. A color is not automatically a crack-depth value, wall-thickness measurement or acceptance category. Preserve the scale, units where applicable and relevant view selection. If the image is included only to illustrate a reviewed indication, say so. The technical conclusion belongs to the actual analysis and evaluation, not to a reader’s intuitive interpretation of red, green or another familiar color.

The FHWA ECA overview describes sensor responses and mapped presentations in a steel-inspection context. It is explanatory material, not a project acceptance rule. For reporting, retain the actual signal meaning and analysis basis used for the selected map. Do not transfer a generic technology description into a claim that the displayed colors directly establish a particular material condition or that all ECA systems produce identical physical-property estimates.

If the analysis uses a mixed, filtered or otherwise processed channel, identify the relevant saved setup or analysis-session reference. Do not describe it as an unprocessed sensor response when that distinction matters to the interpretation. The report does not need an unverified transcription of every setting, but it should preserve the controlling context and the responsible result. A selected processed view can be useful while still requiring access to the source acquisition for further review.

Where several channels contribute to the reported observation, explain their roles through the actual interpretation record. Avoid selecting only the most visually prominent channel and omitting the relationship to the reviewed result. Equally, do not claim that every acquired channel was used for every decision merely because the data file contains them. The worksheet makes the selected evidence traceable without prescribing a processing method or deciding which combination is technically appropriate.

A missing, excluded or questioned channel needs a clear relationship to the affected acquisition and surface region. Do not fill the corresponding map area with a favorable category simply to make the image look continuous. Preserve the responsible assessment of what the available data supports. A gap in the displayed view can also reflect a selection or export setting, so the report preparer should not diagnose an acquisition failure from appearance alone.

Identify whether the limitation concerns data availability, signal usability, physical contact or another documented issue. Keep those states distinct when their follow-up differs. The technical process determines whether additional acquisition or other evidence addresses the question. This worksheet supplies no allowable percentage of missing channels or universal coverage tolerance. It records the actual boundary and responsible decision so the recipient can understand where the report’s conclusion applies and where a limitation remains.

In a fictional surface examination, pass A begins at datum D1 and pass B begins at D2 after the probe is repositioned. Both source files start their displayed scan coordinate at zero. A report preparer places the maps on top of each other because the numerical axes match, making a feature in B appear at the location of a different feature in A. The source records are individually valid, but the combined physical map is unsupported.

The reviewer restores each pass’s actual origin, direction and placement relationship. Any overlap is then identified through the responsible correlation instead of numerical coincidence. This hypothetical example specifies no scan spacing or positional tolerance. It demonstrates why a map needs a physical crosswalk before results are combined. A shared software coordinate can describe separate places on the component, and a polished composite cannot replace the evidence that connects each acquisition to its real location.

When several passes cover adjacent or overlapping regions, preserve the physical extent of each and the reviewed relationship at the boundaries. A composite image can be a communication aid, but it should not conceal repeated acquisition or an unexamined interval. Keep the source pass references retrievable. Do not calculate total covered area by adding nominal probe widths and travel distances unless the actual technical process supports that calculation and accounts for overlap and limitations.

If the location relationship is insufficient to create a defensible composite, deliver separate labeled maps with the unresolved boundary described. That is more useful than forcing them into a continuous-looking mosaic. The report can explain what each view establishes and what additional correlation is needed. The responsible technical reviewer determines the scope conclusion; the report preparer should not resolve an uncertain boundary by stretching, cropping or rearranging images to make their patterns appear to align.

An indication can appear in overlapping passes or in more than one selected channel. Preserve the actual correlation so it is not counted repeatedly as separate physical conditions. Use a stable reviewed indication reference and list the supporting views. Conversely, similar-looking responses should remain separate where the evidence does not establish that they represent the same location. The report table should reflect the responsible interpretation, not a counting rule based on the number of screenshots or colored patches.

Keep any reported dimensions attached to the actual measurement or sizing basis. A region drawn around a display response is not automatically the physical boundary of a discontinuity. The worksheet does not derive length or depth from an image. It connects the reviewed result with the source pass, channel and location context. This lets a recipient understand why several data views support one reported observation without assuming that the report formatter performed a new technical measurement.

Where the examination record identifies changes in coating, geometry, preparation or probe arrangement, preserve their relationship to the acquired segments. A single map may include regions with different relevant conditions. Do not describe the entire acquisition using one convenient condition statement if the source records distinguish them. The responsible technical process determines whether those differences affect the assessment. The report should keep the actual context available without inventing a universal coating allowance or surface-condition acceptance rule.

If a later scan follows cleaning, repair or another physical change, identify it as a separate event with its own condition reference. Do not merge it into the original map in a way that conceals when the component changed. The final conclusion can use the actual combined evidence where the responsible review supports that approach, but the history should remain understandable. A later clearer response does not by itself prove that the original acquisition had the same capability or scope.

Agree which source files, analysis sessions and selected maps belong in the handover. Identify the actual package paths or stable references so a reader can locate the record behind a report image. A screenshot may be sufficient for a particular explanation while the project separately requires native acquisition data. Describe those deliverables accurately. Do not call a PDF image a complete dataset or claim that it preserves every channel and setting needed for further technical analysis.

The digital reporting workspace can hold the reviewed mapping table and narrative, including supported DOCX and XLSX imports. It does not read native ECA files or attach examination maps through its logo fields. Keep the actual images and acquisition data in the agreed external package. The generated report organizes supplied evidence references; it does not independently validate the channel mapping, interpret signals or establish the coverage of the physical examination.

The equipment tracker can organize the probe, instrument and scanner references supporting the event. It does not establish how they were configured for a particular pass. The procedure draft workspace can help structure proposed reporting responsibilities for review, but it cannot approve a channel configuration or a surface-mapping assumption. Keep the actual setup and technical decision connected to the reported result.

The electromagnetic and ultrasonic equipment buyer guide addresses broader method and procurement questions. This worksheet concerns a specific examination’s data relationship. Avoid using product capability descriptions as substitutes for the source event record. A useful report identifies what was acquired and interpreted on the component, including limitations, rather than listing everything the selected instrument could theoretically support under other configurations or conditions.

Choose a known component reference and locate its relationship in the delivered map. Then choose a reported indication and trace it back to the source pass, selected channel context and physical datum. Check orientation, units, map boundaries and the meaning of the color scale. This two-way review reveals errors that are difficult to see by inspecting a visually convincing image alone. Any unresolved mismatch should return to the responsible source review rather than be corrected by guesswork during layout.

Use the report buyer-review guide for wider package checks and replace the fictional worksheet row with actual reviewed evidence. The completed map record should let the recipient distinguish source acquisition, selected signal presentation and physical examination scope. It makes ECA imagery useful for communication while preserving the limits of the data and the separate responsibilities for interpretation, measurement, coverage assessment and technical acceptance.