SOS WESSEX WRAITH Procurement Support DRAFT Attachment 1.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 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) is 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 adversary 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.

b. Maritime OTM

c. Equipped with Primary Telescoping Mast

d. Equipped with three (3) auxiliary mast posts

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

f. Equipped with Hemispheric Azimuth and Elevation (Az/El) Rotator System Capable of supporting greater than 100# of 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. Operate in all weather, terrain and environments (common deployed field conditions expected) with minimum Ingress Protection (IP) of IP64

k. Support remote command, control and communications (C3) over VPN WAN

l. Ability to perform omni-directional radio frequency (RF) direction finding (DF) and geolocation with an N:2 Commutative/Switched DF Head capable of operating from at minimum 160 MHz to 4000 MHz

m. Ability to perform omni-directional DF and geolocation with an N-Channel antenna array and SDR configuration

n. Ability to perform multi-channel, omni-directional and directional Electronic Support (ES), Electronic Attack (EA) and Cyber Operations

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

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

q. Ability to disseminate geo-referenced and time-stamped RF data as Cursor-on-Target (CoT)/Tactical Assault Kit (TAK) messages

r. Ability to operate from shore power, solar power with battery backup, or generator with requisite power conversion and conditioning

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

t. The system must 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

u. The system must have minimum of of four (4) steerable directional antennas that support receive (Rx) and transmit (Tx) from 160 MHz to 7200 MHz

v. The system must have a dedicated 802.11 WiFi Rx/Tx subsystem with at least eight (8) Rx/Tx channels matched with appropriate directional antennas

w. The system must have a dedicated 5G Frequency Region 1 (FR1) cellular subsystem with at least eight (8) Rx/Tx channels matched with appropriate direction antennas

x. The system must have a dedicated subsystem to receive and process Automated Information System (AIS) signals

y. The system must have a dedicated subsystem to receive and process Automatic Dependent Surveillance – Broadcast (ADS-B) signals

3.1 RA Product/Performance Requirements.

3.1.1 RA Physical Requirements.

a. Maximum System Weight of 500 lbs. (including attachments and accessories but excluding mast ballast weight) and be transportable by both military and commercial freight without requiring non-standard loading dock equipment/procedures.

b. System must be mobile on the deck of a ship (i.e., secured to and operating from a ship’s deck with 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 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 minimum 8-Channel Superheterodyne Software-Defined Radio (SDR) Transceiver capable of both Switched and N-Channel DF

d. Equipped with minimum 8-Channel Homodyne SDR Transceiver capable of both Switched and N-Channel DF

e. Equipped with minimum 8-Channel WiFi subsystem

f. Equipped with Inertial Navigation Sensor (INS) and Global Navigation Satellite System (GNSS) sensor

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

h. All Rx antenna inputs must have at minimum low pass filtering (LPF) to protect against harmonics and low noise amplification (LNA) of source signals

i. All Tx antenna outputs must have at minimum LPF to protect against harmonics

g. All Tx antenna outputs must have appropriate power amplification for the RF signals they are meant to emulate (e.g., Cellular, WiFi, other Commercial, military signals)

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

3.1.3 RA Attachments.

a. One (1) Omni-Directional Radio Frequency Direction Finding (RFDF) Head in Commutative/Switched DF Configuration on auxiliary mast post

b. One (1) Very Small Aperture Terminal (VSAT) System, supporting Ku-Band and Ka-Band SATCOM

c. Power generation, distribution, storage and conditioning equipment as required

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 not limited to K/Ku/Ka-Band VSAT SATCOM or OneWeb/Starlink SATCOM.

c. VPN must support OpenVPN and WireGuard architectures as well as Post-Quantum Cryptography (PQC) encryption algorithms.

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 will use J/F-12 certified radios and spectrum-dependent (S-D) equipment for all communications. It is anticipated the RA systems will primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

b. 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 will primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

c. Contractor will 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 will be required to satisfy worldwide spectrum operations. It is anticipated the RA systems will primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands that are valid in any host country.

d. Contractor will 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 will ensure equipment communications are protected, will 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. Contractor will aid the government in obtaining an Approval–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.

a. Contractor will 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).

