From Design Intent to Operable Controls: The BMS Documentation Stack
A controls package is only as good as the documentation behind it. This guide walks through the stack of documents that takes a BMS from design intent to an operable, maintainable system, and what each one is for.
Architecture
The network and system architecture defines what connects to what, over which protocols, and where the integration boundaries sit. Everything else follows from it.
Points schedule
Every input and output, scheduled and budgeted. The points schedule is the contract between the mechanical design and the controls system.
Sequence of operation
The control logic written as a clear, testable narrative — start-up, normal operation, staging, reset, failure and interlock conditions.
Panels
Panel schematics, wiring diagrams and termination schedules, drawn to a consistent standard so the system is serviceable for its whole life.
Network drawings
How controllers, supervisors and gateways are connected and addressed, and how the network is segmented and secured.
Graphics
Operator graphics built around how the building is actually run, with the hierarchy, live data and navigation operators need.
Commissioning
Point-to-point and functional test records that prove the system against the sequences, with witnessing and defect close-out.
As-built documentation
The final record — updated drawings, schedules, backups and O&M material — that the operating team keeps and maintains.
Working through this on a live project?
Send the project details and we will review the controls scope with you.
Discuss a design-stage project