Skip to main content
Employee Sign in
Dansk (Danmark) Español eesti (Eesti) Français Lietuvių (Lietuva) Latviešu (Latvija) Nederlands

Data Anomalies Report

Sharon Dhesi

Data Anomalies Report

The Data Anomalies report provides you with instant visibility into telematics data issues across your assets—helping you quickly assess the reliability of key utilization metrics.

By highlighting anomalies like missing data, sensor inconsistencies, and odometer or ignition irregularities, it enables faster troubleshooting, reduces manual investigation, and ensures you can trust your fleet data with confidence.

Follow the steps below to access the Data Anomalies Report:

  1. Log in to Unity

  2. From the Navigation Panel on the left-hand side, click the Reports module

  3. From the Reports Library tab, withing the Audit category, select the Data Anomalies report

  4. Select the desired report parameters

  5. Click the Open button

  1. View the Data Anomalies report details

Here are some examples of data anomalies:

Anomaly Description Impact
Invalid data More than 90% of incoming data is missing key properties such as latitude, longitude, and ignition. Missing or unreliable movement and utilization information.
Excessive data Incoming data contains too many snapshots per minute. Noisy data, potential performance impact, and difficulty interpreting trips.
Excessive activities Incoming data causes an excessive number (> 500 activities per hour) of asset activity splits. Fragmented trips/activities and inflated activity counts.
No ECM odometer data Asset is not reporting ECM odometer data. Mileage and maintenance intervals are calculated based on GPS data.
Odometer spike ECM odometer has increased or decreased by an unusually large amount in a short time. Inconsistent mileage records and maintenance scheduling.
Odometer data source conflict ECM and GPS odometer distance mismatch. Inconsistent distance reporting and reduced data trustworthiness.
Movement without ignition The asset has registered movement while the ignition remains off. Unreliable trip detection and potential security concerns.
Odometer stagnation ECM odometer doesn't increase despite ongoing trips. Mileage and maintenance intervals are calculated based on GPS data.
GPS stagnation GPS coordinates don't change despite ongoing movement. Inaccurate location tracking and unreliable trip mapping.
No ECM operating hours data Asset is not reporting ECM operating hours data. Engine usage and hour-based maintenance intervals are calculated based on ignition data.
ECM operating hours spike ECM operating hours have increased or decreased by an unusually large amount in a short time. Inconsistent utilization metrics and maintenance scheduling.
ECM operating hours increase without ignition The asset has registered ECM operating hours while the ignition remains off. Inconsistent operating hours and utilization reporting.
Operating hours stagnation ECM operating hours don't increase despite ongoing trips. Engine usage and hour-based maintenance triggers are calculated based on ignition data.

Related articles