Servitization and the Product-Service System (PSS)

1. Overview

A. Definition

Servitization is the strategic process by which a manufacturing firm transitions from merely selling a physical product to a business model that delivers integrated value combining services, solutions, and outcomes with the product. The resulting Product-Service System (PSS) bundles product and service into a single package, satisfying not the customer's "ownership" but their "use" and "outcome."

The fundamental insight of servitization is that "customers do not buy the product itself but the result the product produces." An airline does not want to own an engine; it wants reliable thrust and uptime. A construction firm does not want to own a drill; it wants "a hole drilled on schedule." When manufacturing clings only to competition over product function and performance, it eventually falls into the price war of commoditization; servitization, by contrast, uses the product as a medium to take responsibility for the customer's operational outcomes, life-cycle cost, and even risk, shifting the axis of competition from "product spec" to "customer outcome."

This shift also changes the revenue structure. Revenue centered on one-off sales (transactions) fluctuates with the economy and replacement cycles, but servitization creates recurring revenue through maintenance, subscription, and outcome fees, smoothing revenue and extending the customer relationship over the long term. In practice, the service, consumable, and operating revenue generated across a product's entire life cycle often amounts to several times the initial product sale, and capturing this "aftermarket" is a core motivation for servitization.

B. Background and Necessity

The concept of servitization was first proposed by Vandermerwe and Rada in 1988, but it spread rapidly after the 2010s in tandem with digital transformation (DX). As the cost of sensors and communications plummeted, it became economical to embed IoT in products to observe and control their state remotely, allowing a manufacturer to keep a "connection" to a product even after it is sold. In other words, digital technology completed the technical precondition for servitization.

On the necessity side, first, there is intensifying commoditization and low-price competition in advanced manufacturing. As manufacturers in emerging markets supply products of similar quality at low prices, incumbent manufacturers find it hard to protect differentiation and margins with the product alone. Second, customer demand has shifted from "ownership" to "use and outcome." There is growing demand to convert capital expenditure (CapEx) into operating expense (OpEx) for financial flexibility and to pass the burden of maintenance to the supplier. Third, as the pressure of sustainability and the circular economy has grown, use- and outcome-based models premised on recovery, remanufacturing, and reuse — rather than selling a product and ending the relationship — have come to align with environmental regulation and ESG demands.

Thus servitization is not merely "strengthening after-sales service" but a business model innovation that transforms a firm's value proposition, revenue model, operating capability, and organizational culture together. From the Professional Engineer's perspective, the core task becomes designing the digital platform, data governance, and IoT architecture that make this transition possible.

2. Types of Servitization and the Shift in the Value Chain

Servitization must be understood as a continuous spectrum running from "product-centric" to "outcome-centric." The overall structure diagram below shows how the three PSS types shift along the customer's ownership, risk, and center of gravity of value. The further right one moves, the more the product's ownership remains with the supplier, the customer buys only "outcomes," and the responsibility and potential revenue the manufacturer bears grow together.

flowchart LR
  subgraph PO["Product-oriented"]
    P1["Product sale + add-on services (maintenance·training·warranty)"]
  end
  subgraph UO["Use-oriented"]
    P2["Ownership stays with supplier (lease·rental·sharing)"]
  end
  subgraph RO["Result-oriented"]
    P3["Selling outcome·result (uptime·output guaranteed)"]
  end
  PO --> UO --> RO
  START["Product sale"] -.->|"service share rises"| PO
  RO -.->|"customer-outcome responsibility rises"| END["Integrated solution"]
  style PO fill:#e8f0fe,stroke:#2f6fed,stroke-width:1px
  style UO fill:#eafbea,stroke:#2f9e44,stroke-width:1px
  style RO fill:#fef3e8,stroke:#ed8f2f,stroke-width:2px

The three types are not disconnected options but rather a maturity path up which a firm climbs in stages as it accumulates capability and data. Each type is examined below with its principle and cases.

A. Product-oriented PSS — the stage of "adding" services to a product

In product-oriented PSS, product ownership is still transferred to the customer, but services that support that product's life cycle are provided alongside it. Installation, training, extended warranty, preventive-maintenance contracts, and consumable supply are representative, and many manufacturers already perform these in the form of an "after-sales service division." The core of this stage is to maintain a post-sale customer touchpoint and secure additional revenue streams and customer data.

Even at this stage, digital technology greatly raises value. For example, attaching sensors to a product to provide a predictive maintenance service that detects fault signs in advance reduces the customer's unplanned downtime while raising the added value of the maintenance contract. However, because ownership and operating risk still lie with the customer, the responsibility the manufacturer bears is limited.

