2014-07-02_ECP_RFP_MASTER_LIST_OF_INDUSTRY_QUESTIONS_V.11.docx

MASTER LIST OF INDUSTRY QUESTIONS

RFP SAQMMA14R0308

07/02/14

Please note that “Q” indicates the Offeror’s original question and “A” indicates the DOS answer. Where there are separate responses for the Domestic Data Center and the Remote Offices, “DA” represents the answer for the Domestic Data Center and “RA” represents the answer for the Remote Offices. Where it was unclear if the question was for Domestic Data Centers or Remote Offices, responses for both are provided.

DOS RESPONSES / CLARIFICATIONS (DA, RA, A)

A1

Q: What application(s) do you intend to run on this converged infrastructure?

DA: ECP will be a hosted compute environment, and any application could be hosted on the solution. The Government does not intend to impose application specific requirements, only infrastructure requirements for the Offeror’s solution.

RA: Remote Office requirements are as stated in SOW Section 4.3.4, “Computing.”

A2

Q: What requirements does that (/those) application have? (CPU architecture, #cores, etc.)

DA: ECP will be a hosted compute environment, and any application could be hosted on the solution. The Government does not intend to impose application specific requirements, only infrastructure requirements for the Offeror’s solution.

RA: Remote Office requirements are as stated in SOW Section 4.3.4, “Computing.”

A3

Q: What kind of computing workload(s) are expected to run on the converged infrastructure?

DA: ECP will be a hosted compute environment, and any application could be hosted on the solution. The Government does not intend to impose application specific requirements, only infrastructure requirements for the Offeror’s solution.

RA: Remote Office requirements are as stated in SOW Section 4.3.4, “Computing.”

A4

Q: Approximately how many users do they expect?

DA: User count is not relevant to this RFP.

RA: User count is referenced in the VM Minimum Configuration Table in SOW Section 4.3.4, “Computing.”

A5

Q: How much storage (raw) is required?

DA: DOS has clarified baseline configuration requirements in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

RA: User count is referenced in the VM Minimum Configuration Table in SOW Section 4.3.4, “Computing.”

A6

Q: What precisely is meant by “data offshoring solutions for Disaster Recovery (DR)”?

A: It is the capability to conduct a back-up (site-to-site replication and recovery) from a remote location overseas. Reference SOW Sections 4.2.6 and 4.3.6.

A7

Q: We respectfully request that the Department of State grant a two week extension.

A: No extension to the proposal due date is contemplated at this time.

A8

Q: [We] would like to inquire if the Department of State may be interested in hearing about a new technological solution for these requirements.

A: Offerors are encouraged to develop innovative solutions while satisfying all requirements of the RFP per SOW section 4.1.1.

A9

Q: The general requirements make a number of assumptions about storage architectures that are not relevant to alternative approaches to data storage. Would the Department of State entertain solutions that provide the required functionality in a more efficient and less costly way, but do not strictly adhere to the stated requirements?

A: Offerors are encouraged to develop innovative solutions while satisfying all requirements of the RFP per SOW section 4.1.1.

A: The Government will review the Offeror’s solution with regard to all requirements stated in the RFP.

A: A series of performance counters will be used to determine if a proposed solution provides “near-linear” performance. Offerors are expected to be able to provide performance information as part of their management solution.

A: “Linear capacity” will be determined by the ability to “hot add” the same type of shelves to small, medium, and large storage arrays. The Government requires a standardized solution with interchangeable parts; for example, a shelf for a small array will work on a large array; and vice versa.

A: DOS requires the ability to expand volumes or file systems without operator intervention.

A: DOS requires the capability to separate production data from point-in-time data on differing arrays, disk types, and RAID types from the snapshot data.

A: The requirements remain as stated in SOW Section 4.1.4, “Storage.”

A: Yes, a SFF 2.5” 10K RPM drive would be an acceptable alternative. See Amendment 001.

A: DOS has added requirements for RPO/RTO; see SOW Sections 4.2.6 and 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.” See Amendment 001.

A: The Offeror will not be responsible for shipping. However, data will be transported to offsite locations in one of two ways; the first option is physical media, detailed in the Table in SOW Section 4.3.6, “Removable Media Integration,” and the second option is replication, detailed in the same Table under “Replication.”

A19

Q: The architecture of the solution outlined in the Statement of Work, eliminates other potential architectural solutions, which can provide equivalent or superior performance and cost savings (i.e., Space, Energy, and Operational). Is an equivalent architectural solution, which meets the General Systems Requirements as well as meets or exceeds performance requirements going to be downgraded because of not meeting specific minimum requirements? For example, the use of 15K RPM hard drives can be eliminated by using a Dynamic Random Access Memory (DRAM)-centric Hybrid Storage Pool.

A: Offerors are encouraged to develop innovative solutions while satisfying all requirements of the RFP per SOW section 4.1.1.The Offeror’s solution must comply with or exceed the requirements stated in the solicitation. Flexibility is permitted in places where “or equivalent” is stated.

DA: The Domestic Data Center does not use nor intend to use tape media.

RA: A tape solution is acceptable to meet the requirements in SOW Section 4.3.6, “Backup/Disaster Recovery/Data Offshoring” under the Removable Media Integration Section. However, it cannot replace replication or snapshot requirements.

Q: Can you please clarify the rack requirements: Is the 400lb rack requirement for all deployed solutions, only non-domestic, or mixture of both?

A: The shell of the rack, without any equipment or power distribution installed, must weigh less than 400 lbs., as stated in SOW Section 4.1.2, “General Systems Requirements.” This limitation applies to both the Domestic Data Center and the Remote Offices.

Q: Can you please clarify the rack requirements: Is the 400lb requirement for the rack including all components installed or the rack without any components installed?

A: The shell of the rack, without any equipment or power distribution installed, must weigh less than 400 lbs., as stated in SOW Section 4.1.2, “General Systems Requirements.”

A: It is required that all components fit inside a single rack for the Remote Office solution, but not for the Domestic Data Center solution.

A24

Q: Will any Oracle Databases be deployed on the proposed infrastructure?

DA: Yes, but we are not specifying application-level requirements in this RFP.

RA: This is currently not a requirement, but is possible in the future.

A25

Q: Will any instances of Oracle Weblogic be deployed on the proposed infrastructure?

DA: Yes, but we are not specifying application-level requirements in this RFP.

RA: This is currently not a requirement, but is possible in the future.

B1

Q: Is it the desire of the Government to procure these tools (i.e., SRM tools) separate of ECP and through the existing contract vehicles, or is it the intent that these additional management and provisioning tools be included in the offerors’ proposals?

A: We are looking for the potential Offerors to propose this as a separately priced option, to allow potential Offerors to have a fully inclusive solution. We do not want to limit offerors’ ability to create a complete solution based on the existing Department of state enterprise architecture/licenses.

B2

Q: Were these scenarios anticipated (two systems using the same licensing at the same time), and what is the thought process of how DOS would handle these as part of the solution?

A: Yes we did anticipate it; however, we don’t want to prevent or limit vendors from creating a solution(s) that requires licenses/software that the Department does not have currently.

B3

Q: Your clarity here (regarding support of VMWare licenses through OEM and/or VMWare) would be most appreciated.

A: If the Department determines that additional licensing is required, the Department will contact VMWare directly to procure any additional licenses.

A: The Remote Office environment differs in mission and user quantities that require flexibility in performance and capacity. As stated in the SOW Section 4.1.1, “Innovation,” scalability beyond current deployed systems is one of the goals of this solicitation.

A: Requirements remain as stated.

A: Requirements remain as stated in SOW Section 4.3.4, “Computing.”

A: No, local storage will not be used to store virtual machines. The Offeror must provide appropriate local storage for the VMware or Windows operating system.

A: The Offeror is expected to meet standards where applicable, as listed in SOW Section 11, “Applicable Standards.”

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

C7

Q: Can the DOS provide a roll out schedule of the hardware installations?

A: The installation schedule is not known at this time.

DA: For planning purposes only, the Domestic Data Center anticipates replacement of 20% of their infrastructure annually. This does not obligate the Department to meet this schedule. The Domestic Data Centers’ current infrastructure is described in Identifier 4, “Current Operations Overview.”

RA: Estimated production rates for the Remote Offices are provided in RFP Section L.2.3.4.1.4, “Order Fulfillment.”

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” In addition, Section L.2.5.1 has been revised. See Amendment 001.

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” In addition, Section L.2.5.1 has been revised. See Amendment 001.

A: Section L.2.5.1 has been revised. See Amendment 001.

A: Section L.2.5.1 has been revised. See Amendment 001.

A: The “unit price” is the firm-fixed price for an item proposed to satisfy a CLIN, be it an individual component or fully configured system, in accordance with the instructions at section L.2.5.1.

C13

Q: Does this requirement only apply to mixing of SSD disks and NL disks? If mixing SSD and SAS, what would be the minimum cache requirement?

A: Hybrid disk configurations are acceptable with both SSD/NL and SSD/SAS. There is no minimum cache requirement.

C14

Q: The remote site requirements call for a Keyboard, Video, Mouse (KVM) Console solution – Monitor, keyboard, pointing device. However, there is no mention of a KVM switch. Is a KVM switch required in a multi-server solution?

A: The Offeror shall determine what type of KVM solution will meet the specified requirements. See SOW Section 4.1.9, “Systems Management Suite”, and Sections 4.2.4 and 4.3.4, “Computing.”

C15

Q: Please provide a list of CONUS and OCONUS sites supported. A device count of the legacy platform for each site is also requested.

A: Lists of sites and device counts of the legacy platform are not necessary for the response. Additional information will be provided as task orders are issued under the base contract.

C16

Q: Please define Tier 4 support.

A: See Glossary for definitions of all four Tiers of support.

D1

Q: In which section is the Offeror required to include the Technical Compliance Matrix?

A: The Offeror’s completed Technical Compliance Matrix should be submitted in Volume I, Tab D. The Technical Compliance Matrix is not included in page count limits. See RFP Amendment 0001, section L.2.

D2

Q: Does the Technical Compliance Matrix count against the page limits?

A: The Technical Compliance Matrix does not count against page count limits.

A: Attachment L has been revised; implementation and migration requirements, previously located in Attachment L, Sections L.2.3.3.1, L.2.3.3.1.1, and L.2.3.3.1.2, were relocated to SOW Section 4.3.9. As stated in SOW Sections 4.2.9 and 4.3.9, implementation and migration must be part of the Offeror’s technical solution.

A: “Proof of Configuration” is no longer referenced in Attachment L. However, “Proof of Configuration” is now referenced in SOW Section 4.3.9, and is defined as a quality checklist used to validate that components have been installed, configured, and tested; the Offeror shall include this checklist in its Quality Assurance Plan referenced in SOW Section 5.2.1, “Project Deliverables.”

A: Yes, see the revised DD254.

A: In accordance with SOW section 5.6, all deliveries will be Freight-on-Board (FOB) Origin.

A: The Offeror must meet the requirements described in SOW Section 4.3.4.

A: User sizing is based on total users.

A: Not applicable. User sizing is based on total users.

A: The required security levels are Secret and Top Secret. See the revised DD254.

A: The Offeror is expected to provide a three year base warranty with five optional periods in one year increments, for a maximum of eight years if all options are exercised.

A: SOW Section 4.3.9, “Implementation and Migration,” has been revised to remove “OS version and configuration” and “Installation of applications as necessary.”

A: Yes, it is expected that the ECP Offeror will utilize the existing DOS software ELA’s.

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

A: The percentages of NAS versus SAN storage shall be scalable.

A: Yes, the devices deployed at the remote offices as well as the DDC’s must include the necessary hardware and software to replicate across platforms.

A: There is a new requirement of Intel Xeon Processor E7-2850 or better; the power requirement has been removed. See Amendment 001.

A: In accordance with the SOW Section 4.3.5, “UPS,” the minimum UPS battery run time is 10 minutes. The SOW has been updated to reflect this change. See Amendment 001.

A: Yes, the Offeror is required to provide removable media hardware as part of the backup/off-shoring solution.

A: No, the ECP solution is considered a life-cycle refresh, which will replace legacy equipment to include removable media devices.

A: All ODCs in the LCCM will be assigned a fixed dollar amount that will be used for evaluation purposes for all Offerors for all years in the LCCM.

A: The contract term will be a 1-year base with four 1-year options.

A: This will be completed prior to contract award.

A: No useful data is available for this purpose.

A: The Offeror is expected to provide a three year base warranty with five optional periods in one year increments, for a maximum of eight years if all options are exercised.

A: Yes, the Offeror is required to provide removable media hardware as part of the backup/off-shoring solution. No, the ECP solution is considered a life-cycle refresh, which will replace legacy equipment to include removable media devices.

A: SOW Section 4.2.3, “Storage,” and Section 4.2.10, “Domestic Data Center Baseline Configuration,” have been revised to delete references to “RAID levels 5/6/10,” and it was replaced with “The storage array/system must be able to support a double disk failure without data loss.” See Amendment 001.

A: The storage array/system must be able to support a double disk failure without data loss. See Amendment 001.

A: Yes, this statement is correct. However, the Offeror shall develop a solution that meets all requirements in the RFP.

A: DOS will not require specific application support from the ECP Contractor.

A: The legacy solution consists of NetApp storage with a VMware virtual infrastructure. Applications are listed in SOW Section 4.3.4, “Computing.”

A: There are no current plans to connect devices that are only capable of 100 mb Ethernet.

A: Requirements are as stated in SOW Sections 4.1.3, 4.2.2, and 4.3.2.

A: No, there is not a requirement for the Layer 2 device to be physically separate from the Layer 3 device.

A: Custom RBAC will need to be configurable, but not configured by the ECP Contractor.

F15

Q: Can the Government please clarify which virtualization and cloud management products they management software needs to include plug-ins for?

A: In accordance with SOW Section 4, the ECP solution needs to integrate with VMware.

F16

Q: Can the Government please clarify if the Offeror is expected to perform system pre-shipping work (initial configuration and setup) within a secure facility (SCIF or equal)?

A: No, pre-shipping work, e.g., initial configuration and setup will not be required.

F17

Q: What is the voltage and hertz that is required at each site for CONUS and OCONUS power?

A: Revised requirements are as stated in SOW Sections 4.2.5 and 4.3.5 “UPS.” See Amendment 001.

A: Offeror will certify the interoperability of all OEM-integrated components.

A: No, the licensing is not required in order to preload VMware ESX. The Offeror is only expected to install the software.

A: Enterprise Plus.

A: The Offeror can respond to the solicitation without this information.

A: DOS will apply all WAN QoS configurations.

A: Revised requirements are as stated in SOW Sections 4.2.5 and 4.3.5 “UPS.” See Amendment 001. The Offeror is expected to propose plugs that will meet U.S. and European standards. Power plug types vary by overseas location and will be specified for each task order. See SOW Section 4.1.2, “General Systems Requirements.” After the award of the ECP contract, the contractor shall provide all cabling interconnecting the ECP solution and it shall be clearly labeled at each end of every cable, identifying component endpoints. The contractor is not required to provide any data cabling external to the ECP solution.

A: Yes, the “physical notification of system status” can mean flashing lights, or it can mean an alternative physical notification, such as audible alerts.

A: Yes, a SFF 2.5” 10K RPM drives would be an acceptable alternative.

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

A: Domestic Data Center is a hosted environment and workloads may vary based upon customer base. DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

A: The workload read/write percentages and size are variable based on the applications supported.

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

A: DOS has clarified baseline configuration requirements located in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

DA: There is a new requirement of Intel Xeon Processor E7-2850 or better; the power requirement has been removed. See Amendment 001.

A: DOS has revised the requirements for RPO/RTO. In Amendment 001 see SOW Sections 4.2.6 and 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.”

A: DOS has revised the requirements for RPO/RTO; see SOW Sections 4.2.6 and 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.” See Amendment 001.

A: DOS has revised the requirements for RPO/RTO and retention; see SOW Sections 4.2.6 and 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.” See Amendment 001.

A: The amount and type of data that is being migrated is to be determined after award. All types of data referenced above may be migrated.

A: A list of the locations for remote sites is not required to respond to this RFP. If optional tasks for training or installation services are required, information will be specified in the task order.

A: The requirements for “OS version and configuration” and “installation of applications as necessary” has been deleted from the SOW, paragraph 4.3.9, “Implementation and Migration.” See Amendment 001.

A: Remote Office replication locations and bandwidth will vary. The Offeror shall specify what equipment will be necessary at the replication target.

A: DOS has added requirements for RPO/RTO and restore. In Amendment 001, see SOW Section 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.”

A: DOS has added requirements for RPO/RTO. In Amendment 001, see SOW Section 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.”

A: DOS has added requirements for RPO/RTO and restore. In Amendment 001, see SOW Section 4.3.6, “Back-Up, Disaster Recovery/Data Offshoring.”

A: Not applicable because user sizing is based on total users. The Offeror shall consider the ratio 1:1.

A: This information is contained in SOW Section 4.3.4, “Environmental Parameters.” Space requirements are in SOW Section 4.1.2, “General System Requirements,” under the heading “Rack.”

A: Yes, the Offeror must provide removable media hardware as part of the solution. The ECP is considered a life-cycle refresh, which will replace legacy equipment to include removable media devices.

A: The documents from section 5.2.1 that are to be delivered with the proposal as indicated, are not included in the page count limits for proposals.

A: The Offeror is expected to provide a three year base warranty with five optional periods in one year increments, for a maximum of eight years if all options are exercised.

A: Please reference the Solicitation, page 19 of 37, Section 52.246-19 ALT III “Warranty of Systems and Equipment under Performance Specifications or Design Criteria.”

A: Training will be needed at least annually or anytime there is a major revision of software or hardware.

A: Offerors shall submit a Small Business Subcontracting Plan in Volume III, Tab C with no page limit. See Section L-2, Amendment 001.

A: The VMware vCenter current versions are 4.x and 5.x, but we are currently deploying 5.x.

DA: This information is not needed to answer the RFP.

RA: Currently, 75% of our posts have been virtualized. DOS plans to complete virtualization by July 2015.

A: The ultimate goal for the DOS environment is to be 100% virtualized.

A: Provisioning requirements have been revised. See Amendment 001, SOW Section 4.3.9, “Implementation and Migration.”

A: DOS will provide this information, as appropriate, when task orders are issued.

A: Presently DOS is not soliciting alternative finance options.

A: There is no required or preferred number. Offerors (and its 2 largest subcontractors) may submit as many past performance references as are relevant to this acquisition.

A: Yes, see sections M.3.2.3.1 and M.3.2.3.2.

A: The relative weightings of the evaluation factors are defined in section M.2(a).

A: The relative weightings of the evaluation factors are defined in section M.2(a).

A: The determination of the need for a competitive range and call for final proposal revisions will be made by the CO if such actions are In the best interest of the Government.

A: This question is not relevant to respond to this solicitation. Any inquiries regarding the accomplishment of the Department’s small and disadvantaged business goals can be made to the DOS Office of Small and Disadvantaged Business Utilization.

A: 4th quarter of FY14.

A: No date has been set, but it can be as soon as 30 days after contract award (see section L.2.3.3.2.5), if task order(s) are issued at contract award.

H1

Q: Would the Government supply a list of each Embassies inventory of virtual machines currently running, including provisioned resources?

A: No, the Government has provided workload information in SOW Section 4.3.4, “Computing.”

H2

Q: Would the Government supply a list of the ESXi/vSphere host versions running at all locations within the DOS ecosystem?

DA: For the Domestic Data Center, the current ESXi/vSphere host version is 5.x within the DOS ecosystem.

RA: For the Remote Offices, the current ESXi/vSphere host version is 4.x within the DOS ecosystem. New implementations will be 5.x.

H3

Q: Is there existing Rack Space at the individual Embassies which can be utilized for a hyper-converged deployment? For example, a converged solution only requiring 4U-6U of total rack space.

A: Rack space in existing Remote Offices varies. If a composite solution is ordered, then the Offeror is expected to provide the required space in their rack solution. However, if components are ordered, the DOS will install the components in the existing rack. See SOW Section 4.3.4, “Computing.”

H4

Q: What is the number of vCenter’s running enterprise-wide, and where are they located?

A: This information is not necessary to respond to the RFP.

H5

Q: What is the number of sites being supported per each vCenter?

A: This information is not necessary to respond to the RFP.

H6

Q: Blade server form fact is specifically mentioned in this RFP. Would the Government consider alternative form factor solutions that include features such as power savings, reduced rack consumption, and low heat output?

A: Yes, the Government would consider such alternative form factor solutions.

H7

Q: Does the Government currently have excess switching capacity at the foreign and domestic sites? If so, will the Government provide the availability of the excess switching at each site?

A: The ECP solution must provide all internal switching. The Offeror shall meet all requirements in SOW Sections 4.2.2 and 4.3.2, “Networking.”

A: Yes, the term of the contract is a 1-year base with four 1-year options.

A: RFP Section B-007 is “Rate for Indefinite Delivery Contracts.” There is no penalty associated with this clause.

A: The project documents described in the SOW Section 5.2.1 and Attachment L, Section L2.3.3.2.2 are not included in the page count for Volume I.

A: The project documents described in the SOW Section 5.2.1 and Attachment L, Section L2.3.3.2.2 are not included in the page count for Volume I.

A: Three each corporate experience summaries from the Offeror and its two largest subcontractors (3 ea.) equals nine total.

A: Three each corporate experience summaries from the Offeror and its two largest subcontractors (3 ea.) equals nine total.

A: DOS has no size definitions for “large” subcontractors. As the prime contractor, your organization determines with whom it subcontracts and the relative size of those subcontracts.

A: The Technical Compliance Matrix (TCM) should be included in proposal Volume I as Tab D, which has no page restrictions.

A: Yes, the TCM should be included in proposal Volume I as Tab D, which has no page restrictions.

A: The Offeror should complete the TCM by inserting for each item in the TCM, a reference to its technical proposal by volume, section, paragraph and page number.

A: Yes, the section references in SOW 4.1.5 (“Computing”) should be 4.2.4 and 4.3.4.

A: Section L, Paragraph L.2, Volume I has been revised to allow for an overview of your technical approach and solution. See Amendment 001.

A: The requirement remains as stated.

A: In the Federal Government, all networking equipment is required to be IPV6 compatible. DOS acknowledges that the current version of VMware cannot support IPV6 for iSCSI.

A: SOW Section 4.1.9 has been revised. See Amendment 001.

DA: The Domestic Data Center infrastructure is described in Current Operations Overview Section 2. In addition, we provided baseline configuration requirements in the table in SOW Section 4.2.10 (new), “Domestic Data Center Baseline Configuration.” See Amendment 001.

RA: The Remote Office core infrastructure is described in Current Operations Overview Section 3, “Introduction to the Remote Office Operating Environment.”

I17

Q: The Intel E5-2690 processor is a 135w processor, so there is a discrepancy in the power draw information. Recommend the Government change the statement read "must be 135w or lower processor?

A: There is a new requirement of Intel Xeon Processor E7-2850 or better; the power requirement has been removed. See Amendment 001.

A: The Offeror is not required to provide 8 ECP solutions. The Offeror shall provide the quantity of solutions that best meets the defined requirements. Tiered storage is not specifically required for the Remote Offices, but the performance requirements listed in SOW Section 4.3.4, “Computing,” under VM Minimum Configuration, must be met.

A: The requirements are as stated in SOW Section 4.3.4, “Computing,” under VM Minimum Configuration.

A: There are no tiered storage requirements for the Remote Offices; tiered storage requirements only apply to the Domestic Data Centers. See SOW Section 4.2.3, “Storage.” The Offeror should propose the best solution to meet DOS requirements.

A: The Offerors should provide its best solution to meet the Department’s requirements.

A: The information provided in the VM Minimum Configuration Table in Section 4.3.4 is based on the current environment.