Performance Work Statement.pdf

NAVAL AIR WARFARE CENTER AIRCRAFT DIVISION

Integrated Network Enhanced Telemetry Program

1 SCOPE

The Naval Air Warfare Center - Aircraft Division (NAWC-AD) NAS Patuxent River, Maryland requires contractor support for the maturation of the Telemetry Network Standard (TmNS) based system being developed by the integrated Network Enhanced Telemetry (iNET) program from its current state through deployment of Early Operational Capability (EOC) and Initial Operational Capability (IOC). The Ranges will further mature to the Fully Operational Capability (FOC) with program support.

The support required for this Performance Work Statement (PWS) entails software development, software maintenance, provision of a iNET System Integration Laboratory (iSIL) facility, integration and testing, test authoring and conduct within the iSIL, training, and support for maintenance of the TmNS standards in IRIG 106 published by the Range Commanders’ Council.

1.1 Task Orders

The objectives and requirements identified within this Performance Work Statement (PWS) are described in general terms. Each task order will address specific task requirements, project scheduling, and other related performance criteria as necessary. Tasking under this contract requires the contractor to provide all phases of planning, development, engineering, design, procurement, testing, training, operation, and maintenance, as identified herein, in support of the iNET program.

2 APPLICABLE DOCUMENTS

The documents listed in this section represent the documentation required for accomplishing the work described in this PWS. These documents are available for download via the following link https://www.tena- sda.org/display/INET/Home.

2.1 INET Program Documents

2.1.1 System Documents

1. Telemetry Network System Specification

2. Telemetry Network System Design Document

2.1.2 Component Development Specifications

1. Camera Manager Component Development Specification

2. Data Acquisition Unit Component Development Specification

3. Link Manager Component Development Specification

4. Mission Control System Component Development Specification

5. Multi-Function Display Component Development Specification

6. Network Data Recorder Component Development Specification

7. Network Encryptor Component Development Specification

8. Network Gateway Component Development Specification

9. Network Router Component Development Specification

10. Network Switch Component Development Specification

11. Pulse Code Modulation (PCM) Gateway Component Development Specification

12. Real-Time Telemetry Processing System Component Development Specification

13. Test Article Manager Component Development Specification

14. TmNS Article Radio Component Development Specification

15. TmNS System Manager Component Development Specification

16. Voice Gateway Component Development Specification

17. Video Gateway Component Development Specification

2.1.3 Software Development Applications

1. Link Manager Software Requirements Specification

2. Mission Control System Software Requirements Specification

3. Real-Time Telemetry Processing System Software Requirements Specification

4. TmNS Data Server Software Requirements Specification

5. TmNS System Manager Software Requirements Specification

2.2 Range Commander’s Council (RCC) TmNS Standards

1. IRIG 106 Chapter 21: Telemetry Network Standard Introduction

2. IRIG 106 Chapter 22: Network-Based Protocol Suite

3. IRIG 106 Chapter 23: Metadata Configuration

4. IRIG 106 Chapter 24: Message Formats

5. IRIG 106 Chapter 25: Management Resources

6. IRIG 106 Chapter 26: TmNS Data Message Transfer Protocol

7. IRIG 106 Chapter 27: Radio Frequency Network Access Layer

8. IRIG 106 Chapter 28: Radio Frequency Network Management

2.3 INCOSE Documents

1. System Requirements Review (SRR)

2. Preliminary Design Review (PDR)

3. Critical Design Review (CDR)

4. Test Readiness Review (TRR)

2.4 Security Documents

1. DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) 28 Feb

2. DoDD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective 28 Apr

3. DoD 5400.7-R, Freedom of Information Program Chapter 3, Sep 1998

4. DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI))

Vol. 4, 24 Feb 2012

5. National Security Decision Directive (NSDD) 298

6. OPNAVINST 3440.17A Navy Installation Emergency Management Program, 1 Aug Department of Defense (DoD) Contract Security Classification Specification

7. SECNAV M-5510.36 Information Security Program, 30 Jun 2006

8. SECNAV M-5510.30 Personnel Security Program, Jun 2006

3 GENERAL REQUIREMENTS

The section applies to all task orders issued under this contract.

3.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible with the current Government IT operating environment. The current Government IT operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Office Professional Plus 2016 Microsoft Project 2010 Microsoft Visio 2010 Adobe Acrobat XI (Reader)

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall ensure that all media are malware free when delivered. The Contractor shall be capable of Internet and LAN communications with the iNET Program Office. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the iNET Program Office during working hours whether at Contractor work site or on travel.

