CfWP Topic 0014 - Autonomous Hyperspectral Defenses_RFI_271000JUN2024.pdf

Solicitation: BAA-21-R-NCFT Call #: 0014 BAA Topic #: Autonomous Hyperspectral Defenses

FEDERAL AGENCY NAME: Army Contracting Command-Aberdeen Proving Ground (ACC-APG) on behalf of the Army Futures Command (AFC), Network Cross-Functional Team (Network-CFT)

BROAD AGENCY ANNOUNCEMENT NUMBER: BAA-21-R-NCFT

Originally published on beta SAM: 30 October 2020 Last Updated: N/A

CALL ANNOUNCEMENT NUMBER: 0014

CALL SCHEDULE: Dates: All dates are subject to change

Event Date BAA Released on beta.SAM.gov 30 Oct 2020 Call 0015:

White Paper (WP) Submission Opens 08 July 2024 WP Submission Closes 28 July 2024 Government begins notifying Vendors of WP evaluations: 30 Aug 2024

• Selected for Further Consideration (Invitation to participate in the no-cost technological demonstration)

• Not Selected for Further Consideration Technological Demonstration 09-13 Sept 2024 Government begins notifying Vendors of results of technological demonstration: 04 Oct 2024

• Selected for Further Consideration (Invitation to submit proposal)

• Not Selected for Further Consideration

Government begins accepting proposals from selected Vendors 15 Oct 2024 Government begins notifying Vendors selected for award (if any) 15 Nov 2024

*White papers received after the due date/time shall be governed by the provisions of FAR 52.215-1(c) (3).

BAA TYPE: This is a call for WPs only and will be governed by the two-step process described in General Information of the BAA-21-R-NCFT. Offerors that submit a proposal without first submitting a WP will not be eligible for award.

WP INSTRUCTIONS: Detailed instructions on format for WPs and the two-step submission process can be found in the overarching BAA.

TWO-STEP BAA, CALL ANNOUNCEMENT

BAA-21-R-NCFT, WHITE PAPER CALL #0014

Title: Autonomous Hyperspectral Defenses Date: 28 June 2024

Important Please assess the entire solicitation carefully prior to any response. The Network-CFT BAA utilizes a two-phase process to solicit offers and select a source for award.

• Phase One – Step One: Submission of White Papers *Step Two: Technological Demonstration (By Invitation Only)

• Phase Two – Submission of Proposals (By Invitation Only)

*Please note the Government reserves the right to skip step two of phase one and go directly to Phase Two after white paper evaluations.

WP SUBMISSION: All WPs shall be submitted via Joint Tactical Networking Center (JTNC) Joint Communications Marketplace (JCM) Technical Exchange Meeting (TEM) Industry Community, via https://jtnc.experience.crmforce.mil/TEMIndustry/s/. If there are any technical difficulties during your submissions, please email WPs to the TEM Support Mailbox, usarmy.apg.peo-c3t.mbx.pm-i2s-tem@army.mil Please use the subject line: Network-CFT BAA (i.e., Call for WP Number and Topic/Subtopic Number (example: Call for WP 0001, Subtopic #: N2104A).

TECHNOLOGY AREAS OF INTEREST:

Army Futures Command (AFC), Network-Cross Functional Team (N-CFT) and Program Executive Office for Intelligence, Electronic Warfare & Sensors (PEO IEW&S), Program Manager Electronic Warfare (PM EW&C) in support of Network Modernization priorities, Department of Defense (DoD) Electromagnetic Warfare (EW) Strategy, and the Army’s EW priorities, is issuing this call for WPs in association with BAA Topic Number 0014 - Autonomous Hyperspectral Defenses. To be eligible for consideration and possible contract award, the WP shall be of basic research, applied research, and/or that part of development not related to the development of a specific system or hardware procurement in the following “Technology Areas of Interest” specific to this call:

BAA TOPIC NUMBER: N2101 - AUTONOMOUS HYPERSPECTRAL DEFENSES

WHITE PAPER CALL # 0014

Operational Description of the Problem:

