Skip to content
Warehouse, shipping & traceabilityConstruction & Building ServicesMining & Raw MaterialsWaste & RecyclingEnergy & Utilities+2

Plan vehicle maintenance from fault codes

demi reads fault codes from telematics, spots patterns that come before breakdowns and puts the workshop slot into a gap in the route plan.

Today

Trucks, tractor units and reach stackers often report fault codes for weeks before they break down: a NOx sensor fault, a particulate filter that no longer regenerates, slowly falling oil pressure. The codes flow into telematics, but nobody analyses them, and the workshop only hears from the driver that a warning light is on. By then the appointment comes too late, the vehicle stops on the motorway or at the terminal, and containers, driver and customer wait.

An example

At Nordhanse, tractor unit 31 has been reporting the same NOx sensor fault again and again for eleven days, plus two aborted regenerations of the particulate filter. The agent recognizes the pattern: last year, three tractor units of the same series went into reduced power within three weeks after this, once in the middle of the A7 motorway. It finds the Thursday on which unit 31 has only a short run to the container terminal, sees the sensor in stock and proposes a workshop slot from 13:00, together with the tachograph inspection that is due. Dispatch confirms, and the workshop has codes, history and parts list in the order.
Fictional company, typical workflow.

Your data, wherever it lives

The warning signs of a failure sit in separate systems today: fault codes, mileage and operating hours in telematics, workshop orders and spare parts in the ERP, manuals and service bulletins in the DMS, routes with dispatch, workshop appointments in calendars and e-mails. demi reads, understands and links it per vehicle, with your rights. The AI sees a pattern weeks before the breakdown and proposes a slot in a gap between routes, and dispatch decides.

Where the data lives today

  • Telematics
  • ERP
  • DMS & archive
  • Calendars
  • E-mails
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: telematics, the ERP, route planning, DMS, calendar and e-mail. demi replaces nothing and links, per vehicle, fault codes, mileage and operating hours with workshop orders, past breakdowns, spare-part stock, manufacturers' manuals and service bulletins, the routes and workshop appointments.

  2. 2 · PermitPermission Layer

    The workshop and fleet management see all fault codes and history, dispatch only availability and planned workshop slots, drivers the status of their vehicle. Analysis is per vehicle, not the driving behavior of individuals. demi books appointments only after dispatch confirms, orders to outside workshops only after fleet management releases them, and everything is logged.

  3. 3 · ActIntelligence Layer

    The agent translates every fault code into plain language using the manufacturer's documentation, tracks how often and in which combination it appears and compares that with the workshop history of the whole fleet. If it recognizes a pattern that used to come before breakdowns or expensive repairs, it rates the urgency by the workshop's rules. Then it looks for a gap in the route plan, checks workshop capacity and spare parts and proposes a slot, bundled with inspections that are due.

How it runs

  1. 1

    Every day demi reads fault codes, mileage and operating hours of all vehicles from telematics.

  2. 2

    The agent translates each code into plain language and compares it with workshop orders and breakdowns across the fleet.

  3. 3

    If patterns appear that used to come before failures, it rates the urgency by the workshop's rules.

  4. 4

    It looks for a gap in the route plan, checks workshop capacity and spare parts and proposes a slot.

  5. 5

    Dispatch confirms, and the workshop receives the order with codes, history and parts list.

What changes

  • Fewer breakdowns on the road and at the terminal

  • Workshop slots when the vehicle has little to do anyway

  • The workshop knows in advance what is coming and has the parts ready

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+108 hfreed per year

Assumptions and calculation

demi analyses fault codes and proposes a workshop slot in a gap between routes; dispatch confirms.

30 min → 21 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

60 fault alerts × 30 min × 30% × 1.0 (manual) × 12 months = 6,480 min = 108 h

Value per year, before demi costs

Freed per year+108 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$7,020

gained per year

108 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Does demi understand fault codes from different manufacturers?

Yes. Trucks mostly report codes to the J1939 standard; reach stackers, forklifts and construction machines often in the manufacturer's own format. demi translates them into plain language using the manuals and service bulletins you have. If a code is unknown, the agent shows it as it is and asks the workshop instead of guessing.

How does demi know which patterns come before a breakdown?

From your own history: the agent places fault codes next to workshop orders, breakdowns and towing cases of recent years and looks at what came before. Manufacturers' service bulletins are added. Every warning shows the earlier cases it rests on, and the workshop can sharpen or discard rules.

Does this also work for reach stackers, forklifts and construction machines?

Yes, for anything that reports fault codes and operating hours: trucks, vans, reach stackers, wheel loaders, excavators or sweepers. Vehicles without telematics come in through the workshop's diagnostic reader or through drivers' reports.

Who sets the workshop appointment?

Dispatch, together with the workshop. demi proposes the slot with its reasons: which trip is dropped or swapped, whether the parts are in stock and which inspections can be bundled. Only after confirmation is the slot in the calendar and the order with the workshop.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases