1 / 35

SBIR Phase II Discussion / Demo 6/29/06

Paul Gustavson (Principle Investigator) Ben Sisson (BASS Engineer) Tram Chase (BOMworks Engineer) SimVentions Mike Haddad PEOSTRI – SBIR POC. SBIR Phase II Discussion / Demo 6/29/06. Brief overview of BOM Aggregation Framework SBIR effort Background Our Approach Current Capabilities

daphne-daniel
Download Presentation

SBIR Phase II Discussion / Demo 6/29/06

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Paul Gustavson (Principle Investigator) Ben Sisson (BASS Engineer) Tram Chase (BOMworks Engineer) SimVentions Mike Haddad PEOSTRI – SBIR POC SBIR Phase II Discussion / Demo 6/29/06

  2. Brief overview of BOM Aggregation Framework SBIR effort Background Our Approach Current Capabilities Presentation of WARSIM FOM decomposition to BOMs BOMworks View Composability Benefits Exercise of WARSIM BOM instances using BOMworks and BASS Preliminary demo of the multi-layered agg / deagg of WARSIM BOM models/entities.  Discussion Issues Schedule Next Steps  Topics

  3. 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 SBIR Background Aggregation - the coupling of multiple models/entities into a single inclusive group

  4. Our Approach Use of Base Object Models (BOMs) to represent both aggregated and non-aggregated models and entities Design of an SOA approach that could benefit different simulations / environments (w/ minimal impact) Implementation of BAF web services in Java to maximize integration and deployment

  5. Our ApproachWhy the use of BOMs? • 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, 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. Federate(SOM) Sim / SystemA WeaponsEffect BOM 1 BOM 2 Theater WarfareRepresentation Detect / Jam Federate A Federate B - or - Federation(FOM) BOM 3 BOMAssembly RepairResupply Representation Composition Federate X CompositeInterface - or - BOM n Model#1 Model#2 RadioComms Aggregation Model#3 Model#n

  6. Our Approach to BAFGoals / Capabilities Service Oriented Architecture (SOA) FOCUS • Common interface(s) • Loose coupling • Minimize unnecessary dependencies • Provide a common framework for aggregating and deaggregating models and entities • Facilitate Agg-level / entity-level interoperability • Reduce memory, cpu, & network load • Cost effective • What are its capabilities? • Produces aggregate / deaggregate solutions • Supports transfer control • Manages / stores entity / agg models (library) • Monitors exercise activities • Logger • Scoreboard • Load Balancing Automation • Transformation support • What are its key components? • Web Service Methods • Base Object Models • How is it offered / implemented? • BASS - an adjunct server application • Java • Web Services (SOAP) • SOA • Multi FOM Environments

  7. Our Approach to BAFSupported Aggregations Producer - 1st Level Consumer - 2nd Level Model Aggregation Entity Instance Aggregation Aggregation Types Aggregation Levels

  8. BAF Specification version 1.0b Update expected in Aug BASS Implementation Now Live @ http://70.167.240.174:8080 Represents 90% completion of BAF 1.0b Update expected in Sept Demo-ware SV-AGG BOMworks Now Plugs into BASS More planned! BOMs Developed / Used RPR BOMs WARSIM BOMs Recent white papers / presentations: 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/ Current CapabilitiesWhere Are We?

  9. Highlights - SV-Agg

  10. Highlights - WARSIM FOM Decomposition BOMworks™ Steps we took How we are using BOMs Demonstration Behind The Scenes Discussion - Composability Benefits

  11. Highlights - Use of 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 Community Edition recently delivered to DMSO www.simventions.com/bomworks

  12. Highlights - FOMs -> BOMs (Breaking up a FOM) Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping 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)

  13. Highlights - FOMs -> BOMs (Warsim BOMs) Explore using WarSimBOMs

  14. Nuts and Bolts - Mapping Entity DataComparing it to things we know JSIMS Object Class RPR Object Class Origin org.land.equip_group BaseEntity.PhysicalEntity.Platform RPR FOM abstract.land.equip_type abstract.land.rotary_wing_type org.land.unit platform.fwa BaseEntity.PhysicalEntity.Platform.-Aircraft RPR FOM WARSIM Object Class?

  15. Highlights Exerciser • Exercise of WARSIM BOM instances using BOMworks and BASS

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

  17. Behind The ScenesWhat’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

  18. Behind The ScenesWhat’s Else is Happening? • 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 var reference = new Object(); reference.id_u = null; var common = new Object(); common.security_mark_0 = null; common.faction_id = 31; ... SpiderMonkey C/C++ JavaScriptplug-in Rhino Java – JavaScriptplug-in

  19. Behind The ScenesWhat are the BAF Interface Methods Available? - Agg Solutions - Deagg Solutions -Transfer Control - Load Support BAF Server Simulation Client Entities Simulation Client Aggregated Entities Simulation Client

  20. Discussion - Composability Benefits “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...”* Benefits to BOMs Composability Better Manageability Easy to Reconstitute Helps Tie disparatesystems / simulations Live Constructive Virtual 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,andstandards necessary to enable effective integration, interoperability, and reuse.” - (DoD M&S Master Plan) *Conclusions made by paper/presentation titled 02S-SIW-002

  21. Discussion • How can we get more intimate with WARSIM? • Need to understand conceptual models and use of WARSIM FOM • How can we involve WARSIM team with development / use of • BOMs? • BAF/BASS? • Other topics? • 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 • Nov 06 • I/ITSEC Demo using WARSIM? • Dec 06 – Mar 07 • Continued integration (using CMod) • WARSIM integration? • Phase III contract vehicle in place? As Defined Feb 2006

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

  23. Backup Slides

  24. Two Views of the Same World Aggregate Units Disaggregated Battlefield Entities and Vehicles • BAF/BASS is trying to support these both. • BOMs provide an enabler for representation of these two representations

  25. Key Concept - Using Base Object Models (BOMs) as Building Blocks Pattern of Interplay Events State Machines Definition Concept Standards 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. BOM Palette - x Simulation Components Choose what fits conceptual model? User Requirements A B Simulation Systems • foms • federates X C Illustration Federate(SOM) Sim / SystemA WeaponsEffect BOM 1 BOM 2 Theater WarfareRepresentation Federate A Detect / Jam Federate B - or - Federation(FOM) BOM 3 BOMAssembly RepairResupply Representation Composition Federate X CompositeInterface - or - BOM n Model#1 Model#2 RadioComms Aggregation Model#3 Model#n BOMs are designed for enabling composability, providing extensibility, facilitating interoperability, improving manageability, and encouraging understandibility.

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

  27. BOM Illustration #2 Detection Jamming Pattern of Interplay State Machine Detect /Jamming Activity Jammer(Originator) Radar Threat / Target 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” Emits Reflects Detect Threat Detected in Range (Msg) Jam Federation Activities Federate Capability

  28. What is a BOM really? An Inside Look Model Identification (Metadata) Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Object Model Definition Event Type Mapping HLA Object Classes HLA Object Classes HLA Object Class Attributes HLA Interaction Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Data Types Notes Lexicon (definitions) Essential metadata needed so thatthe BOM can be described, discovered and properly reused 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 mappingthat exists between that conceptual model and object model. Conceptual entitiesand the events whichoccur among thoseentities as well as thestates attainable bythose entities. Not all these pieces are required for a BOM… Mapping of conceptual entities and events to object model object and interaction classes. Object classes,interaction classes,and datatypes used to perform the behavior describedin the conceptualmodel. Notes and definitionssupporting any of theabove mentionedelements BOM template allows BOMs to be captured in a reusable way

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

  30. How Are BOMs To Be Used…Functionally? New “Assemblies” can be “composed” and (for HLA) turned into FOMs These can be swapped out as modules Platform BOM a Human BOM b Munition BOM c Radar BOM d Supplier BOM z Behavior (Conceptual) BOMs Object(Class Structure) BOMs Profile WeaponsEffect BOM 1 Federate A Operation FreedomTraining FOM Homeland DefenseTraining FOM Collision Theater WarfareRepresentation Detect / Jam CAPSupport Federate B BOM 2 BOMAssembly Representation Composition Federate X RadioComms Logistics BOM n CompositeInterface FederationforJoint Training Object Model View Conceptual Model View BOMs

  31. BOM Element Validity Matrix SOM BOM Assembly Xformation FOM n BOMs Aggregate Model Remember, BOMs can take on different “forms”. This chart shows how different BOM Elements may constitute different types of BOMs That BOM Assembly can be transformed into FOMs, SOMs, or a representation of an Aggregate Model A BOM Assembly is a collection of one or more BOMs.

  32. Our ApproachHow are we using BOMs with BAF? radar Humveeplatform gun BOM BOMs vehicle Composite pattern FOM soldier Mapped to BOMs Subsystem models Simulation <<tank BOM>> M1A - 1403 <<container BOM>> agg -123 <<tank BOM>> M1A - 1404 Flyweight pattern <<helo BOM>> Apache - 132 entities • Data exchange interface elements • Model Aggregations • Entity Instance Aggregations

  33. Our Approach to BAFAgg/Deagg 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

  34. Why is Model Composability Desirable? • Creating a simulation requires breaking the problem into parts that can be addressed separately • To reduce the effects of interruption • To permit specialization • To facilitate computing alternative ways of handling a given component • To maintain the software over time • To reduce risk by relying upon previously proven components where possible • Understanding complex systems requires decomposition. • No one can comprehend the whole’s details • Testing systems is simplified if done module by module then at the system level • Controlling M&S costs / economic incentives • Costs are correlated with the amount of new code writing • Maintaining and modifying M&S • Individual modules can be substantively modified or updated as software as necessary, without endangering the overall system. “Modularity is necessary when dealing with complex systems, and some degree of composability is surely possible and desirable.” - Paul Davis (RAND)

  35. Summary - BASS Aggregation Process BOMWorks Simulation 1 Simulation 2 BASS • Information Simulation environment with many entities using WARSIM FOM BASS Database Management System WARSIM FOM Use BOMworks to breakup WARSIM FOM into manageable BOMs WARSIMBOMs Register BOMs to BASS through Library Management Capabilites - Add BOMs to the Library - Simulation clients exchange considerable information • Client requests aggregation solution - Aggregate Solution returned and applied

More Related