Three things not fully covered: how BOB/MCP fits the emerging AI-over-BMS architecture Tridium is still planning, the full depth of IoT-LogIQ's interactive SCADA dashboard and widget platform, and the complete Smart Industry feature set beyond the 19 modules.
Tridium's own CTO confirmed this is the right pattern — and they haven't built it yet
Tridium's own CTO describes the AI pattern they are building toward — positioning Niagara as the data/control foundation for AI agents built externally.
Senzary has already built the exact pattern Tridium's CTO describes as the future — with Niagara JACE as the control/data layer and BOB as the operator AI agent on top.
500+ widgets · interactive SVG SCADA symbols · clickable controls that write to Niagara · responsive breakpoints
Full supervisory control and data acquisition interface — same visual language as traditional SCADA but cloud-served, mobile-responsive, and integrated with AI.
Dashboards adapt to screen size with dedicated layouts per breakpoint — a technician on a phone sees the same dashboard optimized for touch, not a pinched desktop view.
Each symbol displays live data AND sends commands when clicked — through IoT-LogIQ rule chain → BACnet WriteProperty → JACE
WriteProperty on the target output object — AO, BO, AV, or BV —
at the configured priority level. The JACE executes the control action. The SCADA symbol updates its visual state
within seconds as the telemetry confirms the new value. This is a full closed-loop visual control interface
over Niagara — not just a monitoring display.
Full suite of time-series and analytical charts for telemetry history, multi-sensor comparison, and trend analysis.
Buttons, sliders, toggles, knobs, and input fields that send commands to devices — direct write-back to Niagara via rule chain.
Entity lists, telemetry tables, alarm lists, and card displays for structured data presentation across devices and assets.
Geospatial asset visualization with real-time status overlays, worker location, gateway coverage, and click-through to asset detail.
Visual schedule management with complex recurrence — weekly patterns, holidays, exceptions — written back to Niagara or IoT devices.
Industrial alarm panel, alarm list, alarm count badges — with acknowledge workflow, severity filtering, and shift handover summary built in.
Battery level, signal strength, connectivity status, progress bars — for LoRaWAN sensor fleet health and gateway monitoring.
Upload a building floor plan and overlay device markers — click a device on the floorplan to see telemetry or send commands. Works for Niagara and LoRaWAN devices.
Embed custom HTML with live data bindings — build any bespoke display element without creating a full custom widget.
${telemetry.key} data injectionHTML5-based, browser-rendered HMI graphics. Excellent for detailed process visualization — but engineering-heavy and not responsive.
Cloud-served, fully responsive SCADA HMI + IoT dashboard platform. 500+ widgets. Sees all data sources. Configurable without Niagara certification.
All platform capabilities beyond the 19 InduMetrix modules — the full depth of what IoT-LogIQ delivers
| Feature Area | What IoT-LogIQ Provides | Niagara equivalent / gap |
|---|---|---|
| DEVICE & ASSET MANAGEMENT | ||
| Device Provisioning | Automatic device provisioning via token or X.509 — new sensors self-register on first connect. Provisioning templates define device profile, dashboard, alert rules for a device class — zero-touch for N sensors of the same type. | Niagara: manual device creation in Workbench per device. No auto-provisioning. Each LoRaWAN sensor added as a manual Niagara component. |
| OTA Firmware Management | Push signed firmware packages to LoRaWAN devices via ThingPark LRC. Rollback on failure. Track firmware version per device. Schedule OTA updates by device group. | Niagara handles JACE software upgrades via Workbench/platform. No LoRaWAN OTA capability. |
| Device Profiles | Define transport (MQTT/CoAP/HTTP), payload decoder, rule chain, default dashboard, alarm rules per device type. One profile governs all devices of that type — change once, applies everywhere. | Niagara: device templates in Workbench. Less dynamic — changes require re-engineering per station. |
| Entity Groups | Organize devices and assets into groups with shared RBAC, batch operations, and group-level dashboards. Example: "All Asystom vibration sensors — Site A" as one group. | Niagara: folder/network structure in station tree. Less flexible for cross-protocol grouping. |
| Relations (Entity Links) | Formal relationships between any entities: Asset "Chiller-02" → contains → Device "Asystom-001" + Device "BACnet-CH02-SAT". Any query traverses relations. Dashboard follows relation graph. | Niagara Haystack Relations Manager (N4.15) — similar concept but within single station only. |
| Asset Lifecycle Management | Asset profiles, maintenance history timeline, document attachments (manuals, datasheets, photos), QR code generation per asset, install/commission/decommission status tracking. | Niagara: no native asset lifecycle. BACnet device is not a business object with documents. CMMS integration required. |
| ANALYTICS & REPORTING | ||
| Trendz Analytics (Add-on) | Separate ML-powered analytics module. Forecasting, anomaly detection, Remaining Useful Life prediction, custom ML model integration. Drag-drop visualisation for complex multi-entity analysis. Natural language report generation via AI narrative. Auto-generated PDF/email reports on schedule. | Niagara Analytics Framework — algorithm/rule-based FDD. No ML forecasting, no automated narrative generation, no scheduled email reports with AI-generated narrative. |
| Rule Chains — Visual Programming | Cloud-side data processing pipeline: transformation nodes, filter nodes, switch nodes, enrichment from asset attributes, HTTP/REST call nodes, alarm creation nodes, RPC output nodes. JavaScript function nodes for any custom logic. Full visual editor. | Niagara WireSheet: local programmatic logic within station. Excellent for real-time control; limited for cloud-side cross-source data processing. |
| Scheduled Reports | Automated reports delivered by email/webhook on custom schedules. Dashboard snapshots, telemetry exports, alarm summaries. Configure recipients per report. PDF, CSV, or JSON output. | Niagara Analytics: standard report library available. Tridium-native scheduled reports exist but require Niagara Analytics license and are less flexible for cross-source multi-tenant scenarios. |
| Version Control for Dashboards | Full version history for dashboard configurations. Revert to any previous version. Collaborative editing with conflict notification — if two users edit same dashboard, conflict flagged with option to overwrite or discard. | Niagara: station backup/restore covers graphics. No dashboard-level version control in Workbench. |
| MULTI-TENANCY & ACCESS | ||
| White Labeling | Complete platform rebranding per customer — custom logo, color scheme, favicon, custom domain, login page. Each customer sees their own branded platform. InduMetrix, AirportIQ, RotaryIQ etc. are all white-labeled IoT-LogIQ instances. | Niagara: px graphics customizable per project. No multi-tenant white-label platform — each Niagara station is one organization's system. |
| Custom Menu per Tenant/User | Define unique navigation menus per customer scope, per role, or per individual user. An operator sees "Alarms" and "Map". A manager sees full analytics suite. An executive sees portfolio KPI dashboard only. Menu changes deploy without code change. | Niagara: nav tree configurable per station. Does not span multiple tenants or role-based dynamic menus across a portfolio. |
| Customer Hierarchy (Sub-tenants) | Three-tier model: System Admin → Tenant (Senzary customer) → Customer User (end-user of that customer). Tenants see only their data. Customers within a tenant see only their permitted assets. Senzary manages all tenants from one admin console. | Niagara: station-level user/role management. Niagara Cloud Suite adds portfolio-level remote access — not true three-tier SaaS isolation. |
| API Access Tokens per Tenant | Each tenant has independent API tokens — no shared credentials. Rate-limited per tenant. Full Swagger-documented REST API at /api/v1. WebSocket for real-time telemetry stream subscription. MQTT per-device tokens with TLS. | Niagara: NWS REST per station; marketplace REST servers vary. No single unified API across all buildings under one authenticated session. |
| CONNECTIVITY & EDGE | ||
| IoT Gateway Software | IoT-LogIQ IoT Gateway — installable on Linux/Windows/Raspberry Pi. Modbus TCP/RTU, OPC-UA, BACnet, MQTT, REST, Serial connectors. Translates and forwards to cloud. Manages local buffer during WAN outage. This is the software edge node, not hardware-dependent. | Niagara: JACE is the edge — hardware-tied. IoT-LogIQ Gateway runs on any Linux device as software-only. Lower cost for adding legacy device connectivity. |
| IoT-LogIQ Edge | Full IoT-LogIQ platform instance running locally at site. Runs rule chains, dashboards, and alarm management offline. Syncs to cloud when WAN available. Same Workbench, same API as cloud — consistent experience. Target: air-gapped or intermittent-WAN sites. | Niagara JACE: excellent offline local control. IoT-LogIQ Edge adds full dashboard + rule chain capability on-premise, not just control logic. |
| Multi-Protocol Device Connectivity | MQTT, CoAP, HTTP/HTTPS, LwM2M device APIs. BACnet/IP, Modbus RTU/TCP, OPC-UA, SNMP, Serial via gateway. LoRaWAN via ThingPark/ChirpStack AS integration. Any device with MQTT or HTTP connectivity onboards natively. | Niagara: superior native BAS protocol breadth (40 built-in drivers + 1700+ community). IoT-LogIQ broader for modern IoT protocols (MQTT, CoAP, LwM2M, LoRaWAN). |
| NOTIFICATIONS & ALARMS | ||
| Notification Center | In-platform notification system — bell icon with unread count, notification list widget on dashboard, push to mobile app. Configurable notification types: alarm triggered, device offline, rule action, system events. | Niagara: alarm console + email/SMS via Niagara drivers. In-app notification center is a marketplace add-on. |
| Alarm Rules — Multi-condition | Define alarm severity, condition (threshold, duration, rate of change), propagation delay, clear condition, repeat suppression window. Alarm can aggregate across multiple device telemetry keys. Assignable to user, with acknowledgement workflow and comment thread. | Niagara: advanced alarm system — well-developed for BAS. IoT-LogIQ extends to LoRaWAN + cross-source alarms with same management workflow. |
| Notification Delivery | Email, SMS, Slack, Teams, PagerDuty, webhook, in-app — configurable per alarm severity level and business hours schedule. Escalation chains — notify manager if technician does not acknowledge within N minutes. | Niagara: email + SMS via drivers. No native Slack/Teams/PagerDuty delivery. Marketplace connectors exist. |
| MOBILE & DEVELOPER | ||
| Native Mobile Apps | IoT-LogIQ-based iOS and Android native apps — full dashboard access, push notifications for alarms, QR code scanning for asset lookup, offline dashboard viewing for last-sync data. | Niagara: browser-based on mobile (px5 not responsive). Native Niagara mobile app does not exist from Tridium. Marketplace: Tyrrell, WSE offer mobile products. |
| Custom Widget Development SDK | Full JS/HTML/CSS widget development framework — any data visualization buildable as a custom widget. Access to telemetry, attributes, RPC calls, entity relations from within widget JavaScript. Contributing to widget library without platform code changes. | Niagara: Workbench-based px widget development. Custom Java module development for new functionality — requires Niagara certification and Java skills. |
| Solution Templates | Pre-built complete solution packages including dashboards, processing logic, device profiles, sample devices, users, rule chains. Deploy a full smart building, smart energy, or water monitoring solution from a template in minutes. InduMetrix modules are built on this capability. | Niagara: project templates in Workbench. Less complete — dashboards, not full end-to-end solution packages with data model and users pre-configured. |
| Resource Library | Centralized repository for shared resources: custom SVG icons, image files, font files, JavaScript functions, HTML templates. Resources available across all tenant dashboards. Eliminates duplicate uploads per dashboard. | Niagara: kit palette system for reusable graphic components. Platform-specific, not tenant-shared cloud resource library. |