Concurrent engineering

Product development methodology

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)

This article may be unbalanced toward certain viewpoints. Please improve the article by adding information on neglected viewpoints, or discuss the issue on the talk page. (July 2023)

|

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Concurrent engineering" – news · newspapers · books · scholar · JSTOR (December 2007) (Learn how and when to remove this message)

|

(Learn how and when to remove this message)

Concurrent engineering (CE) or concurrent design and manufacturing is a work methodology emphasizing the parallelization of tasks (i.e. performing tasks concurrently), which is sometimes called simultaneous engineering or integrated product development (IPD) using an integrated product team approach. It refers to an approach used in product development in which functions of design engineering, manufacturing engineering, and other functions are integrated to reduce the time required to bring a new product to market.[1]

By completing the design and manufacturing stages at the same time, products are produced in less time while lowering cost. Although concurrent design and manufacturing requires extensive communication and coordination between disciplines, the benefits can increase the profit of a business and lead to a sustainable environment for product development. Concurrent design and manufacturing can lead to a competitive advantage over other businesses as the product may be produced and marketed in less time.[2] However, poorly implemented concurrent engineering can lead to issues.[3][4]

Sequential Engineering vs Concurrent Design and Manufacturing

## Introduction

[edit]

The success behind concurrent design and manufacturing lies within completing processes at the same time while involving all disciplines. As product development has become more cost and time efficient over the years, elements of concurrent engineering have been present in product development approaches. The elements of concurrent engineering that were utilized were cross-functional teams as well as fast time-to-market and considering manufacturing processes when designing.[5] By involving multiple disciplines in decision making and planning, concurrent engineering has made product development more cost and time efficient. The fact that concurrent engineering could result in faster time-to-market is already an important advantage in terms of a competitive edge over other producers. Concurrent engineering has provided a structure and concept for product development that can be implemented for future success.

A 2008 publication described concurrent engineering as a new design management system that has matured in recent years to become a well-defined systems approach to optimizing design and engineering cycles.[6] Concurrent engineering has been implemented in a number of companies, organizations, and universities, most notably in the aerospace industry. Beginning in the early 1990s, CE was also adapted for use in the information and content automation field, providing a basis for organization and management of projects outside the physical product development sector for which it was originally designed. Organizations such as the European Space Agency's Concurrent Design Facility make use of concurrent design to perform feasibility studies for future missions.

The basic premise for concurrent engineering revolves around two concepts. The first is the idea that all elements of a product's life-cycle—from functionality, production, assembly, testing, maintenance, environmental impact, and finally disposal and recycling—should be taken into careful consideration in the early design phases.[7]

The second concept is that design activities should all be occurring at the same time, i.e., concurrently. The idea is that the concurrent nature of these activities significantly increases productivity and product quality.[8] This way, errors and redesigns can be discovered early in the design process when the project is still flexible. By locating and fixing these issues early, the design team can avoid what often become costly errors as the project moves to more complicated computational models and eventually into the actual manufacturing of hardware.[9]

As mentioned above, part of the design process is to ensure that the product's entire life cycle is taken into consideration. This includes establishing user requirements, propagating early conceptual designs, running computational models, creating physical prototypes, and eventually manufacturing the product. Included in this process is taking into full account funding, workforce capability, and time requirements. A 2006 study claimed that a correct implementation of the concurrent design process can save a significant amount of money, and that organizations have been moving to concurrent design for this reason.[8] It is also highly compatible with systems thinking and green engineering.

Concurrent engineering replaces the more traditional sequential design flow, or "Waterfall Model".[10][11] In Concurrent Engineering an iterative or integrated development method is used instead.[12] The Waterfall method moves in a linear fashion, starting with user requirements and sequentially moving forward to design and implementation, until you have a finished product. In this design system, a design team would not quickly look backward or forward from the step it is on to fix or anticipate problems. In the case that something does go wrong, the design usually must be scrapped or heavily altered. The concurrent or iterative design process encourages prompt changes of tack, so that all aspects of the life cycle of the product are taken into account, allowing for a more evolutionary approach to design.[13] The difference between the two design processes can be seen graphically in Figure 1.

Traditional "Waterfall" or Sequential Development Method vs. Iterative Development Method in concurrent engineering.

A significant part of the concurrent design method is that the individual engineer is given much more say in the overall design process due to the collaborative nature of concurrent engineering. Giving the designer ownership is claimed to improve the productivity of the employee and quality of the product, based on the assumption that people who are given a sense of gratification and ownership over their work tend to work harder and design a more robust product, as opposed to an employee that is assigned a task with little say in the general process.[9]

### Challenges associated with concurrent design

[edit]

