HC102816R0012_Amend_0006.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to revise Section 6.10 of the PWS as a result of updated "Cyber Threat Security Plan" information.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 2

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 03-Oct-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC1028-16-R-0012

X 9B. DATED (SEE ITEM 11)

02-Aug-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

03-Oct-2016

CODE

DISA/DITCO-SCOTT-PL83

2300 EAST DRIVE

SCOTT AFB IL 62225-5406

HC1028 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HC1028-16-R-0012

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

(End of Summary of Changes)

RFP No. HC1028-16-R-0012

Section J, Attachment C-1 Revised, Amendment 0006

PERFORMANCE WORK STATEMENT (PWS)

1.0 Contracting Officer Representative (COR).

a. Primary COR. See DARS Clause 52.204-9000

Name:

TBD

Organization:

Defense Information Systems Agency (DISA)

Department of Defense Activity

Address Code (DODAAC):

H98272

Address:

1 Overcash Ave., Bldg 12, LEAD

Chambersburg, PA 17201

Phone Number:

E-Mail Address:

b. Alternate COR. See DARS Clause 52.204-9000

Name:

TBD

Organization:

Defense Information Systems Agency (DISA)

DODAAC:

H98272

Address:

1 Overcash Ave., Bldg 12, LEAD

Chambersburg, PA 17201

Phone Number:

E-Mail Address:

2.0 Contract Title. Capacity Services Communications Contract (CSC II)

3.0 Background. DISA is a provider of information technology solutions for the Department of Defense (DoD). DISA’s DoD customers require processing, storage and communications services for a variety of applications. DISA must have the ability to provide communications capacity in a timely manner whenever and wherever the requirements occur. The purpose of this contract is to provide state-of-the-art communications infrastructure capacity to meet new and emerging customer requirements as well as the ability to replace existing DISA communications capacity that has exceeded its technical or economic life, as determined by the Government.

4.0 Objectives. The purpose of this contract is to obtain reliable, responsive, and cost effective communication infrastructure services in both DISA and at other DISA-approved locations. DISA's goal is to obtain a dynamically scalable communications capability utilizing an on-demand service approach for new (unless approved by the Government) equipment that can readily adjust to both increases and decreases in communications requirements and which is available on an “as ordered" basis for communication hardware.

4.1 For all communications capacity requirements, the service provider will acquire, transport and provide the necessary hardware, hardware maintenance, communications operating software and service to support the communication infrastructure associated with this contract as a Capacity Service. The contractor shall also provide, when requested, the cabinets, racks and cabling as Supply Items to be owned by DISA.

4.2 The Government is responsible for the day-to-day operational control of the environment where the communication equipment will reside. Operational control includes, but is not limited to, monitoring activities, configuration changes based on changing requirements and ensuring that required updates to operating software are received from the contractor and applied.

5.0 Scope. The scope of this project includes the hardware, the communications operating software, network management tools/software, technical services, and operational control required to deliver DISA flexibility to meet the requirements of security, availability, scalability and modernization of the communication infrastructure.

5.1 Unclassified scope. This initiative will support controlled unclassified level environments listed below. Versions listed are current but capacity delivered must be compatible with future versions.

5.1.1 The hardware/Chipsets/operating environments requiring communications infrastructure support for DISA are:

5.1.1.1 IBM System z (IBM z/OS, IBM z/VM, Red Hat Enterprise Linux, SUSE Linux Enterprise server)

5.1.1.2 X-86

· Windows Server (Server 2012 R1, 64 bit, Server 2012 R2, 64 bit, Server 2008 R2, 64 bit)

· Red Hat Enterprise Linux (version 6.x, 64 bit, 7.x, 64 bit)

· SUSE Linux Enterprise Server (version 10-sp3 and version 11-sp1)

· Solaris (version 10 and version 11)

· VMware

· vSphere Enterprise Plus

5.1.1.3 Itanium (HP-UX) (version 11.31, 11i-v3)

5.1.1.4 SPARC (Solaris) (version 10 and 11)

5.1.1.5 IBM System p (AIX) (version 6.1 and 7.1)

5.1.1.6 Any other operating system software that DISA may require in the future.

5.1.2 The contractor is to provide communication environment services using a “utility use concept”. All capacity assets needed for the service shall be provided by the contractor when the utility concept is exercised. Assets provided as a utility include, but are not limited to, hardware, software, software maintenance and licensing, logistical support, field maintenance, and systems engineering support as requested by the DISA engineers. The contractor will clearly identify what make and model is being proposed to satisfy any and all requirements, including hardware or software required to meet the requirements of this PWS.

