--- title: Monitor engine activity, inputs and utilisation description: Review engine-on and idle periods, measure hardware input activity and compare event duration with an operating target. --- [Skip to content](https://support.trackmyride.com.au/knowledge-base/monitor-engine-activity-inputs-and-utilisation#main-content) [![Knowledge-Base-Logo-2](https://support.trackmyride.com.au/hs-fs/hubfs/Knowledge-Base-Logo-2.png?width=319&height=60&name=Knowledge-Base-Logo-2.png)](https://support.trackmyride.com.au/knowledge-base?hsLang=en-au) - [Knowledge Base Home](https://support.trackmyride.com.au/knowledge-base) - [Sign Me Out](https://support.trackmyride.com.au/_hcms/mem/logout) Open main navigation Close main navigation - [Knowledge Base Home](https://support.trackmyride.com.au/knowledge-base) - [Sign Me Out](https://support.trackmyride.com.au/_hcms/mem/logout) - - [Create Support Ticket](https://support.trackmyride.com.au/knowledge-base/kb-tickets/new) [Create Support Ticket](https://support.trackmyride.com.au/knowledge-base/kb-tickets/new?hsLang=en-au) How can we help you? - There are no suggestions because the search field is empty. 1. [Track My Ride Knowledge Base](https://support.trackmyride.com.au/knowledge-base?hsLang=en-au) 2. [Reports & Dashboard](https://support.trackmyride.com.au/knowledge-base/reports-dashboard?hsLang=en-au) 3. [Reports](https://support.trackmyride.com.au/knowledge-base/reports-dashboard?hsLang=en-au#reports) 28 August 2026 # Monitor engine activity, inputs and utilisation ## Review engine-on and idle periods, measure hardware input activity and compare event duration with an operating target. Use the hardware activity reports to answer different operating questions: **When did the tracker detect the engine turning on or off?** **Engine On/Off** **When was the engine running without a recorded journey?** **Engine Idle** **How long was equipment connected to a tracker input active?** **Inputs** **How often did an engine or input event meet an operating-duration target?** **Utilisation** ## Before you start These reports require a compatible hardware tracker and correctly configured event detection. Confirm the vehicle's engine source and input wiring under its tracker settings before treating report results as operational evidence. With positive sensing, an input is active while the corresponding tracker wire receives a signal greater than 9 volts. On a supported TMR-S8, Input 1 can instead use negative sensing and is active while connected to ground. Positive sensing is the default, and Input 2 remains positive sensing. Use a qualified installer for wiring changes and confirm the Input 1 mode matches its physical circuit. Reported engine and input events describe the electrical signals received by Track My Ride; they do not independently prove why equipment was operating. Choose a short representative date range first. This makes it easier to compare results with known vehicle activity before reporting across the whole fleet. ## Steps ### Review engine and idle activity 1. Open **Reports \> Engine On/Off**. 2. Choose the date range and vehicle, then select **Run Report**. 3. Compare the event times with expected shifts and journeys. Repeated, missing or implausibly long events can indicate configuration, wiring, power or connectivity issues. 4. Open **Reports \> Engine Idle** and choose the same period and vehicle. 5. Select **Options** and set the minimum idle duration that matters to your operation. 6. Run the report and review the idle summary, chart and rows. Each row identifies a start, stop, duration and location where the engine was detected as running without a journey. Use idle results as an investigation list. Confirm the engine-event setup and surrounding GPS data before using a result for coaching, fuel analysis or compliance. ### Review connected equipment 1. Open **Reports \> Inputs**. 2. Choose the date range and one vehicle or the relevant fleet selection. 3. Select **Run Report**. 4. Review the event name, start, stop, duration and **Input Channel**. Match the channel with the device recorded in the vehicle's tracker settings, such as a pump, light, alarm or tray. 5. If a channel is missing or remains active unexpectedly, compare the period with Raw GPS data and have the input wiring checked where necessary. ### Measure utilisation against a target 1. Open **Reports \> Utilisation** and select **Options**. 2. Choose whether charts should group results by **Vehicle** or **Driver of the vehicle**. 3. Under **Input event**, choose **Engine On/Off**, **Ignition input wire**, **Input 1 wire** or **Input 2 wire**. 4. Enter the **Benchmark time (sec)**. 5. Choose whether events should **Exceed benchmark time** or remain **Below benchmark time**. 6. Enter the number of **Target goals per day** and select the days that belong in the comparison. ![Utilisation report options for grouping hardware events and setting a duration benchmark and daily target.](https://support.trackmyride.com.au/hubfs/track-my-ride-support/screenshots/monitor-engine-input-utilisation/utilisation-options.png) Utilisation report options for grouping hardware events and setting a duration benchmark and daily target. 1. Close the options, choose the date range and vehicles, then select **Run Report**. 2. Review the charts and event rows together. A row provides the event period, duration and locations; the charts summarise performance against the selected benchmark and target. ![Utilisation results showing an example vehicle event period duration driver and locations.](https://support.trackmyride.com.au/hubfs/track-my-ride-support/screenshots/monitor-engine-input-utilisation/utilisation-results.png) Utilisation results showing an example vehicle event period duration driver and locations. An event counts towards the daily target only when its duration passes the selected benchmark. **Exceed benchmark time** counts events longer than the benchmark; **Below benchmark time** counts events shorter than it. The target percentage compares the number of passing events with **Target goals per day** for each included day. A day is capped at 100%, even when it exceeds the target, and the report averages the included days. For example, with a target of two events across Monday to Friday, daily counts of 1, 2, 3, 0 and 0 produce 50%, 100%, 100%, 0% and 0%. The displayed average is 50%. **Average Utilisation Time (sec)** is separate: it is the average duration of the reported events, not the percentage of the daily target achieved. ## What happens next Export the filtered report when an authorised person needs the event details. Record the report name, filters and option values used for any decision so another reviewer can reproduce the results. Correct tracker configuration before comparing periods. A wiring or engine-detection change can alter what counts as an event even when real-world vehicle use has not changed. ## Troubleshooting - **A report is empty:** Confirm the vehicle uses compatible hardware, widen the date range and check that the selected event is configured and producing data. - **Idle time looks too high:** Compare Engine On/Off, Journeys and Raw GPS for the same period. Incorrect engine detection or missing journey data can create misleading idle periods. - **An input reports the wrong equipment:** Check which physical device is connected to that input channel and update the vehicle's recorded configuration. - **A driver group is missing:** Driver grouping depends on a known driver assignment during the event. Try grouping by vehicle to confirm the underlying activity. - **The target percentage is lower than expected:** Check whether every intended weekday is selected. Included days with no passing events contribute 0%, while days above the target remain capped at 100%. - **Utilisation results changed unexpectedly:** Confirm the benchmark direction, daily target, included days and selected event before comparing the result with an earlier run. - [Getting Started](https://support.trackmyride.com.au/knowledge-base/getting-started?hsLang=en-au#main-content) - [Account Setup](https://support.trackmyride.com.au/knowledge-base/getting-started?hsLang=en-au#account-setup) - [Installation](https://support.trackmyride.com.au/knowledge-base/installation?hsLang=en-au#main-content) - [Hardware Trackers](https://support.trackmyride.com.au/knowledge-base/installation?hsLang=en-au#hardware-trackers) - [Live Tracking & Map](https://support.trackmyride.com.au/knowledge-base/live-tracking-map?hsLang=en-au#main-content) - [Playback](https://support.trackmyride.com.au/knowledge-base/live-tracking-map?hsLang=en-au#playback) - [Zones](https://support.trackmyride.com.au/knowledge-base/live-tracking-map?hsLang=en-au#zones) - [Route Planning](https://support.trackmyride.com.au/knowledge-base/live-tracking-map?hsLang=en-au#route-planning) - [Vehicles & Hardware](https://support.trackmyride.com.au/knowledge-base/vehicles-hardware?hsLang=en-au#main-content) - [Vehicles](https://support.trackmyride.com.au/knowledge-base/vehicles-hardware?hsLang=en-au#vehicles) - [Tracker Events](https://support.trackmyride.com.au/knowledge-base/vehicles-hardware?hsLang=en-au#tracker-events) - [Trackers](https://support.trackmyride.com.au/knowledge-base/vehicles-hardware?hsLang=en-au#trackers) - [People & Mobile Location Sharing](https://support.trackmyride.com.au/knowledge-base/people-mobile-location-sharing?hsLang=en-au#main-content) - [People](https://support.trackmyride.com.au/knowledge-base/people-mobile-location-sharing?hsLang=en-au#people) - [Mobile Location Sharing](https://support.trackmyride.com.au/knowledge-base/people-mobile-location-sharing?hsLang=en-au#mobile-location-sharing) - [Rosters & Reservations](https://support.trackmyride.com.au/knowledge-base/rosters-reservations?hsLang=en-au#main-content) - [Rosters](https://support.trackmyride.com.au/knowledge-base/rosters-reservations?hsLang=en-au#rosters) - [Reservations](https://support.trackmyride.com.au/knowledge-base/rosters-reservations?hsLang=en-au#reservations) - [Reservation Portal](https://support.trackmyride.com.au/knowledge-base/rosters-reservations?hsLang=en-au#reservation-portal) - [Alerts](https://support.trackmyride.com.au/knowledge-base/alerts?hsLang=en-au#main-content) - [Alert Setup](https://support.trackmyride.com.au/knowledge-base/alerts?hsLang=en-au#alert-setup) - [Alert History](https://support.trackmyride.com.au/knowledge-base/alerts?hsLang=en-au#alert-history) - [Reports & Dashboard](https://support.trackmyride.com.au/knowledge-base/reports-dashboard?hsLang=en-au#main-content) - [Reports](https://support.trackmyride.com.au/knowledge-base/reports-dashboard?hsLang=en-au#reports) - [Scheduled Reports](https://support.trackmyride.com.au/knowledge-base/reports-dashboard?hsLang=en-au#scheduled-reports) - [Sharing, API & Integrations](https://support.trackmyride.com.au/knowledge-base/sharing-api-integrations?hsLang=en-au#main-content) - [Map Sharing](https://support.trackmyride.com.au/knowledge-base/sharing-api-integrations?hsLang=en-au#map-sharing) - [API](https://support.trackmyride.com.au/knowledge-base/sharing-api-integrations?hsLang=en-au#api) - [Account, Billing & Security](https://support.trackmyride.com.au/knowledge-base/account-billing-security?hsLang=en-au#main-content) - [Billing](https://support.trackmyride.com.au/knowledge-base/account-billing-security?hsLang=en-au#billing) - [Security](https://support.trackmyride.com.au/knowledge-base/account-billing-security?hsLang=en-au#security) - [Account Settings](https://support.trackmyride.com.au/knowledge-base/account-billing-security?hsLang=en-au#account-settings) - [Sub-accounts](https://support.trackmyride.com.au/knowledge-base/account-billing-security?hsLang=en-au#sub-accounts) - [Troubleshooting](https://support.trackmyride.com.au/knowledge-base/troubleshooting?hsLang=en-au#main-content) - [Account access](https://support.trackmyride.com.au/knowledge-base/troubleshooting?hsLang=en-au#account-access) - [Tracking](https://support.trackmyride.com.au/knowledge-base/troubleshooting?hsLang=en-au#tracking) - [Home](https://www.trackmyride.com.au/) - [Products](https://www.trackmyride.com.au/shop) - [Pricing](https://www.trackmyride.com.au/pricing) - [Company](https://www.trackmyride.com.au/about) [![Knowledge-Base-Logo-3](https://support.trackmyride.com.au/hs-fs/hubfs/Knowledge-Base-Logo-3.png?width=319&height=60&name=Knowledge-Base-Logo-3.png "Knowledge-Base-Logo-3")](https://https://support.trackmyride.com.au/knowledge-base) [www.trackmyride.com.au](https://www.trackmyride.com.au) [mailto:support@trackmyride.com.au](mailto:support@trackmyride.com.au)