ISO 9001 Asset Traceability: Adding Location Evidence to Your Calibration Program

What ISO 9001:2015 clause 7.1.5 actually requires

Clause 7.1.5 of ISO 9001:2015 is titled "Monitoring and measuring resources" and is split into two sub-clauses. Clause 7.1.5.1 requires the organization to determine and provide the resources needed to ensure valid and reliable monitoring and measuring results. Clause 7.1.5.2 requires that when measurement traceability is a requirement, measuring equipment shall be calibrated or verified at specified intervals against measurement standards traceable to international or national standards, identified to determine its status, and safeguarded from adjustments, damage, or deterioration that would invalidate the calibration status.

Read literally, the clause focuses on metrology — calibration intervals, measurement uncertainty, and traceability of standards. That work belongs to a calibration management system (CMS). But the second half of 7.1.5.2 — "safeguarded from adjustments, damage, or deterioration" — opens a door auditors increasingly walk through. If a torque wrench was calibrated in March and a non-conformance turns up in May, an auditor may ask where that wrench has been in the intervening weeks. Was it on the production line where the suspect parts were built? Was it in the calibration lab? Was it loaned to a sister plant?

Most quality systems cannot answer this with evidence. They can answer it with a sign-out sheet and a story. This is the gap TagLogger fills. It is not a calibration management system. It does not replace GageList, Beamex CMX, or Indysoft. It adds a location evidence layer that sits underneath whichever CMS you already run.

IATF 16949:2016 clause 7.1.5.2.1: a stricter bar for automotive

For automotive suppliers operating under IATF 16949:2016, the requirements in 7.1.5.2 are extended through 7.1.5.2.1 ("Calibration/verification records"). The standard requires that records of calibration and verification activities for all gauges and measuring and test equipment include equipment identification, including the measurement standard against which the equipment is calibrated; revisions following engineering changes; any out-of-specification readings as received for calibration; an assessment of the impact of out-of-specification condition; statements of conformity to specification after calibration; and notification to the customer if suspect product or material has been shipped.

The "out-of-specification" assessment is where location evidence becomes valuable. When a gauge fails verification, the question is no longer hypothetical: what parts did this gauge measure since its last good check, and where was it during that window? A location history reduces the customer-notification scope from "every part in the calibration interval" to "every part produced on the lines this gauge was actually present at." That distinction is the difference between a recall and a contained corrective action.

What TagLogger provides — and doesn't

TagLogger provides four things relevant to ISO 9001 and IATF 16949 traceability programs:

• **Location history per asset.** Every tagged item has a continuous location timeline, accessible to anyone in your workspace.
• **Geofences for controlled areas.** Define a calibration lab, a quarantine cage, or a customer-property storage area as a geofence. Entry and exit events get timestamped and can route to designated quality personnel.
• **Multi-user workspace with role-based access.** Quality managers, calibration technicians, and shift supervisors can all see the same data with appropriate permissions.
• **Export and integration.** Location history exports to CSV or JSON; an API is available for programmatic access. This is the integration point with your CMS — see data export and API integration for the formats and endpoints.

What TagLogger does not provide: calibration intervals, measurement uncertainty calculations, calibration certificates, traceability chains to NIST or NMI standards, gauge R&R studies, or any of the metrology-specific records 7.1.5.2 requires. Those remain the responsibility of your CMS. If your auditor asks for a calibration certificate, that comes from your CMS. If they ask where the gauge was between calibrations, that comes from TagLogger.

How location evidence strengthens a calibration program

A typical calibration management program tracks each gauge through a recurring cycle: due date, recall, calibration, certificate issuance, return to service. Between "return to service" and the next "recall," most CMS platforms record nothing about the asset. The gauge enters a black box, comes out 6 or 12 months later, and is verified again. TagLogger fills that black box with a continuous record. Three audit-relevant scenarios benefit directly:

• **Out-of-tolerance investigation.** A micrometer comes back from calibration reading 0.02 mm high. With a location history, the engineer can isolate which production cells the micrometer was used at, narrow the suspect lots, and document the assessment with timestamped evidence.
• **Missed calibration recall.** A gauge is overdue for calibration. With TagLogger, you open the location history and see whether the gauge is still on the floor, in storage, or has left the building. Time-to-find drops from days to minutes.
• **Customer audit on customer-supplied equipment.** Showing a customer a continuous location history that confirms the asset stayed within the agreed-on storage zone is more credible than a binder of sign-out sheets.

Implementation path for a quality team

A defensible rollout has four steps and does not require IT to deploy software on the shop floor.

• **Define scope.** List the gauges, fixtures, and customer-supplied equipment that will be tagged. Tie each to its asset ID in the CMS so the two records can be cross-referenced.
• **Tag and register.** Apply the AirTag, register the asset in the TagLogger workspace under its CMS asset ID, confirm the first location ping. Magnetic Holder for steel fixtures; Extended Battery Case where calibration interval is annual and you want the tag battery to outlast it.
• **Define geofences.** Calibration lab, quarantine, customer-property storage, finished goods, and any controlled area relevant to your QMS. Configure email alerts on transitions that matter — typically lab arrival, lab departure, and exits from customer-property zones.
• **Document the procedure.** Update your control of monitoring and measuring resources procedure to reference TagLogger as the location-evidence source. Identify access, export procedure, and retention rule.

Pricing in context: hardware is one-time ($15 Standard, $21 Magnetic Holder, $45 Extended Battery Case). Service is $10 per tag per month, dropping to $7.50 at 80+ tags. For most plants, the natural starting scope is high-value or high-criticality gauges first — torque wrenches, calibrated fixtures, customer-supplied checking gauges, master samples — rather than every caliper in every drawer. A pilot of 20 to 50 tags is enough to evidence the integration. See running multiple AirTags as a fleet for how this scales.