SOS Wessex Wraith Procurement v2 DRAFT.docx

AIR FORCE RESEARCH LABORATORY

INFORMATION DIRECTORATE

ROME, NEW YORK

STATEMENT OF SCOPE (SOS)

Wessex Wraith: Radiant Alfred (RA), Shadowcat (SC) and Tomahawk (TMK) Procurement and Support

Date: DRAFT

1.0 SCOPE. This statement of scope (SOS) defines the effort associated with the procurement of the Radiant Alfred (RA), Shadowcat (SC) and Tomahawk (TMK) Electronic Warfare (EW) systems. It includes the associated pre-planned product improvement (P3I), testing, training, operations, maintenance and sustainment support required for the duration of the product lifecycle.

2.0 BACKGROUND. The United States Air Force (USAF) and the Department of Defense (DoD) are challenged to keep pace with continually changing Electronic Warfare (EW) and surveillance and reconnaissance (S&R) requirements as well as transforming such activities into actions as part of an integrated non-kinetic kill chain against threat actors. Unfortunately, there is a lack of agile procurement, fielding and support of non-kinetic technology within the DoD, leading to capability gaps in both Force Protection and Force Projection. AFRL/RI has developed multiple systems to address these gaps and now seeks to produce and sustain them at greater scale.

b. Maritime OTM.

c. Equipped with Primary Telescoping Mast.

d. Equipped with three (3) additional auxiliary mast posts.

e. Equipped with Electro-Optical/Infrared (EO/IR) Camera System and Laser Range Finder (LRF).

f. Equipped with a Hemispheric Azimuth and Elevation (Az/El) Rotator System capable of supporting at least 100 lbs. of mounted and rotatable payload weight (e.g., antennas, cameras). The Rotator System shall have a baseline weight capacity of at least 100 lbs. to accommodate future configurations, independent of the initial payload's weight.

g. Equipped with Satellite Communications (SATCOM).

h. Equipped with Terrestrial Communications, e.g., Cellular.

i. Equipped with Dual-Wide Area Network (WAN), load-balancing Virtual Private Networking (VPN) Router.

j. Operates in all weather, terrain and environments (common deployed field conditions expected) with minimum Ingress Protection (IP) of IP65.

k. Support remote command, control and communications (C3) over VPN WAN for all functionality and data flow.

l. Ability to perform omni-directional radio frequency direction finding (RFDF) and geolocation with an N:2 Commutated/Switched DF Head capable of operating from at minimum 160 MHz to 4000 MHz. The contractor shall note that the frequency range of certain antennas, amplifiers and analog components in the RA system may not match the potential/possible frequency range of all Software-Defined Radio (SDR) transceivers.

m. Ability to perform omni-directional DF and geolocation with an N-Channel antenna array and SDR configuration, where N represents a variable number of coherent channels, determined by specific operational configurations, such as 4 or 8.

n. Ability in SDR hardware (HW), software (SW) and RF distribution (RFD) to perform multi-channel, omni-directional and directional Electronic Support (ES), Electronic Attack (EA) and Cyberspace Operations.

o. Ability to perform Digital Signal Processing (DSP) at the edge to calculate geolocation tracks for commercial and military RF emissions with Root Mean Square (RMS) error ≤ 10 degrees and Circular Error Probability (CEP) ≤ 10%.

p. Ability to perform DSP at the edge to correlate radio frequency (RF)-sensed data with commercially/publicly-available information (CAI/PAI).

q. Ability to place all geo-referenced and time-stamped information onto a moving map display, called Movements, accessible remotely via web browser.

r. Ability to disseminate geo-referenced and time-stamped RF data as Cursor-on-Target (CoT)/Tactical Assault Kit (TAK) messages. The system's edge DSP hardware shall possess a maximum latency of ≤ 12 seconds from the moment of initial RF/sensor detection to the successful dissemination of a signal/target geolocation within a formatted Cursor-on-Target (CoT) / TAK message to the tactical network.

s. Ability to protect all electronics in marinized enclosures, e.g., Radiant Alfred Mission Case (RAMC), meeting Ingress Protection (IP) of IP65.

t. Ability to operate from Volts Alternating Current (VAC) shore power or VAC generator power with requisite power conversion and conditioning/protection without the need for any components outside the RAMC.

u. The system shall have a minimum of eight (8) SDR receive (Rx) and transmit (Tx) channels that can tune from 2 MHz to 7200 MHz with a minimum digital instantaneous bandwidth of 100 MHz/channel and RF performance suitable for detecting and geolocating spread spectrum non-commercial signals. This component is referred to as the primary, high-performance SDR transceiver.

v. The system shall have a minimum of four (4) directional antennas mounted and steerable on the Az/El rotator that support receive (Rx) and transmit (Tx) from 160 MHz to 7200 MHz via the primary SDR transceiver.

w. The system shall have a dedicated 802.11 WiFi Rx/Tx subsystem with at least eight (8) Rx/Tx channels matched with appropriate directional antennas on the Az/El rotator.

x. The system shall have a dedicated 5G Frequency Region 1 (FR1) cellular subsystem with at least eight (8) Rx/Tx channels matched with appropriate directional antennas on the Az/El rotator.

y. The system shall have a dedicated omni-directional subsystem to receive and process Automatic Identification System (AIS) signals from atop the Az/El rotator.

z. The system shall have a dedicated omni-directional subsystem to receive and process Automatic Dependent Surveillance – Broadcast (ADS-B) signals from atop the Az/El rotator.

