Concurrent engineering (CE) is a philosophy and set of guiding principles where product design and process design are developed concurrently, with some product design and process development overlapping. This includes production and support planning. Unlike sequential engineering, concurrent engineering involves parallel work and dynamic integration. Software, electrical, and mechanical engineers are in constant contact on integration issues as they design and build prototypes.
Concurrent engineering requires an integrative management and cultural environment, matrix teams, and an improvement system focusing on customer satisfaction as the final "arbiter" of quality.
The concurrent engineering philosophy emphasizes on customer focus. It advocates an organization-wide, systematic approach using a disciplined methodology. It stresses the never-ending improvements of product, processes, production, and support. It involves the concurrent, simultaneous, or overlapping accomplishment of the phases of the project. For instance, the concept and design phases are accomplished concurrently with a design-build approach. The design and development phases are performed simultaneously. The development and production phases are done with some overlapping activities. In most cases of concurrent engineering, all the phases contain some overlapping activities. Concurrent engineering requires upper management's active leadership and support to be successful. It focuses on robust design that decreases loss. It aims at reducing cost and time, while improving quality and productivity. It uses the latest engineering planning initiatives, including automation. Concurrent engineering forges a new reliance on multifunctional teams using tools and techniques such as quality function deployment, design of experiments, Taguchi approach, and statistical process control.
If concurrent engineering is a systematic approach to the integrated, concurrent design of products and their related processes, including manufacture and support, then project integration management involves the "scrubbing" of project schedules in order to maximize concurrency and integration. This means that project schedules are characterized by overlapping task dependencies. This approach is intended to cause the developers, from the outset, to consider all elements of the product life cycle from conception, through disposal, including quality, cost, schedule, and user requirements.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.