Guestroom Control Integration with BMS and PMS: Scope Guide

Guestroom control connects to two systems with different jobs: the property management system (PMS) tells the room who is staying and when, and the building management system (BMS) owns plant, chillers and the building-level view. Define each data point, its owner and its fallback before wiring anything.

This guide is written by Singapore-based AV and IPTV integrator Prestige Solutions for hotel IT managers, facility managers and system integrators who plan smart room control projects. It lists the data points that usually cross each interface, who should own them, what each side does when the link fails, and the tests to run at handover. Protocol support differs by controller and BMS, so every item below should be confirmed against the datasheets and the interface documents of the actual products as of 2026.

What does the PMS tell the room controller?

The PMS provides guest state, not device commands. The useful signals are room status (vacant, reserved, occupied), check-in and check-out events, do-not-disturb and make-up-room flags, and in some projects the departure time. The room controller turns these into a mode.

Keep the PMS link one-directional in the first phase: the PMS informs the room, and the room does not write back to guest records. Writing back, for example to report a minibar or door event, belongs in a separate scope with its own test plan.

What does the BMS exchange with the room controller?

The BMS and the room controller exchange setpoints, status and alarms. The room controller keeps local control of the room, and the BMS limits and monitors it. A hotel normally does not want the BMS to drive each room's valve or damper directly.

Common building protocols are BACnet/IP (UDP port 47808 by default), Modbus TCP (port 502) and KNX over IP (port 3671); a gateway may be needed when the room controller speaks a different one. Ask the BMS contractor which object types and how many rooms the BMS licence and controllers can add, because a 400-room hotel with 10 points per room is 4,000 points before spares.

Where should the interface sit in the network?

Put the integration at the head end, through a server or gateway that talks to the PMS and BMS on one side and the guestroom controllers on a separate VLAN on the other. Do not give room devices a route to the PMS network.

• Guestroom control VLAN separate from guest Wi-Fi, IPTV and the PMS database network.
• Firewall rules that allow only the named gateway and ports, in both directions.
• No inbound access to PMS data from the room devices.
• Time source (NTP) shared by the gateway, controllers and BMS so that logs line up.

The IPTV side often has its own PMS interface for guest names and billing, as in our IPTV and PMS guest data flow reference. Agree which system holds the master copy of room status so the two interfaces do not disagree.

What happens when an interface fails?

Each room must run correctly with both links down. Design the fallback first, because that is the state the rooms will be in during every maintenance window.

Network loss inside the guestroom is a related but separate failure, and is described in our network loss failure mode reference.

Which tests prove the integration at handover?

The integration is accepted when each data point has been exercised end to end in both directions on a sample of rooms, and the fallback has been triggered deliberately. A passed demonstration on one room is not a result for a floor.

1. Send a check-in event from the PMS test environment for three rooms and confirm the mode change within the agreed time.
2. Repeat for check-out, reserved arrival and out-of-order.
3. Change a BMS setpoint limit and confirm the room accepts and holds it.
4. Trigger a fan-coil fault and confirm the BMS alarm names the room.
5. Run the fallback tests in the table above.
6. Record point lists, object IDs, ports and firewall rules in the handover pack.

Combine this with the physical checks in the room-by-room commissioning checklist, so the integration test and device commissioning use the same room list.

How should the rollout be phased?

Phase the integration by interface and by floor, not all at once. A typical order is the room controllers alone, then the BMS monitoring points, then BMS setpoint limits, and the PMS link last, because the PMS interface usually depends on the vendor's schedule and licence.

Moving one phase at a time also means a fault points to one interface, which is faster to isolate than a full launch where all three systems changed on the same night. Keep a rollback step for each phase, so the previous state can be restored within the maintenance window.

What should the scope document state?

State the data points, the owner of each system, the test environment and the support boundary. Disputes between the PMS vendor, BMS contractor and controller supplier almost always come from an unwritten point.

• Point list with direction, data type and update time for each signal.
• Name of the party responsible for the PMS interface licence and for the BMS programming.
• A PMS test environment or simulator available before go-live.
• Who is on call during the first week of live operation.

FAQ

Can the BMS control each room without a room controller?

It can on paper, but a BMS-only design depends on the network for every guest action, and guest scenes such as lighting and curtain control are slower to respond. Most hotels keep local room control and use the BMS for limits, reporting and alarms.

Do all PMS products offer an interface for room control?

No. Interface options differ by PMS vendor and version, and some charge a licence or integration fee. Ask the PMS vendor early what is offered, in what format, and what a test environment costs, since those answers can set the project schedule.

How should energy savings be measured after go-live?

Compare room energy or cooling use by occupancy status against a baseline period, and check guest comfort complaints for the same rooms. A saving with more complaints is not a saving, so review the two together before changing setpoint limits.

Visit Prestige Solutions for the wider AV and IPTV service range.

Recommended next step

Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.