GAP_CIE_Draft_RFP_Question_ _Responses.docx

1: The SOW (1.1 Background) states: While GAP CIE was originally designed as a planning capability for United States Strategic Command (USSTRATCOM), the capability is now applicable to a broader range of organizations and missions due to its doctrinal (Joint Publication 3-0 / 5-0) foundation for JOP. The Joint Requirements Oversight Council (JROC) directed in JROC Memorandum (JROCM) 016-09 that GAP CIE become “the Department of Defense (DOD) Program of Record for joint Course of Action (COA) development at the CCDR/Strategic level.”

Question: Does this imply expansion of GAP-CIE beyond USSTRATCOM to all Combatant Commands, and if so, is that expansion included in Increment 2 or Increment 3?

1: Answer: The expansion for use by Combatant Commands is being executed during Increment 2 development. Increment 2 will reach FOC under the current contract before the new GAP CIE maintenance contract is awarded.

2. SOW describes Enhancements and Modifications. Demonstration Day Brief states that Increment 3 Development is not within scope.

Question: If new requirements arise from the users, how will the contracting officer determine if any new requirement is an Enhancement, Modification, or part of Increment 3 and therefore beyond /out of scope?

2. Answer: The PMO has an approved Capability Development Document (CDD) and Technical Requirements Document (TRD) for Increment 3. Increment 3 requirements will not be included in the requirements for specific delivery orders.

3. Question: Overall - Throughout the documents we notice the program and contract referenced as both GAP-CIE and GAP CIE. For consistency in a proposal response, which is correct?

3. Answer: Use GAP CIE in your proposal response.

4. Question: Model Contract Section B - Does the Government plan to include a CLIN for possible future Development task orders, similar to the model contract structure for MPACS, NIDS III, and GSPS?

4. Answer: No, the Government does not anticipate including a separate CLIN for future development task orders. Inc 3 development is not included within the scope of the contract. All sustainment and enhancement software deliveries occurring under the contract will be awarded via separate delivery orders under CLIN 0001.

5. Section M2.3.3.2 - What other positions, in addition to on-site support, does the government consider to be key to the success of the program? Will resumes be required for those key positions?

5. Answer: Offerors should include all staff required to satisfy the requirements of the SOW. Resumes are not required, but sufficient detail should be included to allow for an understanding of the Offeror’s staffs qualifications, certification, skills and experience.

6. SectionL6.3.1, L4.3.2, L4.3.2.2 - It is unclear what the offeror is to estimate and price for each year in CLIN X001.

Section L6.3.1 indicates that CLIN X001 is for “future software delivery efforts ” that “will not be estimated …during this source selection.” The DRs listed in Section L4.3.2 for Subfactor 2 request a “technical approach” but not pricing. Section L4.3.2.2 indicates that “offerors should have a staffing plan to accommodate the planned Government maintenance budgets” in the Planned Budget table yet the “budget numbers [in the table] do not correspond to the technical hours reflected in the GAP CIE cost/price model at Attachment 7.”

What should be priced for CLIN X001 and reflected in the cost/price model? Are there any special instructions for the pricing of the option years?

6. Answer: L6.3.1 – Specific Software Change Requests (SCRs) for work that will be accomplished after contract award cannot be identified during the source selection. Software deliveries occurring after contract award (ie “future”) will be issued under CLIN 0001.

L4.3.2 - The sample DRs are being used for the technical evaluation only. The DRs under Subfactor 2 will not be priced.

L4.3.2.2 – The budget is provided so that Offers will understand that although the IDIQ ceiling is $98M, the actual budget is only $26.8M. Offerors should plan to staff their team to meet the requirements of L4.3.3.2 with the budget, not the contract ceiling, in mind. Whereas the budget was included to give the Offeror an idea of the minimum staffing level required, the pre-loaded hours in the pricing model reflect the budget plus historical, additional funding received in a given year.

