NATO Improved Link Eleven (NILE) Project Update. -Link 22

Similar documents
NATO IMPROVED LINK ELEVEN (NILE) PROGRAM THIRD PARTY SALES (3PS) PRESENTATION

NATO IMPROVED LINK ELEVEN (NILE) PROGRAM STATUS PRESENTATION

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE N: Consolidated Afloat Network Ent Services(CANES) FY 2012 OCO

Supporting Nations With Acquisition of Multi-functional Information Distribution System (MIDS) Capability

UNCLASSIFIED R-1 ITEM NOMENCLATURE. FY 2014 FY 2014 OCO ## Total FY 2015 FY 2016 FY 2017 FY 2018

The Ship Acquisition Process: Status and Opportunities. NDIA Expeditionary Warfare Conference 24 October 07

Implementation and Integration of TDL's in Maritime Platforms (AWD). CAPT James Nash SEA 4000 FMS Director

Lessons Learned from the MSG- 128 Study on Incremental Implementation of NATO Mission Training through Distributed Simulation Operations

UNCLASSIFIED. R-1 Program Element (Number/Name) PE A / Integrated Personnel and Pay System-Army (IPPS-A) Prior Years FY 2013 FY 2014 FY 2015

US Navy Ships. Surface Warfare Officer First Tours

Joint Tactical Radio System (JTRS)

UNCLASSIFIED FY 2016 OCO. FY 2016 Base

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Air Armament Symposium. 5 October 2011 Col Tim Morris, USAF Director of Development F-35 Lightning II Program

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

OPNAVINST A N2/N6 31 Oct Subj: NAVY ELECTRONIC CHART DISPLAY AND INFORMATION SYSTEM POLICY AND STANDARDS

16 Oct 2007 National Status Netherlands

ARCHIVED REPORT. SSQ-72/108(V) (OUTBOARD/OUTBOARD II) - Archived 7/2002. Outlook. Orientation. Electronic Warfare Forecast

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 15 R-1 Line #232

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE N: Unmanned Combat Air Veh(UCAV) Adv Cp/Proto Dev. FY 2011 Total Estimate. FY 2011 OCO Estimate

Sea Air Space. Sea Power to the Hands of Our Sailors. RDML Jon Hill April 13, 2015

A Common Interface Language For U nm anned System s Technology to the Warfighter Quicker

ROBUST NATO BALLISTIC MISSILE DEFENSE

SSC Pacific is making its mark as

ALTBMD. Dave Kiefer ALTBMD Deputy Programme Manager NATO UNCLASSIFIED

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 17 R-1 Line #87

UNCLASSIFIED R-1 ITEM NOMENCLATURE. FY 2014 FY 2014 OCO ## Total FY 2015 FY 2016 FY 2017 FY 2018

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Navy ManTech Program. ManTech Update. Tom Hite CTC 15 October 2014

TTGL Command Brief Oct 2011

C-IED Working Group Update to the C-IED Conference. COL Juan GÓMEZ MARTIN C-IED WG Chairman

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 8 R-1 Line #156

ARCHIVED REPORT. For data and forecasts on current programs please visit or call

Joint Coordinated Implementation of Digitally-Aided CAS Capability

CHAIRMAN OF THE JOINT CHIEFS OF STAFF INSTRUCTION

UNCLASSIFIED. UNCLASSIFIED Navy Page 5 of 10 P-1 Line #11

An Example for Pooling & Sharing

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE F: Air Force Integrated Personnel and Pay System (AF-IPPS) FY 2012 OCO

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

Exhibit R-2, RDT&E Budget Item Justification

Systems Engineering & LRASM

UNCLASSIFIED UNCLASSIFIED. EXHIBIT R-2, RDT&E Budget Item Justification February 2007 RESEARCH DEVELOPMENT TEST & EVALUATION, NAVY / BA-7

EXHIBIT R-2, RDT&E BUDGET ITEM JUSTIFICATION N/SHIP SELF DEFENSE (ENGAGE: SOFT KILL/EW)

