How to Compare Temperature Behaviour Between Assets

Overview

The Explorer → Assets tool can be used to compare temperature-related signals across multiple assets over the same period of time. This is especially useful when you need to understand whether one asset is behaving normally compared with others, identify unusual temperature patterns, or validate whether a temperature issue is isolated or widespread.

This article explains how to use the Explorer module to compare temperature behaviour between assets, why this is important, and how to interpret the results.

Why comparing temperature behaviour is important

Comparing temperature behaviour between assets helps teams make better operational decisions and troubleshoot faster.

Identify abnormal assets quickly

If one asset’s temperature trend looks significantly different from similar assets, it may indicate:

a refrigeration issue
a sensor issue
a device installation problem
a usage or operational difference that needs review

Validate whether an issue is isolated or systemic

When a customer reports a temperature concern, comparing that asset with similar assets can help determine whether:

only one asset is affected
a group of assets is affected
the issue may be linked to environment, workflow, or integration

Support investigations and compliance checks

Temperature comparisons are useful for:

refrigerated transport and cold-chain monitoring
equipment overheating investigations
sensor validation
proving when a temperature excursion started and how severe it was

Improve workflow design

Before creating a workflow for temperature alerts, comparing historical temperature behaviour helps confirm:

which signal should be used
what threshold is realistic
whether the signal is stable enough for alerting

Where to find it

Open Explorer from the left navigation.
Select Assets.

Temperature comparison is typically done in History mode using Chart view, because this makes it easier to see how values change over time across multiple assets.

Current State vs History for temperature analysis

Current State

Current State shows the latest known value for the selected temperature signal.

Use this when you want to:

check the latest temperature for multiple assets
confirm whether a signal is available
quickly see which asset is currently hottest or coldest

History

History shows how the selected temperature signal changed over time.

Use this when you want to:

compare temperature patterns across multiple assets
identify spikes, dips, drift, or unusual fluctuation
investigate an incident during a specific time range
validate whether a reported issue occurred once or repeatedly

For comparison work, History is usually the better option.

Date Format

The Date Format dropdown controls how the historical period is defined or displayed.

Depending on tenant configuration, this may support options such as relative time ranges or different date groupings.

Use this to make sure the chart reflects the period you want to analyse.

Days

The Days control defines how much historical data to retrieve.

Use a shorter range when:

investigating a recent issue
comparing short-term behaviour
reviewing a single trip, day, or event window

Use a longer range when:

analysing repeated patterns
comparing assets over several days
validating long-term performance

Assets selector

The Assets selector is where you choose the assets you want to compare.

Controls

asset dropdown
selected asset chips
remove controls for each selected asset

Usability

Select multiple assets that are comparable
Try to compare assets of the same type, use case, or operating conditions where possible
Remove assets that create visual noise or are not relevant to the analysis

Best practice: compare only a small number of assets at once for chart readability.

Signals

The Signals section defines which signals are included in the comparison.

Controls

selected signal rows
remove controls on each row
Add Signal button

For this use case, choose the temperature-related signal you want to compare.

Examples might include:

engine coolant temperature
compartment temperature
BLE temperature
refrigerated unit temperature
temperature sensor channels specific to your devices

Important: signal names vary by integration and device type. Use the signal that best represents the temperature behaviour you want to assess.

How to compare temperature behaviour between assets

Step 1 – Open Explorer → Assets

Go to the Assets Explorer.

Step 2 – Switch to History

Select History in Search Mode.

This enables time-based analysis and allows you to review temperature changes over a selected period.

Step 3 – Select Chart view

Choose Chart so you can compare the visual behaviour of the assets over time.

If you need exact timestamps later, you can switch back to Grid.

Step 4 – Set the time range

Use the Date Format and Days controls to define the historical window you want to analyse.

Choose a timeframe that matches the question you are trying to answer.

Examples:

last 1 day for a recent alert
last 3–7 days for operational trend comparison
longer periods for repeated behavioural checks

Step 5 – Select the assets

Choose the assets you want to compare.

For best results:

compare assets with similar operating conditions
avoid mixing unrelated assets unless the comparison is intentional
start with a small group so the chart remains readable

Step 6 – Add the temperature signal

In the Signals section, select the temperature signal you want to compare.

If needed, you may also add an identifier signal in Grid view for exported data, but for charts it is often best to keep the signal selection focused.

Step 7 – Run the search

Select Search to generate the comparison.

Review the chart and look for:

one asset consistently running hotter or colder
abnormal spikes or drops
irregular fluctuation compared with the other assets
missing periods or flat lines that may indicate sensor/device issues

Step 8 – Refine if needed

If the chart is hard to read:

reduce the number of assets
shorten the time range
confirm you selected the correct temperature signal
switch to Grid to validate exact values and timestamps

How to interpret the comparison

Normal comparative behaviour

A comparison is easier to trust when assets:

show broadly similar temperature ranges
follow similar operating cycles
change in ways that make sense for the environment or equipment type

Signs that one asset may need attention

An asset may need investigation if it:

remains consistently hotter or colder than comparable assets
spikes sharply while others remain stable
fluctuates rapidly without operational reason
shows missing data or long flat sections suggesting stale reporting

Signs the issue may be a sensor or device problem

Consider a sensor or telemetry issue if:

only one asset shows unrealistic values
values jump abruptly without a plausible operational cause
there are long data gaps
values appear fixed or frozen when they should be changing

Recommended comparison patterns

Compare similar assets

Compare assets with the same use case where possible, such as:

similar refrigerated units
similar vehicle types
similar sites or routes
similar operating windows

This gives more meaningful results.

Compare one problem asset against a known good asset

This is often the fastest way to confirm whether a reported issue is genuine.

Use History first, then Current State

Start with History to understand the pattern, then use Current State to check what the asset is doing now.

Best practices

Use Chart view for visual comparison and Grid view for validation.
Keep the comparison focused on one temperature signal at a time.
Avoid comparing too many assets at once.
Choose a timeframe that matches the incident or behaviour you are investigating.
Use similar assets for more reliable interpretation.
Export the results if you need to share findings with operations, support, or customers.

Troubleshooting

The chart is too crowded

reduce the number of selected assets
shorten the number of days
remove unnecessary signals

I cannot find the temperature signal

check the correct signal category
confirm the asset’s connected device supports that signal
try Current State first to confirm the signal exists

No historical values are returned

increase the time range
confirm the asset/device was reporting during that period
confirm the selected signal is the correct one

One asset looks flat while others change

verify whether the asset was inactive
check if the sensor stopped updating
switch to Grid view to confirm exact timestamps