Simulation of Overlapping Design Activities in Concurrent Engineering

Abstract

Concurrent engineering is the process of reducing the total project delivery time by overlapping activities that normally occur sequentially. The benefits are a shortening of delivery time and a possible reduction in overall costs. However, there are potential risks to overlapping dependent activities. The interaction between an upstream activity and a downstream activity relies on how information evolves in the upstream activity and how sensitive the downstream activity is to that changing information. This implies that if an upstream activity is slow to evolve information and a downstream activity is highly sensitive to changing information, the risk in overlapping these activities will be higher than activities that are fast to evolve and not as sensitive to changing information. The risk can manifest in rework, or reperforming some aspect of the downstream activity because of the evolution of the upstream activity and the amount of overlapping used. This research developed computer simulation models to better understand the potential risk of rework. The simulation models allow for overlapping different types of slow- and fast-evolving upstream activities with high- and low-sensitivity downstream activities using overdesign and early release strategies and different amounts of overlapping. The overall findings show that simulations of overlapping activities yield a reliable approach to modeling concurrent engineering activities. The simulations provide information on the probability of rework based on the different combinations of evolution, sensitivity, overlapping strategy, and the percent amount of overlapping used between the upstream and downstream activity. The use of computer simulations and modeling of overlapping activities therefore allows engineers and managers to understand the potential risks and what strategies to apply when utilizing concurrent engineering on a project.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 41 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.