Türkçe 
English 
Monitoring Management is an end-to-end visibility layer established within the BMS ecosystem for real-time monitoring of signals from all field devices, controllers, and subsystems, conversion into meaningful indicators, management of alerts/events, and continuous performance improvement. The goal is to make operational continuity, energy efficiency, comfort, indoor air quality, and safety objectives manageable through a single source of reality. For details: Monitoring Management.
BMS Monitoring Management: Purpose and Scope
Real-time visibility: boards, cards, maps
The monitoring layer presents data from heterogeneous systems such as energy, HVAC, lighting, IAQ sensors, elevators, and access control on a single screen. Status cards, heat maps, floor/zone maps, and trend graphs make critical metrics (kWh, kW, COP, ΔT, CO2 , VOC, PM, temperature/humidity, occupancy information) understandable. The user can quickly delve deeper into the building → block → floor → zone → equipment hierarchy.
Alarm & event management: noiseless, action-oriented alerts.
Monitoring isn't just about "seeing"; it's about sending the right alert to the right person at the right time. Alerts are generated using threshold, orientation/ratio, derived signal, and model-based rules. Debounce, alarm deduplication, and escalation policy mechanisms reduce false positives. Alerts are converted into actionable responses through email, SMS, mobile push notifications, and CMMS work order integrations.
Observability: signal + context + root cause
Effective monitoring tracks not only metrics but also context. Equipment health indicators (vibration/current, number of starts), maintenance history, setpoint changes, occupancy information, and outside weather data are combined to accelerate root cause analysis. Event timelines, dependency graphs, and correlation views provide answers to the question, "Why now?".
KPIs and SLOs: defining what's good and what's bad.
- Energy: kWh/m², peak demand, demand factor, reactive power ratio, equipment COP/EER.
- IAQ: CO2, VOC, PM, temperature/humidity comfort band compliance ratio.
- Operation: MTBF/MTTR, alarm recurrence rate, false-positive rate, intervention SLA.
- Compliance: Regulatory, data coverage and accuracy for ESG/carbon accounting.
Role-based experience: different stakeholders, different sets of indicators.
Role-based dashboard profiles are created for facility management, energy manager, HSE, sustainability, and operations teams. Each profile includes relevant KPIs, alarm boxes, task flows, and report shortcuts. Data access is restricted using the RBAC policy.
Edge and cloud balance
Time-critical indicators (e.g., freeze protection, pressure drop, CO2 threshold) are monitored at the edge, while long-term trends and reports are processed in the cloud or data center. Edge buffering prevents data loss during network outages.
Reporting and auditability
Daily/weekly/monthly reports include energy and comfort trends, hygiene alerts, improvement actions, and earnings reports. Monitoring results are made auditable through audit trail and data lineage.
99.9% Monitoring accessibility <60 sec Telemetry freshness target >98% Alarm accuracy rate
Centra Approach and Implementation Roadmap
Modular components
Dashboards & Visualization:
Role-based dashboards, floor/zone maps, trend & dispersion graphs, KPI charts.
Alarm Engine:
Threshold/rate/window rules, deduplication, mute, maintenance modes, gradual escalation.
Event Log & Root Cause:
Event timeline, relational view, dependency graph, and root cause clues.
Observability:
Line latency, gap/outlier tracking, failure rate, SLA/SLO monitoring.
Security & Access:
RBAC, MFA, session policies, signed configuration, audit trail, SIEM integration.
Integrations:
Bidirectional API with BACnet/Modbus/KNX/OPC UA, MQTT; CMMS/FM and energy management software.
Hygiene and quality are a major concern.
To prevent "alarm flooding," dynamic threshold adjustments, rate limits, debounce, and merging rules are applied. The false-positive rate is regularly reviewed; unnecessary rules are removed, and a noise budget is maintained.
Energy and IAQ monitoring scenarios
Energy:
Automatic notifications when peak demand approaches; compensation control alerts when the reactive power ratio increases.
IAQ:
CO2 / VOC/PM thresholds; zone-based warnings for out-of-comfort temperature/humidity, fresh air optimization.
Care:
Pre-failure signal capture using compressor circuit count, motor current, vibration, and ΔT; conversion to CMMS work order.
Security:
Event correlation from pressure drop, leak, and smoke sensors; emergency response workflows.
KPI set and goals
- Data Freshness: 95% of data is displayed with a delay of less than 60 seconds.
- Alarm Quality: False-positive <5%, recurring alarm <10%.
- Operation: MTTR ↓, unplanned downtime ↓, timely response rate ↑.
- Performance: 5–15% annual improvement in kWh/m² and peak demand.
- Compliance: Data coverage for ESG and regulatory reporting >95%.
Implementation roadmap
Stage Explanation Outputs
1) Discovery & Design Equipment/inventory, protocols, target KPIs/SLOs, and alarm strategy are defined. Architectural diagram, role-based dashboard templates, alarm policies.
2) Pilot The selected floor/zone; panels, alerts, and reports are activated and verified. Baselines, false-positive analysis, tuning list.
3) Scaling Multiple building/campus deployments; templates and automation playbooks. Standardized installations, training, and documentation.
4) Continuous Improvement Alarm hygiene, KPI review, new scenarios and integrations. SLA/SLO reports, improvement cycles, earnings reports.
Frequently Asked Questions (short)
- Will it work with the existing BMS? Yes; integration with BACnet/Modbus/KNX/OPC UA and MQTT is possible.
- Is cloud computing mandatory? No; on-premise or hybrid architecture is supported.
- Will there be data loss? Edge buffering and retry minimize the risk.
- Security? TLS, RBAC, MFA, audit trail, and SIEM integration are standard.
- Is it scalable? It works in multi-building/campus and multi-tenant scenarios.
In short, Monitoring Management is the “eyes and ears” of a BMS: it makes data visible within its context, reduces noise, and enables teams to take action quickly. With well-designed dashboards, effective alert policies, and role-based workflows, operational excellence, energy efficiency, and sustainability goals are measurably supported.
