SOW - TIC-WAN Final.pdf

SOW/CIT NS TIC Circuits

STATEMENT OF WORK

CIT NS TRUSTED INTERNET CONNECTION (TIC) Circuits

1. BACKGROUND

The National Insitutes of Health (NIH) Center for Information Technology (CIT) provides leadership to the NIH community in a variety of infrastructure services, applications development efforts, and management of various NIH-wide systems including: (1) determining NIH computational and telecommunications needs at all levels and overseeing the development of appropriate infrastructure support to meet identified needs; (2) developing, operating, and maintaining a state-of-the-art regional computer facility and providing overall guidance based on legislation and policy that is responsive to the NIH mission; (3) developing and providing NIH information technology (IT) policy to implement legislative mandates, such as those under the Clinger-Cohen Act; presidential, and other administration initiatives and policies; (4) developing and implementing policy and standards in the area of IT by identifying, documenting, and communicating IT issues, problems, and solutions to the NIH community in a comprehensive and meaningful way; (5) establishing and operating the necessary organization and infrastructure to assure appropriate security, connectivity, and inter-operability across the NIH Institutes and Centers (ICs), off-campus locations, and remote access; (6) collaborating on, and providing for, research activities in the computational biosciences and statistics; (7) developing, administering, and managing NIH systems, and providing consulting services to the ICs, in support of administrative and business applications; and (8) serving as a Federal Data Processing Center that provides administrative, biomedical, and statistical computing; data processing; and high performance computing facilities and integrated telecommunications data networks that serve the Department of Health and Human Services (DHHS) and other federal agencies.

The NIH Network (NIHnet) consists of the NIH backbone network, providing a high-speed, highly available network infrastructure for NIH, other Government agencies, and a growing number of local area networks (LANs) supporting NIH’s Office of the Director and 27 ICs. NIH acts as the network operator for DHHS OPDIVs, and other Government agencies. NIH interconnects the NIH with the commodity Internet, the Internet2 research network. NIH supports LANs collocated on the NIH campus (9000 Rockville Pike, Bethesda, Maryland), numerous off-campus sites located in or close to the National Capital Region, field offices across the U.S., and disaster recovery centers. The data and information carried by NIH varies widely and includes biomedical, clinical, financial, and administrative data.

Further information about CIT is provided at http://www.cit.nih.gov

2. SCOPE

To acquire Internet Connectivity and associated circuits necessary for Network Support Services.

Dual connections on diverse paths are needed at every location. Diversion include cable path, routing administrations, and in some cases, multiple buildings. Main point of presence (MPOP) located at government facilitied, GSA facilities, and contracting facilities.

http://www.cit.nih.gov/

3. TECHNICAL REQUIREMENTS

3.1 GENERAL REQUIREMENTS

The Contractor shall independently and not as an agent of the Government furnish all the necessary services, qualified personnel, material, and equipment not otherwise provided by the Government as needed to perform all requrements of the Statement of Work.

The Contractor shall provide dual connections on diverse paths are needed at every location.

Diversion include cable path, routing administrations, and in some cases, multiple buildings.

Main point of presence (MPOP) located at government facilitied, GSA facilities, and contracting facilities.

The Contractor shall maintain full functionality of the NIH and TIC Internet Connectivity and Wide Area Network at a 99.99 percent per circuit availability.

The Contractor shall provide the Contracting Officer Representative seven (7) days advance notification of all planned maintenance.

The Contractor provide a transition plan no longer than 90 days.

3.2 TASK AREAS

3.2.1 Task 1: Provide a total of two (2) 1Gb circuits, one (1) 1Gb circuit each between the locations specified below, for connectivity to Centers for Medicare & Medicaid Services (CMS) at Culpeper, VA. Must have diverse paths from each other, diverse routing administration, and physical separation. Dedicated Gig-Ethernet Wave (1Gb, Unprotected).

Circuit Locations:

