Israeli clarification on the “Shield of Achilles” added information about cooperation in the field of software, but didn’t give unambiguous public response about transferring the source code to Greece.
After the initial Statements by the head of the Israeli Missile Defense Authority Moshe Patel The discussion about the program worth €3.035 billion continued. It is now important to compare the initial response with the subsequent explanation and understand exactly what rights of the Greek side remain undisclosed.
What did the Israeli side say?
By publications by iefimerida on September 7a subsequent clarification from the Israeli Ministry of Defense provides for the transfer of knowledge, sharing of software and technology with the Greek Armed Forces. Cooperation should also include Greek enterprises involved in joint production.
In the above formulation, however, there is no direct promise to hand over the source code. A publication source close to the Greek Ministry of Defense said that there was no problem with the agreed terms and referred to this clarification. The full contractual provisions were not disclosed in the publication.
Why did the dispute arise?
How it conveys ArmyvoicePatel, in an interview with Kathimerini, answered negatively to a question about Greek access to the source code of the command and control system. He explained that the code is not included in the license agreement.
This raised questions against the backdrop of statements by Nikos Dendias: the minister previously linked access to code with the ability to independently change the architecture and develop the system. We analyzed the initial contradiction in the material about control over the “Shield of Achilles”.
The current explanation must be taken into account when assessing the situation. But it would be premature to declare the dispute completely closed only on the basis of words about the joint use of technologies.
Exploiting and modifying a program are different rights
Managing the complex within the limits of its functions and changing its software basis are different actions. The buyer may have the ability to detect targets, distribute tasks and use weapons, but depend on the developer to change algorithms, connect new equipment or deep modernization.
Therefore, the statement “Greece will not be able to control its air defense” would be too broad. The subject of public dispute is the degree of independence in the development of software architecture, the amount of access and the conditions for such access.
The mere presence of source code files also does not answer all questions. Contractual rights are important: which modules are allowed to be changed, who can carry out the work, and whether manufacturer approval is required. Without disclosing these terms, it is impossible to accurately describe future dependency.
Why is this important for the entire system?
By Protothema message about signing the agreementthe project is being built as a unified network of detection, weapons and control equipment. A significant role for Greek industry was also announced. Thus, we are talking about long-term organization of defense and technical support, and not just about the supply of individual launchers.
Upgrading weapons involves operating the system for many years. We wrote about the experience of long-term operation of equipment in history of the Greek F-4 Phantom. For software-related systems, the possibility of updates and availability of maintenance are especially important.
In the background new disagreements between Greece and Turkey around Evros the issue of independence of defense infrastructure is acquiring additional political significance. However, the current contract dispute does not in itself indicate a loss of operational control.
What other answers are needed?
The Greek side will have to clearly explain what code it receives, what changes it will be able to make and where the mandatory participation of the supplier will remain. A separate issue is the rights of national enterprises that will be entrusted with the maintenance or development of the system.
Editorial conclusion: The new Israeli explanation should be included in the picture of events. It confirms the stated technological cooperation, but the published wording is not enough to equate it with unlimited Greek independence in working with the source code.
More Stories
The EU has limited Greece’s request to €700 million: assistance is possible, but only within the framework of current rules
Russian gas again in Europe? The US and Russia are discussing a deal around Nord Stream
Greece will purchase American weapons worth $4 billion: what was included in the agreement with the United States