Skip to content

Life Sciences

CSV vs CSA on one BMS alarm function

  • Life Sciences
  • 1 min read

One BMS pressure alarm test often runs to forty pages of screenshots, and none of them shows the transmitter failing.

FDA's Computer Software Assurance guidance goes after exactly that. Classic CSV puts the effort into documentation: a pre-approved script, a screenshot per step, a signature per page. CSA moves it to intended use and risk, and tests hardest where a failure would hurt product or data.

Take the pressure alarm between a Grade C corridor and a Grade D change room. Under a scripted approach, the tester forces the value below setpoint, waits out the delay, captures the banner, acknowledges, captures the event log. Every step is written and evidenced in advance.

Under CSA, the first question is what the alarm is for. It protects the cascade, so it is high risk and still gets scripted tests on setpoint, delay and the record it writes. Then the tester spends time unscripted: pulling the transmitter signal, changing the setpoint without the right role, restarting the server mid-alarm. The record says what was tried and what happened, without a screenshot per click.

The guidance was written for medical device production and quality system software, so a pharma site applies it by analogy, usually alongside GAMP 5. We write the validation strategy in parallel with the design, which is where the test depth for a function like this gets decided.

Which BMS alarm has your thickest test pack and thinnest risk case?

Industries

Related

More on this subject

Infrastructure qualification under a GMP SCADA

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.

InsightRead

Keep the BMS outside the EMS validation boundary

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.

InsightRead

Part 11 applies to electronic records that a predicate rule such as 21 CFR 211 requires. For a BMS or EMS, name the rule behind each point: GMP-critical monitoring usually belongs in a validated EMS. For EU export, Annex 11 has no predicate-rule test, so the BMS still needs a risk assessment.

InsightRead