Q and A Drone Detection.xlsx
XLSX spreadsheet 20 KB Posted
- Attached to
- Counter-Unmanned Aircraft System Detection Services Federal contract opportunity
- Solicitation number
- FA7014-25-Q-0042
About this file
This file is a Questions and Answers (Q&A) document for a Counter-Unmanned Aircraft System (C-UAS) detection services solicitation (FA7014-25-Q-0042) issued by the Department of the Air Force Headquarters District Washington. The procurement is a small business set-aside for a cloud-based, contractor-owned subscription service to support Joint Base Andrews and Joint Base Anacostia-Bolling, requiring a turnkey solution for detecting and tracking Group 1-2 unmanned aerial systems within 3-5 km in urban and 10-15 km in rural environments with 95% accuracy.
Key technical requirements include real-time telemetry decoding, pilot/operator geolocation, mobile and web dashboard access, integration with ATAK and MEDUSA C2 systems, and compliance with FedRAMP High security standards. The solicitation specifies no on-premises hardware installation, 24/7 help desk support, and a 30-calendar day operational timeline post-award. The procurement will use a Lowest Price Technically Acceptable (LPTA) evaluation method with pass/fail technical criteria, and the proposal submission deadline has been extended to September 4, 2025, at 3:00 PM EST.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| PWS Drone Detection v 2.0.pdf | ||
| Solicitation Amendment FA701425Q00420002 SF 30.pdf | ||
| Solicitation Amendment FA701425Q00420001_Final.pdf | ||
| Draft DD Form 254 Drone Detection.pdf | ||
| Performance Work Statement Final.pdf | ||
| Solicitation - FA701425Q0042_Final.pdf | ||
| AFDW Drone Detection Combo Final_Signed.pdf | ||
| WD 2015 4281.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Questions | Answers |
| Can the Interested Vendor List on the announcement be made so that we can see the other interested vendors? | We will make the vendor list available on SAM.gov. |
| Can a Canadian company compete for this contract? Is an address in the US or partial US ownership required? | This requirement is a Small Business Set aside, which requires supplies or services to be performed in the United States or its outlying ares. |
| Is there an approximate budget for this project? This information would help us guide our deployment disposition (number of systems deployed for Geolocation and DF Location Finding). | The USAF has provided a Performance Work Statement, which allows each vendor to create their own solution along with the price. The attached Instructions to Offeror and Evaluation document explain that the award will be made to the lowest priced technically acceptable offeror. Provide real‑time telemetry decoding and pilot/operator geolocation. |
| Would the contractor be allowed to place a sensor on the installation if it does not require permanent install. The access to information will be ported via IL5/6 Microsoft Govt Cloud and not require further infostructure. Example would be a secure tripod or bracket mounted onto a tower; this is strictly a contractor owned sensor. IF so, will the contract be able to access power? | No installations will be allowed on the premises. RF coverage 400 MHz to 6 GHz (per RFQ requirement for geolocation/telemetry). No government‑furnished equipment; turnkey contractor‑owned/operated solution with no on‑prem hardware required, requested, or permitted for this contract. |
| Other than ATAK, are there identified C2 systems that would be required on day one? We currently port into ATAK and can port into other C2 but may require a services CLIN for future integrations. |
| System must be operational within 30 calendar days after award. ATAK and C2 integration (MEDUSA) capatibility must be operational within the first 90 calendar days after award. | |
| Does the government want raw data or pre-processed to a certain level by the contractor’s analyst? Or both. | The government requests the data be pre-processed by vendor analysts. |
| Will there be a security requirement (DD254) for the contractor to maintain; we recommend at minuet secret to Top Secret (Non safeguarding) due to the need for access to ATAK servers, which typically can host secret or higher? | Yes, there will be a need for a DD254. |
| What level help desk is required and is an FSR desired to provide on-site support? If so, is this FSR desired for temporary support or persistent presence on installation | As this is a SaaS contract, there should be no requirement for an FSR. However, 24/7 help desk support is required. |
| We offer enhancement of detection, including Open Source Intelligence as a Service; is this desired? If so, we can provide it as an optional service inside of the proposal. | The requirement is defined in the PWS. |
| Is there an incumbent performing this work today or is this a new requirement. | This is a new requirement. |
| If there is an incumbent performing this work today, please provide the incumbent contract number and name of the incumbent. | This is a new requirement. |
| Regarding the above-referenced RFQ, we note the requirement for “no on-premises hardware.” We realize this certainly requires any server hardware to be cloud-hosted. |
My question: Does it also mean that no sensors (such as passive radio frequency sensors) may be installed on-premises?
| No installations will be allowed on the premises. RF coverage 400 MHz to 6 GHz (per RFQ requirement for geolocation/telemetry). No government‑furnished equipment; turnkey contractor‑owned/operated solution with no on‑prem hardware required, requested, or permitted for this contract. | |
| Can the Government grant a 30-day extension to the proposal due date? | The due date will be extended to 4 September 2025, 3:00 PM EST (email submission) |
| How does the Government intend to transfer Title 10 130i authorities from the Government to the contractor? | The government will not transfer any authorities to the contractor, but will absorb data feed into existing CONOPs. |
| Would the Government consider awarding this as a best-value procurement instead of LPTA? | LPTA using FAR 12.602 and 13.106. Technical (pass/fail) on 5 criteria; Past Performance (≥2 relevant examples in last 3 years); Award to lowest‑priced technically acceptable vendor. |
| Given current supply chain challenges and long-lead procurement items, would the Government consider extending the initial system delivery date by 2–3 months? | See line 6 above. |
| What are the specific compliance standards for C-UAS detection at each location? | Detect and track Group 1–2 UAS within a range of 3–5 km in urban environments and 10–15 km in rural environments with ≥95% accuracy. Conduct Red Air testing annually. |
| Are there defined timeframes or deadlines for detecting and reporting unauthorized UAS activity? | Provide real‑time and immdeiate telemetry decoding and pilot/operator geolocation. |
| Are there any required data security certifications for the secure web and mobile dashboard? | See DD-254. Comply with FedRAMP High or DoD‑authorized equivalent; role‑based, encrypted access. |
| Can the Government provide more details on the expected frequency and method of telemetry data updates? | Provide real‑time telemetry decoding and pilot/operator geolocation. |
| To what extent can mobile technology be leveraged without requiring on-site hardware installation? | No government‑furnished equipment; turnkey contractor‑owned/operated solution with no on‑premises hardware required. |
| Does the Government have a preference for cloud service providers or specific architectures? | No, the requirement is a Cloud‑based, scalable platform with mobile access; zero‑maintenance contractor‑operated architecture. |
| What integration methods or technologies are preferred for connecting with Government C2 systems, and beyond ATAK, which additional C2 systems must be supported? | Compatible with ATAK; supports geofencing, alerting, and integration with AFDW C‑sUAS C2 (MEDUSA). |
| What are the criteria or benchmarks used to validate the ≥95% accuracy requirement for detection and tracking? | Detect and track Group 1–2 UAS within a range of 3–5 km in urban environments and 10–15 km in rural environments with ≥95% accuracy. Conduct Red Air testing annually. |
| Are there any restrictions or guidelines related to the use of third-party software or technologies in the solution? | See DD-254. Comply with FedRAMP High or DoD‑authorized equivalent; role‑based, encrypted access. Third-party software or technologies not permitted. |
| What specific passive RF technologies are expected to be utilized? | Subject to vendor capabilites, but should be able to conduct ≥95% detection in 3–5 km urban and 10–15 km rural environments (Class I/II UAS). |
| Are there specific requirements for user accessibility and authentication for the cloud-hosted system? | Cloud‑based, scalable platform with mobile access; zero‑maintenance contractor‑operated architecture. User access should be limited to user name, password, and two-factor authenitcation. |
| What documentation or validation steps are required to confirm that the system is fully operational within 30 calendar days? | Monthly Performance Reporting, see Service Summary in PWS. |
File details come from the government source that posted it. Updated .