Large commercial buildings — offices above 5,000m², hotels with 100+ rooms, hospitals — use Building Management System (BMS) platforms to aggregate, visualise, and alarm on data from KNX, HVAC BACnet controllers, Modbus energy meters, and access control systems. The two dominant BMS platforms in Europe are Siemens Desigo CC and Schneider Electric EcoStruxure Building Operation. Both support KNX integration via KNXnet/IP — but the integration architecture, data point limits, and licensing models differ significantly. This guide covers OPC UA as the emerging integration layer, KNXnet/IP driver configuration, and practical data point mapping.

BMS integration architecture options

Option 1 — Direct KNXnet/IP: BMS server contains a KNXnet/IP driver (software) that acts as a KNXnet/IP routing client. KNX IP router (Weinzierl 770, MDT KNX IP Router) provides the KNXnet/IP tunnelling or routing endpoint. BMS polls or subscribes to KNX group addresses directly. Advantage: simple, no intermediate gateway. Limitation: BMS vendor's KNX driver quality varies; Siemens Desigo CC KNX driver (OPC module) supports up to 10,000 group addresses per IP router connection. Option 2 — OPC UA gateway: KNX OPC UA server (Lingg and Janke KNX Virtual, or HMS Industrial Networks Anybus KNX) exposes all KNX group addresses as OPC UA nodes. BMS connects as OPC UA client. Advantage: vendor-neutral; any BMS with OPC UA client support connects. OPC UA provides: structured address space, data type coercion, subscription-based updates (no polling), built-in security (X.509 certificates, encrypted transport). Option 3 — BACnet/IP gateway: Intesis IN701KNX300000 or LOYTEC LKNX-100 converts KNX group addresses to BACnet objects (Binary Value, Analog Value, Analog Input). BMS reads via BACnet/IP. Best for BACnet-centric BMS (Honeywell Niagara, Siemens Desigo PX).

Siemens Desigo CC with KNX

Desigo CC (DCC) is a server-based BMS (Windows Server, SQL Server database). KNX integration via Desigo CC OPS module (OPC Data Access server). Configuration: install Desigo CC KNX Driver on BMS server → configure KNXnet/IP routing connection → IP = KNX IP Router address, multicast group 224.0.23.12. Group addresses import: export ETS6 project as OPC DA address list (ETS6 → Export → OPC DA configuration file). Import in Desigo CC OPS: auto-creates OPC DA items for each group address. Desigo CC alarm management: define alarm rule on KNX group address (e.g., fire alarm input GA 1/9/0 = 1 → Priority 1 alarm, auto-acknowledge off, email to FM team). Trend logging: Desigo CC stores group address value history in SQL Server — configurable retention (90 days standard, 5 years for energy data). License: Desigo CC is point-based licensing — each monitored KNX group address = 1 point (approx €3-5/point for 1,000-5,000 point installations).

Schneider EcoStruxure Building Operation with KNX

EcoStruxure Building Operation (EBO) server (Windows, SQL Server). KNX integration: EBO KNX driver (SmartStruxure KNX Server plugin). Configuration: EBO Workstation → Server → KNX Server → Add KNX IP Router (Weinzierl 770 IP, port 3671). Group addresses: manually create in EBO as Analog Input (DPT 9.001), Binary Input (DPT 1.001), etc. — or import from CSV exported from ETS6. EBO advantage over Desigo CC for KNX: native KNX DPT support in data type selector — no manual scaling required. Alarm routing: EBO → email, SMS (via SMTP gateway), BACnet alarm notification to SCADA. Graphics: EBO has vector-based building floor plan editor — place KNX data points on floor plan as sensor icons with live value overlay. License: EBO is server-based + per-point for advanced analytics module.

Lingg and Janke KNX Virtual — OPC UA server

For projects where the BMS team prefers OPC UA over proprietary KNX drivers: Lingg and Janke KNX Virtual runs on any Windows/Linux machine, connects to KNX via KNXnet/IP tunnelling, exposes all group addresses as OPC UA nodes in a structured address space. Configuration: import ETS6 project file → KNX Virtual auto-creates OPC UA node for each group address, with correct DPT mapping and EU unit label. OPC UA endpoint: opc.tcp://[server_ip]:4840. Security: configurable (None, Sign, Sign+Encrypt, X.509 certificate). BMS connects as OPC UA client: Siemens Desigo CC → add OPC UA server connection → browse node tree → drag KNX nodes to Desigo CC asset structure. Subscription: KNX Virtual pushes changed values to OPC UA client within 500ms of KNX telegram — no polling, efficient for 2,000+ data points.

Data point mapping strategy

In large commercial buildings: KNX group addresses easily reach 2,000-5,000 for a 10,000m² office. Not all need BMS integration. Recommended tiers: Tier 1 (BMS mandatory): all energy meters (kWh, kW, cos-phi), HVAC setpoints and actual temperatures, occupancy status, alarm inputs (fire, SPD, intrusion), equipment run status (AHU, pumps). Tier 2 (BMS optional): lighting zone status, blind positions, individual room temperatures. Tier 3 (exclude from BMS): individual switch states, scene activations, button press events — these create noise without value for FM team. Total BMS integration points for 10,000m² office: typically 300-800 Tier 1 + 2 points. ETS6 group address export: use Group Address export with DPT and description column → import to BMS saves 10-20 hours of manual configuration.