Services
What a job is scoped as, and what you get for it
Eleven deliverables rather than eleven offers: these are the shapes the work takes once somebody sends the station, the module, the export or the spreadsheet it has to live with. Four need no building automation system at all, two have no building in them, two run inside a building automation system on Tridium Niagara, and three are done to stations and estates. Each is quoted as a fixed price against a written specification agreed before any work starts, with the deliverables listed first and monthly care available afterwards.
Devices, data and the web
Work that needs no building automation system, and no building, to be useful.
Integration audit
A fixed-scope paid audit of an existing integration: what talks to what, where it breaks, and what fixing it would take.
Read moreIoT & LoRaWAN
Custom IoT and LoRaWAN builds: decoders that survive a station, a self-hosted ChirpStack server, MQTT, and the points or dashboards the readings become.
Read moreProtocols & data
Field protocol integration and the data behind it: BACnet, Modbus, M-Bus and MQTT, into a building system, a database or a dashboard.
Read moreWeb, apps & DevOps
Web and app builds with the DevOps around them: front end, backend, the database under it, and the build, deploy and monitoring work that keeps it up.
Read moreSoftware with no building in it
Work for the office rather than the plant room: a site, and the workbook the team runs on.
Website design
Remote website design services for small firms: a few real pages, fixed price, and a measured handover — HTTPS, broken links, Lighthouse, page weight.
Read moreSpreadsheets & internal tools
An audit of the spreadsheet a team runs on — every rule it encodes, and which ones contradict each other — then one bounded slice of it as a web app.
Read moreBuilding automation: inside the station
Software that runs on a Niagara station and is installed into it.
Custom modules & drivers
Bespoke Niagara rt, wb and ux modules and drivers written against the Baja API: pure Java, signed, and stamped to install across a mixed estate.
Read moreOperator graphics
Niagara operator screens built once and reused: standard PX plant sheets bound by relative ORD, bajaux web widgets and dashboards, and a written standard.
Read moreBuilding automation: stations and estates
Work done to a station, a site, or a fleet of them.
Niagara 5 migration
Niagara 5 readiness audits and migration, including JACE 8000 to JACE 9000: which third-party modules survive the new runtime and mandatory signing.
Read moreStation engineering
JACE controller and Niagara station setup end to end: platform commissioning, TLS, users, roles, BACnet and Modbus, tagging, histories, alarms, backups.
Read moreWorkbench tooling
Custom Workbench views and tools for repetitive Niagara work: bulk renaming and retagging, station audits, provisioning helpers and module inventories.
Read moreStart here
Not sure which of those a job needs?
Most of the list above is named in Niagara vocabulary, which is the right language once there is a station and the wrong one when there is a building. If the problem is still described in BMS terms — the graphics are unusable, that chiller will not come into the head end, nobody knows what is installed — start one level up.
Building automation software on Niagara explains where the framework sits in a BMS, what the software layer of a project actually consists of, and which of these each kind of problem turns into. It also maps the vocabulary both ways, so a quote is not lost in the gap between "trend log" and "history extension".
Engagement
How a piece of work runs
A conversation
Niagara version, target hardware, what exists today and what has to be true at the end. Usually half an hour.
A written specification
Scope, behaviour, failure behaviour, deliverables and what is explicitly out of scope. You keep it whether or not you proceed.
A fixed price
Against that specification. If the scope changes, the specification changes first and the price changes with it.
Build and review
Delivered in reviewable pieces rather than as one drop at the end, so a misunderstanding costs days instead of the project.
Handover
The signed module or the commissioned station, an installation note written for the commissioning engineer, and source where it is in scope.
Next step
Tell us the version, the hardware, and what it has to do.
You will get a written scope and a fixed price against it. If the honest answer is that you do not need us, you will get that instead.