How to increase NATO capabilities interoperability, when dealing with the ‘Unexpected'

How to increase NATO capabilities interoperability, when
dealing with the ‘Unexpected'
18th ICCRTS
June 19-21, 2013
at
The Institute for Defense Analyses
Alexandria, Virginia (USA).
Paper ID:013
By
Dr. Alain Mutambaïe
1
Table of contents
1. Introduction
1. Unexpected challenges
2. ACCS
2. ESB Federation Strategy
1. Coarse grain
2. Fine grain
3. Findings and Conclusions
1. Findings
2. PKI
3. Conclusions
18th ICCRTS
2
Introduction: Interoperability Challenges with “Unexpected” in
Coalition Environment
NII
Technical
Interoperability
Patterns
18th ICCRTS
3
Introduction: Why ACCS is a good Case?
US
Canada
Luxembourg
Albania
Croatia
No “fixed” ARS
or CAOC
Maggeroe
Soerreisa
Karup
Boulmer
Vedbaek
UK
Scampton
Estonia
Erntbruec
Denmark
Latvia
Lithunia
NL
Nieuw Milligen
BE
Glons,
STVF
Cinq Mars La
Pile
Lyon Mont
Verdun
Torrejo
n Portugal
Monsant
o
Germany
LU
France
Italy
ARS
DARS
CAOC
DCAOC
CARS
STVF
Stara
Boleslav
Messtetten
Slovakia
Hungary
Spain
Uedem
Bydgoszc
z
Krakow
Poland
Czech
k
Core
Validation
Replication NATO
Replication National
Poggio
Renatico
Larissa
Romania
Kecskeme
t Veszprem Eskisehir
Bulgaria
Turkey
18th ICCRTS
Moro
n
Zaragoza
Gioia del
Colle
Greece
Souda
Diyarbakir
4
AWCIES with 6500 Physical Interfaces Represents I/O
Challenges Similar to other Coalition Capabilities (connect to
unexpected users)
CIC
NBC
Other ACCS
Nat’l Airspace Mgt
Cell
ADatP-3
AWCIES
ADatP-3
WOC/SQOC
AWCIES
AWCIES
NATO Army/Navy
C2 System
Existing A/D
Systems
ADatP-3
ADatP-3
WAN Router
Interfaces
Intelligence
ADatP-3
SSSB
Afloat
ADatP-3
ADatP-3
ADatP-3
Operational
Processes
WMO
Bit Oriented
Various
Sensors
ADEXP, OLDI
ASTERIX
DLIP
Link-16
Link-11B
Link-1
Link-11B
SSSB/Maritime Afloat
ACCS Liaison
Army/Navy
Nat’l CCIS
ADatP-3
SDCP
METEO
18th ICCRTS
Airbases
Character Oriented
ATDL-1
Link-11B
SAM/SHORAD
Systems
ACCS Liaison
Army/Navy
ATC Services
Link-11B
Link-1
Link - 16
Existing A/D
Systems
5
ESB Federation Strategy (Innovative
Approach)
• The strategy is to federate all vendor-independent ESB
initiatives and allow NATO and Nations’ systems to flexibly
share information
• The ESB federation could be built incrementally with
systems being added or replaced in a repeatable pattern
• Topologically, the ESB federation can be seen as a complex
network of systems, applications and services connected to
nodes, which are the ESBs: The Fractal Approach
18th ICCRTS
6
ESB Federation Coarse Grain Strategy:
ACCS NNEC*
18th ICCRTS
* Prototype for post ACCS LOC1
7
ESB Federation Strategy Based on Four
Similarity Elements
18th ICCRTS
1)
Visibility
2)
Security / IA
3)
4)
Required Information
Other ESB connections
8
Five Environmental Parameters Generating
Irregularity of Patterns
1)
2)
3)
4)
5)
18th ICCRTS
Operation type (i.e.,
relief, asymmetric,…)
NATO partnership (i.e. EU,
UN, PfP,...)
Technology availability
(i.e IPv6, Web,…)
Interoperability targets
(i.e ambition, strategy,
objectives, effects,...)
Time (i.e., operations
duration, deployment
timeframe, operation
date,…)
9
ESB Federation Fine Grain Strategy: ACCS
NNEC* Perspective
• The ESB federation strategy can also be adopted as an agile transition to a
potential direct/better future interface pattern
• However the agile ESB federation strategy will remain extant until it is replaced
by a better strategy because of the instability of environmental parameters (the
Unexpected)
18th ICCRTS
* Prototype for post ACCS LOC1
10
Findings: AWCIES readiness to “Unexpected
Users”
Non Real Time Information
Real Time Information
Unexpected capability
ATO,ACO
Bl11,13,14, 15
VMF, OTH Gold
FFT, MSA
RAP and TBM
picture in XML,
NVG, Other
Format
AWCIES
ESB
ACCS
AWCIES
JC3IEDM
ESB
JPTL, TNL
Unexpected Format
• Some future interfaces, standards and formats have been identified and assessed
• ESB federation patterns from ACCS perspective based on:
• up to 4 different (vendor-independent) ESBs connected, environmental
parameters and Likert scale multi-criteria decisions ( based 8 KPIs and ROIs)
• Stakeholders involvement and governance needed
18th ICCRTS
11
8 Key Performance Indicators (1/2)
to Measure Coalition Information Superiority Success
Operator
Satisfaction/Expectati
on
4
Coalition
Time/Duration
3
Interoperability
Targets Fulfillment
2
1
Pattern Reusability
0
Cost of Ownership
Pattern RT_RAP1
Pattern RT_RAP3
Technology/Infrastruc
ture Availability
Security /IA
Information
Visibility/Quality
18th ICCRTS
12
Key Performance Indicators (2/2)
Operator
Satisfaction/Expect
ation
4
Coalition
Time/Duration
3
Interoperability
Targets Fulfillment
2
1
Pattern Reusability
0
Pattern RT_RAP1
Cost of Ownership
Pattern RT_RAP3
Pattern NRT_JPTL1
Technology/Infrast
ructure Availability
Security /IA
Information
Visibility/Quality
18th ICCRTS
13
Conclusions
• Technical Interoperability with the unexpected is still a challenge
• While not a panacea, ESB Federation Strategy is an innovative
approach to enable information sharing with unexpected capabilities
• Findings implemented in current and future capabilities
• NATO led coalitions C2 can easily implement ESB Federation Strategy
• ESB Federation Strategy will save cost and time when connecting NATO
forces in coalition
• KPIs provide decisive indications to a commander (like hotel stars for
travelers)
• Still changes and proactive actions need to be taken to support NATO
transformation and challenges (stakeholders involvement, security,
governance)
18th ICCRTS
14
BACK UP
15
FFT Proof of Concept Overview
Link16
TST
J3.5
(Friendly)
J12.0 (8) Investigate
J12.0 (5) Engage*
CAS
J12.0 (20) CAS
J12.4 Change to FAC control
ARS
NFFI
TOC/COC
FSE/FSCC
FFTS
Proof of Concept Conditions
PoC Figures
Description
Fighter Simulator
2 (TRS, IABG)
FFT Provider
3 (Imp@ct KFOR,
BFTS-NO ISAF, BFTS
NC3A)
FFT Format
NFFI 2.0, NFFI 1.3
Transport protocol
IP1 (TCP/IP Socket),
IP3 (Web Service
PUB/SUBS)
Operational Scenarios
TST, CAS
ACCS Display
DISPMX (ACCSLOC1),
LUCY (ACCS Exp)
FFT Refreshment Rate
3 Min, 1Min, 10 Sec
L16 Network
SIMPLE
Fighter Location
Remote (IABG)
On Site (TRS)
• Quick-Win: NNEC-2
Software Development
achieved within 7
weeks.
• No change in ACCS
LOC1 designed
architecture
• Minor modifications in
ACCS LOC 1 existing
functionalities
NATO UNCLASSIFIED
17
Qualitative Results
Interoperability Targets
Fulfillment Item
Fighter Simulator:
1.
TRS
2.
IABG (EuroFighter)
FFT provider:
1.
Imp@ct KFOR:
2.
BFTS-NO:
3.
BFTS NC3A:
Status
1.
2.
Success
Limited Success
Comment
1.
2.
No comment
IABG was able to play only
during last CWID week
No Comment
1.
2.
3.
Success
Success
Success
FFT format:
NFFI 2.0, NFFI 1.3
Success
No Comment
Transport protocol:
IP1, IP3
Success
No Comment
Operational Scenarios:
1.
TST
2.
CAS
Success
No Comment
ACCS Display:
1.
DISPMX (ACCS LOC1)
2.
LUCY (ACCS Exp)
FFT refreshment rate:
1.
3 Min
2.
1Min
3.
10 Sec
1.
1.
2.
Success
Success
Success
NATO UNCLASSIFIED
2.
DISPMX resolution to be
improved
No comment
Optimal rate on the log files
See final report
18