J-2_Proposal_Format.docx

Acquisition Sensitive

Acquisition Sensitive

HC1028-13-R-0015

Attachment J-2

ENTERPRISE STORAGE SOLUTION II

PERFORMANCE WORK STATEMENT (PWS)

PROPOSAL FORMAT

Contract Title. DISA, Enterprise Storage Solution (ESS) II

Background. DISA Enterprise Services Directorate (ESD) is a provider of information technology solutions for the Department of Defense (DoD). DISA’s DoD customers require storage for a variety of applications. DISA ESD must have the ability to provide cost-effective storage capacity in a timely manner whenever and wherever the requirements occur.

The purpose of this contract is to provide state-of-the-art storage capacity to meet new and emerging customer requirements and the ability to replace existing DISA storage capacity that has exceeded its technical life as determined by the Government.

DISA is required by the DoD to enhance communications effectiveness through improved information interoperability. DISA’s vision calls for a move from the centralized thinking and planning currently reflected in the Task, Process, Exploit, Disseminate (TPED) paradigm, to an edge-centered Task, Post, Process, Use (TPPU) approach to information sharing and availability. The envisioned changes represent a fundamental paradigm shift from providing platform centric applications to platform independent, web-enabled services requiring the support of a diverse storage environment, that meets the requirements of the end users, and which is highly available, secure, and reliable. DISA ESD will need to provide storage capabilities at DISA-owned and other approved processing locations.

Objectives. The objective of this contract is to obtain reliable, responsive, and cost effective storage infrastructure services of “on-demand” storage capabilities for specified chipset architecture in both DISA and other DISA-approved locations, which are both in the continental United States (CONUS) and outside of the continental United States (OCONUS). DISA's goal is to obtain a dynamically scalable storage capability utilizing an on-demand service approach, for new equipment, that will quickly adjust to changes in storage and throughput requirements, both increases and decreases, and is priced on a utility ("as used") basis or tiered structure.

The service provider will acquire, install, de-install, transport, configure, and provide the necessary hardware (including cabinets/racks/cabling/cable management/PDUs), hardware maintenance, as well as, any software required for the Contractor’s solution to operate, and services to support the storage infrastructure associated with this contract. The Government will maintain day-to-day operational control of the storage environment and complete oversight responsibility. This operational control includes the installation of all software updates after the initial delivery. However, any software required for the Contractor’s solution to operate, including software maintenance and licensing shall be included under this contract.

Scope. The Contractor will design, deliver, install, and maintain storage capacity infrastructure in concert with the Government, at any of the current DISA ESD computing facilities or future DISA ESD computing facilities in the continental US (CONUS), the Government, DISA ESD outside CONUS (OCONUS) and other DISA or DISA approved locations worldwide where DISA ESD may acquire an operational responsibility. The offeror’s proposal shall address all requirements listed in this document.

The hardware/Chipsets/operating environments requiring storage support for DISA ESD 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)

Itanium (HP-UX)

SPARC (Solaris)

IBM System p (AIX)

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

This initiative will support controlled unclassified and classified including SCI level environments.

Current Environment – DISA ESD currently provides processor services at 17 computing facilities in the CONUS, located at:

· Chambersburg, PA,

· Columbus, OH,

· Denver, CO

· Fort Meade, MD

· Huntsville, AL,

· Jacksonville, FL

· Pensacola, FL

· Mechanicsburg, PA,

· Montgomery, AL,

· Ogden, UT,

· Oklahoma City, OK,

· San Antonio, TX,

· St Louis, MO,

· Warner Robins, GA

· Ft Bragg, NC

· FT Eustis, VA

· Ft Knox, KY

Six (6) current OCONUS locations are:

· Germany

· Hawaii

· Alaska

· Bahrain

· Japan

· South Korea

Future locations. Contractor shall have the ability to support DISA or DISA approved locations worldwide where DISA may acquire an operational responsibility.