The practical implication of the product-oriented stage is that it is a "beachhead for servicing the business." The operating data, fault histories, and customer usage patterns accumulated at this stage become the assets needed to climb to the higher stages (use- and outcome-oriented). Conversely, jumping straight to outcome-oriented without this data foundation risks loss, because the supplier cannot reflect the risk it assumes in the price.

B. Use-oriented PSS — from ownership to "use"

In use-oriented PSS, product ownership stays with the supplier and the customer buys the "right to use" the product. Lease, rental, subscription, sharing, and pay-per-use belong here. The customer uses the resource when needed without an upfront investment burden, while the supplier maximizes asset utilization by repeatedly leasing one product to multiple customers or charging by usage.

The principled change in this model is that the supplier's interest reverses from "selling a lot" to "being used long and well." Holding ownership, the supplier profits the longer the product operates without failure, so it has an incentive to maximize durability, maintenance efficiency, and energy efficiency. This promotes a design philosophy opposite to planned obsolescence and connects naturally with the circular economy.

A representative case is the click-charge model in the copier industry. Companies such as Xerox, rather than selling copiers, installed them and charged by the number of pages printed (on the order of a few units of currency per page). The customer escaped the burden of equipment purchase and maintenance, and the supplier secured recurring revenue including toner, paper, and servicing. However, because the use-oriented model keeps the asset on the supplier's balance sheet, the supplier must bear the capital burden and residual-value risk, and a usage-metering and billing infrastructure must necessarily back it.

The use-oriented stage also brings a new management metric — "asset utilization" — to the fore. Because the supplier's unit revenue rises the more it re-leases one asset across multiple customers and time slots, a scheduling, redeployment, and reservation platform that minimizes idle assets determines profitability. For example, in a construction-heavy-equipment sharing model, raising utilization from 40% to 60% lets the same asset earn 50% more revenue, so the digital reservation and logistics system that raises asset turnover itself becomes a core competitive edge. In this way, the use-oriented model demands platform-operating capability as much as product capability.

C. Result-oriented PSS — the stage of selling the "result"

Result-oriented PSS is the highest stage of servitization; even the product does not appear in the foreground, and the customer-desired outcome·result itself is transacted. The customer buys not equipment or usage but a result such as "guaranteed uptime," "output per unit," or "cost reduced," and the supplier takes responsibility for every means of achieving that result (equipment choice, operation, maintenance, replacement). This is called an outcome-based / performance-based contract.

At this stage the interests of supplier and customer align completely. The supplier is rewarded only when it produces the outcome, so the more efficiently it designs and operates the product, the greater its profit. Conversely, in case of underperformance the supplier must bear a penalty or reduced revenue, so it must hold deep data and predictive capability about the product and operation, along with the financial strength to absorb risk. Information asymmetry and measurability (how to objectively measure and agree on the outcome) become the core issues of contract design.

The most famous case is Rolls-Royce's Power-by-the-Hour (TotalCare). Instead of buying engines, airlines pay a "fee per engine flight-hour," and Rolls-Royce remotely monitors engine condition and takes responsibility for maintenance·replacement, selling "guaranteed thrust and uptime." For this model to hold, the capability to analyze in real time the sensor data coming from thousands of engines, predict faults in advance, and perform maintenance at the optimal time to maximize uptime is essential. That is, an outcome-oriented contract is sustained not by the "contract document" but by "data·analysis capability," and this becomes an entry barrier that latecomer competitors cannot easily imitate.

The table below organizes the differences among the three types from the perspectives of ownership, billing, and risk (an aid to the prose explanation).

Category	Product-oriented	Use-oriented	Result-oriented
What the customer buys	Product + support service	Right to use the product	Outcome·result
Ownership	Customer	Supplier	Supplier
Billing method	Sale price + service fee	Lease·usage charge	Outcome·result-unit charge
Supplier risk	Low	Medium (asset·residual value)	High (underperformance penalty)
Required capability	Service operation	Usage metering·billing	Data·prediction·financial strength
Representative case	Extended warranty·predictive maintenance	Xerox click-charge·equipment rental	Rolls-Royce PBH

3. The Realization Architecture and Technology Foundation of Servitization

For outcome-oriented servitization to be possible, a digital closed-loop architecture is needed that collects and analyzes real-time data from sold products and feeds it back into service, billing, and design improvement. The detailed architecture diagram below shows the circular structure in which data generated at the product (Thing) passes through the platform to outcome·billing and feeds back into product operation and design.

