The Coordinated Spiral: Concurrent M

1
The Coordinated SpiralConcurrent MS
Development with C4I Systems
Captain Douglas RauschMajor Scott Johnston Air
Force Agency for Modeling and Simulation (AFAMS)
2
Overview

• MS Challenges
• Why Integrate
• Current Spiral Development Process
• Coordinated Spiral Development
• Success Stories

3
MS Challenges
Decision Makers

• Realism
• Hooks to C4I System
• Mission Rehearsal
• Information Operations
• Responsiveness
• Accelerated Data Builds
• Rewind / Replay
• Crisis Support
• Availability
• In Garrison / Deployed
• Affordability
• PC vs High-End
• Flexibility
• Multipurpose Use

Real World Systems
Staffs
Changing Warfighting Strategies / Concepts
4
C4I Environment
U-2
Satellites
Rivet Joint
Joint STARS
DOD Reach back
SHOOTERS
AIRLIFT
BARE BASE
ASOC
AOC
TACP
AFAC
CRC
WINGS
CRE
5
C4I Integration
Real
Real-World Battlespace
Synthetic
CDRs/Staffs
C4I system
Synthetic Battlespace
MS integration with C4I allows combination of
real-world and synthetic battlespaces for

• Mission Rehearsal
• Requirements Support
• Acquisition Support

• Training
• Test Evaluation
• Experimentation

6
Lack of C4I System Stimulators

• Unable to rehearse with all systems
• Unable to stress all systems/processes
• Simulation allows us to find and fix problems
  faster than can happen in the field
• Simulation provides a realistic environment for
  commanders and staffs to rehearse extracting
  information from all available data
• Need to interface with combined and joint
  systems/processes outside Air Operations Center

7
Current Spiral Development
Only Half the Answer
Concept
C4I System Spiral Development
Fielded System
MS System Spiral Development
Supporting MS
C4I system fielded with incomplete MS
support MS always playing catch-up
8
Non-Concurrent Fielding of Simulators and C4I
Systems

• Training is late to the field, should be provided
  concurrently with the new system
• Simulators developed concurrently with C4I
  systems can aid in fielding through test and
  evaluation
• Robust simulators are key for successful
  experimentation

9
Concurrent Spiral Development
C4I System Development
MS System Development
Concept
Analysis
Evaluation Organizational Change Process
Change Technology Change Hold or Kill
Evaluation Technology Change C4I System Change
Prototype
Battlelab
OpEval
EFX
Fielded System w/Supporting MS
C4I built concurrently with supporting MS
10
Cost of Concurrent Development
Is operational benefit gt increased acquisition
cost?
MS has improved air component readiness. The
CONOPS for Theater Missile Defense and Predator
UAV employment were validated and refined during
UFL98. Lieutenant General Hurd, 7th AF/CC
11
AWSIM/TBMCS Interface (ATI)

• Forms link between Air Warfare Simulation (AWSIM)
  and Theater Battle Management Core System (TBMCS)
• Maps TBMCS and AWSIM databases
• Consumes TBMCS Air Tasking Order
• Produces AWSIM flight plans
• Transmits mission updates back to TBMCS
• Generates United States Message Text Format
  messages for mission results

12
ATI Development Lessons Learned

• Early identification of requirements
• Over a year before fielding, more is better
• Access to TBMCS databases, design
• Excellent ATI/TBMCS working relationship
• Formalize future efforts, beyond grass roots
• Interface available for initial spiral events
• ATI and TBMCS allowed to mature jointly
• Aid test evaluation, available for training
  initial cadre

13
Expeditionary Force Experiment (EFX) 98

• MS Stress Tested Systems, Operators, Concepts
• 2,500 USMTF intelligence messages per day
• Over 4,000 mission updates per day to FLEX
• 12,677 TADIL J, TIBS, TRAP messages through C4I
  every 10 minutes

The bottom line here in my opinion is that TBMCS
will achieve significant maturity during the 6-9
months of concentrated EFX-98 work with a lot
less expenditure of time, money and frustration
rather than the 2-3 years that it would normally
take to get to the same state. Major General
Corder, USAF (Retired)
14
(No Transcript)
15
(No Transcript)