032 RFQ attachment - SOW FINAL.docx

Performance Work Statement DC-QNET-PQNI Project Support

Background:

The Transformational Networks and Services in the Smart Connected Systems Division in the Communications Technology Laboratory (CTL) at the National Institute of Standards and Technology (NIST) is doing research in the development of novel network control and management systems capable of automating the configuring, monitoring, and troubleshooting of complex networks as well as their deployment and operation. This research targets several communication technologies at various layers of the software protocol, from traditional Internet Protocol (IP) to emerging network technologies such as Information-Centric Networking (ICN) and quantum networking.

Scope of Work:

Objective(s):

NIST requires contractor support to prototype, deploy, test, and maintain a highly innovative and complex network testbed that includes classical optical, and quantum network equipment, that is currently in operation on the NIST campus in Gaithersburg, MD. The work includes innovations in both hardware and software components on the testbed. NIST is currently building entangled-photon sources and polarization control hardware, writing software to control them, and also implementing quantum protocols like teleportation protocol.

General Requirements:

The contractor shall perform the following general tasks:

(1) Deploy and test an open-source Network Operating System called SONiC on the classical switches of the testbed.

(2) Deploy and test the commercial Netris Software Defined Networking controller, currently in use on the network, to configure classical switches and routers in the testbed. Configure and test the security policies of the firewall software in collaboration with OISM.

(3) Develop and deploy a configuration and data collection (Telemetry) microservice.

(4) Support a team of NIST collaborators and engineers doing metrology research and developing protocols for these networks. Also, the contractor shall support the set-up of the experiments on the network (program the switches to get fiber path between the different sites involved) and running experiments on these testbeds.

(5) Produce a final report that

a. Describes the network topology, the routing table entries, and the performance of the links observed through telemetry software and validated against values from test equipment.

b. Includes data showing reachability from any node to any other nodes through ping statements or traceroute statements.

c. Includes operational optical performance signals on the receiver side of all the nodes

d. Includes the ability to set up cross-connects on the optical switches and observe the wavelength on the output port when connected to test equipment with a good operational signal power.

e. Covers the overall network test plan in relation to demonstrations of the various networking capabilities: routing, firewall, management system, and connectivity to the Internet.

Specific Tasks:

Task Number Description

Monthly Progress Reports:

Monthly progress reports shall detail progress made during the prior month, progress expected for the next month, any significant problems, risks or issues encountered, recommended actions to resolve identified problems, and any variances or expected variances from scheduled due dates. Monthly progress reports shall be due on the 10th of each month, beginning during the first full month of performance (if the performance period starts on a date other than the first of the month), covering all contract activity during the preceding month.

Weekly Status Updates The Contractor key personnel shall participate in weekly status meetings with the NIST Contracting Officer’s Representative (COR) to discuss progress to date. These meetings shall take place via telephone or virtual video call and are expected to take no more than one hour.

Deliverables:

Standards for Acceptance of Deliverables:

The NIST COR shall review the deliverables and respond with an acceptance or request for revision email to the Contractor Point of Contact (POC) within 14 calendar days of receipt of deliverable. The Contractor shall make any needed changes to the reports or deliverables within 14 calendar days from receipt of electronic or written comments from the COR. This section applies to deliverables which must be reviewed and approved for acceptance. The COR will provide written notification when a deliverable is acceptable.

Performance Requirement Summary:

Desired Output Required Service

Method

implementations.

NIST COR shall monitor the Contractor productivity on a weekly basis.

Deployment of the SONiC network operating system routing protocol (BGP) on the classical switches.

Fiber/Connect all the routers as indicated in figure 1. Install the SONiC network operating system on the routers forming the network infrastructure.

Bring up the routing protocol and test reachability to the various parts of the network.

Test the discovery/ topology , routing, configuration, and telemetry services.

Demonstrate reachability of the various network equipment using test plans to ascertain proper installation and functionality of the routing protocols.

Demonstration of connectivity across the network at NIST and to outside NIST (Internet).

Demonstration of the Netris management system across the network.

Demonstration of the firewall functionality to block incoming not allowed protocols.

NIST COR shall review the progress of the agent implementation and determine its acceptability.

Deployment of the classical switches on the NIST campus, and the deployment of the Optical Switches and classical switches in the DC-QNet.

Install the software on the classical switches and test the connectivity.

Test the routing protocol so all present endpoints on the DC-QNet are reachable.

Retrieve and validate the performance of the links using the telemetry software.

Cable/Connect the optical switches, power them up and ascertain their connectivity by connecting to them from a different computer.

Assemble the topology diagram of the network, that shall contain the connectivity and telemetry data on each switch.

NIST COR shall review the written report and determine its acceptability.

