Skip to content

Life Sciences

GAMP 5 categories 1, 3, 4, 5, and where 2 went

  • Life Sciences
  • 1 min read

GAMP 5 software categories run 1, 3, 4, 5. There is no Category 2 any more; firmware was dropped as a category in 2008.

The gap confuses new CSV engineers every year, so here is the list with the effort that goes with it:

Category 1, infrastructure software: operating systems, databases, network software. Record the version, qualify the platform, move on.

Category 3, non-configured products: used as supplied, with at most run-time parameters. Verify it does what your process needs.

Category 4, configured products: the software is standard, the configuration is yours. SCADA, BMS, most LIMS. Test the configuration against your requirements.

Category 5, custom applications: code written for you. Design review, code review, testing to the depth of the risk.

Firmware did not disappear. It is now placed in whichever category matches what it does and how far you can configure it.

The mistake we see is treating a whole system as one category. A SCADA package is Category 4. The scripts someone wrote inside it to calculate a batch value are Category 5, and they deserve Category 5 testing. The Second Edition (2022) kept the categories and pushed harder on critical thinking: the category tells you the starting effort, the risk to product and data tells you the finish.

Our automation work covers SCADA to 21 CFR Part 11 and Annex 11 on Rockwell, AVEVA, COPA-DATA and Ignition, and the category split is one of the first things we agree with QA.

Industries

Related

More on this subject

Backup and archive are two controls under Annex 11

EU GMP Annex 11 clause 7.2 asks for regular backups whose restore is checked during validation and periodically. Clause 17 asks that archived data stays accessible, readable and intact, with retrieval re-tested after system changes. A green nightly backup does not prove that old trend data opens after an upgrade.

InsightRead

21 CFR Part 11 and EU GMP Annex 11 overlap on validation, access control and audit trails but differ in emphasis: Part 11 on electronic signatures, Annex 11 on a risk-based system lifecycle. Fixing the destination market in the design basis means the URS and validation plan for BMS, EMS and SCADA are written once.

Read

ALCOA+ on the EMS is a design requirement

Environmental monitoring and BMS data that support GMP decisions must meet ALCOA+. In practice that means individual logins, time-synchronized controllers, an audit trail users cannot disable, alarms acknowledged with name and comment, and tested backups, with GMP-critical parameters separated early onto a validated system.

Read