Inactive

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). AS... 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.0 Background The Tactical Air Control Party (TACP) Modernization program office at Hanscom AFB exists to deliver proven technology solutions to the roughly 2,000 Air Force TACPs operating in missions across the world. A TACP is a USAF individual or team aligned with a conventional United States Army unit, or with an Air Force, Army, Marine, or Navy special operations team. TACPs provide precision terminal attack guidance of U.S. and coalition fixed and rotary-wing CAS aircraft, artillery, and naval gunfire. They also establish and maintain C2 communications and counsel ground commanders on the best use of airpower. TACPs are air and ground combat experts, with proficiencies in small unit tactics, personal and crew served weapons, terminal attack control, airspace/fire support de-confliction, and mission planning to maximize airpower effectiveness. The primary certification for TACPs is the Joint Terminal Attack Controller (JTAC) certification. JTAC certified TACPs direct the actions of both combat/non-combat aircraft and direct/indirect fires through Close Air Support (CAS) to support friendly forces from a forward and stationary positions. Both JTAC and non-JTAC TACPs also support forward deployed forces from an Air Support Operations Center (ASOC). The ASOC is the principal command and control (C2) node for integrating Close Air Support power into counter-land operations. An ASOC can be co-located at the Division Tactical Operations Center (TOC) with the Division TACP, and serves warfighters by de-conflicting airspace, coordinating and requesting air and ground resources short of the Fire Support Coordination Line (FSCL), forwarding and filtering frontline analog and digital communications, and providing the best fixed wing asset for CAS missions. Communication is the primary discipline and warfighting proficiency for TACPs. As such, a TACPs tool set is primarily composed of rugged communication systems (mounted, dismounted, and ASOC/TOC), target designators, video and data receivers/transmitters, and associated software. In defining requirements, mounted technologies refer to those utilized by TACPs in and/or connected to mobile vehicles. Dismounted technologies refer to those utilized by TACPs absent from these vehicles. ASOC/TOC technologies, the subject of this RFI, refer to those utilized by TACPs in the ASOC/TOC. Due to greater demands on the ASOC/TOC, TACPs are seeking organic, cloud based, and rapid networking technologies, agile and interoperable software for CAS/C2, and modular hardware that is resource efficient and lightweight. 3.0 Requirements The TACP program office is seeking products and technologies with the potential to improve the performance of TACP ASOC objectives referenced in part 2.0 of this RFI. The TACP C2 Weapon System consists of 5 subsystems: Maneuver Gateway, Baseband Backhaul Kit, C2 Core Computer, Deployable Communications Package, and TAK Server. A brief description of each subsystem is included below with a few high level requirements. Overarching Requirements: TACP C2 sub-systems must be transportable by a single person Sub-systems must be able to communicate with each other Sub-systems must be transportable on commercial airlines Maneuver Gateway: Fail-forward node for Link-16 communications in case the ASOC is unavailable. Transmit and receive Link-16, SADL, and VMF messages Operate from AC, DC, or battery power Operate from within a vehicle Baseband Backhaul Kit: 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. Connect to 4 different user devices Run networks with different classification levels Utilize military and commercial satellite communication networks C2 Core Computer: Ruggedized computer to be paired with any TACP C2 Weapon System for user interfacing and control. Switch between multiple classified networks without re-imaging hard drives Utilize Windows Operating System Meet MIL-STD-810H standards for fluid susceptibility and shock and vibration Deployable Communications Package: HF, VHF, UHF, and SATCOM voice and data communications. Operate 1x HF and 2x UHF/VHF or FM or SATCOM channels simultaneously Receive Full Motion Video (FMV) data streams Capable of using TSM-X mesh networking waveform TAK Server: Process, host, and transfer metadata, .kml files, .kmz files, etc. on a TAK-based server. Bridge HF and TSM-X data 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. 4.0 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 the ASOC. 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 ASOC. 5.0 Responses Interested parties are requested to respond to this RFI with a white paper of their own format. 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 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. 6.0 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. 7.0 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. 8.0 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.