5.1.2.1 No communication hardware currently installed in DISA shall be used to satisfy the requirements of this solicitation, unless approved by the Government. All hardware to support solutions brought into DISA locations for the first time must be new hardware. If the requirement for the hardware is later canceled prior to approval, the hardware to support the service may be reutilized as long as the technology has not already been returned to the contractor, Government approval is sought and received and it is not a product that the Original Equipment Manufacturer (OEM) has withdrawn from marketing/sale.

5.1.2.2 The intent of this contract is to cover both present and future requirements for communication infrastructure solutions. As technology performance and capabilities improve, the class of communication infrastructure will support any advances in improvement to performance or capabilities at the awarded Sub-Line Item Number (SLIN).

5.1.3 After contract award, all requirements must be staffed through the contractor and Government Program Management Offices. Any contractual requirement obtained via another source (i.e., sales) will not be addressed.

5.1.4 Current Environment

5.1.4.1 DISA currently provides communication capacity services at fifteen (15) computing facilities in the CONUS:

· Chambersburg, PA

· Columbus, OH

· Denver, CO

· Fort Meade, MD

· Jacksonville, FL

· Pensacola, FL

· Mechanicsburg, PA

· Montgomery, AL

· Ogden, UT

· Oklahoma City, OK

· San Antonio, TX

· St Louis, MO (See Clause H.1 regarding environmental conditions at the DECC St. Louis.)

· Ft Bragg, NC

· Ft Eustis, VA

· Ft Knox, KY

5.1.4.2 Six (6) current OCONUS locations are:

· Germany

· Hawaii

· Alaska

· Bahrain

· Japan

· South Korea

5.1.4.3 Five (5) current NIPR mini-pod locations are:

· Camp Walker

· Yokota

· Ft. Wainwright

· Bahrain

· Raven Rock

5.1.4.4 Future locations. Contractor shall have the ability to support DISA or DISA approved locations worldwide.

5.2 Classified scope. This initiative will support controlled classified level environments and include all of the items listed above in 5.1 and the following additional requirements:

5.2.1 The scope of this contract for placement of communications equipment capacity includes areas which are classified SECRET. System access required for contractor to perform their duties includes accounts to use a GFE laptop computer to login into the SIPRNET Out of Band (OOB) Virtual Private Network (VPN) and attached Authentication Servers (ACS) in order to audit and verify configurations on attached communications network devices. Because privileged (administrator) rights are required for this type of access, the contractor personnel must possess SECRET/IT-1 level clearances. Additionally, contractors will be required to access the SIPRNET Ports and Protocols Security Management (PPSM) system to register IP addresses for device setup.

5.2.2. The scope of this contract for placement of communications equipment capacity includes areas which are classified at a level higher than SECRET. In the event that communications capacity is required to be installed in an environment classified as higher than SECRET, system access by the contractor is NOT required. The contractor will be escorted into the area to perform physical installation tasks only which include placement of the equipment and connection of required power and cables. Government personnel will assume any tasks requiring system access.

6.0 Performance Requirements.

6.1 Task 1. Communications Capacity Solutions and Capabilities. New communication capacity shall be provided as an ‘on-demand’ service capable of readily adjusting to changes in requirements, both increases and decreases. All components provided for the solution must meet minimum features listed. DISA and the contractor will determine the need for additional capacity and/or communication equipment. The contractor shall accept a call order for additional capacity within one (1) business day of receipt, unless mutually agreed upon to change for date of receipt.

Note that contractor examples are provided in Appendix 1 as a sampling of the current hardware deployed within the DISA environment. Any solution that is capable of meeting the device requirements and complimenting the existing infrastructure would be considered a suitable fit.

The contractor shall provide flexible, highly scalable, solutions that are non-disruptive for:

6.1.1 Subtask 1 – Appliances.

6.1.1.1 Data Center Forward Proxy, Licenses and Modules. This tier is the data center forward proxy, licenses and modules category. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.1.

6.1.1.2 Data Center SSL VPN Appliances. This tier is the data center SSL VPN appliances category. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.2.

6.1.1.3 Data Center/Enterprise Traffic Matrix Appliance, Modules and Licenses. This tier is data center/enterprise traffic matrix appliance, modules and licenses category. These devices must be available on a chassis, line card and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.3.

