Home/Resources/Building Automation & Controls/DDC controllers explained: field, unitary, and supervisory
Fundamentals · 8 min read

DDC controllers explained: field, unitary, and supervisory

DDC (direct digital control) controllers are the microprocessors that run a building’s control logic — reading sensors, executing the sequence of operations, and commanding valves, dampers, and equipment. A building automation system uses a hierarchy of them: small application-specific controllers at each piece of equipment, and supervisory controllers that coordinate the whole building and serve the dashboards.

Section 01

What a DDC controller is

A DDC controller is a small, purpose-built computer for building control. It has inputs (from sensors), outputs (to valves, dampers, and equipment), and a program — the sequence of operations — running on it. “Direct digital” distinguishes it from older pneumatic or analog electric control: the logic is in software, so it can be precise, adjustable, and networked.

Modern building automation is DDC end to end, which is what makes trending, alarming, and remote access possible.

Section 02

Application-specific and unitary controllers

At the equipment level are small controllers built for one job — a VAV box controller, a rooftop-unit controller, a fan-coil controller. Often called application-specific or unitary controllers, they come with the right inputs, outputs, and a pre-built or configurable program for that equipment type.

They keep the controlled equipment running even if the network or the front end goes down, because the logic lives locally on the controller, not in a central computer.

Section 03

Programmable and plant controllers

For central plants and custom equipment — chiller plants, air handlers, cooling towers — fully programmable controllers run sequences written specifically for that system. They handle more inputs and outputs and more complex logic than a unitary controller.

This is where staging logic, reset strategies, and optimization sequences live, coordinating multiple pieces of equipment toward an efficient whole-plant result.

Section 04

Supervisory controllers and the front end

Above the equipment controllers sits the supervisory layer — a controller or server that ties everything together, hosts the operator dashboards, stores trends, manages alarms, and connects the building to the network and the internet. On an open platform, this layer can normalize devices from many manufacturers onto one interface.

This is the layer where specialized supervisory programming sometimes calls for a certified integrator — work we coordinate within one accountable mechanical scope while we self-perform the HVAC controls. See BAS network architecture.

Section 05

Why the hierarchy matters

Distributing intelligence — local controllers doing local jobs, supervisors coordinating — makes a building resilient. If the network drops, equipment keeps running on its local controller. If one controller fails, the rest of the building is unaffected. And the system can grow controller by controller.

It also keeps the building serviceable: an open, well-documented controller hierarchy can be worked on by any qualified contractor, which is the heart of avoiding vendor lock-in.

Operator FAQ

Quick answers

What is a DDC controller?

A DDC (direct digital control) controller is a small, purpose-built computer that runs a building’s control logic — reading sensors, executing the sequence of operations, and commanding valves, dampers, and equipment. The logic lives in software, which enables precise control, trending, alarming, and remote access.

What is the difference between a unitary and a supervisory controller?

A unitary (application-specific) controller runs one piece of equipment — a VAV box, a rooftop unit — with local logic that keeps it running even if the network drops. A supervisory controller coordinates the whole building, hosts dashboards, stores trends, and manages alarms and network connectivity.

Does equipment keep running if the BAS network goes down?

Generally yes. Because application-specific controllers hold their logic locally, the equipment keeps operating on its own controller even if the network or front end is down. This distributed design is what makes a building automation system resilient.

Who programs supervisory controllers?

Equipment-level controls are self-performed within our Class A scope. Specialized supervisory programming and certified systems integration, where a project requires it, are coordinated with a certified integrator under one accountable mechanical scope — we do not claim integrator certification we do not hold.

Get help

Need open-protocol controls in Tampa Bay?

Suncoast Cold Systems installs, wires, and configures the HVAC controls integral to the mechanical systems we provide — and specifies open protocols (BACnet, Modbus, open supervisory platforms) so you own your building’s controls and data, with no proprietary dealer lock-in. Where a project calls for certified systems integration, we coordinate it within one accountable mechanical scope. Licensed Florida Class A Air Conditioning Contractor (FL #CAC1824642).

Building automation & controls Request a controls audit
More

Keep reading

Fundamentals8 min

Control points: inputs and outputs explained

What plugs into a controller.

Read the note
Networks9 min

BAS network architecture explained

How controllers connect into a system.

Read the note
Guide9 min

What is a building automation system?

The system these controllers build up to.

Read the note