Map Additive Build Records to NDT Results

An additive build record can describe several parts and witness items produced during one machine run. An NDT report, however, must identify the physical item and condition that the examination actually represents. The evidence map connects those two levels. It should let a reviewer move from a delivered part serial to its build association, relevant postprocessing records and the exact examination evidence, without assuming that every item from the same build received the same treatment or inspection. Begin with the part identity used by the owner's controlled manufacturing records.

Keep the design part number, individual serial, build identifier and temporary inspection label in separate fields. Each answers a different question. The part number identifies the design configuration; the serial distinguishes an individual item; the build identifier connects manufacturing context; the inspection label may only help a particular laboratory handle the work. If one of those relationships is unverified, preserve the uncertainty and the source needed to resolve it. Do not infer an identity solely from an item's appearance, its position in a delivery tray or an abbreviated filename.

Record the drawing or design revision and the production-plan reference that govern the item. The evidence map should point to the approved manufacturing information rather than attempting to reproduce a complete build recipe inside an inspection report. If the plan changed between the build and a later operation, identify the change and the relevant disposition. A reviewer needs to understand which configuration and process references apply to the item being examined, particularly when similar serials were produced under different revisions or when an experimental build is being compared with production work.

NASA's explanation of its additive manufacturing standards for human spaceflight describes a production plan linking build orientation, witness testing and inspection considerations. That is a program-specific example, not a universal requirement for every commercial print. For this editorial worksheet, retain the applicable plan reference and the relationships supplied by the actual manufacturer. The free reporting tool does not approve a manufacturing process, establish a qualified production route or turn an engineering development part into accepted flight hardware.

Where the controlled build record uses positions or item labels, connect the physical part to the specific position reference. A build image may help, but the association should remain understandable after the item has been removed from the build arrangement. Identify the orientation convention and the source drawing or map used to interpret the position. Do not treat a convenient screenshot as a substitute for the manufacturer's controlled association if the two differ. If the inspection laboratory receives only the part and a delivery note, state which build relationships were supplied and which were not.

Several items can share one build identifier while following different later paths. One may remain in an intermediate condition, another may be machined and a third may be retained for development work. The evidence map should preserve the individual route rather than applying a common completed status to the entire build. If items were transferred between containers or renamed during laboratory receipt, maintain a documented cross-reference. The practical question is whether a person unfamiliar with the original build can establish that the examination evidence belongs to this particular item, not merely to a similar part from the same job.

Describe the actual state represented by the examination using the manufacturer's records and the terminology of the inspection instruction. Relevant steps may include removal from the build arrangement, heat treatment, machining, surface preparation or another specified operation, depending on the process and part. Record only the operations and evidence actually supplied. A label such as finished should not hide uncertainty about which operations occurred before the examination. Connect each relevant stage to its traveler or processing record so the timing of the inspection can be reconstructed.

The public scope of ASTM E3166 for post-build examination of metal AM aerospace parts notes that geometry, surface finish and manufacturing process affect NDT data. The reporting consequence is to identify the state examined instead of treating all records for the serial as interchangeable. This guide does not select a method or prescribe a processing sequence. If a later operation changes the inspected feature or surface, the responsible technical team determines what that change means for the existing evidence and any subsequent examination requirement.

A witness coupon or other test item may share a build or processing relationship with a production part, but it remains a separate physical item. Give it its own identity and record the documented relationship to the production item or population. When a witness result is included in the package, say which record it comes from and what the governing plan authorizes it to support. Do not copy a coupon result into a production-part NDT row as though the production part itself was examined in the same way.

The map can contain a dedicated witness-evidence column or a separate linked table. Keep the witness item's own processing history clear, especially if it did not follow the same later operations as the delivered part. If the association is supported only by a supplier statement, identify that source rather than upgrading it to an independently verified fact. The report author is organizing supplied evidence; deciding whether a witness result is representative or sufficient belongs to the responsible technical and quality process for the actual program.

An examination may address a defined surface, volume, feature or region rather than every part of a complex geometry. Retain the coverage description from the approved procedure and the examiner's actual record. Link any marked region to a drawing, model view or controlled feature designation that the recipient can interpret. Avoid broad statements such as fully scanned when the source record identifies exclusions or limited access. A coverage field should make the bounded claim visible beside the result, not rely on the reader finding a qualification elsewhere in the package.

If different methods address different features, keep those records distinguishable. A surface examination and a volumetric examination may be related to the same serial but have different scopes, stages and references. The evidence map should show which record answers which question. It should also distinguish a requested examination that was not completed from an examination completed with a documented limitation. The reporting software cannot infer coverage from an imported table or determine whether the examination was adequate for the design's critical features.

