ATTACHMENT 1 - Performance Work Statement.docx

PERFORMANCE WORK STATEMENT (PWS)

Award

1. Contracting Officer’s Representative (COR).

a. Primary COR. See Points of Contact in Contract Administration Data

b. Alternate COR (ACOR). See Points of Contact in Contract Administration Data

c. Property Administrator (PA).

2. Contract Title. Capacity Services Communications III (CSC III).

3. Background. DISA is a provider of information technology solutions for the Department of War (DoW). DISA and its Mission Partners 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. CSC provides state-of-the-art communications infrastructure capacity to meet new and emerging 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. Objective. The purpose of this indefinite delivery/indefinite quantity (ID/IQ) 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 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.

5. Scope. The scope of this contract includes the hardware, operating software, storage, network management tools and software, automation tools and software, and technical services required to deliver DISA the flexibility to meet the requirements of security, availability, scalability, and modernization of the communication infrastructure for data centers and hybrid-cloud solutions.

5.1 Unclassified Scope. The contractor must support the controlled unclassified level environments listed below. The platforms and software listed are current, but the capacity delivered must be compatible with future requirements. The Government may need the contractor to support additional operating system software throughout the period of performance due to changes in operating environments. If necessary, these changes will be incorporated through a contract modification.

5.1.1. The hardware, chipsets, and operating environments requiring communications infrastructure support for DISA are:

IBM System z (IBM z/OS, IBM z/VM, Red Hat Enterprise Linux, SUSE Linux Enterprise server) X-86 Windows Server Red Hat Enterprise Linux SUSE Linux Enterprise Server Solaris VMware vSphere Enterprise Plus Red Hat OpenShift Itanium (HP-UX) SPARC (Solaris) IBM System p (AIX) Cloud Service Providers

5.2 Classified Scope. The contractor must support the classified level environment, including all the items listed in section 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 up to TOP SECRET. System access is required for the contractor to perform their duties in environments classified as SECRET. This includes accounts to use a Government Furnished Equipment (GFE) laptop computer to login into the SIPRNET Out of Band (OOB) Virtual Private Network (VPN) and attached Authentication Servers (ACS) to audit and verify configurations on attached communications network devices. Because privileged (administrator) rights are required for this type of access, contractor employees must possess SECRET level clearances. Additionally, the contractor will access the SIPRNET Ports and Protocols Security Management (PPSM) system to register internet protocol (IP) addresses for device setup.

5.2.2. If the Government requires the contractor to install communications capacity in an environment classified as higher than SECRET, the contractor does NOT require system access and contractor employees do NOT require a clearance level higher than SECRET. The Government will escort the contractor into the area to perform physical installation tasks only, which include placement of the equipment and connection of required power and cables. Contractor employees must not perform physical installation tasks in an environment classified as higher than SECRET without a Government escort. Government personnel will assume any tasks requiring system access.

5.3 Contractor Responsibilities. For all communications capacity requirements, the contractor must acquire, transport, and provide the necessary hardware (such as cabinets, racks, cabling, cable management, and power distribution units (PDUs)), hardware maintenance, communications operating software and service to support the communication infrastructure associated with this contract as a capacity service. Communications capacity requirements as defined in PWS paragraph 5.5 can be ordered in the base period and all option periods. The contractor’s pricing for services in the base and option periods must include full communication capacity services as outlined in paragraph 5.5 below. The contractor must also provide, when ordered by the Government, cabinets, racks, cabling, and other infrastructure items as supply items to be owned and retained by the Government.

5.4 Government Responsibilities. The Government is responsible for the day-to-day operational control of the environment where the communication equipment will reside. Operational control includes tasks related to daily operations such as monitoring activities, configuration changes based on Government requirements, and applying operating software updates the Government receives from the contractor.

5.5 Communication Capacity Services. The contractor must provide communication capacity services using a “utility use concept” and the capacity assets needed for the service. Assets provided as a utility include hardware, software, software maintenance and licensing, logistical support, field maintenance, systems engineering support, and other asset types as required by the Government. The contractor must clearly identify what make and model is being proposed to satisfy all requirements, including hardware or software required to meet the requirements of this PWS as defined in section 6.1.

5.6 Hardware. The contractor cannot use communication hardware currently installed in DISA locations to satisfy the requirements of this contract. The contractor may reutilize hardware previously returned under this contract to support the service if the technology has only been utilized on Government networks, Government approval is sought and received, and it is not a product that the Original Equipment Manufacturer (OEM) has withdrawn from support.

5.7 Communication Infrastructure. The scope of this contract covers both present and future DISA 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.

5.8 Post Award. All requirements must be staffed through the contractor and Government Program Management Offices. Any contractual requirement submitted via another source (e.g., sales) will not be accepted by the Government.

