Sovereign Capability Development
Genuine capability development means your people continue to own and operate every aspect of the mission solution after we leave.
Glossary
The International Traffic in Arms Regulations control the export of defense articles, defense services and related technical data on the United States Munitions List. For a partner-nation ISR program, ITAR governs which equipment can be exported, which technical information can be shared, which foreign nationals may receive it, and how long the program will take before any of that happens.
Three things, and the third is the one programs underestimate:
That third category is why ITAR shapes a training program as much as an equipment package.
Releasing controlled technical data to a foreign national counts as an export to that person’s country of nationality, wherever the release physically happens. No border is crossed and no item ships; it is still an export and it still requires authorization.
This has direct consequences for how a partner-nation program is staffed and run:
The last one catches people. Remote support is exactly the arrangement that feels informal and helpful, and it is squarely within scope.
Two instruments do most of the work in this kind of program.
Export licenses authorize shipment of specific hardware to a specific end user, for a specific purpose. They are item-and-recipient shaped.
Technical Assistance Agreements authorize the transfer of defense services and technical data — training, integration support, maintenance instruction — between named parties, listing the nationalities of the people who may receive it. A TAA is what makes a capability-transfer program legal, and it has to be in place before the teaching starts rather than alongside it.
Both take time measured in months, and the clock does not begin until the submission is complete and accurate. A program that treats licensing as an administrative task to start after award has usually added a quarter to its schedule without noticing.
Sensor choice is partly a licensing decision. The most capable payload is not the right one if its licensing pathway takes longer than the program’s political window, or if the end-use monitoring regime it attracts is heavier than the recipient institution can carry.
Training has to be designed around it. What can be taught, to whom, and by whom is constrained. A capability-transfer program whose training plan assumes unrestricted knowledge sharing will encounter this late and expensively — usually at the point where the partner nation’s own instructors were supposed to take over.
Timelines belong in the schedule. Licensing duration is a known quantity, not a risk item, and it should appear in the program plan as a task with a duration rather than a caveat in the assumptions.
It does not stop partner-nation programs, and it is not avoided by contracting route. Direct Commercial Sale is not a way around export control — it is a different contracting path that still requires the license. Foreign Military Sales moves the transaction government-to-government, which changes who holds the paperwork but not whether authorization is required.
Anyone suggesting a structure that avoids the requirement is describing a compliance problem, not a strategy.
Authorization is granted against undertakings the partner nation makes and keeps: that the item stays with the named end user, at the agreed location, used for the agreed purpose, and is not retransferred without prior written consent.
Those undertakings outlive the contract that delivered the equipment, and they are verified — see end-use monitoring. A government that has not built the inventory discipline and physical security to evidence compliance will find the next authorization harder to obtain, which makes compliance capacity part of the capability rather than paperwork attached to it.
A supplier who raises ITAR in the first meeting is telling you what the program will actually take. A supplier who does not mention it until after award is either inexperienced with partner-nation work or is deferring a problem you will pay for later — in schedule, in a training plan that has to be rebuilt, or in a sensor that turns out not to be exportable to you at all.
Common Questions
Three things. Defense articles — physical items on the United States Munitions List, including many sensor systems. Defense services — assistance in designing, operating, maintaining or training on those articles. And technical data: the information itself. Sharing controlled technical data with a foreign national is an export, even in a room in the United States, and even verbally.
It shapes sensor selection, because the most capable payload is the wrong one if its licensing pathway outlasts the political window. It shapes training, because what can be taught, to whom and by whom is constrained. And it shapes the schedule, because licenses and agreements take time that belongs in the plan from the start.
Long enough that it belongs in the program schedule as a dependency rather than as a risk item, and the duration varies considerably by article, destination and case complexity. The practical signal to watch: a supplier who raises export control in the first conversation is telling you what the program will actually take.
An authorisation covering the provision of defense services and the sharing of technical data with foreign persons — the instrument that makes training and technical support on controlled systems lawful. On a capability-transfer program it is frequently the long pole, because transfer is fundamentally an exercise in sharing technical data.
Releasing controlled technical data to a foreign national, which counts as an export to that person's country of nationality wherever the release physically happens. No border is crossed and nothing ships, but it still requires authorization. A video call in which a U.S. technician talks a foreign maintainer through a controlled procedure is within scope.
The instrument that authorizes transfer of defense services and technical data — training, integration support, maintenance instruction — between named parties, listing the nationalities of people who may receive it. A TAA is what makes a capability-transfer program legal, and it has to be in place before the teaching starts rather than alongside it.
No. DCS is a different contracting path that still requires the license. Foreign Military Sales moves the transaction government-to-government, which changes who holds the paperwork but not whether authorization is required. Anyone proposing a structure that avoids the requirement is describing a compliance problem rather than a strategy.