<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Radar Procurement on Counter UAV Radar — Low-Altitude Surveillance Radar</title>
    <link>https://www.counteruavradar.com/en/categories/radar-procurement/</link>
    <description>Recent content in Radar Procurement on Counter UAV Radar — Low-Altitude Surveillance Radar</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0800</lastBuildDate>
    <atom:link href="https://www.counteruavradar.com/en/categories/radar-procurement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Factory Acceptance Testing for Drone Detection Radar</title>
      <link>https://www.counteruavradar.com/en/knowledge-base/factory-acceptance-testing-for-drone-detection-radar/</link>
      <pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/en/knowledge-base/factory-acceptance-testing-for-drone-detection-radar/</guid>
      <description>&lt;p&gt;Factory acceptance testing, or FAT, is the buyer&amp;rsquo;s opportunity to prove that a drone detection radar system is complete, configured, and behaving as expected before it leaves the manufacturer or integration facility. It is not a substitute for site acceptance testing, but it can remove many avoidable risks before equipment reaches the field.&lt;/p&gt;&#xA;&lt;p&gt;For counter-UAS projects, a good FAT should answer a disciplined question: is the delivered radar system ready to be shipped, installed, connected, and tested on site? It should not claim that the system has already proven real site coverage, because buildings, terrain, clutter, mounting height, weather, and local RF conditions only become real after installation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Communicate Radar Requirements to a Supplier</title>
      <link>https://www.counteruavradar.com/en/knowledge-base/how-to-communicate-radar-requirements-to-a-supplier/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/en/knowledge-base/how-to-communicate-radar-requirements-to-a-supplier/</guid>
      <description>&lt;p&gt;Communicating radar requirements to a supplier is not just a purchasing formality. The quality of the supplier&amp;rsquo;s proposal depends heavily on the quality of the requirement brief. If the buyer only asks for &amp;ldquo;a radar that detects drones at 5 km,&amp;rdquo; the supplier has to guess the target, site geometry, clutter, interfaces, alarm workflow, and acceptance conditions.&lt;/p&gt;&#xA;&lt;p&gt;A better brief gives the supplier enough context to propose an architecture, state assumptions, identify risks, and explain what can be proven. The goal is not to make the document longer. It is to make the engineering question clearer.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Can a 10 km Counter-UAS Radar Be Exported?</title>
      <link>https://www.counteruavradar.com/en/knowledge-base/can-10-km-counter-uas-radar-be-exported/</link>
      <pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/en/knowledge-base/can-10-km-counter-uas-radar-be-exported/</guid>
      <description>&lt;p&gt;Can a 10 km counter-UAS radar be exported? The short answer is: not from the range figure alone. It may be exportable, it may require an export license, or it may be prohibited under certain end-user, end-use, or destination conditions. The real answer depends on the specific product, technical parameters, destination, end user, end use, transaction route, and current export-control rules.&lt;/p&gt;&#xA;&lt;p&gt;This article is a high-level compliance overview, not legal advice. Specific projects should be reviewed by the exporter, compliance team, and qualified counsel where needed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Evaluate Counter-UAS Radar Suppliers</title>
      <link>https://www.counteruavradar.com/en/knowledge-base/how-to-evaluate-counter-uas-radar-suppliers/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/en/knowledge-base/how-to-evaluate-counter-uas-radar-suppliers/</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;&#xA;&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