5.9 Status of Forces Agreement. The Government will afford the contractor protection under the DoW Status of Forces Agreement (SOFA) with Outside the Continental United States (OCONUS) host countries that have an existing SOFA with the U.S. When applicable and upon the request of the contractor, the Government will provide the contractor with documentation to assist with obtaining exemptions from local taxes, value-added taxes, excise taxes, and/or other taxes or tariffs incurred in the performance of this contract; however, the Government makes no guarantees that the contractor will be exempted. Taxes will be treated in accordance with FAR 52.212-4 and FAR 52.229- 3.

5.10 Current Environment. DISA currently provides communication capacity services at multiple computing facilities in both the Continental U.S. (CONUS) and OCONUS locations.

5.10.1 DISA Host and Compute Center managed locations in the CONUS:

1) Columbus, OH: DISA Columbus, 3990 East Broad St., Bldg. 23, Columbus, OH 43213

2) Pensacola, FL: DISA Chief Financial Executive, Cfeh91, 45 Industrial Blvd, Suite C, Pensacola, FL 32503

3) Mechanicsburg, PA: DISA Mechanicsburg, Bldg. 308 North End, 5450 Carlisle Pike, Mechanicsburg, PA 17050-0975

4) Montgomery, AL: DISA Montgomery, 401 East Moore Drive, Bldg. 857, Maxwell AFB/Gunter Annex, Montgomery, AL 36114-3001

5) Ogden, UT: DISA Ogden, 7879 Wardleigh Road, Bldg. 891, Hill AFB, UT 84056-5996

6) Oklahoma City, OK: DISA Oklahoma City, Gate 33, Se59 And Air Depot Rd, 8705 Industrial Blvd., Bldg. 3900, Tinker AFB, Oklahoma City, OK 73145-3064

7) San Antonio, TX: DISA San Antonio, 3326 General Hudnell Dr, San Antonio, TX 78226-2023

5.10.2 DISA Host and Compute Center managed locations in the OCONUS:

1) Stuttgart, GE: DISA DATA CENTER Stuttgart, Bldg. 2324, Patch Barracks, Stuttgart, Germany 70569

2) Wiesbaden, GE: DISA DATA CENTER Wiesbaden SEL4E3, MCC Gebaude 1000 Room OC01, Flugplatz Erbenheim, 65205 Wiesbaden, Germany

3) Ford Island, HI: Core Data Center-Hawaii, 477 Essex Street, Bldg. 77, Room 180, Pearl Harbor (Ford Island), HI 96860

4) Bahrain: TECC NSA Bahrain: PSC 451 Box 200, Kingdom of Bahrain

5) Al Udeid AB: 379/ECS/SCPF/GDIT AL UDEID AB, DOHA, QATAR 09309

6) Yokota Air Base, Japan: DISA Data Center – Yokota, Bldg. 650 Room B29, Bong Street, Yokota-kichiani, Fussa-shi, Tokyo-to, Japan 197-0001

5.10.3 SCCA Off-Prem Cloud Access Point locations:

1) Ashburn, NC: Equinix Datacenter DC11, 21721 Filigree Court, Ashburn VA 20147

2) Chicago, IL: Equinix Datacenter CH3, 1905 Lunt Avenue, Elk Grove Village, IL 60007

3) Dallas, TX: Equinix Datacenter DA6, 1950 North Stemmons Freeway, Dallas, TX 75207

4) San Jose, CA: Equinix Datacenter SV5, 9 Great Oaks Boulevard, San Jose, CA 95119

5.10.4 Mission Partner sites – Up to 254 worldwide.

5.10.5 Future locations. The contractor must have the ability to install and operate their communications solution(s) at government approved locations worldwide where the Government may acquire an operational responsibility.

6. Performance Requirements.

6.1 TASK 1 – Capacity Offerings.

6.1.1 Communication Capacity. The contractor must provide communication capacity as an “on-demand” service capable of readily adjusting to changes in requirements, including both increases and decreases. The Government will determine the need for additional capacity and/or communication equipment. The contractor must provide flexible, highly scalable, solutions that are non-disruptive. Examples are provided in Appendix 1 as a sampling of the current hardware deployed within the DISA environment.

6.1.2 Primary Offerings. Appendix 5 lists categories of services required for the Primary Offerings corresponding to SLINs and the minimum features for each category.

6.1.2.1 General Requirements.

6.1.2.1.1 Power. All physical solutions provided by the contractor must support redundant power. Redundant power supplies internal to the chassis is the preferred method of achieving redundant power. However, a vendor-supplied, rack-mounted Automatic Transfer Switch (ATS) included in the base solution is acceptable for solutions which are not capable of internal redundancy. The remote managed power distribution units (mPDU) in Appendix 5, Section 0001G are exempt from this requirement.

6.1.2.1.2 Installation Accessories. All physical Primary Offerings provided by the contractor must include all required accessories for installation, to include rack-mount kits and power cables, as part of the base solution.

6.1.2.1.3 Remote Diagnostics. The contactor must support all CSC solutions by remote diagnostics, administration, and tools that communicate over the DISA management network. The contractor must configure all CSC communications devices to send all management traffic via a dedicated management interface or Virtual Local Area Network (VLAN) capable of isolating management traffic to the management network. The contractor must immediately report system errors to remote tools servers and service center(s).

