AGILE4.0 Framework (A4F)
The AGILE 4.0 Framework (A4F) defines, in a MBSE approach, the logics of the Development System, which is developed in the AGILE4.0 project to accelerate the development of complex aeronautical systems (aircraft). The A4F architecture is solution independent (logical architecture).
System Identification
For a given policy (e.g. sustainable aviation) this activity addresses the identification of system stakeholders and their needs, delivering the set of goals, and capabilities which need to be met by the System of Interest under development. The System of Interest is addressed in the domain of the stakeholders, responsible for the validation.
CloseSystem Specification
For a given set of goals & capabilities, and accounting for all the stakeholders involved, in this phase Concepts of Operations (ConOps) are elaborated to describe through scenarios how the system of interest will operate during its life cycle, delivering the set of requirements, which will need to be verified by the System of Interest under development. The System of Interest is addressed in the domain of its requirements.
CloseSystem Architecting
For a given set of goals & capabilities, and accounting for all the stakeholders involved, in this phase Concepts of Operations (ConOps) are elaborated to describe through scenarios how the system of interest will operate during its life cycle, delivering the set of requirements, which will need to be verified by the System of Interest under development. The System of Interest is addressed in the domain of its requirements.
CloseSystem Synthesis
For a chosen architecture and given set of requirements, this activity addresses the integration and the synthesissizing of the System of Interest. Such activity delivers the sizing and the verification of the design parameters of the physical architecture of the System of Interest under development. The System of Interest can be either initialized, analyzed andor optimized. Such a synthesis is driven by a design andor optimization process (either empirical or simulation-driven and of any level of fidelitydetail). The System of Interest is addressed in the physical domain.
CloseSystem Design
For a given physical architecture and defined design space, this activity includes the selection of the design competence (e.g. disciplinary simulations) according to the design stage (e.g. conceptual, preliminary, detailed), the integration into a design processes, the deployment of design system (e.g. computational environments), the exploration of the design space and the decision making about the optimum solution(s). This phase transfers the physical architecture (e.g. aircraft components) of the System of Interest into the “disciplinary domain” (e.g. aerodynamics, structure, etc.). Sub-activities of setup and execute a design and optimization process are inherited by the AGILE project.
CloseThe AGILE 4.0 Framework addresses different systems:
System of System
Architecting and designing complex System-of-Systems scenarios for a given set of capabilities to be delivered, enabling trade-off between concepts of operations.
CloseSystem of Interest
Architecture Design and Optimization (ADO) of a complex system of interest for a given set of requirements and concept of operations, enabling trade-off between architectures.
CloseDevelopment System
Deployment and operation of a development system and processes (e.g. Multidisciplinary Design Analysis and Optimization (MDAO) process) for the design and optimization of the system of interest, for a given architecture, design for X strategy (e.g. minimum cost), and dimensionality of the design space.
CloseCompetence
Providing heterogeneous capabilities (e.g. disciplinary analysis) and services available, or to be developed, enabling system design and optimization.
CloseAGILE4.0 Operational Collaborative Environment (OCE)
The Operational Collaborative Environment (OCE) represents the implementation of the Development System developed by AGILE4.0 project, and therefore used for the resolution of AGILE4.0 application cases. The OCE translates the A4F logical architecture into a specific physical solution (physical architecture), which is composed of heterogeneous specific modules.
Papyrus
Papyrus is an industrial-grade open-source Model-Based Engineering tool. In AGILE4.0 Papyrus is used for visualization and validation of stakeholders, needs and requirements models. Papyrus allows navigation through all use-case models through interactive diagram views. An SysML-based standard is developed specifically for AGILE4.0 which describe how these models and views can be visualized, specified and analyzed.
Official website CloseCapella
Capella is an Open Source MBSE tool that implements the Arcadia method. It is a comprehensive, extensible and field-proven MBSE solution. In AGILE4.0 capella is used for performing an operation analysis leading to an Operational Entity Scenario diagram.
Official website CloseKADMOS
KADMOS (Knowledge- and graph-based Agile Design for Multidisciplinary Optimization System) is a tool that supports the user in formulating MDAO workflows. KADMOS was originally developed with the AGILE project. Within AGILE4.0 its functionalities are extended to include the sequencing and partitioning of MDAO workflows. KADMOS is a Python package and fully open source.
Bitbucket repository CloseMDAx
MDAx (Agile Generation of Collaborative MDAO Workflows for Complex Systems) provides an environment for the modelling of generic simulation workflows in an XDSM-based user interface. Moreover, it implements features that allow competence specialists to define or upload a CPACS schema instance and easily define tool inputs and outputs for their specific competence tools. MDAx can export the workflow model to various formats, including either a direct export to RCE or CMDOWS.
CloseSMR
The Surrogate Model Repository (SMR) is a web-based central broker for registration, creation, storage, deployment, sharing, and usage of surrogate models. The SMR facilitates sharing and reuse of the surrogate models available in AGILE4.0 among collaborating partners in a knowledge-based way. The SMR enables partners to publish and provide simplified versions of their models to support efficient optimization while protecting the IP of the detailed models. It also provides the opportunity to connect partners with a surrogate model creation request to surrogate modelling specialists.
CloseWhatsOpt
WhatsOpt is a Ruby on Rails web application allowing to define and share multi-disciplinary analyses in terms of disciplines and data exchange. In AGILE4.0 WhatsOpt is used to deliver executable surrogate models in a collaborative workflow as part of the SMR and SMG.
Github repository CloseBRICS
The Brics technology (protocol plus supportive middleware) enables the establishment of cross-organization collaborative aircraft design workflows as an integrated set of expert workflows and tools located in the domains of the collaborating partners. As such, it fosters multi-partner MDO studies, thereby complying with the prevailing security constraints while dealing with technical security measures as firewalls.
CloseRCE
RCE (Remote Component Environment) is an Open Source distributed, workflow-driven integration environment. It is used by design teams to “compose and execute” simulation-based MDO processes of complex systems (e.g., aircraft) by integrating their own design and simulation tools. In AGILE4.0 RCE can automatically generate MDO workflows stored as CMDOWS format and execute cross-organizational MDO processes by leveraging Brics technology.
Official website CloseMultiLinQ
MultiLinQ can be used to link architecture elements (components, QOIs) to nodes in a central data schema (e.g. CPACS). This link is then used to enable the optimization of system architectures, as driven by ADORE, using collaborative MDO workflows, as formulated by MDAx or KADMOS.
CloseADORE
ADORE (Architecture Design and Optimization Reasoning Environment) is a modeling environment for defining system architecture design spaces. Functions, components and Quantities of Interest (QOIs) can be created and linked to each other. Several types of architecture decisions can be modeled: component selection, component instantiation, property value assignment, and component connections through ports. From this, an architecture optimization problem (design variables, objectives, constraints) can be defined.
CloseVALORISE
VALORISE (Value-driven trAdespace visuaLizatiOn, exploRatIon, asSEssment) is an interactive dashboard supporting the decision making process. Leveraging the value model theory, it is especially needed when multiple decision criteria (called attributes) have to be accounted in identifying the best solution in the final tradepsace. VALORISE allows the value-driven tradespace visualization, showing in real time how solutions change while assigning different weights to attributes (thus a different relative importance) or different utility functions (representative the DM´s preferences with respect to attributes).
CloseRVF
The Requirements Verification Framework (RVF) is a tool that enables the derivation of MDAO workflows from requirements and the automatic verification of requirements based on the results from your MDAO problem. These two functionalities are achieved by applying patterns to the requirements, adding verification methods to the requirements and giving the requirements different problem roles (e.g. objective, constraint, design variable bound). Within AGILE4.0 the RVF is fully integrated within KE-Chain.
More information CloseMBSElib
MBSElib is a set of Python libraries developed to model and store use-case model definitions. These libraries are used under-the-hood to export use-case models such as Stakeholders, Needs, Requirements, Requirements patterns, Systems and Glossaries from KE-chain to Papyrus. MBSElib automatically generates an export which can be opened in Papyrus for further inspection.
CloseKE-chain
KE-chain is a commercial web-based collaboration and process integration platform. KE-chain forms and workflows are used for quality assurance, project control, compliance and systems engineering for the infrastructure and manufacturing industries. In AGILE4.0 KE-chain is used as the “control room” for managing all activities related to the MBSE development process for application cases. Moreover KE-chain provides the graphical user interface and data storage for technologies such as KADMOS, MBSElib, ADORE, MultiLinQ, MDAx and SMR. Finally, KE-cahin is used as a central storage per application case for use-case models, CMDOWS and CPACS files.
Official website Close