flowchart TB
  subgraph EDGE["Field layer (Edge)"]
    T["Connected product (sensors·actuators)"]
    G["Edge gateway (collect·preprocess)"]
  end
  subgraph PLAT["Digital platform layer"]
    IOT["IoT platform (connectivity·device mgmt)"]
    DT["Digital twin (state replica·simulation)"]
    AN["AI analytics (predictive maint·optimization)"]
  end
  subgraph SVC["Service·business layer"]
    BILL["Usage·outcome billing"]
    SLA["SLA·outcome monitoring"]
    DESIGN["Design·R&D feedback"]
  end
  T --> G --> IOT --> DT --> AN
  AN --> SLA --> BILL
  AN -->|"fault prediction·remote action"| T
  AN -->|"usage-data feedback"| DESIGN --> T
  style PLAT fill:#e8f0fe,stroke:#2f6fed,stroke-width:1px
  style SVC fill:#fef3e8,stroke:#ed8f2f,stroke-width:1px

Each layer of this architecture plays a different role and is organically connected. The connected product of the field layer measures operating state (temperature, vibration, pressure, operating time, etc.) with sensors, and the edge gateway preprocesses and compresses the data considering network latency and bandwidth. For example, when hundreds of sensors generate thousands of events per second, transmitting all the raw data is difficult, so a design that selects and uploads only the anomalous intervals at the edge is important.

The core of the platform layer is the digital twin. Replicating the state of the physical product in real time as a virtual model allows estimating wear and life and simulating "what-if" scenarios without actual disassembly. Combined with AI analytics, it predicts faults in advance (predictive maintenance) and optimizes operating parameters. In an outcome-oriented contract this prediction accuracy is directly tied to revenue, because many false positives (judging normal as faulty) cause unnecessary maintenance cost, while many false negatives (missing a fault) cause an outcome penalty.

In the service·business layer, the collected and analyzed data leads to usage·outcome billing and SLA monitoring. It objectively measures outcome indicators such as flight-hours, uptime, and output, compares them against contract terms, and automatically generates invoices. Furthermore, field operating data feeds back into R&D to improve the design of the next-generation product, and this data feedback loop is precisely the decisive competitive advantage of servitization that cannot be obtained from product sales alone. The foundational technologies that support it include IoT·5G/LPWAN communications, cloud·edge computing, data lakes, subscription-billing systems, and security·authentication frameworks together.

4. Comparison and Application Cases

The difference between traditional product selling and the servitization model appears not merely in "what is sold" but across the organization, revenue, and customer relationship as a whole. In product selling, the customer relationship loosens the moment the transaction completes and revenue depends on the replacement cycle, whereas servitization keeps the relationship going throughout the contract period and smooths revenue. The fundamental reason this difference arises is that the point at which value is attributed differs. A product's value transfers at the point of delivery, but service·outcome value is created cumulatively throughout the period of use, so the supplier cannot help being continuously involved in the customer's success.

Looking at concrete cases makes the implication clear. Rolls-Royce's Power-by-the-Hour converted a large portion of its commercial-aircraft engine revenue into long-term service contracts, turning the volatility of one-off engine sales into stable cash flow spanning decades. Michelin, targeting freight carriers, introduced a "fee per kilometer driven" model instead of selling tires, creating a structure in which retreading and managing tires to be used longer becomes profit itself. Hilti switched from selling power tools to a "fleet management" subscription, so that a construction firm receives, for a fixed monthly fee, always-working tools and guarantees of replacement·repair·loss. All three cases commonly redesigned the incentive structure so that making the product "fail less and be used longer" aligns with the supplier's profit.

In Korea, too, servitization is spreading. Rental-based use-oriented models such as water purifiers and massage chairs have matured, and in industrial air compressors and elevators, predictive-maintenance services based on remote monitoring have taken root. However, climbing to the outcome-oriented stage requires a system that objectively measures and agrees on outcomes and the supplier's capacity to absorb risk, and this part is pointed to as a major challenge blocking the deepening of servitization in Korean manufacturing.

Another implication the cases commonly show is the "servitization paradox." This is the phenomenon in which profitability falls even as the share of service revenue rises, occurring when the operating cost of providing services and the cost of organizational transition exceed the increase in recurring revenue. To overcome it, one must move away from handling services manually for each customer and instead standardize, automate, and scale them with a digital platform. In other words, the profitability of servitization ultimately depends on how efficiently one can produce services "like a factory" with data and platforms.

5. Deep Dive — Latest Trends and Likely Exam Directions

Recently servitization has been expanding into the currents of XaaS (Everything-as-a-Service) and the outcome economy. Outcome-based models are spreading across all industries — not only manufacturing but also farm machinery (equipment-uptime guarantees), lighting (Light-as-a-Service), and aviation·medical equipment — and as generative AI is combined, an "intelligent servitization" that learns from customer usage data to automatically optimize operation is emerging. The combination with the circular economy is also conspicuous: a use·outcome model in which the supplier owns the product structurally promotes product recovery, remanufacturing, and reuse, simultaneously raising ESG performance and resource efficiency.