a) 1Gb Wave 1, 9000 Rockville Pike Bldg 12 Bethesda, MD 20894 (GFP secured cage) to 18155 Technology Dr Culpeper, VA 22701

b) 1Gb Wave 1, 44480 Hastings Dr Ashburn, VA 20147 (GFP secured cage) to 18155 Technology Dr Culpeper, VA 22701

3.2.2 Task 1: Provide a total of three (3) 10Gb WAN circuits to interconnect three (3) HHS

TIC. One (1) 10Gb circuit each between the locations specified below.

This “WAN A”, consisting of three (3) 10Gb circuits [Bethesda to Atlanta, Bethesda to Albuquerque, and Atlanta to Albuquerque] will serve as the backbone transport for HHS TIC on-net traffic.

HHSWAN Site Locations – “WAN A”:

a) Indian Health Service (IHS) 1011 Indian School Rd NW Albuquerque, NM 87104

b) Center for Disease Control (CDC) 1600 Clifton Rd NE, Building 21 Atlanta, GA 30329

c) National Institutes of Health (NIH) 9000 Rockville Pike, B12 Data Center Bethesda, MD 20817

Listed below are the specific physical, operational, and technical ISP/HHS Internet Wide Area Network Connectivity requirements for each of the three HHS TIC Internet connection sites:

1. Each designated HHS Internet site location requires a base 10Gbps bandwidth connection into the vendor network service.

2. Service to be set up as point to multi-point.

3. The proposed vendor solution must support a minimum 99.99% per circuit availability metric.

4. The proposed vendor solution must support telecommunications service priority

(TSP) to ensure rapid service restoration.

5. The proposed vendor solution average packet transit time through the vendor network is not to exceed 70ms end-to-end.

6. HHS intent is to manage traffic in and out of vendor cloud. Therefore, the proposed vendor solution must support packet traffic tagging.

7. Service must not impede IPv4 and IPv6 traffic through the vendor network.

8. Optical transport technology must be used between HHS TIC sites.

9. Vendor service turn up expediency will be considered as a weighted value.

10. Solutions for WAN A and WAN B must have end-to-end diverse paths that do not use the same inter-site solution. This solution must have diverse routing administration and maintain physical separation.

11. This solution must ensure the failure of WAN B does not affect the operation of WAN A, and vice versa.

3.2.3 Task 1: Provide a total of four (4) 10Gb ISP connections for Internet Connectivity at

Atlanta (A and B). Two (2) 10Gb connections for the A side and two (2) 10Gb connections for the B side.

Site Location:

Center for Disease Control (CDC)

Atlanta, GA 30329

Specific physical, operational, and technical ISP/HHS Internet Connection Requirements at Atlanta, GA:

1. Each designated HHS Internet site location requires a minimum 10Gbps connection to the commodity Internet.

2. The ISP service shall support a minimum 99.99% per circuit availability metric.

3. The ISP service average packet transit time through the ISP network is not to exceed

70ms end-to-end.

4. The ISP service must support telecommunications service priority (TSP) to ensure rapid service restoration.

5. The ISP service must support blocking of malicious Denial of Service (DOS) attacks.

6. The designated HHS Internet site location requires a dedicated, entrance path connection to the ISP vendor Internet points-of-presence (PoP).

7. The ISP service shall support Border Gateway Protocol (BGP) dynamic routing between each ISP vendor PoP and designated HHS Internet site location.

8. The ISP service shall support AS-Path filtering, prefix-lists, Multi-Exit

Discriminators (MEDs), and community strings to control and customize individual customer BGP requirements.

9. The ISP service shall support Federal Government assigned and InterNIC registered IPv4 and IPv6 network addresses, autonomous system numbers (ASN), and domain names.

10. The ISP service IP network must extend internationally, using peering agreements with major (Tier 1) global Internet providers.

11. The service must support BGP for IPv4 and native IPv6 networks.

