Introduction: Overcoming the Service Paradox
As manufacturers transition from selling standalone hardware to offering integrated Product-Service Systems (PSS)—such as heavy machinery bundled with maintenance and financing—they often encounter the "service paradox." Despite increased investment in services, profits can stagnate or drop due to the sheer complexity of multi-actor collaboration. When hardware manufacturers, software developers, and service providers work in silos, the resulting components often fail to integrate seamlessly, leading to costly redesign loops and delayed time-to-market.
This research proposes a structured framework to mitigate these challenges by applying platform design and modular technology to PSS development. By treating services and physical components as interoperable modules, organizations can co-create customizable solutions more efficiently while maintaining a core set of common assets.
Methodology: A Three-Phase Integrated Approach
The proposed framework organizes PSS development into three distinct phases, utilizing established engineering tools like the Kano model, Axiomatic Design, and Service Blueprinting to bridge the gap between physical products and intangible services.
Phase 1: Function Determination and Mapping
The initial phase focuses on aligning technical functions with customer needs. The Kano model classifies requirements into basic, expectable, and adjunctive values. Simultaneously, physical products are decomposed via Axiomatic Design, while services are mapped using Service Blueprinting.
A critical innovation in this phase is the Mapping Matrix. This tool maps existing product and service functions against identified customer values to pinpoint redundancies or gaps. Unlike traditional product design where redundancy is avoided, PSS redundancy can be strategic—for example, offering both an automated sensor (product function) and manual inspection (service function) to enhance reliability.
Phase 2: Modularization and Interface Design
In the second phase, the "closeness" of service activities is calculated using a Correlation Integration Analysis Matrix, considering functional, class, and process correlations. Highly correlated activities are clustered into discrete modules (e.g., "Training" or "Maintenance").
Central to this phase is Interface Design. The framework defines three interface types: product-to-product, service-to-service, and the critical product-to-service interface. Standardizing these interfaces ensures that physical machines can effectively communicate status data to service software, which the authors argue is the "secret sauce" of a successful PSS platform.
Phase 3: Assignment and Integration
Finally, modules are assigned to partners based on their specific capabilities in terms of lead time, cost, and quality. A system integrator then configures these modules into tailored solutions for specific market niches.
Case Study: Engineering Machinery
The framework was validated through a case study with "Company H," a major crane manufacturer. The study analyzed 28 crane types and 45 service offerings. By applying the modular approach, the company successfully partitioned its 45 services into 8 core modules. These were categorized into "Basic" (essential), "Indispensable" (expected), and "Optional" (premium) portfolios.
While the initial development costs were high, the pilot test showed exceptional user acceptance and provided a strategic advantage through a flexible, modular platform that reduced the need for future redesigns.
Key Insights and Future Directions
A primary takeaway is the shift toward Service-as-a-Module. Rigorously defining services like physical parts allows them to be upgraded or swapped without destabilizing the entire system. However, scalability remains a challenge; as systems grow, manual calculation of correlation matrices becomes impractical. Future research will explore Complex Network Theory to automate module clustering in large-scale, interconnected PSS environments.
Summary updated