Scope each update's tests across the plant's validated systems and sign as author
- Each lit function with the passage behind it
- No-test reasons written for an inspector
- Rulings that become rules once QA approves
GxP change control for monthly operating-system patches that draws each validated system as its layers, lights the layers a patch changes, and sizes the test that each validated function standing on them needs, with the reason written and signed.
See one monthly patch scoped screen by screen ↓Each month a security update changes the operating system under most validated systems: the time service that stamps audit trails, the cryptography that carries instrument data over the network, the spooler that prints batch records. Whether a validated function stands on a changed layer sits across each system's configuration specification, the supplier's statements, the test library and the update's own notes, and in no single document.
So the CSV lead falls back on a habit. Testing everything turns a monthly update into a yearly freeze while IT security carries the exposure; writing no impact, often copied from last month, leaves the site unable to tell an inspector how it knows the time stamps did not move.
Built forCSV leadsSystem ownersIT security officersQA heads
Monthly patches reach validated systems, and nobody can show which validated function each one touches.
Read by hand for each update
Built-in controls
Security fixes go in on their clock, and each validated function is tested where a patch reaches it.
The CSV lead runs the read, the supplier answers in fields, a challenger corrects the draft, and owners, IT security and QA sign before each wave, up to the evidence checked after the install.
demoThe plant, its systems, suppliers, people, dates and test hours on these views are sample data.
Sizing, go-ahead, install and any wait each sit with a different role.
Scope each update's tests across the plant's validated systems and sign as author
Give the go-ahead for their own systems before each wave
Raise the change, apply the update and run the post-patch checks
Rate each fix and sign any wait with its compensating control
Past the one plant's read: batch control's own stack, the supplier's side, the record that exposed the historian, the queue across plants, the trail and the rules.
demoSample data, from the working solution.
Four findings from one sample month that a one-line impact assessment would have let through.
Last month's LIMS audit-trail test ran at 10:42 and the server was patched at 11:05; the checker caught it, and the test was re-run at 13:20.
Its older specification said the controllers stamp values; the settings export said the operating system does, the same clock a cooling trace is read from.
The supplier named firmware below 3.2 as affected, and two of the lab's HPLCs run 3.1, so the acquisition run goes to those two.
The MES terminals were due for patching the night before the weekly print of executed batch records for client release packages; a steer held them until after it.
demoSample data, from the working solution.
Seven agents read, map, size, ask, plan, challenge and check; people sign.
Reads the update's notes and classifies each component by the layer it changes and how.
Draws each system's layers and validated functions from its signed configuration specification and the asset inventory.
Sizes the test for each lit function under the site's assurance procedure and applies approved learned rules.
Sends structured compatibility requests and reads replies by their fields.
Reads the production schedule and the change calendar and plans waves around changeovers.
Questions the draft as an inspector might, its fellow agents' conclusions included.
After the patch, re-reads each machine's installed updates and settings and checks each test record's time and build.
GxP change control is the controlled, documented and tested change of a validated computerized system, so it stays validated. Here agents read the update's notes against each system's layers and size the test each lit function needs; people sign.
FDA's computer software assurance guidance favors unscripted testing where risk to the intended use is low and scripted testing where it is high. It is written for device software; drug sites apply it through their own procedure.
The test is sized to what changed. A validated function on a changed layer gets a scripted or unscripted test; a system with none gets the standard post-patch check and a written reason.
How the site knows the update did not change what a validated function relies on, such as the audit-trail clock. Each no-test row carries its reason and record, and QA opens a sample before approval.
The IT security officer, after both options are played forward. The wait needs a compensating control inside the critical target; a tighter clock clears it.
That depends on the quality agreement. In this sample, security updates go in each client's annual change summary, with prior notice only when a validated function, method, process or registered detail changes.
An evidence checker re-reads each machine's updates, versions and time source, and checks each test ran after the install on the patched build. Only the QA head closes the change.
Testing sized to each function's risk, every line linked to its source.
1-min demoAudit Trail ReviewEvery audit-trail period reviewed on schedule and signed, rows cited
1-min demoAI Use Case Risk ClassificationEvery new AI idea classified in minutes, each conclusion tied to its clause.
1-min demoSend one monthly update's change notes, the specifications of the systems it touched and your test library; we will light each stack and size its tests.