Material Traceability

Material traceability is the ability to prove—using objective records—that the exact material used in a delivered part can be traced back to a specific melt/heat, lot, or batch, and that every transformation step (additive build, HIP/PM-HIP densification, machining, heat treat, coating, inspection, and shipment) was performed under controlled conditions. In aerospace and defense manufacturing, traceability is not “nice to have”; it is a core control that supports AS9100 quality management, NADCAP special processes, contractual flow-downs, and U.S. defense requirements such as DFARS material restrictions and ITAR data controls.

For engineers, traceability protects performance: you can connect a nonconformance or fatigue issue to a specific powder lot, HIP cycle, or heat treat. For procurement and program teams, traceability reduces schedule risk: you can close out First Article Inspection (FAI) packages, respond to customer audits, and isolate suspect material quickly without grounding an entire lot of hardware. This article breaks down what “good” traceability looks like in real production workflows—especially where additive manufacturing (AM) and post-processing are involved.

Heat/lot tracking basics

Traceability starts with understanding what you are actually tracing. The common identifiers are:

Heat (melt) number: Identifies a specific melt of material produced by a mill or foundry (typical for wrought bar, plate, forgings). Mechanical properties and chemistry are tied to this heat.

Lot number: Identifies a production lot, which may be a subdivision of a heat, or a discrete manufacturing run (common for powders, wire feedstock, fasteners, and consumables). For AM powders, “lot” can represent a specific atomization run and packaging campaign.

Batch number: Often used interchangeably with lot; in regulated environments, define the term in your procedures and ensure it matches supplier documentation.

In practice, aerospace/defense shops track all three layers: material identifier (heat/lot), internal receiving ID, and part-level serialization. The goal is a one-to-one mapping from each finished part to the material identifiers and key process records.

Example: powder bed fusion (PBF) traceability chain. If you are building a Ti-6Al-4V part on DMLS/SLM equipment, you typically need to track:

1) Powder receipt: Supplier name, powder alloy/specification, powder lot, certificate details, container IDs, and receiving inspection results (including moisture/oxygen checks if required by your control plan).

2) Powder handling: Sieve events, blend events, number of reuse cycles, and any mixing of virgin/reclaimed powder. If you allow blending, your procedure should define allowable ratios and how the “effective lot” is assigned (many customers prohibit mixing lots without written approval).

3) Build assignment: Build job ID, machine ID, parameter set revision, build plate ID, and which powder lot(s) were loaded. If multiple lots are in the hopper, you need clear rules for how the build is traced and how the hopper is purged/cleaned between alloys.

4) Part identification: Part serial number (or unique identifier) is applied as early as practical (e.g., witness tab, tag, or traveler) and then maintained through separation from the plate, HIP, machining, and inspection.

For PM-HIP and HIP workflows, the “material” may not start as a bar heat. PM-HIP commonly begins with powder that is filled into a can, degassed, sealed, HIPed, then machined. In that case, the traceability unit often becomes the can/billet ID, tied back to the powder lot(s), can material heat, weld procedure, degas cycle, and HIP cycle.

Key control point: Define your traceability unit and stick to it. For wrought, it may be a cut piece from a heat. For AM, it may be a build job. For PM-HIP, it may be a can or consolidated billet. Your travelers and ERP/MES must reflect that reality.

Cert packs and records

Aerospace and defense customers rarely accept “trust us” statements. They expect a certification package (often called a cert pack or data pack) that includes objective evidence. The exact contents vary by contract, but strong cert packs are consistent, legible, and internally cross-referenced by part number, revision, and serial number.

Typical cert pack elements include:

Certificates of Conformance (CoC): The supplier’s statement that the delivered parts meet all requirements. A defensible CoC includes purchase order, drawing/spec revision, quantity, serial numbers (or lot), and a clear statement of compliance to specified standards.

Material test reports (MTR/MTC) / mill certs: Chemistry and mechanical properties tied to the heat/lot and to a specification (e.g., AMS, ASTM). Ensure the cert references the exact alloy condition (solution treated/aged, annealed, etc.).

Powder certifications (AM): Chemistry, particle size distribution, flowability, apparent density, and oxygen/nitrogen/hydrogen limits when specified. Many programs also require retained powder samples and periodic verification testing, especially when powder reuse is allowed.

Process certifications: HIP records (cycle charts and setpoints), heat treat records, welding/brazing records (if applicable), and NADCAP approvals for special processes. If you outsource special processes, include subcontractor CoCs and their accreditation status.

Inspection records: First Article Inspection (FAI) per AS9102 when required, in-process inspection logs, final inspection results, and metrology evidence such as CMM reports. For critical hardware, include NDE results such as CT scanning, dye penetrant, or radiography, along with acceptance criteria and inspector qualifications where required.

