Skip to main content

Access Engine Utilization from the T3 Map

Learn how to use the access utilization tools on the T3 Map to make data-driven decisions.

Updated today

The T3 Map shows engine hour usage across your fleet and for individual assets, all in one place. This makes it easier to understand utilization, identify underused equipment, and make quick decisions without leaving the map.

View Fleet Engine Hours

A chart above the asset list shows total engine hours for all visible assets over the last 7 days.

What you can do

  • See total usage across your fleet at a glance

  • Identify low or high usage assets using usage buckets

  • Filter assets directly from the chart by selecting a bar in the chart

  • Sort the asset list by highest or lowest engine hours

  • Apply filters (geofence, group, category) to update the chart

The chart updates automatically based on the assets currently shown on the map.

View Engine Hours for an Asset

Each asset card shows total engine hours for the last 7 days. You can also view a daily breakdown.

How to access

  1. Select an asset on the map

  2. Open the asset preview card

  3. Select the chart icon in the Map Control Bar

  4. Expand the Usage section

View Usage Breakdown

The Usage panel shows how an asset has been used over time.

What you’ll see

  • Daily engine hours for the selected time period

  • Time range options from 7 days up to 4 weeks

  • Week-over-week change to highlight usage trends

Common Use Cases

  • Find underused equipment to prioritize for dispatch

  • Identify idle assets that may not be needed on a jobsite

  • Compare recent usage trends to understand changes in activity

  • Review usage within a location by applying map filters

  • Spot reporting issues when expected assets are missing from results

Data Notes

  • Data updates approximately every five minutes

  • Only assets with engines and compatible trackers are included

  • Engine usage on the map comes directly from T3 trackers

Usage shown in Analytics dashboards may differ due to additional processing and business logic.

Did this answer your question?