6.1.1.4 Enterprise Accounting, Authentication, and Authorization (AAA) Appliances, Licenses and Modules. This tier is the enterprise AAA appliances, licenses and modules category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.4.

6.1.1.5 Enterprise Application Delivery Controller and Modules. This tier is the enterprise application delivery controller and modules category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.5.

6.1.1.6 Enterprise Deep Packet Inspection Appliance and Associated Devices. This tier is the enterprise deep packet inspection appliance and associated devices category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.6.

6.1.1.7 Enterprise DNS Appliances, Modules and Appliances. This tier is the enterprise DNS appliances, modules and appliances category. These devices must be available on a chassis, module and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.7.

6.1.1.8 Enterprise Intrusion/Prevention Detection System, Licenses and Modules. This tier is the enterprise intrusion/prevention detection system, licenses and modules. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.8.

6.1.1.9 Enterprise WAN Acceleration Appliances and Licenses. This tier is the enterprise WAN acceleration appliances and licenses category. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.9.

6.1.1.10 Flexible Extender Appliance. This tier is the lowest category of flexible extender appliances. These devices must be available as all-encompassing appliances. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.10.

6.1.1.11 Network Analysis Platform, Licenses, Modules and Management Devices. This tier is network analysis platform, licenses, modules and management devices category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.11.

6.1.1.12 Enterprise Email Protection System. This tier is the enterprise email protection systems category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.12.

6.1.1.13 Email Security Appliance. This tier is the Email Security Appliance. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.13.

6.1.1.14 Data Center Console Server. This tier is the Data Center Console Server. These devices must be available on an appliance basis. For example products or equivalent list and minimum features, see Appendix 5-1, section 1, number 1.14.

6.1.2 Subtask 2 – Firewalls.

6.1.2.1 Enterprise Application Aware Firewall and Modules. This tier is the enterprise application aware firewall and module category. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 2, number 2.1.

6.1.2.2 Data Center and Enterprise Stateful Firewall, Licenses and Modules. This tier is the data center and enterprise stateful firewall, licenses and modules category. Devices must be available on a chassis, port and license basis. For example products or equivalent list and minimum features, see Appendix 5-1, section 2, number 2.2.

6.1.2.3 Enterprise Boundary Firewall, Licenses, Modules and Management Systems. This tier is the enterprise boundary firewall, licenses, modules and management systems category. These devices must be available on a chassis, line card, licenses and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 2, number 2.3.

6.1.2.4 Database Firewall and Licenses. This tier is the database firewall and licenses category. Devices should be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 2, number 2.4.

6.1.2.5 Data Center Premise Firewall and Modules. This tier is the data center premise firewall and modules category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 2, number 2.5.

6.1.2.6 Data Center VPN Firewall and Modules. This tier is the data center VPN Firewall and modules category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 2, number 2.6.

6.1.3 Subtask 3 – Load Balancers.

6.1.3.1 Data Center Load Balancer Appliances, Licenses, and Modules. This tier is the data center load balancer appliance, license and module category such as Application Security Manager, DNS Add-on, and Global Traffic Manager. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 3, number 3.1.

6.1.3.2 Modular Data Center Load Balancer. This tier is the modular data center load balances. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 3, number 3.2.

6.1.3.3 Firewall Load Balancer Appliances and Modules. This tier is the firewall load balancer appliance and module category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 3, number 3.3.

6.1.4 Subtask 4 – Modules.

6.1.4.1 Enterprise Hardware Security Module. This tier is the enterprise hardware security module category. These devices must be available on a chassis, license and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 4, number 4.1.

6.1.4.2 Flexible Extender Module. This tier is the flexible extender module category. These devices must be available on a chassis and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 4, number 4.2.

6.1.4.3 VPN and Firewall Services Module. This tier is the VPN and firewall services modules category. These devices must be available as a module. For example products or equivalent list and minimum features, see Appendix 5-1, section 4, number 4.3.

6.1.5 Subtask 5 – Routers.

6.1.5.1 Data Center Edge Router. This tier is the smallest category of data center edge router. These devices must be available on a chassis, line card and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 5, number 5.1.

6.1.5.2 Data Center Premise Router, Licenses and Modules. This tier is the data center premise router, licenses and modules category. These devices must be available on a chassis module and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 5, number 5.2.

6.1.5.3 IA Premise Router, Licenses and Modules. This tier is the IA premise router, licenses and modules category. These devices must be available on a chassis, processor and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 5, number 5.3.

