View the file

Other files for this federal contract opportunity

Other files attached to Advisory & Assistance Services & Systems Engineering & Technical Assistance Services for Headquarters, Air Force Space Command, newest first.
File Type Posted
Amendment 8 CSMC RFP.doc DOC document
CSMC RFP Amendment 6.doc DOC document
Block 13 Continuation Sheet 2 Oct 09.docx DOCX document
Amendment 5 Attachment L-3 MWMD PWS FINAL 29 Sep 09.doc DOC document
SF30 Summary of Changes - Amendment 4.doc DOC document
CSMC RFP 23 Sep 09 Amendment 3.doc DOC document
Amendment 3 Attachment L-3 MWMD PWS FINAL 23 Sep 09.doc DOC document
Attachment 1 CSMC PWS FINAL 21 Sep 09.docx DOCX document
Attachment 5 Section L Attachments 21 Sep 09.doc DOC document
SF30 Summary of Changes - Amendment 2.doc DOC document
Q A 22 Sep 09.doc DOC document
MILSATCOM CDRLs 29 9 Sep 09.rtf RTF text file
CDRLS Master List ILSS 11.rtf RTF text file
MILSATCOM CDRLs 30 9 Sep 09.rtf RTF text file
CDRLS Master List SESS 35 36.rtf RTF text file
Attachment 3 CSMC 254 24 Aug 09.pdf PDF
CDRLS Master List MGMT 29.rtf RTF text file
Attachment 2 Acronyms 22 Jul 09.doc DOC document
MWMD CDRLs 29 9 Sep 09.rtf RTF text file
CDRLS Master List SESS 37.rtf RTF text file
Rerevised Contract Mgmt Section.docx DOCX document
One-On-One Session Directions.pptx PPTX presentation
MILSATCOM 2 4 31 May 09.pdf PDF
Section L Past Performance Questionnaire.doc DOC document
9003-0043.doc DOC document
9003-0036.doc DOC document
9003-0035.doc DOC document
Market Research Questions.doc DOC document
SSA.docx DOCX document
A6-0176 CSMC PWS.docx DOCX document
A4 PWS 4 Sep 08.doc DOC document
9003-0019.doc DOC document
9003-0029.doc DOC document
9002-0014.doc DOC document
9002-0017.DOC DOC document
9002-0006.doc DOC document
9002-0009.doc DOC document
9002-0004.doc DOC document
9001-0004.doc DOC document
9001-0028.doc DOC document
9000-0018.doc DOC document
9000-0015.doc DOC document
9000-0027.doc DOC document
9000-0002.doc DOC document
9003-0034.doc DOC document
9000-0030.doc DOC document
9002-0026.doc DOC document
9001-0038.doc DOC document
CAASETAIPrimeandSubcontractorList.doc DOC document
2_MarketResearchQuestions.doc DOC document
Show all 50

Advisory & Assistance Services & Systems Engineering & Technical Assistance Services for Headquarters, Air Force Space Command has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Q&A, 25 Sep 09

Questions & Answers

1. Question: Reference: Table L-3, Task Order Page Limits. The reference provides a page limit for writing to Subfactors 1 and 2 of Factor 1 (Mission Capability) of 30 pages. The technical foundation of the CSMC proposal with a $450M ceiling is combined in two task orders that also require an in-depth treatment of staffing issues and management of the task. The two task orders bundle the requirements of former CAASETA task orders with individual requirements areas that permitted 20 pages of response each. In the case of Subfactor 2, of Factor 1 (MW/MD), our analysis clearly shows a bundling of requirements for four of the eight from prior CAASETA task orders. There are an additional four requirements areas. The point is, had these requirements areas been bid as separate task orders the total page allocation would have exceeded 100 pages, and perhaps extended to 160 pages. Yet as a requirement on a 5-year award, the Government seeks a contractor to provide technical confidence to the Command in just 30 pages (60 pages in two task orders). Since the Draft RFP the page limitation has been increased from 25 to 30 pages. We think this in in recognition by the Government that the difficulty is understood. We seek further relief and recommend the page count be expanded on both task orders to 45 pages in order to adequately address the large number of requirements that have been bundled in these task orders. Will the Government relax page count on the technical portion of the Awardable Task Orders allowing 45 pages?

Answer: No.

2. Question: Reference: RFP Paragraph, L-6e. The reference states: Glossary. Each volume shall contain a glossary of any abbreviations and acronyms used with an explanation of each. Glossaries do not count against page limitations for respective volumes. A common Industry proposal custom is to spell out abbreviations and acronyms on first usage in every volume. We recognize there is no RFP requirement to do so. Over the past 3 years on CAASETA task orders, the Government has allowed a Glossary to serve in place of this practice. Given page count limitations on the technical aspects of the proposal in three of the six volumes, will the Government allow the existence of a Glossary to obviate the need to spell out acronyms on first usage?

