Study guide

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

HVAC Excellence Certification Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction, Safety, Tools, and Diagnostic Method

1.1 HVAC Excellence Certification, Industry Codes, and Standards 1.2 Electrical Safety, PPE, Lockout/Tagout, and Hazard Communication 1.3 Multimeters, Manifold Gauges, Micron Gauges, and Diagnostic Instruments 1.4 HVACR Mathematics, Unit Conversions, and Efficiency Ratings 1.5 OSHA Standards, Fall Protection, Rigging, and Confined Spaces 1.6 HVACR Industry Organizations, Energy Resources, and Building Energy Programs 1.7 Systematic Troubleshooting: Data Plates, Manufacturer Literature, and Diagnostic Method

2 Chapter 2: Electrical Fundamentals and Circuit Theory

2.1 Voltage, Current, Resistance, and Ohm's Law Calculations 2.2 Series, Parallel, and Series-Parallel Circuits and Power Calculations 2.3 AC Fundamentals, Single-Phase vs Three-Phase Power, and Control Transformers 2.4 Conductors, Insulators, Wire Sizing, Voltage Drop, and NEC Ampacity

3 Chapter 3: Electrical Components, Motors, and Schematics

3.1 Contactors, Relays, Switches, Overload Protection, and Thermostats 3.2 HVAC Motors (PSC, CSIR, CSCR, ECM, 3-Phase) and Run/Start Capacitors 3.3 Interpreting Ladder Diagrams, Schematics, and Point-to-Point Wiring 3.4 Motor Testing, Insulation Resistance, Bearings, and Belt Drives

4 Chapter 4: Thermodynamics and the Refrigeration Cycle

4.1 Heat Transfer, Temperature Scales, BTUs, Sensible vs Latent Heat, and Enthalpy 4.2 The Four Vapor-Compression Cycle Stages (Compression, Condensation, Expansion, Evaporation) 4.3 P-T Charts, Saturated Conditions, Target Superheat, and Subcooling Calculations 4.4 Pressure–Enthalpy Diagrams, Compression Ratio, and Cycle Analysis

5 Chapter 5: Refrigerants, Environmental Regulations, and Recovery

5.1 Refrigerant Types (CFC, HCFC, HFC, HFO, HC) and ASHRAE Safety Groups (A1, A2L, A3) 5.2 EPA Section 608 Regulations, Venting Prohibitions, and Evacuation Standards 5.3 Recovery/Recycling/Reclaiming Equipment, Procedures, and Leak Detection 5.4 Refrigerant Retrofits, Cylinder Handling, and Refrigerant Purity 5.5 A2L and Low-GWP Refrigerants: Codes, Charge Limits, and Service Practice

6 Chapter 6: Refrigeration System Components and Accessories

6.1 Compressor Mechanics (Reciprocating, Scroll, Rotary, Screw) and Failures 6.2 Expansion Devices (TXV/TEV, Fixed Orifice, EEV) and Superheat Control 6.3 Condensers, Evaporators, Filter-Driers, Accumulators, Receivers, and Solenoids 6.4 Pressure Controls, Capacity Controls, and System Protection 6.5 Refrigerant Line Sizing, Pressure Drop, Brazing, and Piping Practice

7 Chapter 7: Gas Heating, Combustion Analysis, and Fuel Piping

7.1 Combustion Theory, Fuel Gases (Natural Gas vs LP), and Gas Burners 7.2 Gas Valves, Ignition Systems (Standing Pilot, Spark, HSI), and Safety Limit Controls 7.3 Flue Venting, Draft Principles, Combustion Analysis, and CO Safety 7.4 Fuel-Gas and Oil Piping, Vent System Selection and Sizing, and Installation Practice

8 Chapter 8: Electric Heating, Oil Heat, and Hydronics

8.1 Electric Heating Elements, Sequencers, Limit Switches, and kW Calculations 8.2 Oil Burners, Fuel Pumps, Nozzles, Ignition Electrodes, and Primary Controls 8.3 Hydronic Boilers, Circulator Pumps, Expansion Tanks, and Zone Controls 8.4 Combustion Air, Water Heaters, and Combustion Appliance Zone Testing

9 Chapter 9: Heat Pumps and Dual-Fuel Systems

9.1 Heat Pump Operation in Heating/Cooling Modes and Reversing Valve Operation 9.2 Defrost Controls (Time-Temperature, Demand Defrost), Sensors, and Sequences 9.3 Balance Points, Auxiliary/Emergency Heat, and Dual-Fuel (Hybrid) Systems 9.4 Heat Pump Diagnostics, Refrigerant Flow, and Troubleshooting Procedures 9.5 Heat Pump Types, Cold-Climate Performance, and Sizing Approaches

10 Chapter 10: Air Distribution, IAQ, and System Commissioning

10.1 Airflow Fundamentals, CFM Measurement, External Static Pressure, and Fan Laws 10.2 Duct Sizing Principles, Supply/Return Distribution, Dampers, and Air Balancing 10.3 Indoor Air Quality, MERV Ratings, Electronic Cleaners, Humidification, and Dehumidification 10.4 Deep Vacuum Evacuation (Micron Gauge), Subcooling/Superheat Charging, and System Commissioning 10.5 Duct Leakage, Blower Door Testing, and Building Envelope Performance

