What does it take for a building to earn the label “smart”? If the answer is a fully commissioned building management system, thousands of connected sensors, and a vendor-supplied dashboard running around the clock, then a great many buildings across Southeast Asia and beyond already qualify. And yet the building managers who operate them keep receiving the same quarterly message: the energy bill has gone up again.
That contradiction deserves to be examined seriously. Not because the technology has failed, but because the way it is being used has never been designed to prevent the problem it was sold to solve.
The Paradox of the Instrumented Building
The modern commercial building is, on paper, one of the most data-rich environments in the built environment. A mid-sized Grade A office tower in Kuala Lumpur or Singapore typically carries hundreds of BMS data points: chiller plant performance, air handling unit supply temperatures, VAV damper positions, lighting relay states, elevator energy draws, and water meter readings. The system logs continuously. The data exists.
The problem is not that the data is missing. The problem is that nobody has converted it into a decision.
The facilities manager in this scenario is not negligent. The property developer who commissioned the BMS specified it correctly. The FM service company running the operations has qualified engineers on site. All the pieces are present. What is absent is the interpretive layer that turns a stream of sensor values into a clear, actionable picture of where energy is being wasted, why it is happening, and what should change before the next billing cycle closes.
This is operational blindness in the built environment. And it is costing building owners money every single month.
Occupancy and the Invisible Variable
The single largest driver of energy waste in commercial buildings is not equipment failure. It is the mismatch between occupancy patterns and the systems that serve those patterns.
HVAC systems in most commercial buildings are scheduled around assumptions. The building opens at 8 AM. The floors are assumed to be occupied from 9 AM to 6 PM. The BMS runs the air handling units accordingly. The problem is that assumptions age poorly. Tenants change their working patterns. Floors that were once densely packed now operate at thirty percent capacity on Mondays and Fridays. The hot-desking layout adopted after the pandemic means the third floor might have eighty people at 10 AM and twelve by 3 PM. The BMS, running on its original commissioning schedule, does not know any of this.
Occupancy sensors, where they exist, are often installed at the building perimeter rather than throughout the floor plate. Card access systems log entry and exit but rarely feed that data into the BMS. The result is a sophisticated mechanical system operating on stale assumptions while burning energy to condition space that nobody is using.
A building serving a large corporate tenant in Petaling Jaya conducted an internal analysis in 2024 and found that HVAC was running at full load on floors where occupancy dropped below twenty percent by 2 PM. The energy cost of those afternoon hours across a year represented a six-figure sum in ringgit. The BMS had been logging floor-by-floor return air temperatures the entire time. The data was there. No one had looked at it through the lens of occupancy.
The Gap Between Data Collected and Decisions Made
The core structural failure in most smart building deployments is not technical. It is the distance between the data layer and the decision layer.
A standard BMS dashboard shows what is happening right now. It displays a chiller outlet temperature, a pump speed, a damper position. An experienced engineer can read it fluently. But the building manager presenting a quarterly report to the property owner or REIT asset manager does not need to know what the chiller outlet temperature was at 2:47 PM on a Tuesday three weeks ago. They need to know whether energy performance is improving or deteriorating, where the biggest variances are concentrated, and what intervention would produce the most cost impact before the next reporting period.
Those are different questions. And the BMS dashboard, as it was designed, was never built to answer them.
The FM team ends up doing one of two things. Either they export raw BMS data into a spreadsheet and spend engineering hours trying to manually construct a picture, or they wait until the utility bill arrives and work backwards from the invoice total. Neither approach is proactive. Neither approach surfaces the problem before the cost has already been incurred.
The tenant complaint model compounds this. FM teams throughout the region describe a reactive cycle: a tenant calls to say the office is too hot, an engineer is dispatched, the VAV is adjusted, the complaint stops. A different tenant on another floor calls the following week. The underlying pattern, that the entire HVAC zoning strategy no longer reflects actual floor usage, is never identified because the team is too busy responding to individual complaints to step back and read the system as a whole.
What a Monthly Clarity Report Actually Looks Like
The contrast between a standard BMS dashboard export and a building owner’s monthly clarity report illustrates the gap precisely.
A typical BMS export for a medium-sized commercial building might be a forty-column CSV file containing timestamped sensor readings across all monitored points. It is complete. It is accurate. And it is essentially unreadable without significant processing. An FM engineer familiar with the building can navigate it. A property investor reviewing the asset quarterly cannot.
A monthly clarity report for the same building presents a different picture entirely. It opens with a single-page energy performance summary: total consumption for the month, variance against the same period last year, variance against the benchmark established at commissioning. It then breaks consumption down by system category, HVAC, lighting, vertical transport, auxiliary loads, and flags which category has moved outside its expected band.
The second section covers occupancy correlation. If the building has people-counting data from turnstiles or CO2 sensors, the report plots occupancy load against HVAC energy draw and highlights the hours where the system consumed more than the occupancy justified. These become the target windows for schedule optimisation.
The third section presents two or three specific recommendations, ranked by estimated cost impact, each with a proposed action, a responsible party, and a target completion date before the next report. Not forty columns of raw data. Three decisions.
The final section covers tenant comfort indicators: the number of comfort complaints logged, the average response time, and whether the complaints cluster on specific floors or times of day. A clustering pattern is a signal. A random distribution is a baseline.
The difference between these two documents is not the underlying data. The data is the same. The difference is the interpretive layer that sits between the sensors and the stakeholder.
What the First Ninety Days Reveal
Property developers, REITs, and FM service companies that address operational blindness in their buildings describe a consistent pattern of discovery in the first three months.
In the first thirty days, the primary value is visibility. For the first time, the building owner or asset manager can see energy consumption broken down by system and floor, correlated against occupancy, and compared against the original design intent. For many buildings, this is the first time the gap between what the BMS was commissioned to deliver and what it is actually delivering has been quantified. The number is rarely flattering.
In the second month, the first set of schedule and setpoint changes takes effect. HVAC start times are adjusted to reflect actual occupancy patterns rather than assumed ones. Lighting control schedules are updated. Chillers are staged differently during low-occupancy afternoons. The energy impact of these changes begins to appear in the consumption data, and for the first time the FM team has evidence that their decisions are producing measurable outcomes.
By the third month, the reactive complaint cycle begins to shift. Because the FM team is reading floor-level comfort patterns proactively, many issues are identified and corrected before tenants experience them. Complaint volumes drop. The FM service company can demonstrate, in writing, that their intervention produced that outcome.
For a REIT managing a portfolio of commercial assets, this means the conversation with asset managers changes. Instead of presenting a utility invoice and a complaint log, the FM provider presents a monthly clarity report showing energy performance trends, optimisation actions taken, and a quantified estimate of the savings produced by those actions. The building is not just instrumented. It is interpreted.
The Question Worth Asking Before the Next Bill Arrives
For every property developer, REIT portfolio manager, or FM service company reading this: the building management system in your asset is almost certainly generating data that has never been fully used. The sensors are running. The logs exist. The gap is not in the technology. The gap is between what the system records and what your team is actually able to act on within a billing cycle.
The question worth sitting with is not whether your building is smart. It is whether the people responsible for operating it are receiving information in a form they can use to make decisions before the cost is already booked.
FAVORIOT works with property owners, FM companies, and facilities teams to build the interpretive layer that turns BMS data into monthly clarity reports, occupancy-correlated energy analysis, and proactive maintenance signals. If the quarterly energy bill is still moving in the wrong direction despite a fully installed BMS, that is a conversation worth having.
Schedule a consultation with the FAVORIOT team at favoriot.com/contactus and start building the picture your building has always been trying to show you.
Dr. Mazlan Abbas is the CEO of Favoriot, an IoT platform company focused on helping organisations in ASEAN turn operational data into decisions. He writes on IoT strategy, AIoT deployment, and the future of intelligent infrastructure at iotworld.co.
Leave a Reply