BMS Agent
Inspectr continuously reads BMS trends, alarms, and work order history — clearing false positives, verifying real faults, and catching developing issues before an alarm fires. What matters becomes an action, ready to review or dispatch.
Every alarm and open issue is checked against point history, schedules, related signals, and prior work. False positives are cleared with the reasoning logged, leaving the team with what actually needs attention.
Real faults are checked against runtime, meter data, and operating conditions, then quantified. What's wrong, why Inspectr believes it, and what it's costing are attached to the finding.
Inspectr watches for changes that haven't crossed an alarm threshold yet — fan speed creep, control drift, abnormal cycling, degrading performance. Developing faults are caught early and turned into a remote fix or dispatch-ready work order.
Before — what the BMS showed
No alarm has fired. Every point is within limits. Supply fan speed has crept from 62% → 68% over six weeks to maintain the same duct static.
After — Inspectr prediction
Trend flagged — +6% fan speed for the same static pressure, invisible to existing alarm thresholds.
Source: BMS point history, six-week trend
Pattern matched — The same creep preceded belt failure in prior work order history.
Source: work order history + pattern memory
Likely cause ranked — Belt wear or filter loading identified as the likely cause, weeks before failure.
Source: asset record + O&M specs
Action drafted — Work order ready before the equipment breaks — operator approves, CMMS dispatches.
No alarm. No ticket. Caught in the trend.
Replaces
Alarm floods nobody has time to triage, engineers manually piecing together trends, predictive scores that stop at a dashboard, and failures that only become obvious when equipment stops.
Who it's for
Every cleared alarm, confirmed fault, and resolved issue sharpens what Inspectr catches next — earlier, with better evidence behind it.