Army RFI for “Counter-PNT”

by | Jul 8, 2024 | Blog

Image: Shutterstock

What’s New: The U.S. Army is asking industry about “… waveforms and techniques that limit the enemy’s ability to use PNT systems effectively.”

Why It’s Important:

  • America’s adversaries and potential adversaries have and are continuing to develop multiple means of navigation, some of which are much more difficult to disrupt that GPS and other GNSS. For example: China’s eLoran system is very high power, low frequency and is effective hundreds of miles to the east of Taiwan.
  • Drones and other un-crewed vehicles are becoming more important in warfare. Most rely on radio signals for navigation. Even FPV (fist person view) drones that are guided by an operator through an on-board TV camera rely on radio signals.
  • This RFI could be a sign that DOD is beginning to to take navigation warfare a bit more seriously… or not.

What Else to Know:

  • The RFI goes to great lengths to say that the Army isn’t going to buy anything any time soon. They just want to inform their Science and Technology investments.
  • One journalist reporting on the RFI said that counter-PNT includes the ability for US forces to operate when GPS and other GNSS signals are denied. We didn’t see that at all in the RFI but are trying to follow up with the Army.
  • For decades there has been a debate in the U.S. government, especially in DOD, as to where to pigeon hole counter-PNT. Is it electronic warfare or cyber? In this instance it is clearly EW. The answer is BOTH. That can be a problem for a large organization that has to pigeon hole things.

 

Counter-PNT (Position, Navigation, and Timing) NAVWAR DEFEAT

LINK TO SAM.GOV POSTING

Counter-PNT (Position, Navigation, and Timing) Request for Information (RFI)

Date: 28 June 2024

This RFI is for planning purposes only. This is NOT a request for quotations or proposals. Any information provided will be protected in accordance with the document markings. In accordance with Federal Acquisition Regulation (FAR) 15.201 (e), responses to this notice are not an offer and cannot be accepted by the USG to form a binding contract. Per FAR 52.215-3, Request for Information or Solicitation for Planning Purposes: (a) The USG does not intend to award a contract on the basis of this RFI or to otherwise pay for the information solicited. (b) Although “proposal” and “offeror” are used in this RFI, your response will be treated as information only. It shall not be used as a proposal. (c) This RFI is for planning and market research purposes only and should not be considered as a request for proposal or as a solicitation to do business with the USG.

Introduction

 

The Army Combat Capabilities Development Command (DEVCOM) Command, Control, Communications, Computers, Cyber, Intelligence, Surveillance and Reconnaissance (C5ISR) Center is currently planning Science and Technology (S&T) investments for navigation warfare (NAVWAR) techniques. The overall goal of this RFI is to identify capable technologies and enablers that will inform S&T investments in NAVWAR.

Background

 

The Army must compete against a complex threat environment that will be focused on degrading and denying their ability to effectively operate. The threats they face will be multi-domain, technologically advanced, automated, and highly capable in the modern battlefield. Our objective is to provide the maneuver force the ability to effectively counter these threats through NAVWAR Attack, in order to successfully complete their objectives. We will do this by developing waveforms and techniques that limit the enemy’s ability to use PNT systems effectively. In order to achieve this goal, we are looking to leverage work performed in adjacent technology areas and/or utilize pre-existing capabilities within the Counter PNT domain, while also pursuing promising ideas, in future mission-funded projects. The information gained in this RFI will inform the C5ISR Center of existing and upcoming technology, and it will help with the development of project plans.

 

Topics to include in the whitepaper:

  1. Relevant company background – Describe the company, expertise, experience, and past projects relevant to developing Counter-PNT.

 

  1. Capability description – Describe effects (what the technique does) and how it Please include any details about why the technique is novel, different, or unique, and explain any limitations of the capability. If not designed specifically for NAVWAR, please describe the original intended use of the technique/system (e.g., counter-radar, counter-communication) and how it can be applied to NAVWAR.

 

  1. Operational concept – Describe the scenario(s) and use cases where the capability will be employed. Specifically, what is the operational utility? Does the capability increase survivability or provide Suppression of Enemy Air Defense (SEAD), for example?

 

  1. Host platforms – If the system has been designed with a host platform in mind (e.g., UAS, dismount), please provide If the capability has known platform requirements, such as power or antenna configuration, please explain. A description of the hardware approach and system trade space (e.g., power vs range) would be useful.

 

  1. Configuration and tasking – If multiple, coordinated platforms are required, please explain how and why. If autonomy is leveraged or required, please explain how it is used and what is required. Are there any configurable aspects to the capability? If so, please describe the configuration options and process.

 

  1. Targets – Please provide a list of targets (e.g., UAS, commercial GPS receiver) and the expected effect (i.e., Deny, Deceive, Degrade, Disrupt, or Destroy) of the capability on each target.

 

  1. Maturity – Describe the level of maturity and current TRL of the For example, has the technology been field tested? Has the technology been demonstrated in modeling and simulation? What are the areas of technical risk (e.g., dependent upon quantum technology)?

 

  1. Future Vision – Describe any planned or potential advancements that can advance the capability in the future. Please include details regarding the funding status of future enhancements, including funding source (unfunded, IRAD, PM, Air Force, etc.) and any transition partners. Also include any timelines, risks, and dependencies.

Responses shall be in electronic format, either “.docx” or “.pdf”. White paper submissions shall be limited to fifteen pages in length. There is no page limit on supplemental information (i.e. Security Classification Guide (SCG), publications, laboratory test results). Please do not send previously written proposals or RFIs as supplemental information. They will not be accepted. Responses must be submitted within twenty-one days of the announcement. The Government will review the submitted responses and may schedule further discussions with responding vendors individually. All emailed questions, requests for clarification, and RFI responses shall contain the subject line: “Counter-PNT”.

 

  • Unclassified questions and responses must be submitted to: apg.devcom-c5isr.mbx.rti- [email protected].
  • Classified questions and responses up to SECRET shall be submitted via SIPRNet to: [email protected]. If you do not have access to SIPRNet, classified information will be accepted by mail; please mark it accordingly and send it via proper channels. Instructions for mailing classified information can be requested via unclassified email at usarmy.apg.devcom-c5isr.mbx.rti-industry-engagement@mail.smil.mil.
  • Classified questions and responses beyond SECRET, shall be submitted via If requested, please send a note to the unclassified address above to receive the appropriate submission address.

 

Responses submitted by contractors that contain U.S. classified military information (CMI) generated in conjunction with a DoD program should be classified in accordance with the applicable SCG. Please include a copy of the SCG with the submission. Responses submitted that contain information classified by a foreign government (i.e., Canadian SECRET), should be handled with the same security procedures as U.S. CMI. If the security classification of the foreign government document is shown in English, no other classification marking will be applied. If the classification is not shown in English, the equivalent

U.S. classification designation will be marked conspicuously on the document.