technology to the warfighter quicker sbir phase ii ipr - 5/10/06 paul gustavson (principle...

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

Upload: susan-conley

Post on 02-Jan-2016

213 views

Category:

Documents


0 download

TRANSCRIPT

Technology to the Warfighter Quicker

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

2Technology to the Warfighter Quicker

TopicsTopics

• 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

3Technology to the Warfighter Quicker

Agg/Deagg SBIR Projects / Success to DateAgg/Deagg SBIR Projects / Success to Date

Plu

s up

START11/1/2003

FINISH$100,000 7/1/2004

CLINs START1&3 11/1/2004

FINISH$750,000 9/30/2006

CLIN START CLIN START5 12/1/2005 6 4/1/2005

FINISH FINISH$250,000 9/30/2006 $648,000 3/31/2006

CLIN START CLIN 8 START? 3/1/2006? Sub 1&2 9/1/2005

FINISH$127,000 3/31/2006CLIN 8 STARTSub 3 1/4/2006

FINISH $200K / FINISH$250,000 3/1/2007? $250,000 12/31/2006

CLIN 8 STARTSub ? 4/1/2006

FINISH$137,500 12/31/2006

RCIP IntegratorNavy COR: Larry Gunter

ARMY Funding

RCIP NavigatorNavy COR: Larry Gunter

Navy Funding

Phase I Agg / Deagg Framework

Conceptual Model Generator (CMod)

RCIP Navigator EngineeringNavy COR: Larry Gunter

RCIP AdaptationNavy COR: Larry Gunter

Phase II Agg / Deagg Framework

BAF Automation ofRCIP Navigator (BARN)

4Technology to the Warfighter Quicker

Phase II BAF Task Overview Phase II BAF Task OverviewTasks 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.

• Use of available implementations (BCIs) that can support interface

• Application of metadata to support BOM dimensions

• Leverage other products and technologies (including MRMs)

• Model / Entity Aggregation updated to BAF spec 1.0• 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

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 (BASS 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

• Demonstrated repository developed in MySQL• UDDI being explored for connection with other

repositories• Connected BOMworks and AAXE to BASS web-

service repository• 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

–Waiting on new release to help with RTI issues• SV-AGG, developed in house, to serve as aggregate

level sim• OneSAF quick start guide (for Navy)• BASS inline with federation to provide services• Regression tested upgrades related to BAF spec 1.0

•Identify and Establish DoD and Commercial Partners•Maintain Community Involvement•Schedule and Conduct IPRs

5Technology to the Warfighter Quicker

Phase II Plus Up - BARN Task Overview Phase II Plus Up - BARN Task Overview

Tasks Objectives Current / Recent Activities

Extend Selected BOMs and BOM Assemblies with Behavior Descriptions

• Explore aspects needed to support rapid process integration of “as-is” and “to-be” capabilities

• Enable early simulation of identified requirements for “quick look” analysis

• Recognized BOMs provide mechanism to support modeling “as-is” / “to-be” capabilities

• Outlining use of BOMs in RCIP process

Mature the Capture of BOM Meta-Data from Users

• Facilitate rapid assembly of systems using RCIP Navigator through the use of BOMs

• Use BOMworks as tool to define RCIP supportive BOMs (planned)

• Maintain and populate BAF repository with RCIP BOMs (planned)

Demonstrate RCIP Navigator Access to the BOM Component Repository

• Automate BOM use through RCIP Navigator

• Examined use of BAF / BASS to support process (i.e. loading, retrieval, aggregation).

Design and Prototype a BOM-based Scenario Generator

• Validate BOMs for a given system with minimal time overhead

• Designed and Developed XML Script language to drive execution and integration of applications

–Used by AAXE (see below)–automates (feeds) RCIP process modeling –Intended for insertion of BOMs (planned)

Design and Prototype a BOM- based Component Simulation Environment

• Coordinate quick-look and assembly of systems using RCIP Navigator

• Evaluate BOMs for applicability to the given process or system being investigated

• Developed the Automation and Extraction Agent (AAXE) prototype

– Java-based (uses our Galileo framework)– Uses prototype XML scripts language (see above)– Process Modeler integration (i.e. RCIP Navigator)– BASS integration

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.

6Technology to the Warfighter Quicker

Phase II Plus Up - CMod Task Overview Phase II Plus Up - CMod Task Overview

Tasks Objectives Current / Recent Activities

• Represent ONESAF Objective System as a Set of BOMs

• Represent WARSIM as a Set of BOMs

• identify process for extracting BOMs from existing simulations,

• develop tools to assist in support the extraction of the information into a representative set of BOMs;

• Generate a set of OOS BOMs. • Generate a set of WARSIM BOMs

• Began preliminary collection of system information and related data needed to formulate and populate OOS / WARSIM BOMs;

• Performed manual breakdown of –RPR FOM ->RPR BOM–ACTF and WARSIM FOM to BOM

• Experience Provides basis for tool

Extend OOS and WARSIM BOMs to Include Conceptual Model Information

• complete the capture of conceptual model information for each BOM.

• Update tools to support the collection and entry of conceptual model information

• mature set of OOS and WARSIM BOMs. • Provide value added to OOS program and

WARSIM program via a set of BOMs

• future

Demonstrate Use of Established BOMs within BASS/BAF

• Demo BOMs generated by Tool) for BAF/BASS Library Support

• future

Demonstrate Application of BOMs for Agile OOS-to-WARSIM Interchanges

• Demo BOMs generated by Tool for BAF/BASS Exercise Support during a OOS-to-WARSIM exercise

• future

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.

7Technology to the Warfighter Quicker

Highlights - BAF and BASSHighlights - BAF and BASS

• 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

8Technology to the Warfighter Quicker

Highlights - BOMworksHighlights - BOMworks

• Create BOMsCreate BOMs

• Edit BOMsEdit BOMs

•Grid/XML/UMLGrid/XML/UML

•Cut/Copy/PasteCut/Copy/Paste

• Validate BOMsValidate BOMs

• Import/Export FOMsImport/Export FOMs

•1.3/15161.3/1516

• Source Code Source Code GenerationGeneration

• Built on Galileo Built on Galileo Framework - Framework - extensible and extensible and customizablecustomizable

.NET Version available

Java Version delivered to DMSO last month!!

www.simventions.com/bomworks

9Technology to the Warfighter Quicker

Highlights - FOMs -> BOMsHighlights - 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

ACTFFOM

WARSIMFOM

ACTFBOMs

WARSIMBOMs

10 Technology to the Warfighter

Quicker

Highlights - FOMs -> BOMs (Breaking up a FOM)Highlights - FOMs -> BOMs (Breaking up a FOM)

Model Identification (Metadata)

Notes

Lexicon (definitions)

HLA Object Classes

HLA Object Class Attributes

HLA Object Classes

HLA Interaction Classes

HLA Interaction Class Parameters

HLA Interaction Classes

HLA Data Types

HLA Dimensions

HLA Time

HLA Tags

HLA Synchronizations

HLA Transportations

HLA Switches

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

Pattern Of Interplay

State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type MappingFOM BOM

11 Technology to the Warfighter

Quicker

Highlights - FOMs -> BOMs (Warsim BOMs)

Warsim FOM

Conceptual Model

Object Model Def ManagerObjects

MTProcessorObjects

GameObjects

WorkstationObjects

Adapter Control

RemoteOperation

Model Mapping

c2Artifacts

WimModelObjects

EnvObjects

ScenarioObjects

ItemObjects

ItemTypeObjects

OtherObjects

Adapter Control

FederationOperation

Log ControlApplication Report

InformationExchange

Manager

Game

Initialization

Adapter Control

Adapter Control Acknowledge

Control

Information Exchange Trigger

Application Report

Scenario Parameters

Restart Pending

Remote Update Request

Remote Delete

Remote Create

Federation Save Requested

Manager

Root Int

FederateFederation

NetworkMaster Track Processor

MTP TOMTP TEORoot Obj

WorkstationC2 ArtifactsWim Model

Synthetic Natural EnvironmentSide

ScenarioFaction

Item TypeOther

Item

USMC

NavalLand

JOISIMAir Tasking

NatsimNasm

InitializationGold Nugget

CommsAF

Platform

Civil EnvFacility

Org

Interaction BOMs

Object BOMs

Initialization Complete

15 Technology to the Warfighter

Quicker

Highlights - FOMs -> BOMs (ACTF BOMs]Highlights - FOMs -> BOMs (ACTF BOMs]

ObjectModel

Definition

Manager

Supply_Cache

Space

Population_Group

Concern

Sea

True_Side

Satisfaction

Air

Ground

Formation_Element

Golden_Nugget_xref

Golden_Nugget

Biographic_Data

Basic_Encyclopedia_Facility

entityInformationObjectModelDefBOM

managerInformationObjectModelDefBOM

true_sideInformationObjectModelDefBOM

supplyInformationObjectModelDefBOM

satisfactionInformationObjectModelDefBOM

informationObjectModelDefBOM

ACTFObject BOMs

ACTFObjectClasses

ObjectModel

Definition

Manager

Supply_Cache

Space

Population_Group

Concern

Sea

True_Side

Satisfaction

Air

Ground

Formation_Element

Golden_Nugget_xref

Golden_Nugget

Biographic_Data

Basic_Encyclopedia_Facility

entityInformationObjectModelDefBOM

managerInformationObjectModelDefBOM

true_sideInformationObjectModelDefBOM

supplyInformationObjectModelDefBOM

satisfactionInformationObjectModelDefBOM

informationObjectModelDefBOM

ACTFObject BOMs

ACTFObjectClasses

ACTF BOMsBased on ACTF FOM v3

managerConceptualModelBOM

Subscribe

Issue

Request

Report

UnSubscribe

Engagement

Loss

Initiating Federate

From

Weapon

ACTFConceptual

Model Patterns

ResignServiceReport

RequestAdjust

supplyConceptualModelBOM

satisfactionConceptualModelBOM

entityConceptualModelBOM

Conceptual Model

ACTFConceptual

Model Entity Types

Target Federate

To

From

To

managerConceptualModelBOM

Subscribe

Issue

Request

Report

UnSubscribe

Engagement

Loss

Initiating Federate

From

Weapon

ACTFConceptual

Model Patterns

ResignServiceReport

RequestAdjust

supplyConceptualModelBOM

satisfactionConceptualModelBOM

entityConceptualModelBOM

Conceptual Model

ACTFConceptual

Model Entity Types

Target Federate

To

From

To

16 Technology to the Warfighter

Quicker

BOMs

BOMWorks

BOMs

Highlights - BASS IntegrationHighlights - BASS Integration

BASS

BASS ClientAAXE

BASSDatabase

ManagementSystem

BOMworks helps break down FOMs into BOMs

FOM

But what do you do with the BOMs?How do you manage them?

Use the BASS Library Management System- Add BOMs to the Library- Discover BOMs in the Library- Pull BOMs from the Library

What if I have other items?

- Used to manage items of different types

FOMsData

17 Technology to the Warfighter

Quicker

Highlights - BARN OverviewHighlights - BARN Overview

RCIPNav

BAFAutomationw/ RCIP Nav

(BARN)

DMSOComposability

Effort

BAF

Modeling the Impact of Technology Transition

on Ship Capabilities (N-05-053)

18 Technology to the Warfighter

Quicker

Highlights - BARN OverviewHighlights - BARN Overview

• 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

19 Technology to the Warfighter

Quicker

20 Technology to the Warfighter

Quicker

BAF Automation of the RCIP Navigator (BARN)BAF Automation of the RCIP Navigator (BARN)

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

AAXE

22 Technology to the Warfighter

Quicker

Discussion - Looking Ahead (1/2)Discussion - Looking Ahead (1/2)P

lus

upSTART

11/1/2003

FINISH$100,000 7/1/2004

CLINs START1&3 11/1/2004

FINISH$750,000 9/30/2006

CLIN START CLIN START5 12/1/2005 6 4/1/2005

FINISH FINISH$250,000 9/30/2006 $648,000 3/31/2006

CLIN START CLIN 8 START? 3/1/2006? Sub 1&2 9/1/2005

FINISH$127,000 3/31/2006CLIN 8 STARTSub 3 1/4/2006

FINISH $200K / FINISH$250,000 3/1/2007? $250,000 12/31/2006

CLIN 8 STARTSub ? 4/1/2006

FINISH$137,500 12/31/2006

RCIP IntegratorNavy COR: Larry Gunter

ARMY Funding

RCIP NavigatorNavy COR: Larry Gunter

Navy Funding

Phase I Agg / Deagg Framework

Conceptual Model Generator (CMod)

RCIP Navigator EngineeringNavy COR: Larry Gunter

RCIP AdaptationNavy COR: Larry Gunter

Phase II Agg / Deagg Framework

BAF Automation ofRCIP Navigator (BARN)

• Our ’06 Schedule•July Demo•Sep Demo•Nov Demo

• OneSAF• WARSIM• CAAB• White Papers• Phase III ?

(see next slide)• Other Topics

23 Technology to the Warfighter

Quicker

Discussion - Looking Ahead (2/2)Discussion - Looking Ahead (2/2)

START7/1/2006

FINISH$200K 12/31/2006

START7/1/2006

FINISH$300K 9/30/2007

START1/1/2007

FINISH$300K 10/31/2007

ARMY Funding Navy Funding

Navy Phase III Proposal Submitted Automated Test/Retest

Navy Phase III Proposal Submitted RCIP Integrator Followon II

Navy Phase III Proposal Submitted RCIP Integrator Followon

Possible Army Phase III ?

• Our ’06 Schedule•July Demo•Sep Demo•Nov Demo

• OneSAF• WARSIM• CAAB• White Papers• Phase III ?• Other Topics

Technology to the Warfighter Quicker

Follow on Discussion / Questions?

Paul [email protected]

540 372-7727 (work)540 429-2550 (cell)

www.simventions.com/sbir_agg

25 Technology to the Warfighter

Quicker

FinancialsFinancials

• See separate PPT

Technology to the Warfighter Quicker

Backup Slides

27 Technology to the Warfighter

Quicker

Background - Minimizing the Obfuscation in the “Mix” - The Need for Aggregation SupportBackground - Minimizing the Obfuscation in the “Mix” - The Need for Aggregation Support

• 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

Aggregation - the coupling of multiple models/entities into a single inclusive group

28 Technology to the Warfighter

Quicker

Background - SOA Use Case Design => BAFBackground - SOA Use Case Design => BAF

Service Oriented Architecture (SOA)

FOCUS

• Common interface(s)

• Loose coupling• Minimize

unnecessary dependencies

• 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

.

29 Technology to the Warfighter

Quicker

Background - BAF Supported AggregationsBackground - BAF Supported Aggregations

Model Aggregation Entity Instance Aggregation

Aggregation Types

1st Level 2ndt Level

Aggregation Levels

30 Technology to the Warfighter

Quicker

Background - BAF Aggregate Triggers/CriteriaBackground - 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

31 Technology to the Warfighter

Quicker

Background - BAF Implementation => BASS Background - BAF Implementation => BASS

• Technologies Applied– Java (Eclipse)– Web Services– Independent WSDLs

for each service group– Not dependent on

dedicated server– Uses and generates BOMs– Apache

              

              

Apache Tomcat

32 Technology to the Warfighter

Quickerentities

<<tank BOM>>M1 - 1403

<<tank BOM>>M1 - 1404

<<helo BOM>>Apache - 132

Background - How BASS Uses BOMs for AggregationBackground - How BASS Uses BOMs for Aggregation

RPRBOMs

RP

R F

OM

OneSAF Objective System

• Data exchange interface elements

• Model Aggregations

Subsystemmodels

BO

Ms

gun

radar

vehicle

soldier

Humveeplatform

Compositepattern

BO

M

<<container bom>>agg -123

Flyweightpattern

• Entity Aggregations

33 Technology to the Warfighter

Quicker

Background - BARN TaskBackground - 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.