How to Track Every Machine You've Ever Sold as a Machinery OEM

How to manage installed base machinery OEM operations starts with one principle: every machine you've ever sold needs a single digital record that follows it for life. That record links the customer, location, serial number, service history, and documentation. Without it, your service team is guessing. With it, every service interaction, spare parts order, and upgrade conversation becomes faster, more accurate, and more profitable.

The Hidden Cost of Losing Track of Your Installed Base

A typical machinery manufacturer sells between fifty and several thousand machines per year. Across two or three decades of operation, that means tens of thousands of assets sitting in customer facilities across multiple continents. Yet most machinery OEMs cannot answer with confidence:

• How many of those machines are still in active operation.
  
• Which exact configuration and version each customer received.
  
• What service was last performed and by whom.
  
• Which machines are approaching end-of-warranty or end-of-life.
  
• Which customers have which spare parts on hand.
  
• Which assets are running outdated firmware or recalled components.
  

The costs of this blind spot compound quietly, year after year.

Service teams dispatch the wrong technician or the wrong parts because the machine variant is unclear. A field engineer arrives on site, opens the cabinet, and realises the customer's machine has a different control board than the work order assumed. The visit becomes a return trip. The customer waits another week. Trust erodes.

Sales teams miss upgrade and renewal cycles because they cannot see which customers are running machines that are eight, twelve, or fifteen years old. The competitor who tracks this proactively walks in with a refit quote before your account manager has noticed.

Recalls and compliance bulletins cannot be executed cleanly because the OEM cannot identify which specific machines in which specific facilities are affected. Regulatory exposure rises. Legal teams get nervous. In the EU, the new Machinery Regulation will sharpen this risk further.

Spare parts revenue leaks because customers order parts for the wrong machine variant, receive incorrect items, and lose confidence in ordering through the OEM at all. Many drift toward grey-market suppliers who, ironically, often have better records of what the customer is running.

This is the practical answer to why machinery OEMs lose track of machines in the field: the data was never centralised in the first place. It lives in the original sales order in the ERP, in scattered service reports on a shared drive, in a dispatcher's spreadsheet, in the memory of a senior technician who retires next year, and in the customer's own facility logs. No single team owns the whole picture.

Why Generic Tools Cannot Solve This

Most machinery OEMs try to solve installed base management with tools they already own. CRMs, ERPs, spreadsheets, generic field service platforms. None of them are built for the job, and the reasons are structural rather than configurational.

1. CRMs are contact-centric:
   Salesforce and HubSpot are built around accounts and contacts. Machines, where they exist at all, are crammed into custom objects that no native workflow recognises. A service ticket in a CRM lives against a customer, not against a serial number. When the customer has fourteen machines from your factory, the CRM has no native way to know which one the ticket belongs to.
   
   
2. ERPs treat machines as line items, not living assets:
   Your ERP recorded that you shipped serial number 8849 to a customer in 2018. It does not know that the machine was relocated to a different facility in 2021, upgraded with a new vision system in 2023, and is now nearing end-of-life. ERPs were built for transactions, not lifecycles.
   
   
3. Spreadsheets decay the moment they are created:
   Every dispatcher and regional manager builds their own. None of them sync. When a senior technician retires, their spreadsheet retires with them.
   
   
4. Generic FSM tools track tickets, not machines:
   Salesforce Field Service and Dynamics 365 Field Service can be customised to add an asset object, but the workflow does not revolve around it. Technicians still arrive on site looking up information across multiple screens. The asset record is an afterthought bolted onto a ticket-first system.

This is the core of the installed base tracking vs asset management for manufacturers distinction. Asset management, in the EAM sense, is about lifecycle costs and depreciation. Installed base tracking is about service relationships, ongoing revenue, and customer experience across decades.

The two overlap on the surface, but the workflows, data models, and end users are fundamentally different. EAM is built for the asset owner. Installed base management is built for the asset maker.

A Machine Lifecycle Visibility Guide for Machinery OEMs

A proper machine lifecycle visibility guide for machinery OEMs rests on five layers. Each one builds on the previous, and missing any single layer creates a gap that erodes the value of the others.

Layer 1: The Single Machine Record:‍

Every machine you have ever sold gets one digital record that persists for its lifetime. That record carries the serial number, machine type and variant, original build date, configuration, current customer, current installation site, warranty status, and a link back to the original sales order in the ERP. This is the foundation.

Layer 2: Linked Service History:‍

Every service interaction, ticket, work order, preventive maintenance event, and parts order writes back to the machine record. Three years from now, when a new technician opens that record, they see the complete story: every visit, every part swapped, every issue raised, every signature captured. Built into a dedicated installed base management platform, this happens automatically rather than depending on someone remembering to update a spreadsheet.

Layer 3: Documentation Anchored to the Asset:‍

Manuals, electrical schematics, compliance certificates, training videos, and standard operating procedures live against the machine record itself, not in a separate document library. When a technician scans the QR code on the machine, they see the documents for that exact variant, not a generic manual that covers six configurations.

Layer 4: Customer Access Through a Portal:

Customers can see their own machines, their own service history, and their own documentation through a self-service interface. This is the half of installed base management that most OEMs forget about. If the customer cannot see what you see, they will call your support line every time they need basic information. A customer portal connected to the installed base turns the OEM and the customer into co-stewards of the data.

Layer 5: Distributor and Dealer Access:‍

