NNC RFI Counter UAS_FP25 v2.docx

RFI C-sUAS

Request for Information Pursuant to FAR Part 15.201(e)

Technologies Sought for Capability Discovery Experiment

FALCON PEAK 2025.2

Hosted by North American Aerospace Defense Command and United States Northern Command (N&NC)

Counter – small Unmanned Aircraft System (C-sUAS)

Distribution Statement A: Approved for public release; distribution is unlimited.

SYNOPSIS: Counter – small Unmanned Aircraft System (C-sUAS)

A. INTRODUCTION

The purpose of this Request for Information (RFI) is to identify technologies from industry, government labs, and academia for a C-sUAS event to be conducted by North American Aerospace Defense Command (NORAD) and United States Northern Command (NC). Candidate systems should provide a kinetic Low Collateral Defeat (LCD) capability and/or be a rapidly deployable system that is able to detect, track, identify, and defeat Groups 1 and 2 sUAS using LCD mechanisms as defined by Joint Publication 3-30, Joint Air Operations, 25 July 2019, VR 17 Sept 2021.

N&NC are conducting a field capability experiment, FALCON PEAK 25.2 (FP25.2), to discover new technologies, enhance collaboration, and provide developers with immediate feedback to accelerate maturation of innovative capabilities with DoD-wide applicability that enable operations within the homeland. This C-sUAS experiment will focus on two efforts in a military installation scenario; rapidly-deployable systems, and systems that use LCD mechanisms to defeat Groups 1 and 2 sUAS threats. Capabilities and characteristics of selected systems will be showcased during FP25.2. The results will inform decision makers of emerging or available solutions that may enhance or enable operations.

FP25.2 will be conducted to inform stakeholders from across the DoD and will leverage Peterson Space Force Base/Colorado Springs Municipal Airport and Fort Carson’s Pinon Canyon Maneuver Site as the experimentation locations. This effort is sponsored by N&NC’s Force Protection / C-sUAS Division.

Established dates for FP25.2 are currently listed as 28 Jul through 8 Aug 2025.

To participate in FP25.2, interested parties, herein referred to as respondents, are invited to apply describing their C-sUAS capability.

The application deadline is 1700 MDT (2300Z) on 06 Feb 2025 with no extensions or exceptions to the deadline.

This RFI is NOT a solicitation for procurement or other acquisition proposals, proposal abstracts, or quotations. The Government does not intend to award a contract based on this RFI or otherwise pay for the information solicited.

B. BACKGROUND

Falcon Peak, sponsored by N&NC, is an ongoing series of annual C-sUAS technology discovery and showcase experiments that support first look at innovative technologies. The program supports joint forces and interagency users in exploring the military utility of innovative technologies and enables a collaborative working relationship between government organizations, academia, and industry. These discovery experiments encourage system developers to engage directly with the warfighter in the need to execute Force Protection measures and rapidly adapt technologies around operational needs. This informs and accelerates the delivery of future capabilities needed by the Department of Defense and U.S. interagency partners. The results of this effort will advance learning and innovation to develop technologies and techniques to improve warfighting capability and assist in quicker leadership decision making that enable operations within the homeland.

Participation and attendance at the N&NC FP25.2 are by invitation only. FP25.2 will take place at the unclassified level with an option to increase information distribution with command partners, pending appropriate clearance sharing procedures. Participating in N&NC C-sUAS events may lead to follow-on collaboration, support for further development, experimentation opportunities, and/or opportunities for fielding of matured capabilities.

C. DESCRIPTION

FP25.2 is planned from late July to early August at Peterson Space Force Base/Colorado Springs Municipal Airport located in Colorado Springs, CO and Fort Carson’s Pinon Canyon Maneuver Site located in Las Animas County, CO. FP25.2 will provide a venue for participants to demonstrate their technologies in an operational environment by allowing participants to operate their systems on a military installation to detect, track, identify, and defeat various Group 1 and 2 sUAS using LCD effects. N&NC will provide, operate, and deploy UXS platforms capable of addressing cross-domain and previously unseen threat profiles, including low-emission and no-emission (dark) UAS. FP25.2’s intent is to observe the readiness of commercially available systems, specifically those with a Technology Readiness Level (TRL) of 7, 8, and 9, employed as part of an overall effort to unify military base Force Protection measures falling under the purview of N&NC.

