1. Technology to the Warfighter Quicker SBIR Phase II IPR - 1/26/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 Agg/Deagg Projects / Funding –Army –Navy Task Overview BAF Spec Work BARN / AAXE Discussion –Projects WARSIM ONESAF –Future Demos Financial Picture

3. Technology to the Warfighter Quicker 3 Agg/Deagg SBIR Projects / Funding 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) BOM Assembly -> Model Aggregation BOM w/ container support -> Entity Instance Aggregation Development / Release of Spec and Guidance Doc SIW Paper – 05S-SIW-091 / 06S-SIW-116 Demo concurrent with 05 Fall SIW I/ITSEC Paper/Presentation 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 (BAF 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 Demonstratable repository developed in MySQL UDDI being explored for connection with other repositories 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 WARSIM potential fit as agg level sim BASS inline with federation to provide services RTI used as communication mechanism April SIW Demo (06S-SIW-116) Identify and Establish DoD and Commercial Partners Maintain Community Involvement Schedule and Conduct IPRs

5. Technology to the Warfighter Quicker 5 BAF Spec Work (1/6)

6. Technology to the Warfighter Quicker 6 BAF Spec Work (2/6)

7. Technology to the Warfighter Quicker 7 BAF Spec Work (3/6)

8. Technology to the Warfighter Quicker 8 BAF Spec Work (4/6)

9. Technology to the Warfighter Quicker 9 BAF Spec Work (5/6)

10. Technology to the Warfighter Quicker 10 BAF Spec Work (6/6)

11. Technology to the Warfighter Quicker 11 Spec Work - Load Support Doctrine

12. Technology to the Warfighter Quicker 12 Spec Work – Sequence Diagrams See separate PPT

13. Technology to the Warfighter Quicker BAF Automation with RCIP Navigator (BARN) Effort SimVentions 12/1/2005 to 10/1/2006

14. Technology to the Warfighter Quicker 14 BARN Team Design Support –Tram Chase (Lead) –Matt Morgan –Jerry Oesterheld –Ben Sisson - Eclipse/ Web Srvc SME –Brad Neal - RCIP Navy SME Development Support –Matt Morgan (Lead) –Tram Chase (Oversight) Additional Support –Larry –Paul

15. Technology to the Warfighter Quicker 15 BARN Overview What is 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. 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 DMSO Composability

16. Technology to the Warfighter Quicker 16 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)

17. Technology to the Warfighter Quicker 17 BAF Automation of the RCIP Navigator (BARN) Tool = Automation and Extraction Agent (AAXE) –prototype tool –Java-based, so that it is available 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? – Queries for a script file name – Executes script read in from file or manually entered Next Step –BAF (BASS) Integration Scripts exist already to execute the model in ProcessModel (i.e. RCIP Nav) and force export the data to an Excel spreadsheet.

18. Technology to the Warfighter Quicker 18 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.

19. Technology to the Warfighter Quicker Discussion / Questions? Paul Gustavson pgustavson@simventions.com 540 372-7727 (work) 540 429-2550 (cell) www.simventions.com/sbir_agg Projects WARSIM ONESAF Future Demos

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

21. Technology to the Warfighter Quicker Backup Slides

22. Technology to the Warfighter Quicker 22 entities > M1A - 1403 > M1A - 1404 > Apache - 132 How are we using BOMs? 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 Instance Aggregations

23. Technology to the Warfighter Quicker 23 BOMs being using - RPR BOMs RPR FOM 2.0 DIS 1278 GRIM Repair Resupply Entity Creation Entity Reconst’n Entity Removal Action Request Post Comment Post Event Conceptual Model Object Model Def EntityObjects EnvObjects MinefieldObjects SignalObjects Weapons Effect Collision Entity State Update Minefield Synthetic Enviro SIMAN Logistics RadioComms “The use of interaction classes involves a detailed understanding of the state transitions and timing between events.” - RPR FOM GRIM Model Mapping

24. Technology to the Warfighter Quicker 24 BOM Aggregation Framework 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 Service Oriented Architecture (SOA) FOCUS Loose coupling Minimize unnecessary dependencies BOM oriented interfaces

25. Technology to the Warfighter Quicker 25 BOM Aggregation Support Server BAF Implementation –Java (Eclipse) –Web Services –Independent WSDLs for each service group –Not dependent on dedicated server –Uses and generates BOMs –Apache Apache Tomcat/5.0.28

26. Technology to the Warfighter Quicker 26 SBIR Background/Objectives Develop a common framework for aggregating and deaggregating entities in simulations exercises to:  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 behavior validity throughout the aggregation levels Aggregation - the coupling of multiple models/entities into a single inclusive group

