1. 1 SBIR Phase II Final Report 10/18/06 Paul Gustavson (Principle Investigator) Ben Sisson (BASS Engineer) Tram Chase (BOMworks Engineer) SimVentions, Inc Mike Haddad PEOSTRI – SBIR POC

2. 2 Topics 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion OBJECTIVE: To discuss accomplishments of Phase II effort

3. 3 SBIR Background GOAL: –Develop a common framework for aggregating and deaggregating entities in simulations exercises OBJECTIVES:  Facilitate interoperability between models at different levels of fidelity (allowing agg-level sims to interact with entity-level sims)  Improve system performance for distributed exercises Reduce memory load Reduce CPU load Reduce network load  Manage entity count depending upon system load  Preserve simulation behaviour validity throughout the aggregation levels Aggregation - the coupling of multiple models/entities into a single inclusive group 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion

4. 4 Our Approach Use BOMs to represent aggregated and non-aggregated models and entities –Offers modular way to represent simulation exchange elements –Can be combined to form compositions (model aggregation) –Can be mapped with / produce FOMs –Can be used to define container classes (entity instance aggregation) Design of a loosely coupled (i.e. SOA) framework –Offers well defined interface via Web Services API –Can benefit different simulations / environments (w/ minimal impact) Entity level / Aggregate Level Implementation of BAF web services –Java used to maximize integration and deployment –Provides ability to Monitor exercise (i.e. exchange of information) –Provides Aggregation / Deagg Solutions When requested When triggered* BOM – A piece part of a conceptual model, simulation object model, or federation object model, which can be used as a building block in the development and/or extension of a simulation or federation. *capability still under development 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion

5. 5 Highlights BAF Specification – Version 1.0b (2/1/06) – Version 1.1 (8/31/06) BASS Implementation – Now Live @ http://67.78.242.14 – Represents SimVentions implementation of BAF 1.1 core functionality – Last Demonstrated on 8/23/06 to WarSim Demo-ware – SV-AGG – BOMworks w/ BASS Exerciser Plug-In Programs of Interest – Objective OneSAF – WARSIM – MDA Community BOMs Developed / Used – RPR BOMs – WARSIM BOMs Use of TR-Tracker Tool to track comments White papers / presentations: 04S-SIW-048 – “The Application of BOMs for Supporting Aggregation and Load Balancing” 04S-SIW-052 – “The application of BOMs for Enabling Multi-Resolution Modeling* 05S-SIW- “Moving Towards an SOA for Distributed Component Simulation Environments.” 06S-SIW-115 – “From FOMs to BOMs and Back Again” 06S-SIW-116 – “Adding Aggregation Services to the Mix: An SOA Implementation Use Case” Efforts reflected @ http://www.simventions.com/sbir_agg/ Exerciser 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion

6. 6 Highlights – BAF Spec Simulation Client Simulation Client BAF Server Simulation Client - Agg Solutions - Deagg Solutions -Transfer Control - Load Support Entities Aggregated Entities

7. 7 Highlights - WARSIM FOM Decomposition 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion Explore using Dilemma “Bridging constructive, virtual, live and embedded simulations remains a relevant, challenging, and under-addressed problem”* “The FOM lies at the center of the interoperability challenge...”* Resolution Isolate WARSIM FOM elements into manageable modules (aka BOMs) –Provides logical Simulation Exchange Elements –Easy to reconstitute (composable) –Useful for supporting agg / deagg *Conclusions made by paper/presentation titled 02S-SIW-002 COMPOSABILITY - “The ability to rapidly select and assemble components to construct meaningful simulation systems to satisfy specific user requirements. Composability includes the framework, body of knowledge, tools, techniques, and standards necessary to enable effective integration, interoperability, and reuse.” - (DoD M&S Master Plan)

8. 8 Highlights – BW-BASS Exerciser Exerciser Aggregate / Deaggregate Reflection Battalion Platoon A Soldier 1Soldier 2 Soldier XSoldier Y Platoon B Aggregate Deaggregate Aggregate 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion

9. 9 Highlights – SIW Papers

10. 10 Highlights – SIW Papers

11. 11 Highlights – SIW Papers

12. 12 Highlights – SIW Papers

