Wheel Hub First Article Inspection: Drawing-to-Report Review

Published: August 28, 2026  ·  Last updated: August 28, 2026  ·  Author: Dong, Andy

First article inspection is a product-and-process snapshot for a defined first article or lot. It is not automatically a PPAP, capability study, certificate or approval for every future production condition.

Lock the first article identity

Prove which physical samples, process and design record the report represents. The value of this control in wheel hub FAI report review is that a polished report can belong to another revision, cavity or development sample. A fast answer is useful only when another reviewer can see how it was reached and where its limits begin. Speed without an evidence trail simply moves the delay to receiving, returns or customer service.

Use part numbers, drawing, specifications, site, tool, cavity, process route, sample ID and date as the intake baseline. Next, build a sample genealogy from manufacture through measurement. Make each transformation visible: converted units, normalized numbers, translated wording and calculated totals belong in separate fields from source values. This design exposes errors early and prevents a spreadsheet formula from being mistaken for a supplier commitment.

Decision rule and evidence owner

The approved record should retain material lot, process date, inspector and report version. Link it to the exact SKU, RFQ line, purchase order or lot that it controls. If one attribute changes, reviewers can then locate the affected outputs without replacing unrelated descriptions or repeating the entire investigation.

For example, sample labels show one cavity while the report combines several. Stop release where sample-to-report identity cannot be reconstructed. Capture the reason, the evidence requested and the next review point. A clear hold code is operationally better than an informal warning that warehouse or sales staff may never see.

Reconcile every design requirement

Use a balloon map and characteristic register that includes notes and referenced requirements. The value of this control in wheel hub FAI report review is that dimensions may be complete while surface, material, marking or general-note requirements are omitted. A fast answer is useful only when another reviewer can see how it was reached and where its limits begin. Speed without an evidence trail simply moves the delay to receiving, returns or customer service.

Use drawing balloons, notes, specifications, key characteristics, material and appearance fields as the intake baseline. Next, assign one stable identifier to each requirement and reported result. Make each transformation visible: converted units, normalized numbers, translated wording and calculated totals belong in separate fields from source values. This design exposes errors early and prevents a spreadsheet formula from being mistaken for a supplier commitment.

A workable release condition

The approved record should record requirement source, revision, result field and status. Link it to the exact SKU, RFQ line, purchase order or lot that it controls. If one attribute changes, reviewers can then locate the affected outputs without replacing unrelated descriptions or repeating the entire investigation.

For example, a general tolerance note changes acceptance but is not shown in the report. Stop release where a design requirement has no reviewed status. Capture the reason, the evidence requested and the next review point. A clear hold code is operationally better than an informal warning that warehouse or sales staff may never see.

Check methods, units and equipment status

Ensure the measurement can support the reported characteristic. The value of this control in wheel hub FAI report review is that instrument resolution, fixture datum or unit errors can produce plausible but unusable numbers. A fast answer is useful only when another reviewer can see how it was reached and where its limits begin. Speed without an evidence trail simply moves the delay to receiving, returns or customer service.

Use method, fixture, datum setup, environmental condition where relevant, gauge ID, status and unit as the intake baseline. Next, review method suitability and link equipment to valid calibration evidence. Make each transformation visible: converted units, normalized numbers, translated wording and calculated totals belong in separate fields from source values. This design exposes errors early and prevents a spreadsheet formula from being mistaken for a supplier commitment.

How to document the exception

The approved record should retain procedure, equipment, operator and measurement uncertainty note when required. Link it to the exact SKU, RFQ line, purchase order or lot that it controls. If one attribute changes, reviewers can then locate the affected outputs without replacing unrelated descriptions or repeating the entire investigation.

For example, a bore result is reported without the defined datum or equipment ID. Stop release where the method or calibration status cannot be verified. Capture the reason, the evidence requested and the next review point. A clear hold code is operationally better than an informal warning that warehouse or sales staff may never see.

Preserve sample-level results and exceptions

Show actual values, limits and decisions without hiding variation. The value of this control in wheel hub FAI report review is that ranges or averages can conceal an individual nonconforming sample. A fast answer is useful only when another reviewer can see how it was reached and where its limits begin. Speed without an evidence trail simply moves the delay to receiving, returns or customer service.

Use nominal, upper and lower limit, actual value by sample, pass state and comment as the intake baseline. Next, validate formulas and flag missing, corrected or transcribed results. Make each transformation visible: converted units, normalized numbers, translated wording and calculated totals belong in separate fields from source values. This design exposes errors early and prevents a spreadsheet formula from being mistaken for a supplier commitment.

A case that exposes the hidden risk

The approved record should retain raw record, revision history and reviewer. Link it to the exact SKU, RFQ line, purchase order or lot that it controls. If one attribute changes, reviewers can then locate the affected outputs without replacing unrelated descriptions or repeating the entire investigation.

