ATTACHMENT 01a_NILE ISS4 PWS.pdf

ATTACHMENT 1

PERFORMANCE WORK STATEMENT

FOR

NATO IMPROVED LINK ELEVEN (NILE)

IN-SERVICE SUPPORT (ISS) PHASE

BLOCK CYCLE UPDATES AND

ENGINEERING/MANAGEMENT SERVICES

Prepared by: NILE Project Management Office (PMO)

20 November 2017

DISTRIBUTION STATEMENT A: Approved for public release, distribution is unlimited (20

NOVEMBER 2017)

REVISION HISTORY

Version Reason for Change Date

TABLE OF CONTENTS

Title

1. SCOPE

1.1 Introduction

2. BACKGROUND

3. OBJECTIVES

4. APPLICABLE DOCUMENTS

4.1 Specifications

4.2 Standards

4.3 NILE Documents

4.4 NATO Standards and Documents (latest edition)

4.5 Other documents

5. PERFORMANCE REQUIREMENTS

5.1 Block Cycle Updates and Engineering/Project Management Services for NILE IT Systems (CLINs

X001/X004)

5.1.1 NILE BLOCK CYCLE UPDATES (CLIN X001: NILE Nations’ funds, O&MN, FMS)

5.1.2 ENGINEERING SERVICES (CLIN X001/X004)

5.1.3 PROJECT MANAGEMENT SERVICES (CLIN X001, X004: NILE Nations’ funds, O&MN, FMS) ... 28

5.2 OTHER DIRECT COSTS (CLIN X002/X005/X006: NILE Nations’ funds, O&MN, FMS)

5.2.1 Incidental Materials (X002/X005)

5.2.2 Travel (X002/X005)

5.2.3 Other Hardware for the NILE Compatibility Laboratory (X006: NILE Nations’ funds, O&MN, FMS).. 40