CHAIRMAN OF THE JOINT CHIEFS OF STAFF INSTRUCTION

COMMON AVIATION COMMAND AND CONTROL SYSTEM

2016 Major Automated Information System Annual Report

B. Program Change Summary: RDT&E BUDGET ITEM JUSTIFICATION SHEET (R-2 Exhibit) FEBRUARY 2008 APPROPRIATION / BUDGET ACTIVITY RDT&E, DEFENSE-WIDE / 7

DATE: FY 2013 President's Budget February 2012 PRIOR YR FY 2011 FY 2012 FY 2013 FY 2014 FY 2015 FY 2016 FY 2017 TO COMP TOTAL PROG QUANTITY

R Z SEP 17 FM CMC CDI MEXWID WASHINGTON DC TO RUJIAAA/COMMARFORCOM RUJIAAA/COMMARFORCOM G FOUR RUJIAAA/COMMARFORCOM G THREE G FIVE G SEVEN

Exhibit R-2, RDT&E Budget Item Justification

DEPARTMENT OF THE NAVY

EOD publications - overview

Office of Executive Director for Conventional Ammunition (O/EDCA)

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

UNCLASSIFIED. R-1 Program Element (Number/Name) PE F / Joint Air-to-Surface Standoff Missile (JASSM) Prior Years FY 2013 FY 2014 FY 2015

DATE: FY 2016 President's Budget February 2015 PRIOR YR FY 2014 FY 2015 FY 2016 FY 2017 FY 2018 FY 2019 FY 2020 TO COMP TOTAL PROG QUANTITY

UNCLASSIFIED FY 2016 OCO. FY 2016 Base

UNCLASSIFIED. FY 2017 Base FY 2017 OCO

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 7 R-1 Line #91

Exhibit R-2, RDT&E Budget Item Justification

OPNAVINST F N4 5 Jun 2012

UNCLASSIFIED R-1 ITEM NOMENCLATURE

Joint Program Executive Office Joint Tactical Radio System

Capabilities Presentation

DEPARTMENT OF THE NAVY COMMANDER NAVAL EDUCATION AND TRAINING COMMAND 250 DALLAS STREET PENSACOLA, FLORIDA

CHAIRMAN OF THE JOINT CHIEFS OF STAFF INSTRUCTION

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Exhibit R-2, RDT&E Budget Item Justification

2016 Major Automated Information System Annual Report

UNCLASSIFIED. UNCLASSIFIED Navy Page 1 of 19 R-1 Line #71

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

COMMAND MISSION COMMAND ORGANIZATION

Sea Viper Maritime Missile Defence

International Data Link Symposium 2006 National brief - Norway

Ballistic Missile Defence

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE F: Control and Reporting Center (CRC) FY 2011 Total Estimate. FY 2011 OCO Estimate

UNCLASSIFIED. FY 2016 Base

Enabling Multinational Communications with CENTRIXS

N/SINGLE INT. AIR PICTURE (SIAP) SYS ENG

UNCLASSIFIED UNCLASSIFIED

Code 25 Submarine Network Support Services. Pre-Solicitation Conference

LASD/Metro Transit Security Program

DEPARTMENT OF THE NAVY HEADQUARTERS UNITED STATES MARINE CORPS 3000 MARINE CORPS PENTAGON WASHINGTON, DC

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE BB: Special Operations Aviation Systems Advanced Development

PROGRAM ELEMENT TITLE: Airborne Reconnaissance Advanced Development (ARAD)

Subj: MISSION, FUNCTIONS, AND TASKS OF NAVAL SPECIAL WARFARE COMMAND

UNCLASSIFIED. LandWarNet Army Request for IT (ARFIT) Information Exchange Forum (IEF)

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Legacy Tanker Division

UNCLASSIFIED UNCLASSIFIED

R-1 ITEM NOMENCLATURE / PROJECT NO. PE BB SOF PSYOP/D476. COST (Dollars in Millions) FY07 FY08 FY09 FY10 FY11 FY12 FY12