The following system capabilities are desired:

· Automatic detection of sUAS group 1 and group 2 categorized per Department of Defense Joint Publication 3-30 (Table 1). Detection of low-emission, non-emitting (dark), and 5G-cell enabled sUAS will be prioritized.

· Performance against multiple target aspects, course, speed, and altitude will be captured.

· Target signature thresholds shall be in accordance with the threat repositories maintained by the National Ground Intelligence Center, and National Air and Space Intelligence Center. Estimated signature threshold values available upon request to all industry partners who have access to SIPR or appropriate cage codes. POC for these requests is Jason Mayes at jason.d.mayes.civ@mail.smil.mil

· Ability to detect, track, and identify multiple heterogeneous sUAS threats.

· LCD systems must demonstrate effective neutralization (catastrophic defeat as defined by the recognizable system loss of control authority or the system’s immediate inability to maintain flight) of Group 1 and 2 sUAS threats under operational stress conditions for LCD-Capable Systems:

· LCD capabilities must prioritize precision mitigation with minimal collateral damage, environmental safety, and infrastructure protection.

· Utilize high-precision technologies such as directed energy, high powered microwaves, or modular kinetic effectors to neutralize threats.

· Rapidly Deployable (Fly Away) Systems:

· Systems must be transportable via C-130 aircraft.

· Systems shall minimize pallet requirements for transport.

· Modular design for transport on mil standard pallets (e.g., 463L) and air worthy containers.

· Capable of operational setup within 3 hours of deployment, achieving full functionality (including LCD capabilities) without additional personnel requirements.

· Systems shall be termed “operational” when all systems, including LCD effects, are functional.

· Operable continuously for 24-48 hours without resupply, with redeployment readiness within 1-hour post-mission.

· Real time processing and display of detection, track, and identification information via local or distributed command systems

· Sensors that are deployed/employed from a stationary site or structures, deployed in/on the ground or deployed/operated from a mobile platform such as a tethered balloon must be retrievable without alteration or damage to infrastructure and/or facilities.

· Sensors should maintain operational integrity in nearly all-weather conditions (-30°C to 50°C).

· Sensor data shall be capable of being reported to non-proprietary third-party Command and Control systems.

· Introduction of Advanced C-sUAS Capabilities:

· Detect, track, and identify at extended slant ranges and beyond limits outlined in the JROCM for Joint C-sUAS Capabilities.

· Support competitive engagement of targets with velocities ranging from 0 to 250 knots indicated airspeed (KIAS).

· Operate effectively from surface level to altitudes defined by the system's slant-range sensitivity limit.

· For LCD capabilities:

· Systems shall demonstrate a defeat capability on Groups 1 and 2 sUAS at 175 KIAS.

· Defeat is defined as the catastrophic defeat (recognizable system loss of control authority or the system’s immediate inability to maintain flight).

· Operate autonomously after issuance of launch command while employing C2 provisioned target state data as necessary.

· Data is required to be provided to NORTHCOM data collection team in a .CSV or .XLSX format (this is to expedite our analysis) is to include all tracking data in addition to system radar/EO/RF measurements (unfiltered, and track filtered as applicable) as well as applicable track covariance data.

· Time (Zulu) in thousandth of a second (3 decimal places) minimum

· Preferred minimum: data rate of 10 observations per second

· Decimal Degrees Latitude to 6 decimal places minimum

· Decimal Degrees Longitude to 6 decimal places minimum

· Elevation (meters)

· Earth-Centered Earth-Fixed (ECEF) X, Y, and Z positions (feet)

· For drones only

· Velocity X, Y, and Z (in ft/s)

· Acceleration X, Y, and Z (in ft/s2)

· Orientation X, Y, and Z in terms of yaw, pitch, and roll

· Command inputs if LCD drone is not autonomous

