
It is the week before the quarterly network review, and the regional aftermarket manager has twelve dealer reports open on two screens. Eleven arrived on time. Four are in the agreed template. One dealer measures response time from the moment a call is logged, another from the moment a technician is dispatched and a third doesn’t say.
Halfway through the afternoon an email arrives from a large fleet customer. The same reach truck model has had three hydraulic failures at their site this year. None of the dealer reports mentions it. The customer has written to head office because, as far as they are concerned, the badge on the machine is the brand they bought.
Nobody has done anything wrong. The information simply never travelled far enough.
The view from head office is assembled, not observed
Most manufacturers see their network through what dealers send upward. Monthly reports, warranty submissions, parts orders and the occasional escalation. Each piece is useful. Together they form a picture that is always slightly late and always slightly edited.
That isn’t a criticism of dealers. A dealer’s first job is to keep customers’ machines working, not to prepare reports for someone else. When reporting competes with a breakdown, the breakdown wins, as it should.
The result is that the manufacturer’s understanding of the market is assembled after the fact. By the time a pattern is visible at head office, the customer at the centre of it has often lived with it for months.
Every dealer counts differently
Ask five dealers for their average response time and you may get five honest answers that cannot be compared. One counts calendar hours, another counts working hours. One closes a job when the machine runs, another when the paperwork is done. One records downtime, another doesn’t track it at all.
None of these is necessarily wrong. But a network-wide figure built from them is a sum of different measurements, and decisions based on it can reward the dealer with the most generous definitions rather than the best service.
Comparable performance starts with shared definitions. What counts as a breakdown? When does the clock start? When is a job closed? Agreeing on those answers is less exciting than a new dashboard, and far more useful.
The installed base is a moving target
A machine leaves the factory with a serial number and a first owner. A few years later it may have been moved to another site, sold to a rental company, rebuilt, re-sold or quietly retired in the corner of a yard.
Sales records describe where equipment went. They rarely describe where it is now, how hard it works or who looks after it. For an OEM, that gap matters. It affects parts forecasting, campaign and recall work, service planning and any conversation about which models perform well in which applications.
An installed base is only as accurate as its last update. If updates depend on someone remembering to send them, the register ages quickly.
Warranty tells only part of the story
Warranty activity is often the clearest signal a manufacturer receives from the field, which is exactly why it can mislead. It shows failures that were claimed during the warranty period. It says much less about what happens afterwards, about failures that were repaired without a claim or about the slow, expensive problems that never trigger one: repeat callouts, extended downtime, a component that wears out early in one type of application.
Those are the issues fleet customers remember when the time comes to replace their equipment. They are also the issues that rarely appear in a warranty report.
Customers experience the brand, not the dealer
A fleet customer may never meet anyone from the manufacturer. Their experience of the brand is the dealer’s technician, the dealer’s quotation and the time the dealer takes to get a standing machine moving again.
When one dealer delivers well and another struggles, the customer doesn’t see two businesses. They see one brand behaving inconsistently. A multinational customer with sites in several regions notices this quickly, and asks the obvious question: why is the service so different from one site to the next?
Consistency across a network is not about making every dealer identical. It is about agreeing on a minimum standard and being able to see whether it is being met.
Visibility should support dealers, not police them
There is an understandable worry on the dealer side that more visibility means more scrutiny. Handled poorly, it can.
Handled well, it works the other way. Shared, consistent records show where a dealer is performing strongly, which is useful when a customer complains unfairly. They show where a dealer needs support, whether that is technical training, parts availability or extra technicians in a growing region. And they give both parties the same facts to discuss, instead of two versions of events.
The aim is a better conversation between manufacturer and dealer, not a louder one.
Where FMC fits in the network
FMC for OEMs is designed to create a common operational visibility layer across a dealer network. Participating dealers run their service operations, technicians, parts, contracts and customers in FMC, and every machine builds a traceable record across its lifecycle. That gives the manufacturer a clearer, continuously developing view of the installed base across customers, dealers and regions.
For dealers, the benefit is better operational control, service management and accountability. For the OEM, it means understanding service activity, response times, downtime and compliance on consistent terms, with inspections, load tests and documentation tracked across the network. Dashboards and reporting turn that activity into regional and network-level views, without relying only on manually consolidated reports.
FMC works across brands and mixed fleets, can complement existing dealer and OEM systems and can be deployed by dealer, customer, region or network. Software supports those decisions; manufacturers, dealers and their teams remain responsible for making them.
Where to start
Network visibility doesn’t begin with a platform. It begins with a few direct questions:
- Do all dealers define response time, downtime and job completion in the same way?
- How current is your installed-base record, and who updates it when a machine moves?
- Which field problems do you hear about only when a customer escalates?
- What do dealers get back from the information they share with you?
- Could you compare two regions today without a week of spreadsheet work?
If the honest answers are uncomfortable, that is a useful place to begin. Start with shared definitions, agree what each party needs to see and build from there.
A brand travels further than the machine. The information about how that machine is doing should travel at least as far.

