Use case

Cleanroom conditions, live in every system

Remote particle counters, differential pressure transmitters and temperature and humidity probes in pharma, food and semiconductor cleanrooms publish over MQTT. Your validated EMS records and alarms; QA, production and facilities see the same values live.

No card required

Example message

PUBLISH ems/plant-2/fill-finish/room-b204/pc-03/particles

{"ts":"2026-10-22T09:12:00Z","grade":"B","state":"in_operation","um0_5_m3":1180,"um5_0_m3":0,"flow_lpm":28.3,"sample_s":60}

QoS 1 · TLS 8883 · PUBACK

The problem

Cleanroom data locked in one console

Environmental monitoring often runs as a closed system: counters and transmitters wired to vendor hardware, data visible only on the EMS console. Production wants live room status at the line, facilities needs the same pressures as the BMS, and adding a room or a new counter brand becomes a vendor project. The EMS has to stay independent and validated, so every new consumer turns into a long discussion.

How it works

  1. 1

    Sensors in the room

    Remote particle counters (0.5 and 5.0 µm), differential pressure transmitters, temperature/humidity probes and airflow sensors report over Modbus TCP, 4–20 mA or their own network interface.

  2. 2

    Gateway publishes

    An edge gateway or PLC turns readings into topics per site, area, room and sensor — with the room’s grade and operating state — and publishes them over TLS with QoS 1.

  3. 3

    Your EMS subscribes

    Your validated EMS subscribes and stays the system of record: storage, audit trail, alarm acknowledgement and reports remain there. Dashboards and the MES subscribe to the same topics, read-only.

  4. 4

    Early heads-up

    Alongside the EMS, ConnectMQ threshold rules can give facilities an informal heads-up on a falling pressure cascade or rising humidity. Formal alarms, delays and acknowledgement stay in your EMS.

ConnectMQ

What it needs from the broker

Readings delivered, not dropped

QoS 1 from gateway to broker and on to the EMS, persistent sessions so readings are queued while a subscriber restarts, and a retained status for every sensor.

Read-only for most, write for few

Per-client credentials and topic ACLs: each gateway publishes only its own rooms, dashboards and MES only read, and no one but the gateway writes to a sensor topic. TLS on every connection.

Sensor loss is visible

Last Will marks a gateway or counter offline as soon as its connection drops, so a silent sensor is never mistaken for a clean room.

A structure that matches the facility

The ISA-95 workspace maps site, area, room and sensor, and the 3D Digital Twin can show live values per room on a layout of the facility.

What you get

  • Live room status for QA, production and facilities from one source
  • The EMS stays the system of record; others subscribe read-only
  • New rooms and sensor brands added by topic, not by vendor project
  • Offline sensors flagged instead of silently missing data
Example topics
ems/plant-2/fill-finish/room-b204/pc-03/particles
ems/plant-2/fill-finish/room-b204/dp-01/pressure
ems/plant-2/fill-finish/room-b204/th-02/climate
ems/plant-2/fill-finish/room-b204/pc-03/status   (retained)

Industries that run this use case

Frequently asked questions

Can MQTT be used for GMP environmental monitoring?

MQTT can be the transport inside a monitoring solution you validate: sensors and gateways publish, and your EMS subscribes and handles records, audit trail and alarms. ConnectMQ provides the broker, TLS, per-client permissions and QoS delivery; validating the overall system, including data integrity, is up to you.

How do I connect cleanroom particle counters to an EMS?

Most remote particle counters offer Modbus TCP or a 4–20 mA output. An edge gateway or PLC reads them, adds sample volume and room context, and publishes to ConnectMQ; your EMS — or a connector in front of it — subscribes to the room topics.

Should cleanroom monitoring be separate from the BMS?

Many sites keep the EMS independent of the BMS that controls HVAC, so monitoring isn’t affected by control changes. MQTT respects that split: the EMS and the BMS each subscribe with their own credentials to the topics they need, and neither can write to the other’s data.

Build it on ConnectMQ

Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.