DISA will afford Contractor protection under the Department of Defense’s Status of Forces Agreement with all OCONUS Host countries. DISA will hold Contractor harmless from any and all local taxes, value-added taxes, excise taxes, and/or other tariffs imposed by the Host country on goods and services entering the country in support of this contract. Should DISA not be able to afford Contractor protection from these taxes and tariffs, DISA will reimburse Contractor for any and all reasonable and customary taxes and/or tariffs.

All locations may require a NIPR, SIPR and the potential for a Sensitive Compartmented Information Facility (SCIF) environment.

Offeror Response:

Unclassified, Classified, SCI Level Environments. Where required under this contract, Contractor will provide engineering and maintenance support personnel with the appropriate clearance for DISA’s classified and unclassified environments. (See para 13 for individual personnel security requirements). Contractor will deploy separate equipment for classified and unclassified environments and will provide all assets needed for the storage infrastructure regardless of environment (classified or unclassified).

No storage hardware currently installed in DISA shall be used to satisfy the requirements of this solicitation. All hardware to support solutions brought into DISA locations for the first time must be new hardware. If the call order is later canceled, the hardware to support the service may be reutilized as long as the technology is not a product that the OEM has withdrawn from marketing/sale.

The intent of this contract is to cover both present and future requirements for storage solutions. As technology performance and capabilities improve, the class of storage will support any advances in improvement to performance or capabilities at the awarded SLIN price.

Offeror Response:

Performance Requirements.

TASK 1 – Storage solutions and capabilities.

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities and Section L, Factor 1, Subfactor 2: Service Delivery, 2.2 Call order management, new technology, refresh, technology testing, and cost improvements)

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

- Enterprise class storage solutions. External controller based redundant array of independent disks (RAID) solutions that meet all of the following criteria:

- Use multi-controller architecture

- Supports 256 GB of cache

- Supports controller cache mirroring

- Supports array based heterogeneous data migration which is non-disruptive to ongoing operations

- Supports 32,000 Logical Unit Numbers (LUNs)

- Supports active / active controllers with symmetric assess to LUNs

- Supports 3 way replication of data

- Support mainframe (z/OS, z/VM, and z/Linux) and open system architectures

- Support fibre connectivity (FICON) and fibre channel (FC) host connectivity

- Support synchronous data replication internal to the array, point-in-time and snap shot copies

- Supports snapshots capability to remote storage systems

- Supports space recovery reclamation

- Advanced redundant array of independent disks (RAID) capabilities (RAID 10, 5 (3+1), 5 (7+1) etc.)

- Encryption of data at rest that complies with all levels of the FIPS 140-2 standard

- Supports multi-tenancy

- Thin provisioning virtualization of storage resources to attached servers. This includes a common storage “pool” and presenting logical storage capacity to a server while minimizing the physical storage resources consumed and allows for non-disruptive scaling (up and down) and reconfigurations.

- All of these features above shall be included in the base costs for all enterprise storage solutions. Additional optional priced features for enterprise class storage solutions will include:

- Support asynchronous data replication

- Support synchronous data replication external to the array

- Supports automated multi-tiered life cycle management architecture that is configurable / tunable and has flexi bility in its data protections options

- Supports data erasure / shredding compliant with DoD 5220.22-M

- Mid range class storage solutions. External controller based RAID solutions that meet all of the following criteria:

- Use dual controller or cluster architecture

- Support UNIX, Windows, VMware, Linux operating systems

- Support fibre channel (FC) host connectivity

- Advanced RAID capabilities (RAID 10, 5 (3+1), 5 (7+1) etc.)

- Encryption of data at rest that complies with all levels of the FIPS 140-2 standard

- Supports multi-tenancy

- Supports controller cache mirroring

- Virtualization of storage resources to attached servers. This includes a common storage “pool” and presenting logical storage capacity to a server while minimizing the physical storage resources consumed and allows for non-disruptive scaling (up and down) and reconfigurations.