Answer: As stated at Section L-2C.6.e., each volume shall contain a glossary of any abbreviations and acronyms used with an explanation of each. The Government does not require anything further; however, evaluators will then rely on your glossary for acronym definitions.

3. Question: Reference Volume IV Past Performance, Factor 2, Section L-8, B, Submission Requirements. Our assumption is that a single citation submitted for consideration on an IDIQ contract can include multiple task orders with relevancy write-ups for each task order in the single citation mapped to each of the appropriate relevancy criteria as long as the information required by Attachment L-6 for both the IDIQ contract and each individual task order is provided in the citation. Is this assumption correct?

Answer: No, this is incorrect. See response for Question 3 above.

4. Question: MW/MD PWS. Para 1.3.1 (pg 4-9). Does the scope of the OPIR Requirement include those efforts currently contracted outside of CAASETA in A5FS and A5FG in support of the OPIR and the SBIRS/MD programs? Response needed to accurately determine the scope of the PWS.

Answer: No, the scope of the OPIR Requirement does not include those efforts currently contracted outside of CAASETA in A5FS and A5FG in support of the OPIR and SBIRS/MD programs. The scope of the OPIR requirement only includes the efforts detailed in the PWS.

5. Question: MW/MD PWS, Paras 1.3.3.2.1, 1.3.1.10.2 (pgs 8 & 13). RFP states: Develop and operate a Technical Information Center (TIC) providing and maintaining databases with BMD program documentation material up to and including Secret information, and, Maintain current Technical Information Center and databases containing all current and historroical, classified and unclassified program documentation material. Please clarify if the TIC is to be maintained at a contractor facility. If yes, please provide information on the GFE (computers/safes/file cabinets), file space requirements, safe requirements, and floor space requirements of the TIC. Information is needed to ensure proper facilities are made available and are costed.

Answer: The TIC is to be maintained at the contractor’s facility; it is approximately the size of 1.5 four-drawer safes of historical BMD data to be maintained at up to the SECRET level.

6. Question: MW/MD PWS, Para 1.3.1.10.1. (pg 8). RFP states: “Transition and maintain the OPIR documentation library.” Please clarify if this library is to be maintained at a contractor facility. If yes, please provide information on the GFE (computers/safes/file cabinets), file space requirements, and floor space requirements, and highest classification level of the TIC. Information is needed to ensure proper facilities are made available and costed.

Answer: The OPIR documentation library is to be maintained at the contractor’s facility; it is approximately the size of two four-drawer safes of historical OPIR data to be maintained at up to the SECRET level.

7. Question: Throughout the MW/MD PWS, CONOPS, Concepts, ICDs, CDDs, CPDs, etc. are referenced. Is there an expected number of each per year or contract period?

Answer: There is no “expected” number of these per year, but for each program, there should be no more than one ICD, CDD, or CPD being worked at any one time (some requirements have several programs listed under them). In the same manner, for each program, there should not be more than one CONOPS or Concept being worked at one time. The number could also be zero for a particular program at a certain time as they are all at different stages.

8. Question: Page 16, Section H-9 - "the contractor shall submit the registration or evidence that an application is pending with the State Department with task order proposals." Is a copy of the actual registration form/letter to be submitted with the task order proposals or will the registration number and expiration date for each ITAR registration suffice? Please clarify what "evidence" is required for applications that are pending with the State Department?

Answer: Provide a copy of the ancknowledgement of submission from the State Department.

9. Question: Reference Volume IV Past Performance, Factor 2. Consider the following teaming arrangement. A contractor proposing support to a small business prime CSMC contractor is the prime contractor (Company A) with several subcontractors performing services in an integrated team environment where personnel from other companies/teammates (Teammate B and C) are matrixed to support common requirements. Our assumption is that if Company A provides a detailed Past Performance Citation defining the overall contract details, Teammates B and C may either provide “abbreviated citations” reflecting each subcontractor specifics (e.g. name, address, CCR number, DUNS No., contract/Task Order numbers, contract values) with a reference back to the prime contactor’s citation and an explanation on the teaming arrangements. Is this assumption correct?

Answer: Offerors should comprehensively address why each citation provided is relevant. If a contractor was a subcontractor under a citation and the proposal references the prime’s citation and relevancy, the PCAG would not be able to determine exactly how much of the prime’s work was also done by the subcontractor. Each citation should address relevancy for that contractor.

Note: Please refer to Section L-4D of the RFP: Offerors shall give written notice to the CO of ambiguities in the solicitation, including attachments and the PWS, not later than seven days after RFP release.

File details come from the government source that posted it. Updated .