Buying a drone detection or counter-UAS system is not comparable to buying video surveillance. Technological maturity, regulation and sovereignty stakes call for a specific procurement process. Here is the method we apply across French and European projects.
Step 1 — Define the real need
Before looking at a product, formalise: geographic perimeter, expected drone profiles (cooperative or not), estimated event volume, physical constraints (façades, height, obstacles), operational constraints (24/7 or punctual, local team or remote monitoring), regulatory requirements (DPIA, sovereign cloud, critical infrastructure).
This need document is not three pages — it is ten clear lines you can send to a vendor.
Step 2 — Pick the right architecture
From the need statement, architecture emerges: single RF sensor (simple site), multi-sensor RF (large site), RF + radar (site exposed to non-cooperative drones), RF + radar + EO/IR under hypervision (critical infrastructure).
Avoid over-equipment. A frugal, well-maintained architecture beats a maximum yet poorly run one almost every time.
Step 3 — Frame the tender
Public buyers: include objective technical criteria (Remote ID standards supported, range, IP rating, ONVIF VMS integration) and sovereignty criteria (design, manufacturing, hosting location). Require a mandatory POC before award.
Private buyers: negotiate the POC upfront and a short-term rental option to limit initial risk.
Step 4 — Run a serious POC
A useful POC lasts 2 to 4 weeks with a written protocol: drones used (at least one C1, one C2 and ideally one non-Remote ID), scenarios (fast pass, hover, low flight, maximum distance), weather conditions, metrics (detection rate, latency, distance, false positives).
Leave the POC with a report and a clear decision: yes / no / yes under conditions.
Common mistakes
- Buying from a datasheet without a POC.
- Underestimating the software layer (UI, alerting, reporting).
- Forgetting training and maintenance.
- Picking a vendor with no local presence in France or Europe.
- Investing in effectors without a usable legal framework.
- Not connecting detection to a human operational process.
Recommended procurement model
Three models exist: outright purchase, long-term rental (LLD, 12 to 36 months, maintenance included), short-term rental (per day or per event). For a permanent deployment, the long-term rental is often the best financial and operational compromise; for an event or extended trial, short-term rental is unbeatable. DECTYR offers all three.
FAQ
What budget for an average site?
For an average civilian site (five hectares, mostly cooperative drones), expect a few thousand euros (excl. VAT) for an RF detector + annual Hub licence. Long-term rental smooths the cost.
Do I need an integrator?
Not strictly for a passive detector. For a critical-infrastructure multi-sensor architecture, yes: an experienced security integrator provides network coordination, VMS interfacing and maintenance.
Does GDPR impact procurement?
Yes. You must document the processing (DPIA if personal data is involved), inform employees and third parties, and limit retention to strictly necessary durations.