ReferenceCustomers & equipment

Unit identity

What it's for

Unit identity is the compliance-and-nameplate view of one piece of equipment, opened in the customer's own context. It carries the things a service record does not: refrigerant transactions, warranty claims, meter readings, EPA appliance class, and the QR label you stick on the unit.

Reach it from a customer's Equipment tab. The route is /customers/<customer>/equipment/<unit>. The org-wide view of the same unit is the equipment record.

Tabs

  • Service History — visits against this unit, with Date, Type, Summary, and Tech.
  • Warranty — claims raised, with Description and Resolution.
  • Refrigerant Ledger — every charge and recovery, with Refrigerant, Quantity, Leak Test, Cylinder Serial, Tech Cert, and Notes.
  • Meter — readings logged, with Value, Unit, and the date read.

Panels and controls

Unit Identity

Type, Make, Model, Serial, Install Year, Refrigerant, Tonnage, and Nameplate Charge — the plate, transcribed.

Asset QR Label

Prints a label carrying a QR code that resolves to the unit's public asset card. Stick it on the unit and anyone standing in front of it can scan straight to its record. A whole site can be printed at once from the site's label sheet.

Set Nameplate Charge

The factory refrigerant charge in ounces — "oz (e.g. 56)". Every leak-rate calculation is a percentage of this number, so an empty nameplate charge means compliance maths cannot be done for the unit.

EPA Appliance Class and Compliance Status

The class decides which obligations apply, and Compliance Status shows where the unit stands, with the Citation behind it and the Threshold it is measured against.

Sub-location Zone

Which roof, which mechanical room. It is the difference between "RTU-7" and "RTU-7, north roof, past the stair tower".

Runtime Meter

Current value, PM threshold, Last read, and whether Usage-based PM is on. Save config sets the unit and threshold — "e.g. 2000" — and Log reading records a value. Once the meter passes the threshold, the unit reads as due regardless of the calendar.

Warranty

Status, Start date, and Expiry date, with Add Claim to record a claim against the manufacturer.

No service history is the empty state on a unit that has not been visited yet.

What it accepts

FieldFormatRequiredRule
Nameplate chargeOunces, e.g. 56NoRequired before leak-rate percentages can be worked out
EPA appliance classPick a classNoDecides which compliance obligations apply
Sub-location zonePick a zoneNoWhere in the site the unit sits
Claim dateA dateYes, per claim
Claim descriptionFree text — "What was the claim for?"Yes, per claim
Claim resolutionFree text — optionalNoHow it was settled
Transaction typeCharge, top-up, or recoveryYes, per transaction
RefrigerantPick a refrigerantYes, per transaction
QuantityOuncesYes, per transaction
TechnicianPick a technicianYes, per transaction
Performed onA dateYes, per transaction
Cylinder serialFree textNoTies the charge to the cylinder it came from
Leak test method / resultPick, then recordNoWhat a compliance record needs to be defensible
Technician cert numberFree text — "cert number"NoThe technician's EPA certification
Meter unitFree textYes, to use a meter
PM thresholdA number, e.g. 2000Yes, to use a meterPassing it makes the unit due
Meter readingA numberYes, to logRecorded with the date read

How to configure it

  • Compliance settings decide which refrigerant obligations apply, what the leak-rate thresholds are, and whether cylinder serials are required.
  • Inventory settings supply the cylinders the ledger can be attributed to.
  • Zones on the service site decide what the sub-location picker offers.

Who can see it

This screen sits behind the Customers area.

Owners, office managers and dispatchers can open it. Technicians log refrigerant and readings from the field app instead, on the job. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.

The full role matrix is on Roles & permissions.

On this page