Every tool on this page exists because a Niagara job needed it. None of it was built to be a product — it was built because a station audit took three days by hand, or a commissioning handover kept missing points, or someone needed histories out of forty stations before Friday. That is the honest origin of an engineering toolkit, and it is also the best evidence of what a team actually does day to day.
What follows is our working set for Niagara Framework delivery: diagnostics, commissioning validation, data export, station automation, integrations, and a developer toolkit. Status is stated for each — some are mature utilities we run regularly, some are prototypes we are still refining.
Station Diagnostics and Fleet Reporting
Station Metrics is a Java-based collector that inventories local and remote Niagara stations and produces CSV and HTML reports — effectively CMDB-style reporting across a fleet. It gathers station availability, host and platform identity, Niagara and operating-system versions, CPU, memory, heap, thread and runtime information, Fox sessions, installed software and module status, device products and driver information, station connection state, and the errors and warnings worth investigating.
It supports authenticated remote collection, local platform inspection, and — importantly — down-station reporting, because the stations you most need to know about are usually the ones not answering. Data is gathered through BQL, Spy, resource, and platform sources and consolidated into one view.
Status: working prototype, actively refined.
Commissioning Validation
The BMS Integrity Checker answers a question every commissioning engineer knows: does what was actually installed match what the Control Point List specified? It imports exported Niagara alarm and trend configuration alongside the project CPL spreadsheet, normalises naming and configuration differences, matches installed points against design requirements, and evaluates alarm classes, notification levels, delays, and trend intervals.
The output is a colour-coded Excel compliance report — green for compliant, red for mismatches, yellow for conditions needing engineering review — with separate Siemens and Schneider validation paths. The point is to replace manual, point-by-point verification with something repeatable, so handover discrepancies surface before the client finds them.
Status: functional engineering utility.
Data Export and Interoperability
- Mass History Export — exports many station histories in a single operation and packages the results into one ZIP archive. Built for bulk extraction ahead of analytics work, commissioning, backups, and customer handoff.
- BQL-to-JSON Exporter — runs BQL queries and transforms the results into structured JSON that dashboards, APIs, reporting systems, websites — and increasingly AI agents — can consume directly.
That second one matters more than it looks. Getting station data out in a clean, structured form is the prerequisite for everything downstream: analytics, portfolio reporting, and any credible AI layer over building operations. An agent reasoning about a station is only ever as good as the data model it can read.
Status: utility projects, in regular use.
Station Operations and Automation
- Automatic Backup and Email — scheduled station backups, packaged and delivered with status reporting, so backups are a routine rather than a task someone remembers.
- SFTP/SSH Client — secure exchange of station files, reports, backups, configuration packages, and generated web content.
- Scheduling Utility — create, modify, copy, and manage occupancy and equipment schedules programmatically instead of through repetitive Workbench operations. Anyone who has hand-edited schedules across dozens of stations understands the value immediately.
Status: utility projects.
Integrations
MQTT client and utilities for publishing and subscribing to equipment, sensor, alarm, and control data — connecting MQTT messaging to Niagara for IoT, edge, and cloud-bound telemetry. Status: working prototype, actively refined.
OpenWeather integration brings public weather data into a station for dashboards, control strategies, outdoor-air reset, energy calculations, and forecasting — a small integration that pays for itself the first time a reset schedule uses real outdoor conditions. Status: integration utility.
Interface and Visual Customisation
A set of projects for bringing darker themes and better styling into Niagara dashboards, Workbench-related interfaces, and browser-based station pages — including theme generators and BajaScript/Bajaux interface work. Operators stare at these screens for entire shifts; legibility is not cosmetic. Status: working prototype, actively refined.
Developer Toolkit and Knowledge Base
An ongoing collection of Niagara development resources that shortens the distance between a requirement and a working module:
- BQL query libraries and remote-query examples
- Gradle plugins and Niagara module templates
- BajaScript tutorials and Fox session demonstrations
- Tag dictionary and converter examples for Haystack tagging
- KitControl component libraries and sample stations
- Automated testing and CI/CD demonstrations
- Module installation guides, plus Niagara REST, oBIX, and FRPC experiments
Status: ongoing reference and development collection.
Why a Toolkit Is Worth Asking About
When you are choosing a Niagara partner, the tools they have built are a better signal than the capabilities they list. Tooling only accumulates where the same problems have been hit repeatedly and solved properly — fleet visibility, commissioning accuracy, getting data out cleanly, not doing the same Workbench task four hundred times.
Much of this is deployed on client work rather than sold as products, and we will say plainly which is which. If a network problem sits underneath a station issue, our sister practice covers BACnet and OT network diagnostics; if the goal is AI over building operations, that runs through Software Depo.
Tell us what is slow, manual, or unverifiable in your Niagara estate — fleet reporting, commissioning validation, history extraction, or schedule management — and we will tell you whether we already have something for it.