Screen Workflows

The 16 screens aren’t 16 independent islands — several of them hand real data to each other, and some reach across into the core Fleet module or another add-on entirely. This page traces the major end-to-end flows that cross sub-group boundaries; for a per-screen feature breakdown, see the 4 sub-group pages linked below.

Telematics Fault

→

Work Order (auto)

→

Pool Booking Permit Check

→

Fuel Card Invoice Match

1. Telematics fault → auto-generated diagnostic work order

Telematics & IoT Config’s Trigger Telematics Alarm action picks a random fault code (P0300/P0420/P0128/P0171) and creates a genuine new work order in the Preventive Maintenance group’s shared work order ledger — priority Critical, status Scheduled, type Emergency Repair, titled “Diagnostic fault {code}”. This is the one real cross-group write inside the Vehicle Fleet & Specifications Setup group.

2. Driver permit validation → blocks pool booking dispatch

Driver License & Permits continuously tracks whether each driver is cleared to drive or blocked (medically disqualified or an expired document blocks them). Pool Vehicle Booking’s Approve & Dispatch action checks this for real: if the driver’s license, medical clearance, or professional driving certificate is invalid, the booking is not confirmed and no key is issued — the screen shows the block reason instead — a genuine cross-sub-group dependency, not a simulated one.

3. Fuel card audit → FinAudit invoice-matching ledger

Fuel Card Tariff Setup’s Audit Fuel Station Receipts action compares the card’s monthly spend against station invoice data and writes a real invoice-matching record into the FinAudit add-on’s own data — the only write in this module that crosses an add-on boundary rather than a sub-group boundary. The result today only surfaces via a toast (“matched”/“mismatch flagged”), since FinAudit’s own Invoice Matching Audit screen has not shipped yet to read it back.

4. Asset valuation sync — a known limitation

Vehicle Master Catalog’s Sync Asset Valuation action is a placeholder today: there is no dedicated fixed-asset registry screen yet elsewhere in the app for it to update, so once one ships this action is meant to push the vehicle’s valuation there instead of only touching the vehicle’s own mileage. Today it only rewrites the vehicle’s own mileage field; there is no live integration into another module yet.

5. Where each screen’s AI work happens

The 12 screens in the Preventive Maintenance, Fleet Utilization & Dispatch, and TCO & Asset Life groups all follow the same two-stage pattern described in Overview: a local-Ollama-only Stage 1 embedding search (a real, clickable button on every one of those screens) feeds a writerEngine-routed Stage 2 AI synthesis whose result renders only inside the diagnostic modal — it is never persisted to the record. Each screen’s own group page spells out its specific Stage 2 output shape and the separate action button that does produce a permanent effect.

Pages in this section

Frequently Asked Questions

Does a telematics alarm really create a work order, or is it simulated?

It’s real — a genuine work order is written to the shared work order ledger, visible immediately on Work Order Scheduler.

Can a booking be approved for a driver with an expired license?

No — Approve & Dispatch runs a real permit check; an expired or medically-disqualified driver blocks the dispatch and no key is issued.

Does the fuel receipt audit actually reach FinAudit, or is that just a toast message?

Both — a real invoice-matching record is written to FinAudit’s own data, and today the only visible feedback is a toast because FinAudit’s Invoice Matching Audit screen hasn’t shipped to display it yet. No retrofit will be needed once it does.

Does Sync Asset Valuation update a real fixed-asset ledger?

Not yet — there is no dedicated Fixed Asset Registry screen in this codebase, so it only re-writes the vehicle’s own mileage field today.

Automotive & Fleet Management Ops — Screen Workflows