FTSS V Industry Day QA_82_01.20.21.docx

DOCX document 15 KB Posted

Attached to
Navy Fielded Training Systems Support (FTSS) Federal contract opportunity
Solicitation number
N6134021R0001
Issued by
Department of the Navy Naval Air Systems Command

About this file

This document contains a sources sought notice for the Navy Fielded Training Systems Support (FTSS) contract opportunity. The notice seeks information from potential offerors to provide FTSS services, including contractor operation and maintenance services and contractor instructional services for aircrew and maintenance simulators supporting Navy and Marine Corps customers. Key details include that responses are due by March 16, 2020, and the anticipated requirements include 19 known follow-on task orders valued at approximately $1 billion over eight years. Offerors should describe relevant experience in the last five years, capabilities for program management, logistics management, and meeting information security requirements. The document also lists expected recurring FTSS requirements categorized as suitable for large or small business and provides contact information for the contracting office.

View the file

Other files for this federal contract opportunity

Other files attached to Navy Fielded Training Systems Support (FTSS), newest first.
File Type Posted
DRAFT RFP N6134021R0001_Att L-10 FTSS V Solicitation_QA 10-11_8.3.21.xlsx XLSX spreadsheet
FTSS V Pre-Sol _REGISTRATION_ATTENDANCE_alpha by company 8.4.21.pdf PDF
FTSS V PreSol Conf Brief_8.2.21.pdf PDF
DRAFT RFP N6134021R0001_Att L-10 FTSS V Solicitation_QA 1-9_8.2.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att L-4 FTSS V Rep Hist Req PWS A COMS_7.20.21.docx DOCX document
DRAFT RFP N6134021R0001_Att BC-12 DD 254 PLAN N61340-21-R-0001-FTSS V MAC_7.20.21 RFP.pdf PDF
DRAFT RFP N6134021R0001_Att BC 7_TDV Authorization Form_7.20.21.doc DOC document
DRAFT RFP N6134021R0001_Att BC 6_CIS Add Instruction Request_7.20.21.doc DOC document
DRAFT RFP N6134021R0001_Att BC 4_ COMS Prem Time Request7.20.21.doc DOC document
DRAFT RFP N6134021R0001_Att BC 3_Premium Time Hours Log_7.20.21.xls XLS spreadsheet
DRAFT RFP N6134021R0001_Att L-5 FTSS V Rep Hist Req PWS B CIS_7.20.21.docx DOCX document
FTSS V Pre-Solicitation Conference Etiquette_7.20.21.docx DOCX document
DRAFT RFP N6134021R0001_Att L-8 FTSS V Notional Device Description (Lot2)_7.20.21.docx DOCX document
DRAFT RFP N6134021R0001_Att L-3b FTSS V Contract Data (Lot 2)_07.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att L-3a FTSS V Contract Data (Lot 1) _07.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att L-2 Vol 4 CPAQ_07.20.21.docx DOCX document
DRAFT RFP N6134021R0001_Att L-1 Vol 1 Relevant Contract Summary Tables_07.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att BC 10_On-Call_Maint Spt Log_7.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att BC 5_Addl Inst Hours Log_7.20.21.xls XLS spreadsheet
DRAFT RFP N6134021R0001_Att BC 1_FTSS V SCOPE_FINAL_7.20.21 .docx DOCX document
FTSS V Draft RFP N6134021R0001_7.20.21.docx DOCX document
Joining a WebEx Meeting.pptx PPTX presentation
DRAFT RFP N6134021R0001_Att BC 9_OAWR Form_7.20.21.doc DOC document
DRAFT RFP N6134021R0001_Att BC 2_Data Item Transmittal Form - 7.20.21.doc DOC document
DRAFT RFP N6134021R0001_Att L-10 FTSS V Solicitation_Question_Form_07.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att L-9 CPARS_Update_Questionnaire_07.20.21.docx DOCX document
DRAFT RFP N6134021R0001_Att L-7 FTSS V Military Aircraft Flight Training Devices (Lot2)_7.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att L-6 FTSS V Military Aircraft Flight Simulators (Lot 1)_7.20.21.xlsx XLSX spreadsheet
DRAFT RFP N6134021R0001_Att BC 13 PACT Users Guide_7.20.21.pdf PDF
DRAFT RFP N6134021R0001_Att BC 11_On-Call_Maint Spt Auth Compl Srvcs Form_7.20.21.docx DOCX document
DRAFT RFP N6134021R0001_Att BC 8_Excess Repair_Replacement Form_7.20.21.doc DOC document
Industry QA_85_6.24.21.docx DOCX document
FTSS V Industry QA_84_06.02.21.docx DOCX document
FTSS V Industry Day QA_83_01.20.21.docx DOCX document
FTSS V Industry Day QA_81_12.3.20.docx DOCX document
FTSS V Industry Day QA_77-80_8.4.20.xlsx XLSX spreadsheet
FTSS V Industry Day QA_1-76_8.3.20.xlsx XLSX spreadsheet
FTSS V INDUSTRY DAY_General Session_REGISTRATION_ATTENDANCE_5.5.20.docx DOCX document
27 April 2020_FTSS V Industry Day Slides 29 Apr 2020.pptx PPTX presentation
23 April 2020_FTSS V Industry Day Slides 29 Apr 2020.pptx PPTX presentation
FTSS V Industry Day Etiquette_4.24.20.docx DOCX document
Joining_a_WebEx_Meeting.pptx PPTX presentation
FTSS V Industry Day 1-on-1 Meeting Questions_4.3.20.docx DOCX document
09 April 2020_FTSS V Industry Day Slides 29 Apr 2020.pptx PPTX presentation
FTSS V Industry Day Agenda_4.3.20.docx DOCX document
FTSS V SSN Q&A_2.11.20.xlsx XLSX spreadsheet
Show all 46

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

