Preventive Maintenance & Service Ops
Work order scheduling, parts inventory linkage, inspection checklists and tire lifecycle — the group with a UI-wired 2-stage AI diagnostic on every screen.
What this group does
Preventive Maintenance & Service Ops schedules work, links parts inventory to it, runs driver safety inspections, and tracks tire wear — all 4 screens use the add-on’s 2-stage AI diagnostic pattern (see Overview), and on every one of them Stage 1 is a real, working “Search …” button in the record’s modal, not embedded-but-unwired code.
The shared 2-stage engine in this group
| Screen | What Stage 1 Compares Against | What Stage 2 Diagnoses | What You See in the Result |
|---|---|---|---|
| Work Order Scheduler | Other maintenance rules and work orders on the same screen | Runs the work order audit | Whether the job meets its SLA, an overdue-risk rating (critical/high/medium/low), recurring-component risk, whether a schedule conflict was detected, the recommended technician skill, an estimated cost range, and a summary |
| Parts Inventory Link | Other parts and compatibility records on the same screen | Runs the parts inventory audit | A stockout-risk rating (critical/high/medium/low), the impact of active reservations, suggested alternative parts, an estimated reorder lead time, a recommended reorder quantity, and a summary |
| Inspection Checklist | Other inspection standards and checklists on the same screen | Runs the inspection audit | Whether the vehicle is at out-of-service risk, a list of critical safety defects, a severity grade, DOT compliance status, a recommended action, and a summary |
| Tire Lifecycle Tracker | Other tire telemetry records on the same screen | Runs the tire lifecycle audit | The wear rate (mm per 1,000 km), a predicted replacement distance, whether an alignment anomaly was detected, a description of that anomaly, a recommended action, and a summary |
All 4 screens’ Stage 1 search compares the current record against every other live record on the same screen — there is no static reference corpus (e.g. an OEM service bulletin library); the candidate pool is the screen’s own ledger. All 4 use the same underlying similarity-search logic and route to the user’s local Ollama only. Stage 2 result is rendered in the modal and is never saved to the record — permanent effects come from a separate action button (see below).
1. Work Order Scheduler
Purpose: Vehicle-linked maintenance/repair work orders (Scheduled PM, Emergency Repair, Recall Service) by scheduled date, assigned workshop/technician, estimated cost and status.
Ledger columns
- Vehicle id/plate/VIN, title, description
- Maintenance type — scheduled PM / emergency repair / recall service
- Scheduled date, assigned workshop, estimated cost, priority (low–critical)
- Status — scheduled / in progress / on hold / completed (plus legacy
open, kept for backward compatibility and rendered identically toscheduled) - Source device and fault code — populated when the work order was auto-created by Telematics & IoT Config’s alarm trigger
Key actions
Standard create/edit/delete, plus the 2-stage diagnostic modal above. There is no separate persistent action beyond editing status/fields directly.
ID format: WO-YYYY-XXXX. Saved automatically to the server.
2. Parts Inventory Link
Purpose: Allocates spare parts inventory against open work orders — SKU, compatible vehicle models, stock qty, reorder point and allocation status.
Ledger columns
- Part SKU, description, compatible vehicle models
- In-stock qty, reorder point, unit cost
- Allocation status — reserved for WO / in stock / backordered, reserved work order id
ID format: PRT-YYYY-XXXX. Saved automatically to the server.
3. Inspection Checklist
Purpose: Driver safety inspections (Pre-Trip DVIR, Post-Trip, Annual Safety) by failed item count, severity grade and audit status.
Ledger columns
- Vehicle id/plate/VIN, inspector name, inspection type, inspection date
- Failed item count and description
- Severity grade — pass / minor defect / out-of-service risk
- Audit status — approved / work order triggered, triggered work order id
ID format: INS-YYYY-XXXX. Saved automatically to the server.
4. Tire Lifecycle Tracker
Purpose: Per-vehicle, per-axle-position (front-left, front-right, 4 distinct rear positions, spare) tread depth, cumulative distance and pressure telemetry.
Ledger columns
- Vehicle id/plate, axle position, DOT serial code
- Tread depth (mm), total distance (km), pressure (psi)
- Status — good / rotation due / immediate replacement
ID format: TIR-YYYY-XXXX. Saved automatically to the server.
Server routing (all 4 screens)
Stage 2 for all 4 screens routes through whichever AI engine you’ve selected in Settings → Agentic. When Ollama, Local LLM or Web LLM is selected, the analysis runs entirely on your machine or in your browser and never reaches the server — the Render server has no network path to a user’s own Ollama instance. With Local CLI or API selected, the server handles the analysis instead, calling the Anthropic or Cohere API depending on the selected mode. Every server call is logged (duration, model, success/failure, screen name), visible in Settings → Analytics.
Why the routing check matters
Skipping this check and always calling the server would produce a nonsense error whenever a user has selected Ollama — the server cannot reach a user’s own machine.
Pages in this section
Frequently Asked Questions
open work order status mean?scheduled/in_progress/on_hold/completed set (Telematics & IoT Config’s alarm trigger used to create work orders with this status) and is kept for backward compatibility — the UI renders it identically to scheduled.