Tender
Counter-drone tender: how to write a specification and avoid buying too much
Counter-drone tenders often fail because of the specification, not the price. If it only states '5 km range', suppliers offer systems that cannot be compared. Here is a specification structure that makes bids comparable.
Contents
Structure of technical specificationsDiscovery RequirementsExposure requirementsIntegration and dataEvaluation criteriaCommon mistakesThe problem with most tenders is the lack of a threat model. The technical specifications write “UAV detection and suppression system”, but do not indicate the types of targets, altitudes, weather, zones and rules. As a result, the offers cannot be compared.
Structure of technical specifications
- Description of the object and zones.
- Threat model: drone types, altitudes, scenarios.
- Discovery requirements.
- Impact requirements.
- Integration and data exchange.
- Safety and electromagnetic compatibility.
- Training, service and warranty.
- Acceptance criteria.
Discovery Requirements
Indicate not one number, but a combination: probability of detection at a certain RCS, altitude and weather; number of false alarms per day; viewing sector; update time; identification range. Otherwise, the supplier will write a fancy number that cannot be verified.
Exposure requirements
For each weapon, include range, acceptable zones, reaction times, weather restrictions, and collateral damage. For RF jamming - ranges and electromagnetic compatibility. For a laser - safety class and zones. For interception - areas where debris falls.
Integration and data
The system must feed traces, video and log into the existing loop. Demand an open protocol or API, not “your own remote control”. This is important for operation and for future expansion.
Evaluation criteria
| Criterion | Weight | What to check |
|---|---|---|
| Technical Compliance | 30% | Full-scale tests, not advertising |
| Cost of ownership | 25% | Service, spare parts, training |
| Integration | 20% | API, protocols, compatibility |
| Experience and support | 15% | Objects, terms, service |
| Purchase price | 10% | Shouldn't be the only criterion |
Common mistakes
- Require a specific model instead of a function.
- Do not specify test conditions.
- Forget about training and regulations.
- Compare price only.
- Do not check electromagnetic compatibility.
