Revenue per rig, by lane— built for Class-8 carrier and 500+ rig private-fleet operators.
Pilot evaluation for the long-haul fleet: existing telematics reviewed against a defined scope, declared field-partner coverage checked against the service area, and a candidate alert-to-service workflow that is not automatic, plus the canonical Trodeon sales path on /fleet-pilot — $150 capped Coordination Fee plus 30 days of premium diagnostic access, held off per-truck fees until pilot close.
What runs under the hood
Three things a multi-yard carrier actually gets.
Clear written scope across yards
A defined pilot scope can cover selected terminals under one written operating brief, so AP and operations work from the same window, fleet boundary, and measurement plan instead of separate yard-by-yard requests.
Reads the existing ELD + J1939 telemetry
The signal review reads the ELD / J1939 feed the carrier already runs on /integrations and writes alerts back into the TMS dispatch console — no parallel data workflow for the dispatcher to triage.
ROI proof on /roi
The avoided-downtime math lives on /roi — useful before a pilot conversation starts and again at sign-off, while any later fleet or per-truck scope is agreed from the pilot evidence rather than priced here.
Illustrative operator vignette
Illustrative scenario · national carrier — multi-terminal fleet
Illustrative scenario: a national carrier could use a defined pilot to compare available telemetry with a multi-terminal lane schedule. Any lead window, mechanic coordination, repair timing, or avoided missed turn would need to be observed and documented rather than assumed.
Across a multi-terminal national fleet, the same $150 capped Coordination Fee and 30-day premium diagnostic access window sit inside one written pilot scope — every yard measures against the same downtime ledger the carrier ops team already tracks.
Illustrative operator vignette
Illustrative scenario · large private fleet
Illustrative scenario: a private fleet could evaluate its existing ELD / J1939 stream against internal lanes and record whether a candidate signal changes a maintenance decision. The pilot would not assume a dispatch action, mechanic, or service outcome.
A 500+ rig private fleet can start with the same $150 capped Coordination Fee and 30-day premium diagnostic access window, then use the pilot evidence to decide whether any broader scope belongs in the next operating plan.
Canonical offer
Start with one defined-window fleet pilot.
The approved customer-facing offer is a $150 capped Coordination Fee plus 30 days of premium diagnostic access through a defined fleet pilot. Any later per-truck or service scope is agreed after the pilot and is not priced on this page.
Telemetry → dispatched tech
From a sensor reading to a wrench on the rig.
The path the signal review runs — from the moment Trodeon (or the existing telematics feed on /integrations) flags a component anomaly, to the point where a human reviews the evidence and decides whether a service scope is appropriate. The mobile mechanic network that closes the loop is open to carrier terminals and is browsable at /mechanics/directory.
1. Component anomaly surfaces
A Trodeon sensor — or the existing ELD / J1939 feed on /integrations — surfaces a signal for review on a single rig.
2. Evidence and validation scoped
The review records the signal context, evidence gaps, and physical validation step agreed for the carrier’s lane schedule.
3. Dispatch console pages the tech
The workbench can show a candidate alert and open questions for review. Lane timing, parts, dispatch, and mechanic availability require separate written scope.
4. Vetted tech coverage is checked
When service is needed, Trodeon checks the declared service area and coordinates a vetted field partner for the written job scope — terminal, yard, customer dock, or roadside.
5. Repair confirmed, fee settled
The pilot review compares observed evidence with the carrier’s agreed baseline; any repair or operational outcome is reported only after it is documented.
Buying-committee research
Two analysts. Two starting points.
The procurement analyst opens at /integrations — how Trodeon reads the existing ELD / J1939 telematics feed, what the OEM and right-to-repair posture looks like, and which procurement vehicles a multi-yard rollout can ship against.
The operations analyst opens at /roi — what an avoided breakdown is worth before the defined-window pilot, and how the fleet team can measure the same signal at sign-off.
Procurement fit
One approved commercial path. $150 capped Coordination Fee + 30 days of premium diagnostic access.
Carrier procurement can start with the defined 30-day window and the approved $150 capped Coordination Fee plus 30 days of premium diagnostic access. The pilot uses the fleet’s existing operating data and documents the measurement boundary up front.
Scope a defined-window pilot against a single terminal first. Any later per-truck or service scope is discussed after the window produces real operating evidence; it is intentionally not priced on this page.
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 $150 capped Coordination Fee and 30 days of premium diagnostic access documented up front. Operations can measure the window against the current lane; any later scope follows the evidence.
Or research-first: /integrations for telematics and procurement systems questions, and /roi for the avoided-downtime math.