FRFP RELEASE NO 2 - QA 44-62.pdf

HC1028-10-R-2001

RELEASE NO. 2

QUESTIONS/ANSWERS 44-62

QUESTION #

ANSWER #

POSTED

DATE/

Amend # FRFP 44. Reference: GSM-O RFP Amendment 1, Questions and Answers, FRFP 29.

Question/Comment: The referenced question and answer (i.e., FRFP 29) indicates that "TO-3 Appendix B has been revised to add Warner Robins AFB."

However the TO-3 document released with Amendment 1 does not show

Warner Robins AFB as a location. Please clarify.

FRFP 44. This was an oversight and Warner

Robbins is considered in scope for Task Order

0003 (Appendix B). Revised HC1028-10-R-2000, Section J, Attachment 08 is included with

Amendment 0002.

Amend 0002

FRFP 45. Reference: Amendment 1, Task Order-1, Appendix E, paragraph

6.4(c), items 8, 9, 10, and 11

Question/Comment: The items identified in referenced section includes COOP requirements for CND activities. However, CND activities are not part of Task

Order 1. Request that the Government remove items 8, 9, 10, and 11 from TO-1.

It is noted that these requirements may be appropriate for TO-3.

FRFP 45. CND activities called out in items 8-11 are not within the scope of Task Order 1. Revised

HC1028-10-R-2000, Section J, Attachment 06 is included with Amendment 0002.

Amend 0002

FRFP 46. Section L. Right now Section L.7.1 and L.8.2.4.4 conflict with each other and we’re trying to get some crisp direction on how to proceed.

Paragraph L.7 states for Volume II the offeror’s company name/information shall be reflected only on the title page. However, L8.2.4.4 is requesting the org structure, copies of Teaming Agmts, staffing plans, etc. which will identify company names. Can you please provide further guidance.

FRFP 46. As stated in HC1028-10-R-2000, Amendment 01, Section L, Paragraph L.7: “The offeror’s company name/information shall be reflected only on the title page of the Volumes II and IV. It is necessary that offerors devise a method to comply with the requirements of

Section L. This may include referring to self as the prime and subcontractors as subcontractor 1, subcontractor 2, etc. It is also possible that prospective offerors will need to mark through company identifiers, as necessary. This requirement is necessary to ensure evaluation is unbiased.

FRFP 47. We request a two week extension to the Final RFP Submission Date of March 14th, 2011.

FRFP 47. Proposal due date has been extended to

10:00 AM, CST, Monday, 28 Mar 11

Amend 0002

FRFP 48. Would the Government please provide a copy of “Atch_12_-_GSM-

O_PP_Questionnaire_-_Amend_0001” in Word format?

FRFP 48. HC1028-10-R-2000, Section J, Attachment 12 – Past Performance Questionnaire has been revised and is provided in “Word” version as part of Amendment 0002.

Amend 0002

FRFP 49. We request a two week extension to the Final RFP Submission Date of March 14th, 2011 due to the following reasons:

1. The Final RFP does not contain the CNDSP data and architecture that was referenced in Q&A #419. This information is required to enable industry to develop an appropriate response that will meet Government's needs

2. A significant volume of other data was released in Attachment 14 (CD ROM) of the Final RFP. The CD contains thousands of new artifacts on the Classified

CD that require extensive analysis in order to develop a complete solution and compliant response

3. The Final RFP contained significant changes to Section L and M relative to the updates indicated by the Govt Q&A in September 2010

4. Page count increase (tech volume from 100 to 250 pages, management from

50 to 65 pages, exec summary from 5 to 10 pages)

FRFP 49. See Question/Answer #47, above. Amend 0002

FRFP 50. In Q&A #387, the Government indicated that the GSM-O workscope referenced in Q&A #315 includes CNDSP (PWS 7.1-7.4). The FRFP

Attachment 13 contains the current DGS task orders, however only Task Order

64 references CNDSP tasks, and that is of limited scope relative to the GSM-O

PWS. We request that the government provide the current task orders/contracts

(DGS or otherwise) for the CNDSP scope in GSM-O.

FRFP 50. An additional FOUO-level data file that should assist the vendor in the preparation of a response to task order 3 will be provided via CD-

ROM and available in accordance with Section L

Paragraphs L3 and L4 on Tuesday 23 Feb after

1200 EST. The CD will also contain three updated reference documents that are applicable across the task orders. (This third CD-ROM is considered supplemental information and will be reflected in

RFP as HC1028-10-R-2000 Section J, Attachment

15.)

Amend 0002

FRFP 51. Reference Section H, Paragraph H.37. Amendment 0001 incorporated a significant change to the H.37 Incentive Fee Plan, replicating a third of the ALPs (1-6, 16, 17, 21, 22, 24, 25) across multiple task orders. As a result of this change, if the Contractor receives a Red rating against any of those replicated ALPs, it must now pay the penalty multiple times even if the problem was associated with the work scope of a single task order. Using ALP 1 as an example, if two security spillage incidents occur during a Task Order 2 activity, the Contractor would receive a Red rating and have to pay the Admin/Security penalty associated with each of the GSM-O task orders since ALP 1 is included in each.

Remedy: We recommend that each of the 35 ALPs be allocated to the single task order with which it is most closely associated (as existed prior to

Amendment 0001), removing any duplication across task orders. Since Task