b. Contractor will 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.

c. Contractor will provide all user guides and documentation to include a system overview, installation manuals and a list of all ports with protocols being used by the system, including specific explanations of port functions.

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

a. Contractor must deliver RA using software with continued security support. Software without continued security support, such as Windows 7, is unacceptable.

b. Contractor will provide copies of all software used with RA and associated licenses to install and operate the product(s). The contractor will 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. Contractor will 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. Provide technical information such as Bill of Materials (BOM) sufficient to assist the Government in addressing instances of critical safety concern; prevent DMSMS issues and aid in configuration management control throughout the contract period.

b. Operations and maintenance manuals in electronic format.

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

d. Warranty documentation for all components.

e. 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 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. System shall have no surface-based altitude limits and shall operate to full capacity on the top of mountains wherever the air temperature remains above 14 Degrees Fahrenheit.

3.1.10 RA Environmental.

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

b. The system shall operate at ambient temperatures from at least 14° F (-10° C) to at least 122° F (50° C).

c. The system shall have Ingress Protection (IP) rating of at least IP64.

3.1.11 RA Receiver/Exciter.

a. 8 Channels of Superheterodyne SDR capable of tuning to frequencies at least 2 MHz to 7200 MHz.

b. Superheterodyne SDR capable of 100 MHz/channel digital instantaneous bandwidth.

c. Superheterodyne SDR capable of independent/coherent N-channel Rx/Tx tuning.

d. 8 Channels of Homodyne SDR capable of tuning to frequencies at least 300 MHz to 3800 MHz.

e. Homodyne SDR capable of minimum 40 MHz/channel digital bandwidth.

f. Homodyne SDR capable of minimum 2x2 Multiple-Input, Multiple Output (MIMO).

g. Homodyne SDR capable of targeted multi-channel operations in the 2.4 GHz and 5.8 GHz Industrial, Scientific and Medical (ISM) Bands.

h. Homodyne SDR capable of receiving and transmitting AIS and ADS-B.

3.1.12 RA Safety.

a. EO/IR camera can be used to inspect for objects and personnel in danger from RF emissions from RA system directional antennas.

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 predicative weather conditions 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 and report to the Government within seven (7) calendar days

3.2 RA Sustainment Support.

3.2.1 RA Product Testing (CONUS East Coast)

a. 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 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 will 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. 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 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 will 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. 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 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 will 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. Contractor shall support classroom based instruction (CBI) training at a contractor-provided facility with (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. The training can last less than forty (40) hours at the request of the Government on a case-by-case basis.

c. 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. 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 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. 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 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. 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 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 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 performer shall also apply any security critical patches that have become recommended during that timeframe.

b. The performer shall provide a firmware and software update, that can be installed remotely by the performer 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) 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 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 must 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 performer shall also apply any security critical patches that have become recommended during that timeframe.

b. The performer 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) 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 period along with any other identified standard ODC items and/or consumables required for maintenance.

3.2.10 RA Warranty Repair Plan (Ship to Depot).

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

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

c. Performer 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. Performer 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 performer shall only attempt repair-in-place should it 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. Performer shall replace identified malfunctioning components currently under manufacturer’s original warranty at no additional material cost, only the cost of labor for removal and replacement of the warrantied part(s).

c. Performer 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 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. Performer 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 must be suitable for inclusion inside of the RA mission case (RAMC) along with the other RA electronics.

d. 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). The system shall have Ingress Protection (IP) rating of at least IP64.

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 Spares 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 Optional 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. Potential peripherals include but are not limited to:

a. High gain cellular antennas for cellular C3 with standard mount for Auxiliary mast

b. Starlink/Starshield system for SATCOM C3 with standard mount for Auxiliary mast

