How one issue moves from detection to verified outcome.
Follow a single operational issue — from the moment Mobius detects it through to measured, verified proof that the problem was resolved.
Step 1
Data enters from trusted infrastructure
Before anything is detected, Mobius needs a foundation. It connects directly to national energy data infrastructure — half-hourly settlement records across every meter point in a portfolio. No hardware. No supplier feeds. No site visits.
National settlement data
Half-hourly interval reads from trusted infrastructure
BMS & sub-metering
Connects where available for deeper granularity
Billing & contracts
Tariff and supplier data for cost validation
No hardware to begin
Portfolio baseline delivered without site visits
With this foundation in place, Mobius continuously monitors every meter point in the portfolio. Here is what happens when it finds something.
Step 2 — Real Example
AHU scheduling drift — Building 7, Zone B
A real issue, moving through the full Mobius loop from detection to verified outcome.
AHU units running 14 hours outside occupancy
Mobius identifies that AHU scheduling in Zone B does not align with occupancy patterns. The detection is based on half-hourly interval data from the national settlement record — not a BMS alert, not a site visit.
Source: National settlement data
Estimated NOI impact: £42,000 per year
The issue is automatically ranked against every other opportunity in the portfolio. At £42,000 estimated annual impact with low resolution complexity, it sits at position #1.
Ranked #1 of 47 open opportunities
FM team assigned — due 15 March
The action is pushed into the existing CAFM system. The FM team receives a specific task: correct AHU scheduling in Building 7, Zone B. The task has an assigned owner, a due date, and escalation rules.
Owner: J. Harris · CAFM ref: WO-4471 · Escalation: 5 days
Schedule corrected in BMS
The FM team adjusts the AHU schedule to align with occupancy. The work order is completed and marked closed in the CAFM system. Mobius records the completion timestamp.
Completed: 12 March · 3 days ahead of deadline
£42,000 annual saving confirmed against baseline
Mobius measures post-intervention consumption against the pre-intervention baseline using the same national settlement data. The reduction is real, measured, and traceable — not estimated, not modelled.
Verified saving: £42,000 · Method: measured baseline comparison
Why This Works
The action did not sit in a dashboard. It moved through workflow.
In the example above, J. Harris did not log into a portal to find the issue. The task arrived in the system they already use, with a clear brief, a deadline, and consequences if it slipped.
Named owner
Every action is assigned to a specific person — not a team inbox
Due date
Clear deadlines that are tracked and enforced
Escalation
Overdue actions escalate automatically to senior stakeholders
Existing tools
Actions route into CAFM, BMS, or maintenance systems already in use
The Proof
The £42,000 saving was not claimed. It was measured.
After the AHU schedule was corrected, Mobius continued monitoring the same national settlement data. The pre-intervention baseline was compared to post-intervention actuals. The saving is real, traceable, and ready for reporting.
Verification Summary — Building 7, Zone B
Issue
AHU scheduling drift
Pre-intervention baseline
National settlement record
Action taken
Schedule corrected in BMS
Completed
12 March — 3 days ahead of deadline
Verified saving
£42,000 per year
Method
Measured baseline comparison
Status
Diligence-ready