Explore Analytics
Building management system software, turned into decisions.
Connect Siemens, Schneider, Honeywell, Honeywell Trend, Bastec, or anything BACnet, Modbus, OPC UA or oBIX. Explore reads from your existing BMS and returns a prioritised action queue. It's how teams run energy management systems for commercial buildings on the BMS they already have.
- Nothing to rip out
- No hardware
- One copy of your data, in the EU

How it works
From a BMS feed to ranked queue.
Your BMS
Siemens · Schneider · Honeywell · Bastec · Honeywell Trend
Ingest
BACnet · Modbus · OPC UA · oBIX
FrostDynamics engine
Anomaly · Forecast · Causal
Prioritised queue
What to act on. In what order.
The problem
Why most building management system software stops at the dashboard.
Monitor
Every anomaly, sorted by severity and kind.
- Seven detection methods over the data your building already produces
- Forecast deviation, energy spike, equipment health, sensor calibration
- Research it, open the metric or resolve it from the same card

Investigate
Actual, forecast and anomalies on one chart.
- Compare metrics across rooms and equipment
- A seven-day forecast with its likely range
- Anomalies and BMS writes marked on the timeline

Worked example
A single floor's HVAC drift, captured live.
- Sensor drift detected. A return-air temperature sensor on floor 4 starts drifting +0.4°C/day relative to the supply-air physics model. Statistical-only platforms miss it; physics-aware methods catch it on day three.
- Causal filter applied. Causal filtering connects the drift to elevated chiller cycling downstream, and suppresses the dozen related "alerts" the BMS would have fired.
- Ranked, assigned, resolved. Single ticket lands in the operator queue with severity "High" and suggested action "recalibrate or replace". Mean time to detect drops from weeks to days. Audit trail is captured automatically.

The question every vendor estate asks
Building Advisor already does analytics. Why add Explore?
Local-only BMS
No BMS cloud licence? You don't need one.
Most buildings run a capable BMS that was commissioned years ago and then left alone. The cloud subscription was never bought, or it lapsed quietly. So every data point the building produces sits on one PC in the plant room, and nobody above building level ever sees it.
Explore connects that PC. The FrostLogic Edge Agent goes on that machine, reads your BMS, meters and sensors over BACnet, OPC UA, Modbus or oBIX, and writes back to the points you have granted it. Write starts off; see Automation for how scopes work. Nothing new bolted into the building.
Skip the data-aggregator middleman too. Explore pulls from the BMS directly and stores one copy, in the EU. Not sure which of those protocols your estate actually runs? Our BACnet vs Modbus vs OPC UA guide breaks down the differences. For Edge Agent through queue and write-back, see How it works.
Missing one? Tell us what you run. Focused on energy specifically? See our energy management software.
Beyond HVAC
One queue for HVAC, IoT and every building monitoring system.
Before you ask
What teams ask about running this on their BMS.
Software that connects to a building's BMS and turns its raw points into something an operator can act on. Explore goes past monitoring: it ranks every issue by severity and likely cause, then proposes the fix.
No. It reads from your existing BMS, and adds an analytics and decision layer on top. It works with Siemens, Schneider, Honeywell, Honeywell Trend and Bastec, or anything speaking BACnet, Modbus, OPC UA or oBIX.
BACnet, Modbus, OPC UA, oBIX, MQTT and M-Bus, across Siemens, Schneider, Honeywell, Honeywell Trend and Bastec. If you run something else, tell us what it is.
Most built-in analytics stop at charts and threshold alarms. Explore cross-checks each signal against the building's physics, suppresses the alarm storms, and hands the operator one ranked queue instead of a wall of metrics.
The demo runs against a sample of your data. In production most teams see ranked findings in the first week, with no new hardware.
Yes. It reads the BMS and the IoT sensors layered on top (air quality, occupancy, sub-metering, leak and energy sensors over BACnet, Modbus, OPC UA, oBIX, MQTT and M-Bus) and ranks them in one queue. It adds nothing to the field.
Yes. HVAC is where most building telemetry and most avoidable cost sit. Explore grounds every HVAC signal in the plant's physics, so it catches drift and fighting setpoints the BMS's own thresholds miss.
A building monitoring system shows you charts and fires alarms. Explore goes one step further: it cross-checks each signal, suppresses the alarm storm, and returns a ranked list of what to fix first. Monitoring tells you what happened; Explore tells you what to do.
Building Advisor analyses your Schneider estate, and it does that fine. Explore reads your non-Schneider systems into the same model, grounds every finding in the building's physics instead of a language model's guess, and ranks the whole portfolio into one queue. It runs alongside Building Advisor, so there's nothing to rip out.
Most vendor assistants are a language model with access to your data. Ask one the wrong question and it will confidently suggest something physics forbids. We've seen one propose shutting off cooling at 30°C outside. Explore's reasoning runs through FrostDynamics, a world model of your building, which checks every answer against thermodynamics before you see it.
Yes. We install the FrostLogic Edge Agent on that PC or server, remotely, usually in an afternoon. It reads your BMS, meters and sensors, and writes back to the points you have granted it. Write starts off. There's no hardware, and no BMS cloud subscription needed, even on estates where the licence lapsed years ago.
No. Explore is the aggregator. It pulls from the BMS directly, through the vendor's cloud API where one exists or through a local agent where one doesn't, and stores one copy in the EU. Paying a middleman to move your own data first doubles the cost and adds a procurement round.
No. Explore connects through your vendor's cloud API, through the FrostLogic Edge Agent on the existing BMS PC, or through a custom connector we build when you run something unusual. Nothing gets bolted into the building.
One building, three weeks. We connect remotely, usually to a handful of units, let the data accumulate, and review what Explore found together. If the queue isn't worth your time, you've lost three weeks.
For Explore it means seven anomaly detection methods and forecasting run over the data your building already produces, and the output is a ranked queue of decisions with the evidence attached. Write access starts off. You grant write access one scope at a time, and you decide whether each change waits for a person or runs on its own.
A BMS is the control layer wired into a building's HVAC, lighting and metering: the Siemens, Schneider, Honeywell, Honeywell Trend or Bastec software and controllers that run the equipment, opening dampers, cycling chillers, switching lighting circuits. On its own it runs the building. It doesn't rank what needs attention or tell you what to do next. Explore adds that layer on top, reading the BMS and turning its raw points into issues ranked by severity and likely cause.
Connect one building. Three weeks. We show you what we find.
Pick one building, even a couple of fan coil units. We connect it remotely, let two to three weeks of data accumulate, then go through the findings with you. There's nothing to install and no commitment past the pilot. Remote, and it writes nothing until you grant it a scope.