[November, 2026]

A meeting room is full for an hour, then empty. A perimeter office heats up in the afternoon sun while an interior room still needs cooling. Someone adjusts the wall thermostat, but the building management system changes the setpoint again five minutes later. These are not unusual faults in office HVAC projects. They are often signs that the responsibilities of local room control and central supervision were never defined clearly enough.

Who This Article Is For

This guide is for HVAC contractors, MEP designers, building automation integrators, facility teams and distributors involved in office buildings with fan coil units (FCUs), room thermostats and a building management system (BMS). It focuses on practical control decisions rather than a general explanation of BMS connectivity.

Quick Answer

In most office projects, the room controller should handle the immediate equipment sequence: measure room temperature, regulate the FCU fan and valve, and respond to permitted occupant adjustments. The BMS should supervise the wider building strategy: operating schedules, allowable setpoint ranges, occupancy modes, monitoring and alarms, subject to the actual system design.

The critical detail is authority. A BMS connection does not by itself define whether a local setpoint is temporary, whether a central command overrides it, or who decides heating/cooling mode. Those rules must be agreed, implemented and tested before handover.

1. The Problem Is Not Connectivity. It Is Control Ownership.

A thermostat can communicate successfully over Modbus while still behaving in a way occupants and operators dislike. A central schedule may place a floor in setback mode, yet a user may expect a wall adjustment to restore comfort immediately. Or the BMS may write a new setpoint every polling cycle, effectively cancelling local changes.

The interface is working in both cases. What is missing is a control agreement: which values can be written, by whom, under which conditions and for how long? Resolve that question before configuring registers or graphic pages.

2. What Should Stay at Room Level?

For a typical FCU-controlled office zone, local control is best placed close to the equipment. The room thermostat or controller can read its room sensor, compare temperature with the active setpoint and operate the configured fan and valve outputs. This allows the immediate control loop to continue without depending on a constant round trip to the BMS.

Local functions may also include fan-speed selection, an occupancy or window input, and an approved temperature adjustment range. The exact functions depend on the controller model and project wiring. An AC three-speed fan is not controlled the same way as an EC fan with a 0–10 V speed input; neither should be assumed from the faceplate.

3. What Belongs to the BMS?

The BMS is useful for decisions that apply across rooms, floors or the whole building. These may include occupied/unoccupied schedules, supervisory setpoints, operator permissions, common-area policies, monitoring and fault reporting. It can also coordinate room operation with central plant availability when the system architecture supports that relationship.

Supervision should not mean sending conflicting commands every few seconds. The BMS should write only the parameters it is responsible for and should have a documented policy for what happens after a network interruption or operator override.

4. Agree the Control Boundary Before Commissioning

This is an example responsibility matrix, not a universal rule. A project may assign some functions differently, but every row should have one unambiguous owner and an agreed fallback.

5. The Setpoint Conflict That Creates Complaints

Consider a meeting room with a 22 °C central occupied setpoint. An occupant changes the local setpoint to 23 °C. If the BMS writes 22 °C repeatedly, the display may snap back, making the thermostat appear defective. If the local adjustment overrides the building schedule indefinitely, the facility team may lose the intended energy policy.

There are several workable approaches: allow a temporary local offset that expires after a defined period; permit a bounded local setpoint until the next schedule change; or disable local changes in rooms that require centrally fixed settings. The right choice depends on the space and operating policy. What matters is that the behavior is visible to the user and explicitly tested.

A setpoint range such as 20–24 °C can be useful as a design illustration, but the actual limits should be established by the project team rather than copied as a default recommendation.

6. Who Decides Heating or Cooling?

In a two-pipe FCU system, the available water temperature may be determined centrally. A local thermostat cannot create cooling when the shared circuit is supplying hot water. The room controller may need a changeover signal or supervisory mode command to select the appropriate control sequence.

In a four-pipe system, separate heating and cooling valves may be available, but interlocks and deadbands still matter. The controller should not be allowed to call heating and cooling against each other because of conflicting local and BMS commands.

Before specifying the thermostat, confirm whether changeover comes from the plant, a BMS point, a pipe sensor or a defined local input. Also confirm what happens when that signal is absent or invalid. A communication protocol cannot fix an unresolved hydraulic or sequence-of-operation decision.

7. One Office Floor Does Not Mean One Control Policy

Different spaces create different demands. Open-plan areas often benefit from consistent limits and coordinated scheduling. Meeting rooms may need fast response to occupancy changes and a temporary comfort adjustment. Small cellular offices may allow a little more occupant flexibility. Circulation and support spaces may require limited or no user adjustment.

Do not divide one hydraulically inseparable zone into multiple apparent app or BMS zones. The physical equipment and sensor location must support the promised level of control.

