Concurrent engineering

Last updated

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]

Contents

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 Waterfall vs iterative.JPG
Sequential Engineering vs Concurrent Design and Manufacturing

Introduction

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. Waterfall vs iterative.JPG
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

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

Cross-functional teams

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

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

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

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

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

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

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

Long term benefits

Using C.E.

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

See also

Related Research Articles

<span class="mw-page-title-main">Systems engineering</span> Interdisciplinary field of engineering

Systems engineering is an interdisciplinary field of engineering and engineering management that focuses on how to design, integrate, and manage complex systems over their life cycles. At its core, systems engineering utilizes systems thinking principles to organize this body of knowledge. The individual outcome of such efforts, an engineered system, can be defined as a combination of components that work in synergy to collectively perform a useful function.

<span class="mw-page-title-main">Spiral model</span> Software development process model

The spiral model is a risk-driven software development process model. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.

In business and engineering, product development or new product development covers the complete process of bringing a new product to market, renewing an existing product and introducing a product in a new market. A central aspect of NPD is product design, along with various business considerations. New product development is described broadly as the transformation of a market opportunity into a product available for sale. The products developed by an organisation provide the means for it to generate income. For many technology-intensive firms their approach is based on exploiting technological innovation in a rapidly changing market.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

<span class="mw-page-title-main">Product lifecycle</span> Duration of processing of products from inception, to engineering, design & manufacture

In industry, product lifecycle management (PLM) is the process of managing the entire lifecycle of a product from its inception through the engineering, design and manufacture, as well as the service and disposal of manufactured products. PLM integrates people, data, processes, and business systems and provides a product information backbone for companies and their extended enterprises.

In software project management, software testing, and software engineering, verification and validation (V&V) is the process of checking that a software system meets specifications and requirements so that it fulfills its intended purpose. It may also be referred to as software quality control. It is normally the responsibility of software testers as part of the software development lifecycle. In simple terms, software verification is: "Assuming we should build X, does our software achieve its goals without any bugs or gaps?" On the other hand, software validation is: "Was X what we should have built? Does X meet the high-level requirements?"

Traditional engineering, also known as sequential engineering, is the process of marketing, engineering design, manufacturing, testing and production where each stage of the development process is carried out separately, and the next stage cannot start until the previous stage is finished. Therefore, the information flow is only in one direction, and it is not until the end of the chain that errors, changes and corrections can be relayed to the start of the sequence, causing estimated costs to be under predicted.

<span class="mw-page-title-main">Computer-integrated manufacturing</span> Manufacturing controlled by computers

Computer-integrated manufacturing (CIM) is the manufacturing approach of using computers to control the entire production process. This integration allows individual processes to exchange information with each part. Manufacturing can be faster and less error-prone by the integration of computers. Typically CIM relies on closed-loop control processes based on real-time input from sensors. It is also known as flexible design and manufacturing.

<span class="mw-page-title-main">Computer-aided production engineering</span>

Computer-aided production engineering (CAPE) is a relatively new and significant branch of engineering. Global manufacturing has changed the environment in which goods are produced. Meanwhile, the rapid development of electronics and communication technologies has required design and manufacturing to keep pace.

Design for excellence is a term and abbreviation used interchangeably in the existing literature, where the X in design for X is a variable which can have one of many possible values. In many fields X may represent several traits or features including: manufacturability, power, variability, cost, yield, or reliability. This gives rise to the terms design for manufacturability, design for inspection (DFI), design for variability (DfV), design for cost (DfC). Similarly, other disciplines may associate other traits, attributes, or objectives for X.

<span class="mw-page-title-main">Reconfigurable manufacturing system</span>

A reconfigurable manufacturing system (RMS) is one designed at the outset for rapid change in its structure, as well as its hardware and software components, in order to quickly adjust its production capacity and functionality within a part family in response to sudden market changes or intrinsic system change.

Integrated logistic support (ILS) is a technology in the system engineering to lower a product life cycle cost and decrease demand for logistics by the maintenance system optimization to ease the product support. Although originally developed for military purposes, it is also widely used in commercial customer service organisations.

The process of circuit design can cover systems ranging from complex electronic systems down to the individual transistors within an integrated circuit. One person can often do the design process without needing a planned or structured design process for simple circuits. Still, teams of designers following a systematic approach with intelligently guided computer simulation are becoming increasingly common for more complex designs. In integrated circuit design automation, the term "circuit design" often refers to the step of the design cycle which outputs the schematics of the integrated circuit. Typically this is the step between logic design and physical design.

A software factory is a structured collection of related software assets that aids in producing computer software applications or software components according to specific, externally defined end-user requirements through an assembly process. A software factory applies manufacturing techniques and principles to software development to mimic the benefits of traditional manufacturing. Software factories are generally involved with outsourced software creation.

Engineer to order is a production approach characterized by:

  1. Engineering activities need to be added to product lead time.
  2. Upon receipt of a customer order, the order engineering requirements and specifications are not known in detail. There is a substantial amount of design and engineering analysis required.

Digital Prototyping gives conceptual design, engineering, manufacturing, and sales and marketing departments the ability to virtually explore a complete product before it's built. Industrial designers, manufacturers, and engineers use Digital Prototyping to design, iterate, optimize, validate, and visualize their products digitally throughout the product development process. Innovative digital prototypes can be created via CAutoD through intelligent and near-optimal iterations, meeting multiple design objectives, identifying multiple figures of merit, and reducing development gearing and time-to-market. Marketers also use Digital Prototyping to create photorealistic renderings and animations of products prior to manufacturing. Companies often adopt Digital Prototyping with the goal of improving communication between product development stakeholders, getting products to market faster, and facilitating product innovation.

<span class="mw-page-title-main">Sustainable engineering</span> Engineering discipline

Sustainable engineering is the process of designing or operating systems such that they use energy and resources sustainably, in other words, at a rate that does not compromise the natural environment, or the ability of future generations to meet their own needs.

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

In software engineering, a software development process is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

Predictive engineering analytics (PEA) is a development approach for the manufacturing industry that helps with the design of complex products. It concerns the introduction of new software tools, the integration between those, and a refinement of simulation and testing processes to improve collaboration between analysis teams that handle different applications. This is combined with intelligent reporting and data analytics. The objective is to let simulation drive the design, to predict product behavior rather than to react on issues which may arise, and to install a process that lets design continue after product delivery.

References

  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. 1 2 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. 1 2 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. 1 2 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