13. 13 Phase II BAF Task Overview TasksObjectivesCurrent / Recent Activities Develop and Apply BOMs and BOM Assemblies for representing aggregations Define BOM representations for supporting interfaces of entities and aggregated entities. Use of available implementations (BCIs) that can support interface Application of metadata to support BOM dimensions Leverage other products and technologies (including MRMs) Update to BAF spec 1.1 Final Release of BOM Spec and Guidance Doc SIW Paper – 06S-SIW-115 / 06S-SIW-116 I/ITSEC Tutorial FOM (WARSIM / ACTF) breakdown to BOMs Develop a common framework for aggregating and deaggregating entities in simulations exercises Identify requirements of architecture Define specification detailing the set of available functions Implement services described by specification BAF Design Spec contains 4 major service groupings BOM Aggregation Support Server (BASS Implemtn) Connect the BOM Aggregation Framework web-service to a repository Interface with online repositories containing available models (BOMs, BTMs, BCIs, etc…) Take advantage of BOM metadata Demonstrated repository developed in MySQL UDDI being explored for connection with other repositories Connected BOMworks and AAXE to BASS web-service repository WARSIM and ACTF BOMs stored in repository Demonstrate the BOM Aggregation Framework with constructive simulations Demonstrate Interoperability between BOMs at different levels of aggregation across domains Demonstrate dynamic aggregation and deaggregation based upon system load accomplished by swapping and application of BOMs (and BOM Assemblies) OOS received from PEOSTRI, intended to serve as entity driver using RPR FOM and RTI SV-AGG, developed in house, to serve as aggregate level sim BASS inline with federation to provide services Regression tested upgrades related to BAF spec 1.1 BOMWorks BASS Exerciser (w/ Google Earth) Identify and Establish DoD and Commercial Partners Maintain Community Involvement Schedule and Conduct IPRs

14. 14 Discussion - Current Status Phase II Base Expended (Sept’06) –BASS (i.e., BAF Implementation) Updated to Final Specification During BARN Execution –Deliverables Final Report BAF Spec BASS BOMWorks Executable (w/ BASS Exerciser) Phase II Plus-ups –BARN 65% Complete (Dec’06) –CMOD 10% Complete (May’07) 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion Mar 06 – Complete BASS implementation to BAF version 1 April 06 (Spring SIW – Huntsville) – BASS / SV-AGG demo (compliant with BAF version 1) – 06S-SIW-116 – “Adding Aggregate Services to the Mix: An SOA Implementation Use Case” – BOMworks 1.0 release! July 06 – WARSIM collaboration? – OOS collaboration? – Orlando / VA Demo Aug 06 – BAF Adjudication of Interface Spec (v1.0) Sept 06 (Fall SIW) – Orlando Demo Oct 06 – Phase II Final Report Dec 06 – BARN Completed May 07 -CMOD Completed

15. 15 Discussion – Way Ahead BASS / BOMs is an “enabling technology” –BAF/BASS Concept Proven –Interest From Community Growing Potential Opportunities –Integration of BASS into Program(s) –Extension of BASS Services and Automation –BOMworks Tool Components and Application to Program(s) –Multi-resolution modeling Orlando Presence –SimVentions Available and On Site Phase III Contract Available –ID/IQ Sole Source Contract –Large Ceiling –SOW Supports Agg/Deagg and Tool Development Activities and Integration 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion SBIR Phase II Quality Award Criteria  originality and innovation of research  relevance of the research to the Army mission  immediate commercialization potential of the research, reflecting the primary goal of bringing technology and products to the marketplace  overall quality performance of the project. http://www.armysbir.com

16. 16 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion

17. 17 Phase III Funding 1.Brief overview of SBIR effort Background Approach Highlights 2.Task Overview 3.Discussion

18. 18 Further Discussion / Questions? Paul Gustavson pgustavson@simventions.com 540 372-7727 (work) 540 429-2550 (cell) Mike Haddad Mike.haddad@us.army.mil (407) 384-3853 (work) www.simventions.com/sbir_agg

19. 19 Backup Slides

20. 20 Phase II Plus Up - BAF Automation of the RCIP Navigator (BARN) RCIP - Rapid Capability Insertion Process the overarching process for rapidly introducing new capabilities and technologies to warfighters Uses – open architecture and – spiral evolutionary development. Differs from traditional military acquisition since the emphasis is on hardware / software independence and attempts to maximize software reuse. Process models defined using BOMs Automation and Extraction Agent (AAXE) Tool prototype tool built on Galileo FW and BOMworks Java-based, so that it is available on multiple platforms Capable of automating the execution process of the model using BOMs Leverages BAF web services – Use of Model Aggregation – Library calls to Repository Built on AAXE Use of BAF Calls

