Meter Violation Report

Overview

The Meter Violation report provides a detailed breakdown of telemetry inconsistencies across asset meters, such as odometer and run hour readings. This report is designed to highlight unexpected or invalid changes in meter values—typically when a recorded value regresses or jumps beyond the allowed threshold. These anomalies may indicate issues such as device misconfiguration, duplicate records, communication failures, or backfilled data entries from external systems.

Each row in the report represents an individual meter reading anomaly detected during the selected period. The report compares consecutive readings, calculates the difference (delta), and flags entries where the delta is negative or violates a configured threshold.

This report is particularly useful for diagnosing data integrity issues, preventing billing or maintenance errors, and ensuring that asset usage history remains accurate and reliable.

Report Structure

The generated report includes the following data columns:

Column Name	Description
Timestamp	The date and time the discrepancy was detected by the system.
Asset Id	Unique identifier of the asset associated with the meter violation.
Meter	Indicates which meter type triggered the violation (e.g., odometer, run hours).
Previous Value	The last valid value recorded before the discrepancy.
Current Value	The current value that triggered the violation.
Delta	The calculated difference between the current and previous value. A negative or unexpected value is considered a violation.
Threshold	The defined tolerance level for the delta. A delta outside this threshold raises an alert.
Info	Explains the cause of the violation (e.g., odometer delta < 0).
Asset Timestamp	Timestamp directly from the asset’s data feed, used for context and correlation.
Time Delta	Time difference between data receipt and the asset’s own timestamp. May be used to identify latency or syncing issues.

At the bottom of the report, a generation timestamp confirms when the report was produced, including the local time zone for context.

How to Generate the Report

Navigate to Reports → Asset Telemetry → Meter Violation.
Select the Scope (Relative or Range) and choose your desired Time Period (e.g., Last Week, This Month, Custom Range).
Choose one or more Assets using the asset selector.
Click Run Report.
Once generated, the results are displayed in a structured table and can be exported to PDF, PDF/A, XLS or CSV formats.

Applicability and Use Cases

The Meter Violation report supports a wide range of operational and technical workflows. Common use cases include:

Data Integrity Auditing
Detects backward meter movements or erratic readings that may affect reporting, maintenance tracking, or asset value calculations.
Device Configuration Review
Identifies telemetry device misalignments or firmware issues causing faulty meter readings.
Integration Health Monitoring
Helps confirm consistency of meter data received from third-party ERPs or connectors, such as Baseplan, by comparing them against device telemetry.
Maintenance Accuracy
Ensures run-hour or odometer-based service reminders are triggered from reliable data sources, preventing over-servicing or missed maintenance.
Historical Data Cleansing
Supports reconciliation processes by identifying invalid entries that may need correction or deletion before usage reporting, billing, or compliance exports.

Interpreting the Data

A negative delta (e.g., odometer delta < 0) typically signals a data regression, which should not occur in a properly functioning system.
Repeated violations from a single asset may indicate an underlying device or configuration issue.
A large time delta between the Asset Timestamp and System Timestamp may point to delayed data uploads or device clock drift.
A zero threshold means any deviation is flagged, while a non-zero threshold allows some tolerance for minor discrepancies.

Summary

The Meter Violation report is a vital diagnostic tool for maintaining data trust across your fleet’s telemetry ecosystem. By identifying anomalies in meter readings, it safeguards reporting accuracy, supports device health audits, and prevents cascading operational errors in servicing, billing, and asset lifecycle management.