Gauge Found Out of Tolerance: How to Find Affected Product Using ERP and Calibration Data
gauge found out of tolerance which products were inspected ERP
Also searched as
- calibration out of tolerance impact assessment
- link calibration records to ERP inspection and lots
- AS9100 7.1.5 measuring equipment out of calibration product validity
- calibration management software ERP integration
Short answer
When a calibration finds a gauge out of tolerance, you must assess every product it measured since its last in-tolerance calibration. That is only possible if inspection records carry the gauge ID. Record the gauge on each inspection result, then query by gauge and date window to list lots, jobs and shipments, and raise NCRs for any that are doubtful.
Applies to: ISO/IEC 17025 and ISO 10012 style calibration programs, AS9100 and ISO 9001 clause 7.1.5, ANSI/NCSL Z540.3 where contractually required; any calibration tool (spreadsheet, CMMS, QMS module) with any ERP
Running an out-of-tolerance impact assessment
- 1Record the as-found data and the date of the last calibration where the gauge was in tolerance; the window runs from that date to the date it was removed from service.
- 2Query inspection results for the gauge ID inside that window, in the ERP, QMS or inspection software.
- 3Resolve each result to its job, lot or serial, part number and operation, then to downstream shipments.
- 4Decide for each affected characteristic whether the as-found error could have moved a part across its tolerance, using the size of the error against the tolerance.
- 5Quarantine on-site doubtful lots through the NCR process and re-inspect with a calibrated gauge where parts are still available.
- 6Assess shipped product and decide on customer notification where re-inspection is not possible or shows nonconformance.
- 7Record the assessment, decisions and approvals against the calibration record, and review whether the interval should shorten.
The requirement and why ERP data matters
AS9100 and ISO 9001 clause 7.1.5 require that when measuring equipment is found unfit for its purpose, the organization determine whether the validity of previous measurement results has been adversely affected and take appropriate action. In practice an auditor will pick a gauge that failed and ask you to show what you checked. The answer depends on being able to answer a plain question: which parts did this gauge measure?
Calibration systems know the gauge and its history. ERP and inspection systems know the parts. Unless inspection records store the gauge ID, nobody can connect the two except by asking inspectors to remember. Many shops discover this the first time a micrometer fails and they cannot say whether it was used on aerospace parts or on scrap.
Make the gauge ID a field, not a comment
Add the gauge or instrument ID as a structured field on every inspection result: in-process inspection, final inspection, receiving inspection and FAI Form 3. In an ERP with inspection plans, put it on the plan characteristic as the required instrument type and capture the actual ID at result entry. Where the ERP does not support it, capture it in the QMS or inspection software and carry the job and lot numbers there.
Validate at entry: the ERP or QMS should refuse a result if the gauge's calibration due date has passed or if its status is quarantined or out of service. That prevents the problem at source and is easy to demonstrate to an auditor.
-- Shape of the impact query (names vary by system) SELECT r.job_no, r.lot_no, r.part_no, r.characteristic, r.result_date FROM inspection_result r WHERE r.gauge_id = :gauge AND r.result_date BETWEEN :last_good_cal AND :removed_from_service ORDER BY r.result_date;
Judging whether the failure matters
An out-of-tolerance gauge does not automatically mean bad parts. Compare the as-found error with the tolerance of the characteristics it measured. A caliper reading 0.02 mm off on a feature with a plus or minus 0.5 mm tolerance has not changed any decision. The same error on a 0.05 mm tolerance feature probably has. Direction also matters: a gauge that read small might have passed oversize parts but not failed good ones.
Document the reasoning per characteristic and keep to your own written criteria. Where the error is significant and parts are available, re-inspect. Where parts have shipped, the decision on customer notification should be made by quality with the contract in view, and recorded.
Preventing repeats
Use the as-found history to adjust calibration intervals: instruments that repeatedly fail should be calibrated more often or replaced, and those that never drift can sometimes be extended with a documented rationale. Link gauges to the part numbers or processes that use them so a failure immediately shows the exposure.
For ERP and CMMS integration, a small interface is enough: the calibration system publishes gauge status and due date, and the inspection step reads it. Keep a single authoritative gauge master and avoid duplicating the list by hand in several places.
Common pitfalls
- !Recording the gauge as free text such as caliper 3, so queries by gauge ID miss records.
- !Starting the impact window at the failed calibration date instead of the last good one.
- !Treating every out-of-tolerance finding as a recall without comparing error to tolerance.
- !Ignoring in-process checks and looking only at final inspection records.
- !Keeping separate gauge lists in the CMMS, the QMS and the ERP that disagree.
- !Allowing results to be entered against a gauge whose due date has passed.
How an ERP-grounded AI assistant handles this
Given a failed gauge ID and an as-found value, an assistant grounded in the inspection and ERP data can list the lots, jobs and shipments measured in the window, show the query, and flag the characteristics whose tolerance is small relative to the error. It saves the hours of manual searching that usually delay the assessment. The accept or reject judgement and any customer notification stay with quality.
Frequently asked questions
Does every out-of-tolerance finding need a customer notification?
No. It depends on whether product could have been affected and on the contract. If the error is small relative to the tolerance, or re-inspection confirms conformance, notification may not be required. If nonconforming product has shipped, most aerospace and defense contracts expect notification. Follow your procedure and the purchase order terms.
Where should calibration data live, ERP or a dedicated tool?
Small shops do well with a spreadsheet or the QMS module. Larger shops use a calibration or CMMS tool with certificates, as-found data and scheduling. Few ERPs do this well natively. What matters is a single gauge master with a status the inspection step can read.
What is the difference between as-found and as-left?
As-found is the gauge's error when it arrives for calibration, before any adjustment. It tells you whether past measurements were reliable. As-left is the error after adjustment. The impact assessment uses as-found data, so a calibration certificate that reports only as-left values is not enough.
Related
How to Populate AS9102 First Article Inspection Forms From ERP Data
Roughly half of an AS9102 package is data your ERP already holds: part number, revision, drawing, serial or lot, PO, raw material and special process records on Forms 1 and 2. Form 3 characteristics come from the ballooned drawing and the inspection results, not the ERP. The ERP's best contribution is deciding when an FAI is required and keeping the evidence linked.
How-toHow to Sync an NCR From Your QMS to ERP Quarantine and MRB Disposition
The reliable pattern is two events: when the NCR opens, the ERP moves or flags the affected lot or serial into a non-nettable quarantine status; when the Material Review Board closes it, the disposition (use as is, rework, repair, scrap, return to vendor) triggers exactly one matching ERP transaction. The NCR number is the key that ties both sides together.
How-toHow to Link a CAPA to ERP Lots and Serial Numbers for Containment and Effectiveness
A CAPA is only as good as its containment scope, and the scope comes from ERP genealogy: forward trace from the suspect raw material lot or process to every job, serial and shipment that consumed it, and backward trace from the failed serial to its components. Store the CAPA number against those ERP records, then use ERP rejection and return data to verify effectiveness.
How-toHow to Send Production and Labor Reporting from MES to ERP
Treat the ERP work order as the system of record for cost and quantity, and the MES as the system of record for what physically happened. Send one confirmation message per operation (or per shift or lot) containing work order, operation sequence, good quantity, scrap quantity with reason, and labor start/stop per employee and work center, post it through the ERP's supported transaction API, and make the message idempotent so a retry never double-posts.
How-toHow to Calculate OEE from MES Data and ERP Standards
OEE equals Availability times Performance times Quality. Availability comes from MES run and stop events against planned production time, Performance compares actual output to the ideal cycle time (usually the routing standard from the ERP), and Quality is good units divided by total units. The numbers are only trustworthy if planned time, ideal cycle time and the good/scrap split are defined once and used consistently.
AdvancedISA-95 and B2MML: How to Integrate ERP with MES
ISA-95 defines the boundary between business systems (Level 4, the ERP) and manufacturing operations (Level 3, the MES) and the information that crosses it. B2MML is the XML implementation of those models. In practice you exchange a ProductionSchedule from ERP to MES, and ProductionPerformance, plus material and equipment information, back, mapping each element to your ERP's work order and confirmation APIs.
AI for ERPAI for NCR, CAPA, and 8D Drafting in AS9100 and ISO 9001 Quality Systems
AI drafts NCR, CAPA, and 8D reports from ERP quality data for engineer review, cutting drafting time under AS9100 and ISO 9001 without changing sign-off.
AI for ERPAI for AS9100 Quality Management on Your ERP
AI on top of your ERP quality module for AS9100D suppliers: NCR/CAPA drafting, FAI support, counterfeit parts screening, with a full audit trail.
Stuck on Calibration system (CMMS/QMS) to ERP integration?
Talk to engineers who work inside Calibration system (CMMS/QMS) to ERP integration every week, and who build private AI that answers these questions from your own ERP data.