11 Chapter 11: Psychrometrics, Airside Calculations, and Load Estimation

11.1 Reading the Psychrometric Chart: Properties and Plotting 11.2 The Eight Air-Conditioning Processes and the Process Triangle 11.3 Mixed Air, Ventilation, and Infiltration Calculations 11.4 Residential Heat Loss, Heat Gain, and Equipment Sizing

12 Chapter 12: Light Commercial Air Conditioning

12.1 Packaged Rooftop and Split Light-Commercial Systems 12.2 Water-Cooled Condensers, Cooling Towers, and Chilled-Water Systems 12.3 Economizers, Demand-Controlled Ventilation, and VAV Air Distribution 12.4 Light-Commercial Start-Up, Commissioning, and Troubleshooting

13 Chapter 13: Light Commercial Refrigeration

13.1 Temperature Ranges, Box Loads, and Refrigeration System Types 13.2 Evaporators, Defrost Methods, and Defrost Controls 13.3 Condensing Units, Parallel Racks, Oil Management, and Capacity Control 13.4 Refrigeration Control Valves and Automatic Pump-Down 13.5 Commercial Refrigeration Diagnostics and Ice Machines

14 Chapter 14: Ductless, Mini-Split, and VRF Systems

14.1 Mini-Split Architecture and Inverter-Driven Compressors 14.2 Multi-Zone and VRF Operation, Electronic Expansion Valves, and Controls 14.3 Ductless Installation, Evacuation, Charging, and Diagnostics

15 Chapter 15: Building Automation and Digital Controls

15.1 DDC Fundamentals, Control Loops, and Sequences of Operation 15.2 BAS Networks, Protocols, and NEC-Compliant Cabling 15.3 Building Automation Controllers: Supervisory, Field, and Room Devices 15.4 Digital Logic, Numbering Systems, and Controller Programming 15.5 Sensor Selection, Installation, and Input Point Configuration 15.6 Actuators, Output Devices, and VFD Integration 15.7 Commercial Prints, Equipment Schedules, and BAS Documentation

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

Key Takeaways Explain This Topic AI

A JACE or equivalent supervisory controller bridges RS-485 field buses to the IP network and hosts graphics, schedules, trends, alarms, and global logic; it is not the device that keeps an air handler running.

Programmable controllers accept custom logic written by the technician, while configurable (application-specific) controllers ship with fixed logic and only expose parameters.

Field controllers hold their program in non-volatile memory and continue running their sequence stand-alone when the supervisory controller or network is lost.

A virtual point is a calculated software value with no field wiring, and adding virtual points and network addresses to the database is a named Competency and Task List task.

Always upload and archive a commissioned controller's existing program before downloading any change.

Last updated: August 2026

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:

Function What it means in the field

Protocol translation Presents a BACnet MS/TP chiller, a Modbus RTU power meter, and a LonWorks lighting panel to one browser interface

Web server Serves the graphics and the operator workstation; there is no separate PC required for day-to-day operation

  • Scheduling and calendars Holds occupancy schedules and pushes them to field controllers
  • Trending / historian Samples and stores point histories that field controllers have no memory to keep
  • Alarming and notification Evaluates alarm conditions and routes email or SMS

Global logic Cross-equipment logic: outdoor-air-temperature reset broadcast to every AHU, demand limiting across the building

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.

  • BAS field controller PLC
  • Origin Building HVAC Industrial process and machine control

Programming Block, icon, or line programming; often application-specific Ladder logic (IEC 61131-3), plus structured text and function block

  • Scan Typically 1 s or slower — adequate for thermal processes Millisecond scan; deterministic
  • I/O Analog and binary sized for HVAC High channel counts, rugged, hot-swappable modules

Typical use AHU, VAV, RTU, boiler Supermarket rack control, ammonia machinery room, ice plant, interlock and safety chains

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.

  • Programmable Configurable (application-specific)
  • Logic Written by the technician or integrator Fixed by the manufacturer
  • Technician's job Author the sequence Select an application number and set parameters
  • Flexibility Anything the hardware supports Only what the manufacturer anticipated

Deployment speed Slow; requires programming competence Fast; a VAV box controller can be commissioned in minutes

  • Error exposure High — a logic bug is yours Low — the logic is factory-tested
  • Cost Higher Lower

Typical application Central plants, custom AHUs, unusual sequences VAV boxes, fan-coil units, unit ventilators, heat pumps

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:

Kind Definition Example

Physical (hardware) point Terminates on a controller terminal and connects to a real device Mixed-air temperature sensor on AI-3

Virtual (software) point A calculated or stored value with no field wiring Average of four zone temperatures; a computed setpoint; a runtime accumulator; an occupancy state

Network point A value imported from another controller across the bus Outdoor-air temperature broadcast from the AHU controller to twenty VAV controllers

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).