Johnson Controls Metasys integration
Johnson Controls Metasys analytics, from the BMS you already run.
Explore connects to your Metasys estate, whatever its generation, and returns one ranked queue: what to fix first, where, and what it costs to wait.
Book a time directly- Writes only where you allow
- Works across Metasys generations
- EU-hosted
The problem
The plant-room UI nobody opens until it fails.
A Metasys system does its job. It runs schedules, holds setpoints, raises alarms. But Johnson Controls Metasys analytics, as most estates actually run it, is a Site Management Portal or Metasys UI screen in the plant room, plus trend logs that stay closed until something has already failed.
Explore reads those same 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. Metasys keeps control of the building. You finally get to see what it knows.
What it does
From Metasys points to a ranked queue.
Anomaly detection on live Metasys data.
Six detection methods run on the points Metasys already trends: temperatures, valve positions, runtimes, energy. A compressor drifting out of its envelope shows up days before the alarm would have fired.
Faults ranked by cost, not noise.
Metasys raises alarms by rule. Explore weighs findings by money, comfort and compliance, so the queue starts with what matters rather than what is loudest.
Forecasts with confidence bounds.
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 system.
Compliance evidence, continuously.
BREEAM, LEED, Nordic Swan and EPBD evidence assembled from data Metasys produces anyway, instead of at audit time.
Deployment
Three routes into a Metasys estate.
BACnet, natively.
Metasys supervisory devices (NAE, SNE, SNC, OAS and related) speak BACnet. The FrostLogic Edge Agent on the existing management PC reads the points and pushes them to Explore. Installed remotely, usually in an afternoon. Station and supervisory logic stay untouched.
Cloud or server path where you have it.
Estates already exposing data through ADX, ADS or a cloud path connect with credentials, and data can flow the same day.
The old estate.
Commissioned years ago, never upgraded, licence quiet. Still connectable if a PC can reach the BMS network, and that is about it.
The question every Metasys estate asks
OpenBlue already has analytics. Why Explore?
One model across every vendor.
OpenBlue and Metasys tools see Johnson Controls. Real portfolios mix Metasys with Siemens, Schneider, Niagara, meters and retrofits. Explore normalises all of it into one queue.
Physics, not a chatbot.
FrostDynamics checks every finding against the building thermodynamics before it reaches your queue. Pure pattern tools cannot do that.
Nothing to rip out.
Keep OpenBlue or the Metasys UI where they earn their keep. Explore reads alongside; connecting is not a migration and does not need a rip-and-replace integrator project.
At a glance
- Works with
- Metasys UI / Site Management Portal estates, mixed Johnson Controls generations that expose points
- Connection
- BACnet via local FrostLogic Edge Agent, or cloud / ADX-ADS path where available
- Write access
- off by default, granted per scope
- Hardware
- none
- Data residency
- EU, GDPR-native
- First findings
- in the first week
- Also reads
- meters, IoT sensors, and the non-Metasys buildings in your portfolio
Running Siemens, Schneider or Niagara alongside Metasys? Explore reads Desigo, EcoStruxure and Niagara into the same model, and ranks across all of it with portfolio-wide BMS analytics. The analytics layer itself lives on the FrostLogic Explore platform page.
Before you ask
Johnson Controls Metasys analytics, the questions we get.
No. Metasys keeps running the building. Explore adds detection, forecasting, ranking and evidence. Nothing about your BMS setup changes.
Yes. The FrostLogic Edge Agent on the existing management PC reads the system over BACnet and syncs to Explore. You do not need a BMS cloud subscription or new hardware.
Anything that exposes points over BACnet, or a documented cloud or server path. Tell us if yours is unusual.
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. Metasys stays the control layer.
One. Explore normalises mixed estates into a single model and one queue. Mixed portfolios are the normal case, not the exception.
One building, three weeks. The agent goes in remotely, data accumulates, and we walk you through what Explore found. If the queue is not worth your time, you have lost three weeks.
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.
What's your building not telling you?
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.
Johnson Controls, Metasys and OpenBlue are trademarks of Johnson Controls International plc or its affiliates. FrostLogic is an independent vendor and is not affiliated with or endorsed by Johnson Controls.