Don't check every system separately
Sites, assets, and gateway health are merged into one shared view.
Solution 路 Direct use
Building monitoring for operators, monitor assets without reinventing your infrastructure.
MonitoringHive gives operators a dependable view of sites, assets, alarms, and data quality, without replacing existing building infrastructure. You start with a clear slice and extend once the value is visible.
For grown building infrastructure, multiple sites, and technical teams that want less flying blind.
Sample data 路 not a live customer view
At a glance
In short: MonitoringHive fits when you want to use technical building data dependably.
01
You stay in control
Data scope, purpose, roles, and operating model are defined. The data comes from your infrastructure and stays your data in substance.
02
You start in a controlled way
One site, one asset class, or one clear data flow is enough to start. Existing infrastructure does not need to be replaced.
03
You build up value
Dashboard, alarms, data quality, reports, and Studio analysis grow from the same data foundation.
Offline-hardened is possible, but deliberately less flexible: integrations and extensions must be planned more thoroughly up front.
In everyday operation
Less flying blind. Better decisions.
MonitoringHive should not just collect data. It should help operations teams see faster what is relevant, where data is missing, and which topics recur.
Spot data quality
Gaps, sluggish data points, and implausible values become visible before they lead to wrong conclusions.
Triage alarms better
States and alerts become traceable, prioritisable, and reusable.
Justify maintenance
Trends, reports, and Studio analysis help discuss maintenance and investment with data.
What you get as an operator
A platform built around everyday operations.
MonitoringHive does not replace building automation and does not intervene uncontrolled in assets. The focus is on controlled data capture, cross-site operational overview, and data quality and alarms, defined concretely per site.
- Cross-site operational overview. Your properties and assets in a consistent view, without tool sprawl.
- Data quality and alarms. Gaps, dropouts, and sluggish sensors become detectable and traceable, with clear escalation levels instead of alert floods.
- Monitor assets without an island solution. Heating, ventilation, pumps, and meters from various manufacturers on a unified data foundation.
- Local connection. The Monitoring Box as physical anchor point between asset and platform.
- No vendor lock-in. Devices and protocols remain replaceable, the data model stays stable.
Z眉rich Nord
Basel Areal A
Bern West
Geneva office
Process
From the connection to a dependable operational overview.
A structured path to monitor assets, from the first connection to a cross-site operational overview.
STEP 01
On-site connection
Install the Monitoring Box on site and connect it to the existing assets, via standard protocols and manufacturer-specific adapters.
STEP 02
Define data points
Relevant measurement points are structured in the platform, with clear names, units, and asset assignment.
STEP 03
Thresholds & alarms
Sensible thresholds and escalation rules are configured, tuned to each asset type and site.
STEP 04
Ongoing operation
Site overview, data quality, open alerts, as a dependable basis for decisions and maintenance.
Data sovereignty
Your data. Your control. Our secure operation.
MonitoringHive is not designed to take over data sovereignty. The connected measurements, states, and operational data belong to your infrastructure. MonitoringHive helps to capture this data securely, prepare it traceably, and make it usable for operation, alarms, analysis, and reports.
01
You set the scope
Which data points are connected, which sites and systems are included, which roles and views are needed, you define this per project.
02
We ensure secure processing
MonitoringHive provides encrypted transport, clear states, tenant-separated storage, and usable analysis, within the agreed boundaries.
03
Purpose is clearly governed
Data use, access, and purpose are clarified per project. Nothing is automatically opened up, nothing is used without limit.
Low-risk entry
Start in a controlled way, without unnecessary interference with existing systems.
The entry can be deliberately low-risk: defined data points are captured read-only, connected in a structured way through the Monitoring Box, and made visible in the dashboard. Existing building or control systems do not need to be replaced unnecessarily.
Operating model
Start locally. Connected creates more value.
The Monitoring Box can create local value. The full MonitoringHive benefit, however, emerges with secure platform connection: cross-site view, central alarms, Studio analysis, reports, data-quality comparisons, and long-term data models. Offline or on-premises remain possible if requirements demand.
LOCAL
Locally usable
Structured data points, local state overview, data quality, and configurable local buffering on site.
ONLINE
Continuously connected
And still offline-capable on connection loss. With central dashboards, alarms, site comparisons, Studio analysis, reports, and long-term data models.
SPECIAL CASE
Offline-hardened
Offline-hardened is possible, but deliberately less flexible: integrations and extensions must be planned more thoroughly up front.
Entry for operators
From the first site to a dependable operational overview.
MonitoringHive doesn't have to start as a big project. A sensible entry begins with one site, one asset class, or one clear data flow. What matters is that in real operation it becomes visible: Which data holds up? Which alarms are relevant? Which analyses really help?
Stage 01
First site
One site or one asset class, defined data points, Monitoring Box, dashboard, data quality, and security clarification.
Typical use cases
- first state overview
- gateway health
- make data quality visible
- review integration scope
How we recognise the next step
Shows whether data quality, states, and first alarms hold up in everyday work.
Stage 02
Multiple sites
Central view across multiple buildings, reusable data models, alarms, site comparison, and roles.
Typical use cases
- compare multiple buildings
- spot recurring alarms
- central operational overview
- prioritise maintenance
How we recognise the next step
Shows which models, alarms, and views are reusable across sites.
Stage 03
Build up data value
Studio analysis, historical trends, operational reports, management reports, and long-term decision bases.
Typical use cases
- data-quality reports
- site comparisons
- trend analyses
- prepare investment and maintenance decisions
How we recognise the next step
Shows which reports, trends, and Studio analyses improve decisions.
Recommended
TRRT-operated platform
The full value emerges with secure platform connection: central dashboards, alarms, Studio analysis, reports, data history, and ongoing platform operation.
From operation to analysis
Monitor stably first. Then make better decisions.
MonitoringHive begins in everyday operation: states, alarms, gateway health, and data quality. When this data is stably collected and cleanly modelled, reports, comparisons, and long-term decision bases emerge from it.
Stage 路 01
Operational overview
Sites, assets, current states, and gateway health.
Stage 路 02
Alarms
Prioritised alerts, escalation logic, and traceable events.
Stage 路 03
Data quality
Make gaps, dropouts, sluggish sensors, and implausible values visible.
Stage 路 04
Studio & reporting
Historical trends, site comparisons, reports, and decision bases.
Dashboard & Studio
For the day-to-day and for the next decision.
MonitoringHive Dashboard
What is relevant right now?
For ongoing operation.
Site and asset overview, active alarms, gateway health, data quality per data point, and role-based operational views, the working surface for people who need to keep operations in view.
- Site and asset overview
- Active alarms and states
- Gateway health
- Data quality per data point
- Role-based operational views
MonitoringHive Studio
What do we learn from the data?
For analysis, reports, and maintenance preparation.
Turn collected data into concrete insights, for optimisation, service conversations, and management reports on technical infrastructure.
- Consumption and performance trends over time
- Compare sites or asset classes
- Document data gaps and quality issues
- Prepare maintenance or service conversations with data
- Management reports for technical infrastructure
Fit
Does MonitoringHive fit your situation?
Good fit when
You want to run heterogeneous infrastructure in a structured way
- multiple sites or assets
- heterogeneous technical systems
- need for state overview and data quality
- wish for long-term analysis
- security requirements on data paths
Less of a fit
If you only want a visualisation tool
- you are only looking for a simple single-device app
- no data points can be connected
- a pure visualisation tool without integration work is expected
Frequent questions
Building monitoring for operators, frequent questions.
Does MonitoringHive own the data?
No. The data comes from your infrastructure and stays your data in substance, MonitoringHive provides the secure platform to make it usable.
Does everything have to be online?
Offline-hardened is possible if a project must be operated deliberately isolated. The full dashboard, reporting, and Studio value, however, emerges in connected platform operation.
Can offline installations be extended later?
Yes, but in a controlled way on site. That is why the integration list before project start is especially important.
Does MonitoringHive intervene in assets?
The entry is designed as a monitoring and analysis solution. Whether data is only read or extended functions are planned later is defined explicitly.
Can existing assets be connected?
Yes. Technically supported today: Modbus TCP/IP, Modbus RTU, KNX, and MQTT / REST; LAMPEC and TSE have direct integration paths. The concrete scope is qualified per project.
How does the platform handle multiple sites?
Sites, assets, and data points are modelled hierarchically. You see your entire property structure in a consistent view.
Which data leaves the site?
The Monitoring Box transports only the defined data points over a controlled, secured connection, no uncontrolled asset communication.
What happens during a connection failure?
Data can be configurably buffered locally and transmitted traceably after reconnection. Scope and behaviour depend on operating mode, storage limits, and project configuration.
Contact
Discuss sites and assets.
We review with you which assets to connect sensibly first, which protocols are relevant, which security and data requirements apply, and what the data model should look like for your operation.