- All of these features above shall be included in the base costs for all mid-range storage solutions. Additional optional priced features for enterprise class storage solutions will include:

- Support asynchronous data replication

- Supports data erasure / shredding compliant with DoD 5220.22-M

- Support synchronous data replication, point-in-time and snap shot copies

- Inexpensive bulk storage disk solutions. Inexpensive, scalable, external controller based storage system that meets the following criteria:

- Basic RAID capabilities (RAID 0, 1, 5)

- Use single or dual controller architecture

- Virtualization of storage resources to attached servers. This includes a common storage “pool” and presenting logical storage capacity to a server while minimizing the physical storage resources consumed.

- Network attached storage (NAS) solutions. NAS solutions that meet all of the following criteria:

- Support UNIX, Windows, VMware, Linux operating systems

- Support synchronous data replication, point-in-time and snap shot copies

- Support Network File System (NFS) and Common Internet File System (CIFS) protocols

- Maximum scalability options

- Advanced RAID capabilities (RAID 10, 5 (3+1), 5 (7+1) etc.)

- Encryption of data at rest that complies with all levels of the FIPS 140-2 standard

- Supports multi-tenancy and multiple VLANs

- Virtualization of storage resources to attached servers. This includes a common storage “pool” and presenting logical storage capacity to a server while minimizing the physical storage resources consumed and allows for non-disruptive scaling (up and down) and reconfigurations.

- All of these features above shall be included in the base costs for all enterprise storage solutions. Additional optional priced features for enterprise class storage solutions will include:

- Support asynchronous data replication

- Supports data erasure / shredding compliant with DoD 5220.22-M

- Big data, object-addressable storage solution. Provide solution for object-addressable storage for large scale data storage. Provide storage solution that is optimized for large scale file and unstructured data and has non-disruptive scale out capabilities. This solution should support petabytes of unstructured data under a single name space. Big data solutions that meet all of the following criteria:

- Support UNIX, Windows, VMware, Linux operating systems

- Support asynchronous data replication

- Support a distributed file system capable of working across multiple, globally distributed nodes

- Support a minimum of 15 PB global name space / file system

- Support for NFS, CIFS, HTTP and HTTPS, FTP, FTPS or SFTP, REST API

- Supports multi-tenancy

- Supports a minimum of 10 gigabit, fiber Ethernet connects

- Allows for non-disruptive scaling (up and down) and reconfigurations.

· Provide storage solutions that include data de-duplication capabilities which support data replication, are scalable up and down and minimize downtime.

Deliverable/s: Solution for each class of storage listed in above including specific technologies used in the solution.

Offeror Response:

- Provide solutions that can be delivered, installed, implemented, scaled, reconfigured, and maintained throughout their life at an optimum level of performance according to the original equipment manufacturer’s (OEM) best practices without service disruption. Non-disruptive changes must include increases and decreases in disk and port capacity and firmware updates. Offeror will provide their method for how they will address storage performance including (but not limited to) array cache configurations, controller configurations, disk configurations, and switch port configurations.

Deliverable/s: Utility storage services with the ability to increase and decrease as required non-disruptively while delivering optimum levels of performance.

· Provide solutions that support multi-tenancy.

Deliverable/s: Solutions that function in a multi-tenancy environment.

Offeror Response:

- Provide solutions that are highly available (minimum 99.95% up to 99.999% availability) and readily scalable to adjust to increases and decreases in required storage capability and prevent data loss in the event of component failure(s).

Deliverable/s: Provide the technical specifications which describe how the provided solutions meet the availability and scalability storage capability.

Offeror Response:

TASK 2 - Additional Storage Capabilities.

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities and Section L, Factor 1, Subfactor 2: Service Delivery, 2.2 Call order management, new technology, refresh, technology testing, and cost improvements)

The contractor shall provide:

Provide storage solutions that facilitate DISA’s ability to provide private, public and hybrid cloud storage capabilities to the DoD.

