Transcript SBIR Phase II Discussion / Demo 6/29/06

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
1
Topics
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.Task Overview
3.Discussion
OBJECTIVE: To discuss accomplishments of Phase II effort
2
SBIR Background
•
1.Brief overview of
SBIR effort
– Develop a common framework
for aggregating and
deaggregating entities in
simulations exercises
• Background
• Approach
• Highlights
2.Task Overview
3.Discussion
GOAL:
•
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
3
Our Approach
•
1.Brief overview of
SBIR effort
–
• Background
• Approach
• Highlights
–
2.Task Overview
3.Discussion
–
–
•
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.
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)
•
•
BOM – A piece part of a
Use BOMs to represent aggregated
and non-aggregated models and
entities
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*
4
*capability still under development
Highlights
•
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
BAF Specification
– Version 1.0b (2/1/06)
– Version 1.1 (8/31/06)
•
BASS Implementation
– Now Live @
http://67.78.242.14
2.Task Overview
3.Discussion
– Represents SimVentions
implementation of BAF
1.1 core functionality
– Last Demonstrated on
8/23/06 to WarSim
•
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”
Demo-ware
– SV-AGG
– BOMworks w/ BASS
Exerciser Plug-In
•
Programs of Interest
– Objective OneSAF
– WARSIM
– MDA Community
•
Exerciser
BOMs Developed / Used
– RPR BOMs
– WARSIM BOMs
•
Use of TR-Tracker Tool to
track comments
Efforts reflected @ http://www.simventions.com/sbir_agg/
5
Highlights – BAF Spec
Model Aggregation Methods
Model_RequestAggSolution()
Model_RequestDeaggSolution()
Model_FetchAggSolution()
Model_FetchDeaggSolution()
Model_AppendToAgg()
Model_ExtractFromAgg()
Model_QueryAgg()
Entity Aggregation Methods
Entity_RequestAggSolution()
Entity_RequestDeaggSolution()
Entity_FetchAggSolution()
Entity_FetchDeaggSolution()
Entity_AppendToAgg()
Entity_ExtractFromAgg()
Entity_QueryAgg()
Session Support
Session_ClientJoin()
Session_ClientLeave()
Session_GetClients()
Session_FetchHistory()
Session_RegisterEntity()
Session_GetEntities()
Session_TransferControlRequest()
Session_TransferControlCheck()
Session_TransferControlStatus()
Session_LoadSupport_SetDoctrine()
Session_LoadSupport_GetDoctrine()
Session_LoadSupport_AggCheck()
Session_LoadSupport_DeaggCheck()
BAF
Server
Simulation
Client
Entities
Simulation
Client
Aggregated
Entities
- Agg Solutions
- Deagg Solutions
-Transfer Control
- Load Support
Simulation
Client
Statistics / Scoreboard
Session_SetScoreboard()
Session_GetScoreboard()
Library Support Service
Lib_AddItem()
Lib_DeleteItem()
Lib_UpdateItemMetadata()
Lib_SearchItemsByMetadata()
Lib_LookupIDByName()
Lib_LookupNameByID()
Data Logging Support
Logger_SetSettings()
Logger_GetSettings()
Logger_SetMode()
Logger_GetMode(()
Logger_FetchDataLog()
Transformation Support
Transform_BOM()
Transform_HLAFOM()
Transform_Metadata()
Error Handling
Error_GetString()
Error_GetCode()
6
Highlights - WARSIM FOM Decomposition
1.Brief overview of
SBIR effort
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...”*
• Background
• Approach
• Highlights
2.Task Overview
3.Discussion
Resolution
•
Isolate WARSIM FOM elements into
manageable modules (aka BOMs)
–
Provides logical Simulation Exchange Elements
–
Easy to reconstitute (composable)
–
Useful for supporting agg / deagg
Explore using
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,
and standards necessary to enable effective integration, interoperability, and
reuse.” - (DoD M&S Master Plan)
7
*Conclusions made by paper/presentation titled 02S-SIW-002
Highlights – BW-BASS Exerciser
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
Exerciser
Battalion
Platoon A
Soldier 1 Soldier 2
Platoon B
Soldier X Soldier Y
Aggregate
Aggregate Deaggregate
2.Task Overview
3.Discussion
8
Highlights – SIW Papers
9
Highlights – SIW Papers
10
Highlights – SIW Papers
11
Highlights – SIW Papers
12
Phase II BAF Task Overview
Tasks
Objectives
Current / Recent Activities
Develop and Apply BOMs
and BOM Assemblies for
representing
aggregations
• Define BOM representations for supporting
interfaces of entities and aggregated entities.
• Update to BAF spec 1.1
• Use of available implementations (BCIs) that
can support interface
• Application of metadata to support BOM
dimensions
• 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
• Leverage other products and technologies
(including MRMs)
Develop a common
framework for
aggregating and
deaggregating entities in
simulations exercises
• Identify requirements of architecture
• BAF Design Spec contains 4 major service groupings
• Define specification detailing the set of available
functions
• 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…)
• Demonstrated repository developed in MySQL
• Take advantage of BOM metadata
• Connected BOMworks and AAXE to BASS web-service
repository
• Implement services described by specification
• UDDI being explored for connection with other repositories
• 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
• SV-AGG, developed in house, to serve as aggregate level
sim
• BASS inline with federation to provide services
• Regression tested upgrades related to BAF spec 1.1
• BOMWorks BASS Exerciser (w/ Google Earth)
•Identify and Establish DoD and Commercial Partners
•Maintain Community Involvement
•Schedule and Conduct IPRs
13
Discussion - Current Status
•
1.Brief overview of
SBIR effort
Phase II Base
Expended (Sept’06)
– BASS (i.e., BAF
Implementation)
Updated to Final
Specification During
BARN Execution
• Background
• Approach
• Highlights
2.Task Overview
3.Discussion
– Deliverables
• Final Report
•
–
•
–
–
•
•
• BOMWorks
Executable
•
(w/ BASS Exerciser)
•
Phase II Plus-ups
– BARN 65% Complete
(Dec’06)
– CMOD 10% Complete
(May’07)
•
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
–
•
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
–
–
–
• BASS
Complete BASS implementation to BAF
version 1
April 06 (Spring SIW – Huntsville)
–
• BAF Spec
•
Mar 06
BARN Completed
May 07
-
CMOD Completed
14
Discussion – Way Ahead
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.Task Overview
3.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
15
ARMY Funding
Navy Funding
START
11/1/2003
Phase I Agg / Deagg Framework
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.Task Overview
3.Discussion
$100,000
FINISH
7/1/2004
CLINs
1&3
START
11/1/2004
Phase II Agg / Deagg Framework
$750,000
FINISH
9/30/2006
CLIN
5
START
12/1/2005
CLIN
6
BAF Automation of
RCIP Navigator (BARN)
RCIP Navigator
Navy COR: Larry Gunter
$250,000
FINISH
12/31/2006
CLIN
5 Sub 02
START
4/1/2006
Conceptual Model Generator (CMod)
$250,000
START
4/1/2005
FINISH
5/1/2007
$648,000
FINISH
3/31/2006
CLIN 8
START
Sub 1&2
9/1/2005
RCIP Navigator Engineering
Navy COR: Larry Gunter
FINISH
$127,000
3/31/2006
CLIN 8
START
Sub 3
1/4/2006
RCIP Adaptation
Navy COR: Larry Gunter
$200K /
FINISH
$250,000
9/30/2006
CLIN 8
Sub 5
START
4/1/2006
RCIP Integrator
Navy COR: Larry Gunter
$137,500
FINISH
9/30/2006
16
Phase III Funding
1.Brief overview of
SBIR effort
ARMY Funding
• Background
• Approach
• Highlights
2.Task Overview
3.Discussion
Navy Funding
CLIN
1
Possible Army Phase III ?
START
7/31/2006
Navy Phase III Proposal Submitted RCIP
Integrator Followon
$200K
FINISH
1/31/2007
START
?
Navy Phase III Proposal Submitted
Automated Test/Retest
FINISH
?
$300K
START
1/1/2007
Navy Phase III Proposal Submitted
Integrator Followon II
$300K
RCIP
FINISH
10/31/2007
17
Further Discussion / Questions?
Paul Gustavson
[email protected]
540 372-7727 (work)
540 429-2550 (cell)
Mike Haddad
[email protected]
(407) 384-3853 (work)
www.simventions.com/sbir_agg
18
Backup Slides
19
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.
Use of BAF Calls
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
AAXE
Built on
20
Phase II Plus Up –
Conceptual Model (CMod) Generator
Model Identification (Metadata)
Conceptual Model
Pattern Description
State Machine
Analyze underlying
design within
a simulation
DoDAF
OV-1
Leverage existing
informal conceptual
model information
BOM conceptual model
view as a standard
template for the
production of
formal conceptual models
Entity Type
Event Type
Model Mapping
Entity Type Mapping
Event Type Mapping
Object Model Definition
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)
Analyze
Leverage
CMOD Generator
Extension to
21
Our Approach to BAF
Supported Aggregations
Aggregation Types
1.Brief overview of
SBIR effort
Model Aggregation
Entity Instance Aggregation
• Background
• Approach
• Highlights
2.WARSIM FOM
decomposition to
BOMs
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
∑
Summation of
models
(BOM assembly)
Containment of related
instance information
(BOM container)
• BOMworks Exerciser
•
BASS (BAF
Implementation)
•
Google Earth
4.Discussion
Aggregation Levels
Producer - 1st Level
Consumer - 2nd Level
22
Our Approach
How we used BOMs with BAF?
• Data exchange
interface elements
• Model Aggregations
Mapped to
BOMs
Simulation
gun
vehicle
soldier
Humvee
platform
BOM
FOM
BOMs
radar
Composite
pattern
Subsystem
models
• Entity Instance Aggregations
<<tank BOM>>
M1A - 1403
<<tank BOM>>
M1A - 1404
<<helo BOM>>
Apache - 132
entities
<<container BOM>>
agg -123
Flyweight
pattern
23
Our Approach to BAF
Agg/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
24
Key Concept - Using Base Object Models (BOMs) as Building Blocks
Definition
BOM Palette
Standards
- x
Simulation
Components
Choose what fits
conceptual model?
User
Requirements
A
B
X
Simulation
Systems
• foms
• federates
Illustration
Sim /
System A
BOM 1
Federate B
- or BOM 3
BOM
Assembly
Representation
Composition
Composite
Interface
Pattern of Interplay
State Machines
Events
Federation
(FOM)
Federate A
BOM 2
BOM n
Federate
(SOM)
C
Federate X
- or Model
#1
Model
#2
Model
#3
Model
#n
BOMs are designed for enabling composability, providing extensibility, facilitating interoperability,
improving manageability, and encouraging understandibility.
Aggregation
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.
Concept
25
BOM Illustration #1
Weapons Effect
states
pattern actions
Derived
from RPR
FOM
Pattern of Interplay
State Machines
Federation Activities
Federate Capability
26
BOM Illustration #2
Detect /Jamming Activity
Jammer
(Originator)
Here there are
actually two
patterns of
interplay
“Detection”
and “Jamming”
Radar
Threat /
Target
Emits
Reflects
Detection
Detect
We could
conceivably use
the “Detection”
pattern for
other purposes
besides just
“Jamming” such
as “Vectoring
Interceptors”
Threat Detected in Range (Msg)
Jam
Jamming
State Machine
Federation Activities
Pattern of Interplay
Federate Capability
27
What is a BOM really?
An Inside Look
An XML based
standard
for capturing
Model Identification (Metadata)
Conceptual Model
Pattern Of Interplay
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,
State Machine
Entity Type
Event Type
Model Mapping
Entity Type Mapping
Event Type Mapping
Object Model Definition
HLA Object Classes
HLA Object Classes
Conceptual entities
and the events which
occur among those
entities as well as the
states attainable by
those entities.
Mapping of
conceptual entities
and events to
object model
object and
interaction classes.
Not all
these
pieces
are
required
for a
BOM…
HLA Object Class Attributes
HLA Interaction Classes
HLA Interaction Classes
and the mapping
that exists
between that
conceptual
model and object
model.
Essential metadata
needed so that
the BOM can
be described,
discovered
and properly reused
HLA Interaction Class Parameters
HLA Data Types
Notes
Lexicon (definitions)
BOM template allows BOMs to be captured in a reusable way
Object classes,
interaction classes,
and datatypes used
to perform the
behavior described
in the conceptual
model.
Notes and definitions
supporting any of the
above mentioned
elements
28
Hierarchical View of the RPR BOMs…
RPR FOM 2.0
Behavior Rep
Weapons Effect
Logistics
Behavior Representations
•
Weapon Effects
•
Logistics Support
•
Collision
•
Entity State Update
•
Simulation Management
•
Distributed Emission Regeneration
•
Radio Communications
•
Entity Management
•
Minefield
•
Synthetic Environment
Repair
Resupply
Collision
Includes Model Mapping
Entity St Update
SIMAN
Entity Creation
Entity Reconst’n
RadioComms
Entity Removal
Minefield
Action Request
Synthetic Env
Post Comment
Post Event
Object Rep
Object Representations
•
Entity Object Types
•
Env Object Types
•
Minefield Object Types
•
Signal Object Types
EntityObjects
EnvObjects
MinefieldObjects
SignalObjects
29
How Are BOMs To Be Used…Functionally?
These can be
swapped out as
modules
New “Assemblies”
can be “composed”
and (for HLA) turned
into FOMs
Profile
BOM a
BOM 1
BOM b
Federate A
BOM c
Federate B
BOM 2
BOM d
BOM
Assembly
Composition
BOM n
BOM z
Conceptual Model Object Model
View
View
BOMs
Behavior
(Conceptual)
BOMs
Object
(Class
Structure)
BOMs
Composite
Interface
Representation
Federate X
Federation
for
Joint Training
30
How Comments are Captured/Tracked
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.WARSIM FOM
decomposition to
BOMs
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
• BOMworks Exerciser
•
BASS (BAF
Implementation)
•
Google Earth
4.Discussion
Available at http://70.167.241.198/CommentTracker
*Site Administered by SimVentions, Inc. Access is limited
31
Demo #1
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.WARSIM FOM
decomposition to
BOMs
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
• BOMworks Exerciser
•
BASS (BAF
Implementation)
•
Google Earth
4.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
32
FOMs -> BOMs (Breaking up a FOM)
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.WARSIM FOM
decomposition to
BOMs
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
Model Identification (Metadata)
Model Identification (Metadata)
HLA Object Classes
Conceptual Model
HLA Object Classes
Pattern Of Interplay
HLA Object Class Attributes
State Machine
Entity Type
HLA Interaction Classes
HLA Interaction Class Parameters
BASS (BAF
Implementation)
•
Google Earth
4.Discussion
Model Mapping
Entity Type Mapping
HLA Dimensions
HLA Time
Event Type Mapping
Object Model Definition
HLA Object Classes
HLA Tags
• BOMworks Exerciser
•
Event Type
HLA Interaction Classes
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
Lexicon (definitions)
Notes
Lexicon (definitions)
FOM
BOM
33
Behind The Scenes
What’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
Instance1
Soldier1
interfaceA
soldierInterface
behaviorA
Instance2
3
soldierInterface
soldierbehavior
behaviorA
Container
Aggregation “solution” from BASS
provides BOM with new container
class (interface)
Application of the aggregate
“solution” is up to the Simulation!!!
soldierbehavior
interfaceA
- Allows “attachment” of behavior
2
Soldier2
interfaceB
Container
Platoon
interfaceB
interfaceB
behaviorA
platoonbehavior
May require
mapping
34
Behind The Scenes
What’s Happening w/ BASS?
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
•
•
– Participates as a passive player /
monitors Simulation
– Web Service request is made by
BOMworks Exerciser
2.WARSIM FOM
decomposition to
BOMs
• BASS evaluates relative exercise
data
• BASS builds a “solution” and
returns the ID
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
– BOMworks Exerciser fetches
solution from BASS
– Client applies Aggregation solution
(see previous slide)
• BOMworks Exerciser
•
BASS (BAF
Implementation)
•
Google Earth
4.Discussion
BASS creates the aggregate
solution for BOMworks Exerciser
How?
•
What Solutions does BASS
provide?
– BOM (Container Class)
– JavaScript
35
Behind The Scenes
What’s Else is Happening?
•
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.WARSIM FOM
decomposition to
BOMs
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
• BOMworks Exerciser
•
BASS (BAF
Implementation)
•
Google Earth
4.Discussion
BASS also provides JavaScript (dynamic
code) solution for populating container
since container class is “new” to the sim
var reference = new
Object();
reference.id_u = null;
•
JavaScript could also be used to perform
the mapping mentioned earlier for
behaviors
var common = new Object();
common.security_mark_0 =
null;
common.faction_id = 31;
•
Sim can choose to keep instances “alive”
while using container class / object
–
...
to preserve sim validity 100%
SpiderMonkey
•
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
C/C++ JavaScript
plug-in
Rhino
Java – JavaScript
plug-in
36
Google Earth Extensions
1.Brief overview of
SBIR effort
• Background
• Approach
• Highlights
2.WARSIM FOM
decomposition to
BOMs
• Benefits
• BOMworks Tool
• Analysis
3.Exercise of
WARSIM BOM
instances
• BOMworks Exerciser
•
BASS (BAF
Implementation)
•
Google Earth
4.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
37