TotalApp Docs

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.

Pool Vehicle Booking
→
Driver Shift & Tachograph
→
Geofence & Route Limits
→
Fuel Telemetry Audit

Screen preview

A quick look at the screen. Use the toggle in the corner to switch between the dark and light themes.

app.totalapp.app/fleetops/pool-vehicle-booking
PBK-2026-0141 — 34-TR-1281
A. Young — Logistics dept — 214 km
Confirmed
PBK-2026-0142 — 06-AF-9042
M. Davis — Sales dept — 88 km
Permit Block
PBK-2026-0143 — 35-LC-5521
S. Kelly — Field Ops — 412 km
Pending Approval
GFN-2026-0006 — Port Corridor
Max 70 km/h — 2 breaches / 24h
Monitoring

Pool vehicle booking with permit checks and geofence limits

The shared 2-stage engine in this group

ScreenWhat Stage 1 searchesWhat Stage 2 diagnosesWhat you see in the result
Pool Vehicle BookingSimilar bookings across the ledgerBooking conflict & optimization riskWhether 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 & TachographSimilar shifts across the ledgerTachograph infringement riskA 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 LimitsSimilar zones across the ledgerCorridor breach riskWhether 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 AuditSimilar audits across the ledgerFuel theft & discrepancy riskWhether 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; the hosted API routes through the server; every server call is logged and visible in Settings → Analytics.

Embedded AI Assistant

Every screen in this group has an embedded AI Assistant panel docked to the right edge. Tick one or more rows in the ledger and the panel lists them under Selected, with Analyze and Summarize shortcuts that send those records to the assistant by id and key fields. With no selection it works on the whole ledger. The ledgers are also paginated, with the page size adapting to your screen height.

ScreenExample suggestions
Pool Vehicle BookingFlag overlapping bookings for a vehicle; list bookings with no trip purpose
Driver Shift & TachographFlag shifts exceeding continuous drive limits; list drivers with repeated speed violations
Geofence & Route LimitsFlag zones with frequent breaches; list zones with no speed limit set
Fuel Telemetry AuditFlag refuels above tank capacity; list open discrepancies without notes
  • Save as Report stores an assistant answer in the reports list so it can be reopened later.
  • Add Knowledge attaches your own reference text so the assistant answers with it as additional context.
  • The assistant follows the engine you selected in Settings → Agentic. With Ollama, Local LLM or Web LLM it runs on your machine or in your browser and never reaches the server. Panel width, font size, accent color and whether it opens automatically are controlled in Settings → AI Assistant.

Frequently Asked Questions

What happens if I try to approve a pool booking for a driver with an expired license?
The booking is not confirmed — Approve & Dispatch runs a real permit check, and an invalid document set blocks the dispatch with a reason shown on screen.
Is this the same permit check as Driver License & Permits’ own “Block Uncertified Driver Dispatch” button?
Yes — both run the identical permit check. On Driver License & Permits it’s a standalone preview action; here it’s wired into a real dispatch decision.
Does Update Geofence Boundary support drawing a shape on a map?
No — it takes latitude/longitude/radius values (a circular geofence), not an arbitrary polygon editor.
What makes a fuel discrepancy “fraud suspicious” vs. “minor variance”?
That classification is set by whoever reconciles the record via Reconcile Fuel Discrepancy — it is not auto-computed from the raw refuel/CAN-bus delta; the Stage 2 AI diagnostic can suggest a fraud risk level, but setting the final discrepancy status is a manual reconciliation step.