Track Odometer Readings and Audit Tampering

1. Overview & Business Value#

This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for Track Odometer Readings and Audit Tampering within SmartERP.

Automated and manual odometer tracking, anomaly detection, unreasonable mileage jumps, and tamper audit trails.

{screenshot:odometer-tracking-and-tamper-audit-overview-dashboard}

2. Prerequisites & Security Access Groups#

• Required Modules: fleet, smarterp_fleet_operations, smarterp_fleet_insurance
• Security Groups:
  • Fleet Operator (Technical ID: fleet.group_fleet_user)
  • Fleet Administrator / Transport Manager (Technical ID: fleet.group_fleet_manager)
• Master Data Dependencies: Vehicle asset cards, license plate registry, fuel cards, driver profiles, scheduled maintenance intervals, and third-party insurance policies.

3. Step-by-Step Configuration & Execution#

Step 1: Navigating to the Module Interface#

1. Log into your SmartERP instance at https://smarterp.et/odoo.
2. Open the main App Switcher (grid icon in the top-left corner).
3. Select the Fleet app icon.
4. From the top navigation bar, open Fleet → Vehicles → Fleet Registry / Odometer Logs / Service Logs / Insurance Policies.

{screenshot:odometer-tracking-and-tamper-audit-app-switcher-navigation}

Step 2: Creating and Parameterizing Records#

1. Click the New button in the top-left control panel.
2. Complete the mandatory fields in the record form:
   • License Plate & Vehicle Model (Mandatory): Official Ethiopian registration plate number and chassis VIN
   • Assigned Driver (Mandatory): Licensed company employee or authorized transport driver
   • Current Odometer Reading (Mandatory): Kilometer milestone verified against vehicle dashboard
   • Insurance Policy Reference (Mandatory): Mandatory Ethiopian third-party insurance certificate details
3. Configure optional operational parameters and localized tags as required:
   • Fuel Card Identifier (Optional): Designated commercial petroleum electronic fuel card number
   • Service Workshop Vendor (Optional): Approved maintenance garage or internal fleet workshop
   • Vehicle Department / Cost Center (Optional): Analytic account absorbing vehicle operating expenditures
4. Click the Save icon in the control bar to commit the record.

{screenshot:odometer-tracking-and-tamper-audit-record-creation-form}

Step 3: Validating and Processing Transactions#

• State Transitions: Execute operational state progression (Available → Dispatched / En Route → In Workshop → Service Completed → Available).
• Ledger & System Impact: Service invoices and fuel receipts debit fleet vehicle operational expense accounts and credit vendor payables or fuel imprest accounts.
• Audit Verification: Automated recording of author ID, timestamp, and immutable revision history.

{screenshot:odometer-tracking-and-tamper-audit-transaction-processing-state}

Odometer Integrity in Fleet Governance#

Accurate odometer logging is essential for scheduling preventative maintenance, validating fuel consumption rates, and calculating accurate billing for project transport allocations.

[fleet-fuel-odometer-audit]

Procedure: Logging an Odometer Reading#

1. Navigate to Fleet > Operations > Odometer and click New.
2. Select Vehicle (e.g., 3-B12345 AA).
3. Enter the Date and Reading (km) (e.g., 18,450 km).
4. Click Save.

Automated Tamper and Anomaly Audits#

SmartERP enforces strict mathematical validation rules on odometer inputs:

1. Rollback Prevention: The system rejects any odometer entry lower than the highest historical reading recorded for that vehicle.
2. Speed-Distance Sanity Check: If an odometer jump implies an average traveling speed exceeding $130\text{ km/h}$ over the elapsed time since the previous log, SmartERP flags the entry as an anomaly.
3. Audit Trail: Any supervisory correction of an odometer reading requires a recorded business justification and leaves an immutable log in the chatter.

4. Advanced Configuration Points#

• Automated Actions & Scheduled Tasks (Crons):
  • Fleet: Trigger preventive maintenance intervals (fleet.ir_cron_service_interval): Runs daily to alert transport officers when vehicles approach service kilometer thresholds
  • Insurance: Alert expiring third-party liability policies (fleet.ir_cron_insurance_alert): Runs weekly to flag insurance policies expiring within 30 days
• Custom Print Templates & Reports:
  • Vehicle Preventive Maintenance Work Order
  • Fleet Fuel Consumption & Mileage Analysis (km/L)
  • Third-Party Liability & Comprehensive Insurance Schedule
  • Driver Incident & Vehicle Lifecycle Cost Ledger
• Multi-Company Rules: Record-level security isolation under Company 1 (Ashewa Technology Solutions S.C.), preventing cross-company ledger leakage across parent and subsidiary legal entities.

5. Comprehensive Troubleshooting Matrix#