The Problem
The Problem Is Not Device Counting. It Is Information Reuse.
A diagnosis of why BMS engineering workflows break — before any engineering starts.
BMS engineering produces a chain of documents — inquiry, IO list, controller selection, BOQ, sequence of operations, submittals, commissioning records. Every document in that chain is built from the same underlying information. But most firms enter that information manually, from scratch, at every stage. That is the problem. Not the complexity. The repetition.
Where Information Gets Reused (and Re-Entered)
An air handling unit appears in the mechanical spec. An engineer reads it and manually extracts the IO points. Those points are manually entered into the IO list. The IO list is manually used to select controllers. The controllers are manually entered into the BOQ. The BOQ is manually used to generate a price.
At no stage does the information from the previous stage automatically flow into the next. Every handoff is a manual step. Every manual step is an opportunity for error — and a cost no one explicitly measures.
The Revision Trap
A drawing revision arrives. The engineer finds every place that information lives. The IO list. The submittal. The controller schematic. The BOQ. On a project with five revision cycles, that process runs five times. Hours gone — every cycle.
The Talent Cost
This is not a junior engineer problem. In most BMS contracting firms, the extraction, rebuilding, and documentation work falls on the engineers who understand the systems well enough to catch errors — the senior people. That is the highest-cost misuse of engineering expertise in the industry.
When agents handle information reuse, senior engineers can focus on sequence validation, troubleshooting, and real engineering decisions. That is where their expertise actually belongs.