Private cloud capabilities should include a solution to fully automate common storage provisioning and management functions and can easily be configured to integrate into other orchestration tools and strong out of the box functionality.

Private cloud capabilities should include a file sharing solution that provides access to content via both desktop and mobile devices. Solution should have ability for end users to control security access to their files and include reporting capabilities for administrators and end users. Solution must support DoD Public Key Infrastructure (PKI) Common Access Card authentication.

Private cloud capabilities should include a storage solution to store disaster recovery backups and archival data for long retention periods. This solution will encrypt data in ‘flight’ and at rest with FIPS 140-2 compliant encryption. Solution should include reporting and management interfaces for DISA administrators to use in day to day operations.

Deliverable/s: Storage solutions that facilitate DISA’s ability to provide cloud storage services to DoD based on the NIST definition.

Offeror Response:

Provide solutions for multi-site enterprise scale backup/data protection and archiving. Solution should cover all related aspects of backup and data protection, including server software components and host agents. Solution will include centralized management capabilities, robust reporting features, be easy to install and maintain. Solution must support Microsoft Exchange backup (file level and exchange agent), user mailbox and compliance archiving, journaling and content indexing. Solution should be able to support retention rates greater than one year. Solution must support data archive, retrieval and user capacity limits across the entire Exchange environment, regardless of archive locations.

Deliverable/s: Solutions for storage data protection backup and archiving.

Offeror Response:

Provide automated physical linear tape-open (LTO) tape solutions for specialized environments to include any hardware and software required to make the solution complete.

Deliverable/s: Solutions for physical tape storage.

Offeror Response:

Provide IBM mainframe compatible solution for virtual tape that has no physical tape components. This solution should be scalable up and down in capacity and reconfigurable with no disruptions. This solution will have no physical tape and include de-duplication and replication capabilities.

Deliverable/s: Solutions for IBM mainframe compatible virtual tape storage solution.

Offeror Response:

Provide solutions to allow for automated data tiering across different hardware devices for enterprise, mid-range, and bulk class storage offerings. Solution should virtualize storage locations so that changes to the data location are transparent to operating system and applications.

Deliverable/s: Solutions for auto tiering between storage devices.

Offeror Response:

Provide solutions for continuous data protection. Solution should also include ability to configure restoration of data at 30 minute, 8 hour and 24 hour intervals. Solution should provide capability to restore locally and remotely. Optionally, solution should provide method to reduce bandwidth of replicated data.

Deliverable/s: Solutions for continuous data protection.

Offeror Response:

TASK 3 – Supported Environments.

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities and Section L, Factor 1, Subfactor 2: Service Delivery, 2.2 Call order management, new technology, refresh, technology testing, and cost improvements)

Storage solutions will be required to support the following chipsets/operation environments for DISA:

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)

Itanium (HP-UX)

SPARC (Solaris)

IBM System p (AIX)

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

Ensure all components are Ipv6 capable. This is defined as a system or product capable of receiving, processing and forwarding Ipv6 packets and/or interfacing with other systems and protocols in a manner similar to that of Ipv4. Criteria to be considered Ipv6 capable are: conformant with the Ipv6 standards profile contained in the DOD IT Standard Registry (DISR); maintaining interoperability in heterogeneous environments and with Ipv4; commitment to upgrade as the Ipv6 standard evolves; and availability of contractor/contractor Ipv6 technical support.

Deliverable/s: Interoperability and support for Ipv6.

Offeror Response:

Provide solutions that are interoperable and compatible with the current installed DISA ES information storage baseline. See Attachment 1, Storage Inventory.

Deliverable/s: Interoperability with current DISA storage infrastructure.

Offeror Response:

Provide solutions that are interoperable and compatible with the DISA ESD chosen enterprise systems management (ESM) architecture. See Attachment 2, Enterprise Management Products for the list of ESM architecture major components.

Deliverable/s: Interoperability with current DISA ESM architecture.

