Every machine we deliver is a potential source of revenue—long after the sale is complete. Maintenance, spare parts, upgrades, and data-driven services often account for a more stable portion of the business in the machinery industry than new business. However, this potential remains untapped as long as the installed base—all machines and systems in the field—is not fully accounted for and digitally connected.
Those who systematically track their installed base, integrate its data, and use it to make informed decisions can turn it into a driver of growth. This article outlines the path to achieving this: from digital tracking to integrated service processes to decision intelligence—and the role Salesforce plays as a service hub in this process.
Why the Installed Base Is the Untapped Asset in the Service Sector
In many service organizations, information about the installed base is scattered across various systems: serial numbers in the ERP, maintenance histories in Excel, customer contacts in the CRM, and condition data—if available at all—in individual IoT portals. Without knowing which machine is running where, in what configuration, and when it was last serviced, it’s impossible to offer proactive service or sell spare parts or upgrades in a targeted manner.
The first step, therefore, is not an AI project, but a clean data foundation. The digital machine file maps the installed base in Salesforce using an object-oriented approach—including serial numbers, components, lifecycle, and links to Service, Sales, and Assets. Only this structure makes the installed base addressable in the first place.
Why the Aftermarket Is Key to Competitiveness
In the field of serial machine manufacturing, competition is increasingly shifting from new business to the aftermarket. New machines require explanation and are price-sensitive, whereas the service business delivers more stable margins and recurring revenue over the entire life cycle of a system. Companies that systematically focus on this part of the business become less dependent on economic fluctuations in new business.
The prerequisite is to eliminate blind spots. As long as no one can reliably determine which systems are no longer covered by warranty, which components are nearing the end of their service life, or where an above-average number of malfunctions occur, the aftermarket will remain a matter of chance rather than strategy. A structured, interconnected installed base answers precisely these questions—and turns scattered service data into a predictable source of revenue.
Not sure exactly how comprehensive your installed base data is?
An Installed Base Assessment quickly provides clarity on your data and potential.
→ Learn more about the assessment
From a Machine to a Source of Revenue
Once the installed base has been systematically mapped, specific service models can be derived from it. Three levers are particularly effective in mechanical engineering.
Predictive Maintenance and Remote Support
Connected IoT data provides visibility into a machine’s condition before a failure occurs. Sensors report anomalies, and the system automatically creates a service ticket and notifies the responsible technician. This reduces unplanned downtime and shifts service from a reactive approach to a predictable service model.
The value is not derived from the sensor data alone, but from its integration with the machine’s records. A single temperature reading means little on its own; when viewed in the context of the model series, configuration, and maintenance history, it becomes a reliable warning signal. It is this integration that distinguishes predictive maintenance from mere threshold monitoring, which triggers an alarm at every deviation and overwhelms the service team with false alarms.
Remote support complements this: Many issues can be diagnosed remotely or resolved via a firmware update, without the need for an on-site visit. Through integration with Salesforce, remote maintenance is initiated directly from the service ticket; the device ID is transferred, and the session is documented. This shortens resolution time, saves on travel costs, and increases the first-contact resolution rate—especially for customers with facilities located around the world.
Service Sales from the Installed Base
A structured installed base is the foundation for targeted service campaigns. By segmenting the base by age, usage, or region, spare parts needs, maintenance intervals, and upgrade opportunities can be automatically identified and translated into service offers.
The difference from traditional sales lies in the trigger: It is not a fixed campaign calendar, but a real-time data signal that initiates the activity. If the warranty for a product series expires in three months, the system generates a notification for a maintenance contract offer. When a component reaches its typical service life, a spare part or retrofit offer is prepared. If certain malfunctions occur frequently in a product series, an upgrade can be proactively offered. Because these triggers are linked to asset, opportunity, and lifecycle data, the offer reaches the right customer at the right time. The article shows how this can be used to build a systematic sales pipeline Service-Sales Campaigns.
Self-Service and Customer Portals
Through a customer portal , customers can access their machine files, documentation, and spare parts orders—around the clock. This significantly reduces the workload on the back-office staff while also creating a digital sales channel for service products. The head of order processing, in particular—who handles the majority of spare parts requests manually—gains back valuable capacity here.
A typical scenario
A typical process in serial machine manufacturing illustrates how these factors interact. A manufacturer supports several thousand machines in the field. The installed base is recorded in the digital machine file, and the machines transmit operational data. Across multiple locations, a particular model series shows rising vibration levels in a specific component. The system recognizes the pattern, generates prioritized service cases for the affected machines, and notifies the service department. At the same time, it suggests preventive maintenance to the affected customers—before downtime occurs. A maintenance signal thus simultaneously triggers a service call and a quote. No individual case is overlooked because the analysis covers the entire installed base, rather than relying on the memory of individual technicians.
Salesforce as a service hub
For these models to work together, a platform is needed that connects customer data, assets, and service processes. Salesforce fulfills this role as a service hub: Field Service connects customers, field service teams, and assets on a single platform, automates work order assignment, and consolidates service metrics. The Experience Cloud enables the creation of portals, while the Manufacturing Cloud allows service processes to be integrated with ERP data.
The real benefit lies in bringing together previously separate data silos. As long as sales, service, and order processing operate in separate systems, this leads to data disconnects, duplicate entries, and an incomplete view of the customer. A 360° view in Salesforce consolidates asset information, service history, contracts, and—via the integration—IoT metrics all in one place. When a service representative opens a case, they can immediately see which piece of equipment is involved, what components are installed, and what happened most recently—all without switching between systems.
For mass-production manufacturers involved in manufacturing, the Manufacturing Cloud supplements this view by linking it to ERP and order data, thereby integrating service context and material flow. This transforms individual tools into a seamless process chain, from the customer’s request to the delivery of replacement parts.
logicline builds on this platform and enhances it with industry-specific modules—self-service portals, spare parts web shops, and the digital machine file with IoT connectivity. Proven partner solutions are seamlessly integrated: TeamViewer for remote support and Empolis Service Express for knowledge management. logicline helped develop the Salesforce integration for both solutions.
From Networking to Decision-Making
Connected data is a prerequisite, but not the end goal. True service quality is determined where data is transformed into informed decisions: during triage, diagnosis, claims, and warranty. This is exactly where Service Decision Intelligence (SDI) —the intelligence layer that connects fragmented data from ERP, Salesforce, IoT, and documentation and empowers AI agents to make reliable service decisions. Every recommendation includes its sources and indicates its level of confidence; the AI runs on the customer’s infrastructure.
The difference from a generic AI assistant lies in its grounding in the mechanical engineering context. SDI does not work solely on documents; rather, it understands the data model of mechanical engineering: assets, serial numbers, error codes by model series, telemetry, and case history. It can identify patterns across multiple systems and test a hypothesis even against contradictory data, rather than simply confirming the first explanation that comes to mind. The result is not a list of matches, but a decision-making basis anchored in the specific service case, which a human can review and take responsibility for.
This sequence follows the logicline stage model:
- Digitization: Map the installed base in a structured manner within the digital machine file.
- Connect: Integrate portals, IoT, and processes seamlessly within Salesforce.
- Decision-Making: Use SDI to make informed service decisions with source citations.
- Automation: Performing defined service tasks in a software-like manner (Outlook).
Each step provides independent value and is a prerequisite for the next. Without structured data, there is nothing to link; without linked data, there can be no sound decision.
Claims and Warranty as a Specific Use Case
The value of decision intelligence is particularly evident in warranty and claims processing. Whether a warranty claim is valid depends on the system’s configuration, its usage, the error history, and the terms of the contract—information that is stored in various systems. Today, service representatives compile this information manually, often under time pressure. SDI connects these sources and provides a well-reasoned assessment, complete with evidence to support it. Processing becomes faster, decisions are more transparent, and valid and invalid claims can be more clearly distinguished. Humans continue to make the final decision, but on a reliable basis rather than based on gut instinct.
Recurring Service Revenue and New Business Models
A well-maintained installed base is not only the foundation for individual service calls, but also for predictable, recurring revenue. Maintenance contracts, spare parts subscriptions, and condition-based service offerings can be calculated and implemented in a targeted manner based on real usage data. Instead of billing each service call individually, this creates a continuous stream of revenue that also strengthens customer loyalty.
Looking ahead, this path leads to usage- and results-based models, in which it is no longer the machine that is sold, but rather the guaranteed availability or the success of the service provided. Such models require reliable data and decision intelligence—exactly what stages one through three build up. Those who structure their installed base today are laying the foundation for the service business models of tomorrow.
Prerequisites for Success
Whether the digitization of service is successful depends less on individual tools than on three fundamental principles.
Data quality. The installed base must be fully and systematically mapped in order for IoT data and AI to realize their full potential. An Installed Base Assessment identifies gaps before they become bottlenecks.
System compatibility. ERP systems, maintenance software, and production equipment must communicate with the platform. Standardized architectural blueprints and open interfaces ensure that the integration remains maintainable.
Data Sovereignty and Compliance. Service data contains technical expertise and customer context. The GDPR and the EU AI Act, which takes effect on August 2, 2026, require traceability and control. An architecture that runs AI on its own infrastructure and provides sources for every recommendation meets these requirements from the outset.
Overview: Building Blocks and Their Benefits
| Module | Benefit | Impact on service revenue |
|---|---|---|
| Digital Machine File | Structured and up-to-date installed base | Foundation for targeted service sales |
| IoT Integration | Real-time status data, predictive maintenance | Proactive service offerings instead of reactive ones |
| Remote Support | Remote Diagnosis Directly from the Service Case | Fewer on-site visits, higher first-time fix rate |
| Self-Service Portal | Customers resolve issues on their own | Digital channel for replacement parts, reducing the workload on internal staff |
| Service Decision Intelligence | Well-Informed Decisions with Source Citation | Faster triage, fewer false alarms |
Introduce it gradually rather than all at once
Digitizing the installed base doesn’t have to be a large-scale project with an uncertain outcome. It makes sense to start small, with quick, tangible benefits: a product line or a plant where the value becomes apparent before expanding the rollout.
A proven starting point is an assessment of the current situation. An Installed Base Assessment clarifies what data is available, where gaps exist, and which use case will yield the fastest return. Often, this involves the structured mapping of the installed base itself, followed by an initial portal or an IoT connection for a critical product line. Building on this foundation, service-sales triggers and, later, decision intelligence can be added.
It is crucial to involve the relevant stakeholders early on—from the service manager to the back-office staff to senior management. Even the best technical solution will be ineffective if the teams don’t embrace it. By starting small, measuring the benefits, and expanding gradually, you can keep effort and risk manageable and maintain control over the investment.
Conclusion
The installed base becomes a driver of growth when it is systematically captured, connected, and leveraged to support informed decisions. Salesforce serves as a service hub that brings together customer data, assets, and processes; SDI uses this information to make sound service decisions. This process can be approached step by step—each stage pays off on its own.
It’s easy to determine where you stand today and where the greatest leverage lies:
- Review the data: An Installed Base Assessment shows how comprehensively your installed base has been captured and where revenue potential lies untapped.
- Discuss the process: In a no-obligation initial consultation , we’ll determine which level will be most beneficial for you to start with.
FAQs
Why is the installed base so important in mechanical engineering?
The installed base—all machines and systems in the field—is the foundation for long-term, recurring service revenue. Those who systematically track and digitally connect this data can use it to develop targeted predictive maintenance, spare parts sales, remote support, and upgrade offerings. However, as long as the data remains scattered, the revenue potential in the aftermarket remains largely untapped.
How Does IoT Data in Salesforce Boost Service Revenue?
Connected IoT data provides real-time visibility into a system’s condition. Maintenance can be planned proactively, reducing unplanned downtime. Above all, however, condition data translates into specific service opportunities: When a component reaches the end of its service life or malfunctions become frequent, a notification is automatically generated for a suitable service or replacement part offer—proactive rather than reactive.
How does Salesforce, as a service hub, support service processes?
Salesforce brings together previously separate data sources: asset information, service history, contracts, and—via the integration—IoT metrics, all in one place. This 360° view speeds up case handling because service representatives can immediately see which piece of equipment is involved and what happened most recently. Field Service, Experience Cloud, and the Manufacturing Cloud connect field service teams, customer portals, and ERP data into a seamless process chain.
What challenges are involved in digitizing the installed base?
The biggest hurdle is data quality: The installed base must be fully and systematically documented so that IoT and AI can deliver their full value. Other challenges include integrating existing ERP and maintenance systems via standardized interfaces, ensuring IT security at the OT-IT interface, and engaging the teams. A phased rollout—starting with a single product line or a single plant—keeps effort and risk manageable.
How can AI-driven service decisions be made transparent and legally sound?
As soon as AI supports decisions such as triage, diagnosis, or warranty reviews, traceability and data sovereignty become essential. Service Decision Intelligence (SDI) provides each recommendation with a source reference and a confidence assessment and runs on the customer’s infrastructure. This ensures that the requirements of the GDPR and the EU AI Act (effective August 2, 2026) are built in from the outset, allowing humans to make decisions based on a robust foundation.