A Cloud In TheSky

The best informations source on the internet for Niagra related questions, will always be Tridiums official Niagara Community - Remember to use the search button before asking any questions, and that although an answer might be 5 years old, many basic functions remains the same today.

So, what is this Niagara Framework (Framework), I keep talking about, you might ask?

Basically it's a computer system (Framework), that can be run in a windows PC (Supervisor/server) or a unix based controller, and is programmed primarily from a Windows PC (Workbench). Niagara is maintained and developed by Tridum, owned by Honeywell International. Centraline and Trend Control Systems are both using the Niagara framework.

Niagara has in my opinion 4 primary functions:

• First, controlling output and input points (IO), which in turn can control all kind of actuators, motors or sensors.
• Second, integration of pretty much any network (Driver) or system you can imagine. My personal favorites being Bacnet, Modbus. But can also do more exotic things like MQTT.
• Freely programmable using functions blocks or java code.
• Presentations from a webserver (Any framework installation contains build in web server)

Licensing is working really well in the framework. The standard method is using “The” licensing server, it contains licenses for both technician workbench, supervisor or controllers. Any installation of the framework generates a Host ID, any licensing is bound to this Host ID.

Normally your company would create a partnership with the preferred system provider, which offers training courses and after this, the technician can obtain a license for a workbench PC. Both partnership and workbench license would be an annual-fee-type-of-deal. A technician license is “unlimited” for programming, and testing purposes. But if using exotic drivers in developing, might require an extra license for the driver.

Installing the workbench program on a windows pc, obtaining the Host ID and ordering a license from the system provider, turns the PC into a supervisor/server. A supervisor license also contains an amount of points, each hardware or driver point can count towards the limit. Programming points isn't counted.

Controllers of a specific provider is primarily based on the same processing unit, what matters is how many points you order with it. It comes with a pre ordered amount of points, usually cheaper then buying points afterwards. But here you get the Host ID from controller, and use it to order extra points if needed, after purchase, the extra license is fetched from the licensing server. Points in controllers don't count on supervisors too, you only pay once!

Common for all customer licenses is that after purchase, it is bound to that specific Host Id. I've never seen a license being moved. Workbench license can be moved to a new PC, but it's not something you do for fun.

A typical office customer setup would be comprised of the following:

• Supervisor (PC or Controller)
• Main controllers (1 pr floor typically)
• IO Room controllers connected to main controllers (1 pr 1-2 room)
• Airhandling unit with integrated controller connected to supervisor or main controller
• Airhandling unit with direct IO controllers from a main controller or dedicated controller.
• Any integration from light or other, connected to main controller or supervisor.

All network connections is preferred to be TCP/IP but serial 2 wire connections is widely used too.

Best practice is to keep as much programming and calendars as local as possible. Meaning, if you can keep a 0 point supervisor, it's preferred. Also, direct signal transfer from controller to controller is preferred. This way, if supervisor restarts, controllers keep running their programs.

The supervisor is then used for collecting alarms, history data and proxy points from controllers, to present on a website.