Installed Base Visibility Guide for Machinery OEMs

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

You can probably give someone a rough count of machines in the field. What you likely cannot do, without searching across spreadsheets and email threads, is tell them the service history of a specific machine at a specific customer site, its current warranty status, the exact configuration including any modifications since installation, and when it last had attention. That gap is where after-sales service breaks down.

Every machine you have ever sold needs a single digital record that follows it through its lifetime. That record links the customer, location, serial number, configuration, service history, and documentation. Without it, your service team is working from incomplete information. With it, every service interaction, parts order, and contract renewal becomes faster, more accurate, and less dependent on the right person being available to answer a question.

The hidden cost of losing track of your installed base

A typical machinery manufacturer sells between fifty and several thousand machines a year. Across two or three decades of operation, that means tens of thousands of assets sitting in customer facilities across multiple countries, often multiple continents. Most OEMs cannot say with confidence how many of those machines are still in active operation, which exact configuration each customer received, what service was last performed, or which machines are approaching the end of their warranty.

The costs of that blind spot are specific and compound over time.

Service teams dispatch the wrong parts because the machine variant is unclear. A technician arrives on site, opens the panel, and finds a different control board than the work order assumed. The visit becomes a return trip. The customer waits another week. Turmec, a waste management machinery manufacturer with customers across Australia, the UK, Ireland, and the EU, experienced exactly this: manual after-sales processes were generating costly dispatch errors, and the team had no real-time view of what was actually in the field. At their scale, sending the wrong part to Australia is not a small line item.

Sales teams miss upgrade and renewal opportunities 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 proposal before your account manager has noticed the window exists.

Compliance and recall risk grows quietly. When a service bulletin is issued, the OEM needs to identify exactly which machines in which facilities are affected, notify those customers, and track remediation. Without structured installed base data, this takes weeks rather than days. In the EU, the Machinery Regulation sharpens this exposure further.

Spare parts revenue leaks in a less visible way. Customers order parts for the wrong variant, receive incorrect items, and lose confidence in ordering through the OEM. Over time, some drift toward grey-market suppliers who often have better records of what the customer is running than the manufacturer who built it.

Why the tools you already own don't solve this

Most machinery OEMs try to address the installed base problem with software they already have. CRMs, ERPs, spreadsheets, and general field service platforms. None of them are built for the job, and the limitations are structural rather than fixable through configuration.

CRMs are contact-centric. Salesforce and HubSpot are built around accounts and relationships. Where machines exist at all, they sit in custom objects that no native workflow recognises. A service ticket in a CRM lives against a customer. When that customer has fourteen machines from your factory, the CRM has no native way to know which one the ticket belongs to.

ERPs record transactions, not lifecycles. Your ERP captured that serial number 8849 was shipped to a customer in 2018. It does not know the machine was relocated to a different facility in 2021, upgraded with new controls in 2023, and is now approaching end of life. That is not a gap you configure your way out of. It is a different data model.

Spreadsheets decay the moment they are created. Every dispatcher and regional manager builds their own version. None of them sync. When the senior technician who maintained the master file retires, their version of the installed base retires with them.

Generic field service platforms are built around tickets, not machines. Salesforce Field Service and Dynamics 365 Field Service can be extended with a custom asset object, but the workflow does not revolve around it. The machine becomes an afterthought attached to a ticket-first system. Technicians still arrive on site looking across multiple screens for information that should be in one place.

There is also a category distinction worth naming. EAM software (IBM Maximo, Infor, SAP AM) is built for the company that owns assets and cares about depreciation, utilisation, and lifecycle cost. Installed base management is built for the company that made the assets and cares about service relationships, ongoing revenue, and customer experience across the machine's full lifetime. The two overlap on the surface. The data models, the workflows, and the users are fundamentally different. EAM is built for the asset owner. Installed base management is built for the asset maker.

What a complete installed base record looks like

A well-structured installed base has five layers. Each builds on the previous, and missing any one of them creates a gap that reduces the value of the rest.

The foundation is the single machine record: one digital file per machine, created at the point of sale and updated throughout the machine's working life. It holds the serial number, machine type and variant, original build date, configuration details, current customer, current installation site, and warranty terms, with a link back to the original sales order in the ERP.

