OneSAF and the Research, Development and Acquisition (RDA) Domain

1
OneSAF and the Research, Development and
Acquisition (RDA) Domain
John Thomas US Army Materiel Systems Analysis
Activity Aberdeen Proving Ground, Maryland 20
August 2007
2
Outline
Purpose
provide an update to the OneSAF user community on
the RDA domains current and future involvement
with OneSAF.

• MS Domain User Community
• RDA Domain Community
• Requirements
• Things We Like
• Path Ahead
• Summary

3
Army M S User Community(Force Modeling)
Application Domains
Army M S Domains
Advanced Concepts and Requirements (Doctrine,
Analysis Concepts Forces)
ACR
Constructive
Research, Development Acquisition (Equipping
the Force)
RDA
OneSAF
Virtual
Live
Training, Exercises Military Operations (Prepari
ng the Warfighter)
TEMO
4
Modeling Simulation - RDA Domain
Research, Development Acquisition
ATEC
PEO/PMs

• System Development
• Technology Development/
• Evaluation
• Test Evaluation
• Logistics
• Costing

AMSAA
AMRDEC
ARDEC
NSRDEC
ARL
STTC
ECBC
CERDEC
TARDEC
SOSI
Supporting Current Fielded and Future Forces
AMSAA is the RDA Domain Technical Representative
5
OneSAF Fulfillment of RDA Requirements (Some
Examples)
Aviation Missile Research, Development Eng
Center
Aviation Missile Research, Development Eng
Center

• Aircraft Survivability Equipment
• Ground Radar Modeling
• Signature Modeling
• Air Vehicle Dynamics
• Realistic Aviation Behaviors
• Entity Level Behavior Modeling
• Digital Messaging Capabilities
• Hi Fidelity Capability vs Table
• lookup
• Night Operations

• Scalability
• Analytical Requirements
• Improved Smart Munition Modeling
• Improved Sensor Modeling
• Operator Control of Entity Responses
• Realistic Representation of OPFOR
• Entity Editor

OneSAF Components
Tank-Automotive Research, Development Eng Center

• Correctly represent US Army
• Ground Vehicles
• Correctly Represent Hunter/Killer
• Methodology
• Provide Entity Editor
• Represent Countermeasure
• Devices on Ground Vehicles
• Add Sensors to OneSAF Vehicles
• Support Digital Command Control
• Message- Send Receive
• High Resolution Terrain Databases
• Modifiable Behaviors
• Represent Ground Vehicle Mobility
• correctly

• Entity Composer
• Composition Tool
• Behavior Composer
• Scenario Generation
• Model Development Verification Test Tool
• .
• .
• .

The OneSAF ..
composition tools are helping provide solutions
to satisfy RDA requirements.
6
OneSAF Requirements Who
TRADOC Project Office OneSAF Combat Developer
User Rep
Program Management Office Materiel Developer
Director, TPO OneSAF LTC Gene Reedy
PM OneSAF LTC Rob Rasch
Deputy, TPO OneSAF Sean Hallinan
Deputy PM John Logsdon
Domain Representatives ACR, RDA, TEMO
Lead Engineer-Interoperability
ACR Domain

• Tom Loncarich
• LTC Silvernail

Co Development Activities POC
RDA Domain

• RDECOM MS IPT
• ATEC Direct Engage

• Rob Miele
• John Thomas

TEMO Domain

• Mike Black
• LTC Greenwalt

7
OneSAF Providing Improved Representation
Behaviors
Combat Physical Models

• Operator Control HITL /No HITL
• Automated Up to Battalion
• SASO Not Automated
• Suppression Direct/Indirect-Fire
• Beh Degradation Stress, Fatigue
• Beh Rep Authoritative Sources

• Physical Model Rep Validated- AMSAA Other
• Standardization Entity Level
• Fidelity Varying Capability
• Focus Reuse
• Traceability PKAD
• Synchronization w/COMBAT XXI
• Data Structures Commensurate w/APEDS

Synthetic Natural Environment
New SAF Capability
Enhanced SAF Capability
HITL - Human In The Loop SASO -
Stability And Support Operations AMSAA
Performance Estimate Data System Physical
Model knowledge Acquisition Document
8
Concept of Model/Entity Resolution