Concurrent design comes with a series of challenges, such as implementation of early design reviews, dependency on efficient communication between engineers and teams, software compatibility, and opening up the design process.[14] This design process usually requires that computer models (computer aided design, finite element analysis) are exchanged efficiently, something that can be difficult in practice. If such issues are not addressed properly, concurrent design may not work effectively.[15] It is important to note that although the nature of some project activities imposes a degree of linearity—completion of software code, prototype development and testing, for example—organizing and managing project teams to facilitate concurrent design can still yield significant benefits that come from the improved sharing of information.

Service providers exist that specialize in this field, not only training people how to perform concurrent design effectively, but also providing the tools to enhance the communication between the team members.

## Elements

[edit]

### Cross-functional teams

[edit]

Cross-functional teams include people from different area of the workplace that are all involved in a particular process, including manufacturing, hardware and software design, marketing, and so forth.

### Concurrent product realization

[edit]

Doing several things at once, such as designing various subsystems simultaneously, is critical to reducing design time and is at the heart of concurrent engineering.

### Incremental information sharing

[edit]

Incremental information sharing helps minimize the chance that concurrent product realization will lead to surprises. "Incremental" meaning that as soon as new information becomes available, it is shared and integrated into the design. Cross-functional teams are important to the effective sharing of information in a timely fashion.

### Integrated project management

[edit]

Integrated project management ensures that someone is responsible for the entire project, and that responsibility is not handed-off once one aspect of the work is done.

## Definition

[edit]

Several definitions of concurrent engineering are in use.

The first one is used by the Concurrent Design Facility (ESA):

> Concurrent Engineering (CE) is a systematic approach to integrated product development that emphasizes the response to customer expectations. It embodies team values of co-operation, trust and sharing in such a manner that decision making is by consensus, involving all perspectives in parallel, from the beginning of the product life cycle.

The second one is by Winner, et al., 1988:

> Concurrent Engineering is a systematic approach to the integrated, concurrent design of products and their related processes, including, manufacturing and support. This approach is intended to cause the developers from the very outset to consider all elements of the product life cycle, from conception to disposal, including quality, cost, schedule, and user requirements.[16]

## Concurrent vs sequential engineering

[edit]

Concurrent and Sequential engineering cover the same stages of design and manufacturing, however, the two approaches vary widely in terms of productivity, cost, development and efficiency. The 'Sequential Engineering vs Concurrent Design and Manufacturing' figure shows sequential engineering on the left and concurrent design and manufacturing on the right. As seen in the figure, sequential engineering begins with customer requirements and then progresses to design, implementation, verification and maintenance. The approach for sequential engineering results in large amounts of time devoted to product development. Due to large amounts of time allocated towards all stages of product development, sequential engineering is associated with high cost and is less efficient as products can not be made quickly. Concurrent engineering, on the other hand, allows for all stages of product development to occur essentially at the same time. As seen in the 'Sequential Engineering vs Concurrent Design and Manufacturing' figure, initial planning is the only requirement before the process can occur including planning design, implementation, testing and evaluation. The concurrent design and manufacturing approach allows for shortening of product development time, higher efficiency in developing and producing parts earlier and lower production costs.

Concurrent and Sequential Engineering may also be compared using a relay race analogy.[17] Sequential engineering is compared to the standard approach of running a relay race, where each runner must run a set distance and then pass the baton to the next runner and so on until the race is completed. Concurrent engineering is compared to running a relay race where two runners will run at the same time during certain points of the race. In the analogy, each runner will cover the same set distance as the sequential approach but the time to complete the race using the concurrent approach is significantly less. When thinking of the various runners in the relay race as stages in product development, the correlation between the two approaches in the relay race to the same approaches in engineering is vastly similar. Although there are more complex and numerous processes involved in product development, the concept that the analogy provides is enough to understand the benefits that come with concurrent design and manufacturing.

## Business benefits

[edit]

Using concurrent engineering, businesses can cut down on the time it takes to go from idea to product. The time savings come from designing with all the steps of the process in mind, eliminating any potential changes that have to be made to a design after a part has gone all the way to production before realizing that it is difficult or impossible to machine. Reducing or eliminating these extra steps means the product will be completed sooner and with less wasted material in the process. During the design and prototyping process, potential issues in the design can be corrected earlier in the product development stages to further reduce the production time frame.

The benefits of concurrent design and manufacturing can be sorted in to short term and long term.

### Short term benefits

[edit]

* Competitive advantage with implementing part into market quickly
* Large amounts of same part produced in a shorter amount of time
* Allows for early correction of part
* Less material wasted
* Less time spent on multiple iterations of essentially the same part

### Long term benefits

[edit]

* More cost efficient over several parts produced and several years
* Large amounts of different parts produced in a shorter total amount of time
* Better communication between disciplines in company
* Ability to leverage teamwork and make informed decisions[17]

