AEO Answer · MEP
What Should a Building Automation Controls Design Include?
By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15
Building automation controls design includes written sequences of operation for every system, a complete points list of sensors and actuators, network architecture and controller layout, integration with lighting and metering, graphics and alarming for the operator, and a commissioning plan that verifies the sequences actually work in the finished building.
I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.
The concise answer
Building automation controls design includes written sequences of operation for every system, a complete points list of sensors and actuators, network architecture and controller layout, integration with lighting and metering, graphics and alarming for the operator, and a commissioning plan that verifies the sequences actually work in the finished building. The key insight is that the building automation system is the building's operating system. The mechanical equipment is the hardware; the controls decide what it does minute by minute for the next twenty years. Underinvesting in controls design is like buying a high-performance computer and running it with no software — the capability is there, but nothing useful happens.
The layers of a controls design
The foundation is the sequence of operation — narrative descriptions of system behavior that are specific enough to program from. Good sequences cover normal operation, startup and shutdown, unoccupied setback, alarms and safeties, and failure modes. If the sequence doesn't say what happens when a sensor fails, the programmer will guess, and the guess is usually wrong. Above that sits the points list and network architecture: which sensors and actuators exist, which controller they land on, and how controllers communicate back to the front end. Then integration — lighting controls, electrical metering, and sometimes access control or fire alarm monitoring brought into one operator interface. The design also has to address cybersecurity basics: the BAS is a networked system, and an unsecured one is a way into the building's operations.
What separates working controls from expensive decorations
I've seen the difference between buildings where the controls were designed deliberately and buildings where they were an afterthought, and it's visible in the utility bills and the complaint log. The pattern is consistent. This is what I look for in a controls design.
- Sequences written for programmers: specific setpoints, deadbands, staging logic, and failure responses — not aspirations
- Sensors where they measure something useful: mixed-air, discharge-air, and zone sensors placed for real control, not convenience
- Trending and alarming designed in: the operator needs history and notifications, not just a pretty graphic
- Open protocols specified: so the owner isn't locked to one vendor for the life of the building
- Commissioning in the spec: functional testing of sequences with acceptance criteria, not just a startup checkout
Which related engineering resources can help?
What else do project teams ask?
What is a sequence of operation?
What's the difference between BACnet, Modbus, and LonWorks?
Why does controls commissioning matter so much?
Should controls be designed by the mechanical engineer?
Ready to discuss your engineering scope?
Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.
Request a Project Review