The Army has been shifting from a counter insurgency (COIN) operation focus, where they had spectrum advantage over adversary entities within their respective geographic locations. Commanders had the ability to broadcast continuously and utilize the spectrum when they needed situational awareness within their area of operations (AO). Focusing on large scale combat operations (LSCO) and multidomain operations (MDO) based on current activities in the European Theater, the Army has come to understand the use of the electromagnetic spectrum (EMS) will be used against friendly forces. To enable Commanders to move from conducting COIN operations to LSCO and MDO operations, they need to:

• Understand how organic radio frequency devices, power generating capabilities, natural and man-made environmental phenomenon, and adversarial effects will affect how their unit operates in the EMS in near-real time operations.

• See themselves, in near-real time, within the EMS to provide units the ability to conduct emissions control (EMCON), electromagnetic protection (EP), defensive electromagnetic attack (DEA), and enhance survivability during any phase of operations.

• Manage how units operate and/or maneuver within the EMS to provide ability to optimize, scale, and prioritize their usage of the EMS while conducting operations within the unit’s AO.

While the Army is conducting command and control (C2) on the move, spectrum awareness will be key to survivability in a contested and congested electromagnetic operation environment (EMOE). The Army needs networked and remote sensors to provide data to a central repository that can be assessed and dynamically visualized on a software program (e.g. Electronic Warfare Planning Management Tool (EWPMT)). The spectrum managers (25E MOS), electromagnetic warfare (EW) (17 series MOS) can use this visualization of the EMS to inform Commanders how they currently appear within the EMS. The program of record (PoR) to give Commanders a tool to view their own spectrum footprint is the Spectrum https://jtnc.experience.crmforce.mil/TEMIndustry/s/ mailto:usarmy.apg.peo-c3t.mbx.pm-i2s-tem@army.mil mailto:usarmy.apg.peo-c3t.mbx.pm-i2s-tem@army.mil

Situational Awareness System (S2AS), is currently a FY25 start (under Product Manger Electronic Warfare Integration (PdM-EWI)). In addition to knowing what formations look like within the EMS, Commanders need a networked sensor architecture using a common data format that can be consumed by and with other mission command systems. Additionally, they must be able to have the ability to employ countermeasures (e.g. counter-unmanned arial systems (C-UAS), DEA) to protect their formation against adversarial actions.

Use Case 1: A joint task force (JTF) division is deploying to an unnamed area of operations (AO) in support of contingent actions with joint and multinational partners in a combatant command (COCOM) area of responsibility (AOR). During movement operations, the division was having intermittent communication between subordinate units because of the heavily congested and contested EMS. Based on the tempo of the events and location of data-generating sensors, Spectrum Managers and EW personnel were unable to make timely assessments of the electromagnetic operational environment (EMOE) to inform the Commander what was contributing to the interference of subordinate unit communications.

Use Case 2: The division cyberspace electromagnetic activity (CEMA) cell is establishing the area of interest for S2AS monitoring the EMS within the unit’s AO, to include all subordinate, attached, and tactical controlled (TACON) units. Additionally, other operational controlled (OPCON) units are setting up DEA capabilities within the area of AO. The Commander asks the CEMA cell to provide a daily update on how the unit is propagating within the EMS and is directed to be the centralized cell to manage and control (when necessary) DEA systems that other subordinate units have emplaced. The CEMA cell needs EWPMT to add additional databases with hyperspectral imagery, accurate path-loss impacts from foliage/man-made objects, and more in-depth weather data to simulate and model the division’s spectrum footprint during planning or during employment of effects to achieve their maximum effectives.

Technical Description of the Problem:

• Reducing the cognitive burden of Spectrum Managers and EW professionals of distinguishing and identifying signal characteristics of multiple simultaneous signals in a complex EMS.

• Curating relevant data to the user based on need for situational awareness of the EMOE.

• Obtaining and connecting to authoritative databases to inform the Electronic Order of Battle

(EOB).

• Structured, flexible, and rapid sensor-to-management-to-effects architecture.

• Common and structured data that can be ingested by mission command systems.

• Integration within a mission partner environment (MPE) that will have varying levels of releasable data.

Required Capabilities:

• Platform mounted (e.g., ground, arial) low profile sensor(s) with cognitive capability to autonomously process, assess, and define entities (foreign to friendly) operating within a unit's EMS footprint through S2AS and EWPMT. [Use Case 1]

