The VR Session Manager: A Tool to Co-Ordinate a Collaborative Product Development Process in a Virtual Environment

Author(s):  
Ralph Stelzer ◽  
Wolfgang Steger ◽  
Dirk Petermann

The paper elucidates a process integration method in which the virtual reality (VR) application moves beyond being just a visualisation tool to functioning as an interface for collaboration. The central module of this system is the so-called session manager. The session manager co-ordinates the collaboration of several authorised individuals and various software tools all working together on one development project. The session manager is at the centre of the product data management (PDM) system managing product structure, product documents and project state. The associated VR system synchronously presents the current state of the project. It is thus possible to visualise changes in geometry, appearance or structure in real time. In this way, VR can be integrated into a heterogeneous system consisting of CAD workstations and simulation applications. Integration is based on a bi-directional link among all applications via the PDM system. Thus, it is possible to use and represent not only the product’s design and structure, but also its non-geometric information using PDM. Additionally, the persons working with it may select product components in VR and assign tasks to workstations or persons, since, in VR, relevant information from the PDM is available.

Author(s):  
Delia Ilie ◽  
Udo Lindemann ◽  
Andreas Kain

During the initial stages of a project, a crucial course is set that can determine the success or failure of the project. During this phase requirements are determined, analyzed and allocated to the corresponding product development phase. Complex products with a high degree of customization require the management of a large amount of information. The prioritization of this information in regard to their time sequence in the product development process has to be analyzed. Interviews conducted in the automotive industry show that the requirement management processes in the early design phases are insufficient and lack solid categorization and prioritization methodologies. This study presents a methodical procedure to improve the allocation of the right information to the right time in the development process. In this methodology, the prioritization of requirements as a function of the degree of cross-linking was achieved through three steps: 1. the evaluation criteria definition, 2. the establishment of a computational procedure, 3. the evaluation of requirements and the calculation of their priority. In the first step, an information prioritization signature was created consisting of a set of relevant information criteria and class structures to allow for the evaluation of the varied spectrum of requirements. In the second step, not only the degree of cross-linking is considered but additionally the types of links between requirements are worked out to allow for prioritization. Finally in the third step, a case study is presented to validate the methodology and provide the reader with an example of how requirements are evaluated and prioritized.


Author(s):  
Javier Pereda ◽  
Mauricio Hincapie ◽  
Arturo Molina

For a rapid configuration of a given product development process, taking into account today unavoidable market’s requirements as is the integrated product, process and manufacturing system development considering their entire lifecycles, in this paper, an enterprise holistic framework, consisting in a three dimensional model, is described to support the model driven architecture (MDA) concept for global product development projects (GPDP). The holistic framework has been established based on the integration of three fundamental areas of research: concurrent engineering (CE), product lifecycle, and enterprise integration engineering (EIE). The integration of these three fields of knowledge, using a 3D holistic framework, generates a solid support for a model driven architecture. As a result, through a 3D matrix, more important elements of the product development process can be combined and modeled following their natural interactions through the project realization. Questions about a global product development project like: What needs to be developed? Who will develop it? Where will be developed? How will be developed? When is being developed? can be generated during the planning and execution of the project but, as part of this research effort, these questions are answered in an organized manner using the proposed enterprise holistic framework. The conceptual model (enterprise holistic framework) for the global product development project was established as a base to capture, store and configure a project including the integration of product, manufacturing process and manufacturing system development considering their entire lifecycles in the enterprise context.


2020 ◽  
Vol 9 (6) ◽  
pp. 2630-2636
Author(s):  
Nora Khaled Al Ghanmi ◽  
Nor Shahida Mohd Jamail

Nowadays, Agile software development practices are being widely adapted all over the world. Scrum is one of the most known Agile models, it satisfies the business needs and put the main focus on the product. One common challenge for the development of customer-facing products is having a good user experience. This paper presents integrating Scrum development process with user experience design flow. In this study, papers relating to the topic of user experience (UX) process integration with Agile development process, how to measure it and how to improve it, from the year 2010 onwards are reviewed. This is to identify how organizations can integrate UX design flow and Scrum development and get the benefits of both. The conducted review identifies a number of limitations in the existing integrations efforts. A proposed process model to resolve these limitations is presented. Along with our experience in implementing it on an ongoing software development project. The results of applying this process, its impact on the project outcomes quality and the employees’ satisfaction with the process are discussed. The goal of this study is to aid organizations in integrating UX design into their development process. 


Author(s):  
Daniel Svensson ◽  
Johan Malmqvist

Abstract Various database systems are used during the product development process to store and retrieve data about products. For example product data management (PDM), enterprise resource planning (ERP) and requirement management (RM) systems. All those might be needed to support the product development process. Earlier research has investigated the co-existence of PDM and ERP systems. This paper extends this question and takes a look on how requirement management systems fit into the picture and how these systems can be used together in order to support the product development process. A comparison of functionality and product models of RM and PDM systems is made. A requirements driven product model of a car cockpit implemented in a RM tool is used as a theoretical reference. The actual situation at the company developing the cockpit is then described. Based on the comparison of the functionality and the product models, three strategies for how the systems could cooperate are presented. The strategies are discussed from both a theoretical and a practical point of view. The conclusions are that RM systems has functionalities for requirements management that do not exist in a PDM system, which calls for the use of both systems. This results in problems with traceability and duplicate data. A certain degree of requirements traceability can be achieved between the systems by applying the strategies presented, but this is not a trivial task.


