✦ Ensmart BMS Academy 📞 +91 99410 42612 Home
Products
All Products
⚙ Controller
DDC Controller IO Modules EnNode Gateway
🖥 Software
BMS I³IOT Energy Management Tenant Billing
✦ AI
AI Analytics AI BMS Library
Solutions
All Solutions Commercial BMS IT Parks & SEZs Pharma / 21 CFR Healthcare Industrial Retail & Malls Data Centres
Knowledge Hub
Case Studies Blog Press Release Downloads · Tools DDC Designer & BOQ Tool Design Engg Portal
Company
About Us ⬡ The 4 Pillars Our Team Approvals FAQ
Contact Get a Demo →
Home › Blog › DDC Controllers
Educational DDC Controllers

How DDC Controllers Control AHU, Chiller, and FCU Systems

August 27, 2026 · 15 min read · By EnSmart
DDC Controller · Operational Workflows

How DDC Controllers Control AHU, Chiller, and FCU Systems

Published by EnSmart  ·  Building Intelligence  ·  15 min read  ·  Updated: August 2026

Written by EnSmart BMS Engineering Team — experts in Building Automation, DDC Controllers, and Energy Management Systems

Direct answer: A DDC controller runs a continuous sense-compare-decide-act loop for each piece of equipment — reading sensors, checking interlocks, and driving actuators, valves, dampers, and VFDs to hold setpoint — with each equipment type (AHU, chiller, FCU) running its own specific sequence. A supervisory BMS layer then coordinates scheduling, alarms, and setpoints across all of them, without running the local control loops itself. This guide walks through each component and a full real sequence for all three equipment types.

3 sequencesAHU, chiller, and FCU — each genuinely different logic
Local firstEach controller keeps running even if the BMS front end drops
Interlocks firstSafety conditions checked before any control action executes
Supervisory ≠ localBMS coordinates; it doesn't replace each unit's own loop

Quick Answer: The Universal Building Block

Every DDC-controlled sequence — regardless of equipment type — follows the same basic loop: read sensors, check interlocks, compare against setpoint, and drive an output. What differs between an AHU, chiller, and FCU is which sensors, which interlocks, and which outputs are involved.

The Building Blocks Every Sequence Uses

Before the full sequences, here's what each component actually contributes to a control loop:

  • Sensors — measure temperature, pressure, humidity, CO2, or status, feeding real conditions into the controller's logic
  • Actuators — physically move dampers and valves to a commanded position based on the controller's output signal
  • Dampers — control airflow: outside air, return air, and exhaust dampers modulate together to manage fresh air intake and pressure
  • Valves — control water flow through cooling/heating coils, modulating to adjust the heat transfer rate
  • VFDs — vary fan or pump speed continuously, rather than running fixed-speed with mechanical throttling
  • Relays — switch simple on/off loads like a compressor stage or an auxiliary pump
  • Occupancy sensors — feed real-time presence data into scheduling and setback logic
  • Alarms — trigger when a reading or condition falls outside acceptable bounds, alerting operators to a fault
  • Scheduling — defines occupied/unoccupied periods that shift setpoints and equipment run status accordingly
  • Setpoint control — the target value (temperature, pressure) the loop continuously works to maintain
  • Interlocks — safety/sequencing conditions that must be satisfied before an action is allowed to proceed

Commissioning AHU, chiller, or FCU sequences and want them pre-loaded rather than programmed from scratch? EnSmart's SmartNova DDC ships with ECBC 2017 sequences built in.

See SmartNova DDC specs →

A Full AHU Control Sequence

  1. Schedule check — the controller checks whether the current time falls within occupied hours before starting the sequence
  2. Interlock check — confirms filter status, smoke detector status, and freeze stat are all normal before allowing startup
  3. Fan start — the supply fan VFD ramps to minimum speed via a relay/start command; a status input confirms the fan is actually running (fan-proving) before the next step proceeds
  4. Damper sequencing — outside air, return air, and exhaust dampers modulate to their minimum-position occupied setting
  5. Temperature control — a supply air temperature sensor feeds a PID loop that modulates the cooling or heating valve to hold setpoint
  6. Static pressure control — a duct static pressure sensor drives VFD speed to maintain design pressure as VAV boxes downstream open and close
  7. Continuous monitoring — the loop repeats every few seconds, with alarms triggered if any reading exceeds normal bounds (e.g. a filter pressure drop indicating a clogged filter)

A Full Chiller Plant Sequence

  1. Load calculation — the controller monitors chilled water supply/return temperature and flow to calculate current cooling load
  2. Lead chiller start — condenser water pump starts first, proven running via status interlock, before the chiller is allowed to start
  3. Chiller staging (lead-lag) — as load rises past a defined threshold (e.g. 80% of lead chiller capacity for a set duration), the controller stages on an additional chiller; as load drops, chillers are staged off in reverse order
  4. Condenser water reset — condenser water temperature setpoint is reset based on outdoor wet-bulb temperature and load, reducing compressor energy when full condenser capacity isn't needed
  5. Safety interlocks — low chilled water flow, high condenser pressure, or a compressor fault immediately blocks staging additional chillers on and can trigger a safe shutdown of the affected unit
  6. Alarm and trend logging — every stage change, setpoint reset, and fault is logged, giving operators a clear record of plant behavior over time