6.1.6 Subtask 6 – Switches.

6.1.6.1 Campus LAN Access Layer Switch with redundant supervisors. This tier is the LAN access layer switch. These devices must be available on a chassis with supervisor, module and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.1.

6.1.6.2 Campus LAN Access Layer Switch This tier is the category of campus LAN access layer switch for both redundant and single supervisors. These devices must be available on a chassis with supervisor, module and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.2.

6.1.6.3 Campus LAN Stackable Switch. This tier is the category of Campus LAN Stackable Switch. These devices must be available on a chassis and port Model. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.3.

6.1.6.4 Data Center Collocated Switch. This tier is the lowest category of collocated switch. These devices must be available on a chassis, module and port model. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.4.

6.1.6.5 Data Replication Switch. This tier is the data replication switch. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.5.

6.1.6.6 Fabric Capable Switch. This tier is the lowest category of fabric enabled or capable switch. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.6.

6.1.6.7 Switch Fabric License and High Volume Access Control List (ACL) Feature. This tier is the switch fabric license and high volume ACL feature category. For example products or equivalent list and minimum features, see Appendix 5-1, section 6, number 6.7.

6.1.7 Subtask 7 – VoIP Equipment.

6.1.7.1 VOIP Call Manager. In a VOIP enterprise solution, a call manager is a call processing solution used to track all active VoIP network components; these include phones, gateways, conference bridges, transcoding resources, and voicemail boxes. For example products or equivalent list and minimum features, see Appendix 5-1, section 7, number 7.1.

6.1.7.2 VOIP Voicemail. In a VOIP enterprise solution, a voicemail system is required for user access to voicemail messages. A VOIP voicemail system should integrate with a call manager appliance. For example products or equivalent list and minimum features, see Appendix 5-1, section 7, number 7.2.

6.1.7.3 VOIP Automatic Call Distribution System (ACD). In a VOIP enterprise solution for ACD, the application is required to distribute incoming calls to a specific group of terminals that agents use. In an enterprise environment it should integrate with the call manager. For example products or equivalent list and minimum features, see Appendix 5-1, section 7, number 7.3.

6.1.7.4 Enterprise VOIP Phones. This tier is the enterprise VOIP phones category. These devices must be available on a per phone model. For example products or equivalent list and minimum features, see Appendix 5-1, section 7, number 7.4.

6.1.8 Subtask 8 – Software Defined Network.

6.1.8.1 Software Defined Networking (SDN). This tier is the SDN. These devices must be available as a solution model. For example products or equivalent list and minimum features, see Appendix 5-1, section 8, number 8.1.

6.1.9 Subtask 9 – Video Equipment.

6.1.9.1 Video Conference Room System. This tier is the Video Conference Room System equipment. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.1.

6.1.9.2 Video Codec. This tier is the Video Codec equipment. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.2.

6.1.9.3 Video Gatekeeper. This tier is the Video Gatekeeper equipment. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.3.

6.1.9.4 Video Gateway Server. This tier is the Video Gateway Server. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.4.

6.1.9.5 Video Portal Server. This tier is the Video Portal Server. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.5.

6.1.9.6 Video Router Server. This tier is the Video Router Server. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.6.

6.1.9.7 Video Multipoint Control Unit (MCU)/Media Gateway. This tier is the Video MCU/Media Gateway equipment. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.7.

6.1.9.8 Video Resource and Content Manager. This tier is the Video Resource and Content Manager equipment. These devices must be available as an appliance model. For example products or equivalent list and minimum features, see Appendix 5-1, section 9, number 9.8.

6.1.10 Subtask 10 – Virtual Capabilities - Appliances.

6.1.10.1 Data Center Forward Proxy Virtual Appliances, Licenses and Modules. This tier is the data center forward proxy virtual appliances, licenses and modules category. These devices must be available as a chassis and license model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.1.

6.1.10.2 Data Center SSL VPN Virtual Appliances. This tier is the data center SSL VPN virtual appliances category. These devices must be available as a chassis and license model. For example products or equivalent list and minimum features, see Appendix 5.2, section 1, number 1.2.

6.1.10.3 Enterprise Accounting, Authentication, and Authorization (AAA) Virtual Appliances, Licenses and Modules. This tier is the enterprise AAA virtual appliances, licenses and modules category. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.3.

