15.3 Building Automation Controllers: Supervisory, Field, and Room Devices

15.3 Building Automation Controllers: Supervisory, Field, and Room Devices

The Building Automation sheet of the Competency and Task List devotes an entire competency block to controllers. It requires describing the function and application of a Java Application Control Engine (JACE) controller, a field controller, a room operator, and a PLC used in refrigeration applications; comparing programmable and configurable controllers; installing controllers per NEC requirements; wiring a power supply to a controller per NEC requirements; configuring a room operator/controller; and adding virtual points and network addresses to the network database.

Section 15.1 covered what a control loop does. Section 15.2 covered how devices talk. This section covers the devices themselves — what runs where, and what happens when the network goes down.

---

1. The Three-Tier Architecture

Almost every building automation system on the market resolves into three tiers, regardless of manufacturer branding.

           +---------------------------------------------+
           |   ENTERPRISE / SERVER (optional)            |
           |   Multi-building, historian, reporting      |
           +----------------------+----------------------+
                                  | IP (Ethernet, BACnet/IP)
           +----------------------+----------------------+
  TIER 1   |   SUPERVISORY CONTROLLER  (JACE, etc.)      |
           |   Graphics, schedules, trends, alarms,      |
           |   global logic, protocol translation        |
           +----------------------+----------------------+
                                  | Field bus (RS-485: BACnet MS/TP, Modbus RTU)
     +----------------+-----------+-----------+----------------+
  T2 | FIELD CTLR AHU | FIELD VAV | FIELD RTU | FIELD BOILER   |
     +--------+-------+-----+-----+-----+-----+--------+-------+
              | Sensor bus / dedicated pair
  TIER 3  +---+----------------+
          |  ROOM OPERATOR     |
          |  space sensor + UI |
          +--------------------+

Tier 1 — the supervisory controller

JACE stands for Java Application Control Engine. It is the supervisory controller in the Tridium Niagara Framework, and because Niagara is licensed by dozens of manufacturers under their own model names, "JACE" is used generically in the trade for any supervisory/network controller. Its jobs:

What a supervisory controller is not: it is not what keeps equipment running. This is the single most common misconception the exam tests. If the JACE is unplugged, a correctly commissioned building keeps heating and cooling — it just loses graphics, trends, alarms, global resets, and schedule changes.

Tier 2 — field controllers (unit controllers)

A field controller runs one piece of equipment: an air handler, a rooftop unit, a VAV box, a boiler plant, a cooling tower. It owns the physical I/O — the sensors and actuators are wired to its terminals — and it executes the sequence of operation.

Stand-alone operation is the defining characteristic. The program lives in the field controller's non-volatile memory. When the field bus is cut, the controller keeps executing its sequence with its own sensors and its last-known values for anything it used to receive over the network. A well-written sequence includes fail-soft defaults: if the outdoor-air temperature normally arrives over the network and communication is lost, the controller reverts to a fixed default rather than holding a stale value from last Tuesday or dropping to zero.

Tier 3 — the room operator

A room operator (also called a sensor-controller, network sensor, or wall module) combines the space sensor with a user interface. Depending on model it offers a temperature display, a setpoint adjustment within a limited range, an occupancy override button with a timed "after-hours" duration, a fan-speed selector, and a service port for a laptop.

It is usually not the controller. It is an input device that reports to a field controller. Some products blur this — a "smart" room operator with onboard logic exists — but on the exam, the distinction between a room operator and a field controller is the one being tested.

Configuring a room operator is a named task-list competency. The parameters that matter: the setpoint adjustment range (a ±3°F limited range prevents an occupant from commanding 60°F), the override duration, whether the display shows setpoint or space temperature, and the address if the operator sits on a sensor bus.

---

2. PLCs in Refrigeration

The task list specifically asks for "the function and of a PLC used in refrigeration applications." A Programmable Logic Controller comes from the industrial-automation world rather than the HVAC world, and it appears in supermarket refrigeration, industrial ammonia plants, and process cooling.

