BAS controls handoff: a guide for operating readiness
How to evaluate point lists, sequences, alarms, overrides, trend data, documentation, and ownership before relying on a building automation system.
Short answer: A BAS handoff is ready when the operating team can identify what each important point means, understand the intended sequence, recognize alarms and overrides, access the needed trend evidence, and know who owns changes and recovery.
Inventory the operating boundary
List controllers, supervisory devices, gateways, networks, critical equipment, remote-access paths, graphics, schedules, and responsible parties. A point list alone does not show the operating boundary. Include dependencies that can change whether a control action is safe, visible, or reversible.
Test point meaning and quality
For priority points, verify the name, unit, range, timestamp behavior, source, sensor status, commandability, and relationship to the equipment. Flag points that are stale, mislabeled, duplicated, overridden, or disconnected from the sequence. A value with no reliable definition should not be treated as decision-grade evidence.
Read the sequence as an operating contract
The sequence should explain modes, enable conditions, safeties, setpoints, resets, overrides, alarms, and failure responses in language the operations team can use. Compare the documented intent with observed behavior. Record deviations rather than assuming the graphics or program are authoritative.
Make alarms actionable
An alarm needs a credible trigger, an owner, a response expectation, enough context for triage, and a closeout or suppression rule. Count and display volume are not alarm governance. Review nuisance alarms, stale alarms, missing priorities, and alarms that do not map to an accountable workflow.
Plan change and recovery
Document who can change sequences, schedules, credentials, graphics, and network settings; how changes are reviewed; how backups are verified; and how the system is restored after a failed update or compromised account. Controls readiness includes people and recovery, not only the software configuration.