12. The ISP service shall announce the full Internet routing table to each site plus a default originate route.

13. The ISP service turn up expediency will be considered as a weighted value.

14. Diverse paths end-to-end, diverse routing administration, and physical separation are mandatory.

15. The service provider 10G WAN service P/Label Switch Routers must maintain geographic diversity by not utilizing the same physical address at ingress or egress to the service provider WAN network.

3.2.4 Task 1: Provide a total of (8) 10Gb ISP connections for Internet Connectivity at the DC Bi-located at Bethesda, MD (A) and Ashburn, VA (B) Internet HUB. Four (4) 10Gb connections for the Bethesda, MD (A) and four (4) 10Gb connections for the Ashburn, VA (B).

Site Locations:

a) National Institutes of Health (NIH) 9000 Rockville Pike, B12 Data Center Bethesda, MD 20817

b) Food and Drug Administration (FDA)

ACC4 Datacenter, 44480 Hastings Drive Ashburn, VA 20147

Specific physical, operational, and technical ISP/HHS Internet Connection Requirements and Bethesda, MD and Ashburn, VA.

1. Each designated HHS Internet site location requires a minimum 20Gbps connection to the commodity Internet.

2. The ISP service will must support a minimum 99.99% per circuit availability metric.

3. The ISP service average packet transit time through the ISP network is not to exceed

70ms end-to-end.

4. The ISP service must support telecommunications service priority (TSP) to ensure rapid service restoration.

5. The ISP service must support blocking of malicious Denial of Service (DOS) attacks.

6. The designated HHS Internet site location requires a dedicated, entrance path connection to the ISP vendor Internet points-of-presence (PoP).

7. The ISP service shall support Border Gateway Protocol (BGP) dynamic routing between each ISP vendor PoP and designated HHS Internet site location.

8. The ISP service stichall support AS-Path filtering, prefix-lists, Multi-Exit

Discriminators (MEDs), and community strings to control and customize individual customer BGP requirements.

9. The ISP service shall support Federal Government assigned and InterNIC registered IPv4 and IPv6 network addresses, autonomous system numbers (ASN), and domain names

10. The ISP service IP network must extend internationally, using peering agreements with major (Tier 1) global Internet providers.

11. The ISP service must support BGP for IPv4 and native IPv6 networks.

12. The ISP service shall announce the full Internet routing table to each site plus a default originate route.

13. The ISP service turn up expediency will be considered as a weighted value.

14. Diverse paths, diverse routing administration, and physical separation are mandatory.

15. The service provider 10G WAN service P/Label Switch Routers must maintain geographic diversity by not utilizing the same physical address at ingress or egress to the service provider WAN network.

3.2.5 Task 1: Provide a total of three (3) 10Gb WAN circuits to interconnect three (3) HHS

TIC. One (1) 10Gb circuit each between the locations specified below.

This “WAN B,” consisting of three (3) 10Gb circuits [Ashburn to Atlanta, Ashburn to Albuquerque, and Atlanta to Albuquerque] will serve as the backbone transport for HHS TIC on-net traffic.

HHSWAN Site Locations – “WAN B”

a) Indian Health Service (IHS)

1011 Indian School Rd NW Albuquerque, NM 87104

b) Center for Disease Control (CDC)

Atlanta, GA 30329

c) Food and Drug Administration (FDA) 44480 Hastings Drive

Ashburn, VA 20147

Specific physical, operational, and technical ISP/ HHS Internet Wide Area Network Connectivity requirements for each of the three HHS TIC Internet connection sites.

1. Each designated HHS Internet site location requires a base 10Gbps bandwidth connection into the vendor network service.

2. Service to be set up as point to multi-point.

3. The proposed vendor solution must support a minimum 99.99% per circuit availability metric.

4. The proposed vendor solution must support telecommunications service priority

(TSP) to ensure rapid service restoration.

