21 CFR 11.10(e) asks for "secure, computer-generated, time-stamped audit trails". A logbook beside the EMS is none of those.
Start with who writes the entry. The system has to record each change as it happens, with the user, the old value and the new one. A handwritten note about an alarm limit helps an investigation, but the inspector will ask for the software's record.
Security means nobody can edit or delete an entry, the administrator account included. Plants get caught by housekeeping here: an archive job or database purge that drops old trail entries is a data integrity problem, however tidy the result looks.
A time stamp only helps if the clocks agree. Synchronise the EMS server, the particle counters and any data loggers to one time source and record the time zone, or the order of events cannot be rebuilt after an excursion.
The paragraph also asks that changes do not obscure earlier entries, and that the trail is kept as long as the records it covers.
For an environmental monitoring system this is URS material. Setpoint and alarm-limit changes, acknowledgements with a reason, user and role changes and data edits all go in the trail, and a named role reviews it on a defined frequency. Many plants keep GMP monitoring on a separate EMS because a BMS built for facility control often lacks these functions.
We design SCADA and monitoring systems to Part 11 and Annex 11, audit trail requirements included in the URS.
Industries