Offeror Response:

Provide solutions that operate seamlessly with DISA’s communication and server infrastructure. DISA will provide all required bandwidth. Provided solutions must include all components required to interface to the DISA provided bandwidth. Contractor will provide solutions that optimize bandwidth usage.

Deliverable/s: Interoperability with DISA’s communication and server infrastructure.

Offeror Response:

The offeror will ensure all infrastructure components provided are capable of being managed remotely via a dedicated DISA management network.

Deliverable/s: Solutions capable of being managed remotely via dedicated DISA management network.

Offeror Response:

TASK 4 – Provisioning, Management, and Reporting Infrastructure

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities and Section L, Factor 1, Subfactor 2: Service Delivery, 2.2 Call order management, new technology, refresh, technology testing, and cost improvements)

The offeror will provide a centralized management infrastructure solution to include provisioning capabilities, hardware diagnostics, hardware monitoring, virtualization management, event logging, performance management or additional back office processes required to reside in the ESD infrastructure to support the offeror’s technical solution. This solution will be required to scale in a way that will support DISA’s storage environment and provide customizable, detailed reporting of infrastructure performance. This offeror-provided infrastructure will be managed and maintained by the offeror while DISA personnel will have access to the solution.

Provided solution will facilitate and be capable of both local and remote (via a wide area dedicated DISA management network) centralized management. This includes operational control, performance and monitoring for storage and SAN switching networks. Solution will be required to send error and performance alerts to DISA’s IBM Netcool Omnibus system. Solution should provide role-based access control to limit access.

Solution should follow DISA Security Technical Implementation Guides (STIG) and be ready for implementation within 45 calendar days after contract performance start. This solution will be subjected to Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) accreditation processes as well as relevant DISA STIG and security policies.

Deliverable/s: An accredited management infrastructure solution with the ability to manage provided storage infrastructure either locally or remotely and provide centralized reporting via solution.

Offeror Response:

Provide a single integrated storage resource management (SRM) solution that fully supports all storage services provided under this solicitation and maximizes the integration with DISA ESD’s current installed inventory. Solution should be capable of running in DISA’s STIGed environment and itself be STIGed and ready for implementation within 45 calendar days after contract performance start. This solution will be subjected to DIACAP accreditation processes as well as relevant DISA STIG and security policies. Solution should be a simple, easy to use and maintain system that has reporting which is flexible, detailed, and maximum out of the box capabilities.

The SRM solution should provide server storage and array capacity utilization information for DISA financial billing purposes.

The SRM solution should provide configuration and asset management information for tracking current configuration details and which components of a solution are in use and which are not.

The SRM solution should provide a central management interface for the control and management of solution components.

The SRM solution must provide integration with DISA’s implementation of BMC Software’s Information Technology Service Management (ITSM) system.

Deliverable/s: A single integrated storage resource management solution that fully supports all the solutions provided under this solicitation and its ability to support DISA’s current storage architecture.

Offeror Response:

TASK 5 – Maintenance.

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities)

Provide all Preventative maintenance actions as required by the Original Equipment Manufacturer (OEM), Predictive and Remedial Maintenance, on all equipment delivered as a part of this contract.

Maintenance Response and Repair Time.

The offeror shall provide storage capacity that delivers a minimum of 99.95% availability per orderable system with options to provide up to 99.999 % availability per orderable system. Response and repair times for CONUS and OCONUS will be 2 hour response/4 hour restore, unless otherwise specified by DISA ESD. These response times do not change the requirement for 99.95 or 99.999% availability, but represent requirements to repair components which might be causing a degraded state. Offeror will detail plans on how they will address solution failures of redundant components which might not impact system availability but do create performance issues or introduce single points of failure in systems.

Provide 24x7/365 problem escalation/resolution support for hardware, software, and capacity management. The offeror 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.

Deliverable/s: Response after being notified by the Government to commence remedial maintenance for any component required for the Contractor’s solution to operate. Storage performance/availability of 99.95% or better for each solution.