Command Overview Naval Surface Warfare Center, Carderock Division

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 11 R-1 Line #92

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 15 R-1 Line #222

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

2016 Major Automated Information System Annual Report

Transcription:

Slide 1 NATO Improved Link Eleven (NILE) Project Update -Link 22 LCDR Peter Duffley Third Party Sales Officer / Canadian Representative Statement A: Approved for public release; distribution is unlimited (26 SEPTEMBER 2012)

Slide 2 Agenda (1/2) 1. NILE Project Overview a. Objective b. Project Background c. Project Milestones & Challenges d. Link 22 Overview e. Organization / Tasks f. Coordinated Meetings g. Liaison with Link 22 Related Organizations 2. NILE Project Status a. Link 22 Force Structure & Implementation Plans b. National Developments & Operational Testing c. COMSEC Update

Slide 3 Agenda (2/2) 3. NILE Test Tools (NRS/MLST3) 4. Third Party Sales(3PS) a. 3PS Status & Procedures b. Link 22 Vendors 5. Access to NILE Information/ POCs a. Link 22 Guidebook b. Link 22 Customer Information Guide (CIG) c. C&IWG Overview / Attendance Procedures d. NILE Points of Contact

Slide 4 NILE PROJECT OVERVIEW

Slide 5 Objective 1. Provide an overall NILE Project summary & update a. Focus on changes since IDLS 2010 b. Major Milestones achieved / on-going 2. Highlight the current state of implementation, testing and global interoperability a. Link 22 already fielded in operational platforms (IOC achieved)

Slide 6 Project Background (1/3) 1. Developed collaboratively by 7 Nations under the aegis of Memorandum of Understanding (MOU) 2. NILE Nations currently conducting In-Service Support (ISS) under MOU Amendment 3 (Jun 07 Jan 14) 3. MOU Amendment 4 is under negotiations 4. Spain replaced Netherlands as part of the NILE ISS Phase in 2004 5. United States of America (USA) is Host Nation 6. NILE Nation representatives form the Steering Committee (SC) which governs the direction and future growth/distribution of Link 22

Slide 7 7. Objective a. 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 b. Develop flexible and operational Beyond Line of Sight (BLOS) means to exchange Tactical Data amongst platforms and to obtain better overall tactical connectivity and coordination 8. Requirements Project Background (2/3) a. Operational: NATO Staff Requirement, revised Mar 90 b. System, Functional and Performance: NATO Elementary Requirements Document, 12 Dec 94

Project Background (3/3) PD D&D MOU Start July 2002 SNC V9.5 (Jul 2009) SNC V9.6 (Jul 2011) MOU Amd 3 Ends Jan 2014 ISS Phase MOU Amd 4 (In Staffing) Slide 8 Oct 2012 2002 2009 2014

Slide 9 Project Milestones / Challenges 1. NILE In-Service Support (ISS) MOU Amd 4 a. NILE Project is governed by the NILE ISS MOU Amd 3 i. Amd 3 expires 1 Jan 2014 b. NILE Nations have agreed on content of MOU Amd 4 i. Amd 4 takes the project to 1 Jan 2020 ii. Expect formal staffing & signing to be completed by summer 2013 2. USN Link 22 Implementation Plans a. As of Feb 2012, USA has provided a Link 22 implementation plan b. Very positive step towards global interoperability 3. Third Party Sales (3PS) Process/ Procedures a. NILE Nations have agreed on the process after much discussion b. NILE 3PS Document was signed 4 Sep 2012 c. This permits future 3P Nation to begin discussions with NILE Nations 4. MLLC Procurement a. Moved from Proof of Concept (PoC) to Full Development (FD)

Slide 10 Link 22 Overview - Layered Architecture

Organization PM Mr. Manuel Gómez Deputy PM CDR Alessandro Capecchi (ITA Rep) UK Rep Mr. James Nuttall (75%) ESP Rep CDR Francisco Aznar Fernández-Montesinos FRA Rep TBD Slide 11 CAN Rep LCdr Peter Duffley DEU Rep LT Alexander Koschig Project Support Mr. Ron Bilbrey (Booz Allen & Hamilton)

