One SemiAutomated Forces OneSAF within Research, Development and Acquisition RDA M

1
One Semi-Automated Forces (OneSAF) within
Research, Development and Acquisition (RDA) MS
Domain
John G. Thomas 31 March 2009 US Army Materiel
Systems Analysis Activity Aberdeen Proving
Ground, Maryland 21005-5071
Approved for public release distribution is
unlimited.
2
Agenda
The RDA MS Domain
has been actively engaged with program support,
testing, co-development activities and use of
OneSAF. This presentation provides an update to
the OneSAF user community on some of the RDAs
involvement with OneSAF.

• MS Domain User Community
• RDA Domain Community
• Requirements Update
• Transition and Current OneSAF Efforts
• OneSAF v3.0 User Assessment Participation
• Way Ahead

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

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

AMSAA
AMRDEC
ARDEC
NSRDEC
ARL
STTC
ECBC
TARDEC
CERDEC
AMSAA Army Materiel Systems Analysis
Activity AMRDEC Aviation and Missile Research
Development Eng Center ARDEC Armament, Research
Development Eng Center ARL Army Research
Lab ATEC Army Test Evaluation Command CERDEC
Communications-Electronics Research,
Development Eng Center
ECBC Edgewood Chemical Biological Center NSRDEC
Natick Soldier Research, Development Eng
Center PEO Program Executive Office PM
Program Manager STTC Simulation Training
Technology Center TARDEC Tank Automatic
Research, Development Eng Center
5
Requirements Generation Process
RDA Users
ACR Users
TEMO Users
NLT Mid-March
RDA
TEMO
ACR
Domains provide their consolidated list of
requirements to TPO OneSAF
NLT Mid of April
OneSAF Draft PRL
TPO OneSAF merges three lists into a single list
called the Draft OneSAF Priority Requirements
List (PRL), with a best guess prioritization, and
send to domains
RDA
ACR
TEMO
TPO TRADOC Project Office
6
OneSAF v4.0 Requirements
OneSAF Requirements

• TPO OneSAF collected all domain requirements
• Requirements Integration Board (RIB) generated
  an initial prioritized list
• 13-14 April 08 RIB Meeting conducted (Orlando,
  FL)
• FCS, MATREX and 3CE personnel Participated
• Based on ROM, RPB (CoC) approved final list for
  v4.0 20 June 2008
• Process worked better than previous years
  (improved domain coordination/collaboration)

3CE Cross Command Collaborative Effort CoC
Council of Colonels FCS Future Combat
Systems P3I PrePlanned Product
improvement MATREX Modeling Architecture for
Technology, Research, Experimentation PM
Product Manager ROM Rough Order of Magnitude
7
Status of RDA Requirements(OneSAF V5.0)
Phase I

• 22 Jan 2009 TPO OneSAF Memo, OneSAF
  Requirements Prioritization Process, FY, v5.0
• 27 Jan 2009 RDA Domain lead received memo and
  passed to RDA users
• 04 Mar 2009 RDA users provide input to RDA
  domain lead
• 06 Mar 2009 All domains (RDA, ACR, TEMO)
  submit list back to TPO OneSAF
• 13 Mar 2009 TPO OneSAF provides integrated
  list back to all domains for prioritization

Phase II

• 01 Apr 2009 RDA users domain lead finalize
  RDA top 10-12 list
• 02 Apr 2009 Domain leads provide Top 10-12
  Requirements to TPO OneSAF
• 06-10 Apr 09 Requirements Integration Board
  (RIB) develops integrated priority requirements
  list
• 13 Apr 2009 RIB provides prioritized
  integrated domain list to PM OneSAF

Invited domain guest to participate w/domain
lead
Phase III

• 08 May 2009 PM OneSAF provides TPO OneSAF ROM
  cost for v5.0 Top 30 list
• 08 May 2009 TPO OneSAF provides domains ROMd
  cost for v5.0 Top 30 list
