Q A_19_Aug_2013_(4).pdf

PDF 81 KB Posted

Attached to
Weapon System Support Contract
Solicitation number
FA3002-13-R-0005
Issued by

About this file

Q As

View the file

Other files

File Type Posted
Atch_2-j_Exhibit_J_ELINS_Amendment_0006.pdf PDF
FA3002-13-R-0005_Amendment_0006.pdf PDF
Amendment_0005.pdf PDF
Atch_2-d_Exhibit_D_ELINS_Amendment_0003.docx DOCX document
Attch_11_WSSC_Section_B_(Aug_13)_Amendment_0003.xlsx XLSX spreadsheet
FA3002-13-R-0005_Amendment_0003.pdf PDF
FA3002-13-R-0005_Amendment_0002.pdf PDF
Q A_19_Aug_2013_(3).pdf PDF
Questions_for_F-16_WSSC.pdf PDF
Questions_on_F-16_WSSC_RFP.pdf PDF
Q A_19_Aug_2013_(5).pdf PDF
Questions_2_on_F-16_WSSC_RFP.pdf PDF
Q A_19_Aug_2013_(3).pdf PDF
Inventory_All_2013.pdf PDF
FY14_PFT.pdf PDF
F-16_WSSC_PWS_08192013_Final.pdf PDF
Atch_2-c_Exhibit_C_ELINS_Amendment_0001.docx DOCX document
FA3002-13-R-0005_Amendment_0001.doc DOC document
Attachment_1-g_PWS_Appendix_7_corrected.pdf PDF
Attch_11_WSSC_Section_B_(Aug_13)_Amendment_0001.xlsx XLSX spreadsheet
Atch_2-d_Exhibit_D_ELINS_Amendment_0001.docx DOCX document
Atch_2-f_Exhibit_F_ELINS_Amendment_0001.docx DOCX document
Atch_2-g_Exhibit_G_ELINS_Amendment_0001.docx DOCX document
Atch_2-e_Exhibit_E_ELINS_Amendment_0001.docx DOCX document
Atch_2-a_Exhibit_A_ELINS_Amendment_0001.docx DOCX document
Atch_2-j_Exhibit_J_ELINS_Amendment_0001.docx DOCX document
Atch_2-k_Exhibit_K_ELINS_Amendment_0001.docx DOCX document
Atch_1_Performance_Work_Statement.pdf PDF
Atch_9_WSSC_Luke_AFB_CBA_2012-2015.pdf PDF
Atch_2-b_Exhibit_B_ELINS.pdf PDF
Atch_1-e_PWS_Appendix_5.pdf PDF
Atch_2-c_Exhibit_C_ELINS.pdf PDF
Atch_7_Past_Performance_Information_Sheet.docx DOCX document
Atch_1-d_PWS_Appendix_4.pdf PDF
Atch_2-m_Exhibit_M_ELINS.pdf PDF
Atch_1-g_PWS_Appendix_7.pdf PDF
Atch_6_Past_and_Present_Performance_Questionnaire.docx DOCX document
Atch_2-f_Exhibit_F_ELINS.pdf PDF
Atch_3_CDRLs.pdf PDF
Atch_4_WD_No._2005-2511_Rev_17_Holloman_AFB.pdf PDF
Atch_2-h_Exhibit_H_ELINS.pdf PDF
Atch_10_Contract_Security_Classification_Specification.pdf PDF
WSSC_RFP_FA3002-13-R-0005.pdf PDF
Atch_2-k_Exhibit_K_ELINS.pdf PDF
Atch_2-d_Exhibit_D_ELINS.pdf PDF
Atch_2-j_Exhibit_J_ELINS.pdf PDF
Atch_2-l_Exhibit_L_ELINS.pdf PDF
Attch_11_WSSC_Section_B_(Jul_13).xlsx XLSX spreadsheet
Atch_2-a_Exhibit_A_ELINS.pdf PDF
Atch_5__Past_Performance_Cover_Letter.doc DOC document
Show 40 more

50 files listed here. See the rest on GovTribe.

On GovTribe

Work with this file

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

Text version

FA3002-13-R-0005 WSSC Responses to Questions 19 Aug 13

Question # Document Reference Question/Issue Government Response

1 Exhibit D. With the programmed move of two squadrons from Luke to Holloman AFB, the number of GTIMS

Squadron Associate requirements stays constant at Luke AFB. Why are the GTIMS Squadron Associates kept at a constant number of four (4) at Luke AFB throughout all option years?

This Exhibit has been corrected and was posted with Amendment 0001 on FBO

2 Exhibit L.

With the programmed move of two squadrons from Luke to Holloman AFB, the number of GTIMS

Squadron Associate requirements stays constant at Holloman AFB. Why are the GTIMS Squadron

Associates kept at a constant number of three (3) at Holloman AFB throughout all option years?

Since the squadron begins its move on 1 Apr and the first class is programmed for 25 Apr the need to have a GTIMS assoc was identified and is a requirement beginning in the base year.

3 Exhibit C. With the programmed move of two squadrons from Luke to Holloman AFB, the number of Flying Squadron

Scheduling requirements stays constant at Luke AFB. Exhibit K shows an incremental growth of one Flying

Squadron Scheduling requirement in Option Year 1 to account for a second squadron arriving at Holloman.

Why are the Flying Squadron Scheduling requirements kept at a constant number of three (3) at Luke AFB throughout all option years?

This Exhibit has been corrected and was posted with Amendment 0001 on FBO

4 Exhibit E. Courseware development requires are shown as coming from CDRL A004 through A013 and Appendices 1, 6, and 6A. However, Appendix 6A refers to requirements for the Republic of Singapore Air Force (RSAF) courseware workload. Also, Appendix 6B shows additional courseware workload for the US Air Force students at Holloman. Shouldn’t the reference to Appendix 6A be changed to 6B?

No the expectations for WSSC CWD is that all will be developed at Luke and will include Holloman, Luke AF and RSAF.

5 Exhibit L. The number of months in the “QTY” (quantity) block of GTIMS Squadron Associates changes in the

Option Year 1 to show “12” in ELIN 1016AA but only “11” in ELINs 1016AB and 1016AC. Then in

Option Year 2, the QTY block shows “12” for ELINs 2016AA and 2016AB, but “11” for 2016AC. For

Option Years 3 and 4, all “QTY” entries are “12.”Shouldn’t all Option Year “QTY” blocks show “12”?

This Exhibit has been corrected and was posted with Amendment 0001 on FBO

6 Exhibit L. In Option Year 2, the “Unit Price” block has an entry of “0016AB.”Should this entry be deleted and show a blank?

This Exhibit has been corrected and was posted with Amendment 0001 on FBO

7 PWS Section 2.3.4, GFE

When does GFE move to Holloman? Will it be in place during the transition/mobilization period (1-31

March 2014) for the first squadron moving to Holloman?

Most of the GFE will be purchased and placed at Holloman ahead of contract award. An inventory will need to be conducted shortly after contract award for all GFE at HO.

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