3.1 RA Product/Performance Requirements.

3.1.1 RA Physical Requirements.

a. The maximum RA system weight shall be 500 lbs. (including attachments and non-power peripherals but excluding mast ballast weight and power peripherals (e.g., fuel-powered generator)) and shall be transportable by standard military and commercial freight without requiring specialized loading dock equipment or procedures.

b. System shall be mobile on the deck of a ship (i.e., secured to and operating from a ship’s deck while the ship is underway) or the bed of a truck (i.e., secured to and operating from the truck’s bed while the truck is in motion) in an operational configuration.

c. System and all components and attachments shall be uniform color (e.g., Desert Tan, Haze Gray) to match the primary field conditions.

b. Equipped with laser range finder (LRF).

c. Equipped with a minimum of one (1) 8-Channel Software-Defined Radio (SDR) Transceiver (potentially fulfilled by two (2) phase-coherent/time-synchronized 4-Channel SDR Transceiver subsystems) capable of both Switched DF and N-Channel DF against spread spectrum non-commercial signals. This is the primary RA SDR.

d. Equipped with a minimum of one (1) 8-Channel Software-Defined Radio (SDR) Transceiver (potentially fulfilled by two (2) phase-coherent/time-synchronized 4-Channel SDR Transceiver subsystems) capable of both Switched and N-Channel DF against 5G NR FR1 commercial signals. This is the auxiliary RA SDR.

e. Equipped with minimum two (2) 4-Channel band-specific WiFi subsystems covering the 2.4 GHz band and 5.8 GHz band.

f. Equipped with Inertial Navigation Sensor (INS) and Global Navigation Satellite System (GNSS) sensors that perform together as an Attitude and Heading Reference System (AHRS). This AHRS capability shall be able to cold start in a Global Positioning System (GPS)-denied environment (i.e., there is no U.S. GPS signal of any kind usable from space before and during RA initialization and operations) and be robust against all forms of GPS jamming and spoofing.

g. All Rx antenna inputs shall have a minimum of 1 Watt limiter protection.

h. All Rx antenna inputs shall have low noise amplification (LNA) of source signals, high/band pass filtering (HPF/BPF) to perform out-of-band signal rejection and low pass filtering (LPF) to perform anti-aliasing.

i. All Tx antenna outputs shall have a minimum of LPF to protect against harmonics.

j. All Tx antenna outputs shall have appropriate power amplification for the RF signals they are meant to emulate (e.g., ADS-B, AIS, Cellular, WiFi, other commercial, military signals).

k. Purpose-built SDR capable of receiving ADS-B.

l. Purpose-built SDR capable of receiving AIS.

m. Weather Station with ability to measure temperature, barometric pressure and wind direction/speed.

3.1.3 RA Standard Attachments.

a. All RA systems come standard with an Az/El rotator and payload assembly along with three auxiliary mast posts that are all integrated as part of the Primary Telescoping Mast.

b. One (1) Omni-Directional Radio Frequency Direction Finding (RFDF) Head in N:2 Commutated/Switched DF Configuration on an auxiliary mast post.

3.1.4 RA Communications.

a. 5th Generation (5G) Wireless Cellular VPN for Terrestrial Communications.

b. End User Terminal (EUT) providing Virtual Private Network (VPN) security, failover and load-balancing across 5G cellular wide area network (WAN) and at least one additional simultaneous WAN link including but not limited to K/Ku/Ka-Band VSAT SATCOM or Eutelsat OneWeb/Starlink SATCOM.

c. VPN shall support OpenVPN and WireGuard architectures as well as NIST-standardized (e.g., FIPS 203, 204, and 205) Post-Quantum Cryptography (PQC) encryption algorithms (e.g., ML-KEM, ML-DSA).

d. RA systems are interoperable with each other throughout the deployed system fleet, allowing each RA node to collaborate on geolocation/targeting objectives and to combine sensors/effects from multiple RA nodes. RA nodes are interoperable with SC nodes and Tomahawk (TMK) nodes. More information on SC nodes and TMK nodes is below.

3.1.5 RA Radio Frequency (RF) Spectrum Supportability/Certification.

a. System shall use J/F-12 certified radios and spectrum-dependent (S-D) equipment for all communications. It is anticipated the RA systems shall primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

b. The contractor shall aid Air Force Spectrum Operations (AFSO) in ensuring all S-D equipment is allocated and assigned for use, at all locations, prior to any test event or equipment operations. It is anticipated the RA systems shall primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

c. The contractor shall use S-D equipment operating on approved frequency bands for agile, flexible, efficient and effective communications worldwide. Equipment with more than one operational frequency range shall be required to satisfy worldwide spectrum operations. It is anticipated the RA systems shall primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands that are valid in any host country.

d. The contractor shall provide POC information necessary to assist in obtaining U.S. & Possessions and Host Nation radio frequency assignments prior to equipment delivery. Frequency assignments can take between 90-120 days or longer, depending on backlog, from time of submission. RF supportability, certification and assignment processes shall ensure equipment communications are protected, shall operate when required with no interference, is not seized nor fines incurred due to transmitting on non-federal, non-approved frequencies.

3.1.6 RA Cyber-Security and Risk Management Framework (RMF) Hardware Requirements.