FP25.2 will assess system technology readiness using direct measurement, when possible. This will include, but is not limited to, detection ranges, times, false contacts/alarms, track management, identification, collateral footprint, “cost per shot,” and track data.

In addition to a quantitative assessment of detection and tracking capability, other important considerations that will be assessed qualitatively include:

· Installation and integration requirements

· Reliability, availability, and maintainability

· Tactical requirements

· Demonstrated ability to relocate and become operational.

N&NC will coordinate use of the test platforms and required integration for each selected technology. N&NC will assist in identifying and integrating additional components required for sensor testing and assist with access, coordination, engineering, installation, interface with regulatory bodies, operation, test, and evaluation services.

Respondents will be selected by the Government stakeholders for FP25.2 based on readiness and ability to meet the objectives. The Government may or may not enact a partnering arrangement with selected respondents in the form of a Cooperative Research and Development Agreement (CRADA), to enable continued collaboration on selected C-sUAS detect, track, identify, engage, and/or assess capabilities. FP25.2 is intended to foster highly collaborative engagement with interested technology developers, with the dual objectives of providing the DoD, civilian agencies, and the commercial marketplace new insight into promising C-sUAS detection technologies while enabling industry collaborators the opportunity to better understand the military installation Force Protection marketplace and evaluate their technology’s respective applicability.

FP25.2 is anticipated to last three weeks, with the first week being a set-up week. The intent is to execute one ten-day iteration, followed by a relocation to Peterson SFB for redeployment assessment and preparation for Distinguished Visitor Day participation. Each selected respondent (technology developer) will have multiple opportunities to showcase their capabilities. A series of standard profiles will be presented for the chosen technologies. N&NC will provide venues, supporting infrastructure, and personnel (operational and technical), based on available resources. Costs specific to operating the developer’s technology, as well as the technology developer’s travel costs, will be at the technology developer’s expense.

Industry participation in N&NC activities does not suggest or imply that the DoD or any other government activity will endorse, procure, or purchase equipment.

Respondents are encouraged to describe fully all C-sUAS system characteristics in their submissions, per Section D and Appendix I, to include all design considerations that may be relevant for integration and operations. All submissions will be considered and potentially selected based on strength of application and relevance to the FP25.2 goals.

