---
title: Predictive maintenance platform that tells you which asset to fix first
canonical: "https://www.frostlogic.se/platform/predictive-maintenance/"
lastUpdated: 2026-11-14
twinOf: "https://www.frostlogic.se/platform/predictive-maintenance/"
---
# Predictive maintenance platform that tells you which asset to fix first

Explore reads the sensors and BMS points you already have, forecasts equipment behavior before it fails, and turns the result into one ranked queue — not another alarm stream.

> Last updated: 2026-11-14. Twin of https://www.frostlogic.se/platform/predictive-maintenance/.

## The model was never the hard part. Getting someone to act on its output is.

Most predictive-maintenance pilots don't fail because the anomaly detection is wrong. They fail because the output is another alert stream, and the team already ignores three of those. A vibration spike, a temperature drift, a runtime anomaly — each lands in its own dashboard, competing for attention with everything else that's already flashing red.

Explore starts from the actionability problem, not the detection problem. The [same detection engine that powers BMS analytics](/platform/bms-analytics/) runs seven anomaly-detection methods against every point continuously, then forecasts where each one is heading with a confidence bound — so a developing bearing fault or a refrigerant leak shows up days or weeks before it trips a threshold, not after.

The output isn't a feed. It's a ranked decision queue: one list, ordered by cost and risk, that tells a technician what to look at first — instead of a wall of equally-urgent alarms nobody has time to triage.

This page is the product view. The methodology behind it — why most predictive-maintenance projects stall, and the failure modes that actually show up in sensor data — is in [Predictive maintenance for buildings: a practical guide](/articles/predictive-maintenance-buildings/). How Explore stacks up against Clockworks, Facilio and CopperTree Analytics on this specific job is in [the vendor comparison](/articles/best-predictive-maintenance-software/). For where predictive maintenance ends and condition-based maintenance begins, see [the CBM guide](/articles/condition-based-maintenance/).

## Four capabilities, one ranked queue

### Seven-method anomaly detection

Every BMS point and connected sensor is checked continuously against seven detection methods, not one fixed threshold. Covers drift, stuck values, runtime anomalies, and pattern breaks a static alarm limit misses. Full mechanics are on the [anomaly detection](/glossary/anomaly-detection/) glossary entry.

### Forecasting with confidence bounds

Detection tells you something is already wrong. Forecasting tells you it's about to be. Explore projects equipment behavior forward with a confidence interval, so slow bearing wear or coil fouling surfaces while there's still time to schedule a fix instead of an emergency callout.

### One ranked decision queue

Findings are ranked by cost and risk and merged into a single queue — not scattered across a BMS alarm panel, a spreadsheet, and three inboxes. A technician opens one list and knows what to look at first.

### Write access starts off, action on request

**Write access starts off**. Findings can feed the Edge Agent to propose a maintenance action or schedule change — a person reviews it, or it executes automatically inside a scope you've explicitly granted. Nothing runs on your BMS without that scope.

## Raw alarms and a paper calendar vs. a ranked queue

Predictive maintenance platform: raw BMS alarms, manual PM schedules, and Explore compared

Raw BMS alarms

Manual PM schedule

Explore

Trigger

Fixed threshold breach only

Fixed calendar interval, regardless of condition

Condition and forecast, seven detection methods

Lead time

After the limit is already crossed

Arbitrary — unrelated to actual wear

Days to weeks ahead, with a confidence bound

Coverage

Only points with a hardcoded limit set

Only equipment on the PM calendar

Every point already in your historian

Prioritisation

None — every alarm is equally urgent

None — fixed schedule regardless of risk

Ranked by cost and risk, one queue

False positives

High — floods the operator

N/A, but wastes visits on healthy equipment

Filtered by confidence before it reaches the queue

New hardware

Usually none, but limited to already-sensored points

None

None — reads existing BACnet, Modbus, OPC UA, oBIX points

Path to action

Manual triage by an operator

Technician dispatched whether needed or not

Write access starts off; Edge Agent can propose or execute inside a granted scope

## The mechanics

A predictive maintenance platform in Explore isn't a separate module bolted onto a BMS dashboard — it's the same sensor-intelligence layer used for energy and BMS analytics, applied to HVAC and plant health.

Predictive maintenance platform

Software that reads sensor and BMS data to forecast equipment failure and rank the findings — instead of fixing on a calendar or waiting for an alarm.

Detection methods

Seven, run continuously against every connected point

Forecast horizon

Days to weeks ahead, with confidence bounds

Protocols read

BACnet, Modbus, OPC UA, oBIX — no new hardware

Output

One ranked decision queue, not a raw alert stream

Automation

**Write access starts off** — the Edge Agent acts only inside a scope you grant

Hosting

EU (Hetzner), GDPR-compliant

Inference

Grounded in your own data — nothing invented

## From sensor data to a ranked fix list

### Sensor and BMS data

01 — In

Explore reads points you already have over BACnet, Modbus, OPC UA, and oBIX. No new sensors, no new gateway hardware.

### Detection + forecasting

02 — Analyse

Seven anomaly-detection methods run continuously; forecasting projects each point forward with a confidence bound, catching developing faults before they trip a threshold.

### Ranked decision queue

03 — Out

Findings merge into one queue, ranked by cost and risk. **Write access starts off** — or feed the Edge Agent to propose and execute fixes inside a scope you've granted.

## Predictive maintenance platform, answered

### What does a predictive maintenance platform for buildings do?

A predictive maintenance platform for buildings reads BMS and sensor data, forecasts with a confidence bound when HVAC or plant is likely to fail, and ranks findings into one decision queue — so a fix can be scheduled before a breakdown. Explore's AI predictive maintenance does that from the points your BMS already has.

### How is this different from the alarms my BMS already generates?

BMS alarms fire after a fixed threshold is crossed — a temperature limit, a runtime cap. Explore forecasts where a point is heading with a confidence bound, so a developing fault can surface days or weeks before it would ever trip that threshold, and every finding lands in one ranked queue instead of a raw alarm panel.

### How is this different from a manual PM schedule or a CMMS?

A calendar-based PM schedule services equipment on a fixed interval regardless of actual condition — sometimes too early, sometimes too late. A CMMS owns work orders and history; Explore is Sensor Intelligence with a ranked queue, not a CMMS. Explore ranks findings by real condition and forecasted risk, so maintenance effort goes where it's actually needed first.

### What's the difference between predictive maintenance and condition-based maintenance (CBM)?

Condition-based maintenance triggers a maintenance action when a measured condition crosses a defined limit. [Predictive maintenance](/glossary/predictive-maintenance/) goes a step further and forecasts when that limit will be crossed, with a confidence bound, before it happens. Explore does both: continuous condition monitoring plus forward-looking forecasts, merged into one ranked queue.

### Does this need new sensors or hardware?

Usually not. Explore reads the points your BMS and existing sensors already expose over BACnet, Modbus, OPC UA, and oBIX. New hardware is only needed where a piece of equipment genuinely isn't instrumented yet.

### Can Explore act on what it finds, or is it just monitoring?

Write access starts off — Explore detects and forecasts, nothing more, until you say otherwise. Findings can feed the Edge Agent to propose a maintenance action or schedule change, which a person reviews, or which executes automatically inside a scope you've explicitly granted. It can't act outside that scope.

