GAMP 5 software categories are 1, 3, 4 and 5; firmware stopped being Category 2 in 2008. Validation effort rises with each step, and a configured Category 4 SCADA can still hold Category 5 scripts that need custom-code testing. The 2022 Second Edition kept the categories.
A spreadsheet that calculates F0, an assay result or an airflow figure is a computerized system under EU GMP Annex 11 once its answer drives a GMP decision. Locked formula cells, one released template under version control and formulas checked once by hand are the minimum an auditor will look for.
EU GMP Annex 11 clause 3.2 makes supplier competence and reliability part of computerized system validation, with the need for an audit set by risk. For SCADA, BMS and EMS, supplier records can reduce the testing the user repeats; the URS, risk assessment and configuration tests such as alarm limits and user roles stay with the user.
A recovery test with a 20-minute limit, traced to a 15-minute URS requirement, passes and leaves the requirement unproven. Reading a trace matrix from each test back to its requirement finds these weak links and orphan tests. Pick three signed results at random and trace them back.
Servers, network, virtualisation, backup and time sync under a GMP system are qualified as a controlled platform; the application on top is validated for its intended use. With the platform qualified, a routine OS patch needs an impact assessment and a targeted check, not a new OQ of the SCADA.
Scripted CSV evidences every step of a BMS pressure alarm test. FDA's Computer Software Assurance guidance keeps scripted tests for high-risk checks such as setpoint, delay and the audit record, then adds unscripted testing of failure modes, recorded by what was tried and what happened.
GAMP 5 Second Edition (2022) scales validation effort to risk to patient safety, product quality and data integrity, and adds agile and cloud guidance. On a GMP BMS, test alarms, audit trail and data transfer deeply. A quick check: count low-risk functions that still carry full test scripts.
When the BMS and the validated EMS share one platform, the validation boundary takes in the control logic and every setpoint change becomes change control. An EMS with its own sensors, database and QA alarms under Part 11 and Annex 11 allows the BMS to be managed under good engineering practice.