Statement of Work (SOW) - DRAFT.docx

STATEMENT OF WORK (SOW)

Prototyping Platform System

SCOPE

This Statement of Work (SOW) defines the requirements for the Contractor to provide, deliver, install, integrate, calibrate, provide training/support, perform studies, and conduct one (1) training course on the operation of a Prototyping Platform System, including the creation of test signals/scenarios. Activities are in support of the Airborne Electronic Attack (AEA) Laboratory at the Naval Air Warfare Center – Weapons Division (NAWCWD) Point Mugu, California.

APPLICABLE DOCUMENTATION

No Applicable Documents

REQUIREMENTS

Prototyping Platform System Requirements The Contractor shall provide a Prototyping Platform System, which shall include the following:

· Field-Programmable Gate Array (FPGA) based capability to emulate the hardware/firmware operation

· Allow multiple users to run different models of variable sizes concurrently

· Allow for growth of both model size and number of models

· Allow for additions/upgrades to the interface components

· Automated flow using a emulation style clocking (CAKE clock)

· Engineering Development Kits (EDKs) including protocol interface solutions for an emulation platform that enables efficient driver and application-level testing, targeting validation of pre-silicon Register Transfer Language (RTL) of Application-Specific Integrated Circuits (ASICs) and systems on chip (SoCs) for physical connection to real-world interfaces

· Virtual Solutions including software adapter enabling user applications and Operating System (OS) drivers to establish virtual protocol connections, Accelerated Verification Internet Protocol (AVIP), Hybrid, Virtual Debug and InfiniBand-based link to virtual interfaces

· Job Scheduler and virtual manager to manage workloads

· Clock control to stop and resume the hardware at any time

· Joint Test Action Group (JTAG) and Universal Asynchronous Receiver/Transmitter (UART) interfaces

· Real-time monitoring of predefined (at compile time) signals

· Backdoor memory access

· Clock control for start/stop the clock on demand

· Fully scriptable runtime environment

· Remote accessible

· Two 6U blades (12 FPGA per blade) Delivery The Contractor shall deliver a Prototyping Platform System to the AEA Laboratory located at NAWCWD Pt. Mugu, CA. The Contractor shall receive authorization from the Government Contracting Officer’s Representative (COR) or Technical Point of Contact (TPOC) prior to shipment and/or delivery of any equipment. All tasks associated with shipment and delivery are the responsibility of the Contractor.

System Installation The Contractor shall install and integrate the hardware with the software, calibrate a Prototyping Platform System, and coordinate with the TPOC for installations of the Prototyping Platform System.

The Contractor shall provide a drawing package to document the interconnections between the system components. (CDRL A001) The Contractor shall provide and install a complete system with all software and hardware components listed in Paragraph 3.1.1 above.

The Contractor shall provide a scenario to demonstrate operational performance of the system, documenting the expected output of all components.

Training and Product Support The Contractor shall provide a demonstration of all system capabilities to Government personnel.

The Contractor shall conduct a System Operation & Developer Training Class for up to eight (8) Government personnel. It shall include all student training materials, presentation materials, and student laboratory assignments. (CDRL Items A001, A002) Studies The Contractor shall provide support to study, analyze, and demonstrate virtualization of system components. Studies include analyzing development requirements to virtual existing hardware and capability growth. (CDRL Item A003) Travel The Contractor personnel shall travel to the AEA Laboratory at NAWCWD Pt. Mugu, CA for the purpose of Prototyping Platform System installation, integration, calibration, and to conduct classroom training.

Contractor Data Requirements Lists (CDRLs) Specific items of operation/maintenance instructions and training materials shall be provided in accordance with the applicable CDRLs.

Table 1. CDRL List

SECURITY

Unclassified Contract In the case of an unclassified contract that requires no access to Classified Military Information (CMI), but that does require access to Controlled Unclassified Information (CUI), NAWCWD Restricted Areas, and/or Government IT systems, contractors are required to comply with (non- National Industrial Security Program) non-NISP processing requirements before local access to CUI, Restricted Areas, and IT can be granted. This process shall be coordinated by the Contracting Officer’s Representative (COR) or Technical Point of Contact (TPOC) through the NAWCWD Industrial Security office.

IT Security: Access to CUI, For Official Use Only (FOUO), and/or Government IT Systems Information Security. Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAVINST 5510.36B (series). The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of CUI and to control distribution of CUI in accordance with National Industrial Security Program Operating Manual (NISPOM) 32 CFR Part 117, 24 Feb 2021, and SECNAVINST 5510.36B.

CUI information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDI 5200.48, CUI. Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

Operations Security (OPSEC) The contractor shall comply with the OPSEC requirements outlined within the Department of Defense (DD) Form 254, as applicable.

The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified 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 be in accordance with DoD and Department of the Navy (DON) OPSEC requirements, to include:

1) Assignment of responsibility for OPSEC direction and implementation

2) Planning guidance for the use of the OPSEC Process to identify vulnerabilities and apply applicable countermeasures (Contact NAWCWD Industrial Security Office for a current OPSEC Annex and Controlled Information (CI) Guide)

3) Establishment of OPSEC education and awareness training

4) Provisions for management, annual review, and evaluation of OPSEC programs

5) Oversight for accountability of OPSEC requirements to subcontractors.

Public Disclosure of Information Public Release. Disclosure of information is covered by Defense Federal Acquisition Regulation Supplement (DFARS) 252.204-7000 Disclosure of Information, incorporated in Section I of the contract. Concerning subsection (a)(2), “information otherwise in the public domain” is information officially released into the public domain, e.g. via Distribution Statement A, and does not include information in the public domain that has not been officially released. For disclosure of unclassified information that has not been officially released, the contractor shall seek specific approval from the Contracting Officer, with approval from the NAWCWD Public Affairs Office (PAO).