27. Technology to the Warfighter Quicker 27 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 composed of a group of interrelated elements, which can be used as a building block in the development and extension of a federation, individual federate, FOM or SOM. BOM elements include object classes, interaction classes, patterns of interplay, state machines, and events. Weapons Effect Radio Comms Repair Resupply Detect / Jam DefinitionConceptStandards Illustration Using Base Object Models (BOMs) as Building Blocks

28. Technology to the Warfighter Quicker 28 Why a BOM Approach? Offers modular way to represent simulation exchange elements Platform independent (XML) Captures / carries forward conceptual model Allows implementations to be represented independently Can be combined to form compositions (model aggregation) Can be used to define container classes (entity instance aggregation) Facilitates interoperability (the exchange of data) –BOMs can be mapped across different BOMs, FOMs and SOMs BOM – a piece part of a conceptual model composed of a group of interrelated elements, which can be used as a building block in the development and extension of a federation, individual federate, FOM or SOM. BOM elements include object classes, interaction classes, patterns of interplay, state machines, and events. 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 Weapons Effect Radio Comms Repair Resupply Detect / Jam

29. Technology to the Warfighter Quicker 29 BOM Elements a component-based standard describing reusable piece parts of a simulation or simulation space. BOMs can be used to document one or more of the following piece part elements: –Conceptual Model Patterns of interplay State machines Entities Events –Interface Description Object classes / attributes Interaction classes / parameters –Mapping between Conceptual Model and Interface Description Used as a building block in the development and extension of a simulation and/or a federation of simulations. Provides developers and users a modular approach –for defining and adding new capabilities to a federate or federation, –for quickly composing object models such as HLA FOMs and SOMs through BOM Assemblies. 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 Definition Pattern of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping

30. Technology to the Warfighter Quicker 30 Automation and Extraction Agent (AAXE) PLANNED OR IN PROGRESS Rebuild the interface to be more “production friendly” Add a file dialog to allow easy selection of scripts Add a list of common commands for easy reference (help section) Revamp the command language (low priority) Add support for BOM extraction from Process Model Excel spreadsheet export Modify and generate scripts as needed UNDER CONSIDERATION Create a script building tool to assist in script generation Process Model (i.e. RCIP Nav) Export Data PLANNED OR IN PROGRESS Analyzing exported data for identification of BOMs Generate unique filename for export to individual runs are not overwritten

31. Technology to the Warfighter Quicker 31 What are the RCIP Navigator Features? Focus on Open Architecture (OA) and Spiral Technology Insertion Assist in the management and reporting of a capability that is moving through the various stages of the insertion process Identify the RCIP steps the capability must step through - based on program ACAT level (SHIPMAIN impact), number of interfaces (testing impact), weapons involvement (WSERB impact) and complexity (Sea Trial impact) Assist in the packaging of capabilities that can be rolled-up into the Navy’s planned bi- annual introduction of new warfighter technology into fleet programs Automate the generation of technology roadmaps which will enable users to perform capability roll-ups by date, warfighter gap, major program and insertion platform Automate the generation of capability “Quad Charts” used by the Program Managers to brief their programs Identify capability inter-dependencies to ensure that the bi-annual introduction packages contain all of the technology required to support the insertion Wizard support Web Accessible Ability to leverage BOM repositories, BOM tools, and BOM-based simulation environments to assist in the required analysis <- extensions required

32. Technology to the Warfighter Quicker 32 Integration into OA CT3 Program NSWCDD desires to improve its methods for the ‘eXchange of Knowledge’ (XK) for both technical and programmatic XK efforts include: –efforts within current and emerging DoD systems and systems-of-systems; and, –efforts within existing Science & Technology (S&T) activities [i.e., SBIRs, Advanced Concept Technology Demonstrations (ACTDs), Rapid Technology Transitions (RTTs)]. NSWCDD is initially interested in those S&T activities that have been identified by the Capability Technology Transition Team (CT3) as candidates for the Rapid Capability Insertion Process (RCIP). XK needs –Provide analysis / RCIP insight –Assist in the determination of capability and/or program candidates. –Used as a decision-support aides –Potential adopters – could be used by the Navy to support spiral technology insertion decisions and development planning for new ship designs and existing ship modernizations. RCIP currently an emerging process that will require refinement and modification as it moves forward. NSWCDD desires that the processes and technologies used to help move this forward will also contribute to better and more effective ways of providing and monitoring the RCIP, and perhaps provide Joint applicability.

