Service
PX graphics and standard sheets
Most PX estates are not a graphics problem, they are a duplication problem: eighty sheets that were copied, hand-edited and now disagree. The fix is a small set of bindable standard sheets and a rule for applying them.
- PX templates
- Relative ORDs
- Nav hierarchy
- Graphics standard
- Retrofit
The duplication problem
A site with forty AHUs typically has forty AHU sheets. They started as one sheet, copied. Then a set point moved on unit twelve, a label was fixed on unit nineteen, and someone added an override on the four units in the east block. Now a change to "the AHU page" is forty edits, and nobody is confident they all match.
A standard sheet solves this the way Niagara intends: one PX file per plant type, bound with relative ORDs, pointed at a different equipment node each time it is opened. Forty units, one sheet. A change is one edit and it lands everywhere at once.
Scope
| Item | What it means in practice |
|---|---|
| A sheet per plant type | AHU, FCU, VAV, chiller, boiler, LTHW/CHW circuit, meter, zone, plant overview. Drawn once, to a consistent layout, with the same control affordances in the same place on every one. |
| Relative binding | Sheets bind relative to the equipment node they are opened against, so one file serves every instance of that plant type. |
| Navigation | A nav tree and landing pages — site, building, floor, plant — so an operator reaches any unit in three clicks and never needs the Workbench tree. |
| Alarm and status conventions | One colour and shape language for healthy, running, warning, fault and stale, used identically on every sheet. Defined in writing so it survives the next engineer. |
| A written graphics standard | The document your team applies on the next project: naming, layer structure, the token palette, what gets a standard sheet and what does not. |
| Retrofit of an existing estate | Auditing what is there, identifying the real variants behind the eighty sheets, and collapsing them onto the standard set — normally the larger half of the work. |
PX or bajaux? PX sheets are the right answer for plant views your own engineers must be able to edit in Workbench without a developer. bajaux widgets are the right answer when a view has to be responsive, has behaviour no stock widget offers, or carries a brand. Most sites want both, and the two are designed to sit on the same page — a bajaux widget drops into a PX sheet like any other widget.
Deliverables
What you actually receive
Fixed price per deliverable, quoted against a written specification. No hourly billing, and no price before the scope is in writing.
| Deliverable | Detail |
|---|---|
| The standard sheet set | PX files, relatively bound, in a module or a shared folder, ready to point at any equipment node. |
| Navigation | Landing and nav pages wired to the sheet set. |
| A graphics standard document | Conventions written down, so the standard outlives the project. |
| A migration list | If retrofitting: which existing sheets map to which standard, and which genuinely need to stay bespoke. |
Also
Other services
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.
bajaux widgets
Custom Niagara web widgets built with bajaux and BajaScript: HTML5 dashboards, navigation, equipment views and charts, bound to live station ORDs and BQL.
Station engineering
Niagara station and controller setup end to end: platform commissioning, TLS, users and roles, BACnet and Modbus, tagging, histories, alarms, backups.
Workbench tooling
Custom Workbench views and tools for repetitive Niagara work: bulk renaming and retagging, station audits, provisioning helpers and module inventories.
Niagara 5 migration
Niagara 5 readiness audits and migration: which third-party modules survive the new runtime and mandatory signing, and porting your modules so they load.
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.