Buildings & Industry · Automation and Controls
A decision hub for building automation: translate operating outcomes into architecture, sequences, interfaces, owner rights, cybersecurity and acceptance evidence.
For: Owners, operators, engineers, IT/OT teams and procurement teams evaluating BAS projects.
Key decisions on this page
Specify outcomes and behavior
Point counts and graphics are not substitutes for sequences, fallback modes and measurable acceptance criteria.
Make interoperability testable
A protocol name does not prove that data, tools, programming and integrations will be available to the owner.
Plan the operating life
Documentation, backups, support, change control, training and re-tuning determine long-term value.
What a building automation system may include
A building automation system can include sensors, meters, actuators, variable-speed drives, local controllers, supervisory servers, databases, graphics, alarms, schedules, trend logs and interfaces to other systems. The boundary varies. Some projects focus on HVAC; others connect lighting, electrical metering, distributed energy, access or enterprise platforms. The specification should describe the required functions and interfaces rather than rely on labels such as BAS, BMS or EMS.
| Layer | Core responsibility | Evidence at acceptance |
|---|---|---|
| Field | Measure conditions and act on equipment. | Sensor calibration, actuator operation, point list and field checkout. |
| Control | Execute sequences, interlocks, schedules and safe fallback. | Functional tests, trend evidence and approved sequence behavior. |
| Supervisory | Provide graphics, alarms, history, administration and reporting. | Role tests, alarm routing, trend retention, backup and restore. |
| Integration | Exchange selected data and commands with equipment or platforms. | Interface matrix, protocol services, failure handling and witnessed tests. |
| Operations | Govern users, changes, maintenance, cybersecurity and performance review. | Training, documentation, access, change log and support process. |
Interoperability is broader than a protocol
BACnet is designed for interoperable building-automation data communications, but a BACnet statement does not establish the complete owner outcome. A project still needs compatible objects and services, a network design, naming conventions, device profiles, gateway responsibility, tested integrations and clarity about programming tools, licenses and credentials. An “open system” should be defined through owner rights and acceptance tests.
Ask what the owner can read, command, trend, configure, back up and restore without the original vendor. Then require a demonstration using the delivered system.
Use the guide that matches the current decision
The supporting pages divide explanation, cost, terminology and selection so that each owns a distinct task.
Building automation explained
Architecture, functions, data flow, sequences, integrations and operating limits.
BAS cost
Hardware, engineering, integration, commissioning, software, service and owner effort.
BMS vs BAS vs EMS
Translate overlapping market labels into required capabilities and system boundaries.
Selecting a BAS
Requirements, vendor evidence, demonstrations, contract controls and acceptance.
Sequences and commissioning define real behavior
Controls implement sequences of operation: how equipment starts, stages, resets, limits, alarms and responds to faults. Hardware cannot compensate for an incomplete sequence, and a sequence on paper does not prove correct field behavior. The design should identify applicable high-performance sequences, project-specific adaptations, safety and equipment constraints, and the trend data required for functional testing.
Commissioning should verify the installed system under representative conditions, including failure and recovery. Acceptance evidence may include point-to-point checks, sensor calibration, alarm tests, trend reviews, sequence tests, integration tests, backup restoration and operator demonstrations. Deferred or seasonal tests should have owners and completion dates rather than disappearing after handover.
Cybersecurity and continuity
NIST includes building automation among operational-technology systems. That means security controls must be compatible with physical operation, maintenance windows and safety. Define asset inventory, network zones, remote access, user identity, logging, patch governance, backups, incident response and vendor obligations. Cloud-connected features should have an offline or degraded-mode strategy where loss of service could affect critical operation.
Common specification failures
- Buying a point count without an approved point schedule and sequence responsibility.
- Accepting “open protocol” without owner access, tools, licenses and integration tests.
- Treating graphics as the main deliverable while trends, alarms and naming remain inconsistent.
- Leaving cybersecurity, remote support and backup until after network connection.
- Failing to define data retention, export, time synchronization and change history.
- Closing the project without operator training, seasonal testing and a re-tuning process.
Use shared tools without turning scoring into false precision
The Technology Evaluation Scorecard can separate mandatory requirements from weighted preferences, while the Vendor Comparison Worksheet preserves exclusions and commercial differences. A failed life-safety, cybersecurity, interoperability or owner-rights gate should not be cured by a high total score.
Keep terminology, cost and selection aligned
Use BMS vs BAS vs EMS when stakeholders use the labels differently, then record the required capabilities independently of the name. The BAS cost guide should use the same scope and owner-rights boundary as the technical requirements. Finally, Selecting a Building Automation System turns those requirements into demonstrations, due diligence and acceptance evidence.
Scope and review
This hub does not provide a final controls design, sequence specification, code determination or cybersecurity approval. Qualified controls, mechanical, electrical, commissioning, IT/OT and life-safety specialists should adapt the requirements to the facility and verify the completed work.
Sources and evidence
These sources establish the framework and current evidence boundary for this hub. Detailed child guides use additional page-specific evidence.
- Building Controls — U.S. Department of Energy
- SP 800-82 Rev. 3: Guide to Operational Technology Security — National Institute of Standards and Technology
- BACnet resources — ASHRAE
- Building Technologies Office — U.S. Department of Energy
- Project Control authority: approved project authority, page map, complete page criteria and page-rules addendum — Future Green Technology
Reviewed and updated 29 June 2026. Organizational author: Future Green Technology, published by Zenith Star Media.