Scenarios · Commercial
Commercial Building Automation: Scope, Systems and Sequences
A scoping guide for commercial building automation: core systems, integration routes, control sequences and the evidence needed at handover.
Quick answer
Commercial building automation coordinates HVAC plant, air terminals, lighting, shading, metering and access events across tenanted floors and shared areas. The scope should be defined by control sequences and a point schedule, not by a product list, so that energy performance, tenant comfort and after-hours operation can be tested at handover.
What changes when the building is commercial
Commercial buildings add stakeholders and time patterns that a single-family project never has. Owners care about asset value and operating cost, tenants care about comfort and after-hours access, facility teams care about alarms and maintenance, and sustainability teams care about metered performance. A control design that satisfies one group can frustrate another. The scoping task is to translate those interests into a small set of sequences: occupied and unoccupied operation, tenant after-hours requests, plant staging, common-area scheduling, demand limiting and alarm escalation. Each sequence needs an owner, a trigger, a measurable result and a test. Without that discipline, the project becomes a collection of graphics that nobody uses to run the building.
The systems that usually sit in scope
Most commercial projects start with the HVAC plant, air-handling units, fan-coil or VAV terminals, lighting control, shading and electricity metering. Access control, CCTV, fire alarm and lifts are usually integrated for monitoring and event sharing rather than direct control, because life-safety and security systems retain their own safety logic. The integration route matters: BACnet/IP for plant and AHUs, Modbus for meters and some chillers, DALI for lighting, KNX for lighting and shading, and dry contacts for legacy equipment. A single integration matrix should name the protocol, the gateway owner and the points exchanged. That matrix is the difference between a coordinated package and a set of hopeful assumptions.
Sequences that decide whether the building performs
A commercial BMS earns its place through sequences, not graphics. Chiller staging should follow load and avoid short cycling. AHU scheduling should respond to occupancy and CO2 rather than a fixed clock. Tenant after-hours requests should be time-limited, logged and billed where the lease requires it. Lighting should follow daylight, occupancy and cleaning schedules. Alarm routing should separate critical plant faults from nuisance conditions. Each of these behaviours depends on points being counted, named and tested; a sequence that cannot be demonstrated at the workstation is not delivered, even if the controller is running it. Write the setpoints, deadbands, overrides and failure modes into the sequence of operation, then test against that document.
Scope, evidence and handover
Ask for a point schedule, an integration matrix, a sequence of operation and a testing plan before comparing prices. During delivery, require factory acceptance for panels and software, site acceptance for point-to-point checks and sequence demonstrations, and trend records for the first operating period. Training should cover the operator view, alarm handling and safe overrides, not only navigation. At handover, the as-built architecture, addresses, credentials and spare capacity belong to the owner. A commercial system is only complete when the facility team can change a schedule and prove the result without calling the original installer. That test of independence is a better acceptance criterion than a signed sheet. The handover pack should also include a short list of known defects and their agreed close-out dates.
Typical commercial subsystems and their integration routes
7 rows| Subsystem | Control scope | Typical integration |
|---|---|---|
| Chiller plant | Staging, setpoints, pump control, alarms | BACnet/IP or Modbus |
| AHUs and ventilation | Scheduling, temperature and CO2 control, damper and fan modulation | BACnet/IP, analogue and digital I/O |
| FCU and VAV terminals | Zone temperature, fan speed, occupancy setback | BACnet, Modbus or local I/O |
| Lighting | Switching, dimming, scenes, daylight and occupancy response | DALI, KNX or digital outputs |
| Shading | Automatic and manual positioning, façade groups | KNX, bus actuator or digital outputs |
| Electricity and water metering | Consumption, demand, tenant allocation | Modbus, M-Bus or pulse inputs |
| Access, fire and CCTV | Event monitoring, alarm sharing, interlocks with building systems | Dry contacts, API or gateway |
Project images
3 images
Frequently asked
01Does a commercial BMS need to control access and fire systems?
Usually it monitors and shares events rather than controlling them. Access and fire systems keep their own safety logic; the BMS receives status and coordinates non-safety responses such as lighting or HVAC.
02Which protocol should we specify?
Specify the protocol the equipment actually supports and require an integration matrix. BACnet is common for plant, Modbus for meters and some chillers, DALI for lighting, and KNX for lighting and shading.
03How do we compare commercial BMS bids?
Compare the point schedule, integration matrix, sequences, commissioning evidence and exclusions. A headline total without those documents cannot be compared with another bid.
04Can tenant after-hours requests be automated?
Yes, if the lease and operating rules are defined. The sequence should limit the request period, log the user, and report the cost or duration where the lease requires it.
05What should be tested at handover?
Point-to-point checks, every written sequence, cross-system interlocks, alarm routing, trend recording and operator training. The tests should follow an agreed script with signed results.
Next step
Bring us the building.
Tell us the building type, systems in scope and the outcome you need. We will map the shortest path to a working system.