Where the examination creates instrument data, identify the source package, relevant dataset or image reference and the software context needed by an authorized reviewer. Keep the original record distinguishable from a screenshot or a presentation export. When files are repackaged for delivery, retain a manifest that maps the delivered names to the intended source records; changing a folder structure should not erase the association. A PDF can summarize findings and point to the source, but it does not necessarily contain all information required for independent review. The evidence map should explain where the authoritative data resides and which item, stage and examination event it represents, using the organization's approved storage and access arrangements.

NDT Connect's free reporting workspace imports editable Word and Excel table content. It does not read native CT volumes, reconstruct a scan or analyze an AM build log. Enter the reviewed findings and usable references, then retain the native evidence separately. If a delivery contains a reduced presentation package, state that boundary and the process for authorized access to the fuller source. Do not claim that a report attachment is a complete digital twin simply because it shares the part serial or includes an image of the design.

Imagine a fictional build B-240 containing parts P-101 and P-102 plus witness item W-09. Both parts are associated with the same design revision, but P-101 is examined after one recorded processing stage while P-102 proceeds to an additional machining operation before examination. A spreadsheet initially lists the same stage description for both because the author copied the first row. The evidence map should reveal the mismatch by linking each examination to its own traveler reference. Shared build membership does not justify a shared examination-state description.

In the example, W-09 has a separate test report referenced by the production plan. Its result remains in the witness-evidence relationship rather than replacing either part's examination outcome. The corrected package shows B-240 as common context, individual stage records for P-101 and P-102 and a separate association for W-09. If the processing sequence for one part cannot be confirmed, that row remains open for the manufacturer to clarify. The fictional case supplies no acceptance decision; it demonstrates the identity and state relationships the reviewer needs before using the evidence.

Use a row for each meaningful part and examination-state relationship. Include individual part identity, design revision, build and position reference, processing state, examination event, coverage, report reference and any witness association. Add a source or evidence-status field where it helps distinguish confirmed relationships from unresolved ones. Long technical descriptions can remain in the referenced reports, while the crosswalk carries the information required to locate them. Do not let a compressed summary hide the fact that two examinations occurred at different stages of the same item's history.

Before import, check for duplicate serials, truncated identifiers and copied stage labels. A duplicate may be legitimate if it represents another examination event, but the distinguishing fields must make that clear. Separate absent evidence from a deliberately inapplicable relationship. For example, no witness item specified in the supplied plan is different from witness report not received. The editable worksheet provides a starting structure for these distinctions. Adapt it to the actual controlled terminology and have the responsible records owner confirm the associations before treating the crosswalk as a completed handover index.

Open the free digital NDT reporting workspace and import the prepared Word or Excel table. Preview the content, select the intended headers and edit the grid to keep identity, stage and coverage readable. Enter the actual method, procedure, specification and personnel information in their relevant fields. Use the report observations to explain unresolved evidence or bounded findings, and keep the conclusion within the responsible author's authority. Company and client logos can identify the document parties where their use is authorized; they do not establish technical approval.

A draft PDF is available without signup. A verified free account supports private saved reports, assigned numbers and revisions. Keep the report number separate from the part serial and build identifier so each remains stable for its own purpose. Before issue, inspect the downloaded PDF and follow several cross-references to their source documents. The equipment tracker can organize instrument records, and the procedure draft workspace can support a document prepared for responsible review. Neither replaces the program's qualification, process-control or part-acceptance decisions.

If further work occurs after the reported examination, retain the earlier record as evidence of the state it actually describes. Record the new operation and the responsible determination of how existing inspection evidence may be used. Do not change an old report date or stage description merely to make it appear to describe the latest part condition. Where a new examination is required by the authorized process, give that event its own reference and connect it to the same individual part through the updated history.

A corrected identity association can also require attention even when no physical processing changed. If a laboratory label was mapped to the wrong serial, preserve the correction, its supporting evidence and the authorized redistribution of affected reports. Do not quietly rename the file and assume the recipients will discover the change. The evidence map should show the current verified relationship while the controlled record process retains the history. This lets the recipient distinguish a documentation correction from a new inspection or a change to the physical item.

Choose a delivered serial and trace the package as an external reviewer would: design revision, build relationship, processing state, examination coverage, report and native-data reference. Then choose a witness item and verify that its separate identity and authorized relationship are clear. Use the actual delivery package rather than a working directory that contains files the recipient will never receive. If a reference requires a private system or specialist viewer, confirm the approved access arrangement and state the boundary in the handover notes.

The resulting map should be useful even when part of the package is unresolved. It can show exactly which identity, stage or source record needs clarification and who owns that action. Avoid converting the completeness of a document bundle into a claim of part acceptance. The value of the free reporting workflow is a readable, retrievable account of the evidence supplied for the examined part, with enough context for the responsible manufacturing and technical teams to make their own documented decisions.