6.1.2.2 Solution Minimum Requirements. The contractor’s proposed solutions must meet the minimum requirements in Appendix 5. The Government will deem any solution that can meet the device requirements and complement the existing infrastructure as a suitable fit.

6.1.2.3 Example Products. Appendix 5 contains example products to demonstrate the type of device for each category. The example products listed in Appendix 5 are examples only and are not intended to represent products that will meet specifications. It is the responsibility of the contractor to validate that product specifications meet the Government’s requirement.

6.1.3 Emerging Technology Offerings. Due to ever-changing communications requirements to meet the needs of DISA and its Mission Partners, the Government may need the contractor to add new solutions to the ID/IQ contract. The purpose of the Emerging Technology Offerings is to provide the Government the flexibility needed to meet new short-notice requirements and keep pace with industry and service requirements.

6.1.3.1 Usage. The Emerging Technology Offerings shall be used for time-sensitive requirements. Once made available on contract, Emerging Technology Offerings are subject to all applicable contract requirements for capacity, including support, installation, and renewals. The Emerging Technology Offerings will be made available using the appropriate Emerging Technology SLIN available in each category.

6.1.3.2 Minimum Requirements. The Emerging Technology Offering solutions must meet the requirements presented for the specific project.

6.1.4 Managed Solutions. To keep pace with industry, the Government may request new solutions be made available on contract as Managed Solutions. The Government will request Managed Solutions either through Emerging Technology Offerings for time-sensitive projects or through contract modifications as requirements are defined.

6.1.4.1 Usage. Once made available on contract, Managed Solutions are subject to all applicable contract requirements for capacity, including support, installation, and renewals. The contractor must provide the management of the service.

6.1.4.2 Minimum Requirements. The Government will define Managed Solution requirements for each effort upon contract modification or for each Emerging Technology project.

6.1.5 Capacity Support. The contractor must include U.S.-only OEM support with all capacity offerings; however, the Government may grant exceptions to this requirement. For all capacity delivered, the contractor must have an OEM agreement in place to ensure uninterrupted delivery and quality of service to the Government. The contractor must provide copies of these agreements to the Government within 30 days of contract award.

6.1.5.1 Service Tiers. The contractor must provide the following tiers of OEM service and response for each solution as applicable:

Level I (Gold) service: The contractor must provide 24x7x365 premium OEM phone support with Same Business Day Return Merchandise Authorization (RMA) service for physical hardware. The contractor must be on site within two hours of delivery of replacement hardware or at the start of a government coordinated maintenance window to perform remedial maintenance. On site labor support may be waived by the Government.

Level II (Silver) service: The contractor must provide 24x7x365 premium OEM phone support with Next Business Day RMA service for physical hardware. The contractor must be on site within four hours of delivery of replacement hardware or at the start of a government coordinated maintenance window to perform remedial maintenance. On site labor support may be waived by the Government. Virtual solutions which do not include any hardware are exempt from the RMA requirement.

Level III (Bronze) service: The contractor must provide 8x5 OEM phone support with Next Business Day RMA service for physical hardware. The contractor must be on site within four hours of delivery of replacement hardware or at the start of a government coordinated maintenance window to perform remedial maintenance. On site labor support may be waived by the Government. Virtual solutions which do not include any hardware are exempt from the RMA requirement.

6.1.5.2 Remedial Maintenance. If needed, as determined by site personnel, calls will be initiated by the Government to the contractor’s toll-free help desk service. The contractor must respond and make the necessary repairs in accordance with the timelines identified in this PWS and as specified by the service tier level selected by the Government.

PWS

Task# Deliverable Title

6.1.5

CDRL

A001

OEM

agreements Contractor format in PDF or MS Word file.

Within 30 calendar days of award.

6.1.6 Technology Refresh (Tech Refresh) of Equipment.

6.1.6.1 Life Cycle Management. For all capacity offerings, the contractor must track the life cycle of all solutions, to include published end of sale, end of software maintenance, end of vulnerability support, and end of support dates.

6.1.6.2 Solution Replacement Availability. Once an offered solution is no longer available for sale, the contractor must coordinate a replacement solution with the Government. The replacement solution will be made available on contract with the same technical requirements and at an equitable price to the replaced solution and utilize the same SLIN. The Government retains final approval for all replacement solutions.

6.1.6.3 Tech Refresh Initiation.

6.1.6.3.1. Six months prior to an offered solution reaching end of software maintenance or end of vulnerability support, the contractor must initiate a Tech Refresh project in coordination with the Government.

6.1.6.3.2. The Government will establish project timelines.

6.1.6.3.3. The contractor must provide the approved replacement solution for each affected call order in accordance with project timelines.

6.1.6.3.4. For solutions which are issued both end of software maintenance and end of vulnerability support dates by the OEM vendor, the contractor must use the earliest date to initiate a Tech Refresh. However, the Government may elect to defer to the latter date.

