Outline ! Program Background ! A typical C2 Architecture, Issues to - PDF document

Rapid Synthesis of Multi-Model Simulations for Computation Experiments in C2 Himanshu Neema, Harmon Nine, Graham Hemingway, Janos Sztipanovits, Gabor Karsai ISIS, Vanderbilt University {himanshu,hnine,hemmings,sztipaj,gabor} @isis.vanderbilt.edu GMU-AFCEA SYMPOSIUM on Critical Issues in C4I Lansdowne, VA May 19, 2009 Outline ! Program Background ! A typical C2 Architecture, Issues to study ! Multi-modeling integration challenges ! Our approach: The C2 Wind Tunnel (C2WT) ! C2WT capabilities ! Recent C2 scenario demonstrated with C2WT ! C2WT current status !"###$%&'()&&*+ ,)-.&#!*&(/%0# 1*2%3& 2

Program Background AFOSR: Partnership for Research Excellence and Transition (PRET) in Human System Interaction Program Project: Human Centric Design Environments for Command and Control Systems: The C2 Wind Tunnel Program manager: Dr. John Tangney and Dr. David Luginbuhl PRET Team: Vanderbilt University: Institute for Software Integrated Systems(ISIS) George Mason University: System Architectures SAL Laboratory (SAL) UC Berkeley !"###$%&'()&&*+ ,)-.&#!*&(/%0# 1*2%3& 3 Typical C2 Architecture Unmanned Sensor Platforms Adaptive Mixed Context Dep. Adaptive Human Initiative Command Resource Organization Controller Interpretation Allocation Assigned Abstract HCI Platform Commands Platform Commands Commands Decision Coordination Support COP Platform COP COP Status Elements Elements Elements Data Distribution Network Model-Based Experiment Integration Environment: C2 Windtunnel C2 issues to be studied experimentally: • Distributed Mission Operation • Increased Information Sharing – Synchronization and coordination – Shared situation awareness – Distributed dynamic decision making – Common Operation Picture (COP) – Network effects – Network effects • System Level Impact Analysis • Seamless Integration of – Cyber attacks Manned/Unmanned Assets – Resilience solution – Mixed-Initiative Teams 4 – Strategy/gaming

Multi-Model Simulation Integration Controller/Vehicle Dynamics Processing (Tracking) Organization/Coordination 3-D Environment (Sensors) CPN Delta3D SL/SF Devs Adaptive Mixed Context Dep. Adaptive Human Initiative Command Resource How can we integrate the simulated heterogeneous system components? Organization Controller Interpretation Allocation Abstract Assigned HCI Platform How can we integrate the simulation engines? Commands Platform Commands Commands Decision Coordination How can we rapidly synthesize and deploy integrated simulations? Support COP COP Platform COP Elements Elements Status Elements Data Distribution Network Model-Integrated System and Software Laboratory Environment: C2 Windtunnel GME GME Simulation Interaction Simulation Architecture OMNET 5 Network Architecture Multi-Model Integration Challenges Integrating models Integrating the system ! Heterogeneous models for ! Heterogeneous simulators and different domains: human emulators for different organizations, communication domains: Colored Petri Nets, networks, C2 software systems, OMNET++, DEVS, vehicle simulations, etc. These Simulink/Stateflow, Delta3D, models need to talk to each- etc. other somehow. ! Needed: an underlying ! Needed: an overarching software infrastructure that integration model that connects connects and relates the and relates these heterogeneous simulators in a heterogeneous domain models logically and temporally in a logically coherent coherent framework. framework. Key idea: Integration is about messages and shared data across system components. Why don’t we model these messages and shared data elements and use these models to facilitate model and system integration? 6

C2WT Metamodel Defines language for integrating models in scenarios InteractionInheritance FOM Sheet ObjectInheritance <<Connection>> <<M odel>> <<Connection>> 0..* 0..* FEDFileOutputLoc : field JavaClassPath : field JavaPackageName : field src 0..* dst 0..* dst 0..* src 0..* CppOutputLoc : field Note: Only a part of the ObjectBase JavaOutputLoc : field InteractionBase <<FCO>> metamodel is shown here. <<FCO>> 0..* 0..* 0..* FederateBase StaticInteractionPublish <<FCO>> <<Connection>> 0..* 0..* Interaction StaticInteractionSubscribe InteractionProxy Parameter Object ObjectProxy <<M odel>> <<Connection>> <<Reference>> <<A tom>> <<M odel>> <<Reference>> Federate FederateProxy 0..* Delivery : enum <<M odel>> <<Reference>> ParameterType : enum Order : enum Lookahead : field 0..* 0..* StaticObjectAttributeSubscribe A ttribute <<Connection>> <<Atom>> Delivery : enum Order : enum 0..* ParameterType : enum StaticObjectPublish CommInteraction <<Connection>> <<M odel>> CPNFederate OmnetFederate <<M odel>> <<M odel>> 0..* CPNFile : field FederateCommConnection ConfigFile : field •Graphical representation of definition of <<Connection>> M axStep : field the Model Integration Language (MIL) 0..* 0..* StaticObjectAttributePublish Place EndPoint <<Connection>> •Compatible with OMG’s Unified 0..* <<Atom>> <<Atom>> Modeling Language (UML) standard •Defines the syntactic, semantic, and presentation information of a domain 7 Example: A specific data-model used in a complex C2 scenario Inheritance !"###$%&'()&&*+ ,)-.&#!*&(/%0# 1*2%3& 8

Example: Integration model of a specific C2 scenario Federates (component simulators) publish and subscribe to various types of interactions. ( ) Specific dataflows across networks are specified via ported federates and dataflow connections ( ) !"###$%&'()&&*+ ,)-.&#!*&(/%0# 1*2%3& 9 C2WT Integration Platform Modeling and Run-time Environment Simulation models Delta3D Domain specific models CPN Simulink Devs Java OMNeT++ Graphics -- abstract simulation models Models Models Models Models Models • Data models Model -- interaction & data models transformation • Integration models -- data-flow, timing, & parameters Configuration Sensor Domain specific federates OMNeT++ CPN Devs Java Simulink Physics simulation federate federate federate federate federate federate HLA RTI (Portico) !"###$%&'()&&*+ ,)-.&#!*&(/%0# 1*2%3& 10

Example: Simulink Model Integration (Vehicle dynamics) GME integration model Original Simulink model (X4 simulator) Add input-output bindings Input binding Code generation Output binding Modified model Generated .m Receiver and Sender S-function code + .java code for representing Simulink federate RTI runtime communication Signal flow Signal flow HLA Run-Time Infrastructure (RTI) !"###$%&'()&&*+ ,)-.&#!*&(/%0# 1*2%3& 11 Multi-modeling with C2WT Three levels of modeling & customization: Modeling the modeling tools - ! Infrastructure Performed “one-time” when a new simulation " platform (model type) is integrated [usually by developers] Modeling the integration of the models – ! Scenarios Performed when a new scenario has to be " experimented [usually by subject matter experts who can describe scenarios] Requires: " • Models of model tools used (‘federates’) • Data models • Integration models: Interactions among the models Modeling the situations – Experiments ! " Execution platform, experiment setup, deployment [usually by experimenters who can parameterize experiments and analyse !"###$%&'()&&*+ experimental results] ,)-.&#!*&(/%0# 1*2%3& 12