Perceived Conflicts of Systems Engineering in Early-Stage Research and Development 1

Abstract

Early Systems Research and Development (ESR&D) is one of the most crucial phases in the product development process. It both blends and blurs the lines between science and engineering, and requires a risk-based, disciplined, and graded approach to effectively manage scope, cost, and complexity of the final product. Many leaders, program managers, and scientists are unwilling to involve systems engineering because of the perception that systems engineering is heavily process oriented, adds unnecessary costs, and should be applied only to mature technologies. The value of systems engineering as applied to ESR&D is unclear to these key individuals. The unfortunate result is that system engineering is not applied to ESR&D. This results in R&D efforts that may have solved the wrong problem, selected the wrong architecture, require technical rework, have difficulty transitioning later maturity levels, and result in higher R&D costs and extended development timelines. This work discusses the difficulty of introducing systems engineering to the research and early development process and their inclination perspectives of researchers, engineers, and managers. The article shall offer potential means to manage the cultural transformation of early adoption of right-sized systems engineering in ESR&D and reverse the attitudinal positions.