Partial vs Delta FAI in AS9102 Software: Practical Digital Strategies

Under AS9102 Rev C, you no longer have to choose between re-doing an entire first article inspection or risking gaps in coverage when designs or processes change. Partial and delta FAI give aerospace manufacturers a structured way to verify only what has actually changed—provided you can manage the details correctly.

This article explains how full, partial, and delta FAI relate to each other, where organizations struggle when managing them manually, and how modern AS9102 software can automate reuse, lineage, and impact analysis. The perspective here reflects common industry practice, not a legal interpretation of the standard, and final scope decisions must always follow customer and regulatory requirements.

For teams putting this topic into daily operation, digital AS9102 FAI help connect the concept to traceability, work-order reality, and audit-ready evidence.

For teams putting this topic into daily operation, digital AS9102 FAI, a connected execution platform, Connect 981’s aerospace execution solutions help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on real aerospace execution examples, Connect 981’s aerospace operations guidance, practical aerospace operations FAQs, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

If you need a broader overview of digital AS9102 and FAIR workflows before diving into change scenarios, see our guide on AS9102 and digital FAI fundamentals.

Definitions: Full, Partial, and Delta FAI Under AS9102 Rev C

AS9102 Rev C clarifies terminology so suppliers and customers can distinguish between a brand-new verification and targeted re-verification when things change.

When a full FAI is mandatory

In practice, organizations treat a full FAI as the baseline reference FAIR for a given part configuration. Typical triggers include:

• New part introduction – First production run of a new part number for a site or supplier.
• Major design changes impacting form, fit, or function – For example, a new rib structure on a wing component or a significant geometry change on a turbine blade.
• New manufacturing source – Moving production to a different supplier or facility when the customer requires full re-validation.
• Extended production lapse – When no parts have been produced for an extended period (often around two years, but this can be customer-specific).

Under a full FAI, every characteristic on the drawing and applicable specifications must be ballooned and accounted for on Form 3, with supporting material and process evidence on Forms 1 and 2.

Typical triggers for partial FAI

Partial FAI is used when only selected characteristics require re-verification, usually because the manufacturing process has changed while the design itself has not. Common triggers include:

• Process or operation changes – A drilling or milling operation is moved to a different machine, cell, or facility.
• Tooling or fixture changes – New cutting tools, workholding, or gaging that could affect particular dimensions.
• Supplier or sub-tier changes for specific operations – For example, moving a plating step to a new special process supplier while the base part remains unchanged.
• Documented process issues – A corrective action drives re-validation of a specific subset of characteristics.

The scope of a partial FAI is defined by which characteristics are affected by the process change. You still rely on the existing baseline FAIR for unchanged items.

Typical triggers for delta FAI

Delta FAI applies when there is a design or specification change, and you must verify only the impacted characteristics against the new configuration while referencing the prior full FAI.

• Drawing revision changes – A revision adds, removes, or modifies dimensions, tolerances, GD&T callouts, or notes.
• Specification updates – A new material spec is called out, a test requirement changes, or a surface treatment is updated.
• Additional features – New holes, cutouts, stiffeners, or bosses are added to an existing part.
• Tolerance changes – A previously generous tolerance is tightened on high-risk features.

The delta FAIR documents only changed and newly added characteristics, but it must clearly reference the baseline FAIR for everything else. This is where digital lineage and linking are especially valuable.

Common Challenges with Manual Partial and Delta FAI

On paper and spreadsheets, partial and delta FAI often create more confusion than efficiency. The standard allows targeted verification, but without structured tools, teams struggle to manage scope correctly.

Over-documentation and unnecessary re-inspection

To be “safe,” some organizations treat every change as a reason to redo a near-full FAI:

• Re-ballooning entire drawings instead of only the affected areas.
• Copy-pasting a prior Form 3 and re-entering measurements for most characteristics.
• Running duplicate inspections on features that are demonstrably unaffected by the change.

This wastes engineering capacity, clogs CMM queues, and delays deliveries. It also undermines the original purpose of partial and delta FAI: focusing effort where risk actually changed.

Under-documentation and missed linked features

The opposite problem is just as common: teams underestimate scope.

