UNCLASSIFIED

UNCLASSIFIED

Joint Staff J7 Future

Larry Hose, General Dynamics Joint Staff J7 Environment Development JTLS Project Coordinator

Don Weter, CIV Joint Staff J7 Environment Development JTLS & JCATS Program Manager M&S Technical Manager

UNCLASSIFIED

UNCLASSIFIED

Agenda

Future M&S

Mandate For Change

Objective

Joint Force Training Environment Today

JLVC 2020 Roadmap

DoD Strategy for JTLS

JTLS Future

JS J7 JTLS POC Contact Info

UNCLASSIFIED

UNCLASSIFIED

Cloud Infrastructure

• Supports JF2020 • Web Accessible • Discoverable • Event Planning &

Design Tools

• Easy to Use • Scalable • Tailored Resolution

& Fidelity • Affordable

3

UNCLASSIFIED

UNCLASSIFIED

Mandate for Change

Why • Operating & Sustainment Costs • Keep pace with the operating

environment • Joint Force 2020 • 2012 National Defense

Authorization Act (NDAA) • DoD CIO Enterprise IT Strategy • DoD CIO Cloud Computing

Strategy • Joint Information Environment

(JIE) Affordable, Adaptive, Agile Joint Training Environment

How • Enterprise Architecture vice

integration of monolithic models • Converged infrastructure and

shared resources (cloud computing)

• Web 2.0 technologies • Lean processes • Requirements-based, risk-

managed • Enterprise collaboration/ Unity

of Effort

4

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

• Revolutionize Joint Force Development Environment to: • Keep pace with operational environment – JF2020 imperatives • React to strategic changes – rapid development, pivot to Pacific • Drive warfighter innovation • Comply with DoD IT enterprise architecture requirements – Joint Information Environment

UNCLASSIFIED

UNCLASSIFIED

Joint Training Enterprise Architecture

• Unsustainability of Current M&S• JLVC is a federation of Service/Joint developed models• Manpower (cost) intensive• Constant burden on integration (version control)

• DoD Mandates to Move M&S to DoD IT Enterprise• Training enclave joining “mainstream” without being consumed • Joint M&S available wherever NIPR/SIPR are

• Discoverability & Accessibility• Driving jointness deeper = joint training context for Service use• Current Joint M&S is too monolithic (i.E., Not composable)• Trainers have to compete for sim center support

• Technology Changes• Cloud enables linkages now to facilitate trainer involvement• Hardware speed = more efficient modular software approaches• More can be automated to reduce manpower costs

• Efficiency• Trainers are unique with specific training objectives – thus need unique training environments• Providing a bigger, more complex training environment than trainers require is wasteful

• Fidelity• Trainers have varying need for fidelity (usually related to C4ISR devices M&S input to)• One-size-fits-all approach (either JLVC or JTLS) is too restrictive

Joint Force Development Environment:

• Relevant to Warfighter Needs• Less Expensive to Sustain• Within DoD IT Enterprise Framework• Discoverable & Accessible to Home-Station• Optimized for Cloud & Faster/Better Hardware• A Composable Training Environment (Right-Sized)

Objective

Focused on: • Putting joint M&S in broader

context of Joint Training Enterprise Architecture (JTEA).

• Saving $$$ to reduce O&S costs and re-invest in Warfighter relevance.

• Mitigating risk to “what is” – Do No Harm.

• Building collaboration as we establish an enterprise approach.

• Delivering JLVC 6.0 (Last of Class) by end of FY13.

5

“Move quickly toward Joint information and simulation networks that support secure and agile command and control.” Chairman’s Strategic Direction to the Joint Force, February 2012

UNCLASSIFIED

UNCLASSIFIED

• Inefficient Processes ─ Labor for each simulation –

database, C4I output, scenario, interoperability

─ High integration costs to maintain federation

─ Design, build, and take down connections / network for each event

• Redundant capability across simulations

• Unsustainable ─ Foundation of Sims dates to

the 1980’s

• Lack of Compliance ─ Tech protocols not supported

with Joint Information Environment

─ Does not support Cloud Computing

Joint Force Training Environment - Today

Complex training federations and models rely heavily on manual processes

6

UNCLASSIFIED

UNCLASSIFIED

October 2016

March 2015

Roadmap

March 2014

October 2018

7

UNCLASSIFIED

UNCLASSIFIED 8

Key elements of the strategy concerning the Joint Theater Level Simulation (JTLS) and the Joint Conflict and Tactical Simulation (JCATS) are as follows:

• Development of JTLS and JCATS capabilities will continue through September

2015.

• Both JTLS and JCATS will be sustained (cyber security, defect correction, federation integration, and minor functionality) through Sep 2019.

• Investments to migrate both JTLS and JCATS to a joint training cloud, within the

Joint Information Environment (JIE) architecture, will begin in October 2014 and continue through September 2015.

BRYAN G. WATSON Major General, U.S. Army Vice Director J7, Joint Staff Joint Force Development

MEMORANDUM FOR THE CHIEF OF STAFF, NORTH ATLANTIC TREATY ORGANIZATION HEADQUARTERS, SUPREME ALLIED COMMANDER TRANSFORMATION

JTLS Strategy

Dated 03 July 2013

UNCLASSIFIED

UNCLASSIFIED 9

JTLS R&D efforts in support of JS J7 for JTLS between now through next April (2015) will be to complete the terrain enhancements (JTLS 5.0)

• This is a must for sustainment of JTLS in future years

• Provides a new terrain modeling concept

JTLS version 5.0 will be the last programed JS J7 major release of JTLS

Sustainment of JTLS is planned through 2019

JTLS Future

UNCLASSIFIED

UNCLASSIFIED

QUESTIONS?

Don Weter, CIV Joint Staff J7 Program Manager Comm: (757) 203-7649 DSN: 668-7649 donald.e.weter.civ@mail.mil Mr. Larry Hose, General Dynamics Joint Staff J7 JTLS Project Coordinator Comm: (757) 203-7714 DSN: 668-7714 larry.w.hose.ctr@mail.mil