4Sight2 Tags vs Instruments: Map Before You Price
A 4Sight2 tag is not an instrument. Map plant > location > tag > device > range to a per-instrument count and keep every calibration result traceable.
A 4Sight2 tag is not an instrument. Map plant > location > tag > device > range to a per-instrument count and keep every calibration result traceable.
If your old Access calibration database still accepts edits after go-live, someone will keep using it. How to freeze it on cutover day and keep history.
'±0.02', '+0.05/-0', '4%', 'see dwg' — one Access Tolerance column. How to turn free text into limits a system can judge before you migrate.
An as-found OOT result needs one of four decisions: no impact, re-inspect, notify or recall. A one-page template, the evidence each needs, worked through.
The label says reference only. The inspection record says accepted. Here's how to control non-calibrated instruments before your 7.1.5 audit samples one.
Ten green calibration records from your own register prove little. A stratified 7.1.5 sampling plan that traces four ways, with a worked example.
Access said 9 overdue. The new system says 61 on day one. Where the gap comes from, and how to brief management before go-live instead of after.
Leaving MET/TEAM 3.3.x? Set migration depth from your retention obligations, not the integrator's quote. Three tiers, a worked example, a checklist.
A clean calibration sheet can go live in one day if it passes three go/no-go gates. Here is the hour-by-hour plan, and the point at which to stop.
Ten things an auditor circles on a calibration workbook, each mapped to its ISO 9001, IATF 16949, AS9100 or 17025 clause, and what to fix before import.