6.1.6.4. Any call orders and/or call order amendments issued for a Tech Refresh Project must not result in increased costs that are duplicative in nature for the affected service, such as an overlap of equipment or software license periods.

6.1.7 Structure. The contractor must provide capacity offerings as both physical and virtual solutions as structured in PWS Appendix 5. Physical and Virtual capacity offerings will use SLINs from the B-table in the corresponding category and subcategory. Capacity offerings will use the following structure:

Category Number – Description

000 - Physical Capacity 0001 - General Appliances

· 0001A - Enterprise Wide-Area Network (WAN) Acceleration Appliances and Licenses

· 0001B - Data Center Console Server

· 0001C - Data Center Circuit to IP Converter Appliance

· 0001D - Enterprise Network Policy Compliance Appliance and Licenses

· 0001E - Mobility Controller Appliance

· 0001F - Enterprise Time Server Appliance, Licenses, and Accessories

· 0001G - Remote-managed mPDU

· 0001Z - Physical Emerging Tech - General 0002 - Firewalls

· 0002A - Layer 7 Firewall

· 0002B - Network Stateful Firewall, Licenses, and Modules

· 0002C - Boundary Firewall, Licenses, Modules, and Management Systems

· 0002D - Data Center Premise Firewall Device and Modules

· 0002Z - Physical Emerging Tech – Firewalls 0003 - Load Balancers

· 0003A - Application Delivery Controller Appliances, Licenses, and Modules

· 0003B - Modular Data Center Load Balancer

· 0003C - Enterprise Load Balancer and Modules

· 0003Z - Physical Emerging Tech - Load Balancers 0004 - Security

· 0004A - Intrusion Detection Systems

· 0004B - Intrusion Detection System Management Appliance

· 0004C - Intrusion Detection System Transceivers

· 0004D - Next Generation Security Gateway

· 0004E - Accounting, Authentication, and Authorization (AAA) Appliance

· 0004F - Two Factor Authentication Management

· 0004Z - Physical Emerging Tech - Security 0005 - Routers

· 0005A - Data Center Edge Router

· 0005B - Premise Router, Licenses, and Modules

· 0005Z - Physical Emerging Tech – Routers 0006 - Non-Software Defined Networking (Non-SDN) Switches

· 0006A - Campus LAN Switch

· 0006B - Campus LAN Switch Transceivers

· 0006C - Non-SDN Fabric Spine Switch

· 0006D - Non-SDN Fabric Leaf Switch

· 0006E - Non-SDN Fabric Flexible Extender Appliance

· 0006F - Non-SDN Fabric Switch Transceivers

· 0006Z - Physical Emerging Tech - Switches 0007 - Software Defined Networking (SDN)

· 0007A - SDN Controllers

· 0007B - SDN Fabric Spine Switches

· 0007C - SDN Fabric Leaf Switches

· 0007D - SDN Fabric Flexible Extender Appliance

· 0007E - SDN Transceivers

· 0007Z - Physical Emerging Tech - SDN 0008 - Domain Name System (DNS)

· 0008A - Enterprise DNS Appliances

· 0008B - Enterprise DNS Management

· 0008C - Enterprise DNS Reporting and Collection

· 0008D - Enterprise DNS Transceivers

· 0008Z - Physical Emerging Tech - DNS 0009 - Network Packet Capture (NPC)

· 0009A - Traffic Matrix Switching Node, Modules, and Licenses

· 0009B - Traffic Matrix Management Appliance

· 0009C - Traffic Matrix Modular Taps

· 0009D - Traffic Matrix Transceivers

· 0009E - Network Monitoring Switches

· 0009F - Network Monitoring Aggregation Appliance

· 0009G - Network Monitoring Analysis Appliances

· 0009H - Network Monitoring Fiber Taps

· 0009I - Network Monitoring Copper Taps

· 0009J - Network Monitoring Transceivers

· 0009Z - Physical Emerging Tech - NPC 0010 - Email

· 0010A - Enterprise Email Protection System

· 0010Z - Physical Emerging Tech - Email 0011 - Virtualization Platforms

· 0011A - Branch Network Virtualization Platform

· 0011B - Data Center Network Virtualization Platform

· 0011Z - Physical Emerging Tech - Virtualization Platforms 0012 - Voice over IP (VoIP) Equipment

· 0012A - VoIP Call Manager (Appliance)

· 0012B - VoIP Voicemail (License/Module)

· 0012C - VoIP Automatic Call Distribution System

· 0012Z - Physical Emerging Tech – VoIP 0013 – Infrastructure Storage

· 0012A – Infrastructure Storage

100 - Virtual Capacity 1001 - General Virtual Appliances

· 1001A - Enterprise WAN Acceleration Virtual Appliances and Licenses

· 1001Z - Virtual Emerging Tech - General 1002 - Virtual Firewalls

· 1002A - Layer 7 Virtual Firewall

· 1002B - Network Stateful Virtual Firewall