Technologies beyond the scope of the primary topic areas described above will be considered on a case-by-case basis and potentially admitted based on strength of application and relevance to the mission area. Technologies brought to FP25.2 should be at a TRL of 7 or greater (https://api.army.mil/e2/c/downloads/404585.pdf). Respondents shall provide the current TRL of the proposed system.

D. SUBMISSION INSTRUCTIONS

Respondents shall submit applications electronically, to NORAD-USNC-FalconPeak@groups.mail.mil. Applications shall be no more than a three-page, single-spaced, Times New Roman 12 font, white paper description of your technology consistent with the template and information provided in Appendix I. Content beyond three pages will not be considered. Email NORAD-USNC-FalconPeak@groups.mail.mil if you have any questions.

When submitting your application, your email shall include the following information:

a. Email Subject: N&NC C-sUAS Capabilities Discovery.

b. Company name/business division/address:

c. Capability name:

d. Capability Type: Kinetic LCD / Rapidly Deployable / Both

e. Primary POC: name, email, and phone number

f. Alternate POC: name, email, and phone number

g. System description:

h. Application document per Appendix I

You will receive an email within two business days verifying your application was received. Any application not meeting the criteria outlined above will not be considered.

Each application shall address only one technology solution; multiple applications may be submitted. If you have questions regarding the submittal, please contact: NORAD-USNC-FalconPeak@groups.mail.mil.

DO NOT SUBMIT CLASSIFIED INFORMATION IN THE APPLICATION. This N&NC C-sUAS event, FP25.2, will be held at the unclassified level, with the understanding that some aspects of the event my require higher classifications. If the exchange of Secret-level information appears unavoidable, request separate correspondence with NORAD-USNC-FalconPeak@groups.mail.mil. Capabilities may be or contain Controlled Unclassified Information (CUI) and may be subject to International Traffic in Arms Regulations (ITAR) and/or Export Administration Regulations (EAR) restrictions. Respondents shall ensure that these restrictions are outlined in their application and adhered to during FP25.2.

DO NOT SUBMIT ACQUISITION PROPOSALS. N&NC C-sUAS technology applications shall be submitted no later than 17:00 MDT (23:00Z) February 06, 2025. Proposals received after the deadline will not be considered for FP25.2. No contracts will be awarded based solely on this announcement. Submission of an application does not guarantee an invitation to participate in the N&NC FP25.2 event or any other DoD event.

The Government is not committed financially, legally, or contractually by an invitation to present your technology. The costs incurred to make an in-person presentation are at the expense of the respondents. An invitation shall not be construed as the Government's desire to enter a contractual relationship with a respondent.

Your organization will be contacted no later than February 28, 2025, to notify you of your selection to participate in FP25.2.

E. BASIS FOR SELECTION TO PARTICIPATE

Submissions will be reviewed by the supporting government organizations.

Selection of respondents to participate will be based on the extent to which the technology represents a particular class or level of capability that can be provided to interested commands or interagency partners. Other considerations include:

a. Relevance to the FP25.2 focus areas and desired capabilities

b. Completeness of application and supporting information

c. Technical maturity

d. Readiness, or adaptability to support current and/or future intragovernmental (e.g. Departments, Agencies, Services, Combatant Commands) operations/missions

e. Demonstrated operational demand from a governmental entity (e.g., ongoing, or planned RDT&E, PROC, or O&M resourcing via Departments, Agencies, Services, Combatant Commands)

f. Ability to integrate associated measurement report (AMR) level sensor data into a Government owned common operating picture via the Athena C-sUAS Integration Kit

g. Ability to receive a fused air picture from the Athena C-sUAS Integration Kit and incorporate into its actionable air picture

F. ADDITIONAL INFORMATION

Respondents shall assure that all proprietary information, documentation, and equipment are clearly marked. Be advised that lessons learned from FP25.2 will be broadly disseminated through official channels within the Federal Government and partner government agencies associated with the N&NC C-sUAS program. If selected for participation, respondents may be requested to provide additional information that will be used in preparation for the event, such as graphics, video, and other material that may be needed to support audio visual production before, during, and after the event.

G. USE OF INFORMATION

The purpose of this notice is to gain information for potential future use and/or collaboration for development of technology capabilities. All proprietary information contained in the response shall be clearly marked. Any proprietary information contained in response to this request will be properly protected from any unauthorized disclosure. The Government will not use proprietary information submitted from any one firm to establish future capability requirements.

All non-DOD participants may speak factually about their participation in Falcon Peak 25. However, they may not imply any endorsement from the U.S. Government, Department of Defense, or NORAD and USNORTHCOM. The N&NC Public Affairs team will confer and consult with any participants prior to the publication of any press release that directly includes a written or visual reference to the name of their organization, employees, or technology. Respondents shall not use the name, logo, or images of any U.S. Government organization, employee, or contractor without prior approval from the relevant organization.

H. SPECIAL NOTICE

University affiliated research centers (UARCs), federally funded research and development centers (FFRDCs), and/or contractor consultant/advisors to the Government will review and provide support during evaluation of submittals. When appropriate, non-government advisors may be used to objectively review a particular functional area and provide comments and recommendations to the Government. All advisors will comply with procurement integrity laws and shall sign non-disclosure and rules of conduct/conflict of interest statements. The Government will take into consideration requirements for avoiding conflicts of interest and ensure advisors comply with safeguarding proprietary data. Submission in response to this RFI constitutes approval to release the submittal to government support contractors.

I. FEDERAL ACQUISITION REGULATION (FAR) 52.215-3

Per FAR 52.215-3 Request for Information or Solicitation for Planning Purposes (Oct 1997):

a. The Government does not intend to award a contract based on this RFI notice or to pay for the information.

b. Although "proposal" and "technology developer" are used in this RFI, your responses will be treated as information only. It shall not be used as a proposal.

c. In accordance with FAR Clause 15.209(c), the purpose of this RFI is to solicit technology candidates from R&D organizations, private industry, and academia for inclusion in future N&NC events.

Appendix I Application to Participate at N&NC Counter – small Unmanned Aircraft System Capability Discovery Experiment, FALCON PEAK 2025.2 Full name of Company & Name of Technology Insert Picture or Graphic of Technology

Technology Description

Please provide a description of your capability. The following information is recommended for the executive summary:

· Describe why the technology is needed and the problem you are solving.

· Describe the “so what” or what is new or advanced in your approach and why it will meet FP25.2 goals.

· Describe the maturity of your technology and if applicable what is needed to take your technology to the next level (e.g., R&D funding, procurement, etc.).

· Describe anticipated performance and any other pertinent details about your technology.

Primary POC: Provide name of person who will serve as Primary POC for this effort. This POC will be responsible for all deliverables and RFI(s) leading up to event.

Team: Include name, email, phone number, and complete address of key stakeholders / focal point and identify if any are foreign nationals. May include up 2 in addition to Primary POC. (Team is capped at 3 personnel unless appropriate justification for additional support is provided to the joint planning team).

Company / Organization:

· Provide full name, address, and other contact information for your organization. Include specific division if applicable.

· Provide brief company description, discussion of company capabilities with respect to the purpose and objective described in this RFI.

· Note if your company is designated as a “Small Business” and/or is “Foreign Owned”.

Objective/Scenarios: Describe objectives and goals. In addition, include a brief description of the scenario or mission that would best highlight your capabilities strengths.

Capability Technical Specifications/Description: Technical description should include, at a minimum, the following information:

· Describe the capabilities that you plan to highlight (detect, track, identify, relocate, kinetic LCD, etc.).

· Describe the sensor capabilities and specifications (i.e. resolution, field of view, etc.), as applicable. Identify transmitter frequency(ies) and source level(s).

· Describe how the planned capability differs from a fully realized implementation, e.g. will surrogate sensors, or a limited quantity of sensors, be utilized and why.

· Describe past performance, present and future uses – and predicted performance.

· Describe the design outcome of the capability and its intended value to the user.

· Describe the problem that you are solving (current / future) with your capability.

· Describe the capability application for the Department of Defense.

· Describe installation, integration, and operating requirements to include set up, tear down time.

· Describe the level of product maturity. Is it in the commercial marketplace or still under development? If under development, please describe status. Indicate Technical Readiness Level (TRL).

· Briefly describe structured testing conducted on the prototype or completed technology (i.e., whether prototype or completed technology was tested; and the test conductor, location(s), scenario(s), and environment). Has the technology been independently tested?

· Define the classification ontology, if applicable.

· Describe functionality available via an Application Programming Interface (API).

· Describe the outputs, input interface(s), and update rate.

· Detail the Ingress Protection (IP) rating for all system components.

· Detail the shock and vibration ratings for all system components.

· Include / Attach Specification Sheets and Interface Control Documents (ICDs).

· Include a basic system diagram including major components and interfaces (one-line diagram)

Capability Classification: Provide the classification level of the capability proposed for highlighting. (Unclassified, Confidential, Secret, Top Secret). Note: information for this event is expected to not exceed Secret, releasable to command partners.

Export Administration Regulations (EAR) and International Traffic in Arms Regulations (ITAR): Identify what (if any) parts of your capability have FAR and/or ITAR restrictions.

Set-up Requirements: Briefly describe, as appropriate, the details of the proposed capability set-up for FP25.2.

· Major System Component Dimensions and Weights:

· Power Requirement:

· Network Connections: (if needed)

· Data Requirement:

· Special Handling: (crane, forklift, etc.)

· Restrictions: (cable length, conditioned space, environmental constraints, etc.)

· Anticipated Number of Personnel for Event: (not to exceed 3 total personnel, unless approved by N&NC team)

· Set up time to install/uninstall.

· Hazardous Materials:

· Calibration requirements:

· On-site Storage:

Government Contracts (if applicable): Identify any government contracts and the supporting agencies that have or are expected to support the system and/or system components.