Managing design variety, process variety and engineering change: a case study of two capital good firms

Many capital good firms deliver products that are not strictly one-off, but instead share a certain degree of similarity with other deliveries. In the delivery of the product, they aim to balance stability and variety in their product design and processes. The issue of engineering change plays an important in how they manage to do so. Our aim is to gain more understanding into how capital good firms manage engineering change, design variety and process variety, and into the role of the product delivery strategies they thereby use. Product delivery strategies are defined as the type of engineering work that is done independent of an order and the specification freedom the customer has in the remaining part of the design. Based on the within-case and cross-case analysis of two capital good firms several mechanisms for managing engineering change, design variety and process variety are distilled. It was found that there exist different ways of (1) managing generic design information, (2) isolating large engineering changes, (3) managing process variety, (4) designing and executing engineering change processes. Together with different product delivery strategies these mechanisms can be placed within an archetypes framework of engineering change management. On one side of the spectrum capital good firms operate according to open product delivery strategies, have some practices in place to investigate design reuse potential, isolate discontinuous engineering changes into the first deliveries of the product, employ ‘probe and learn’ process management principles in order to allow evolving insights to be accurately executed and have informal engineering change processes. On the other side of the spectrum capital good firms operate according to a closed product delivery strategy, focus on prevention of engineering changes based on design standards, need no isolation mechanisms for discontinuous engineering changes, have formal process management practices in place and make use of closed and formal engineering change procedures. The framework should help managers to (1) analyze existing configurations of product delivery strategies, product and process designs and engineering change management and (2) reconfigure any of these elements according to a ‘misfit’ derived from the framework. Since this is one of the few in-depth empirical studies into engineering change management in the capital good sector, our work adds to the understanding on the various ways in which engineering change can be dealt with

Requirements analysis in the implementation of integrated PLM, ERP and CAD systems

Product Lifecycle Management (PLM) system implementation is a major investment when the technology is used in manufacturing companies. This paper provides an analysis of the requirements for the integration of PLM systems with Enterprise Resource Planning (ERP) systems incorporating the design aspects of Computer Aided Design and Manufacturing (CAD/CAM) within the product development process. PLM implementation deals with various existing product data and information generated over years both from CAD and ERP systems. Data integration is very challenging and has important impact on future decisions while creating new processes. The information management plays very important role not only in PLM implementation but also in the way this will be used in future production. Therefore it is very important to analyse how product information is transferred to PLM system. It also need to be investigated that what, when and how the data will flow from and to PLM systems

Managing engineering design in complex supply chains

The trend towards organising design, development and manufacture via supply chains, rather than predominantly in-house, poses major challenges for design management. Procurement methods based on adversarial competitive tendering are generally unsuited to complex engineering products requiring strong design and development coordination. Literature on ‘supplier partnerships’ has largely overlooked the implications for managing design and development. This paper reports the results of a major project that focuses upon this issue, concentrating on practical case studies – from British Rail, Netherlands Railways, Rolls Royce and British Coal – that involve the management of ‘devolved’ engineering design by large business organisations. A spectrum of approaches from in-house to fully devolved design is described. It is concluded that there does not appear to be a single best approach for managing devolved design, but that appropriate approaches for an organisation depend on its location in the supply chain and its ability to manage organisational change

Estimating, planning and managing Agile Web development projects under a value-based perspective

Context: The processes of estimating, planning and managing are crucial for software development projects, since the results must be related to several business strategies. The broad expansion of the Internet and the global and interconnected economy make Web development projects be often characterized by expressions like delivering as soon as possible, reducing time to market and adapting to undefined requirements. In this kind of environment, traditional methodologies based on predictive techniques sometimes do not offer very satisfactory results. The rise of Agile methodologies and practices has provided some useful tools that, combined with Web Engineering techniques, can help to establish a framework to estimate, manage and plan Web development projects. Objective: This paper presents a proposal for estimating, planning and managing Web projects, by combining some existing Agile techniques with Web Engineering principles, presenting them as an unified framework which uses the business value to guide the delivery of features. Method: The proposal is analyzed by means of a case study, including a real-life project, in order to obtain relevant conclusions. Results: The results achieved after using the framework in a development project are presented, including interesting results on project planning and estimation, as well as on team productivity throughout the project. Conclusion: It is concluded that the framework can be useful in order to better manage Web-based projects, through a continuous value-based estimation and management process.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-

Housing supply chain model for innovation: research report

The aim of this research is to undertake a case study analysis of successful delivery of an innovation to the Australian housing construction industry. This study is conducted on the “innovator group”; that is, the group that created the idea of an innovation for the housing sector and then were intimately involved in creation, development and diffusion. It is apparent that there were key players involved in this process which are representative of various organisations along the supply chain – designer, developer, subcontractor and supplier. Much rhetoric states that integration of the supply chain actors will solve construction problems, however, in reality we know little beyond this in the Australian context as there has been little research conducted previously. This study will examine in detail the process undertaken by this particular group to deliver an innovation to the housing sector which required an integrated construction supply chain model. This report was published by the Australian Housing Supply Chain Alliance and written by Professor Kerry London, School of Property, Construction and Project Management, RMIT University with Research Fellow, Jessica Siva

A dashboard-based approach for efficient requirements change management

Requirements gathering and documentation are important first steps for a successful software engineering project. The documented requirements act as a guideline for design and development of software products. Requirements also represent customer expectations for the end product. Since these documented requirements serve important purposes for many stakeholders, managing requirement changes effectively plays a major role in the overall success of any project. Changes in requirements are very common in software engineering and can occur during any phase of software development lifecycle (SDLC). Though the impact of requirement changes differs depending on the SDLC phase in which it occurred, there is almost always a setback that happens in terms of the project timeline. This scenario is common in projects that follow both Agile/Scrum methodology and ones that follow the more traditional Waterfall model. In this report, I will first present two case studies of how requirement changes impacted the timelines of two projects (one following Agile/Scrum methodology and another following Waterfall methodology). In the second part of this report, I will propose and design a user-friendly dashboard, which could be used to speed up the delays caused by changing requirements.Electrical and Computer Engineerin

Design Within Complex Environments: Collaborative Engineering in the Aerospace Industry

The design and the industrialization of an aircraft, a major component, or an aerostructure is a complex process. An aircraft like the Airbus A400M is composed of about 700,000 parts (excluding standard parts). The parts are assembled into aerostructures and major components, which are designed and manufactured in several countries all over the world. The introduction of new Product Lifecycle Management (PLM) methodologies, procedures and tools, and the need to reduce time-to-market, led Airbus Military to pursue new working methods to deal with complexity. Collaborative Engineering promotes teamwork to develop product, processes and resources from the conceptual phase to the start of the serial production. This paper introduces the main concepts of Collaborative Engineering as a new methodology, procedures and tools to design and develop an aircraft, as Airbus Military is implementing. To make a Proof of Concept (PoC), a pilot project, CALIPSOneo, was launched to support the functional and industrial design process of a medium size aerostructure. The aim is to implement the industrial Digital Mock-Up (iDMU) concept and its exploitation to create shop fl oor documentation