GTB / GTC (Building Technical Management / Central Control Unit)

Building Management Systems (BMS) are the "nervous system" of technical installations: they supervise, control, and optimize HVAC, ventilation, domestic hot water, lighting, blinds, metering, security, and more, all from a centralized interface. In practice, local controllers manage the equipment, fieldbuses transmit measurements, and a platform (BMS server) aggregates data, alarms, schedules, control laws, and dashboards. The goal: comfort, energy efficiency, and service continuity, with clear rules and actionable KPIs.

Building Management Systems (BMS/BAS): Operational Definition and Typical Architecture

A typical building management system (BMS) combines: sensors/actuators, batch controllers (HVAC, AHU, boiler room, refrigeration, electricity), buses (BACnet/IP, Modbus RTU/TCP, KNX, LON, M-Bus), a server (SCADA/BMS), and a web-based user interface. Configuration is carried out within it

- Regulations: water law, adaptive setpoints, anti-cycling, defrosting sequences.

- Calendars : schedules, holidays, special days, exceptions by zone.

- Alarms : thresholds, acknowledgments, priorities, escalations (email/SMS).

- Cross-cutting scenarios : pre-heating/pre-cooling, closing of solar protections, load shedding.

- Data : historical data, energy dashboards (kWh, kW, DH of discomfort), API export to EMS/CMMS.

Best practices: clear naming conventions for endpoints, granular access rights, change logs, and dependency mapping (who controls what). Cybersecurity aspects include: network segmentation, updates, strong passwords, and remote access monitoring.

Advantages, limitations and points of attention of BMS/BAS

Interests

• Energy: optimization of instructions/schedules, load shedding, peak shaving.
• Comfort & IAQ: CO₂/Temp° monitoring, early alarms, stability of regulations.
• Operation: accelerated diagnostics (trends), condition-based maintenance.
• Global management: multi-site vision, reports for trustees/asset managers.
• Interoperability: gateways to EMS, CPE, sub-metering.

Boundaries

• initial CAPEX (automation, licenses, integration) and OPEX (maintenance, updates).
• Heterogeneity of protocols/equipment → risk of non-integrated pockets.
• Problems arise if the GTB is not kept up to date (instructions, schedules).
• Integrator dependency: quality of the parameterization = quality of the building.

Points to consider

• Specifications: measured/controlled points, KPIs, scenarios, alarm SLAs.
• Standardized tree structure & naming, quick search for points.
• Measurement quality: calibration, time step, NTP synchronization.
• Cybersecurity: Dedicated VLAN, workstation hardening, remote access management.
• Reversibility: open formats (BACnet, API), access to sources/backups.
• Operator training and procedures (degraded mode, lockouts/tagouts).

Anecdote — “A click that calmed the Croisette”

In Cannes, an office building saw its complaints increase every summer. The building management system (BMS) showed that solar blinds were rarely closed despite the sunshine and that the HVAC operating hours were too long. The integrator added a weather scenario (proportional closure of the external blinds + pre-cooling before occupancy) and a sequence of restarts. The result for the season: a 9% reduction in electricity consumption, complaints halved, and meeting rooms finally tolerable at 2 p.m. The moral of the story: a BMS doesn't save anything… as long as its rules don't tell the right story.