An Ontology for Product-Service Systems

Industries are transforming their business strategy from a product-centric to a more service-centric nature by bundling products and services into integrated solutions to enhance the relationship between their customers. Since Product- Service Systems design research is currently at a rudimentary stage, the development of a robust ontology for this area would be helpful. The advantages of a standardized ontology are that it could help researchers and practitioners to communicate their views without ambiguity and thus encourage the conception and implementation of useful methods and tools. In this paper, an initial structure of a PSS ontology from the design perspective is proposed and evaluated

Understanding new venture market application search processes: A propositional model.

Technology-based ventures are confronted with complex decisions on how to apply their technology platform in highly uncertain and ambiguous market environments. Based on four case studies, a dynamic decision model is developed in which we highlight the similarities between the search and learning processes in venture development contexts and in new product development contexts. This entrepreneurial search and learning process is understood as consisting of sequences of episodes – characterized by uncertainty and ambiguity - and scripts – i.e. approaches to market application search. The model implies that a venture's adaptability - i.e. its ability to move efficiently and effectively between these episodes and their related scripts - influences its survival.Case studies; Decision; Decisions; Learning; Market; Model; Processes; Product; Product development; Research; Sequences; Similarity; Studies; Technology; Uncertainty;

Challenges in Product Lifecycle Management - Evidence from the Automotive Supply Industry

Against the backdrop of a steady shift in value added from the automotive original equipment manufacturers to the automotive suppliers, product lifecycle management in the automotive supply industry gains importance. Prior literature has acknowledged product lifecycle management as paradigm for manufacturing industries, yet little is known about the specific characteristics and boundary conditions in this emerging industry branch. Grounded on extensive empirical evidence from a typical and revelatory case study at a global leader for mechatronic assemblies, this exploratory paper identifies, visualizes, and discusses challenges in product lifecycle management in the automotive supply industry. With the limitation of an exploratory and interpretive single-case study approach, we (1) supply scholars and practitioners with grounded, stakeholder-related insights and (2) link the field of product lifecycle management with information systems

The Impact of Requirements on Systems Development Speed: A Multiple-Case Study in Automotive

Automotive\ua0manufacturers have historically adopted rigid\ua0requirements\ua0engineering processes. This allowed them to meet safety-critical\ua0requirements\ua0when producing\ua0a\ua0highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the\ua0automotive\ua0industry.\ua0In\ua0particular, the needs of improving\ua0development\ua0speed\ua0are increasingly pushing companies\ua0in\ua0this domain toward new ways of developing software.\ua0In\ua0this paper, we investigate how the goal to increase\ua0development\ua0speed\ua0impacts how\ua0requirements\ua0are managed\ua0in\ua0the\ua0automotive\ua0domain. We start from\ua0a\ua0manager perspective, which we then complement with\ua0a\ua0more general perspective. We used\ua0a\ua0qualitative\ua0multiple-case\ua0study, organized\ua0in\ua0two steps.\ua0In\ua0the first step, we had 20 semi-structured interviews, at two\ua0automotive\ua0manufacturers. Our sampling strategy focuses on manager roles, complemented with technical specialists.\ua0In\ua0the second step, we validated our results with 12 more interviews, covering nine additional respondents and three recurring from the first step.\ua0In\ua0addition to validating our qualitative model, the second step of interviews broadens our perspective with technical experts and change managers. Our respondents indicate and rank six aspects of the current\ua0requirements\ua0engineering approach that\ua0impact\ua0development\ua0speed. These aspects include the negative\ua0impact\ua0of\ua0a\ua0requirements\ua0style dominated by safety concerns as well as decomposition of\ua0requirements\ua0over many levels of abstraction. Furthermore, the use of\ua0requirements\ua0as part of legal contracts with suppliers is seen as hindering fast collaboration. Six additional suggestions for potential improvements include domain-specific tooling, model-based\ua0requirements, test automation, and\ua0a\ua0combination of lightweight upfront\ua0requirements\ua0engineering preceding\ua0development\ua0with precise specifications post-development. Out of these 12 aspects, seven can likely be addressed as part of an ongoing agile transformation. We offer an empirical account of expectations and needs for new\ua0requirements\ua0engineering approaches\ua0in\ua0the\ua0automotive\ua0domain, necessary to coordinate hundreds of collaborating organizations developing software-intensive and potentially safety-critical\ua0systems

Remanufacturing and product design: designing for the 7th generation

The following is taken directly from the research report. This report investigates Design for Remanufacture in terms of both detailed product design and the business context in which Design for Remanufacture may operate. Key Study Objectives • To understand the link between design and remanufacture • To understand how Design for Remanufacture can lead to increased innovation and Sustainable Development (SD) • To identify proactive strategies to further Design for Remanufactur

Modelling for data management & exchange in Concurrent Engineering - A case study of civil aircraft assembly line

This research aims to improve the dataflow performance of the Concurrent Engineering (CE) practice in the detail design stage of the aircraft Assembly Line (AL) in the C919 aircraft project. As the final integrator of the aircraft, Shanghai Aircraft Manufacturing Company Ltd. (SAMC) is responsible for developing the AL with global suppliers. Although CE has been implemented in AL projects to shorten lead time, reduce development cost and improve design quality, the lack of experience and insufficient infrastructure may lead to many challenges in cooperation with distributed suppliers, especially regarding data management/exchange and workflow control. In this research, the particular CE environment and activities in SAMC AL projects were investigated. By assessing the CE performance and benchmarking, the improvement opportunities are identified, and then an activity-oriented workflow and dataflow model is established by decomposing the work process to detail levels. Based on this model, a Product Data Management (PDM) based support platform is proposed to facilitate data management/exchange in dynamic workflow to improve work efficiency and interoperability. This solution is mocked-up on the Siemens Teamcenter 8.1 PLM(Product Lifecycle Management) software and its feasibility is checked. The mock-up is evaluated by SAMC experts and suppliers. The feedback shows the acceptance of the model by experts and the urgency of improving data/work flow design before PLM implementing. The result of this research is useful for enterprises in similar environments transiting from pre-PLM to implementing PLM and who wanting to strengthen CE in the new product development

Creating a Flexible IT Organization

In 2004, the nearly billion dollar software company Business Objects undertook a major acquisition. Now, the business is looking to improve operations and position itself as a major player in the business intelligence market. This paper focuses on how Business Objects can create a flexible IT organization that can evolve with changing corporate strategies in today\u27s competitive markets. The analysis section completes a SWOT analysis and reviews business strategy, organizational strategy and IT strategy. The analysis concludes that increased legislated process and broad geographic reach in a truly flexible IT organization are not feasible. However, action can be taken to balance control and flexibility that will make IT an enabler for the business. Recommendations include appointment of a CIO, hybrid organizational structure and establishment of performance metrics. As part of implementation strategy, a gradual change management approach is recommended with a dedicated team to monitor progress and adapt the plan as the environment evolves

A Case Study of the Architecture Business Cycle for an In-Vehicle Software Architecture

This paper presents the theoretical and practical benefits from a case study using a the Architecture Business Cycle to understand the management of software architecture at an automotive manufacturer. The study was done to prepare for architectural changes driven by new technology and in the automotive business environment. Our results show that the architecture business cycle worked well in defining the theoretical context for the study after some modifications; the architecture had to be precisely defined in the interview situation to gain more useful data rather than broad generalisations. Further contributions of the study were a deeper understanding of role of the architecture and it's position among other artefacts in the organisation, and an increased focus on architectural issues in management meetings. The study also indirectly affected a subsequent re-organisation