1. JTLS IUC 2016 ALLIED COMMAND TRANSFORMATION JOINT WARFARE CENTRE
Mr Ivan Vianello
Chief Team A
CAX Support Branch
Simulation Modelling & C4 Division

2. JWC Mission
JWC plans, conducts and executes operational training; conducts and supports collective training of joint and combined staffs of the NATO Command Structure (NCS) and NATO Force Structure (NFS) for Major Joint Operations (MJOs) and Small Joint Operations (SJOs)
EXERCISE PRODUCTION DIVISION (XP) is responsible for the planning, management and provision of Computer  Assisted Exercises (CAX) and Content (MSEL) environments related to the JWC Programme of Work (POW).  
CAX SUPPORT BRANCH is responsible for  providing appropriate modeling and simulation support to deliver CAX capabilities for training events. 
he NATO Force Structure encompasses national and multinational forces and their associated operational headquarters, placed under the Alliance’s disposal on a permanent or temporary basis under specified readiness criteria.
The NATO Command Structure has a strategic scope, primarily intended to command and control the Alliance’s joint operations (i.e. operations in which more than one service are involved).
The NATO Force Structure is tactical in scope and provides additional command and control capabilities at the single service level. It is at present in the process of radical changes:

3. JWC Customers - Distrib Ex:
Joint Warfare
Centre
Joint Force
Command Brunssum
MCC Northwood
ACC Ramstein
SHAPE
Joint Force
Command Naples
LCC Izmir

4. JWC Exercises Juncture Series Jaguar Series Jewel/Jet Series CWIX
Full Joint Operations . Certification Of NRF for the following Year. All HQ’s involved . MJO , MJO+
Jaguar Series
NRDC type of exercises. Usually 2 HQ trained “almost” simultaneously.
(Nato Rapid Deployable Corps)
Jewel/Jet Series
Single Components Exercise with Joint Flavor.
Components are playing the JTF HQ role as well
CWIX
Interoperability Exercises.

5. JWC JTLS Infrastructure
JTLS has been virtualized since 2009
In 2011 All JWC IT environment has been Virtualized including C2* .
Users has only Thin Clients on their desks
5 JTLS games instances are running simultaneously and managed by Tech control (1 R&A and 1 NATO) during an Exercise :
Main
Test
Shadow
Ato
Run Ahead /Wargame
* Start looking into the impact of big Scenarios

6. 2017 Activities 2 TRJR17 2 TA’s ,2 DB’s 2 Exercises in 4 weeks time
SFJN17
Biggest NATO EX last 10 years– MJO+ (Full Command structure)
SKOLKAN 3 scenario (Norway – challenges with Terrain)
National forces / Ex Embedded
4 Cores deployed in North Europe
143 Bn’s in JTLS
“NATO” CAX team
CWIX 2017
Interoperability Exercise

7. 2016 Last Activities TRJE16 (scenario : NATO Territory)
Article V – Very Heavy Air Targeting operations
Challenges in how TA was planning Joint targeting Strikes : COMAO’s + TLAMS + ATACAMS + SOF .
TBMD (JTLS has stimulated NATO TBMD C2 System via L16)
Space Operations *

8. TRJE16 JTLS Highlights Space
Hybrid Warfare (i.e Civilian different Ethn , military Armed)
Logistics
Contractors (additional side)
SPOD – APOD / MSR attacks limiting capacity
Cyber
Jammers
AAR
Wargame Specific VIGNETTEs
Model Performance on Big Scenarios in VM
Impact of Huge numbers of civilian ships & A/C missions
Possible Future Approach?

9. Space Environment impact
UNCLASSIFIED
UNCLASSIFIED
HF COMM
Signal Fades / RFI
(Tactical Comms)
RADARS
RFI / Tracking Errors
(Missile Warning)
SATCOM
(data/voice, GBS)
GPS Dual-Frequency
Loss of Signal Lock
(Navigation, PGMs)
GPS Single-Frequency
Tactical Location Errors
(Troops, mines, maps)
INTEL Collection
Geolocation Errors / RFI
(INTEL, Targeting)
Primary Threats
Solar Flares
Solar Radio Bursts
Ionospheric Scintillation

10. What We played in Space Solar Effects
RADAR effects (Tracks Shadows on the COP)
Modify 1 A/C type : no detection from specific side
X Number a/c (11 ) flying
Hide button: we make them appear and disapper
COMM
Changed the COMM PROT  less power required for Jamming effect.
Change the C3 to increase the average delay in Comms : min 1 hr max 1.5

11. What We played con’t Jamming Cyber
40 daily Satcom , Spoofer , GPS jammers active per day
Satcomm = Affect Comm to alliance
GPS accuracy of gps guided ammunition affected (multiple set PH data)
Spoofer = we were forcing perception of units
Cyber
possibility to inject fake tracks in C2 or manipulate C2 feed will help

12. TRJE16 JTLS highlights
Wargaming
Planning: - To have a more realistic picture in terms of figures / casualties / timing to help Scenario writing the “Road to Crisis ” and why NATO is I involved in a specific operation.
Execution: - To Support Opfor in forecasting their Plan , check / evaluate the effects on the TA of the planned Incidents or the dynamic scripting .
Evaluating training opportunities
- To Support Excon in adjudicating specific Kinetic Event (i.e TLAMS strikes , Comao’s outcome)

13. Ad hoc Vignette / Wargaming
TLAM Wargaming
A full MJO scenario was not flexible/fast enough to run multiple iteration of the game.
We were asked to create and wargame specific Vignettes (limited entities involved). Possibility to have tailored light - checkpoints?
Super Viewer for Wargaming and EXCON Sit Awarness?
Idea : Separating Civilian game from “Combat” game? (fusion At COP level)

14. TRJE16 Con’t
AAR : We start looking into AAR capabilities in order to have easy access to data
Support the Wargaming vignette approach
RC Support and Reporting (How many ..? Who?)
Web access Reports fully customized by users?
Detailed customization of AAR collection (reducing amount of data)
Reporting
Elint – general Intel Report
TRIPP package (stand alone) + Ad hoc Reports
Human Migration (due to NATO Territory Scenario)

15. JWC and 5.0 Testing last Ex DB in 5.0 Next NATO Test Dec 16
i.e Civilian shipping on sea lanes and Flight on corridor
Next NATO Test Dec 16
Nato Acceptance Test - Feb 17
First Exercise :
Data Repository
Logfas generation for upcoming Ex.
CSP concept will help - we are repr all NATO Countries now.

16. We’re Spoiled Nov 14 – Nov 16 (4.1.X)
Orders Sent during last 5 Ex
3% (Magic)
Model Execution Hours
2400
Model Crashes 6
Settings (Geo) (including TRJE16) 3

17. JWC M&S view CAX Environment needs to be as simplier as possible
Scenarios Size and Exercises themselves are by default already complicated enough (Gravity Points)
CAX Environment has to be easily reproducible after the exercise with minimum manpower and resources
CAX Environment has to be easily manageable , deployable with minimum manpower and resources (1 , 2 people to handle it)
Minimize the possibility of frequent Architecture updates . Such an approach prevents a new model version to be used for an event.
Ex Requirements Change drastically and dynamically several time per year .With such a evolving environment is very easy to end up with useless , counter productive solutions.

18. Simulation Modelling & C4 Division
QUESTIONS
Mr Ivan Vianello
Chief Team A
CAX Support Branch
Simulation Modelling & C4 Division