Skip to content

Life Sciences

The room data sheet changes jobs at qualification

  • Life Sciences
  • 1 min read

The room data sheet written for the design basis often ends up as the document an inspector checks your monitoring limits against.

It does two different jobs in its life, and each needs different revision control.

At design stage it is an input. Grade, pressure, temperature and RH ranges, process heat, people, equipment, finishes. It changes every week while loads settle and the process team makes up its mind, and it should. The design team owns it. A revision letter and a log are enough.

After qualification it is a record. It holds the values OQ tested against and PQ proved, and the limits the monitoring system alarms on. Now a changed setpoint without a revised sheet means the BMS and the qualified record disagree, and the change belongs under change control, owned by QA.

The trouble starts when nobody decides the moment the sheet changes role. Design keeps editing a file QA already treats as approved. Or QA freezes it before the loads are settled, and the engineers keep a private copy.

EU GMP Annex 15 expects the URS to stay a point of reference through the validation life cycle. The room data sheet is the room-level part of that reference.

We start projects from a set of 34 standard pharma room data sheets and write the URS alongside them. Our view: agree the freeze point before DQ, not at OQ.

At which gate does your room data sheet move under change control?

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

CSV vs CSA on one BMS alarm function

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.

InsightRead

Part 11 or Annex 11: fix the destination market on day one

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