New approach in interoperability between JTLS simulation system and SZAFRAN C2 system

1. XVIII International JTLS Users Conference Monterey, 15-16 November 2016 New approach in interoperability between JTLS simulation system and SZAFRAN C2 system Przemysław NIERODA, PIT-RADWAR S.A.

2. Company profile

3. PIT-RADWAR S.A. • Company background and identification: • 1934: StateTelecommunicationInstitute / TelecommunicationResearchInstitute (PIT) • 1954: WZR RAWAR/CNPEP RADWAR, • mergedinto PIT-RADWAR S.A. • part of PGZ (PolishArmamentGroup) • Fullyowned by Polish MOD Location of facilities: – headquarter, R&D and production: Warszawa, ul. Poligonowa 30; – Gdańsk, – Wrocław – Kobyłka/k. Warszawy.

4. MAIN AREAS OF ACTIVITIES • Radar Systems • Electronic Recognition Systems • Command & Control Systems • Anti-Aircraft Missile and Gun Systems

5. C4ISR SYSTEMS AIR DEFENCE SYSTEMS- surveillance systems RecognisedAir Picture Active Radars Air Defence Systems „DUNAJ”Radars data fusion RAP production and distribution Weapons Control Network Enabled Capability IP-WAN ”OP-NET” Data Exchange Time synchronisation Electronic Warfare System „WOLCZENICA” Passive Radar data Fusion PassiveRadars

6. COMMAND AND CONTROL SYSTEMS GROUND BASED AIR DEFENCE SYSTEMS AIR FORCE SYSTEMS SDP-20 (SAMOC)Surface-to-Air Mission Operations Centre DL-15Interceptor Control Post ŁOWCZA/REGAArmy SAM System TU-20L Approach and Landing System

7. X X X X X XX X X X X XX X X X X XX X X X X II II x II II C4ISR SYSTEMS – LAND FORCES FENIKS – C2ISArmy Information System OPERATION COMMAND Corps SZAFRAN C2IS Land Command and Control Information System X Common Operational Picture Plans Orders Regulations Common Operational Picture Reports Division FENIKS – BMSBattle Management System RadioIP-WAN Brigade Battalion

8. SZAFRAN C2IS FENIKS C2IS

9. X X X X X XX X X X XX X X X X X XX X X X X II x II II II SZAFRAN/FENIKS Support of information flow and command processes X XX Plans X X X X Planned tactical situation Current Operational Picture Orders Reports | | EXER/POKAZ 2013// MSGID/ENSITREP/22KZZZZ/-/AUG// AMPN/BASELINE 12.2// GEODATUM/W84// DTG/182003ZAUG2013// ORGIDDFT/22KZZZZ/CORPS/-/CBT/INF/-/MECH/-/A/-// CMDRELI/SUBORDINATE// EORGID/44DZ097/DIVC/-/CBTC/INFC/-/MECHC/1KA097C/AC/-// ESUBORD/OPCONC// Information flow in the operational structure

10. SZAFRAN/FENIKS Functionalities • Targeting, artillery and rocket forces • Collecting targeting information; • Nominating targets; • Creation of fire plans; • Ordering firing tasks for subordinated units; • Planning fire resources; • Command and control • Common Operational Picture adjusted to commanding level using APP6A; • Support of raster and vector maps; • Hierarchical and layered access to operational data; • ORBAT management; • Creation and distribution of staff documents (orders and reports) using STANAG 2014 and ADatP-3; • Working with many plans and variants at one time; • Support many task organizations; • Layered planning; • Force ratio calculations; • Force deployment planning support; • Terrain analysis (Line of sight, flooding areas, 3D terrain, visibility calculations); • Feeding subordinates with aggregated operational information; • Logistics • Keeping track of resources; • Aggregation of resources by subordinates; • Collecting parameters of resources; • RIC based creation of new resources types; • Creation of reports and calculations; • Forces movement planning: • March column organization; • Planning march points; • Calculation of march route; • Calculation of march time; • Air defence • Live air picture; • Preparing of tactical background for subordinates; • Tasking subordinates; • Calculation of sensor and air defence asset ranges; • Automated processing of Air Defence documents(ATO, ACO, COVREP, SHORADLOCSTAT, etc.) • Interoperability • See next slide • Reconnaissance and intelligence • Collecting information on enemy forces; • Collecting information on enemy activities; • Keeping layered and structured information on enemy; • Maintaining information on enemy facilities and tactical objects; • Automated reports processing;

