The defence ministry is expected to issue the Request For Proposal (RFP) to French jet maker Dassault in May, and contract negotiations will begin thereafter.| India News
www.hindustantimes.com
The people cited above said the plan is to “hardwire” ICD into the final contract for the ₹3.25 lakh crore mega deal. ICD is a critical system engineering document that controls and defines all the vital protocols between a system and sub-systems. According to the proposal cleared by DAC, 18 fighters will be delivered in fly away condition from France while remaining 96 will be manufactured in India
with indigenous content of over 25%.
Yes. If we take this logic all the way to the Rafale F5, the challenge for India is no longer simply to have an aircraft capable of carrying the Astra or the Rudram. The challenge becomes integrating the Rafale into a much broader Indian combat system, while retaining control of the interface without touching the aircraft’s core French technology. And that’s where the evolution toward the F5 becomes very interesting.
The first point is that the F5 standard will automatically make India’s requirements more ambitious. With a Rafale F3R or even an F4, it’s already possible to integrate indigenous weapons, provided you have the right interface documentation and a well-managed validation process. But with the F5, we’re moving to a whole new level, because we’re no longer just talking about a fighter jet; we’re talking about a network node, a tactical orchestrator, a platform that distributes information, controls remote effectors, and serves as an interface between multiple layers of combat. For India, this means that the battle will no longer focus primarily on “source code” in the media sense of the term, but on the degree of openness of the functional architecture: which buses, which protocols, which data streams, which services are exportable to an Indian combat cloud, which weapons and which drones can be connected without touching the core French software.
This is precisely where the “communication server” comes into its own. If the Rafale evolves toward an architecture where part of the connectivity is outsourced to a more modular block, then India may seek not control of the radar, SPECTRA, or native fusion, but a robust insertion point between the aircraft and the outside world. This would allow India to develop its own tactical communications environment, its own encryption, its own gateways to the IACCS, and even its own management logic for indigenous drones or missiles, without having to penetrate the most sensitive intellectual property of Dassault, Thales, or Safran. In other words, the F5 is potentially much more compatible with the Indian philosophy than previous versions, provided that the boundary between the “French sovereign core” and the “Indian integration zone” is clearly defined.
The second point is the integration of national weapons into an F5 ecosystem. On an older aircraft, integrating a weapon primarily involves making the missile “talk” with the aircraft: power supply, pre-launch communication, launch sequences, potential terminal guidance, separation tests, etc. On an F5 aircraft, integrating a weapon means much more. It means embedding it within a collaborative combat architecture. An Indian long-range missile, such as a new-generation Astra or an air-to-ground missile like the Rudram or BrahMos-NG, will no longer be merely an object dropped by the aircraft: it can be engaged based on a tactical picture built collaboratively, with remote targeting, in-flight updates, track sharing, and even coordination with an escort drone. So for India, obtaining an ICD is only the beginning. What it will ultimately want is an ICD rich enough that its weapons are not merely “Rafale-compatible,” but fully “F5-compatible.”
The same applies to sensors and the Indian combat cloud. India is well aware that it won’t get access to SPECTRA’s or the radar’s internal algorithms, and in truth, it doesn’t need them if it can seamlessly integrate the Rafale into its own combat system. The real ambition is to use the Rafale as a premium sensor-shooter within a broader Indian system, not to “de-Frenchify” it. In this context, the Rafale is even better positioned than a so-called fifth-generation aircraft with a highly restricted architecture, because France has historically taken a more pragmatic approach to customer sovereignty. It protects what needs to be protected, but it doesn’t lock the user in to the same extent as a fully captive American system. This is, in fact, one of the key arguments in favor of the Rafale in India: it’s not just a good aircraft, it’s a good platform for relative autonomy.
The third point is the issue of escort drones. Here again, we must clearly distinguish between what India wants and what it can reasonably obtain. While the Rafale F5 is designed to operate with a loyal wingman-type escort drone, India’s concern will not be to request the source code for the French autonomous control system. Rather, it will be to determine to what extent it can integrate its own drones—or develop a locally co-developed drone—within an operational framework inspired by the F5. In other words, the real issue is not “Will France hand over the drone’s brain?”, but “Can the Indian Rafale serve as a mother platform in an environment of Indian drones?”. If the answer is yes, even partially, then the Rafale F5 becomes a training ground for collaborative combat for India, while awaiting the AMCA and what follows.
And this is where timing works in the Rafale’s favor. The AMCA is higher on the priority list than the TEDBF, but it will remain a high-risk program for a long time, dependent on the engine, stealth capabilities, system integration, and industrial ramp-up. The TEDBF, for its part, has drifted away, shifting toward a more ambitious stealth approach. So in the 2030s, the only system truly available to India in significant numbers, with advanced network capabilities, domestically produced weaponry, and potentially drones, will very likely be the Rafale F5. This means that the F5 will not merely be a transitional purchase: it risks becoming, for India, the first true “pre-6th generation” combat system available on an operational scale.
The industrial implications are significant. If India acquires 114 “Made in India” Rafales, plus 26 naval variants, and likely additional units, it will have every interest in making the F5 not just a simple imported version, but the foundation of a local ecosystem. Indian missiles will be integrated onto it. Maintenance and testing tools will be localized. The M88 could have a local support network, with Safran having even publicly hinted at its openness to an engine assembly line in India, according to reports from late 2025. And above all, Indian personnel will learn to work on a top-tier Western platform, within a framework where France remains demanding but not stifling. For the AMCA, for future drones, and for engines, this accumulation of experience will count for a great deal.
Ultimately, the Rafale F5 in India could play three simultaneous roles. First, an immediate operational role: restoring the size and quality of the fleet, with a platform whose effectiveness against Pakistan and Chinese-origin systems has already weighed heavily in decision-making. Second, a doctrinal role: learning to conduct collaborative combat, integrate national missiles, and utilize the combat cloud, even before indigenous programs are mature. Finally, an industrial role: serving as a springboard toward future autonomy, not by handing over all French secrets, but by giving India the interface points that truly matter.
This is why the false debate over source codes masks the real issue. The F5 does not need to be “open” in the naive sense of the term. It must be “interoperable in a controlled manner.” If France accepts this logic and if India understands that sovereignty depends on interfaces, weapons, communications, and industrial chains rather than on ownership of the software core, then the Rafale F5 can become much more than a fighter jet purchased abroad: it can become the backbone of India’s transition to its own air combat system of the future.
