Automotive & Fleet Management Ops — Overview
What the add-on is, its 4 sub-groups, who uses it, and the two-stage hybrid AI engine pattern used across the module.
Module Overview
The Automotive & Fleet Management Ops add-on — package id fleetops, domain AUTOFLEET — covers the full operational lifecycle of a commercial vehicle fleet: cataloguing vehicles and telematics hardware, tracking driver licenses/permits across jurisdictions, scheduling preventive maintenance, dispatching pool vehicles, auditing fuel telemetry, and tracking total cost of ownership through to asset decommission.
At a glance
- Domain: AUTOFLEET
- URL prefix:
/fleetops/… - Governance screens: Roles, Fleet & Maintenance Staff (staff master)
- 16 operational screens across 4 sub-groups (see below)
- Default roles: Chief Fleet & Maintenance Manager, Fleet Setup Coordinator, Maintenance Supervisor, Dispatch & Utilization Analyst, Fleet Asset & Insurance Officer
The 4 sub-groups
The add-on’s 16 operational screens are organised into four titled sub-groups, on top of the standard Administration & Access group (Roles, Staff).
| Group | Screens |
|---|---|
| Vehicle Fleet & Specifications Setup | Vehicle Master Catalog, Telematics & IoT Config, Driver License & Permits, Fuel Card Tariff Setup |
| Preventive Maintenance & Service Ops | Work Order Scheduler, Parts Inventory Link, Inspection Checklist, Tire Lifecycle Tracker |
| Fleet Utilization & Dispatch | Pool Vehicle Booking, Driver Shift & Tachograph, Geofence & Route Limits, Fuel Telemetry Audit |
| Total Cost of Ownership & Asset Life | Vehicle Depreciation & TCO, Insurance Claims & Accident, Lease Contract Fleet, Asset Decommission |
See Vehicle Fleet & Specifications Setup, Preventive Maintenance & Service Ops, Fleet Utilization & Dispatch and Total Cost of Ownership & Asset Life for the per-screen breakdown of each group.
Who uses it
Automotive & Fleet Management Ops targets fleet managers, maintenance supervisors, dispatchers and asset/insurance officers — the people who keep a commercial vehicle fleet compliant, serviceable and cost-efficient. A tenant activates the fleetops package, then assigns each team member one of the five default roles (or a custom role built from the same capability catalog) as a domain “hat” — see Roles & Capabilities.
Key concepts
Vehicle & telematics catalog
Vehicle Master Catalog shares the core Fleet module’s own vehicle record (read/write, not a separate data set) and layers fleet classification on top; Telematics & IoT Config tracks the OBD-II/CAN bus/BLE devices paired to those vehicles and can auto-open a diagnostic work order on a critical fault code.
Jurisdiction-aware driver permits
Driver License & Permits is the one screen in the Setup group that varies its form fields by country — TR (SRC/Psikoteknik/TÜVTÜRK), US (CDL/DOT), EU-14 (Driver CPC/Tachograph) or a generic Default — using a Strategy Pattern schema engine, the same architecture as ComplianceEngine/CustomsEngine, not the 2-stage AI pattern.
2-stage AI diagnostic (12 of 16 screens)
Every screen in the Maintenance, Utilization & Dispatch, and TCO & Asset Life groups runs a UI-driven Stage 1 similarity search followed by a Stage 2 AI analysis routed through your selected AI engine — see below.
Real cross-screen writes
A critical telematics fault auto-creates a work order; a pool booking approval calls the same permit-validation function Driver License & Permits exposes; a fuel card audit writes a real record into FinAudit’s invoice-matching ledger.
Financial metrics (TCO group)
Vehicle Depreciation & TCO, Insurance Claims & Accident, Lease Contract Fleet and Asset Decommission are the only screens whose gauge bars are monetary formulas — cost-per-km, recovery ratio, mileage consumption, retirement pipeline.
Non-AI CRUD (4 screens)
Vehicle Master Catalog, Telematics & IoT Config and Fuel Card Tariff Setup are plain CRUD tables with no embedding/AI step — only Driver License & Permits in that group uses the jurisdiction schema engine.
The two-stage hybrid engine (12 of 16 screens)
Every screen in the Preventive Maintenance, Fleet Utilization & Dispatch, and Total Cost of Ownership & Asset Life groups follows the same two-stage pattern — and, unlike some other add-ons, Stage 1 is a real, clickable button in the UI on every one of these 12 screens, not embedded-but-unwired code:
| Stage | What it does | Where it runs |
|---|---|---|
| Stage 1 — Similarity Search | User clicks a “Search …” button in the record’s 2-Stage AI Diagnostic modal. Compares the record’s text against every other live record on that same screen (there is no static reference corpus — the candidate pool is the screen’s own ledger, minus the current record) and ranks the closest matches (up to 5, above a minimum similarity threshold). | Always runs through the user’s own local Ollama instance — never proxies through the server. Never crashes; if Ollama isn’t configured or the search fails, it returns no matches and the UI shows a plain warning instead of an error. |
| Stage 2 — AI Synthesis | Takes the user-selected Stage 1 matches (checkboxes, all selected by default — or skips Stage 1 entirely and sends the whole ledger as context) and reasons over them, producing a structured result (risk levels, recommended actions, a summary) rendered as cards/badges in the modal. | Routes through whichever engine the user picked in Settings → Agentic (Ollama / Local LLM / Web LLM stay on the user’s machine or browser; Local CLI / API route through the server, and every server call is logged). |
Stage 2 result is never persisted
Unlike some other add-ons, the Stage 2 JSON in this module is never written back to the record — it renders only inside the diagnostic modal and disappears when the modal closes. Any permanent effect (dispatching a work order, reserving parts, flagging a violation) comes from a separate, independent action button — see each group page’s per-screen action tables.
Terminal Screen Style (Settings → Appearance) is supported across all 16 screens via fc-terminal-optin.
Pages in this section
Frequently Asked Questions
fleetops package activated, and your user must hold an AUTOFLEET domain role. See Roles & Capabilities.