## Using C.E.

[edit]

Currently, several companies, agencies and universities use CE. Among them can be mentioned:

* Concurrent Design Facility[18] \- European Space Agency
* NASA Team X \- Jet Propulsion Laboratory
* NASA Integrated Design Center (IDC), Mission Design Lab (MDL), and Instrument Design Lab (IDL) \- Goddard Space Flight Center
* NASA Compass Team[19] \- Glenn Research Center
* CNES[20] – French Space Agency
* ASI – Italian Space Agency
* Boeing
* EADS Astrium – Satellite Design Office
* Thales Alenia Space
* The Aerospace Corporation Concept Design Center
* STV Incorporated
* German Aerospace Center Concurrent Engineering Facility
* EPFL Space Center
* Schlumberger
* Harley Davidson
* ASML
* Fiberthree
* Toyota

## See also

[edit]

* ESA's Concurrent Design Facility
* Iterative design
* New product development
* Open Concurrent Design Server
* Product Life Cycle
* Product lifecycle management
* Traditional engineering

## References

[edit]

1. ^ "The Principles of Integrated Product Development". NPD Solutions. DRM Associates. 2016. Retrieved 7 May 2017.
2. ^ Partner, Concurrent Engineering | PTC. "What is Concurrent Engineering?". www.concurrent-engineering.co.uk. Retrieved 2016-02-16.
3. ^ Okpala, Charles Chikwendu; Dara, Jude E. (August 2017). "Benefits and Barriers to Successful Concurrent Engineering Implementation" (PDF).
4. ^ Mathiasen, John Bang; Mathiasen, Rasmus Munksgard (September 23–25, 2016). "Concurrent engineering: The drawbacks of applying a one-size-fits-all approach" (PDF).
5. ^ Loch, Terwiesch (1998). "Product Development and Concurrent Engineering". INSEAD. Retrieved March 8, 2016.
6. ^ Ma, Y., Chen, G. & Thimm, G.; "Paradigm Shift: Unified and Associative Feature-based Concurrent Engineering and Collaborative Engineering", Journal of Intelligent Manufacturing, doi:10.1007/s10845-008-0128-y
7. ^ Kusiak, Andrew; Concurrent Engineering: Automation, Tools and Techniques
8. ^ a b Quan, W. & Jianmin, H., A Study on Collaborative Mechanism for Product Design in Distributed Concurrent Engineering IEEE 2006. DOI: 10.1109/CAIDCD.2006.329445
9. ^ a b Kusiak, Andrew, Concurrent Engineering: Automation, Tools and Techniques
10. ^ "The standard waterfall model for systems development", NASA Webpage, November 14, 2008
11. ^ Kock, N. and Nosek, J., "Expanding the Boundaries of E-Collaboration", IEEE Transactions on Professional Communication, Vol 48 No 1, March 2005.
12. ^ Ma, Y., Chen, G., Thimm, G., "Paradigm Shift: Unified and Associative Feature-based Concurrent Engineering and Collaborative Engineering", Journal of Intelligent Manufacturing, doi:10.1007/s10845-008-0128-y
13. ^ Royce, Winston, "Managing the Development of Large Software Systems", Proceedings of IEEE WESCON 26 (August 1970): 1-9.
14. ^ Kusiak, Andrew, "Concurrent Engineering: Automation, Tools and Techniques"
15. ^ Rosenblatt, A. and Watson, G. (1991). "Concurrent Engineering", IEEE Spectrum, July, pp 22-37.
16. ^ Winner, Robert I., Pennell, James P., Bertrand, Harold E., and Slusarczuk, Marko M. G. (1991). "The Role of Concurrent Engineering in Weapons System Acquisition", Institute for Defense Analyses Report R-338, December 1988, p v.
17. ^ a b Prasad, Biren (1995). "Sequential versus Concurrent Engineering—An Analogy". Concurrent Engineering. 3 (4): 250–255\. doi:10.1177/1063293X9500300401. S2CID 110354984. Retrieved 2016-03-04.
18. ^ "Concurrent Design Facility". www.esa.int. Retrieved 2021-11-30.
19. ^ "Compass Lab". Glenn Research Center | NASA. Retrieved 2021-10-07.
20. ^ Bousquet, P. W.; Benoist, J.; Gonzalez, Fr; Gillen, Ph; Pillet, N.; Sire, J.-P.; Vigeant, F. (2005), "Concurrent Engineering at CNES", 56th International Astronautical Congress of the International Astronautical Federation, the International Academy of Astronautics, and the International Institute of Space Law, American Institute of Aeronautics and Astronautics, doi:10.2514/6.iac-05-d1.3.06, retrieved 2021-11-30