8. Select the Room Controller for the Actual FCU

The term “BMS-compatible thermostat” is not enough for a product specification. Identify whether the FCU uses a three-speed AC fan or a modulating EC fan; whether valves are On/Off or 0–10 V; whether the installation is two-pipe or four-pipe; and which supply voltage and terminal arrangement are required.

Check any key-card, window-contact or external sensor requirements as well. A dry-contact output should not be confused with a powered relay output, and a 0–10 V signal should not be connected to equipment expecting a switched mains supply. Verify every interface against the approved equipment schedule and wiring diagrams.

For projects with different FCU types across floors, a configurable controller platform may simplify the user interface and spare-parts strategy, provided each hardware version genuinely supports its assigned outputs.

9. Modbus Integration Needs More Than an Address

For Modbus RTU projects, confirm the physical RS-485 arrangement, baud rate, parity, device addressing and register map. More importantly, classify each point as read-only, writable, or writable only under specified conditions. Record units, scaling and enumerated values for modes and fan speeds.

A BMS graphic showing room temperature is not proof that central setpoint control is correctly implemented. Test the write path, priority behavior, invalid values, communication recovery and any persistence after power failure. The same point name can mean different things across controller families, so use the actual manufacturer map rather than an assumed generic list.

10. Define the Failure Modes Before the Building Is Occupied

An office should not become uncontrollable because the BMS server is unavailable. For each room type, decide whether local temperature regulation continues during a network outage, what setpoint and mode remain active, and how a recovered connection resumes supervision. These behaviors must be supported by the selected controller and explicitly configured.

Also test sensor failure, window-contact operation where installed, and power restoration. For some systems, the safest response may be to disable an output; for others, a defined local operating state may be appropriate. Avoid universal fallback claims without reference to the equipment and project safety requirements.

11. Commission a Representative Room Before Replicating It

A pilot room is worth more than a stack of successful device-discovery screenshots. Select a representative room for each FCU/output type, then run a short test script with the contractor and integrator present.

· Verify temperature sensing and sensor placement, including any external sensor.

· Confirm fan and valve outputs against the actual FCU wiring and two-/four-pipe sequence.

· Change the setpoint locally, then observe the BMS display and write-back behavior.

· Apply occupied and unoccupied modes; confirm which settings are retained.

· Test heating/cooling changeover under the available plant conditions.

· Disconnect the BMS communication link and verify the agreed local fallback.

· Restore communication and confirm the recovery rule rather than assuming it.

· Record device address, room name, firmware/configuration version and test results.

Only after the pilot passes should the configuration be replicated. Rooms with different equipment or authority rules need their own tested template.

12. Handover Is Part of the Control Design

Facility staff need a concise explanation of what they can change centrally, what occupants can change locally and what each alarm means. Occupants need to know whether a local adjustment is temporary and why a heating/cooling request may be unavailable during seasonal changeover.

Keep the as-built room schedule, Modbus point list, wiring diagrams, configuration backups and override rules together. Otherwise the next service contractor may spend hours rediscovering decisions that were made during commissioning.

Pre-Order and Commissioning Checklist

· List every FCU type and its fan, valve and pipe configuration.

· Assign one temperature sensor and one controller to each genuine control zone.

· Identify the source and priority of heating/cooling changeover.

· Agree the local setpoint range, override duration and reset event.

· Define occupied/unoccupied and window-contact behavior where applicable.

· Confirm BMS protocol, physical network, point list and write permissions.

· Specify offline and power-restoration behavior based on the chosen model.

· Test a representative room for each control sequence before bulk rollout.

· Provide clear room labels, configuration records and handover instructions.

Conclusion: Good Office Control Makes Responsibilities Invisible

Occupants should be able to adjust comfort without fighting the BMS. Facility teams should be able to supervise the building without micromanaging every fan and valve. That balance comes from clear control ownership, equipment-compatible outputs and tested override rules — not simply from adding Modbus to a thermostat.

When the room controller and BMS are designed as complementary layers, the system is easier to operate, commission and maintain. When their responsibilities overlap without a rule, the resulting complaints can look like product failures even when the devices themselves are working correctly.

Discuss Your Office HVAC Control Requirements with CosyClimate

CosyClimate offers FCU room-control options for different AC/EC fan and valve applications, including selected models with WiFi and Modbus connectivity. The available outputs, inputs and communication functions depend on the exact model and configuration.

For office contractors, system integrators and HVAC distributors, share the FCU schedule, two-/four-pipe arrangement, fan and valve interfaces, required BMS points and proposed local/BMS authority rules. We can review which control configurations are suitable before specification and commissioning.

Contact CosyClimate  to discuss your next HVAC control project.