Offeror Response:

Maintenance types.

Predictive Maintenance. Contractor shall monitor equipment/component performance using diagnostics defined in paragraph 6.4.2.4 for the purpose of identifying whether equipment is operating in accordance with established specifications. This includes hardware, software and any other components required to make the contractor solution operable. The contractor shall, upon determining equipment/component is about to fail or is operating outside OEM specifications, initiate action to effect repair even though no call for remedial maintenance has been initiated by the site help desk or shift supervisor.

Contractor shall call the managing site service desk or shift supervisor to inform them they are coming in for predictive maintenance and request a DISA ESD Form 7 be generated and coordinated with the physical site. Upon arrival at the physical site, the contractor’s technician shall report to the site help desk or shift supervisor in order to comply with reporting requirements.

Deliverable/s: Storage capacity that delivers a minimum of 99.95% or better availability for each orderable solution with options up to 99.999% availability per orderable solution.

Offeror Response:

Remedial Maintenance. Calls will be initiated by the site help desk or shift supervisor to the contractor’s toll free help desk service. Contractor shall respond and repair, or when necessary, obtain required OEM support, in accordance with this specification. The contractor shall complete remedial maintenance within the response and repair times required to meet the availability minimums defined in paragraph 6.5.1. Upon arrival on site, contractor’s technician shall report to the site help desk or shift supervisor in order to comply with reporting requirements. This includes hardware, software and any other components required to make the contractor solution operable.

Deliverable/s: Storage performance/availability of 99.95% or better for each storage solution deployed.

Offeror Response:

Preventative Maintenance. Preventive maintenance shall be scheduled as agreed to by the managing site POC, local site support and the contractor. This includes hardware, software and any other components required to make the contractor solution operable. The contractor shall submit in writing its preventive maintenance schedule for equipment to the Contracting Officer (KO) within 30 days after contract award. Submission of the schedule shall be in accordance with contractor format. The preventive maintenance schedule may be modified at no cost by mutual agreement of both parties. The contractor’s proposed schedule shall not be less than that recommended by the OEM and shall include, as a minimum, the following information:

· Nomenclature of hardware item.

· Model.

· Serial Number.

· Remote diagnostics and reporting capabilities

· Frequency and duration of preventive maintenance, and type of service to be performed.

The contractor shall commence preventative maintenance in accordance with (IAW) the approved preventative maintenance schedule within 30 days after award for all maintenance equipment. Preventative maintenance shall be scheduled outside of the normal business hours.

If during the course of preventative maintenance, an equipment malfunction is identified, the contractor shall report the malfunction to the site point of contact (POC). The malfunction shall be corrected as a Remedial Maintenance Service and comply with response times .

Deliverable/s: Storage performance/availability of 99.95% or better for each storage solution deployed.

Offeror Response:

Remote Diagnostics. Permanent recorded system errors must be immediately reported to remote service center(s). This includes hardware, software and any other components required to make the contractor solution operable. The contractor shall provide written confirmation that reports and remote diagnostics support for applicable equipment exist within 7 calendar days after contract performance start. Storage systems will support built in diagnostics with “phone home” type capabilities using HTTPS, SFTP, or SSH protocols.

Verbal contact between the local maintenance technician and an off-site support technician is not acceptable for remote diagnostics. There shall be a diagnostic system usable by the remote technician.

The dial-in feature can be used, but ONLY with site authorization. The feature must be capable of disabling and set up to provide the site the ability to enable the feature upon request from the contractor.

Deliverable/s: Storage performance/availability of 99.95% or better for each storage solution deployed.

Offeror Response:

Under certain conditions, the offeror may be required to be available on “stand by” after hours, weekends, and/or holidays. All “stand by” hours will be included in the technical assistance and consulting support pricing. “Stand by” includes having a field engineer available on-site during a facility power upgrade.

