Drone Technical Questionnaires.xlsx
XLSX spreadsheet 12 KB Posted
- Solicitation number
- 19AQMM26R0289
About this file
This file is a technical questionnaire template in Excel format designed to collect detailed information from potential contractors interested in responding to the Counter-Unmanned Aircraft Systems (C-UAS) Defensive Equipment Solution RFI/Sources Sought issued by the Department of State Office of Acquisition Management (Solicitation Number 19AQMM26R0289).
The questionnaire is structured to gather company profile information, including company name, address, point of contact details, CAGE Code, Unique Entity Identifier (UEI), business size, socioeconomic status, and applicable NAICS codes. The technical portion of the questionnaire requires respondents to address specific capability questions related to C-UAS systems, with emphasis on demonstrating how their solutions handle detection, tracking, identification, and controlled mitigation of Group 1 and Group 2 Unmanned Aircraft Systems (UAS) in complex, high-clutter operational environments. Respondents must also indicate whether they are currently performing similar work, whether capabilities can be obtained through existing Government contracts, and provide relevant contract numbers. The questionnaire serves as the primary mechanism for market research to assess the current market availability, technical maturity, and operational feasibility of comprehensive, multi-layered C-UAS defensive equipment solutions. Prospective contractors must be registered in the System for Award Management (SAM) database to be eligible for award of a Department of State contract.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| TECHNICAL QUESTIONNAIRE | ||
| Item | Requirement / Evaluation Question | Response |
| 1 | Threat Set Versatility: Provide the specific threat libraries and drone models your system has been tested against. Does your passive RF library detect custom, home-built, or modified DIY protocol variants? | |
| 2 | Autonomous / Dark Drone Detection: Explain how the system handles targets flying autonomously via pre-programmed waypoint navigation without active RF uplink/downlink emissions. Which secondary sensors (e.g., Radar, EO/IR) maintain track? | |
| 3 | Pilot vs. Drone Geolocation: Define the operational delta between detecting the aircraft and locating the Ground Control Station (GCS). What is the expected geolocation margin of error (CEP) under complex terrain conditions? | |
| 4 | Track Confirmation Metrics: What criteria constitutes a "confirmed track" vs. an unconfirmed signal anomaly? Specify the minimum time-on-target required for confident classification. | |
| 5 | Signal Discrimination: Detail the software algorithms used to automatically isolate UAS signatures from local environmental noise (e.g., biological clutter/birds, ground traffic, or high-density urban RF environments). | |
| 6 | Operational Testing Data: Provide summaries of verified test results or deployments in high-clutter urban zones, dense maritime/coastal environments, or topographically challenging terrain. | |
| 7 | Siting & Keep-Out Parameters: Define the physical deployment constraints, required lines of sight, or mandatory structural elevation needed to prevent critical blind spots. | |
| 8 | RF Spectrum Impact: Define the exact physical radius and frequency spectrum impact during active electronic mitigation. How does the system prevent disruption to nearby authorized infrastructure or civil GPS/Wi-Fi? | |
| 9 | Surgical Interdiction: Does the architecture support protocol-specific cyber takeover or surgical jamming? Can the system isolate a malicious threat while whitelisting "friendly" UAS operating in the same airspace? | |
| 10 | Kinetic/Fail-Safe Outcome: What is the predictable post-mitigation behavior of the target drone (e.g., forced hover, controlled vertical land, automated return-to-home)? Detail how the system minimizes kinetic fallback hazards. | |
| 11 | Modular API Support: Is the Command and Control (C2) software completely hardware-agnostic? Detail your capabilities for integrating third-party sensors (e.g., upgrading to an external radar or EO/IR suite) via open APIs. | |
| 12 | Signature Library Update Cycle: Outline the process and frequency for pushing new firmware/protocol signature updates. Clarify if library updates are included in the base procurement or structured under a recurring SaaS fee. | |
| 13 | Swarm & Automation Capabilities: Detail the operator workload required during a multi-target or swarm engagement. Does the system utilize an AI-driven data fusion layer to autonomously prioritize targets into a ranked threat matrix? | |
| 14 | Logistical Footprint: For mobile or transportable configurations, specify the number of personnel required for setup/teardown, estimated time-to-ready, and mandatory calibration protocols upon site arrival. |
_x000D_&1#&"Calibri"&14&K000000 SBU - CONTRACTING AND ACQUISITIONS
File details come from the government source that posted it. Updated .