REFERENCE NOTE / MACHINED PARTS
What a First-Article Inspection Package Should Contain for Machined Parts
A first article is useful only when the inspected part, the controlled requirement, the manufacturing state, the measurement result, and the approval decision can be traced to one another.
00 / SHORT ANSWER
The package is a traceable decision record, not a stack of screenshots
A useful first-article inspection package identifies the exact part and revision, states why the first article was triggered, maps the customer-controlled characteristics to inspection records, records actual results and exceptions, identifies the manufacturing and measurement state, and shows who was authorized to accept or reject the result. It should also index any material, special-process, or external records that the purchase order actually requires.
Three responsibilities must remain separate. The customer or design authority controls the drawing, specifications, characteristic scope, acceptance criteria, governing contractual system, and approval authority. The supplier creates the agreed first-article evidence for the part it made. Statistical monitoring, sampling, in-process checks, capability work, and other controls used after release belong to the production-control plan. A complete first-article record does not, by itself, prove that later output will remain conforming.
RESPONSIBILITY INDEX
Keep three evidence layers distinct
Customer-controlled basis
Drawing revision, specifications, characteristic designations, acceptance rules, required forms, approval authority, and any named industry or customer scheme.
Supplier first-article record
Part identity, manufacturing state, characteristic mapping, methods, actual results, linked evidence, exceptions, review, and disposition for the inspected article.
Ongoing production control
Sampling, process monitoring, tool and offset management, in-process inspection, capability evaluation, reaction plans, and later-lot release controls.
01 / REQUIREMENT BASELINE
Start with the controlled requirements that govern the inspection
List every controlled document used for inspection with its revision or effective identifier. That list can include the drawing, model, specification, customer quality clause, approved deviation, inspection instruction, and any form explicitly required by contract. Do not silently treat the supplier's downloaded copy as current. Record how the revision was checked and identify conflicts before measurement. If the model and drawing carry different authority, the customer-controlled hierarchy must settle the conflict; the supplier should not infer which requirement wins.
Define the scope in the package itself. State whether the record covers a complete part, selected characteristics, a delta review after change, one cavity or tool position, one operation state, or an assembly. If a customer-designated key characteristic receives additional treatment, preserve the designation without inventing a new one. If a characteristic is excluded, identify the exclusion and its authority. Blank space, an unmarked balloon, or a missing spreadsheet row is not a controlled exclusion.
02 / ARTICLE IDENTITY
Identify the part and the manufacturing state that produced it
A first-article result without a physical identity is difficult to audit. Record a serial, batch, traveler, temporary tag, or other agreed identifier that connects the inspected piece to the job. For multi-piece submissions, say which piece produced each result. If a destructive test uses a coupon or sacrificial sample, link that sample to the represented material and process state; do not let its result appear to have come from the finished part.
Describe the manufacturing route at a level that explains the evidence without disclosing unnecessary proprietary detail. The record may need to identify the relevant raw-material lot, operation sequence or traveler revision, program revision, fixture or setup identity, tool or cavity position, heat-treatment or finishing route, and outsourced operation reference. Which fields are required depends on the drawing, purchase order, risk, and customer system. Their purpose is change traceability, not the creation of a universal form.
State the inspection state. A dimension measured before coating, heat treatment, stress relief, final deburring, or assembly may not represent the delivered state. Conversely, a feature intentionally verified at an intermediate operation may become inaccessible later. Name the state and explain how the result relates to final acceptance. When temperature, support, restraint, orientation, cleaning, or stabilization materially affects measurement, record the agreed condition rather than leaving the reader to reconstruct it.
03 / CHARACTERISTIC MAP
Map each controlled characteristic to one unambiguous record
Ballooning or otherwise indexing the product definition creates the bridge between the customer's requirement and the supplier's result. Give every reportable dimension, geometric control, drawing note, specification callout, material requirement, finish requirement, marking requirement, and documented visual criterion a stable identifier. Then use the same identifier in the result sheet. The reader should be able to move from drawing to record and back without guessing which row belongs to which feature.
Do not reduce a compound requirement to a single unexplained check mark. A hole callout can combine size, depth, thread, position, quantity, edge condition, and relationship to a datum system. A surface note may combine process, texture, direction, protected area, and cosmetic acceptance. Split the record enough to make each acceptance decision visible, while retaining the parent callout so the relationship is not lost.
Use explicit states for characteristics that do not produce a scalar number: observed result, document reference, method, acceptance basis, and authorized disposition. Avoid ambiguous entries such as "OK," "see cert," or "typical" when the package does not say what was reviewed. If one certificate supports several rows, repeat its controlled reference or provide a clear cross-index. If a result is not applicable, record why and who accepted that status.
CHARACTERISTIC REGISTER
A result needs more than a pass mark
Illustrative taxonomy only. The identifiers and states do not describe a real part or a completed inspection.
04 / MEASUREMENT EVIDENCE
Record method, datum realization, equipment identity, and decision basis
The result row should say enough about the method to make the result interpretable. Depending on the characteristic and agreed plan, that may include the instrument or system category, equipment identifier, calibration status or record reference, resolution, program or routine revision, probe or fixture identity, sampling strategy, and environmental or support condition. More fields do not automatically create better evidence. The goal is to preserve the factors that could change the result or its interpretation.
Geometric results require particular care with datums. ISO 5459:2024 addresses datums and datum systems, while ISO 1101:2017 addresses geometrical tolerancing for form, orientation, location, and run-out [5] [6]. These citations identify the standards' public subjects only. The customer's controlled product definition must establish the applicable edition, symbols, datum scheme, and acceptance requirements. This article neither reproduces those requirements nor claims conformity to them.
Measurement uncertainty and task suitability should be considered where they can affect a conformity decision. Haitjema discusses task-specific uncertainty estimation in dimensional metrology [3]. That principle argues against naming an instrument category as if it were automatically suitable for every tolerance and feature. The package should preserve the agreed decision rule, any required guard band or uncertainty treatment, and the authority that selected it. It should not invent a default ratio or acceptance margin.
ISO 10012:2003 addresses requirements for measurement processes and measuring equipment when that standard is invoked [7]. A calibration label alone does not establish that a method is appropriate for the task, just as a sophisticated machine does not repair an incorrect datum setup. Record enough method evidence to support the actual decision, while keeping calibration systems, laboratory competence, and contractual certification claims separate.
05 / RESULTS & EXCEPTIONS
Record actual results, then keep exceptions visible through disposition
For variable data, record the actual observed value in the agreed units and precision rather than only a pass/fail word. For attribute evidence, state what was observed, which requirement controlled, and how acceptance was determined. Preserve original electronic outputs when the contract or risk calls for them, but do not make a proprietary data file the only readable result. The package should contain or index a human-reviewable record that remains intelligible outside the inspection software.
Never overwrite a failed result with a later passing value. Keep the initial result, identify the affected characteristic and article, open the applicable nonconformance or deviation record, record the authorized disposition, and link any rework and reinspection. The final package should show the sequence. Otherwise a buyer cannot distinguish a clean first pass from a corrected article, and the organization loses information that may matter to production planning.
A supplier cannot approve a departure from a customer-controlled requirement unless that authority has been explicitly delegated. "Use as is," drawing-note interpretation, tolerance change, and acceptance of an alternative process require the designated authority and a controlled reference. Verbal agreement should be captured through the approved project channel before the package is closed. The record should state which article and which future production, if any, the authorization covers.
06 / LINKED EVIDENCE
Include material and process records only against a defined requirement
If the drawing or purchase order requires material or process evidence, index each record to the represented lot, operation, and part identity. Capture the controlled specification, processor record, requested traceability fields, and acceptance status without implying that one document proves dimensions or final-part conformity beyond its scope. Approved-source, qualification, accreditation, packaging, marking, cleanliness, and preservation checks belong only where the project requires them. This article does not claim that StelParts or any unnamed provider holds a specific approval, certification, or process capability.
07 / PRODUCTION BOUNDARY
Do not use first-article approval as a substitute for production control
A first article answers a bounded question: did the identified article, made in the recorded state, produce acceptable evidence against the controlled scope? It does not establish that the process distribution is centered, stable, or capable over time. It does not select the sampling frequency for later pieces, predict tool wear, control operator changes, or prove that every subsequent part matches the first.
Research on first-off inspection of capable manufacturing processes treats the initial inspection decision in relation to broader process behavior rather than as a universal release guarantee [2]. Published work specifically describing first-article inspection likewise frames it as a production activity involving planning and records [1]. Neither paper supplies a customer-specific control plan for a machined part. The drawing, contract, process risk, and approved quality system must determine what follows.
Keep the ongoing control plan in a linked but distinct record. It may address setup verification, in-process checks, sampling, tool-life or offset controls, measurement-system monitoring, process capability evaluation, reaction to trends, lot release, and reinspection after interruption. A capability statistic, when required, needs a defined characteristic, data set, distribution assumption or method, measurement basis, and acceptance rule. It should not be copied into an FAI form merely because a template has a blank field.
Three records, three questions
| Record layer | Question it answers | What it must not imply |
|---|---|---|
| Customer requirement set | What definition and acceptance authority control this job? | That the supplier may change or interpret requirements without authorization |
| First-article package | What evidence supports disposition of the identified first article? | That every later part is automatically acceptable |
| Production-control record | How is the running process monitored and reacted to after release? | That one control method is suitable for every feature or lot |
08 / FILE PACKAGE
Build a searchable package that survives handoff and revision
Give the package a cover index, stable filenames, and a clear revision. A practical structure separates the requirement baseline, ballooned or indexed definition, characteristic results, original measurement outputs, material and process evidence, exception records, approvals, and the production-control reference. Each file should carry enough identity to remain meaningful after download. Avoid names such as "report-final-new" or links that depend on one employee's desktop folder.
Use one source of truth for identifiers across the package. Part number, revision, job, lot, characteristic ID, equipment ID, nonconformance reference, and approval reference should not change format between PDF, spreadsheet, inspection export, and traveler. Zhao and colleagues discuss dimensional-metrology interoperability and standardization in manufacturing systems [4]. The practical lesson here is modest: structured, consistent identifiers reduce translation loss. The paper does not require a particular customer file format.
FAI package index
- 01Cover and submission scope
part / revision / trigger / represented quantity - 02Controlled requirement index
drawing / model / specifications / approved changes - 03Characteristic map
stable IDs linked to every reportable requirement - 04Inspection result register
method / state / actual result / disposition - 05Linked material and process evidence
only when required and tied to represented parts - 06Exceptions and authorization
original result / disposition / rework / reinspection - 07Review, approval, and transmittal
roles / dates / controlled delivery reference - 08Production-control cross-reference
separate plan / change triggers / later-lot controls
Example filing architecture, not a mandatory form or evidence that a specific industry scheme has been satisfied.
09 / RELEASE CHECK
Ask these questions before the package leaves the supplier
Does the cover identify the exact part, revision, job, represented article, submission scope, and trigger?
Was the document hierarchy confirmed, and are all requirement revisions listed?
Can every reportable characteristic be traced from the controlled definition to one result or authorized exclusion?
Do compound callouts retain their separate acceptance elements and their parent relationship?
Are manufacturing state, measurement state, datum realization, units, and relevant method details clear?
Are actual results preserved, with readable source outputs where required?
Are initial failures, deviations, rework, and reinspection visible rather than overwritten?
Does every approval or exclusion point to the person or authority entitled to make that decision?
Are material and process records linked to the represented parts and limited to the required scope?
Is the production-control plan referenced separately, without treating the first article as proof of future stability?
Do filenames, identifiers, links, units, symbols, and protected files survive transfer to the recipient?
Does the package state what remains open, what would trigger revalidation, and who controls that decision?
A package is ready when an authorized reviewer can reconstruct the requirement, represented part, inspection state, evidence, exceptions, and release decision without oral history. For quotation, the buyer should provide the controlled definition, revision, quantity, material and process requirements, designated characteristics, required form or scheme, approval path, submission format, and production-control expectations. The supplier can then define what it will record and return rather than assuming every customer means the same thing by "FAI package."
10 / SCOPE LIMIT
What this reference note does not establish
This page is general manufacturing documentation guidance. It does not reproduce a complete standard, select a tolerance, approve a drawing, define a sampling plan, prescribe a measurement method, grant deviation authority, or certify a supplier. Contract documents and controlled customer requirements govern the real package. The cited ISO records identify normative subjects; they do not make an unnamed project compliant.
No production photograph, inspection result, tolerance achievement, instrument inventory, process capability, certification, customer approval, or industry-scheme compliance is claimed here for StelParts. Those facts require current, reviewable evidence and an agreed scope. The visual records on this page are native HTML and CSS examples created to explain information structure only.
FILE / SOURCES
References
- M. Rusu, I. Soare, M. Botan, A. Dragomirescu and C. Militaru, "FAI First Article Inspection in production activity," INCAS Bulletin, 2019. https://doi.org/10.13111/2066-8201.2019.11.3.18
- J. Sheil, "First-off inspection of capable manufacturing processes," Journal of the Operational Research Society, 2001. https://doi.org/10.1057/palgrave.jors.2601122
- H. Haitjema, "Task specific uncertainty estimation in dimensional metrology," International Journal of Precision Technology, 2011. https://doi.org/10.1504/IJPTECH.2011.039461
- Y. Zhao, X. Xu, T. Kramer, F. Proctor and J. Horst, "Dimensional metrology interoperability and standardization in manufacturing systems," Computer Standards & Interfaces, 2011. https://doi.org/10.1016/j.csi.2011.02.009
- ISO, "ISO 5459:2024 - Geometrical product specifications (GPS) - Geometrical tolerancing - Datums and datum systems." Official ISO record.
- ISO, "ISO 1101:2017 - Geometrical product specifications (GPS) - Geometrical tolerancing - Tolerances of form, orientation, location and run-out." Official ISO record.
- ISO, "ISO 10012:2003 - Measurement management systems - Requirements for measurement processes and measuring equipment." Official ISO record.