Nonconformance and concession records: If any deviations occurred, record disposition (use-as-is, repair, scrap) and customer approvals. A “clean” pack is good; a transparent pack is better. Hidden discrepancies are what trigger audit escalation.

Configuration control evidence: Document revisions, process plan revisions, AM parameter set revisions, and inspection plan revisions. In regulated environments, traceability must include which revision you built to, not only what you built.

Practically, a cert pack should read like a story: material received → controlled processing → verified conformance → shipped under controlled conditions. The most common failure is missing cross-references: for example, the HIP chart exists, but it is not linked to the specific part serials, or the powder cert exists, but it does not match the lot number recorded on the build traveler.

Chain of custody

Chain of custody is the controlled, documented custody of material and parts as they move between internal operations and external suppliers. It is especially important in defense/aerospace because:

Counterfeit risk: Without custody controls, it is difficult to prove you did not receive substituted material.

Mixed lot risk: Mislabeling or physical commingling can destroy traceability instantly—particularly with powders, small machined details, or bulk heat-treat loads.

Regulated data risk: With ITAR programs, custody includes controlling technical data access (drawings, build files, parameter sets) and ensuring only authorized parties handle controlled information.

Effective chain-of-custody controls include:

Receiving quarantine and verification: Incoming material is tagged and quarantined until paperwork and receiving inspection are complete. For powders, confirm container integrity, label accuracy, and storage conditions (humidity control, segregation by alloy).

Positive identification (PID) throughout processing: Maintain identification through cutting, deburring, HIP, heat treat, and machining. Where physical marking is not feasible, use travelers, sealed totes, and controlled staging locations. For high-mix shops, add barcode/RFID to containers and travelers.

Segregation by status: Clear separation of accepted, nonconforming, awaiting inspection, and scrap prevents accidental use. This is a frequent AS9100 audit focus area.

Subcontractor control: When you send parts out for HIP, heat treat, coating, or NDE, include a purchase order with explicit traceability requirements: serial/lot list, required records, handling/packaging requirements, and return of unused material (e.g., witness coupons). Ensure the subcontractor returns documentation that matches your identifiers.

Special note for AM builds: If a build includes multiple part numbers or multiple customer programs, custody becomes more complex. Best practice is to treat each build as a controlled lot and to avoid mixing programs with different flow-downs in the same build unless your procedures explicitly address documentation, export control, and segregation.

Special note for HIP and furnace loads: Heat treat and HIP often process multiple parts in a single load. Your load map (or load record) must clearly list the serial numbers included, the fixture arrangement if required, and the cycle used. If parts from different material lots are combined in one load, you still must retain traceability for each part back to its starting material and confirm that load-level records can be unambiguously tied to part serials.

Common audit findings

Auditors (customer, AS9100, NADCAP, or internal) are not looking for perfect paperwork; they are looking for evidence that your system reliably prevents escapes. The following issues repeatedly show up in aerospace and defense audits:

1) Lot/heat mismatch between documents. The traveler says Heat X, but the mill cert says Heat Y, or the powder lot recorded on the build sheet does not match the supplier cert. This is often caused by transcription errors—solve it with scanning/barcodes and controlled data entry.

2) Incomplete linkage between part serials and process records. A HIP chart exists, but it is not tied to the serial numbers in that run. Or the CT scan report lists only a “job number” that is not traceable in your system.

3) Powder reuse and blending not controlled. Missing sieve logs, missing reuse cycle counts, undocumented virgin/reclaim ratios, or uncontrolled topping-off of hoppers. For PBF, this is one of the fastest ways to lose customer confidence because it directly affects oxygen pickup, porosity risk, and consistency.

4) Commingling of parts. Unmarked parts combined in a single tote, mixed WIP areas, or mixed scrap bins. Once commingled, you may be forced to scrap parts because traceability cannot be re-established.

5) Special process accreditation not current or not applicable. A subcontractor CoC is provided, but the NADCAP scope does not cover the specific process (e.g., heat treat of that alloy family) or the accreditation was expired at the time of processing.

6) Calibration and measurement traceability gaps. CMM or inspection tools out of calibration, missing calibration stickers, or unclear linkage between measurement results and calibrated equipment. Remember: material traceability is weakened if the verification evidence is questionable.

7) Data integrity issues. Hand-edited PDFs, missing signatures, or records that cannot be shown to be controlled. Digital workflows can solve this, but only if access control, revision control, and audit trails are implemented.

Preventing these findings requires a combination of procedure clarity, training, and system design. The most resilient systems reduce manual transcription, force required fields, and make the “right way” the easiest way to execute.

How to request traceability

Procurement teams often ask for “full traceability,” but that phrase can mean very different things. To get what you need (and avoid RFQ delays), specify traceability requirements clearly and in the same language your suppliers use.

Use the following practical checklist when creating an RFQ or purchase order:

