Predictive maintenance, diagnostics and service reminders
A fault code, a service reminder and a failure prediction are three different things. A fault code supports review of that reported condition; a reminder follows its interval rule; prediction needs a defined outcome, horizon and validation; diagnosis stays an accountable technical judgment.
Where ReWheel stands
ReWheel FMS offers AI-assisted reporting. ReWheel FMS connects supported vehicle information with equipment and operational records for field and institutional operations. Vehicle compatibility, data-access requirements, connectivity and installation are assessed per deployment, never assumed. A workflow discussion starts from the maintenance question you need answered and the records behind it.
Five different capabilities
On a small screen, scroll this table horizontally. Keyboard users can focus the table region and use arrow keys.
| Capability | What the claim means here | Ask for | What it cannot show |
|---|---|---|---|
| Fault indication | A source reports a current or stored fault condition | Code/source/time plus supported vehicle and field mapping | Root cause, future failure or fitness to drive |
| Threshold alert | A configured rule crosses a stated limit | Rule version, units, threshold, raw inputs and crossing time | A learned forecast or diagnosis |
| Scheduled interval | A service becomes due under an approved time/distance/hour rule | Authoritative service policy, last service and compatible counter | Condition-based prediction or safe service deferral |
| Statistical prediction | A defined future outcome is estimated for a specified horizon | Labelled outcomes, held-out evaluation, false alarms, missed failures and lead-time distribution | A fault-code screenshot alone or guaranteed failure time |
| Qualified diagnosis | An accountable technical role determines the issue using appropriate records | Inspection/testing record, qualified reviewer and disposition | A map, alert or generated explanation alone |
Ask for the exact source, vehicle and field support rather than assuming an OBD connection exposes every parameter.
A fault code is not a forecast
Questions to ask about a prediction claim
Ask the supplier
- What failure and horizon are predicted, and where do the labels come from?
- Do the labels cover both failures and non-failures?
- Were vehicles or periods held out of the training data?
- How are false positives and missed failures counted?
- How long before a confirmed outcome does a warning appear?
- Which vehicles, models, years and fields are covered?
The download is a blank scorecard. Each criterion starts as not supplied and unassessed, which is not a score of zero.
Check engine-hour counter meaning before using it
AI fleet reporting: useful questions and the records they need
Neutral maintenance validation scorecard
The CSV turns the six supplier questions into a blank scorecard. There is no benchmark or predicted failure.
This table is shown in the section above.
What ReWheel provides
ReWheel FMS connects supported vehicle information with equipment and operational records for field and institutional operations. Vehicle compatibility, data-access requirements, connectivity and installation are assessed per deployment, never assumed.
Continue with ReWheel: How a ReWheel workflow discussion works
Discuss your workflow