Joint Rapid Scenario Generation (JRSG) Update for the DoD M

1
Joint Rapid Scenario Generation(JRSG)Update
for the DoD MS Community
Mr. Bill Robinson USJFCOM Study Supervisor,
JRSG Evaluation of Alternatives
2
Rapidly generating scenario based data for Joint
Warfighter mission preparation and decision
support
3
Scenario Generation for the Warfighter

• Mission rehearsal, training, acquisition, TE,
  analysis, planning, and experimentation scenarios
  must be warfighter centric provide relevant
  scenario data at the right time
• Current capabilities are inefficient, incomplete,
  disjointed and siphon critical resources away
  from the fight failing to provide rapid,
  comprehensive, collaborative production

Must improve our rapid scenario generation
processes - faster, more resilient, cheaper - to
support the warfighter!
4
Problems Consistent Across Domains

• Mission Rehearsal
• Training
• Acquisition
• Test Evaluation (TE)
• Analysis
• Planning
• Experimentation

Encountered same inefficiencies and deficiencies
within each of the application domains - from
source data to execution
5
JRSG EoA Problem Statement

• There is no rapid, distributed initialization
  data set generation capability that supports
  identified warfighter requirements for
• Collaborative mission planning and rehearsal
• Strategic, operational and tactical situational
  analysis
• Collective training at multiple levels
• Operational TE
• Scenario-based acquisition
• in a networked, Joint, combined,
  interagency
• intergovernmental environment
• with mission critical
  timelines.

6
LVC Mission Training Rehearsal

• Multi-billion dollar, annual DoD-wide training
  and mission rehearsal effort - from JNTC to
  flight simulators to C2 developments
• All rely heavily on data from mission relevant
  authoritative source data for geospatial, target
  and order of battle databases for initialization
  of C2 and MS runtime data sets
• Current capability is built on increasing use of
  labor to build and integrate the data across
  system at the execution initialization database
  level

Current scenario generation processeslaborious,
inefficient, duplicative and time-consuming
It takes a WHOLE lot of time, technology and
effort to get the data ready for an MS event.
7
JRSG Problem Statement Examples
Example 1 USJFCOM identified 53 major DoD
Baghdad databases which have been produced.
Stove piped, not interoperable, not compatible,
not harmonized, with little sharing, re-use, or
updates being conducted. Example 2 USJFCOM
Joint Warfighting Center (JWFC) expends over
18,000 man-hours each year to develop individual
event databases. Each Combatant Command,
Service, and Agency devotes additional resources
to similar, independent, and often duplicative
efforts at their MS centers of
excellence. Examples 3 Air National Guard
A-10 simulator database production normally 1
month/100K. JRSG proof of concept test for
Emerald Warrior 07 completed same database in 1
day at trivial cost. New database available for
rapid re-use, sharing, and update.
Cannot afford to do business as usual!
8
JRSG correlates to NECC objectives

• Technologies that enable effective, reliable, and
  scalable service oriented architectures
• Technologies that hide information service
  complexity from the end customer
• Technologies that enable network services to
  function effectively across low performance
  networks
• Technologies that enable network services to
  effectively support rapid resynchronization of
  users reestablishing connection to the GIG after
  disconnected operations
• Technologies that enable JC2 services to meet the
  ultra-high reliability/survivability targets
  (99.9999) specified in the draft JC2 CDD
• Technologies that facilitate the incremental
  security accreditation of services
• Technologies that enable strong identity
  management and access control across loosely
  coupled Service-Oriented Architectures (SOAs)

NECC Net Enabled Command Capability
9
Capability Required

• Significant improvement in speed and efficiency
  in producing mission-relevant data sets requires
• Access to authoritative data in usable formats
• Ability to collaborate on production processes
  from distributed mission locations
• Rapid manipulation, correlation, and generation
  of initialization ready data sets
• Version control and configuration management of
  data sets throughout the discovery, retrieval,
  production, distribution and archiving processes
• Reuse of products (disassemble, modify,
  reassemble, archive)
• Joint community awareness and accessibility of
  JRSG processes and products