a. The contractor shall aid the Government in obtaining an Authorization to Operate (ATO) for the Radiant Alfred (RA) system through the DoD Risk Management Framework process. Detailed system information is vital for all certification packages.

b. The contractor shall work directly with AF/AFRL Cyber Security POC to ensure all delivered information technology (IT) hardware is in compliance with AFMAN 17-1203, Information Technology (IT) Asset Management (ITAM).

c. The contractor shall provide all computer hardware information, including type, manufacturer, model number, and serial number for each major component and discrete components of computer hardware (i.e., graphics card, network card, memory type, etc.) identified to facilitate government approval of each component.

d. The contractor shall provide all user guides and documentation to include a system overview, installation manuals and a list of all logical network ports and protocols (e.g., TCP/UDP ports) being used, including specific explanations of port functions.

3.1.7 RA Cyber-Security and Risk Management Framework (RMF) Software Requirements.

a. The contractor shall deliver RA using software with continued security support. Legacy operating systems and software dependencies without continued security support (e.g., Windows 7, Windows 10) are unacceptable.

b. The contractor shall provide copies of all software used with RA and associated licenses to install and operate the product(s). The contractor shall provide any software operating or installation manuals, End User License Agreements (EULA), or documentation supporting open-source software that may be used in the development of the product.

c. The contractor shall provide information regarding installed software: Name of application and version numbers, software product description to include functionality, use, and capabilities, type of data processed by the application, compatibility with IPv6, vendor address, phone number and web site address, peripheral hardware use and application requirements for any additional software.

3.1.8 RA Other Documentation.

a. The contractor shall provide a complete Technical Data Package (TDP) for the entire RA system including but not limited to the following Intellectual Property (IP): all hardware drawings, hardware schematics, software (to include all gateware and firmware) source code, software build environment including build scripts, Software Bill of Materials (SBOM), Application Programming Interfaces (APIs) and Interface Control Descriptions (ICDs). All IP shall identify the Government’s Data Rights to said IP and shall be accompanied by an appropriate rationale. The Government desires Government Purpose Rights (GPR) or Unlimited Rights, and the contractor shall submit a formal Data Rights Assertion List with their proposal to identify any components with Restricted/Limited rights.

b. The contractor shall provide technical information such as Bill of Materials (BOM) sufficient to assist the Government in addressing instances of critical safety concern; prevent Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues and aid in configuration management control throughout the contract period.

c. Operations and maintenance manuals in electronic format.

d. User’s manual, supplemental data and general engineering drawings.

e. Warranty documentation for all substantive components.

f. Mean Time Between Failures (MTBF): (e.g., > 2,000 operational hours) and Mean Time To Repair (MTTR): (e.g., < 2 hours for organizational-level field repairs) for all substantive components.

g. The contractor shall be responsible for affixing Item Unique Identification (IUID) labels to each required complete system in accordance with DFARS Clause at 252.211-7003, Item Unique Identification and Valuation and DFARS 211.274-2, Policy for Unique Identification. Markings shall be in accordance with MIL-STD-129 and MIL-STD-130. All major modular components shall have IUID for tracking warranty, manufacturing information, and location.

3.1.9 RA Mobility.

a. For transport the system shall be able to ship worldwide via FedEx, UPS, DHL, XPO or military transport.

b. Able to operate outdoors in all terrain conditions, including on the flat deck of a ship and the flat bed of a truck.

c. The system shall operate without degradation at any surface elevation up to 12,500 feet above Mean Sea Level (MSL) wherever the ambient air temperature remains within a range of 14° F (-10° C) to 122° F (50° C) or wider.

3.1.10 RA Environmental.

a. The system shall be capable of both day and night operations.

b. The system shall operate at an ambient temperature range of 14° F (-10° C) to 122° F (50° C) or wider without any external thermal management. The system can be stored or transported at an ambient non-operating/storage temperature range of -22° F (-30° C) to 158° F (70° C).

c. The system shall have Ingress Protection (IP) rating of at least IP65 without any external environmental management.

d. The system shall be MIL-STD-810H (Method 514.8 (Vibration), Method 516.8 (Shock), Method 509.7 (Salt Fog), and Method 506.6 (Rain)) for ground mobile and maritime use) compliant and MIL-STD-461H (Electromagnetic Interference and Compatibility) compliant.

3.1.11 RA Receiver/Exciter.

a. 8-Channel primary SDR transceiver capable of tuning to frequencies from at least 2 MHz to 7200 MHz.

b. 8-Channel primary SDR transceiver capable of 100 MHz/channel digital instantaneous bandwidth.

c. 8-Channel primary SDR transceiver capable of independent/coherent N-channel Rx/Tx tuning.

d. 8-Channel auxiliary SDR transceiver capable of tuning to frequencies at least 160 MHz to 7200 MHz for purposes of 5G NR FR1.

e. 8-Channel auxiliary SDR transceiver capable of minimum 40 MHz/channel digital instantaneous bandwidth.

f. 8-Channel auxiliary SDR transceiver capable of minimum 4x4 Multiple-Input, Multiple Output (MIMO).

g. 8-Channel auxiliary SDR transceiver system with signal-specific subsystem capable of targeted 4-channel MIMO operations in both the 2.4 GHz and 5.8 GHz Industrial, Scientific and Medical (ISM) Bands. ISM band operations shall never interrupt 5G NR FR1 operations.

h. Purpose-built SDR capable of receiving ADS-B. The 8-Channel primary SDR transceiver shall never be necessary to receive ADS-B.

