Distech Controls integration
Distech Controls analytics, from the EC-Net or ECLYPSE station you already run.
Explore reads the points your Distech Niagara station already exposes and returns one ranked queue across the estate: faults, waste, and what fixing each is worth.
Book a time directly- Writes only where you allow
- No station changes
- EU-hosted
The problem
Open Niagara station, closed analytics path.
Distech EC-Net is a Niagara OEM. ECLYPSE sits in the same Distech family. Operators already have the station. What they lack is portfolio analytics that does not mean building wire-sheet logic per site or buying another dashboard that never sees the rest of the estate.
Explore connects through the Niagara station. It reads the points EC-Net or ECLYPSE already expose, grounds every finding in the building physics with FrostDynamics, and ranks the estate into one queue. The station keeps control. You finally get the analytics path the plant room never had.
What it does
From Distech station points to a ranked queue.
Detection without wire-sheet logic.
Seven detection methods run on the points the station already trends: temperatures, valve positions, runtimes, energy. Nobody has to build or maintain analytic logic per building.
Every station, one queue.
Distech sites next to Siemens, Schneider, Metasys or Trend. Explore normalises them into one model and ranks findings by what ignoring them costs.
Forecasts and what-if.
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.
Compliance evidence, continuously.
BREEAM, LEED, Nordic Swan and EPBD evidence assembled from data you already have, instead of at audit time.
Deployment
Through the Niagara station you already run.
Through the Niagara station.
Distech EC-Net and ECLYPSE estates that expose points through a Niagara station connect the same way as any other Niagara site. Explore reads those points over oBIX or BACnet via the FrostLogic Edge Agent alongside the station. Write starts off. The station path is the same as on the Honeywell Niagara page.
Agent beside the station.
The FrostLogic Edge Agent sits on the existing PC or server next to the Niagara supervisor, reads the points the station already exposes, and writes back only where you grant a scope. Station logic and the wire sheet stay untouched.
Points the station already trends.
No Distech-native cloud connector to invent, and nothing rebuilt on the wire sheet. If the station exposes the points, Explore reads them into the same ranked queue as the rest of the portfolio.
The question every Distech estate asks
We already have station analytics. Why Explore?
Keep what earns its keep.
If Niagara Analytics or station logic already pays for itself on a site, keep it. Explore adds portfolio ranking, forecasting and permissioned automation on top, without replacing Distech or editing the wire sheet.
Sees past one station.
Station tools see the sites they were commissioned for. Real portfolios mix Distech with Siemens, Schneider, Metasys, Trend and meters. Explore normalises all of it into one queue.
Physics, not another dashboard.
FrostDynamics checks every finding against the building thermodynamics before it reaches your queue. Pure pattern tools and wire-sheet analytics cannot do that across the estate.
At a glance
- Works with
- Distech EC-Net / ECLYPSE via Niagara station
- Connection
- through the Niagara station (FrostLogic Edge Agent)
- Write access
- off by default, granted per scope
- Hardware
- none
- Data residency
- EU, GDPR-native
- First findings
- in the first week
- Also reads
- other BMS, meters, IoT sensors in the same portfolio
Distech is one route in. Explore also reads Honeywell Niagara, Siemens Desigo, Schneider EcoStruxure, Johnson Controls Metasys 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
Distech Controls analytics, the questions we get.
Yes, when the estate exposes points through a Niagara station. Explore connects through that station over oBIX or BACnet. Product-line branding on the panel does not change the read path.
No. Explore never edits the wire sheet. It reads the points the station exposes. Writes to those points start off; you grant them one scope at a time.
No. FrostLogic is independent. We are not affiliated with or endorsed by Distech, Tridium or Honeywell. Explore connects through the Niagara station the estate already runs.
No. Keep what earns its keep on the station. Explore adds portfolio-wide detection, forecasting, ranking and permissioned automation on top.
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 station 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.
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.
Distech Controls, EC-Net and ECLYPSE are trademarks of their respective owners. Niagara, Tridium and Honeywell are trademarks of their respective owners. FrostLogic is an independent vendor and is not affiliated with or endorsed by Distech Controls, Tridium or Honeywell.