The second layer is linked service history. Every service event (ticket, work order, preventive maintenance visit, parts order) writes back to that machine record automatically. Three years from now, when a new technician picks up a job for the first time, they see the complete history: every visit, every part replaced, every fault raised, every report signed. This needs to happen automatically, not through someone remembering to update a file.

Third is documentation anchored at the asset level. Manuals, electrical drawings, compliance certificates, and service 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 written for six different configurations.

The fourth layer is customer access through a portal. Customers should be able to see their own machines, their own service history, and their own documentation without calling your support team. Döinghaus, a German manufacturer of precision ultrasonic cutting equipment, now has around ten major customers logging service issues directly through the platform, which means their service team sees every open issue in one view without managing a single email thread. If the customer cannot see what you see, they call every time they need basic information. A connected portal turns both sides into active stewards of the same data.

The fifth layer is distributor access. For OEMs that sell through dealer networks, distributors need role-scoped access to the machines they service. They see their customers only, but they see the complete record for those customers. The OEM retains full visibility across the network.

[Button text: See how Makula manages your installed baseLink: [demo booking URL]Style: Primary button

Getting from where you are to where you need to be

Most machinery OEMs approach installed base management not as a one-time migration but as a phased process that runs alongside normal service operations.

The first phase, typically taking two to three weeks, is pulling the foundation data: every machine record from the ERP, covering sales orders, serial numbers, machine types, customer assignments, install dates, and warranty terms. Most OEMs find that 60 to 80 percent of the base record can be reconstructed automatically from ERP data and historical sales documents. The remaining 20 to 40 percent needs field validation, which happens gradually as technicians visit customer sites.

The second phase layers in service history. Existing service reports, tickets from previous platforms, and technician notes get imported and attached to machine records. The quality of this data varies depending on how well records were kept, but even imperfect historical data is more useful than no data at all. This phase typically runs from weeks two to six, overlapping with the first.

The third phase is customer portal activation. Once machine records are clean enough to share with customers, the portal goes live. This does two things simultaneously: it delivers immediate value to the customer relationship, and it starts customers flagging their own data corrections when they notice discrepancies. The customer becomes part of the data quality process.

From week four onward, the system is live and every new service event enriches the record automatically. After six to nine months of normal service activity, most OEMs have a mature installed base covering the large majority of their active field population. The goal is not a perfect database on day one. It is a progressively more complete picture that gets more useful with every job that closes.

How to know if it's working

Four metrics show whether installed base management is delivering value. Track these from go-live and review them quarterly.

Installed base coverage rate measures the percentage of machines sold for which you hold a complete, validated digital record. A mature OEM targets 90 percent or higher for machines under fifteen years old. Starting from spreadsheets, most reach 70 to 80 percent within the first three months and close the gap through ongoing service visits.

Time to machine context measures how quickly a service request can be matched to a complete machine record. With a structured installed base, this drops from hours or days to under sixty seconds. That speed affects every part of the service workflow, from dispatch accuracy to customer communication to parts ordering.

First-time fix rate is the clearest downstream indicator. Installed base visibility is the single biggest driver of whether a technician resolves a problem on the first visit or comes back for a second. Most machinery OEMs see a 15 to 25 percentage point improvement in first-time fix rate once technicians have reliable access to machine-specific information before and during a site visit.

Service revenue per asset tracks how much annual revenue each machine generates through contracts, parts, and labour. Tracking this by machine variant, by region, and by customer reveals where the highest-value service relationships are and where the largest gaps in contract coverage remain.

[LINK: See the full field service KPIs guide for machinery OEMs][URL: /products/field-service/buying-guide/field-service-kpis]

How Makula approaches installed base management

Makula's installed base module is built for the data structure machinery OEMs need: machine-centric records that link serial numbers to configurations, customer sites, service histories, documentation, and commercial relationships. Every other part of the field service platform works from this foundation. A ticket raised through the customer portal links to the machine. A work order created by the dispatcher links to the machine. A technician opening the mobile app on site sees the machine's full history.

The platform handles distributed installed bases across dealer and distributor networks. Distributors get access to records for the machines they are responsible for, with permissions controlled by the OEM.

The Glave Group, an industrial group in Lower Saxony managing NLT Automation GmbH as an OEM alongside Norder Band AG as a factory customer, brought their installed base into a single platform. Both the OEM service team and the internal maintenance team now share a view of machine activity and service status across company lines, without duplicating data or managing two separate systems.

For companies currently managing installed base data in spreadsheets or ERP exports, migration is part of Makula's onboarding process. The team works with your data in its current format and structures it before go-live.

[LINK: See the installed base management feature in full detail][URL: /products/field-service/features/installed-base-management]

[LINK: Read the guide to scheduling, dispatch and work order management][URL: /products/field-service/buying-guide/scheduling-dispatch-work-orders]

[LINK: Read the guide to growing after-sales service revenue][URL: /products/field-service/buying-guide/grow-after-sales-service-revenue]

[LINK: Read the guide to service performance analytics][URL: /products/field-service/buying-guide/service-performance-analytics]

[LINK: Back to the complete field service buying guide][URL: /products/field-service/buying-guide]

[SECTION END]

[SECTION: FAQ]

[H2]Frequently asked questions

[FAQ — H3]What is installed base management for a machinery OEM?

Installed base management for a machinery OEM is the practice of maintaining a complete, accurate, lifetime digital record of every machine the company has ever sold. The record links each machine to its customer, location, configuration, service history, and documentation. It exists so service, sales, and support teams can act on accurate information rather than searching across disconnected systems.

[FAQ — H3]How is installed base tracking different from asset management?

The distinction comes down to perspective. Asset management is built for the company that owns the asset and cares about depreciation, utilisation, and lifecycle cost. Installed base tracking is built for the company that made the asset and cares about service relationships, recurring revenue, and customer experience across the machine's full lifetime. The data models overlap, but the workflows and the people who use them are different.

[FAQ — H3]Why do machinery OEMs lose track of machines after they leave the factory?

Because the data was never centralised in the first place. The original sale lives in the ERP. Service history sits in scattered tickets and email threads. Customer relocations and upgrades are rarely captured anywhere. Distributors hold their own records that do not sync back. Without a single asset-first system designed to consolidate this, the picture fragments year after year until no team can answer basic questions about the field population.

[FAQ — H3]Can installed base management work for OEMs that sell through distributors?

Yes, and for OEMs with channel partners it is more valuable, not less. A well-designed installed base platform gives distributors role-scoped access to the machines they service, while the OEM retains full visibility across the network. Every service action the distributor performs writes back into the shared record, which keeps the OEM in oversight without removing the channel's ability to deliver good service.

[FAQ — H3]How does installed base data connect to service contracts?

Directly. When every machine has a structured record including warranty status and contract expiry dates, your service sales team has a prioritised view of renewal and upsell opportunities. Machines approaching end of warranty, machines without active contracts, and machines with high service frequency are all visible without building a separate report. The installed base record is the starting point for every service contract conversation.

[FAQ — H3]What return on investment should a machinery OEM expect from installed base management?

Most machinery OEMs see payback within six to twelve months. The largest drivers are higher first-time fix rates, fewer wrong-part dispatches, increased spare parts revenue through customer self-service, and the ability to identify and convert uncontracted machines into service agreement customers. Improved recall execution and reduced compliance exposure are harder to quantify but often more significant over a multi-year horizon.

[SECTION END]

[SECTION: End CTA]

[CTA BUTTON — END PAGE]Button text: Book a demo to see Makula's installed base platformLink: [demo booking URL]Style: Primary button, large

[SUPPORTING TEXT BELOW BUTTON]30-minute sessions. Tailored to your machine type and team size. No commitment required.

[SECTION END]

[PAGE END]

INTERNAL NOTES — REMOVE BEFORE PUBLISHING

• FAQ schema: add JSON-LD for all six FAQ questions
• KPIs section: the four metrics here are selected for relevance to installed base specifically. The full field service KPI set belongs in /buying-guide/field-service-kpis
• Evaluation checklist: the writer's original draft included a vendor checklist section — this has been intentionally removed from this page. That content belongs at /buying-guide/evaluation-checklist
• Meta description: trim to 160 chars before publishing
• Word count: approximately 2,300 words excluding annotations
• Cluster 1 of 7 in the buying guide cluster architecture