How to Compare Run Hours Between Assets

Overview

The Explorer → Assets tool can be used to compare run hours-related signals across multiple assets over the same period of time. This is useful when you need to understand whether one asset is being used more heavily than others, identify abnormal operating patterns, or validate whether a utilisation issue is isolated or affecting a broader group of assets.

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

Why comparing run hours is important

Comparing run hours between assets helps teams make better operational, servicing, and utilisation decisions.

Identify overused or underused assets

If one asset is accumulating significantly more or less run hours than comparable assets, it may indicate:

uneven asset utilisation
scheduling or dispatch imbalance
operational inefficiency
maintenance risk due to higher usage

Support servicing and maintenance planning

Run hours is often a key driver for:

preventative maintenance
service intervals
engine-hour based servicing
wear-and-tear assessment

Comparing run hours helps determine whether an asset is approaching service needs faster than similar assets.

Validate customer or site usage patterns

Run hours comparisons can help confirm:

whether assets at one site are used more heavily than others
whether a customer is operating assets as expected
whether a specific asset is idle, underutilised, or overworked

Improve workflow and alert design

Before building a workflow for overrun, excessive idle time, or servicing thresholds, comparing historical run hours behaviour helps confirm:

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

Where to find it

Open Explorer from the left navigation.
Select Assets.

Run hours comparison is usually best performed in History mode using Chart view, because it allows you to visualise and compare how the selected run hours signal changes over time across multiple assets.

Current State vs History for run hours analysis

Current State

Current State shows the latest known value for the selected run hours-related signal.

Use this when you want to:

check the latest run hours value for multiple assets
confirm the signal exists and is populated
quickly compare the most recent reading across selected assets

History

History shows how the selected run hours signal changed over time.

Use this when you want to:

compare utilisation patterns between assets
see how quickly run hours accumulates
investigate when usage increased or stopped
validate whether one asset is running more often than others

For comparison work, History is usually the better option.

Screen layout and controls

Left panel: query configuration

The left panel is where you define what you want to compare.

Search Mode

At the top of the panel, choose:

Current State
History

For run hours comparison across a period, select History.

View

When History mode is selected, you can usually choose between:

Grid
Chart

Grid

Shows the data as a timestamped table.

Best for:

checking exact values
identifying precise times of change
exporting evidence for analysis

Chart

Shows the data visually as a trend line.

Best for:

comparing run hours accumulation between assets
identifying unusual growth patterns
spotting idle periods or unexpected spikes

For most comparison tasks, select Chart.

Date Format

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

Use this to make sure the returned data matches the period you want to analyse.

Days

The Days control defines how much historical data to retrieve.

Use a shorter range when:

reviewing a recent operational issue
checking a recent utilisation concern
validating a specific incident window

Use a longer range when:

comparing weekly usage patterns
reviewing servicing trends
analysing long-term asset utilisation

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 assets that are comparable in purpose and operating conditions
Use a smaller number of assets for clearer visual analysis
Remove unrelated assets that add noise to the chart

Best practice: compare similar asset types wherever possible so the run hours patterns are meaningful.

Signals

The Signals section defines which signal you want to compare.

For this use case, choose the run hours-related signal that best represents asset usage.

Examples may include:

engine hours
run hours
ignition time
operating hours
compressor runtime
equipment runtime
utilisation-related signals specific to your device type or integration

Important: signal names vary depending on the asset type, device model, and integration. Use the signal that most accurately reflects the run hours you want to assess.

Query controls

At the bottom of the panel you will usually see:

Reset
Search

Reset

Clears the current query setup.

Use this when:

you want to restart the comparison
you selected the wrong signal or assets
the chart becomes cluttered

Search

Runs the query using the selected assets, signal, and date range.

Use this whenever you:

change assets
change the signal
change the historical period
switch between Grid and Chart

How to compare run hours 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 how run hours changes over the selected period.

Step 3 – Select Chart view

Choose Chart to compare the behaviour visually across multiple assets.

If you need exact values later, you can switch 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 investigating.

Examples:

last 1–3 days for a recent issue
last 7 days for weekly utilisation comparison
longer periods for servicing and maintenance trend analysis

Step 5 – Select the assets

Choose the assets you want to compare.

For best results:

compare assets with similar roles or operating environments
avoid mixing unrelated asset types unless the comparison is intentional
start with a small group to keep the chart readable

Step 6 – Add the Run Hours signal

In the Signals section, choose the run hours-related signal you want to compare.

If required, you can also use identifier signals in Grid view for export or validation, but for charts it is usually best to keep the selection focused.

Step 7 – Run the search

Select Search to generate the comparison.

Review the chart and look for:

one asset accumulating run hours much faster than the others
one asset showing very little or no run hours compared with the group
long flat sections that may indicate inactivity
unusual jumps that may suggest data quality or device issues

Step 8 – Refine if needed

If the chart is difficult to interpret:

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

How to interpret the comparison

Normal comparative behaviour

A comparison is usually easier to trust when assets:

show broadly similar accumulation patterns for similar usage scenarios
increase at expected times based on operations
remain relatively consistent with their role or site

Signs that one asset may need attention

An asset may need investigation if it:

accumulates run hours much faster than similar assets
shows little or no run hours when it is expected to be operating
starts or stops accumulating unexpectedly
behaves inconsistently with known usage patterns

Signs the issue may be a signal or device problem

Consider a device or data issue if:

run hours jumps in unrealistic steps
values remain flat when the asset is known to be operating
there are long gaps in data
one asset’s pattern is clearly inconsistent with real-world use

Recommended comparison patterns

Compare similar assets

Compare assets with the same or similar purpose, such as:

similar vehicles
similar machinery
similar refrigeration units
similar customer/site allocations

This makes the comparison much more meaningful.

Compare one concern asset against a known good asset

This is often the fastest way to confirm whether the reported issue is real or simply normal for that asset type.

Use History first, then Current State

Start with History to understand the pattern over time, then use Current State to check the most recent value.

Best practices

Use Chart view for comparison and Grid view for validation.
Focus on one run hours signal at a time.
Avoid comparing too many assets at once.
Choose a timeframe that matches the operational question you are trying to answer.
Compare assets with similar functions or workloads.
Export results if you need to share the comparison with maintenance, operations, or support teams.

Troubleshooting

The chart is too crowded

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

I cannot find the run hours signal

check the available signal categories
confirm the connected device supports that signal
use 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 correct

One asset looks flat while others increase

verify whether the asset was inactive
confirm whether the device stopped reporting
switch to Grid view to validate timestamps and actual values