How should teams decide between full FAI and partial FAI?

Teams should decide between full FAI and partial FAI based on whether the existing FAI still represents the current part configuration and production method. A full FAI is generally needed when there is no valid baseline for the part as it is now being built. A partial FAI is appropriate only when a prior FAI remains valid and the change impact can be bounded, documented, and reviewed against the affected characteristics and operations.

The wrong question is often, “Can we avoid a full FAI?” The better question is, “What evidence shows that the previous FAI still applies?” If that evidence is weak, incomplete, or spread across disconnected systems, a partial FAI becomes difficult to defend.

When full FAI is usually appropriate

A full FAI is commonly required when the part, configuration, source, or production method lacks a valid prior first article baseline. Typical triggers include:

• A new part number or product configuration entering production.
• A new or substantially revised design where prior characteristic verification no longer applies.
• A new manufacturing source, supplier, or facility when customer or internal rules treat the source change as invalidating the prior FAI.
• Major process, tooling, material, or equipment changes that affect many characteristics or cannot be cleanly isolated.
• A long production lapse where the governing standard, customer requirement, or internal procedure requires revalidation.
• Loss of confidence in the original FAI package because of missing records, unclear ballooning, obsolete revision references, or unresolved nonconformances.

Customer-specific requirements matter. Some customers or programs are stricter than the general standard, especially in aerospace and defense supply chains. Internal convenience does not override contract, drawing, purchase order, or quality clause requirements.

When partial FAI is usually appropriate

Partial FAI is usually appropriate when there is an accepted prior FAI and a specific change affects only part of the product or process. The partial FAI should cover the affected characteristics and any other characteristics that could reasonably be affected by the change.

Common examples include:

• A drawing revision changes a limited set of dimensions, notes, materials, or specifications.
• A manufacturing operation changes, but the impact can be traced to specific features or characteristics.
• A tool, fixture, machine, software program, or inspection method changes in a way that affects defined outputs.
• A corrective action requires re-verification of the affected characteristic and related controls.
• A supplier or sub-tier process change affects a known material, treatment, coating, or special process requirement.

A partial FAI is not simply a shorter full FAI. It needs a clear rationale explaining why the selected scope is sufficient. That rationale should be traceable to the design change, process change, routing change, nonconformance, or customer requirement that triggered the review.

How to make the decision

A practical decision process is to start with the existing FAI baseline and ask four questions:

• Configuration: Does the prior FAI match the current drawing, model, specification, bill of material, and revision level?
• Production method: Does it match the current routing, work instructions, tools, machines, programs, inspection methods, and special processes?
• Source: Does it match the current supplier, facility, sub-tier process, and approved source requirements?
• Evidence: Can the team show which characteristics are affected and why unaffected characteristics remain valid?

If the answer is no or unclear on any of these, the team should either expand the partial FAI scope or perform a full FAI. In regulated environments, uncertainty usually becomes a documentation and traceability problem later, even if the part itself is technically acceptable.

System and ownership issues

The decision should not sit with one function alone. Engineering usually owns design impact. Manufacturing engineering owns routing, tooling, and process impact. Quality owns FAI procedure conformance and record completeness. Supply chain must identify supplier, source, and sub-tier changes. Program or customer quality may impose additional requirements.

In brownfield environments, the relevant evidence may be split across PLM, ERP, MES, QMS, document control, inspection systems, and supplier portals. That is normal. Full replacement of these systems just to improve FAI governance is usually unrealistic because of validation cost, integration complexity, downtime risk, qualification burden, and long asset lifecycles. A more realistic control is to define authoritative sources, required cross-references, and change-control checkpoints between systems.

Common failure modes

• Treating a drawing revision as the only trigger and missing routing, tool, supplier, or inspection method changes.
• Assuming unchanged ERP part revision means the FAI baseline is still valid.
• Limiting a partial FAI to changed drawing balloons without considering dependent operations or special processes.
• Failing to link the FAI package to the exact drawing, model, specification, work instruction, and inspection revision used.
• Using partial FAI to recover schedule instead of because the technical impact is bounded.
• Not documenting why unaffected characteristics did not require re-verification.

The conservative rule is simple: use partial FAI when the prior baseline is valid and the impact is understood; use full FAI when the baseline is absent, invalid, or the impact cannot be bounded. The final decision still depends on customer requirements, internal procedures, configuration control, and the quality of the available records.