Most FM teams will tell you they are moving toward smarter, more data-driven maintenance. Sensors are going in, systems are being connected, dashboards are being built. Somewhere in that process, predictive maintenance became the goal.
Predictive maintenance is not the end goal. It is a milestone, and there is a next stage that most organizations in the industry have not seriously thought through yet. The gap between where FM currently operates and where it needs to go is wider than most leaders are willing to admit.
Still largely reactive
Maintenance in most buildings starts when something breaks, when a user complains, or when an inspection catches a problem that has already been developing for weeks. The conditions that keep this the default are still very much in place across the sector: fragmented data, limited budgets, and systems that do not talk to each other.
This is the operational reality for a large part of the sector, including organizations that consider themselves ahead of the curve. That observation tends to land differently when you are sitting in a strategy meeting talking about smart buildings.
Four levels that are not the same thing
Reactive maintenance is run-to-failure. An asset stops functioning, someone responds, and the system is restored. Most buildings spend more time here than their managers would like to admit.
Preventive maintenance adds a schedule that is calendar-driven and interval-based. It reduces surprises, but it creates a different problem, because you end up replacing components that still have useful life left simply because the date says so.
Condition-based maintenance changes the trigger. Instead of the calendar, you use the actual condition of the asset, and measurement decides when intervention is warranted. This is where a lot of organizations think they have arrived once they have installed sensors and built a dashboard. Most of the time, they have not.
Predictive maintenance is a different thing entirely. The standard definition describes it as condition-based maintenance performed on the basis of a forecast derived from repeated analysis of significant degradation parameters. A sensor telling you the temperature is too high right now is condition monitoring. A system telling you a component is likely to fail in the next three weeks, based on its degradation trajectory, is predictive maintenance. Most organizations conflate the two, and that confusion is expensive.
The groundwork most organizations want to skip
Treating the gap between reactive and predictive as a technology problem is the most common mistake organizations make. The technology is rarely the bottleneck.
The real obstacles are far more mundane. Maintenance histories were never properly recorded, and building automation systems do not connect to maintenance management platforms. Technicians notice things in the field that never make it into any system at all. Models that work well in one building fall apart in another, because the occupancy patterns or the climate differ enough to break the assumptions they were built on.
What holds predictive maintenance back in practice is the heterogeneity of the data and the distance between research conditions and real-world deployment, not a shortage of algorithmic sophistication. Organizations that fail at this transition usually did not pick the wrong software. They skipped the groundwork.
It starts with the assets that hurt when they fail
HVAC is the most defensible place to begin, because it is energy-intensive, always running, and directly tied to comfort and air quality. Faulty HVAC operation can drive 20 to 30 percent excess energy consumption, and that is a cost being paid every month by organizations that believe they are reasonably in control.
Applied to HVAC, predictive algorithms show real potential, and the constraints are just as real: data quality, model transferability, and the difficulty of validating predictions in a live environment. The workable route is to pick a small number of assets where failure has real consequences for energy, comfort, or continuity. Build the data infrastructure there first, get the feedback loops working, and expand from there.
Beyond prediction
Predictive maintenance tells you what is likely to happen. Prescriptive maintenance tells you what to do about it, factoring in technician availability, scheduling constraints, cost trade-offs, and contract obligations. It does not stop at the forecast but produces a recommendation.
The distinction matters more than it might seem. Prescriptive maintenance folds predictions into a wider maintenance plan, while predictive approaches stop at the failure probability. Industrial manufacturing has already demonstrated this, connecting maintenance directly to production planning and resource allocation in real time. That is not FM, but the direction is clear.
Where prescriptive maintenance stands today is easier to describe. Interest is growing fast while deployment remains limited, held back by interoperability issues, real-time optimization demands, and scalability constraints. For buildings specifically, it is mostly still conceptual, with a handful of pilots. That will change. The question is which organizations are building toward it deliberately, and which will still be catching up on predictive maintenance when it does.
A lag that is built in
Buildings are generating more operational data than ever, and the analytical capability to use it keeps improving. What is not keeping pace is the organizational capacity to act on what the data reveals.
Prescriptive maintenance can be understood as predictive maintenance with an action-planning layer on top, and that layer is demanding both technically and organizationally. FM decision structures were designed for scheduled maintenance and reactive repair. They were not built to absorb continuous data streams and turn probabilistic forecasts into coordinated operational decisions.
That is not a criticism of the people running these organizations. It is a description of a design that made sense for a different era. The problem is that the era is shifting faster than the structures are.
Three questions for you
For the ten most critical assets under management, do you know when each was last serviced, what its current condition is, and when it will likely need attention next? Not roughly, but with enough certainty to base a decision on.
Is the maintenance history of your portfolio recorded in a way a system can actually learn from? Or does the knowledge of how your assets behave and fail live mostly in the heads of people who will retire in the next several years?
Who in your organization owns the connection between building data and operational decisions? Not the BMS or the CMMS, but the underlying question of what your buildings know and what happens with that knowledge.
If those answers are vague, the distance to prescriptive maintenance is longer than the roadmap suggests, and it does not close on its own.
Originally published on LinkedIn.