Building Automation System (BAS) Basics for Small Commercial HVAC

Why this matters

Small + mid commercial buildings (5,000 - 50,000 sq ft) increasingly run a Building Automation System (BAS) instead of dumb thermostats. The HVAC contractor who can service + integrate + extend a BAS captures the recurring service contract + the upgrade work; the contractor who can't gets locked out when the controls integrator owns the relationship. BAS-literate techs bill at a meaningful premium over straight mechanical rates, often 50% or more per hour.

What BAS actually is

A BAS is a network of controllers + sensors + actuators that operate HVAC equipment based on schedules, setpoints, + logic. Components:

• Supervisory controller / front-end: web-based UI; stores schedules, alarms, trend data
• Field controllers: programmable boxes near each piece of equipment (RTU, AHU, VAV box, chiller)
• Sensors: temperature, humidity, CO2, occupancy, differential pressure, current
• Actuators: valves + dampers + VFDs that controllers command
• Network: BACnet IP / BACnet MS/TP / Modbus / proprietary; ties everything together

The end state: facility manager logs into a browser at 7 AM + sees every zone temp + every alarm + adjusts setpoints from a phone.

Common BAS platforms

• Tridium Niagara (open framework; integrators of all sizes build on it; 50%+ of new small-commercial)
• Johnson Controls Metasys (incumbent in older buildings)
• Honeywell WEBs / EBI (legacy + retrofit)
• Schneider EcoStruxure (large-building dominant)
• Trane Tracer (Trane-equipment buildings)
• Carrier i-Vu (Carrier-equipment buildings)
• Distech / Delta Controls / KMC / ALC (mid-market BACnet specialists)

Niagara dominates new install in the small-to-mid commercial BAS market because it's vendor-neutral; integrator can mix any BACnet equipment.

Protocols

BACnet - the dominant open protocol. Two flavors techs encounter:

• BACnet IP - runs on standard Ethernet / WiFi network alongside computers; modern
• BACnet MS/TP - twisted-pair RS-485 daisy-chain; older + simpler; still common on VAV boxes

Modbus - older industrial protocol; common on chillers + boilers + VFDs as a secondary interface.

Proprietary - older systems use vendor-locked protocols (LON, N2, etc.); these get gateway'd to BACnet on retrofits.

Service tech BAS competencies

Three tiers of capability:

Tier 1 - Service mechanic with BAS awareness

• Reads zone status on front-end
• Identifies alarms
• Mechanically services equipment per normal procedure
• Calls integrator if BAS work needed

Tier 2 - Service tech with controls competence

• Reads + interprets trend logs (zone temp over 24 hr, fan command vs status)
• Override / commands setpoints from front-end
• Replaces field sensors + actuators
• Tests + commissions individual loops (PID tuning at basic level)

Tier 3 - Controls technician

• Programs field controllers (Niagara Workbench, Honeywell WEBs, etc.)
• Adds new equipment to BAS network
• Builds front-end graphics + schedules
• Handles BACnet network architecture issues

Tier 2 is the sweet spot for the mechanical contractor adding BAS to their service book. Tier 3 typically lives at the controls integrator.

Common service calls

"No heat in zone 3" - front-end shows zone 3 calling for heat, damper open, but supply temp at zone is 65°F. Diagnosis: AHU heating valve actuator failed open → close → repair. Fix without BAS: 2 hours guessing. Fix with BAS: 20 minutes diagnostic, 30 minutes repair.

"Building hot in afternoon" - trend log shows zone temps climbing 2°F/hour after 2 PM. Outdoor air damper stuck open + cooling can't keep up. Mechanical fix.

"Alarm: chilled water flow" - chilled water differential pressure low. Pump VFD slowed by leaky valve elsewhere. Investigation across building.

"Setpoint changes ignored" - facility manager changes setpoint but zone doesn't follow. Schedule override active OR zone in unoccupied mode despite occupied schedule. UI training issue.

"No communication to RTU-4" - BACnet MS/TP wire damaged OR terminator missing OR address conflict. Network troubleshooting.

Network architecture (BACnet basics)

BACnet IP runs on the same Ethernet as office computers. Concerns:

• Firewall / VLAN may block BACnet (UDP port 47808 default)
• DHCP-assigned controller addresses can change + break the front-end
• Best practice: dedicated VLAN for BAS with static addressing

BACnet MS/TP is a daisy-chain on shielded twisted pair (Belden 9841 or equiv):

• Max 32 devices per segment without repeater
• Max 4,000 ft total segment length
• Both ends MUST have 120-ohm terminator
• Master addresses 0 - 127; common errors: duplicate addresses, missing terminator

Sensor + actuator service

• Temperature sensors: 10K thermistor common; verify with calibrated meter, replace if drift > 1°F
• CO2 sensors: NDIR type; recalibrate annually or per drift
• Occupancy sensors: PIR / dual-tech; battery + line-voltage versions
• Damper actuators: Belimo / Honeywell / Siemens; failure modes: stripped gear, dead motor, calibration drift
• Valve actuators: same vendors; same failure modes; plus stuck valve stem

Replacement: like-for-like is easiest but increasingly substitution required as products discontinue.

Add-on revenue from BAS

A BAS-literate contractor captures work the mechanical-only shop never sees: remote monitoring contracts (recurring fee to watch alarms + trend logs, catching failures early), ongoing sensor + actuator replacement bundled into the service contract, sequence-of-operation tuning as building use changes, gateway/protocol upgrades bringing a legacy system onto BACnet, and front-end graphics + reporting for a facility manager who wants better visibility. These carry higher margin than straight mechanical service, since controls-only integrators rarely also carry the mechanical trade license.

Common BAS install + service mistakes

Network ungrounded: BACnet shielded twisted-pair shield needs grounding at one end (not both). Floating shields cause comm errors.

Address conflicts: two devices on MS/TP with same address. Devices intermittently drop offline.

Missing terminators: signal reflections cause comm errors. Both ends of segment need 120-ohm terminator.

Schedule confusion: facility manager changes occupied setpoint at thermostat instead of front-end → setpoint overridden at start of next schedule period.

Sensor placement: zone temp sensor next to a doorway + reads cold air → zone never satisfies → mechanical equipment cycles excessively.

References

• ASHRAE Guideline 13 (Specifying BACnet)
• BACnet International (industry association)
• Niagara Tridium training (Univ-level cert path)
• Manuall internal: Commercial RTU Service, HVAC Light Commercial Equipment Service