If you’re managing a facility with standard HVAC/mechanical systems, you probably have some form of a Building Management System (BMS). Like how the iPhone changed communication with its launch in 2007, BMS have fundamentally changed how you communicate with your building’s equipment. Your BMS or Building Automation System (BAS) communicate to your equipment through either open or proprietary protocols.
The difference between open and proprietary protocols
All of the major BMS branches sell a proprietary product that only their branch can work on. This is the difference between proprietary and open protocols. It also means that if that system needs to be serviced, it requires a technician with a workbench for that particular system.
At Fairbanks Energy Services, we want customers to have a controls system they are comfortable working with and can be serviced by any contractor with any workbench. We are going to reuse and integrate into as many of the existing controllers and field devices as possible to keep project costs down. At the end of the project, our customer can choose whichever service provider they like working with to support the system over its lifetime. Every manager should make his or her own decision about whether to work with open or proprietary controls.
The typical open protocol sits in the Niagara framework
The BMS “open protocol” we often integrate into BMS resides in the Niagara framework. Tridium is the company that built the Niagara network and makes all of the JACEs (Java Application Control Engine) that host Niagara.
Most mainstream controls companies have open protocol products besides their proprietary solution as well. They include:
- Tridium – Vykon
- Johnson Controls – Facility Explorer
- Honeywell – WEBs
- Distech – EC-Net
- Siemens – TALON
- Schenider Electric – EcoStruxure
- Lynxspring – JENEsys
A note – Fairbanks Energy is a brand agnostic company, meaning that we are solutions engineers; we engineer every project to its own specifications and select the best product solutions for the space, regardless of manufacturer. While Tridium is the company that built the Niagara network, it is this framework into which any open protocol can connect, thus allowing us the freedom to build a BMS system that’s right for each customer.
Changes and challenges in the old AX controls framework – a brief history lesson
Niagara has been through three iterations in the last 30 years: R2, AX and now N4. Most sites with Niagara have a version of AX running in their buildings right now. Before N4, there were expensive limitations to some of these legacy JACEs and it made it very difficult to upgrade sites because of the need to often install new hardware.
Some of the individual JACE pain points included:
- Decreased capacity with multiple systems on the same JACE
- High cost of ownership having to license each protocol – each driver was purchased separately in AX, which meant that you had to purchase a driver for each protocol that was communicating back to the JACE
- Ordering was difficult and nonrefundable, so if you ordered MODBUS TCP and needed MODBUS RTU, then you would be stuck with having to buy a driver twice.
- Limited number of ports available to connect additional buses. It was built with a single RS485 port and therefore might require the installation of dual port cards.
On the supervisor side of things in AX you had three options:
- 3 stations
- 100 stations
- Unlimited stations.
And that was it. You had to pick one of those three tiers and too bad if you had 4 or 5 stations – you’d have to pay for 100.
These issues aside, the biggest challenge with the original Niagara AX structure was JAVA (the “J” in JACE). JAVA was prone to crashing, causing major issues in sites and making the JACES “lock up” and no longer be able to function, called bricking. Because AX relied on JAVA, its updates would cause the controller to need to be rebooted with new security patches, making the process time consuming and frustrating.
Fortunately for facility mangers everywhere, the brains at Niagara kept working to develop the much-improved solutions available today.
The open protocol solution: Niagara N4 + the JACE-8000
The new JACE developed to solve these struggles was the JACE-8000. Ironically, Niagara kept the name JACE although the JACE-8000 does not use JAVA at all. The JACE-8000 is now the only JACE being sold. It is no longer licensed based off point count and protocol but is now based off of device count (each device is allotted 25 points). This update allows for a facility manager to easily expand by simply adding additional device capacity. All of the drivers are built into the JACE-8000 and it comes with a dual port RS485 card. Should you have greater need, more cards can be snapped right into the JACE.
In addition to developing a new JACE, Tridium moved away from JAVA with their new platform, N4. In contrast to the AX version supervisor, now in N4 you can adjust the size of the supervisor based on exactly how many Niagara connections you are bringing into it. The N4 supervisor also allows for a site to add IP devices directly to the supervisor. This was not even an option in AX where it would have been cost prohibitive to add an IP driver plus individual points packs. Some additional changes to N4 included:
- Additional security
- HTML5 Graphics (much better than AX)
- Ease of upgrades
- Does not rely on JAVA
- Has become the building standard for all open protocol systems
Ultimately, N4 is the modern choice for facility BMS and the old AX systems are no longer supported.
What does this mean for you?
It’s great news. You can upgrade any site to N4 by replacing the existing JACE(s) with the JACE-8000. Also, if you have a site with a lot of AX JACEs, they can be updated with a piece of software added to the last version of AX 3.8 and brought right into the new N4 supervisor. This allows for a gradual upgrade path if an entire system replacement isn’t a current option. Either way, ensuring BMS are modernized to current tech means a better functioning facility, improved energy efficiency and more informed decision making.
Originally published on April 24, 2019 | Last updated on 10/01/2019
READ MORE POSTS LIKE THIS ONE
Sign up to receive the previous month's content right in your inbox in one, easy-to-read email.