Productization
HVAC

HVAC AHU Fan, Static & Filter Performance

Whether the supply (and return) fan and its variable-frequency drive deliver the airflow and static the floor needs at the fan speed and power they should — speed and power read against the air actually moved. A fan running fast and drawing power for little airflow signals a slipping belt, a fouled wheel, a failing bearing, or a VFD fault; a VFD in bypass or faulted removes the reset's ability to save energy. The health-and-efficiency signal for the AHU's largest moving part.

01 Metric Definition

What it measures and how it is calculated

What it measures

How efficiently and reliably the air handler's fan and its variable-frequency drive move air — the fan speed and electrical power read against the airflow and static the fan actually delivers, plus the VFD's own state (modulating, in bypass, or faulted). It is an equipment-health and efficiency signal for the AHU's largest moving part, distinct from duct static (the control target) — the fan is the machine that meets that target.

How it is calculated

The core read is power and speed against work done — the fan's kW and percent speed compared with the airflow and static it delivers, so a fan drawing more power or running faster to move the same air is flagged as degrading.

The VFD state is scored alongside: a drive in bypass or faulted is running the fan at full speed regardless of the static reset, which both wastes energy and removes the reset's control authority — a distinct finding from a mechanically degrading fan.

Degradation separates by signature: a gradual rise in power-for-airflow points to a fouling wheel or a slipping belt; a step change points to a belt failure or a VFD event; abnormal vibration or bearing signals (where instrumented) point to a bearing on its way out — read the pattern before scoping.

Reference thresholds

RangeClassificationInterpretation
Power and speed in line with airflow and static delivered; VFD modulatingExpected — healthy fanThe fan moves the floor's air at the expected power and the drive is following the reset — no action.
Rising power-for-airflow, or the VFD running near max to hold staticDegrading or capacity-limited — monitorThe fan works harder than expected for the air moved, or is near its ceiling; scope belt, wheel, or capacity before it fails or starves the floor.
VFD in bypass/faulted, or a step change in power-for-airflowFault — investigateThe drive has lost modulation or the fan has a mechanical fault; the reset cannot save energy and a failure may be imminent — scope the AHU.

Reference behavior only, not fixed absolutes — a fan's expected power-for-airflow depends on its size, its duct system, and its operating point. Calibrate against the fan's own commissioned curve before alerting, and confirm the airflow and power signals are valid so a sensor fault is not read as degradation.

Portfolio compliance target

There is no universal fan-efficiency number — the target is a fan whose power-for-airflow tracks its commissioned curve with the VFD modulating to the static reset. Calibrate the degradation threshold per fan against its own baseline; a VFD in bypass or faulted is a finding regardless of the efficiency figure.

02 Impact

How this metric moves the customer value drivers

The table below shows how moving AHU Fan, Static & Filter Performance impacts each customer value driver the product is designed to improve — the metric page explains the mechanism; the product pages express the magnitude.

Value driverImpact strengthHow AHU Fan, Static & Filter Performance moves this lever
Energy savingsDirect, primaryThe supply fan is one of the largest continuous electrical loads on an all-air floor, and its energy is only recoverable while the VFD modulates to the static reset — a drive in bypass or a fouling fan spends fan energy the reset should have saved. Catching degradation and bypass early protects the fan-energy savings the whole add-on depends on. Magnitude is expected (pending validation) — offices have no named Keedian reference deployment yet.
Asset lifespanDirectA slipping belt, a fouling wheel, or a failing bearing shows first as a rising power-for-airflow or a vibration signature — long before the fan fails. Flagging it turns an unplanned fan failure that shuts down a floor into a planned belt, wheel, or bearing service.
Avoided truck rollsIndirect, leading indicatorA VFD fault or a developing mechanical problem caught remotely is scoped into one planned visit with the right parts, rather than an emergency call after the floor loses air — and a bypass caught remotely is often a reset a technician can clear without a return trip.
03 Detection

How it surfaces and when it is reviewed

How it surfaces

Alarm
Fires on a VFD bypass/fault, or when power-for-airflow rises past a degradation threshold for a sustained period, so a failing fan or a lost drive is caught before the floor loses air.
Equipment
The finding is attributed to the specific AHU fan and drive, with the signature (gradual vs step, mechanical vs VFD) so the service is scoped correctly.
Site
Fan speed, power, and airflow/static shown together per AHU, with the VFD state, so efficiency and health are read at a glance.
Portfolio
Fans running degraded or in bypass surface in the Executive Summary, ranked so the biggest energy and reliability exposures are worked first.

Review cadence

Monthly
Reviewed in the MBR — power-for-airflow trend per fan and any VFD running in bypass, against the fan's commissioned curve.
Weekly
Operations reviews fans trending up in power-for-airflow and any new bypass/fault events for a scope.
Real-time
Bypass/fault and step-change alerts where configured, so a lost drive or a belt failure is caught immediately.
04 Alarms

Principal alarms derived from this metric

The table below summarizes the alarms that fire directly from AHU Fan, Static & Filter Performance. Each row links to the full operational detail (trigger, preconditions, action plan, human role, escalation, prevention) in the SOPs catalog.

