ATTACHMENT 01d - PTDL3_PWS.pdf

“Performance Work Statement”

N0003916R006, PTDL #03

Wideband HF/Independent Sideband Modulation Implementation

1 PURPOSE

1.0.0.1 This Performance Work Statement (PWS) establishes the requirements for the services that the Contractor shall provide to PMW 150 NATO Improved Link Eleven (NILE) Project Management Office (PMO). Specifically, the NILE PMO requires the provision of the services indicated herein in order to continue in the pursuit of the objectives of the In-Service Support phase of the NILE Project.

2 OBJECTIVES

2.0.0.1 The objective of this Technical Direction Letter (TDL) is to obtain professional engineering and software modification services to the PMW 150 NILE PMO. In particular, Block Cycles Updates, Software Patches, Engineering Support, and Project Management Services are needed. The set of requirements included in this PWS may be summarized in the continuous activities of modification, maintenance and configuration control of the NILE IT Products. The establishment of an effective project management structure to oversee execution of tasks as directed by this PWS and the supply of technical and subject-matter expertise on various Link 22 related matters is also required. The Contractor shall coordinate work undertaken in support of this PWS with work being accomplished under other CLINs and/or other TDLs, if any, so as to ensure that tasks are not being delayed or duplicated.

3 TECHNICAL DIRECTION AND REQUIREMENTS

3.0.0.1 Within the scope of the overarching Contract PWS, and under CLINs 0001/0002, the

Contractor shall fulfill the requirements of this TDL PWS, detailed as follows. The Contractor shall identity possible courses of action, via a White Paper (WP) and obtain approval via e-mail from the NILE PMO before implementing any solutions.

Specifically, the Contractor shall provide:

(a) A WP, as part of CDRL A006, that outlines a detailed analysis of options for the implementation of new Wideband HF within the NILE products. The WP shall discuss:

(i) The possibility of using wideband HF to increase the bandwidth of Link 22 transmissions, and

(ii) An assessment of the improved data rate using HF wideband modulation.

(b) A WP, as part of CDRL A006, that provides a detailed analysis of options for the implementation of Independent Single Sideband (SSB) Modulation within the NILE products. The WP shall discuss:

(i) The possibility of using lower and upper sideband (LSB and USB) modulation to transmit different data on each sideband; and

(ii) An assessment of the improved data rate using LSB and USB modulation compared to transmitting the same data on both sidebands.

(c) For (a) and (b) above, the Contractor shall:

(i) Identify and propose the necessary changes to the:

a) DLP-SNC interface,

b) LLC Interface Requirement Specification,

c) MLST3 (from a system perspective),

d) NRS,

e) SNC, and

f) SPC (Contractor to provide any necessary changes for interface compliance. Implementation will be a national responsibility).

(ii) Provide a recommended approach based upon a trade-off assessment regarding impacts on the overall Link 22 system, including SPCs and MLST3, and cost effectiveness of implementation.

(iii) Identify, if any, system and operational planning procedures to be modified and propose the consequent amendments.

(iv) Identify if NILE (and related NATO) documentation requires updating as a result of implementing this solution, such as the Link 22 Guidebook, IRSs, IDDs, SDDs, SSs, SRSs, STMs, SSs, STDs, ATDLP-7.33, ATDLP-5.22, ATDLP-6.16 and ATDLP-6.02.

(v) Provide a brief estimate of the scope of changes (description and cost estimate) to each document covered by the ISS contract.

3.1 NILE IT BLOCK CYCLE UPDATE

3.1.0.1 The Contractor shall deliver an IT Block Cycle Update in accordance to a subset of the requirements identified in Contract PWS paragraph 5.1.1.

3.1.0.2 The IT Block Cycle Update shall include, as a minimum, the following :

(a) SNC and NRS software to include all the source and executable files, command files and data files for the SNC (CDRL A010) and NRS (CDRL A015) in accordance with Contract paragraph 5.1.1.2, including completion of LLC 7M system integration as described in paragraph 5.1.2.1.4.

(b) Updated Technical Data Package (TDP) (CDRL A011) in accordance with Contract PWS paragraph 5.1.1.3, including:

(i) Updated System Technical Manual of the SNC and NRS in accordance with Contract PWS paragraph 5.1.1.3.1.

(ii) Updated Link 22 Guidebook in accordance with Contract paragraph 5.1.1.4.

(c) Updated Test Documentation in accordance with the requirement of Contract PWS paragraph 5.1.1.5, including:

(i) Software Test Description for the SNC and NRS (CDRL A007 and A012) in accordance with Contract PWS paragraph 5.1.1.5.1.

