Indian Army Gears Up for Rigorous Evaluation of FRCV Contenders with "Make in India" Focus

frcv_drdo_2_0.jpg


The Indian Army is preparing for a comprehensive evaluation of companies vying to build the Future Ready Combat Vehicle (FRCV), a critical program aimed at replacing the aging T-72 Main Battle Tanks (MBTs) by 2030.

With an Acceptance of Necessity (AoN) already in place for the procurement of 1,700 FRCVs, the competition is expected to be fierce, attracting both domestic and international players.

A key aspect of the evaluation process will be a special audit conducted by the Indian Army and DRDO. This audit will focus on ensuring adherence to the government's "Make in India" initiative by verifying the indigenous content of each proposed tank. This step is crucial to prevent the submission of rebranded foreign MBTs and to promote the growth of India's domestic defence industry.

While international companies are expected to participate, they will need to demonstrate a strong commitment to manufacturing the FRCV in India, even at the prototype stage. This may involve partnering with local private sector firms like Mahindra, Kalyani Group, and Tata Systems, who are considered major contenders in the FRCV program.

The evaluation will involve rigorous trials to assess the performance and capabilities of the proposed FRCV designs. The DRDO's own Next Generation Main Battle Tank (NGMBT) will also be a contender in this competition.

The selection process will prioritize genuine interest and commitment to the "Make in India" initiative, ensuring that the chosen FRCV is truly a product of Indian manufacturing and contributes to the country's self-reliance in defence technology.

The FRCV program represents a significant step in modernizing the Indian Army's armored fleet and ensuring its preparedness for future challenges. The outcome of the bidding process will have a lasting impact on the Indian defence landscape, shaping the future of its main battle tank fleet and its ability to meet evolving security threats.
 
We need four types of Tanks ! First FRCV jointly developed with General dynamics and land systems,Second Arjun MBT-1A jointly developed with Germany ,third T-14 Tech based Arjun-MK-II and 4th,Light Tank Zorawar based on Abram-X technology !
 
We need four types of Tanks ! First FRCV jointly developed with General dynamics and land systems,Second Arjun MBT-1A jointly developed with Germany ,third T-14 Tech based Arjun-MK-II and 4th,Light Tank Zorawar based on Abram-X technology !
We want everything but have nothing
 
Please do not try to put every system in one platform other wise it will be designed to fail. Have a separate air defence/ anti drone vehicle which accompanies tanks on battle ground.
 
Why involve DRDO in the audit? It will definitely favour LT-Gujarat, who have agreed to give them credit for 'design & development' of Zoravar tank & allow 'DRDO' nameplate on the tank. Also, like LT-Gujarat most of the bidders will use local fasteners & other 'C' category items to qualify for 60-70% local content in terms of number of total items i/o in terms of value.
 
Another Arjun in making this should be marked in bold or put in headline some where some general would have seen star war and would put up a requirement some where in the document and it will become a Arjun part 2
 
Another Arjun in making this should be marked in bold or put in headline some where some general would have seen star war and would put up a requirement some where in the document and it will become a Arjun part 2
Let’s be very clear bro. Client can only be blamed for giving unrealistic requirements as long as the developer doesn’t accept those specs. As soon as specs are accepted and money is taken, the entire blame shifts to the developer. That is, only and only DRDO is to be blamed for whatever happened to Arjun.
 
Let’s be very clear bro. Client can only be blamed for giving unrealistic requirements as long as the developer doesn’t accept those specs. As soon as specs are accepted and money is taken, the entire blame shifts to the developer. That is, only and only DRDO is to be blamed for whatever happened to Arjun.
But as a developer u have to put ur foot down some where how much was wasted on Arjun even god doesn not knows
 

Forum statistics

Threads
3,389
Messages
28,043
Members
1,574
Latest member
ruudra
Back
Top