i. Purpose-built SDR capable of receiving AIS. The 8-Channel primary SDR transceiver shall never be necessary to receive AIS.

3.1.12 RA Safety.

a. The EO/IR camera shall be capable of visually sweeping the RF hazard zone to ensure personnel and objects are clear of directional antenna emissions.

b. Unintended Electromagnetic Interference (EMI) from the RA system shall be minimized.

c. RA systems shall support automatic thermal shutoff and automatic optimization for incoming weather patterns (e.g., above average nighttime heat, strong winds).

d. RA system shall support a weather conditions prediction feature that allows system shutoff and rotator positioning in anticipation of high temperatures and high winds.

3.1.13 RA Shipping.

The contractor shall research and resolve, at no additional cost to the Government, shipping damages, losses, discrepancies or delays. The contractor shall report to the Government within seven (7) calendar days from the occurrence/discovery of the issue, and subsequently research and resolve at no additional cost to the Government.

3.2 RA Sustainment Support.

3.2.1 RA Product Testing (CONUS East Coast)

a. The contractor shall travel to CONUS locations on the East Coast (e.g., Virginia Beach, VA) to conduct developmental testing (DT) and operational testing (OT) with military users allowing the military users to perform Field User Evaluation (FUE) of RA and complete necessary Concepts of Employment (CONEMPs) before fielding or deployment of the system. RA product testing shall include two (2) Field Service Representatives (FSRs) for two weeks (i.e., ten (10) total business days) on location, not including travel time to the testing destination, the time for standard testing preparation (e.g., production of test plan with the Government) and the time to prepare a standard After-Action Report (AAR) and Test Report as deliverables. A separate Trip Report shall not be required. This item is for labor-related charges only. Actual travel costs and actual shipping costs shall be handled separately on an actual cost-basis.

3.2.2 RA Product Testing (CONUS West Coast)

a. The contractor shall travel to CONUS locations on the West Coast (e.g., San Diego, CA) to conduct developmental testing (DT) and operational testing (OT) with military users allowing the military users to perform Field User Evaluation (FUE) of RA and complete necessary Concepts of Employment (CONEMPs) before fielding or deployment of the system. RA product testing shall include two (2) Field Service Representatives (FSRs) for two weeks (i.e., ten (10) total business days) on location, not including travel time to the testing destination, the time for standard testing preparation (e.g., production of test plan with the Government) and the time to prepare a standard After-Action Report (AAR) and Test Report as deliverables. A separate Trip Report shall not be required. This item is for labor-related charges only. Actual travel costs and actual shipping costs shall be handled separately on an actual cost-basis.

3.2.3 RA Product Testing (OCONUS INDOPACOM)

a. The contractor shall travel to OCONUS locations within INDOPACOM (e.g., Guam; Yokota AB) to conduct developmental testing (DT) and operational testing (OT) with military users allowing the military users to perform Field User Evaluation (FUE) of RA and complete necessary Concepts of Employment (CONEMPs) before fielding or deployment of the system. RA product testing shall include two (2) Field Service Representatives (FSRs) for two weeks (i.e., ten (10) total business days) on location, not including travel time to the testing destination, the time for standard OCONUS testing preparation (e.g., production of test plan with the Government, host country paperwork) and the time to prepare a standard After-Action Report (AAR) and Test Report as deliverables. A separate Trip Report shall not be required. This item is for labor-related charges only. Actual travel costs and actual shipping costs shall be handled separately on an actual cost-basis.

3.2.4 RA Product Classroom Training.

a. The contractor shall support classroom-based instruction (CBI), i.e., training, at a contractor-provided facility with one (1) full-time trainer.

b. CBI shall be for up to one (1) full business week (i.e., 8 hours/day instruction for 5 consecutive business days, not including separate lunch hour) for up to twelve (12) students per classroom training session.

c. The contractor shall develop, maintain and publish an electronic-based instruction manual detailing all operational capability of the system, general maintenance procedures and other related products and materials. Training shall also include information covering the logistical support side of the contract, including system maintenance, parts ordering, and system repair processes.

i.

3.2.5 RA Product Field Training (CONUS East Coast).

a. The contractor shall travel to CONUS locations on the East Coast (e.g., Virginia Beach, VA) to provide onsite training to users following the initial RA system delivery.

b. RA product training shall include two (2) Field Service Representatives (FSRs) for two weeks (i.e., ten (10) total business days) on location, not including travel time to the training destination, the time for standard training preparation (e.g., production of training documents) and the time to prepare a standard After-Action Report (AAR) and Trip Report as deliverables. This item is for labor-related charges only. Actual travel costs and actual shipping costs shall be handled separately on an actual cost-basis.

3.2.6 RA Product Field Training (CONUS West Coast).

a. The contractor shall travel to CONUS locations on the West Coast (e.g., San Diego, CA) to provide onsite training to users following the initial RA system delivery.

b. RA product training shall include two (2) Field Service Representatives (FSRs) for two weeks (i.e., ten (10) total business days) on location, not including travel time to the training destination, the time for standard training preparation (e.g., production of training documents) and the time to prepare a standard After-Action Report (AAR) and Trip Report as deliverables. This item is for labor-related charges only. Actual travel costs and actual shipping costs shall be handled separately on an actual cost-basis.

3.2.7 RA Product Field Training (OCONUS INDOPACOM).

