Ghost equipment — machines assigned to customers who no longer own them — skews every fleet report you run. Here's what causes it, how to find it, and why it's harder to fix than it looks.
In every dealer's fleet data, there are machines that exist on paper but don't exist in reality — not because they're missing, but because the customer assignment hasn't been updated after a sale, transfer, or trade-in.
These are called ghost machines. They show up in your utilization reports. They inflate your customer's apparent fleet size. They generate PM schedules that go to the wrong place. And nobody flags them — because the telematics system has no way to know a sale happened.
The DMS handles the sale. The telematics system doesn't talk to the DMS. The machine gets transferred to a new owner, but VisionLink still shows it assigned to the old customer — because nobody manually updated the customer record in the telematics system after the transaction closed.
At a dealer doing 50–100 transactions per year, it takes roughly 18–24 months before this problem is visibly affecting reporting. By then, the cleanup effort is significant and the historical data is compromised.
Ghost equipment doesn't just make reports look wrong. It creates downstream problems:
VisionLink and JDLink surface machine data — they don't cross-reference it against your transaction history. The telematics system knows the machine exists and is being used. It doesn't know it was sold.
The signal for ghost equipment isn't technical — it's behavioral. A machine assigned to Customer A that has had no service orders, no invoices, and no contact with Customer A in 90+ days is likely no longer owned by Customer A. That's a pattern that lives in your DMS and service history, not in the telematics feed.
Finding ghost machines requires crossing two data sources that don't normally talk to each other: telematics assignment (who the machine is assigned to in VisionLink) and DMS transaction/service history (who has actually been doing business with you recently around that machine).
The tempting answer is to build a rule: "if no service activity in 90 days, remove from customer assignment." The problem is that this rule would also flag machines that are simply sitting in the field between jobs, or seasonal equipment that goes dormant in winter.
The right answer is a human review workflow. The system surfaces the flag: "Unit 950M has had no activity against Summit Groundworks in 110 days." A service advisor looks at the record, calls the customer, and either confirms the sale or confirms the machine is still active. The system doesn't decide — it just makes the problem visible.
In dealer fleet data I've worked with directly, ghost equipment typically represents 3–8% of assigned machines at any given time. For a dealer managing 500 machines, that's 15–40 machines with incorrect assignments — enough to meaningfully skew customer profitability reports and PM compliance rates.
Most dealers don't know this number because they've never had a tool to calculate it.
OIQ Fleet Intelligence automatically flags ownership staleness — surfacing machines with no service activity against their assigned customer and putting them in a review queue for your service advisors. See the data quality layer →
Related