• A tooling change that affects multiple related features is treated as affecting only one dimension.
• A GD&T callout is revised, but only one characteristic is updated instead of the entire feature pattern.
• Downstream processes or mating parts impacted by a tolerance change are not considered.

Without structured impact analysis, it is easy to miss derived or associated characteristics, exposing you to customer rejections or findings during AS9102 or AS9100 audits.

Traceability gaps between baseline and follow-on FAIRs

Manual systems often handle follow-on FAIRs as isolated files:

• Baseline and delta FAIRs live in different network folders with inconsistent naming.
• Form 1 status (full, partial, delta) is not used consistently, so reviewers cannot tell what they are looking at.
• There is no simple way to see how many FAIRs exist for a part and what changed each time.

These gaps make it hard to prove configuration history and FAIR lineage when customers or auditors ask for evidence.

Designing Software Workflows for Partial FAI

Modern AS9102 software can codify partial FAI logic so engineers execute consistent, risk-based scopes instead of reinventing the process each time.

Tagging FAIRs with status (full, partial, delta)

Start with explicit status tagging:

• Every FAIR record uses the Form 1 field to mark full, partial, or delta.
• Workflows and dashboards filter and report based on that status.
• Search tools allow users to quickly find the most recent full FAI for a part and all associated partial or delta FAIRs.

In a software system, status tagging can also drive automated routing and required approvals—for example, forcing quality or customer approval when a partial FAI is used to qualify a new facility.

Reusing baseline characteristic data safely

The biggest efficiency gain from digital FAI comes from treating the baseline FAIR as a structured data set rather than a static PDF.

• Characteristics extracted and ballooned once are stored as reusable digital objects.
• When a partial FAI is created, the software clones the baseline FAIR metadata, but flags only selected characteristics as “in scope” for re-verification.
• Unchanged characteristics remain present for context but carry a clear indication that they are not being re-inspected as part of this partial FAI.

This approach preserves one source of truth for the part while avoiding duplicated Form 3 lines and repeated manual entry.

Controlling scope when process changes occur

Well-designed workflows guide engineers through scope decisions instead of leaving everything to memory:

• Partial FAI templates prompt users to identify the operation, machine, or facility that changed.
• Characteristics in the baseline FAIR are linked to process steps and work centers.
• The system proposes a list of characteristics likely affected by the changed operation.

Engineers can then review, expand, or narrow that list, but they are no longer starting from a blank spreadsheet. This reduces the chance of missing characteristics that should logically be within partial FAI scope.

Managing Delta FAI for Engineering Changes

Delta FAI sits at the intersection of engineering change control and production verification. Software can bridge PLM, drawings, and FAIRs so the right characteristics are re-verified every time a revision is released.

Linking ECNs and drawing revisions to affected balloons

An effective digital workflow starts with change artifacts—Engineering Change Notices (ECNs), Engineering Change Orders (ECOs), or PLM change objects.

• Each ECN or drawing revision is associated with the relevant part numbers in the FAI system.
• The system compares old and new drawings, highlighting changed callouts, dimensions, notes, or specifications.
• These differences are mapped directly to balloon numbers on the digital drawing and their corresponding Form 3 rows.

With this linkage in place, the delta FAIR can be generated from a concrete list of changed characteristics instead of relying on manual visual comparison.

Impact analysis to identify which characteristics must be re-verified

The next layer of capability is impact analysis—looking beyond the explicitly edited dimension to understand what else should be considered in scope.

• A tighter positional tolerance on a hole pattern may also bring associated datum features, countersinks, or threads into scope.
• A surface finish requirement might impact both the machining operation and subsequent coating steps.
• Changes to a material specification could trigger new or repeated material tests and special process verifications.

Software can use rules and relationships embedded in the data model to suggest affected characteristic groups. Engineers then review and finalize the scope rather than building it from scratch.

Building FAIR family trees and lineage views

Over the life of a part, you may have one full FAI plus multiple partial and delta FAIRs. Without tools, keeping track of this family is difficult.

• Digital systems construct a FAIR family tree that shows the baseline full FAI and every associated partial or delta FAIR, in chronological order.
• Each child FAIR contains explicit links back to its parent FAIR and drawing revision.
• Users can click into a characteristic and see a history of all times it was re-verified and why.

