J-6_Question_Answer_Submission_026_thru_122.doc
DOC document 761 KB Posted
- Attached to
- Enterprise Storage Services (ESS II)
- Solicitation number
- HC102813R0015
- Issued by
-
Defense Information Systems Agency
About this file
Questions and Answers 026 thru 122
View the file
Other files
Show all 33
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment J-6 - Question Answer Submission Template for RFP HC1028-13-R-0015
| QUESTION # |
| 026 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 2 |
| SECTION NO. |
| 5.3 |
| SECTION NAME |
| Scope |
| SECTION TEXT |
| The objective is for the Contractor to provide storage services using a “utility contract concept”. This utility concept requires that the Contractor provide all assets needed for the storage service. These assets shall include, but are not limited to, hardware, software, software maintenance and licensing, design capabilities, logistical support, field maintenance, and systems engineering. |
| QUESTION |
| Does DISA intend for any related personnel for field support to reside on the site or will these personnel be on an as needed basis? If to reside on site will personnel be provided office space, parts locker space and communications connectivity? |
| ANSWER |
| The Government may provision space for field support personnel at sites. The Offeror should not assume any space will be provisioned for parts. Offeror has to meet required response times as noted in PWS paragraph 6.5.1. |
| QUESTION # |
| 027 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 |
| SECTION NO. |
| 5.8 |
| SECTION NAME |
| Scope |
| SECTION TEXT |
| 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. |
| QUESTION |
| Does this imply that the existing capacity on the DISA data center floor will be removed by the current vendor and replaced with more current hardware? An unfair advantage could be exploited by the current vendor by underbidding with the assumption that they would be allowed to keep the existing hardware on the floor for an extended period of time which in some cases may already be paid for. |
| ANSWER |
| All existing capacity from the old contract must be removed and replaced with new hardware. Hardware is tracked by Serial Number and Bar Code that will be used to verify existing hardware is not being redeployed. Incumbent must provide new serial numbered assets that are not barcoded by the government. |
| QUESTION # |
| 028 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 – 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| FIPS 140-2 has four associated levels. Is it the intent of DISA to require up to level four for all proposed storage solutions? Also, will this include the key management system that will be needed for the encryption operations? |
| ANSWER |
| The offeror’s solution must include all software and hardware required, to include key management. Encryption has been moved to the optional section. Storage systems that require the encryption option are listed in the PWS. The offerors solution should have the flexibility to support any and all levels of FIPS compliance. |
| QUESTION # |
| 029 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.2 |
| SECTION NAME |
| Mid Range Class Storage Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| Can DISA expand on what is intended by the "multi-tenancy" requirement or provide an example of how this is implemented in the current environments |
| ANSWER |
| Multi-tenancy is defined as the ability to utilize the same solution for multiple client systems, while providing the same level of service to all workloads accessing the solution. |
| QUESTION # |
| 030 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 4 |
| SECTION NO. |
| 6.1.1.3 |
| SECTION NAME |
| Inexpensive bulk storage disk solutions |
| SECTION TEXT |
| 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.
| QUESTION |
| Inexpensive disks in the industry represent SATA or NL-SAS disks with a rotation of 7200 RPM's and are typically deployed in a RAID 6 configuration to protect against higher failure rates. Is it the intent of DISA not to use any SATA or NL-SAS drives or RAID 6 for this category of disks? If so, can DISA provide performance characteristics that can assist vendors in determining a type of disk to provide? |
| ANSWER |
| Offeror’s solution can be flexible with drive and RAID offerings, but must support a minimum of RAID 0, 1 and 5. |
| QUESTION # |
| 031 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 4 - 5 |
| SECTION NO. |
| 6.1.1.4 |
| SECTION NAME |
| Network Attached Storage (NAS) Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| Can DISA expand on the requirement "Maximum scalability options"? This requirement if vague in terms of what is being requested. |
| ANSWER |
| Maximum scalability options have been deleted from Section 6.1.1.4 of the PWS. |
| QUESTION # |
| 032 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 5 |
| SECTION NO. |
| 6.1.1.5 |
| SECTION NAME |
| Big Data, Object-addressable Storage Solution |
| SECTION TEXT |
| 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.
| QUESTION |
| Can DISA expand on what is intended by the "multi-tenancy" requirement or provide an example of how this is implemented in the current environments |
| ANSWER |
| Multi-tenancy is defined as the ability to utilize the same solution for multiple client systems, while providing the same level of service to all workloads accessing the solution. |
| QUESTION # |
| 033 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 5 |
| SECTION NO. |
| 6.1.1.6 |
| SECTION NAME |
| Provide storage solutions that include data de-duplication |
| SECTION TEXT |
| Provide storage solutions that include data de-duplication capabilities which support data replication, are scalable up and down and minimize downtime. |
| QUESTION |
| Data de-duplication is one approach that will increase physical storage efficiency. However, de-dupe will also decrease performance in any DISA storage environment where it is deployed. That is why de-dupe is generally limited to environments other than production – like Backup and Archive. There are other data optimization technologies that will increase storage efficiency without any performance degradation. We therefore recommend that in order to give DISA the broadest range of storage optimization technologies to evaluate, DISA revise the requirement to read: |
Provide storage solutions that include data de-duplication and/or other storage optimization capabilities which support data replication, are scalable up and down and minimize downtime. To enable DISA to accurately assess each proposed technology, vendors will identify proposed technologies and specify vendors own best practices for use of each type of technology.
Recommend that DISA require bidders to demonstrate the actual performance characteristics of de-dupe or other proposed optimization technology in the live test demo, with actual application data.
Please add a requirement that de-dupe or other storage optimization technology proposed “will be tested by DISA to insure acceptable performance for each data type where the optimization will be used.”
| ANSWER |
| If a Proof of Concept (POC) is required, a detailed POC test plan will be sent to the offeror 14 calendar days prior to POC demonstration. |
| QUESTION # |
| 034 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 5 |
| SECTION NO. |
| 6.1.3 |
| SECTION NAME |
| Subtask 1.3 |
| SECTION TEXT |
| Provide solutions that support multi-tenancy. |
Deliverable/s: Solutions that function in a multi-tenancy environment.
| QUESTION |
| Can DISA expand on what is intended by the "multi-tenancy" requirement or provide an example of how this is implemented in the current environments? |
| ANSWER |
| Multi-tenancy is defined as the ability to utilize the same solution for multiple client systems, while providing the same level of service to all workloads accessing the solution. |
| QUESTION # |
| 035 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 5 |
| SECTION NO. |
| 6.1.6 |
| SECTION NAME |
| Subtask 1.6 |
| SECTION TEXT |
| Provide storage area network (SAN) solutions that support common industry storage networking protocols such as Fibre Channel and Ethernet. Provide solutions for storage switching requirements priced on a per port basis. |
Deliverable/s: Solutions which support common industry storage protocols and are on a per port basis.
| QUESTION |
| Can it be assumed that the reference in this requirement for "Ethernet" are intended for management purposes only or does it also refer to FCoE and/or iSCSI? |
| ANSWER |
| The current environment is Fiber Channel. The offeror’s solution must support the current environment and should be flexible to include other storage networking protocols like FCoE and iSCSI. |
| QUESTION # |
| 036 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 6 |
| SECTION NO. |
| 6.2.2.3 |
| SECTION NAME |
| Private cloud capabilities |
| SECTION TEXT |
| 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. See Attachment 6.
| QUESTION |
| Can DISA clarify what is meant by “will encrypt data in ‘flight’” for this requirement in terms of where the data is expected to be encrypted? (Between sites, within the site the data resides, between hosts and storage) |
| ANSWER |
| Offeror’s solution may provide encryption at any point, but all data that is sent beyond the DISA premise routers must be encrypted while in transit. |
| QUESTION # |
| 037 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 7 |
| SECTION NO. |
| 6.4.1 |
| SECTION NAME |
| Subtask 4.1 |
| SECTION TEXT |
| 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.
| QUESTION |
| Can DISA define the statement "This offeror-provided infrastructure will be managed and maintained by the offeror while …..". Does this imply that the offeror will have remote access or on-site office space to access the infrastructure as the solution will be connected to a DISA network? |
| ANSWER |
| The Government may provision space for field support personnel at sites. The offeror should not assume any space will be provisioned for spare parts. Offeror has to meet required response times as noted in PWS paragraph 6.5.1. |
| QUESTION # |
| 038 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 8 |
| SECTION NO. |
| 6.4.2.1 |
| SECTION NAME |
| Provisioning, Management, and Reporting Infrastructure |
| SECTION TEXT |
| The SRM solution should provide server storage and array capacity utilization information for DISA financial billing purposes. |
| QUESTION |
| Since DISA's intent, as stated in 3.0, Background, is to 'provide state-of-the-art storage capacity to meet new and emerging customer requirements' and 'to provide cost-effective storage capacity in a timely manner whenever and wherever the requirement occurs', we suggest DISA evaluate its enterprise, mid-range, bulk-data, NAS, and object-addressable storage around useable capacity at desired service levels in conjunction with raw capacity. For example, not all vendors have the same effective useable capacity after RAID is applied. Some may only provide 50% - 60% disk utilization once RAID is applied compared to another having a 75% - 85% effective utilization. This would result in DISA having to deploy an estimated 25% - 35% more RAW capacity to gain the same effective capacity resulting in higher costs for power, cooling, floor space and higher rates for DISA end users due to the required additional RAW capacity. |
To ensure selection of cost effective and efficient storage solutions, we suggest DISA require vendors to provide useable capacities for a sample raw capacity in a RAID-5 for FC or SAS drives and a RAID-6 or better configuration for SATA or NL-SAS drives. These drives should be a common drive such as 600GB for FC/SAS and 3TB for SATA/NL-SAS.
| ANSWER |
| Offeror should provide a Provisioning, Management, and Reporting Infrastructure which will provide server and storage array capacity utilization. |
| QUESTION # |
| 039 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 8 |
| SECTION NO. |
| 6.4.4.2 |
| SECTION NAME |
| Provisioning, Management, and Reporting Infrastructure |
| SECTION TEXT |
| 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. |
| QUESTION |
| Can DISA provide more detail on what specific data is to be collected and reported for this requirement? |
| ANSWER |
| Offeror’s solution should provide a comprehensive view of configuration details for all technical requirements included in Attachment J-1 PWS. |
| QUESTION # |
| 040 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 9 |
| SECTION NO. |
| 6.5.2.4 |
| SECTION NAME |
| Remote Maintenance |
| SECTION TEXT |
| 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.
| QUESTION |
| Does this requirement imply that an on-site technician cannot contact via telephone back line support in those cases where higher level of support or development involvement may be needed? If this is the case vendors may be delayed in meeting the requirement for fix within 4 hours indicated in Section 6.5.1 Subtask 5.1. |
| ANSWER |
| Language has been modified in section 6.5.2.4 of the PWS to reflect the following: “Verbal contact between the local government maintenance technician and an off-site vendor support technician is not acceptable for remote diagnostics. “ |
| QUESTION # |
| 041 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 11 |
| SECTION NO. |
| 6.8.1 |
| SECTION NAME |
| Subtask 8.1 – Implementation Transition Strategy |
| SECTION TEXT |
| . 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).
| QUESTION |
| Can DISA define the term "non disruptive" in this context? Moving between storage systems may require short outages for migrations to take place. Even if the current vendor was able to virtualize the new storage platforms, an outage would have to occur to remove the existing virtualization platform from the architecture. |
| ANSWER |
| The potential for minimal disruption is understood, but all potential outages and durations should be identified in the migration plan with details on how to minimize disruption. Migration plan is subject to government review and approval. |
| QUESTION # |
| 042 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 13 |
| SECTION NO. |
| 6.11.2.3 |
| SECTION NAME |
| TASK 9 – Delivery, Installation and Configuration Support |
| SECTION TEXT |
| 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. |
| QUESTION |
| Since DISA's intent, as stated in 3.0, Background, is to 'provide state-of-the-art storage capacity to meet new and emerging customer requirements' and 'to provide cost-effective storage capacity in a timely manner whenever and wherever the requirement occurs', we suggest DISA evaluate its enterprise, mid-range, bulk-data, NAS, and object-addressable storage around useable capacity at desired service levels in conjunction with raw capacity. For example, not all vendors have the same effective useable capacity after RAID is applied. Some may only provide 50% - 60% disk utilization once RAID is applied compared to another having a 75% - 85% effective utilization. This would result in DISA having to deploy an estimated 25% - 35% more RAW capacity to gain the same effective capacity resulting in higher costs for power, cooling, floor space and higher urates for DISA end users due to the required additional RAW capacity. |
To ensure selection of cost effective and efficient storage solutions, we suggest DISA require vendors to provide useable capacities for a sample raw capacity in a RAID-5 for FC or SAS drives and a RAID-6 or better configuration for SATA or NL-SAS drives. These drives should be a common drive such as 600GB for FC/SAS and 3TB for SATA/NL-SAS.
| ANSWER |
| Offeror’s solution should meet the required call order format that is listed in 6.11.2.3. Question does not relate to text of PWS Section 6.11.2.3. |
| QUESTION # |
| 043 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| Can DISA expand on the requirement "Supports snapshots capability to remote storage systems" to clarify it this means to virtualized remote storage systems or to geographically dispersed locations? |
| ANSWER |
| Supports snapshots capability to remote storage systems has been removed as a performance requirement in Section 6.1.1.1 of the PWS. |
| QUESTION # |
| 044 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| Can DISA expand on what is desired for the requirement that reads "configurable / tunable and has flexi-ability in its data protections options"? |
| ANSWER |
| The offeror’s solution should define the characteristics of the multi-tiered life cycle, but should at a minimum provide tiering at a LUN level. |
| QUESTION # |
| 045 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| Specifying specific architectural characteristics limits choice for DISA and may eliminate innovative new technologies already in use in enterprise data centers which may result in higher costs for DISA's customers. Request DISA respecify its Enterprise class storage requirement in terms of capacity, response time, throughput and availability to enable the use of the best available technology for each class of service, including enterprise class. |
| ANSWER |
| The Government has provided requirements; offeror solution can be innovative but needs to meet the requested specifications. |
| QUESTION # |
| 046 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| Requiring array based migration limits the choice of available migration technologies and may result in a less robust and/or more expensive solution for DISA and its customers. Request this requirement be changed to “Supports heterogeneous data migration which is non-disruptive to ongoing operations”. |
| ANSWER |
| Language in Section 6.1.1.1 of the PWS has been modified to - Supports heterogeneous data migration which is non-disruptive to ongoing operations. |
| QUESTION # |
| 047 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| Requiring z/OS, z/VM, and z/Linux and FICON support along with open systems and fibre channel support in the same storage subsystem may eliminate many cost effective high performance storage solutions currently in use in open systems only enterprise class environments today. Since only 10% of DISA's current infrastructure requires mainframe attach capabilities, we suggest DISA modify their enterprise requirement to allow bidders to split their enterprise offerings into two classes, one with mainframe specific OS and FICON support and one without, if desired. This would not prevent any bidder from offering a single class of enterprise storage which includes FICON and Fibre Channel connectivity in a single subsystem, but would broaden the pool of enterprise solutions available to DISA resulting in lower overall cost to DISA and its customers. |
| ANSWER |
| The current PWS allows the vendor to split offerings as long as all requirements listed in Section 6.1.1.1 are met. |
| QUESTION # |
| 048 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.1 |
| SECTION NAME |
| Enterprise Class Storage Solutions |
| SECTION TEXT |
| 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 flexibility in its data protections options
- Supports data erasure / shredding compliant with DoD 5220.22-M
| QUESTION |
| To enable the broadest range of potential solutions including new data protection approaches which may not map directly to traditional RAID 10 or RAID 5 layouts, we suggest DISA amend this specification to require RAID 5 or better for FC or SAS drives and RAID 6 or better for SATA or NL-SAS drives. |
| ANSWER |
| Offeror’s solution can be flexible with drive and RAID offerings, but must support a minimum of RAID 10, 5 (3+1), 5 (7+1) etc. |
| QUESTION # |
| 049 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.2 |
| SECTION NAME |
| Mid Range Class Storage Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| FIPS 140-2 has four associated levels. Is it the intent of DISA to require up to level four for all proposed storage solutions? Also, will this include the key management system that will be needed for the encryption operations? |
| ANSWER |
| The offeror’s solution must include all software and hardware required, to include key management. Encryption has been moved to the optional section. Storage systems that require the encryption option are listed in the PWS. The offerors solution should have the flexibility to support any and all levels of FIPS compliance. |
| QUESTION # |
| 050 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.2 |
| SECTION NAME |
| Mid Range Class Storage Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| There is no associated threshold where mid-range class begins or ends. Can DISA provide guidance on what the expected thresholds would be in over for vendors to categorize their solutions? |
| ANSWER |
| If the offeror’s solution meets requirements listed in 6.1.1.2, it is classified as a mid-range storage system. |
| QUESTION # |
| 051 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 3 - 4 |
| SECTION NO. |
| 6.1.1.2 |
| SECTION NAME |
| Mid Range Class Storage Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| VMWare is the only virtualization hyper-visor listed for mid-range disks. Should this list also include other hyper-visors such as Zen, KVM, Hyper-V, Power VM and any other not included? |
| ANSWER |
| Mid-range storage class solutions must support environments referenced in 6.3.1.1 with the exception of IBM z/OS and IBM z/vm. |
| QUESTION # |
| 052 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 4 |
| SECTION NO. |
| 6.1.1.3 |
| SECTION NAME |
| Inexpensive bulk storage disk solutions |
| SECTION TEXT |
| 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.
| QUESTION |
| There is no associated threshold where inexpensive disks begins or ends. Can DISA provide guidance on what the expected thresholds would be in over for vendors to categorize their solutions? |
| ANSWER |
| If the offeror’s solution meets requirements listed in 6.1.1.3, it is classified as a bulk storage system. |
| QUESTION # |
| 053 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 4 - 5 |
| SECTION NO. |
| 6.1.1.4 |
| SECTION NAME |
| Network Attached Storage (NAS) Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| Can DISA expand on what is intended by the "multi-tenancy" requirement or provide an example of how this is implemented in the current environments? |
| ANSWER |
| Multi-tenancy is defined as the ability to utilize the same solution for multiple client systems, while providing the same level of service to all workloads accessing the solution. The granularity will be defined by the offeror’s solution |
| QUESTION # |
| 054 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 4 - 5 |
| SECTION NO. |
| 6.1.1.4 |
| SECTION NAME |
| Network Attached Storage (NAS) Solutions |
| SECTION TEXT |
| 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
| QUESTION |
| FIPS 140-2 has four associated levels. Is it the intent of DISA to require up to level four for all proposed storage solutions? Also, will this include the key management system that will be needed for the encryption operations? |
| ANSWER |
| The offeror’s solution must include all software and hardware required, to include key management. Encryption has been moved to the optional section. Storage systems that require the encryption option are listed in the PWS. The offerors solution should have the flexibility to support any and all levels of FIPS compliance. |
| QUESTION # |
| 055 |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS).docx |
| PAGE |
| 5 |
| SECTION NO. |
| 6.1.6 |
| SECTION NAME |
| Subtask 1.6 |
| SECTION TEXT |
| Provide storage area network (SAN) solutions that support common industry storage networking protocols such as Fibre Channel and Ethernet. Provide solutions for storage switching requirements priced on a per port basis. |
Deliverable/s: Solutions which support common industry storage protocols and are on a per port basis.
| QUESTION |
| For SAN connectivity does DISA currently use or desire to migrate to 16Gb fiber switches? |
| ANSWER |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .