Omaha NDT Reporting for Retired Generation Asset Records

An equipment archive is useful only when the reader can tell what happened, to which physical item, and under which instructions. Retired generation assets make those questions especially important. An old report might describe equipment while it was operating, a later record might concern a removal activity, and a current request might ask about a component held in storage. Those are different events. A new digital document should clarify their relationship without implying that all three have the same technical purpose.

The Omaha Public Power District’s energy portfolio provides regional generation context, including Fort Calhoun’s cessation of operations in 2016. The NRC’s Fort Calhoun decommissioning information provides separate facility context. Fort Calhoun is outside Omaha. Historical schedule statements on a source page should not be treated as a current project schedule, and neither source establishes that the organizations use NDT Connect or endorse this reporting approach.

This guide concerns document provenance and bounded examination records. It does not provide decommissioning instructions, radiological clearance criteria or a records-retention rule. The free editor can organize tables and produce a browser-generated PDF, while a verified account supports private report storage and revisions. Those capabilities help present evidence; they do not establish the present condition, disposition or release status of an asset merely because its historical records have been imported.

Give the original examination date its own field. A document digitized today may describe an examination performed many years earlier. If the new preparation date is placed where a reader expects the examination date, the archive can accidentally appear to contain a recent inspection. State whether the new document is a transcription, an index, a review summary or the report of an actual new examination. The description should remain visible when the PDF is separated from its covering email.

Preserve the source document’s issue date and revision independently. An examination may have occurred before the original report was issued, and a corrected version may have followed later. Keeping those dates distinct allows a reviewer to reconstruct the sequence without guessing. Where the original record contains an ambiguous date or an unreadable field, label that uncertainty. A plausible date inferred from the surrounding folder is not equivalent to a date confirmed in the source.

For a current examination of a retained item, start with the current event and link the historical evidence as supporting material. Do not overwrite the old event date to make the archive match the new report. The current examiner’s scope may differ substantially from the original scope. A clear event chain lets the responsible technical reviewer decide which earlier evidence remains relevant without presenting all archived observations as newly verified facts.

A station equipment tag often identifies a function or location, while a manufacturer serial identifies a particular physical item. Retirement, removal and storage can break the familiar relationship between them. Retain both references where available and describe their verified relationship. A component that occupied a tagged location does not become identical to every replacement that later occupied the same location. Historical report applicability depends on the physical item and the documented examination scope.

Record the state relevant to the event: installed at the time of examination, removed before examination, held in storage or another state confirmed by the responsible organization. Avoid converting an old operating description into a present-tense statement. A historical report saying that an item was installed does not prove that it remains installed. The archive author should identify the source of any current location or state information and distinguish it from the original examination record.

When identifying marks are incomplete, preserve the evidence used to establish the relationship. That might be an authorized removal list, a controlled photograph reference or an owner-confirmed cross-reference. The editor does not authenticate these records. If the relationship is unresolved, use a clear identity question rather than assigning the nearest matching serial. It is better for an archive to expose a gap than to conceal it behind a confident but unsupported asset mapping.

Historical examination reports should retain the procedure identifier, revision and evaluation basis that actually governed the event. Replacing an older document reference with a newer edition can falsely suggest that the historical work was performed under requirements that did not apply to it. A current engineering review may consider whether additional work is needed, but that is a separate decision with its own author, scope and reference. The archive should preserve the distinction.

Do not reconstruct missing acceptance criteria from memory. A familiar method name or standard family is not enough to establish the original instruction. If the archived report omits a necessary reference, identify the missing information and the responsible records owner. The report can accurately state what the source contains while declining to infer what it does not contain. This protects the value of the available evidence without pretending that the archive is complete.

An old acceptance statement should be attributed to the source record and its scope. It should not be promoted into a current fitness, service-life or reuse conclusion. If a retained component is being considered for another purpose, the responsible organization must determine the required assessment. The reporting tool provides fields for user-supplied criteria and evaluation; it does not decide whether historical acceptance remains applicable to a changed configuration or proposed use.

The DOCX and XLSX importer can reduce manual entry when a source already contains a usable table. Preview the selected table before applying it. An archive workbook may combine transcribed results, document-index rows and reviewer comments on separate sheets. Identify which one you are importing and what each row represents. An index entry that names a report should not become a result row that appears to describe an examination the current author performed.

Record the original issuer, report number, revision and source location in the new document. A file name alone may change during an archive migration, so retain the stable identifiers shown inside the original record where available. If information was transcribed from a scan into a workbook before import, identify that intermediate step and verify the transferred values. The current product imports supported document tables; it does not authenticate the original report or recover illegible handwriting.

Keep uncertainty visible during cleanup. A blank source cell might mean not recorded, not applicable or something that cannot be determined from the surviving document. Do not replace it with zero or an acceptance statement simply to complete the table. Use explanatory wording that accurately reflects the source and, where necessary, keep the item open for records review. A polished PDF should improve legibility without hiding the limitations of the underlying evidence.

Older files may use different unit conventions or abbreviated headings. Preserve the source units and clarify them before combining records. If the responsible team requires a converted value, label it as a conversion and retain the original value beside it or in the supporting record. Avoid silently replacing the original measurement. A reader should be able to distinguish a source observation from a later calculation or a value entered for comparison.

A nominal dimension, a measured dimension and a reference value can look similar in a sparse spreadsheet. Determine their roles from the authorized source rather than assuming that every number is a test result. Likewise, an instrument setting is not automatically a measured property of the component. Use column names that retain the original meaning. If the source does not support a confident interpretation, state the ambiguity instead of creating a more precise-looking but unsupported data set.

Be cautious about apparent trends across archived reports. Different locations, surface conditions, configurations or examination procedures can limit comparability. A sequence of numbers sorted by date is not by itself a defensible degradation assessment. The archive can provide the relevant references and identify differences for review, but it should not claim a rate of change or remaining life without the separate technical work needed to support that conclusion.

An NDT finding, a property transfer, a waste classification and a radiological release decision answer different questions. Keep the relevant records in separate categories even when they concern the same physical item. A document package may need all of them, but their presence together does not make one a substitute for another. The archive index should show the responsible issuer and purpose of each record rather than presenting a single broad accepted status.

The same boundary applies to storage and reuse. A component can have a well-organized historical report without being approved for a new installation. Record any current disposition only from an authorized source and attribute it appropriately. The report author should not infer that a removed item is reusable, unrestricted or safe to handle because the last available examination recorded no reportable indication within its limited scope.

Protect the organization’s actual access and distribution requirements. A private saved report is available within the product’s account workflow; it is not an automatic submission to an owner’s archive, regulator or document-control platform. Confirm what may be included and who may receive the final packet. Keep sensitive supporting material in the authorized system and reference it appropriately rather than assuming that every archive item belongs in a broadly circulated PDF.

Imagine a fictional archive containing report OM-EX-17 for component serial EX-S104, examined while installed at location EX-P02. A later storage list names EX-P02 but does not include a serial. The team is asked to prepare a readable report packet for a retained component. The author records the original examination identity and flags the missing relationship between the storage entry and the physical item instead of assuming the location tag proves continuity.

The owner then supplies an authorized removal record connecting EX-S104 to storage entry EX-B08. The new archive summary records that cross-reference and its source. It keeps the historical examination date, original procedure revision and reported result unchanged. A current visual condition note is entered as a separate event with its actual scope, rather than appended to the old result as though the original examiner had observed the stored component.

The resulting packet helps a reviewer locate the evidence and understand what remains unresolved. It does not declare the item suitable for reuse or establish any release status. All identifiers in this example are fictional. The useful outcome is the explicit chain between a historical installed item, an authorized movement record and a current retained item, with each event retaining its own date, issuer and evidentiary limits.

An archive can contain an original signed report, a later spreadsheet transcription and a reviewer’s summary of that spreadsheet. Identify those layers rather than treating the most convenient file as the original evidence. A reviewer may reasonably use the summary to navigate the collection, but should be able to reach the source when a value or qualification matters. Preserve the original file in the organization’s authorized repository and give the new report a clear reference to it.

If two copies disagree, record the discrepancy and the basis for selecting an authoritative version. A later file-modification date does not necessarily establish that a document is a later issued revision. It may simply reflect a migration or download. Confirm revision status through the document’s controlled identifiers or the records owner. Where that confirmation is unavailable, retain the uncertainty instead of quietly discarding the conflicting copy and making the archive look more certain than it is.

A current reviewer can add a useful interpretation, but attribution matters. Label the interpretation with its own purpose and source references so it cannot be mistaken for the original examiner’s statement. If the review changes the proposed use of an item or identifies a need for additional examination, carry that action through the responsible organization’s process. The archive document should make the recommendation traceable without rewriting what the historical examination actually established.

A transcription correction and a new examination are different reasons to update a document. State which occurred. If a digit was entered incorrectly, identify the corrected field and the source used to verify it. If a new examination has been performed, give that event its own date, scope and report relationship. Avoid using a vague revision description such as updated information when the change affects how the evidence should be interpreted.

Verified accounts support sequential report-number patterns, private search and immutable issued versions with later revisions. Use a stable number to identify the document and descriptive fields to identify the asset. Packing every changing storage location into the report number can make the number misleading when the item moves. A clear asset reference and revision explanation provide more durable context than an elaborate identifier that tries to encode the entire archive history.

Before issuing the PDF, ask a reviewer to follow one item from the archive index to its source examination record and current identity reference. Check that the dates, units, source revisions and limitations remain readable after export. Company and client PNG or JPEG logos can be added where authorized, but their presence should not suggest that the original issuer has approved a new transcription. Keep the author and purpose of the new document clear.

The equipment tracker, certificate manager and calibration reminder can help organize current user-entered records and supporting dates. They do not retroactively verify historical personnel authorization or instrument condition. For an archive, retain the qualification and equipment references that actually accompany the source event, and identify missing evidence honestly. The downloadable worksheet provides fictional reconciliation questions to adapt, not a regulatory retention schedule or a mandatory decommissioning checklist.