Sbir phase ii final report 10 18 06
Download
1 / 37

sbir phase ii final report - PowerPoint PPT Presentation


  • 356 Views
  • Updated On :

Paul Gustavson (Principle Investigator) Ben Sisson (BASS Engineer) Tram Chase (BOMworks Engineer) SimVentions, Inc Mike Haddad PEOSTRI – SBIR POC. SBIR Phase II Final Report 10/18/06. Topics. Brief overview of SBIR effort Background Approach Highlights Task Overview Discussion.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'sbir phase ii final report' - paul


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
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

SBIR Phase II Final Report 10/18/06


Topics
Topics

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

OBJECTIVE: To discuss accomplishments of Phase II effort


Sbir background
SBIR Background

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

  • 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


Our approach
Our Approach

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

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.

  • 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*

*capability still under development


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”

Exerciser

Highlights

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

Efforts reflected @ http://www.simventions.com/sbir_agg/


Highlights baf spec
Highlights – BAF Spec

- Agg Solutions

- Deagg Solutions

-Transfer Control

- Load Support

BAF

Server

Simulation

Client

Entities

Simulation

Client

Aggregated

Entities

Simulation

Client


Highlights warsim fom decomposition

Explore using

Highlights - WARSIM FOM Decomposition

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

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

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


Highlights bw bass exerciser

Battalion

Platoon A

Platoon B

Aggregate / Deaggregate

Soldier X

Soldier Y

Exerciser

Reflection

Highlights – BW-BASS Exerciser

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

Deaggregate

Aggregate

Soldier 1

Soldier 2

Aggregate






Phase ii baf task overview
Phase II BAF Task Overview

  • Identify and Establish DoD and Commercial Partners

  • Maintain Community Involvement

  • Schedule and Conduct IPRs


Discussion current status
Discussion - Current Status

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

  • 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)

  • 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


Discussion way ahead
Discussion – Way Ahead

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion

  • 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

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



Phase iii funding
Phase III Funding

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • Task Overview

  • Discussion


Paul Gustavson

[email protected]

540 372-7727 (work)

540 429-2550 (cell)

Mike Haddad

[email protected]

(407) 384-3853 (work)

Further Discussion / Questions?

www.simventions.com/sbir_agg



Phase ii plus up baf automation of the rcip navigator barn
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

Use of BAF Calls

AAXE

Built on


Phase ii plus up conceptual model cmod generator

Analyze

Leverage

CMOD Generator

Phase II Plus Up – Conceptual Model (CMod) Generator

Analyze underlying

design within

a simulation

BOM conceptual model

view as a standard

template for the

production of

formal conceptual models

Leverage existing

informal conceptual

model information

DoDAF

OV-1

Extension to


Our approach to baf supported aggregations

Containment of related instance information (BOM container)

Summation of models(BOM assembly)

Producer - 1st Level

Consumer - 2nd Level

Our Approach to BAFSupported Aggregations

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

Aggregation Types

Model Aggregation

Entity Instance Aggregation

Aggregation Levels


Our approach how we used 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

Our ApproachHow we used BOMs with BAF?

  • Data exchange interface elements

  • Model Aggregations

  • Entity Instance Aggregations


Our approach to baf agg deagg triggers criteria
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


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.


Bom illustration 1

states

pattern actions

Pattern of Interplay

State Machines

BOM Illustration #1

Weapons Effect

Derived from RPR FOM

Federation Activities

Federate Capability


Bom illustration 2

Detection

Jamming

Pattern of Interplay

State Machine

BOM Illustration #2

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


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)

What is a BOM really? An Inside Look

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


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

Hierarchical View of the RPR BOMs…

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


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

How Are BOMs To Be Used…Functionally?

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


How comments are captured tracked
How Comments are Captured/Tracked

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

Available at http://70.167.241.198/CommentTracker

*Site Administered by SimVentions, Inc. Access is limited


Demo 1
Demo #1

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

  • 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

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


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

FOMs -> BOMs (Breaking up a FOM)

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

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

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)

FOM

BOM


Behind the scenes what s happening w bomworks exerciser

Soldier1

Instance1

Instance2

Soldier2

interfaceA

interfaceA

soldierInterface

soldierInterface

Container

interfaceB

behaviorA

behaviorA

soldierbehavior

soldierbehavior

Platoon

Container

interfaceB

interfaceB

behaviorA

platoonbehavior

Behind The ScenesWhat’s Happening w/ BOMworks Exerciser?

1

- 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

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


Behind the scenes what s happening w bass
Behind The ScenesWhat’s Happening w/ BASS?

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

  • 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


Behind the scenes what s else is happening
Behind The ScenesWhat’s Else is Happening?

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

  • 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


Google earth extensions
Google Earth Extensions

  • Brief overview of SBIR effort

    • Background

    • Approach

    • Highlights

  • WARSIM FOM decomposition to BOMs

    • Benefits

    • BOMworks Tool

    • Analysis

  • Exercise of WARSIM BOM instances

    • BOMworks Exerciser

    • BASS (BAF Implementation)

    • Google Earth

  • Discussion

  • 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


ad