Good morning, Sabine.
Workshop Chase
Every car out for repair or inspection, watched against the date the workshop quoted. Asks you first
Good morning, Sabine.
How can I help with your fleet?
Workflows
What Lanterne runs for you. Each one carries its own playbook, and you set how far it goes: advise, ask first, or run on its own.
Logbook
Every run and every decision, with its receipt. Click a row to see exactly what was read and what was done.
Analytics
What Lanterne is carrying for you. June, month to date.
End to end means no operator touch. Handle time runs from a case opening to its close, receipts included.
Integrations
Lanterne plugs into what you already run. Reads flow continuously; writes go through the same gates as everything else.
Bookings, vehicles, damage files and incoming tasks, read continuously over the CarMa API. Writes only ever go through your approval gates.
Lock state, ignition, fuel level and location. It's how a return gets verified, and how a refuelling claim gets checked against the tank.
The fleet sheet, the in-fleeting and out-fleeting lists, the filed check PDFs. Lanterne reads and updates the files you already keep, and never overwrites.
Workshop replies, forwarded EBuS tasks and customer mail land here and become runs on their own — each send and reply kept as a receipt.
Field workers just text. A blocked task opens a case with the vehicle and task-ID attached before they finish typing.
Every card transaction, matched to the booking window and the INVERS fuel-level change behind it. The ones that don't line up surface as cases.
Nothing to migrate and no API to build. Lanterne works the same screens your team does. The workshop portals and the licensing portal already run this way, and every click lands in the Logbook.
Bulk inspection booking
Asks you first
Mileage watch
Runs on its own
VDU-882 runs at 164% of plan. A station swap with TCP-514 would bring both back toward 100%.
The ID.3 sits at Hauptbahnhof Südseite, one of the busiest stations in the network, and has driven 24,540 km in 12 months against a 15,000 km line. TCP-514, the same class, sits at Offenbach Marktplatz at 84% of its plan. Swapping stations points the demand at the under-plan car. Existing bookings stay untouched; the swap applies from Friday.
Workflow details· step 3 of 4 in the watch
-
15 vehicles sit outside the 80–120% band. One is far enough out to be worth a proposal.Receipt · input data
- VDU-882
- 164% · 24,540 km in 12 months · line 15,000 km
- TCP-514
- 84% · same class · Offenbach Marktplatz
- Band
- 80–120% of plan
-
TCP-514: same class, 84%, free from Friday · suggested.KDS-112: a different class · JQL-140: an interior check is still open.
-
No car moves until you approve. The excess-mileage clock on VDU-882 keeps running at €0.09 per kilometre over.
-
On approval, two relocation tasks join the field team's round, and the watch keeps recomputing every night.
How Lanterne got here
Seven vehicles at four workshops need your decision. The other 19 were handled automatically.
Needs your decision· 7 vehicles at 4 workshops
- HLK-520
- workshop said 17:40 instead of 17:00 · next booking 19:00 · back in time, nothing to decide
- TVM-284
- workshop said 12:20 instead of 12:00 · next booking 14:30 · back in time, nothing to decide
Show 17 vehicles
- BRK-210
- Reifen Westhafen, North · back 09:30
- BRK-345
- Reifen Westhafen, North · back 10:15
- CLF-180
- Autohaus Hafenstraße, North · back 11:00
- CLF-567
- Autohaus Hafenstraße, North · back 13:30
- DTV-690
- EV Service Hauptbahnhof, Central · back 09:00
- DTV-742
- EV Service Hauptbahnhof, Central · back 14:45
- ETB-408
- Autohaus Bockenheim, Central · back 09:30
- ETB-092
- Autohaus Bockenheim, Central · back 10:30
- ETB-771
- Autohaus Bockenheim, Central · back 16:20
- FMK-817
- Autohaus Sachsenhausen, West · back 12:00
- FMK-654
- Autohaus Sachsenhausen, West · back 15:30
- GRS-031
- Autohaus am See, Wiesbaden · back 11:15
- GRS-988
- Autohaus am See, Wiesbaden · back 13:00
- GRS-604
- Autohaus am See, Wiesbaden · back 17:05
- HPL-276
- Grove Street Garage, East · back 10:45
- HPL-113
- Service-Center Adler, Offenbach · back 16:00
- HPL-360
- Service-Center Adler, Offenbach · back 09:45
Workshop emails· 4 drafts, 7 vehicles
Thank you for your time on the phone just now. To confirm what we agreed on PLW-118: the vehicle will be ready at 19:15 and we will collect it then. Please let us know if that time moves again.
Kind regards
Sabine Keller · Fleet operations
book-n-drive Mobilitätssysteme GmbH · Tel. 069 24 74 78-30
Thank you for your time on the phone just now. To confirm on TRC-206: the part is still on order and you will come back to us with a completion date as soon as you have one from your supplier.
Kind regards
Sabine Keller · Fleet operations
book-n-drive Mobilitätssysteme GmbH · Tel. 069 24 74 78-30
Thank you for your time on the phone just now. To confirm what we agreed, all three vehicles will be ready on Wednesday by 12:00:
GLN-411, PLW-244, CRF-901
Please let us know as soon as any of them is ready earlier.
Kind regards
Sabine Keller · Fleet operations
book-n-drive Mobilitätssysteme GmbH · Tel. 069 24 74 78-30
We tried to reach you by phone today about DGN-330 and DGN-577. Both are booked to customers tomorrow morning. Could you confirm whether they will be ready as planned?
Kind regards
Sabine Keller · Fleet operations
book-n-drive Mobilitätssysteme GmbH · Tel. 069 24 74 78-30
Workflow details· one run, four steps
-
One request per workshop covers every vehicle it holds, not one request per vehicle. The request asks whether each vehicle will be ready at the time it was booked in for and, if not, when.11:30: reminder sent to the three workshops that had not answered.
-
17 confirmed ready at the time they were booked in for. 2 came back late but still before their next booking, so Lanterne logged the new time and left everything else alone.7 could not be settled: one running late against a booking tonight, four staying overnight or longer, and two at a workshop that did not reply.
-
The rules settled everything a reply could settle on its own. What is left needs a person on the phone, so it stays with you.
-
After the calls, Lanterne drafts one email per workshop covering every vehicle, so what was agreed on the phone is on the record. A workshop holding three vehicles receives one message, not three.
Teach Lanterne something new
Fuel cards · DKV
Autonomous
Workshop monitoring
Asks you first
Checklists
Asks you first
112 inspection appointments, planned around every customer booking.
Task allocation
Asks you first
Today's plan across the fleet, ready for one review.
Workflow details· one run, four steps
-
Cleaning intervals, charging and telematics from INVERS, and damage and complaint tasks, combined into one list per field agent.
-
Each field agent gets one round, ordered by drive time. Time-critical charging targets and complaints come first; cleanings follow by interval.Receipt · assignment
- Grouping
- By sub-area · each field agent clears one area before the next, not a performance rating
- Priority
- Areas weighted by station value and open-task count
- Availability
- Live from EBuS · book in one click on the agent's own login
- Balancing
- Where an area has two field agents, load is levelled
-
Items that need a decision are flagged. The remaining plan takes five minutes to review instead of an hour to assemble.
-
Each field agent receives the round on their phone. Lanterne processes the EBuS task-completed notifications and resets the relevant intervals, so the same task is not raised twice.
Every checklist submitted overnight, written into EBuS and filed to SharePoint.
Twelve field agents submitted 31 checklists between 05:40 and 06:50, covering interior checks, cleaning and handovers. Every one matched the EBuS entry form on the first attempt, with the required fields, photos and car record present.
DKV issue detected for MZR-806
Lanterne reads every DKV transaction and matches it to the EBuS booking window and the INVERS fuel level behind it. This week, 40 of 41 lined up. This one it held: 42.7 litres billed to MZR-806's card at 21:14, when the booking had ended at 19:40 and the tank sat flat at 63% all evening. Lanterne assembles the evidence and drafts the ticket; no case reaches billing without a person confirming it.
- DKV line
- 42.7 L · €81.13 · 21:14
- Booking window
- ended 19:40 · next 08:10
- Fuel level
- 63%, unchanged 18:00–00:00
- Verdict
- Suspected misuse · your call
How Lanterne got here
- Every card transaction parsed into date, time, litres, amount and station.
- 40 transactions sat inside an active booking with a matching rise in fuel level.This one had neither: no active booking at 21:14, and no change in the tank.
- Lanterne flags and assembles; a person checks plausibility. Confirming sends the ticket to billing, releasing logs the decision and keeps the evidence.
- After your decision, the ticket goes to billing to handle, or the flag is released — and the outcome, time and evidence stay on the vehicle record.
Fleet Ledger
The commercial record of every vehicle, kept current by the workflows. Every value can show where it came from. Flags, never decides
| Vehicle | Status | Mileage index | Term left | Residual vs gate | Last confirmed |
|---|
VDU-882 · VW ID.3
Exceptions
Everything the ledger is not sure about, with the evidence attached. Nothing is overwritten silently.