Fleet Utilization & Dispatch
Pool vehicle booking, driver shift/tachograph compliance, geofence route limits and fuel telemetry — with a real cross-group permit-validation integration.
What this group does
Fleet Utilization & Dispatch handles pool vehicle booking, driver shift/tachograph compliance, geofence route limits, and fuel telemetry reconciliation — the same 2-stage AI architecture as Preventive Maintenance (UI-wired Stage 1, non-persisted Stage 2), plus this group’s own distinguishing feature: Pool Vehicle Booking’s dispatch approval genuinely calls into the Vehicle Fleet & Specifications Setup group’s driver-permit validation — a real cross-group integration, not a documented limitation.
The shared 2-stage engine in this group
| Screen | What Stage 1 searches | What Stage 2 diagnoses | What you see in the result |
|---|---|---|---|
| Pool Vehicle Booking | Similar bookings across the ledger | Booking conflict & optimization risk | Whether an overlap conflict was detected, a description of the conflict, a vehicle idle-risk percentage, whether the mileage projection looks accurate, a suggested alternative vehicle, a priority reallocation recommendation, and a plain-language summary |
| Driver Shift & Tachograph | Similar shifts across the ledger | Tachograph infringement risk | A fine-risk rating (critical/high/medium/low), whether a mandatory rest stop is required, a list of fatigue indicators, the weekly-hours projection risk, a recommended action, and a summary |
| Geofence & Route Limits | Similar zones across the ledger | Corridor breach risk | Whether a route deviation was detected, a description of it, whether there is a prolonged-idle risk, whether a speed threshold was breached, whether route tampering is suspected, a recommended action, and a summary |
| Fuel Telemetry Audit | Similar audits across the ledger | Fuel theft & discrepancy risk | Whether fuel theft is suspected, a suspected drop location and time, a card-fraud-risk rating (critical/high/medium/low), whether engine inefficiency was detected, a recommended action, and a summary |
Same pattern as Preventive Maintenance: candidate pools are each screen’s own live ledger (minus the current record), Stage 1 always runs against the user’s local Ollama and never fails hard, Stage 2 routes through the selected AI engine and its result is never persisted to the record.
1. Pool Vehicle Booking
Purpose: Department-level reservations of company pool vehicles — start/end time, trip purpose, projected mileage.
Ledger columns
- Driver id/name, department, vehicle id/plate
- Start time, end time, trip purpose, projected mileage (km)
- Status — pending approval / confirmed / active trip / completed / conflict risk
Key action — the group’s real cross-group integration
Approve & Dispatch genuinely checks the driver’s permit status — the same check Driver License & Permits (Vehicle Fleet & Specifications Setup group) exposes. If the driver’s license, medical clearance, or permit documents are invalid, the booking is not confirmed and no key is issued — the screen shows the block reason instead; otherwise the booking moves to Confirmed. See Screen Workflows.
ID format: PBK-YYYY-XXXX.
2. Driver Shift & Tachograph
Purpose: Driver shift duration, continuous driving hours, rest status and speed violation count — a tachograph compliance ledger.
Ledger columns
- Driver name, driver card id, vehicle id/plate, shift start
- Continuous drive hours, rest status — on schedule / rest due / rest overdue
- Speed violation count, compliance grade — compliant / warning / infringement active
- Last violation type and notes
Key action
Flag Tachograph Infringement writes the violation type and notes to the record — violation types: continuous-drive overrun, missing rest break, speeding, weekly-hours overrun.
3. Geofence & Route Limits
Purpose: Geofence zones/route corridors — restricted vehicle type, max speed limit, active vehicles inside, and 24-hour breach count.
Ledger columns
- Zone name, restricted vehicle type (heavy truck / LCV / passenger pool / all)
- Max speed limit (km/h), active vehicles inside, 24h breach count
- Boundary status — active / maintenance bypass / alert level high
- Latitude, longitude, radius (meters)
Key action
Update Geofence Boundary updates the zone’s latitude, longitude, and radius.
ID format: GFN-YYYY-XXXX.
4. Fuel Telemetry Audit
Purpose: Reconciles fuel card transactions (card reference, purchase volume) against CAN-bus telemetry (recorded tank change, distance travelled) to detect fuel theft, card fraud or engine inefficiency.
Ledger columns
- Vehicle id/plate, fuel card reference, tank capacity (L)
- Refuel volume (L), CAN-bus recorded delta (L), distance travelled (km)
- Discrepancy status — balanced / minor variance / unexplained drop (fraud suspicious)
- Reconciliation notes
Key action
Reconcile Fuel Discrepancy updates the discrepancy status and reconciliation notes.
ID format: FLA-YYYY-XXXX.
Server routing (all 4 screens)
Same AI-engine routing as every other 2-stage screen in this add-on — Ollama, Local LLM, and Web LLM run entirely in the browser and never touch the server; Local CLI and API route through the server; every server call is logged and visible in Settings → Analytics.