Commercial VRF Controls: Commissioning and Handover Checklist

Define the building's control responsibilities

This checklist is for a commercial project that has identified a candidate controller or gateway. Its purpose is to agree how the installed controls will be tested and handed over, not to repeat product selection. If the hardware route is still undecided, start with how to choose a VRF thermostat or gateway.

Record who can change the room setpoint, operating mode and schedule: occupants, reception, facilities staff or a BMS operator. Decide which requests should take priority and ask the system supplier to confirm how the chosen equipment handles conflicting commands. Do not assume that a connected app overrides the original controller, or that a BMS can restrict local controls without a supported function.

Create a room and zone schedule

Keep one project record for each controlled room or zone. Include its location, indoor-unit identifier, existing controller, selected device/configuration, intended control owner and acceptance-test reference. Where several indoor units share a control group, document the grouping and have it confirmed before assuming individual-room control.

• Hotel rooms: agree guest adjustment permissions, staff access and the response after a room becomes vacant. Occupancy or key-card integration must be separately confirmed, not assumed from WiFi connectivity.
• Offices: agree working-hour schedules, after-hours overrides and which team maintains the schedule.
• Shared spaces: identify the responsible operator and a process for conflicting comfort requests.

Use a representative pilot, not just one successful pairing

Include each materially different equipment/interface/configuration group in the pilot plan. A successful app connection in one room does not validate another indoor-unit series, firmware profile or control architecture. Agree expected results and a pass/fail record before testing.

1. Basic operation: test supported power, modes, setpoints and fan commands and compare the displayed state with actual equipment response.
2. Multiple control points: test commands from the room controller and any app or BMS. Record what happens when requests conflict.
3. Schedules: test the agreed timing, time-zone settings where applicable, and manual override behavior. Establish which device or service owns each schedule.
4. Recovery: with site approval and qualified personnel, test the agreed response to power interruption or loss of the relevant communication service. Record which controls remain available and how reconnection occurs; do not assume offline behavior.
5. Faults and feedback: check only the status and fault indications documented for the ordered configuration, and record unsupported points explicitly.

For Modbus projects, approve a point list

Obtain the register map and serial settings for the supplied configuration. For every required BMS point, record its register, read/write access, value format, units or scaling, valid range and the expected equipment response. Agree addressing, polling and wiring requirements with the integration team rather than reusing settings from a different gateway.

Compare commanded values with returned status during commissioning. A successful RS485 connection alone is not proof that the BMS interprets every point correctly. Treat any required control lockout, alarm reporting or centralized grouping as an acceptance item needing explicit support.

Define acceptance and handover deliverables

• An as-installed room/zone schedule and device/configuration inventory.
• Approved wiring drawings, addressing records and configuration versions.
• Completed pilot and rollout test records, with unresolved limitations identified.
• For Modbus, the final point list, register-map version and integration settings.
• A named owner for app or gateway accounts, access transfer and maintenance; do not put passwords in public project documents.
• Operator instructions covering routine changes, fault escalation and recovery procedures.

Agree the scope of final acceptance with the project team. This is a planning checklist, not a certification standard or a promise that every listed feature is supplied. Any claimed energy saving requires a separate baseline and measurement method; connectivity alone does not establish a saving.

Configuration-specific references

Use the documentation for the equipment actually ordered: S20 wall thermostat, AcmeLink ME configurations, AcmeLink DK P1/P2 route or AcmeLink_GW Modbus converter. Confirm project-specific requirements with the supplier and integration team before rollout.

Commissioning questions