The practical reason a PLC appears on a refrigeration rack is that a parallel compressor rack is a sequencing and interlock problem — staging compressors on suction pressure, rotating lead compressor for even wear, coordinating defrost across many circuits, and enforcing safety interlocks — which is exactly what PLCs were built for. Ladder logic on a PLC reads like the relay ladder diagrams from Section 3.3, which is why the task list places relay logic and ladder logic side by side (Section 15.4).

---

3. Programmable Versus Configurable

This is an explicit task-list comparison, and it drives real purchasing and troubleshooting decisions.

The field consequence: when a configurable VAV controller will not do what the sequence of operation requires, no amount of parameter-setting will fix it. The correct answer is to change the controller, not to keep hunting for a setting. Conversely, when a programmable controller misbehaves, the fault is far more likely to be in the logic than in the hardware.

Programming workflow, and the rule that saves jobs. Connect a laptop to the field controller over USB, RS-485, or IP. Upload and archive the existing configuration before touching anything. Edit offline, download, then verify by watching live point values — not by assuming the download succeeded. An unsaved overwrite of a commissioned controller costs days of re-commissioning, and there is rarely another copy.

---

4. Controller Power and NEC-Compliant Installation

The task list ties both controller installation and controller power supply to NEC requirements.

Transformer sizing and loading. BAS controllers and actuators run on 24 VAC from a Class 2 transformer. Add the VA of the controller plus every actuator and device it powers, then add margin — an actuator's inrush VA is substantially higher than its holding VA, and a transformer sized on holding VA alone will brown out on a simultaneous start.

Half-wave versus full-wave rectification is the classic field failure. Many controllers rectify the 24 VAC input, and devices with half-wave rectifiers share a common reference. Powering half-wave devices from two different transformers, or getting the transformer's hot and common reversed at one device, creates a return path through the signal wiring. The result is erratic readings, hot commons, and destroyed inputs.

The rules that prevent it:

• Observe transformer polarity. Mark and keep hot and common consistent at every device on that transformer.
• Do not parallel transformer secondaries unless the manufacturer explicitly permits it and phasing is verified.
• Ground one side of the secondary where the manufacturer requires it, and only at one point.
• One transformer per controller group, sized with margin, is cheaper than diagnosing a phantom.

Enclosure and mounting practice:

• Mount controllers in an accessible enclosure — not above a hard ceiling with no access panel and not on top of an air handler where condensate drips on them.
• Respect the ambient temperature and humidity ratings; a controller in an unconditioned penthouse in a humid climate will fail.
• Keep Class 2 control wiring out of raceways and enclosures shared with line-voltage conductors unless a permanent barrier separates them (Article 725, and Section 2.4).
• Use plenum-rated cable (CMP) anywhere the cable runs through a duct, plenum, or a ceiling cavity used as a return-air plenum.
• Label every conductor at both ends. The next technician will not have your notes.

---

5. Points and the Network Database

The task list names "adding virtual points to network database" and "adding network addresses to network database" as distinct competencies.

A point is one piece of data. Three kinds:

Virtual points cost nothing in hardware and are how most useful logic gets built: a calculated wet-bulb, an economizer-enable flag, a computed reset setpoint, an equipment-runtime total that drives a maintenance alarm.

Addressing. Every device needs a unique identity, and on BACnet there are two distinct identifiers that candidates routinely confuse:

• The MAC address on an MS/TP segment (0–127 for master nodes) must be unique on that segment.
• The device instance number (0 to 4,194,302) must be unique across the entire internetwork.

A duplicate MAC address on a segment produces exactly the symptom pattern of a wiring fault — devices dropping in and out — so verify addressing before re-pulling cable.

Point naming discipline is what makes a system maintainable. AHU2_MAT tells the next technician what the point is; AI3 does not. Establish the convention before the first controller is commissioned, and document it alongside the address schema (Section 15.7).