backicon

Why Xempla Is Not a CMMS

Published by :

June 12, 2026

by

Anisha Bhattacharjee

A CMMS records maintenance activity. Xempla is a System of Decisions that discovers anomalies, investigates root causes, implements the right interventions, verifies outcomes, and governs how operational decisions are made, whether they deliver the intended result, and what happens when they do not. That is not the same thing, and the difference matters more than it might seem.

Most facilities organisations today do not suffer from a lack of maintenance records. They suffer from a lack of visibility into whether maintenance decisions are actually working.


What a CMMS does

A Computerised Maintenance Management System (CMMS) is a system of record. It stores work orders, schedules preventive maintenance, tracks asset histories, and documents what happened, when, and by whom. CMMS platforms are essential to modern FM operations, but a completed work order only confirms that work occurred. It does not tell you whether the work was necessary, whether it addressed the root cause, or whether asset performance improved as a result. That gap between activity and outcome is where most facilities teams struggle.


What a System of Decisions does

A System of Decisions is an intelligence layer that discovers anomalies, investigates underlying causes, implements prioritised interventions, verifies outcomes, and governs how operational decisions are made across an asset portfolio. It covers how decisions are made, whether they deliver the intended result, and what happens when they do not.

Xempla is built on this model, sitting above existing CMMS, BMS, IoT, and ERP systems and continuously monitoring operational signals. Its purpose is not to create another source of operational data. It is to ensure that the right decisions are being made, at the right time, on the right signals, and that they are producing the outcomes they were intended to achieve.


How Xempla operationalises this

Through the DIIV Cycle : Discover, Investigate, Implement, Verify

Discover — AI agents continuously monitor operational signals across connected systems, surfacing anomalies and emerging risks before they escalate into failures.

Investigate — The root cause behind each anomaly is examined, not just the symptom, so that the right intervention is identified rather than the most obvious one.

Implement — Actions are executed with full traceability between the original signal, the investigation, and the operational response.

Verify — Xempla evaluates whether the intervention produced the expected outcome. If it did not, the loop closes, the decision is reassessed, and the cycle improves.

Most FM systems stop at implementation. Xempla continues to verification, and that is what determines whether an organisation learns from its decisions or merely records them.


The Assurance Score: making governance visible

Governance is only useful if it is measurable. Xempla's Central Assurance Score continuously evaluates operational health across facilities and locations, distilling complex FM signals into a single, auditable indicator of decision quality. Rather than surfacing raw metrics that teams must interpret, it answers a simpler question: are your assets and sites performing as they should be? This is how facilities teams move from assuming work is working to knowing it is.

Viewable at the individual asset level and the wider site level, it gives facilities teams, asset owners, and leadership a shared, real-time measure of portfolio health, making governance visible rather than assumed.


Three differences that matter

Activity vs. outcome - A CMMS measures whether work was completed. Xempla measures whether it worked.

Execution vs. governance - High PM completion rates can coexist with recurring failures and rising costs. Execution alone does not guarantee performance improvement. Governance closes that gap.

Data vs. decisions - A CMMS presents information that teams must interpret. Xempla surfaces prioritised recommendations with humans in the loop for judgement, not burdened with first-pass analysis of fragmented operational data.


The right question to ask

Most organisations ask: does our CMMS have AI features?

A more important question is: do we have a system that governs how operational decisions are made across our assets  and closes the loop when those decisions fail?

Facilities performance is not a record-keeping problem. It is a decision-making problem. A CMMS records maintenance activity. Xempla is a System of Decisions that discovers anomalies, investigates root causes, implements the right interventions, verifies outcomes, and governs how operational decisions are made, whether they deliver the intended result, and what happens when they do not. That is why it is not a CMMS.


FAQs

What is the difference between a CMMS and a System of Decisions?

A CMMS is a system of record that documents maintenance activity, work orders, and asset histories. A System of Decisions is an intelligence layer that discovers anomalies, investigates root causes, implements prioritised interventions, verifies outcomes, and governs how operational decisions are made across an asset portfolio, covering whether they deliver the intended result and what happens when they do not.

Is Xempla a replacement for my existing CMMS?

No. Xempla sits above your existing CMMS, BMS, IoT, and ERP systems and does not replace them. It acts as the intelligence and governance layer above the record layer, using signals from connected systems to ensure that decisions being made using that data consistently improve reliability, compliance, cost performance, and service outcomes.

What is a System of Decisions?

A System of Decisions is an intelligence layer that discovers anomalies, investigates root causes, implements prioritised interventions, verifies outcomes, and governs how operational decisions are made across an asset portfolio. Xempla is built on this model, structured around the DIIV Cycle: Discover, Investigate, Implement, Verify.

What is the DIIV Cycle?

The DIIV Cycle is Xempla's operational framework. It discovers anomalies before they escalate, investigates root causes to identify the right intervention, implements actions with full traceability, and verifies whether those actions produced the expected outcome, closing the loop when they did not.

What is the Central Assurance Score?

The Central Assurance Score is Xempla's continuous measure of operational health across facilities and locations. It distils complex FM signals into a single, auditable indicator of decision quality, viewable at the individual asset level and the wider site level, giving FM teams, asset owners, and leadership a shared view of portfolio health. It is how facilities teams move from assuming work is working to knowing it is.

Why does verification matter in facilities management?

Most FM systems stop at implementation. A work order is closed and the activity is recorded, but no one evaluates whether the intervention actually worked. Verification asks whether the fault recurred, whether reliability improved, and whether the decision reduced cost or service disruption. Without it, organisations record decisions but never learn from them.

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Paragraph

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Bold text

Emphasis

Superscript

Subscript

More ShortBytes

The Central Assurance Score: The FM KPI Beyond SLA

SLA tells you the work was done. It does not tell you whether it actually made a difference. In facilities management, that distinction matters ...

What Happens to Recurring Asset Problems After One Year of Autonomous Maintenance?

After one year of Autonomous Maintenance operations, recurring-problem assets drop, and the ones that remain turn out ...

What Is an Assurance Score in Facilities Management?

An Assurance Score in facilities management (FM) is a real-time measure of an asset's health, expressed as a single signal ...