PHARMA AUTOMATION
Pharmaceutical Automation: GMP, GAMP 5, 21 CFR Part 11 and ISA-88 for Control Engineers
What changes when a PLC or DCS makes medicines: the validation lifecycle, electronic records and audit trails, data integrity, and ISA-88 batch control, explained for control engineers.
Pharmaceutical automation is PLC, DCS and SCADA work done under Good Manufacturing Practice (GMP): every system that affects product quality must be specified, tested and documented, keep secure audit trails and protect data integrity. The main references are GAMP 5 for validation, 21 CFR Part 11 and EU GMP Annex 11 for electronic records, and ISA-88 for batch control.
The control techniques are the same as in any process plant: analog loops, sequences, batch phases, HMIs and historians. What changes is the evidence. In most industries a system that works is finished. In a GMP plant, a system is finished when you can prove it does what it was specified to do, and that its records can be trusted.
The rules, in general terms
GMP is the set of regulations and guidelines that govern how medicines are made, enforced by national regulators. For automation, the relevant parts concern computerised systems.
[21 CFR Part 11](https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11) is the US FDA regulation on electronic records and electronic signatures. In general terms it expects systems to be validated, access to be limited to authorised individuals, secure computer-generated and time-stamped audit trails to record the creation, change and deletion of records, and electronic signatures to show the signer's name, the date and time, and the meaning of the signature (such as review or approval).
EU GMP Annex 11, in Volume 4 of the European Commission's EudraLex, covers computerised systems for the EU, with similar themes: risk management, validation, data integrity, audit trails, security and signatures.
GAMP 5, published by ISPE and now in its second edition, is industry guidance on a risk-based approach to compliant GxP computerised systems. It is not a law, but it is how most companies and suppliers organise validation. Its software categories help scale the effort: infrastructure software (category 1), non-configured products (3), configured products (4) and custom applications (5). A configured SCADA package usually sits in category 4; custom PLC or DCS logic in category 5, which needs the most scrutiny.
In this lesson by GMP GUIDE, from our free AI for Pharmacists course, computer system validation (CSV) is compared with computer software assurance (CSA), with reference to FDA Part 11 and GAMP 5. The lifecycle below is the structure that both approaches work within.
The validation lifecycle
Each specification on the left is verified by a test on the right. The URS says what the users need. The FS says how the system will meet it. Design specifications detail hardware, software modules and configuration. Testing then works back up: FAT at the supplier, installation qualification that the system is installed as designed, operational qualification that it works across its operating ranges, and performance qualification that it performs in real production.
A traceability matrix links every requirement to the design and to the test that proves it. Change control means that once validated, nothing changes (code, configuration, even a PID tuning parameter if it is under control) without an assessed, approved and tested change. For an engineer used to editing online in a running PLC, this is the biggest adjustment.
Data integrity and ALCOA+
Regulators expect GMP records, paper or electronic, to meet the ALCOA+ principles.
For a control engineer this becomes concrete design work:
- Individual user accounts with roles, never a shared operator login on an HMI.
- Audit trails on setpoint, recipe, alarm limit and mode changes, recording who, when, the old value and the new value, and where required, why.
- Time synchronisation across PLCs, HMIs, servers and historians, so events are in the right order.
- Electronic signatures on critical actions such as batch release, applied in the way the procedure defines.
- Protected data: no local administrator rights for operators, no way to delete or edit records outside the audit trail, and backups that are tested by restoring them.
Batch control with ISA-88
Most pharmaceutical processes are batch processes, and ISA-88 is the standard model for them. It defines a physical model (process cell, unit, equipment module, control module), a procedural model (procedure, unit procedure, operation, phase) and a set of recipe types (general, site, master and control).
The practical value is separation. Equipment phases such as charge, heat, agitate and transfer are written and validated once in the controller. Recipes, which say which phases run in which order with which parameters, are managed as data in a batch system. A new product or a parameter change becomes a recipe change rather than a code change, which is far cheaper to validate. The same structure shapes the electronic batch record, often held in an MES, so every step and parameter of a batch is recorded against the recipe that ran it. Major DCS platforms, including Emerson DeltaV and Siemens PCS 7, offer batch packages built on ISA-88; our DCS training guide explains how those platforms are organised.
Other pharma-specific systems
Beyond production equipment, automation engineers in pharma meet clean utilities (purified water, water for injection and clean steam), room pressure cascades and environmental monitoring for clean areas, clean-in-place and sterilise-in-place cycles, and serialisation on packaging lines. Each has its own records and validation. For the packaging side, see packaging automation trends at PACK EXPO 2026.
How to prepare
Learn the control platforms first; GMP knowledge on top of weak automation skills does not help anyone. Then practise the habits: write a requirement you can test, write a test script someone else can execute, and document a change before you make it. Those habits are what a validated environment rewards.
It also helps to understand who does what. The regulated company owns the system and its validation. Suppliers and integrators provide specifications, tested software and documents that the company can use as evidence, and GAMP 5 encourages making full use of supplier testing rather than repeating it. An engineer at a system integrator therefore spends a good share of the project writing and executing documents the customer's quality team will review line by line.
Free pharmaceutical automation courses for the control side
EDWartens has no course dedicated to GMP, and we will not pretend otherwise. These free courses teach the control systems pharmaceutical plants use:
- Emerson DeltaV DCS: architecture, Control Studio, PID, sequences, operator displays, alarms and history.
- Siemens SIMATIC PCS 7 DCS: AS and OS configuration, CFC, SFC sequences, alarms and control templates.
- HMI Design: Siemens WinCC and FactoryTalk View ME: screens, alarms, recipes and users, including security and 21 CFR Part 11 features in FactoryTalk View ME.
- Industrial Instrumentation and Process Control: measurement, 4-20 mA loops and calibration.
Every course is free in full, with credited video lessons, notes, practice tasks and one final assessment; no card is needed. The optional EDWartens Certificate of Completion is a small one-off fee, US$8.99 for the beginner courses and a little more for the intermediate DCS courses. It can be checked at edwartens.com/verification. It is not a GMP, GAMP or vendor qualification and is not accredited. Create a free account to start.
Take the free course
Questions
What is GAMP 5?
A guide published by ISPE describing a risk-based approach to compliant GxP computerised systems. It sets out a lifecycle of specification, verification and operation, scaled to each system's risk to patients, product quality and data integrity.
What does 21 CFR Part 11 require of an automation system?
Part 11 is the US FDA regulation on electronic records and electronic signatures. In general terms it expects validated systems, access limited to authorised people, secure computer-generated time-stamped audit trails of record changes, and electronic signatures that show who signed, when and what the signature meant.
What is the EU equivalent of Part 11?
EU GMP Annex 11, on computerised systems, in Volume 4 of EudraLex. It covers similar ground: risk management, validation, data integrity, audit trails, security and electronic signatures.
Why is ISA-88 used in pharmaceutical batch control?
Because it separates the recipe from the equipment control. Product recipes can change without rewriting and revalidating the underlying phase logic, and the batch record follows the same structure as the recipe.
Is there a free GMP course on EDWartens?
No course is dedicated to GMP. The free DeltaV, PCS 7, HMI and instrumentation courses teach the control-system side, including user security and 21 CFR Part 11 features in FactoryTalk View ME in the HMI course.
Sources
- eCFR: 21 CFR Part 11, Electronic Records; Electronic Signatures
- European Commission: EudraLex Volume 4, EU GMP guidelines including Annex 11
- ISPE: GAMP 5 Guide, 2nd Edition
- ISA: ISA-88 series of standards, batch process control
Written by the EDWartens engineering team for general education. Product names are trademarks of their owners; mentioning them does not imply endorsement. Prices and terms of other providers were checked on the date shown and can change.
Oil and Gas Automation: How DCS, SCADA and Safety Systems Fit Together
HMI Programming Training: How to Design Industrial Operator Screens
Safety PLCs, SIL and SIS Explained: Functional Safety for Engineers
Process Instrumentation Basics: Pressure, Level, Flow, Temperature and the 4-20 mA Loop
Water Treatment Automation: How PLC and SCADA Control a Treatment Works
4-20 mA Current Loop Explained: Wiring, Loop Power and Faults (Video)