Slide 12 Tasks (1/2) 1. Configuration control & management of the NILE Products: a. Software (SNC & NRS) b. Baseline product specifications & documentation 2. COMSEC development a. Ensuring integration / compatibility with NILE Products b. Management of COMSEC production 3. Modification of SNC SW and NRS SW to mitigate obsolescence and maintain interoperability 4. Investigation and development of improvements of the products of the NILE Project 5. Performance of necessary activities to support Link 22 interoperability in a multi-link environment

Slide 13 Tasks (2/2) 6. Investigation of deficiencies in the NILE system 7. Provision of software and hardware engineering services for problems which are common to all Participants relating to the NILE Products 8. Support and replacement, if necessary, of jointly acquired support equipment from any phase of the NILE Project 9. Joint acquisition of project equipment 10. Provision of items and services intended for the individual NILE Nation s support requirements for their national NILE systems

Slide 14 Coordinated Meetings 1. NILE Steering Committee (SC) a. Exercises executive-level oversight of the Project b. NILE Nations only; works on unanimous approval c. Meets 2 times per year 2. NILE Configuration Control Board (CCB) a. Technical body that executes the Configuration Control function for the SC b. NILE Nations only; works on unanimous approval c. Meets 2 times per year 3. Link 22 Communications and Interoperability Working Group (Link 22 C&IWG) a. A more open technical forum for Nations interested in Link 22 b. Includes various workshops c. Meets 1 or 2 times per year

Liaison with Link 22 Related Organizations Slide 15 1. Participation in: a. International Data Link Symposium (IDLS) b. NATO Tactical Data Links Capability Team (TDL CaT) i. Previously referred to as DLWG c. NATO TDL CaT Interoperability Testing Syndicate (ITS) i. Previously referred to as TDLITS d. NATO Line of Sight Capability Team (LOS CaT) i. Previously referred to as AHWG 2 (V(U)HF) e. Beyond Line of Sight WG (TBD) i. Previously referred to as AHWG 1 (BLOS)

Slide 16 NILE PROJECT STATUS

Link 22 Force Structure (1/5) 1. Most of the 7 NILE Nations are at various stages of implementation 2. National Implementation plans include the following platforms in all environments (air, land and sea): a. CV (Carriers) b. LHD, LHA, LPD c. Destroyers d. Frigates e. Submarines f. Aircraft (Helos / MPAs) g. Various shore sites Slide 17

Slide 18 Link 22 Force Structure (2/5) 3. NILE Nations Force Structure slide is approved by the NILE SC 4. The approval also gives the the authority to release this information to: a. NATO and NATO Nations b. C&IWG and IDLS 5. Force Structure slide for the NILE Nations follows

NILE Link 22 Force Structure Platform CAN DEU ESP FRA UK ITA USA CV 1 (2016) 2 QE Class Carrier LHD, LHA, LPD Destroyer Frigate 12 Halifax Class (2013-15) 4 F125 Class (2016 19) 2 LPD (2017) 1 LHD (2017) 5 F-100 Class (TBD) (2016-19) 1 Cavour (2010) 1 Garibaldi (TBD) 11 NIMITZ Class (2019-23) 3 (2014-15) 8 WASP Class (2019-23) 2 HORIZON Class (2014-15) 11 FREMM Class (2015-) 2 JEAN BART Class (2015-16) 5 La Fayette Class (2015-17) 6 Type 45 AAW (2016-19) 13 Type 23 (2016-19) Type 26(2020) 1 Mimbelli (2010) 1 DeLaPenne (2011) 2 Horizon Class (TBD) 6 FREMM Class (2013-17) 2 AMERICA Class (2020-23) 11 SAN ANTONIO Class (2019-23) 22 TICONDEROGA Class (2019-22) 65 A. BURKE Class (2019-23) 3 ZUMWALT Class (2021-23) Slide 19 Submarine Other Aircraft Shore Sites Helos (TBD) 1 Halifax 1 Greding 1 (Wilh.) 4 S80 Class(2016) 6 BAM ships (2017) 1 BAC ship (2017) Helos (TBD/TBC) 1 Madrid 1 Rota (2015) 6 BARRACUDA Class (2016-) Helos: NH-90 (2016-) Fixed Wing: MPA (ATL2) (2016-) E2C (2016-) 2 Toulon, Bruz 1 (Mobile) Helos: Wildcat(TBD) ) Fixed Wing: E3 Sentry (TBD) 1 Portsdown Helos (TBD): NH-90, EH-101 Fixed Wing (TBD): MPA (ATR72), MMA (Poseidon P-6) Note: Dates in the table represent Initial Operational Capability (IOC) and Final Operational Capability (FOC) 26 FREEDOM class (2020-23) 12 HAMILTON class (USCG) (2020-23) 8 LEGEND class (USCG) (2020-23) 1 Taranto 5 (Dahlgren (2), Wallops Island, Dam Neck, Moorestown) (2018)

