Store DCC uncertainty as data, not a spreadsheet string
"± 0.3" is not the uncertainty. See what a PTB DCC really carries — k, coverage probability, distribution — and why to store it, not re-key it.
"± 0.3" is not the uncertainty. See what a PTB DCC really carries — k, coverage probability, distribution — and why to store it, not re-key it.
Migrating off an Access calibration database? If the import stamps the cutover date on every record, your traceability collapses. Preserve it instead.
An as-found fail, as-left pass gauge is a modified gauge. PPAP element 8 wants a fresh MSA before it re-qualifies parts. Here's why, and how to prove it.
A re-keyed spreadsheet cell proves nothing at audit. A signed Digital Calibration Certificate is evidence your assessor accepts — and how to ingest one.
A block-by-block tour of the PTB DCC XML schema v3.3.0: administrative data, measurement results, D-SI units, and the signature that makes it trustworthy.
A spreadsheet can't prove who moved a calibration due date, or when, or why. How record data integrity holds up under ISO 9001 and 17025 scrutiny.
Your Access calibration DB lets anyone edit a past result with no trace. Here's why that's an audit finding waiting to happen — and how to migrate safely.
Your Access calibration DB logs pass/fail but not as-found/as-left. Here's why auditors ask for it, and how to migrate without losing history.
A gauge came back as-found out of tolerance. Here is how to scope every measurement it touched since its last good calibration — and survive the audit.
The certificate came back but the due date didn't. How false-overdue flags erode trust in your recall list — and how to close the gap before an audit.