• System-agnostic algorithms to identify, classify, and baseline various electromagnetic signals autonomously from many sources in near real-time. [Use Case 1]

• Integration of data from authoritative databases (additional databases will be determined after selection) to inform and enhance RF modeling and simulation results, to include the following, but not limited to:

o Weather effects – predictive weather outlook based on near-real time data (Atmospheric conditions – humidity, cloud types and amounts, wind speeds and directions, and precipitation types and amount) o Foliage – tree and vegetation geometry and density (branches and leaves) o Man-made objects – object(s) density, material(s), composition, and geometry

• Agnostic algorithms to model and simulate the impacts of terrain, foliage, manmade objects, RF spectrum, and weather on friendly communications in near real time. [Use Case 2]

• Provide integrated sensor data into visualization tool (EWPMT) for spectrum awareness, including calculated environmental metrics (e.g., terrain, weather, man-made objects), with the ability to extend the ability to plan countermeasures and EA effects to deny or destroy foreign emissions within a specified or predetermined distance. [Use Case 1 &2]

• Integrate into legacy sensors, commercial-off-the-shelf (COTS), government-off-the-shelf (GOTS), DEA capabilities, and publish consumable data to other mission command systems.

[Use Case 1 &2]

Technical Constraints/Dependencies:

1. Spectrum requests are needed for transmitting devices used for outside demonstrations, testing, and STPs. Requests need to be submitted NLT local frequency request policy or procedure.

2. Machine Learning models of radio frequency (RF) signals will be trained and developed in the PEO IEWS Project Linchpin development pipeline.

3. Capabilities that are identified to eventually be integrated with a PoR will need to adhere cybersecurity requirements and integration requirements for those specific programs

Enclosures (References):

• AR 525-24, Army Cyberspace and Electromagnetic Warfare Operations, July 2023

• FM 3-12, Cyberspace Operations and Electromagnetic Warfare, August 2021

• ATP 3-12.3, Electromagnetic Warfare Techniques, January 2023

• S2AS A-CDD, April 2023

** The vendor shall identify any current ongoing same/similar efforts associated with the proposed white paper solution/technology area. The vendor shall provide the contract/agreement number and a brief description of the effort.

