“Using FLAMES to Enable Capability-Based Design and Technology Evaluation”

Author: Patrick Biltgen, Senior Graduate Researcher, Georgia Institute of Technology

Outline:

  1. Title Slide: Using FLAMES to Enable Capability-Based Design and Technology Evaluation

  2. Overview chart

  3. Motivation

    1. The design of future architectures must take into account the capabilities that are provided

    2. Capability = “the ability to achieve an effect to a standard under specified conditions”

    3. Organizations such as DARPA, NASA, and AFRL are tasked with the development of advanced technologies

      1. How do we develop technologies that maximize capabilities?

      2. Is there a traceable process that allows quantitative evaluation of candidate technologies across the hierarchical levels of an architecture?

    4. Methods to address this issue have been largely ad-hoc

    5. A structured process to rapidly perform architecture studies is needed

  4. Goal: Create a Simulation-Based Technology Evaluation Environment

    1. [Chart showing the goal of translating capabilities to technologies]

    2. According to the NSF (cite SBES report), empirical data only allows known behavior to be explored. Simulation has the potential to analyze new advances… etc.

  5. Focus: Long Range Strike as a Testbed Problem

    1. What is Long Range Strike

  6. What has been done: Progress to date

    1. Used a homegrown MATLAB code to test the proposed methodology

    2. Problems with the hardcoded MATLAB code

    3. Summarize modules developed for the simulation

    4. (this part will be very brief because this is what we did BEFORE we got FLAMES)

  7. Introduction to Surrogate Modeling Approach

    1. Benefits

    2. Why we are using them

  8. Types of surrogate models

  9. How surrogate models can be linked to do hierarchical studies

  10. Vision for modeling and simulation

  11. FLAMES is an enabling technology

    1. Creating flexible architectures demands a “breadboard” like approach to component model development

    2. Ideally, the integration framework should be user-friendly, non-proprietary, and utilize object-oriented programming practices

    3. Although a variety of simulations are available, FLAMES is a framework that meets all of the above criteria

  12. Five Levels of Fidelity Using FLAMES and Surrogate Models

  13. Status of Development in FLAMES

  14. Example of Expected results: Exercising Surrogate Models to Discover Solutions

    1. Example scenario results- time critical targets

    2. Show how visualization tools can be used to discover solutions

  15. Top-Down Capability Focused Discovery

    1. a. Graphical example of how we can discover solutions using probability theory and surrogate models

    2. b. Have proven this with hardcoded tool, but are working to do it with FLAMES

  16. Summary and Conclusions

  17. Questions and Contact Information