1. Technology to the Warfighter Quicker SBIR Phase II IPR - 5/10/06 Paul Gustavson (Principle Investigator) Ben Sisson (Principle Engineer) Karl Crosson (BAF Developer) Matt Morgan (BARN Developer) Tram Chase (Developer) SimVentions Mike Haddad PEOSTRI – SBIR POC

2. Technology to the Warfighter Quicker 2 Topics SBIR Projects / Tasking –BAF –BARN –CMod Highlights –BAF and BASS –BOMworks –FOMs -> BOMs WARSIM ACTF –BASS Integration –BARN RCIP Navigator AAXE Discussion –Current Issues –Looking Ahead –Future SBIR Opportunities Financial Picture

3. Technology to the Warfighter Quicker 3 Agg/Deagg SBIR Projects / Success to Date Plus up

4. Technology to the Warfighter Quicker 4 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) Model / Entity Aggregation updated to BAF spec 1.0 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 –Aggregation Services –Library/Support Services –Monitoring/Intercessory Services –Transformation Support Services 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 –Waiting on new release to help with RTI issues SV-AGG, developed in house, to serve as aggregate level sim OneSAF quick start guide (for Navy) BASS inline with federation to provide services Regression tested upgrades related to BAF spec 1.0 Identify and Establish DoD and Commercial Partners Maintain Community Involvement Schedule and Conduct IPRs

5. Technology to the Warfighter Quicker 5 Phase II Plus Up - BARN Task Overview TasksObjectivesCurrent / Recent Activities Extend Selected BOMs and BOM Assemblies with Behavior Descriptions Explore aspects needed to support rapid process integration of “as-is” and “to-be” capabilities Enable early simulation of identified requirements for “quick look” analysis Recognized BOMs provide mechanism to support modeling “as-is” / “to-be” capabilities Outlining use of BOMs in RCIP process Mature the Capture of BOM Meta-Data from Users Facilitate rapid assembly of systems using RCIP Navigator through the use of BOMs Use BOMworks as tool to define RCIP supportive BOMs (planned) Maintain and populate BAF repository with RCIP BOMs (planned) Demonstrate RCIP Navigator Access to the BOM Component Repository Automate BOM use through RCIP Navigator Examined use of BAF / BASS to support process (i.e. loading, retrieval, aggregation). Design and Prototype a BOM- based Scenario Generator Validate BOMs for a given system with minimal time overhead Designed and Developed XML Script language to drive execution and integration of applications –Used by AAXE (see below) –automates (feeds) RCIP process modeling –Intended for insertion of BOMs (planned) Design and Prototype a BOM- based Component Simulation Environment Coordinate quick-look and assembly of systems using RCIP Navigator Evaluate BOMs for applicability to the given process or system being investigated Developed the Automation and Extraction Agent (AAXE) prototype – Java-based (uses our Galileo framework) – Uses prototype XML scripts language (see above) – Process Modeler integration (i.e. RCIP Navigator) – BASS integration Overall Objective – Add BOM-level functionality to RCIP Navigator so that BOMs can be used to perform a “quick-look” simulation analysis of “as-is” and “to-be” capabilities.

6. Technology to the Warfighter Quicker 6 Phase II Plus Up - CMod Task Overview TasksObjectivesCurrent / Recent Activities Represent ONESAF Objective System as a Set of BOMs Represent WARSIM as a Set of BOMs identify process for extracting BOMs from existing simulations, develop tools to assist in support the extraction of the information into a representative set of BOMs; Generate a set of OOS BOMs. Generate a set of WARSIM BOMs Began preliminary collection of system information and related data needed to formulate and populate OOS / WARSIM BOMs; Performed manual breakdown of –RPR FOM ->RPR BOM –ACTF and WARSIM FOM to BOM Experience Provides basis for tool Extend OOS and WARSIM BOMs to Include Conceptual Model Information complete the capture of conceptual model information for each BOM. Update tools to support the collection and entry of conceptual model information mature set of OOS and WARSIM BOMs. Provide value added to OOS program and WARSIM program via a set of BOMs future Demonstrate Use of Established BOMs within BASS/BAF Demo BOMs generated by Tool) for BAF/BASS Library Support future Demonstrate Application of BOMs for Agile OOS-to-WARSIM Interchanges Demo BOMs generated by Tool for BAF/BASS Exercise Support during a OOS-to-WARSIM exercise future Overall Objective – Develop a tool to assist in the reverse engineering of a set of existing systems and extract their models (i.e., FOMs) into reusable BOMs: BOMs that can be used in understanding each system’s capabilities at the conceptual level. Resulting tool (identified as CMod Generator) is intended to provide a mechanism to support conceptual execution of a proposed models and capabilities.