On the standards·regulation side, the trend of combining digital information with products underpins servitization. As systems that track and disclose a product's life-cycle data spread — like the European Union's Digital Product Passport (DPP) discussion — they naturally mesh with a servitization model in which the manufacturer continues to manage the product after sale. However, because such recent systems·figures change continuously, in an answer it is safer to describe them centered on direction and implication rather than asserting specific years·versions.

For a Professional Engineer second-stage answer, the following composition is effective. (1) Present the definition of servitization and the three PSS types as a spectrum, (2) draw the digital platform·IoT·digital-twin architecture that realizes it as a conceptual diagram, (3) explain the change in revenue·risk structure with concrete cases such as Rolls-Royce·Hilti, and (4) close with Professional Engineer-perspective success factors and challenges such as data governance, outcome measurement, and organizational transition, which shows both depth and balance. It is highly likely to be set in connection with questions asking about "servitization and digital transformation," "platformization of manufacturing," and "IoT-based business models."

6. Considerations and Implications

Servitization is not completed by technology adoption alone; from the Professional Engineer's perspective, the following must be considered comprehensively.

• Application strategy (staged maturity): One should transition in stages — product-oriented → use-oriented → result-oriented — accumulating capability and data. Leaping to an outcome-based contract without data·prediction capability worsens profitability because the supplier cannot reflect the risk in the price. Early on, securing a beachhead with low-risk digital services such as predictive maintenance is realistic.
• Trade-off (risk and financial structure): Servitization smooths revenue, but the supplier takes on asset holding (capital burden) and underperformance risk. The way revenue is recognized also changes from lump-sum sales to period allocation, which can worsen short-term financial indicators, so managing the expectations of executives·investors and redesigning the financial model is essential.
• Data governance and security: Because connected products continuously collect customer operating data, contractual·legal agreement on data ownership, scope of use, and privacy must come first. Also, because a product constantly connected to the network widens the attack surface, OT/IoT security and a secure remote-update framework become preconditions for service reliability.
• Measurability of outcome and contract design: The outcome-oriented model is decided by "how objectively the outcome is measured and agreed." If the measurement criteria, allocation of responsibility, and force-majeure exceptions are not clarified, disputes are frequent. The outcome indicators (uptime, output, etc.) and the penalty·incentive structure must be designed to be verifiable by data.
• Transition of organization·capability·culture: Because a product-centric organization is accustomed to "end at sale" thinking, it must transition to a service-centric organization·evaluation·workforce system that bears long-term responsibility for customer outcomes. Sales must be redefined from closing deals toward customer success, and engineering from spec competition toward life-cycle operation optimization.
• Linkage with sustainability·circular economy: A use·outcome model in which the supplier owns the product structurally induces product recovery, remanufacturing, and reuse, raising resource efficiency and ESG performance. The Professional Engineer must view servitization not only as a revenue model but as part of a sustainability strategy responding to carbon·resource regulation and design it in linkage with a life-cycle data tracking system.
• Linked technologies: Realizing servitization is inseparable from digital capabilities such as IoT·digital twin·AI prediction·cloud/edge·subscription billing·data lake. The Professional Engineer must take the perspective of designing and governing these elements not as individual technologies but as an integrated architecture that underpins the business model.

References

• Vandermerwe, S. & Rada, J., "Servitization of Business: Adding Value by Adding Services" (European Management Journal, 1988): https://www.sciencedirect.com/science/article/abs/pii/0263237388900333
• Tukker, A., "Eight types of product–service system" (Business Strategy and the Environment): https://onlinelibrary.wiley.com/doi/10.1002/bse.414
• Rolls-Royce, "Power-by-the-hour / TotalCare": https://www.rolls-royce.com/products-and-services/civil-aerospace/aftermarket-services.aspx
• Hilti Fleet Management: https://www.hilti.com/content/hilti/W1/US/en/services/tool-services/fleet-management.html
• European Commission, Digital Product Passport (Ecodesign for Sustainable Products Regulation): https://commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/ecodesign-sustainable-products-regulation_en

---

In one line: Servitization is an innovation in which a manufacturer transitions from selling products to selling "use·outcome," realizing the product-oriented→use-oriented→result-oriented PSS spectrum through a closed-loop architecture of IoT·digital twin·AI analytics, where the data·risk·organizational transition that trades recurring revenue for responsibility over customer outcomes decides success or failure.