Concurrent engineering

From Wikipedia, the free encyclopedia
  (Redirected from Concurrent Engineering)
Jump to: navigation, search
For the journal, see Concurrent Engineering (journal).

Concurrent engineering is a work methodology based on the parallelisation of tasks (i.e. performing tasks concurrently), which is sometimes called Simultaneous Engineering or Integrated Product Development (IPD). 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 elapsed time required to bring a new product to the market.[1]


A publication in 2008 described the concurrent engineering method as a relatively new design management system that has had the opportunity to mature in recent years to become a well-defined systems approach towards optimizing engineering design cycles.[2] Because of this, 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.

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, producibility, assembly, testability, maintenance issues, environmental impact and finally disposal and recycling, should be taken into careful consideration in the early design phases.[3]

The second concept is that the preceding design activities should all be occurring at the same time, i.e., concurrently. The idea is that the concurrent nature of these processes significantly increases productivity and product quality.[4] 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.[5]

As mentioned above, part of the design process is to ensure that the entire product's 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 the process is taking into full account funding, work force capability and time. A study in 2006 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.[4] It is also highly compatible with systems thinking and green engineering.

Concurrent engineering replaces the more traditional sequential design flow, or ‘Waterfall Model’.[6][7] In concurrent engineering an iterative or integrated development method is used instead.[8] The difference between these two methods is that the ‘Waterfall’ method moves in a linear fashion by starting with user requirements and sequentially moving forward to design, implementation and additional steps until you have a finished product. In this design system, a design team would not look backwards or forwards from the step it is on to fix possible problems. In the case that something does go wrong, the design usually must be scrapped or heavily altered. On the other hand, the iterative design process is more cyclic in that, all aspects of the life cycle of the product are taken into account, allowing for a more evolutionary approach to design.[9] 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 that is being produced, 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.[5]

Challenges associated with concurrent design[edit]

Concurrent design comes with a series of challenges, such as the implementation of early design reviews, the dependency on efficient communication between engineers and teams, software compatibility, and opening up the design process.[10] A concurrent 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.[11] It is important to note that although the nature of some activities during a project imposes a degree of linearity—completion of software code, prototype development and testing, for example—the concurrent organization and management of the project teams can still yield significant benefits based on the improved sharing of information as each functional area progresses.

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. Organizations such as the European Space Agency's Concurrent Design Facility make use of concurrent design to perform feasibility studies for future missions.

Concurrent engineering elements[edit]

Cross-functional teams[edit]

A team of people from different area of the workplace that are all involved in the process, including manufacturing, hardware and software design, marketing, and so forth.

Concurrent product realization[edit]

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

Incremental information sharing[edit]

It helps minimize the chance that concurrent product realization will lead to surprises. 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]

It ensures that someone is responsible for the entire project, and that responsibility is not abdicated once one aspect of the work is done.


Several definitions of concurrent engineering are in use.

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

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

Using C.E.[edit]

Currently, several companies, agencies and universities use CE. Among them can be mentioned:
European Space Agency Concurrent Design Facility
NASA Team X - Jet Propulsion Laboratory
NASA Integrated Design Center (IDC), Mission Design Lab (MDL), and Instrument Design Lab (IDL) - Goddard Space Flight Center
CNES - French Space Agency
ASI - Italian Space Agency
EADS Astrium - Satellite Design Office
Thales Alenia Space
The Aerospace Corporation Concept Design Center
STV Incorporated - [1]
German Aerospace Center Deutsches Zentrum für Luft- und Raumfahrt
JAQAR Concurrent Design Services
EPFL Space Center

See also[edit]


  1. ^ "The Principles of Integrated Product Development". 2016. Retrieved 1 December 2016.  |first1= missing |last1= in Authors list (help); External link in |website= (help)
  2. ^ 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
  3. ^ Kusiak, Andrew; Concurrent Engineering: Automation, Tools and Techniques
  4. ^ 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
  5. ^ a b Kusiak, Andrew, Concurrent Engineering: Automation, Tools and Techniques
  6. ^ “The standard waterfall model for systems development”, NASA Webpage, November 14, 2008
  7. ^ Kock, N. and Nosek, J., “Expanding the Boundaries of E-Collaboration”, IEEE Transactions on Professional Communication, Vol 48 No 1, March 2005.
  8. ^ 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
  9. ^ Royce, Winston, "Managing the Development of Large Software Systems", Proceedings of IEEE WESCON 26 (August 1970): 1-9.
  10. ^ Kusiak, Andrew, "Concurrent Engineering: Automation, Tools and Techniques"
  11. ^ Rosenblatt, A. and Watson, G. (1991). "Concurrent Engineering", IEEE Spectrum, July, pp 22-37.
  12. ^ 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.