Defense radar with AI — a T/R module out of spec is not an incident, it is a delayed program.
Building AESA radars demands three cross-checks that almost nobody has all at once: an SMT defect caught in line, calibration cross-referenced with the drawing and the MMIC batch, and signed ITAR/EAR traceability. iLEAN Edge sees the T/R module, Connect captures the supplier's certificate of conformance, and an agent prepares the program dossier. The certified person signs.
A radar does not fail because of one big defect — it fails because of a thousand small ones nobody cross-referenced.
A modern AESA radar is a mosaic of hundreds or thousands of T/R modules on subarrays, each one with its MMIC, its SMT circuitry and its individual calibration. Manufacturing combines three worlds that on the shop floor each live on their own island:
- The SMT defect — tombstoning, a BGA joint with voids, contamination of the ceramic substrate. Today they are caught by the classic AOI and the operator's eye. The AOI sees what is in its recipe; what is not there, it does not see. And short-run radar programs change recipe with every batch.
- RF calibration — the gain curve, the phase, the LNA noise figure. It is measured with dedicated equipment, saved in a spreadsheet and signed with the technician's initials. Cross-referencing it with the MMIC batch that came in that day is detective work.
- ITAR/EAR traceability — which MMIC came from which country, which authorized end customer receives it, which supplier certificate of conformance backs it up. The export audit rebuilds all of this by hand when the moment comes.
The program manager lives between the three worlds and, when a T/R module fails in integrated testing, has to go back and rebuild the chain part by part. It is not that the plant is bad — it is that cross-referencing those three realities by hand consumes an entire program.
iLEAN does not touch the AOI or the calibration equipment — it seals the crack between them and the ITAR dossier.
The problem in defense radar is not buying more equipment: it is that the AOI, the RF calibration equipment, the ERP, the supplier delivery note and the export manager's email do not talk to each other in real time. iLEAN acts as putty between the systems you already have, without asking you to change the Yamaha, the Anritsu or the program's ERP.
Edge sees the T/R module and flags what the AOI did not have in its recipe. Connect captures the MMIC certificate of conformance whether it comes by email, EDI or a photographed delivery note. The agent cross-references it with calibration and prepares the ITAR dossier — the certified person signs.
The three iLEAN pieces applied to an AESA radar:
- iLEAN Edge — a terminal with computer vision (CNN) over the SMT line and over the T/R module inspection bench. It detects tombstoning, BGAs with voids, badly positioned bond wires and substrate contamination. It flags the part for review by the IPC-certified operator. It works with no network: if the plant goes isolated (SCIF, military operational island), Edge keeps capturing and syncs once it is back.
- iLEAN Connect — captures the MMIC supplier's certificate of conformance whether it arrives by email, by EDI or as a photo of the delivery note; reads the Anritsu/Keysight calibration equipment (modern interface, or the photographed screen of an older unit) and drops the data into the system at second zero. That forgotten spreadsheet with the calibration parameters becomes usable data.
- iLEAN Agents — the agent cross-references MMIC serial ↔ T/R module ↔ subarray ↔ radar and assembles the ITAR/EAR dossier plus the program file the auditor asks for. It does not sign: it prepares it and hands it to the program or compliance manager. The human signature is sacred; the three safety rings exist precisely to protect it.
A manual radar program vs. a program cross-referenced with iLEAN
| Aspect | Manual + classic AOI + Excel | With iLEAN Edge + Connect + Agents |
|---|---|---|
| SMT defect outside the recipe | The AOI only sees it if it was anticipated | The CNN also detects the unanticipated, flags it for IPC validation |
| Calibration ↔ MMIC batch | Manual reconstruction from spreadsheets and signatures | Automatic cross-reference at second zero |
| ITAR/EAR traceability | The audit rebuilds it by hand, weeks of work | Dossier by serial generated by the agent |
| Certificate of conformance | Email/PDF in the buyer's folder | Captured by Connect, linked to the batch |
| Operation in a SCIF / OT island | n/a | Edge keeps inspecting with no network |
| Program manager's signature | On a dossier rebuilt by a person | On a dossier prepared by the agent |
Impact estimate for your plant — to be validated with your numbers.
The block below is an estimate to be validated with the specific data of your program. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.
- A defense radar program in short or medium runs, two SMT assembly lines + an RF calibration booth + an ITAR/EAR compliance team.
- Edge pilot on one SMT line plus screen capture from the calibration equipment. First value expected within a few weeks: the system sees an SMT defect pattern the classic AOI did not have in its recipe.
- Expected reduction of ≥30% in T/R module rework and ≥50% in the time spent preparing the ITAR dossier. Indicative payback between 4 and 9 months, depending on how often program hold tags occur and how many compliance hours go into rebuilding traceability today.
- The hard lever is the program manager's hours recovered to run the program instead of rebuilding traceability part by part.
And the defense CAIO's reasonable doubt
“What if the CNN invents a defect or, worse, ignores a real one on a T/R module?” — hallucination is a problem of free generation, not of anchored tasks. Flagging candidate defects on an SMT board and comparing them with the reference part is an anchored task: the best models brought error below 1.5% [1]. And even so, the system does not decide — it proposes, flags, records. The signature of the IPC operator, of RF calibration or of the program stays exactly where it has to be. The three safety rings exist precisely for this: the decision on a critical defense part is not closed out by an AI, it is closed out by a certified person.
[1] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.
What people ask about defense radar with AI
What defects typically show up in the T/R modules of a radar?
The transmit/receive (T/R) modules of an AESA radar pack very fine SMT solder joints, waveguide connections and RF components sensitive to voltage and humidity. Typical defects are tombstoning on passives, excess or insufficient solder on BGAs, badly positioned bond wires, contamination of the ceramic substrate and calibration drift on the LNA or the PA. The eye does not catch them all in line — a classic AOI only sees what is in its recipe; Edge vision trained with a CNN also sees what nobody anticipated.
How is ITAR/EAR traceability of critical components handled?
In defense, every critical component (MMIC, phase shifter, mixer) has a serial number and a country of origin that the export dossier has to reconstruct. iLEAN Connect captures that number at second zero — from the batch label, from the scanned supplier delivery note, from the buyer's email with the certificate of conformance. The agent links it to the assembly, to the radar's serial number and to the end customer. The ITAR/EAR compliance officer signs the dossier; the system prepares it, it never closes it alone.
Does iLEAN Edge work in a SCIF or an isolated plant?
Yes. The iLEAN architecture is designed with three safety rings precisely for environments where the OT network is isolated by rule (IEC 62443, military customer requirements). Ring 1 — where the PLCs, the RF calibration equipment and the primary database live — accepts no inbound connections; it only reads from a signed mailbox. Inference and the AI live in ring 3, outside. Critical calibration does not depend on the Internet or on WiFi, and if the plant goes island-mode, Edge keeps inspecting modules.
What does the agent cover for a defense program audit?
The agent prepares the file the program auditor asks for and that today is rebuilt by hand: traceability MMIC ↔ T/R module ↔ subarray ↔ radar serial, calibration conformity by frequency and by gain, NDT of the mechanical body, ITAR supplier certificates. The agent does not sign: it prepares the dossier and hands it to the program manager, who is the one who signs. It closes the case of the “boring, concrete file” that a defense or export auditor asks for and that empties an entire office for weeks.
How much does it cost and what payback should you expect in radar manufacturing?
The order of magnitude of an Edge pilot on a T/R module assembly line is close to that of any Edge pilot in a plant with high unit value: an initial investment covering terminals + cameras + integration with the RF calibration equipment, plus the annual license. For a defense radar manufacturer, the hard levers are the rework hours saved on T/R modules and the program hours saved on the ITAR/EAR dossier. Indicative payback between 4 and 9 months — an estimate to be validated with your numbers. We send you the estimated ROI in 48h with your program's data.
Related: Defense missile with AI · Avionics with AI · Satellite components with AI
Tell us about your radar program and in 48h we'll send you the estimated ROI of this AI project for your plant.
We work on your program's real data, not ours. Diagnostic with no commitment.
Request estimated ROI in 48h See other sectors