21. 21 CMOD Generator Analyze Leverage Phase II Plus Up – Conceptual Model (CMod) Generator Analyze underlying design within a simulation Leverage existing informal conceptual model information BOM conceptual model view as a standard template for the production of formal conceptual models DoDAF OV-1 Extension to

22. 22 Our Approach to BAF Supported Aggregations 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion Model AggregationEntity Instance Aggregation Aggregation Types Producer - 1 st LevelConsumer - 2 nd Level Aggregation Levels Containment of related instance information (BOM container) Summation of models (BOM assembly) ∑

23. 23 entities > M1A - 1403 > M1A - 1404 > Apache - 132 Our Approach How we used BOMs with BAF? Mapped to BOMs FOM Simulation Data exchange interface elements Model Aggregations Subsystem models BOMs gun radar vehicle soldier Humvee platform Composite pattern BOM > agg -123 Flyweight pattern Entity Instance Aggregations

24. 24 Proximity to a specific obstacle, entity or feature A change in the level of interest An increase (or decrease) in the physical entity load Possible aggregation due to proximity to geographical location or point Possible aggregation due to proximity to client entities or domain of interest Our Approach to BAF Agg/Deagg Triggers/Criteria

25. 25 Federate (SOM) BOM Assembly BOM 1 BOM 3 BOM n Composite Interface Composition Sim / System A Representation Federation (FOM) Federate B Federate X Federate A Aggregation Model #1 Model #2 Model #3 Model #n - or - Theater Warfare Representation BOM 2 BOMs are designed for enabling composability, providing extensibility, facilitating interoperability, improving manageability, and encouraging understandibility. BOM Palette -x Choose what fits conceptual model? A B C X State Machines Pattern of Interplay Events User Requirements Simulation Components Simulation Systems foms federates BOM – A piece part of a conceptual model, simulation object model, or federation object model, which can be used as a building block in the development and/or extension of a simulation or federation. Weapons Effect Radio Comms Repair Resupply Detect / Jam DefinitionConceptStandards Illustration Key Concept - Using Base Object Models (BOMs) as Building Blocks

26. 26 BOM Illustration #1 Derived from RPR FOM State Machines Pattern of Interplay pattern actions Weapons Effect states Federation ActivitiesFederate Capability

27. 27 BOM Illustration #2 Jammer (Originator) Radar Threat Detected in Range (Msg) Threat / Target Emits Reflects Detect Jam Detection Jamming Pattern of Interplay State Machine Detect /Jamming Activity Federation ActivitiesFederate Capability Here there are actually two patterns of interplay “Detection” and “Jamming” We could conceivably use the “Detection” pattern for other purposes besides just “Jamming” such as “Vectoring Interceptors”

28. 28 Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping What is a BOM really? An Inside Look Not all these pieces are required for a BOM… Essential metadata needed so that the BOM can be described, discovered and properly reused Conceptual entities and the events which occur among those entities as well as the states attainable by those entities. Mapping of conceptual entities and events to object model object and interaction classes. Notes and definitions supporting any of the above mentioned elements Object classes, interaction classes, and datatypes used to perform the behavior described in the conceptual model. An XML based standard for capturing model metadata, aspects of the conceptual model, the class structures of an object model which are to be used by a system (and a federation) for representing the conceptual model aspects, and the mapping that exists between that conceptual model and object model. BOM template allows BOMs to be captured in a reusable way

29. 29 Hierarchical View of the RPR BOMs… RPR FOM 2.0 Repair Resupply Entity Creation Entity Reconst’n Entity Removal Action Request Post Comment Post Event Behavior Rep Object Rep EntityObjects EnvObjects MinefieldObjects SignalObjects Weapons Effect Collision E ntity S t U pdate Minefield Synthetic Env SIMAN Logistics RadioComms Includes Model Mapping Behavior Representations Weapon Effects Logistics Support Collision Entity State Update Simulation Management Distributed Emission Regeneration Radio Communications Entity Management Minefield Synthetic Environment Behavior Representations Weapon Effects Logistics Support Collision Entity State Update Simulation Management Distributed Emission Regeneration Radio Communications Entity Management Minefield Synthetic Environment Object Representations Entity Object Types Env Object Types Minefield Object Types Signal Object Types Object Representations Entity Object Types Env Object Types Minefield Object Types Signal Object Types

