ATTACHMENT 01b -PTDL1_PWS.pdf

“Performance Work Statement”

N0003918R0006, PTDL #01

NILE Software/Hardware Maintenance, Systems Engineering and NILE Configuration/Data Management

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, 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. The Contractor shall coordinate work done 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 or a one page summary if a White Paper is not required, and obtain approval via e-mail from the NILE PMO before implementing any solutions. Specifically the Contractor shall provide:

(a) IT Block Cycle Update activity according to the guidance provided in the Contract PWS paragraph 5.1.1.

(b) A subset of Engineering Services as described in the Contract PWS paragraph 5.1.2.1 and in particular LLC 7M system integration described in the Contract PWS paragraph 5.1.2.1.4. External dependencies may affect GFE availability.

(c) A subset of Project Management Services as described in the Contract PWS paragraph 5.1.3.

3.1 TASK A – 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.

(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 Defects

3.1.1.1 In accordance with Contract PWS paragraph 5.1.1.2 and Appendix C Section 1, the

Contractor shall identify and fix defects in the software code.

3.1.1.2 For each defect identified, the Contractor shall submit a Problem Change Report (PCR) in accordance with the requirement of Contract PWS Appendix A.

(a) PCRs may be submitted as a result of issues submitted by nations in Feedback Reports (FRs) or as a result of the Contractors Engineering Support and Software Modification activities, including LLC 7M system integration.

(b) Prioritization and selection of PCRs to be implemented during the Period of Performance (PoP) shall be managed in accordance with the requirements of Contract PWS paragraph 5.1.3.11 (Configuration Management).

3.1.1.3 The Contractor shall analyze, design, implement and test the solution to PCRs in accordance with requirements of Contract PWS Appendix C Section 1.

(a) The Contractor shall implement solutions for up to 10 PCRs to be completed before the end of the PoP.

3.1.2 Software Enhancements

3.1.2.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) Item #48 Expand NRS to 8 NILE Networks shall be completed within 6 months of contract award

(b) Item #33 NRS removal of support for break-out box shall be completed within 6 months of contract award

(c) Item #45 Congestion Study shall be completed within 6 months of contract award

(d) Item #23 Scenario Generator (SG) Enhancements shall be completed within 12 months of contract award

(e) Item #46 UHF EPM SPC SS Interoperability Test and Support shall be completed within 12 months of contract award

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

3.1.2.3 All items shall be fully tested and documented by 31 Jul 2019.

3.1.3 Software and Documentation Baseline

3.1.3.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.

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

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

(a) Incorporate those 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.

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

(i) This shall include regression testing to ensure implementation of Software modifications do not adversely affect other functions.

3.1.3.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 TASK B – ENGINEERING SERVICES

3.2.0.1 The Contractor, throughout the PoP, shall provide:

(a) Analysis and resolution of all Feedback Reports (FRs) and other technical issues the NILE Nations may raise. Such an activity shall be executed in accordance with the Contract PWS paragraph 5.1.2.1.1. Based on historical data/information, the Contractor shall plan for an average rate of 1 FR/month to be addressed;

(b) Technical and Subject Matter Expertise (SME) in support to the PMO attending international meetings/forums as specified at Contract PWS paragraph 5.1.2.1.5. The Contractor shall support and attend, with at least one ISS team member, the following meetings:

(i) NILE CCB and Link 22 C&IWG in Italy (December 2018);

(ii) NILE CCB and Link 22 C&IWG in Canada (May 2019).

(iii) TDL CaT Subgroup meeting.

(iv) 2 LLC 7M in El Segundo (CA)

(c) Maintain the NILE Test Environment/Lab as described in the Contract PWS paragraph 5.1.2.1.7;

3.2.0.2 In accordance with Contract PWS Paragraph 5.1.2.1.4, the Contractor shall support the NILE PMO in assessing the system level aspects of the LLC 7M Integration effort, specifically with regard the integration and testing of the LLC 7M within the NILE Products.

3.2.0.3 The Contractor shall assess the impact/viability of proposals that may affect the System, answering specific technical questions as raised.

3.2.0.4 The Contractor shall continually assure the SNC’s compliance with IA requirements as described in Item #35 (Appendix C) of the Contract PWS. In accordance with Contract PWS paragraph 36 and WP#64, the Contractor shall execute periodic CodePeer1 assessments of the SNC source code and present the NILE PMO with a list of the high and medium vulnerabilities identified. Once the agreed list of vulnerabilities to be corrected is approved by the NILE PMO, the Contractor shall raise and implement PCRs, in accordance with 3.1.1.2, to rectify the issues.

3.3 TASK C – PROJECT MANAGEMENT SERVICES

3.3.0.1 The Contractor, throughout all the 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.

(i) Formal assessment of schedule and cost as requested by the Government.

(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.

1 Ada source code analyzer

(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;

(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.