Niagara Framework

Niagara Framework is the archetype of this classification and the reason the directory separates integration frameworks from finished head-ends. Tridium describes it as a comprehensive software platform for the development and deployment of connected products, and as a comprehensive software infrastructure that addresses the challenges of creating device-to-enterprise applications. Niagara 4.15 is the version shown on the product page. Tridium is a Honeywell business, a fact that comes from Honeywell 2005 acquisition announcement and third-party records rather than from tridium.com, which does not state a parent relationship on any page read.

At the core is a control engine that lets users build logic driving control programming, running inside a station runtime. The same station runs on a JACE controller, on a Niagara Edge 10, or on a Niagara 4 Supervisor server, so the edge versus head-end boundary is a deployment decision rather than a product decision. The Supervisor adds server-level functions over a network of JACE, Edge and other field devices, brings remote Niagara instances under supervisory control, does batch provisioning of JACE and Edge firmware, keeps a System Database for managing those instances, and ships the engineering toolset used to build and configure applications. Built-in applications handle histories, schedules and alarms, with centralised data logging and trending plus archiving to external databases, and tag-based HTML5 graphics.

BACnet conformance is stated at the top of the scale: Niagara 4 releases are BACnet Advanced Workstation (B-AWS) and BACnet Building Controller (B-BC) compliant, which is both the highest operator-workstation profile and the controller profile in one platform. The Supervisor also ships an MQTT driver that supports public clouds such as AWS and Google Cloud, and exposes APIs for work order and analytics packages. The ecosystem is the real integration story: a public Niagara Marketplace carries third-party drivers reaching into competitors proprietary buses, including Johnson Controls N2, Siemens Apogee P1 and P2 and Desigo, Schneider TAC Xenta and EcoStruxure, Trend IQ, Automated Logic WebCTRL, Satchwell, Sauter, Cylon and Andover Infinet, plus utility and industrial protocols such as IEC 61850, IEC 60870-5-104 and DLMS metering, and OCPP for EV charging. Tridium claims over one million instances in use, and runs a Powered by Niagara OEM programme and a Developer Programme.

Security is the strongest published posture in this category: a centralised Niagara Security Dashboard showing the posture of the entire infrastructure, configurable user accounts with PKI, LDAP integration and password expiration, digitally signed code checked for integrity at runtime with third-party module signing enforced, FIPS 140-2 Level 1 conformance, and secure boot plus 802.1X network authentication on JACE 8000 and Edge 10. Separate Niagara Cyber Defense and Niagara Enterprise Security products exist. Cloud is additive rather than a hosting model: Niagara Cloud Suite provides Niagara Remote for remote station access, Niagara Recover to keep a current copy of station data against planned and unplanned outages, and Niagara Data Service for partner solution development, all requiring a supported framework version and an active Software Maintenance Agreement.

Two limitations deserve emphasis. First, it is not a finished product: Tridium states that integrators can build custom end-user interfaces or buy graphics and dashboarding templates from partners, so every deployment is bespoke engineering and the client is practically tied to whoever built the station. Second, public technical information is scattered and partly broken: the Niagara Drivers product page returned HTTP 500 on three URL variants, the Tridium documents library returned no results, and the documentation portal is login gated. The protocol question is nonetheless answerable, because Tridium publishes an Included Drivers list, document 2024-0007, stating that the drivers included with its standard licence models are BACnet IP client and server, BACnet MS/TP, BACnet Secure Connect, the BACnet AWS and OWS workstation profiles on Supervisor, KNX IP, Lon IP and Lon FTT-10, M-Bus IP and serial, Modbus TCP master and slave, Modbus Async master and slave, MQTT, oBIX, OPC UA client and server, and SNMP, with some entries JACE-only or Supervisor-only. The same document carries the commercial catch: each driver must still be licensed with sufficient Global Capacity available, and Global Capacity is purchased separately, so an included driver is not a free driver. Vendor-specific and legacy connectors, for example Carrier Comfort Network, Andover Infinity, American Auto-Matrix and McQuay, plus database and camera drivers on Supervisor, are paid options rather than included.

Who it fits. Heterogeneous brownfield estates nobody wants to rip out, where the requirement is to harmonise several vendors proprietary systems behind one layer. That is the standard answer Niagara exists for, and the Marketplace driver catalogue is the practical measure of its reach. It also fits OEMs and product companies that want to ship a branded building or device platform without writing a framework, through the Powered by Niagara programme, and organisations with a strong security mandate, given the security dashboard, code signing, FIPS 140-2 Level 1 and 802.1X support.

Who it does not fit. Anyone expecting to buy a product. There is no out-of-the-box operator interface, no published price, no public licence tier table, an undocumented edge licensing scheme, a mandatory active Software Maintenance Agreement for cloud services, and even the free trial requires an existing reseller relationship. Owners who cannot sustain a relationship with a competent integrator, or who want a vendor to be accountable for the user interface and logic quality, should buy a finished head-end instead.

Typical use. Integrator-engineered multi-site estates, campuses, data centres and smart city projects, with JACE or Edge 10 controllers at the edge, a Niagara 4 Supervisor above them, and Cloud Suite services layered on. Tridium names its audiences as systems integrators, specifying engineers, developers, energy managers, facility managers, cybersecurity teams and manufacturers, which is the clearest signal of who actually buys it.