Grade Your Access Calibration DB Against ALCOA+

Three days before her IATF 16949 surveillance audit, Dagmar opened the Access calibration database to rehearse the one question she knew was coming: show me the history of this bore gauge. The record was there — interval, last calibration, as-left result. Then the auditor’s imaginary follow-up landed in her head: this due date used to be March. Who changed it to June, and when? She had no answer. The field simply said June. There was no log of the edit, no name, no timestamp, no reason. The database had been telling her the truth as it currently stood, and it had quietly overwritten every earlier version of that truth.

If that scene is familiar, this article is a tool, not a lecture. Before anyone migrates anything, it helps to grade what you already have — honestly, against the same framework your auditor is using. That framework has a name.

Why the Access database was the right call — once

Someone on the quality team built it, and they built it well for the moment. Access was already licensed. It gave you tables, forms, and reports without a purchase order or an IT project. When the choice was between a spreadsheet that everyone edited and a real relational database with drop-downs and a due-date query, Access was a genuine step up. It worked. For a small instrument catalog and one or two people entering results, it worked for years.

None of that is in dispute. The problem is not that you made a bad decision; it is that the decision was made against requirements that have since grown teeth. Auditors no longer just ask whether a record exists. They ask whether the record can be trusted — and they have a vocabulary for exactly what "trusted" means.

What ALCOA+ is, and why your auditor thinks in it

ALCOA+ is a data-integrity framework: Attributable, Legible, Contemporaneous, Original, Accurate — plus Complete, Consistent, Enduring, and Available. It originated in regulated data-integrity practice and has since become the common language for judging whether a record is reliable evidence.

You will not find the letters "ALCOA+" printed in ISO 9001, but the ideas are threaded through the clauses your calibration program is certified against. ISO 9001:2015 clause 7.1.5 requires that monitoring and measuring resources be suitable and that you retain documented information as evidence of fitness for purpose. IATF 16949 sharpens this in clause 7.1.5.2.1, which explicitly lists what calibration records must contain — including revisions following engineering changes, notifications when suspect product may have shipped, and the condition of equipment as-found. ISO/IEC 17025:2017 goes further still, with clause 7.5 on technical records, 7.11 on managing data and information systems, and 8.4 on the control of records. ISO 10012 wraps the whole measurement management system around the same expectation. Read together, they describe records that are attributable, unalterable without trace, complete, and durable. That is ALCOA+ in all but name.

So the useful move is to stop guessing what the auditor will find and grade yourself first.

The 10-point ALCOA+ scorecard for your Access database

Score each item 0 (fails), 1 (partial), or 2 (fully met) for a legacy Access or Access+Excel setup. Be strict — an auditor will be. ALCOA+ has nine attributes; I add a tenth, Traceable, because in metrology traceability is inseparable from integrity.

1. Attributable

Can you prove who recorded each result and who changed it later? A shared Access file where everyone opens the same front end under one Windows login, or where records carry no user stamp, scores 0. This is the question that undid Dagmar.

2. Legible

Are results readable and permanent, not a cell someone can retype? Free-text fields and Excel cells that accept anything, including a value that overwrites the last one, score low.

3. Contemporaneous

Was the result recorded at the time of calibration? If technicians batch-enter a week of results on Friday from paper notes, the database timestamp is the entry time, not the event time — and nothing enforces the difference.

4. Original

Is the record the original entry, or a transcription? A number keyed from a handwritten sheet into Access, with the sheet then discarded, is a copy. The as-found/as-left values live nowhere in their original form.

5. Accurate

Does the system stop wrong data at the door? Access forms rarely validate that a tolerance is numeric, that an interval is positive, or that as-left is within tolerance. A typo in a due-date field is a finding waiting to be discovered.

6. Complete

Are all data present, including reworks, repeat calibrations, and out-of-tolerance events with their impact assessment? If an overwrite erased the prior due date, the record is by definition incomplete — the earlier state is gone.