2002 ◽  
Vol 10 (3) ◽  
pp. 203-211 ◽  
Author(s):  
Fu Qian ◽  
Zhang Shensheng

Product data management (PDM) systems are enabling tool of concurrent engineering (CE). Although the PDM system provides good support for product data, particularly at the early stages of design, it is seldom used beyond the design process. Furthermore, it provides few facilities for activity definition and no facilities for the enactment of production activities. In order to manage the whole lifecycle of motorcycle development, this paper presents a product development process management system that integrates the workflow management system (WFMS) with the PDM. On one hand we can use the powerful product data management functionality of PDM systems, on the other hand we can use the effective process management and control functionalities of WFMS. For the sake of guiding and constraining the workflow modeling, we provide an integrated product development workflow model named P_PROCE model. It is made up of five views that are the process view(P), the product view(P), the resource view(R), and the organization view(O), the control & evaluation view(CE). Based on this model, the architecture and implementation of the product development process management system is presented. It consists of the workflow modeling module, the workflow enactment module and the PDM system. The first module includes process modeling, system sustain and API. The second module includes the personal desktop and the workflow engine. The PDM system is regarded as a workflow-enabled application. The workflow engine invokes it by the Tool Agent.


1996 ◽  
Vol 118 (3) ◽  
pp. 455-457 ◽  
Author(s):  
J. I. Izuchukwu

This paper discusses the role of automation in not only achieving faster product development and deployment, but also forging better collaboration between the functions responsible for product development and support. It presents how information should be shared, managed, and communicated throughout the product development process. The role of product data management system as an information technology for integrated product development is discussed.


2010 ◽  
Vol 118-120 ◽  
pp. 944-947
Author(s):  
You Jun Zhang ◽  
Shi Jie Wang ◽  
Han Li

Product Data Management (PDM) enables the management of the entire product lifecycle and related information about its design and its manufacturing. The key of implement PDM technology is realization of the structure and configuration management about the product. The main functions of PDM and the product development process based on PDM are detailed in this paper. An implementation method is proposed and it is applied for a system by means of an example, which achieves a good result.


2017 ◽  
Vol 20 (3) ◽  
Author(s):  
Daniel A. Magües ◽  
John W. Castro ◽  
Silvia T. Acuña

Background: Interest in the integration of the agile software development process(ASDP) and user-centred design (UCD) has grown over the last decade. However, there are not many papers that study this issue holistically and uncover the current state of this integration. Aim: This study sets out to answer the following research question: What is the current state of integration between agile processes and usability? Method: We conduct a systematic mapping study (SMS). We analyze the articles and the results were cross checked by the authors, and any disagreements were discussed and resolved in meetings. Results: We retrieved a total of 161 Primary Studies. There are very few papers that study the literature holistically and report the current state of usability in the ASDP. Conclusions: We categorized according to four criteria: process, practice, team and technology integration. The largest group refers to process integration with a total of 76 Primary Studies.


2021 ◽  
Vol 1 ◽  
pp. 2267-2276
Author(s):  
Camilla Arndt Hansen ◽  
Michael Deininger

AbstractPrototypes can be used to create value in all phases of the product development process. Prototyping strategies that determine how prototypes are developed should therefore be considered for the prototyping process as a whole. In this paper, we analyse how partitioning strategies were used by ten novice design teams to navigate their prototyping processes during a three-week mechatronic development project. Using the ‘ProtoMapping’ method, their prototyping strategies were visualized and five different types of strategies identified. Four of the ten teams formally planned how to divide their product into modules that could be prototyped in parallel or planned when to integrate prototypes to test the full product. Still, the ProtoMaps showed that most of the teams used some partitioning strategies during their project even when they did not formally decide to do so. Novice designers should be supported in making such strategies for the prototyping process deliberately. Therefore, prototyping tools should be expanded to support not only individual prototyping activities but also the prototyping process.


Author(s):  
Peter Gust ◽  
Alina Sersch ◽  
Tobias Steger ◽  
Christoph Schluer

AbstractThe aim of this paper is to examine the current state of research on tolerance-induced costs in Germany. Through a literature research already existing approaches for the determination of costs related to tolerances during the specification of technical components are pointed out and possible approaches for the reduction of these costs are presented. In addition, the actuality of these approaches will be considered. One question that is supposed to be answered here is to what state of standard for the specification of components these approaches can be assigned to. On the other hand, it should be clarified whether the existing approaches are applicable to the currently valid standard system of the Geometrical Product Specification (GPS).Can the economic efficiency of the specifications selected for tolerancing be determined in a technical drawing during the product development process in accordance with GPS on the basis of the current state of research?


Sign in / Sign up

Export Citation Format

Share Document