7. Technology to the Warfighter Quicker 7 Highlights - BAF and BASS BAF Specification version 1.0b –SOA Design Spring SIW white papers / presentations: –“Adding Aggregation Services to the Mix: An SOA Implementation Use Case” –“From FOMs to BOMs and Back Again” BAF Specification 1.0 Usage –BASS implementation –BOMworks Client –AAXE Client Tracking comments related to BAF specification 1.0 Efforts reflected at blog: http://www.simventions.com/sbir_agg/ http://www.simventions.com/sbir_agg/ Being updated to reflect BAF Spec 1.0b –Entity Aggregation Services –Model Aggregation Services –Session Support Services –Library Support Services –Error Handling Services Links to the BASS Web Services: http://162.83.93.18:8080/ http://162.83.93.18:8080/ BASS Services JSP Clients –Axis Services WSDL –BAF Specification –BASS and BAF Comments Incorporated BASS Session and Library Services into BOMworks and AAXE

8. Technology to the Warfighter Quicker 8 Highlights - BOMworks Create BOMsCreate BOMs Edit BOMsEdit BOMs Grid/XML/UMLGrid/XML/UML Cut/Copy/PasteCut/Copy/Paste Validate BOMsValidate BOMs Import/Export FOMsImport/Export FOMs 1.3/15161.3/1516 Source Code GenerationSource Code Generation Built on Galileo Framework - extensible and customizableBuilt on Galileo Framework - extensible and customizable.NET Version available Java Version delivered to DMSO last month!! www.simventions.com/bomworks

9. Technology to the Warfighter Quicker 9 Highlights - FOMs -> BOMs BOMworks was used to breakdown the WARSIM and ACTF FOMs Manageable BOMs that represent the FOM BOMs stored in BASS repository BOMs can be assembled and transformed back to a FOM ACTF FOM WARSIM FOM ACTF BOMs WARSIM BOMs

10. Technology to the Warfighter Quicker 10 Highlights - FOMs -> BOMs (Breaking up a FOM) 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 FOM BOM

11. Technology to the Warfighter Quicker 11 Highlights - FOMs -> BOMs ( Warsim BOMs) Warsim FOM Conceptual Model Object Model Def ManagerObjects MTProcessorObjects GameObjects WorkstationObjects Adapter Control RemoteOperation Model Mapping c2Artifacts WimModelObjects EnvObjects ScenarioObjects ItemObjects ItemTypeObjects OtherObjects Adapter Control FederationOperation Log Control Application Report InformationExchange Manager Game Initialization Adapter Control Adapter Control Acknowledge Control Information Exchange Trigger Application Report Scenario Parameters Restart Pending Remote Update Request Remote Delete Remote Create Federation Save Requested Manager Root Int Federate Federation Network Master Track Processor MTP TO MTP TEO Root Obj Workstation C2 Artifacts Wim Model Synthetic Natural Environment Side Scenario Faction Item Type Other Item USMC Naval Land JOISIM Air Tasking Natsim Nasm Initialization Gold Nugget Comms AF Platform Civil Env Facility Org Interaction BOMs Object BOMs Initialization Complete

12. Technology to the Warfighter Quicker 12 WarSimBOMs Based on ACTF FOM v3 Highlights - FOMs -> BOMs (Warsim BOMs)

13. Technology to the Warfighter Quicker 13

14. Technology to the Warfighter Quicker 14