6.1.10.4 Enterprise Application Delivery Controller Virtual Appliances and Modules. This tier is the enterprise application delivery controller virtual appliances and modules category. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.4.

6.1.10.5 Enterprise Deep Packet Inspection Virtual Appliance and Associated Devices. This tier is the enterprise deep packet inspection virtual appliance and associated devices category. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.5.

6.1.10.6 Enterprise DNS Appliances, Modules and Virtual Appliances. This tier is the enterprise DNS appliances, modules and virtual appliances category. These devices must be available as a virtual chassis and module model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.6.

6.1.10.7 Enterprise Intrusion/Prevention Detection System Virtual Appliances, Licenses and Modules. This tier is the enterprise intrusion/prevention detection system virtual appliances, licenses and modules. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.7.

6.1.10.8 Enterprise WAN Acceleration Virtual Appliances and Licenses. This tier is the enterprise WAN acceleration virtual appliances and licenses category. These devices must be available as a chassis and license model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.8.

6.1.10.9 Network Analysis Platform Virtual Appliances, Licenses, Modules and Management Devices. This tier is network analysis platform virtual appliances, licenses, modules and management devices category. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 1, number 1.9.

6.1.11 Subtask 11 – Virtual Capabilities - Firewalls.

6.1.11.1 Enterprise Application Aware Virtual Firewall and Modules. This tier is the enterprise application aware virtual firewall and module category. These devices must be available as a chassis and license model. For example products or equivalent list and minimum features, see Appendix 5-2, section 2, number 2.1.

6.1.11.2 Data Center and Enterprise Stateful Virtual Firewall, Licenses and Modules. This tier is the data center and enterprise stateful virtual firewall, licenses and modules category. Devices must be available as a chassis and license basis. For example products or equivalent list and minimum features, see Appendix 5-2, section 2, number 2.2.

6.1.11.3 Database Virtual Firewall and Licenses. This tier is the database virtual firewall and licenses category. Devices should be available as a chassis and license model. For example products or equivalent list and minimum features, see Appendix 5-2, section 2, number 2.3.

6.1.12 Subtask 12 – Virtual Capabilities - Load Balancers.

6.1.12.1 Data Center Load Balancer Virtual Appliances, Licenses, and Modules. This tier is the data center load balancer virtual appliance, license and module category such as Application Security Manager, DNS Add-on, and Global Traffic Manager. These devices must be available as a chassis and license model. For example products or equivalent list and minimum features, see Appendix 5-2, section 3, number 3.1.

6.1.12.2 Firewall Load Balancer Virtual Appliances and Modules. This tier is the firewall load balancer virtual appliance and module category. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 3, number 3.2.

6.1.13 Subtask 13 – Virtual Capabilities - Routers.

6.1.13.1 Data Center Virtual Router. This tier is the smallest category of data center virtual router. These devices must be available as a chassis model. For example products or equivalent list and minimum features, see Appendix 5-2, section 4, number 4.1.

6.1.14 Subtask 14 – Virtual Capabilities - Switches.

6.1.14.1 Campus LAN Access Layer Virtual Switch with Redundant Supervisors. This tier is the LAN access layer virtual switch. These devices must be available as a chassis with supervisor and module model. For example products or equivalent list and minimum features, see Appendix 5-2, section 5, number 5.1.

6.1.15 Subtask 15 – Virtual Capabilities - Software Defined Network

6.1.15.1 Software Defined Networking (SDN). This tier is the SDN. These devices must be available as a solution model. For example products or equivalent list and minimum features, see Appendix 5-2, section 6, number 6.1.

6.1.16 –Subtask 16– Interface/Integration with Existing DISA Network

6.1.16.1 Integration/Interfaces. All equipment provided must work with the existing DISA infrastructure. Documentation on the DISA network and interfaces in use, can be requested from the Contracting Officer/Contract Specialist.

6.1.16.2 RESERVED.

6.1.16.3 The offeror must ensure all infrastructure components provided are compatible with and operate seamlessly with DISA’s communications, processor, and storage infrastructure.

6.1.16.4 The contractor must ensure all infrastructure components in the solution involving make and model changes are coordinated with and concurred by DISA before introduction into the communications environment.

6.1.16.5 The contractor must provide migration services to ensure that syntax from DISA’s current communications environment is transferable to the vendor provided solution. All migration services are included in the “utility” pricing.

Deliverable/s: See Section 11 - Delivery Schedule for deliverable details.

6.1.17 Subtask 17- Delivery, Installation and Acceptance