· 1002C - Boundary Virtual Firewall

· 1002Z - Virtual Emerging Tech - Firewalls 1003 - Virtual Load Balancers

· 1003A - Data Center Load Balancer Virtual

· 1003B - Enterprise Application Delivery Controller Virtual Appliances and Modules

· 1003C - Containerized Load Balancer

· 1003Z - Virtual Emerging Tech - Load Balancers 1004 - Virtual Security

· 1004A - Intrusion Detection System Virtual Appliances

· 1004B - Intrusion Detection System Management Virtual Appliances

· 1004C - Account, Authentication, and Authorization Virtual Appliances

· 1004D - Two Factor Authentication Management Virtual

· 1004Z - Virtual Emerging Tech - Security 1005 - Virtual Routers

· 1005A - Virtual Data Center Router and Licenses

· 1005B - Virtual Edge SD-WAN Router

· 1005Z - Virtual Emerging Tech - Routers 1006 - Virtual Switches

· 1006Z - Virtual Emerging Tech - Switches 1007 - Virtual SDN

· 1007A - SDN Centralized Controller Virtual

· 1007Z - Virtual Emerging Tech - SDN 1008 - Virtual DNS

· 1008A - Virtual Enterprise DNS Appliances

· 1008B - Virtual Enterprise DNS Management

· 1008C - Virtual Enterprise DNS Reporting Collectors

· 1008Z - Virtual Emerging Tech - DNS 1009 - Virtual NPC

· 1009A - Virtual Traffic Matrix for Private Cloud

· 1009B - Virtual Traffic Matrix for Commercial Cloud (Gov Cloud Environments)

· 1009C - Virtual Traffic Matrix Management Appliance

· 1009Z - Virtual Emerging Tech - NPC 1010 - Virtual Email

· 1010A - Virtual Email Security Appliance

· 1010B - Virtual Email Security Management Appliance

· 1010C - Virtual Enterprise Email Protection System Appliance

· 1010Z - Virtual Emerging Tech - Email 1011 - Virtual Network Management

· 1011A - Virtual Network Virtualization Platform Management

· 1011B - Virtual Network and Security Analytics Solution

· 1011Z - Virtual Emerging Tech - Network Management 1012 - Cloud and Automation

· 1012A - Automation Platform - Virtual

· 1012B - Secret Manager - Virtual

· 1012C - System Management Software - Virtual

· 1012D - Hybrid Cloud Container Platform - Virtual

· 1012E - Distributed Event Store and Stream-Processing Platform

· 1012F - Distributed Time-Series Data Store

· 1012G - Centralized Analytics Platform

· 1012Z - Virtual Emerging Tech - Cloud and Automation 1013 - Certificates

· 1013A - Commercial Certificates - Standard

· 1013B - Commercial Certificates - Wildcard

· 1013Z - Virtual Emerging Tech – Certificates

6.1.8 Integration with Existing DISA Network and Migration Services.

6.1.8.1. The contractor must ensure the provided solutions will integrate with the existing DISA solutions of the same type (e.g., the proposed Domain Name System/IP Address Management (DNS/IPAM) solution must integrate with the existing DNS/IPAM solution, and the proposed switching solution must integrate with the existing switching solution).

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

6.1.8.3. The contractor must ensure all changes to infrastructure component make and models are tested and coordinated with and concurred by DISA before introduction into the communications environment. After testing, coordination, and concurrence for a make and model change, the contractor must provide an updated list of the make and models.

6.1.8.4. 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, including tools required to perform the services, must be included in the utility pricing. At contract award, the contractor must provide a written document containing their migration services strategy as it was described in their proposal. The contractor must provide, install, and initially configure any tools or hardware needed for the migration services. however, any software tools installed on government issued workstations required for the migration services will be provided by the contractor and approved and installed by the Government.

PWS

Task#

6.1.8.4

CDRL

A002 Migration solution

6.1.9 Removal of Equipment. The contractor must 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 or Property management group. Removal will be at no cost to the Government.

6.2 TASK 2 – Non-Capacity Offerings.

6.2.1 Technical Assistance.

6.2.1.1 Technical Personnel. The Government may require Technical Personnel to modify services to meet the needs of DISA and its Mission Partners. The contractor must provide technical support in the creation and delivery of technology solutions designed to meet the Government’s business needs. The Government will identify all requirements for Technical Personnel support. The contractor must provide all tasks based on the Government requirements in a statement of work that will be approved by the Government and included with the Technical Assistance call order. The call order will not exceed a period of performance of 12 months. Technical Personnel support does not include predictive or remedial maintenance for hardware, software, or release management. Technical Personnel support will be available on firm fixed price (FFP) hourly basis.

6.2.1.1.1. For each Technical Assistance call order, the Government will reimburse the contractor only for hours consumed per billing cycle and not exceed the hours authorized on the call order.

6.2.1.1.2. The Technical Assistance will be divided into eight levels depending upon the level of support required as described in Appendix 4, Technical Assistance Support. The contractor must also use the labor categories in Appendix 4 when performing such services.