7. Consistent

Do dates, sequences, and formats behave identically for everyone? A regional-settings mismatch that reads 06/03 as June 3 on one PC and March 6 on another silently shifts due dates. Access inherits the workstation’s locale; nothing guarantees consistency across machines.

8. Enduring

Will the record survive? An .accdb depends on a compatible Office version, an untested backup, and a file that lives outside IT’s disaster-recovery scope. "Enduring" is not a property of a file you compact-and-repair every Monday.

9. Available

Can you retrieve any instrument’s full history on demand, during the audit, without the one person who understands the schema? If the answer depends on a specific engineer being in the building, you score 0 here regardless of how good the data is.

10. Traceable

Can you show the unbroken chain from the instrument’s result back to a national or international standard — reference standard, its certificate, its own calibration due date — as ISO/IEC 17025 clause 6.5 expects? If traceability lives in a separate folder of PDFs that the database never links to, the chain is only as strong as your memory of where the files are.

Reading your score

A modern, controlled system should sit at or near 20. Most honest legacy setups land between 6 and 11 — strong on Legible and Available-to-the-author, weak on Attributable, Complete, Enduring, and Traceable. The value of the number is not the number. It is that it converts a vague anxiety — I think we’d be fine — into a specific, defensible list of gaps you can hand to management. Nobody funds a migration to escape a feeling. They fund it to close eight named integrity failures before the next surveillance visit.

What closing the gaps actually looks like

The reassuring part is that every low-scoring item maps to a capability you can simply have, rather than maintain. In PrüfDesk, each result is recorded under a named user, so Attributable is automatic. Records are not editable in place; the history of an instrument is retained rather than overwritten, which is where Complete and Original come from. Due dates are auto-calculated from the last calibration and the interval, removing the typo-in-a-date-field failure that hurts Accurate. As-found/as-left values, pass/fail status, and the certificate are captured together, and configurable overdue blocking — a hard block or a soft warning per tenant — means an overdue instrument surfaces instead of hiding. Reusable procedure templates move the calibration steps out of one engineer’s VBA form, so the method is Available to the whole lab. Audit-ready PDF reports render the full, controlled history on demand — which is the difference between Available to its author and available to an auditor. And because reference-standard links and their own due dates live in the same system, Traceable stops depending on a folder nobody controls.

Grading is not the same as leaving today

The scorecard tends to provoke one of two overreactions: we’re fine, ignore it, or we have to rip everything out this weekend. Neither is right. A calibration record is legal and quality evidence with a retention obligation; you move it deliberately, not in a panic. The safe path is staged: export the Access tables, clean the obvious integrity debris (duplicate serials, impossible dates, orphaned records), map each Access field to its destination, validate the migrated data against the source record by record, and run in parallel for one calibration cycle so you can prove the new system agrees with the old before you retire it. Crucially, you preserve real history — you do not stamp every legacy record with the migration date, because rewriting your own dates fails Contemporaneous and Original in one move. When you are confident, the old database becomes a read-only archive your retention policy already expects, not a deleted file.

A short pre-migration checklist

• Export a full copy of every Access table and keep the original untouched.
• List duplicate serial numbers, blank intervals, and impossible or overwritten dates.
• Confirm which file is genuinely the master, not Cal_Database_FINAL_v3.accdb.
• Gather the certificate PDFs and note which records they belong to.
• Write the field-by-field map from Access to the new system before importing anything.
• Decide the parallel-run window — one full calibration cycle is a safe default.
• Agree who signs off that the migrated data reconciles with the source.

Where to start

Run the ten questions this week, on your real database, with your team in the room. If you score above 16, you are in good shape and this was a useful confirmation. If you score below 12 — and most legacy setups do — you now have a concrete, standards-anchored case rather than a hunch. When you want to see how the same instruments and their full history look in a system built to score 20, that is a conversation worth having on your timeline, not under audit pressure.