6.1.17.1 Delivery. Equipment shall be properly packaged to prevent damage and marked to allow CSC II identification (ID) at the docks to include manufacturer and call order number, contract and delivery order number, and site point of contact. Site point of contact will be contacted to coordinate installation activities. The Government reserves the right to consider an alternative delivery schedule.

6.1.17.2 Installation. The contractor is responsible for installing the ordered capacity. Installation tasks include rack placement, power on and check for operational status. Installations should be performed between 0600-1800 Local Time at the requested location. The contractor shall install, power up, and confirm operational status of communications capacity. The contractor shall complete power-up configuration as detailed by the Government. The Government shall perform final configuration as required.

6.1.17.2.1 After Hours Installation. If installation is required to be accomplished after normal duty hours, the After Hours Installation Services SLINs (0015D07 in CONUS or 0015D08 OCONUS) will be ordered with the hardware capacity.

6.1.17.3 Government acceptance. The written acceptance of new capacity by the Government starts the billing cycle for this service. The Government requires the ability to place orders for new technology throughout the Period of Performance (PoP) for this contract. The contractor shall work with DISA to develop an acceptance testing methodology and smoothly transition the new (unless approved by the Government) equipment into the DISA production environment.

6.1.18 Subtask 18 - New Technology. Evolutions in communications technology may, during the life of this contract, result in the availability of equipment in the market that is determined by the Government to be in their best interest to use. Should this occur, the contractor will propose pricing for the new technology in a format suitable for Section B to add to the contract upon agreement with the Government. The contractor will describe their method of informing the Government of the availability of new technology in their proposal and will describe the method that the Government will use to request new technology. If the new technology being proposed will replace an existing technology, the unit price of new technology proposed post-award will be equal to or lower than the original unit price of similar technology and the contractor will identify how quickly the hardware will be available to the Government for release. DISA requires a semi-annual meeting with the contractor to discuss current technologies and proposed replacements based on requirements and industry marketplace developments. The contractor will highlight and describe any situations where a DISA decision to implement new technology is possible without limitations or contingencies.

6.1.19 Subtask 19- Remote Diagnostics

6.1.19.1 Diagnostics. The Government requires that all CSC II solutions be supported by remote diagnostics, administration, and tools that communicate over the DISA out-of-Band network (OOB). All CSC II communications devices will be configured to send all management traffic via a dedicated management interface or Virtual Local Area Network (VLAN) capable of isolating management traffic to the OOB network. System errors will be immediately reported to remote tools servers and service center(s). The contractor shall provide written confirmation that capacity devices delivered can be supported by remote diagnostics within 7 calendar days after start of performance.

6.1.19.2 Device deployment support. The contractor shall develop the automated workflows for all device types that are purchased using CSC II. These automated workflows will be developed and run using Government owned Hewlett-Packards’ Network Automation (HPNA) and Hewlett-Packard’s Operations Orchestrator (HPOO) servers. The configuration standards and Security Technical Implementation Guide (STIG) requirements will be set by the Government and developed by the contractor. Because each device must be provisioned with this standard STIG compliant configuration in order to be compliant on the network, the contractor is required to deliver these configurations prior to delivery of equipment.

6.1.20 Subtask 20 – Maintenance of capacity equipment. When maintenance of capacity equipment is required, contractor shall respond to DISA within the Government designated service tier level.

6.1.20.1 Service tier levels. Lower pricing will be associated with lower service tier level selected.

6.1.20.1.1 Level I (Gold) service: The contractor shall arrive within two (2) hours after being notified by the Government, to commence remedial maintenance and complete all repairs within four (4) hours after arriving on site. The total time for repair is six (6) hours.

6.1.20.1.2 Level II (Silver) service: The contractor shall arrive on-site to commence remedial maintenance on the Next-Business-Day (NBD) after being notified by the Government, and complete all repairs by 1700 hours on the Second-Business-Day (SBD) after arriving on-site. The total time for repair is two (2) business days.

6.1.20.1.3 Level III (Bronze) service: The contractor shall arrive on-site to commence remedial maintenance on the Next Business Day (NBD) after being notified by the Government, and complete all repairs by 1700 hours local time on the third business day after arriving on-site. The total time for repair is four (4) business days.

6.1.20.2 OEM agreement. For all capacity delivered, the contractor will have an OEM agreement in place to ensure uninterrupted delivery and quality of service to the Government. Copies of these agreements will be provided to the Government within 30 days of contract award.

