Cold rooms, chillers and freezers keep high-value dairy and food products safe, but issues are often noticed late. This use case shows how Spectra, Servy, OpsForms and OpsBot monitor assets in real time and trigger the right service workflows automatically.
| Solution | Role in this use case |
|---|---|
| Spectra | Connects to cold rooms & chillers; reads temperature, door, power in real time; applies rules to detect anomalies. |
| Servy | Turns alerts into tickets with SLA, warranty and vendor context; manages technicians, visits, parts & escalations. |
| OpsForms | Checklists for on-site checks, repairs, preventive maintenance and audits; captures readings, photos and notes. |
| OpsBot | Guides teams on likely causes, SOPs and recommended actions; can create Servy tickets or open forms. |
Cold rooms, chillers and controllers connected to Spectra — continuously reading temperature, door status, power, compressor cycles and other key signals.
You define rules in Spectra for acceptable ranges, door open times, power outages and sensor failures. Spectra filters noise and raises only meaningful alerts.
Critical alerts automatically create Servy tickets with asset, site, SLA, warranty and vendor details — assigned with priority and category.
Technician assigned via Servy rules; receives job on mobile with OpsForms checklist (diagnosis, repair, verification) and captures all data.
OpsBot helps teams with probable causes, SOPs and communication guidance — can open checklists or create tickets when needed.
Managers see live dashboards of cold rooms, alarms, open tickets, response times and energy/maintenance patterns.
| ❌ Today | ✅ With Starlly |
|---|---|
| Temperature issues found during manual checks or complaints — often after product loss. | Issues detected in real time; critical deviations instantly create Servy tickets and notify the right team. |
| Service teams juggle calls, chats and spreadsheets; ownership and response times unclear. | Every event becomes a Servy ticket with clear owner, SLA, status and escalation path. |
| Field visits poorly documented; no consistent checklists for analysis or audits. | OpsForms standardizes technician checklists, capturing readings, photos and notes tied to each ticket. |
| Root causes trapped in senior staff memory; new team members struggle. | OpsBot makes manuals, SOPs and past cases accessible to everyone. |
Catch temperature, door and power problems earlier before product loss occurs.
Automated ticket creation and escalation reduces incident response times significantly.
Analyze cycles, faults and patterns across sites to optimize energy and maintenance spend.
Structured logs and checklists for visits, repairs and inspections always ready for audits.
Guided checklists, full asset history and OpsBot suggestions make every technician more effective.
Clear view into uptime, alarm volume, service performance and vendor contributions.
| Step in the flow | What happens | Solution(s) |
|---|---|---|
| 1. Condition / event | Temperature drifts out of range, door open too long, or power unstable. | Spectra |
| 2. Classify & decide | Rules decide if informational, warning or critical; repeated deviations can be grouped. | Spectra |
| 3. Create work | Critical events auto-create Servy ticket with asset, site, SLA, warranty and vendor info. | Spectra Servy |
| 4. Guide teams | OpsBot suggests likely cause, pulls SOPs, advises checklist and customer communication. | OpsBot |
| 5. Execute work | Technician receives job in Servy, executes on-site using OpsForms checklist, records all data. | Servy OpsForms |
| 6. Vendor & parts | Servy handles vendor allocation and escalation; procurement API triggers early part orders. | Servy Hubsource |
| 7. Learn & improve | Data feeds dashboards; OpsBot gets smarter from resolved cases and feedback. | Spectra Servy OpsBot |