If you work around building automation, you have heard the word JACE. It shows up in specs, on wiring diagrams, and in maintenance contracts, often without anyone explaining what it actually is. Here is the plain version: a JACE is the small but critical computer that makes a Niagara building system work at the edge — and understanding it makes the whole architecture click.
What a JACE Is
JACE stands for Java Application Control Engine. It is a compact, dedicated controller that runs a Niagara station — the software that connects to your field devices, runs control logic, stores trends and alarms, and serves the data upward. Physically it is a small device in a panel; functionally it is the on-site brain that keeps working whether or not anything above it is reachable.
That last point is the whole reason it exists at the edge. Because the JACE runs its logic locally, the building keeps operating — schedules run, alarms fire, control loops hold — even if the network or the central server goes down. Edge control means the building does not stop when the cloud does.
Where It Sits in the Architecture
A Niagara system is layered, and the JACE is the middle:
- Field devices — sensors, actuators, meters, and unit controllers, speaking BACnet, Modbus, and other protocols.
- The JACE — connects to those devices, normalizes their data, runs local control, and stores history. One JACE typically serves one building or one section of a large one.
- The Supervisor — the server tier that aggregates many JACEs into one view for an enterprise, campus, or portfolio, with central dashboards, reporting, and long-term data.
So a single building might have one JACE talking to a few dozen devices; a campus might have twenty JACEs rolled up under one Supervisor. The pattern scales by adding controllers at the edge and aggregating them above.
Why It Matters When You Are Planning a System
Two practical implications. First, JACE sizing and placement are real design decisions — how many devices each one carries, how the control logic is distributed, and whether a given model can run the Niagara version you need (a live concern for anyone still on older hardware facing an N4 upgrade). Second, because the JACE holds your control logic and integrations, how well it is configured and documented determines how maintainable the whole system is. A well-built JACE station is a pleasure to work on years later; a tangled one is a liability.
The Takeaway
A JACE is the edge controller that runs a Niagara station: it connects to your field devices, runs control locally so the building keeps working independent of the network, and feeds a Supervisor above it. Get the JACE layer right — sized, configured, and documented well — and everything built on top of it is easier.
SoftwarePile designs, builds, and maintains Niagara systems at every layer — JACE stations, Supervisors, and the integrations between them. Tell us about your building or portfolio and we will help you architect it properly.