Forty buildings, and the same question forty times.
An estate assembled over thirty years runs more than one head-end, because each building was bought by different people in different decades. Nobody can ask all of them the same question, so nobody asks.
One model across the estate
Sites and buildings are modelled entities like any other, so an air handler in one building is the same kind of thing as an air handler in another. That is what makes “which of our chillers is running hardest for what it delivers” a query rather than a project.
Comparable, because the model is shared
Comparison between buildings usually fails on naming: two sites that call the same thing different names cannot be ranked. Equipment inherits its type, so the comparison holds without anyone reconciling spreadsheets first.
Rolled out building by building
An estate does not cut over at once. Each building joins the namespace when its survey and parallel run are done, and it is comparable with the others from the day it joins rather than at the end of the programme.
Specifics
- Modelled
- Sites and buildings as entities, with equipment typed across them
- Compared
- Like equipment against like, without per-site reconciliation
- Rolled out
- Building by building, comparable from the day each joins
Common questions
Do all our buildings have to run the same head-end today?
No, and most estates do not. Each building is surveyed against whatever it runs — Metasys, Desigo, WebCTRL or something older — and joins the same namespace regardless.
Can we start with one building?
That is the usual shape. One building proves the survey, the parallel run and the cutover, and the second is faster because its equipment types already exist.
Bring your point list.
The first conversation is a survey: what you run today, and what it would look like modelled.