33. Technology to the Warfighter Quicker 33 End-state Capability (i.e. RCIP Navigator Function & Use) facilitates the tracking and analysis of emerging technologies important to CT3 and the RCIP, would become the heart of the OA CT3 Coordination efforts, would be used by all levels of management. This effort relies on the establishment of the –XK Framework (i.e., extension of the BOM Aggregation Framework (BAF) currently being developed in the Phase II), –the M&S Test and Analysis Tool (MSTAT) (i.e., could be a BOM capable OneSAF Objective System (OOS) currently being considered in Phase II -- MR - Federate), and –the RCIP Navigator. The focus will be BOM-based so as to provide rapid, repeatable analysis and technology assessment capabilities. M&S technologies, such as the BOM, will be used –to maximize the re-use of emerging technology models (like the RPR BOMs) and –to create the ability to “mix-and-match” emerging and existing technologies to assess potential new warfighter capabilities and associated life-cycle system engineering implications. We will use this effort to support the final definition and generation of the RCIP.

34. Technology to the Warfighter Quicker 34 Original Schedule (now moved earlier to start 1 Dec 2005)

35. Technology to the Warfighter Quicker 35 Use of OOS

36. Technology to the Warfighter Quicker 36 Terminology TermDefinition AbstractionAn idea that concentrates on the essential properties of a common pattern of interplay rather than on concrete realizations or actual cases. Aggregationthe coupling of multiple entities/models into a single inclusive group Behavior Componentsmodel the needed behavior required of a conceptual entity to support patterns (Federate level) BOMa piece part of a conceptual model composed of a group of interrelated elements, which can be used as a building block in the development and extension of a federation, individual federate, FOM or SOM. ComponentA unit with a known set of inputs and expected output behavior, but the implementation details may be hidden. Composability“The capability to select and assemble components in various combinations into complete, validated simulation environments to satisfy specific user requirements across a variety of application domains, levels of resolution, and time scales.” [1] [1] Fidelitythe level of attribution in the model at a given level of resolution; Load Balancingdelegation of work responsibility among a federation to prevent overtaxing an individual federate and/or network and to ensure proper execution BOM AssemblyA composition of BOMs used to represent a higher order pattern. Pattern ComponentsRepresenting the relationship of activities among conceptual entities (FOM level), Pattern of Interplayreflects a set of activities related to one or more conceptual entities used for accomplishing a common objective, capability, or purpose Precisionthe accuracy of attributes and parameters in the model during input, processing, and output. Resolutionthe level of abstraction in the simulation or model, defining the things to be modeled; Simulation SpaceAny part of a simulation environment, which may be represented by one or more conceptual entitles modeled and reflected by a federate, federation, or as an aggregated force within a federation execution. [1] [1] M. D. Petty and E. W. Weisel, “A Composability Lexicon”, Proceedings of the Spring 2003 Simulation Interoperability Workshop, Orlando FL, March 30-April 4 2003, 03S-SIW-023.

37. Technology to the Warfighter Quicker 37 Some Details – BOM Aggregation Types Model Aggregations –Interface Groupings –Non-exercise specific (class based) –Examples Car (Engine / Wheels / Suspension / Braking System / Frame) Ship (Weapon System / Radar / CIC) Equipment Pack (Ammo / Weapon / Grenade / Water / First Aid Kit / MRE) First Aid Kit (Gauze / Wrap / Ointment / Knife / Aspirin / Blood Clot (kitty litter)) Human Anatomy (Heart / Liver / Kidney / Digestion system, Epidermis, etc…) Entity Instance Aggregations –Entity Groupings –Exercise specific (object driven) –Examples Battalion (Collection of Individual Soldiers) Air Squadron Battle group Weather (Storm Cells / Wind / Temperature / Atmospheric Pressure/ Bathymetry) Close Air Support (Forward Air Controller / Aircraft / Target / Target Locater / Designator) Crowds Composite PatternFlyweight Pattern

38. Technology to the Warfighter Quicker 38 Aggregate Triggers/Criteria Proximity to a specific obstacle, entity or feature in the synthetic battlespace; A change in the level of interest or significance regarding the specific domain a model supports; or An increase (or decrease) in the physical entity load by the system and/or over the entire federation.

39. Technology to the Warfighter Quicker 39 Federate Service-oriented Architecture (SOA) Loosely Coupled Approach Minimize Unnecessary dependencies among systems and software Maintain functionality / individuality Potential Technologies –XML –WSDL –SOAP / XML-RPC –UDDI –BOMs –XSLT (FOM Mappings, BTMs –BOM Impl (Java Beans) Other Technologies (not SOA) –Network Distribution (RTI) –Federation Agreements (FOM) BAF Design – Architecture View http://www.informit.com/articles/article.asp?p=336265&seqNum=1 BOMs Federates Interface elements discovery services messaging BAF Web Services The common interface must be leveraged by all participating software agents (i.e. federates) That the interfaces must be accessible and understood by all providers and consumers Interfaces serve as the framework for the messages that are to be exchanged Minimal system behavior is provided by these interfaces (or messages) An XML schema should be applied to define the vocabulary and structure Additional services should be able to be added without impairing the common interface. Service Oriented Architecture (SOA) FOCUS