SEE WHAT CHANGED.

Routine logs capture readings. Chiller Trend shows what changed.

Routine logs can look normal on paper while hiding a meaningful performance shift. Chiller Trend compares readings against baseline, peer, design, or prior data so service teams can see what changed, why it matters, and what to verify next.

The readings were already there. Chiller Trend made the change visible.

Change detection example

Change detected: one chiller used 45% more kW/ton.

The static log sheets captured the readings. Chiller Trend made the change visible by calculating and comparing the data the same way.

CH-1 0.58
CH-2 0.40
Operating gap 45%

The readings were there. The change was hidden.

As static log sheets, both logs looked usable. The readings were recorded, but the performance change was not obvious until the data was calculated, standardized, and compared against the peer chiller.

Static log sheet view

CH-1 Static Log Sheet
CH-2 Static Log Sheet
The static log sheets recorded the readings.
They did not reveal the change.
Chiller Trend did.

Change detection view

Detected kW/ton change
CH-1 0.58
CH-2 0.40
CH-1 was operating at roughly 45% higher kW/ton than CH-2 under comparable conditions.
(0.58 - 0.40) ÷ 0.40 = 45%
Change detection depends on comparable readings. Chiller Trend standardizes the method first.

Change detection only works when the comparison is fair.

A log can look complete and still be hard to compare. One technician may record panel values. Another may verify sensors. Another may calculate flow differently.

Chiller Trend structures the method so routine readings can be compared with stronger confidence.

Once the method is consistent, baseline changes, peer comparisons, and findings become more defensible.

Standardization makes change detection repeatable.

A strong chiller mechanic can spot patterns that raw logs often miss. The problem is that expertise does not scale cleanly across every site, every technician, every vendor, and every report.

Chiller Trend turns the method into a repeatable workflow. Each reading follows the same structure, uses the same calculation logic, and creates a record that can be compared over time.

The same method, repeated over time,
is what makes change detection useful.

Built for repeatable change detection, not fake precision.

Field data is not perfect. Sensors drift. BAS values can be biased. Measurement methods vary.

Chiller Trend does not treat every field value as certified truth. It checks whether the method, measurement location, and operating condition are consistent enough to detect a meaningful change.

If the data is not strong enough, the output should be limited, downgraded, or marked for verification.

From routine log to change detected

Log the Chiller
Compare Against Baseline / Peer / Design
Check Confidence
Detect Meaningful Change
Recommend Verification
Generate Finding
Detected changes become findings, verification steps, recommended actions, and usable equipment history.

Why change detection matters

1

Detect Change Earlier

See when performance shifts from baseline, peer, design, or prior readings.

2

Check Confidence

Know whether the comparison is strong, limited, or needs verification.

3

Standardize the Method

Give teams one repeatable way to collect, calculate, compare, and document chiller data.

4

Create Usable History

Turn routine logs into equipment history that supports follow-up, verification, and better customer conversations.

Start with free field tools

Use the calculators to run common chiller checks the same way every time. The same repeatable logic supports Chiller Trend’s change detection workflow.

Open Free Calculators →

Start with one chiller. See what changes.

Start with structured water-cooled chiller logging. Build repeatable history. Detect meaningful changes over time.

Request Free Mechanic Early Access

GET FIELD NOTES AND UPDATES

Calculator updates, field notes, and Chiller Trend launch updates.