6.1.20.3 Predictive Maintenance. If it is determined that a piece of equipment or component is about to fail or is operating outside OEM specifications, the contractor shall initiate action to effect repair even though no call for remedial maintenance has been initiated by the site service desk or shift supervisor.

6.1.20.3.1 The contractor shall call the service desk or shift supervisor to inform them that they are coming in for predictive maintenance. Upon arrival on site, the contractor’s technician shall report to the site service desk or shift supervisor to initiate the DISA Form 7 Process as defined in paragraph 6.7 and Appendix 4.

6.1.20.4 Remedial Maintenance. If needed, as determined by site personnel, calls will be initiated by the site service desk or shift supervisor to the contractor’s toll free help desk service. Contractor shall respond and make the necessary repairs in accordance with the time lines identified in the contract and specified by the service tier level selected by the Government. When necessary, the contractor shall obtain any required OEM support. The contractor shall complete remedial maintenance within the response and repair times. Upon arrival on site, contractor’s technician shall report to the site service desk or shift supervisor to initiate the DISA Form 7 Process as defined in paragraph 6.7 and Appendix 4.

6.1.21 Subtask 21 - New solution testing. New engineering solutions may require testing to evaluate proposed equipment configuration and security. The contractor shall provide equipment for testing at no cost to the Government and a DISA Product License Agreement (PLA) will be utilized.

6.1.22 Subtask 22 – Tech Refresh of Equipment. The contractor shall provide technical refreshment as new (unless approved by the Government) equipment, as equipment and/or software becomes End of Life (EOL). The old equipment/software must be replaced prior to the actual EOL date and support terminated. It is the responsibility of the contractor to track the lifecycle of all hardware/software provided through this contract and work with the Government to plan the replacement. The contractor shall work with the Government to develop an updated solution no later than 12 months of the hardware/software being identified as EOL.

6.1.23 Subtask 23 - Removal of Equipment. The contractor shall conduct any necessary de-installation and removal of hardware items on this contract upon request by the Government both during and at the end of the contract. Removal of all contractor equipment will be coordinated with the site Accountable Property Custodian (APC) or Property management group. Removal will be at no cost to the Government.

6.1.24 Subtask 24- Training . Provide in-depth detailed technical training for all provided solutions. Formal contractor provided or equivalent quality training shall be provided for all new device types. Training will be used for engineering and operations teams to become proficient in design and operating of new devices. The contractor shall provide a plan showing how they will provide training to employees prior to capacity being deployed for the first time. Additional training required by the Government must be available.

6.1.25 Subtask 25- Hardware Security

6.1.25.1 The contractor must comply with all applicable security directives, including the DoD Directive 8500.01, "Cyber Security"; the Assistant Secretary of Defense Memorandum, Subject: Disposition of Unclassified DoD Computer Hard Drives, dated June 4, 2001; DISA STIGs. All documents are available at http://iase.disa.mil.

6.1.25.2 The contractor must provide device STIG template development support as described in paragraph 6.1.19.2. The Government will routinely audit STIG templates and notify the contractor when there are deficiencies.

6.1.26 Subtask 26 – Non-Capacity Offerings.

6.1.26.1 Technical assistance support. Technical assistance may be provided on as needed basis to provide flexibility to modify services to meet the needs of DISA and its customers. The contractor will be responsible for providing technical support and/or leadership in the creation and delivery of technology solutions designed to meet the Government’s business needs. All technical assistance requirements must be documented in a statement of work to be submitted with the technical assistance call order. Technical Assistance and Consulting Support is a specified requirement needed by DISA and does not include predictive or remedial maintenance for hardware, software or release management. Technical assistance will be available on firm fixed price (FFP) hourly basis. The contractor is authorized to invoice only for hours authorized by call order.

6.1.26.1.1 The support will be divided into five levels depending upon the level of support required as described in Appendix 3, Technical Assistance and Consulting Support. The labor categories will also be used for performing services that will require a FFP effort with a detailed agreement with DISA on the scope of work.

6.1.26.1.2 The contractor will be responsible for funding any training and certification testing as well as any certification maintenance requirements for their personnel. In addition, the contractor will ensure compliance with DoD 8570.01-M Information Assurance Workforce Improvement Program. Certification must be gained within six months of contractor personnel commencing service.

