Skip to content

Manufacturing & Distribution

Make a stopped FFU visible at the room

  • Manufacturing & Distribution
  • 1 min read

In a ceiling of forty fan filter units, a stopped one looks exactly like a running one from the floor.

The grille is the same and the noise barely changes. Room pressure may drop a pascal or two, well inside the alarm band, and the particle counter may not be anywhere near that unit. Meanwhile the unidirectional airflow over one part of the zone has gone, and nobody knows until the next smoke study or a count that fails.

Most EC-driven FFUs can report their own status over a network: running, speed, fault. Reading it takes a network cable and some integration work, which is small next to an impact assessment covering every batch made in that zone since the last good reading.

Send each unit's fault to the BMS or SCADA, and give the room a local indication the operator can read without a laptop. A panel at the door showing a dead unit by its grid position is enough. The BMS keeps the time-stamped record for the deviation, and the panel stops the batch from starting.

If the monitoring holds GMP data, it is designed to 21 CFR Part 11 and Annex 11 like the rest of the system, including an audit trail on who acknowledged the alarm.

FFU status is cheapest to add while the SCADA point list is still being written at design stage. Added after OQ, it becomes a change to a qualified system.

How does your team find out that a single FFU has stopped?

Industries

Related

More on this subject

Individual logins make records attributable, but user lists drift as people move and leave. A periodic access review exports users and roles from the system, checks them against HR's leavers and movers, justifies every admin or generic account and is signed with its corrections, the record an inspector will ask for.

InsightRead