c. OneWeb system for SATCOM C3 with standard mount for Auxiliary mast

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

e. Radar with standard mount for Auxiliary mast

f. Acoustic sensor with standard mount for Auxiliary mast

g. Gimballed sniper rifle with standard mount for Auxiliary mast

h. Gimballed optical telescope with standard mount for Auxiliary mast

i. Radio telescope

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

k. Operator laptop

3.2.16 RA Optional Consumables.

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

a. Cellular service time

b. Starlink/Starshield system SATCOM service time

c. OneWeb system SATCOM service time

d. Subscription to Commercially-Available Information (CAI) source and Application Programming Interface (API) access

4.0 Shadowcat (SC) Requirements.

The Contractor shall deliver the Shadowcat (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 with Terrestrial Communications, e.g., Cellular

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

g. Support remote command, control and communications (C3) over VPN WAN

h. Ability to perform antenna array flexible (as dictated by host platform) omni-directional radio frequency (RF) direction finding (DF) and geolocation

i. Ability to perform antenna array flexible (as dictated by host platform) 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

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

m. Ability to operate from shore power, solar power with battery backup, or generator with requisite power conversion and conditioning

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

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

p. The system must 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 must have a dedicated 5G Frequency Region 1 (FR1) cellular subsystem with at least four (4) Rx/Tx channels matched with appropriate omni-direction antennas

r. The system must have a dedicated subsystem to receive and process Automated Information System (AIS) signals with a single omni-directional antenna

s. The system must 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. Maximum System Weight of 350 lbs. (including attachments and accessories) and be transportable by both military and commercial freight without requiring non-standard loading dock equipment/procedures.

b. System must 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.

b. Equipped with minimum 4-Channel Homodyne SDR Transceiver capable of N-Channel DF.

c. Equipped with minimum 4-Channel WiFi subsystem

d. Equipped with Inertial Navigation Sensor (INS), FOG and Global Navigation Satellite System (GNSS) Sensor

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

f. All Rx antenna inputs must have at minimum low pass filtering (LPF) to protect against harmonics and low noise amplification (LNA) of source signals

g. All Tx antenna outputs must have at minimum LPF to protect against harmonics

h. All Tx antenna outputs must have appropriate power amplification for the RF signals they are meant to emulate (e.g., 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.

b. Two (2) RFDF Heads in N-Channel Coherent DF 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.

c. Power generation, distribution, storage and conditioning equipment as required

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

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 will use J/F-12 certified radios and spectrum-dependent (S-D) equipment for all communications. It is anticipated the SC systems will primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

b. 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 will primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands.

c. Contractor will 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 will be required to satisfy worldwide spectrum operations. It is anticipated the SC systems will primarily use commercial 5G cellular and commercial SATCOM on licensed frequency bands that are valid in any host country.

d. Contractor will 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 will ensure equipment communications are protected, will 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. Contractor will aid the government in obtaining an Approval–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. Contractor will 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. Contractor will 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. Contractor will provide all user guides and documentation to include a system overview, installation manuals and a list of all ports with protocols being used by the system, including specific explanations of port functions.

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

a. Contractor must deliver SC using software with continued security support. Software without continued security support, such as Windows 7, is unacceptable.

b. Contractor will provide copies of all software used with SC and associated licenses to install and operate the product(s). The contractor will 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. Contractor will 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. Provide technical information such as Bill of Materials (BOM) sufficient to assist the Government in addressing instances of critical safety concern; prevent DMSMS issues and aid in configuration management control throughout the contract period.

b. Operations and maintenance manuals in electronic format.

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

d. Warranty documentation for all components.

e. 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 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.

4.1.9 SC 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 inner/outer mold line (IML/OML) of a ship and the IML/OML of an aircraft.

c. System shall be capable of airborne operation in an unpressurized fuselage up to 30,000 feet mean sea level (MSL).

4.1.10 SC Environmental.

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

b. The system shall operate at ambient temperatures from at least 14° F (-10° C) to 122° F (50° C).

c. The system shall have Ingress Protection (IP) rating of at least IP64.

4.1.11 SC Receiver/Exciter.

a. 8 Channels of Superheterodyne SDR capable of tuning to frequencies at least 2 MHz to 6000 MHz.

b. Superheterodyne SDR capable of 100 MHz/channel digital bandwidth.

c. 4 Channels of Homodyne SDR capable of tuning to frequencies at least 300 MHz to 3800 MHz.

d. Homodyne SDR capable of 40 MHz/channel digital bandwidth.

e. Homoedyne SDR capable of 4x4 MIMO.

f. Homodyne SDR capable of targeted multi-channel operations in the 2.4 GHz and 5.8 GHz Industrial, Scientific and Medical (ISM) Bands.

g. Homodyne SDR capable of receiving and transmitting AIS and ADS-B.

4.1.12 SC Safety.

a. Unintended Electromagnetic Interference (EMI) from the SC system shall be minimized.

b. SC systems shall support automatic thermal shutoff.

4.1.13 SC Shipping.

The contractor shall research and resolve, at no additional cost to the Government, shipping damages, losses, discrepancies or delays and report to the Government within seven calendar days

4.2 SC Sustainment Support.

4.2.1 SC Product Testing (CONUS East Coast)

a. 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 SC and complete necessary Concepts of Employment (CONEMPs) before fielding or deployment of the system. SC product testing shall include two (2) Field Service Representatives (FSRs) for two weeks 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 will 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.

4.2.2 SC Product Testing (CONUS West Coast)

a. 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 SC and complete necessary Concepts of Employment (CONEMPs) before fielding or deployment of the system. SC product testing shall include two (2) Field Service Representatives (FSRs) for two weeks 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 will 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.

4.2.3 SC Product Testing (OCONUS INDOPACOM)

a. 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 SC and complete necessary Concepts of Employment (CONEMPs) before fielding or deployment of the system. SC product testing shall include two (2) Field Service Representatives (FSRs) for two weeks 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 will 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.

4.2.4 SC Product Classroom Training.

a. Contractor shall support classroom based instruction (CBI) training at a contractor-provided facility with (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. The training can last less than forty (40) hours at the request of the Government on a case-by-case basis.

c. 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.

4.2.5 SC Product Field Training (CONUS East Coast).

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

b. SC product training shall include two (2) Field Service Representatives (FSRs) for two weeks 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.

4.2.6 SC Product Field Training (CONUS West Coast).

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

b. SC product training shall include two (2) Field Service Representatives (FSRs) for two weeks 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.

4.2.7 SC Product Field Training (OCONUS INDOPACOM).

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

b. SC product training shall include two (2) Field Service Representatives (FSRs) for two weeks 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.

4.2.8 SC 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 SC in the deployed conditions. 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 performer shall also apply any security critical patches that have become recommended during that timeframe.

b. The performer shall provide a firmware and software update, that can be installed remotely by the performer 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. SC Remote Maintenance Plan is to be provided in quarterly increments (i.e., three (3) calendar months) and assume a one (1) 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 period along with any other identified standard ODC items and/or consumables required for maintenance.

4.2.9 SC 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 SC in OCONUS deployed conditions. In certain instances, the Government may determine that in order to provide sufficient maintenance support to the SC product the work must 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 performer shall also apply any security critical patches that have become recommended during that timeframe.

b. The performer 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. SC Local Maintenance Plan is to be provided in quarterly increments (i.e., three (3) calendar months) and assume a one (1) 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 period along with any other identified standard ODC items and/or consumables required for maintenance.

4.2.10 SC Warranty Repair Plan (Ship to Depot).

a. Performer shall coordinate shipment and repair of SC systems that are not fully functioning in the field.

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

c. Performer shall replace identified malfunctioning components no longer covered under manufacturer’s original warranty.