Niagara Workbench

Workbench is where Niagara engineers spend their day – and most of them are doing something repetitive that a tool could do faster. Software Pile builds Workbench extensions and engineering utilities that turn hours of clicking into minutes of review.

Tools We Build

  • Bulk operations – mass tagging (including Project Haystack), renaming to naming standards, point re-parenting, and property edits across whole station trees
  • Station audits – automated checks against your engineering standards: orphaned points, missing histories, alarm classes without routing, license headroom
  • Custom views and managers – purpose-built Workbench views for tasks your team does constantly that the stock views make slow
  • Deployment utilities – checklist-driven station commissioning, config export/compare between stations, and pre-cutover validation
  • Migration helpers – inventory and readiness tooling for AX-to-N4 moves

Why Integrators Commission These

The math is simple: a tool that saves each engineer an hour a week pays for itself across a team in a quarter – and it encodes your standards, so quality stops depending on who did the work. Tools are built as proper signed modules, versioned, and documented for your engineering group. White-label delivery for integrators is standard.

Start With the Bottleneck

Describe the task your engineers grumble about – what it involves, how often, on which Niagara versions. We will tell you what a tool would look like and what it would save.

What Is Niagara Workbench?

Workbench is the engineering tool for the Niagara Framework. It is the desktop application used to build and configure stations: wiring logic on the wiresheet, configuring drivers and points, building Px graphics, managing users and permissions, setting up histories and alarms, and provisioning controllers. Operators generally use a browser; engineers use Workbench.

It is also a platform in its own right. Workbench can be extended with custom views, tools and wizards, which is what makes it possible to automate engineering work that would otherwise be done by hand across hundreds of points.

What Is the Difference Between Workbench and Workbench Web?

Workbench is the full desktop engineering environment with the complete toolset. The browser-based experience is aimed at operational and lighter configuration tasks and does not replace it for engineering work — module development, wiresheet engineering at scale and platform-level provisioning belong in the desktop tool. Check what your Niagara version and licence actually permit, as capabilities differ by release.

What Can You Build as a Custom Workbench Tool?

Anything repetitive an engineer currently does by hand is a candidate. In practice the tools that pay for themselves fastest are:

  • Bulk tagging and point naming — applying a naming or Haystack tagging standard across thousands of points instead of one at a time.
  • Station audits — reporting on points with no history, alarms with no recipient, disabled devices, duplicated logic, or drift from the site standard.
  • Deployment and provisioning utilities — pushing a standard configuration to many controllers consistently.
  • Migration helpers — mapping and validating changes during an AX to N4 migration.
  • Import and export tools — getting engineering data in and out of spreadsheets or an asset system without manual re-keying.
  • Commissioning checklists — verifying a station against a standard before handover and producing the evidence.

Which Workbench Version Do You Need?

Workbench version must be compatible with the stations you are connecting to, and a tool built for one Niagara release will not automatically load in another. If you support an estate spanning several Niagara versions — which most integrators do — version compatibility is part of the tool’s specification, not an afterthought. Tools are built and signed against defined target versions, and retesting is part of any station upgrade.

Is a Custom Tool Worth It?

The arithmetic is usually straightforward: multiply the time a task takes by how often it happens across your estate, and compare it to a bounded development effort. A tagging task that takes an engineer two days per building, repeated across twenty buildings, is a clear case. A task done once a year is not.

The second argument is consistency rather than time. A tool applies the same standard every time; a person working through a point list at 5pm does not. For anything that feeds reporting, analytics or a tagging model, that consistency is often worth more than the hours saved.

Related services: Niagara engineering tools · custom module and driver development.