Plain-spoken pieces on building controls, open systems and using less energy — written by the engineers who do the work, for the people who run the buildings.
A single main meter tells you almost nothing. How submetering, honest baselines and one simple 2am test turn energy-saving from guesswork into engineering.
DocumentationThe DoO is the contract between design intent and installed reality. What a good one contains, who depends on it, and why it should be written before the software.
The loopEvery control strategy we write follows the same loop that's on our badge. What each stage demands — and why the loop only earns its name when it learns.
ModernisationSystems rarely fail loudly — they fade. The warning signs that yours is costing you, and how to migrate to modern control without switching the building off.
TechnicalAn open framework rather than a product: how Niagara lets one supervisor speak every protocol in the building, and the honest caveats that come with it.
EnergyIf your plant starts at the same minute every morning regardless of the weather, you're paying for hours of heating nobody feels. The fix is already in your system.
OpinionLocked tools, missing passwords and single-supplier servicing cost building owners dearly. What independence actually looks like — and the questions that reveal it.
TechnicalThe four languages your building's devices speak, what each is genuinely good at, and why 'open protocol' on a datasheet doesn't automatically mean an open system.
FundamentalsThe plain-English answer: what the system is made of, what it does all day, and why it quietly decides how your building feels and what it costs to run.