To specify building automation for a data center or hospital, an engineer is choosing the nervous system of the plant. Controls decide how chillers stage, how pumps ramp, how alarms reach staff and how well the building saves energy. Weak controls spoil good equipment, and strong controls make an ordinary plant perform well. This guide lays out the key choices.

Architecture
A building automation system, or BAS, usually has field controllers, network controllers, a supervisory server and operator workstations. Specify the number of operator seats, the level of redundancy, local override capability and what happens if the network fails. Critical equipment should run safely on local control without the server.
Open protocols
Open protocols such as BACnet and Modbus let different systems exchange data. Require open, documented interfaces, native BACnet where possible and point lists that the owner can use without vendor lock in. Many projects add a separate electrical power monitoring system and a data center infrastructure management system. Specify who owns each interface and how data will be shared.
Sensors and field devices
Control quality depends on sensors. Specify accuracy for temperature, pressure, flow and humidity, plus calibration and replacement plans. Use redundant sensors for critical control points. Include differential pressure sensors for pumps, flow meters for energy calculations and leak detection where needed. Choose actuators that match valve torque and response speed.
Sequences of operation
The sequence of operation is the most important page in the section. It says how each system behaves under normal, partial load and failure conditions. A good sequence names setpoints, staging triggers, reset logic, alarm limits and fail safe behavior. Without it, the contractor will program what they assume. Require the engineer to write sequences in detail and the commissioning agent to test each one.
Cybersecurity
Controls networks connect to remote support and cloud analytics, which opens them to attack. Specify network segmentation, strong authentication, patching procedures, logging and limits on remote access. Align with owner security policy and relevant standards such as ISA and IEC 62443.
Eco and energy features
Controls produce much of a building efficiency. Chilled water reset, condenser water reset, fan and pump speed control, economizer logic, demand response and metering all depend on the BAS. Specify energy dashboards, trending, fault detection and monthly reporting so that savings are measured, not guessed. These features also support green building certifications.
Commissioning and training
Require point to point testing, functional performance testing of sequences and training for operators. Ask for a final programming backup, graphics and a written operations guide. Include a seasonal tuning visit, because systems behave differently in winter and summer.
A short checklist for specifiers
- Name the scope: which systems, sizes and service conditions the section covers.
- State the standards the product must meet and the tests required before shipment.
- List acceptable manufacturers and a basis of design, and say how substitutions are reviewed.
- Require submittals that show performance data, materials, weights and dimensions.
- Define startup, commissioning, training and warranty.
- Record what the owner needs at turnover so operators can keep the system running.
How suppliers and specifiers can work together
Engineers write better sections when they have clean, current information early. Suppliers who share a clear cut sheet, a short basis of design paragraph and honest lead time and stock information make it easier to write controls requirements that can actually be bought and installed. The most useful conversations happen while the mechanical specification is still open, before bids go out. Be specific about what is standard, what is custom and what changes the price or the schedule. Specifiers should keep notes on what worked, so the next master spec starts stronger than the last one.
Common mistakes to avoid
Weak controls usually come from rushed projects. Sensors are placed in poor locations. Alarm limits are left at defaults so operators ignore them. Overrides are left in place after commissioning. Trend logs are not saved. The graphics do not match the field, which slows down troubleshooting. Software licenses and passwords are not delivered to the owner. A strong section requires a clean handoff, a written alarm philosophy and a plan for seasonal tuning in the first year.
Owner standards and graphics
Many owners have their own naming standards, graphics templates and alarm priorities. Ask for these early and write them into the section, so every project looks the same to the operators who work across several sites. Consistent point names and screens cut training time and reduce mistakes during a real event.
Frequently asked questions
What is BACnet?
It is an open communication protocol designed for building automation and control networks.
Why are sequences of operation important?
They define how equipment should behave in each condition, and they are the reference for programming and testing.
Should controls be cybersecure?
Yes. Building networks can be an entry point for attacks, so segmentation, authentication and patching should be specified.
Related reading: Building specification directory, Specifying chillers, PUE explained. External reference: BACnet International.