6.2.1.2 OEM Professional Services. OEM Professional Services will be used to obtain engineering and/or deployment support from manufacturers as needed by the Government. The Government will identify all requirements for OEM Profession Services. The contractor must provide all tasks based on the Government requirements in a statement of work that will be approved by the Government and included with the Technical Assistance call order. The contractor must establish the service and agreements with the manufacturer. OEM Professional Services will be available via an hourly rate established at the time of procurement. The Government will reimburse the contractor only for hours consumed per billing cycle and not to exceed the hours authorized on the call order.

6.2.1.3 Training and Certification. Contractors required to support this contract will comply with Training and Certification requirements as detailed in 6.3.4.

6.2.1.4 Travel. The contractor may need to travel locally to and around the places of performance throughout the period of performance; the Government will not reimburse the contractor for this travel. The contractor may need to travel long distances within CONUS or OCONUS to support the requirements of this PWS. For Technical Assistance call orders, the Government will reimburse the contractor for long-distance travel-related costs in accordance with FAR 31.205-46. The contractor must not travel to support the requirements of this PWS without advance, written approval from the Contracting Officer Representative (COR) on a Travel Authorization Request (TAR).

Should the travel expenses exceed the amount authorized in the TAR or the associated call order, the contractor must submit a travel report to the COR and KO via electronic mail no later than five business days after the completion of the trip. This report must include a detailed written justification for the excess costs, a complete travel itinerary, and all corresponding itemized receipts for lodging, transportation, and any other expenses to substantiate the claim.

Travel for Government meetings will be included in the utility pricing of the contract (See Section 6.6).

PWS

Task#

6.2.1.4

CDRL

A003

6.2.2 Infrastructure Components.

6.2.2.1 Cables. The contractor must deliver the physical cables as a supply item, not a service, when ordered by the Government. Supply item requirements will be ordered through a one-time charge call order. As such these cables will be allocated/owned/retained by the Government. All cabling must conform to existing DISA cabling standards. All cabling must be certified. See Appendix 7 for Cabling Specifications.

6.2.2.2 Racks and Rack Accessories. The contractor must deliver racks and associated components in support of this contract as supply items, not a service when requested by the Government. Supply item requirements will be acquired through a one-time charge call order. As such these cabinets, racks and associated components will be allocated/owned/retained by the Government. 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 Appendix 3 – Facilities Power Details. All cabinets and racks must support configurable options allowing for optimized storage of hardware. Examples of common configurable options include:

· Horizontal and vertical cable management

· Interface to overhead cable tray conveyance

· Under floor conveyance

· Front to back air flow

· Side to side air flow

· Shelves

· Mounting hardware

· Jumpers

· Patch panels

6.2.3 Relocation.

6.2.3.1 Relocation defined. Relocation refers to movement and is defined as the transfer of equipment within the same DISA site or between sites. The “Relocation Services” CLIN/SLIN supports this requirement. The contractor must complete relocation within 10 calendar days of hardware turn-over and notification from the Government.

6.2.3.2 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 once per item ordered. The call order will be modified using the relocation services CLIN/SLIN at zero cost to the Government.

6.2.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. The contractor must complete delivery 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 reimbursement will be based on a quote provided by the vendor and approved by the Government that outlines specific moving requirements and associated costs. The reimbursement will cover direct shipping costs only and must be accompanied by a receipt from the shipping provider as proof of payment when invoiced to the Government.

6.2.4 Restitution.

6.2.4.1 Restitution defined. Restitution refers to recoupment of losses imposed by the Government as described in the scenarios below. The Government will add a restitution SLIN to the affected call order via an amendment. Pricing of the restitution SLIN will be calculated when the call order amendment is generated and will be based on the depreciated value of the assets involved, minus the total amount previously paid by the Government for the service. Depreciation will be calculated by the contractor IAW DoD FMR 7000.14-R, Vol. 12, Ch.7 and approved by the Government.

6.2.4.2 Restitution Scenarios defined

6.2.4.2.1 Property Loss by Government. The Property Loss by Government restitution SLIN will be used when a contractor owned asset is lost by the Government. This SLIN cannot be used to recoup losses for property not in the Government’s possession, damaged by vendor or carrier actions, nor required by Government policy (e.g., hard drive destruction). Proper documentation showing the asset was in Government possession, such as Proof of Delivery from the carrier showing the asset was delivered to the proper facility and signed for by authorized personnel at the destination facility, should be submitted to the COR and Government Program Manager for the call order amendments using this SLIN.

6.2.4.2.2 Early Return for Non-reusable Items. The Early Return for Non-reusable Items SLIN will be used when the Government returns an asset that cannot be reused to fulfill another service, such as SSL certificates which are issued for specific domains. This SLIN cannot be utilized to recoup costs of reusable assets.

6.2.5 Structure. Non-Capacity offerings will use SLINs from the B-table in the corresponding category and subcategory. Non-Capacity offerings will use the following structure:

