1
NATO IMPROVED LINK ELEVEN (NILE) PROGRAM THIRD PARTY SALES (3PS) PRESENTATION LCdr Troy Richard (CAN) CAN Rep/3PS Officer LCdr Alessandro Battaglia ITA Rep/Technical Lead INFORMATION NOT RELEASEABLE FOR COMMERCIAL USE OR BEYOND IMMEDIATE AUDIENCE WITHOUT PRIOR PERMISSION OF THE NILE PMO 2
OBJECTIVE Provide an update on the NILE Project and Link 22 implementation and testing activities for the purpose of furthering interest in Link 22 as a vital tool in Network Centric Warfare (NCW) and in building global interoperability Demonstrate that Link 22 is real and being implemented today 3
Background Functional Architecture LINK 22 Operational Characteristics NILE/Link 22 Working Groups National Developments and System Testing National Implementation Strategies Third Party Sales Q&A OUTLINE 4
Objective Design a New Tactical Data Link System (Link 22) consisting of a computer-to-computer digital data link among tactical data systems equipped ships, submarines, aircraft and shore sites which will meet the requirements of the NATO Staff Requirement, dated 9 March 1990 Develop flexible and operational BLOS means to exchange Tactical Data amongst platforms and to obtain better overall tactical connectivity and coordination Requirements BACKGROUND Operational: NATO Staff Requirement, revised Mar 90 System, Functional and Performance: NATO Elementary Requirements Document, 12 Dec 94 5
Goals Replace Link 11 Complement Link 16 LINK 22 BACKGROUND Improve Allied Interoperability Enhance Commanders War-Fighting Capability 6
BACKGROUND Developed collaboratively by 7 Nations under the aegis of a Memorandum of Understanding (MOU) NILE Nations currently conducting the In-Service Support (ISS) Phase under MOU (effective Jul 2002), Amendment 3 (effective Jun 2007 to Jan 2014) Current ISS contract with Northrop Grumman to cover MOU period (until January 2014) Spain replaced Netherlands as part of the NILE ISS Phase in 2004 United States is Host Nation NILE Nation representatives form Steering Committee (SC) which governs the direction and future growth/distribution of Link 22 7
BACKGROUND Nov. 1987 June 1992 June 1996 July 2002 Jan. 2014 PD Phase D&D - SP1 D&D - SP2 ISS Phase 1985 1990 1995 2000 2005 2010 SNC V9.2 8
BACKGROUND Project and System Governance provided by: Project documents Interface/System design documents, requirements specifications, etc Release of NILE Project Information available to NILE Nations and approved 3PS nations (following payment of levies/maintenance fees) Link 22 Guidebook under development NATO Documents NATO Standardization Agreements (STANAGS) (ie. 5522) NATO Allied Data Publications (ADatP) (ie. ADatP-33) 9
BACKGROUND Concept of mutual operation governed principally by: ACO Joint Concept of Employment (COE) for Tactical Data Links in NATO describes how NATO commanders will employ TDLs in a joint multi-link environment in pursuit of operational objectives Applies to coalition operations involving NATO and non- NATO nations Allied Data Publication (ADatP-33) Multi-Link SOPs for Tactical Data Systems employing Link 11, Link 11B, Link 16, IJMS and Link 22 10
FUNCTIONAL ARCHITECTURE Host system Signal Processing Controller HF FF Radio HF FF and Data Link Processor System Network Controller Link Level COMSEC Link Level COMSEC Signal Processing Controller UHF FF Signal Processing Controller HF EPM Radio UHF FF Radio HF EPM Signal Processing Controller UHF EPM Radio UHF EPM Application, Presentation and Session layers (OSI 7, 6, 5) Transport layer (OSI 4) Network layer (OSI 3) Data Link layer (OSI 2) Physical layer (OSI 1) 11
OPERATIONAL CHARACTERISTICS Link 22 overcomes the following Link 11 deficiencies: Lack of Electronic Protective Measures (EPM) Insufficient capacity in terms of Tactical Message Throughput Insufficient robustness (i.e. over-reliance on NCS) Insufficient error detection and correction Inflexible and slow data link procedures Message standard limitations Limited routing 12
OPERATIONAL CHARACTERISTICS Differences Link 22 has no Net Control Station Link 11 does not distinguish between Urgent and Routine Information Link 22 has built in Relay Commonalities The same frequencies (HF and UHF Fixed frequency) The same radios (HF and UHF FF) That s it! 13
OPERATIONAL CHARACTERISTICS Link 22 as a complement to Link 16: Provides a multi-media TDL BLOS capability, but without the requirement for satellite connectivity Uses the same dictionary elements and 70% message format commonality to Link 16 to facilitate data forwarding Maintains in excess of 95% commonality of DFIs/DUIs 14
OPERATIONAL CHARACTERISTICS Link 22 Operations SN NU5 NU3 NU2 NU1 NN1 - HF NU6 NU12 NU7 Interrupt Slot NU9 NU7 NU16 NU8 NU9 NU17 NU26 NN3 - UHF NU24 NU18 IS NU2 NU11 NU6 NU13 IS NN2 HF EPM NU14 NU16 NU15 NU9 NU20 NU9 NU17 NU15 NU21 NU24 NN4 UHF EPM NU 23 NU10 NU19 15
OPERATIONAL CHARACTERISTICS Key Features Multi-Media/Multi-Network 1 globally-maintained Super Network (SN) Seamless connection of up to 8 simultaneous physical networks (each platform on up to 4 physical networks) A SN can be: As simple as 2 units communicating over an RF link As comprehensive as 125 units on 8 different medias (HF/UHF FF/EPM) Depending on national implementation, Link 22 is capable of operating in fixed frequency or EPM mode, in either the HF or UHF bands Selected waveforms have further parameters that allow tailoring to the prevailing RF channel conditions 16
OPERATIONAL CHARACTERISTICS Key Features Dynamic Time Division Multiple Access (DTDMA) TDMA protocols allocate dedicated transmission capacity to each active unit and avoids dependence on a single net control node DTDMA allows a unit to request and receive more bandwidth on a physical network in order to accommodate increased transmission requirements Accomplished without service interruption and without operator intervention Dynamic Congestion Management Allows the management units to monitor network congestion and take any necessary steps to rectify problems 17
OPERATIONAL CHARACTERISTICS Key Features Routing and Relay Each SNC keeps an internal routing table, updated in realtime and based on technical feedback transmitted on the networks Allows decision on which NNs will relay messages (relay responsibility) to which NNs based on the best route Allows units to relay messages between NUs that are not within direct RF range of each other The SNMU uses its knowledge of the operational requirements, the location and movements of NUs and their communication requirements, to tailor the operation of the SN routing capability 18
Participation in: LINK 22 NILE/Link 22 Working Groups Communications and Interoperability Working Group (C&IWG) NILE Configuration Control Board (CCB) NATO Data Link Working Group (DLWG) NATO Tactical Data Links Interoperability and Testing Syndicate (TDLITS) NATO Tactical Data Links Symposium (NTDLS) NATO Radio Working Groups International Data Link Symposium (IDLS) 19
C&IWG NILE/Link 22 Working Groups O&IWG (NATO controlled) major goals accomplished including NATO Multi-TADIL COE (including Link 22), approved Jan 2007. O&IWG suspended by unanimous consent C&IWG Terms of Reference (TORs) Established under the NILE SC Remaining L22 OIWG items (STANAG 5522, COMSEC Issues), potential future Link 22 waveform improvements, Interoperability Testing, etc 2 nd C&IWG conducted May 2008 in UK Link 22 Portal for the C&IWG, open to all nations (individual registration must still be approved): https://www.link22.org/link22ciwg 20
CCB LINK 22 NILE/Link 22 Working Groups Responsible for configuration of the NILE software and specifications Attended by PMO and representatives from NILE Nations Technical and Secretarial support provided by the PMO Annually, one in-person and several virtual meetings 3PS Nations are able to submit issues and are represented by their Sponsor Nation DLWG PMO attends to advise/report on and remain aware of Link 22-relevant issues/activities 21
TDLITS LINK 22 NILE/Link 22 Working Groups Assist in the incorporation of the Link 22 system and protocols into the SIMPLE Testing protocols, as defined in STANAG 5602 Will continue to be involved as we progress towards national implementations and in-the-field interoperability NTDLS An international forum open to NATO and partner nations Provides an opportunity to exchange experiences, introduce national approaches and discuss general concepts on NATO TDLs on an expert level in order to improve knowledge and enhance interoperability 22
NILE/Link 22 Working Groups NATO Radio Working Groups As required/requested to remain aware of current issues and provide input. For example: IDLS To concur in the development of new waveforms To provide input towards NILE-related STANAGs (ie. 4539, 4205, 4444, 4372) To avoid discrepancies between STANAGs and NILE documents Provides a forum to bring together government and industry/military and civilian within the international data links community Provides the PMO the opportunity to educate and showcase Link 22 and has proven invaluable in making contacts WRT 3PS 23
National Developments and System Testing As a project, we have taken a sharp turn towards implementation and multi-national cooperation Tremendous Spirit of cooperation and Leadership role exercised by nations and industry Sharing of information by participating nations (NILE and 3PS Nations) will benefit the community at large As a system, Link 22 is at a stable level of maturity Transitioning to an actual field-tested, multi-national system System Implementations are commencing 24
National Developments and System Testing IDLS 2007 Demonstrations (Oct 2007) Finland/Germany Ship/Shore Live Trial (Nov 2007) FRA/DEU Industry Live Experiment (Nov 2007) NILE SPC Compatibility Testing (Dec 07 and Beyond) FRA and GBR Deployed Ship-to-Shore Trial (Jun 08) FRA/DEU Interoperability Testing (Sep 08) CV CAVOUR (ITA) Implementation (Sep 08) French LUCID Live Reference Platform (TBD) 25
NATIONAL IMPLEMENTATION STRATEGIES Italy 2008 France 2009 Germany 2010 Spain 2010 Canada 2011 US TBD UK 2014 26
NATIONAL IMPLEMENTATION STRATEGIES 2008 CV CAVOUR (1) (2008) CV GARIBALDI (1) (2009) DDG ORIZZONTE (2) (TBD) DDG DE LA PENNE (2) (2010) FREMM Frigates (6) (2011) Link 22 DLP is already available Link 11-16 M-DLP (with Data Forwarding) already available On going fusion among different DLP segments Installation in CV Cavour completed, testing through remainder of 2008 Completion of Link 11-16-22 M-DLP (inclusive of all data forwarding capabilities) expected in second half of 2009 27
NATIONAL IMPLEMENTATION STRATEGIES 2009 Multi-Mission Frigate (FREMM) CV Charles De Gaulle Anti-Air Frigate Amphibious Assault and Command Ships Mistral and Tonnerre La Fayette Class Frigates SSN Barracuda 2 Link 22 Fixed and 1 Mobile Station currently available. Link 22 operational implementation will occur in the Multi-Mission Frigate (FREMM) in 2009. Future Link 22 operational implementation is planned for the Carrier Vessel Charles de Gaulle, the Anti-Air Frigate, and the Amphibious Assault and Command ships Mistral and Tonnerre, but not before 2012. Additional ships are planned for later integration including AD destroyers, Amphibious Assault and Command ships, La Fayette Class frigates and the Submarine SSN Barracuda. As for airborne Link 22 integration, studies are in process for the HELO NH90, and the Maritime Patrol Aircraft ATL2 28
NATIONAL IMPLEMENTATION STRATEGIES 2010 F123 class F125 class Ground facilities in place Germany has stated that they planned for implementation in four F 123 class ships between 2011 and 2014 Implementation in four F 125 class ships between 2012 and 2017 29
NATIONAL IMPLEMENTATION STRATEGIES 2010 LPDs Galicia and Castilla Aircraft Carrier Príncipe de Asturias F-100 frigates LHD Juan Carlos I BAC Cantabria S-80 submarines BAM ships Land Training Center, CPT/CIA Spain is planning for the first Link 22 Spanish ship by 2010, with Link-22 implementation in all Spanish Navy ships, based on an overall Spanish Navy Data Link Migration Strategy that includes Link 11, Link 16, and Link 22. There will be two types of integration, based on the C2 technology: F-100 with C2P technology, and the remaining platforms (LPDs, S-80 and SCOMBA units) via the multi-link processor LINPRO Mobile Shore facilities to be in place in 2008 30
NATIONAL IMPLEMENTATION STRATEGIES 2011 Halifax Class Frigates Canada will employ a multi-tdl implementation approach: leverage existing technology to acquire a DLP capable of hosting Link 11, Link 16, Link 22 and JREAP. Starting in 2011, this would provide Canada operational link capability across a wide range of interoperability, and provide a wide spectrum of link capability 31
NATIONAL IMPLEMENTATION STRATEGIES TBD TBD Link 22 is an unfunded requirement. 32
NATIONAL IMPLEMENTATION STRATEGIES 2014 Data Link System for Maritime Platforms In-Service Date (ISD) for 2 platforms by Dec 2014 33
NATIONAL IMPLEMENTATION STRATEGIES Per Platform Transition Costs/Strategy Cannot be determined by PMO Factors to be considered: Anticipated host system (Platform, Tactical Data System, Data Link Processor) Required level of integration Current Link capability Ability to regenerate SPCs and Radios for L22 etc 34
THIRD PARTY SALES (3PS) All requests for Link 22 are processed by the NILE PMO and forwarded to the NILE SC for consideration/approval Background The NILE Third Party Sales (3PS) Document was Approved by the NILE Steering Committee (SC) 21 May 2002 currently under revision Provides for the sale and/or transfer of NILE products to third parties IAW provisions of the NILE Design and Development (D&D) and In-Service Support (ISS) Memoranda of Understanding (MOUs) 35
THIRD PARTY SALES (3PS) Background (cont.) Governing Principle: No NILE Nation will sell, transfer title to, disclose, or transfer possession of NILE project foreground information without prior written consent of all NILE Nations via the NILE SC Exception: COMSEC (Link Level COMSEC) Transfer must have prior US approval Types Government-to-Government (FMS) or Direct Commercial Sales (DCS) Sales can be conducted by any NILE Nation 3PS Process remains the same 36
Process LINK 22 THIRD PARTY SALES (3PS) NILE Nation sponsors Request to Transfer NILE Products Application sent to NILE PMO for technical review/processing NILE PMO sends reviewed application to the NILE Nations for approval Once unanimous approval is granted, 3PS may commence Fee Calculation Levy/Maintenance fees calculated as part of sale Levy per Link 22 system (SNC software) sold Maintenance fee on annual basis per third party nation Fees do not include hardware and integration costs 37
THIRD PARTY SALES (3PS) Country DLP Integration LLC SPC Radios Tools Training Canada France Thales DCNS Atos Origin Rockwell-Collins France Thales Atos Origin Atos Origin Germany ATLAS ELEKTRONIK ATLAS ELEKTRONIK Telefunken RACOMS Rohde & Schwarz Hagenuk Marinekommunikation ATLAS ELEKTRONIK Italy Elsag-Datamat Elsag-Datamat SELEX Comms Spain TECNOBIT TECNOBIT CIDA UK IBM UK Aerosystems International IBM UK Aerosystems International 3SDL SyntheSys LM/STASYS US Northrop Grumman Northrop Grumman ViaSat DRS Northrop Grumman Northrop Grumman 38
NILE Nations: LINK 22 Access to NILE Information Contact Steering Committee Member or refer to Link 22 Portal: https://www.link22.org The Portal is the main source for Link 22 documentation, configuration management and knowledge management Questions posted to the forums will always be answered by the NILE PMO Access is permitted to NILE Nations (Government and Industry) following approval by the sponsoring Nation s Steering Committee (SC) Representative 39
Access to NILE Information Non-NILE Nations: Contact the Acting Program Manager CDR Francisco Cornago Phone: (858)537-0151 Fax: (619)524-7856 E-mail: francisco.cornago.sp@navy.mil 40
QUESTIONS? 41
ACRONYMS 3PS ACO ADatP AP BLOS C&IWG C2P CCB CG CJCSI CMS COE Third Party Sales Allied Command Operation Allied Data Publication Adjunct Processor Beyond Line Of Sight Communications and Interoperability Working Group Command and Control Processor Configuration Control Board Guided Missile Cruiser Chairman of the Joint Chiefs of Staff Instruction Combat Management System Concept Of Employment 42
ACRONYMS COMSEC COTS CV D&D DCS DDG DF DFI/DUI DLP DLWG DTDMA DTS Communications Security Commercial Off The Shelf Carrier Vessel / Multi-purpose Aircraft Carrier Design and Development Direct Commercial Sales Guided Missile Destroyer Data Forwarding Data Field Identifier / Data Use Identifier Data Link Processor Data Link Working Group Dynamic Time Division Multiple Access Data Terminal Set 43
ACRONYMS EPM FFF FMS FREMM HF HF FF HF EPM HMI IDD IDLS IO IRS Electronic Protection Measures Form Fit Function Foreign Military Sales Frigate European Multi-Mission High Frequency High Frequency Fixed Frequency High Frequency Electronic Protection Measures Human-Machine Interface Interface Design Document International Data Link Symposium Interoperability Interface Requirement Specification 44
ACRONYMS ISS JREAP LHD LINPRO LLC LMS LNE LPDs LUCID MASN M-DLP MLST3 In-Service Support Joint Range Extension Application Protocol Landing Helicopter Dock/Amphibious Assault Ship Link Processor Link Level COMSEC Link Monitoring System Late Net Entry Landing Platform Dock/Amphibious Transport Dock Link 22 Unit Controller and Interoperability Demonstrator Mission Area Sub-Network Multi-Data Link Processor Multi-Link System Test and Training Tool 45
ACRONYMS MS NATO NCE NCS NCSTI NILE NMU NN NMT NRS NSA NTDLS Media Simulator North Atlantic Treaty Organization NILE Communications Equipment Net Control Station / Network Cycle Structure US Naval Center for Tactical System Interoperability NATO Improved Link Eleven Network Management Unit NILE Network Network Management Tool NILE Reference System National Security Agency NATO Tactical Data Link Symposium 46
ACRONYMS NU OIWG ONCS OSI PMO RF RIP RIS SC SIMPLE SN SNC NILE Unit / Link 22 Unit Operations and Interoperability Working Group Operational Network Cycle Structure Open System Interconnection Program Management Office Radio Frequency Release In Principle Release In Specific Steering Committee Standard Interface for Multiple Platform Link Evaluation Super Network System Network Controller 47
ACRONYMS SNMU SOP SPC STANAG TDL TDLITS TDMA TDS TOD TOR UHF UHF EPM UHF FF Super Network Management Unit Standard Operating Procedure Signal Processing Controller NATO Standardization Agreement Tactical Data Link Tactical Data Link Interoperability Test Syndicate Time Division Multiple Access Tactical Data System Time Of Day Terms Of Reference Ultra High Frequency Ultra High Frequency Electronic Protection Measures Ultra High Frequency Fixed Frequency 48