Industry Question #82:

Following review of the recently posted Q&A #81 for FTSS V, a question has arisen regarding FCLs for Joint Ventures. In November, the SBA implemented new rules regarding Joint Ventures. One in particular, 13 CFR 121.103 (h) section 4 added FCL language to support unpopulated Joint Ventures. Contracts can be awarded to a joint venture even if the joint venture does not hold an FCL but the partners do. For your convenience I have added the wording below. Will NAWCTSD consider these new rules when awarding the FTSS V MAC and TOs? Thank you in advance for your review of this matter.

(4) Facility security clearances. A joint venture may be awarded a contract requiring a facility security clearance where either the joint venture itself or the individual partner(s) to the joint venture that will perform the necessary security work has (have) a facility security clearance.

(i) Where a facility security clearance is required to perform primary and vital requirements of a contract, the lead small business partner to the joint venture must possess the required facility security clearance.

(ii) Where the security portion of the contract requiring a facility security clearance is ancillary to the principal purpose of the procurement, the partner to the joint venture that will perform that work must possess the required facility security clearance

Government’s Response:

A follow-up question was posed regarding Facility Clearance Levels (FCL) for joint venture (JV) entities. The question seeks clarification re: whether or not the Government will consider the recent SBA regulation at 13 CFR 121.103(h) which allows a contract to be awarded to a JV even if the JV does not hold a FCL but the individuals partner(s) to the JV that will perform necessary security work hold a FCL. Specifically, 13 CFR 121.103(h) provides, “A joint venture may be awarded a contract requiring a facility security clearance where either the joint venture itself or the individual partner(s) to the joint venture that will perform the necessary security work has (have) a facility security clearance.” (emphasis added) The use of the word “may” is meaningful since it does not mandate contract award be made where the JV itself does not possess a FCL but the individual partner(s) to the JV that will perform the security works has a FCL.

In the Government’s response to question #81, it was identified that for a JV to receive a facility clearance, all member companies must have a FCL at the level of the contract. At the Industry Day in April 2020, the Government communicated that, “The current plan is that an offeror (per CAGE code proposing) must possess at least a Secret Facility Clearance (FCL) for FTSS V MAC award.” This continues to be the Government’s plan and position since it reflects the preponderance of the FTSS V MAC Lot 1 and Lot 2 task order requirements.

While our acquisition strategy is still being developed for the FTSS V MAC award, the Government continues to intend to require each Prime Offeror to meet the FTSS V MAC Secret FCL award prerequisite as follows:

The Prime Contractor shall provide, with their proposal, evidence that they currently hold a Secret, or higher, Facility Clearance. In the case of a Joint Venture, the Prime JV entity shall provide, with their proposal, evidence that they currently hold a Secret, or higher, Facility Clearance. The clearance must be in the name of legal entity identified in Block 15A of the Offeror’s SF33. This evidence shall be submitted with the proposal at the proposal submission date/time specified on Standard Form 33. The Secret, or higher, Facility Clearance shall be valid at time of proposal submittal. Any clearances that are pending or in process are not permissible.

While it is too soon to determine acquisition plans for the subsequent TO competitions, the Government anticipates they follow an approach similar to that of the MAC regarding FCLs.

As a courtesy, please find potential DRAFT language for the “FCL Prerequisite” which may be included in the Draft RFP Section L:

L.2.1.2 PREREQUISITE

1. Each Prime Offeror shall provide documentation to demonstrate that the Offeror meets the prerequisite listed below. The requirement will first be validated on a pass/fail assessment. Offerors who do not meet the prerequisite, will be deemed UNACCEPTABLE and will be eliminated from this competition. As such, their proposal will not be evaluated.

1. Secret Facility Clearance:

Lot I and Lot II: The Prime Contractor shall provide, with their proposal, evidence that they currently hold a Secret, or higher, Facility Clearance. In the case of a Joint Venture, the Prime JV entity shall provide, with their proposal, evidence that they currently hold a Secret, or higher, Facility Clearance. The clearance must be in the name of legal entity identified in Block 15A of the Offeror’s SF33. This evidence shall be submitted with the proposal at the proposal submission date/time specified on Standard Form 33. The Secret, or higher, Facility Clearance shall be valid at time of proposal submittal. Any clearances that are pending or in process are not permissible.

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