At minimum, an AS9102 FAIR package should include the completed AS9102 forms and the objective evidence needed to support what those forms claim. The exact attachment set varies by customer flowdown, part criticality, manufacturing route, outsourced processing, and how your organization maintains traceability.
In practice, the supporting documents commonly attached or referenced include:
-
the ballooned drawing or annotated design record used to map characteristics to Form 3
-
the revision-controlled drawing, model, or specification set that defines the part at the time of the FAI
-
inspection and measurement results for each required characteristic, including CMM reports, manual inspection records, or other metrology outputs where applicable
-
material certifications or mill test reports tied to the specific lot or heat used
-
special process certifications from approved sources, such as plating, heat treat, NDT, welding, or coating, if those processes apply
-
functional test results, acceptance test records, or inspection reports required by drawing or specification
-
raw material, component, and subcomponent traceability records where required for the assembly or detail part
-
certificates of conformity from suppliers or outside processors, when those are part of the evidence chain
-
approved nonconformance, deviation, waiver, or concession documentation, if any characteristic or configuration depended on formal disposition
-
process verification records when the FAI scope includes processes that must be demonstrated as part of first article evidence
-
part marking or serialization evidence if marking is a design requirement
-
purchase order, traveler, router, or work order references that connect the FAIR to the actual build history
What should not be assumed is that every site should attach every possible record as a single static packet. Some organizations attach full copies. Others attach only the required forms plus an indexed evidence list with controlled references into MES, QMS, PLM, ERP, or a document management system. Either approach can work if retrieval is reliable, revisions are controlled, and the evidence trail is complete during review.
What matters most
The key requirement is not paperwork volume. It is whether the FAIR package provides a clear, auditable link between design requirements, the actual manufactured configuration, measurement results, material and process evidence, and any approved exceptions. If that chain is broken, the package may be challenged even if it looks complete on the surface.
Common failure modes include:
-
certifications that cannot be tied to the exact lot, serial, or work order
-
CMM outputs that do not clearly map to ballooned characteristics
-
special process records from the wrong revision or wrong supplier approval status
-
missing evidence for characteristics derived from notes, flag notes, or model-based definition
-
attachments stored in disconnected systems with inconsistent part numbers, revisions, or naming conventions
-
use of superseded drawings or forms after engineering change
Brownfield system reality
In many plants, the FAIR package is assembled from multiple systems rather than produced end to end in one application. That is normal. The challenge is maintaining controlled linkage across ERP, MES, PLM, QMS, metrology software, supplier portals, and shared document repositories.
If your environment is brownfield, focus on:
-
consistent part, revision, lot, and work order identifiers across systems
-
clear ownership for which system is the source of record for each attachment type
-
change control over templates, mappings, and attachment rules
-
validation of any automated population or document pull-through
-
fallback procedures when integrations fail or evidence is incomplete
Full replacement of legacy quality and manufacturing systems is often not the practical answer. In regulated, long-lifecycle environments, replacement efforts commonly stall because of qualification burden, validation cost, downtime risk, integration complexity, and the need to preserve traceability across existing records.
So the short answer is yes: attach the supporting evidence needed to substantiate the FAIR. But no, there is not one universal attachment list that fits every AS9102 package without reference to customer requirements, process scope, and your actual evidence architecture.