Fleet Ops Agent
Fleet Ops Agent autonomously tracks driver permits, tachograph data, and the periodic maintenance calendar for a vehicle fleet.
What Is the Fleet Ops Agent?
Fleet Ops Agent is the specialist behind the fleet screens in Fleet Operations — it tracks driver permits, reads tachograph data and keeps the periodic maintenance calendar, flagging what is about to expire or fall due.
- Driver Permits — No driver on the road with an expired permit
- Tachograph — Driving and rest time read from the data
- Maintenance — Service scheduled before the breakdown, not after
In one sentence
Permit tracking, tachograph checks and a maintenance calendar that watches itself — one specialist behind the fleet screens in Fleet Operations.
How the Agent Builds Its Context
Every screen in Fleet Operations follows the same two-step approach, and Fleet Ops Agent always provides the second step:
| Step | What it does |
|---|---|
| Step 1 | Searches the tenant's own live records for the ones relevant to the item being reviewed, entirely on the user's own device. |
| Step 2 | Takes the most relevant matches and reasons over them the way a specialist in that field would, producing the structured finding the screen displays. |
The candidate pool is always the tenant's own records
Fleet Ops Agent works with the records already on file for the tenant rather than an external archive, so every finding can be traced back to something the team can open and verify.
What Fleet Ops Agent Checks
Each area below is backed by its own dedicated reasoning, grounded in the same kind of records a specialist reviews every day:
| Area | Check | What it looks at |
|---|---|---|
| Driver Permits | License and SRC | expiry dates tracked |
| Medical certificates | renewal reminders | |
| Training records | required courses current | |
| Assignment check | only valid drivers assigned | |
| Tachograph | Driving time | daily and weekly limits |
| Rest periods | breaks and daily rest | |
| Download gaps | data not downloaded in time | |
| Early warnings | before a limit is reached | |
| Maintenance | Service intervals | by mileage and date |
| Inspections | statutory dates tracked | |
| Workshop booking | slots proposed | |
| Owner hand-back | tasks go to the fleet manager |
AI diagnostics registered for Fleet Operations
Every AI check in Fleet Operations is registered as its own agent with a stable id, a prompt, an expected result shape and, where it applies, the reference documents it may read. Twelve are registered today — one per screen below. The id appears in the analytics log, so you can tell which diagnostic produced a given run.
| Screen | Agent id | What it assesses | Mode |
|---|---|---|---|
| Work Order Scheduler | fleet-ops.work-order-audit | SLA compliance, overdue-risk rating, recurring-component risk, schedule conflict, technician skill, cost range | Single-step |
| Parts Inventory Link | fleet-ops.parts-inventory-audit | Stockout-risk rating, impact of active reservations, alternative parts, reorder lead time and quantity | Single-step |
| Inspection Checklist | fleet-ops.inspection-audit | Out-of-service risk, critical safety defects, severity grade, DOT compliance status | Single-step |
| Tire Lifecycle Tracker | fleet-ops.tire-lifecycle-audit | Wear rate, distance to replacement, alignment or irregular-wear anomaly — reads the tire wear standards itself | Multi-step |
| Pool Vehicle Booking | fleet-ops.pool-booking-audit | Booking overlap, vehicle idle risk, mileage plausibility, alternative vehicle, priority reallocation | Single-step |
| Driver Shift & Tachograph | fleet-ops.tachograph-audit | Fine-risk level, mandatory rest stop, fatigue indicators, weekly-hours projection | Single-step |
| Geofence & Route Limits | fleet-ops.geofence-audit | Route deviation, prolonged idling, speed-limit breach, suspected route tampering | Single-step |
| Fuel Telemetry Audit | fleet-ops.fuel-audit | Suspected fuel theft and where/when, fuel-card fraud risk, engine inefficiency | Single-step |
| Vehicle Depreciation & TCO | fleet-ops.vehicle-tco-audit | TCO spike, economic tipping point, projected replacement date | Single-step |
| Insurance Claims & Accident | fleet-ops.insurance-claim-audit | Disputed fault assignment, subrogation recovery opportunity, deductible loss mitigation | Single-step |
| Lease Contract Fleet | fleet-ops.lease-contract-audit | Projected excess-mileage fee, early-termination penalty, buyout recommendation | Single-step |
| Asset Decommission | fleet-ops.asset-decommission-audit | End-of-life readiness, best disposal route and yield comparison, environmental certificate risk | Single-step |
Single-step diagnostics send one request to the AI model and show its answer. The multi-step diagnostic (Tire Lifecycle) can first read a reference document — the tire wear standards — and then answer, so its thresholds come from the standard instead of from the request.
Multi-step behavior applies only when the AI engine selected in Settings → Agentic is handled by the server (Cloud LLM or Local LLM). With Ollama or an in-browser model, every diagnostic runs as a single request on your own machine.
Where Fleet Ops Agent Fits
Fleet Ops Agent has no ledger of its own — every record lives in the add-on's own tenant-scoped store. Its job is strictly the reasoning step: given the context a screen already assembled, produce a structured judgment and hand it back to the person responsible for that record.
A reasoning layer, not a data layer
Fleet Ops Agent never reads or writes stored records directly — it receives the context the calling screen assembled, reasons over it and returns a result. Saving that result and any follow-up action remain the screen's responsibility, and every finding is handed back to a person rather than acted on automatically.