Describe the sequence and the agent builds it on your Tridium Niagara station — a Guideline 36 AHU, or something no guideline covers. It plans the sheet, finds the blocks in your own palettes, wires them in columns, and applies nothing until you press apply.
niagara module install wiresheetDriver-rt.jar01/The workspace
Nav tree, wiresheet, property sheet and point manager, rendered live from the station. Pan it, zoom it, click a block. Nothing here is a screenshot.
02/What you get
Minus the laptop image and the licence seat.
Blocks, ports, links and the values flowing through them — redrawn from the station's component space, not exported once and left to rot. Pan, zoom, select, follow a link to its source.
Every slot with its real type, facets and status flags. Tuning parameters where you expect them.
Discovered points with live values, status flags and trend, filterable across the whole station.
Supervisors, JACEs and remote stations under a single hierarchy. Jump between a site's AHU sheet and its boiler plant without opening a second tool, and search components across all of them at once.
The workspace opens read-only. Commissioning mode is an explicit, per-session switch — and the agent cannot write a single slot without it.
Who, when, which ORD, the value before and the value after. Exportable, and the same record whether a human or the agent made the change.
14:02:31 agent · SET AHU_1/MinOffTimer.minimumOffTime +00:03:00
13:47:08 a.morgan · LINK FanCall.out → MinOffTimer.in
11:20:55 a.morgan · OVERRIDE AHU_1/SaSetpoint 58.0
03/The agent
The agent reads the station, proposes a concrete diff against real ORDs, and waits. Nothing reaches the JACE until you apply it in commissioning mode.
04/Rollout
No cloud migration, no re-engineering, no touching your control logic to get started.
Drop wiresheetDriver-rt.jar into the station's modules folder and add the driver under Drivers. One restart, no other station changes.
> niagara module install wiresheetDriver-rt.jar
> station restart
Give the workspace the station's address and a station account to use. The credentials are sealed on the server; nobody's browser is ever handed them.
station https://jace-01.example
account wiresheet · sealed AES-256-GCM
The station's component space appears in your workspace within seconds. Invite your team, set who can commission, and put the agent to work.
app.wiresheet.ai/workspace/hq-jace-01
→ 4 218 points · 34 ms
05/Architecture
One place holds the credentials, one path performs the writes, and the station keeps the record. Small enough for an IT team to check rather than take on trust.
The browser holds no credentials
It has no route to a JACE and no account on one. Every read and write goes through the server, which holds the station's own login — so a tab left open on a train is not a way into the station.
Per-station credentials, sealed
Each station carries its own address and account, encrypted with AES-256-GCM before it is stored. Change one and only that station is affected.
Read-only by default
Commissioning is an explicit per-session mode gated by role. Without it, the API refuses every write, including the agent's.
Nothing applied silently
The agent produces a diff against real ORDs. A human presses apply. There is no autonomous-write mode to turn on.
Your network
reached by the server
JACE / Supervisor
wiresheetDriver-rt.jar
Field devices
BACnet · Modbus · Lon
Wiresheet.ai
holds the credentials
Server
the only thing that logs in
Agent runtime
proposes · never auto-applies
AuditHistory
read from the station
Credentials
server-side
At rest
AES-256-GCM
Write path
human-gated
Audit
the station's own
06/Pricing
Nothing here counts your estate — a site with forty small JACEs costs what one large Supervisor does. We're still settling the commercial side, so it starts with a conversation.
The station in the browser, and an agent that builds on it.
talk to us
Contact salesPrices exclude VAT · no station or point limits · Tridium licences sold separately by your integrator
07/Questions
If yours isn't here, ask us directly — we answer with specifics, not a discovery call.
Tell us which station you want to start with and we'll set it up with you. Pairing takes about ten minutes once the account exists.
Niagara 4.10 → 4.15 · credentials server-side · writes human-gated