TASK 7 – Performance and Availability.

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities)

The contractor shall:

Provide solutions that are deployed and priced on a utility (“as used”) basis. Capacity can be canceled at any time at no cost to the Government.

Deliverable/s: Utility service with the ability to increase and decrease solutions capacity as required. Billing must reflect increases and decreases.

Offeror Response:

(Reference Section L, Factor 1, Subfactor 2: Service Delivery, 2.1 24x7x365 problem escalation/resolution support.)

Provide 24x7/365 problem escalation/resolution support services including POCs, phone numbers and escalation chart.

Deliverable/s: Problem escalation/resolution support process with details about whom and their authority at each level in the process.

Offeror Response:

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.1 Storage Solutions and Capabilities)

Provide solutions that can be deployed in both classified and non-classified processing environments. Classified solution components must be separate from unclassified solution components. All solutions must adhere to the applicable STIGs.

Deliverable/s: Provide methodology and plan to support both unclassified and classified environments.

Offeror Response:

TASK 8 - Service Transition.

(Reference Section L, Factor 1, Subfactor 1: Technical, 1.2 Data Migration Strategy)

Implementation Transition Strategy. The implementation transition strategy will begin immediately upon award of the contract. The contractor must provide a detailed non-disruptive strategy for transitioning data stored on the current storage inventory to solutions provided in their proposal. The transition strategy must provide for completing the transition of all data to the proposed contractor’s solutions by, or before, the end of the existing Enterprise Storage Services (ESS) contract’s period of performance. This plan must address how it will minimize the impact to current storage operations and data replication. The contractor will be required to meet with the existing Enterprise Storage Services contractor and the government within 45 days of award to plan the transition strategy. The contractor will provide a written transition plan within 60 days of award.

Deliverable/s: Methodology for transitioning data stored on current storage inventory to Contractor provided utility solution(s).

Offeror Response:

Transition Exit Strategy. The transition exit strategy will begin at the end of the base contract. The Governments goal is that there will be a follow on contract in place by the end of the base period. It is the Governments desire that the option years will be exercised for sustainment of all orders. However, the Government can place new orders against the new contract in the option years should the need arise. At the end of the option years of the contract, or canceling a call order, the contractor shall be responsible for the removal of all their owned equipment related to this contract at no cost to the Government.

Deliverable/s: Removal of all contractor owned equipment related to this contract at no cost to the Government.

Offeror Response:

TASK 9 – Delivery, Installation and Configuration Support.

(Reference Section L, Factor 1, Subfactor 2: Service Delivery, 2.3 Training Solution)

Provide current detail technical documentation for all provided solutions.

Deliverable/s: Methodology for providing DISA personnel with access to technical documentation for all capacity.

Offeror Response:

Provide in-depth detailed technical training for all provided solution.

Deliverable/s: Methodology for providing DISA personnel with in-depth training for all capacity services provided in the Contractor’s offerings and utility pricing.

Offeror Response:

(Reference Section L, Factor 1, Subfactor 2: Service Delivery, 2.1 24x7x365 problem escalation/resolution support.)

Provide a strategy for allowing DISA to test new storage technologies on a limited time basis at one or more of its designated locations. The testing will be conducted for determination of adding the technology to the contract and/or determination of the optimum strategy for deployment in the DoD enterprise.

Deliverable/s: Strategy for testing new storage technologies added or under consideration for addition to the Contractor’s utility offerings.

Offeror Response:

TASK 11 – Ordering/Payment Process

(Reference Section L, Factor 1, Subfactor 2: Service Delivery, 2.2 Call order management, new technology, refresh, technology testing, and cost improvements)

Ordering. All services will be placed via a call order process. A call order will be initiated by the Government through authorized call order personnel.

The contractor must provide an ordering process to effectively manage the introduction or termination of technology, as well as changes to current and existing capacity offerings.

