1 / 16

ALLIED COMMAND TRANSFORMATION JOINT WARFARE CENTRE

ALLIED COMMAND TRANSFORMATION JOINT WARFARE CENTRE. JTLS IUC 2015. Mr Ivan Vianello Chief Team A CAX Support Branch Simulation Modelling & C4 Division. JWC Optimization. CAX Branch , Scenario Production , Geo Production , Mel Mil is now under the same umbrella.

fredn
Télécharger la présentation

ALLIED COMMAND TRANSFORMATION JOINT WARFARE CENTRE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

  2. JWC Optimization CAX Branch , Scenario Production , Geo Production , Mel Mil is now under the same umbrella. Mel Mil (MSEL) is now becoming “professional” positions in JWC MEL MIL – CAX – SCENARIO are domains naturally linked . Now this is reflected in the Organization

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

  4. JWC IT 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

  5. Last 11 Months Activities TRJR14 2 Different TA’s Playing simultaneously in 2 Different adjacent JOA’s. Challenges : Airspace control , cross interaction / detection of units. TRJE14 (scenario : NATO Territory) Article V – Very Heavy Air/Targeting operations - Challenges in how TA was planning the use of Stand-off weapons and COMAO’s (Orbiting , On alert , Splitting A/C etc) TBMD (JTLS has stimulated NATO TBMD C2 System via L16) Space Operations – JSAT OPFOR Building a proper ATO . 2 Sides Air C2 stimulated , 2 RAP

  6. J-Sat Feed

  7. Last 11 Months Cont’ TRLE14 – LAND CENTRIC in NATO Territory (TRJE14 follow on) 3 CORES 15 BDE’S TROOPS moving on FROZEN Sea ~ 900 sorties with No Air component and no ATO JTLS running in Stavanger & Whips Deployed to GR & TU (15 Operators remotely) 4 Land C2 systems involved (2 national 2 Nato’s) Every C2 was stimulated with their own perceived picture using Ownsitrep from JTLS. C2 couldn t handle the full Orbat in a single message . We had Specific Whips generating Land Messages for Sub Branches of the Orbat. Every Cores was responsible to generate the RGP and send it to Joint level in order to generate the Common Join t Land Pic

  8. C2 Stimulation TRLN14 LANDCOM & MNC(NE) RC LC2IS LC2IS GRAF MCCIS NCOP Adat-p3 Ownsitrep Ensitrep JWC TACCIS SDEP Oth Gold messages Adat-p3 Ownsitrep Ensitrep Manual Update Simulation RC CAX RC CAX NRDC-G NRDC-T

  9. Last 11 Months Cont TRJL15 MARITIME CENTRIC Intense and realistic RMP requirements AIS (automatic Identif System) feed required To Role play AIS feed , JTLS was sending every hour a FULL update of the white Shipping Orbat to a separate MCC C2 BOX TRJR15 2 Training Audiences (2 different DB’s) with 1 Week in between Hybrid Warfare (combining kinetic operations with subversive efforts)

  10. Last 11 Months Cont Wargaming Planning: To support scenario in providing a consistent picture to TA after Ph2b (Crisis response 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 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 any dynamic scripting . Evaluating training opportunities

  11. Some Figures Nov 14 – May 15

  12. Upcoming Exercise • TRJE15 High Visibility NATO Exercise (CAX+LIVEX) . • CANADA will join from remote (combined NATO + National EX) • Canada will have some national forces contributing to the operation. • Canada will Run an Exercise (National ) inside the NATO Exercsie • 24 / 7 Exercise • SIM deployed Overseas and in Spain • SPACE OPS (Needs to Play Space effects i.e Solar Flares) • New RC’s : • Civilian Air (Italian National Air Traff Control is joining). • Intel Cell to support TA with Reporting coming from JTLS • Heavy JISR’s Gameplay with Live UAV Sim Streaming . • Civilian White Shipping Feed required (AIS / Live feed etc etc)

  13. Ex upcoming requirements: • J – ISR capabilities - Intel Cell , Reporting • Hybrid Warfare (Already started with new scenario's) military strategy that blends conventional warfare , irregular warfare and cyber warfare , by combining kinetic operations with subversive efforts. • Cyber effects • Already played using JTLS • Human Behavior Modeling • JWC is looking into some solutions to possibly integrate in JTLS gameplay.

  14. JWC ROADMAP to 5.0 • Initially planned for next Oct Ex • LOGFAS Interface (Initialization) + several ECP’s would have improved RC operations • DB developed already • Maps 70% built • Will be used for an internal NATO Project in Nov • We are considering to use it in Jan For JET 16 • Definitely for JR16 (March/Apr)

  15. JWC 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 that required Architecture updates , can prevent a new model version to be used for an event. Ex Requirements Change drastically and dynamically several time per year .Without a manageble system , with such a evolving environment is very easy to end up with useless , counter productive solutions.

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

More Related