a. The contractor shall travel to OCONUS locations within INDOPACOM (e.g., Guam; Yokota AB) to provide onsite training to users following the initial RA system delivery.

b. RA product training shall include two (2) Field Service Representatives (FSRs) for two weeks (i.e., ten (10) total business days) on location, not including travel time to the training destination, the time for standard training preparation (e.g., production of training documents) and the time to prepare a standard After-Action Report (AAR) and Trip Report as deliverables. This item is for labor-related charges only. Actual travel costs and actual shipping costs shall be handled separately on an actual cost-basis.

3.2.8 RA Remote Maintenance Plan (CONUS Remote Maintenance).

a. The Government may aggregate a list of observed firmware bugs, software bugs and desired software maintenance that applies specifically to operational performance optimization of RA in the deployed conditions. The Government may acquire up to a specified maximum quantity of quarterly maintenance plans to address the items above with the appropriate urgency to meet the Government’s estimated level of effort. During rectification of the aforementioned the contractor shall also apply any security critical patches that have become recommended during that timeframe.

b. The contractor shall provide a firmware and software update, that can be installed remotely by the contractor or locally by the Government, depending on the preference of the Government. An automated installer/updater is strongly preferred. The update is to be accompanied by installation/update instructions and a Changelog that identifies the requested fixes/patches that have been implemented. The Changelog shall also contain a running list of any requested fixes/patches that remain unaddressed after the update, and the reason.

c. RA Remote Maintenance Plan is to be provided in quarterly increments (i.e., three (3) calendar months) and assume a one (1) annualized Full-Time Equivalent (FTE) of the appropriate mix of labor (e.g., software engineer, systems engineer, test engineer, technical writer) over those three (3) months, i.e., the equivalent of four (4) laborers working full-time during that three (3) month period, along with any other identified standard ODC items and/or consumables required for maintenance.

3.2.9 RA Local Maintenance Plan (OCONUS On-Site Maintenance).

a. The Government may aggregate a list of observed firmware bugs, software bugs and desired software maintenance that applies specifically to operational performance optimization of RA in OCONUS deployed conditions. In certain instances, the Government may determine that in order to provide sufficient maintenance support to the RA product the work shall be done on-site in cooperation with local mission partners and host country representatives. The Government may acquire an unlimited number of quarterly maintenance plans to address the items above with the appropriate urgency to meet the Government’s estimated level of effort. During rectification of the aforementioned the contractor shall also apply any security critical patches that have become recommended during that timeframe.

b. The contractor shall provide continuous on-site firmware and software maintenance as well as provide maintenance support to on-site mission partners and/or on-site foreign partners as required. All firmware and software maintenance is to be accompanied by installation/update instructions and a Changelog that identifies the requested fixes/patches that have been implemented. The Changelog shall also contain a running list of any requested fixes/patches that remain unaddressed after the update, and the reason.

c. RA Local Maintenance Plan is to be provided in quarterly increments (i.e., three (3) calendar months) and assume a one (1) annualized Full-Time Equivalent (FTE) of the appropriate mix of labor (e.g., software engineer, systems engineer, test engineer, technical writer) over those three (3) months, i.e., the equivalent of four (4) laborers working full-time during that three (3) month period, along with any other identified standard ODC items and/or consumables required for maintenance.

d. Travel costs for visiting the RA system in the field shall be handled separately on an actual cost-basis.

3.2.10 RA Warranty Repair Plan (Ship to Depot).

a. The contractor shall coordinate shipment and repair of RA systems that are not fully functioning in the field.

b. The contractor shall replace identified malfunctioning components currently under manufacturer’s original warranty at no additional material cost, only the cost of non-warrantied labor for removal, replacement and verification of the warrantied part(s).

c. The contractor shall replace identified malfunctioning components no longer covered under manufacturer’s original warranty. Actual replacement material costs and shipping costs for those items not under warranty shall be handled separately on an actual cost-basis.

d. Actual shipping costs for retrieving the RA system from the field and returning the RA system to the field shall be handled separately on an actual cost-basis.

3.2.11 RA Warranty Repair Plan (Repair-in-Place).

a. The contractor shall travel to worldwide locations to repair RA systems that are not fully functioning in the field should the Government determine that is advantageous over returning the item to the depot. The contractor shall only attempt repair-in-place should the contractor determine with the Government that the RA in question can be repaired by the FSR in no more than one business week on location, not including travel time, standard preparation time, and the time required to prepare a Trip Report as a deliverable.

b. The contractor shall replace identified malfunctioning components currently under manufacturer’s original warranty at no additional material cost, only the cost of non-warrantied labor for removal, replacement and verification of the warrantied part(s).

c. The contractor shall replace identified malfunctioning components no longer covered under manufacturer’s original warranty. Actual replacement material costs and shipping costs for those items not under warranty shall be handled separately on an actual cost-basis.

d. Travel costs for visiting the RA system in the field shall be handled separately on an actual cost-basis.

3.2.12 RA Very Small Aperture Terminal (RA VSAT).

a. The contractor shall produce a K/Ku/Ka-Band VSAT suitable for multiband SATCOM capable of automatic electronic band-switching (K/Ka-Band, K/Ku-Band) and automatic electronic polarization switching (Right Hand Circular Polarization (RHCP), Left Hand Circular Polarization (LHCP)).

b. The RA VSAT shall be optimally matched to the RA EUT and to the overall RA system with appropriate logistics, mounting, cabling, marinization/weatherization and color-matched coatings (RF transparent where required).

