What BMS actually controls in modern construction
A modern commercial BMS typically integrates:
- HVAC — Air handling units, VAV boxes, chillers, cooling towers, boilers, and the sensors and actuators that control them.
- Lighting control — Daylight harvesting, occupancy sensing, scheduling, dimming control. Increasingly via DALI, 0-10V, or networked drivers.
- Energy monitoring — Submetering of major loads, real-time energy data, demand response capability.
- Fire alarm integration — Smoke control, HVAC shutdown sequences, elevator recall coordination.
- Security and access control — Door schedules, after-hours HVAC reset, occupancy-based controls.
- Specialty equipment — Generator status, ATS position, UPS status, refrigeration plant data, kitchen equipment monitoring.
Major BMS platforms include Johnson Controls Metasys, Honeywell EBI, Siemens Desigo, Schneider EcoStruxure Building, ABB, and Distech. Each has different integration capabilities and protocol support.
Where electrical scope intersects BMS
Power for BMS infrastructure
BMS controllers, network switches, and DDC panels need clean, reliable power. Often on a dedicated panel with surge protection and sometimes UPS backup for the head-end. Coordination with the BMS contractor on power requirements during design.
Hardwired interfaces
Some BMS connections are simple dry contacts (generator running, ATS position, alarm input). Electrical scope brings the wiring to a terminal that the BMS contractor reads. Specifying which side terminates is critical to avoid finger-pointing during commissioning.
Network protocol integration
BACnet/IP, Modbus TCP, Modbus RTU, and increasingly proprietary cloud protocols connect BMS to electrical systems. Generator controllers, UPS systems, transformer monitors, and EPMS frequently expose data via these protocols. Coordination on IP addressing, network architecture, and gateway configuration during design.
Lighting control wiring
The electrical contractor typically wires lighting controls per the lighting control system specification (which may be a BMS subsystem or a separate system). The split between electrical scope (line voltage to control panels, network cable to controllers) and lighting control contractor scope (controller programming, scene setup) is project-specific.
Submetering installation
Electrical submeters for energy monitoring (typically Veris, Schneider PowerLogic, Eaton xPert, or similar) are installed by the electrical contractor with conduit and wiring back to a BMS panel or directly to the BMS network. CT installation, voltage tap installation, and meter commissioning.
Scope-split disasters we’ve seen
- "BMS contractor provides everything" mythology. Owner assumes the BMS contractor handles all integration. Electrical scope omits BMS infrastructure power, network cabling for distributed I/O panels, and hardwired interfaces. Discovered at commissioning. Schedule slip.
- Submeter scope gap. Submeters specified but neither electrical contractor nor BMS contractor includes them clearly in scope. Discovered late in construction. Change order.
- Generator monitoring half-built. Generator controller installed by mechanical, BACnet IP integration assumed but no one configured the gateway or set up the BMS points. Commissioning team finds it the week of energization.
- Lighting control responsibility gap. Electrical installs the fixtures, drivers, and controllers. BMS contractor expects to program. Lighting control contractor (a separate entity sometimes) wasn’t hired. Programming doesn’t happen.
- Cybersecurity coordination missing. BMS network connects to the corporate network without proper segmentation, firewall configuration, or vulnerability management. Operations IT discovers it post-handover and demands rework.
What clean scope splits look like
For a typical commercial building, a reasonable scope split:
- Electrical contractor — Line voltage to all BMS power, conduit and 120V from panel to BMS controllers, line voltage to lighting controllers, submeter installation including CTs and voltage taps, hardwired interfaces (point-to-point wiring per BMS schedule), labor for installing BMS-supplied panels.
- BMS contractor — Network cabling between BMS panels, sensor and actuator field installation in HVAC equipment, programming and graphics, system commissioning, all software configuration, training.
- Lighting controls contractor (if separate) — Controller programming, scene setup, daylight harvesting calibration, occupancy sensor commissioning.
- Fire alarm contractor — Fire alarm system itself; BMS interface limited to specific monitored points per scope.
- Security contractor — Access control system; BMS interface for after-hours HVAC and similar limited.
The exact splits vary by project, but having them documented in writing before bid award prevents most of the scope gap issues.
What owners should ask during preconstruction
- What BMS protocol architecture is the building using? (BACnet/IP only? Multi-protocol? Cloud-connected?)
- Which integrations are required versus desired versus future-state?
- Who owns the responsibility for system commissioning across the integration boundary?
- What cybersecurity standards govern the BMS network architecture?
- What does post-handover support look like, and how are issues triaged across contractors?