Türkçe 
English 
BMS Data Collection Management encompasses the end-to-end collection, standardization, verification, and secure preparation of data from building field devices, automation controllers, and third-party systems for analytics. The goal is to enhance operational continuity, reduce energy costs, improve comfort and indoor air quality, and create a reliable data backbone for sustainability objectives.
This page summarizes the architectural approach, protocols and integrations, data quality and security topics, real-time monitoring and analytics layer, typical use cases, and implementation roadmap in practical terms. You can find the details of the solution in the Data Collection Management content on the Centra page.
What is Data Collection Management and Why is it Critical?
Scope in the context of BMS
Modern buildings contain a heterogeneous array of data sources, including energy meters, HVAC controllers, lighting automation, access control, elevator systems, fire detection, water and gas meters, and IAQ (indoor air quality) sensors. Data Acquisition Management makes this data, flowing at different speeds and protocols, visible by bringing it together under a single data model. This allows maintenance teams, energy managers, HSE (Health, Safety, Environment) and sustainability teams to work together on the same facts.
Value added to stakeholders
Energy Management:
Minute-by-minute consumption from the grid and sub-meters; peak demand optimization, reactive power penalty prevention, demand response alignment.
Facilities & Maintenance:
Condition-based maintenance, early failure warnings, spare parts planning, MTTR abbreviation.
Indoor Air Quality & Comfort:
Ventilation optimization based on CO2, VOC, and temperature-humidity balance.
Sustainability:
A traceable and auditable database for ESG reporting and carbon accounting.
Typical architecture: edge-to-cloud.
Layered approach: Field devices → Local controllers (DDC/PLC) → Edge IoT Gateway → BMS/SCADA → Time series/data lake → Analytics/applications (FM, CMMS, energy management, dashboards).
- Edge IoT Gateway: Protocol translation, lightweight preprocessing, buffering.
- Time Series Storage: Compression and storage policies for high-volume telemetry.
- Data Model: Device-type/area/zone/floor-building hierarchy; digital twin-compatible naming convention.
Protocols and integrations
The most common open protocols in the field are: BACnet/IP, Modbus, TCP/RTU , KNX , OPC, UA , MQTT , and LoRaWAN. REST/GraphQL API and Webhook integrations are recommended for third-party software. Data schema conversions and unit standardization (°C ↔ °F, kW ↔ kBTU/h) should be performed automatically.
99.9% Collection accessibility <60 sec Telemetry freshness target >98% Data accuracy rate
Centra's End-to-End Solution Approach
Solution sheet and scope
Centra, within its Data Collection Management framework, brings together multi-protocol support, edge preprocessing, secure transport, schematic modeling, data quality controls, and analytical integrations under a single umbrella. The architecture supports both on-premise and cloud deployments.
Data quality and governance
- Validation & Improvement: Range checking, outlier detection, interpolation.
- Standard Naming Conventions: Zone/Equipment/Point templates; unit-to-unit conversions.
- Metadata: Device type, location, manufacturer, maintenance history, calibration date.
- Versioning & Traceability: Change log and audit trail.
Security and compliance
Data and control traffic are protected with end-to-end TLS, certificate management, network segmentation (OT/IT), role-based access (RBAC), multi-factor authentication (MFA), and the least-privilege policy. Logging/SIEM integration, incident response procedures, and backup and recovery policies complement operational security.
Edge/Fog computing and buffering.
Secure buffering and retry mechanisms are used at the edge to prevent data loss during network outages. Latency is reduced by running event rules (e.g., "alert if CO2 >1000 ppm and occupancy=1") at the edge.
Real-time monitoring, alarms, and analytics.
- Dashboards: Energy consumption, IAQ indicators, system status, and alerts all on a single screen.
- Event/Alarm Management: Threshold, rate, and derived signal-based rules; notification flows.
- Analytics: Demand forecasting, anomaly detection, failure prediction (PdM), and optimization.
Use cases
Energy Optimization:
HVAC setpoint strategies according to time zone schedules; lighting calendars; peak cutoff.
Fault Prediction:
Early warning is provided through attributes such as fan vibration/current, coil ΔT, and compressor on/off frequency.
IAQ & Comfort:
According to occupancy data, fresh air flow; CO2 / PM management; sick building syndrome risk reduction.
ESG & Reporting:
Carbon accounting, scope 1-2 data and evidence sets; auditable data footprint.
Implementation roadmap
Stage Explanation Outputs
1) Exploration & Inventory Device/protocol mapping, existing BMS/SCADA and network topology analysis. Source list, data gap analysis, integration plan.
2) Pilot Installation of edge gateways, data models, and dashboards for the selected floor/zone. KPI baseline, feedback, and improvement list.
3) Scaling Multiple building/campus spread, implementation of security policies. Standard templates, automation playbooks.
4) Continuous Improvement Alarm settings tuning, model updates, maintenance rituals. SLA reports, audit trails, cost/energy savings report.
KPIs and success criteria
- Data Freshness: 95% of data is collected with a delay of less than 60 seconds.
- Data Accuracy: Outliers <2%, sensor calibration compliance >98%.
- Operation: MTTR ↓, recurring alarm rate ↓, false-positive alerts ↓.
- Energy: Targeted annual improvement of 5–15% in kWh/m² and peak demand.
- ESG: Auditable data coverage >95%.
Frequently Asked Questions (short)
- Will it work with the existing BMS? Yes; integration is possible with open protocols such as BACnet/Modbus/OPC UA.
- Is cloud computing required? No; on-premise or hybrid architecture is supported.
- Will there be data loss? Edge buffering and retry minimize the risk.
- Security? TLS, RBAC, network segmentation, audit trail, and backup are standard.
- Is it scalable? Multi-building/campus and multi-tenant scenarios are supported.
In conclusion, BMS Data Collection Management generates measurable value for operational excellence, energy efficiency, and sustainability goals by integrating data from diverse sources into a single, reliable backbone. The secret to success lies in a phased implementation roadmap supported by the right architecture, robust data governance, and security principles.