5. The proposed vendor solution average packet transit time through the vendor network is not to exceed 70ms end-to-end.

6. HHS intent is to manage traffic in and out of vendor cloud. Therefore, the proposed vendor solution must support packet traffic tagging.

7. Service must not impede IPv4 and IPv6 traffic through the vendor network.

8. Optical transport technology must be used between HHS TIC sites.

9. Vendor service turn up expediency will be considered as a weighted value.

10. Solutions for WAN A and WAN B must have end-to-end diverse paths that do not use the same inter-site solution. This solution must have diverse routing administration and maintain physical separation.

11. This solution must ensure the failure of WAN A does not affect the operation of WAN B, and vice versa.

3.2.6 Task 1: Provide one (1) 1Gb circuit for connectivity between Atlanta, GA and Albuquerque, NM. Dedicated Gig-Ethernet Wave (1Gb, Unprotected).

Circuit Location:

a) 1Gb Wave 1, SOC TIC Office, Rm 350 Telco, 6 Executive Park Dr. NE, Atlanta, GA 30329 to Indian Health Service (IHS) 1011 Indian School Rd NW Albuquerque, NM 87104.

3.2.7 Task 1: Provide Distributed Denial of Service Mitigation service for the HHS Washington D.C. region TIC POP Internet circuits at Bethesda, MD and Ashburn, VA.

ISP will provide service instructions and 24x7 access to their SOC (Security Operations Center) for management and coordination of traffic offload to scrubbing centers.

o ISP will provide DDoS Clean Traffic Return Path, Flow Based Monitoring, Additional Protected Subnets, and Clean Banwidth.

DDoS Service Location:

o Configure sub-interface and applicable settings on the 20-Gig ISP circuit at 9000

Rockville Pike, Bethesda, MD 20892 Configure sub-interface and applicable settings on the 20-Gig ISP circuit at 44480 Hastings Drive, Ashburn, VA 20147

3.2.8 Task 2: Provide a total of two (2) 10Gb circuits for connectivity to NIEHS at Research.

One (1) 10Gb circuit each between the locations specified below.

Must have diverse paths from each other, diverse routing administration, and physical separation. Dedicated 10 Gig-Ethernet Wave (10Gb, Unprotected).

Circuit Location:

a) 10Gb Wave 1, 9000 Rockville Pike Bldg 10 Bethesda, MD 20894 to 111 TW

Alexander Dr Research Triangle Park, NC 27709 Bldg 104 Data Center

b) 10Gb Wave 1, 9000 Rockville Pike Bldg 12 Bethesda, MD 20894 to 111 TW Alexander Dr Research Triangle Park, NC 27709 Bldg 101 Module F

3.2.9 TRANSITION

a) Transition-In

The transition-in period shall begin with the execution of the TO and may continue for up to ninety (90) calendar days. The transition-in shall involve the build out of ciruits, installation of equipment, ,transfer of documentation (circuit notations, drawings, operating procedures, point of contact listings) and other resources, including but not limited to, devices, equipment, databases, and systems under NIH’s responsibility. Transition-in activities shall include contractor attendance at program reviews, participation in working groups, briefings, on-site communications, and full disclosure of technical and programmatic information. During the transition-in period, the incumbent is responsible for performance.

b) Transition-Out

The transition-out period may begin as early as ninety (90) calendar days prior to the end of the current TO performance period. The contractor shall provide a transition-out plan to include the transition of the documentation, operating procedures, and other resources, including but not limited to, devices, equipment, databases, and systems under NIH’s responsibility as related to this SOW to any follow-on contractor or the Government. The contractor shall execute its transition plan and work closely with the follow-on contractor or the Government to ensure uninterrupted contract service support. Transition-out activities shall also include contractor attendance at program reviews, participation in working groups, briefings, on-site communications, and full disclosure of technical, cost, and programmatic information and removal of equipment. The incumbent contractor shall be responsible for contract performance during the transition-out period.