Across a real estate portfolio, the drawings say one thing and the controllers do another. Before an energy retrofit touches a single setpoint, you want proof of what the control programs actually do.
An illustrative scenario — a composite of the situations we build for, not a customer reference.
A campus operator runs air-handling units from different vendors and different eras — some installed with the building, some retrofitted, each carrying its own integrator’s conventions. Frost protection, fire modes, night cooling and the interlocks between them live in the controllers, not in the drawings.
An energy programme wants to adjust setpoints and schedules across the portfolio. The question that blocks it is simple: what will actually happen when we do?
Each unit is assessed at the depth it needs, then composed into one model of the site — with the interfaces between units, and to the fire system, catalogued explicitly.
Multi-unit systems get an interface catalogue covering the connections inside the system and out — the thing every retrofit wishes existed.
Claims cite the source of whichever vendor’s program proves them. The model speaks one language even when the plant floor speaks five.
A named engineer verifies the model before you act on it.
From a synthetic building automation & hvac system — we never show customer data.
Tell us what you run — an Orientation assessment takes days, not months.