A SCADA historian can write thousands of audit trail entries in a week. If nobody can filter them, nobody really reviews them.
The Annex 11 draft that went out for consultation in July 2025 says far more about audit trail review than the 2011 text: what is reviewed, how often, by whom, with frequency tied to risk. Check the status of the final text before relying on its exact wording.
An SOP can be rewritten in a few weeks. Whether the system supports review at all is settled in the URS, which is why we would act there first. Requirements we now write into new SCADA and historian URS documents:
- Audit trail filterable by batch, time window, user and record type, so a reviewer sees setpoint and recipe changes without paging through alarm acknowledgements.
- Each change to GxP data shown on one line with old value, new value, reason and user.
- The review itself recorded in the system: who reviewed which range, when, and what they flagged.
- No role able to switch the audit trail off or edit it, administrators included.
A system bought now without these will still be running when the final text applies, and adding a review function to a validated historian later is a change project of its own.
We write automation and SCADA requirements to 21 CFR Part 11 and Annex 11, and new URS documents take the draft as design input.
How do you review a SCADA audit trail today: on screen, as a printed report, or as an export?
Industries



