Fault-code-driven servicing
Turn engine fault codes into work orders — what Yipii does on its own today, what it still leaves to a person, and what that is worth in a week.
A driver mentions the engine light "has been on for a bit". Nobody knows when it came on, what the code was, or whether it is still active — because the only record was a conversation.
Vehicles with an OBD-connected tracker report diagnostic trouble codes (DTCs) as they happen. Yipii captures them, decodes them, and lets you raise a work order from one.
Be clear about what this is
This page is deliberately blunt about the boundary, because the gap is where people get caught out.
What Yipii does today
- Captures DTCs reported by the vehicle, with the time they occurred.
- Decodes the code into a plain-language description.
- Shows them fleet-wide and per vehicle in Diagnostics.
- Lets you raise a work order from a fault.
What Yipii does not do today
- There is no automation trigger on fault codes. Mobility's rule engine can fire on distance, service due dates, failed inspections, expiring documents and geofences — but not on a DTC. A person reviews the list and decides.
- It does not clear codes or write to the ECU. Clearing happens at the vehicle.
- It does not diagnose. A code names a symptom and a circuit, not a repair.
If you were expecting "fault appears → work order books itself", that is not the product today. What you get is that no fault goes unseen, and the one that matters becomes a job in two clicks.
What goes wrong without it
- Faults live in the driver's head. Codes come and go between services and never reach the workshop.
- Intermittent faults are invisible. A code that appears on cold mornings and clears by the time the vehicle reaches the bay looks like nothing — unless something logged it.
- No history at the point of repair. The mechanic sees today's symptom, not that the same code appeared four times this quarter.
- Small faults become big ones. An emissions code ignored for months turns into a catalytic converter.
How Yipii handles it
| Problem | What you use | What you get |
|---|---|---|
| Faults never reaching the workshop | Diagnostics fleet view | Every reported code across the fleet in one list, with the vehicle and the time |
| Intermittent codes | The DTC log over a date range (last 30 days by default) | Repeat offenders become visible as a pattern rather than a one-off |
| Turning a fault into work | Create work order on the fault row | A work order pre-linked to the vehicle, so the repair is costed and recorded |
| Understanding the code | Decoded descriptions alongside the raw code | The mechanic starts from a description, not a number |
| Live detail per vehicle | The OBD faults panel in Yipii IoT | Current faults next to live telemetry for that vehicle |
A week in the life
Tuesday 06:40 — A van throws P0420 on a cold start. The tracker reports it.
Tuesday 09:00 — The maintenance coordinator opens Diagnostics, filters to active faults, and sees the van listed with the decoded description.
Tuesday 09:02 — It is the third time this month for the same vehicle. They use Create work order on the row, which opens a work order against that van.
Thursday — The van is in the bay. Parts and labour go onto the work order, so the repair cost sits against the vehicle's lifetime record.
Month end — The vehicle's cost history shows the pattern: three visits for the same circuit, which is the argument for replacing the part properly rather than clearing it again.
What you'll need
- An OBD-connected tracker. Fault codes come from the vehicle's diagnostic port. A tracker wired only to power and ignition reports position, not DTCs.
- A vehicle that reports codes. Coverage varies by make, model and year. Older commercial vehicles and most plant will report little or nothing.
- Somebody who reviews the list. This is the honest requirement. Because nothing fires automatically, fault-code servicing works when it is part of someone's weekly routine.
- Both products. The fault data originates in Yipii IoT and surfaces in Mobility.
Typical results
| Lever | Assumption | Annual effect |
|---|---|---|
| Early catch on an emissions fault | 1 catalytic converter avoided every 2 years, €900 | €450/yr amortised |
| Repeat faults fixed properly | 3 avoided repeat visits, €160 of labour each | €480 |
| Breakdowns avoided | 2 roadside call-outs, €220 each | €440 |
| Diagnostic time saved | 20 min/job × 24 jobs, €35/h | €280 |
Worked examples using the assumptions shown, not measured customer outcomes.
Get started
- Confirm the vehicle has an OBD-connected tracker.
- Open Diagnostics and check codes are arriving.
- Put a weekly review in someone's calendar — this is the step that makes it work.
- Raise work orders from the faults worth acting on.
Servicing that does run itself? See servicing by distance.