Uptime, by yard day-window— built for postal, municipal, and state fleet operators.
Predictive intelligence for USPS-scale postal, city municipal, and state-fleet operators: lead time sized to the yard-day window, no upfront capex, and the 17% Trodeon success fee settled only on confirmed completed repairs.
What runs under the hood
Three things an essential-service fleet actually gets.
Predictive alerts days ahead
A component degradation curve surfaces hours to days before the rig parks itself, so the yard supervisor can route the dispatch inside the same week the failure mode appears — not the morning the route goes dead.
Certified mobile mechanics
A vetted tech from the dispatch network rolls to the rig — yard, depot, lot — parts-loaded for the predicted job, so the repair closes inside the forecast window the procurement boundary pays against.
Single monthly invoice
The per-truck SaaS line and the 17% success-fee settlement roll up into one monthly invoice per yard, so procurement trails both numbers against the same budget cycle and ops audits one downtime ledger.
Operator vignette
USPS-scale postal fleet
A postal district runs NGDV-class routes that cannot slip — a missed turn strands a route carrier at the curb and pulls the dispatch board apart for the rest of the day. The forecast keeps the route on the mail by surfacing the degradation curve hours to days before the rig would park itself, so the yard has the lead time to dispatch a cert-certified tech with the part already loaded.
Across a postal district the same statement of work covers every yard it touches — one fleet, one procurement boundary, one monthly settlement read against the same downtime ledger ops is already running on.
Operator vignette
City municipal fleet
A city municipal yard runs refuse, transit, and public-works rigs on day-windows the budget cycle does not bend to — a school bell, a refuse route, a transit block, a paving shift. The forecast sizes the lead time to that day-window, so the dispatched mobile tech closes the repair before the rig re-enters revenue service and the schedule absorbs the slip as a service complaint instead of a work order.
Across a multi-yard municipal fleet the same per-truck line and the same 17% settlement apply yard-by-yard under one procurement statement — one invoice, one downtime ledger, one settlement the budget office can trail against an existing vehicle.
Per-truck tiers
The right tier lives one click away.
1–9 trucks
Solo Fleet
See pricing →$189
per truck · per month
10–49 trucks
Regional Operator
See pricing →$109
per truck · per month
50+ trucks
Enterprise
See pricing →$98.10
per truck · per month
The same 17% success fee sits underneath every tier, settled only on confirmed repairs. The full per-truck math runs at /pricing.
Telemetry → dispatched tech
From a sensor reading to a wrench on the rig.
The path the forecast runs — from the moment Trodeon (or the existing telematics feed on /integrations) flags a component anomaly, to the moment the dispatched tech closes the work order. The mobile mechanic network that closes the loop is open to public-sector yards and is browsable at /mechanics.
1. Component anomaly surfaces
A Trodeon sensor or the existing telematics feed flags a degradation curve on a single rig.
2. Forecast lead time assigned
The model assigns a component-specific lead time — hours to days, sized to the failure mode and the yard's day-window.
3. Yard dispatches the tech
The yard supervisor receives the alert with the lead time, the registry, and the parts the mobile tech should arrive with.
4. Mobile tech arrives on-site
A certified tech from the dispatch network rolls to the rig — yard, depot, lot — with parts already loaded for the predicted job.
5. Repair confirmed, fee settled
The tech closes the work order against the forecast; Trodeon settles the 17% success fee only on this confirmed completion.
Buying-committee research
Two analysts. Two starting points.
The procurement analyst opens at /integrations — how Trodeon reads the existing telematics feed, what the OEM and right-to-repair posture looks like, and which procurement vehicles the rollout can ship against.
The operations analyst opens at /roi — what an avoided breakdown is worth against the per-truck tier and where the 17% success fee sits inside the budget cycle the yard already runs on.
Procurement fit
No upfront capex. A 17% fee, settled only on outcomes.
Public-sector procurement doesn’t have to commit capex to stand Trodeon up. Per-truck SaaS runs at the tier your fleet size lands in — $189, $109, or $98.10 per truck per month — and the same 17% success fee sits underneath every tier, settled only on completed repairs dispatched through Trodeon.
Scope a defined-window pilot against a single yard first — the success fee math doesn’t kick in until the pilot closes and the per-truck tier is in place. The pilot agreement spills out into a multi-yard statement of work with a single settlement across yards, so procurement trails one number against the budget cycle the operator is already running on.
Run a defined-window pilot
Stand Trodeon up across your yards — before any per-truck commitment.
A real-rig pilot, bounded by start and end dates, with the 17% success-fee settlement documented up front. Procurement can trail it against a current vehicle; ops gets the downtime metric the pilot agreement names.
Or research-first: /integrations for procurement systems questions, and /roi for the avoided-downtime math.