Fields
Fields we work in
Seven fields, one core: read the system, name its data, act on it safely, show it, hand it over. Each field below lists the jobs it usually means, the roles a project in it is staffed with, and the case studies, tools and notes that show the work.
Building automation
Building automation and Niagara
Stations, modules, schedules, alarms and the Niagara 5 move. JACE-8000 is the usual target. The building automation page →
Typical jobs
- Station engineering and clean-up
- Custom Niagara modules, signed
- Niagara 5 module scan and audit
- Workbench tooling
Who is on it
- Project lead
- Integration and software
- Interfaces
Projects
- A Niagara module workshop — ux widgets, PX graphics, signing and a licence issuer, built for a JACE-8000 on Niagara 4.14 and tested on a licensed station.
- Fourteen read-only station tools — One-file scanners for modules, schedules, alarms, BACnet priority and Modbus addressing, each MIT-licensed.
The work and notes behind it
Connected devices
Connected devices and LoRaWAN
Sensor fleets, payload decoders and the firmware behind them, into whatever platform has to read them. The connected devices page →
Typical jobs
- Payload decoders, tested against real frames
- LoRaWAN and MQTT into a platform or station
- Device fleet back ends
- Firmware review
Who is on it
- Project lead
- Hardware and firmware
- Integration and software
Projects
- An industrial IO gateway firmware — One ESP32 image carrying WiFi, Ethernet and GSM with a priority order, Modbus RTU/TCP to MQTT, 130 host test cases and a Modbus capacity stress harness on bench hardware.
- A LoRaWAN occupancy platform — Sensors, decoders, a Rails back end and an operator web app for a device fleet, worked on alongside other engineers.
The work and notes behind it
Systems integration
Protocols and systems integration
BACnet, Modbus, MQTT, oBIX and REST between systems that were never meant to talk. The systems integration page →
Typical jobs
- Gateways and drivers
- Point maps that survive a handover
- Integration audits
- Data out of a station into a platform
Who is on it
- Project lead
- Integration and software
Projects
- A station connector API — A write-capable JSON API inside a Niagara station with a fleet dashboard in front of it, under-privileged by design.
The work and notes behind it
AI agents
AI agents on live systems
Letting a language model read a control system, and deciding what it may never write. The ai agents page →
Typical jobs
- MCP servers over building data
- Read-only by default, writes gated
- Agent tooling for engineers
Who is on it
- Project lead
- Integration and software
Projects
- An AI engineer for Niagara — A signed station module plus a self-hosted app that lets a model read, query and engineer a station through 45 tools, with every write scoped.
- An oBIX MCP server — Read-only bridge from an AI agent to a live station.
The work and notes behind it
Interfaces
Operator interfaces and dashboards
Graphics and dashboards operators look at all day, built against the live data model. The interfaces page →
Typical jobs
- PX graphics
- bajaux widgets
- Web dashboards over plant data
Who is on it
- Project lead
- Interfaces
- Integration and software
Projects
- Operator dashboards as bajaux widgets — Plant dashboards running live in the browser against a simulated station.
The work and notes behind it
Web and DevOps
Web apps, sites and DevOps
The web app nobody can deploy, the spreadsheet a business runs on, and the site that sells it. The web and devops page →
Typical jobs
- Spreadsheet to web app
- Deploy pipelines and hosting
- Fast static sites
- HTTPS and certificate moves
Who is on it
- Project lead
- Integration and software
Projects
- A weather-aware truck routing app — Three candidate routes scored on the forecast at the hour the truck reaches each checkpoint. Django API, React and MapLibre, no API keys.
- A market-intelligence dataset — A local service market scraped from maps listings, enriched from each business's own site, verified, and turned into a SaaS specification.
- This site — One Python file, no framework, every claim gated by a check that a sabotage run proves.
The work and notes behind it
Hardware
Hardware, enclosures and 3D printing
Boards, firmware, SOLIDWORKS enclosures and printed parts, for the projects that need something physical. The hardware page →
Typical jobs
- Electronics and PCB layout
- Firmware
- Enclosures in SOLIDWORKS
- 3D-printed parts and fixtures
Who is on it
- Project lead
- Hardware and firmware
- Mechanical design
Projects
- A printed display part, design to bed — Modelled in code, validated as a printable mesh, sliced and printed in ABS on an enclosed CoreXY printer, first time. The render below is the model; no photograph of the print is published.
The work and notes behind it
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.