Catching after-hours HVAC exceptions before parts got damaged

The pattern was always the same. On Saturday morning, a service advisor opened a bay door and found the cabin temperature in the parts area was wrong overnight. Sometimes it was a thermostat override left in place by a closing tech. Sometimes it was a real HVAC fault. Either way, by the time anyone noticed, sensitive parts had spent 14 hours outside spec — and the only signal was a complaint at 8 a.m.

No one was watching the building between 6 p.m. Friday and 7 a.m. Monday.

Pelican HVAC was already deployed at six of the seven rooftops. F2 Core treated Pelican as the signal layer for the Energy lane. Schedule windows, exception thresholds, and after-hours notification rules were configured per site.

When a thermostat event crossed a configured threshold outside open hours, F2 Core didn't just send an alert. It created a ticket on the operating record, routed it to the on-call service manager via SMS, and surfaced the runtime sparkline next to the ticket. If acknowledgement didn't happen inside the SLA window, the ticket escalated to the regional lead.

Three things changed operationally. Signal events follow the asset workflow rule meant every after-hours threshold breach became a real piece of work, not a notification someone could dismiss. One event creates one ticket meant the Saturday morning advisor walked into a record that already had context. Evidence is captured during workflow meant the post-event review had thermostat history, runtime, and corrective action all on the same record.

• After-hours HVAC exceptions detected before the next business day: ~0% → ~92%
• Avoided parts-area rework / re-shelf labor: ~$38K annualized
• Mean time to acknowledgement on overnight events: not tracked → 18 minutes (median)

“We didn't realize how much weekend damage was ‘just the cost of doing business.’ Once F2 surfaced the pattern, we couldn't unsee it.”