Siemens Desigo CC Driver for Tridium Niagara

The Desigo CC driver integrates Siemens’ Desigo CC supervisor with Tridium Niagara through the Northbound Open RESTful Integration Service (NORIS) – the HTTP API Siemens exposes for third-party clients. Niagara discovers Desigo CC objects, reads and writes their properties, executes commands, subscribes to alarms and events, and respects the per-user access rights configured inside Desigo CC.

Authentication uses OAuth 2.0 token-based access. Once a token is issued, the driver groups requests so that a single round-trip can read or write hundreds of points at once – meaningful efficiency on large multi-discipline sites where the alternative is thousands of individual REST calls per scan cycle. Alarm and value-change events are delivered through a long-running subscription, so updates reach Niagara within a second or two of the change happening in Desigo CC.

Because NORIS exposes the full Desigo CC object model, the driver presents one unified point catalogue regardless of which protocol carries the data inside Desigo CC at the field layer. A site that mixes BACnet, LonWorks, KNX, M-Bus, and proprietary Siemens fire and security panels appears to Niagara as a single REST source. NORIS covers every Desigo CC subsystem – HVAC (typically delivered through Desigo PX field controllers), lighting and shading (KNX), fire detection (FS20, Sinteso), security and access (SiPass, Siveillance), and energy metering – with operational properties (present value, status, alarm state, command target) alongside their native discipline-specific metadata. Niagara dashboards can be organised by discipline directly off the Desigo CC system tree without needing per-protocol drivers underneath.

Configuration on the Niagara side is short: the Desigo CC base URL, OAuth client credentials issued from a dedicated Desigo CC service account, and the system-tree node from which discovery starts. The driver enforces Desigo CC’s per-user access rights as the platform itself enforces them – if the service account is not granted read access to the fire system, those objects do not appear in Niagara at all, regardless of Niagara-side configuration. Role-based segregation between disciplines stays managed in Desigo CC rather than reimplemented in Niagara, which matters on sites where fire and security data must remain inaccessible to HVAC operators for regulatory reasons.

The driver supports Desigo CC V3 through V8, including the Compact edition, and runs on JACEs, Niagara Supervisors, and cloud-hosted Niagara instances reaching on-prem Desigo CC through a secure tunnel.

Desigo CC is Siemens’ modern unified building management supervisor and the natural front-end above their two regional field-controller lines – Desigo PX in Europe and the Apogee P1 (FLN) and Apogee P2 (ALN) lines in the US. Where Niagara needs to talk to those field controllers directly rather than through Desigo CC – typically older retrofits, sites where Desigo CC is not licensed for the relevant disciplines, or projects replacing Desigo CC rather than keeping it – the field-controller drivers are the right entry point instead of this one. For Siemens industrial PLCs running alongside the BMS, the Simatic S7 driver covers S7-1200, S7-1500, and earlier families.