Technology denial regimes have historically catalysed India's indigenous capabilities in the nuclear sector. Discuss with examples.
New · District CollectorCan you hold the district for 72 hours?Floods, a heatwave, an outbreak, a grievance queue. Take the decisions, see the consequences.Play →Technology denial means suppliers cut off reactors, components or know-how in order to limit a country's nuclear programme. After India's 1974 test, Canada and other suppliers did this to India [2]. Instead of stalling the programme, the denial pushed India to build domestic capability across the PHWR (pressurised heavy water reactor) chain, though this came at the cost of speed.
Denial as catalyst: key examples
- Completing RAPS-2 alone: Canada withdrew while Rajasthan Unit 2 was still being built. India chose to carry on alone, and the unit began supplying power in 1981 [2]. BARC took over the development of pumps, fuelling machines, fuel and cladding [3].
- Heavy engineering: In 1976 BHEL Tiruchi rolled out India's first nuclear steam generator, for MAPP-II at Kalpakkam. Rajasthan's units had used ones imported from Canada [1]. To build it, BHEL set up clean rooms, trained nuclear-grade welders, and developed a "hot pull-out" process that made heavy water headers indigenous [1].
- Scaling the design: The indigenous 700 MWe PHWR is now in commercial operation at Kakrapar 3 and 4 and RAPP-7 [5].
- Supply-chain depth: Under NPCIL's fleet mode programme, BHEL won 12 steam generators through competitive bidding in 2021 [4]. That depth of domestic supply comes from capability first built under denial.
The other side: limits of forced self-reliance
- Slow scale-up: Fifty years on, capacity is expected to reach only about 22,380 MW by 2031–32 [7]. Isolation made India build every link itself, one after another.
- Constraints persisted: Limited access to fuel and large reactors held back output until India's civil nuclear opening in the late 2000s.
- Imports were no quick fix: The Russian-built Kudankulam units also ran years late, and the CAG linked many delays to the Russian contractor. The estimated cost rose from ₹13,171 crore to ₹22,462 crore [6].
1974 test → supplier withdrawal → BARC/BHEL in-house R&D
→ indigenous PHWR (220 → 700 MWe) → fleet-mode supply chain
Flowchart: how denial turned into capability
Overall, technology denial gave India a working reactor design and a supply chain that outsiders cannot cut off, but it cost India speed. To reach the 100 GW by 2047 target [7], India needs to keep that strategic autonomy while adding scale through bulk orders, more suppliers and global partnerships. That would turn necessity-driven self-reliance into the competitive strength that the vision of an Atmanirbhar nuclear sector calls for.
Sources
- 1Nuclear steam generator from BHEL ("50 years ago"), The Hindu, Chennai edition, 13 Oct 20261976 rollout at Tiruchi, earlier Canadian imports, clean rooms and welders, hot pull-out headers (exact article page could not be fetched; domain root linked)
- 2NPCIL feature on India's nuclear power journey (Azadi ka Amrit Mahotsav), March 2022sanctions after the 1974 test, Canada's withdrawal from RAPS-2, India's decision to go alone, power supply from 1981
- 3BARC activities for Indian Nuclear Power ProgramBARC's development of PHWR components, fuel and cladding
- 4BHEL press release: BHEL bags order for Nuclear Steam Generators from NPCIL against stiff competition (July 2021)12 steam generators, fleet mode, competitive bidding, Tiruchi manufacture
- 5Committee on Public Undertakings: Report on NPCIL, Lok Sabha Digital Librarycommercial operation of Kakrapar 3 and 4 and RAPP-7 (document server unreachable; domain root linked)
- 6CAG Report No. 38 of 2017: Performance Audit on Kudankulam Nuclear Power Project, Units I and IIcompletion delays linked to the Russian contractor, cost rise from ₹13,171 crore to ₹22,462 crore
- 7PIB: In Rajya Sabha, Union Minister Dr. Jitendra Singh Affirms Fast-Track Nuclear Expansion; Capacity Set to Triple by 2031–3222,380 MW by 2031–32 and 100 GW by 2047 (release page returned 403; domain root linked)