Skip to content
Book a Demo
stacked Tridium Niagara 4
Tridium Niagara Map
stacked Tridium Niagara 4
Tridium Niagara Map
software
Data Management, Energy Management, Operations
use cases
Data Integration, Equipment Monitoring, FDD, Predictive Maintenance
Licensing
3rd party

Tridium Niagara

Tridium’s Niagara4 Framework provides the critical, cybersecure device connectivity and data normalization capabilities needed to acquire and unlock operational data from device-level and equipment-level silos. The control engine at the core of Niagara enables users to not just monitor data flows, but to create logic sequences that effect controls programming based on data observation.

 

Overview

What it does: Niagara N4 is a comprehensive software platform for developing, deploying, and managing smart devices and systems in buildings (HVAC, Lighting, Security).

Why it exists: It acts as a normalization layer, allowing disparate protocols (BACnet, Modbus, LonWorks, SNMP) to communicate and be managed from a single “Station” interface.

Who uses it: Facility managers, System Integrators (SIs), and OT (Operational Technology) teams

Contact us to add to Neeve
Benefits of Niagara Containers on Neeve
Through this unique partnership Tridium’s Niagara Framework can run within the container environment on Neeve Secure Edge, making it cloud managed and configurable – all within a fully managed service. For mission critical features the container can run across highly-available and redundant edge clusters for increased resiliency.
Simplify maintenance with managed hardware solution and cloud managed Niagara
Reduce maintenance and risk by minimizing hardware footprint
Access and normalize real-time data for all OT devices
Standardize automation across the portfolio with Niagara’s latest tools for creating logic sequences and controls
Improve resiliency with “edge cloud” clustered compute infrastructure
Deployment Architecture on Neeve
Niagara N4 requires a license tied to the Host ID
Deployment model: Singleton (One pod per building/environment). Scaling is vertical (CPU/RAM) rather than horizontal due to the stateful nature of “Stations.”
Workload: High-memory, stateful Java application.
Data flows: * TCP 1911/4911: Fox/Foxs (Niagara-to-Niagara communication) | TCP 80/443: Web UI access. UDP 47808: BACnet/IP (if applicable).
Failure domains: Single instance. Loss of the pod results in loss of real-time control and history logging until the pod restarts.
Pro tip: In a containerized environment, ensure the Host ID is stable (often mapped to the MAC address or a persistent volume UUID) to prevent licensing failures.