Describe the main characteristic of its design. Present its implementation and the conclusions that can be drawn based on experiments performed on one or more test deployments.

Place of Performance:

The work shall be performed primarily at NIST, Gaithersburg, Maryland campus located at the following address:

National Institute of Standards and Technology (NIST) 100 Bureau Drive Buildings 222, 220,221, and 225 (Multiple labs that include equipment connected to PNI) Gaithersburg, MD 20899-1640

Work may also be performed offsite in order to continue work during times when NIST is closed or access is restricted, for example during a government shutdown or due to pandemic-related restrictions. Offsite work may also be permitted whenever the Government determines it is advantageous to the Government for progress or performance of the work. All offsite work or telework requests must be approved prior by the COR.

All work shall be accomplished Monday through Friday with the exception of Federal holidays or other official closures.

Period of Performance/Delivery Date:

The period of performance shall be 12 months from the date of award. The anticipated dates are from 05/01/2023 – 04/30/2024.

Government-Furnished Property, Material, Equipment, or Information:

(GFP, GFM, GFE, or GFI)

All property, data and information provided by the Government in the performance of this task remains the property of the Government and shall be surrendered to the government upon completion or termination of this requirement. Likewise, all deliverables generated under this requirement remain the property of the Government.

The property listed in this section (below) is property that is incidental to the place of performance due to the contract requiring contractor personnel to be located on a Government site. Any property used by the Contractor within the location remains accountable to the Government. Per FAR Part 45.000(5) items considered to be incidental to the NIST place of performance include onsite office space, desks, chairs, telephones, computers, fax machines, email and Internet access, routine office supplies, and access to all facilities needed for the project. NIST will not provide Internet, telephone, or furniture resources for approved off-site work. Government-furnished equipment will be provided in an as-is working condition. The Government will not provide the contractor with internet or telephone resources off-site; any such resources required are the responsibility for the contractor.

All property, data and information provided by the Government in the performance of this task remains the property of the Government and shall be surrendered to the government upon completion or termination of this requirement. Likewise, all deliverables generated under this requirement remain the property of the Government.

Security:

(1) NIST is a restricted campus. An identification badge is required for access into buildings and must be presented to the armed Security Police when entering the campus.

(2) Regular Business Hours: Regular business hours are Monday through Friday, 8:00 am to 5:00 pm Local Time.

(3) Identification Badges: Contractor employees shall comply with NIST identification and access requirements. Each Contractor employee shall wear a visible identification badge provided by the NIST Security Office.

(4) Vehicle Registration: All Contractor employees must register their vehicles with the NIST Security Office to gain access to the campus. A valid driver’s license, Government-furnished civilian ID, proof of insurance and current registration must be presented to the NIST Security Office, at which time a NIST vehicle pass will be issued. The pass shall be displayed on the vehicle in accordance with NIST Security Office instructions.

Travel:

Local travel to the DC-QNet sites may be required in the event the site administrator is unable to fix any networking issues that arise. Travel may also be required to present the results of the work at a conference. However, the COR will provide the contractor at least 2 weeks notice prior to any travel engagement requirements. Travel engagements and anticipated costs must be approved by the COR in advance.

The Not to Exceed (NTE) budget/costs for travel under this purchase order shall be $5,000.00.

CONTRACT TYPE

The contract type will be firm fixed price in accordance with the following CLIN structure:

CLIN 0001: Firm-Fixed-Price – Completion of all Deliverables in this Statement of Work CLIN 0002: $5,000 Not-to-Exceed (NTE) for Travel requirements.

RISK LEVELS

The work under this purchase order is designated as IT-Low Risk and Non-IT Low Risk. The Contractor shall only access low risk general-purpose IT equipment and common network services available to NIST associates.

KEY PERSONNEL REQUIREMENTS

One (1) Key Personnel is required to be assigned by the contractor and must meet the following minimum qualifications:

One (1) Key Personnel:

This individual shall oversee all purchase order efforts, and shall have at least a Master’s degree in a related field to the Statement of Work requirements and at least 2 years of demonstrated experience in each of the subject areas described below.

(1) The Contractor Key personnel shall possess theoretical knowledge and practical experience in distributed systems, network measurements, network management, standard network protocols (e.g., IPv4 and IPv6), and basic security and cryptography concepts (e.g., digital signatures, digital certificates, authenticated symmetric encryption, key agreement schemes).

(2) The Contractor must also be familiar with at least one emerging networking paradigm such as Software Defined Networking, Disaggregated Network Architecture, and Named Data Networking (NDN).

(3) The Contractor must be able to independently design and efficiently implement and test all aspects of an operational high-speed network.

(4) Knowledge of IP, OSPF, BGP, SSH, and management protocols is required for the implementation tasks. Experience with software version control systems such as Git and GitHub are also needed.