Product-service systems (PSS) are often presented as an inherently sustainable business model. The argumentation is often based on theoretical considerations, which cite circular economy (CE) characteristics in PSS business models as an explanation. In this paper we examined to what extent positive and negative sustainability effects of PSS could actually be observed, based on use cases. For this purpose, we conducted a systematic literature review and analyzed the statements on sustainability effects based on the triple bottom line approach. We find that positive sustainability effects, especially on the environmental sustainability of PSS, are described disproportionately often, which may be indicating a possible publication bias. In addition, the methods used to derive statements on sustainability effects are very heterogeneous and often unsystematic, making it difficult to compare the described effects. Furthermore, we were able to identify drivers that are particularly often considered in literature to be responsible for sustainability effects. As a result, we were able to derive direct implications for future research in the field of sustainability assessment of PSS.

No abstract

No abstract

In collaborative product development, diverse stakeholders are involved in distributed engineering activities. This situation makes it difficult to ensure, manage, and improve the quality across company boundaries. Therefore, this work determines the characteristics of collaborative engineering which have an influence on the quality of distributed product development. Several interoperability frameworks were analyzed in order to get insights into key areas for collaboration design. Furthermore, a systematic literature review provided the best practices for improvement efforts. The derived quality attributes were condensed and adapted to collaborative product development in the four key areas of organization and processes, data/artifacts, information technology systems and infrastructure, and social factors. This enables product developers to examine their collaborative engineering environment and to identify room for improvement and to enhance quality. A case example of an engineering change order shows a collaborative data flow process, in which the quality attributes may indicate improvement measures.

No abstract