Medical Gas Alarm Modbus: Integrating Alarms with the BMS

What the local alarm does and what the BMS adds

Local medical gas alarm panels are the safety-critical element. They give audible and visual warnings to clinical staff when pressure, flow or supply departs from normal. The BMS link is an additional, operational layer for engineers: it records events, notifies the maintenance team and allows trend analysis.

The standard you design to defines which alarms are clinical and which are operational, and which must remain independent of the BMS. Never rely on the BMS as the only means of alarm. See medical gas alarm panel requirements for the principles.

Protocols: Modbus RTU, Modbus TCP/IP and BACnet

Modbus is a simple master-slave protocol. Modbus RTU runs over a serial link such as RS-485, while Modbus TCP/IP runs over Ethernet and suits modern networks. BACnet is common in building automation and offers object-based data models. Many BMS platforms support several, and gateways can convert between them.

Do not assume a given alarm monitor supports a given protocol. Ask the manufacturer which interfaces are available on the model, which register map or object list is provided and what the update rate is. For example, the MZU II monitoring unit can send status information to external devices; confirm the exact interface and protocol options for your project with the manufacturer.

• Physical layer: RS-485, Ethernet or dry contacts
• Protocol and addressing scheme
• Register map or object list in writing
• Update rate and timeout behaviour

Signals worth sending to the BMS

A useful signal list includes pressure of each gas, high and low pressure alarms, source status (duty, standby, reserve in use), plant faults such as compressor or dryer fault, valve status where available, and communication health of the alarm monitor. Devices such as the MZU II can display one to twelve gases and measure flow and consumption, which can feed useful consumption trends.

Keep naming consistent. Each point should carry the gas, location, severity and a description that an engineer at night can understand. Agree alarm priorities with the clinical engineering and facilities teams before programming.

Where consumption is trended, define a baseline first. Sudden changes in flow at night often reveal leaks, and rising consumption on one ward can signal a change in patient load that the plant must be ready for.

Remote monitoring, alarm logs and cybersecurity

Remote monitoring is only as good as the response process. Define who receives alarms, how escalation works and how acknowledgement is recorded. Keep logs of alarm events with time stamps for audit and for tracing recurring faults. Time synchronisation between systems avoids confusing reports.

Place alarm monitors on a controlled network segment. Use access control, avoid exposing devices directly to the internet and involve the IT team early. Consider what happens if the network fails: local alarms must continue unaffected.

Decide who may silence or acknowledge alarms remotely, and make sure the remote acknowledgement never cancels the local audible warning in the clinical area.

Commissioning and maintenance of the integration

Test every point end to end: simulate or create the condition, confirm the local alarm, confirm the BMS point and the notification, and record results. Repeat after software or network changes. Include the interface in the maintenance plan; see medical gas pipeline maintenance.

Beckfinity can help engineers define the interface requirements with MZ Liberec for your project; contact our specialists with your BMS protocol and point list.