Refrigeration monitoring across every site, one platform

Critical refrigeration alarms are delivered to on-call phones within seconds of the threshold breach. The edge gateway evaluates thresholds locally at the store, so alarms fire even during a WAN outage, and the cloud fans the event out over SMS, push, and email in parallel rather than one channel at a time. Routing follows alarm groups, so the store manager gets the door-propped warning as a push notification while the walk-in-down critical pages the on-call tech by SMS, and escalation paths re-page when an alarm goes unacknowledged. Trend-based anomaly events fire earlier still, on the door cycling too often or the compressor slowly degrading, before the temperature ever crosses the threshold. Acknowledgement is one tap on the mobile app, with full user attribution and timestamp logged for the audit trail. There is no nightly summary email and no waiting for the next round.

Yes. Multi-site refrigeration is the core use case. Asset hierarchy lets you group every walk-in, prep-station, reach-in, and rack by region, district, site, and unit, and portfolio dashboards benchmark refrigeration uptime, energy per location, excursion rate, and truck-roll volume site against site, so the underperforming stores surface automatically instead of at the end-of-month review. A map view shows the whole portfolio colored by alarm state, with live weather overlays, which reads very differently when twelve stores go amber under the same heat wave versus one store going amber alone. Access is scoped by the same hierarchy: a store manager sees one location, a district manager sees their district, and corporate sees everything, all from the same underlying data. The same portfolio view drops to PDF on a schedule for the operations and ESG distribution lists, with any date range available on demand.

ControlCom Connect implements the controls a regulated pharmacy program expects: continuous temperature logging, tamper-evident audit trail, role-based access with enforced MFA, time-stamped electronic acknowledgement on every alarm, and AES-256 encryption at rest with TLS 1.3 in transit. Pre-built report templates cover CDC VFC, FDA, and 21 CFR Part 11 controls, so the downloadable temperature logs a state immunization program reviewer asks for are a date-range query, not a reconstruction from chart recorders. The record stays gap-free through network incidents because the edge gateway keeps logging locally during an outage and backfills with source timestamps preserved when the connection returns. Every alarm event carries its full history: which severity fired, who was notified on which channel, who acknowledged and when, and none of it can be edited after the fact. We hold a SOC 2 Type II report, available under NDA, and every account signs in with MFA or a magic link.

In almost every case, yes. ControlCom Connect is vendor-neutral by design and reads from any calibrated probe, datalogger, rack controller, or BMS point over Modbus TCP/RTU, BACnet IP/MSTP, OPC UA, MQTT, SNMP, 4-20mA, RTD, thermocouple, and dry contact. That covers the typical chain estate: rack controllers from one refrigeration vendor, walk-in dataloggers from another, door switches wired as dry contacts, and a BMS that predates all of them, often varying store by store because sites were built and remodeled in different years. All of it lands in one platform with one alarm engine, so the monitoring program stops depending on which vendor equipped which store. You keep the refrigeration investment you already made, and there is no per-tag licensing, so monitoring every case and every door instead of a critical shortlist is a coverage decision within the data volume and device allotment of your plan rather than a per-point license purchase. The OEM portals can stay or go; the data no longer lives only there.

They do, because acknowledgement is one tap and the alarm tells them what to bring. Native iOS and Android apps ship with push notifications, MFA, and a simple per-site view designed for non-technical staff, so a store manager can check the walk-in from the sales floor without training. Access follows the asset hierarchy: store managers see only their location, regional managers see their district, and corporate sees the portfolio, all from the same app. The alarm that reaches the on-call tech carries diagnostic context, the temperature trend, the door state, the compressor behavior, so they can tell a propped door from a failing compressor before leaving the depot, decide what parts to bring, or resolve it from the parking lot instead of after driving back to a workstation. That context is where the 30-50% reduction in truck rolls comes from: fewer dispatches, and the ones that happen arrive prepared.

A single-store or single-region pilot is typically live within two to three weeks. Week one is discovery: we inventory the probes, rack controllers, dataloggers, and protocols already in the stores, plus the alarm and escalation workflows your operations team actually wants, who gets paged for a walk-in-down at 2am, and who just needs the morning summary. Week two is the edge install and configuration: thresholds per asset, severity tiers, the store and district dashboards, and the report templates. From there the platform runs in parallel with whatever you have today, OEM portals, dataloggers, or manual rounds, so you evaluate refrigeration monitoring on real alarms and real product without any cutover risk. Most chains pilot on three to five stores in one region, check the alert quality and the truck-roll numbers against the old way, then expand to the rest of the fleet on their own schedule.