Category Number – Description

200 - Non-Capacity 2001 - Technical Assistance

· 2001A - Technical Personnel

· 2001B - OEM Professional Services

· 2001C - Travel 2002 - Restitution

· 2002A - Property Loss by Government

· 2002B - Early Return of Non-Reusable Items 2003 - Relocation

· 2003A - Relocation Services 2004 - Infrastructure Components

· 2004A - Rack/Cabinets

· 2004B - Rack Accessories

· 2004C - Cables

· 2004D - Conveyance

· 2004E - Disposable Technology

6.3 TASK 3 – Program and Project Management.

6.3.1 Program Management Office (PMO). The contractor must establish and maintain a PMO 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, to include service and support; the Government’s requests for capacity; reporting capacity failures; relocation services; supply items such as cables and racks; resolving monthly invoice questions; reporting installed inventory; escalating emergency issues; and other related items outlined in the PWS.

6.3.2 Technical Assistance Center (TAC). Standard commercial communications technical support, such as call center support and firmware updates, must be provided to the Government. The contractor must provide a call center located in the U.S. and staffed with U.S. citizens. The contractor must 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. The contractor must include all maintenance requirements in the utility pricing. The contractor must provide a24x7/365 problem escalation/resolution support services including POCs, phone numbers and escalation chart.

6.3.3 Engineering Support. The contractor must provide specialized engineering support to evaluate existing infrastructure solutions to properly engineer future technology. Engineers will be authorized to make changes to the DISA Data Center communications infrastructure if they are following documented change policies.

6.3.3.1 Experience.

6.3.3.1.1. The contractor’s Engineering Support team must have extensive knowledge of large data center and enterprise networks.

6.3.3.1.2. The contractor’s Engineering Support team must consist of at least one network systems architect fully versed in industry design standards for architectures including on-prem data center and campus networks, cloud, and hybrid cloud.

6.3.3.1.3. The remaining contractor employees on the Engineering Support team must be senior level network engineers with design experience.

6.3.3.2 Locality. Most engineering support provided by the contractor must be collocated with a DISA facility for access to classified environments. The remaining engineering support provided by the contractor may be remote or local area at the contractor’s discretion to bolster engineering support for unclassified environments.

6.3.3.3 Sizing. The number of engineers provided for Engineering Support is at the discretion of the contractor. The contractor may scale the number of engineers as needed to perform the associated tasks as detailed in PWS Section 6.3.3.

6.3.3.4 New Technology. The contractor must recommend new solutions as technology and requirements change and will assist DISA with testing new solutions as well as documenting engineering design guides that will aid implementation of new technologies. The Government retains final decision authority on all design change recommendations.

6.3.3.5 Mission Partner Engineering Support. Engineering support personnel will develop solutions for Mission Partner requirements as requested by the Government. Government communications engineers assigned to Mission Partner projects will engage the contractor Engineering Support team as needed to verify solutions proposed to meet Mission Partner projects.

6.3.3.6 Technology Failure. The contractor must perform Root Cause Analysis (RCA). The contractor must provide RCA when requested by the Government for all failures that occur on the contractor provided solutions within five business days of Government request. The RCA must include the reason for the failure, lessons learned, corrective actions/mitigations, timeline to implement corrective actions/mitigations, and updated procedures.

PWS

Task#

6.3.3.6

CDRL

A004

6.3.3.7 Capacity Planning. To facilitate cost effectiveness and capabilities of the solutions provided, the contractor must monitor the solutions in use for underutilized and overutilized assets. The contractor must provide a monthly capacity report detailing under and over-utilized assets, assets nearing performance thresholds, and summary recommendations for downgrades and upgrades to be considered by the Government. The Government has final decision authority for courses of action regarding the contractor’s recommendations.

6.3.3.8 Managed Solutions. For any managed solutions executed, the contractor must include personnel with the service to manage the solution. Personnel for managed solutions are subject to all Training and Certification requirements outlined in PWS section 6.3.4.

PWS

Task#

6.3.3.7

CDRL

A005

6.3.4 Training and Certification.

6.3.4.1. The contractor must meet all DoD 8140 requirements as detailed in PWS section 12.

6.3.4.2. The contractor is responsible for ensuring all contractor personnel complete all training and certification testing required to meet the performance standards under this PWS or comply with U.S. Government or DoW policy, regulations, or law.

6.3.5 Capacity Training. The contractor must provide in-depth detailed technical training to the Government for all solutions provided (to include any proposed (see PWS section 6.1) or new devices and capacities) as part of their utility pricing. The Government’s engineering and operations teams will use the training to become proficient in the design and operation of new devices. The contractor must provide a plan showing the methodology on how they will provide training to the Government prior to the capacity being deployed for the first time.

6.3.6 Testing/Lab Equipment. The contractor must provide the ability for the Government to test newly released communications equipment in a lab setting for a three-to-six-month period as requested by the Government. The Government may or may not decide to utilize this equipment in a production setting based on test results from the lab environment.

