ADITI 4 – Conversion of T-72 into Autonomous Armoured Fighting Vehicle: Development milestone in India

Development and reported outcome

On 19-Mar-26, iDEX / Defence Innovation Organisation; supplier to be selected advanced ADITI 4 – Conversion of T-72 into Autonomous Armoured Fighting Vehicle Platform, an R&D, requirements or institutional milestone focused on Autonomous conversion kit / platform for T-72 tank for Indian Army.[S1]

Program, platform and stakeholders

Programme or contract: ADITI 4 – Conversion of T-72 into Autonomous Armoured Fighting Vehicle Platform. Platform or product: Autonomous conversion kit / platform for T-72 tank. Recorded supplier, developer or relevant organization: iDEX / Defence Innovation Organisation; supplier to be selected (reported headquarters/country: India). Recorded customer, operator or intended user: Indian Army (reported headquarters/country: India).[S1]

Mission and technical scope

The following are classifications recorded in the source master, not additional claims of operational deployment: Mission/use-case classification: Autonomous AFV; high-risk missions; minefield entry; breaching; decoy; reconnaissance patrols. Mobility classification: Tracked. Operating mode: Remotely Piloted / Fully Autonomous.

Contract, value and shipment signals

Recorded quantity, delivery, demonstration or volume signal: 2 prototypes required under challenge outcome. Delivery schedule, procurement window or milestone status: R&D challenge / prototype pathway; no production order established.[S1]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Official iDEX source supports the R&D challenge and prototype requirement. It is not presented as a production contract.

Interpretation boundary: A development milestone does not by itself establish completion, acceptance or fleet induction.[S1]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — product or engineering development: The India UGV record for ADITI 4 – Conversion of T-72 into Autonomous Armoured Fighting Vehicle Platform is best treated as a technical progression signal. The record documents a capability step or integration scope, not proof of mass production or repeatable sales.

Traceability for buyers: The dataset associates iDEX / Defence Innovation Organisation; supplier to be selected with Indian Army for Autonomous conversion kit / platform for T-72 tank. This supports stakeholder mapping; supply-chain tier, exclusivity and signed-customer relationships need the underlying source before firm classification.

Client-use interpretation: For intelligence users tracking Autonomous AFV; high-risk missions; minefield entry; breaching; decoy;…, the relevant next proof points are mine-warfare mission suitability, payload integration and acceptance milestones. Watch for successful acceptance testing, commercial availability, customer commitments and quantified deliveries.[S1]

Quantitative evidence, calculations and limits

Quantity/scope signal: 2 prototypes required under challenge outcome. Counting rule: Scope or component count; not a count of procured or delivered unmanned platforms. Delivery/timing evidence: R&D challenge / prototype pathway; no production order established. Scheduling language is not independently proof of completion or acceptance.

Keep reported, derived and prospective quantities separate; do not convert activity into installed-base counts without a shipment or acceptance source.[S1]