c. The SATCOM modem, antenna controller unit (ACU) and SATCOM mission management module associated with the RA VSAT shall be suitable for inclusion inside of the RA mission case (RAMC) in a modular fashion along with the other RA electronics.

d. The RA VSAT, with the assistance of an RA, shall be able to cold start in a Global Positioning System (GPS)-denied environment (i.e., there is no U.S. GPS signal of any kind usable from space before and during RA VSAT initialization and operations) and be robust against all forms of GPS jamming and spoofing.

e. RA VSAT shall be able to match RA system operating environment requirements, including Ground At-the-Halt (ATH) e.g., Stationary; and Ground On-the-Move (OTM), e.g., Mobile, and Maritime OTM. The system shall be capable of both day and night operations. The system shall operate at ambient temperatures from at least 14° F (-10° C) to at least 122° F (50° C) without requiring any external thermal management. The system shall have Ingress Protection (IP) rating of at least IP65 without requiring any external environmental management.

f. The RA VSAT shall have Intermediate Frequency (IF) monitoring from 950 MHz to 2150 MHz on receive (Rx) and transmit (Tx).

3.2.13 RA Maintenance Kit. The contractor shall assemble and make available for purchase a general-purpose user maintenance kit. The purpose of this kit is to minimize the need for an RA system to be shipped back to depot for repair, or for an FSR to have to travel to an RA system for repair, in cases where no system component needs to be replaced with a spare.

3.2.14 RA Spare Parts Kit. The contractor shall assemble and make available for purchase a spares kit containing replacement parts of commonly worn items such as connectors and fasteners that can break during normal use. The purpose of this kit is to minimize the need for an RA system to be shipped back to depot for repair, or for an FSR to have to travel to an RA system for repair, in cases where system components need to be replaced.

3.2.15 RA Peripherals.

The contractor shall provide pricing for any additional potential RA system peripherals, i.e., accessories that are peculiar to the RA system not limited to RA-specific mounting, cabling, marinization/weatherization and color-matched coatings (RF transparent where required), to include the cost of full peripheral integration and testing at the time of the RA system build. Offerors are not required to propose all peripherals. The Government highly recommends that the proposer price out peripherals a., b., c., d. and o. as detailed below. Potential peripherals include but are not limited to:

a. Minimum IP65 High gain cellular antennas for cellular C3 with standard mount for Rotator or Auxiliary mast.

b. Minimum IP65 Starlink/Starshield system for SATCOM C3 with standard mount for Rotator or Auxiliary mast.

c. Minimum IP65 Eutelsat OneWeb system for SATCOM C3 with standard mount for Rotator or Auxiliary mast.

d. Auxiliary case for third-party SDR payloads complete with fully integrated cable, environmental, thermal and power management with IP65 ingress protection.

e. Minimum IP65 Radar with standard mount for Rotator or Auxiliary mast.

f. Minimum IP65 Acoustic sensor with standard mount for Rotator or Auxiliary mast.

g. Minimum IP65 Gimballed sniper rifle with standard mount for Rotator or Auxiliary mast.

h. Minimum IP65 Gimballed optical telescope with standard mount for Rotator or Auxiliary mast.

i. Minimum IP65 Electromagnetic Field/Interference (EMF/EMI) sensor with mount for Rotator or Auxiliary mast.

j. Minimum IP65 Chemical, Biological, Radiological, and Nuclear (CBRN) sensor with mount for Rotator or Auxiliary mast.

k. Minimum IP65 advanced weather forecasting system that in addition to measuring temperature, barometric pressure and wind direction/speed could potentially measure any of the following: humidity, Wind Chill/Heat Index, illuminance (i.e., light intensity), lightning strikes, air quality, and ambient noise level.

l. Minimum IP65 Line Replaceable Unit (LRU) power amplification kits for various RF bands and power levels.

m. Minimum IP65 Solar-based power generation, battery backup and power management system that can provide VAC to RA akin to shore power or generator.

n. Minimum IP65 Volts Direct Current (VDC) to VAC converter that can accept a range of VDC power (e.g., 24 VDC – 270 VDC, for example) and provide VAC to RA akin to shore power or generator.

o. Minimum IP54 Operator laptop, not expected to remain out in the elements, but expected to be able to perform local maintenance, control, etc. in potential natural weather conditions (e.g., rain storm). MIL-STD-1472H requires that displays intended for outdoor daylight use (up to 25,000 lux) have sufficient luminance contrast. Furthermore, the displays must have dimming capabilities to support night operations and blackout discipline.

3.2.16 RA Consumables.

The contractor shall provide pricing for any additional potential RA system consumables. Potential consumables include but are not limited to:

a. 5G Cellular service time.

b. Starlink/Starshield system SATCOM service time.

c. Eutelsat OneWeb system SATCOM service time.

d. Subscription to Commercially-Available Information (CAI) source and Application Programming Interface (API) access. The contractor shall note that the Government would expect to pay for only one CAI subscription (e.g., API access) fleet-wide across all RA systems, SC systems and TMK systems.

e. Cloud-based services that enhance the functionality of RA nodes.

4.0 Shadowcat (SC) Requirements.

The work required by this contract shall be performed in accordance with standards and formats identified within this SOS. Given that the Shadowcat (SC) systems are intended to operate in a variety of hostile environments and terrain characterized by congested and contested EMS, the systems will be subjected to a variety of environmental conditions and expected to withstand a significant amount of RF jamming and Cyberspace attacks during operations. The contractor shall deliver an SC system that meets the following capabilities:

