One of the most common questions we get from clients planning a Niagara N4 deployment is whether they need a JACE, a Supervisor, or both. The short answer is that it depends on how many buildings you are managing, how many points you have, and what you need the system to do at an enterprise level. Here is the practical breakdown.
What a JACE Actually Does
A JACE (Java Application Control Engine) is an embedded hardware controller made by Tridium that runs the Niagara Framework directly on the device. It handles several functions simultaneously.
First, a JACE communicates with field-level devices: DDC controllers, meters, VFDs, chillers, and other equipment using BACnet, Modbus, LON, and dozens of other protocols. It polls those devices, stores their data, and executes control logic.
Second, a JACE runs a local copy of the Niagara front end, so an operator can connect directly to the JACE via a web browser and see a graphical interface of the building systems. This local capability is important: if the network connection to a central server goes down, the JACE keeps running and keeps controlling, and a local operator can still access the interface.
Third, a JACE can run its own control programs, logic, and alarms independent of any upstream system. In a single-building scenario with no higher-level supervisor, the JACE is the entire system.
The practical point capacity of a JACE 8000 is roughly 500-1,000 points in comfortable operation. You can push it higher, but performance starts to degrade, and you lose the snappiness that makes a front end pleasant to use. The JACE 8000 hardware runs approximately $3,000-$5,000 including Niagara licensing, depending on the license tier and point count you need.
What a Niagara Supervisor Does
A Niagara Supervisor is not a hardware device. It is a software installation of the Niagara Framework that runs on a standard Windows or Linux server (physical or virtual). Unlike a JACE, a Supervisor has no field device connections of its own. It is purely a management layer.
The Supervisor connects to multiple JACEs across a campus or building portfolio and aggregates their data into a single interface. An operator logging into the Supervisor sees every building, every system, and every alarm from one place. The Supervisor handles enterprise functions that a JACE is not designed for:
- Multi-building alarm management. Route alarms to different technicians based on building, equipment type, or time of day. Escalate alarms if they are not acknowledged within a set window.
- Role-based access control. Give a tenant access to see only their floor's temperature sensors. Give a property manager read-only access to their specific building. Give your service team full access to everything. These permission structures are straightforward to configure in a Supervisor.
- Portfolio-wide reporting. Generate monthly energy reports across all buildings automatically. Export trend data to Excel or to a connected analytics platform.
- Integration with enterprise IT systems. A Supervisor can connect to Active Directory for single sign-on, push alarm data to a ticketing system, and feed energy data to sustainability reporting tools.
A Supervisor server, including hardware (or virtual machine licensing), operating system, and Niagara software licensing, typically runs $8,000-$15,000 depending on the point count licensed and the server specifications.
When a JACE Is Enough
For a single building under approximately 200,000 square feet with a single dominant protocol (say, all BACnet), a JACE 8000 handles the job without needing anything above it. The scenarios where a JACE alone makes sense:
A single commercial office building where you have a maintenance tech on site who logs into the JACE directly. You are not managing multiple properties. Your alarm volume is low enough that a single inbox handles it. You do not need role-based access for different user groups.
A small campus with one mechanical room. If your "campus" is two buildings that share a mechanical room and one BAS front end serves them both, a single JACE with enough point capacity might cover it.
A tenant improvement where the building already has a Supervisor. If you are fitting out a single floor in a larger building that already runs a Niagara Supervisor, your new tenant space typically connects to the existing infrastructure rather than adding its own head-end.
When You Need a Supervisor
The signals that point toward a Supervisor are fairly clear:
Multiple buildings with multiple JACEs. Once you have two or more JACEs in different locations, a Supervisor gives you the portfolio-wide visibility that would otherwise require logging into each JACE separately.
Complex alarm routing. If you need alarms from one building to go to a different on-call person than alarms from another building, or if you need alarm escalation workflows, the Supervisor's alarm manager is where that logic lives.
Different user groups needing different access. Tenants, property managers, facility technicians, and executives all need different views of the same data. Role-based access in a Supervisor handles this cleanly.
IT system integration. If ownership wants building performance data in their ERP system, or if the security team needs HVAC systems to respond to access control events, the Supervisor is the integration point.
Point counts above 2,000-3,000. At this scale, trying to make a single JACE handle everything becomes an exercise in frustration. A Supervisor with multiple JACEs distributed across the facility is the right architecture.
The Hybrid Approach: Usually the Right Answer
For most multi-building clients, the answer to "JACE or Supervisor" is actually "both, in the right roles."
A JACE at each building handles local control, device communication, and local resilience. If the network between a remote building and the corporate Supervisor goes down, the JACE at that building keeps running without interruption. Local operators can still connect directly to the building's JACE and see what is happening.
The Supervisor at the corporate office or in the cloud aggregates data from all the JACEs, handles enterprise alarm management, generates portfolio reports, and provides the single-pane-of-glass view that portfolio managers and executives want.
This architecture scales naturally. Adding a new building means adding a new JACE and connecting it to the existing Supervisor. The Supervisor's capacity grows with it.
The most common mistake we see is clients who want to save money by not installing a Supervisor when they have five or six buildings. They end up with five or six separate JACE front ends, no unified alarm management, and no way to generate portfolio-wide reports without logging into each system individually. The $10,000-$15,000 Supervisor investment pays for itself quickly in reduced management overhead.
If you are planning a Niagara deployment and want to talk through the right architecture for your specific building count and requirements, we are glad to work through it with you.