What information should be included in a digital traveler for an FAI build?

A digital traveler for an FAI build should include the controlled information needed to execute the part in the approved configuration, record what actually happened, and support the First Article Inspection Report. It should not be treated as a generic shop packet. For an FAI build, the traveler must preserve configuration, traceability, inspection evidence, deviations, and approvals tightly enough that the FAIR can be reconstructed and reviewed without relying on tribal knowledge.

The exact content depends on the customer contract, AS9102 applicability, drawing and model authority, internal procedures, special process requirements, and how well the MES, ERP, PLM, and QMS are integrated. A digital traveler can support FAI execution, but it does not by itself guarantee AS9102 acceptance, customer approval, or audit outcomes.

Core identification and configuration data

The traveler should clearly identify what is being built and under which controlled configuration. At minimum, this usually includes:

• Part number, part name, revision, and configuration baseline
• Work order, job, lot, batch, or serial number as applicable
• Customer, program, purchase order, and flowdown references where required
• Drawing, model, specification, planning, and routing revision references
• FAI type, such as full FAI, partial FAI, delta FAI, or customer-specific equivalent
• Reason for FAI, such as new part, design change, process change, location change, tooling change, or lapse in production

This is a common failure point. If the traveler does not lock the build to the correct drawing, model, planning revision, and customer requirements, later inspection records may be technically complete but tied to the wrong configuration.

Routing and operation-level execution details

The traveler should show the approved sequence of operations and the required controls at each step. This commonly includes operation numbers, work center, responsible role, setup requirements, required signoffs, and hold points.

For an FAI build, operation-level detail matters because the manufacturing method is part of what is being proven. If operators bypass steps, use alternate tooling, or change the sequence without controlled approval, the FAI package may no longer represent the approved production process.

Work instructions, specifications, and acceptance criteria

The traveler should link to the current controlled work instructions and any applicable specifications, standards, and acceptance criteria. This may include visual work instructions, setup sheets, inspection instructions, torque requirements, cure profiles, cleanliness controls, FOD controls, and special handling requirements.

Links are not enough unless document control is enforced. The system should make it clear which revision was in effect at the time of execution and prevent uncontrolled copies from becoming the record of work.

Characteristics and inspection requirements

For an FAI build, the traveler should align with the characteristic accountability expected in the FAIR. This often includes ballooned drawing or model characteristics, characteristic numbers, nominal values, tolerances, inspection method, gage or equipment used, sample requirement, and actual results.

Where AS9102 is applicable, the traveler should support the data needed for the FAIR forms, but the FAIR itself may still be generated, reviewed, and submitted through a separate quality system or customer portal. Whether the traveler can serve as a source record depends on procedure, validation, and customer acceptance.

Material, process, tooling, and equipment traceability

The traveler should capture the traceability needed to show that the right inputs and controlled resources were used. Depending on the product and process, this may include:

• Material lot, heat, batch, certificate, and expiration data
• Purchased part and supplier certificate references
• Special process supplier, specification, approval, and certification references
• Tooling, fixture, NC program, software, or machine setup identifiers and revisions
• Calibration status and gage identifiers for inspection equipment
• Environmental or process parameters where required, such as temperature, humidity, cure cycle, pressure, or time

Some of this data may originate in ERP, PLM, calibration systems, maintenance systems, supplier portals, or QMS workflows. In brownfield environments, integrations are often incomplete. If data is manually transcribed or attached after the fact, the traveler should make that visible rather than implying automated traceability that does not exist.

Personnel, training, and approvals

The traveler should record who performed and accepted each operation, when the work occurred, and whether required certifications or training were current according to the site’s procedures. For regulated operations, this typically requires electronic signatures or controlled approvals with time stamps and audit trails.

This does not mean every operator action needs an excessive signature burden. The control level should match risk, customer requirements, and internal quality procedures. Over-signing creates noise; under-signing creates weak evidence.

Nonconformances, deviations, and changes

The traveler should record any nonconformance, deviation, rework, repair, concession, or engineering disposition that occurred during the FAI build. It should link to the controlling NCR, MRB, deviation, or change record in the QMS or engineering system.

Uncontrolled changes are one of the fastest ways to undermine an FAI. If a process, tool, material, program, supplier, or drawing changes during the build, the traveler should show whether the change was approved, when it became effective, and whether the FAI scope was affected.

Objective evidence and record retention

The traveler should retain or link to objective evidence such as inspection results, machine reports, process logs, photos, certificates of conformance, material certifications, special process certifications, calibration records, and approvals. The record should be retrievable for the required retention period and protected from uncontrolled alteration.

A practical digital traveler also needs audit trails, version history, access controls, and a clear record of attachments. Otherwise, the system may digitize the shop packet without improving evidence quality.

Common failure modes

• The traveler references the wrong drawing, model, or planning revision.
• FAI characteristics are measured but not tied back cleanly to ballooned requirements.
• Material or special process evidence is attached manually with weak traceability.
• Rework or deviations occur outside the controlled NCR or MRB process.
• ERP, MES, PLM, and QMS disagree on part revision, routing, or effectivity.
• Operators use printed instructions or local files that are not under document control.
• Electronic signatures exist, but the workflow has not been validated for the intended recordkeeping use.

In many aerospace and regulated manufacturing environments, the realistic goal is not to replace every legacy system at once. Full replacement is often impractical because of qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, and long equipment lifecycles. A better FAI traveler usually depends on controlled integration, clear ownership of source data, and disciplined change control across existing systems.