Evoke: A value-driven concept selection method for early system design

The development of new technologically advanced products requires the contribution from a range of skills and disciplines, which are often difficult to find within a single company or organization. Requirements establishment practices in Systems Engineering (SE), while ensuring coordination of activities and tasks across the supply network, fall short when it comes to facilitate knowledge sharing and negotiation during early system design. Empirical observations show that when system-level requirements are not available or not mature enough, engineers dealing with the development of long lead-time sub-systems tend to target local optima, rather than opening up the design space. This phenomenon causes design teams to generate solutions that do not embody the best possible configuration for the overall system. The aim of this paper is to show how methodologies for value-driven design may address this issue, facilitating early stage design iterations and the resolution of early stage design trade-offs. The paper describes how such methodologies may help gathering and dispatching relevant knowledge about the ‘design intent’ of a system to the cross-functional engineering teams, so to facilitate a more concurrent process for requirement elicitation in SE. The paper also describes EVOKE (Early Value Oriented design exploration with KnowledgE maturity), a concept selection method that allows benchmarking design options at sub-system level on the base of value-related information communicated by the system integrators. The use of EVOKE is exemplified in an industrial case study related to the design of an aero-engine component. EVOKE’s ability to raise awareness on the value contribution of early stage design concepts in the SE process has been further verified with industrial practitioners in ad-hoc design episodes