International Radar Project Delivery: Direct Export vs. Local Integration vs. Local Assembly

Radar procurement is also a delivery-model decision.

For an international project, selecting the radar is only one part of the decision. The buyer must also decide: Who will integrate, install, commission, maintain and support the system locally?

For many projects, three delivery models are possible: Direct supply → Local integration → Local assembly/localization.

The right model depends on project scale and capability—not simply on purchase quantity.

Model Comparison

Facteur	Direct Export	Local Integration	Local Assembly
Initial complexity	Faible	Moyen	Haut
Local technical role	limitée	Significant	Significant
Manufacturer control	Haut	Shared	Process-dependent
Multi-sensor integration	Limited–Medium	Forte	Forte
Local field support	Requires partner	Forte	Forte
Best for pilot	Excellente	Bonne	Usually inefficient
Best for repeated projects	Bonne	Excellente	Potentially strong
QA complexity	Faible	Moyen	Haut
Localization value	Faible	Moyen	Haut

This gives buyers a better framework than asking only: “Can you export directly?”

For supplier scoring and bid normalization, see the surveillance radar quotation comparison guide.

Option 1 — Direct Export

Direct supply is usually appropriate when quantity is limited, installation is relatively simple and the customer has enough local engineering capability.

The radar manufacturer typically controls configuration, testing, software baseline and factory documentation. The local party may manage customs/import, tower, power, cabling and physical installation.

The main risk is an unclear boundary between equipment supply and site responsibility.

Option 2 — Local System Integration

This model becomes attractive when radar is part of a integrated perimeter protection solution. The local integrator may be responsible for towers, network, systèmes EO/IR, C2/VMS, installation and field service.

The radar manufacturer remains responsible for radar de surveillance, configuration, documentation, interface support and radar-specific testing.

This structure can work particularly well in Brazil and selected African markets where strong local EPC or security integrators already serve infrastructure customers.

The Most Important Tool: RACI

For international projects, responsibility should be documented early.

Task	Radar OEM	Local Integrator	EPC	End User
Radar configuration	R	C	I	I
Étude de site	C	R	C	C
Tower	C	C	R	I
Network	C	R	R	C
C2 integration	C	R	C	C
FAT	R	C	I	UN
Installation	C	R	R	I
SAT	C	R	C	UN
Formation	R/C	R	I	UN
Local support	C	R	I	UN

The exact matrix changes by project, but creating it early prevents later disputes.

Option 3 — Local Assembly

Local assembly can become relevant when a market has repeatable volume, local-content requirements, long-term service needs and suitable technical partners.

But local assembly should not be confused with simply attaching mechanical parts. Radar production may involve RF calibration, antenna alignment, software control, traceability, environmental sealing and acceptance testing.

If those processes are not controlled, localization can reduce product consistency instead of improving delivery.

A Safer Localization Roadmap

Rather than moving immediately to local production, a partnership can evolve through stages.

1. Stage 1 — Direct supply: validate product and market.
2. Stage 2 — Local installation/service: train local technicians.
3. Stage 3 — Local system integration: integrate radar with cameras, networks and C2.
4. Stage 4 — Selected local assembly: move approved processes locally after QA capability is established.
5. Stage 5 — Deeper cooperation: consider expanded production or technical cooperation only when commercially and technically justified.

This staged model reduces risk for both sides.

Use Stage Gates From Pilot to Scale

A delivery model should evolve only when the previous stage has produced evidence. After a pilot, the parties should review technical performance, installation effort, support workload, fault history, interface stability and commercial demand before moving to a broader integration or localization model. This creates a decision gate rather than an automatic promise that “the next order will be locally assembled.”

For a structured acceptance baseline, see the guide de test sur le terrain et d'acceptation.

For repeat deployments, the project should also freeze a reference configuration. If every site receives a different radar software version, interface mapping or cable design, the local-support burden can grow faster than the installed base.

Configuration and Change Control Matter More as Localization Deepens

Local integration and assembly introduce additional handoffs. The parties should define who controls the approved bill of materials, firmware/software baseline, calibration data, configuration files, serial-number traceability and engineering changes. A seemingly small local substitution—such as a connector, power supply or enclosure component—can affect environmental verification guide or maintainability.

A change-control process should therefore specify what the local partner may change independently, what requires manufacturer approval, and how the updated configuration is recorded for warranty and future service.

Where the delivery model also includes product customization, Midradar’s radar OEM/ODM delivery guide provides a complementary framework for configuration baselines, engineering changes and repeatable delivery.

Spare Parts, Training and Escalation Should Be Designed Before the First Failure

A credible international delivery model includes a service architecture. Define which spares are held locally, which faults can be diagnosed by L1 technicians, which require L2 remote engineering, and which require L3 factory intervention. Training should be linked to those support roles rather than delivered as a generic product presentation.

The contract or project plan should also define warranty return flow, software update responsibility, remote-access rules where permitted, and the expected technical-response path when the cause of a problem spans radar, network and third-party C2.

When Does Each Model Make Sense?

Example A — 2-unit pilot: Direct supply is usually the simplest.

Example B — 10-site industrial deployment: Local system integration becomes more valuable because installation, networking and support begin to dominate project complexity.

Example C — repeated 20–50 unit regional program: A deeper localization discussion may become commercially meaningful—if there is a qualified partner and stable demand.

Volume alone should not trigger local assembly.

Partner Qualification Should Be Evidence-Based

A local partner does not need to manufacture radar to be valuable, but it should be able to demonstrate the capabilities it claims. Depending on scope, useful evidence can include completed integration projects, trained engineers, network/C2 experience, field-service coverage, test equipment, spare-parts handling, documented installation procedures and an escalation path to the radar OEM.

A useful cross-check is the supplier due-diligence criteria guide.

For larger programs, buyers should also ask how the partner manages configuration records and serial-number traceability across sites. This becomes important when dozens of systems are deployed over multiple years.

What Buyers Should Evaluate in a Local Partner

A technically credible integration partner should be able to demonstrate capability in installation, networks, EO/IR, C2/VMS, onsite commissioning, field support and project management.

Government-project experience or large-infrastructure delivery capability can also matter depending on the target market.

Lifecycle Support Is Part of the Delivery Model

The buyer should define L1 local support → L2 technical support → L3 factory engineering.

The same should apply to spare parts, firmware/software, warranty, training and fault escalation.

A delivery model is incomplete if it only defines who installs the equipment.

Important Compliance Boundary

Import, local-content, certification and technology-transfer requirements vary by jurisdiction.

Any Brazil, South Africa, Morocco, Namibia or other country-specific version of this article should be checked against current local requirements before publication.

The generic article should explain decision architecture, not provide legal conclusions.

FAQ

Is local integration the same as local assembly?

No. Integration connects and deploys complete systems; assembly moves part of the production process into the destination market.

When should a project consider localization?

Usually when there is repeatable demand, a qualified partner and a long-term support requirement.

Does local assembly automatically reduce cost?

No. Training, QA, tooling, test equipment and management can add cost.