761 resultados para product development processes
Resumo:
This paper presents a method to manage Engineering Changes (EC) during the product development process, which is seen to be a complex system. The ability to manage engineering changes efficiently reflects the agility of an enterprise. Although there are unnecessary ECs that should be avoided, many of the ECs are actually beneficial. The proposed method explores the linkages between the product development process features and product specifications dependencies. It suggests ways of identifying and managing specification dependencies to support the Engineering Change Management process. Furthermore, the impacts of an EC on the product specifications as well as on the process organization are studied. © 2009 World Scientific Publishing Company.
Resumo:
This paper presents the result from a case study at Scania on product development processes. The objective with the case study was to gather information on Scania’s product development process (PDP) including the use of CAD and simulation tools, and project work. The objective was also to find any deviations or different interpretations among the employees on the PDP. To gather the information, semi-structured tape-recorded interviews have been used to ensure that individual interpretations from the interviewees could be gathered. Scania uses a defined and structured PDP which facilitates concurrent and cross-functional work. The PDP is implemented and followed to various degrees. The newly employed personnel may have difficulties with communication, both to find and to give information. Although, newly graduated personnel may find it easier to adapt to changes, and also to use a structured process which they have studied at universities. It was also known during the case study that the PDP is a major support for the newly employed personnel, which in turn decreases the time to get into the same working process as the more experienced personnel. Employees with decades of experience know the right sources from which to both give and gather information. Also, the terminology and definitions in the product development process may not be used as intended. This makes it difficult for other project members or teams who need to interpret the information received. At the same time, the routines among the more experienced personnel, which have been set-up throughout the years, make them more inflexible in adapting changes. The findings in the case study as well as challenges with implementing the PDP are known to Scania and are a part of the continuing work with improvement.
Resumo:
New high technology products usher in novel possibilities to transform the design, production and use of buildings. The high technology companies which design, develop and introduce these new products by generating and applying novel scientific and technical knowledge are faced with significant market uncertainty, technological uncertainty and competitive volatility. These characteristics present unique innovation challenges compared to low- and medium technology companies. This paper reports on an ongoing Construction Knowledge Exchange funded project which is tracking, real time, the new product development process of a new family of light emitting diode (LEDs) technologies. LEDs offer significant functional and environmental performance improvements over incumbent tungsten and halogen lamps. Hitherto, the use of energy efficient, low maintenance LEDs has been constrained by technical limitations. Rapid improvements in basic science and technology mean that for the first time LEDs can provide realistic general and accent lighting solutions. Interim results will be presented on the complex, emergent new high technology product development processes which are being revealed by the integrated supply chain of a LED module manufacture, a luminaire (light fitting) manufacture and end user involved in the project.
Resumo:
Proficiency in management activities undertaken in product development processes is regarded as a key competitive advantage for companies, particularly for high-tech industrial firms, which benefit from the important competitiveness factor of launching products with a differentiated technological content. This paper's objective was to identify, through case study, practices for integration between the roles of R & D with others involved in product development in a large Brazilian company of industrial automation. The results suggest some management practices to improve the integration in new products development, such as the use of employees from marketing with knowledge and experience previously gained from R & D activities and uses the heavyweight product manager to solve synchronization problems between product and technology development. © Universidad Alberto Hurtado, Facultad de Economía y Negocios.
Resumo:
As identified by Griffin (1997) and Kahn (2012), manufacturing organisations typically improve their market position by accelerating their product development (PD) cycles. One method for achieving this is to reduce the time taken to design, test and validate new products, so that they can reach the end customer before competition. This paper adds to existing research on PD testing procedures by reporting on an exploratory investigation carried out in a UK-based manufacturing plant. We explore the organisational and managerial factors that contribute to the time spent on testing of new products during development. The investigation consisted of three sections, viz. observations and process modelling, utilisation metrics and a questionnaire-based investigation, from which a proposed framework to improve and reduce the PD time cycle is presented. This research focuses specifically on the improvement of the utilisation of product testing facilities and the links to its main internal stakeholders - PD engineers.
Resumo:
In various industrial and scientific fields, conceptual models are derived from real world problem spaces to understand and communicate containing entities and coherencies. Abstracted models mirror the common understanding and information demand of engineers, who apply conceptual models for performing their daily tasks. However, most standardized models in Process Management, Product Lifecycle Management and Enterprise Resource Planning lack of a scientific foundation for their notation. In collaboration scenarios with stakeholders from several disciplines, tailored conceptual models complicate communication processes, as a common understanding is not shared or implemented in specific models. To support direct communication between experts from several disciplines, a visual language is developed which allows a common visualization of discipline-specific conceptual models. For visual discrimination and to overcome visual complexity issues, conceptual models are arranged in a three-dimensional space. The visual language introduced here follows and extends established principles of Visual Language science.
Resumo:
Knowledge has been widely recognised as a determinant of business performance. Business capabilities require an effective share of resource and knowledge. Specifically, knowledge sharing (KS) between different companies and departments can improve manufacturing processes since intangible knowledge plays an enssential role in achieving competitive advantage. This paper presents a mixed method research study into the impact of KS on the effectiveness of new product development (NPD) in achieving desired business performance (BP). Firstly, an empirical study utilising moderated regression analysis was conducted to test whether and to what extent KS has leveraging power on the relationship between NPD and BP constructs and variables. Secondly, this empirically verified hypothesis was validated through explanatory case studies involving two Taiwanese manufacturing companies using a qualitative interaction term pattern matching technique. The study provides evidence that knowledge sharing and management activities are essential for deriving competitive advantage in the manufacturing industry.
Resumo:
Designers need to consider both the functional and production process requirements at the early stage of product development. A variety of the research works found in the literature has been proposed to assist designers in selecting the most viable manufacturing process chain. However, they do not provide any assistance for designers to evaluate the processes according to the particular circumstances of their company. This paper describes a framework of an Activity and Resource Advisory System (ARAS) that generates advice about the required activities and the possible resources for various manufacturing process chains. The system provides more insight, more flexibility, and a more holistic and suitable approach for designers to evaluate and then select the most viable manufacturing process chain at the early stage of product development.
Resumo:
We all have fresh in our memory what happened to the IT sector only a few years ago when the IT-bubble burst. The upswing of productivity in this sector slowed down, investors lost large investments, many found themselves looking for a new job, and countless dreams fell apart. Product developers in the IT sector have experienced a large number of organizational restructurings since the IT boom, including rapid growth, downsizing processes, and structural reforms. Organizational restructurings seem to be a complex and continuous phenomenon people in this sector have to deal with. How do software product developers retrospectively construct their work in relation to organizational restructurings? How do organizational restructurings bring about specific social processes in product development? This working paper focuses on these questions. The overall aim is to develop an understanding of how software product developers construct their work during organizational restructurings. The theoretical frame of reference is based on a social constructionist approach and discourse analysis. This approach offers more or less radical and critical alternatives to mainstream organizational theory. Writings from this perspective attempt to investigate and understand sociocultural processes by which various realities are created. Therefore these studies aim at showing how people participate in constituting the social world (Gergen & Thatchenkery, 1996); knowledge of the world is seen to be constructed between people in daily interaction, in which language plays a central role. This means that interaction, especially the ways of talking and writing about product development during organizational restructurings, become the target of concern. This study consists of 25 in-depth interviews following a pilot study based on 57 semi-structured interviews. In this working paper I analyze 9 in-depth interviews. The interviews were conducted in eight IT firms. The analysis explores how discourses are constructed and function, as well as the consequences that follow from different discourses. The analysis shows that even though the product developers have experienced many organizational restructurings, some of which have been far-reaching, their accounts build strongly on a stability discourse. According to this discourse product development is, perhaps surprisingly, not influenced to a great extent by organizational restructurings. This does not mean that product development is static. According to the social constructionist approach, product development is constantly being reproduced and maintained in ongoing processes. In other words stable effects are also ongoing achievements and these are of particular interest in this study. The product developers maintain rather than change the product development through ongoing processes of construction, even when they experience continuous extensive organizational restructurings. The discourse of stability exists alongside other discourses, some which contradict each other. Together they direct product development and generate meanings. The product developers consequently take an active role in the construction of their work during organizational restructurings. When doing this they also negotiate credible positions for themselves
Resumo:
Many Finnish IT companies have gone through numerous organizational changes over the past decades. This book draws attention to how stability may be central to software product development experts and IT workers more generally, who continuously have to cope with such change in their workplaces. It does so by analyzing and theorizing change and stability as intertwined and co-existent, thus throwing light on how it is possible that, for example, even if ‘the walls fall down the blokes just code’ and maintain a sense of stability in their daily work. Rather than reproducing the picture of software product development as exciting cutting edge activities and organizational change as dramatic episodes, the study takes the reader beyond the myths surrounding these phenomena to the mundane practices, routines and organizings in product development during organizational change. An analysis of these ordinary practices offers insights into how software product development experts actively engage in constructing stability during organizational change through a variety of practices, including solidarity, homosociality, close relations to products, instrumental or functional views on products, preoccupations with certain tasks and humble obedience. Consequently, the study shows that it may be more appropriate to talk about varieties of stability, characterized by a multitude of practices of stabilizing rather than states of stagnation. Looking at different practices of stability in depth shows the creation of software as an arena for micro-politics, power relations and increasing pressures for order and formalization. The thesis gives particular attention to power relations and processes of positioning following organizational change: how social actors come to understand themselves in the context of ongoing organizational change, how they comply with and/or contest dominant meanings, how they identify and dis-identify with formalization, and how power relations often are reproduced despite dis-identification. Related to processes of positioning, the reader is also given a glimpse into what being at work in a male-dominated and relatively homogeneous work environment looks like. It shows how the strong presence of men or “blokes” of a particular age and education seems to become invisible in workplace talk that appears ‘non-conscious’ of gender.
Resumo:
This paper presents novel collaboration methods implemented using a centralized client/server product development integration architecture, and a decentralized peer-to-peer network for smaller and larger companies using open source solutions. The product development integration architecture has been developed for the integration of disparate technologies and software systems for the benefit of collaborative work teams in design and manufacturing. This will facilitate the communication of early design and product development within a distributed and collaborative environment. The novelty of this work is the introduction of an‘out-of-box’ concept which provides a standard framework and deploys this utilizing a proprietary state-of-the-art product lifecycle management system (PLM). The term ‘out-of-box’ means to modify the product development and business processes to suit the technologies rather than vice versa. The key business benefits of adopting such an approach are a rapidly reconfigurable network and minimal requirements for software customization to avoid systems instability
Resumo:
The essence of lean is very simple, but from a research and implementation point of view overwhelming. Lean is the search for perfection through the elimination of waste and the insertion of practices that contribute to reduction in cost and schedule while improving performance of products. This concept of lean has wide applicability to a large range of processes, people and organizations, from concept design to the factory floor, from the laborer to the upper management, from the customer to the developer. Progress has been made in implementing and raising the awareness of lean practices at the factory floor. However, the level of implementation and education in other areas, like product development, is very low.
Resumo:
“What is value in product development?” is the key question of this paper. The answer is critical to the creation of lean in product development. By knowing how much value is added by product development (PD) activities, decisions can be more rationally made about how to allocate resources, such as time and money. In order to apply the principles of Lean Thinking and remove waste from the product development system, value must be precisely defined. Unfortunately, value is a complex entity that is composed of many dimensions and has thus far eluded definition on a local level. For this reason, research has been initiated on “Measuring Value in Product Development.” This paper serves as an introduction to this research. It presents the current understanding of value in PD, the critical questions involved, and a specific research design to guide the development of a methodology for measuring value. Work in PD value currently focuses on either high-level perspectives on value, or detailed looks at the attributes that value might have locally in the PD process. Models that attempt to capture value in PD are reviewed. These methods, however, do not capture the depth necessary to allow for application. A methodology is needed to evaluate activities on a local level to determine the amount of value they add and their sensitivity with respect to performance, cost, time, and risk. Two conceptual tools are proposed. The first is a conceptual framework for value creation in PD, referred to here as the Value Creation Model. The second tool is the Value-Activity Map, which shows the relationships between specific activities and value attributes. These maps will allow a better understanding of the development of value in PD, will facilitate comparison of value development between separate projects, and will provide the information necessary to adapt process analysis tools (such as DSM) to consider value. The key questions that this research entails are: · What are the primary attributes of lifecycle value within PD? · How can one model the creation of value in a specific PD process? · Can a useful methodology be developed to quantify value in PD processes? · What are the tools necessary for application? · What PD metrics will be integrated with the necessary tools? The research milestones are: · Collection of value attributes and activities (September, 200) · Development of methodology of value-activity association (October, 2000) · Testing and refinement of the methodology (January, 2001) · Tool Development (March, 2001) · Present findings at July INCOSE conference (April, 2001) · Deliver thesis that captures a formalized methodology for defining value in PD (including LEM data sheets) (June, 2001) The research design aims for the development of two primary deliverables: a methodology to guide the incorporation of value, and a product development tool that will allow direct application.