Bastec integration
Explore connects to your Bastec estate over Modbus or M-Bus and returns one ranked queue: what to fix first, where, and what it costs to wait.
Book a time directlyThe problem
Bastec BAS3 and BAS2 controllers (XU16, XL13, XE16 and kin) run a large share of Swedish commercial estates from Malmö outward. Bastec analytics, as most sites actually run it, is a station screen in the plant room and trend logs that stay closed until something has already failed. Operators who also use BASTEC Cirrus, BASTEC Smart or BASTEC Elspot keep those tools; they stay theirs.
Explore reads those same Modbus or M-Bus points continuously. Every finding is grounded in the physics of your building by FrostDynamics, our world model, and lands in one queue, ranked by what ignoring it costs. BAS3 and BAS2 keep control of the building. You finally get the analytics layer on the same data.
What it does
Seven detection methods run on the points BAS3 and BAS2 already trend: temperatures, valve positions, runtimes, energy. A compressor drifting out of its envelope shows up days before the alarm would have fired.
Demand and consumption forecasts per building, checked against the physics. What-if simulation tests a setpoint change in the model before anyone touches the live station.
Bastec sites next to Siemens, Schneider, Trend or meters. Explore normalises them into one model and ranks findings by what ignoring them costs.
Smart Schedules and permissioned setpoint changes stay off until you grant a scope. Outside that scope, nothing moves. The Bastec station stays the control layer.
Deployment
BAS3 and BAS2 expose Modbus TCP/RTU (client and server) and M-Bus on the controllers you already run. The FrostLogic Edge Agent on the existing PC or server reads the points, and writes back to the points you have granted it. Write starts off. Installed remotely, usually in an afternoon. No new plant-room hardware. Not Niagara.
The FrostLogic Edge Agent sits beside the BAS3, BAS2 or plant-room PC you already have, reads your BMS, meters and sensors over Modbus and M-Bus, and writes back only where you grant a scope.
Estates already exposing data through a credentials path connect the same day. Mixed portfolios that also run non-Bastec buildings land in the same feed.
The question every Bastec estate asks
BASTEC Cirrus, BASTEC Smart and BASTEC Elspot are Bastec's own cloud and EMS tools. If you already use them, keep them. Explore is the analytics layer on the same Modbus or M-Bus data: detection, forecasting and a portfolio queue those tools were never built to own across mixed vendors.
A BAS3 or BAS2 station sees the sites it was commissioned for. Real portfolios mix Bastec with Siemens, Schneider, Trend and meters. Explore normalises all of it into one queue.
FrostDynamics checks every finding against the building thermodynamics before it reaches your queue. Pure pattern tools cannot do that across the estate.
At a glance
Bastec is one route in. Explore also reads Siemens Desigo, Schneider EcoStruxure, Honeywell Niagara, Distech Controls, Johnson Controls Metasys, Kieback&Peter, Regin and Honeywell Trend into the same model, ranked with portfolio-wide BMS analytics. The analytics layer itself lives on the FrostLogic Explore platform page.
Before you ask
Yes. The FrostLogic Edge Agent on the existing PC or server reads your BMS, meters and sensors over Modbus or M-Bus, and writes back to the points you have granted it. Write starts off. You do not need a BMS cloud subscription or new hardware.
No. The connection is software: an agent on the existing BAS3, BAS2 or plant-room PC. Nothing gets mounted, wired or certified.
Yes, once you turn it on. Write access starts off. You grant it one scope at a time, and Explore proposes the change with its reasoning and the expected effect before anything moves. You choose whether that proposal waits for someone to approve it, or runs automatically inside the scope you set. Points outside that scope stay untouched. The Bastec station stays the control layer.
An agent install is typically an afternoon, done remotely. Where a credentials path already exists, data can flow the same day. The slow part is rarely the technology; it is finding the person with access to the plant-room PC.
BAS3 and BAS2 over Modbus and/or M-Bus, including controllers such as XU16, XL13 and XE16. If your Bastec generation exposes points the agent can read, Explore connects. Tell us what you run if you are unsure. BASTEC Cirrus, Smart and Elspot stay yours if you keep them.
No. FrostLogic is independent. We are not affiliated with or endorsed by Bastec. Explore connects to the BAS3 or BAS2 estate you already run.
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.
Tell us what you're trying to figure out: energy drift, a BMS you don't trust, compliance you're chasing. We listen first, then tell you straight whether Explore helps. 30 or 60 minutes, your pick. No commitment either way.
Bastec, BAS3, BAS2, BASTEC Cirrus, BASTEC Smart and BASTEC Elspot are trademarks of their respective owners. FrostLogic is an independent vendor and is not affiliated with or endorsed by Bastec.