Know the fix before the truck arrives.

Fault detection and diagnostics (FDD) is the practice of identifying equipment faults automatically from operating data and determining their cause, rather than waiting for a person to notice a symptom. FDD is the established industry and research vocabulary, used in ASHRAE and Berkeley Lab literature, for what Actuate delivers as predictive diagnostics. The distinction Actuate adds is timing and plain language: the fault is identified as drift begins, and the correction is explained before a technician is dispatched.

Commercial HVAC maintenance that waits for a breakdown is the expensive kind. Most emergency failures announce themselves first: a compressor short cycles, a runtime creeps up, an amp draw shifts. At high-frequency resolution those patterns are visible weeks before the failure; at a monthly inspection interval they are not. MaintenanceHub finds the drift, names the likely cause, and puts it on a planned work order instead of a 2 a.m. call. Comparable operators see 40 to 60% fewer emergency breakdowns and repairs completed 2x to 3x faster.

Commercial HVAC maintenance cost varies by site, equipment mix, and service history, so a single per-site figure is a guess. Actuate replaces the guess with a Maintenance Cost Baseline, a bottom-up estimate of a facility’s repair-and-maintenance spend, built equipment by equipment, every rooftop unit, compressor, walk-in, and motor, from real service data and industry benchmarks. Unlike a “1 to 3% of sales” rule of thumb, it produces a real number by system and per site, and it consistently shows HVAC and refrigeration at 50 to 65% of the R&M budget. Actuate runs it for every operator in its sales process, so an operator sees what commercial HVAC maintenance costs today, system by system, before deciding what to change. From there, MaintenanceHub works on that spend by finding performance drift as it begins, so work moves from emergency calls to planned service.

Far less often. The diagnosis travels with the work order: what changed, when it started, the likely cause, and the parts most probably needed. The technician arrives to perform a repair rather than to begin an investigation, which is what shortens repairs and reduces second visits for the same fault. After the work, equipment performance data confirms whether the fix held, so a failed repair surfaces immediately rather than as another call.

Three things separate systems that change outcomes from systems that add screens. First, data frequency: high-frequency data reveals short cycling and runtime creep that periodic readings miss. Second, whether the output is a diagnosis or an alert: whether it says what changed and why, or only that a limit was crossed. Third, whether the repair is validated afterward with data, because an unconfirmed fix is how one call becomes two. Kitchen equipment fails in patterns generic building rules do not model, so restaurant-specific behavior matters more than feature count.