Slide 20 Link 22 Force Structure (4/5) 6. created a Third Party (3P) Nation Force Structure slide in Jun 2010 that was approved by DNK, FIN, and NLD 7. This approval gave the the authority to release this information to: a. NATO and NATO Organizations b. NILE Nations and other 3P Nations c. C&IWG, IDLS, & DLWG 8. 3P Nations can update their information as required by contacting the 9. Will be reviewed at future C&IWGs 10. Force Structure slide for 3P Nations follows

Third Party (3P) Nation Link 22 Force Structure (Planned) Platform Plans to Implement DNK FIN NLD GRC, JPN, NOR, PRT, AUS, BEL, SWE, TUR Yes (2015) Yes (2012) Yes (2012) CV - - - - TBD LHD, LHA, LPD, FPB - 4 HAMINA-FPB (2015) 4 RAUMA FPB (2015) LPD1 (2015) LPD 2 (2015+) - Destroyer - - 4 ADCF (2015+) - Frigate IVER HUITFELT Class (3) (2015) - 2 M-FF (2012-13) - Submarine - - 4 Walrus (2013-18) - Other ABSALON Class (2) Thetis (1) 2 HÄMEENMAA cl (2015) 3 MCMV (2015) 4 Patrol Ship (2013-15) AOR (2012) JSS (2014) - Aircraft TBD TBD - Slide 21 Shore Sites TBD 2 MOC (2015) 1 Ref sys SSSB (2013) -

Slide 22 National Developments and Operational Testing (1/3) 1. As a project, much progress has been made towards implementation and multi-national cooperation a. Sharing of information by participating nations (NILE and 3PS Nations) is benefitting the community at large 2. As a system, Link 22 is at a stable level of maturity a. Is currently being implemented b. Field-tested in multi-national environments c. Initial Operational Capability (IOC) is achieved d. Many Nations and NATO organizations are discussing the strategy for the phasing in of Link 22 with implementing Nations

National Developments and Operational Testing (2/3) Slide 23 1. Multiple IDLS 2007 Demonstrations (Oct 2007) 2. FIN / DEU Ship / Shore Live Trial (Nov 2007) 3. FRA / DEU Industry Live Trial (Nov 2007) 4. SPC Conformance and Compatibility Testing (Dec 07- present) 5. FRA Deployed Ship / Shore Live Trial (May 08) 6. FRA / UK Link 22 Trial (Jun 08) 7. FRA / DEU Interoperability Testing (Sep 08) 8. ITA CV CAVOUR Implementation (Sep 08) 9. FRA / DEU / ESP Interoperability Tests (Mar 09) 10. DEU / FIN Long Distance Trial (Oct 09) 11. ITA Live Demo among operational Platforms using real DLPs and LLCs Target engaged (Nov 09) 12. Live demonstration at IDLS 2009 (Dec 09) 13. NC3A / FRA Link 22 Testing over SIMPLE (TDLITS) (Apr 10)