5.2.4 Radios for the NILE Compatibility Laboratory (X007: NILE Nations’ funds, O&MN, FMS

5.2.5 Procedures for advance approval of Other Direct Costs (ODC)

5.3 DATA – CDRLs (CLIN X003) Not Separately Priced (NSP)

5.4 SECURITY (X001/X004)

5.5 Enterprise-wide Contractor Manpower Reporting Application (ECMRA) (X001/X004)

APPENDIX A - SOFTWARE MODIFICATION PROCESS – BLOCK CYCLE 10 AND FOLLOWING

BLOCK CYCLES

APPENDIX B - LIST OF ACRONYMS

APPENDIX C - WORK PACKAGE DESCRIPTION (NILE NATIONS’ FUNDS, O&MN)

1. PROBLEM CHANGE REPORTS (PCRS) AND ANY ADDITIONAL PROBLEM REPORTS

1.1 Problem description

2. ITEM #101 (FORMERLY REGISTERED AS #05) – SIMPLE PROTOCOL IMPLEMENTATION

IN THE SNC AND NRS

2.1 Problem description

2.2 Requirement

3. ITEM #102 (FORMERLY REGISTERED AS #06) – RECORD SIMPLE IN THE SG DX

3.1 Problem description

3.2 Requirement

4. ITEM #103 (FORMERLY REGISTERED AS #07) – NETWORK MONITORING AND

MANAGEMENT DECISION SUPPORT/AUTOMATION

4.1 Problem description

4.2 Requirement

5. ITEM #104 (FORMERLY REGISTERED AS #27 - 64 BIT TIME IMPACTS

5.1 Problem description

5.2 Requirement

6. ITEM #105 (FORMERLY REGISTERED AS #34) – LINK 22 TRAINING DEVELOPMENT

6.1 Problem description:

6.2 Requirement

7. ITEM #106 (FORMERLY REGISTERED AS #35) – NILE INFORMATION ASSURANCE (IA) 53

7.1 Problem description:

7.2 Requirement

8. ITEM #107 (FORMERLY REGISTERED AS #43) – NILE DOCUMENTATION UPDATE

8.1 Problem description:

8.2 Requirement

9. ITEM #48 – EXPAND NRS TO ALLOW 8 NILE NETWORKS

9.1 Problem description

9.2 Requirement

10. ITEM #33 – NRS REMOVAL OF SUPPORT FOR BREAKOUT

10.1 Problem description:

10.2 Requirement

10.3 Reference material

11. ITEM #45 – CONGESTION STUDY

11.1 Problem description

11.2 Requirement

12. ITEM #23 - SCENARIO GENERATOR (SG) ENHANCEMENTS

12.1 PROBLEM DESCRIPTION

12.2 Requirement

13. ITEM #46 – UHF EPM SPC SS INTEROPERABILITY TEST AND SUPPORT

13.1 Problem description

13.2 Requirement

APPENDIX D - REFERENCE DOCUMENTATION AND PRODUCT MAINTENANCE

RESPONSIBILITY REGISTER

1. INTRODUCTION

2. DOCUMENTATION LIST

2.1 Link-22 System, SNC and NRS related documents

1. SCOPE

1.1 Introduction

The Space and Naval Warfare Systems Command (SPAWAR), in support of the Program

Executive Office Command, Control, Communications, Computers, and Intelligence (PEO

C4I), Navy Command and Control Program Office (PMW 150), is initiating a follow-on

In-Service Support (ISS) contract on behalf of the North Atlantic Treaty Organization

(NATO) Improved Link Eleven (NILE) Nations.

This In-Service Support Performance Work Statement (PWS) establishes the requirements for the continued Modification, Maintenance, and Configuration Control of the NILE

Products including: the System Network Controller (SNC) software, the NILE Reference

System (NRS) test tool, the NILE Compatibility Laboratory, and associated documentation.

The contract covers SNC/NRS enhancements due to the implementation of potential new system capabilities such as new waveforms, wideband HF, independent sideband modulation or improved resistance to jamming. Assessments regarding the impact of NILE Product software changes (executed under the provisions of this contract) on the Multi-Link System

Test and Training Tool1 (MLST3) will also be required. Engineering and project management services will also form part of this contract.

2. BACKGROUND

During the late 1980s, NATO, agreeing on the need to improve the performance of Link

Eleven (Link 11), produced a Mission Need Statement (MNS) that became the basis for the establishment of the NILE Project.

The NILE Project was initially developed collaboratively by seven nations under the aegis of a Memorandum of Understanding (MoU). The original seven nations were Canada (CAN), France (FRA), Germany (DEU), Italy (ITA), the Netherlands (NLD), the United Kingdom

(UK) and the United States of America (USA). Spain (ESP) replaced the Netherlands in

2003. The current seven nations are hereinafter referred to as the “NILE Nations”.

1 MLST3 will be provided to the ISS contractor as GFE.

This multi-nationally funded project is guided by a Steering Committee (SC) consisting of a representative appointed by each NILE Nation. The project is managed by the NILE Project

Management Office (NILE PMO), located at PEO C4I, PMW 150.

The NILE PMO consists of one representative from each NILE Nation and a Project Manager

(PM) who is appointed by the United States Department of the Navy and endorsed by the

NILE Steering Committee (NILE SC).

The configuration control function is exercised, on behalf of the SC, by a Configuration

Control Board (CCB). The CCB is composed of a representative of each NILE Nation and is chaired by the NILE PM.

NILE has been designated Link 22 by NATO. Link 22 is a standard for wireless and secure information interchange between military units. Link 22 provides improved High Frequency

(HF) and Ultra High Frequency (UHF) radio communications of tactical data. Link 22 offers a more robust terrestrial Beyond Line of Sight (BLOS) Waveform than Link 11. It also provides better Real Time Tactical access compared to Satellite Communications, and improves Allied Interoperability through a Common Design. Link 22 offers a BLOS tactical data link that is designed to fully complement its Link 16 Line of Sight (LOS) counterpart, without the complex planning, monitoring and network management overhead.

As the project progresses through each life cycle phase, each phase demands a new amendment to the MoU. A summary of the project’s life cycle history is as follows:

Project Definition Nov 87 – Jun 92 (Completed)

Design and Development Subphase 1 Jul 92 – Jun 97 (Completed)

Design and Development Subphase 2 Jul 97 – Jun 02 (Completed)

In-Service Support Phase (Amd 1-4) Jul 02 – Jan 20 (On-going)

The primary objective of Subphase 1 of the Design and Development (D&D) Phase of the

NILE Project was to design a system consisting of a computer-to-computer, digital data link among Tactical Data System (TDS) equipped platforms, in order to meet the NATO Staff

Requirement for NILE. An additional NILE objective of the D&D Phase was to develop common specifications and project information sufficient to enable the participating nations to develop Link 22 systems which will be interoperable and compatible with those of other nations.

The objective of Subphase 2 of the Design & Development Phase was to design, develop, build, and test a SNC, a NRS and the Link 22 element of MLST32 that met the requirements of the specifications referenced herein, and to develop sufficient technical data to enable each

NILE Nation to utilize and maintain the SNC, NRS and MLST3, as part of their national

Link 22 implementation programs.

The SNC provides common operational software that is compatible among the seven current

NILE Nations. The NRS is a test tool, which enables compatibility testing of Link 22 implementations by the participating nations.

The Link 22 system uses the LINK-22 Modernized Link Level COMSEC (LLC 7M) device to provide communication security services at the link level. This cryptographic equipment also provides time-of-day (TOD) based encryption and decryption services for network messages sent over multiple NILE transmission networks.

3. OBJECTIVES

The overall objectives of the ISS phase are to provide in-service support for, maintain commonality of, and pursue modifications resulting from user inputs for the NILE Products and to ensure integration of the SNC and the LLC 7M. The NILE Products include the SNC, NRS, and associated documentation. This PWS defines the scope of efforts required from the

Contractor in support of achievement of the NILE ISS phase objectives.

The Contractor shall provide the following services:

a. The Contractor shall provide Link 22 system expertise to the developer/manufacturer of the LLC 7M, in order to integrate the COMSEC into the Link 22 architecture. This effort may include, where necessary, changes to the SNC/NRS and its interfaces. The Contractor shall closely collaborate with the LLC 7M manufacturer to ensure the design and implementation of the system meets requirements.

2 MLST3 is not a NILE Product, it is under configuration control of SPAWAR SSC Pacific Code 591

b. The Contractor shall assess the impact on the Link 22 system when implementing enhancements such as additional Radio Frequency (RF) Waveforms, Wideband

HF, Independent Sideband modulation or improved resistance to jamming; and, if approved, the Contractor shall implement them.

c. NILE Software Block Cycle Updates, covering:

As specified on a Technical Direction Letter (TDL), the Contractor shall provide analysis and design of items as identified and listed, but not limited to, in

Appendix C, implementation of the recommended solutions, approved by the

NILE PMO, determined during the period of performance, and, as a recurring effort for each contractual year, correction items.

The result of the combined analysis, design, and implementation activities will result in an updated product baseline, labeled “Block Cycle”. The contactor shall maintain Configuration Management (CM) of each Block Cycle Release (BCR).

Delivery of electronic copies of updated NILE Products and execution of formal software (SW) acceptance tests may be required every one or two contractual years.

d. Engineering Services, covering:

The Contractor shall provide system engineering, investigative, technical and maintenance support services for tasks as outlined in this PWS on Link 22-related matters as specified on a TDL by the NILE PMO or by a specific NILE

Nation in support of its Link 22 implementation effort. Examples of engineering support might be:

Execute interoperability tests between Link 22 system devices developed by different vendors and evaluate the results;

Provide expertise to the NILE PMO or to the Government committed to maintain proper system level integration and compatibility throughout future modifications to the LLC 7M.

e. Project Management Services, covering:

The Contractor shall establish an effective project management structure to oversee execution of tasks directed by this PWS and to provide life cycle support and configuration management of the NILE Products delivered.

Throughout this PWS, unless specified otherwise, the term “SNC” implicitly encompasses all existing SNC variants. Similarly, the term “NRS” implicitly encompasses the Scenario

Generator (SG) Computer Software Configuration Item (CSCI), and the Media Simulator

(MS) CSCI as defined in documentation listed in Appendix D – Paragraph 2.1.

Throughout this PWS, the terms "Contractor" and “ISS Contractor” refer to the Contractor selected for evolving and maintaining the NILE Products during this ISS contract. The term

"Government" refers to the United States Government (encompassing the NILE PMO and the

NILE Nations). The term “MLST3-ISEA” refers to the In-Service Engineering Agent-entity

(SSC Pacific Code 591) contracted for supporting the overall MLST3 maintenance activities, which are outside of the scope of this PWS. The following Figure 1 provides a high level identification of the areas of the ISS Contractor responsibilities.

Figure 1: High-Level Identification of support and Test Equipment required for organizational-level maintenance items

Prior to and following any changes implemented on the SNC and NRS segment, the

Contractor shall evaluate and provide an assessment of the impact on the MLST3 Link 22 components.

The Contractor shall analyze, design, implement, integrate and test the required modifications to produce an updated version of the SNC and/or NRS in accordance with the objectives defined in this paragraph.

The contractor shall validate software modifications in the NRS, and shall deliver the validated modifications to the Government as an incremental version from the baseline version. Implementation of the SNC version is a national decision; Link 22 nations may choose to implement sometime after a Block Cycle delivery.

GOV’T

ISS-Contractor Maintenance of:

-SNC segment -NRS System including SG/SGEX/SNCd/MS CSCIs Documentation

NILE Compatibility Laboratory:

NRS system capability + MLST3 Representative

NILE

CCBs

MLST3-ISEA

Maintenance Center in San Diego, CA Maintenance of:

MLST3 components and MLST3 SNCd/MS CSCIs qualification testing

MLST3 Test Equipment Suite:

NRS and MLST3 system capability

The Contractor shall generate sufficient technical data to enable each participating nation to maintain the SNC and NRS, as part of their national NILE, or Link 22 implementation program.

The Contractor shall support these objectives using the Model Based Systems Engineering

(MBSE) process. MBSE is a process used to provide System of Systems decisional information to Navy acquisition throughout the entire engineering lifecycle.

4. APPLICABLE DOCUMENTS

The following documents are provided as applicable references. As these documents are subject to update, the Contractor shall adhere to the most current version, as required.

4.1 Specifications

The baseline documents are specified in Appendix D – Paragraph 2.

4.2 Standards

MIL-HDBK-61A (SE) Configuration Management Guidance, February 2001

STANAG 4107 Mutual Acceptance of Government Quality Assurance Edition 8, 6 July 2007

MIL-STD-882E DEPARTMENT OF DEFENSE Standard Practice for System

Safety, 11 May 2012

ANSI/EIA 649B Configuration Management Requirements for Defense Contracts, 20 November 2014

NATO SDIP-29 Installation of Electrical Equipment for the Processing of

Classified Information, Jan 2006

4.3 NILE Documents

NILE PMP NILE Program Management Plan

NILE CMP NILE Configuration Management Plan

WP (#3) Network independent SG EX

WP (#20) DR Time Tag selection

WP (#21) DR Filters enhancement

WP (#25) Link 22 Diagnostics

WP (#36) NMU's SN Dir update of DTDMA Flag

WP (#42) Modernized LLC (MLLC) Migration

WP (#43) HF FF Extension, System Impact Analysis

WP (#44) LNE Silent Join Enhancements Analysis

WP (#45) Non Backward Compatible Release Updates

WP (#46) Repetition of Messages based on own LRQ

WP (#47) Re-Initialization and Reconfiguration Protocol Improvements

(SNC NCS)

WP (#48) Adding NUs Online

WP (#49) Merge of Multiple DX Files

WP (#50) Windows 8 Compatibility Assessment

WP (#51) NRS Expansion to use 6 UUTs

WP (#52) DA Enhancements - Minimize Manual Checks During Testing

WP (#53) DA Expected Responses Not Matched Improvements

WP (#54) Network Monitoring and Management Decision Support

WP (#55) Unnecessary messages in LNE protocol

WP (#56) DA Enhancements - DA Performance Analysis

WP (#57) NRS Default File Locations

WP (#58) Automated Test System

WP (#59) Timeslot Space Utilization and Padding

WP (#60) MWF – Analysis of SNC-SPC Message fields

WP (#61) 64 Bit Time Impacts

WP (#62) New Waveforms, Handling Future New Waveforms

WP (#63) NILE Compiler Software Upgrade

WP (#64) Information Assurance Report

WP (#65) HF FF Management Waveform (MWF)

WP (#66) Windows 10 NRS and SNC

WP (#67) OLM Checksum Implementation

WP (#68) DLP-SNC Message Improvements

WP (#69) LNE Related DLP-SNC Message Improvements

WP (#70) HF FF Management Waveform (MWF) Analysis Simpler Solution

WP (#71) Red Hat Linux 7 SNC Compatibility

WP (#72) LNE NCS Timeslot Size Calculation Analysis

4.4 NATO Standards and Documents (latest edition)

STANAG 4203 Technical standards for single channel radio equipment

STANAG 4205 Technical standard for single channel UHF radio equipment

STANAG 4285 Characteristics of 1200/2400/3600 bits per second single tone modulators demodulators for HF radio links

STANAG 4372 SATURN – A fast frequency hopping ECCM mode for UHF radio

STANAG 4430 Precise time and frequency interface and its management for military electronic systems

STANAG 4444 Technical standards for a slow hop HF EPM Communications system

STANAG 4539 Technical standards for non-hopping HF communication waveforms

ATDLP-5.16 TACTICAL DATA EXCHANGE - LINK 16

ATDLP-5.22 TACTICAL DATA EXCHANGE - LINK 22

ATDLP-6.02 STANDARD INTERFACE FOR MULTIPLE PLATFORM LINK

EVALUATION (SIMPLE)

ATDLP-6.16 Tactical Data Forwarding

ATDLP-7.33 Multi-Link Standard Operating Procedures for Tactical Data

Systems Employing Link 11, Link 11B, Link 16, IJMS and Link

ADatP–3 NATO MESSAGE TEXT FORMATTING SYSTEM

(FORMETS) – CONCEPT OF FORMETS (CONFORMETS)

APP–11 NATO MESSAGE CATALOGUE

4.5 Other documents

DFARS SUBPART Security and Privacy for Computer Systems dtd 21 Sep 15

5239.71

DoDI 8500.01 DoD Instruction – Cybersecurity dtd 14 Mar 14

DoDD 8140.01 DoD Directive –Cyberspace Workforce Management dtd 11 Aug

DoD 8570.01-M Information Assurance Workforce Improvement Program dtd 19

Dec 05 with Change 4 dtd 10 Nov 15

SECNAVINST 5239.20A DON Cyberspace Information Technology and Cybersecurity

Workforce Management and Qualification dtd Jun 16

SECNAV M-5239.2 DON Cyberspace Information Technology and Cybersecurity

Workforce Management and Qualification Manual dtd Jun 16

DON CIO Memo Acceptable Use of Department of the Navy Information

Technology (IT) dtd 12 Feb 16

Navy Telecoms System Authorization Access Request (SAAR) - Navy

Directive (NTD 10-11)

SECNAVINST 5239.3B DON Information Assurance Policy, 17 Jun 09

ISO 9001:2015 Quality Management Systems – Requirements, 23 September 2015

ISO 10007:2017 Quality Management-Guidelines for Configuration Management , ISO/IEC 8652 Information technology, programming languages – Ada, 28 March

2013, with COR.1, 01 February 2016

IEEE/EIA 12207 Industry Implementation of International Standard ISO/IEC 12207

– 2008 (ISO/IEC 12207) Standard for Information Technology –

Software Life Cycle Process, 31 Jan 08

007-500028-001 LLC 7M Installation, Configuration, and Operation Instructions, Revision C, Apr 2016

PI-L22D-RM-03 LINK-22 Modernized Link Level COMSEC (MLLC)

System/Subsystem Specification

SPAWARINST 3058.1 Naval SYSCOM Risk Management Policy, 07 April 2008

SPAWARINST 5234.1A Naval Warfare Systems Certification Policy, 24 August 2012

PI-L22D-DP-10 Key and Certificate Management Plan (KCMP)

007-500028-001 LLC 7M Installation, Configuration and Operation Instructions

(includes Outline and Mounting Drawings)

LLC 7M Outline Solid Model (PDF/STEP format)

PI-L22D-TP-41 TEMPEST Test Evaluation Report

PI-L22D-TP-31 Environmental Test Report

DoD 5220.22-M National Industrial Security Program Operating Manual dtd 18

May 16

5. PERFORMANCE REQUIREMENTS

During the period of performance of the contract, and when tasked by TDLs, the Contractor shall provide services according to the following specific requirements. TDLs will provide specific information relating to the tasks contained in this PWS and will be provided to the

Contractor in writing.

5.1 Block Cycle Updates and Engineering/Project Management Services for NILE

IT Systems (CLINs X001/X004)

5.1.1 NILE BLOCK CYCLE UPDATES (CLIN X001: NILE Nations’ funds, O&MN, FMS)

The Contractor shall be responsible for the following tasks:

a. Conducting technical and support analyses and designing of SNC and NRS modifications and issue resolution as assigned by the Government;

b. Identifying change requirements and recommending change proposals;

c. Coding, integrating and testing changes when approval to proceed to implementation has been received from the NILE PMO;

d. Updating NILE documentation to reflect software changes. Updates shall be approved through the Configuration Management Change Proposal process as detailed in Section 5.1.3.11 of the PWS;

e. Providing an impact assessment on the MLST3 CSCIs (prior to performing any code changes) in sufficient detail to enable the Government to contract for the relevant changes on the MLST3 CSCIs with the MLST3 ISEA;

f. Providing updated relevant baseline documentation, and the SNC, MS, and NRS executable code as a minimum, to the MLST3 ISEA upon approval of code changes with MLST3 impact;

g. Analyzing deficiencies identified within the SNC and NRS software versions;

h. Investigating possible deficiencies in the NILE Products as they are reported by individual NILE Nations, or other Link 22 Nations, in the course of their national

Link 22 system integration (to the extent that such items or services do not adversely impact NILE Products or compatibility or interoperability among the

Link 22 systems of the Nations);

i. Tracking software/hardware obsolescence and maintaining interoperability among all identified platforms;

j. Mitigating software/hardware obsolescence and maintaining interoperability among all identified platforms.

k. Performing modification, implementation and validation of test cases to demonstrate the modified functionality, making full use of existing SNC and NRS

CSCI and System Qualification Test procedures and scenarios.

Appendix C defines possible work packages currently identified for the entire contract period although emergent in-scope tasks may be added. Each Block Cycle shall contain a combination of analysis, design, implementation and engineering tasks. The detailed content of the potential follow-on Block Cycles will be defined through a TDL.

The Software Modification Process approach for Block Cycle Ten and following is illustrated in Appendix A Figure 1. The Contractor shall deliver a new release of the documentation in

Appendix D and of the SW CSCIs (both source and executable) upon completion of each

Block Cycle as specified on a TDL.

Whenever analysis and design proposals are required, the Contractor shall provide White

Papers (WP) to allow an interactive dialogue with the Government, to identify possible courses of action before any solutions are implemented. When existing functionality is removed, the Contractor shall maintain a history of the deleted or modified lines of code, relative to the baseline software. The Contractor shall amend the software design documentation to describe the “sidelining” of the existing functionality. Following approval from the NILE PMO, the Contractor shall amend the specification documentation to reflect the modified baseline requirements, deleting existing functionality requirements as necessary.

The CM process (as per paragraph 5.1.3.11) shall maintain the old versions of documentation

(CDRL A004).

Any changes to the SNC, which result in an updated version of the software, shall be backwards compatible with the last SNC major version (e.g., 10.x, or 11.x) unless directed by the NILE PMO in a TDL.

Additionally, the Contractor shall provide technical support, analysis, and design activities necessary to support current and evolving Link 22 interfaces and specifications including

COMSEC, Signal Processing Controllers (SPC), and Radios. These activities shall be performed as specified on a TDL and with reference to the waveforms presently used by the

Link 22 system, as well as to potential new waveforms (CDRL A011).

5.1.1.1 Generic Software Development Approach

The SNC has been developed in a single software environment, Intel Pentium and Windows

XP, and then modified to function under the Red Hat Linux 7 and Windows 10 software, using an Intel platform. In the future, the Contractor may be tasked to analyze, document and implement solutions that will allow the NRS and SNC to be installed on other operating systems and other platforms (in addition to the Intel platform). Details about the actual baseline Software Development Plan (SDP) are provided in the existing NILE Program

Management Plan (PMP) for the NILE ISS Phase, available for reference. Any modification of software shall meet the requirements specified in Paragraph 5.1. The Contractor shall modify software using the mandated computer platform types to meet the requirements outlined in this PWS. The Contractor shall identify in the PMP (CDRL A001) those software management indicators to be used, and shall collect, interpret, apply, and report (CDRL

A006) on those indicators which provide a quantitative measurement of schedule and progress, quality, and technical adequacy of software modification.

5.1.1.1.1 Software Language Requirements

The Contractor shall perform the SNC/SNCd software modifications using Ada 95, as defined by ANSI/ISO/IEC 8652:1995. The software modifications to the NRS CSCIs shall be performed using C++. The Government reserves the right to evaluate/approve more advantageous programming languages during contract performance.

5.1.1.1.2 Processing Capacity

The Contractor shall estimate the modified SNC and NRS processing capacity using appropriate peak throughput scenarios. The estimated spare processor capacity shall be presented to the NILE PMO, and then verified during system qualification testing of final delivered software.

5.1.1.1.3 Memory Capacity

The revised memory capacity and utilization for each Central Processing Unit (CPU) shall be also estimated. Measurements of memory capacity and utilization for each CPU shall be verified during system qualification testing.

5.1.1.1.4 Software Version Identification

The Software Version identification is provided in Section H of the RFP.

5.1.1.2 SNC and NRS System/Segment Design change

The Contractor shall perform engineering design studies to define the modified design, configuration, and performance characteristics of the SNC and NRS software, in accordance with the requirements of the current Segment Specifications and the list of specified functional modifications in Appendix C. The design shall be carried out to a level of detail such that the necessary modified segment components (including computer resources) and their functional characteristics are identified; the external and major internal hardware and software interfaces are characterized as to function; the physical layout of the segment is described, and feasibility, cost effectiveness, and reproducibility of the design are verified. If the documents specified at Appendix D need to be modified, change pages shall be provided via a Change Proposal (CP). Design changes resulting from modifications shall be documented through Contractor procedures/processes and delivered as part of CDRL A011.

Updates to the current SNC Software Design Description (SDD) shall be provided upon modification of the SNC. The Contractor shall deliver Software Version Description (SVD) documents: one for the SNC and one for the NRS (CDRLs A009 and A014) to control and track the software release.

When specified on a TDL, the Contractor shall deliver all the Source and Executable

Software, including any batch files, command files, data files or other software files needed to regenerate the executable software and to install and operate the software on its target computer: one for the SNC and one for the NRS (CDRLs A010 and A015).

5.1.1.3 Technical Data Package (TDP)

To maintain Configuration Management, the Contractor shall generate and maintain a TDP

(CDRL A011) which details all information and requirements pertaining to the upgrade, testing, installation, training, and support for the SNC and NRS. As specified on a TDL, an updated TDP shall be delivered upon completion of each Block Cycle. The TDP shall constitute a complete design disclosure of the SNC and NRS necessary for the Government to build an identical system via a third party. The TDP shall include engineering design documentation baseline (Appendix D Paragraph 2.1) specifications, product drawings and associated lists, special tooling and test equipment drawings and associated lists, technical manuals, Commercial Off The Shelf (COTS) manuals, source and object code listings, software documentation, test plans and procedures, installation drawings, support documentation, and configuration changes. COTS manuals shall consist of only the information that is normally supplied by the vendor. The TDP shall not include any classified COMSEC/TEMPEST information or requirements. The TDP shall exactly represent the as-built configurations of the modified SNC and NRS that successfully completed Block Cycle Testing.

5.1.1.3.1 System Technical Manual

The Contractor shall deliver a SNC and NRS System Technical Manual documents (STMs)

(CDRL A011) that reference the executable software, source files, and software support information, including build design information and compilation, and modification procedures for a CSCI. The Contractor shall provide appropriate update pages to the SNC and NRS system level technical manuals according to SNC and NRS implemented changes.

5.1.1.4 Link 22 Guidebook

The Link 22 Guidebook includes both high-level and detailed descriptions of all components of the Link 22 system and their modes of operation and key features. This guidebook provides suitable information for Link 22 operators, planners, managers, developers, and testers. The intent of the document is to provide both an introduction for new users, as well as a detailed reference for established users. The Link 22 Guidebook shall be updated and released (CDRL A011) in three different versions that have specific distribution procedures:

a. "Link 22 GUIDEBOOK" (COMPLETE GUIDEBOOK); for NILE Nations, their approved contractors / industry suppliers & Contributing 3PS Nations only;

b. "Link 22 GUIDEBOOK - OVERVIEW AND OPERATIONS" (includes Chapters

1 & 2, Appendices A, B, E, F & G, and the Index); for NILE Nations, their approved contractors/industry suppliers, Contributing 3PS Nations and approved

3PS Nations only;

c. "Link 22 GUIDEBOOK - OVERVIEW" (includes Chapter 1 and Appendices A, E, F & G); for nations that have requested a copy and been approved by the NILE

PM.

The Contractor shall provide configuration control of the Link 22 Guidebook in the same manner required for documents listed in Appendix D - Paragraph 2.1.

5.1.1.5 Contractor Conducted Test and Evaluation

5.1.1.5.1 Test and Evaluation Program

The Contractor shall conduct software testing following the guidance of IEEE/EIA 12207 as specified in Paragraph 4.5. The Contractor shall deliver two Software Test Description

(STD) documents: one each for the SNC and NRS (CDRLs A007 and A012). The STDs shall encompass both CSCI and System Qualification Testing. Existing CSCI and System

Qualifications tests, which are reused, shall be incorporated into the revised STDs. The

Contractor shall conduct a sequence of testing that follows the testing phases of Computer

Software Unit (CSU) testing, CSCI Integration testing, System Integration testing, and

System Qualification testing and shall deliver two Software Test Report (STR) documents:

one for the SNC and one for the NRS (CDRLs A008 and A013).

5.1.1.5.2 General Rules for Testing

The following general rules shall apply for all formal verification activities:

a. All Contractor conducted testing shall be performed following Government approved plans and procedures (STDs). Unlike CSCI and System Qualification

Test (SQT) phases, where the Government is witnessing all test activities, test witnessing by Government representatives is not required during CSU and

Software Integration Test phases, but shall be allowed and shall be at the discretion of the Government. The Contractor shall notify the Contracting Officer’s

Representative (COR) of testing dates at least 30 calendar days in advance. The

Government will notify the Contractor of intent to witness individual tests. The

Contractor shall notify the Government at least five (5) business days in advance whenever the start of any testing will be delayed and shall concurrently notify the

Government of the new start date;

b. The Contractor shall prepare and submit STRs of testing activity results (CDRLs

A008 and A013). Two documents shall be delivered after CSCI tests: one for the

SNC and one for the NRS, noting that the Scenario Generator and Media Simulator

CSCIs are incorporated into the NRS. The test reports shall include soft copy versions (.pdf) of the completed Acceptance Test Procedures. They shall provide evidence that the tests were conducted, the results that were obtained, and bear the signatures of the personnel who conducted or witnessed the tests;

c. The Contractor shall conduct retests of previously completed testing for which correction of a deficiency or any other modification affects the results of those previously completed tests. The selection of requirements for retesting is a joint

Contractor and Government decision, with the Government having the final authority.

5.1.1.5.3 Testing Requirements

The Contractor shall perform all necessary testing phases including Computer Software Unit

(CSU) testing, CSCI Integration testing, System Integration testing, and System Qualification testing to demonstrate to the Government that each individual CSCI and the overall SNC and

NRS Systems meet the new requirements derived from the item list in Appendix C and requirement items identified in the course of the contract.

The table below presents the possible sequence of events within a specific development phase. Item (A) represents SNC CSCI and NRS CSCIs, while item (B) represents MLST3

Link 22 related CSCIs, and (I) represents the ISS Contractor.

Reviews Informal

TRR

Formal CSCI

Acceptance

Formal TRR

Test

Phases

CSCI

Dry-Run

Testing

CSCI

Qualifi-cation

Testing

CSCI /

HWCI

Integration

& Test +

System Dry-

Run

System

Quali-fication

Testing

Items (A)+(B) (A)+(B) (A)+(B) (A)+(B) (A) (A) (A)

Respon-sible

(I) (I) (I) (I) (I) (I) (I)

MLST3

CSCIs impact assessment delivered to

Gov’t

Figure 2: Test phases with major milestones. Key: Item (A) represents SNC CSCI and NRS CSCIs, (B) represents MLST3 Link 22 related CSCIs, and (I) represents the ISS Contractor.

5.1.1.5.4 Test Readiness Review (TRR)

As specified on a TDL, a TRR shall be scheduled, for each BCR, prior to the conduct of both

“formal” CSCI and SQT. The Contractor shall call for a TRR when confident that the amended software, test scenarios and test procedures are complete and ready to be conducted.

The purpose of the TRR is for the Contractor to present enough evidence to allow the

Government to authorize to proceed to the next phase of testing. The following considerations shall be addressed:

a. Requirements Issues and Changes;

b. Acceptance (Block Cycle) Test Procedures, and Scenarios;

c. Software Test Resources and Tools;

d. Hardware and Support Environment;

e. Configuration Management and Software Quality Assurance;

f. Test Team;

g. Recommended Tests to Conduct for Formal CSCI/System Testing;

h. Known Software Problems;

i. Test Schedule.

As shown at Paragraph 5.1.1.5.3 – Figure 2, the CSCI TRR shall also address the impact on the MLST3 CSCIs (i.e. SNCd, MS). The impact statement shall be given by the Contractor to the Government for subsequent forwarding to the MLST3-ISEA for integration into the

MLST3. The Contractor shall prepare and submit minutes of the TRR (CDRL A005).

5.1.1.5.5 Personnel Requirements

The Contractor shall ensure the availability of personnel with Information Assurance qualifications. As a minimum, the Contractor’s PM shall be GSCL (SANS) certified and the

Lead Engineer shall be CISSP (ISC2) certified. Equivalent certifications, if approved by the

Government, are also acceptable. Certified personnel should be directly involved in the execution of item #108.

5.1.2 ENGINEERING SERVICES (CLIN X001/X004)

5.1.2.1 Engineering Services for the NILE PMO (CLIN X001: NILE Nations’ funds, O&MN, FMS)

The Contractor shall provide technical/engineering services to the NILE PMO with respect to tasks related to Appendix C Items and Link 22 System Engineering elements.

5.1.2.1.1 Analysis of System Issues and Enhancement Proposals

The Contractor shall provide SME to assist the NILE PMO in the resolution of system issues and bug fixes. These services shall include:

a. Feedback Reports (FR) assessment and response: record all incoming FRs and analyze them for technical feasibility, validity, including schedule and cost impacts as specified on a TDL. The Contractor shall recommend a resolution;

b. Support on all issues and questions related to the four different media types (HF

FF, HF EPM, UHF FF and UHF EPM), including testing and documentation changes;

c. Problem verification, reporting, tracking and resolution, using the NILE PMO designated tools and procedures;

d. Incorporation of hardware and software updates by retrofit.

5.1.2.1.2 Planning and execution of integration and field testing

As specified on a TDL, the Contractor shall provide Subject Matter Expertise to assist the

NILE PMO in the preparation and execution of testing of all the systems which encompass the Link 22 architecture to be held either at the Contractor facility or Government sites.

These services shall include developing Test Plans and Test Procedures (CDRL A003) for assessing conformance and compatibility/interoperability of devices designed by Third

Parties for the Link 22 System, including Radios, SPCs and DLPs. Conformance means compliance to the relevant specification and suitability in the overall Link 22 system environment. Compatibility/interoperability is the condition among communications-electronics systems or items of communications-electronics equipment where information or services can be exchanged directly and satisfactorily between them and/or their users. At test completion the Contractor shall also provide detailed Test Reports (CDRL A003) of the activity performed, and the technical analysis and evaluation of the results.

5.1.2.1.3 Training

The Contractor shall provide tailored training sessions for NILE Nations or any nation purchasing Link 22 services via Foreign Military Sales (FMS) either at the Contractor's site, or a worldwide location as designated by the Government. The training will be provided to familiarize national participants and their national contractors with the Link 22 system, including system operational aspects, operation and use of the SNC, NRS, supporting ancillary equipment, and documentation. The Contractor shall provide options for either user-focused training or train-the-trainer training. The Contractor shall provide fully editable training material along with the training course.

5.1.2.1.4 LLC 7M System Integration

As specified on a TDL, the Contractor shall be required to ensure continued compatibility between the LLC 7M and the NILE Products to support the NILE PMO in assessing the system level aspects of the LLC 7M. This shall involve supporting future modifications to

COMSEC requirements definition, analysis, integration, and testing. This may include, but is not limited to providing continued System-Level Engineering support to the NILE PMO regarding the LLC 7M. The support may include:

Review of COMSEC updates proposed by the LLC 7M developer/manufacturer and provision of recommendations to the NILE PMO regarding the proposed updates;

Independent Verification and Validation (IV&V) of the LLC 7M to evaluate the adequacy and completeness of the LLC 7M, ensuring that it conforms to

Link 22 system requirements (excluding requirements relating to the encryption/decryption algorithm);

Assessments and/or recommendations on the impact/viability of the vendor or authority proposals that may affect the Link 22 System;

Answering specific technical questions from the NILE PMO relating to the review of system level CDRLs submitted to PEO C4I regarding the LLC 7M.

Answers to such questions shall ensure engineering feasibility and compatibility to the Link 22 System;

Test and analyze COMSEC units reported as ‘not faulty’.

5.1.2.1.5 Services Provided for International Forums

As specified on a TDL, the Contractor shall support the NILE PMO at the following types of international forums, providing subject matter expertise and input on technical issues

(including NILE White Papers and Presentation Material), arrangements and conduct of:

a. The NILE Steering Committee;

b. The NILE Configuration Control Board (NILE CCB);

c. The Link 22 Communications and Interoperability Working Group (Link 22

C&IWG);

d. The Interoperability Testing being conducted between NILE Nations and/or contributing Third Party Nations;

e. Other meetings or workshops on Link 22 or TDL related matters providing material for easing the update of ATDLP-5.22 and other standards used for Link 22

System design.

5.1.2.1.6 NILE Website

As specified on a TDL, the Contractor shall maintain/enhance the Link 22 Website, publishing content identified by the NILE PMO.

5.1.2.1.7 NILE Test Environment/Compatibility Laboratory

The Contractor shall provide and maintain a test environment/compatibility laboratory suitable for the development and maintenance of the NILE Products, and for compatibility/IV&V testing with Link 22 equipment, irrespective of the manufacturer. For testing of some requirements (e.g. IV&V testing of LLC 7Ms that are not yet converted to a

Controlled Cryptographic Item), the Contractor shall identify and implement appropriate procedures necessary to test up to and including U.S. SECRET/NATO SECRET. General support, including NRS/SNC infrastructure and OS support, shall be part of the implementation of the Integrated Support Plan (ISP) as defined in section 5.1.3.12 of this

PWS.

The Contractor shall set-up and maintain a NILE Compatibility Laboratory at the

Contractor’s site. The Contractor shall ensure availability of the following capabilities:

a. Two operational NRS environments (current and previous Block Cycle) shall be maintained for the duration of the contract. Software will be provided as

Government Furnished Equipment (GFE);

b. An operational MLST3 environment shall be maintained for the duration of the contract. Software shall be provided as GFE;

c. Availability of personnel trained in the operation of the NRS components, SNC, SNCd, interfaces, ancillary equipment (e.g. TOD card) and MLST3.

The Contractor shall recommend and provide any general purpose and special purpose electronic test equipment required for the operation and maintenance of the SNC, NRS and laboratory hardware, including GFP items specified in the contract.

The Contractor shall conduct an ongoing analysis of software and hardware obsolescence issues. These issues shall be reported to the Government as they arise.

When new hardware is procured under this contract, the Contractor shall recommend only hardware that can be maintained and repaired via service organizations with facilities located in each NILE participating Nation, to the extent such hardware is available. An exception to this applies to the procurement of a commercial development configuration. The Contractor shall deliver all information about procured or modified hardware to the Government IAW

MIL-PFR 49506 specified at paragraph 4.2.(CDRL A003).

5.1.2.1.8 Software Repository

The Contractor shall maintain all software files, updates, revisions, and upgrades under configuration control. The Government retains the right to monitor and review, via the

Integrated Product Team (IPT) process, all software information maintained by the

Contractor. The Contractor shall provide a final release at formal delivery for all software modified or purchased under this contract.

5.1.2.2 NATION-SPECIFIC Support (CLIN X004: NILE Nations’ funds, O&MN, FMS)

The Contractor shall provide technical/engineering services to any requiring NILE Nation, or any nation purchasing Link 22 services via FMS, and their national contractors, with respect to any Link 22 system engineering matter. These services shall include:

b. Assistance with LLC 7M integration;

c. Operation of national NRS components, SNC, SNCd, interfaces and ancillary equipment (e.g. TOD card) on Intel based computer platforms;

d. Analysis and evaluation of national SNC and NRS integration test results;

e. Tailored training sessions to familiarize national participants with the Link 22 system, including system operational aspects, operation and use of the SNC, NRS, supporting ancillary equipment, and/or documentation. The Contractor shall provide options for either user-focused training or train-the-trainer training.

The Contractor shall provide fully editable training material along with the training course.

5.1.3 PROJECT MANAGEMENT SERVICES (CLIN X001, X004: NILE Nations’ funds, O&MN, FMS)

5.1.3.1 Project Structure

The Contractor shall establish and maintain an effective project management structure to oversee execution of tasks directed by this PWS. The Contractor shall designate a single

Program Manager (PM) who shall have overall responsibility for control and coordination of all work performed. This PM shall act as the single focal point within the Contractor’s activity for all required project status information. The Contractor shall provide an open channel of communication, both via phone and email, during PMO working hours. The

Contractor shall maintain current knowledge to support the system engineering tasks. The

Contractor shall provide identification of issues and problems with the specifications, implementations and overall Link 22 system to enable the Government to achieve efficient, effective and interoperable Link 22 systems.

The Contractor shall not proceed with changes to the baseline software without USG approval. The Contractor shall provide NILE PMO access to Contractor facilities upon request. Contractor shall have a facility within the greater San Diego area (or be able to secure a facility within 90 days of award).

Within 30 days from the beginning of each contractual year, the Contractor shall generate a one page summary (format to be agreed with the NILE PMO) for each task included within the TDL for that contractual year. The summary shall include, but not be limited to i) any changes required to external interfaces ii) whether implementation of a task would result in a non-backwards compatible version of the SNC, iii) a basic schedule showing analysis and implementation (separately) and iv) the estimated effort for analysis and implementation

(separately). For each task, the Contractor shall obtain approval via e-mail from the NILE

PMO before implementing any solutions. Throughout the year, if it becomes apparent that the details contained within any of the one-page summaries requires updating, the Contractor shall immediately notify the NILE PMO and provide an updated summary.

5.1.3.2 Project Planning and Control

The Contractor shall identify, plan, organize, direct, coordinate, and control activities necessary to accomplish overall contract requirements. The Contractor shall establish a formal organization responsible for accomplishing the tasks outlined in this PWS. The

Contractor shall ensure that all plans and procedures required by this PWS and CDRLs approved by the Government, are adhered to by the Contractor and all sub-contractors, if any.

A clear line of project authority shall exist between all organizational elements and the PM.

This shall be communicated to the COR within 7 days of any updates or changes.

The Contractor shall document, in a tailored Program Management Plan (PMP) (CDRL

A001), management (and associated organizational chart), cost, engineering, logistics, and software development plans. This single document shall include a Contract Work

Breakdown Structure (CWBS) which represents how the Contractor plans to accomplish the entire contract work scope, consistent with the Contractor’s internal organizations and processes. The CWBS will serve as the framework for contract planning, budgeting, and reporting of cost and schedule status to the Government.

The Contractor’s Project Manager shall be the primary authority who will interface with the

NILE PMO and, as directed by the NILE PMO and in accordance with the PWS, with the other entities participating in the NILE ISS phase including:

a. The Governmental Configuration Management forums (CCB, etc.);

b. The Governmental entity responsible for implementing MLST3 system evolution

(i.e. SSC Pacific Code 591);

c. NATO and NILE working groups;

d. National Link 22 segment integrators, as contracted by the NILE Nations and other

Link 22 Nations, when required.

5.1.3.3 Monthly Status Report (MSR)

The Contractor shall provide, on a monthly basis, a report (CDRL A002) detailing the schedule of events and the integrated cost and schedule status of work progress on the contract. The schedule will consist of a logically networked schedule in Microsoft Project

2010 (or later). The schedule shall reflect the tasks, dates (baseline, forecast, and actual), external and internal dependences and relationships necessary to support accurate forecasts of contract milestone delivery dates by both the contractor and the Government. The report shall be prepared for planning work, controlling costs, and generating timely, reliable and valuable information for the Government. Supporting schedules detailing the sub-events required to achieve milestones in the schedule shall also be prepared and maintained.

Changes to the schedule shall be highlighted, with reasons for the changes. The Contractor shall address the effect of the changes on interrelated milestones. The Contractor shall also relate technical accomplishment with cost and schedule accomplishment. The MSR shall be also briefed and discussed at any In Process Reviews (IPRs).

5.1.3.4 Electronic Databases and Management Tools

The Contractor shall manage data generated as part of the contract in databases or with specific data management tools. Data shall be maintained in the following formats:

Microsoft WORD for text and tables, Microsoft ACCESS for databases, Microsoft EXCEL for spreadsheets, Microsoft PROJECT for project…