A VAV Building Running 24/7: Overrides, No Static Reset, and a Failed Airflow Sensor
A 14-AHU, VAV office building has 25 hp supply fans, each drawing 18.5 kW at 60 Hz. Trend data for a mild October week shows every AHU running 24/7 against a 6 a.m.–6 p.m. weekday schedule, with duct static pressure held at the 1.5 in. w.c. design setpoint around the clock and nearly all VAV boxes at their 30% minimum from 8 p.m. to 5 a.m. Two boxes on AHU-7 report 0 cfm while their electric reheat stages cycle 100%/0% about every 4 minutes; the spaces they serve are comfortable. The after-hours override log shows 340 events in 30 days, 272 of them from one badge reader at the loading dock, each starting the full AHU group for the rest of the night. Energy is $0.09/kWh with a $12/kW-month demand charge.
1. Quantify the cost of running 24/7 instead of on schedule, and estimate how much of it is realistically recoverable. State your assumptions.
Read the worked answer
Fan power: 14 AHUs x 18.5 kW = 259 kW at 60 Hz. Excess hours: 168 h/wk actual vs 60 h/wk scheduled = 108 h/wk x 52 = 5,616 h/yr. Excess energy: 259 x 5,616 = 1,454,544 kWh/yr ≈ 1.45 GWh Cost: x $0.09 = $131,000/yr, plus 259 kW of demand at $12/kW-mo = $3,100/month.
Assumptions and the honest caveat: this is the upper bound - it assumes every AHU could stop. Some surely cannot (24/7 labs, server rooms, a night-operations floor, telecom closets). Those must be identified and scheduled onto their own program rather than lumped in.
Recoverable portion: with the building unoccupied and all boxes at 30% minimum, a static-pressure reset would let the fans fall to roughly 35–40% speed. Fan power follows the cube law: 0.375³ = 5.3% of full power, i.e. about 1 kW per AHU instead of 18.5 kW. Realistically, expect to recover 70–85% of the excess - on the order of 1.0–1.2 GWh/yr and $95,000–$115,000/yr, plus most of the demand. Even at 50% recovery this is the largest single item in the building.
2. Explain the AHU-7 symptom: 0 cfm reported with comfortable spaces and reheat cycling every 4 minutes. What is the failure mode, and how would you verify and correct it?
Read the worked answer
Failure mode: a failed airflow sensor driving the box into a limit cycle.
The sequence repeats every few minutes:
- The airflow station (hot-wire element fouled, pitot tubes plugged or disconnected, or the transducer drifted) reports 0 cfm.
- The box controller believes it is far below its 30% minimum, so it drives the damper fully open trying to make flow.
- The zone overcools.
- Reheat stages fire 100% to hold setpoint; the zone warms; the damper modulates back; airflow still reads 0; the loop restarts.
The space stays 'comfortable' precisely because the reheat is masking the failure - which is why nobody reported it. Meanwhile the box is cooling and heating the same air simultaneously, and the fully open damper on two boxes is helping hold the 1.5 in. w.c. setpoint high for the whole AHU.
Verify:
- Take a handheld balometer reading at the box inlet diffuser and at the box. If actual flow is ~30% minimum while the BAS reads 0, the sensor is at fault, not the damper.
- Compare damper command vs. feedback; check the tubing for kinks/disconnection and the transducer output at zero flow.
- Pull the 4-minute trend of damper position, airflow, zone temp, and reheat stage - the square-wave reheat pattern confirms the loop.
Correct:
- Clean/recalibrate or replace the airflow station; re-zero the transducer.
- Configure a sensor-fail fallback in the box program (fixed damper position or BMS-commanded flow) so a dead sensor parks the box instead of driving it wide open.
- Add an airflow-fault alarm (reported flow < 10% of minimum while the damper is > 80% open for 10 minutes).
- Add a reheat/cooling conflict alarm (reheat energized while the zone is below cooling setpoint by more than 2°F).
- Sweep the whole building for the same pattern - airflow sensors fail in batches when they come from the same install crew and vintage.
3. The override log shows 272 of 340 events from one loading-dock badge reader. What sequence and programming changes would you specify, and what would you trend to prove they worked?
Read the worked answer
Diagnosis: a single badge reader is starting the entire AHU group - all 14 air handlers, at full static pressure - for the rest of the night. That is almost certainly a janitorial or delivery badge used repeatedly, with no expiry and no zone-level granularity. It is the direct cause of the 24/7 operation quantified in Task 1.
Specify these changes:
- Scope the override to the zone served, not the AHU group. A loading-dock badge should condition the dock and adjacent corridor, not the 12th floor.
- Time-limit every override: 1 hour default, 2 hours maximum, renewable only by a second badge swipe inside the active window.
- Tie overrides to occupancy confirmation: require a badge or occupancy-sensor event in the requested zone before the override is honored, and auto-cancel if the zone goes vacant for 20 minutes.
- Replace fixed 6 a.m. start with optimal start (learn the warm-up rate, start just early enough to hit setpoint at occupancy) - this also removes the temptation to leave units on overnight 'so the building is ready.'
- Add static-pressure reset during occupied hours (reset from the most-open VAV damper), and a much lower unoccupied setpoint or fan-off at night.
- Exception reporting: an automated weekly report to the chief engineer listing every override by badge, zone, duration and outside normal hours. Visibility alone usually cuts this by half in a month.
Trend to prove it:
| Point | Frequency | Purpose |
|---|---|---|
| AHU supply-fan status and command (start/stop) | 15 min | Prove scheduled shutdown actually occurs |
| Override events with badge ID, zone, duration | Event log | Attribute and police the residual overrides |
| Fan VFD speed and kW per AHU | 15 min | Convert schedule compliance into kWh and $ |
| Duct static pressure and reset setpoint | 15 min | Prove the reset is active and tracking |
| Most-open VAV damper position per AHU | 15 min | Confirms the reset is not starving a box |
Measurement & verification tie-in: use these trends as the IPMVP Option B evidence - pre/post 15-minute interval kW on the fan VFDs, normalized by occupied hours and CDD, so the savings claim survives a mild winter and a tenant change.