The file's text, extracted by GovTribe without its formatting.
AMENDMENT 0002 - Questions and Answers for 006 through 025 for RFP HC1028-11-R-0104
| DOCUMENT |
| J-1 SOO, revised 11 May 11 |
| SECTION NAME |
| Technology Refresh Program |
| SECTION TEXT |
| “The Government can decide to refresh hardware based on functions and technology updates, at any point in time during the first five years.” |
| QUESTION |
| If the Government is not buying hardware, but rather capacity services or “processor infrastructure services” as stated in the Scope in Section 2, how does the Government intend to “refresh hardware?” |
| ANSWER |
| When the Government decides to tech refresh capacity, a new call order will be issued. The Government will migrate to the new capacity and cancel the original call order. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NAME |
| Maintenance Response and Repair Time |
| SECTION TEXT |
| “The offeror will provide a multi-level solution for response after being notified by the Government,…. Each orderable system will be identified to a level of response based on Government need.” |
| QUESTION |
| The CLIN list only identifies hardware tiers, and not an option for a response level that the government will stipulate. How would Offerors accommodate the varying government needs in a constant price structure? |
| ANSWER |
| The Offeror’s multi-level solution must meet the availability requirement (99.95%) in a constant price structure. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NAME |
| Asset Management |
| SECTION TEXT |
| “An established process for handling asset recovery and redeployment shall be developed by the offeror.” |
| QUESTION |
| Since the Government can cancel and place Call Orders at any time, what is the need for this process? |
| ANSWER |
| It is the offeror’s responsibility to reclaim/recover the physical assets from a canceled call order. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION TEXT |
| “Provide provisioning servers to support the infrastructure . “ |
| QUESTION |
| 1. Will the Government order the provisioning servers or is it expected they be included in the overall Capacity rate? |
2. Are the provisioning server(s) required for the Z Chipset?
3. If so, will the Government order the provisioning servers for the Z Chipset or is it expected they be included in the overall Capacity rate?
| ANSWER |
| 1. Provisioning servers should be included in the overall Capacity rate. |
2. Provisioning servers are not required for the Z Chipset.
3. Provisioning servers are not required for the Z Chipset.
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION TEXT |
| “Provide IBM Mainframe Capacity Backup (CBU) feature for the temporary activation of Central Processors for Disaster Recovery. Annually, DISA routinely conducts 50-70 days of testing for each of the two sites. Testing days will be included in the processor utility service. Invocation fees will be identified and priced separately.” |
| QUESTION |
| 1. Are these two sites Mechanicsburg and Ogden? |
2. Are these to be separate machines from production machines?
| ANSWER |
| 1. Disaster recovery site locations and number of sites will not be identified. J2, Requirements Document, para 3.3 and J-5, PWS para 6.3.4 is revised. |
2. Yes, the machines for disaster recovery must be separate from production machines.
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NO. |
| 5.0, 5.1, 5.2 |
| SECTION NAME |
| Release Management |
SECTION TEXT
| QUESTION |
| 1. Do these subsections include all mainframes OS’s? |
2. Would the Government specifically state what is required by the offeror as it pertains to Mainframe OS (z/OS, z/VM, Red Hat and SuSE on Linux on System z) for Sections 5.0, 5.1, and 5.2?
| ANSWER |
| 1. Section 5.1 and 5.2 does not apply to mainframe OS. Section 5.3 does apply to mainframe OS. J-2, Requirements Document, para 5.3 has been added. J-5, Requirements Document, para 6.5.2 has been revised slightly. |
2. Section 5.1 and 5.2 does not apply to mainframe OS. Section 5.3 does apply to mainframe OS. J-2, Requirements Document, para 5.3 has been added. J-5, Requirements Document, para 6.5.2 has been revised slightly.
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION TEXT |
| “Equipment will be connected to BAS system for control and monitoring” |
| QUESTION |
| What is the BAS system? |
| ANSWER |
| BAS is BioAnalytical System. J-2, Requirements Document, para 6.3 and J-5, PWS, para 6.8.2.3 have been revised. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NAME |
| Call Order Management System |
| SECTION TEXT |
| “This system will be utilized to create and place call orders” |
| QUESTION |
| Will this system be used by the Offeror after receipt of a “Call Order” from DISA or will DISA have direct access to the Call Order management System? |
| ANSWER |
| DISA will have direct access to the Call Order Management System. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NAME |
| Call Order Management |
| SECTION TEXT |
| “The offeror call order management system will manage excess hardware, and software licenses. Excess hardware and software will be defined as any hardware and/or software that has received a 'cancelation' request via the call order process. This equipment will be marked in the call order management system appropriately to include cancelation date and date removed from DISA location.” |
| QUESTION |
| What is the purpose of this subsection? |
“Excess hardware and software licenses” will not be owned by the Government, so what is the necessity of tracking them?
| ANSWER |
| In order for the Government to verify the vendor billing against call order cancellation dates, the Offeror must maintain the configuration management files for what has been deployed. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NAME |
| Call Order Management System |
| SECTION TEXT |
| “After contract award, contractor will collaborate with DISA to finalize format and information required.” |
| QUESTION |
| Does the Call Order Management System need to be fully operational at the Proof of Concept? |
| ANSWER |
| Offerors must be able to demonstrate the Call Order Management System at the Proof of Concept. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION NO. |
| 16.4 and 16.5 |
| SECTION TEXT |
| 16.4: “…the media will be retained by the government.” and 16.5: “…the media may or may not be returned to the Contractor in an unusable state.” |
| QUESTION |
| Will the media be retained by the government or not and under what circumstances? |
| ANSWER |
| When hardware is no longer required, the Government will ensure the media (tapes, hard drives, mass storage devices, etc.) is sanitized or destroyed in accordance with appropriate regulations. If the media cannot be sanitized and rendered to the unclassified level, the media may or may not be returned to the Contractor in an unusable state. This process is to ensure the protection of controlled both sensitive but unclassified and classified information. J-2 – Processor Requirements Document, para 16.4 is revised accordingly. J-5 PWS, para 13.3 is revised accordingly. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION TEXT |
| “IAW DoD Cybercom USB Flash Media Communication Tasking Order (CTO) 10-084, USB Flash Media/Thumb drive devices are prohibited in DoD” |
| QUESTION |
| Please provide a hyperlink or reference to where the CTO can be found. |
| ANSWER |
| Requires additional information that the govt will publish as soon as it is resolved. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 |
| SECTION TEXT |
| “Security Managers will submit requests for investigative service to DISA Security (MPS6) utilizing the attached format” |
| QUESTION |
| Where is the attached format? |
| ANSWER |
| The format will be provided at contract award. J-2, Requirements Document, para 16.8.2 is revised accordingly. J-5, PWS, para 13.7.2 is revised accordingly. |
| DOCUMENT |
| J-2 Requirements Document, revised 11 May 11 and J-6 IBM System z Chipset Pricing Model |
| SECTION NO. |
| J-2 Attachment 2 and J-6 All Scenario Tabs |
| SECTION NAME |
| System Z Tier Definitions |
| SECTION TEXT |
| The J2 Attachment 2 specifies Tier 4 as having >2,500 MIPS. |
| QUESTION |
| The Evaluation scenario tabs of the J6 show a quantity of 200 MIPS in Tier 4 in several months. |
Please explain how this could be if Tier 4 by definition has a minimum of 2,500 MIPS?
| ANSWER |
| J-6 All scenario tabs are revised for Tier Zero and Tier 4. |
| DOCUMENT |
| J-5 Processor PWS Template revised 10 May 11.docx |
| SECTION NO. |
| Section 6.2.2.5.1 and Section 6.2.4 |
| SECTION NAME |
| Template Submitted as a Draft for Offeror to Work From |
SECTION TEXT
| QUESTION |
| Document goes from 6.2.2.5.1 to 6.2.4. There is no 6.2.3. Is something missing? |
| ANSWER |
| Para 6.2.3 was inadvertently left out. J-5 PWS is revised accordingly. |
| DOCUMENT |
| J-6 IBM Chipset Pricing Model 2 Jun 2011 |
| PAGE |
| Tab “Evaluation Price – All Scenarios” |
SECTION NO.
SECTION NAME
| SECTION TEXT |
| CLINS 1001AA through AE, 1002AA through AP, and 1005AA through AC |
| QUESTION |
| The formula for all months in CLINs 1001AA-AE, 1002AA-AP, and 1005AA-AC seem to contain an error. Please review the formulas as they pertain to Scenario 3. As an example, the formula in cell E4 contains a reference to cell EVALUATION PURPOSES - Scenario3'!AL4 that should reference cell EVALUATION PURPOSES - Scenario3'!E4. Similar errors seem to occur for all months and all CLINs in the referenced set. |
| ANSWER |
| J-6 IBM Chipset Pricing Model has been revised to correct the error. |
| DOCUMENT |
| HC1028-11-R-0104 |
| PAGE |
| 23 and SLINs 1001 AA – 1001 AE |
| SECTION NO. |
| Section J-2 and Section J-6 |
| SECTION NAME |
| Requirements Document – Processor Environment |
| SECTION TEXT |
| Characteristic – Tiers 1-4 |
| QUESTION |
| Section J-2 page 23 describes the characteristics of the System z Tier Definitions as having four tiers. The CLIN/SLIN structure for System z in Section J-6 has five tiers (1001 AA – 1001 AE). Which is correct? |
| ANSWER |
| J-6 IBM Chipset Pricing Model has been revised to correct the error. |
| DOCUMENT |
| HC1028-11-R-0104 |
| SECTION NO. |
| Section L.7.1.3 |
| SECTION TEXT |
| “Proposed Delivery Schedule. If Offerors propose an alternative schedule, the government may not accept or evaluate this alternative, unless it is in the best interest of the government. The Offeror must propose their alternative delivery schedule by completing the blanks in Section F of the solicitation.” |
| QUESTION |
| How can offerors propose an alternate schedule of Section F if the RFP says N/A for the delivery schedule? |
| ANSWER |
| The “Proposed Delivery Schedule” in Section F is automatically generated by our system and is based on the CLINs/SLINs. At contract award, Section F will reflect the effective dates for the base period and |
option years for the CLINs/SLINs.
Para L.7.1.3 incorrectly references Section F. Per J-2, Requirements Document, para 10.2 and J-5, PWS, para 6.2.4.2 the Government requires 30 day delivery of capacity by issuance of a Call Order. Offerors will be evaluated for their ability to deliver capacity within 30 days, per Section M002, "Evaluation of Offers", Paragraph B, Subfactor 2, subparagraph 2.3. If offerors propose an alternate schedule, they need to include that in their PWS response.
Para L.7.1.3 has been reserved.
| DOCUMENT |
| HC1028-11-R-0104 |
| SECTION NO. |
| Section M Subfactor 4 |
| SECTION NAME |
| Release Management |
SECTION TEXT
| QUESTION |
| All other subfactors say “specifically, the evaluators will consider…” but this subfactor does not. Was this an oversight? |
PAGE
| SECTION NO. |
| 1.3.2.1, 1.3.2.2, and 1.3.2 |
SECTION NAME
SECTION TEXT
| QUESTION |
| The first and third paragraphs make reference to paragraph 3.2.1, 3.2.3, and 2.2.2; however, there is no section with that number in the document. |
| ANSWER |
| J-2, Requirements Document, paras 1.3.2.1, 1.3.2.2, and 1.3.2.3 are revised accordingly. J-5, PWS, 6.2.2.1, 6.2.2.2.1, 6.2.2.3, and 6.2.2.4.2 are revised accordingly. |
Defense Information Systems Agency