Keep CR Plate and Image Identities Traceable

A computed radiography plate can participate in many examinations over its working life. Its equipment identifier therefore cannot uniquely identify a particular exposure or image. Start the report record with separate fields for the plate, the examination event and the retained image. Connect them through the actual source documentation. This makes it possible to retrieve one result without assuming that every image carrying the same plate reference belongs to the same component, date or examination condition.

The distinction matters most when plates return quickly to service and several people handle acquisition, scanning and reporting. A plate number may be correctly transcribed while the associated weld or image is wrong. The worksheet creates a deliberate event relationship rather than relying on memory or the order of items on a desk. It does not establish an exposure technique or approve image suitability; those decisions remain in the responsible radiographic procedure and technical review process.

DÜRR NDT’s description of computed radiography distinguishes exposure of the imaging plate, scanner readout and erasure for reuse. That sequence explains why the physical plate and the resulting digital image need separate references. The report should identify the actual event that produced the retained image. Do not infer a new exposure merely because the plate was scanned or a new file appeared, and do not infer that an earlier image belongs to the plate’s latest use.

Keep the source event description precise. A repeat exposure, a new readout attempt and a later image export are different activities, even if all involve the same plate identifier. Record what actually happened rather than selecting a generic retake label. The responsible technical process determines whether the available record is usable and what follow-up is needed. The reporting task is to preserve that history so the recipient can understand which acquisition and readout support the stated result.

Choose the examination-event reference already used by the project wherever possible. Connect it to the component, weld or view identifier and the applicable date or sequence. Avoid inventing a second numbering system that cannot be reconciled with the field log. If an additional local reference is needed for the report, preserve a clear crosswalk to the source event. The identifier should distinguish separate uses of the same plate without requiring the recipient to decode an undocumented filename convention.

A useful event reference remains meaningful when the digital file is renamed or moved to a different package folder. Keep the image’s actual system identifier where available and the human-readable filename used for delivery. Do not treat either as automatically authoritative if the source metadata conflicts with the field record. Record the discrepancy and obtain the responsible resolution. Consistent-looking names are helpful for retrieval, but they are not a substitute for evidence linking the physical examination to the retained image.

The plate, cassette and scanner carrier may have different identifiers and may not remain permanently paired. Preserve the actual relationships needed by the project rather than using one convenient equipment number for all three. If plates move between cassettes, record the event-specific pairing through the source workflow. A cassette label alone should not be assumed to establish which plate was exposed or which image was produced unless the actual records support that connection.

Carestream’s HPX-1 Plus product description describes handling single, multiple and custom-cut plates. This illustrates that the scanner workflow can involve different physical arrangements; it does not establish the identity of any particular examination record. For a report, preserve the actual plate and event relationships used on the job. Do not infer one image per scanner load or one permanently paired cassette per plate from a general product description.

Where timing is part of the required record, distinguish exposure time, scanner readout time and later export time. A file’s modified date may reflect copying or processing rather than the examination. Use the source records and identify the time convention where it matters. Do not reconstruct missing event times from folder order or assume two systems used the same clock. An honest unknown is preferable to an invented timestamp that creates a false sequence of plate use.

If the recorded sequence appears inconsistent, preserve the conflict for review. For example, an image may appear to precede its listed exposure because one record uses a different time zone or because the event link is wrong. The report preparer should not diagnose the cause without evidence. Record the actual correction and its basis through the project process. This keeps the chronology useful for tracing plate reuse while avoiding unsupported conclusions about acquisition conditions or the validity of the image.

Identify the scanner and the readout session that produced the retained image. Where the project requires particular settings or verification evidence, reference the actual record rather than copying a default configuration from a previous job. A scanner model name does not describe the settings used for an individual event. Keep the relationship concise but retrievable, especially when the same exposure batch was processed across more than one scanner or during more than one session.

Do not confuse a scanner equipment record with proof that a specific image met the examination requirements. Equipment status, event configuration and image evaluation are separate questions. The responsible technical review determines the significance of a settings discrepancy or missing verification record. The worksheet provides a place to link that review and its outcome. It should not automatically mark an image acceptable because the scanner appears in the equipment register or because a file was successfully generated.

Record the source convention that connects the image to the component and exposure view. A plate can be loaded or displayed in different orientations, and later rotation may make the picture easier to read without preserving an obvious physical direction. Keep the reviewed orientation and location reference available. Do not assume that the top of the displayed image corresponds to the top of the component or that a plate identifier establishes the direction in which a weld was examined.

Where one examination uses several plates or views, identify the relationship between their physical extents through the actual technical record. The worksheet does not define required overlap or coverage. It records the approved or reviewed map that supports the report. If the images cannot be connected to the intended locations, leave that question visible. Arranging files in a visually continuous sequence is not evidence that the physical examination covered the intended region without gaps or ambiguity.

In a fictional shift, plate P4 is used for event E101 on weld W7 and later for event E118 on weld W9. The scanner exports images into a folder whose names begin with the plate identifier. A coordinator imports the list into a report and assigns both files to W9 because that was P4’s latest use. The plate number is correct in both rows, yet the examination relationship is wrong. The error cannot be resolved by checking the plate register alone.

