Attachment 1 QOS Implementation PWS.pdf

Statement of Work

Non-classified Internet Protocol Router Network (NIPRNet) and Secret Internet

Protocol Router Network (SIPRNet) Quality of Services (QOS) Implelmentation

5 Aug 2020

1.0. GENERAL INFORMATION AND SCOPE

1.1. Period of Performance (PoP):

Completion date of 31 December 2021

1.2. Overview:

The 21st Communications Squdron (21 CS) located on Peterson AFB, CO requires contractor support in the development and implementation of Quality of Service for NIPRNet and SIPRNet.

Peterson AFB NIPRNet and SIPRNet is used by United States Space Force, United State Space

Command, the Peterson-Schriever Garrison (on PAFB) and multiple on and off base tenant units to accomplish their mission.

1.3. Objectives:

21st Communications Squadron on Peterson Air Force Base is seeking contractor support in the development and implementation of NIPRNet and SIPRNet Quaity of Service. At project completion the Peterson - Schriever Garrison PAFB location NIPRNet/SIPRNet networks and branch locations will have QoS implemented to support Assured VoIP services. The implementation of NIPRNet and SIPRNet will be treated as independent projects. All of the work from hearout will be required for NIPRNet and the SIPRNet networks.

1.4. Location of Performance:

The work will be conducted remotely and on PAFB, Colorado .

2.0. WORK TO BE PERFORMED

2.1. General:

The contractor shall review the current network device platforms, the DoD Military Unique

Features Guide for ASLAN equipment, and the AVAYA VoIP CMM 7 integration to ensure the appropriate QoS configurations are selected for NIPRNet. The contractor shall review the current network device platforms, the DoD Military Unique Features for ASLAN equipment to ensure the appropriate QoS configuration sare selectedfor SIPRNet. The Contractor shall deliver and implement a series of templates per device type and utilize the Customer’s SolarWinds

Network Configuration Manager (NCM) platform to schedule and execute the rollout.

2.2. Project Lead:

The contract shall assign a project lead and initiate project planning which will cover, at a minimum:

Roles and responsibilities

Project objectives, priorites, technologies being deployed and key deliverables

Identification of the work required to achieve the project goals

The establishment of a high-level schedule for the project

Development strategies for mitigating major project risks

Time line for deliverables (status of project)

The creation of a QoS Design Plan

The creation of a QoS Implementation Plan

2.3. QoS Design Plan:

The contractor shall develop a QoS Design Plan for enterprise QoS planning and implement recommendations on up to four hundred NIPRNet network devices and sixty SIPRNet network devices. Device types include but are not limited to Catalyst 3850, 9300m 4500, 6500 switches, Juniper WX4300 switches, and Cisco ISR routers using IPSEC VPN. The following are examples of tasks the contractor will execte as part of a QoS design effort:

Review DoD JITC Miliatary Unique Deployment Feature Guides (MUDGE) Cisco, Juniper and Avaya (just Juniper and Cisco for SIPRNet)

Review Cisco and Avaya VoIP best practices (just Cisco for SIPRNet)

Assign classifications and allowances to each traffic type

Develop Enterprise QoS Policies

Determine markings fo each classified traffic type

Determin network trust points

Determin network marking and re-marking points

Determin the number and types of output queues per switching platform

Determine the queuing mechanism of each switching platform

Determin the number and type of thresholds per queue in each switching platform

Create Class of Services (CoS) to Differentiated Services Code Point (DSCP) map templates for each switching platform

Create policy to re-mark unknown traffic exceeding the specified bandwidth threshold as scavenger traffic

Design trust with downstream switch QoS policies o Develop traffic shaping and policing policies o Configure matching of incoming trusted traffic queues o Develop internal and external queue map diagrams

Design switch QoS policy templates

Desigh router QoS policy templates

Provide 21 CS POC with a finalized QoS design plan for review and approval

Provide an ATP

2.4. QoS Implementation Plan ( Upon approval of the finalized QoS Design):

Contractor will conduct pilot testing on all device tpes to ensure there will be no unplanned service disruption caused by changes. Perform test and acceptance procedures

2.5. Testing:

Utilizing the data obtained at the project initation meeting the contractor will develop a ATP documentation package. The ATP will include a document detailing test resource requirements, procedures, and expected results. The test plan document package will be reviewed by 21 CS to confirm both parties agree to the test plan criteria and methodologies. After reaching agreement, major changes to the ATP packages as a result of feature, application, or design change will go through a change control process to ensure no changes are implemented without having an agreed upon ATP.

2.6. Cutover procedures:

The contractor will formally turn the site over to 21 CS for daily operational support after the successful testing of the solution.

2.7. Documentation:

Contractor will employ a formal documentation development process, which utilizes a document change management tool to protect and control content production and editing. All documentation will be considered confidential and available for official use only, and with contributing staff unable to share data outside the project’s Information Technology (IT) domain.

3.0. SECURITY REQUIREMENTS

Facility Clearance: None required.

Classified Material: In the execution of this task order, the contractor is not expected to receive, generate, or reproduce classified material.

4.0. MINIMUM QUALIFICATIONS:

Prior experience implementing QoS on a combined Juniper/Cisco/Avaya network.

5.0. GOVERNMENT FURNISHED EQUIPMENT / INFORMATION (GFE / GFP):

5.1 GFE:

The Government will not provide physical workspace.

5.2 GFI:

Government will provide access to all required data sources necessary to provide required support. The contractor shall require access to various Government furnished databases and the government Senior Engineer shall arrange this access.

6.0. GOVERNMENT RESPONSIBILITIES

The government will be responsible for the following:

Designate a single point of contact

Have suitable technical staff as mutually agreed upon by both parties available for the duration of the engagement as defined by the project schedule

Provide reasonable access to 21 CS assets, facilities and workspace

Jointly define standard configuration templates by the mutually agreed upon dae defined during the project kick-off and documented in the project plan of record

Provide written feedback within 5 buisiness days on all project artifacts, documents, or presentations developed or updated by the Contractor.

Supply access information and credentials to the conractors for any 21 CS tools and all existing equipment that needs to be configured or may need to be modified

Provide escorts to secure areas as needed