For example, three samples are summarized as pass although one exceeds the limit. Stop release where an exception lacks an authorized disposition. Capture the reason, the evidence requested and the next review point. A clear hold code is operationally better than an informal warning that warehouse or sales staff may never see.

Separate FAI review from production release

State what the first article supports and what additional approval remains. The value of this control in wheel hub FAI report review is that teams may treat one accepted report as evidence of stable volume production. A fast answer is useful only when another reviewer can see how it was reached and where its limits begin. Speed without an evidence trail simply moves the delay to receiving, returns or customer service.

Use buyer review, PPAP or change requirement, capability, production controls and open actions as the intake baseline. Next, issue a bounded acceptance, rejection or resubmission decision. Make each transformation visible: converted units, normalized numbers, translated wording and calculated totals belong in separate fields from source values. This design exposes errors early and prevents a spreadsheet formula from being mistaken for a supplier commitment.

What a second reviewer should see

The approved record should retain authority, conditions, effective scope and next trigger. Link it to the exact SKU, RFQ line, purchase order or lot that it controls. If one attribute changes, reviewers can then locate the affected outputs without replacing unrelated descriptions or repeating the entire investigation.

For example, purchasing releases repeat orders after engineering only acknowledged receipt. Stop release where the acceptance authority or scope is ambiguous. Capture the reason, the evidence requested and the next review point. A clear hold code is operationally better than an informal warning that warehouse or sales staff may never see.

First article report reconciliation

The reconciliation follows each requirement from drawing to sample-level result and decision.

Repeat first article evidence when its basis changes

Timken's public prototype procedure lists design records, inspection results, inspection devices, material certification and layouts as separate evidence objects in its own customer process.

The Timken supplier manual distinguishes change validation, FAI and PPAP decisions rather than treating them as interchangeable.

The requesting buyer defines whether a first article, PPAP, sample approval or another process applies and which characteristics must be reported.

Claim boundary: This guide does not define a universal sample count, claim JNHJDP FAI acceptance, replace PPAP or state any wheel hub dimension, tolerance or inspection result.

Additional review scenarios for wheel hub FAI report review

Review scenario 1 for wheel hub FAI report review: Start from part numbers, drawing, specifications, site, tool, cavity, process route, sample ID and date. The reviewer should build a sample genealogy from manufacture through measurement. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain material lot, process date, inspector and report version. If sample-to-report identity cannot be reconstructed, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.

Review scenario 2 for wheel hub FAI report review: Start from drawing balloons, notes, specifications, key characteristics, material and appearance fields. The reviewer should assign one stable identifier to each requirement and reported result. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will record requirement source, revision, result field and status. If a design requirement has no reviewed status, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.

Review scenario 3 for wheel hub FAI report review: Start from method, fixture, datum setup, environmental condition where relevant, gauge ID, status and unit. The reviewer should review method suitability and link equipment to valid calibration evidence. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain procedure, equipment, operator and measurement uncertainty note when required. If the method or calibration status cannot be verified, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.

Review scenario 4 for wheel hub FAI report review: Start from nominal, upper and lower limit, actual value by sample, pass state and comment. The reviewer should validate formulas and flag missing, corrected or transcribed results. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain raw record, revision history and reviewer. If an exception lacks an authorized disposition, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.

Review scenario 5 for wheel hub FAI report review: Start from buyer review, PPAP or change requirement, capability, production controls and open actions. The reviewer should issue a bounded acceptance, rejection or resubmission decision. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain authority, conditions, effective scope and next trigger. If the acceptance authority or scope is ambiguous, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.

Review scenario 6 for wheel hub FAI report review: Start from part numbers, drawing, specifications, site, tool, cavity, process route, sample ID and date. The reviewer should build a sample genealogy from manufacture through measurement. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain material lot, process date, inspector and report version. If sample-to-report identity cannot be reconstructed, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.

Related wheel hub buyer resources

• Wheel Hub Assembly catalog
• Wheel Hub Bearing catalog
• wheel bearing versus wheel hub assembly guide
• ABS encoder identification guide
• wheel hub OE number and RFQ guide
• fitment verification workflow
• sample approval workflow
• kit contents and BOM verification
• supplier evaluation evidence guide
• export packaging checklist
• MOQ and lead-time planning guide
• incoming inspection checklist
• About Jinan Huayuan Auto Bearing

Sources, dates and claim boundaries

• Timken Purchased Product for Prototype procedure — official example distinguishing prototype evidence and production PPAP; it applies to Timken transactions, not automatically to JNHJDP orders
• Timken Supplier Requirements Manual — public requirements covering revision control, identification, lot traceability, shipment records and supplier evidence boundaries
• AIAG Production Part Approval Process overview — official PPAP scope: demonstrating that design-record and specification requirements can be met during an actual production run; the customer defines the applicable submission
• NIST metrological traceability FAQ and policy — official boundary that traceability requires a documented measurement result and unbroken calibration chain, not merely an instrument carrying a NIST label