3.2 Work Location and Facilities

3.2.1 Work Location

The vast majority of the work is expected to be performed at the Contractors site while less than ten percent of the work will be performed at Government sites. Government site(s) include:

• NAVAIR sites such as Patuxent River Maryland, China Lake California, Point Mugu California;

• Air Force Test Center sites such as Edwards AFB California and Eglin AFB Florida; and

• Army sites such as White Sands New Mexico and Redstone Alabama.

3.2.2 Meeting and Conference Room Support

In support of the tasking outlined in this PWS, the Contractor shall have the capability to host, conduct, locate and secure conference room facilities for conducting meetings at the classification levels up to the Secret level. The conference room should hold a minimum of 20 persons and have VTC capability (non- GFE). The conference room shall contain sufficient equipment to conduct meetings with presentations.

Therefore, the facility shall have projectors and/or TV displays, computer(s) with compatible software as required in Paragraph 3.1, and telephone(s) to meet the minimum requirements. This support shall be provided at the contractor’s facility.

3.3 Work Breakdown Structure

The Contractor shall establish a Work Breakdown Structure (WBS) for all work proposed under this PWS. The WBS shall be established in detail to the third level identifying the project tasks, schedule for each task, performance metrics, project milestones, deliverfables, and other efforts required to achieve the objectives of the project. The WBS shall be delivered with the Contractors proposal.

3.4 Contract Status Reporting

The Contractor shall provide a Periodic Status Report (PSR) in accordance with Contract Data Requirements List (CDRL) A001. The PSR shall be in electronic form in an agreed to format and delivered to the Government. The PSR shall be a stand-alone deliverable that addresses the WBS concerning performance, schedule, and cost against the agreed established baseline to the third level WBS, including deliverable status. The Contractor shall also provide an accumulative project summary of accomplishments, identify tasks accomplished for the reporting period, identify tasks planned for the upcoming month, explain corrective actions for maintaining baseline, and provide forecast relative to the completion of the work identified in this PWS.

3.5 Risk Assessment

The Contractor shall identify, forecast, track, and report project risks that affect technical performance, cost, and schedule for the work identified in this PWS. For each risk higher than low, the Contractor shall provide a risk mitigation plan to be included in the PSR (CDRL A001). The project risks shall be reported at technical interchange meetings, design reviews, and as a part of the PSR.

3.6 Technical Interchange Meetings

The Contractor shall organize and conduct Technical Interchange Meetings (TIM)’s that are estimated to take place once a month on average to discuss issues and status concerning tasks identified this PWS.

This includes topics such as requirements, specifications, standards, development, integration, and testing efforts or other topics of importance to the iNET program. These meeting will be conducted at the Contractors site and at times via Telephone Conferences or Web Conferencing. The Contractor shall provide meeting minutes in accordance with CDRL A002.

3.7 Subcontractors

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS shall flow down to subcontractors providing support under this contract.

3.8 Management of Contractor Personnel

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services.

3.9 Security

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information and to control distribution of controlled unclassified and classified information in accordance with the National Industrial Security Program Operating Manual (NISPOM) and DoDM 5200.01, Information Security Manual. The DoD Contract Security Classification Specification, DD Form 254, Attachment 1, defines program specific security requirements.

3.9.1 Contract Security Classification Specification

The contractor shall comply with security requirements specified in the DD-254 attached to this contract.

Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only”. Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC of this contract for approval.

3.9.2 Security Clearances

In general, the work required under this PWS is unclassified. However, Information Assurance (IA) measures and access to information regarding Communications Security (COMSEC) is required to ensure the requirements for satisfying interoperability and performance requirements are met. Additional information regarding COMSEC is included in the DD254. Designated personnel shall require Secret clearances for access.

3.9.3 Citizenship Requirements

Only U.S. citizens may perform under this contract, unless waived. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.9.3.1 Access to Government Facilities

The Contractor needs to be aware that Government facilities restrict access of foreign nationals and must be taken into consideration in order to fulfill the requirements of this PWS.

3.9.4 Information Security

If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and CUI and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and SECNAV M-5510.36. If the work is performed at the Government’s facility, the Contractor shall comply with instructions/guidance required by that facility.

CUI is defined and governed by laws, international agreements, Executive Orders, and regulations that address the identification, marking, protection, handling, transmission, transportation, and destruction. A category of CUI includes For Official Use Only (FOUO) information. FOUO is a designation used by DoD to identify information or material which may not be appropriate for public release. FOUO information may be disseminated within DoD components and between officials of DoD components and DoD contractors, consultants, and grantees as necessary in the conduct of official business only with permission of the government activity. FOUO information may also be released to officials in other departments and agencies of the executive and judicial branches in performance of a valid Government function only with permission of the government activity.