• Three levels in OneSAF standard, autonomous,
  and focused
• Interactions between entities of different
  levels of resolution are tested
• Allows users to compose the level of resolution
  where it is needed

Focused (High)
Autonomous (Medium)
Standard (Low)
9
Things We Like

• Development Process
• Early Continuous Domain Participation
• Single Development Facility
• Reuse (Emphasis on Standardization)
• Continuous User Assessments
• Incremental Development (program Blocks)
• Composer Tools
• Behavior
• Unit
• Entity
• Combat Physical Models
• Varying Fidelity Capability
• Standard Algorithms
• Physical Model Verification Testing

Reuse, Standardization, Combat Physical Models,
Frequent Testing, Composability
10
Combat Physical Model
Battle Environment
Target Acquisition
Attrition
Communication
Movement
Sustainment
11
Combat Physical Models
Knowledge Acquisition Knowledge Engineering
12
Requirements Flow - KA/KE Process
Domain Representation
Combat Physical Model Development

• Requirements
• Staffing

• 52 physical models developed and integrated
• Combat physical models documented

Requirements
Artifacts
Implementation
Testing
OneSAF MDVT Other Tools
13
Combat Physical Models
Verification Testing
14
Requirements Flow Testing
Requirements
Artifacts
Implementation
Testing
Documentation
OneSAF MDVT Other Tools
15
FY07 P3I RIB Items Immediate Focus on Analysis
FY07 16 Requirements Integration Board Items

• Vehicle / personnel mobility based on terrain
  (RDA/ACR)
• Data Collection and Analysis (ACR/RDA)
• COE OPFOR Behaviors (TRISA)
• Direct vision optics (RDA/ACR)
• Target Acquisition (RDA/ACR)
• Increase in entity count 15K and 32K (ACR/TEMO)
• Repeatability and Replicability (ACR/RDA)
• Tools / processes to quickly generate, to brigade
  sized, classified scenarios (ACR/RDA)
• Up to Brigade Size Behavior representation (ALL)
• Model FCS platforms (ACR/RDA
• Atmospheric effects on communications (ACR/RDA)
• RSTA sensors (SIGINT and IMINT) (ACR/RDA)
• Causality Tools (Cause/affect tracking) (ACR/RDA)
• Varying light levels (man made illuminations)
  (ACR/RDA)
• 15. AAR replay of entire selected event (TEMO)
• 16. SE Core integration (TEMO/TPIO Virtual)

Key Analysis Components
16
Planned FY07 Testing

• OneSAF 1.5 Release Testing
• Repeatability and Replicability
• Classified Data Loading
• Data Collection
• Combat Physical Models (Regression Testing)
• OneSAF 2.0 Evaluation (Dec 07)
• Test Thread Writing Workshops
• Test Thread Development
• Mid Planning and Final Planning Conference
  Participation
• Test Participation--FLVN, NSC, Dec 07
• Potential additional RDA Domain Participants
  (ATEC, MATREX)

Modeling Architecture for Technology and
Research EXperimentation
17
FY07 OneSAF Shake Out Effort(When How)

• Phase I 3rd Qtr FY07
• Define Scenario/Vignette
• Prepare submit weapon system performance data
  request
• Phase II 4th Qtr FY07
• Load data Configure OneSAF (entity physical
  model configuration and behavior data tables)
• Phase III 1st Qtr FY08
• Execute run matrix
• Analyze data collection
• Document phase I II
• Brief results to PM OneSAF
• Phase IV 2nd Qtr FY08
• Identify appropriate use case attempt to
  conduct an analysis for record

Currently working with ACR Domain on FY07 RIB
items 2,7,8 and 13
18
Summary

• Domain co development efforts currently ongoing
  using OneSAF v1.x
• Expect more co development efforts with the
  release of OneSAF v1.5
• Some domain use with OneSAF versions 1.5 2.0
  (transitioning, shakeouts,etc.)
• Expect significant increase in domain use with
  OneSAF release of v3.0

Due to various levels of MS experience within
the RDA domain expect some organizations to
transition to OneSAF earlier than others