PWS

Task#

6.3.5

CDRL

A006

6.4 TASK 4 – Ordering.

6.4.1 Call Order Management System (COMS). The contractor must deliver a secure and/or Common Access Card (CAC)-enabled web-based, call order management system capable of creating, amending, canceling, tracking, and accepting all call orders. This call order management system must be available for demonstration within 30 calendar days after award and must be available for use within 60 days. This system will be utilized by DISA to create and place call orders (including cancelations and amendments), document and update order status, and track financial data associated with the call order. The COMS must meet the following requirements.

6.4.1.1 Hosting/Security Requirements. If the system runs within a DISA facility, the system must be CAC- authenticated and must follow DISA Security Technical Implementation Guides (STIG). If the system runs within a DISA facility, the system will be subjected to the DoD Risk Management Framework (RMF) accreditation processes as well as relevant DISA security policies. If the system runs outside of a DISA facility, the system must be secure and authenticate users to ensure a secure system.

6.4.1.2 Functionality Requirements. The COMS must be able to handle the complete order process to include the following: ordering, order validations, invoicing, billing, returns, financial tracking, and contractor asset management, throughout the life of the contract. This system will include fields for tracking orders, assigning DISA internal tracking numbers, and call order status.

6.4.1.2.1. The COMS must track equipment moves to include the equipment moved, date(s) of move(s), which site equipment is moved from, and which site the equipment is moved to.

6.4.1.2.2. The COMS will include the ability to cancel existing equipment/workload and remove capacity services gear from the DISA site.

6.4.1.2.3. The COMS will manage excess hardware and software licenses. Excess hardware and software will be defined as any hardware and/or software that has received a ‘cancelation’ request via the call order process. This equipment will be marked in the call order management system appropriately to include cancelation date and date removed from DISA location.

6.4.1.2.4. The COMS must be able to track excess hardware and software for re-utilization.

6.4.1.2.5. The COMS will contain no more than two decimal places in the financial data.

6.4.1.2.6. The COMS will have functionality for all pricing changes.

6.4.1.2.7. The COMS should support up to 20 DISA concurrent users in addition to the number of contractor concurrent users required and be scalable to support future growth. The total number of users will vary over the life of the contract.

6.4.1.2.8. The COMS will distinguish call order types as follows:

· Quote: Will be used to generate quotes for projects.

· Capacity: Will be used to place orders for Capacity SLINs.

· Non-capacity: Will be used to place orders for Non-Capacity SLINs.

· Technical Assistance: Will be used for Technical Assistance and Travel SLINs.

6.4.1.3 Call Order Field/Column Requirements. At a minimum, call orders will contain the following information with the ability to add additional columns as required. The contractor may also add additional fields/columns as needed.

System-generated call order tracking fields/columns must include:

· Call order number

· Amendment number

· Call Order creation date

· First estimated billable date

· Call order line-item fields/columns

· Line-Item Number

· CLIN/SLIN with description

· Quantity Total

· SLIN Cost

· Discount

· Extended Unit Cost

· Total Cost

· Cost Type: Implementation (one-time cost), Recurring (monthly cost)

User-entered/editable call order tracking fields/columns must include:

· Call order type

· Environment Designation. NIPR/SIPR/Other

· Application/Mission Partner

· Requestor

· Technical POC

· Project Type

· Project Name

· Project Number

· Implementation Resource Pool

· Recurring Resource Pool

· Implementation Billing Account Number (BAN)

· Recurring BAN

· DISA Project Code

· MIPR/Funding Change Request (FCR) number

· Spend Plan ID

· Site

· Staging Site

· Twelve-month minimum

· Acceptance Date (contractor entered)

· Completion Date (contractor entered)

· Call order line-item fields/columns:

· Line-Item Number

· Network Type: Prod, OOB

· Quantity Add

· Quantity Remove

6.4.1.4 Export/Reporting Requirements. The COMS must be capable of providing reports, with the ability to be exported in either Excel or Adobe .PDF format. To include the following: all call orders and their status/metrics, equipment (capacity and maintenance) listed by serial number and invoicing.

6.4.1.4.1. The COMS must generate quotes that will be used to provide pricing for projects.

6.4.1.4.2. The COMS must provide inventory reporting to include call order number, project name and number, line-item number, Resource Pools, BANs, SLIN, hardware make and models, serial number, physical location, and costs.

6.4.1.4.3. The COMS will support exporting all call order types in MS Excel format. The contractor will provide a sample Call Order export file within 30 days of contract award, along with the COMS demo in 6.4.1. Call Order export types must include the following:

· Full exports with costs and without costs that include call order line items, call order Bill of Materials (BOM), installation information, and serial numbers.

· Project Pricing export which includes call order line items with costs and cost types and call order BOM.

PWS

Task#

6.4.1.4.3

CDRL

A007

6.4.2 Call Order Process. The contractor must provide all services via a call order process. A call order will be initiated by the Government through authorized call order personnel.