National Developments and Operational Testing (3/3) Slide 24 14. ESP tested real DLP over SIMPLE during Coalition Warrior I/O Exercise (Jun 10) 15. DEU sea trial in the North and Baltic Seas using the maritime version of the National NILE Basis System (NNBS) (Jul 10) 16. Collective training demo at IDLS 2010; L22 Data exchange demonstrated between multiple vendor DLPs (Sep 10) 17. Coalition Warrior I/O Demo (Jun 11) 18. Live demonstration at IDLS 2011 (Sep 11); Approx. 10 vendors involved 19. ESP completed DLP LINPRO trials for new Subs S-80 (Nov 11) 20. Link 22 Technical Demo with SWE / Technobit (May 11) 21. Technical Demo during AFCEA West 2012 conducted by DRS/SELEX/DIGINEXT (Jan 12) 22. Coalition Warrior I/O Demo (Jun 12) 23. UK Technology Demo. Back to Back Link 22 between Type 45 and Type 23 Combat Systems. (Jul 12)

Slide 25 COMSEC Update (1/2) 1. Production Contract for current Link Level COMSEC (LLC) expired 30 Sep 2011 a. A replacement COMSEC is under development 2. Modernized LLC (MLLC) contract was awarded to SafeNet on 28 Feb 2011 and involves the following: a. MLLC Proof of Concept (PoC) phase; completed Aug 2012 b. MLLC Full Development (FD) phase; awarded Aug 2012 i. Expected to take 18-24 months c. MLLC Production contract i. Planned for end of MLLC FD phase 3. MLLC is the only Link 22 COMSEC initiative supported by

Slide 26 COMSEC Update (2/2) 4. Key points a. MLLC will be developed by the USA, in conjunction with the NILE Nations: i. As a functional LLC replacement ii. To meet Air and Surface Requirements (multi-purpose) iii. With releasability to NILE and 3P Nations in mind iv. To satisfy US National Security Agency s (NSA) requirements b. Link 22 Nations (NILE & 3P) will be advised once Production Contract is in place i. Link 22 Nations will have to acquire via US Foreign Military Sales (FMS) ii. iii. iv. Case Procedure NILE and 3P Nations will only be able to order the MLLC after the Production Contract is in place FMS Case Letter of Offer and Acceptance (LOA) can not be approved by Navy IPO / FMS until this Production Contract vehicle is in place USA s national authorities will assess release of the MLLC in response to the FMS Letter of Request (LOR)

Slide 27 NILE Test Tools Overview NRS / MLST3 1. NRS and MLST3 are two separate test tools: a. NRS (NILE Reference System) is a NILE Product i. Considered a compatibility test tool ; tests SNC ii. iii. iv. Managed and distributed by the to the NILE Nations It is updated IAW NILE Project regulations NRS will be distributed to 3P Nations by one of the NILE Nations b. MLST3 is sponsored by US Navy and US joint services i. MLST3(Multi Link System Test and Training Tool ) is an I/O test tool (i.e DLP) ii. iii. iv. Managed by SSC Pac Code 591 and distributed outside US iaw US regulation It is updated iaw MLST3/SSC Pac regulations Although the L22 portions embedded in MLST3 were developed by the NILE Project, MLST3 is not considered a NILE Product 2. From a L22 perspective, NRS and MLST3 can be used as stand-alone or together

Slide 28 MLST3 and NRS in combination 1. Used in combination they provide a complete L22 Interoperability Test capability a. MLST3 reuses SW components offered by NRS NILE DLP-SNC IDD Implementation STANAG 5522 Implementation NRS

Slide 29 MLST3 Software Update 1. Current Baseline Link 22 implementation in MLST3: a. STANAG 5522 - Edition 1 + some DLCPs b. NILE Products - Block Cycle 2 (SNC v9.0) 2. It is not fully interoperable with most up-to-date Link 22 implementation 3. An update is necessary to be iaw the latest Link 22 baseline documentation 4. MLST3 will be updated in 2013: a. STANAG 5522 - Edition 4 + DLCP(s) b. NILE Products- Block Cycle 6 (SNC v9.7 to be released Jul 2013) c. Government Acceptance Testing (GAT) 5. This update will be available to all MLST3 Users

