After an office converts to VRF or multi-zone ductless, comfort depends on controls as much as equipment. Decide who may change setpoints, build occupancy schedules, use a central controller for oversight, integrate with the building automation system only through a defined interface, and settle cost allocation before tenants ask. Most post-conversion complaints trace to default settings, unclear authority or zones fighting each other.
- Every indoor unit is its own zone. That is the benefit and the burden: decisions about who controls each one must be made on purpose.
- Set the control hierarchy first: local thermostat, tenant-level schedule, central controller limits, then BAS supervision. Conflicts between levels create most complaints.
- Occupancy-driven operation saves energy only when schedules match how the space is actually used. Review them after the first month.
- Cost allocation is a policy decision, and the control system only supplies data. Decide the method before the first bill.
- Heating and cooling conflicts between adjacent zones are the classic VRF pitfall. Mode settings and zone grouping prevent them.
What changes when every room has its own zone
A rooftop system typically gave an office a handful of zones, each with a thermostat that few people had access to. A VRF or multi-zone conversion often gives the same space dozens of indoor units, each with its own controller or wireless remote. The comfort potential is real. So is the opportunity for confusion: tenants who used to complain about one cold corner now have a remote that seems to promise they can fix it.
The first control decision, then, is not technical. It is who gets to decide what, and where the limits are. The physical design of the system is covered in replacing office rooftop units with multi-zone VRF, and the architectural choices between VRF and ductless are in VRF vs multi-zone ductless vs rooftop units for offices. This page picks up after the equipment is installed.
The four control layers, and who owns each
| Layer | What it does | Typically owned by | Usual limits |
|---|---|---|---|
| Local thermostat or remote | Lets an occupant adjust the nearest indoor unit | Tenant | Setpoint range locked to a comfort band; mode and fan speed may be restricted |
| Tenant or suite controller | Groups units into a suite, sets schedules, locks local controls | Tenant, with property manager rules | Schedules must stay inside building operating hours |
| Central controller | Shows every indoor unit, outdoor unit and fault in one place; applies schedules and limits | Property or facility manager | Sets the outer boundaries that tenants cannot override |
| Building automation system | Supervises the whole building and ties HVAC to other systems | Building engineer or controls contractor | Exchanges a defined set of points; does not replace the manufacturer's own control logic |
Each layer should be able to narrow what the layer below it can do, never widen it. If a tenant can set a suite to 60 degrees while the central controller is trying to keep the building efficient, the controller is a decoration. If the BAS issues commands that the VRF controller keeps overriding, the integration was designed wrong.
Lock-outs that prevent the usual complaints
- Set a narrow setpoint range at the local level, wide enough for personal comfort but not for extremes.
- Prevent occupants from changing operating mode (cool, heat, auto) where the system cannot support mixed modes on one circuit. This is the single most important lock on heat-pump VRF.
- Disable or hide functions that tenants do not need, such as fan-only modes that break ventilation logic.
- Document the defaults so the next technician knows what was intended.
Schedules and occupancy-driven operation
Schedules are the cheapest efficiency tool in a converted office, and also the most neglected. A schedule that matches the building's real use keeps units off when no one is there and ready when people arrive. A schedule copied from the old rooftop thermostat, or never set at all, defeats the purpose of having granular zones.
Build schedules from how the space is used, not from the lease hours on paper. Conference rooms, break rooms, training rooms and open offices all follow different patterns. Warm-up and cool-down time depends on the zone and the weather, and an early-start setting that works in September may be wrong in January.
- Occupied, setback and off. Use all three. Setback keeps the space within a safe range without conditioning it to comfort.
- Holiday and special-day calendars. Make sure someone owns the calendar. The Monday after a long weekend is the day owners find out nobody did.
- Occupancy sensing where it fits. Sensors or door and badge-reader signals can switch zones to setback in rooms that are used intermittently. They are useful in meeting rooms and less useful in open areas where one person leaves and others remain.
- Override timers. A tenant who stays late can press a button and get a limited extension, which then expires. Open-ended overrides stay on all weekend.
- Review after a month. Check the central controller's operating history against what you intended. Adjust once the building has shown its real behavior.
For other building-level schedule and sensor verification work, the building controls and automation service and the building automation controls upgrade scope describe what a controls scope usually includes.
Integrating with a building automation system
Many office buildings already have a BAS controlling lighting, ventilation, central plant or the remaining rooftop units. Linking the VRF system to it is possible through a gateway or interface supplied for the purpose. Treat it as a design item, not an add-on at the end.
- Decide what the BAS needs. Typical goals are viewing status and alarms, applying building-wide schedules, and coordinating ventilation. Resist the urge to expose every point if no one will use it.
- Choose the interface. Manufacturers offer gateways to common building protocols. Confirm compatibility with the BAS vendor before ordering.
- Define who commands what. If the BAS sets the schedule, the central controller must not set a competing one. One system leads, the other follows.
- Map and name points consistently. Indoor units named by suite and room save hours later. Naming indoor unit 47 is a gift to no one.
- Test the link at commissioning. Verify that a command from the BAS changes a unit, and that a fault on a unit appears on the BAS.
- Name the controls responsibility. Davinci performs controls work as part of its own crew's scope. Where the BAS is a third-party platform, the scope should state who programs each side, and the owner or GC should confirm the responsible party.
Contractor will install and configure the central controller and any manufacturer-supplied gateway, name indoor units according to the Owner's room and suite schedule, and verify communication of agreed points with the Owner's building automation system. Programming of the building automation system itself is by the party identified in the project documents.
Cost allocation concepts for multi-tenant buildings
A converted office has many indoor units but usually one outdoor system serving several tenants, which raises the question: how is the energy shared? The control system will supply data, but the method is a policy decision made with the lease in hand.
- Separate outdoor systems per tenant or floor. If each tenant has their own outdoor unit and meter, allocation is simple. Plan this during design if leases require it.
- Runtime or load-based allocation. Some central controllers and add-on devices estimate each tenant's share using runtime, capacity or load data. The result is an estimate, not a utility-grade meter, and leases should say so.
- Submetering electrical feeds. The most defensible method for leases that require it, but it is an electrical scope and must be designed with that in mind.
- Flat allocation by area. Simple and often adequate when tenants are similar. It gives no incentive to conserve.
Whichever you choose, write it down before tenants start asking. Property managers and their counsel decide how it fits the lease; the contractor's job is to confirm what the equipment and controller can and cannot measure.
Common pitfalls we see in converted offices
These are the issues that show up in the first months after a conversion. Each is preventable with a few settings or one conversation.
| Symptom | Likely cause | What to check |
|---|---|---|
| One side of the floor is heating while the other cools | Mixed-mode requests on a system that cannot do both, or auto-changeover fighting itself | Mode lock settings, zone grouping and the system type (heat pump vs heat recovery) |
| Tenant says the thermostat does nothing | Local controls locked, or the unit is following a schedule or the central controller's limit | Lock settings, schedule status and any override timer |
| Spaces are cold on Monday morning | Weekend schedule or setback too deep, or a holiday not entered | Calendar, setback temperature and early-start logic |
| Same alarm on one unit again and again | Communication wiring issue, address conflict or a unit operating outside its range | Controller log, wiring and addressing; root-cause before resetting |
| Rooms stuffy even though the unit runs | Ventilation design not tied to occupancy, or filter or fan speed restricted | Outdoor air path, fan settings and filters |
| Energy use higher than expected | Schedules not set, overrides left on, or setpoints widened without limits | Central controller history and tenant overrides |
When controls problems persist, a second opinion diagnostic looks at the whole chain from thermostat to refrigerant circuit instead of resetting faults one at a time. Ongoing care of the system, including controller communication checks, is the focus of maintaining VRF and multi-zone systems in offices. The commercial HVAC diagnostics guide explains the root-cause approach that controls issues usually need.