11. SZAFRAN/FENIKS Interoperability Air defence • COVREP • SENSCOVREP • AOAD LOCSTAT • SSTO • WEZREQ • ACMREQ • KILLREP • SHORADLOCSTAT • ATO • ACO Artillery • ATI.TIR • ATI.ATR • FM.CFF • SPRT.ACA • SPRT.GEOM • NNFP.FP • NNFP.COMFP • NNFP.RESFU • Automatic tools • Support of baseline 11, 12.2 • Generating from database • Importing to database • Visualization in GIS • Grammatical validation LOGFAS v. 6.X JEMM v. 3. X ICC ADatP-3 IP1 v 1.3, 1.4 • Land • OWNSITREP • ENSITREP • LOGSITLAND TOPFAS v. 5.X IP2 v 1.3, 1.4 JOCWATCH v. 2.X NATO FAS SIP3 v 1.3 MCCIS NFFI HUB SZAFRANFENIKS • Data import and export • RIC based types • Exercise events and actions • Operational overlays • Near RT on Map Track Presentation • Possible Track  Unit Association • Possible Location Transfer to DB JTLS NVG Link 11 Subset TD-LINK • NVG 1.4, 1.5, 2.0 • Full coverage of APP6A ŁOWCZA GEO MIP • RAP in nearrealtime • Updatingoperationaldatabase (with resourcesstates) • Exchange of airspacecoordinationfactors Baseline 2 Baseline 3 • Map formats: • Raster: CADRG, GEOTIFF, MRSID, ECW, JPEG2000, DTED • Vector: VPF, SHP, MIF, MAP, KML, XYZ • Online: WMF, WFS • Gazetteer Baseline 3.1 • Data conversionbetween MIP baselines • Full APP6-Acoverage • Transparent to the user

12. The operational concept of JTLS and SZAFRAN integration The need • Multinational Corps North East (MNCNE) planning annual CPX asked for CAX support (JTLS), • Compact Eagle 2015 – involving more than 14 subordinated units (TA), more than 400 staff officers, • Additionally a goal was to exercise as much as possible Standard Operating Procedures involving SZAFRAN C2IS • After some studies on potential use of JTLS it was decided to have JTLS as much as possible in the background and perform the exercise as much as possible in SZAFRAN

13. The operational concept of JTLS and SZAFRAN integration The vision • Supporting the staff exercises on the tactical and operational level using C2IS: • The JTLS may be used as a controlling cell of the exercise, • The JTLS is a key system of CAX exercise providing a more realistic scenario to the exercise participants (LOCON, HICON, TA). • Analysis of planned in the C2iS variants of operation using simulation system: • The JTLS provides a simulation of the battlefield with many factors not available to C2IS, • The JTLS provides a time coordination. • Playing the role of the “intelligent” enemy in tactical exercises facilitating command and control system; • The JTLS plays „red cell” of the staff exercises, • The JTLS provides more automatic and reactive enemy.

14. The operational concept of JTLS and SZAFRAN integration Optimal information exchange • Bi-directional exchange of information • Exchange of own, enemy, neutral and unrecognized forces • ORBAT • Location of units and HQs • Logistics • Units’ status • Information on battle theatre • Information on tactical objects • Tasks and event

15. The operational concept of JTLS and SZAFRAN integration Definition of the task • Task of interconnecting simulation system to C2IS class system is too complex to solve in one step • Two phases has been defined • Phase 1 – establish a straightforward, rich and automated connection from JTLS to SZAFRAN to sent a simulated common operational picture to SZAFRAN, • Phase 2 – establish an automated connection from SZAFRAN to JTLS to initialize JTLS with data and to send orders and updates to JTLS. • MNCNE agreed to participate in this project as a test and verification body

16. Starting level of interoperability between SZAFRAN and JTLS • ADatP-3 messages(OWNSITREP, ENSITREP) sent from JTLS to SZAFRAN • KML layers (Keyhole Markup Language) sent from JTLS to SZAFRAN • ADatP-3 message exchange requires overriding the standard to accept JTLS messages (JTLS messages are not conformant with STANAG 5500) • The exchange is one way (from JTLS to SZAFRAN)

17. The operational concept of JTLS and SZAFRAN integration The solution JTLS • Automated connector which could bi-directionally exchange information between JTLS database and SZAFRAN’s IEG • Mechanism is completely persistent to the JTLS • Mechanism is completely persistent to SZAFRAN or other C2IS class system • The core of the solution is proper mapping the simulation data SDR Information Exchange Gateway (IEG) Buffer database JTLS Connector MIP 2 MIP 3.1 MIP 3.0 SZAFRAN C2IS or other C2 class system Operational database

18. The current level of interoperability between SZAFRAN and JTLS – the use case HICON/EXCON (SZAFRAN) Real-time feed • Currently achieved JTLS interoperability: • One-directional exchange of information – when manually prepared scenario in JTLS is ready • Exchange of own, enemy, neutral and unrecognized forces • ORBAT and TASKORG • Location of units and HQs • Logistics • Units’ status C2IS data exchange TA(SZAFRAN) JTLS TA(SZAFRAN) Scenario day STARTEX feed TA(SZAFRAN) C2IS data exchange JTLS players LOCON JTLS Only LOCON JTLS Only LOCON JTLS Only

19. THANK YOU FOR YOUR ATTENTION Przemysław NIERODA, PIT-RADWAR S.A.