Slide 30 Third Party Sales Status / Procedures

Slide 31 Third Party Sales (3PS) Overview 1 1. Over the last 2 years, the NILE SC conducted a detailed review of the 3PS Process in parallel with MOU Amd 4 staffing 2. The NILE Nations agreed to a way forward and the 3PS Document was agreed and signed 4 Sep 2012 a. NILE Nations may now be able to process applications for the Request and/or Sale of NILE Products from 3P Nations b. 3P Nations may wish to approach specific NILE Nations to determine if or when they could support a request for the NILE Products

Slide 32 Third Party Sales (3PS) Overview 2 1. NILE SC confirmed that there are no longer any Approved Third Party Sales (3PS) Nations a. All 3P Nations will have to submit requests to a NILE Nation for the future sale / transfer of NILE Products 2. From a 3P Nation perspective, the envisioned 3PS Process has not changed significantly 3. NILE products and services can only be procured or transferred from one of the 7 NILE nations a. The NILE nations do not collaboratively enter into sales and/or transfer agreements 4. The key steps in the process are highlighted in the following slide

Third Party Sales (3PS) Overview Diagram Third Party (3P) Nation requests NILE Products via a Requesting NILE Nation (previously sponsor ) Requesting NILE Nation reviews the request & forwards to Requesting NILE Nation transfers NILE products to 3P Nation after payment of required levies and fees Requesting NILE Nation advises 3P of decision sends request to NILE SC NILE SC Reps advise NILE Nations / of decision *Decision of the NILE SC must be unanimous

Slide 34 Third Party Sales Acquiring Link 22 Capability 1. To acquire Link 22 capability, 3P nations will need: a. NILE SW (SNC and NRS) i. Via the Requesting NILE Nation b. NILE Project Core Documentation (including the Link 22 Guidebook) i. Via the Requesting NILE Nation c. COMSEC i. Via USA (FMS Case procedure) d. Other system elements (DLP, SPC and Radio; National responsibility) i. Acquired through one or more NILE Nation vendors ii. Develop their own using the NILE Specifications developed by the NILE Project in conjunction with the related STANAGs 2. Purchase of remaining System elements (DLP, SPC, Radio) is not subject to NILE Fees / Control a. NILE Interface Documentation is still required

Slide 35 Third Party Sales (3PS) Interim Process (until MLLC is available) 1. Until MLLC is available (2015/2016) the NILE SC agreed to allow the de-coupling of COMSEC and SNC a. That is, the SNC (and other NILE Products on the NILE BC DVD) can be released in advance of the MLLC being available 2. During this time, 3P Nations will need to: a. Find a NILE Nation to support their initial request for the sale and /or transfer of NILE Products (NILE BC DVD) b. Will need to pay levies for the required number of platforms to the Requesting NILE Nation or to the individual NILE Nations that require them c. Requesting NILE Nation, not the, is the Point of Contact (POC) for the 3P Nation d. CCB Representation and the processing of Feedback Reports (FRs) needs to be discussed with the Requesting NILE Nation

Slide 36 Third Party Sales (3PS) Future Process (after MLLC is available) 1. After the MLLC is available (2015/16) 3P Nations will need to: a. Find a NILE Nation to support their initial request for the sale and /or transfer of NILE Products (NILE BC DVD) or will need to staff an FMS Case for NILE BCR Updates b. Pay levies for the required number of platforms to the Requesting NILE Nation or to the individual NILE Nations that require them (if not previously paid in an initial request) c. Pay annual NILE BCR Fees for NILE BC Updates and processing of Feedback Reports (FRs) through USA FMS d. Liaise with the Requesting NILE Nation, not the, as the Point of Contact (POC) for the 3P Nation e. Account for NILE Configuration Control Board (CCB) Representation as an additional service under the FMS case

