Run the day · The record everything hangs off
Every rooftop unit, boiler, and walk-in condenser gets one serialized record — age, warranty, refrigerant, and every visit ever done to it — instead of a calendar reminder or a line buried on a customer account.
What it is
A piece of installed equipmentin Thermal is a serialized record — a rooftop unit, a boiler, a walk-in condenser — that carries its own nameplate data, warranty status, and full service history. It sits between the service site and the service agreement in Thermal's core schema: customer → service site → equipment → agreement → work order → invoice.
Tracking jobs tells you what happened. Tracking equipment tells you what to do next — which unit is aging out, which one has called back twice this quarter, and which one is still under warranty. That timeline is what turns mean time to failure and mean time to repair from a guess into a number you can plan a replacement around.
Everything hangs off the unit on purpose. A dispatch call, a coverage decision, a PM visit and an invoice all point back at the same serialized record, so a callback connects to a cause instead of starting over.
One account. Every site under it.
The address, and the branch that covers it.
Make, model, serial, and everything ever done to it.
You are hereCoverage, price, escalation, visit frequency.
Raised against the unit, worked in the field.
Built from the work, minus what's covered.
Because the unit is the anchor, coverage from a service agreement attaches to the equipment itself — so the answer to "is this compressor covered" is on the work order before the tech leaves. PM visits generate against the unit's own schedule, and its history stays in one place forever.
| Unit | Site · Branch | Model / Serial | Installed | Warranty | Last visit | Next PM |
|---|---|---|---|---|---|---|
| EQ‑1142 | Northgate MedicalRoof B · Ottawa | York YDAL · 88A10457 | 2019 | Expires 60 days | 2026‑07‑12 | 2026‑09‑18 |
| EQ‑1188 | Riverside FoodsWalk-in A · Winnipeg | Bohn · RB34-7712 | 2021 | Active | 2026‑08‑02 | 2026‑08‑30 |
| EQ‑1201 | Cedar Park LogisticsDC 3 · Mississauga | Trane RAUC · XG2210-884 | 2015 | Expired | 2026‑08‑11 | 2026‑09‑02 |
| EQ‑1215 | Harbour Point TowerPenthouse · Halifax | Carrier 19XR · C190-3321 | 2018 | Active | 2026‑07‑28 | 2026‑10‑05 |
| EQ‑1222 | Westfield Distribution4 sites · Prairie | Lennox LGA · 65V220-91 | 2023 | Active | 2026‑06‑30 | 2026‑09‑11 |
The equipment record is the thing every other part of the platform reads from — here's what's on it.
Model, serial number, install date, refrigerant type, and run hours live on the unit itself — not scattered across old work orders a technician has to dig through before a visit, and not a spreadsheet that lives on one computer and goes stale the moment anyone's out of the office.
A technician photographs a nameplate on site and the unit's model and serial data populate the record — no re-typing a data plate by hand back at the office at the end of the day, and no transcription typos to chase on a service call.
Every visit, part, and finding tied to a unit builds one continuous timeline — so the technician standing in front of it sees exactly what failed last time before they climb onto the roof, and the office sees the whole picture without opening five job folders. The history is attached to the machine, not to a person's memory.
Warranty coverage and claim status live on the unit, checked against the install date and manufacturer terms — so a claim doesn't get missed and a customer doesn't get billed for covered work. What's covered and what isn't is on the record, not in a drawer.
When a unit is under a service agreement, that coverage attaches directly to the equipment record — so billing and SLA response times follow the unit, not a guess about what the contract includes.
A dispatched job references the specific equipment it's for, not just a customer address — so the technician arrives already knowing which rooftop unit, which floor, and which past visits are relevant. See how jobs surface on the dispatch board.
Preventive-maintenance work generates against the equipment's own schedule under its agreement, not a generic customer-level reminder — the visit is for this unit, on this route, on this date. The full scheduling rules live on the preventive maintenance page.
Three things the unit record deliberately doesn't promise, so you don't build a plan on them.
Thermal stores the nameplate data you capture — it doesn't carry an external parts-and-specs catalogue for every model. A native equipment-data lookup is on the roadmap; today the record holds what you record on it.
Nameplate capture reads the plate into the record you open it in. Auto-matching a photo to an existing unit in the fleet is not built — matching stays a person's call, so a serial never gets attached to the wrong machine.
Equipment in Thermal is the asset record — there isn't a parallel register to keep in sync. The same unit powers rentals, serialized parts and service, so what you maintain is what you bill from.
If a capability isn't on this page, assume it isn't built. We'd rather lose a deal on a missing feature than win one on a sentence that turns out to be aspirational.
The unit record is the hub — these are the surfaces it feeds, in the order the work flows.
The ones that come up when a shop realizes equipment is the record to run from.
Because the unit, not the customer, is what actually breaks, ages, and needs coverage — a customer can own many units across many sites, each with its own warranty status and service history that would get lost on a single flat customer record. Equipment is the spine for exactly this reason.
A technician photographs the equipment's data plate in the field and the model and serial information populate the unit's record — instead of hand-typing it from a photo back at the office at the end of the day. The plate is the source, and the record matches it.
Yes — warranty status and claim tracking live on the unit itself, checked against the install date and manufacturer terms, so a covered repair doesn't accidentally get billed to the customer. The answer is on the unit before the invoice is built.
Coverage attaches directly to the unit, not just the customer account — so a work order on a covered rooftop unit is billed differently than one on equipment the agreement doesn't include, even at the same site.
Yes — every visit, part used, and finding on a unit builds one continuous timeline, visible to the office and to the technician on the field app before they even leave for the call. Nobody has to ask anyone what happened last time.
Yes — the rental fleet is the same equipment record the rest of Thermal tracks. A unit generates its own work order when it deploys, returns, or swaps mid-rental, and its service history stays on the unit either way.
Bring the unit that keeps calling back and we'll show you its whole record — every visit, every part, and the coverage decision made before the next tech rolls.