6.1.26.1.3 Contractor travel shall be required to support this contract. TO related travel costs, i.e., relocation and temporary duty (TDY) to include travel, lodging and meals are reimbursable in accordance with FAR 31.205-46. No contractor travel shall be conducted to support the requirements of this PWS without advance, written approval from the Contracting Officer‘s Representative (COR) on a Travel Authorization Request (TAR).

Contractor employee travel may be required, but not limited to the primary places of performance identified in Section 9. Additionally, travel to other facilities both CONUS and OCONUS may be required.

The Contractor shall provide trip reports to the COR and KO via electronic mail no later than five (5) business days after the completion of the trip. Travel for Government meetings will be at the contractors’s expense. (See Section 6.6 Task 6.)

6.1.26.2 – Infrastructure Components.

6.1.26.2.1 Cables.

6.1.26.2.1.1 The contractor shall deliver the physical cables as a supply item, not a service. As such all cables will be owned by DISA and reused to the maximum extent possible. 6.1.26.2.1.2 CLIN/SLIN options for a variety of cable types must be available. All cabling must conform to existing DISA cabling standards. All cabling must be certified. See Appendix 7 for Cabling Specifications.

6.1.26.2.2 Cabinets and Racks.

6.1.26.2.2.1 Most cabinets will be in the data center but some will be in small communications closets where a two post solution is necessary. Wall mountable enclosures must also be available. Refer to Appendix 2 – Facilities Rack and Power Details.

6.1.26.2.2.2 All cabinets and racks shall support configurable options allowing for optimized storage of hardware. Examples of common configurable options are listed below but not limited to:

· Horizontal and vertical cable management

· Interface to overhead cable tray

· Under floor conveyance

· Front to back air flow

· Side to side air flow

· Power Distribution Unit

· Shelves

· Mounting hardware

· Jumpers

· Patch panels

6.1.26.3 Relocation. Relocation defined. Relocation refers to movement and is defined as the transfer of equipment within the same DISA site. There will be “Relocation Services” CLIN/SLIN to support this requirement.

6.1.26.3.1 Free move - The relocation CLIN/SLIN may be used for the one-time free move when requested by the Government. Free moves are defined as relocations within a single DISA approved location (CONUS & OCONUS) and can be used one time per item ordered. The call order will be modified using the relocation services CLIN/SLIN at zero cost to the Government.

6.1.26.3.2 Timeframe - Relocation must be accomplished within 10 calendar days of hardware turn-over and notification to the contractor.

6.1.26.3.3 Cost Reimbursable Move - The relocation CLIN/SLIN may be used for a cost reimbursable move when requested by the Government. Cost reimbursable moves are defined as relocations within and between DISA approved locations (CONUS & OCONUS). The equipment being relocated may be contractor owned, DISA owned or customer owned. Delivery must be accomplished within 10 calendar days of hardware turn-over to the contractor and must include appropriate packaging of equipment to prevent damage in shipment. A call order will be generated using the relocation services CLIN/SLIN and will be billed on a cost reimbursable basis. The contractor must provide actual invoice for reimbursement. Reimbursement will be based on DISA PM approved quote detailing specific move requirements. This will be a direct cost reimbursement for shipping costs and must be supported with a receipt from the shipper.

6.2 Task 2 Support.

6.2.1 Subtask 1- PMO. The contractor must establish and maintain a Program Management Office to be the single point of contact for the Government to communicate with the contractor on all matters related to the operation and execution of the contract. In the proposal, the contractor will provide a description of the organization of the PMO. They will define processes related to providing service and support and address relevant functions including how to request capacity, report capacity failures, request technical assistance and relocation services, request supply items such as cables and racks, resolve monthly invoice questions, report installed inventory, escalate emergency issues and other related items. The contractor will describe any methods they will utilize to provide continuous, responsive action when needed, including backups for PMO functions, experience and certifications possessed by the PMO members, how security requirements for labor will be met, contract administration including scope and modification discussions, if they arise, and subcontractor management.

6.2.2 Subtask 2- Technical assistance center (TAC). Standard commercial communications technical support, such as call center support and firmware updates, must be provided at no additional charge to the Government. The call center must be manned by United States Citizens with the ability to hold the required clearance level. (Secret IT-1 for system access and Secret IT-2 for all other CSC II support). The contractor will provide a multi-level solution for response after being notified by the Government, to commence remedial maintenance for hardware and any software required for the contractor solution to operate. Each orderable system will be identified to a level of response based on Government need. All maintenance requirements are included in the “utility” pricing.