a. Ground At-the-Halt (ATH) e.g., Stationary; and Ground On-the-Move (OTM), e.g., Mobile.

b. Maritime OTM.

c. Airborne OTM.

d. Equipped with Fiber-Optic Gyroscope (FOG).

e. Equipped with Dual-Wide Area Network (WAN), load-balancing Virtual Private Networking (VPN) Router with embedded Terrestrial Communications, e.g., Cellular.

f. Operate in all weather, terrain and environments (common deployed field conditions expected) with minimum Ingress Protection (IP) of IP65.

g. Support remote command, control and communications (C3) over VPN WAN for all functionality and data flow.

h. Ability to perform N-Channel, host platform flexible (i.e., no fixed one-size-fits-all antenna array but rather platform-optimized mounting) omni-directional radio frequency direction finding (RFDF) and geolocation using a cumulative soft plate/patch panel area between 162 square inches and 441 square inches total. This explicitly means that the SC system meets the requirements in Section 4 with a flexible menu of potential N-Channel Geolocation Array options that can be built-to-suit commensurate with host platform constraints.

i. Ability to perform antenna array flexible (as dictated by host platform, commensurate with 4.0.h. above) omni-directional or directional Electronic Support (ES), Electronic Attack (EA) and Cyber Operations.

j. Ability to perform Digital Signal Processing (DSP) at the edge to calculate geolocation tracks for commercial and military RF emissions with Root Mean Square (RMS) error ≤ 10 degrees and Circular Error Probability (CEP) ≤ 10%.

k. Ability to place all geo-referenced and time-stamped information onto a moving map display, called Movements, accessible remotely via web browser.

l. Ability to disseminate geo-referenced and time-stamped RF data as Cursor-on-Target (CoT)/Tactical Assault Kit (TAK) messages. The system's edge DSP hardware shall possess a maximum latency of ≤ 12 seconds from the moment of initial RF/sensor detection to the successful dissemination of a signal/target geolocation within a formatted Cursor-on-Target (CoT) / TAK message to the tactical network.

m. Ability to operate from Volts Direct Current (VDC) power, with a range from 24 VDC to 36 VDC, with requisite power conversion and conditioning/protection without the need for any components outside the primary IP65 SC enclosure(s).

n. Ability to protect all electronics in marinized enclosures meeting Ingress Protection (IP) of IP65.

o. The system shall have minimum of eight (8) SDR receive (Rx) and transmit (Tx) channels that can tune from 2 MHz to 7200 MHz with a minimum digital instantaneous bandwidth of 100 MHz/channel.

p. The system shall have a dedicated 802.11 WiFi Rx/Tx subsystem with at least four (4) Rx/Tx channels matched with appropriate omni-directional antennas.

q. The system shall have a dedicated 5G Frequency Region 1 (FR1) cellular subsystem with at least four (4) Rx/Tx channels matched with appropriate omni-directional antennas.

r. The system shall have a dedicated subsystem to receive and process Automatic Identification System (AIS) signals with a single omni-directional antenna.

s. The system shall have a dedicated subsystem to receive and process Automatic Dependent Surveillance – Broadcast (ADS-B) signals with a single omni-directional antenna.

4.1 SC Product/Performance Requirements.

4.1.1 SC Physical Requirements.

a. The maximum SC system weight shall be 350 lbs. (including attachments and peripherals) and shall be transportable by standard military and commercial freight without requiring specialized loading dock equipment or procedures.

b. System shall be multiple-domain capable, installable on a ground vehicle, maritime platform or airborne platform.

c. System and all components and attachments shall be uniform color (e.g., Desert Tan, Haze Gray) to match the primary field conditions or host platform.

4.1.2 SC Sensors

a. Equipped with minimum of one (1) 8-Channel Software-Defined Radio (SDR) Transceiver capable of N-Channel RFDF and geolocation against spread spectrum, non-commercial signals.

b. Equipped with minimum 4-Channel SDR Transceiver capable of N-Channel RFDF and geolocation against 5G NR FR1 signals.

c. Equipped with minimum 4-Channel WiFi subsystem.

d. Equipped with Inertial Navigation Sensor (INS), FOG and Global Navigation Satellite System (GNSS) sensors that perform together as an Attitude and Heading Reference System (AHRS). This AHRS capability shall be able to cold start in a Global Positioning System (GPS)-denied environment (i.e., there is no U.S. GPS signal of any kind usable from space before and during SC initialization and operations) and be robust against all forms of GPS jamming and spoofing.

e. All Rx antenna inputs shall have a minimum of 1 Watt limiter protection.

f. All Rx antenna inputs shall have low noise amplification (LNA) of source signals, high/band pass filtering (HPF/BPF) to perform out-of-band signal rejection and low pass filtering (LPF) to perform anti-aliasing.

g. All Tx antenna outputs shall have a minimum of LPF to protect against harmonics.

h. All Tx antenna outputs shall have appropriate power amplification for the RF signals they are meant to emulate (e.g., ADS-B, AIS, Cellular, WiFi, other commercial, military signals).

4.1.3 SC Attachments.

a. One (1) Omni-Directional or Directional Electronic Attack (EA) aperture in an Antenna Array Assembly (AAA) complete with Array Conditioning Electronics (ACE). The ACE provides required limiter protection, gain/attenuation, analog filtering and Rx/Tx switching. The EA AAA and ACE shall be minimum IP65.

