The file's text, extracted by GovTribe without its formatting.
Attachment J-6 - Question Answer Submission Template for RFP HC1028-13-R-0015
| SECTION NAME |
| L; Page Size and Format |
| SECTION TEXT |
| “Pages should be typed with 1.5 line spacing.” |
| QUESTION |
| Does the 1.5 line spacing statement apply to our responses provided in attachments including L3, L6 and L7? The Government didn’t provide these attachments in 1.5 line spacing. |
| ANSWER |
| Attachments L3, L6 and L7 may be submitted with the same line spacing as in the Government-provided templates. |
| DOCUMENT |
| Solicitation Amendment 004 and Questions and Answers |
| SECTION NAME |
| 5.2 Relevant Contracts; 2.2 Organization/Page Limits - Table 2.2; Attachment L-2. B. Past Performance Information Sheet; Answer 250 |
| SECTION TEXT |
| 5.2 Relevant Contracts - Total page count will not exceed 40 pages |
Table 2.2 – Proposal Organization
Table of Contents – 1 page
Summary Page – 1 page per past performance effort.
Organizational Documentation – 1 Summary Page, 1 pamphlet or 1 commercial document.
Past performance efforts - 40 total pages – Cannot exceed a total of 4 pages each to include Attachment L-3, Attachment L-3 – 4 pages per effort.
Offerors must submit a minimum of two references for the offeror/prime, teaming partner, and/or joint venture partner (within the same division or cost center) and a minimum of two references for each subcontractor as stated in L-2 para b. Consent letters cannot exceed a total of 2 pages. Client Authorization letters cannot exceed 1 page.
Attachment L-2, B. Past Performance Information Sheet
Answer 250: The maximum number of Past Performance Information Sheet/Reference submissions is 4. The page limit for each Past Performance Information Sheet (Attachment L-2) is 4 pages. The page limit for each past performance effort submitted, to include the Past Performance Information Sheet, is 10 pages.
3. The total for Performance Information sheets only will not exceed four - two of which must be from the offeror/prime. Total page count will not exceed 40 pages.
| QUESTION |
| There were several questions regarding the instructions for page counts for Volume III, Past and Present Performance. Questions include 003, 069, 087, 088, 153, 212, 216 and 250. |
With respect, the answers provided, and the changes to the instructions did not clarify the Government’s requirements. The Past Performance Information Sheets, Attachment L-3 are slightly more than 2 pages as provided by the government. When completed by the offeror, the instructions seem to require that L-3 can be no more than 4 pages in length, effectively limiting the offerors response to L-3 to 2 pages. “Past performance effort” is mentioned in several places, not defined. The page limit of each “past performance effort” is 10 pages.
Since Volume II represents 40% of the evaluation, clarity in requirements is important.
To clarify all the requirements of Volume III, please confirm or correct the following:
1. Volume III Table of Contents is limited to one (1) page. The Table of Contents is not included in a total page count for Volume III.
2. No matter what the configuration of an offeror’s team is, there must be a minimum of two (2) and maximum of four (4) past performance references. The answer to question 088 and 250 state: “The page limit for each past performance effort submitted, to include the Past Performance Information Sheet, is 10 pages.” Please confirm that “past performance effort” includes the Attachment L-3 Past Performance Information Sheet and any other relevant information, and that each “past performance effort” may be up to 10 pages in length. Please confirm that Attachment L-3 together with other relevant information, when completed by the offeror may be up to ten (10) pages in length. Further, please confirm that only total of all “past performance efforts” submitted are limited to a total of forty (40) pages. If this is not correct please clarify.
3. The answer to question 088 states “The Summary Page (per offeror, subcontractor, teaming partner, and/or joint venture partner) is limited to 1 page.” And, in Attachment L-2, item A.2 it also states a “Summary Page (per offeror, subcontractor, teaming partner, and/or joint venture partner)…”. However, Table 2.2 in Section L states “Table of Contents – 1 page Summary Page – 1 page per past performance effort.” Please confirm that the Government wants one Summary limited to one page (per offeror, subcontractor, teaming partner, and/or joint venture partner), and that this/these page(s) are not included in the total forty (40) page count for “past performance efforts”.
4. Please confirm that the “Consent Letters” cannot exceed two (2) pages, AND that the “Consent Letters” are not included in the total forty (40) page count for “past performance efforts”.
5. Please confirm that the “Client Authorization Letters” cannot exceed one (1) page, AND that the “Client Authorization Letters” are not included in the total forty page count for “past performance efforts”.
6. Please confirm that “Organization Structure Change History” is limited to one (1) summary page, or one (1) pamphlet (which has no page limit), or one (1) commercial document (which has no page limit), AND that the “Organization Structure Change History” is not included in the total forty page count for “past performance efforts”, as is stated in the answer to question 216.
| ANSWER |
| 1. It is correct that the Table of Contents is not included in the total page count for Volume III. |
2. Attachment L-3 may only include up to 4 pages. Additional past performance information per effort may be provided up to 6 pages. The total page limit for Attachment L-3 and additional past performance information, per effort, may not exceed 10 pages. The total of all past performance efforts submitted may not exceed 40 pages.
3. It is correct that the summary page is limited to one page for each offeror, subcontractor, teaming partner, and/or joint venture partner. The summary page is not included in the total page count for Volume III.
4. As stated in Table 2.2 of the RFP, consent letters cannot exceed two pages. It is correct that consent letters are not included in the total page count for Volume III.
5. As stated in Table 2.2 of the RFP, Client Authorization Letters cannot exceed one page. It is correct that Client Authorization Letters are not included in the total page count for Volume III.
6. As stated in Table 2.2 of the RFP, the Organization Structure Change History cannot exceed one summary page, one pamphlet or one commercial document. It is correct that the Organization Structure Change History is not included in the total page count for Volume III.
| DOCUMENT |
| HC102813R0015Amd0004 |
| SECTION NO. |
| Table 2.2 Proposal Organization & 2.2.1 Page Limitations |
| SECTION TEXT |
| Table 2.2 – Executive Summary/Page Limit 10 (Includes Master Table of Contents) |
Question 070 Response: The master table of contents is included in the 10-page limit for the total Executive Summary.
2.2.1 - Each page will be counted except the following: Cover pages, tables of contents, tabs, glossaries.
| QUESTION |
| These statements are in conflict. Can the government please clarify that it wants a nine (9) page Executive Summary and a very condensed one (1) page Master Table of Contents? |
| ANSWER |
| The Government has determined that the Master Table of Contents will be excluded from the page limit for the Executive Summary. The Master TOC pages will not be counted IAW Section 2.2.1 of the RFP. |
| DOCUMENT |
| Solicitation Amendment 0004 |
| SECTION NAME |
| Information to Offerors and Instructions for Proposal Preparation |
| SECTION TEXT |
| 7.1 Representations and Certifications. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal must include a signed copy of the solicitation and completion of Sections A through K. |
| QUESTION |
| Amendment 0004 made changes to Section I, leaving some of the original Section I unchanged. The Government did not provide a complete replacement of Section I in Amendment 0004. How should the offeror complete Sections A through K? Does the Government require the offeror to “redline” the original Section I in accordance with Amendment 0004, submit copies of Amendment 0004 (and all other amendments), or will the Government replace the original solicitation with an entire new solicitation that includes Sections A through K conformed to all amendments? |
| ANSWER |
| Each amendment supersedes the previous version of the RFP. Offerors should base proposal submissions on the most current amendment posted on FedBizOpps. Changes to the RFP have been highlighted to assist offerors in identifying revisions. A conformed copy of the RFP will be included on FedBizOps. |
| DOCUMENT |
| Solicitation Amendment 0004 |
| SECTION NAME |
| Contract Clauses |
| SECTION TEXT |
| The following have been added by reference: 52.212-4 Contract Terms and Conditions--Commercial Items JUL 2013 |
| QUESTION |
| Amendment 0004 incorporated 52.212-4, and deleted certain specific FAR clauses that do not apply to contracts for commercial items. Most of the FAR and DFAR clauses that were incorporated by reference or incorporated by full text in the original solicitation were retained. The result is that there are several redundancies between 52.212-4 and the original FAR clauses in section I, specifically: |
Original Solicitation
FAR 52.212-4
52.229-3 Federal State and Local Taxes
52.212-4 (k) Taxes
52.243-1 Alt I Changes--Fixed Price (Aug 1987) - Alternate I APR 1984
52.212-4 (c) Changes 52.246-20 Warranty of Services
52.212-4 (o) Warranty
52.249-2 Termination for the Convenience of the Government (Fixed Price)
52.212-4 (l) Termination for the Government’s convenience 52.249-8 Default (Fixed Price Supply and Service)
52.212-4 (m) Termination for cause We understand that the PWS and QASP set forth the standards of performance required by the contract. However, with regard to warranty, 52.212-4 (0) and the prescription at 12.302 (d) permit the negotiation and inclusion of customary commercial warranties to the extent they do not conflict with statutory or other contract requirements.
With regard to termination, the prescription at 12.403 Termination provide in part: “(a) General. The clause at 52.212-4 permits the Government to terminate a contract for commercial items either for the convenience of the Government or for cause. However, the paragraphs in 52.212-4 entitled “Termination for the Government’s Convenience” and “Termination for Cause” contain concepts which differ from those contained in the termination clauses prescribed in Part 49. Consequently, the requirements of Part 49 do not apply when terminating contracts for commercial items…”
Will the Government resolve these redundancies by deleting 52.229-3, 52.243-1, 52.246-20, 52.249-2, and 52.249-8? In the alternative will the Government agree that FAR 52.212-4 takes precedence in the event of a conflict between FAR 52.212-4 and any other FAR clause in Section I?
| ANSWER |
| The Government will remove FAR 52.229-3, 52.243-1 and 52.249-8. FAR 52.246-20 applies to the services portion of the requirement and 52.212-4 applies to the supply deliverables. FAR 52.249-2 will remain in addition to the information in paragraph (l) of FAR 52.212-4. |
| DOCUMENT |
| Solicitation Amendment 0004 |
| SECTION NAME |
| Standard Form 30 |
| SECTION TEXT |
| The answers to Questions 005 and 074 are: “The resultant contract awarded from RFP HC102813R0015 will be a contract for commercial items.” |
| QUESTION |
| If the resultant contract will be a contract for commercial items, will the Government Amend the solicitation and replace Standard Form 30 with Standard Form 1449 Solicitation/Contract/Order for Commercial Items? |
| ANSWER |
| The SF 33 Solicitation was issued in order to use the Uniform Contract Format and will not be changed. The Standard Form 30 is the form used for solicitations and contract modifications. |
| DOCUMENT |
| Solicitation Amendment 0004 |
J-1 PWS
| PAGE |
| 2 of the Solicitation; Page 2 of the PWS |
| SECTION NO. |
| SECTION I and PWS Section 4.0 |
| SECTION NAME |
| Contract Clauses and PWS Objectives |
Contract Terms and Conditions--Commercial Items JUL 2013
| QUESTION |
| The answers to Questions 005 and 074 are: “The resultant contract awarded from RFP HC102813R0015 will be a contract for commercial items.” |
52.212-4 (s) (4) permits including “Addenda to this solicitation or contract, including any license agreements for computer software”.
PWS 4.0, page 2: “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. “
FAR 12.302 Tailoring of provisions and clauses for the acquisition of commercial items generally,
(d) Tailoring shall be by addenda to the solicitation and contract provides that” …addenda may include, any other terms or conditions necessary for the performance of the proposed contract ...”
In commercial item contracts additional terms such as commercial software, express warranties or other additional terms necessary for the performance of the contract are incorporated through addenda, as specified in 52.212(s)(4). In order for the Government to maintain operational control, the Government will have to be properly licensed to operate contractor owned and installed products. Where in Volume V shall additional terms, such as software licenses be included?
| ANSWER |
| If offeror’s software licensing agreements mandate licensure to operate software products, the offeror will perform these tasks with government oversight. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 1.CA eHealth |
| QUESTION |
| It is unclear to the offeror how the government will incorporate eHealth into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as CA eHealth without impacting CA eHealth. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 2.Novel Managed Objects / Formula |
| QUESTION |
| It is unclear to the offeror how the government will incorporate Novell Managed Objects / Formula into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as Novel Managed Objects/Formula without impacting Novel Managed Objects/Formula. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 3.IBM Tivoli Monitor |
| QUESTION |
| It is unclear to the offeror how the government will incorporate IBM Tivoli Monitoring into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as IBM Tivoli without impacting IBM Tivoli. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 5.CA Spectrum for Networking |
| QUESTION |
| It is unclear to the offeror how the government will incorporate Spectrum for Networking into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as Spectrum for Networking without impacting Spectrum for Networking. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 7.HP SiteScope |
| QUESTION |
| It is unclear to the offeror how the government will incorporate HP’s SiteScope into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as HP Sitescope without impacting HP Sitescope. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 8.BladeLogic for Server |
| QUESTION |
| It is unclear to the offeror how the government will incorporate BladeLogic into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as BladeLogic without impacting BladeLogic. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 9.Sensage – Log Aggregation |
| QUESTION |
| It is unclear to the offeror how the government will incorporate Sensage into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as Sensage without impacting Sensage. |
| SECTION NAME |
| Enterprise Management Products |
| SECTION TEXT |
| 12.SAP BusinessObjects XI or BOXI |
| QUESTION |
| It is unclear to the offeror how the government will incorporate SAP BusinessObjects into the storage utility model. Can the government provide the level of interoperability and integration needed with the storage environment? |
| ANSWER |
| Offeror’s solution must be capable of operating within the same environment as SAP BusinessObjects XI or BOXI without impacting SAP BusinessObjects XI or BOXI. |
| DOCUMENT |
| PWS Attachment J-1 |
| SECTION NAME |
| 6.2.3 Subtask 2.3 |
| SECTION TEXT |
| 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 email archiving, single instancing, compression, compliance archiving, eDiscovery (content indexing, search, export), and journaling. Solution should be able to support retention rates greater than one year. |
| QUESTION |
| Attachment 2 lists Veritas Netbackup as part of the DISA environment. Can the government confirm the intended use of Netbackup as it pertains to the storage utility, both in scope and capacity? |
| ANSWER |
| Currently, Veritas Netbackup is maintained outside of the ESS I contract. Offeror’s technical solution may be utilized to replace the current Netbackup infrastructure. |
| DOCUMENT |
| PWS Attachment J-1 |
| SECTION NAME |
| 6.2.6 Subtask 2.6 |
| SECTION TEXT |
| 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. |
| QUESTION |
| Can the government please define what they mean by “devices”? Are “devices” disk drives (LUNs) or are they storage arrays? |
| ANSWER |
| The offeror’s technical solution will define the approach for data tiering. Within Section 6.2.6 Subtask 2.6 the Government is looking for a solution that allows for data tiering between storage arrays. |
| DOCUMENT |
| PWS Attachment J-1 |
| SECTION NAME |
| 6.2.6 Subtask 2.6 |
| SECTION TEXT |
| 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 |
| QUESTION |
| In addition, can the government provide the retention policies for each of these intervals? |
| ANSWER |
| Customer Service Level Agreements define the retention policies and will vary based on customer requirements. The Offeror should provide a solution that allows for variable retention rates depending upon customer requirements and service level agreements. |
| DOCUMENT |
| Solicitation Amendment 0004 and J-1 Performance Work Statement |
| PAGE |
| Amendment 0004 Questions 027, 134, and 222. Page 3 of J-1 |
| SECTION NO. |
| Questions 027, 134, and 221. Section 5.8 of the PWS |
| SECTION NAME |
| Questions and Answers and Scope |
| SECTION TEXT |
| Section 5.8: All hardware to support solutions brought into DISA locations for the first time must be new hardware. |
Q 027: 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.
Q 134 All vendor owned hardware must be new to the DISA environment. Hardware is tracked by Serial Number and Bar Code that will be used to verify existing hardware is not being redeployed.
Q 222 The Government maintains an inventory of storage hardware installed in the current environment. 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 |
| From the answers we understand that the definition of “new” means a storage array or frame with a serial number that has not been installed in the DISA environment before. Can an offeror propose or deliver, or both, “remanufactured” or “refurbished” serialized storage arrays or frames as those terms are defined in FAR 11.001 Definitions? |
| ANSWER |
| All existing capacity from the existing contract must be removed and replaced with new hardware, warranted as new from the OEM, and not previously sold, remanufactured, refurbished or otherwise used. All hardware must be new to the DISA environment. |
| DOCUMENT |
| Attachment J-1 PWS / Attachment J-6 |
| SECTION NAME |
| Subtask 2.3 / Question Answer Submission Template |
| SECTION TEXT |
| From the response to Question #177, the government modified section 6.2.3 as follows: |
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 email archiving, single instancing, compression, compliance archiving, eDiscovery (content indexing, search, export) and journaling. Solution should be able to support retention rates greater than one year.
Original question:
Does the multi-site enterprise scale backup/data protection and archiving solution need to support any applications or environments other than Microsoft Exchange? If so, can the government please provide the same level of detail (i.e. compliance archiving, journaling and content indexing, retention rates, etc) for these other environments and applications?
PWS paragraph 6.2.3 is being updated to clarify government requirements.
| QUESTION |
| The government clearly answers the first question, but the second question on compliance archiving, journaling and content indexing, retention rates, etc remains unanswered. Can the government please provide detail on what compliance archiving includes, such as hardware, software, and archiving capacities, as well as the percentage of archive data that needs to be retained over 1 year? |
The incumbent contractor likely has access to, or inherently knows, this information. Incumbent Chipset contractors that may submit proposals for ESS II may have insight as well. All other offerors are at a competitive disadvantaged in terms of pricing and scoping of solutions.
| ANSWER |
| Offeror’s solution should define the archiving capabilities based on common legal compliance requirements. The percentage of data archived varies by customer application and customer use cases. |
| DOCUMENT |
| Attachment J-1 PWS / Attachment J-6 |
| SECTION NAME |
| Subtask 2.3 / Question Answer Submission Template |
| SECTION TEXT |
| From the response to Question #177, the government modified section 6.2.3 as follows: |
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 email archiving, single instancing, compression, compliance archiving, eDiscovery (content indexing, search, export) and journaling. Solution should be able to support retention rates greater than one year.
Original question:
Does the multi-site enterprise scale backup/data protection and archiving solution need to support any applications or environments other than Microsoft Exchange? If so, can the government please provide the same level of detail (i.e. compliance archiving, journaling and content indexing, retention rates, etc) for these other environments and applications?
PWS paragraph 6.2.3 is being updated to clarify government requirements.
| QUESTION |
| If the incumbent has acquired and deployed software to operate in the environment, can that software be transferred to this acquisition or does it have to be re-purchased. For example, if backup and archive licenses (for example Symantec or CommVault) were previously acquired for back up or archive, can the software be reused or redeployed? |
This information is critical to our pricing calculations and represents an advantage to competitors with an existing install base.
| ANSWER |
| There is no specific requirement for any named software in the PWS and the Government is seeking technical proposals to address the stated technical requirements. Offerors providing technical solutions for this solicitation must provide new software and appropriate licensing to meet the stated technical requirements. All software provided by any offeror is licensed by the offeror through the software vendor(s) and the Government is not a party to or responsible for any software licensing within the scope of this contract. |
| DOCUMENT |
| Q&A files released by Gov on October 24th, 2013 |
| SECTION NO. |
| Question #66 on Section 6.2.2.3 |
| 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 |
Previous question was – “What are the required retention periods for disaster recovery backups and archival data?”
| QUESTION |
| The government’s answer to this previous question was “Current retention requirements vary based on security policies, customer requirements and legal statutes, and may not accurately reflect future requirements. Offeror solution should be flexible and capable of supporting any future retention requirements.” |
For migration sizing, can the government please provide the “current retention requirements” and the amount of archived data that exists in the environment today that maps to each of those retention requirements?
The incumbent contractor likely has access to, or inherently knows, this information. Incumbent Chipset contractors that may submit proposals for ESS II may have insight as well. All other offerors are at a competitive disadvantaged in terms of pricing and scoping of solutions.
| ANSWER |
| Customer Service Level Agreements define the retention policies and will vary based on customer requirements. The Offeror should provide a solution that allows for variable retention rates depending upon customer requirements and service level agreements. |
| DOCUMENT |
| Attachment J-1/J-6 |
| SECTION TEXT |
| 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 ser-vice 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 con-tract. 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.
| QUESTION |
| For pricing purposes, are new software licenses required for the new hardware environment? Does new storage hardware mean that the array or appliance based software licenses are new or can be redeployed from previously installed hardware? |
The incumbent contractor likely has access to, or inherently knows, this information. Incumbent Chipset contractors that may submit proposals for ESS II may have insight as well. All other offerors are at a competitive disadvantaged in terms of pricing and scoping of solutions.
| ANSWER |
| There is no specific requirement for any named software in the PWS and the Government is seeking technical proposals to address the stated technical requirements. Offerors providing technical solutions for this solicitation must provide new software and appropriate licensing to meet the stated technical requirements. All software provided by any offeror is licensed by the offeror through the software vendor(s) and the Government is not a party to or responsible for any software licensing within the scope of this contract. Additionally, licensing for array or appliance based software would be the responsibility of the offeror through their technical solution. |
| DOCUMENT |
| Q&A files released by Gov on October 24th, 2013 |
| SECTION NO. |
| Question #178 on Section 6.2.3 |
| SECTION TEXT |
| 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 email archiving, single instancing, compression, compliance archiving, eDiscovery (content indexing, search, export) and journaling. Solution should be able to support retention rates greater than one year. |
Previous question was – “Can the government please provide detail on the level of compliance archiving they expect in the solution?”
| QUESTION |
| The government’s answer to this previous question was “PWS paragraph 6.2.3 is being updated to clarify government requirements.”, yet no additional details were provided to the level of compliance archiving. |
Can the government please provide the details on the level of compliance archiving that they expect in the solution?
| ANSWER |
| Offeror’s solution should define the archiving capabilities based on common legal compliance requirements. The percentage of data archived varies by customer application and customer use cases. |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS) / Attachment J-6 |
| SECTION NO. |
| 6.1.1.6 / #63 |
| SECTION NAME |
| TASK 1 – Storage solutions and capabilities |
| SECTION TEXT |
| Provide storage solutions that include data de-duplication capabilities which support data replication, are scalable up and down and minimize downtime. |
Question/Response for #63
Does the requirement for data de-duplication, data replication apply as features of all storage classes, or a separate capability that can be added as needed?
De-duplication can be provided as a separate capability. The de-duplication solution must include the ability to replicate de-duplicated data.
| QUESTION |
| Will this class of storage be utilized primarily for backup/archiving? |
| ANSWER |
| The primary use for the capacity will be to accomplish backup and archiving; but the solution may be used for any other capabilities that the offer’s solution can support. |
| DOCUMENT |
| J-1 PWS / Attachment J-6 |
| SECTION NO. |
| 6.2 Task 2 / #127 |
| SECTION NAME |
| Additional Storage Capabilities. And, Attachment 6 of the PWS, Page 2, NIST Definition of Cloud Computing |
| SECTION TEXT |
| “6.2.2 Subtask 2.2 – Provide storage solutions that facilitate DISA’s ability to provide private, public and hybrid cloud storage capabilities to the DoD.” NIST definitions: “Deployment Models: Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.” |
Original Question
Will DISA adhere to the NIST definition of private cloud, specifically that a private cloud may exist on or off DISA and government premise?
The following footnote has been added to PWS Attachment 4: "While NIST definition states private cloud may exist on premise or off premise, the DISA private cloud will exist on premise within DISA managed facilities."
| QUESTION |
| Will DISA allow a cloud solution that ensures all data is kept on premises, but utilizes an authentication protocol, which resides off premise in CONUS? |
| ANSWER |
| No. The offeror’s solution should be CaC and PKI enabled, and allow for authorization from within the Government enclave. |
| SECTION NO. |
| Task 2 – Additional Storage Capabilities |
| SECTION NAME |
| 6.2.1 Subtask 2.1 |
| SECTION TEXT |
| Provide solutions for archive data storage that provides compliance with DoD 5015-2 Records Management Directive. |
| QUESTION |
| In order for a storage device to maintain 5015.2 compliancy; the software writing to the storage must also be 5015.2 compliant. What software is the government planning on using to write to the 5015.2 compliant storage? |
| ANSWER |
| The Government currently does not have a records management solution. The Offeror’s solution should provide all required software to manage, utilize, and maintain the solution that is compliant with DoD 5015.2. |
| SECTION NO. |
| Task 2 – Additional Storage Capabilities |
| SECTION NAME |
| 6.2.3 Subtask 2.3 |
| SECTION TEXT |
| 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 email archiving, single instancing, compression, compliance archiving, eDiscovery (content indexing, search, export) and journaling. Solution should be able to support retention rates greater than one year. |
| QUESTION |
| Can the government please explain what they mean by “compliance archiving”? |
| ANSWER |
| Offeror’s solution should define the archiving capabilities based on common legal compliance requirements. The percentage of data archived varies by customer application, and customer use cases. |
| DOCUMENT |
| Amendment 004, J-6 |
| PAGE |
| Various Pages. Questions: 003,059,061,150,157,158, 159,160,161,162,163,164,165,166,182,222,224 |
| SECTION NAME |
| Question Answer Submission Template for RFP HC1028-13-R-0015 |
| SECTION TEXT |
| Answer 172: The offeror is expected to provide solutions based on requirements dictated in the PWS. The storage environment is dynamic, and the current environment is not a reflection of future requirements. |
Answer 182: The storage environment within DISA is dynamic and the current environment is not a reflection of future requirements. This information will be passed to the Offeror once the award has been made.
Answer 222: The Government maintains an inventory of storage hardware installed in the current environment. 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 |
| We and other potential offerors asked questions seeking specific information about DISA’s current environment. The questions above were answered in substantially the same way, as in answer 172 and 182 above. |
We understand that DISA’s future requirements are dynamic, and that offeror’s solutions must be dynamically flexible as a result.
However, our questions were not directed toward DISA’s future environment. Rather we seek information about DISA’s current, existing environment. This information is critical in order to develop a migration plan and transition strategy, and to properly size SRM requirements for purposes of migration. Most importantly, this information is critical so that transition and migration can be priced in the most cost effective manner for DISA and DISA’s customers.
DISA stated in its answer to Question 222 that the Government maintains an inventory of storage hardware, tracked by serial number. Although Attachment 1 is labeled “Storage Inventory”, it is only a list of products by manufacturer. It does not provide the kind of information that a detailed, serialized inventory would contain.
The incumbent contractor likely has access to, or inherently knows, this information. Incumbent Chipset contractors that may submit proposals for ESS II may have insight as well. All other offerors are at a competitive disadvantaged in terms of pricing and scoping of solutions.
To be fair to all competitors, will DISA please amend the solicitation and incorporate the detailed “inventory of storage hardware installed in the current environment” so that all competitors have equal access to this information?
| ANSWER |
| The storage environment within DISA is dynamic and the current environment is not a reflection of future requirements. This information will be passed to the Offeror once the award has been made. Additionally, the migration approach may not incorporate a like-for-like end state of installed hardware. The offeror’s solution should provide flexibility to support a dynamic environment currently. |
| DOCUMENT |
| J-3 Cost Model Amd 4 |
| PAGE |
| B-Table, Scenario 1, 2, and 3 tabs |
| SECTION TEXT |
| SLIN 0001AN - Continuous data protection solution - CONUS. Unit of Per terabyte protected per day |
SLIN 0003AN - Continuous data protection solution - OCONUS. Unit of Per terabyte protected per day
| QUESTION |
| Can the government please: |
1) Provide the number of recover point objectives that will be required and maintained for each of the 30-minute or less, 8-hour or less, and 24-hour SLINs so we can accurately size the solution
- or –
2) To make costs predictable, can the government make the SLIN numbers measured as raw terabytes per day for replicated capacity.
| ANSWER |
| The offeror’s solution will dictate the number of recover points available for each interval. |
The Government will utilize a protected per TB per day metric to maintain consistency.
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS) |
| SECTION NAME |
| Task 7 – Performance and Availability |
| SECTION TEXT |
| 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. |
| QUESTION |
| Based on the first round of questions (Question 067) for this section you answered: Physical separation of all components is required between all classification levels. Management and billing systems will require completely separate instances on unclassified and classified networks. Does your answer to Question #67 in the first round of question mean that two (2) independent billing and invoicing systems must be implemented by the offerer? |
| ANSWER |
| For the purposes of ESS II contract administration, the offeror should implement a single call order management system for billing and invoicing. |
| DOCUMENT |
| J-3 Cost Model Amd 4 |
| SECTION NAME |
| Storage Area Networks SAN Switches - (OCONUS) |
SECTION TEXT
| QUESTION |
| During contract month 48, there is a listing for total SAN ports installed of 1,380,282. |
How does this break out for storage side ports and server side ports?
| ANSWER |
| Quantities for SLINs 0003AF01 and 0003AF02 have been updated. |
| DOCUMENT |
| HC102813R0015Amd0004.doc |
| SECTION NAME |
| Organization/Page Limits; Table 2.2 - Proposal Organization |
| SECTION TEXT |
| “10 (Includes Master Table of Contents)” |
| QUESTION |
| In order to provide a comprehensive Master Table of Contents (TOC) that includes a List of Exhibits, would the Government please allow offerors to attach the Master TOC as an appendix to the Executive Summary that is not included in the 10-page limit? |
| ANSWER |
| The Government has determined that the Master Table of Contents will be excluded from the page limit for the Executive Summary. The Master TOC pages will not be counted IAW Section 2.2.1 of the RFP. |
| DOCUMENT |
| HC102813R0015Amd0004.doc; J-6_Question_Answer_Submission_001_thru_014.doc |
| SECTION NO. |
| L.2.2, Table 2.2; Question #002 |
| SECTION NAME |
| Organization/Page Limits, Table 2.2 – Proposal Organization; Question #088 ANSWER |
| SECTION TEXT |
| Table 2.2 – Proposal Organization, Volume III Relevant Past Performance: “Table of Contents – 1 page Summary Page – 1 page per past performance effort. Organizational Documentation – 1 Summary Page, 1 pamphlet or 1 commercial document. Past performance efforts - 40 total pages – Cannot exceed a total of 4 pages each to include Attachment L-3, Attachment L-3 – 4 pages per effort. Offerors must submit a minimum of two references for the offeror/prime, teaming partner, and/or joint venture partner (within the same division or cost center) and a minimum of two references for each subcontractor as stated in L-2 para b. Consent letters cannot exceed a total of 2 pages. Client Authorization letters cannot exceed 1 page.” |
Question #002 ANSWER: a) The maximum number of Past Performance Information Sheet/Reference submissions is 4. b) The page limit for each Past Performance Information Sheet (Attachment L-2) is 4 pages. The page limit for each past performance effort submitted, to include the Past Performance Information Sheet, is 10 pages.”
| QUESTION |
| Section L.2.2, Table 2.2, states that each past performance effort should include: (1) a 1-page Summary Page; (2) a 1-page Organizational Documentation Summary Page; (3) a 4-page Past Performance Information Sheet; (4) a 2-page [max.] Consent Letter; and (5) a 1-page [if applicable] Client Authorization Letter. We calculate this totals a maximum of 9 pages per past performance effort. Question #088 ANSWER states, “…The page limit for each past performance effort submitted, to include the Past Performance Information Sheet, is 10 pages….” |
Question: If Section L.2.2., Table 2.2 indicates a maximum of 9 pages per effort and Question #088 ANSWER indicates a maximum of 10 pages per effort, will the Government please clarify what is to be included in the additional one page per past performance effort?
| ANSWER |
| The Summary Page, Organizational Documentation, consent letters and client authorization letters are excluded from the 40 page limit for all past performance efforts. |
| DOCUMENT |
| HC102813R0015Amd0004.doc |
| SECTION NO. |
| Attachment L-2, A.2 |
| SECTION TEXT |
| “2. Summary Page (per offeror, subcontractor, teaming partner, and/or joint venture partner)…” |
| QUESTION |
| Attachment L-2 indicates that a Summary Page shall be provided “per offeror, subcontractor, teaming partner, and/or joint venture partner.” Table 2.2 in Section 2.2 of Section L indicates that a Summary Page shall be provided “per past performance effort.” |
In an effort to reduce redundancy, would the Government please confirm that a Summary Page is required for each “offeror, subcontractor, teaming partner, and/or joint venture partner” and not for each past performance effort?
| ANSWER |
| A Summary page should be submitted per offeror, subcontractor, teaming partner and/or joint venture partner with an understanding that only four past performance efforts may be submitted per proposal. |
| DOCUMENT |
| HC102813R0015Amd0004.doc |
| SECTION NO. |
| Attachment L-2, B. |
| SECTION NAME |
| Past and Present Information Sheets |
| SECTION TEXT |
| “B.2. TWO – Performance Information Sheets (Attachment L-3) for each major or critical subcontractor.” |
“B.3. The total for Performance Information sheets only will not exceed four – two of which must be from the offeror/prime.
L.2.2, Table 2.2: “a minimum of two references for each subcontractor as stated in L-2 para b”
| QUESTION |
| Please clarify whether the two Past Performance Information Sheets for each major or critical subcontractor must be for the same subcontractor or can they be for different subcontractors. |
| ANSWER |
| Two Past Performance Information Sheets may be submitted for the same subcontractor or one Past Performance Sheet may be submitted for up to two different subcontractors. RFP language has been updated. |
| DOCUMENT |
| HC102813R0015Amd0004.doc |
| PAGE |
| 19 of 49; 26-27 of 49 |
| SECTION NO. |
| L.5.1; Attachment L-2, B. |
| SECTION NAME |
| General; Past and Present Information Sheets |
| SECTION TEXT |
| “This information is required on the Offeror and subcontractors, teaming partners, and/or joint venture partners who are proposed to perform at least 40% of the proposed effort based on the total proposed price or perform aspects of the effort the Offeror considers critical to overall successful performance.” |
“B. …This information is required on the offeror/prime, teaming partners, and/or joint venture partners and subcontractors proposed to perform at least 40% of the proposed effort based on the total proposed price, or perform aspects of the effort the offeror considers relevant to overall successful performance.”
“B.2. TWO – Performance Information Sheets (Attachment L-3) for each major or critical subcontractor.”
“B.3. The total for Performance Information sheets only will not exceed four – two of which must be from the offeror/prime.”
| QUESTION |
| If the two Performance Information Sheets for each major/critical subcontractor must be from the same subcontractor, this limits our ability to include past performance for an additional subcontractor whom we consider to be critical and relevant to overall successful performance. We respectfully request that the number of Past Performance Information Sheets be increased to six in order to include past performance from an additional major/critical subcontractor whom we consider to be critical to overall successful performance. |
| ANSWER |
| Two Past Performance Information Sheets may be submitted for the same subcontractor or one Past Performance Sheet may be submitted for up to two different subcontractors. RFP language has been updated. Offerors may utilize other subcontractors to support their technical solution, but only four past performance information sheets/past performance efforts will be evaluated per proposal. |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS)_RFP_Amd_4.docx |
| SECTION TEXT |
| 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 |
| Does this response imply that unbarcoded equipment can be reused? |
| ANSWER |
| For disk drives that are not barcoded, incumbent will provide the Government with a list of disk drive serial numbers as old equipment is decommissioned, the new vendor will provide new disk drive serial number and Government will verify and ensure old serial numbers are not reused. |
| DOCUMENT |
| J-1_Performance_Work_Statement_(PWS)_RFP_Amd_4.docx |
| SECTION TEXT |
| “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 email archiving, single instancing, compression, compliance archiving, eDiscovery (content indexing, search, export) and journaling. Solution should be able to support retention rates greater than one year.” |
This is the start of the file's text. The full file is on GovTribe.