The Boardroom Doesn't Speak BACnet

The boardroom doesn't speak BACnet

A problem in the chiller plant, by the time it reaches the boardroom, has been through more translations than a tourist phrasebook, and like a phrasebook it arrives mostly wrong. The technician says, accurately, "we've got low delta-T syndrome on the primary loop." The facilities report turns that into "HVAC underperformance." The slide deck softens it to "opportunities in building efficiency." And the executive, three layers of abstraction later, sees a vague phrase next to a request for capital and quietly files it under things to think about never. Nobody lied. The signal just decayed at every handoff until nothing actionable was left.

This is the C-suite's relationship with the building, and it's worth understanding honestly, because the people who hold the budget are also the people furthest from the data, and that distance costs real money.

Energy is a board-level issue that never reaches the board intact

From the top, a building's energy is not a technical curiosity. It's one of the largest controllable operating costs the organisation has, a growing compliance exposure under the EECA and the TNB tariff, a reputational and trade risk through ESG and CBAM, and a quiet factor in the value of the asset itself. By any reasonable measure it belongs on the executive agenda.

The trouble is that it arrives there in one of two useless forms. Either it's too technical, a wall of points and kilowatts and acronyms that means nothing to someone running a P&L, or it's too vague, a reassuring sentence about "ongoing efficiency efforts" that contains no number, no direction and no decision. The executive is left to govern a major cost and a real risk through a fog, and the rational response to fog is to wait, which is the one response that guarantees the cost and the risk keep growing.

What an executive actually wants is embarrassingly simple

Spend time with the people in the corner offices and you find they don't want what the technology industry keeps trying to give them. They do not want a dashboard. They will not log in to a dashboard. They have no intention of learning what a sensor is called.

What they want is roughly four things:

- One number, in money. Not kilowatt-hours, ringgit. What is this costing, across the whole portfolio, and what is the trend.
- A direction. Is it getting better or worse than last year, and than budget. Up or down is more useful to a board than any amount of detail.
- Where the money and the risk are. Which sites, which exposures, so attention and capital go to the few things that matter.
- Confidence the number is real. Not someone's annual estimate, but a figure they can repeat to an auditor, a regulator or an investor without flinching.

That's it. The detail matters enormously, but it matters one or two levels down. At the top, the job of the data is to become a decision, and a decision needs clarity, not completeness.

The translation problem, again

What the boardroom really suffers from is the same thing the whole building industry suffers from: nobody built a clean path from the operational reality at the bottom to the language of money and risk at the top. The data exists. It's simply trapped in a dialect the people with the budget can't read, and rekeyed by hand into slide decks that smooth away exactly the precision a decision needs.

Closing that gap is less about adding executive features and more about translation, the same theme we keep hitting in building software for both OT and IT. The same underlying data that the operator sees as equipment and the energy manager sees as KPIs has to be able to present, to the executive, as a cost, a trend and a risk, without losing its honesty on the way up. A portfolio view that rolls every site into a headline. The ability to ask a plain question, "what's our energy cost trend this year, and where's it worst," and get a straight answer rather than a meeting, which is part of what CobiBot is for.

The executives who manage energy well are not the ones who learned to read a BMS. They're the ones who got the building's reality delivered to them in their own language, money and risk and direction, with enough confidence in the numbers to act on them. Everything technical underneath still has to be right. It just shouldn't be their problem to decode.

If the building only ever reaches your boardroom as a vague slide and a capex request, the gap isn't your team's competence, it's the translation. Come and see what the building looks like when it speaks the language of the people who fund it.