🚀
On 10 September 2025, ISRO handed over the entire Small Satellite Launch Vehicle (SSLV) to Hindustan Aeronautics Limited (HAL) — the first time a space agency has given a complete rocket to a company. HAL won the contract worth ₹511 crore, beating two other consortia. The goal: let ISRO focus on advanced projects like Gaganyaan, while industry manages routine satellite launches.
📅 The Two-Year Timeline
HAL gets drawings, two years of joint work with ISRO engineers, and two rockets to build. After that, HAL must operate independently under a non-exclusive licence. The concern: transferring a decade of ISRO’s experience in just 24 months may be unrealistic.
✈️ Lessons from HAL’s Past
Su-30MKI Fighters (2004–2020): HAL licence-built 222 jets with Russian kits. Indigenous content was only 13% (vs. 60% promised), and expertise failed to take root.
Dhruv Helicopter (1984 onwards): Joint design with German engineers gave HAL genuine design capability. 👉 The difference: design knowledge sharing vs. mere assembly.
🧠 The Challenge of Tacit Knowledge
Rocket programmes rely heavily on unwritten, experiential knowledge — why a weld angle matters, or which vibration signals danger. This cannot be captured in manuals. Transfer depends on absorptive capacity — the receiving firm’s ability to understand and internalize knowledge.
🌍 Global Case Studies
Toyota (NUMMI Plant, USA): Success came from embedding workers in Japan and long-term collaboration. Manuals alone failed.
Japan (F-15J to Sixth-Gen Fighter): Used licence production as a training ladder over decades.
South Korea (F-16 to KF-21): Progressed step by step, co-developing with Lockheed Martin, eventually mastering radar technology.
NASA & SpaceX (2006 onwards): NASA placed engineers inside factories, shared decades of failure data, and stayed engaged — enabling SpaceX’s rapid success.
🔑 Common Success Factors
Across industries and countries, successful transfers required:
Years of joint work, not months
Sequential programmes building on each other
Supplier presence long after handover
🇮🇳 The Open Question for India
The SSLV agreement gives HAL two years of joint work, then nothing more. ISRO spent over a decade developing SSLV, including failures and redesigns. HAL risks missing the tacit knowledge unless ISRO treats this as the first stage of a longer partnership, continuing support like NASA did with SpaceX.
🎯 Conclusion
India’s decision to transfer SSLV is strategically sound. But the two-year limit may be insufficient. For HAL to truly master rocket-building, ISRO must remain engaged beyond the initial handover — otherwise, India risks repeating past mistakes of “assembly without design.”
No comments:
Post a Comment