01
Reviews a signal developing over time
Per-part wear signals are scored against a rolling 14-day baseline — the model flags drift, not a single-frame snapshot read.
How it works · the evidence-led uptime platform
Review the signal before the pilot decision — not after the truck stops.
Four illustrative stages — available telemetry is reviewed inside the written pilot scope, candidate signals surface for operator review, and any service coordination is checked separately against declared coverage.
Plug-in→signal review→Alert→Dispatch
Signal review lead across the in-service fleet
To be measured
Median · rolling 6-week fleet average
Evidence state
I review your telematics data for signals across DPF and aftertreatment, turbo, electrical, and fuel delivery. Every flag comes with the evidence behind it and a physical validation step. When the data isn't there to say something useful, I say so.
Public examples are scoped evidence reviews, not detection or outcome guarantees. The next step is a physical validation check inside the written pilot scope.
No public family capability is currently eligible for presentation.
More than a diagnostic scanner
Six jobs the platform does that a code reader cannot.
Every row carries a proof-led sentence. Synthetic and pilot-validation states stay labeled; no guaranteed prevention is implied.
02
States the evidence and operating context
Every finding names the contributing bus signals and the duty-cycle / load / ambient conditions in play at the moment it was scored.
03
Weighs competing causes, not a single DTC answer
Ranked evidence review over the active hypothesis set — a thermistor fault and a sticky VGT both surface near the top when the J1939 stream shows either is plausible.
04
Recommends the least-invasive validation step
Trodeon prefers a cab-side CAN read or a bench quick-test before any teardown.
05
Expresses calibrated evidence and uncertainty
Evidence review percentage and a window of review timing — no lone-precision claims, no “always” / “never” language.
06
Connects the validated fix to repair timing and avoided downtime
Once the cheap read confirms the cause, the platform reserves the install slot, stages the part, and posts an avoided-downtime range against your loaded hourly cost.
The walkthrough
The four stages, as the operator would see them.
Each card below is an illustrative interface state — synthetic telemetry rows, a candidate window, an evidence review, and a scope-dependent coordination step. It is not a live-fleet result or a guarantee.
01 · Stage 01 · Connect
Start with the data path your written pilot scope allows.
The current pilot path evaluates existing J1939 or compatible telematics data when the fleet can provide the required access.
Illustrative review state
Evidence window pending physical validation.
02 · Stage 02 · Compare
The workflow compares signal drift without calling a candidate a certainty.
The prototype scores an incoming stream against a rig's baseline and surfaces a candidate window for review.
Illustrative review state
Evidence window pending physical validation.
03 · Stage 03 · Review
A candidate lands in the workbench with evidence and open questions in view.
The operator reviews the rig context, candidate signal, evidence gaps, and next physical validation step.
Illustrative review state
Evidence window pending physical validation.
04 · Stage 04 · Coordinate
Service coordination is scope-dependent and never guaranteed by the signal alone.
If the written pilot scope includes service coordination, Trodeon can review declared coverage and the agreed job scope.
Illustrative review state
Evidence window pending physical validation.
Synthetic demo data
Watch the VGT drift develop across 14 days — not a snapshot.
Today · +6.6% drift · high
Evidence review
Evidence review over the active hypothesis set, not a single DTC.
1. Primary hypothesis
Turbo VGT actuator wear
Evidence factors stay visible; the next physical check determines whether this explanation is useful.
2. Review path
Sticking VGT vanes (soot-loading)
Evidence factors stay visible; the next physical check determines whether this explanation is useful.
3. Review path
Wastegate hose leak
Evidence factors stay visible; the next physical check determines whether this explanation is useful.
4. Review path
ECU boost-map drift (calibration)
Evidence factors stay visible; the next physical check determines whether this explanation is useful.
Pilot first
Project the downtime your fleet is leaving on the table.
The same evidence path gives your fleet a defined pilot, a written scope, and the next physical validation step.
Apply for the 30-day pilot