Siemens Desigo CC and KNX: Driver Configuration and Data Points
Siemens Desigo CC is the BMS platform of choice for airports, hospitals, data centres and universities across Europe. Connecting KNX building automation to Desigo CC requires the KNX Driver plugin, a structured ETS6 export, and careful point configuration — from alarm rules and graphics to trend logging and licensing.
Siemens Desigo CC overview
Desigo CC is a server-based BMS running on Windows Server 2019 or later with SQL Server 2019 as its database backend. The platform scales from 500 points in the Compact Edition (embedded database, no SQL Server required) to 250,000 points in enterprise deployments. It is used across airports (Frankfurt, Munich, Zurich), university campuses, large hospitals, and data centre facilities where a single BMS platform must integrate HVAC, electrical, fire, and access control subsystems.
| Module | Function |
|---|---|
| OPS (OPC Server) | OPC DA/UA server — imports ETS6 group address list, exposes as OPC items for Desigo CC point database |
| KNX Driver plugin | KNXnet/IP tunnelling client — connects Desigo CC OPS to a KNX IP router, reads and writes KNX group telegrams |
| Desigo PX integration | Field controller integration for HVAC plant (AHU, chillers) — separate from KNX driver |
| Alarm Management | Priority classification, acknowledgement workflow, escalation (email, SMS), alarm log retention |
| Plant Viewer | Vector floor plan graphics with live KNX point values, drill-down to room level |
| Trend / Reporting | SQL-backed time-series logging, energy reports, ISO 50001 degree-day normalisation via Analytics module |
KNX integration architecture
The Desigo CC KNX Driver plugin acts as a KNXnet/IP tunnelling client. It connects to a KNX IP router — typically a Weinzierl 770 or MDT KNX IP Router installed on the KNX TP network segment — via the LAN on UDP port 3671. The KNX IP router bridges KNXnet/IP telegrams from the Desigo CC server to the KNX TP bus and vice versa.
One KNX IP router connection per Desigo CC KNX driver instance is the standard configuration. For buildings with multiple KNX areas — for example, one KNX TP line per floor with its own KNX IP router — configure one Desigo CC KNX driver instance per KNX IP router. Each instance appears as a separate OPS namespace in Desigo CC, keeping area separation clear in the point browser.
Desigo CC KNX connection topology
Desigo CC Server (Windows Server 2019, SQL Server 2019)
└── OPS module (OPC DA/UA server)
└── KNX Driver instance 1
└── KNXnet/IP tunnelling → Weinzierl 770 (Floor 1 TP)
└── KNX Driver instance 2
└── KNXnet/IP tunnelling → Weinzierl 770 (Floor 2 TP)
All KNX IP routers on dedicated BMS VLAN (e.g. 10.10.5.0/24)
Managed switch: IGMP snooping enabled for multicast
Firewall: permit UDP 3671 inbound on BMS VLAN from Desigo CC server
ETS6 export and Desigo CC import
The integration begins with an ETS6 export. In ETS6, navigate to File — Export — OPC DA Address List. ETS6 produces an XML file containing all group addresses in the project, with each GA represented as an OPC DA item with its address, DPT type, name, and description. This is the import file Desigo CC OPS reads.
In Desigo CC Engineering, navigate to Project — New — KNX OPS Import and browse to the ETS6 export XML. Desigo CC auto-creates one OPC DA item per group address, named following the ETS6 GA name. Each item path in the OPC DA namespace mirrors the ETS6 group address hierarchy (main group — middle group — group). DPT information is preserved: Desigo CC knows a GA of DPT 9.001 carries a 2-byte float in degrees Celsius and applies the correct scaling automatically.
OPC DA item naming example after ETS6 import
OPS namespace path: KNX.Floor2.HVAC.Office3_Temp_Actual_degC
GA address: 5/3/1
DPT: 9.001 (2-byte float, unit: °C)
OPC DA item ID: KNX.5.3.1 (auto-generated from GA)
Point configuration in the Desigo CC point browser
After the ETS6 import, review each KNX point in Desigo CC Engineering — Point Browser. Each point displays the OPC DA path, current value (if the KNX driver is connected), engineering unit from the DPT, and configuration tabs for alarm, trend, and plant assignment.
Key configuration properties to review and set for each point after import:
Analog point settings
- Unit: verify °C, kW, kWh, % — auto-filled from DPT but check
- High limit: alarm threshold (e.g. temperature above 30°C)
- Low limit: alarm threshold (e.g. temperature below 15°C)
- Deadband: prevent limit alarms from chattering (e.g. 1°C)
- Trend interval: 5 min (HVAC), 15 min (energy)
- Plant: assign to building — floor — room hierarchy
Binary point settings
- Active text: "ON" / "ALARM" / "OPEN" (display in graphics)
- Inactive text: "OFF" / "NORMAL" / "CLOSED"
- Alarm on: active state (value = 1) or inactive state as appropriate
- Alarm class: define alarm priority and notification recipient
- Maintenance mode: suppress alarm during planned maintenance
- Plant: assign to same hierarchy as related analog points
Alarm configuration and escalation workflow
Alarm configuration in Desigo CC is performed in Alarm Management — Alarm Classes and Alarm Rules. An alarm class defines the priority, notification behaviour (audible alert, email recipient group, mandatory acknowledge flag), and escalation rules. Alarm rules attach a class to a specific KNX point condition.
Example: fire alarm KNX point alarm rule
Point: KNX.1.9.0 "Fire_Alarm_Zone_1" (DPT 1.001 binary)
Condition: present-value = 1 (ACTIVE)
Alarm Class: Priority 1 - Fire
Audible: Yes (immediate on Desigo CC workstation)
Email: [email protected] (SMTP, immediate)
SMS: +44-7700-900xxx (via Desigo CC SMS gateway)
Mandatory acknowledge: Yes
Acknowledge requires reason code: Yes
Auto-suppress if maintenance mode: No (fire alarms never suppressed)
Acknowledge workflow:
1. Engineer logs in to Desigo CC (password required)
2. Opens alarm — reads zone, time, value
3. Physically inspects zone
4. Acknowledges with reason: "False alarm - steam from catering"
5. Entry written to fire log (retained 5 years)
Floor plan graphics in Plant Viewer
Desigo CC Plant Viewer provides a vector floor plan editor for creating live building graphics. Import the AutoCAD DWF floor plan (exported from the project architect drawings) as the background layer. Place KNX data point icons — temperature sensor, power meter, occupancy indicator, alarm indicator — on the floor plan at the physical location of each sensor or actuator.
Each icon is linked to its corresponding KNX OPC DA point in the Desigo CC database. Live values update on the graphic every 5 seconds by default. The FM operator sees the current temperature of each room on the floor plan, colour-coded by alarm status (green normal, amber warning, red alarm). Clicking any room opens a panel showing all KNX points for that room with live values and a trend graph button for the last 24 hours.
Drill-down hierarchy recommended: building overview → floor plan → room detail → point detail with trend graph. Each level is a separate Plant Viewer page linked by navigation buttons. For a 10,000 m² building: 1 building overview page, 5–10 floor plan pages, and room detail pages created on demand via Point Browser. The floor plan pages provide the FM team's primary interface for comfort complaint investigation and equipment status checks.
Trend logging configuration
Trend logging is configured per point in Desigo CC Trend. Each KNX point that requires historical data must have a trend profile assigned specifying the logging interval, retention period, and delta (minimum change before a new record is written).
Energy circuit trend profile
- Interval: 15 minutes (cyclic logging)
- Retention: 5 years (SQL Server storage)
- Delta logging: 0.1 kW (only log when value changes by more than 0.1 kW)
- Monthly report: Desigo CC Report — Energy Overview
- Export: CSV for FM team utility bill verification
Temperature trend profile
- Interval: 5 minutes (cyclic logging)
- Retention: 90 days rolling
- Delta logging: 0.2°C (ignore sensor noise)
- Use: comfort complaint investigation, HVAC fault diagnosis
- Degree-day normalisation: via Desigo CC Analytics module
ISO 50001 energy review via Desigo CC: Desigo CC Report — Energy Overview allows selection of energy points, date range, and export to CSV. The Analytics module (licensed separately) provides degree-day normalised heating analysis using outdoor temperature data from a KNX weather station GA. The 12-month normalised energy trend is the primary ISO 50001 baseline comparison document.
Desigo CC licensing and cost guidance
Desigo CC uses a per-point licensing model under the Desigo CC Flex framework. Enterprise purchases include a base of 500 points; additional points are purchased in blocks (typically 500-point increments). Each monitored KNX group address counts as one point in the Desigo CC license.
| Edition | Points | Database | Typical use |
|---|---|---|---|
| Compact Edition | Up to 500 points | Embedded (no SQL Server required) | Small commercial buildings, single-system integration |
| Flex (standard) | 500–250,000 points | SQL Server 2019 | Medium to large buildings, multi-system BMS |
| Flex + Analytics | 500–250,000 points + analytics | SQL Server 2019 + Analytics DB | ISO 50001, advanced energy reporting, degree-day normalisation |
Budget guidance for KNX integration
For a typical 10,000 m² office building with 500 KNX BMS points (Tier 1 and Tier 2 GAs), the Desigo CC Flex license cost is approximately €15,000–25,000 depending on support and maintenance contract level. This excludes server hardware, SQL Server license, implementation and commissioning time. Compact Edition for smaller projects with up to 500 KNX points is significantly less, typically €3,000–6,000 for the base license. Request a formal Siemens quotation via a Desigo CC certified system integrator for accurate pricing.
Need KNX panels configured for Desigo CC?
We build KNX panels with the Weinzierl 770 IP router pre-configured, ETS6 OPC DA exports ready for Desigo CC OPS import, and all group addresses named to Siemens naming conventions — reducing BMS commissioning time significantly.
Request a quote →