The autonomous service layer that solves the first visit — before anyone rolls out.
AEDIL condenses the entirety of your service data — history, repair reports, technician notes, fault codes, parts, telematics, manuals, site data — into the finished decision: root cause, exact part, fix path. Telematics is one signal among many. The technician rolls out prepared. The first time.
The first visit doesn't fail at dispatch — it fails at diagnosis.
Dispatch decides who drives out. It doesn't decide whether the first visit fixes the machine. That's settled earlier — at diagnosis. And right there, before departure, the answer is missing today. Every single time.
The answer has long been sitting in the customer's systems — in the entirety of your service data: history, repair reports, technician notes, fault codes, parts and materials data, telematics, manuals and bulletins, customer and site data. Telematics is one signal among many. It just gets pulled together too late: in one person's head at a desk, long after the truck has rolled. You drive on a guess. The wasted second van is the price you pay.
Not a deck — hard numbers on real machines.
A decision that reasons — and answers when you ask.
A machine signal fires. AEDIL pulls together every piece of your service data on its own — service history, repair reports, technician notes, fault codes, parts, telematics, manuals, location data — and condenses your entire service-data memory into a finished dispatch decision. Live in the AEDIL web app, queryable anytime. Telematics is one signal among many — not one sensor, the whole picture.
AEDIL does not pick the technician · 88% diagnostic precision on real machines
The obvious sensor was wrong. AEDIL found the real root cause.
An anonymized case from Phase 1. The obvious sensor was already swapped — the steering faults stayed. AEDIL ranked the non-obvious causes · with confidence and historical evidence. The real fault sat right at the top.
Real case, Phase 1 · customer and asset anonymized · error codes and cause ranking verbatim from the pilot
A layer over your stack — no rip-and-replace.
The Enterprise Adapter reads the entirety of your service data across every system you already run — ERP, FSM, CRM, telematics, knowledge base — not just one source, and lays the diagnosis layer on top. No migration. No second database. Live in weeks, not quarters.
AEDIL extends your systems — it replaces nothing. The adapter sits between the agents and your ecosystem, reads the entire service-data landscape and translates both ways.
One engine, multiple entry points — the lead grows with every job.
One engine, from machine signal to diagnostic decision. It runs live in three places today and gets more autonomous with every deployment. Multiple entry points, one data lead.
The same engine, more autonomous stage by stage. This is the roadmap — here's where the engine lands next.
Diagnosis is the bridgehead.
Today AEDIL nails the first visit — before anyone rolls out. That's only the start. On the diagnosis layer grows the autonomous service layer: it doesn't recommend. It acts.
Two minutes. From one machine signal to a dispatch-ready decision — root cause, exact part, the fix.
- 88%Diagnostic precision — the right root cause, on the first pass.
- 81%Top-3 spare part — the right part among the first three.
- >90%Risk detection — the failure flags itself before a ticket even exists.
- AutoPart ordered, written back into the system — no hands on the desk.
- SelfEnd-customer self-diagnosis, before service even kicks off.
- FlowEvery visit sharpens the next prediction — the flywheel turns.
Service is where the lead is decided now. We win the decision where it's made — before the visit.