Knowledge architecture supporting the next generation of MDO in the AGILE paradigm

Abstract

After almost three decades of evolution, it is not yet possible to apply MDO in collaborative projects within large, heterogeneous and distributed teams of experts, whilst nowadays necessary for the development of any complex product. The H2020 project AGILE took the challenge of devising a novel paradigm to swiftly set up and deploy large distributed MDO systems, that are easy to (re)configure and monitor during the whole process, from requirements definition to data post-processing. The main outcome is an advanced set of tools and methods contributing to a 3rd generation MDO environment, specifically tailored to the aerospace industry. The AGILE paradigm is built on top of two main pillars, the so-called knowledge architecture and the collaborative architecture. The former, which is the main focus of this paper, provides a structured approach and the related workbench to formulate and inspect any automated design process, including fully formalized MDO systems. The latter includes the tools and methods to translate these formulations into executable workflows and deploy them across distributed networks. Although AGILE aims specifically at aircraft MDO, the proposed knowledge architecture provides a general conceptual framework that is suitable for the development of any complex product. The knowledge architecture has a multi-level hierarchical structure, consisting of four layers: development process, automated design, design competences and data schemas. Interfaces between the various layers are defined to achieve a fully.interconnected development process. This paper provides first a description of the knowledge architecture as a generalized paradigm to formulate collaborative and distributed MDO systems. Then, the specific implementation of such a paradigm within the AGILE project is illustrated: four knowledge architecture applications and two data schemas are described in detail. Finally, the whole approach is demonstrated by means of a realistic aircraft design case. This implementation proved successful in multiple aspects. First of all, in allowing heterogeneous teams of experts to generate complete and correct MDO system formulations involving large amount of distributed disciplinary tools, while maintaining full control and systematic overview of the complete system archi- tecture. Second, in offering the necessary agility to adjust and reconfigure the formulated MDO systems, such to support the iterative and evolutionary nature of their development process. Finally, by dramatically accelerating the setup time of the MDO system, thanks to the automation of the complex, lengthy and repetitive operations involved in the partitioning and coordination process, and to the effective support in inspecting and resolving the eventual inconsistencies in the data flow, arising every time tools are added or modified, or different solution strategies are implemented.