Andrews Logistics — Remote Diagnostic Support

/ unit fieldEnter look upCtrl+Enter file actionCtrl+S save caseBelow 8 resolved episodes no repair path is shown. Sorted by cost to rule out, not frequency.

Enter a unit, an SPN with FMI, or a DAVIE code. A lookup arms the case draft; nothing is written until you press Save.

● No case FleetRock: not synced 00:00

Running a call

Find the truck. Unit number in the box at the top, Enter. The codes it is throwing right now come up with the worst first.
Open the repair order in FleetRock first. A case will not push anything to a truck that has no open RO — that is deliberate, not a bug. If there is no RO yet, the shop or the terminal opens one, then you put its number on the case.
Start the case. Pick the code you are calling about, enter the RO number, and save. The case now owns the link between that truck, that code and that order.
Work the code. Check first is what to look at before anyone orders a part. What the shops did is what vendors actually billed for this code. What actually fixed this stays empty until we have eight repairs followed through to an outcome — expect it blank for months.
File each line as you go. Type what was done or what to do next in the action box and press Enter. One line per thing, in plain language, as if the tech who reads it next has not heard the call.
Attach a document if you have one. Attach file… takes a PDF or a photo — a dealer estimate, a DAVIE screenshot, a picture of the part. It sends with the next push. 4 MB limit.
Push to FleetRock. Sends your latest action line, and the attachment if there is one, onto the repair order so the shop sees it. Watch the chip: sent means it landed, dry run means the live write is still switched off and nothing left this building.
Close the case with an outcome when the call ends. If a vendor did the work, fill the vendor follow-up — what they did, the root cause, their codes. That is the only way the desk learns what actually fixes a code.

No open repair order, no push. Every note has to land somewhere a shop will read it, and an RO is the only such place.

Never guess a part. If the board says general guidance only, there is no procedure on file for that code — say so on the call rather than filling the silence.

Write for the next person. The note you file is what a tech at Rush reads at 6am with a truck down.

Nothing armed. Run a lookup to arm a draft.

Unit *

Cost center

Caller

Complaint

Action log go-do-this / come-back — every line also goes to FleetRock

No actions yet.

Outcome

Est. avoided cost ($)

Avoided a road call

Notes

Attach file… No file attached

Management surfaces — out of the call loop.

Repeat-fault unitsLive ECU counters beside 90 days of captured episodes. Click a row to look the unit up.

Loading…