What was reported?
Keep driver notes and fault reports distinct from an explanation of the cause.

Class 8 fleet maintenance · Evidence before action
The founder’s market rationale is that a truck sitting still can cost thousands of dollars per hour. Trodeon is developing maintenance decision support to help teams assemble the story across records; no Trodeon savings or live-fleet result has been measured.
Fleet teams retain every inspection, repair, and dispatch decision. No automatic operational action is implied.
TRODEON · ONE-EVENT ESTIMATE
Estimate the cost associated with one roadside tow using your own inputs. No annualized totals, avoided-tow rate, or Trodeon savings are assumed.
Change any value; the single-event estimate updates immediately.
Fleet size for context. The estimate below covers one event.
Illustrative starting value1 trucks–2,500 trucks
Your estimate for the roadside tow and related service invoice.
Illustrative starting value$0–$50,000
Hours associated with this single roadside event.
Illustrative starting value0 hours–168 hours
Your operating-cost estimate for each out-of-service hour.
Illustrative starting value$0 / hr–$50,000 / hr
Illustrative · one roadside event
Estimated cost associated with one avoided roadside tow
$9,250
Illustrative single-event cost estimate if one roadside tow were avoided; this is not a realized or guaranteed saving.
If a tow were avoided, this estimate is not a guaranteed saving, a Trodeon result, or a prediction of fleet performance. Fleet teams keep all maintenance and dispatch decisions.
All starting values are illustrative and editable. The one-event estimate is tow/service cost plus out-of-service hours multiplied by your entered hourly cost. Fleet size is context only; the result is not multiplied across trucks. An estimate is not a guaranteed saving or a Trodeon outcome.
The information problem
Driver complaints, fault reports, and service notes each tell a different part of the story. A useful review separates observations from assumptions and makes recurring concerns, previous work, and missing context visible.
Keep driver notes and fault reports distinct from an explanation of the cause.
Bring service notes into the chronology without assuming an inspection resolved it.
Show missing context and conflicting records so a reviewer can decide what matters.
TRODEON · PROPOSED REVIEW FORMAT
ILLUSTRATIVE EXAMPLE — SYNTHETIC RECORDS
This synthetic walkthrough brings observations, previous work, uncertainty, and missing context into view for a fleet manager. It demonstrates a review format, not a diagnosis or prediction.
Not live vehicle data. No customer case, validated fault, repair instruction, service dispatch, or operational action is represented.
01 / RECORD CHRONOLOGY
ILLUSTRATIVE EXAMPLE — SYNTHETIC RECORD
“Warning appeared intermittently.”
No exact code, operating context, or source timestamp is supplied.
ILLUSTRATIVE EXAMPLE — SYNTHETIC RECORD
“Inspected reported concern.”
Inspection findings, repair details, and follow-up outcome are missing.
ILLUSTRATIVE EXAMPLE — SYNTHETIC RECORD
“Warning reported again.”
The available notes do not establish whether this matches the earlier warning.
Proposed process · not activated
Proposed evaluation workflow—not an activated service or data connection.
Any future evaluation would begin with the maintenance question and written scope. Records and permissions are agreed before access or transfer.
Security and data handling are supporting conditions; the maintenance value is clearer evidence for human review.
Choose a maintenance question.
Agree on records and permissions before access or transfer.
Review chronology, observations, and gaps within the agreed scope.
Agree how to assess usefulness, such as preparation effort or evidence clarity.
Preparation effort and evidence clarity are proposed measures to agree on—not demonstrated benefits or promised outcomes.
Independent offline evaluation
In an offline selected-record comparison, history-informed features improved repair-event ranking, while a separate calibration experiment improved probability scoring. The methods, results, and limitations are published for review.
The reused source cohort contains 5,045 vehicles and 142 labelled events. The reported comparison uses a selected set of 505 records from that offline research.
Independent offline research only. It is separate from the Trodeon application and is not customer-fleet validation or named-fault diagnosis.
Read the methods, complete results, and limitationsEvidence and development status
Offline research and local engineering checks answer different questions. Neither is evidence of live-fleet performance or independent Polsia reproduction.
DOCUMENTED WORK
STILL TO ESTABLISH
Three distinct offerings
01 / MAINTENANCE DECISION SUPPORT
Organize maintenance evidence for human review: recurring concerns, previous work, missing context, and unconfirmed possibilities.
Decision support is in development. Hypotheses are not confirmed faults; no automatic repair authorization, service dispatch, or operational action is implied.
Explore Fleet EvaluationSupplied conceptual illustration only. Its J1939, OBD-II, ELD/telematics, and physical-validation labels do not show deployed integrations or completed service.

02 / FUEL RECONCILIATION
Clean, validate, and reconcile fuel-card or accounting CSV records into an IFTA-ready report.
One-time plans; no subscription. Founding Carrier pricing is locked for the first 25 signups.
View Combust plans and checkoutFigures in this supplied fuel-summary image are illustrative, not customer results or Combust plan prices.

03 / INQUIRY · SCOPE CONFIRMED DIRECTLY
Send an inquiry and confirm the current scope directly with the team.
Services, rates, coverage, and transaction terms are not established by the supplied images and are not stated here.
Make a Chasehaul inquirySupplied truck and rate-confirmation images are context only; the document is not a live customer deal or current offer.


The founder’s service vision
The aspiration is IoT monitoring of big-rig engine wear, with an early repair alert to dispatch when evidence warrants attention. An equipped mobile unit could reach a disabled truck on the road or at a lot, where skilled diesel mechanics could make a fast, high-quality on-site repair. Longer term, the founder envisions growth through local mechanics.
“Built by a mechanic who got tired of showing up too late.”
Sensors, alerts, equipped units, mechanic capacity, and coordination are not represented as operating today. Coordination depends on confirmed scope, partner support, and local availability.
90-DAY DOWNTIME PREVENTION AUDIT
90-Day Downtime Prevention Audit
Includes weekly health briefs, priority fault triage, and a final ROI summary.
The 90-Day Downtime Prevention Audit is $99 total for three months, not a monthly charge.
You choose whether to continue after the audit. If you continue, your first continuation month is free.
Pricing after that first continuation month is unspecified. No later price has been set; any later charge requires a current owner-approved price and your acceptance.
Any evaluation scope, records, and permissions are agreed before access or transfer. The existing application receives human review before checkout.
Start with the cost and the question.
Use your own assumptions, then see the proposed evaluation scope.