An early warning is a change in how the unit behaves under a defined condition. Longer operation, more icing or repeated excursions are recorded observations, not diagnoses by themselves. If mode, load, weather, door traffic or defrost changed, the comparison may not represent the same condition.
Trend table: from observation to service review
| Observation | Context to record | Log information | Service review |
|---|---|---|---|
| Longer time to reach the same target | Product starting condition, load, stops and doors, ambient weather, operating mode and defrost | Start and target time, setpoint, return or supply air, product and logger record | Controls, airflow, defrost, electrical and refrigeration circuit against the model manual |
| More icing | Ice location, defrost completion, humidity, doors and loading layout | Photo, event time, defrost state and prior comparable record | Air passage, drain, defrost control and required technical parts |
| Repeated temperature excursion | Separate product from air sensor; compare route, doors, load and device | Product reading, sensor identity and position, alarm, setpoint and last good record | Qualified review of measurement chain, capacity, control and body condition |
| Changed sound or vibration | Movement, standby, fan or defrost mode and safe observation position | Time, mode, location and event description without touching parts | Mechanical, fan, connection and electrical checks |
| Longer engine or operating time | Weather, load, doors, mode and defrost; engine hours are not compressor hours | Unit operating mode, time window and comparable trip | Technical review using model capacity, controls and maintenance records |
The operator's safe check is limited to visible seal and door closure, whether the load blocks an air path, display mode, alarm time, defrost record, logger identity and last good reading. Opening panels, electrical measurement, refrigerant, pressure, fan or component work belongs to qualified technical personnel.
Longer operation is not always a capacity loss. A different operating mode, warmer weather, a fuller load, more door openings or a defrost cycle can lengthen the time. Likewise, more ice is not called a failure without its defrost context and location; the observation is recorded safely.
A live alarm or a condition marked urgent by the model manual does not wait for a monthly trend meeting. Make the vehicle and unit safe, preserve product condition and independent records, and involve authorised service and the quality decision owner according to the model's severity. Even without an alarm, an observable urgent condition follows the same prompt handover; a quiet trend supplies data for planned technical assessment. The Thermo King Precedent C-600M, S-610M and S-610DE manual notes that alarm codes vary by controller and software, so match the exact model (Thermo King Precedent manual, pp. 114-115).
How to compare records
The review interval is set by the operation's risk and record discipline. Each comparison should show the same unit identity, product and load profile, operating mode, ambient range, stop and door events, defrost state and sensor position. Engine hours, energy use, cycle time and product temperature are separate measures; one does not replace another.
In a hypothetical desk review, the same unit on the same route takes 24 minutes in one record and 32 minutes in a second to bring an empty body to a defined air setpoint. If ambient weather, door openings or defrost also changed on the second run, the record is only a warning. The operations owner marks those differences, the operator records a new observation and qualified technical staff review the same model's maintenance and control data; the number alone is not proof of failure.
Separate the trend from the emergency path with the first-five-minutes cooling-unit fault-code guide. It explains matching the code to the model manual and preserving the alarm, product condition and independent records together.
Tie the maintenance decision to evidence
When repeated records become a service request, include unit model, event times, operating mode, load and weather context, photos, alarms, measurement files and the last maintenance work. Add the service result to the same incident number. Do not infer a universal equipment life or replacement decision from repair frequency alone without considering downtime effect, product risk and available capacity.
The purpose of a trend file is not to make the operator diagnose parts. A useful file separates normal operating variables from repeated observations that merit technical review; it enables a quick handover for a live alarm and comparable records with planned service for a quiet trend.