What information about gages and calibration must be stored with FAI measurement data?

FAI measurement data should store, or reliably link to, the gage or inspection equipment used for each measured characteristic and enough calibration evidence to show that the equipment was acceptable at the time of measurement. In an AS9102 context, the FAI record normally needs objective evidence for the result; the exact gage and calibration fields are often driven by customer flowdown, internal procedures, and the site’s calibration system.

Common information to capture

For each measured characteristic, the record should usually capture:

  • Gage or equipment identifier, such as asset number, serial number, tool number, CMM identifier, fixture identifier, or inspection software/device ID.
  • Gage type or method, such as micrometer, height gage, CMM, optical comparator, thread plug gage, torque tool, hardness tester, or qualified inspection fixture.
  • Calibration status at time of use, including whether the equipment was in calibration when the measurement was taken.
  • Calibration due date and, where required, the last calibration date.
  • Calibration certificate or record reference, preferably by controlled record number rather than an uncontrolled file attachment.
  • Measurement date and inspector or system identity, so the calibration status can be evaluated against the actual time of inspection.
  • Units, resolution, and actual measured value where variable data is required or expected.
  • Special tooling or qualified tooling identification if the characteristic was accepted using designed tooling, a fixture, or another qualified inspection aid.

Not every organization attaches a full calibration certificate to every FAI result. Many maintain the certificate in a calibration management system or QMS and store a controlled reference in the FAI package. That can be acceptable if the link is durable, access-controlled, and retained according to the applicable quality records requirements.

What is not always required

A full gage R&R or measurement system analysis record is not automatically required for every FAI measurement. It may be required by the customer, by the control plan, by the characteristic criticality, by internal procedure, or by a specific program requirement. The same is true for environmental conditions, uncertainty values, accredited calibration details, and raw machine output files. These are important where required, but they are not universal fields for every FAI record.

Common failure modes

The most common problem is not missing measurement data; it is weak linkage between the measurement and the equipment status at the time of inspection. A gage listed as calibrated today does not prove it was in calibration when the FAI measurement was taken unless the dates and records support that conclusion.

Other common issues include using expired gages, recording a gage type without a unique asset ID, relying on uncontrolled certificate PDFs, failing to identify CMM programs or qualified fixtures, and losing the connection between ballooned characteristics, Form 3 results, and calibration evidence.

System implications

In brownfield environments, this data may live across an FAI tool, MES, QMS, calibration system, CMM software, ERP work order, and PLM drawing record. Full replacement of those systems is usually unrealistic because of validation cost, qualification burden, downtime risk, integration complexity, and long equipment lifecycles. A more practical approach is often to define the minimum controlled data set, establish system-of-record ownership, and validate the integrations that populate or reference gage and calibration information.

The key control is traceability: the FAI package should allow a reviewer to determine what was measured, what equipment was used, whether that equipment was acceptable at the time, and where the controlled calibration evidence resides. It should not depend on tribal knowledge or a file name on a shared drive.

Content classification

Visible verification fields for authorship, dates, taxonomy, and ST assignments.

Author:

Published:

Updated:

Tags:

Glossary category:

Glossary tag:

Colour:

Content type:

Location:

Audience:

Intent:

Dev-only relationship debug

Content relationships

Rendered from saved content and bridge metadata. Nothing in this panel writes back to WordPress.

Inline glossary links

No inline glossary links found in saved content.

Attached glossary terms

No glossary bridge terms attached.

Attached FAQs

No FAQ bridge items attached.

Diagnostics

Inline glossary links
0
Attached glossary terms
0
Attached FAQs
0
  • No glossary or FAQ relationships found for this item.