Order 1 provides the overall GSM-O “foundation”, most of the ALPs would be associated with that Task Order. Task Orders 2-5 would include those ALPs that are somewhat unique to those Task Order activities. ALP 5 (Transition

Activities) could remain in each of Task Orders 1-3 since those activities are unique to each.

FRFP 51. PWS paragraph 3.5 will be revised to add the following: "If a given ALP is used to assess performance in more than one task order, as documented in the QASP for each task order, the

ALP shall be used in each such task order to assess the performance of that task order separately, without regard of or effect on the performance and assessment of any other task order. For example, a performance level of Red for ALP #1 in TO-1 does not affect or carry over to the use of that same ALP in TO-2. This requires that both positive and negative outcomes and assessments be focused on and attributed to the performance of the TO being controlled, independent of the application of that same ALP in another TO."

FRFP 52. Reference Section I. FAR 52.204-10 Reporting Executive

Compensation and First-Tier Subcontract Awards - Since the GSM-O solicitation is "classified" as defined in FAR Part 2; this clause is not applicable and therefore should be deleted.

FRFP 52. The GSM-O Solicitation (and resultant contract) is not considered a “classified” action.

Some information when placed together is considered to be and shall be treated as “sensitive” information. FAR 52.204-10 will not be deleted.

FRFP 53. Section I. 952.236-0001 Electrical and Structural Building Standards for Construction Projects -- Per Joint Contracting Command Acquisition

Instructions, this clause should be included in Construction Contracts; this clause is not applicable to GSM-O and therefore should be deleted.

FRFP 53. Section I – 952.236-0001 will be deleted.

Amend 0002

FRFP 54. Reference Section L, Paragraph L8.4.3.2.2.2. Given the small business subcontracting goals of the RFP, there will be a need to provide subcontractor cost detail directly to the Contracting Officer. If the prime and subcontractors cannot be identified in Volume IV, the cost detail will be difficult

FRFP 54. See Question/Answer #46, above.

Subcontractor cost detail is required.

to correlate with Volume IV. In that the award of the contract is expected to be based on adequate price competition, and the initial task orders will be FFP, request that the requirement to submit subcontractor cost detail be removed from the RFP.

FRFP 55. Reference Section L, Paragraph L7.11. For DITCO Web Site Up-load - is it possible to have more than one person simultaneously upload proposal documents.

FRFP 55. Prospective offerors may register more than one person to upload proposal documents.

However, keep in mind that prospective offerors must ensure all documents are uploaded appropriately.

FRFP 56. Reference Section I. FAR 52-245-1 Alt 1 - Government Property -

Since the contractor has a Government approved Property System that will maintain and monitor a master, effective and efficient system that provides coordinated and uniform controls for the management of property in accordance with laws, regulations, policies and prcoedures, consistent with FAR Part 1

(52.245-1), we recommend that the Government delete "Alt 1" and use FAR

52.245-1.

FRFP 56. FAR 52.245-1; Alternate I will not be deleted.

FRFP 57. Reference Section H. H.10 - Government Property - Since the contractor has a Government approved Property System that will maintain and monitor a master, effective and efficient system that provides coordinated and uniform controls for the management of property in accordance with laws, regulations, policies and prcoedures, consistent with FAR Part 1 (52.245-1), we recommend that the Government delete "Alt 1" and use FAR 52.245-1.

FRFP 57. See Question/Answer #56, above.

FRFP 58. Reference Amendment 0001; a)3)a). Under the noted paragraph of

Amendment 01 it states that "Section A - Section A - Standard Form 30 is in

Final Format; not Draft as reflected on initial release of Final RFP HC1028-10-

R-2000." Should this be Standard Form 33 instead? If so, could a final format of

Standard Form 33 be provided.

FRFP 58. Reference should have been made to the Standard Form 33 (not Standard Form 30).

The “Final” Standard Form 33 is included with

Amendment 0002.

Amend 0002

FRFP 59. Reference Section H, Paragraph H.9 .b., Nondisclosure of Sensitive and/or Proprietary Data, states that “Nondisclosure Agreement for Contractor

Employees at Section J, Attachment 2 shall be signed by all indoctrinated personnel and forwarded to the Contracting Officer and Task Monitor (TM) for retention, prior to commencement of work.”

FRFP 59. Section H, Paragraph H9.b has been changed to delete the reference to Section J

Attachment.

Please provide the Nondisclosure Agreement for Contractor Employees, as

Section J, Attachment 2 specifies the Department of Defense Security

Classification Specification – DD Form 254

FRFP 60. Reference Section L, Paragraph L8.2.4.4. In order to comply with

Amendment 0001 L8.2.4.4 Part D – Subfactor 3 where it requests that the offeror include Organizational Structure (including teaming agreements, subcontractor management, staffing plan and key personnel), we request that the

Government allow bidders to include names of subcontractors within Volume II

(reference L7.1).

FRFP 60. See Question/Answer #46, above.

FRFP 61. Reference Section H. Section H.31 states that "The initial start-up period is established as sixty (60) days after contract award and shall be completed six months after award". Request that the Government remove the six month timeframe in accordance with Q&A #309 which removes the transition timeline criteria.

FRFP 61. RFP Section H.31 will be revised to state, "The initial start-up period for each year 1 task order shall be completed nine months after award".

FRFP 62. Reference Section I. Since the GSM-O program will not be a

“system of records” we recommend that FAR 52.224-1 “Privacy Act

Notification” and FAR 52.224-2”Privacy Act” be deleted due to non-applicability

FRFP 62 FAR 52.224-2 Privacy Act is deleted. Amend 0002