The contractor must provide standard operating procedures to support the system including but not limited to the following: management of new or first time orders, returns, back orders, special orders, processing invoices, processing refunds, credits and exchanges, managing both deliveries and lost deliveries, billing processes, complying with quality assurance reviews and effectively balancing/managing inventories with orders.

On a regular basis the Government may have a requirement for new/revised IT products which shall require the contractor to respond in a sufficiently fast turn-around time to meet Government mission requirements. Consequently, the contractor must be able to expeditiously respond to requests to accomplish any changes and must be able to specify a response time relevant to accomplishing any Government requested change to a product line.

The offeror has one business day to validate a call order for accuracy. Once the offeror validates a call order for accuracy, the hardware should be delivered within 30 days or less. Call orders received on Friday, requires validation by the following business day.

Deliverable/s: A methodology for call order management.

Offeror Response:

Call Order Management System. Contractor will create a secure and/or CAC-enable web-based, call order management system. If the system runs within a DISA facility, the system must be CAC- authenticated and must adhere to DISA security guidelines. If the system runs outside of a DISA facility, the system must be secure and authenticate users to ensure a secure system. 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. It must be able to track excess hardware and software for re-utilization. DISA personnel will require access to this system.

The contractor call order management system will include the ability to cancel existing equipment/workload and remove capacity services gear from the DISA site.

The contractor call order management system 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.

The format of call orders may contain some or all of the following information: DISA call order number, call order date, first estimated billable date, DISA resource pool, DISA project code, customer ID, application ID, CLIN/SLIN with description, NIPR/SIPR designation, quantity, service fee or one-time charge (OTC), serial number, MIPR number, power required, power order tracking number, project type, project name(s), Mission Assurance Category (MAC) level, type of capacity service, delivery site, brand type, security environment (level), host type for disk or tape subsystem, DISA engineer/requestor, site supervisor technical point of contact (TPOC), remote TPOC, on-site TPOC, array model, array frames, disk raid level, disk size, raw capacity in terabyte (TB), local data replication, remote data replication, remote data replication site, switch type, ports, tape drive type, tape slot count, instructions to site, justification, reviewed-by field.. Note that this list represents a sample of fields needed for a call order but is not a definitive list. After contract award, contractor will collaborate with DISA to finalize call order format and information required.

The call order management system must be able to handle the complete order process to include, but not limited to 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 and assigning DISA internal tracking numbers, call order status.

The call order management system must track equipment moves to include the equipment moved, date/s of move/s, which site equipment moved from and which site equipment moved to.

The call order management system will contain no more than two decimal places in the financial data.

Deliverable/s: A call order management system solution with the ability to create and place call orders, track changes to call orders, manage invoices, asset management and reporting.

Offeror Response:

Invoice Creation and Billing Cycle. Offeror will provide solutions to create invoices directly from order data and does not require the collection, manipulation, or review of utilization data. Contractor will create the invoice directly from data provided by DISA in its “contract call order,” augmented by the “Acceptance” and “Deactivation” date that begins daily charges (increases and decreases) for the resources ordered and provisioned. Contractor will employ a monthly billing cycle with 28/29/30/31 days per month. At the end of a month, the order processing system is queried to display a draft invoice based on:

1. Orders that remained in service the entire month with no changes;

2. Orders placed in service during the month; and

3. Orders implemented during the month that reduced or canceled services.

Contractor will create a draft invoice and submit it to the designated DISA COR who reviews/corrects, as necessary, the draft invoice. Following this feedback, Contractor formally submits the invoice via the DoD Wide Area Workflow System (WAWF). The invoice will be constructed to DISA specification and supporting details will be appended in the form of a spreadsheet file that can be easily manipulated to provide a variety of different sorts and views of the underlying data. Submission of the monthly invoice for the prior month’s activity is routinely completed no later than the fifth of the month.

Deliverable/s: A methodology for invoicing/billing based on acceptance and deactivation of call orders.

Offeror Response:

PWS Proposal Template Page 1 of 10 Pages