This lineage not only supports audits; it also helps engineers quickly understand what has already been proven when planning further changes.

Examples: Partial and Delta FAI Scenarios in Aerospace

Concrete scenarios help clarify when to consider partial versus delta FAI and how software can handle each case. The exact decision in your organization should always follow customer and internal requirements, but these patterns are common.

Machine or facility relocation of a machining operation

Scenario: A supplier moves a 5-axis machining operation for a structural bracket from Plant A to Plant B. The drawing and spec do not change.

• FAI type: Typically a partial FAI focused on characteristics produced by the relocated operation.
• Manual challenge: Determining which dimensions are affected by the moved operation and which remain untouched.
• Software approach: Link each characteristic in the baseline FAIR to its operation routing. When the routing changes, the system suggests the affected characteristics and generates a partial FAIR pre-populated with those characteristics only.

Tolerance changes on critical hole patterns

Scenario: Engineering tightens the positional tolerance and surface finish requirement on a critical hole pattern in a landing gear component.

• FAI type: A delta FAI covering the modified pattern and any associated datums or related features deemed impacted.
• Manual challenge: Ensuring all holes in the pattern, and not just one edited dimension, are included in the delta scope.
• Software approach: The system compares drawing revisions, identifies the updated tolerance and finish, and maps those edits to all ballooned features in the pattern. Engineers validate the automatically generated list for the delta FAIR.

Material substitution for specific callouts

Scenario: A casting alloy spec is updated, or a substitute material is permitted for specific callouts on a structural part.

• FAI type: Often a delta FAI covering characteristics and tests influenced by the new material, plus a new record of material certifications on Form 2.
• Manual challenge: Understanding which tests or special processes need to be repeated and which geometric characteristics need closer scrutiny.
• Software approach: Characteristics and Form 2 entries linked to the original material spec are flagged; the system prompts for updated certs, test results, and any newly required verifications.

Measuring the Impact of Digital Partial and Delta FAI

Organizations often adopt digital FAI tools to solve immediate pain, but you should also measure the impact of better handling of partial and delta FAI over time.

Cycle time reductions and engineering capacity gains

Key metrics for partial and delta FAI include:

• Average time to complete a full FAI vs. partial/delta – With robust reuse and impact analysis, delta FAIRs should routinely take 50–80% less time than a full FAI.
• Number of FAIRs completed per quality engineer – Automation should increase throughput without extending work hours.
• Queue time at CMM and inspection resources – Reduced scope directly shortens queues when only affected characteristics are re-measured.

Effect on audit findings and customer rejections

Digitizing partial and delta FAI should also improve compliance outcomes:

• Fewer documentation-related FAIR rejections – Clear status tagging and lineage reduce confusion about what has been verified when.
• Reduced AS9100/AS9102 audit findings related to configuration control and traceability.
• Better responsiveness in customer reviews – FAIR family trees and instant retrieval of supporting evidence shorten review cycles.

Best practices for standardizing partial/delta policies

To get consistent value from your software, codify your decision logic:

• Create a partial vs. delta decision matrix aligned with the AS9102 standard and major customer requirements.
• Embed that matrix into workflow rules and templates so engineers see guidance in context.
• Review edge cases regularly and adjust rules to reflect lessons learned from audits and customer feedback.

Over time, your partial and delta FAI process becomes repeatable, auditable, and scalable across sites and suppliers rather than dependent on a few experts.

Using Partial and Delta FAI as a Strategic Lever

Done well, partial and delta FAI strategies turn engineering change from a recurring scramble into a controlled, data-driven process. Modern AS9102 software helps you:

• Reuse baseline FAIR data with confidence instead of rebuilding every time.
• Focus verification on clearly defined, risk-based scopes.
• Maintain transparent lineage across full, partial, and delta FAIRs for each part number.
• Demonstrate robust configuration control during customer and certification audits.

As your organization advances its digital FAI capabilities, consider how partial and delta FAI workflows align with broader goals like standardizing processes across plants, integrating with PLM and MES, and supporting a connected aerospace operations platform.

For a deeper foundation on digital FAI tools, templates, and integrations, review the cluster hub on AS9102 and digital FAI fundamentals and then map your current partial and delta FAI workflows against the capabilities described there.