1) Define the traceability level. Specify whether you require traceability to heat, lot, build (AM), or can/billet (PM-HIP). For serialized flight hardware, request part-level serial traceability end-to-end.

2) Call out material and specification requirements. Include alloy, condition, and governing specs (AMS/ASTM), plus any DFARS restrictions or domestic source requirements if applicable. If the program requires specific approved mills or powder suppliers, list them.

3) Require cert pack contents explicitly. List required documents: CoC, mill cert/powder cert, HIP/heat treat charts, NADCAP certificates, NDE reports, CMM reports, FAI per AS9102, and any witness coupon testing requirements.

4) Clarify additive manufacturing controls (if applicable). For PBF/DMLS/SLM parts, specify expectations for powder management (reuse limits, blending rules, storage controls), build parameter control (parameter set revision), and build-level records (machine ID, build ID, plate ID). If you require CT scanning or specific porosity acceptance criteria, state it up front.

5) Define serialization and marking requirements. Specify where and how parts must be marked (direct part marking, tag, or packaging label), and how serial numbers must appear on all documents. For small parts where marking is not feasible, require sealed packaging with label control and traveler continuity.

6) Address special process outsourcing. If the supplier will outsource HIP, heat treat, coating, or NDE, require prior approval of subcontractors, evidence of accreditation (NADCAP where applicable), and flow-down of your traceability and record requirements.

7) Set retention and access expectations. State record retention duration (commonly years) and whether you require electronic copies. For ITAR programs, specify how controlled technical data will be handled and who is authorized.

8) Require notification triggers. Ask suppliers to notify you of lot changes, powder lot changes, parameter set changes, machine changes, or any deviation/repair. Traceability is not only about records—it’s about change control.

9) Define what happens if traceability is lost. Contractually, specify that loss of traceability is a nonconformance requiring immediate notification and disposition. This avoids ambiguity when something goes wrong.

When these requirements are written clearly, you reduce back-and-forth and avoid situations where a supplier technically meets the order but fails your program’s compliance expectations.

Digital traceability workflows

Digital traceability is not just scanning paperwork into a folder. In aerospace/defense manufacturing—especially with additive plus HIP plus machining—you need a workflow that preserves data integrity, supports audits, and makes retrieval fast.

A practical digital traceability workflow typically includes:

1) Controlled item master and revisioning. Part numbers, drawing revisions, process plans, and inspection plans are controlled in a QMS/PLM/ERP environment. When a build or job is released, the system records exactly which revision set was used.

2) Digital receiving with verified identifiers. Material certs are uploaded and linked to a receiving lot in ERP/MES. Critical fields (supplier, heat/lot, spec, condition) are captured as structured data—not only as a PDF. Where possible, barcodes on supplier labels are scanned to reduce manual entry errors.

3) Traveler/MES execution with enforced data capture. Each operation (AM build, depowdering, stress relief, HIP, support removal, 5-axis CNC machining, surface finishing) is executed against a digital traveler that requires key fields: operator, machine, program number, parameter set revision, timestamps, and inspection checkpoints.

4) Build records and machine data for AM. For PBF, store build job files, parameter sets, machine logs, and environmental data where relevant. Tie them to the build ID and to the part serials on that plate. This is especially valuable when investigating spatter events, recoater issues, or shifts in oxygen content.

5) Load-based records for HIP/heat treat and NDE. HIP charts, furnace charts, and NDE reports are linked to the load ID and to the serial numbers in that load. A robust system prevents closing the operation until serial lists are attached and verified.

6) Inspection data capture and metrology traceability. CMM results, CT scan results, and other inspection outputs are stored with part serials, acceptance criteria, and the calibration status of equipment used. If a gage is later found out of calibration, you can query affected serials immediately.

7) Immutable audit trail and access control. Digital signatures, role-based permissions, and change history are essential. For ITAR-controlled programs, ensure only authorized personnel can access controlled files, and maintain logs of access and transfer.

8) Packaging and shipment traceability. Shipment records reference part serials/lot, packaging requirements, and CoC. For sensitive programs, custody may include tamper-evident packaging and documented handoffs.

One of the highest ROI improvements is to build a one-click “traceability report” capability: enter a serial number and retrieve the full genealogy—material heat/lot, powder lot, build ID, HIP/heat treat loads, machining programs, inspections, and shipment. This is what turns traceability from a compliance burden into an operational advantage.

Implementation tip: Start by mapping your process as a genealogy tree (material → WIP lots → serials → loads → inspections). Then decide which nodes must be captured as structured fields versus attached documents. Structured fields enable fast queries; attached documents provide supporting evidence. The best systems use both.

In defense and aerospace, the organizations that scale additive manufacturing successfully are the ones that treat traceability as part of the engineering system—not an after-the-fact filing exercise. When traceability is designed into your workflows, you can qualify suppliers faster, close audits confidently, and protect program schedules when issues arise.