Building Automation Cabling and Controls Network Infrastructure

What a BAS looks like at the cabling layer#

Telelink Business Services is a licensed C-7 Low Voltage Systems Contractor, CSLB License #472017. The C-7 classification text expressly names instrumentation and temperature controls. This work sits inside the license rather than at its edge.

Strip the graphics and sequences off a building automation system and three layers of wire and network are left, plus the panels they land in.

• An IP backbone connecting supervisory controllers, the head end server or workstation, and any IP-native field controllers. Copper to the nearest telecom room, fiber between buildings.
• Controller trunks. Field controllers daisy chained on a shielded twisted pair bus, most often BACnet MS/TP, running panel to panel through mechanical rooms, ceilings and shafts.
• Device home runs. Space temperature, CO2 and humidity sensors, occupancy sensors, differential pressure switches, current sensors and actuator control wiring, each run back to its field controller or panel.
• Panels. Control panels in mechanical rooms and above ceilings, each needing a network drop, a pathway in, and terminations someone can trace two years from now.

That is the layer we install. What runs on it, the sequences, the graphics and the tuning, belongs to the controls integrator.

Protocols and what each one asks of the cable#

Protocol	Typical media	Topology	What the installation has to get right
BACnet MS/TP	Shielded twisted pair	Daisy chain	End-of-line termination, one shield ground, no T-taps
BACnet/IP	Cat6 or fiber	Star to a switch	VLAN, plus broadcast management across subnets
Modbus RTU	Shielded twisted pair	Daisy chain	Same bus rules, plus address and baud rate discipline
Modbus TCP	Cat6	Star to a switch	Another device on the automation VLAN
LonWorks	Twisted pair	Free topology or bus	Termination matched to the chosen topology

BACnet MS/TP is the workhorse at the field level. It is a token passing protocol on a two wire RS-485 bus: every device on the trunk shares one pair, one device transmits at a time, and the physical bus has to behave like a bus. It is unforgiving of topology mistakes in a way Ethernet is not.

BACnet/IP puts the same data model on Ethernet, and the wiring is ordinary structured cabling: one drop per controller, star to a switch, certified and labeled like any other link. Where the network spans more than one IP subnet, a BACnet broadcast management device has to be configured so broadcasts cross the boundary, a point the IT department and the integrator settle together.

Modbus RTU behaves like MS/TP electrically: same two wire bus, same termination rules, with addressing and baud rate per device. It shows up on meters, variable frequency drives, boilers and packaged equipment. Modbus TCP is its Ethernet version. LonWorks is still in service on older buildings and in some current specifications, on twisted pair in either free topology or a bus, and which one the design uses changes where the terminator goes.

For an estimator, the protocol determines the cable, the topology and the labor. A floor of BACnet/IP controllers is a cabling job that looks like a data floor. A floor of MS/TP unit controllers is a different job with a different crew rhythm, bid differently.

Daisy chain or home run: MS/TP topology rules#

An MS/TP trunk is a daisy chain and only a daisy chain. Cable enters a device, lands, and leaves for the next. No stars, no T-taps, no spur off a junction box because the run was easier that way.

Home run MS/TP devices jumpered together on a terminal strip turn each of those runs into a stub hanging off the bus. Stubs reflect signal, and the reflections show up as intermittent communication errors that pass a quiet walkthrough and start failing once the trunk is loaded, which is after the ceilings are closed.

The rules we hold on every trunk:

• One continuous chain with both physical ends identified on the drawing.
• End-of-line termination at both ends and nowhere else, at the value the controller manufacturer specifies.
• Device count and trunk length inside the manufacturer’s limits for the baud rate in use. Where the design exceeds them, a repeater goes in as a documented segment, not a field improvisation.
• Polarity consistent the whole way. Reversing two wires at one device is half a day of hunting.
• Every device labeled with the trunk name and its position on it, so the next technician can find the break instead of tracing the whole trunk.

Device home runs are the opposite: each sensor and each controlled device on its own cable back to its controller, point to point and simple, where the discipline is labeling, slack and pathway rather than topology.

Shielding, grounding, separation and cable ratings#

Controls cable lives in mechanical rooms next to the noisiest equipment in the building. Variable frequency drives and their motor leads radiate broadband noise, and an unshielded trunk alongside them collects it.