15. Technology to the Warfighter Quicker 15 Highlights - FOMs -> BOMs (ACTF BOMs] ACTF BOMs Based on ACTF FOM v3

16. Technology to the Warfighter Quicker 16 BOMs BOMWorks BOMs Highlights - BASS Integration BASS BASS ClientAAXE BASS Database Management System BOMworks helps break down FOMs into BOMs FOM But what do you do with the BOMs? How do you manage them? Use the BASS Library Management System - Add BOMs to the Library - Discover BOMs in the Library - Pull BOMs from the Library What if I have other items? - Used to manage items of different types FOMsData

17. Technology to the Warfighter Quicker 17 Highlights - BARN Overview RCIP Nav BAF Automation w/ RCIP Nav (BARN) DMSO Composability Effort BAF Modeling the Impact of Technology Transition on Ship Capabilities (N-05-053)

18. Technology to the Warfighter Quicker 18 Highlights - BARN Overview What is the RCIP Navigator? –Represents a wizard-style approach to assisting Program Managers, PEOs, OPNAV and other users in navigating their efforts through the RCIP. –Also provides web-accessible views of all programs within the RCIP, allowing high-level monitoring and status reporting as needed. What integration is required for BAF Automation of the RCIP Navigator? –RCIP Navigator will utilize Base Object Models (BOMs) to support the RCIP process –Provide capability (via BOMs) to determine/evaluate proposed and existing capabilities and systems. –Leverage and use BAF accordingly Related work – N-053 - Modeling the Impact of Technology Transition on Ship Capabilities

19. Technology to the Warfighter Quicker 19

20. Technology to the Warfighter Quicker 20 BAF Automation of the RCIP Navigator (BARN) Tool = Automation and Extraction Agent (AAXE) –prototype tool –Java-based, –runs on multiple platforms –Can integrate / wrap-around any client application E.g. RCIP Nav –Will leverage BAF web services & BOMs How does it interact with the RCIP Navigator? – Capable of automating the execution process of the model – Able to extract/write BOM info from the model’s execution output –Can be retooled as a component instead of a standalone application Where is it at this moment in time? –Executes XML script –Allows manipulation of XML scripts –BASS Integration (storage and retrieval of files) Scripts developed to execute the model in ProcessModel (i.e. RCIP Nav) and force export the data to an Excel spreadsheet. AAXE

21. Technology to the Warfighter Quicker 21 Highlights – BARN [AAXE and the Galileo Framework] AAXE inherits functionality from Galileo, upon which it is built Navigable XML tree diagram Syntax-highlighted XML Text View Synchronicity between tree and text views AAXE scripts are written in XML format Grid and Text Views (Text View shown)Direct script editing (also supported in Grid View) Grid View shows each script command broken into components

22. Technology to the Warfighter Quicker 22 Discussion - Looking Ahead (1/2) Plus up Our ’06 Schedule July Demo Sep Demo Nov Demo OneSAF WARSIM CAAB White Papers Phase III ? (see next slide) Other Topics

23. Technology to the Warfighter Quicker 23 Discussion - Looking Ahead (2/2) Our ’06 Schedule July Demo Sep Demo Nov Demo OneSAF WARSIM CAAB White Papers Phase III ? Other Topics

24. Technology to the Warfighter Quicker Follow on Discussion / Questions? Paul Gustavson pgustavson@simventions.com 540 372-7727 (work) 540 429-2550 (cell) www.simventions.com/sbir_agg

25. Technology to the Warfighter Quicker 25 Financials See separate PPT

26. Technology to the Warfighter Quicker Backup Slides

27. Technology to the Warfighter Quicker 27 Background - Minimizing the Obfuscation in the “Mix” - The Need for Aggregation Support Aggregation Obstacles –Models typically not built for aggregation –Simulation systems often have to be customized –Data loss during the aggregation process –limited resources to perform aggregation Aggregation Needs –Reduced customization of simulation systems –Minimal burden to manage aggregation by simulation systems –Maintain validity Aggregation - the coupling of multiple models/entities into a single inclusive group

