SBIR Phase II IPR - 5/10/06

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 -gt BOMs
• WARSIM
• ACTF
• BASS Integration
• BARN
• RCIP Navigator
• AAXE
• Discussion
• Current Issues
• Looking Ahead
• Future SBIR Opportunities
• Financial Picture

3
Agg/Deagg SBIR Projects / Success to Date
Plus up
4
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. 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

5
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.
6
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 -gtRPR 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
  systems 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.

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

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
9
Highlights - FOMs -gt 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
10
Highlights - FOMs -gt 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 Tags
HLA Object 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
Notes
Lexicon (definitions)
Lexicon (definitions)
11
Highlights - FOMs -gt BOMs (Warsim BOMs)
Warsim FOM
InformationExchange
Information Exchange Trigger
Conceptual Model
Log Control
Control
Application Report
Application Report
Adapter Control
Adapter Control
Adapter Control
Adapter Control Acknowledge
Manager
Manager
Interaction BOMs
Initialization Complete
Initialization
Scenario Parameters
Remote Update Request
RemoteOperation
Remote Delete
Remote Create
FederationOperation
Restart Pending
Federation Save Requested
Model Mapping
Game
Root Int
USMC
Object BOMs
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
Workstation
Nasm
c2Artifacts
C2 Artifacts
Initialization
WimModelObjects
Wim Model
Gold Nugget
Synthetic Natural Environment
EnvObjects
AF
Side
Comms
ScenarioObjects
Scenario
Faction
Platform
OtherObjects
Other
Facility
ItemTypeObjects
Item Type
Civil Env
ItemObjects
Item
Org
12
Highlights - FOMs -gt BOMs (Warsim BOMs)
WarSimBOMsBased on ACTF FOM v3
13
(No Transcript)
14
(No Transcript)
15
Highlights - FOMs -gt BOMs (ACTF BOMs
ACTF BOMsBased on ACTF FOM v3
16
Highlights - BASS Integration
BOMworks helps break down FOMs into BOMs
BOMs
But what do you do with the BOMs?How do you
manage them?
BASS Database Management System
FOM
What if I have other items?
BOMs
FOMs
Data
Use the BASS Library Management System
- Add BOMs to the Library
- Discover BOMs in the Library
- Pull BOMs from the Library
- Used to manage items of different types
17
Highlights - BARN Overview
DMSOComposabilityEffort
RCIPNav
BAFAutomationw/ RCIP Nav(BARN)
Modeling the Impact of Technology Transition on
Ship Capabilities (N-05-053)
BAF
18
Highlights - 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
(No Transcript)
20
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 models
  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)

AAXE
Scripts developed to execute the model in
ProcessModel (i.e. RCIP Nav) and force export the
data to an Excel spreadsheet.
21
Highlights BARN AAXE and the Galileo Framework
AAXE inherits functionality from Galileo, upon
which it is built

• AAXE scripts are written in XML format

Grid and Text Views (Text View shown)
Direct script editing (also supported in Grid
View)
Grid View shows each script command broken into
components
Syntax-highlighted XML Text View
Navigable XML tree diagram
Synchronicity between tree and text views
22
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
23
Discussion - Looking Ahead (2/2)

• Our 06 Schedule
• July Demo
• Sep Demo
• Nov Demo
• OneSAF
• WARSIM
• CAAB
• White Papers
• Phase III ?
• Other Topics

24
Follow on Discussion / Questions?

• Paul Gustavson
• pgustavson_at_simventions.com
• 540 372-7727 (work)
• 540 429-2550 (cell)

www.simventions.com/sbir_agg
25
Financials

• See separate PPT

26
Backup Slides
27
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

28
Background - SOA Use Case Design gt 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
• .

29
Background - BAF Supported Aggregations
Aggregation Types
Model Aggregation
Entity Instance Aggregation
Aggregation Levels
30
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
31
Background - BAF Implementation gt BASS

• Technologies Applied
• Java (Eclipse)
• Web Services
• Independent WSDLsfor each service group
• Not dependent on dedicated server
• Uses and generates BOMs
• Apache

                            
Apache Tomcat
32
Background - How BASS Uses BOMs for Aggregation

• Data exchange interface elements

• Model Aggregations

• Entity Aggregations

33
Background - 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
  
• Macromedias 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.