Shielding. Trunk cable is shielded twisted pair with a foil shield and drain wire. The shield works only when it is continuous and grounded at exactly one end, normally at the controller panel. Carry the drain through each device without landing it, cap it at the far end, and never ground both ends: two grounds create a loop that puts current on the shield and makes the noise worse.

Separation. Keep controls cable out of conduit shared with line voltage conductors and away from VFD output leads, and cross power at right angles where a crossing cannot be avoided. Where separation is not achievable, the answer is metallic conduit.

Cable ratings. Plenum rated cable in ceilings and spaces used as return air plenums, riser rated in vertical shafts, and the rating matched to every space the cable passes through, not just where it starts. Support on J-hooks at proper intervals: not draped on ceiling tile, not tied to sprinkler pipe, not laid on ductwork.

Gauge and cable selection follow the controller manufacturer’s requirement for the bus, and we submit actual part numbers for the controls manufacturer to confirm before a reel is bought. Line voltage power to control panels, transformers and mechanical equipment is electrical scope performed by a licensed C-10 contractor, and we show that handoff on the submittal.

Putting the BAS on the building IP network#

More of the automation system moves onto Ethernet every cycle. Supervisory controllers, IP-native field controllers, meters and rooftop unit controllers all want a drop, landing in the same telecom rooms as everything else.

Give the automation system its own VLAN. Building controllers are not general purpose computers. They ship with default credentials, sit on long firmware cycles, and are administered by a vendor who visits a few times a year. Their own segment means a compromised controller reaches other controllers and nothing else: not the file server, not the camera network, not the tenant Wi-Fi.

The rest is ordinary and still worth writing down. No automation device is exposed directly to the internet. Remote access for the integrator goes through the owner’s VPN or an IT-approved gateway, not a port forward opened during startup and forgotten. Default credentials are changed, recorded, and turned over to the owner at closeout along with the VLAN and addressing.

Physically it is the same cabling we install everywhere else: Cat6 or Cat6A drops certified and labeled like the data floor, fiber between buildings, switches with the PoE budget counted, and rooms built to the same standard. Our structured cabling and network room buildout scopes cover that side, and on a campus the automation backbone rides the same fiber as everything else.

Commissioning support and point to point checkout#

Point to point checkout is where the cabling either proves itself or costs the job time. For each point we confirm the field device matches the point list, the cable is landed on the correct terminal at both ends, polarity is right, the shield is grounded at one end only, and the value reads at the controller. Analog inputs are checked against a known condition, not accepted because a number appeared on a screen.

We keep the record as we go: a point list cross referenced to cable IDs, labels at both ends of every cable, and a marked-up drawing of trunk routing and device positions. When the commissioning agent starts functional testing and a damper does not move, the first question is whether it is a wiring problem or a programming problem, and a documented installation answers that in minutes.

Writing and verifying the sequence of operations is the integrator’s work and the commissioning agent’s. Confirming that an economizer behaves correctly across outside air conditions happens on their side of the point list. We prove the wire, support their testing, and correct anything on our side without pulling them back for a second visit.

Coordinating with mechanical and the controls integrator#

Building automation is the scope most likely to have a hole in it: it crosses four trades, and each assumes another trade bid the wire.

• Mechanical contractor: the equipment, the actuators, valves and dampers, and the wells and taps that sensors mount into.
• Electrical contractor (C-10): line voltage to control panels and transformers, motor power, and disconnects.
• Controls integrator: controllers, the sequence of operations, programming, graphics, the point list, and system commissioning.
• Telelink: pathway, trunk and device cabling, terminations, labeling, the IP backbone, switching and telecom rooms, and point to point checkout support.

Five questions settle it, and they belong in the first coordination meeting, in writing:

1. Who lands wire on the controller terminal strip, our technician or the integrator’s?
2. Who issues the point list, and by what date, because it is the cable schedule.
3. Who furnishes and mounts the control panels?
4. Which sensors are furnished by the integrator and which by mechanical, and who mounts them?
5. Are the mechanical room network drops in anyone’s package?

Answer those and the automation scope stops being the one argued about at closeout. Our Division 27 and Division 28 spec checklist covers the same failure across the other low voltage packages.

Next step#

Send the controls drawings, the point list if one exists, and the mechanical equipment schedule through request a bid. We return a cable count by type, a trunk layout, an IP drop count and a price, with the mechanical, electrical and integrator handoffs written out so nobody assumes we bid theirs. General contractors can find our prequalification packet at for general contractors.