Evaluating a counter-UAS radar supplier is not just about comparing brochure range or checking whether the company calls itself a manufacturer. A reliable supplier should be able to explain product capability, test assumptions, site limitations, delivery process, compliance needs, and support responsibilities.
Counter-UAS radar is rarely a simple hardware purchase. It involves low-altitude target detection, track stability, false-alarm management, EO/IR cueing, platform integration, deployment, acceptance testing, and post-deployment tuning. Supplier quality shows up in whether the company can support those realities.
Look for Conditional Technical Answers
A reliable supplier will not end the technical conversation with “our radar detects up to this many kilometers.” It should explain what target, RCS or size, altitude, environment, probability, and false-alarm assumptions sit behind the number.
Ask:
- What target assumption supports the range claim?
- Are maximum detection range and stable tracking range separated?
- How does performance change in urban, port, industrial, mountain, or water environments?
- How do birds, vehicles, trees, water, and moving machinery affect false alarms?
- Can the radar cue EO/IR for confirmation?
- Can the supplier provide test records, demonstration data, or a site validation plan?
If every answer is simply “no problem” or “full coverage,” be cautious.
Check Site Survey Discipline
Counter-UAS radar performance depends strongly on site geometry. Buildings, tree lines, cranes, water, roads, mast height, power, network, grounding, and maintenance access all affect the final result.
A good supplier will ask about:
- site drawings and protected zones;
- candidate mounting points;
- nearby buildings and terrain;
- likely approach directions;
- power, network, and lightning protection;
- whether multiple radars are needed for blind spots;
- where operators will receive alarms.
If a supplier promises single-radar full coverage without understanding the site, the promise has weak engineering value.
Test Integration Capability
Counter-UAS radar is usually not an isolated device. It sends tracks to a platform and may cue EO/IR cameras, correlate with RF detection or Remote ID, trigger alarms, or connect to a third-party security system.
The supplier should explain:
- track output format;
- coordinate, height, speed, heading, and timestamp fields;
- API, SDK, or platform interfaces;
- camera cueing method;
- alarm zones and priorities;
- log replay and evidence export;
- loss-of-link, reconnect, and duplicate-alarm handling.
A supplier that sells hardware but cannot explain interfaces and workflow may leave integration risk with the customer.
Ask About FAT and SAT
Reliable suppliers separate factory acceptance and site acceptance. FAT can prove hardware completeness, power-up, interface output, simulated targets, platform integration, and documentation. SAT proves real site coverage, blind spots, clutter, representative targets, alarm workflow, and operator usability.
Ask for:
- FAT checklist;
- SAT recommendations;
- test inputs and pass criteria;
- version and configuration records;
- deviation handling;
- site tuning and retest plan.
If a supplier treats a demo video as acceptance or avoids site test conditions, the project may face disputes later.
Review Compliance Discipline
Counter-UAS radar projects may involve export control, radio licensing, spectrum management, end-user and end-use review, import permits, and local operating restrictions. A responsible supplier will not promise exportability before understanding destination, end user, and use.
Watch whether the supplier asks about:
- destination country or region;
- end user and end use;
- government, military, law-enforcement, or critical-infrastructure involvement;
- radio or spectrum license needs;
- resale, transshipment, or re-export;
- required compliance documents.
Any supplier that minimizes compliance or suggests hiding real information should be treated as high risk.
Make Support Specific
After delivery, radar projects may require tuning, training, maintenance, spare parts, software updates, and troubleshooting. Reliable suppliers define support clearly.
Confirm:
- who supports installation and commissioning;
- whether remote support is available;
- how response time is defined;
- warranty scope and exclusions;
- spare-part lead time;
- software update process;
- operator and maintenance training;
- post-event review or rule optimization support.
“Lifetime support” has limited value if it has no response path, responsibility boundary, or service process.
Common Warning Signs
Be cautious when a supplier:
- focuses only on maximum detection range;
- avoids test conditions;
- refuses technical or interface documentation;
- promises coverage without site review;
- blames every false alarm on user error;
- cannot separate detection, tracking, identification, and confirmation;
- avoids FAT/SAT discussion;
- ignores export compliance and end-user information;
- offers unusually low price for an unusually complete scope;
- promises aggressive delivery with no risk explanation;
- gives inconsistent answers between sales and technical staff.
One warning sign does not always disqualify a supplier, but several together should trigger a deeper review.
Conclusion
A reliable counter-UAS radar supplier does more than sell hardware. It helps the buyer connect mission, site, technology, integration, compliance, and acceptance. It explains limits, provides evidence, supports site survey, and remains involved after delivery.
The best buyer strategy is to ask specific questions: target assumptions, site constraints, interface methods, acceptance plan, compliance path, and support responsibility. Reliable suppliers treat these questions as the foundation of project success, not as obstacles to the sale.