For OEMs that sell through partners, distributors need role-scoped access to the machines they service. They see only their customers, but they see the complete record for those customers. This keeps the OEM in oversight while letting the channel deliver good service.

These five layers together are what separates real installed base visibility from a list of serial numbers in a spreadsheet.

How to Manage Installed Equipment After Sale as an OEM

Knowing what good looks like is one thing. Getting there from where you are today is another. Here is the practical sequence on how to manage installed equipment after sale OEM without a multi-year IT project.

Phase 1: Migrate the Foundation (Weeks 1 to 3):‍

Pull every machine record from the ERP. Sales orders going back as far as your ERP holds them. Map the fields: serial number, machine type, customer, install date, warranty terms, original configuration. Import this into your installed base system. Most machinery OEMs find that 60 to 80 percent of the record can be reconstructed automatically from ERP data and historical sales documents. The remaining 20 to 40 percent will need field validation, which happens in Phase 3.

Phase 2: Layer In Service History (Weeks 2 to 6):‍

Import historical service tickets, work orders, and parts orders. Tie each one to the correct serial number. Where the historical data is too messy to migrate cleanly, set a cutoff date: everything from that date forward is captured cleanly through the new system, and the historical archive remains read-only in the old system for reference. Trying to clean every historical ticket is a trap. Set a line and move on.

Phase 3: Field-Validate Through Service Visits (Months 2 to 9):‍

This is where most OEMs underestimate the work, but it is also where the data gets honest. Every time a technician visits a customer site over the next six to nine months, they confirm or correct the machine record on their mobile app. They scan the QR code, check the configuration, confirm the install location, and flag any discrepancies. After two service cycles, the installed base record is largely accurate. After three, it is the source of truth.

Phase 4: Open Customer Access (Month 4 onwards):‍

Roll out the customer portal in waves. Start with your top twenty accounts. Train them on what they can see, what they can update, and what they can request through the portal. Customer-driven corrections close the last gaps in your data faster than any internal effort can.

Phase 5: Connect Distributors (Month 6 onwards):

Bring distributors and dealers onto the platform with role-scoped access. They see only their assigned customers. Their service activity writes back into the same installed base record the OEM sees.

The full sequence, done seriously, takes six to nine months to reach a state where the installed base is genuinely trustworthy. Most machinery OEMs find that the operational benefits, faster ticket triage, fewer wrong-part dispatches, higher first-time fix rate, are visible from week three. The strategic benefits, recurring service revenue tied to assets, distributor accountability, recall execution speed, take a full cycle to compound.

KPIs That Prove Installed Base Management Is Working

Once the foundation is in place, measure it. These are the metrics that show whether installed base management is actually delivering value for a machinery OEM. They are also the metrics your manager, your CFO, and your customers will eventually ask about.

Installed base coverage rate: The percentage of machines you have ever sold for which you hold a complete, validated digital record. A mature OEM targets 90 percent or higher for machines under fifteen years old.

Time to machine context: The average time between a service request arriving and a technician having full machine context. With proper installed base management, this drops from hours or days to under sixty seconds.

First-time fix rate: The percentage of service visits that resolve the issue without a return trip. Installed base visibility is the single biggest lever on this metric. Most machinery OEMs see a fifteen to twenty-five point improvement.

Service revenue per asset: How much annual service revenue, including contracts, parts, and labour, each machine in the installed base generates. Tracking this per machine variant, per region, and per distributor reveals where the highest-value service relationships live.

Customer portal adoption rate: The percentage of active customers who log into the portal at least once a quarter. Adoption above 60 percent typically correlates with materially lower inbound support volume.

Recall execution time: The time between a recall or service bulletin being issued and confirmation that every affected machine in the field has been notified, inspected, and remediated. Mature installed base systems collapse this from weeks to days.

Distributor data sync rate: The percentage of service activity from partner channels that flows back into the OEM's installed base record within seventy-two hours. Below 80 percent indicates a process or training gap.

Installed Base Management Evaluation Checklist

Before booking demos with any vendor, run them against this checklist. Anything missing here means the platform is not actually built for machinery OEMs.

• Every ticket, work order, and service report is automatically tied to a specific serial number, not just to a customer record.
  
• QR code or NFC tag support so physical machines link to digital records with a single scan.
  
• Asset-variant tracking, so different configurations of the same model are distinguishable in the data.
  
• Native ERP integration with SAP, Microsoft Dynamics, and Sage to pull and sync serial numbers, install dates, and warranty terms.
  
• Customer portal included as part of the platform, not sold as a separate module.
• Distributor and dealer access with role-scoped visibility to their own customers.
  
• Offline mobile access for technicians working in factories without WiFi, with automatic sync on reconnect.
  
• Document management at the asset level, so manuals and certificates live against the specific machine variant.
  
• Bulk import tools for migrating historical sales and service data from ERPs and spreadsheets.
  
• GDPR compliance and EU data hosting if you operate in or sell into the European Union.
  
• Time to go live measured in weeks, not months.

See Installed Base Management in Action

Book a free demo and see how machinery manufacturers and distributors are using Makula to turn their installed base into a living, revenue-generating asset. Or watch the 20-minute OEM walkthrough webinar first to see the full platform in context.

For the complete evaluation framework across all ten challenges machinery OEMs face, return to the main Field Service Software Buying Guide for Machinery OEMs