U.S. Navy (USN) Tactical Combat Training System Increment II (TCTS II) and United States Air Force (USAF) equivalent P6 Combat Training System (P6CTS)

Sources Sought - Procurement of required supplies and services to support the U.S. Navy (USN) Tactical Combat Training System Increment II (TCTS II) and United States Air Force (USAF) equivalent P6 Combat Training System (P6CTS) requirements. The TCTS II and USAF P6CTS are equivalent, and hereinafter also referred to as TCTS II. The Naval Air Warfare Center Training Systems Division (NAWCTSD), Orlando, Florida has a requirement to provide range-tethered and untethered air combat training with secure air-to-air and air-to-ground data link for the USN and USAF. TCTS II includes the Airborne Subsystem (AS), the Ground Subsystem (GS), the Remote Range Unit (RRU) Subsystem, and the Portable Support Equipment Subsystem (PSES). TCTS II provides encryption, an enhanced threat environment, and platform interfaces, with applications for several Type Model Series (T/M/S) aircraft. TCTS II operates on a fixed range with live monitoring and portable configurations and provides autonomous, rangeless tactical training and is interoperable with existing range infrastructure, TCTS I and TCTS II variants. Interoperability refers to the ability of different systems, applications, or devices to communicate and exchange data with each other seamlessly, efficiently, and effectively. It enables them to work together, share information, and coordinate their actions to achieve a common goal, even if they are from different manufacturers, use different technologies, or have different architectures. Use Government provided BMW waveform Compatible with End Cryptographic Units (ECU); (i.e. KOV-74A) Operable on current range infrastructure Connect to external range operating systems (E.g. Joint Debriefing Subsystem (JDS), Live Mission Operating Capability (LMOC), Battle Monitor etc.) via Test and Training Enabling Network Architecture (TENA) connection Mount using existing hanger band design on the following aircraft launchers: LAU-7, LAU-100/101 (F-5), and LAU-127 attached to the F/A-18E/F, to the 16S210, LAU-129 attached to an F-16, LAU-105 (B-52/A-10), and LAU-128 (F-15). Interoperable with the following aircraft via 1553 bus connection and AIM-9 umbilical connection: AH-1Z (AS Light or Heavy), B-52H (AS Light), EA-18G (ASHeavy), F-15E/EX (AS Light), F-16A/B/C/D (ASLight), F-5N/F (AS Heavy), F/A-18A/B/C/D/E/F (AS Heavy), P-8A (AS) The subject efforts include but are not limited to: supplies and services necessary for five (5) USN and USAF TCTS II ordering periods not to exceed twelve (12) months each. These procurements include system qualification and integration; test/production assets; engineering support; cybersecurity support to include Risk Management Framework (RMF); and COMSEC; spares/consumables; site surveys/installs; field engineering/training support; ancillary support equipment; integrated logistics support to include Interim Contract Support (ICS); data products such as the Technical Data Package (TDP), technical manuals and training curriculum; and Engineering Change Proposals (ECPs) for obsolescence and capability upgrades. Each procurement order may include current design solution or proven form-fit-function-interface technical equivalent AS, PSES, RRU, and/or GS. It is anticipated that this requirement will be solicited as a single-award contract with the associated PSC 6910 and NAICS 336413. The estimated USN and USAF efforts within TCTS II requirements will have five (5) ordering periods as tentatively outlined below: USAF FY26 FY27 FY28 FY29 FY30 Total PODs 201 201 201 201 201 1005 PSES 8 8 8 8 9 41 CGS 6 7 7 7 7 34 RRU 25 25 24 24 25 123 USN PODS 78 79 79 236 PSES 11 8 4 2 25 CGS 3 5 1 9 RRU 13 9 3 2 27 Estimates subject to budget constraints in a given year. To assist the Government in determining the current capacity of industry, all respondents are requested to provide responses to the following capabilities questions: 1. The Government's objective is for interoperability and backwards compatibility, including use of Blended Mesh Waveform (BMW), between the existing TCTS II subsystems and vendor proposed solution. Provide detailed approach for interoperability and backwards compatibility between the currently fielded TCTS II subsystems and vendor proposed solution. 2. Provide substantiation that your proposed TCTS II/P6CTS design solution has a trusted guard data filter capability and has the ability to encrypt the over the air data link up to TS with an approved NSA Type 1 encryption that is cryptographically interoperable with the KOV-74A. 3. Provide substantiation that your proposed TCTS II/P6CTS design solution has the ability to encrypt up to TS/SCI on the GS using an approved NSA Type 1 encryption that is cryptographically interoperable with the KOV-74A and certified Cross Domain Solution (CDS). 4. Provide substantiation that your proposed TCTS II/P6CTS design solution has the ability to appropriately filter data using a Multi-Level Security (MLS) or Multi-Independent Level Security (MILS) system. 5. Provide substantiation that your proposed CDS has a technical path to achieve RTB 4.2 compliance. What is your timeline to achieve RTB 4.2 certification? 6. Demonstrate your ability to manufacture and deliver the TCTS II at a full-rate production level (at least 279 AS delivered from start to finish within an eighteen (18) month period, no later than twenty-four (24) months after contract award). What are your known challenges and barriers to achieve this production capability? Please address technical barriers, manpower, facilities, etc. From contract award, what is your proposed timeline to produce a production representative article? If you are a small business interested in being the prime contractor for this effort, be advised that the FAR 52.219-14 Limitations on Subcontracting, Deviation 2021-O0008 rev 1 is now in effect which includes the definition of - Similarly Situated Entity and provides a methodology for the 50% calculation for compliance with the clause. Small business primes may count - first tier subcontracted work performed by similarly situated entities as if it were performed by the prime itself. Read the full text of the clause deviation (52.219-14 Class Deviation 2021-O0008 rev 1 dated 02/15/23 at https://www.acq.osd.mil/dpap/policy/policyvault/USA000277-23-DPC.pdf ).To assist in our market research and determination of any applicable small business set-aside for this effort, if you are a small business interested in priming this effort and plan to utilize - similarly situated entities to meet the Limitations on Subcontracting, identify the name & CAGE Code of the specific firm(s) you intend to partner/subcontract with to meet the requirements as well as their SB size status under the NAICS that you as the prime would assign for their workshare. Information regarding any planned similarly situated entity should be included in answering any questions outlined in the SSN in order to assist the Government's capability determination. THIS SOURCES SOUGHT IS NOT A REQUEST FOR PROPOSAL. It is a market research tool used to determine potential and eligible contractors prior to determining the method of acquisition and issuance of a Request for Proposal. Detailed capabilities must be submitted in an electronic format that is compatible with Word 2016, no later than 26 July 2024. All responses must include the following information: company name, CAGE code, company address and responses to capabilities questions 1-6. Additionally, Small Businesses must include the following additional information as appropriate: Identify your firm's CAGE code Identify if your firm is considered small under the size standard associated with the chosen NAICS code. Identify your firm's socio-economic status (indicate all that apply: WOSB, EDWOSB, SDVOSB, HUBZone, SDB, 8(a)). Address if your firm is interested in participating as a prime or subcontractor. If interested in the prime contractor role, identify anticipated teaming partners and their role in the overall acquisition (specific capabilities/solutions that partner brings to the acquisition, size and status of the partner, CAGE code, approx. workshare, etc). Successful awardees will be required to have a Government approved accounting system upon contract award. Responses are to be no more than TEN (10) pages in length using 12-point Times New Roman font. This Sources Sought is for informational purposes only. This is not a request for proposal. It does not constitute a solicitation and shall not be construed as a commitment by the Government. Responses in any form are not offers and the Government is under no obligation to award a contract as a result of this announcement. No funds are available to pay for preparation of responses to this announcement. Any information submitted by respondents to this technical description is strictly voluntary. Matters pertaining to this notification may be directed to Kurt Susnis at 407-380-4243 or via email at Kurt.A.Susnis.Civ@us.navy.mil, and Ms. Andrea Gordon-Eubanks at 407-380-4389 or via email at Andrea.L.GordonEubanks.Civ@us.navy.mil. The Government may provide some technical documents to assist Offerors with their capability statements. Some of the attachments and technical documents contain Controlled Unclassified Information (CUI). Distribution of CUI by an Offeror to that Offeror's team members, partners, subcontractors, suppliers and/or vendors shall be the responsibility of the Offeror and shall be limited to a - need to know basis. All guidance contained herein with regard to handling, distribution and destruction of CUI shall be flowed down to all team members, partners, subcontractors, suppliers and/or vendors. Those who access or take receipt of CUI shall comply with all laws, export controls and distribution statements associated with the document. Due to certain CUI being export-controlled, all requests for access to attachments and technical documents containing CUI must be in writing and able to be verified via the Defense Logistics Agency website https://www.dla.mil/Information-Operations/LogisticsInformationServices/. Upon completion of the request, each Offeror shall transmit via email its written request for access to solicitation attachments and technical documents containing CUI to Kurt Susnis at kurt.a.susnis.civ@us.navy.mil and Andrea Gordon-Eubanks at Andrea.L.GordonEubanks.Civ@us.navy.mil. The Government will verify the certification information via a Joint Certification Program (JCP) search on the Defense Logistics Agency (DLA) Logistics Information Service website. All CUI will be provided via DoD SAFE. Each potential Offeror shall certify that no dissemination of any export-controlled solicitation attachments and technical documents containing CUI subject to this requirement will occur in a manner that would violate applicable export control laws and regulations. Upon review of the Offeror's written request, verification of Offeror's status and acknowledgement of the Offeror's responsibility under the US Export laws and regulations, the Government will provide the Offeror access to the solicitation attachments and technical documents. Each Offeror who was granted access to the solicitation attachments and technical documents and later decides to - no bid shall provide certification of the destruction of the attachments and technical documents. Each Offeror shall provide the destruction certification on corporate letterhead within 10 business days of such a decision or by the proposal submittal deadline, whichever is earlier via email to the aforementioned contract specialists. All Offerors, other than the successful Offeror(s), shall destroy all solicitation attachments and technical documents obtained and provide proof of such destruction via signed letter on corporate letterhead transmitted via email the aforementioned contract specialists.