Helpful Airborne Wireless Communication Ecosystem Yielding Enhanced Sharing (HAWCEYES).

Page 1 of 2 STATEMENT OF WORK 418 th FLIGHT TEST SQUADRON (418FLTS) WIRELESS COMMUNICATIONS 27 MARCH 2026 1.0 SCOPE: This Statement of Work documents the requirements for a wireless communications innovation project titled Helpful Airborne Wireless Communication Ecosystem Yielding Enhanced Sharing (HAWCEYES). The overall objective is to improve communications by creating a wireless communications network that is carried on/off the aircraft and can connect all members of the test team. 1.1 BACKGROUND: The 418th Flight Test Squadron (418FLTS) at Edwards Air Force Base, CA, requests a proposal for work to be accomplished for the development of a wireless communications network that is carried on/off the aircraft and can connect all members of the test team. The communication systems on existing aircraft like the C-17, KC-135, and KC-46 aircraft is designed for an operational crew of 3-6 individuals split between the flight deck and the back of the plane (boomers or loadmasters). This presents a communication challenge for test missions with airborne control rooms where upwards of 20 individuals are on the plane. The existing solution involves comm splitter cables and extension cords which can connect some extra crew members but are clumsy, don't reach all parts of the aircraft, and present a tripping hazard. As a result, some members of the test team are not on comms during parts of the flight test. They're missing out on critical communications and the opportunity to add their knowledge to the team. 2.0 REQUIREMENTS: The contractor shall accomplish the following: 1. Design and build a carry-on/off wireless communications network that is self- contained and portable. Two copies shall be built in the first phase with the design retained for future options to build more copies. 2. Utilize existing 802.11xx (wifi) and/or Bluetooth protocols with a minimum range of 30 meters. 3. Be self powered via batteries for a minimum period of 30 minutes (60 minutes desired) and have the capability to be plugged into to 115VAC “wall power” for the duration of the flight test. 4. Utilize commercial VOIP software such as TeamSpeak or Mumble (or another commercially available software as determined jointly by the government and contractor) which supports device connectivity for both iOS and Android devices. Software shall have the ability to receive version updates. 5. Support a minimum of 32 connected devices. 6. Plug in to receive audio from the aircraft’s existing intercom system (ICS) via U-174 (single prong) connector and retransmit the audio to wirelessly connected -- 1 of 5 -- Page 2 of 2 devices. The ability to transmit audio on the aircraft ICS is desired (not required) for a future phase. 7. Provide all hardware and software design and specifications to support any required airworthiness and cybersecurity approvals. Approvals will be handled by the government using existing processes. 8. Ship or deliver two copies of the system to the 418FLTS at Edwards Air Force Base for ground checkouts. Retain the ability to build future copies if requested by the government. 9. Travel to the 418FLTS to support troubleshooting or tuning of the system on the aircraft. 10. Contractor personnel may be required to troubleshoot the system during flight tests on Air Force aircraft such as (but not limited to) C-17, KC-135, and KC-46 aircraft. Personnel for flight tests shall meet the 418FLTS requirements to fly as Mission Essential Personnel (MEP) with no inflight duties. If required, those requirements will be sent to the contractor by the 418FLTS and coordinated through existing MEP approval processes. 3.0 ADMINISTRATIVE: Contractor shall coordinate initial design with the government within 90 days of contract award to ensure it is expected to meet all requirements prior to build. As a new capability, some iteration is expected prior to finalizing the design and build for the final product. Once the final design is agreed upon, the contractor will build and deliver two copies within 90 days. Timelines for any on site troubleshooting, ground tests, and flight tests (if required) will be coordinated between the contractor and the 418FLTS based on aircraft availability. Future copies of the system may be requested by the government. 3.1 PROCEDURAL 3.1.1 All works for this project shall be cleared by the customers’ security and given a daily temporary worker’s badge before entering the customers’-controlled area. 3.1.2 Any waste or excess material resulting from any contract requirement shall be removed and disposed of at a proper disposal site off Edwards Air Force Base by the Contractor in strict accordance with applicable Federal, State, Country and local laws. 3.1.3 The contractor is permitted to work holidays and weekends to prevent delays due to conflicting schedules from the organizations listed above. 3.1.4 Safety and Health Requirements: It is the contractor's responsibility to ensure its employees and managers have a comprehensive understanding of OSHA requirements. Detailed information is available on the OSHA website at http://www.osha.gov. Contractors are responsible for complying with federal and state occupational safety and health standards for their employees, except where the Air Force contractually agreed to assume responsibility. -- 2 of 5 -- Page 3 of 2 3.1.5 Mishap Reporting. The Contractor shall promptly report pertinent facts to the Government Program Office (GPO) regarding mishaps involving government personnel or property, on or off the Air Force Installation, incidental to work performed IAW DAFI 91-204, Safety Investigation and Hazard Reporting. Direct costs related to the mishap shall be separated from other cost and provided to the GPO and Safety Investigators. 3.2 TEMPORARY FACILITIES AND TEMPORARY CONTROLS Not applicable 3.3 SECURITY REQUIREMENTS 3.3.1 All Contractor employees will be subject to a criminal history background check IAW DoDM 5200.08V3_AFMAN 31-101V3…