(ii) Software Test Report for the SNC and NRS (CDRL A008 and A013) in accordance with Contract PWS paragraph 5.1.1.5.1.

(d) Software Version Descriptions for the SNC and NRS (CDRL A009 and A014) in accordance with the requirements of Contract PWS Paragraph 5.1.1.2.

(e) The Configuration Management Information System (CMIS) (CDRL A004), Technical Documentation including WP, FR, PCR, CP etc. (CDRL A006) and CCRB Meeting Minutes (CDRL A005) in accordance with Contract PWS paragraph 5.1.3.11.3.

3.1.1 Software Enhancements

3.1.1.1 In accordance with Contract PWS paragraph 5.1.1.2, and Appendix C, the Contractor shall analyze, design and obtain NILE PMO approval via e-mail or at an IPT/IPR before implementing and testing solutions for the following Software Enhancements (in order of priority):

(a) Wideband HF, and

(b) Independent Sideband Modulation

3.1.1.2 Additionally, the Contractor shall continually assess, analyze and rectify SNC IA vulnerabilities as described in paragraph 3.2.0.4.

3.1.1.3 All items shall be fully tested and documented within 12 months of contract award.

3.1.2 Software and Documentation Baseline

3.1.2.1 The Contractor shall maintain a Software and Document Repository in accordance with Contract PWS paragraphs 5.1.2.1.8 and 5.1.3.11.3.1. This Repository shall:

(a) Include the current and previous Block Cycles (BCs) Packages, and

(b) Include a working baseline for the next BC.

3.1.2.2 Where the Contractor implements Software Modifications (either as a result of a PCR or Software Enhancement), the Contractor shall:

(a) Incorporate these modifications into the working baseline for the next formal BC in accordance with the requirement of Contract PWS paragraph 5.1.1,

(b) Update, as necessary, NILE documentation affected by the implemented software changes. This shall include all documents released as part of the TDP (CDRL A011) in accordance with Contract PWS paragraph 5.1.1.3 and 5.1.1.4,

(c) Update the System Test Description (STD) documents for the SNC and NRS (CDRL A007 and A012) to reflect the Software modifications, and

(d) Conduct Computer Software Unit (CSU) Testing, Computer Software Configuration Item (CSCI) Integration Testing and System Integration Testing to ensure the Software modifications perform as expected.

These tests shall include regression testing to ensure implementation of Software modifications do not adversely affect other functions.

3.1.2.3 Prior to release of the IT Block Cycle Update required by paragraphs 3.0.0.1, 3.1.0.1 and 3.1.0.2, the Contractor shall ensure the Testing Requirements of Contract PWS Paragraph 5.1.1.5 are met. This shall include CSCI and System Qualification Testing and delivery of Software Test Report for the SNC and NRS (CDRL A008 and A013).

3.2 PROJECT MANAGEMENT SERVICES

3.2.0.1 The Contractor, throughout the Period of Performance (PoP), shall provide the following Project Management Services:

(a) Project Structure as described in the Contract PWS paragraph 5.1.3.1;

(b) Project Planning and Control as described in the Contract PWS paragraph

5.1.3.2. The Government may request a formal assessment of schedule and cost at any time

(c) Monthly Status Reports (MSR) as described in the Contract PWS paragraph

5.1.3.3 (A002). The Contractor shall deliver a logically networked Integrated Master Schedule (IMS) in Microsoft Project 2010 (or later). The IMS 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.

(d) Electronic Data Bases and Management Tools as described in the Contract PWS paragraph 5.1.3.4;

(e) Project Reviews as described in the Contract PWS paragraph 5.1.3.5;

(f) A Post Award Conference, IPRs and IPTs as described in the Contract PWS paragraphs 5.1.3.5, 5.1.3.6 and 5.1.3.7;

(g) Project Risk Management as described in the Contract PWS paragraph 5.1.3.8;

(h) Project Security Management as described in the Contract PWS paragraph 5.1.3.10;

(i) Project Configuration Management as described in the Contract PWS paragraph 5.1.3.11 and 5.1.2.1.8 (SW Repository);

(j) Integrated Support as described in the Contract PWS paragraph 5.1.3.12;

(k) Project Quality Assurance as described in the Contract PWS paragraph 5.1.3.13, and

(l) All deliverables required within the above mentioned Contract PWS paragraphs (CDRLs A001, A002, A004, A005 and A006) are due during the PoP of this TDL as specified on their respective CDRLs.

4 ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

4.0.0.1 The Contractor shall maintain proprietary data protection agreements with other companies to the extent that their proprietary data is made available to the Contractor.

5 PERIOD OF PERFORMANCE (PoP)

5.0.0.1 The PoP shall be twelve (12) months, from contract award.