• 10 Jun 2009 OneSAF Requirements Prioritization
  Board (RPB) finalizes a prioritized resourced
  v5.0 list
• 30 Jun 2009 TPO OneSAF obtains final approval
  of the v5.0 requirements list from OneSAF
  proponent
• (Commander, CAC) and provides to PM
  OneSAF for execution

CAC Combine Arms Center PM Project
Manager
8
RDA Domain Use of OneSAF
OneSAF.
has demonstrated significant progress after each
major release starting with version 1.0. The RDA
user community is in the process of
transitioning to OneSAF. Some components of RDA
have been using an older version of OneSAF.

• OneSAF is critical to RDA
• Integral component for MATREX
• Test Evaluation (Model-Test-Model, provide
  synthetic test environment and stimuli)
• Future Combat System program is currently using
  OneSAF
• Some RDECOM organizations are already using
  OneSAF (analysis experimentation)
• Transitioning from legacy simulations (OTB,
  Janus-A) to OneSAF
• Near-Term
• OneSAF very close to meeting today's needs
• Much focus has been placed on loading of weapon
  system performance data and data collection
  analysis capabilities
• Currently being used to support some applications
• Way Ahead
• RDA will require new requirements to keep up with
  changing technologies
• Strong emphasis on co-development

9
MATREXOneSAF Transition Roadmap
10
AMSAAs Role (within Analytical Community)
CAA (Warfighting in a Joint/Combined Context)
Theater
TRAC (Tactical Operations - Organization Design
Force Effectiveness thru Corps)
Force Level
Small Units
AMSAA Data/ Meth.
AMSAA (Logistics Systems Network Performance
Analysis)
AMSAA (Materiel Sys. Performance Analysis)
System Technology
RDECs/Labs (Sub-System/Component Performance
Technology Capabilities)
Sub-Systems, Engr Technology
CAA Center for Army Analysis
TRAC TRADOC Analysis Center
RDECs Research, Development and Engineering
Centers
AMSAA Army Materiel Systems Analysis Activity
AMSAA, TRAC CAA Collaborate to Provide Army an
Effective, Responsive, In-House Analysis
Capability for Army Decision Makers
11
Notional Use Case
System Development Using simulation,
investigate system effectiveness of a blue tank
equipped with a new round.
System - The new round is ...
Scenario/Approach - Compare system effectiveness
of a baseline (w/o new round) versus a new
equipped friendly company heavy task force
against an opposing force in a designated
scenario.
12
AMSAA OneSAF Analysis
Focused on assessing OneSAF analytical
capabilities

• FY08 Conducted OneSAF shakeout for a small
  scale modeling effort
• FY08 Conducted a second OneSAF shakeout effort
  for a more complex modeling effort
• FY09-10 Multiple study efforts scheduled

Notional
13
OneSAF v3.0 User Assessment (RDA Participation)

• OneSAF Baseline v3.0 Initial Planning
  Conference (Jun 08)
• OneSAF Baseline v3.0 Mid-Planning Conference (
  Aug 08)
• OneSAF Baseline v3.0 Final Planning Conference
  (Oct 08)
• RDA participated in OneSAF version 3.0 baseline
  release user assessment (Feb 09)
• Some of RDA participated in ACR user assessment
  event conducted at TRAC-WSMR
• Focused on data collection, data loading, and
  new combat physical models
• Operational Test Command, Transformation
  Technology Directorate is planning on co hosting
  a RDA event as part of the OneSAF v4.0 baseline
  release user assessment

Other

• Participated in Army Analytical Community MS
  Data Summit
• Possible Army Training MS Data Summit

TRAC-WSMR TRADOC Analysis Center-White Sands
Missile Range
14
Way Ahead

• Continue with transition planning and execution
  efforts
• Participate in OneSAF user assessment events
• Promote Domain co-development activities
• Encourage Cross Domain Collaboration
• Transition to OneSAF v3.0