3.9.4.1 Marking

All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01.

Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance.

3.9.4.2 Public Release

No information pertaining to this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the appropriate U.S. government authority. Proposed public releases shall be submitted to the TPOC for initial approval and awareness. Upon initial approval, the contractor shall submit proposed public releases for approval prior to release through the NAWCAD Public Affairs Office via nawcadinfo@navy.mil, 301-757-2211, 22449 Saufley Rd., Building 1354, Patuxent River, MD 20670 or as described for specific programs in the contract DD-254.

3.9.4.3 Information Handling

All instances of loss, compromise, and electronic spillage of classified or CUI shall be reported to the TPOC and Government Security Office within 24 hours of the incident occurring.

3.9.5 Operations Security Program

The Contractor shall develop, implement, and maintain an Operations Security (OPSEC) Program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The OPSEC Program shall document the IA and COMSEC provisions. The OPSEC Program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

• Assignment of responsibility for OPSEC direction and implementation.

• Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

• Establishment of OPSEC education and awareness training.

• Provisions for management, annual review, and evaluation of OPSEC programs.

• Flow down of OPSEC requirements to subcontractors when applicable.

The Contractor’s established OPSEC Program developed under contract N00421-10-C-0010, is still applicable, and shall be maintained and revised throughout performance of this contract. The Contractor shall prepare and submit a revised OPSEC Plan based on this PWS and in accordance with CDRL A017.

3.9.5.1 Facilities

The Contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, equipment, and materials in accordance with OPSEC requirements.

4 SOFTWARE APPLICATIONS (CLIN 0001)

The Contractor shall provide support for the design, development, testing, integration, demonstration, training, maintenance, and operations of the System Manager and Link Manager applications for the Telemetry Network Standard (TmNS) based system. These applications will be utilized during integration and testing activities as described elsewhere in this PWS.

As directed, all software developed, maintained, updated shall be posted to the iNET program website at https://www.tena-sda.org/display/INET/Home for sharing with the community.

4.1 System Manager Software Development

The Contractor shall mature and enhance existing capabilities to the previously developed System Manager Software application. In general, the task orders will include new features or enhancements that will be formulated on the results of Range Integration efforts, Flight Testing, and other feedback collected during transition and deployment of the iNET capabilities. The Contractor maybe tasked to demonstrate these System Manager capabilities in the iSIL or at a designated facility.

Installation disk(s) shall be delivered in accordance with the DD250 for all major releases and shall contain all the required libraries, configuration scripts and utilities, and source code to build and install a fully executable System Manager using a standard compiler tool chain that documents the Software Build and Install process. For each major release, the Contractor may be tasked to conduct a code review at its facility.

4.2 Link Manager Software Development

The Contractor shall mature and enhance existing capabilities to the previously developed Link Manager Software application. In general, the task orders will include new features or enhancements that will be formulated on the results of Range Integration efforts, Flight Testing, and other feedback collected during transition and deployment of the iNET capabilities. The Contractor maybe tasked to demonstrate these Link Manager capabilities in the iSIL or at a designated facility.

Installation disk(s) shall be delivered in accordance with the DD250 for all major releases and shall contain all the required libraries, configuration scripts and utilities, and source code to build and install a fully executable Link Manager using a standard compiler tool chain that documents the Software Build and Install process. For each major release, the Contractor may be tasked to conduct a code review at its facility.

4.3 Technical Reviews

The Contractor shall organize and conduct technical reviews utilizing the International Council of System Engineering (INCOSE) documents identified in Section 2.3 as a guide. These Formal Reviews shall be conducted in accordance with CDRL A003 and meeting minutes for these Reviews delivered in accordance with CDRL A002.

4.4 Design and Test Documentation

The Contractor shall update and maintain the design and test documentation created under the previous contract, N00421-14-C-0010. The Software Development Plan, Software Design Document, Software Test Plan, Software User Manual, and the Engineering Specifications shall be updated as work is performed on each software application and delivered in accordance with CDRLs A004, A005, A006, A007, and A012. As a minimum, the Contractor shall deliver these CDRLs with each major release.

4.4.1 Software Testing

The software application testing shall be conducted at the Contractor’s facilities on all software to ensure compliance prior to release. For each major release, the Contractor shall update and deliver Software Acceptance Test Procedures in accordance with CDRL A008 and provide Software Acceptance Test Reports in accordance with CDRL A009. The Government may choose to observe testing prior to delivery.