AlarmDescriptionSeverityTierAI executes?Value driversSOP
AHU not holding static — floor losing air with the fan near max The air handler cannot hold the duct static its VAV boxes are calling for — the worst-case box stays pinned open, or several boxes saturate open at once, while the supply fan runs at or near maximum speed. The floor is running out of air even though no single box has failed: a static setpoint or reset capped below demand, a fan at its capacity ceiling, or a system restriction. High Essential Hybrid Customer experience · Energy savings Open SOP →
AHU fan drive in bypass or faulted — modulation and reset authority lost The supply-fan variable-frequency drive is running in bypass or has faulted — the fan runs at full speed regardless of what the static-pressure reset is asking for. Both an energy finding (the reset can no longer save fan energy) and a control-authority finding (the fan can no longer follow the floor's demand): a drive fault, a manual bypass left in place after service, or a tripped protection. Medium Essential Hybrid Energy savings · Asset lifespan · Avoided truck rolls Open SOP →
AHU filter loading high — pressure drop past the change threshold The pressure drop across the air handler's filter bank has risen past its change threshold — the filters are loaded and the fan is working harder to push the same air through them. Left alone it raises fan energy, erodes the fan's ability to hold static for the floor, and eventually lets the filter bypass; caught in time it is a planned filter change, not an emergency. Medium Essential Hybrid Energy savings · Asset lifespan Open SOP →
More alarms in development

More alarms in development (single-metric): a power-for-airflow degradation trend that separates fouling from belt slip, and a bearing/vibration early-warning where instrumented. Composite AHU alarms that weigh this metric's duct-static, filter and fan-health alarms together to attribute a high fan power to its cause will appear in a future release.

05 Actions

What to do based on the alarm

The action plan for each alarm lives on its own SOP page in the SOPs catalog — with the diagnostic steps, human role, value drivers, escalation, and prevention specific to that alarm. The list below maps each alarm to its SOP.

  • AHU not holding static — floor losing air with the fan near max → — The air handler cannot hold the duct static its VAV boxes are calling for — the worst-case box stays pinned open, or several boxes saturate open at once, while the supply fan runs at or near maximum speed. The floor is running out of air even though no single box has failed: a static setpoint or reset capped below demand, a fan at its capacity ceiling, or a system restriction.
  • AHU fan drive in bypass or faulted — modulation and reset authority lost → — The supply-fan variable-frequency drive is running in bypass or has faulted — the fan runs at full speed regardless of what the static-pressure reset is asking for. Both an energy finding (the reset can no longer save fan energy) and a control-authority finding (the fan can no longer follow the floor's demand): a drive fault, a manual bypass left in place after service, or a tripped protection.
  • AHU filter loading high — pressure drop past the change threshold → — The pressure drop across the air handler's filter bank has risen past its change threshold — the filters are loaded and the fan is working harder to push the same air through them. Left alone it raises fan energy, erodes the fan's ability to hold static for the floor, and eventually lets the filter bypass; caught in time it is a planned filter change, not an emergency.

Confirm the airflow and power signals before scoping degradation (metric-level)

Power-for-airflow degradation is only meaningful if the airflow and power signals are valid — a drifted airflow station or a mis-scaled power meter manufactures false degradation. Confirm the signals and compare against the fan's commissioned curve before scoping a mechanical fault, and treat a VFD bypass as a distinct, immediately actionable finding regardless of the efficiency figure.

Responsible
Keedian operations team
Urgency
High — a bad signal manufactures a false fan fault
Client approval
No

Tiered response — visibility, managed ops, then fan-speed control

At Essential the customer sees the fan's health and VFD state and acts themselves; at Managed, Keedian Ops runs the bypass/fault and degradation alarms, triages the signature, and dispatches; at Optimized, Keedian commands fan speed through the static-pressure reset (with an audit trail) and refers a mechanical fault — belt, wheel, bearing — or a failed VFD for a scoped field service.

Responsible
Keedian operations team (Managed/Optimized), customer team (Essential)
Urgency
Medium — a degrading or bypassed fan wastes energy and risks the floor
Client approval
No for surfacing and in-authority speed command — a mechanical or VFD repair is scoped separately
06 Escalation

When and how to escalate

Per-alarm escalation criteria live in the Escalation block of each SOP in the SOPs catalog. The patterns below are metric-level — read from the portfolio view, not from any single alarm firing.

Portfolio-level patterns — typically communicated in the MBR
  • Fans with a rising power-for-airflow across months — a belt, wheel, or bearing service candidate before failure
  • VFDs found running in bypass — energy recovery and control authority lost; a re-commissioning candidate
  • Fans running near max speed to hold static across peak periods — a capacity question
Cross-alarm urgency — typically requires out-of-cycle communication
  • A VFD faulted or a fan stopped on an occupied floor — the floor is losing air; direct action
  • A step change in power-for-airflow or a vibration spike — a belt or bearing failure in progress; scope before the fan fails
07 Prevention

Controls to avoid recurring issues

Configuration controls

  • Record each fan's commissioned power/airflow/speed curve as the baseline degradation is scored against
  • Confirm the airflow, static, and power signals and the VFD state points are valid at onboarding
  • Record the VFD's normal modulating range so a bypass or a max-speed condition is detectable

Monitoring controls

  • Alert on VFD bypass/fault immediately and on a sustained rise in power-for-airflow, with a step-change detector for belt failures
  • Trend power-for-airflow against the commissioned curve so a slow fouling or belt-slip is caught early
  • Watch bearing/vibration signals where instrumented for an early mechanical-failure signature

Reporting controls

  • Include per-fan power-for-airflow against its curve and any bypass events in the MBR
  • Flag VFDs in bypass explicitly — both an energy and a control-authority finding
  • Maintain a per-fan health log so a developing mechanical fault is visible across visits