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.
A gauge fails as-found at recalibration. Now prove which parts it touched — the out-of-tolerance impact assessment auditors expect, spreadsheets can't.
A 90-day, auditor-grade calibration checklist for Q4 surveillance: overdue status, traceability, uncertainty, as-found/as-left, retention — no scramble.
A bare PASS won't survive an audit. Name the decision rule (ISO/IEC 17025 7.8.6), account for guardbanding, and store what makes it defensible.