Service
Workbench tooling and bulk engineering
The repetitive work that quietly eats project hours — renaming four thousand points, applying tags by hand, auditing a station before a migration. Tools your engineers run themselves, inside Workbench.
- Bulk rename
- Retagging
- Station audit
- Provisioning
- BQL
- Repeatable
The economics
Bulk engineering is the clearest return in the whole Niagara toolchain, because the work it replaces is measured in engineer-days and the tool is written once. A rename that takes two engineers a week across an estate is a rule set and an afternoon. The point is not only the time: a scripted change is uniform, and a hand-edited one is uniform right up until somebody's concentration lapses on row 1,900.
Tools commonly asked for
Bulk rename and retag
Pattern-driven renaming and tagging across a station or a Niagara Network, with a dry-run that shows every proposed change before anything is written, and a CSV of what actually changed afterwards.
Station audit
A report on what is actually in a station: points without histories, histories without consumers, alarms nobody has acknowledged in a year, duplicate schedules, orphaned components, poll load by device.
Module inventory
Every third-party module across an estate, with its vendor, version, signature state and stamped Niagara version — the document you need before scoping any migration.
Mass configuration
Applying history extensions, alarm extensions or display names to thousands of points from a rule set or a spreadsheet, rather than through the property sheet.
Provisioning helpers
Repeatable jobs across a Niagara Network: pushing a module version, running a batch job, collecting backups, verifying that every station is on the version you think it is.
Export and reporting
Scheduled extracts from BQL queries to CSV, a share or an API, for the monthly report somebody is currently assembling by hand.
Every bulk tool ships with a dry run. A tool that writes four thousand changes to a live station without showing you the diff first is a liability, not a saving. Preview, then commit, then a record of what changed.
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 |
|---|---|
| A Workbench view or tool | Installed as a module, run by your engineers from Workbench — not a script only the author can operate. |
| A dry-run report | Every proposed change, previewable and exportable, before anything is written. |
| A change record | CSV of what was actually written, so the job is auditable after the fact. |
| A short operating note | One page. What it does, what it will not touch, and how to reverse it. |
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.
PX graphics
Niagara PX graphics as a reusable template set: standard sheets per plant type, relative-ORD binding, navigation hierarchy and a graphics standard.
Station engineering
Niagara station and controller setup end to end: platform commissioning, TLS, users and roles, BACnet and Modbus, tagging, histories, alarms, backups.
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.
Notes
Written up in more detail
The engineering behind this service, in public, with no pitch attached. All notes.
Renaming and tagging points in bulk
Point names arrive from the field device and there is no standard. What to use to select, rename and tag in bulk — and what a rename quietly breaks.
- Bulk engineering
- Tagging
- Workbench
Scheduled station backups, and the gap
A Supervisor can back up every station in its Niagara Network on a schedule. The station it does not cover that way is its own.
- Backups
- Provisioning
- Supervisor
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.