VRF Branch Controller Addressing and Commissioning Inspection

It covers the branch controller box identification, refrigerant line labeling, indoor unit addressing, communication checks, pre-energization safety, and final sign-off. The template is built for commissioning and startup verification, not for routine maintenance or full HVAC performance testing. It helps document whether the installed VRF network matches the design intent before turnover.

Use it during VRF commissioning, after branch controller installation, after indoor unit addressing, and before final energization or owner handoff. It is also useful after control changes, replacement of indoor units, or troubleshooting communication faults. If the system is already in steady-state operation, a maintenance checklist may be more appropriate than a commissioning inspection.

A qualified commissioning technician, HVAC controls contractor, or service supervisor should complete it, with a competent person verifying safety conditions where required. The inspector should be able to confirm addressing logic, controller communication, and installation defects against the drawings and equipment schedule. If local rules require it, the AHJ or project commissioning authority may also review the record.

Yes, it includes pre-energization checks that support safe work practices, including lockout-tagout where required and secured access panels before startup. It is aligned with general OSHA expectations for safe commissioning work and with standard electrical and mechanical safety practices. It does not replace a site-specific energy control procedure, permit process, or qualified-person verification.

Common findings include duplicate indoor unit addresses, a branch controller label that does not match the installed location, and communication alarms caused by wiring or network continuity issues. Inspectors also often find unsecured covers, missing line identification, or unresolved refrigerant leak concerns before startup. Catching these items here prevents commissioning delays and avoids handoff with hidden defects.

Yes, it is meant to be adapted to the specific controller logic, addressing method, and naming conventions used by the manufacturer. You can add fields for manufacturer-specific tools, software screens, or controller menus without changing the core inspection flow. Keep the observable checks intact so the record still proves what was verified on site.

It is typically performed once during commissioning for each VRF branch controller and repeated whenever the system is readdressed, expanded, or repaired in a way that affects controls. For phased projects, each new area or branch controller should be inspected before it is placed into service. It is not usually a daily or monthly inspection unless the site has frequent control changes.

An ad-hoc startup checklist often misses traceability, such as which indoor unit was assigned which address and whether the controller matched the drawings. This template creates a structured record of identification, addressing, communication, and safety checks in the order a technician actually commissions the system. That makes it easier to resolve deficiencies, support closeout, and defend the handoff record later.

Attach the equipment schedule, control drawings, addressing list, startup notes, and any photos of deficiencies or corrected labels. If the site uses commissioning software or BAS records, include those references as well. Keeping the reference documents on site makes it easier to verify conflicts and confirm that the final configuration matches the design.