FDD vs DDM isn’t really a case of the industry disagreeing on definitions. Fault detection and diagnostics (FDD) and data driven maintenance (DDM) are both well understood capabilities among specialists, the real issue is that most building owners don’t know DDM properly exists as an option, and a lot of vendors claiming to offer it don’t have the depth to actually deliver it. This article sets out what each layer actually does, and how to tell genuine DDM from a label stuck on top of a basic ticketing system.
Key facts
- FDD identifies and explains a fault. DDM decides what to do about it, who should act, how urgent it is, and confirms afterward that the fix actually worked.
- Many platforms that market themselves as offering DDM stop at simple asset scoring or a basic ticket, without root cause diagnostics, cost quantification, or a verification step behind it.
- Genuine DDM requires real depth, accurate fault diagnosis, severity and cost ranking, clear assignment, and confirmation the issue is actually resolved, not just logged.
- DDM goes by different names in different regions and industries, condition based maintenance (CBM) in the UK and Europe, predictive maintenance (PdM) in North America, and Smart Maintenance across parts of Asia. All describe the same underlying shift, using real data instead of a fixed calendar to decide when maintenance happens.
- A BMS alarm is not FDD, and a work order generator is not DDM. Both require genuine analytical depth behind them to be worth the name.
FDD vs DDM - What is the actual difference between Fault detection and diagnostics (FDD) and data driven maintenance (DDM)?
FDD is the analytical layer, it scans building data and tells you what’s wrong, where, and why. DDM is the operational layer, it takes that diagnosis and turns it into a specific, prioritised, assigned action, then checks the fix actually worked.
Put simply, FDD’s output is an insight. DDM’s output is a completed, verified task. A platform that only does FDD will hand a facilities team a list of faults and leave the interpreting, prioritising, and follow up to them. A platform that does DDM properly turns that same list into a work order that says exactly what’s wrong, how much it’s costing, how urgent it is, and confirms the job is actually done once someone acts on it.
Why do so many vendors claim DDM without actually delivering it?
Because DDM sounds achievable to describe and much harder to build properly. Producing a fault list is one thing, producing accurate root cause diagnosis, ranking it by real cost and urgency, routing it to the right person, and then verifying the fix held, is a materially harder engineering problem, and it shows in how thin some vendors’ version of DDM actually is.
Looking across the market, there are genuinely three different levels of depth being sold under the same label. Some platforms don’t attempt DDM at all, they generate a fault list and stop there, leaving prioritisation and follow up entirely to the building’s own team. Others, often mechanical services or BMS controls firms, offer a version of DDM that’s little more than a basic scoring exercise or a maintenance contract with a new name, no real root cause logic, no verification loop, no proof the fix worked. A smaller group build the full closed loop properly, detection through to a verified, completed action, and that’s a meaningfully different product to buy, even when the marketing sounds similar.
For a buyer, the practical takeaway is to ask what’s actually behind the label. Does the platform explain why a fault happened, or just that something is out of range? Does it rank issues by real cost and urgency, or just list them in the order they were found? Does it confirm afterward that the fix worked, or does the ticket just get marked closed? Those three questions separate genuine DDM from a relabelled alarm feed.
Is DDM the same as condition based maintenance or predictive maintenance?
Yes, at their core. DDM, condition based maintenance (CBM), predictive maintenance (PdM), and Smart Maintenance all describe the same underlying idea, using real operating data rather than a fixed calendar to decide when maintenance should happen. The differences are regional habit and formality, not four separate technical approaches.
CBM is the older, more formal reliability engineering term, common in the UK and Europe and used well before smart buildings existed, applied just as often to industrial machinery as to HVAC. PdM is the North American equivalent and is technically a small step further, forecasting a future failure rather than just reacting to a current condition crossing a threshold, though in practice most people use CBM and PdM interchangeably.
Smart Maintenance is more of a regional marketing label common across parts of Asia, roughly equivalent to DDM or PdM but branded for a broader smart building conversation. A related but broader term, Asset Performance Management (APM), shows up in investment and REIT contexts, treating CBM, PdM, and FDD as components inside a wider asset lifecycle and financial strategy rather than a maintenance method in its own right.
Bueno uses DDM consistently across its own material for this reason, it’s the clearest, most building specific term of the group, but readers searching under any of these regional names are asking exactly the same question.
FDD vs DDM - How is DDM different from a BMS alarm system?
A BMS alarm and genuine DDM sit at opposite ends of the same spectrum, and the gap between them is where FDD does its work. A BMS alarm triggers on a simple threshold and generates a large volume of unfiltered noise, which is why building engineers are used to a constant stream of low value alerts.
FDD sits above that noise, filtering, correlating, and root causing it down to a manageable list of real issues. Genuine DDM then takes that filtered list and does what a raw alarm, or a shallow DDM label, never does properly, ranks it by real cost and urgency, assigns it to the right person, and confirms afterward that the fix actually worked. A building relying on BMS alarms alone has visibility but no prioritisation or follow through. A building relying on a thin, relabelled version of DDM often has the appearance of a solution without the depth behind it.
Bueno’s own platform is built around the full progression done properly, FDD identifies the fault, DDM turns it into a tracked, verified action, and a further optimisation layer uses that same data to improve how the whole building runs, not just one asset at a time. For a closer look at how that progression works in practice, see Bueno’s DDM solution overview and fault detection and diagnostics page.
So when it comes to understanding the difference between FDD vs DDM, Bueno can help.
Talk to Bueno about FDD vs DDM
Want to know more about FDD vs DDM? Contact Bueno for a demonstration of how genuine FDD, DDM, and building optimisation work together in a single platform, not a fault list with a maintenance label stuck on top.
