AI System for Preparing Fleet Maintenance Signals for Review

The problem

In day-to-day operations, fragmented signals can obscure an approaching maintenance requirement. When vehicle identifiers, mileage, fault codes, driver notes, maintenance and parts records are scattered across sensors, documents, field records or team files, issues may not become visible in time.

This fragmented data delays preparation of the maintenance review list and forces teams to search manually for supporting evidence again. The fleet technical lead must complete missing records and verify each conflict before making a decision.

A common exception is that sensor calibration or a newly fitted part may generate a temporary alert. Incomplete or incorrect automation that fails to check this context could remove a sound vehicle from service or leave a higher-risk vehicle in operation, so no physical or operational action can be carried out directly.

What we set out to improve

• Proportion of maintenance reviews verified by the technical lead
• Proportion of outputs corrected or rejected by the fleet technical lead
• Time between the source event and the review output

How the system works

1. 01 Define the review scope and the role of the authorised fleet technical lead
2. 02 Retrieve the inputs: vehicle identifiers, mileage, fault codes, driver notes, maintenance and parts records
3. 03 Check source identity, date, calibration or version, and data recency
4. 04 Combine signals by vehicle and time
5. 05 Check the context of maintenance and parts replacement
6. 06 Check for exceptions: sensor calibration or a newly fitted part may generate a temporary alert
7. 07 Place low-confidence or conflicting records in a separate specialist queue
8. 08 Write the source identity, rule, output and timestamp to the audit trail
9. 09 Have the fleet technical lead approve, correct, defer or reject the output

Methods we used

• Combined rule-based and time-series maintenance signals
• Source, format, timing and required-field checks for vehicle identifiers, mileage, fault codes, driver notes, maintenance and parts records
• A missing-data warning instead of an estimate when inputs are incomplete or conflicting
• A separate exception check outside the main rule
• Combined retention of the source, rule result, maintenance review list and human decision

Where people stay involved

Data and security

Access to vehicle identifiers, mileage, fault codes, driver notes, maintenance and parts records is restricted to the minimum permissions required for the task. Commercial, location and employee information is masked where possible, and only the necessary portion of the dataset is sent to the model. Access, outputs and the fleet technical lead's decision are logged; production use does not begin until the organisation has approved the retention period and data location.

Who this suits

Frequently asked questions