Download
sbir phase ii ipr 5 10 06 n.
Skip this Video
Loading SlideShow in 5 Seconds..
SBIR Phase II IPR - 5/10/06 PowerPoint Presentation
Download Presentation
SBIR Phase II IPR - 5/10/06

SBIR Phase II IPR - 5/10/06

124 Views Download Presentation
Download Presentation

SBIR Phase II IPR - 5/10/06

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. 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. 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 2

  3. Agg/Deagg SBIR Projects / Success to Date Plus up 3

  4. Phase II BAF Task Overview Identify and Establish DoD and Commercial Partners Maintain Community Involvement Schedule and Conduct IPRs 4

  5. Phase II Plus Up - BARN Task Overview 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. 5

  6. Phase II Plus Up - CMod Task Overview 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. 6

  7. 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/ 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/ BASS Services JSP Clients Axis Services WSDL BAF Specification BASS and BAF Comments Incorporated BASS Session and Library Services into BOMworks and AAXE Highlights - BAF and BASS 7

  8. Highlights - BOMworks • Create BOMs • Edit BOMs • Grid/XML/UML • Cut/Copy/Paste • Validate BOMs • Import/Export FOMs • 1.3/1516 • Source Code Generation • Built on Galileo Framework - extensible and customizable .NET Version available Java Version delivered to DMSO last month!! www.simventions.com/bomworks 8

  9. ACTF BOMs WARSIM BOMs 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 9

  10. Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Highlights - FOMs -> BOMs (Breaking up a FOM) Model Identification (Metadata) Model Identification (Metadata) HLA Object Classes HLA Object Classes HLA Object Class Attributes HLA Interaction Classes HLA Interaction Classes HLA Interaction Class Parameters BOM FOM HLA Dimensions HLA Time Object Model Definition HLA Object Classes HLA Tags HLA Object Classes HLA Synchronizations HLA Object Class Attributes HLA Transportations HLA Interaction Classes HLA Interaction Classes HLA Switches HLA Interaction Class Parameters HLA Data Types HLA Data Types Notes Notes Lexicon (definitions) Lexicon (definitions) 10

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

  12. Highlights - FOMs -> BOMs (ACTF BOMs] ACTF BOMsBased on ACTF FOM v3 15

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

  14. Highlights - BARN Overview DMSOComposabilityEffort RCIPNav BAFAutomationw/ RCIP Nav(BARN) Modeling the Impact of Technology Transition on Ship Capabilities (N-05-053) BAF 17

  15. 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 Highlights - BARN Overview Related work – • N-053 - Modeling the Impact of Technology Transition on Ship Capabilities 18

  16. 19

  17. BAF Automation of the RCIP Navigator (BARN) AAXE • 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. 20

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

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

  20. Follow on Discussion / Questions? Paul Gustavson pgustavson@simventions.com 540 372-7727 (work) 540 429-2550 (cell) www.simventions.com/sbir_agg

  21. Financials • See separate PPT 25

  22. Backup Slides

  23. Background - Minimizing the Obfuscation in the “Mix” - The Need for Aggregation Support Aggregation - the coupling of multiple models/entities into a single inclusive group • 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 27

  24. Service Oriented Architecture (SOA) FOCUS Common interface(s) Loose coupling Minimize unnecessary dependencies Background - SOA Use Case Design => BAF • 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 . 28

  25. 1st Level 2ndt Level Background - BAF Supported Aggregations Aggregation Types Model Aggregation Entity Instance Aggregation Aggregation Levels 29

  26. 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 30

  27. Background - BAF Implementation => BASS • Technologies Applied • Java (Eclipse) • Web Services • Independent WSDLsfor each service group • Not dependent on dedicated server • Uses and generates BOMs • Apache 31

  28. radar Humveeplatform gun BOM BOMs vehicle Composite pattern soldier RPR FOM RPR BOMs Subsystem models OneSAF Objective System <<tank BOM>> M1 - 1403 <<container bom>> agg -123 <<tank BOM>> M1 - 1404 Flyweight pattern <<helo BOM>> Apache - 132 entities Background - How BASS Uses BOMs for Aggregation • Data exchange interface elements • Model Aggregations • Entity Aggregations 32

  29. 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. Background - BARN Task 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. 33