Industries

Carry the revision into your Partial FAI.

Connect affected characteristics, datum impact and balloons to AS9102 Forms 1–3 and QIF records.^¹

Start free trial ↗

Prepare the FAI record

Bring the change reason, both file hashes and affected characteristic numbers into Form 1.^¹

Carry requirements into Form 3

Review nominal values, limits, units, modifiers and datum references alongside the revision delta.^¹

Keep the handoff connected

Review re-measurement decisions, proposed balloons and baseline/delta QIF in the same workflow.^¹

Sources and further reading

IAQG · 9102 First Article Inspection ↗

Scope & limits

Prepare a Partial FAI record with the design-change reason, both source filenames and SHA-256 hashes, and the affected characteristic numbers. Part, drawing and revision fields remain available for completion.
Form 2 is a blank preparation template. Form 3 provides numeric Nominal, LSL and USL fields where readable source values exist, alongside Unit, modifiers such as Ⓜ MMC, Datum refs and Revision delta. Measurement results remain blank.
Characteristics linked to changed faces can be marked “Re-measure”. Datum changes and their effect on referenced characteristics remain part of the review. Missing nominal values or unresolved associations require an engineer decision; no requirement is invented.
Review model-linked balloons and a separate datum list. A new geometric feature can receive a suggested next balloon number. The suggestion remains unassigned until reviewed; it is not an approved characteristic.
Export a baseline and delta QIF 3.0 file with supported typed characteristics and geometry-change context. Typed output depends on the available nominal, tolerance-zone and datum semantics. Missing or unsupported semantics remain explicit; the export does not invent them.
AS9102 exports are preparation records. Measurement results, missing requirements and customer approvals remain the responsibility of the engineering and quality team. A model comparison or schema-valid QIF export does not approve an FAI.
Do not upload files subject to ITAR or EAR export controls to the browser service. Discuss restricted-data requirements with your organisation and the PartDatum team before using the service. No export-control compliance or defence accreditation is claimed.
No export-control or defence accreditation is claimed. Do not upload ITAR/EAR-controlled files to the browser service.
These exports are preparation records, not a completed or approved FAI.
PMI extraction and typed QIF coverage depend on the source export. Unsupported geometry or characteristic semantics may remain in explicit fallback records.
A schema-valid QIF file does not prove complete semantic transfer or inspection conformity.
The responsible engineer confirms the re-measurement scope, drawing requirements and customer acceptance.
AS9102 Forms 1–3 are preparation data sheets; not all Rev C form fields are included yet. Form 2 is a blank preparation template. Measurement results remain blank.
Nominal, LSL, USL, units, modifiers and datum references depend on readable source values. Missing nominal values and unresolved associations require an engineer decision.
New-feature balloon numbers are unassigned proposals until reviewed; they are not approved characteristics.
Typed QIF requires supported nominal, tolerance-zone and datum semantics. Missing or unsupported semantics remain explicit.
PPAP and ECN outputs are preparation data and review prompts, not resubmission decisions or customer approval.
Browser processing uploads data to the PartDatum server in Germany. Final inspection scope and acceptance remain with the responsible engineer and customer.