28. Technology to the Warfighter Quicker 28 Background - SOA Use Case Design => BAF Service Oriented Architecture (SOA) FOCUS Common interface(s) Loose coupling Minimize unnecessary dependencies Aggregation Services –Model Composition aggregation / deaggregation –Entity Instance aggregation / deaggregation Library Support Services –Library Methods (load, search, fetch, add) –Support for BOMs, FOMs, BTMs, BCIs Monitoring/Intercessory Services –Data Logging Support –Load Balancing Support –Transfer Control Support –Model Transformation Support –Statistics/Scoreboard Support Support Services –BOM to FOM transformations –FOM to BOM transformations –FOM to FOM transformations BAF goals: Cost-effective mechanism for aggregation /deaggregation before or during large- scale simulation exercises Reduce high resolution models to more efficient lower resolution models that can be aggregated Allow models representing various levels of resolution and depth of aggregation to be able to interact with one another.

29. Technology to the Warfighter Quicker 29 Background - BAF Supported Aggregations Model AggregationEntity Instance Aggregation Aggregation Types 1 st Level2nd t Level Aggregation Levels

30. Technology to the Warfighter Quicker 30 Background - BAF Aggregate Triggers/Criteria 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

31. Technology to the Warfighter Quicker 31 Background - BAF Implementation => BASS Technologies Applied –Java (Eclipse) –Web Services –Independent WSDLs for each service group –Not dependent on dedicated server –Uses and generates BOMs –Apache Apache Tomcat

32. Technology to the Warfighter Quicker 32 entities > M1 - 1403 > M1 - 1404 > Apache - 132 Background - How BASS Uses BOMs for Aggregation RPR BOMs RPR FOM OneSAF Objective System Data exchange interface elements Model Aggregations Subsystem models BOMs gun radar vehicle soldier Humvee platform Composite pattern BOM > agg -123 Flyweight pattern Entity Aggregations

33. Technology to the Warfighter Quicker 33 Background - BARN Task General –Community involvement - SIW, Papers, I/ITSEC –maintain and populate a web-based repository Extend Selected BOMs and BOM Assemblies with Behavior Descriptions –BOM Component Implementations Mature the Capture of BOM Meta-Data from Users –User friendly capture process of metadata pre-fill all possible information based on already known details (such as user information, project information, etc.), limit the use of keyboard entry for the collection of information –Web service search / candidate list of BOMs recommend and/or allow use of other BOMs as a pattern template if an exact match cannot be found, provide pertinent graphical representation when at all possible, maximum the use of color to quickly reflect status and interest points to the user. –NOTE: feature not restricted only to RCIP Navigator Demonstrate RCIP Navigator Access to the BOM Component Repository ( –to be used by AAXE –Create a reusable component that can provide the access needed to interact appropriately with the BOM Component Repository. –Demonstrate the use and application of this component with RCIP Navigator – show “smart” access to the repository –Make use of rule-sets, access-mechanism, UDDI, etc… Design and Prototype a BOM supported Script Language –Script Language to be used by AAXE –Leverage metadata in BOMs to establish first- generation test scenario. –Use for a quick-check of the validity of the BOM-mix –SG capability may be represented as a web-service, such that BOMs and/or BOM-sets can be submitted and the first-order scenario returned. –The representation of the scenario would most likely be in an XML-based language set like the Military Scenario Definition Language (MSDL). Design and Prototype a BOM-based Component Simulation Environment –a “quick-look” simulation of the RCIP candidate capability formulate the set of BOMs into an executable model, ensure that the behavior has been appropriately described for the model, generate first-order scenario, and then execute the “quick-look” simulation. –The results from this simulation would then be delivered to the RCIP Navigator. –Possible candidates for this include Simulation Reference Markup Language (SRML), OneSAF Objective System (OOS) Java Beans, or even Macromedia’s Flash. –This environment could also be stood-up as a “BOM Evaluator” such that the results would be used to grade the completeness-level and complexity-level of the BOM, BOM Assembly, or BOM Aggregate. Overall Objective – Add BOM-level functionality to RCIP Navigator so that BOMs can be used to perform a “quick-look” simulation analysis of “as-is” and “to-be” capabilities.