Niagara Framework versus Siemens Desigo CC

What you get on day one

• Desigo CC: a defined product. HVAC, lighting, fire safety and security plus elevators and room booking, advanced event management with automated reactions and a scripting engine, Powermanager metering, trending with export, long-term storage in the Compact edition, Flex Client mobile app with push notifications.
• Niagara: a runtime and a toolkit. Built-in applications manage histories, schedules and alarms, the core control engine lets you create logic, and dashboarding uses tag-based graphics and HTML5, but the interface is built or bought from partners. No energy metering capability is stated on any Tridium page opened, although third-party meter drivers exist on the Marketplace.

Protocols and conformance

Niagara states top-tier BACnet conformance: Niagara 4 releases are both BACnet Advanced Workstation, B-AWS, and BACnet Building Controller, B-BC, compliant, and there is a confirmed MQTT driver supporting public clouds including AWS and Google Cloud. Beyond that, public verification is genuinely poor: the Niagara Drivers product page returned HTTP 500 at every URL variant, the documents library returned no results and the documentation portal is login gated, so Modbus, LonWorks, SNMP, OPC UA, KNX, M-Bus, oBIX and REST could not be confirmed from a vendor page despite being the platform core selling point. They are unverified, not absent. Desigo CC publishes the opposite picture: BACnet and BACnet/SC southbound with a northbound BACnet IP server, Modbus, KNX, OPC DA and UA and SNMPv3 all on vendor datasheets, with MQTT absent from both edition lists and therefore unverified. The twist is that on Siemens the published list is edition dependent, so KNX in Connect does not mean KNX in Compact DMS.

Edge, security and ecosystem

Niagara wins the edge comparison outright on evidence. JACE controllers and Niagara Edge 10 run the same station software as the Supervisor, which does batch provisioning of JACE and Edge devices, and remote Niagara instances come under supervisory control through a System Database. Desigo CC manages Desigo PXC controllers but is not itself an edge runtime. Niagara also publishes the most detailed security posture in this category: a Security Dashboard, PKI, LDAP, password expiration, runtime integrity checks on digitally signed code with enforced third-party module signing, FIPS 140-2 Level 1 and 802.1X on JACE 8000 and Edge 10. Against that, Siemens public cybersecurity material is marketing grade. The Niagara ecosystem is real, with a public Marketplace, a Developer Programme and a Powered by Niagara OEM programme, but Tridium explicitly disclaims third-party driver quality: the Marketplace states seller information and product descriptions are not independently verified.

Licensing posture

Neither publishes a price. Tridium publishes no price and no licence tier table anywhere, with the licensing link leaving the site, and the Supervisor page mentions a new edge licensing scheme without detail. Siemens publishes a licence catalogue structure of roughly a hundred point-quantity codes. In both cases the system is specified, supplied and commissioned through integrators, and the software line is small beside engineering and controllers. On Niagara, engineering is the cost.