4.5 Software Maintenance

The Contractor shall perform troubleshooting and fault isolation as well as identify corrective actions and proposed solutions to defects identified with both the Link Manager and System Manager software applications as the result of Flight testing, iSIL testing, or other users of the software.

5 SYSTEM INTEGRATION AND TESTING SUPPORT (CLIN 0002)

The Contractor shall provide system engineering activities required to maintain and mature the TmNS architecture to ensure interoperability through System/Subsystem and component level integration testing.

This support includes integration and testing of Government furnished TmNS components used in conjunction with the software applications culminating in utilizations of an interoperable TmNS based system.

5.1 iNET Systems Integration Lab

The Contractor shall continue to develop and maintain the iSIL that was established under the previous contract, N00421-14-C-0010. The Contractor shall maintain the equipment and materials in good working order. The Government will designate a timeframe in which the iSIL will be moved to the Patuxent River NAS to support flight test activities. The Contractor shall continue to provide partial iSIL capabilities at their facility to support ongoing software development/maintenance and support activities. These partial capabilities shall be identified in the Contractors integration plans.

The iSIL will continue to be populated with Government Furnished Equipment (GFE) and will be easily reconfigurable to allow for testing and fault isolation of flight-test system mock-ups, as well as specifications and standards validation.

5.1.1 System/Subsystem Integration and Testing

The Contractor shall perform system/subsystem level integration and testing of TmNS Components developed by third parties. The Contractor shall utilize components delivered by the Government, as GFE, and integrate them together to validate the interoperability of the TmNS Components and as necessary compliance with the TmNS standards and iNET/TmNS specifications. The Contractor shall utilize the Integration Test Plans, Test Tools, and software applications previously developed and maintained under this PWS.

5.1.1.1 Design and Test Documentation

The Contractor shall update and maintain the integration and test documentation created under the previous contract, N00421-14-C-0010. Architecture Refinement, Technical Drawings, and Integration Test Plans shall be updated as integration and testing activities are performed and delivered in accordance with CDRL A010, A014, and A015. As a minimum, the Contractor shall deliver these CDRLs at the conclusion of each task order.

5.1.1.2 Vendor Component Integration and Testing

The Contractor shall support, as required, the Government’s participation and testing at the component vendor sites to ensure compliance with the iNET/TmNS specifications and interoperability among the vendor’s TmNS Components.

5.1.1.3 Test Tools

In support of the integration test plans, the Contractor shall develop, deliver, and maintain the test tools necessary to validate component developed to the specifications and standards. The Contractor may propose Application Interface tools to help insure interoperability across the system. The Contractor shall provide all the necessary documentation to allow an independent entity to maintain and operate the test tools. The Contractor shall propose format and content of the developed tools and are subject to Government approval. As the test tools are developed and updated they shall be posted in accordance with the DD250 on the iNET program website.

5.1.1.4 Test Reports

The Contractor shall provide test reports of system/subsystem/components undergoing testing in the iSIL to document compliance of the system/subsystem/components under test. The Contractor shall provide test reports in accordance with CDRL A016. The Government may choose to observe testing prior to execution.

5.1.1.4.1 Non-Compliance Testing

In conducting testing on the TmNS components, where a component fails to meet the requirements identified in the specifications or standards, the Contractor shall perform additional testing to determine the level of non-compliance. These non-compliance(s) along with the level of non-compliance shall be submitted to Government for review and resolution.

5.2 Conferences

The Contractor may prepare technical papers and present them in the form of technical presentations to inform the community of the technical work in support of the ongoing development activities. The Contractor shall submit all technical papers and presentations in accordance with CDRL A019 thirty (30) days prior to the conference due date for review, approval, and public release authorization by the Government. The Contractor shall outline a plan as part of the Contractor’s proposal.

5.3 Standards

The Contractor shall update and deliver the TmNS standards proposals in accordance with CDRL A011 as identified in Section 2.2. This task is concurrent with committee efforts and may require conducting technology evaluations to resolve conflicting requirements. The Contractor shall provide support, estimated at two (2) RCC meetings per year, to help facilitate community participation in reviewing the updates to the RCC Networked Telemetry Standards.

5.3.1 Specifications

The iNET specifications are interlinked with the TmNS standards. Section 2.1 identifies a snapshot of the current specifications that will be matured by the Government. The Contractor shall provide support on updating these specifications as required.

5.4 Range Support

