Building Automation & Controls

How It Works & Technology Overview

Building automation is supervisory control over a building's mechanical and electrical systems: field controllers reading sensors and driving actuators (dampers, valves, VFDs, relays), a network layer (BACnet/IP and BACnet MS/TP dominate; Modbus and LonWorks persist in legacy plant), and a head-end/front-end for graphics, schedules, alarms, and trending. The unit of estimation is the point: a physical input/output that must be wired, terminated, addressed, and verified, or an integration point mapped from third-party equipment over a protocol. Physical points are predictable labor; integration points depend on someone else's firmware and documentation. Lighting control (Lutron, Crestron, KNX, DALI) is a sibling discipline — keypads, zones, scenes, daylighting — that either runs standalone or integrates into the BAS. Sequences of operations (SOO) are the system's actual logic; a controls project without a written SOO is a design project wearing an install label. Commissioning is where the engineering lives: making dissimilar systems (HVAC ↔ lighting ↔ occupancy ↔ metering) behave as one, and proving every point end-to-end.

Common Deployment Scenarios

• New construction: controls follow the mechanical contractor; sequences come from the design engineer; labor is per-point predictable but schedule-dependent on other trades — commissioning always lands in the compressed pre-occupancy window.
• Retrofit/upgrade: replacing obsolete controllers or a dead front-end on a live building; as-builts are unreliable, existing wiring must be proven, and undocumented legacy logic must be reverse-engineered before it can be replaced.
• Integration overlay: equipment stays, a supervisory layer is added (energy dashboards, unified alarming, tenant comfort apps) — cheapest install, most expensive commissioning.
• Lighting control projects: room/floor-level keypads, scenes, schedules, daylight harvesting; frequently attached to AV or TI projects; commissioned after electrical rough-in.
• Takeovers: assuming service on someone else's installed system — license status, admin credentials, and controller support status determine whether it's a service account or a hidden rip-and-replace.

Products, Vendors & Characteristics

• Niagara Framework (Tridium) is the de facto open supervisory platform; many OEM front-ends (Honeywell WEBs, Distech EC-Net, JCI FX) are Niagara underneath. License tiers gate point counts and drivers.
• Field controllers: Distech, Honeywell, Johnson Controls, Siemens, Schneider (EcoStruxure), Delta, KMC. Proprietary-protocol legacies (older JCI N2, Siemens P1) constrain retrofit options sharply.
• Lighting: Lutron (dealer-programmed ecosystems; Vive for commercial retrofit), Crestron (programming is a specialized trade), KNX/DALI open standards in commercial lighting.
• "Open protocol" is a spectrum: BACnet conformance varies by firmware version; some equipment exposes read-only points, some requires a licensed vendor gateway with per-point mapping fees. Verify against installed firmware, not sales literature.
• Integration middleware: when vendors share no open protocol, gateways (or custom middleware) bridge them — a scope item, never a footnote.

What Makes It Hard (Gotchas & Failure Modes)

• The points list is the estimate, and everyone else's points list is wrong: mechanical schedules miss field-discovered devices, and integration point counts get quoted before anyone confirms which points the equipment actually exposes writable.
• Scope boundary with the electrician moves job to job: who mounts and wires field devices, who provides line-voltage transformers, who owns conduit — read the spec; the gap defaults to controls.
• Orphaned head-ends: lost admin passwords, expired licenses, dead brands — a "just reconnect it" request becomes replacement.
• Existing wiring is a rumor in retrofits: budget point-to-point verification or price the risk; unusable wiring discovered mid-project is a change-order war.
• Sequences by omission: "you're the controls guy, figure it out" means unpriced design liability — require a written SOO or bill its authoring.
• Commissioning compression: controls functional testing depends on TAB and mechanical completion; upstream slips land on the controls window, and untested points become warranty callbacks.
• Pilot creep in lighting/overlay work: one approved floor quietly becomes three; each floor re-opens design, not just installation.
• No spare capacity: additions that land on a controller with no spare inputs/outputs need a new controller, enclosure, power and network drop — confirm spare I/O before pricing per point.
• Witnessing and balancing support: owner's commissioning agents often witness every sequence, and specs commonly put a controls technician on site while the air balancer works the boxes — labor the per-point rate does not carry.
• IT network rules: many IT departments refuse controls devices on the corporate network, or demand device approval and patching commitments — a separate network or firewall work becomes scope.

Effort & Estimation Patterns

• Hardwired physical point (mounted, wired, terminated, addressed, verified): 1.5–2.5 hours all-in across the project lifecycle; estimate per-point and let the count do the math.
• Integration points: 30–60 minutes per mapped BACnet point on cooperative equipment; 4–8 hours of gateway configuration and discovery for the first point on each new device type.
• Graphics/head-end build: ~1 hour per equipment graphic plus a day of navigation, alarm, and user setup on a mid-size building.
• Functional testing: 20–30% of total controls labor — non-negotiable; a point that hasn't been end-to-end tested is a callback, not a deliverable.
• Retrofit multiplier: add 30–50% over new-construction per-point rates until a survey proves wiring and access.
• Lighting control, per room/zone (keypads, scenes, commissioning): 2–4 hours per zone after electrical rough-in; whole-floor daylighting/tuning adds a commissioning day.
• Sequence programming: never quoted without a written SOO; SOO authoring for a typical AHU runs 4–8 hours of engineering time.
• Takeover audit (licenses, credentials, controller support status, backup extraction): a half-day to a day before any service commitment is priced.