SOURCES SOUGHT
58 -- TACP C2 Weapon System
- Notice Date
- 2/24/2022 12:15:34 PM
- Notice Type
- Sources Sought
- NAICS
- 334220
— Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
- Contracting Office
- FA8730 DIGITAL DIRECTORATE AFLCMC H HANSCOM AFB MA 01731-2100 USA
- ZIP Code
- 01731-2100
- Solicitation Number
- TACP_C2_1
- Response Due
- 3/14/2022 12:00:00 PM
- Point of Contact
- Michael Monte
- E-Mail Address
-
michael.monte.4@us.af.mil
(michael.monte.4@us.af.mil)
- Description
- 1. Introduction This RFI is for the Tactical Air Control Party (TACP) Modernization office. The TACP-M office is currently interested in hardware and software to modernize the Air Support Operations Center (ASOC). ASOC TACPs are aligned with a conventional Army forces to provide precision terminal attack guidance of U.S. and coalition CAS aircraft, artillery, and naval gun fire; establish and maintain C2 communications; and advise ground commanders on the best use of air power.�� THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes � it does not constitute a Request for Quote (RFQ) or a promise to issue an RFQ in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Air Force is not seeking proposals and will not accept unsolicited proposals at this time. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party�s expense. Not responding to this RFI does not preclude participation in any future RFQ, if any is issued. 2. Requirements The TACP C2 Weapon System (TCWS) is the next evolution of ASOC technologies and systems. TCWS architecture is broken into 5 subsystems as referred to in the attached Requirements, Context, and Use Case diagrams. The ID number next to each subsystem below correlates to the system ID number in the requirements diagram: Maneuver Gateway (ID 2): Fail-forward node for Link-16 communications in case the ASOC is unavailable. Provides Link-16, JREAP-C, and SADL capabilities in a modular, small form-factor kit. BLOS Baseband Backhaul (ID 3): Organic high capacity Beyond Line of Sight Internet, IP to IP for real time information sharing, friendly force tracking, battlefield SA, and the ability to connect to AOC, HHQ, and Government Cloud. DCP Refresh (ID 4): HF, VHF, UHF, and SATCOM voice and data communications. TAK Server (ID 4.3.1): Process, host, and transfer metadata, .kml files, .kmz files, etc. on a TAK-based server. C2 Core Computer (ID 5): Ruggedized computer for TACPs to interface and control any TACP C2 Weapon System. Please refer to the system Requirements, Context, and Use Case diagrams in attachments 1-3 for information regarding the subsystems. The program office is seeking information on industry solutions both for the entire TCWS, or for a specific subsystem/component of the TCWS. To be clear, we will accept solutions even if they are only for specific components. If you question whether your solution is acceptabe, please contact us and we will work to provide you an answer. All proposed inputs/guidance must currently meet or have a notional plan to meet existing and applicable National Security Agency (NSA), Air Force, and Department of Defense (DoD) mandates for security. These include, but are not limited to, cyber security, cryptographic, physical, and procedural mandates. 3. Requested Information The TACP Program Office is requesting industry input/guidance on the TACP C2 Weapon System. These inputs may include products that are production ready or in development, but they must have the potential to improve the efficiency of TACP. The TACP Program Office is requesting feedback, questions, and any other support information to meet the end objectives of the TACP user community. Please be prepared to explain how supplemental information relates to the concept of a modernized TACP. 4. Responses Interested parties are requested to respond to this RFI with a white paper of their own format. Given the MBSE nature of this RFI, the PMO is requesting MBSE diagrams be part of each response. Diagrams are not required but are preferred. If responding to a specific subsystem, please reference the component�s block ID number as shown in the Requirements diagram (i.e. Maneuver Gateway requirements are ID 2). White papers in Microsoft Word compatible format are due no later than 28 Feb 2022, 3:00pm EDT. Responses will be limited to 10 pages and will be submitted via e-mail only to Mr. Christopher McCabe, Buyer, at christopher.mccabe.5@us.af.mil and to Captain Michael Monte, Contracting Officer, at michael.monte.4@us.af.mil. Each email transmittal cannot exceed 10MB. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. All Government support contractors have signed a Non-Disclosure Agreement (NDA), which are on file with the cognizant Government contracting office. Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum: Company name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and name, e-mail, and phone of designated point of contact. The facility security clearance of the offeror. 5. Industry Discussions TACP Program Office representatives may or may not choose to meet with potential offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks. 6. Questions Questions regarding this announcement shall be submitted in writing by e-mail to Mr. Christopher McCabe, Buyer, at christopher.mccabe.5@us.af.mil and to Captain Michael Monte, Contracting Officer, at michael.monte.4@us.af.mil. Verbal questions will NOT be accepted. Accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received shortly before the RFI closes will be answered, but we will attempt to provide respnses quickly. 7. Summary THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources and equipment that can support the ASOC-Mod software solution. The information provided in the RFI is subject to change and is not binding on the Government. The Air Force has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.
- Web Link
-
SAM.gov Permalink
(https://sam.gov/opp/ebf682399c124ba8a85a70c72eba11ba/view)
- Place of Performance
- Address: Hanscom AFB, MA, USA
- Country: USA
- Country: USA
- Record
- SN06250766-F 20220226/220224230102 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |