On a small site, the engineer who configures the SCADA is often the same person who runs it on night shift.
That person can change audit trail settings and also generate GMP data.
Data integrity guidance treats that as a conflict. PIC/S PI 041-1 (2021) expects system administrator rights to be restricted and, where possible, held by people independent of those who generate, review or approve the data. The MHRA GxP Data Integrity Guidance (2018) takes the same line on segregation of duties.
Plenty of sites cannot staff a separate administrator for a BMS, an EMS and three SCADA stations. The guidance allows for that with its "where possible", provided the conflict is documented and controlled.
The controls are ordinary ones. Every admin account carries a person's name; there is no shared "admin" login. The engineer who holds both roles gets two accounts and logs in as an operator on shift. Admin activity is logged and reviewed on a fixed schedule by someone else, usually QA or IT, and configuration changes go through change control instead of being made from the operator's chair.
Write the arrangement into a user role matrix: each account, its privileges, and who reviews its activity. An inspector can then follow it in a few minutes.
Automation and SCADA to 21 CFR Part 11 and Annex 11 are part of our engineering scope.
Who reviews your system administrators' activity, and how often?
Industries



