A Windows patch on the SCADA server should not trigger a new SCADA validation, unless nobody qualified the platform underneath.
Below a GMP application sits a stack unrelated to the process: physical or virtual servers, storage, network switches, domain controllers, backup and the time server. GAMP 5 and its IT infrastructure guidance treat that layer differently. The application is validated for its intended use. The infrastructure is qualified: installed to a documented specification, its configuration recorded, then held under change control and periodic review.
On a qualified platform a routine OS patch goes through infrastructure change control with an impact assessment, and the application gets a targeted check rather than a fresh OQ. Moving a virtual machine between hosts in a qualified cluster is handled under the platform's own procedures, and the SCADA's validation stays as it was.
Some infrastructure items decide data integrity directly. Audit trail timestamps come from the server clock, so time synchronization belongs in the qualification. A backup counts once a restore has been tested. Hypervisor console access reaches every GMP system on the host, so it belongs in the same access review.
Our validation strategy is written in parallel with the design, and our automation work delivers SCADA to 21 CFR Part 11 and Annex 11.
Who owns change control for the hypervisor on your site, IT or QA?
Topics
Industries



