Future Combat Systems Use of M

1
Future Combat Systems Use of MS for TE

• DoD Modeling and Simulation Conference
• Acquisition and TE MS Practitioners Panel
• Phil Zimmerman, FCS MS, and Analysis
• 13 Mar 08

2
MS Overview

• Force Effectiveness Analysis
• Requirement maturity
• Risk mitigation
• Technology maturity

• Accredited full FCS BCT wrap around environment
• Provides data and artifacts in support of
  analysis, test and VV
• Supports experimentation and Spin Outs
• Supports developmental and operational test and
  evaluation

• Embedded Live, Virtual, Constructive Training
• Course of Action Analysis
• Operational Mission Planning and Rehearsal on
  Platforms
• Logistics and Support Planning

MS is a key program enabler for all aspects of
the program
3
Modeling and Simulation Implementation Strategy
Integration Phases
S2F Library
MS Products
Operational SW HW
Live Virtual Entities
Live Virtual Entities
Live Virtual Entities
Live Virtual Entities
Using FSE 4
Using FSE 3
Using SVF
Using FSE 2
Using FSE 1
Integration andTest Configurations from S2F
Toolset repository
4
S2F Enterprise Management and Product Development

• S2F MS Requirements Flowed down
• Established a Community of Practice
• MS technology Insertion in Critical Technology
  Demos
• MS Product alignment to CPM to support IP events

• Successful Integration Events 1-6 for SO1
  Testing
• MS Requirements alignment for DT/OT, FDTE,
  Training
• S2F and FSE component utilization in SO1 TFT,
  LUT

• Constructive MS Use in Ongoing FEA, Trade
  Studies per
• SoSAP and INAP
• Ongoing VV of MS for Test/Demonstration (Exp
  1.1, IMT1)
• IMT1 Assessment Data Supports Incremental VbA

MS Technology and Development Insertion

• Development/Execution of OnePlan for ETE Network
  Modeling
• Utilization of FSE/CES for IMT1, CT Demos.
  Baseline Analysis, BCSS Trade Studies, Exp
  2.2 Lab AOs (DFM, RBD)
• CES 4.0 - FCS Network Transport Sim Configured
  w/ FCS Baseline Design (i.e. WLS, Spectrum
  allocation, etc.)
• CES 5 and CES 6 with NMS and dynamic Config. of
  FCS Network.

Cross Command Collaborative Effort (3CE)
SoS Analysis
Network Analysis and Modeling

• Successful use of MS to complete Exp. 1.1
• Completed MS EI (Delta RAP)
• S2F Requirements Baselined in DOORS
• Successful Conduct of SoSIL CDR for IMT1 Road
  to WSMR
• Successful conduct of MS VVA in IMT2
• Execution of Distributed MS and Testing
  Capabilities for IP2

TE - Integrated Lab and Range
Engineering Design and Manufacturing
Embedded MS

• OTP use Engineering MS to Support System in
  Design SIL
• MS VV as part of OTP PDR and CDR (UGS)

The S2F Enterprise is the collaborative union of
the FCS MS Communities of Practice with the
overall shared goal of providing MS for both SBA
and objective operations

• MS Requirements Definition and Phased
  Allocation for Embedded MS (TCC PIDS, CPM)

5
MS Horizontal Integration and Product Flow for
Test and Evaluation
Requirements Flowdown
S2F Enterprise Management and Product Development
MS Library
From requirements to integration using MS
6
Integrated SoS MS and Test Overview
Comp Programs
Distributed Systems
Simulation to Live Field Test
IP3
MS-C
IP2
IP1
Log /Training FQT (BCS)
Component Qualification
KPP 4 Transportability
KPP 1 Net Ready
Component Qualification (FQT's)
KPP 3 Net Lethality
ESOH/ MANPRINT
KPP 5 Sustainment Reliability
OTP
Structures

• INTERFACES
• IRDs, ICDs, IRSs
• CP SW HW
• CP MS
• CP SME Support

Kpp 7 Survivability
Environments
E3 /Constraints
Core software/ comp/Radio
KPP 6 Traning
Kpp 2 Network BC
Maneuver

• MS and test activities contribute requisite
  verification and validation data to successfully
  demo FCS BCT capability

7
Summary

• FCS MS is driven by both the program
  requirements (the what), and the users needs
  (the how much)
• Test is one of the users
• Shares the same program requirements sets
• Needs are both as a program tester, and a govt
  tester
• MS solutions may or may not be different
• Test shares the available MS assets, and
  contributes to the asset set (S2F)