You are here

Subscription-Based, Real-Time UAS Detection, Tracking, and Identification


OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Human-Machine Interfaces


The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.


OBJECTIVE: Design and develop an affordable and scalable subscription-based, real-time UAS tracking information system to provide authorized DoD end users with tailorable data feeds (UAS identity, location, and altitude) to meet DoD security and operational needs.


DESCRIPTION: The United States (U.S.) Department of Defense (DoD) is responsible for ensuring the safety, security, and protection of DoD personnel, facilities, and assets from various threats or hazards, including certain UAS operating in the National Airspace System (NAS).  Given the increasing adoption of UAS for various legitimate purposes (recreation, commerce) and the potential for malicious actor use, DoD has a need to detect, track, and identify UAS operating in proximity to certain DoD facilities and assets in the U.S., pursuant to all applicable federal, state, and local laws and regulations.      In the U.S., outside of certain DoD facilities, UAS tracking, unlike tracking of manned aircraft, is nearly non-existent, which introduces new risks to the safety, security, and protection of DoD personnel, facilities, and assets.    As the Federal Aviation Administration (FAA) pushes out direction on how to integrate UAS into the NAS—including the remote identification of unmanned aircraft—there is an anticipated need for geographically scalable, filterable, and affordable commercial hardware and software solutions for UAS tracking, fusion, and data integration of existing and future DoD information systems. This approach would allow for widespread coverage and need-based service and cost levels to address DoD’s dynamic current and future needs.  Acceptable proposals may consider novel or efficient methods for detecting, tracking, and identifying UAS (compliant and/or non-compliant with applicable FAA rules and regulations); fusing, moving and storing data; and secure ways for providing data, in real-time, to authorized DoD entities with responsibility to ensure the safety, security, and protection of DoD personnel, facilities, and assets.  In particular, proposals shall address how data feeds will be tailored or filtered to only include data (UAS location, altitude, identity) associated with certain UAS operations in the NAS (e.g., UAS operating in proximity to DoD covered facilities and assets pursuant to section 130i, Title 10, U.S. Code).  Additionally, proposed solutions shall demonstrate compatibility with current and future FAA remote identification standards and rules, and the ability to integrate with existing and future DoD information systems.


PHASE I: This is a Direct to Phase 2 (D2P2) topic.  Phase 1 like proposals will not be evaluated and will be rejected as nonresponsive.   For this D2P2 topic, the Government expects that the small business would have accomplished the following in a Phase I-type effort via some other means (e.g. IRAD, or other funded work).  It must have developed a concept for a workable prototype or design to address at a minimum the basic capabilities of the stated objective above.  Proposal must show, as appropriate to the proposed effort, a demonstrated technical feasibility or nascent capability to meet the capabilities of the stated objective.  Proposal may provide example cases of this new capability on a specific application.  The documentation provided must substantiate that the proposer has developed a preliminary understanding of the technology to be applied in their Phase II proposal to meet the objectives of this topic.  Documentation should include all relevant information including, but not limited to: technical reports, test data, prototype designs/models, and performance goals/results.


PHASE II: Based on current performance and effectiveness data this effort would provide a new offering in industry to fill this warfighter need.  Proposals must define expected final performance data and evidence to support it.  The proposal must address design features in terms of at least:  i. Employment strategy for UAS sensors providing coverage in proximity to DoD equities located throughout the U.S. (pursuant to all applicable federal, state, and local laws and regulations);  ii. Hardware or software guardrails to ensure data feeds are tailored or filtered to only include authorized DoD user needs; iii. Scalability and affordability curves for notional adoption and subscriptions; iv. Sensor to Database and Database to User Security plans; v. User Data consumption technical approach; and vi. Open architecture approach to support adaptability and integration with other systems. vii. Integration with at least one DoD information system.


PHASE III DUAL USE APPLICATIONS: The Government has an interest in transition of the demonstrated concept to an operational capability in support of many MAJCOM and COCOMs across the DoD.



  1. FAA, “Concept of Operations v2.0”, 2. FAA,


KEYWORDS: UAS activity, Drone, Remote ID, RF, Signal Detection, Radar Detection, Data Fusion, Data Management, Cloud data,

US Flag An Official Website of the United States Government