📘 Resource Overview & Documentation Details

You are viewing the technical directory listing for Data-Driven Product-Service Systems: A Design Method. This engineering resource is curated under our Digital manufacturing division to support automation specialists, control systems engineers, and manufacturing technicians looking for verified reference materials.

🔍 Contextual Abstract & Technical Scope

Share Summary:LinkedInEmail

Data-driven product-service systems (PSS) connect the design of an industrial product and its associated services with information gathered during real-world delivery. For manufacturers offering equipment alongside maintenance or other services, this creates a structured way to use operational experience—not only initial customer feedback—to identify needs and improve future PSS decisions. The 4DPSS methodology brings these activities together in a four-phase cycle.

Rather than treating product design, service delivery, and performance monitoring as separate efforts, 4DPSS links them through the collection and analysis of operational data. Its aim is to help teams recognize problems in products and service processes, then use those findings to inform subsequent design work. The methodology is presented as a theoretical framework; its complete implementation and validation in a single case study remain future work.

Why connect product-service design with operational data?

A Product-Service System combines product and service elements in an offering. Designing one requires teams to consider customer needs, product characteristics, service processes, and the value the overall solution is intended to provide. Those considerations involve different functions and disciplines, making it important to share information and understand the implications of design choices across the system.

In practice, companies may have information from maintenance and other delivery activities, but not a consistent way to manage and use it for design decisions. The 4DPSS approach addresses this gap by treating data collection, management, and analysis as part of the PSS lifecycle. Operational findings can inform decisions at two levels: day-to-day service delivery and the broader design of the product-service offering.

The methodology combines four perspectives: organizing the design process, evaluating value across multiple dimensions, supporting collaborative engineering decisions through visualization, and incorporating data from operations. In this context, models can act as shared reference points—or boundary objects—for cross-functional discussions, helping participants compare assumptions and consider trade-offs.

The four phases of data-driven product-service systems design

1. Identify needs

Needs can come from customers, products, or services. Customer needs may be identified through direct dialogue, interviews, surveys, or feedback. Product and service needs can also emerge from monitoring operational data, such as maintenance records and information about delivery activities.

Teams prioritize identified needs according to the criticality of the problem, which may be associated with the time or cost required to address it. Bringing operational findings into this phase broadens the evidence used to define what the PSS should address. Needs are not based solely on designers’ experience or direct customer input; they can also reflect issues observed in the field.

2. Generate concepts and design

The prioritized needs inform PSS concept development. Teams can update the value creation strategy and assess the potential contribution of new technologies. They then consider possible changes to a baseline design and explore alternatives using simulation models.

For complex design problems where simulations may take substantial time, a Design of Experiments approach can generate a set of simulation results. Those results can be used to build surrogate models that approximate the design space, supporting exploration of alternatives. Models and visualizations can then support collaborative decision-making, particularly when the team must weigh product and service considerations together.

This phase also defines how data should be collected and analyzed during PSS delivery. Planning those activities during design helps establish what information is needed from the product and service components and how it may later support operational decisions and future design work.

3. Implement the PSS

Implementation focuses on collecting field data and using it to support operational decisions during delivery. Relevant information can come from product and service activities and may also include general customer information. The objective is to build a usable body of information that supports service-delivery decisions.

Historical and aggregated data can help teams consider operational choices using information from both sides of the PSS. The methodology describes optimization models as one possible support for cross-analysis and service-delivery decisions. The usefulness of this phase depends in part on the collection and analysis strategies established during concept generation and design.

4. Monitor performance

Monitoring uses aggregated information from implementation to identify PSS performance issues and operational criticalities. Analysis can examine product-related and service-related data. For example, repeated failures of the same component may indicate a product design issue. Maintenance information may also reveal unnecessary process activities or unsuitable tools in service delivery.

Findings from monitoring feed back into needs identification, restarting the cycle. This connection is central to 4DPSS: operational data is not collected only to manage current delivery, but is also considered a potential input to future PSS design and process improvement.

Practical considerations for industrial teams

For manufacturers and system integrators, the framework highlights several questions to address when connecting maintenance operations with design:

  • What needs to be learned? Define the product, service, or customer questions that data collection should help answer.
  • What information is available? Identify relevant operational sources and consider how information will be managed and analyzed.
  • How will findings affect decisions? Connect analysis to maintenance choices, service-process adjustments, or design reviews.
  • How will teams interpret results together? Use models and visualizations to support discussion across functions and disciplines.

The framework does not prescribe a single data source or analytical technique for every situation. Instead, it emphasizes aligning the inputs and outputs of each phase so that information gathered during delivery can be interpreted and reused appropriately.

Conclusion: close the loop between delivery and design

The 4DPSS methodology offers a lifecycle view of data-driven product-service systems: identify needs, develop and evaluate concepts, implement delivery, and monitor results. Its practical implication is that operational data can inform both immediate service decisions and longer-term product-service design—provided collection, analysis, and decision-making are connected across phases.

Because the methodology has not been implemented and validated as a whole in one case study, it should be understood as a proposed framework rather than a proven end-to-end deployment model. For industrial teams, its central principle remains useful for planning: treat field information as a potential design input, and establish clear links between what operations capture and what design and service teams need to decide.

Access Official Technical PDF