A Full FCU Control Sequence

  1. Occupancy check — a room occupancy sensor or schedule determines whether the zone is in occupied or setback mode
  2. Fan speed selection — the controller selects low/medium/high fan speed (or modulates via VFD on more advanced units) based on the deviation between room temperature and setpoint
  3. Valve modulation — a local room thermostat drives the cooling or heating valve to maintain the room setpoint, independent of the central AHU's own control loop
  4. Condensate interlock — a condensate overflow sensor can shut down the unit if drainage is blocked, preventing water damage
  5. Setback during unoccupied periods — setpoint widens and fan may cycle off entirely when the zone is unoccupied, resuming normal control ahead of scheduled occupancy

Note how much simpler and more localized this is compared to the AHU sequence — an FCU typically manages one small zone independently, while an AHU coordinates fresh air and central conditioning for many zones at once.

How Supervisory BMS Control Fits Above All Three

The supervisory BMS doesn't run any of the sequences above itself — each DDC controller runs its own loop locally, continuously, whether or not the BMS front end is even online:

Supervisory BMS Scheduling · alarms · setpoints · trends — coordination only AHU Controller Runs its own loop locally Chiller Controller Runs its own loop locally FCU Controller Runs its own loop locally If the BMS front end drops, every controller below keeps holding its own setpoint The BMS coordinates and reports — it isn't a dependency for basic control to continue
The supervisory BMS is a coordination and visibility layer, not the thing actually keeping the building comfortable minute to minute — that's the job of each DDC controller's local loop.

What Supervisory BMS Control Actually Adds

  • Building-wide scheduling — coordinating occupied/unoccupied schedules across every AHU, chiller, and FCU from one interface, rather than programming each independently
  • Aggregated alarms and trends — a single dashboard showing every fault and trend across all connected equipment
  • Cross-equipment strategies — building-wide demand limiting or load shedding, which requires visibility across multiple pieces of equipment a single DDC controller can't see on its own
  • Remote setpoint adjustment — operators can adjust setpoints centrally instead of visiting each panel individually

People Also Ask

  • What happens if a fan-proving interlock fails? The controller will not open the cooling/heating valve or continue the startup sequence, and typically raises an alarm, since running the coil without airflow risks equipment damage.
  • Can FCUs be integrated into the same BMS as AHUs and chillers? Yes — FCU controllers commonly communicate over the same BACnet network as AHU and chiller controllers, appearing in the same supervisory front end.
  • Why does chiller staging use a time delay, not just a threshold? A time delay (e.g. load above 80% for 15 minutes) prevents short-cycling chillers on and off from a brief, temporary load spike, which would waste energy and add mechanical wear.
  • Where can I see these sequences applied to a real building? See EnSmart's case studies for documented deployments across Indian facilities.

Frequently Asked Questions

What is an interlock in DDC controller logic?

An interlock is a safety or sequencing condition that must be true before a DDC controller allows an action to proceed — for example, confirming a supply fan is actually running before opening a cooling valve, or verifying a freeze stat hasn't tripped before allowing outside air dampers to open in cold weather.

What is a typical AHU control sequence?

A typical AHU sequence starts the supply fan on schedule, opens outside air dampers to a minimum position, modulates the cooling or heating valve based on supply air temperature against setpoint, and continuously checks safety interlocks like filter status and freeze protection throughout operation.

How does chiller sequencing work with multiple chillers?

Multi-chiller sequencing typically uses a lead-lag strategy, staging additional chillers on only when the lead chiller's load reaches a defined threshold, and staging them off in reverse order as load drops, to avoid running more chiller capacity than the actual cooling demand requires.

What is the difference between an AHU and an FCU control sequence?

An AHU sequence typically manages fresh air intake, filtration, and central cooling/heating for multiple zones or a large space, while an FCU (Fan Coil Unit) sequence is simpler and more localized, usually controlling a single room or small zone's fan speed and valve position based on a local thermostat.

How does supervisory BMS control coordinate individual DDC controllers?

The supervisory BMS layer doesn't run individual control loops itself — each DDC controller runs its own local sequence — but it coordinates scheduling across units, aggregates alarms and trend data, allows setpoint changes from a central interface, and can implement building-wide strategies like demand limiting that require visibility across multiple DDC controllers at once.

Does EnSmart's DDC controller ship with pre-built AHU, chiller, and FCU sequences?

Yes. EnSmart's SmartNova DDC controller ships with pre-loaded ECBC 2017 HVAC sequences for AHU, chiller plant, and FCU control, reducing the programming effort needed to commission standard equipment types.

Where to Go Deeper

One Loop, Applied Three Different Ways

AHU, chiller, and FCU control sequences all run the same fundamental sense-compare-decide-act loop — what changes is which sensors, interlocks, and outputs are involved, and how localized versus centralized the equipment is. A supervisory BMS ties all three together for visibility and coordination, but the actual comfort and safety of the building rests on each DDC controller running its own sequence reliably, locally, continuously — whether or not anyone is watching the dashboard.

Commissioning AHU, chiller, or FCU sequences on a project?

Send your equipment list — an EnSmart engineer will confirm pre-loaded sequence coverage within 24 hours.

See SmartNova DDC Controller → See Case Studies Get a Demo
← Back to all articles