The team reconciles each image to its actual exposure and readout records, then restores the E101-to-W7 and E118-to-W9 relationships. It preserves the plate identity as supporting equipment information. This hypothetical example establishes no reuse interval, exposure requirement or image-quality threshold. Its purpose is to show why a reusable detector identifier cannot replace the event-level link between the inspected item and the digital record used for interpretation and reporting.

If the examination process identifies a possible plate-related concern, record the affected plate and the image events referred for review. Do not diagnose the cause from the report table or erase a finding because it appears repeatedly. Similar-looking features can require technical investigation. Preserve the responsible assessment and its scope, including which images were reviewed and what follow-up was required. A plate maintenance entry and an interpretation decision should remain distinguishable even when they are related.

Keep any later plate withdrawal, cleaning or replacement record separate from the disposition of earlier images. A change to the equipment’s current status does not automatically establish that every prior examination is invalid or unaffected. The responsible process determines which records need review. The event crosswalk makes that review practical by identifying the actual uses of the plate, rather than forcing the team to search every report containing a broad scanner or equipment description.

When a result is replaced or supplemented, identify the actual activity that produced the additional record. A repeated exposure has its own examination event, while another processing or export operation may relate to the existing image. Use the terminology supported by the source workflow. Do not label every additional file a new exposure or silently replace the earlier image reference with the newest one. The recipient needs to understand which record controls the report and why the history contains more than one file.

If a source record describes another readout attempt, preserve its actual relationship and technical disposition without assuming that it provides equivalent information to the earlier readout. The reporting guide does not prescribe rescanning or determine whether such a record is suitable. Keep the responsible assessment retrievable. That approach avoids turning a practical identity table into an unsupported instruction about detector operation, while still making the sequence clear enough to resolve duplicate files and report references.

A batch can contain images from several plates, components and exposure events. Check the identifiers before sorting or combining records. Do not align two spreadsheets solely by row position when one lists exposures and the other lists scanner outputs. Missing or repeated entries can shift the entire relationship. Use the actual event and image references, and retain an exception list for records that cannot be matched. A partially reconciled batch should not become a fully matched report by default.

When importing a reviewed table, preserve identifier formatting, including meaningful leading zeros and separators. A numeric conversion can turn two distinct event labels into the same displayed value. The reporting workspace’s preview helps inspect the candidate table, but it does not establish that the underlying event correlation is correct. Complete that reconciliation through the actual source records before relying on the table as evidence for the report. Keep unresolved rows visibly separate from those with a confirmed relationship.

The equipment tracker can hold plate, cassette and scanner references where useful. Treat it as supporting equipment information. It does not automatically build the history of exposures or link images to components. Preserve the actual event crosswalk in the report package or the organization’s controlled examination records. A well-maintained equipment entry helps identify the physical item, but the event log explains what that item was used to record on a particular occasion.

The CR and detector workflow guide addresses broader equipment-workflow choices. This page concerns the identity of individual records after a CR examination. Keep those questions separate when discussing the handover with a client. Choosing an appropriate system does not eliminate the need to reconcile plate reuse, and a detailed plate-event table does not independently demonstrate that the system or technique was suitable for the project.

Use the free reporting workspace for the reviewed cross-reference table and notes. It supports DOCX and XLSX table imports after preview; it does not read CR scanner files or attach radiographic images through its logo fields. Keep native or agreed image files in the actual external package. State the source location accurately and make sure the report’s image references resolve to the delivered records rather than to temporary filenames used during preparation.

The procedure draft tool can help organize proposed responsibilities for event identification and handover, subject to the appropriate review. It cannot approve plate handling, erase cycles or image suitability. Before delivery, trace one report result to its image, readout and exposure event, then back to the correct component. The buyer-review guide adds wider package checks, while this worksheet concentrates on the reusable-plate identity problem.

If work transfers between crews, identify whether each listed event awaits readout, interpretation, identity reconciliation or report preparation. Those are different unfinished tasks. A note saying plates pending can refer to physical items while another team assumes it refers to image review. Use the actual event references and state where the relevant plate or retained image is located. Do not rely on a shared memory of the last plate handled. A clear stage description lets the receiving team continue the correct activity without accidentally treating an unreviewed image as a completed result or a reused plate as evidence of the earlier event.

If a later review changes the component-to-image relationship, record the correction and its evidence through the applicable amendment process. Identify the affected report rows and any earlier delivery that used the incorrect link. Do not fix the filename alone and assume every downstream record now agrees. A corrected source relationship can affect several reports or package indexes, particularly where the same image was copied for different recipients. The project process determines the necessary notifications and technical reassessment.

Replace the worksheet’s fictional entries with actual plate, exposure, scanner and image references. Keep the completed crosswalk with the examination and delivery records. Its value is a reliable connection across reuse: the physical plate can return to service while the image remains tied to the correct historical event. The recipient can then retrieve the right evidence without confusing detector identity, acquisition chronology, technical evaluation or the later administrative act of exporting a report.