10
JRSG EoA Core Tasks
Application Domains
Planning
Acquisition
JRSG Mission Tasks
Define Event
Schedule
Process Data
Analysis
Training
User Management
Obtain Data
Release Product
Experimentation
Mission Rehearsal
Test Evaluation
11
Notional JRSG Capability
Data Sources
Manning DBs
Target DBs
Geo- spatial DBs
Intel DBs
Platform DBs
Force Structure DBs
Readi- ness DBs
Weapon DBs
Other DBs
MS DBs
Weather DBs
Logistics DBs
PMESII DBs
GIG
NCES
JRSG
Define Event
Schedule
Process Data
User Management
Obtain Data
Release Product
Experiment Apps
Adaptive Planning Apps
Mission Analysis Apps
Training Apps
Testing Apps
Acquisition Apps
Scenario Generation Apps
Mission Rehearsal Apps
Command Control Apps
Force Planning Apps
Other Apps
Event Owners End Users
GIG Global Information Grid NCES Net Centric
Enterprise Services
12
JRSG Cross Domain/Cross Function
Experimentation
Order of Battle
JRSG Outputs Stored as Intermediate Final
Product Archives
Event/Mission Ready Products
Scenarios Orders TTPs etc
Intel
Mission Planning Rehearsal Training
GeoInt
JRSG Process Accessed Via GIG
Define Event
Schedule
Process Data
Input
Centered on Event Derived Specified Authoritative
Sources
PMESII
User Management
Obtain Data
Release Product
Tech
Others
Acquisition Test and Evaluation
Planning Analysis
Scenario lineage defined by appropriate authority
13
JSRG Implications

• Warfighter Impact Provide required scenario data
  within critical, mission-driven time lines for
  mission rehearsal, operational analysis and
  adaptive planning through rapid, distributed,
  comprehensive, collaborative production
• Business Impact Provide scenario data at the
  right time and place while reducing operational
  and maintenance costs through increased
  efficiencies savings can be applied to other
  critical issues

14
The Evaluation of Alternatives and the Concept
Decision Review
Feb 07
Oct
Aug
Jan 08
CD Memo
AoA
EoA
ADM
ATL
30 60 days
PPBE
IDM
PAE
JROCM
JCIDS CBA
VCJSC
Study
Report
Implement
Decide
Concept Decision Review Pilot Implementing QDR
acquisition reforms
EoA Evaluation of Alternatives, CD Concept
Decision, AoA Analysis of Alternatives, PPBE
Program Planning Budget Execution, JCIDS
Joint Capabilities Integration and Development
System, CBA Capability Based Assessment, ADM
Acquisition Decision Memorandum, IDM Investment
Decision Memorandum, JROCM Joint Requirements
Oversight Council Memorandum
15
EoA Primary Study Requirements

• Establish a trade space for use by senior
  decision makers for determining if and to what
  extent gaps in capability should be closed and
  for considering divestiture options
• Identify Mission Tasks to satisfy JRSG Mission
  Needs
• Develop materiel and non-materiel alternatives
• Define Measures of Effectiveness (MOEs) and
  Measures of Performance (MOPs) to measure
  operational effectiveness
• Determine the operational effectiveness for each
  alternative, using the MOEs and MOPs
• Determine the life cycle costs for each suitable
  alternative
• Characterize technical risk associated of each
  materiel alternative
• Determine the relative advantages and
  disadvantages of each alternative based on a
  cost-effectiveness alternative comparison
• Identify, as required, alternatives for materiel
  and non-materiel development sponsorship
• Develop a roadmap for further capability
  development and integration

16
Key Engagement Efforts

• Working Integrated Process Teams
• Next WIPT 15-16 May
• Members designated by primary POCs
• COCOM/Service/Agency Surveys, Data Calls and
  Interviews underway
• Distributed IAW POC guidance
• Call for Industry submission through web portal

USJFCOM NewsLink Or FedBizOps Or search for
USJFCOM JRSG
17
JRSG Across Mission Areas and Domains
Rehearsal
Training
Planning
TE
Acquisition
Experimentation
Analysis
18
Contacts

• OSD
• Principle Staff Assistant Rep Fred Hartman, OSD
  PR
• frederick.hartman_at_osd.mil [phone]
• Joint Staff
• EoA Task Force Lead CAPT Rudy Lupton, JS J7,
  Joint Training FCB
• sherman.lupton_at_js.pentagon.mil [phone]
• JFCOM POCs
• Study Supervisor Bill Robinson
• charles.robinson_at_jfcom.mil [phone]
• Study Team Lead Ralph OConnell
• ralph.oconnell_at_jfcom.mil [phone]
• Contractor Team Lead Bill Pfeiffer
• pfeiffer_bill_at_bah.com [phone]

19
Questions