Skip to content

Audit trail and electronic signatures in WinCC: meeting 21 CFR Part 11

What 21 CFR Part 11 requires, what WinCC provides, and how to specify, configure and qualify compliant supervision.

Published on October 17, 2026

21 CFR Part 11 is the FDA regulation that sets the conditions under which electronic records and signatures are equivalent to paper records and handwritten signatures. For WinCC supervision running a pharmaceutical, medical device or sterilization process, it translates into three concrete requirements: knowing who did what and when, being able to sign a critical action, and protecting these records.

What the regulation requires

RequirementReferenceWhat it means for supervision
Secure, computer-generated, time-stamped audit trail§11.10(e)Record date, time, user and action for every creation, change or deletion, without obscuring previous values
Access limited to authorized individuals§11.10(d), (g)Named accounts, role-based rights, authority checks before each action
Signature manifestation§11.50Show the signer’s printed name, date, time and meaning (review, approval, responsibility)
Signature/record linking§11.70The signature cannot be copied or detached from the signed record
Unique identification§11.100, §11.300One ID per person, never reassigned, managed passwords
Two identification components§11.200Non-biometric signature: at least an ID and a password

The regulation does not only call for software functions: it also requires procedures (account management, periodic audit trail review, training). Supervision provides the means; the site’s organisation ensures they are used.

What the WinCC environment provides

In the TIA Portal environment, GMP functions in supervision rely on the WinCC Audit option, which is licensed, and on suitable user management: local or central depending on the version (WinCC Advanced or WinCC Unified) and the installed components.

In practice, a compliant project relies on:

  • an audit trail of the tags and actions declared quality-relevant: setpoint change, acknowledgement, cycle start or stop, recipe change;
  • electronic signatures on critical actions: supervision asks for the user ID and password, then a comment or reason, before executing the action;
  • audit trail protection: controlled storage and integrity checking;
  • user management: named accounts, role-based groups and rights, lock-out after failed attempts, password expiry.

Available functions depend on the WinCC version and installed options: the choice is made at specification stage.

How EAi implements it

  1. Specify what is GMP. With your quality department, we list the tags and actions that must go into the audit trail and those that require a signature. Too few, and the audit trail proves nothing; too many, and it becomes unreadable.
  2. Design the rights. We describe the roles (operator, production manager, quality, maintenance) and what each one can do.
  3. Configure and develop audit, signatures and rights in the WinCC project, together with batch reports (PM-Quality, PM-Analyze) when used.
  4. Test and qualify. Each requirement in the table above has its OQ test: action logged, signature refused without rights, consistent time stamps, audit trail not editable.
  5. Document for the audit: specification, traceability matrix, qualification protocols and reports.

Common audit findings

  • Shared accounts ("operator", "maintenance"): they make the audit trail unattributable.
  • Unsynchronised clocks: a wrong time stamp weakens the whole record. Time synchronisation is part of the design.
  • Audit trail never reviewed: the regulation expects a review. Provide a simple view, filtered by batch or period.
  • Untracked changes to the supervision itself: the WinCC project must be versioned and any change must go through change control. See Change control and requalification.

In short

Meeting 21 CFR Part 11 in WinCC is first a matter of specification: deciding what must be logged and signed. The tools exist; their configuration, their qualification and the procedures around them are what make a system compliant.

A regulated supervision project to start, or an existing system to bring into compliance? Let’s talk.

Let’s discuss your project.

Continuous improvement, revamping, qualification or root cause analysis: let us define together the solution suited to your installation.

Thierry Pontlevy, manager of EAi SARL, in front of a process supervision screen

Thierry Pontlevy

Manager, independent consultant in automation and EO sterilization