XVIII International JTLS Users Conference Monterey 15 -16

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

Company profile

PIT-RADWAR S. A. Company background and identification: • 1934: State Telecommunication Institute / Telecommunication Research Institute (PIT) • 1954: WZR RAWAR/CNPEP RADWAR, • merged into PIT-RADWAR S. A. • part of PGZ (Polish Armament Group) • Fully owned by Polish MOD Location of facilities: – headquarter, R&D and production: Warszawa, ul. Poligonowa 30; – Gdańsk, – Wrocław – Kobyłka/k. Warszawy.

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

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

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

C 4 ISR SYSTEMS – LAND FORCES XX X OPERATION COMMAND X X X FENIKS – C 2 IS Corps X X XX X X Common Operational Picture X X XX Division X X X Common Operational Picture SZAFRAN C 2 IS II Plans Reports II II x Orders Army Information System Brigade Battalion II Regulations FENIKS – BMS Battle Management System Radio IPWAN Land Command Control Information System

SZAFRAN C 2 IS FENIKS C 2 IS

SZAFRAN/FENIKS Support of information flow and command processes XXX Plans XX X XX X X X II x II II || Information flow in the operational structure Current Operational Picture X X X Orders Planned tactical situation X Reports EXER/POKAZ 2013// MSGID/ENSITREP/22 KZZZZ/-/AUG// AMPN/BASELINE 12. 2// GEODATUM/W 84// DTG/182003 ZAUG 2013// ORGIDDFT/22 KZZZZ/CORPS/-/CBT/INF /-/MECH/-/A/-// CMDRELI/SUBORDINATE// EORGID/44 DZ 097/DIVC/-/CBTC/INFC /-/MECHC/1 KA 097 C/AC/-// ESUBORD/OPCONC//

SZAFRAN/FENIKS Functionalities Targeting, artillery and rocket forces Command control • • • Common Operational Picture adjusted to commanding level using APP 6 A; • Support of raster and vector maps; • Hierarchical and layered access to Collecting targeting information; Nominating targets; Creation of fire plans; Ordering firing tasks for subordinated units; Planning fire resources; operational data; • ORBAT management; • Creation and distribution of staff • • Logistics documents (orders and reports) using STANAG 2014 and ADat. P-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, 3 D terrain, visibility calculations); Feeding subordinates with aggregated operational information; • • • 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 • • 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; 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. )

SZAFRAN/FENIKS Interoperability Air defence LOGFAS v. 6. X JEMM v. 3. X Ø COVREP Ø SENSCOVREP Ø AOAD LOCSTAT Ø SSTO Ø WEZREQ Automatic tools Ø Support of baseline 11, 12. 2 Ø Generating from database Ø Importing to database Ø Visualization in GIS Ø Grammatical validation Ø ACMREQ Ø KILLREP Ø SHORADLOCSTAT Ø ATO Ø ACO Artillery Ø ATI. TIR Ø NNFP. FP Ø ATI. ATR Ø NNFP. COMFP Ø NNFP. RESFU Ø FM. CFF Ø SPRT. ACA Ø SPRT. GEOM ICC ADat. P-3 TOPFAS v. 5. X IP 1 v 1. 3, 1. 4 Land IP 2 v 1. 3, 1. 4 Ø OWNSITREP Ø ENSITREP Ø LOGSITLAND JOCWATCH v. 2. X SIP 3 v 1. 3 NATO FAS MCCIS NFFI Ø Data import and export Ø RIC based types Ø Exercise events and actions Ø Operational overlays SZAFRAN FENIKS JTLS Ø Near RT on Map Track Presentation Ø Possible Track Unit Association Ø Possible Location Transfer to DB NVG Link 11 Subset TD-LINK Ø NVG 1. 4, 1. 5, 2. 0 Ø Full coverage of APP 6 A ŁOWCZA GEO MIP Ø RAP in near realtime Ø Updating operational database (with resources states) Ø Exchange of airspace coordination factors HUB Baseline 2 Baseline 3. 1 Ø Data conversion between MIP baselines Ø Full APP 6 -A coverage Ø Transparent to the user Map formats: Ø Raster: CADRG, GEOTIFF, MRSID, ECW, JPEG 2000, DTED Ø Vector: VPF, SHP, MIF, MAP, KML, XYZ Ø Online: WMF, WFS Ø Gazetteer

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 C 2 IS • 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

The operational concept of JTLS and SZAFRAN integration The vision • Supporting the staff exercises on the tactical and operational level using C 2 IS: • 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 C 2 i. S variants of operation using simulation system: • The JTLS provides a simulation of the battlefield with many factors not available to C 2 IS, • The JTLS provides a time coordination. • Playing the role of the “intelligent” enemy in tactical exercises facilitating command control system; • The JTLS plays „red cell” of the staff exercises, • The JTLS provides more automatic and reactive enemy.

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

The operational concept of JTLS and SZAFRAN integration Definition of the task • Task of interconnecting simulation system to C 2 IS 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

Starting level of interoperability between SZAFRAN and JTLS • ADat. P-3 messages(OWNSITREP, ENSITREP) sent from JTLS to SZAFRAN • KML layers (Keyhole Markup Language) sent from JTLS to SZAFRAN • ADat. P-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)

The operational concept of JTLS and SZAFRAN integration The solution JTLS • Automated connector which could bidirectionally exchange information between JTLS database and SZAFRAN’s IEG • Mechanism is completely persistent to the JTLS • Mechanism is completely persistent to SZAFRAN or other C 2 IS class system SDR Information Exchange Gateway (IEG) Buffer database MIP 2 • The core of the solution is proper mapping the simulation data MIP 3. 1 JTLS Connector MIP 3. 0 SZAFRAN C 2 IS or other C 2 class system Operational database

The current level of interoperability between SZAFRAN and JTLS – the use case Real-time feed HICON/EXCON (SZAFRAN) • Currently achieved JTLS interoperability: C 2 IS data exchange • 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 LOCON JTLS Only TA (SZAFRAN) TA TA (SZAFRAN) Scenario day STARTEX feed C 2 IS data exchange JTLS players LOCON JTLS Only JTLS

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