The Contractor shall support range integration for up to five (5) MRTFBs (i.e. Edwards AFB, Patuxent River NAS, China Lake NAS, Eglin AFB, Point Mugu NAS, etc.) as needed. This additional support would be in terms of technical support, travel, training, additional development, and supporting materials.

The Contractor shall outline a plan as part of the Contractor’s proposal.

5.4.1 Technical Studies and Demonstrations

The Contractor may be tasked to conduct technical studies and/or demonstrations to help identify and resolve technical issues such as performance characteristics, data delivery characteristics, efficiency issues, and other characteristics that effect operational usage of the system/subsystem/components. The Contractor shall document the method of the study and/or demonstration and provide the detail results in a technical report in accordance with CDRL A013.

5.5 Training

The Contractor shall develop and conduct a comprehensive training class that is geared toward “train the trainer” where the trainer is a Government designated person whom will train the range users. However, as training is being setup at ranges, the Contractor may be tasked to conduct/support training offsite.

5.5.1 Course Material and Training Aids

The Contractor shall develop the necessary training materials to support the training objectives defined in the Training Course requirement identified in Section 3.9 of the System Specification document and shall be delivered in accordance with CDRL A018.

5.5.2 Familiarization Class

The Contractor shall conduct introductory familiarization class at the Contractor’s facility using the material (Course Material and Training Aids) provided by the Contractor for the purpose of describing and demonstrating the TmNS Components, test procedures, and any special test equipment used in testing or maintenance of the components. At times as the ranges develop their own lab facilities, the Contractor may be tasked to conduct training offsite.

6 OTHER REQUIREMENTS

The section applies to all task orders issued under this contract.

6.1 Government Furnished Equipment

The Government will provide TmNS Components as GFE when they become available for integration and testing. The applicable components and software applications are identified in Section 2. The GFE list is contained in Attachment 2.

6.2 Data Rights

The Contractor shall relinquish all copyright and intellectual property rights to any material (documentation and software) developed under this PWS to the Government. It is expected that the deliverables, in whole or in part, delivered under this PWS will be released to the iNET development community.

6.3 Other Direct Costs

Contractor purchases of materials shall be limited to that incidental to or required for contract performance in accordance with NAVAIR Clause [ Restriction on the Direct Charging of Material.

6.3.1 Material (CLIN 0003)

Prior written approval of the TPOC is required for all material and ODC purchases per NAVAIR Clause 5252.242- 9515 [ Restriction on the Direct Charging of Material. Prior written approval of the Contracting Officer shall be required for purchases that exceed $250,000.

All contractor purchased materials procured with Government supplied funds that have not been depleted during the performance of this contract shall be considered Government Property. The contractor shall transfer all materials not depleted to the TPOC in accordance with the DD250. Material costs may include general and administrative expenses but shall not include profit.

6.3.2 Travel (CLIN 0004)

The contractor shall be required to travel in support of this PWS. Travel will be allowable only when it essential to the performance of the tasks detailed in this PWS. The TPOC shall approve all travel performed in support of this contract prior to commencement of the travel. Possible travel locations include NAS Patuxent River, Edwards AFB, Conferences, and other Ranges as deemed necessary. This list is not all inclusive as locations may change over the life of the contract. Travel may include general and administrative expenses, but shall not include profit.

7 DATA (CLIN 0005)

The section applies to all task orders issued under this contract.

7.1 Contract Data Requirements List

The Contractor shall provide all personnel and resources necessary to produce and deliver the Data Items identified in the CDRL. Contractor’s format and content for these deliverables must be submitted to Government prior to development of the data items for approval. All data items shall be deliverable in electronic form utilizing commercially available and commonly used public software.

7.1.1 Data Items

CDRL PWS Reference Title

A001 3.4 & 3.5 Periodic Status Reports A002 3.6 & 4.3 Meeting Minutes A003 4.3 Formal Reviews A004 4.4 Software Development Plan A005 4.4 Software Design Document A006 4.4 Software Test Plan A007 4.4 Software User Manuals A008 4.4.1 Software Acceptance Test Procedures A009 4.4.1 Software Acceptance Test Reports A010 5.1.1.1 Architecture Document A011 5.3 Standards Proposals A012 4.4 Engineering Specifications A013 5.4.1 Technical Reports A014 5.1.1.1 Technical Drawings A015 5.1.1.1 Integration Test Plans A016 5.1.1.4 Test Reports A017 3.9.5 OPSEC Plan A018 5.5.1 Training Materials A019 5.2 Technical Papers and Presentations