CMDOWS: a proposed new standard to store and exchange MDO systems

Abstract

Important note To cite this publication, please use the final published version (if applicable). Please check the document version above.

Streamlining Cross-Organizational Aircraft Development: Results from the AGILE Project

“…Figure 2.2 shows the development process in relation to the specific technologies adopted in the AGILE Framework. The AGILE development process provided an integrated environment, implemented in the KE-chain platform [7] as front-end, with the main function to interface with components from the automated design and design competence layer using CPACS [8] and CMDOWS [9] as data standards for aircraft products and MDO processes. The five steps and its associated technology enablers can be summarized as follows:…”

Integrated collaboration capabilities for competitive aircraft design

“…The AGILEspecific business workflow guides the MDA/MDO study architect through the process of competence specification and selection, and workflow composition, execution, and results inspection. (Requirement 1)  CMDOWS (Common Multidisciplinary Design Optimization Workflow Schema) [9]: XML-based data format for specification of knowledge about competences and for workflow-tool independent specification of workflows.…”

A Critical Look at Design Automation Solutions for Collaborative MDO in the AGILE Paradigm

“…The tool repository itself, which consists of the set of tools and their I/O interconnections, is then stored by calling a KADMOS method from KE-chain and using a second standardized file format: Common MDO Workflow Schema (CMDOWS). [9] CMDOWS, the third component (C3) discussed in this paper, is another XML-based schema developed in AGILE with a twofold objective: 1) To facilitate the integration of the various MDO support applications in the AGILE framework, as visualized in Figure 3. 2) To enable the storage of an MDO system at different stages of the five-step approach: tool repository, MDO problem, and MDO solution strategy, as visualized in Figure 2.…”