Integrations
BMS integrations: Explore reads what you already run.
Siemens in one building, Schneider in the next, a twenty-year-old estate at the back of the portfolio. FrostLogic Explore connects to each of them read-only and returns one ranked queue of what to fix.
Book a time directly- Read-only
- No hardware
- EU-hosted
Three ways in
How Explore connects.
Every integration lands in the same place: a read-only feed into Explore. What varies is the route.
The vendor's cloud API.
Your BMS vendor's cloud is already running? Then the integration is credentials: a client ID, a token, done. Data usually flows the same day.
An agent on the existing PC.
No cloud anywhere? A small software agent on the BMS PC or server reads the system over BACnet, OPC UA or Modbus and syncs to Explore. Installed remotely, usually in an afternoon, and nothing new goes into the building.
Or we build the connector.
Running something we haven't met yet? We build the connector, usually in under a week. That covers the long tail of regional and legacy systems.
By vendor
Start with your BMS.
Siemens Desigo
Explore reads Desigo estates over BACnet or a local agent, whatever their generation.
Schneider EcoStruxure
Cloud or on-prem. One agent install covers the estates that never bought the cloud tier.
Honeywell Niagara
Explore reads any Niagara station without touching the wire sheet.
Trend, Bastec and the rest
Anything that speaks BACnet, Modbus, OPC UA, MQTT or M-Bus connects the same way. Something else? We build the connector.
One copy of your data
Skip the data-aggregator middleman.
A pattern we keep meeting: a portfolio hires one vendor to move BMS data into a cloud, then shops for an analytics vendor to make sense of it. Two contracts, two integrations, and the same data stored twice. Explore is the aggregator. It pulls from the BMS directly, stores one copy in the EU, and does the analysis in the same place. When you leave, the data and the models leave with you.
What happens after the connection is the platform's job: detection, forecasting and ranking are covered on the FrostLogic Explore platform page, and running it across many buildings on portfolio-wide BMS analytics.
Before you ask
BMS integrations, the questions we get.
No, it's the normal case. Most estates we meet run a capable BMS with no cloud subscription at all. A small agent on the existing BMS PC reads the system locally and syncs read-only to Explore. The licence that lapsed in 2019 doesn't need renewing.
No. The connection is software: the vendor's cloud API where one exists, an agent on the existing PC where one doesn't. Nothing gets mounted, wired or certified.
No. Explore connects read-only by default. It tells you what to change and what the change is worth; your team makes the change in the BMS. What-if simulation happens in Explore's model of the building, never on the live system.
Cloud API connections usually flow the same day. An agent install is typically an afternoon, done remotely. A connector we've never built before takes about a week. The slow part is rarely the technology; it's finding the person with the password to the plant-room PC.
Siemens, Schneider, Honeywell, Trend and Bastec cover most of what we meet, plus anything speaking BACnet, Modbus, OPC UA, MQTT or M-Bus. If you run something regional or old, tell us what it is. Odds are we've met something stranger.
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 read-only. Senior engineer on the review call.
See what your BMS already knows.
A 20-minute demo on your own building's data. Senior engineer on the call, no procurement round.