WP QUESTIONS/ANSWERS: Government will publish WP Q&As in the JCM TEM Industry Community applicable Topic Collaboration Group area. Instructions for the Q&A session shall be posted to the JCM TEM Industry Community (https://jtnc.experience.crmforce.mil/TEMIndustry/s/) when the call is issued.

WP PREPARATION, SUBMISSION, AND REVIEW PROCESS: Instructions for submissions of WPs, including response content and format, are covered in Section B of the baseline BAA, BAA-21-R- NCFT. The submitted white paper should not exceed eight (8) pages.

TECHNOLOGY READINESS LEVEL (TRL): For all the subtopic areas listed above, the maturity of the proposed technology should be at a TRL 6 or higher (please see enclosed TRL definitions). If the proposed technology is not TRL 6 or higher at the onset of the prototype project, the vendor shall include a detailed analysis of how the technology will be TRL 6 at the end of the prototyping effort.

https://jtnc.experience.crmforce.mil/TEMIndustry/s/

WP EVALUATION CRITERIA:

The Government will evaluate WPs to determine which have the potential to best meet the Network- CFT’s needs utilizing a two-part evaluation criterion as follows:

• Part One (1): WPs will be evaluated using “Go” or “No-Go” gate criteria listed below.

The “Go” or “No-Go” requirements are listed below which will determine if the WP receives further consideration. If during the evaluation one of the “Go” or “No-Go” requirements is not met, that evaluation will automatically receive a “No-Go” determination and will not receive further consideration.

o Cost. The Government will review the Offeror’s Rough Order of Magnitude (ROM) cost estimate for compliance with the BAA. ROM must be broken out by Base and Option, to include applicable cost elements.

o TRL. The Government will review the Offeror’s TRL to ensure it meets requirements as detailed in the Call for WP. Offeror must meet at a minimum TRL 6 at delivery.

o Schedule. The Government will review the Offeror’s proposed schedule to ensure the Offeror meets the period of performance when the Government specifies a Not-to-Exceed schedule. The Not-to-Exceed schedule for this effort is 24-Months (one 12-month base period, which means vendors can deliver their prototype before 12-months, and one 12-month option period). If either the base or option period proposed exceeds 12-months, the white paper will be considered “No-Go” and not receive further consideration.

o Compliance with all white paper submission requirements outlined in BAA-21-

R-NCFT.

• Part Two (2): WP will be evaluated using the following factors, which are listed in descending order of importance:

o Importance to Agency Programs (Relevance/Potential for Impact). The Government will review the Offeror’s description of the technology proposed on how it solves the capability/gap/problem presented, the relevance to the Highly Desired/Desired Capabilities, scalability of the solution, and assess its worth in relation to the stated “Technology Areas of Interest.” WPs will be scored as highly likely, likely, or marginally likely to address the stated operational and technical descriptions of the problem.

o Technical Merit/Challenge (Innovative or Revolutionary Technology (Scientific & Engineering Viability)). The Government will review the Offeror’s technology proposed to satisfy the technical challenges and design objectives by reviewing the Offeror’s enabling technology (innovative or revolutionary approach); feasibility;

technical risk and mitigation plan; alternatives (other technical data/information conveyed); technology maturation (the ability to achieve technology maturity); and time to field solution. WPs will be scored as fully or partially meeting or exceeding the stated Highly Desired and Desired capabilities.

o Schedule. The Offeror’s schedule will be evaluated based on the reasonableness of the allocation of time to meet major activities/milestones, deliverable, metrics measures of success, potential risks, and mitigation plans. WPs will be scored as having a preferable, acceptable, or questionable schedule for delivery.

TECHNOLOGICAL DEMONSTRATION EVALUATION CRITERIA:

Note: The process outlined below is subject to change.

“Technology demonstration” entails a prototype sample presented by an Offeror to showcase the proposed characteristics of the offered product described in the whitepaper as well as expand on aspects of the product that cannot adequately be described by specifications, purchase descriptions, or white paper (e.g. ease of use, quality of user experience, etc.). Demonstrations of capabilities not yet ready for a practical demonstration may be provided by an in-person paper or slide show presentation. This demonstration is also an opportunity to clarify and expand upon concepts not fully explored in the white paper and to field Government questions about the proposed prototype solution.

The Contractor must present the technology demonstration during the time specified in the Invitation to Demo. Individual time slots will be allotted to the Contractors selected to attend. If the Contractor fails to present the technology demonstration on time the Government will reject the invitation to continue through the selection process

1. Unless otherwise specified in the solicitation, technology demonstration shall be:

(1) Presented at no expense to the Government.

(2) Operated and maintained by the Contractor during technology demonstration evaluation.

2. The Government will not be liable for any damages to technology demonstration during evaluation or shipping.

Rules & Expectations

The Contractor’s technology demonstration will be observed during a 45-minute session. Time slots will be provided to afford Contractors time to prepare for the demonstration at the venue.

The technology demonstration evaluation will consist of the following:

Activity Time Allotted Setup/Tear Down: Up to 5 min Technology demonstration Fixes: 10 min if needed Presentation: 45 minutes Total Technology demonstration Time:

45-60 Minutes

The Government will allow the Contractor to prepare their equipment in a classroom prior to beginning of the event. It is recommended not to show up more than 60 minutes prior to demonstration time to prevent crowding of the classroom.

The Government will allow each Contractor up to 5 minutes to move their equipment from the classroom to the demonstration area which is approximately 30 feet from the classroom door.

The Government will allow each Contractor up to 10 minutes to fix any problems encountered between the classroom and demonstration area. After 10 minutes has elapsed, the timer will start for the 45-minute formal evaluation.

The Government will provide the Contractors a space to deliver their technology demonstration. This area will consist of a table, podium, and a projector with screen. The Contractors should expect 3-4 Government leaders presiding over the demonstration event with supporting technical evaluators seated behind. Contractors invited to attend the event will only be allowed in the demonstration area during their allocated time until the day has concluded.

Please note, the Government reserves the right to eliminate the technical demonstration and go directly to a Request for Proposal OR hold the technical demonstration virtually.

EXPECTED NUMBER OF AWARDS: The Government reserves the right to award as many (or as few) contracts as it deems appropriate. There are no set percentages of funding allocated to each investment category.

AWARD INFORMATION: The Army may elect to award a base period with an option period as follows:

• Base Period: Design and Build a Prototype (Up to 12 Months)

(a) The Offeror shall deliver the prototype(s) necessary to prove their technology proposed.

o A Safety Assessment Report (SAR) shall be delivered with the prototype.

Before the completion of the base period, the Government will assess the technology proposed, looking at the broad areas of technical performance and suitability for experimentation with Army units. Based on this assessment, the Government may decide to exercise the option period. Additionally, the government will require specific artifacts as deliverables, which include but not limited to the following items:

- Software design documentation.

- Interface design documentation.

- Interface control documentation.

- Overall test plan.

- Data flow diagrams.

• Option Period: Follow-On Training and Experimentation (Up to 12 Months)

(a) If the Option period is exercised, the Contractor will take the Government feedback from the phase 1 training event and further refine the software prototype functionality in preparation for a Soldier Touch Point (STP) event(s).

(b) The Contractor shall provide follow-on training and experimentation for the improved of finalized prototype solution at a STP event(s). The Contractor shall propose the number of days required to train personnel on their proposed solution.

(c) The Contractor should also be prepared to deliver user and training manuals, as well as technical support necessary to demonstrate the prototype.

(d) Technical support necessary to make repairs and replace parts as required to keep the proposed technology operational throughout this phase.

The Rough-Order-of-Magnitude (ROM) shall be broken out by base and option period, as the Government may only fund the base period and not the option period.

NON-GOVERNMENT ADVISORS: Offerors are advised that employees of the firms identified below may serve as Non-Government advisors in the evaluation/source selection process. These individuals will be authorized access only to those portions of the proposal data and discussions that are necessary to enable them to perform their respective duties. The Non-Government advisors will not have access to the non- sanitized cost/price volumes of the proposals. Such firms are expressly prohibited from competing on the subject acquisition:

SMART Engineering Consultants 427 Bostonian Way Havre de Grace, MD 21078

In accomplishing their duties related to the evaluation process, the aforementioned firms may require access to proprietary information contained in the Offerors proposals. Therefore, pursuant to FAR 9.505- 4, these firms must execute an agreement with each Offeror that states that they will (1) protect the Offerors information and (2) refrain from using the information for any purpose other than that for which it was furnished. To expedite the evaluation process, each offeror must contact the above companies to effect execution of such an agreement prior to submissions of proposals. Each offeror shall submit copies of the agreement with their proposal.

The companies identified above are prohibited from submitting proposals either as a prime contractor or as subcontractors at any tier or partner and from entering into contractual arrangements as subcontractors at any tier or as consultants or partners in response to this call for white paper.

ANTICIPATED FUNDING: The Government reserves the right to select all, part, or none of the WPs received, subject to the availability of funds. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

ANTICIPATED TYPE OF CONTRACTS/INSTRUMENTS: The Government reserves the right to award the instrument best suited to the nature of research proposed.

PERIOD OF PERFORMANCE: The contract(s) will have one (1) base period and one (1) option period, each of which will be up to 12 Months. The option period is not guaranteed and is subject to funding availability.

CALL AMENDMENTS: Offerors should monitor the beta SAM site, via https://beta.sam.gov/, and Joint Tactical Networking Center (JTNC) Joint Communications Marketplace (JCM) Technical Exchange Meeting (TEM) Industry Community, via https://jtnc.experience.crmforce.mil/TEMIndustry/s/, for additional notices to this Call that may permit extensions of the WP submission date or otherwise modify this announcement.

APPLICABILITY OF BASELINE BAA: All requirements of BAA-21-R-NCFT apply. For complete information regarding BAA-21-R-NCFT, refer to the BAA announcement as posted on beta SAM. It contains information applicable to all calls issued under the BAA and provide information on the overall program, proposal preparation and submission requirements, proposal review and evaluation criteria, award administration, agency contacts, etc. If there is conflicting information, this call for white paper and instructions contained herein takes precedent over the BAA.

http://www.fbo.gov/ https://jtnc.experience.crmforce.mil/TEMIndustry/s/

Rules & Expectations