
Where Predictive maintenance fits
03 Dispatch + 04 Route is the operating context.
This page should not feel like an isolated feature sheet. It belongs to a role, a stage, a control, and an outcome in the Haultro operating spine.
The challenge
- ! Preventive intervals slip when they live on a whiteboard.
- ! Fault codes fail to reach the shop with the truck context intact.
- ! Parts, labor, and downtime history is separated from the repair.
- ! Dispatch cannot see the operating state maintained by the shop.
- ! Prediction claims become unsafe when they are not tied to recorded evidence and a model version.
What it does
- ✓ Schedule preventive maintenance by configured calendar, mileage, or engine-hour evidence.
- ✓ Create and manage work orders with priority, assignment, due date, proof, and completion notes.
- ✓ Record technician labor and consumed parts against the exact work order.
- ✓ Track outage, restoration due date, SLA state, and downtime.
- ✓ Ingest accepted diagnostic fault records and compute rule-versioned truck risk predictions.
- ✓ Preserve asset inspection and maintenance history for review.
Inside the module
What your team can work with.
Predictive maintenance · Connected to the work on the groundBuilt for the shop floor
From recorded fault to closed work order
A fault or failed inspection remains attributable to its source. The shop can create work, assign it, record the parts and labor, preserve proof, and close the outage without inventing warranty, recall, or failure-rate data.
Accepted fault-code intake with truck and severity context
Work-order priority, schedule, technician, and skills
Parts, labor, notes, proof, and completion actor
Downtime and restoration evidence
Connected across the platform
One source of truth.
Fleet telematics
Accepted fault, odometer, and engine-hour records become attributed maintenance evidence.
Routing & dispatch
Dispatch uses the truck's recorded availability and service state; the current contract does not claim automatic route removal.
Asset tracking
Plans, inspections, and work orders stay connected to the specific registry asset.
Analytics
Recorded labor, parts, work-order, and downtime totals feed current financial and operational reporting.
How it works
Adopting predictive maintenance.
Create the plan
Define the maintenance interval and next due evidence for the registry asset.
Open the work
Create a work order from a plan, inspection, accepted fault, or authorized manual action.
Record the repair
Assign a technician and capture labor, parts, downtime, notes, proof, and events.
Close and review
Complete the work with an actor and timestamp, then review the preserved history and rule-versioned prediction evidence.
Standards & compliance
Built in, not bolted on.
FAQ
Questions, answered.
Do I need new hardware?
No hardware is required for calendar-based plans or manual shop records. Mileage, engine-hour, and fault-driven evidence requires an accepted data source.
Can it track preventive plans and inspections together?
Yes. Registry assets can carry maintenance plans, inspections can create or link work orders, and due or overdue states are visible in the maintenance workspace.
Does it predict every part failure?
No. Current predictions are rule-versioned and evidence-bounded. Haultro does not claim universal part-failure prediction, warranty or recall automation, or a certified maintenance outcome.
Does maintenance automatically remove a truck from dispatch?
No. The shop records asset and truck service state for dispatch review; automatic route removal is not part of the current production contract.
Does it calculate MTBF or cost per mile and engine hour?
Not in the current reporting contract. Haultro records parts, labor, work orders, downtime, mileage, and engine hours, but it does not advertise derived MTBF or normalized maintenance-cost analytics until those calculations are shipped and tested.
Get started
See predictive maintenance on your routes.
We'll tailor a demo to your fleet and the business you run.