b. One (1) 8-Channel, N-Channel Coherent Geolocation Configuration in an Antenna Array Assembly (AAA) complete with Array Conditioning Electronics (ACE). The ACE provides required limiter protection, gain/attenuation, analog filtering and Rx/Tx switching. The Geolocation AAA and ACE shall be minimum IP65.

4.1.4 SC Communications.

a. Embedded 5th Generation (5G) Wireless Cellular VPN for Terrestrial Communications.

b. Wide Area Networking (WAN) port on VPN router for platform/third-party provided Terrestrial communications or SATCOM. VPN shall support OpenVPN and WireGuard architectures as well as NIST-standardized (e.g., FIPS 203, 204, and 205) Post-Quantum Cryptography (PQC) encryption algorithms (e.g., ML-KEM, ML-DSA).

c. SC systems are interoperable with each other throughout the deployed system fleet, allowing each SC node to collaborate on geolocation/targeting objectives and to combine sensors/effects from multiple SC nodes. SC nodes are interoperable with RA nodes and TMK nodes. More information on TMK nodes is below.

4.1.5 SC Radio Frequency (RF) Spectrum Supportability/Certification.

a. System shall use J/F-12 certified radios and spectrum-dependent (S-D) equipment for all communications. It is anticipated the SC systems shall primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

b. The contractor shall aid Air Force Spectrum Operations (AFSO) in ensuring all S-D equipment is allocated and assigned for use, at all locations, prior to any test event or equipment operations. It is anticipated the SC systems shall primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

c. The contractor shall use S-D equipment operating on approved frequency bands for agile, flexible, efficient and effective communications worldwide. Equipment with more than one operational frequency range shall be required to satisfy worldwide spectrum operations. It is anticipated the SC systems shall primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands that are valid in any host country.

d. The contractor shall provide POC information necessary to assist in obtaining U.S. & Possessions and Host Nation radio frequency assignments prior to equipment delivery. Frequency assignments can take between 90-120 days or longer, depending on backlog, from time of submission. RF supportability, certification and assignment processes shall ensure equipment communications are protected, shall operate when required with no interference, is not seized nor fines incurred due to transmitting on non-federal, non-approved frequencies.

4.1.6 SC Cyber-Security and Risk Management Framework (RMF) Hardware Requirements.

a. The contractor shall aid the Government in obtaining an Authorization to Operate (ATO) for the Shadowcat (SC) system through the DoD Risk Management Framework process. Detailed system information is vital for all certification packages.

b. The contractor shall work directly with AF/AFRL Cyber Security POC to ensure all delivered information technology (IT) hardware is in compliance with AFMAN 17-1203, Information Technology (IT) Asset Management (ITAM).

c. The contractor shall provide all computer hardware information, including type, manufacturer, model number, and serial number for each major component and discrete components of computer hardware (i.e., graphics card, network card, memory type, etc.) identified to facilitate government approval of each component.

d. The contractor shall provide all user guides and documentation to include a system overview, installation manuals and a list of all logical network ports and protocols (e.g., TCP/UDP ports) being used, including specific explanations of port functions.

4.1.7 SC Cyber-Security and Risk Management Framework (RMF) Software Requirements.

a. The contractor shall deliver SC using software with continued security support. Legacy operating systems and software dependencies without continued security support (e.g., Windows 7, Windows 10) are unacceptable.

b. The contractor shall provide copies of all software used with SC and associated licenses to install and operate the product(s). The contractor shall provide any software operating or installation manuals, End User License Agreements (EULA), or documentation supporting open-source software that may be used in the development of the product.

c. The contractor shall provide information regarding installed software: Name of application and version numbers, software product description to include functionality, use, and capabilities, type of data processed by the application, compatibility with IPv6, vendor address, phone number and web site address, peripheral hardware use and application requirements for any additional software.

4.1.8 SC Other Documentation.

a. The contractor shall provide a complete Technical Data Package (TDP) for the entire SC system including but not limited to the following Intellectual Property (IP): all hardware drawings, hardware schematics, software (to include all gateware and firmware) source code, software build environment including build scripts, Software Bill of Materials (SBOM), Application Programming Interfaces (APIs) and Interface Control Descriptions (ICDs). All IP shall identify the Government’s Data Rights to said IP and shall be accompanied by an appropriate rationale. The Government desires Government Purpose Rights (GPR) or Unlimited Rights, and the contractor shall submit a formal Data Rights Assertion List with their proposal to identify any components with Restricted/Limited rights.

b. The contractor shall provide technical information such as Bill of Materials (BOM) sufficient to assist the Government in addressing instances of critical safety concern; prevent Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues and aid in configuration management control throughout the contract period.

c. Operations and maintenance manuals in electronic format.

d. User’s manual, supplemental data and general engineering drawings.

e. Warranty documentation for all substantive components.

f. Mean Time Between Failures (MTBF): (e.g., > 2,000 operational hours) and Mean Time To Repair (MTTR): (e.g., < 2 hours for organizational-level field repairs) for all substantive components.

g. The contractor shall be responsible for affixing Item Unique Identification (IUID) labels to each required complete system in accordance with DFARS Clause at 252.211-7003, Item Unique Identification and Valuation and DFARS 211.274-2, Policy for Unique Identification.