11:30 A counter-UAS supplier should be evaluated as a system-delivery partner, not only as a radar manufacturer. Buyers need evidence that the supplier can define the threat, design the sensor architecture, deliver stable track data, integrate C2 and EO/IR, support site deployment, agree measurable acceptance criteria and maintain the system after handover. Commercial comparison is meaningful only after every supplier has disclosed the same project scope, assumptions, exclusions and lifecycle responsibilities.
This guide is intentionally different from a radar procurement guide. It does not ask only which radar has the longest range. It asks whether the proposed system can produce a usable warning, visual confirmation, evidence and operational response within the buyer’s site, legal and infrastructure constraints.
How to Evaluate a Counter-UAS System Supplier: 12 Due-Diligence Criteria
Use the drone detection radar procurement guide to define requirements before supplier scoring.
This framework is for prequalification, shortlist and final due diligence of a Counter-UAS system supplier. It assumes the buyer has already defined, or is separately defining, the threat, site, legal boundary and RFI/RFP requirements. It does not replace the radar procurement guide, which should own requirement definition, sensor roles, field-test design and acceptance planning. Supplier evaluation begins only after proposals are normalized to the same mission and project scope. A supplier should fail the process if a mandatory safety, compliance, evidence or interface requirement is not met, even when its weighted commercial score is high.
The supplier should first translate the project into an operational concept. That means defining the target types, RCS assumptions, altitude and speed profiles, protected area, warning time, required confirmation, operator workflow, evidence retention and authorized response boundaries. A proposal that begins with a fixed equipment list before these questions are answered is likely to transfer design risk to the buyer.
Ask the supplier to show how a target moves through the workflow: first detection, track initiation, stable tracking, priority assignment, EO/IR acquisition, operator confirmation, alarm escalation, event recording and recovery after loss. The answer should identify both system behavior and responsibility boundaries.
Separate pass/fail gates from weighted scoring. Gates should cover legal eligibility, final-user and export review, mandatory performance evidence, required interfaces, cybersecurity minimums, acceptance-test commitment and disclosure of exclusions. Only suppliers that pass every mandatory gate should enter weighted scoring.
Weighted criteria can then compare mission fit, architecture, radar evidence, software maturity, integration discipline, deployment readiness, support, commercial completeness and delivery risk. The scoring sheet should cite evidence for every score and identify the reviewer. Avoid awarding points for brochure statements that have no approved specification, test record, interface document or contractual commitment. A structured clarification process is often more valuable than adding more scoring categories: record the question, supplier answer, evidence, deviation, owner and closure date.
Twelve-Criterion Supplier Due-Diligence Matrix
| Criterion | Evidence to Request | Decision Use |
| 1. Mission fit | Operational concept and responsibility matrix | Pass/fail gate |
| 2. Sensor architecture | Coverage drawing, sensor roles and failure analysis | Technical score |
| 3. Radar evidence | Approved model data and representative tests | Technical score |
| 4. C2 and software | Version, functions, logs, permissions and release record | Technical score |
| 5. Interfaces | ICD, sample messages, drivers and test plan | Pass/fail + risk |
| 6. Cybersecurity | Architecture, authentication, logging, patch and vulnerability policy | Pass/fail gate |
| 7. Deployment | Site survey, infrastructure and installation method | Delivery score |
| 8. FAT/SAT | Agreed cases, metrics, evidence and retest procedure | Pass/fail + contract |
| 9. Configuration control | Baseline, drawings, software records and change process | Quality score |
| 10. Lifecycle support | SLA, spares, updates, training and escalation | Support score |
| 11. Compliance | Destination, final user, spectrum and export review | Pass/fail gate |
| 12. Commercial completeness | Itemized scope, assumptions, exclusions and recurring costs | Commercial score |
A credible supplier explains why each sensor is included. Radar provides non-cooperative detection and track measurements. RF detection may identify emitters or protocols when signals are present. Remote ID can support cooperative identification where available. EO/IR provides visual confirmation and evidence. A C2 platform combines these inputs and manages the workflow.
No single sensor should be presented as universally sufficient. The correct mix depends on the threat, terrain, clutter, weather, legal restrictions, required warning time and operator capacity. The supplier should also explain blind zones, overlap, redundancy and the consequence of losing one sensor.
A system-level reference is available in Midradar’s solução integrada de contra-UAV.
Headline range is not enough. Require target-specific first-detection, track-initiation and stable-tracking performance with RCS, altitude, speed, aspect, environment, probability and test method stated. Ask for minimum range, coverage geometry, update interval, track capacity, accuracy, clutter behavior, installation limits and evidence.
Performance should be tied to the exact model and software version. If a brochure, catalogue and specification sheet disagree, the supplier should provide one approved master data source and a documented change-control process.
When a supplier claims low-probability-of-intercept performance, use the LPI radar evidence buyer guide to separate engineering evidence from marketing terminology.
How to Evaluate a Counter-UAS System Supplier: 12 Due-Diligence Criteria
System suppliers should be able to discuss track fields, coordinate systems, timestamps, health data, camera control, event logs, user permissions and failure behavior. They should not rely on the phrase “open API” without interface documentation, sample messages or a test plan.
Ask who owns coordinate conversion, time synchronization, device drivers, cybersecurity design, third-party software licensing and integration testing. A mature supplier will identify what is standard, what is configurable and what requires development. It will also specify how changes are versioned and accepted.
OEM or ODM capability is valuable only when it is controlled. Ask which items can be customized: branding, enclosure, mounting, power, environmental protection, interfaces, data fields, software UI, workflows, documentation and test plans. Then ask what remains fixed because of safety, compliance, performance or maintainability.
The supplier should use configuration baselines, drawings, interface documents, software-version records and approval gates. Uncontrolled customization can create an unmaintainable one-off system. The objective is repeatable project adaptation, not unlimited modification.
For a controlled customization workflow, review the radar OEM and ODM project guide.
A supplier demonstration can confirm basic function, but site-specific coverage, nuisance-alarm behavior and cueing performance require an agreed field method. Before contract award, define the test target, route, weather or equivalent conditions, system configuration, data to retain, pass/fail criteria and retest process.
Evidence should include approved specifications, drawings, interface documents, sample messages, factory test records, calibration records, event exports, installation procedures, training material and maintenance documentation. Where a claim cannot be supported, it should be conditional or removed.
Require itemized disclosure of sensors, cameras, servers, network equipment, masts, foundations, software licenses, integration, freight, installation, commissioning, training, spares, warranty, maintenance, updates and recurring charges. Assumptions, exclusions and buyer responsibilities must be visible.
A low equipment price can become an expensive project when integration, infrastructure or support is excluded. Compare evaluated project cost only after the technical scope is normalized. Also assess response time, spare-part availability, software-support period, local partner model and escalation path. After compliant proposals are received, compare surveillance radar quotations.
Detection, radio monitoring and active response functions may be regulated differently. The supplier should separate detection and evidence functions from any authorized response function and identify the required final-user checks, export review, spectrum approval, aviation coordination and local operating authorization.
A responsible supplier includes legal, technical and cybersecurity approval gates in the project plan rather than treating compliance as a disclaimer at the end of the proposal.
The best counter-UAS proposal is not the one with the most impressive headline specifications. It is the one that defines the operating outcome, assigns sensor roles, documents interfaces, proves performance under agreed conditions, controls customization, allocates responsibilities and remains supportable after handover.
For a project-specific review, request a technical and commercial compliance review. Provide the threat and site information, existing systems, required interfaces, procurement schedule, destination country and expected acceptance method. Midradar can then prepare a preliminary architecture, compliance matrix and clarification list.
No. Range must be evaluated with target, RCS, altitude, environment, probability, tracking behavior and test method. Integration, evidence and support are equally important.
No. Buyers should score controlled, documented and maintainable customization—not unlimited modification.
Before contract award, together with test targets, routes, system configuration, evidence format, pass/fail thresholds and retest procedure.
Request approved specifications, interface documents, configuration records, representative tests, FAT/SAT capability, support scope, exclusions and the responsible party for each subsystem.
Normalize equipment, software, licenses, integration, infrastructure, freight, installation, commissioning, training, spares, maintenance and recurring charges over the same project period.
Responderemos dentro de 24 horas. Se for um caso urgente, por favor adicione WhatsApp/WeChat: 86 86 13361376820,. Ou ligue directamente para 86 86 13361376820.
*Respeitamos a sua confidencialidade e protegemos todas as informações fornecidas.
Utilizaremos os seus dados exclusivamente para responder ao pedido e nunca enviaremos mensagens de correio eletrónico não solicitadas nem comunicações promocionais.
