Connecting HVAC and Building Automation Controls to the Network

The mechanical contractor finishes the new rooftop units and says the controls "just need an internet connection." A week later a technician is on the roof with a laptop, asking where he can plug in, and the IT provider has never heard of the project. The building is now partly controlled by equipment nobody on the network side knew about.

Building automation, often shortened to BAS, covers thermostats, rooftop units, boilers, chillers, air handlers and sometimes lighting, all managed by controllers that talk to each other and to a front-end computer. These are real network devices. They deserve the same care as anything else plugged into your switches.

What the controllers need

Building automation equipment is often installed by a mechanical or controls contractor who does not think in terms of your network. A few practical needs come up on nearly every job.

Wired network ports. Controllers usually connect by Ethernet cable. Some use older serial wiring between devices, with a gateway that joins them to the network. Ask how many ports are needed and where.

Addresses. Controllers commonly need fixed network addresses. They should be assigned and written down, not picked at random by the contractor.

A separate network segment. Control equipment should live on its own segment (a VLAN), away from staff computers and guest Wi-Fi.

Standard communication. Many systems use open protocols such as BACnet or Modbus. Your IT provider does not need to understand the control logic, but should know which kinds of traffic must pass.

Time synchronization. Schedules for heating and cooling depend on a correct clock, so confirm how the controller gets the time.

Power. The network switch, and anything else the controller depends on, needs stable power. A controller that reboots after a short outage may reset to default behavior.

Remote access is where problems start

Contractors often want to log in remotely to adjust settings or diagnose a fault. That is useful, but it is also a common way for outsiders to reach a building network. Avoid these practices:

Opening ports on the firewall so the controller can be reached directly from the internet.

Leaving the default username and password on a controller.

Giving the contractor a permanent connection to the main network.

Placing a cellular modem on the system without telling IT, which creates a path around the firewall.

Better practice is to route vendor access through a managed secure connection, with named accounts, and to turn off access when work is done or limit it to scheduled windows.

How to coordinate the contractor and IT

The cheapest fix is a conversation before the work starts.

Introduce them early. Give the contractor your IT provider's contact and ask for a short call before installation.

Request a network requirements sheet. The contractor should list the ports, addresses, protocols and remote access needs for each device.

Assign a network segment and addresses before anything is plugged in.

Decide who owns what. Who maintains the switch, who updates controller software and who responds when the building is too hot at 2 a.m.?

Collect documentation. Get a diagram, a device list with addresses and the login credentials, and keep them with your other building records.

Test failure. Ask what the equipment does when the network goes down. Most systems keep running their last schedule, but confirm that for yours.

Why it matters in a care building

Temperature control in a care building is a comfort and a safety issue. A resident room that overheats during a summer night, or a medication room that drifts out of range, can become a clinical problem. Equipment that is secure, documented and monitored is far less likely to surprise you. Also keep in mind that some systems affect smoke control or other life-safety functions, so those connections require approval by qualified professionals and the authority having jurisdiction.

Keep the contractor's closeout package, too. When the controls vendor changes or a technician leaves, the diagram and address list are what keep a two-hour troubleshooting call from becoming a two-day one. Store a copy where the administrator and your IT provider can both find it, not only on the contractor's laptop.

Finally, treat later changes the same way. Adding a new rooftop unit or a few extra thermostats should trigger the same short call with IT, so the address list and network segment stay accurate and nobody is surprised by a device that appeared on its own.

How we can help

UnityCare IT works with your mechanical contractor to put building controls on a properly separated, documented network segment, with remote access that is managed instead of left open. We support care buildings across Oklahoma, Texas and Kansas, and can review a controls proposal before you sign it.

Related service

Wi-Fi, switching, firewalls and internet that hold up across a whole facility.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support