Products

Detect

Fault detection that runs on site, around the clock. Every unit is checked continuously against what it should be doing, and each fault is named with its likely cause.

Inside a unit

Every check, with its reasoning.

Open any unit to see each diagnostic, its status and what it found. Discharge air off setpoint is told apart: out of capacity with the valve wide open, out of control with room to spare, or the other coil fighting it.

A sensor that is offline or reads an impossible value is named and set aside, so one bad reading never turns into a false fault. A check that needs a sensor the unit does not have says so, and can be hidden.

Detect · AHU-38 · Fault Detection & DiagnosticsExample
Hide unavailable (2)
DiagnosticStatusDetails
Discharge airWarning8 °F above setpoint for 1 d 6 h. Cooling valve fully open: out of capacity, not out of control.
Duct staticWarning0.31 in. wc below setpoint. Fan near full speed: no headroom left.
Mixed airUnreliableSensor reads 212 °F, outside its physical range. Named, and left out of every check that uses it.
FilterInfoPressure drop 1.1 in. wc: schedule a change.
EconomizerInfoUnavailable: needs an outside air temperature, which this unit does not have.
Supply fanOKProven, near full speed.
CoilsOKNo heating and cooling at the same time.
CO2OKReturn air 640 ppm.
SafetiesOKFreeze stat, smoke detector and high-static switch normal.

What it checks

Checked the way an engineer walks the unit.

Detect works from the points your building automation system already has: commands, status, setpoints, temperatures, pressures and valve positions. Each kind of equipment has its own set of checks, and each check names the likely cause instead of just raising a flag. Some of what it looks for:

Air handlers

  • Fans commanded on but not proven, or left running in hand when commanded off
  • Duct static off setpoint, and whether the fan has capacity left
  • Discharge air off setpoint or hunting around it, with the likely cause: out of capacity, out of control, or the other coil fighting it
  • Heating and cooling at the same time, and valves open on a stopped unit
  • Economizers taking warm air or missing free cooling, and damper linkage faults worked out from the temperatures
  • Return fans and building pressure
  • Running while the building is unoccupied, or off while it is occupied
  • Filters, CO2, safety trips and short cycling

Terminal units

  • Zones outside their comfort band, and for how long
  • Dampers wide open but short of airflow
  • Dampers hunting back and forth
  • Reheat open with no temperature rise
  • Discharge air far from the air handler’s supply without reheat
  • Box fans, duct static at the box and CO2

Chillers

  • Compressor current, bearing and motor winding temperatures
  • Evaporator and condenser approach
  • Oil pressure and temperature
  • Leaving water above setpoint
  • Lost flow while running, chiller alarms and short cycling
  • Enabled but sitting idle
  • Voltage and power factor

Checks for other kinds of equipment are built the same way and added as a building needs them.

Score and history

A running score, and the slide behind it.

Every unit carries a score from 0 to 100 that its own checks set. A critical finding takes more off than a warning, a check waiting on a sensor barely counts, and how much each check matters can be tuned.

The score is recorded every hour beside the readings the checks use, so the history shows when a unit started to slide, what its fan and valves were doing at the time, and whether a repair brought it back.

Detect · AHU-38 · HistoryExample
Business hoursDual axis
  • Discharge air (°F)
  • Setpoint (°F)
  • Equipment score
506070050100MonTueWedThuFriSatSun

Tuned per unit

Fitted to the building, not a textbook.

  • Every limit can be set unit by unit: how far from setpoint, for how long, and at what level.
  • Each condition keeps the time it started, through a restart, and one bad reading never resets the clock.
  • Every unit keeps a record of how long it spent in each state.
Detect · AHU-38 · PropertiesExample
SettingValueEdit
Fan proof delay60 sEdit
Discharge air warning band±7 °FTuned. Default ±5 °FEdit
Discharge air warning after15 minEdit
Discharge air critical band±10 °FEdit
Duct static warning band0.25 in. wcEdit
Duct static warning after20 minTuned. Default 10 minEdit
Filter change at1.0 in. wcEdit
Return CO2 warning1,000 ppmEdit

In your building system

Where your operators already look.

Each unit’s status is published on your network as a BACnet point: OK, warning or critical. The building automation system your team already uses can put it on its graphics and alarm on it, so a fault Detect finds reaches the operator’s screen with nothing new to log into.

Building automation system · PointsExample
PointValueUpdated
AHU-12 Detect statusCRITICAL2 s ago
AHU-38 Detect statusWARNING2 s ago
AHU-07 Detect statusOK3 s ago
VAV-2-14 Detect statusWARNING2 s ago
Chiller 1 Detect statusOK4 s ago

The operators’ own graphics and alarms read these points. Nothing new to log into.

Where findings go

To the people and systems that act on them.

  • On screen. Every unit’s diagnostics, live, on the server in your building.
  • In your building system. A status point per unit, for its graphics and alarms.
  • By email, Slack, Teams or PagerDuty. Alarms you set on any point, for a value out of range or a status that changes, go to the people who need them. Rules filter by severity, equipment and location, and batch messages so nobody is flooded.
  • Into Insight. With Insight, the findings feed the morning briefing and the equipment reports, ranked and explained.

Runs on site

Beside the system you already have.

Detect runs on a small server in your building, next to your building automation system, and reads it over BACnet. Detection keeps running if the internet connection drops. Nothing is ripped out or replaced.

Detect and Insight

Detect finds it. Insight explains it.

Detect finds and names faults on site, around the clock. Insight ranks them across the building, explains them in plain language, and writes the morning briefing and the reports your team and owners read.

Explore Insight

What would Smart Tenants find in your building?

Tell us about your building systems and we will show you what a morning briefing would say.