The cost/price for CLIN 0001 will be established by using the data included in the cost/price model, and will be for evaluation purposes only. CLIN 0001 will be priced as specified in L6.2. Basically, the Government will pre-load hours under each functional area in the “0001Skill Mix Hrs” tab (See line 10, 33, 56, 79, & 102 in the draft cost/price model). The pre-loaded government generated hours is based on the aggregation of multiple sustainment contracts within the ISPAN PMO. Offerors will provide a skill mix consisting of themselves and subcontractors with hours that equal the pre-loaded hours for a given functional area. The hours, in conjunction with the labor rates calculated under tabs “0001Prime” and “0001Sub”, will establish the Offerors proposed cost for CLIN 0001. Only the established labor rates will be included in the resultant contract.

7. Section L4.3.2.4 - Are the 6 sample DRs in the sample task representative of the full complement of future Delivery Order enhancements, modernizations, or defects? Can these sample DRs be used to derive the skillmix required to perform GAP CIE Operations and Sustainment?

7. Answer: The purpose of the sample DRs is to allow Offerors the opportunity to provide their understanding of the GAP CIE baseline as it relates to their technical solution for those specific DRs. The sample DRs do not represent a full complement of future DRs, nor can they be used to derive the full staff or skillmix required to perform GAP CIE Operations and Sustainment deliveries.

8. Section L2.0 - Section L2.0 provides the page limits for the 5 Subfactors in the Technical Volume. Section L4.2.1 provides the Technical Volume organization which reflects that same 5 Subfactors plus item (10) Technical Risk.

It is unclear if item (10) Technical Risk is another section in the Technical Volume like the Subfactors. It is unclear how the 80 page limit overall applies to item (10) Technical Risk. Please clarify.

8. Answer: Section L2.0 will be updated to include a three page limit for the Offeror to identify potential risks. The page limit for Volume II is increased from 80 to 83.

9. Incentive Fee Plan & SOW 2.10 - The Incentive Fee Plan and SOW appear to describe an unbounded requirement for GDT&E that also establishes an incentive fee criteria that is influenced by factors outside the technical requirements of each unique delivery order. Please clarify.

9. Answer: The Government has amended paragraph 2.10 of the SOW. See below... All DRs found by the Government during GDT&E will be classified using T.O. 00-35D-54, regardless if they occur as a result of the specific delivery or from a DR currently residing, but not previously identified, in the system. The rework percentage used to determine fee was normalized to account for those DRs “outside the technical requirements of each unique delivery order.” It is the Governments intent to minimize GDT&E by incentivizing the Contractor to deliver a higher quality product to GDT&E.

2.10. GDT&E Integration Support

Support to Government:

The contractor shall provide integration support to the Government during GDT&E. Support shall include technical consultation to resolve integration problems associated with the deployment of the software. This support shall include technical support during normal work hours. GDT&E support also includes DR workoff for DRs identified during GDT&E.

Schedule:

The length of GDT&E support will vary depending on the size and complexity of the delivery but will normally not exceed 90 days. The Government will specify the length of GDT&E in the RFP for the delivery. GDT&E will end when all CAT I DRs (as defined in T.O. 00-35D-54) found within the specified GDT&E period, regardless of when they were introduced into the system, have been closed. GDT&E may be condensed if/when the Government finds no CAT I DRs and/or the Contractor fixes all, and introduces no additional, CAT I DRs in subsequent patches. In the event the Government determines to field a delivery prior to all identified CAT I DRs being closed, the contractor shall still be responsible for resolving all CAT I DRs for that delivery.

As DRBs are held, the Government will identify a list of opened DRs to the contractor. The contractor shall minimize patches during baseline testing which disrupt the Government’s test schedule. Fixes to the Contractor’s baseline are expected during GDT&E, but the delivery of any patch to the Government’s GDT&E baseline shall be at Government PMO direction only, which should consider Contractor recommendations for patches that improve the testability of the system during GDT&E. The Government’s ideal test schedule consists of a single software delivery at GDT&E TRR and a final patch delivery to close out GDT&E.

10. Question: I would just like to confirm that the ceiling value presented at the New Horizons Conference as $100M is correct?

10. Answer: The IDIQ ceiling is $98M

11. Question: Is Internet Explorer the only browser that GAP CIE works in?

11. Answer: No, it is also designed to work in Firefox.

12. Question: For DR#3 (adding a training tab), is the any more information on what content should go under that tab?

12. Answer: No, the task is to only add an additional tab.