30. 30 How Are BOMs To Be Used…Functionally? Profile BOMs BOM 1 BOM 2 BOM n Conceptual Model View Object Model View Weapons Effect Detect / Jam Radio Comms BOM z Sup plier BOM b BOM a Platform Human BOM c BOM d Radar Munition Logistics CAP Support Collision BOM Assembly Composite Interface Composition Representation Federate B Federate X Federate A Theater Warfare Representation Federation for Joint Training Homeland Defense Training FOM Operation Freedom Training FOM Behavior (Conceptual) BOMs Object (Class Structure) BOMs These can be swapped out as modules New “Assemblies” can be “composed” and (for HLA) turned into FOMs

31. 31 How Comments are Captured/Tracked 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion Available at http://70.167.241.198/CommentTracker *Site Administered by SimVentions, Inc. Access is limited

32. 32 Demo #1 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion Create BOMsCreate BOMs Edit BOMsEdit BOMs –Grid/XML/UML –Cut/Copy/Paste Validate BOMsValidate BOMs Import/Export FOMsImport/Export FOMs –1.3/1516 Source Code GenerationSource Code Generation Built on Galileo Framework - extensible and customizableBuilt on Galileo Framework - extensible and customizable BOMWorks™ and Galileo Framework™ developed exclusively by SimVentions. Intellectual Property Owned By SimVentions. All Rights Reserved. BOMWorks™ Community Edition (BCE) Executable with limited capability is available to the public for free, but its distribution is restricted to citizens of qualified countries, which includes but is not limited to NATO members and its affiliates. For more information visit www.simventions.com/bomworks

33. 33 FOMs -> BOMs (Breaking up a FOM) 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion Model Identification (Metadata) Notes Lexicon (definitions) HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types HLA Dimensions HLA Time HLA Tags HLA Synchronizations HLA Transportations HLA Switches Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping FOMBOM

34. 34 Behind The Scenes What’s Happening w/ BOMworks Exerciser? - BOMworks creates “class instances” from BOM - Allows initializing of values with an XML init file - Allows offsets when creating multiple “class instances” at once - Allows “attachment” of behavior interfaceA behaviorA Instance1 interfaceA behaviorA Instance2 Aggregation “solution” from BASS provides BOM with new container class (interface) interfaceB Container Application of the aggregate “solution” is up to the Simulation!!! interfaceB Container behaviorA soldierInterface soldierbehavior Soldier1 soldierInterface soldierbehavior Soldier2 interfaceB Platoon platoonbehavior May require mapping 1 2 3

35. 35 Behind The Scenes What’s Happening w/ BASS? BASS creates the aggregate solution for BOMworks Exerciser How? – Participates as a passive player / monitors Simulation – Web Service request is made by BOMworks Exerciser BASS evaluates relative exercise data BASS builds a “solution” and returns the ID – BOMworks Exerciser fetches solution from BASS – Client applies Aggregation solution (see previous slide) What Solutions does BASS provide? – BOM (Container Class) – JavaScript 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion

36. 36 Behind The Scenes What’s Else is Happening? var reference = new Object(); reference.id_u = null; var common = new Object(); common.security_mark_0 = null; common.faction_id = 31;... SpiderMonkey C/C++ JavaScript plug-in Rhino Java – JavaScript plug-in BASS also provides JavaScript (dynamic code) solution for populating container since container class is “new” to the sim JavaScript could also be used to perform the mapping mentioned earlier for behaviors Sim can choose to keep instances “alive” while using container class / object –to preserve sim validity 100% Otherwise Sim can remove instances and use container object to deagg back to instances when needed –deltas in container are static if instances are deleted –depends on sims role, requirements, and where they want to benefit from aggregation network load, Memory savings CPU processing reduction 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion

37. 37 Google Earth Extensions Use Google Earth as a 3D Stealth tool Integration Includes –Live Captured Navy Tactical/Sensor Data –Simulation Data HLA DIS OneSAF Microsoft Flight Sim BOMworks/ BASS Includes Augmentation using –KLM –Sketch up –Google Maps overlay 1.Brief overview of SBIR effort Background Approach Highlights 2.WARSIM FOM decomposition to BOMs Benefits BOMworks Tool Analysis 3.Exercise of WARSIM BOM instances BOMworks Exerciser BASS (BAF Implementation) Google Earth 4.Discussion