Nation DLP SNC CAN IBM Canada NILE Prod PMO Link 22 Support Vendors by Sub System Slide: 37 SPC Radio Test Integration Training Government Tools PoC COMSEC NILE Prod Telefunken Racoms (TFK) Lockheed Martin Canada-LMC Cdr Troy Richard troy.richard@ forces.gc.ca DEU Atlas Elektronik Telefunken Racoms (TFK) Rohde & Schwarz Hagenuk Marinekommunikation Atlas Elektronik Atlas Elektronik Mr Bodo Lükermann bodoluekermann@ bundeswehr.org ESP Tecnobit Evalink- 22 (ITM) Tecnobit Col Luis Beltrán lbeltal@oc.mde.es FRA Thales DCNS Rockwell- Collins France (RCF) Thales Rockwell-Collins France (RCF) Atos Origin DIGINEXT Atos Origin DIGINEXT Atos Origin DIGINEXT Mr. Michel Sandoz michel.sandoz@ dga.defense.gouv.fr ITA Selex SI DRS ICAS Selex Elsag Selex SI CAPT Francesco Marchetti francescoa.marchetti @marina.difesa.it UK IBM UK BAES IBM UK BAES 3SDL LM SyntheSys Mr David Hayles david.hayles994@ mod.uk US Mr. Paul Bobrowich paul.bobrowich@ navy.mil NILE PMO Northrop Grumman (NG) ViaSat Safenet NG NG NG Mr Manuel Gomez manuel.gomez@ navy.mil

Slide 38 Access to NILE Information

Slide 39 Link 22 Guidebook 1. The Link 22 Guidebook is available in 3 versions: a. Overview (Ch 1) - available in the Public Domain i. http://www.link22.org/link22ciwg.html b. Overview and Operations (Ch 1&2) - available to 3P Nations once an initial request for the NILE Products is approved by the NILE SC (and prior to the payment of fees) c. Complete Guidebook (Ch 1-3)- delivered with other NILE Products (SNC S/W etc.) after the payment of required Fees

Slide 40 Link 22 Customer Information Guide (CIG) 1. Now that the NILE Third Party Sales (3PS) Document was approved by the NILE SC (Sep 2012), work on the CIG can begin 2. CIG will provide an extensive and releasable overview of: a. Link 22 b. 3PS Procedures c. Entitlements / Fees d. Integration requirements e. NILE core software and documents

C&IWG Overview 1. Any Nation interested in acquiring or learning more about Link 22 and the NILE Project should consider joining the Link 22 C&IWG community Slide 41 2. Key Points to remember about the C&IWG: a. Attended by NATO and non-nato Nations b. Nations may attend once approved by the or the NILE SC c. To attend, Nations must have at least a government representative designated as the Head of Delegation (HoD) i. Each Nation should also designate a C&IWG DHoD d. HoDs/DHODs i. Must be either military or government civilians ii. May be supported, if required, by contractors

Slide 42 C&IWG Attendance Procedures 1. Any Nation can request attendance to the C&IWG through a NILE Nation or the, but there are different processes for approval: a. NATO Nations Government / NATO Organization i. Requests are typically approved automatically by the after verification of the requestor b. Non-NATO Nation s Government i. Request will be forwarded to the NILE SC for approval or denial ii. Notification of approval or denial will be communicated via the NILE PMO or the NILE Nation that received the request c. Contractor of a Nation not represented in the Link 22 C&IWG i. If the Nation is not yet represented by at least one Official Rep, the contractor s request will automatically be denied

Points of Contact (POC) Slide 43 1. POC for overall Project Management a. Mr. Manuel Gomez, NILE Project Manager b. manuel.gomez@navy.mil 2. POC for Third Party Sales a. LCDR Peter Duffley, CAN Representative b. NILE Third Party Sales Officer c. peter.duffley.ca@navy.mil 3. POC for Link 22 C&IWG Attendance a. LT Alexander Koschig, DEU Representative b. Alexander.koschig.gm@navy.mil SPAWAR PEOC4I PMW 150 4301 Pacific Highway San Diego, CA 92110 United States of America

Slide 44 QUESTIONS?