Baseline downtime
To be agreed
A real pilot would establish the baseline from the operator’s records.
Illustrative scenario · not customer evidence
Uptime recovered, before the truck stopped.
This page shows a synthetic workflow example for a Gulf Coast fleet. It does not represent a named customer, a completed pilot, a verified signal review lead, mechanic coverage, parts availability, dispatch timing, or savings.
Illustrative fleetIllustrative · 40 rigsGulf Coast · TX/LA intermodal
Pilot window: 30-day scope · example only.
Illustrative scenario · not customer evidence
Review a coolant-drift scenario without treating it as a customer result.
This synthetic 40-rig Gulf Coast scenario demonstrates how a coolant-drift signal could be reviewed against an agreed baseline. It is not a named customer, completed pilot, verified finding, mechanic assignment, parts record, savings result, or service guarantee.
By the numbers
What the platform moved in three months.
Dollars saved
Not reported
No savings figure is published without a current source, agreed baseline, and post-pilot evidence.
Cost per hour
Operator actuals
The fleet and Trodeon would agree the cost basis before reporting a result.
Candidate signal
Illustrative
A synthetic coolant-drift candidate is shown for workflow explanation.
Hours avoided
Not reported
The pilot does not promise avoided downtime.
Before vs. after
Example comparison · validation required
Illustrative workflow only. A pilot review would compare observed evidence with the agreed baseline; it would not assume a positive outcome.
| Dimension | Before Trodeon | After Trodeon |
|---|---|---|
| Coverage tightness | Existing data path · access to confirm | Pilot data path and signal quality to be measured |
| Evidence for parts review | Timing and validation not yet measured | Candidate window only · no parts-availability claim |
| Mobile dispatch | Service path depends on written scope | Coverage, dispatch, and location to be confirmed if included |
| Downtime bill | No verified cost or outcome baseline | Post-pilot review only · no savings outcome promised |
The recovery
This illustrative scenario uses a Gulf Coast intermodal operating context to show the evidence sequence: establish a baseline, review coolant drift, choose a discriminating validation step, and compare the observed repair path with agreed measures. It intentionally omits a customer name, completed outcome, mechanic coverage claim, parts promise, and savings figure.
In their region
1 jobs routed to Gulf Coast (TX · LA).
Illustrative service path only. Coverage, parts, timing, and any completed repair would be confirmed separately in the written pilot scope.
Your fleet
Measure the evidence your pilot can actually support.
Use the defined pilot as an illustrative planning tool. A pilot review should use your agreed baseline and observed evidence; it does not promise recovered downtime or savings.
Project your own downtime exposure