DISC 14 and ADITI 4.0 Outreach Session - Indian Army (Apr 20)

Tech-focused summary of the session (DISC 14 + ADITI 4.0 outreach)

1) Snow traction system automation (metallic snow chains) — problem statement discussion

• Operational need: Heavy “B category” load-carrying vehicles (e.g., similar range to Mahindra Scorpio) must negotiate snow-ridden terrain including fresh snow and verglas (solid ice formation).
• Current method: Drivers/co-drivers manually install metallic snow chains on four vehicles, then retract them after passing.
• Pain point: Manual chain installation/retraction is time-intensive and effort-intensive in extreme cold; goal is reducing human workload.
• Proposed solution concept: An automatic snow-chain install/retract system controlled from the driver compartment:
  • Driver presses a button → chains install onto wheels automatically
  • Driver presses again → chains retract
  • Minimal human intervention
• Clarification: Requirement is for snowy/ice conditions, not only hard surfaces.

---

2) Weaponized “hive” of AI-enabled autonomous robot dogs — special forces concept

• Goal: Develop a weaponized hive of AI-enabled autonomous robot dogs for special forces, operating as manned and unmanned teams.
• Capabilities described:
  • Point A to B movement: one mode with human involvement, another autonomously
  • Enter buildings, clear interiors, and neutralize visible threats
  • Targeting must be human-in-the-loop (not fully autonomous targeting)
• Model: Multiple robot dogs collaborating as a group/hive.

---

3) Counter-UAS “drone catcher” (hard-kill) for artillery close protection — modular mobile CUAS

• Base requirement: A counter-drone system to detect, track, and neutralize drones using hard-kill, including net/catcher concepts.
• Target effectiveness:
  • Capture/neutralize UAS and other munitions
  • Should handle swarm drones
• Use case: Protect artillery gunnery assets within an area roughly 500 m–1 km behind the front line; intercept drones approaching the protected zone.
• System form factor:
  • Low cost, high performance
  • Modular design for future integrations
  • Prefer indigenous, upgradeable system
  • Autonomous and portable interception
• Coverage / range (from Q&A):
  • Expected 360° azimuth coverage
  • Approx 3–5 km detection/engagement capability
  • Neutralization expected around 1–2 km
• Integration platforms discussed:
  • Can be integrated on vehicle-mounted gun platforms (e.g., K9 Vajra, long-range vectors, Pinaka/Smash type mentioned in later CUAS context)
  • Otherwise deploy as an independent identity near the gun area
• Kit expectations (hard/soft kill versions):
  • Compact plug-and-play kit combining soft-kill + hard-kill
  • Man portable (up to 1–2 operators), easy to deploy
  • Battery operation ~3–4 hours
  • Weight ≤ 25 kg
  • Neutralization technologies left open; responses emphasized effectiveness and avoiding heavy systems

Key Q&A themes for CUAS

• Interfaces: catcher can be independent, or integrated onto certain gun vehicles (vehicle integration where feasible).
• Similarity check: whether it matches an earlier Army Air Defense RFI—nodal response indicated they would check and confirm.
• Protected assets / mounting: examples included Tatra 6x6/8x8 and Smash/Pinaka/other long-range vector platforms, plus possibility of ground deployment.
• Minimum order quantities: 100 initially, desire to scale if effective.
• Hard-kill modality: soft-kill discussed as present; hard-kill options are broader/negotiable with AI-assisted detection for automation (no manual firing interface).

---

4) Standardized GCS for UAS — interoperability to reduce training burden

• Problem: Multiple UAS/loitering munitions/swarm systems arrive with different Ground Control Stations (GCS) across vendors and equipment batches.
• Impact: Training is difficult because operators switch GCSs when moving between units and drone categories (loitering → swarm → ISR UAS, etc.).
• Requirement concept: Create a Standardized GCS (SGCS) so that:
  • Users train on one standardized controls/display interface
  • Existing contracted systems remain; SGCS acts as a plug-and-play integration layer
  • Interoperability is supported via compatible modules/data handling (telemetry/video and possible AI-related data)
• Important clarifications from Q&A:
  • SGCS is not intended to replace/alter drone-side interoperability; drone interoperability stays with its original GCS
  • SGCS should integrate vendor hardware by absorbing/reading data rather than changing drone native control architecture
  • Consolidated “unified GCS” integrating multiple systems: must fit procurement constraints and likely requires vendor cooperation or defined integration conditions

---

5) Infantry 5: heavy load-carrying drone using IC engine + GPS-denied operation — performance constraints

• Aim: Enable 100 kg payload aerial delivery with an IC engine drone to improve feasibility over battery-only approaches.
• Performance/constraint points mentioned:
  • Ceiling limit ~18,000 ft
  • Payload: 100 kg
  • Endurance: ~3 hours
  • Terrain distance/operating consideration: mentioned about ~25 km
  • GPS-denied environment capability (explicitly required)
  • Configuration flexibility: fixed wing / multicopter / hybrid acceptable
• Training/testing planning: minimum two drones for testing was indicated (broader quantities to be decided later).

---

6) Infantry 5: 360° awareness + night EO + AI detection + driver AR assistance

• Use case: Protected mobility vehicles where size/dimensions make it hard to drive/off-road through obstacles.
• Requirement:
  • 360° situational awareness using multiple cameras
  • AI-based detection (object recognition)
  • Electro-optical cameras operable at night, 0.01 lux
  • Augmented driver assistance concept (e.g., AR goggle/screen) for night navigation/visibility
• AI detection scope (from Q&A):
  • Terrain obstacles: sand/trees/ditches/rock faces, etc.
  • Enemy equipment detection: tanks/vehicles
  • Adversary/own equipment models expected from Army; developers responsible for terrain model training
• Procurement/industrial constraint: indigenous development only (no Chinese components) for 360° capability since treated as an IDEX case.
• Environment factors: vehicle may operate in high-altitude, deserts, semi-arid, snow, windy, and water/canal/river terrain.

---

7) Aviation: helicopter-mounted anti-drone early warning + jamming (Aditi 4.0) — EO integration + UI warnings

• Core goal: Helicopter-mounted capability to detect (and potentially jam) emerging UAS threats.
• Problem motivation: Current Indian Army helicopters (including LCH variants Mark 1–4; Apache LCH mentioned) lack adequate tools to identify/detect and neutralize/jam drones.
• Requirement described:
  • Helicopter-mounted embedded system integrating EO part / avionics
  • AI-assisted detection/tracking
  • Jam incoming drone signals/waveforms using passive sensors (as described)
  • Display threat info with coordinates, distance on MFD, and warnings on HUD
  • Visual and audio warnings
  • Threat localization in-flight
  • Range stated: ~200–400 m
• Integration approach discussed in Q&A:
  • Use existing EO pod (CCD and laser-related sensors mentioned)
  • Use detection/RF threat location to direct EO pod to threat angle
  • Friendly vs adversary classification via a library concept
• Soft-kill vs hard-kill:
  • Discussion suggested soft-kill (jamming/spoofing) feasible first; hard-kill harder for helicopter version at time of response
• Weight expectation constraint: starting point ~15–20 kg (integration certification still matters)
• Certification / EMC-EMI: SEMILAC certification concerns raised; nodal response indicated appropriate SEMILAC-related certification and avionics EMI/EMC checks are required.

---

8) Aditi 4.0 final outreach statement: Air crew protection vest

• Requirement overview:
  • Vest must be ballistic/resistant (resist ballistics/trigger surges)
  • Must use advanced materials and work in all-weather conditions
  • Include sensors to monitor body parameters
  • Support connectivity and sensor-driven monitoring

---

Program/framework logistics shared (IDEX / DISC / Aditi outreach)

IDEX overview and schemes

• IDEX: Innovations for Defense Excellence (fund managed by the Defense Innovation Organization) with grant schemes:
  • DISC: max spot grant 1.5 CR
  • IDEX: 25 CR
  • Open Challenge (OC): 1.5 CR

Challenge focus and duration

• Shift toward reducing duplicity and focusing on tech (not product)
• Emphasis on dual-use transition (military → civil)

Timeline highlights

• Applications receipt: by 4th May
• Max ideal completion timeline: 24 months
• Steps include: eligibility check → shortlisting → provisional winner after HPSC → compliance checks → milestone development → SSCT trials → AON + procurement award

Submission guidance

• Outreach schedule and the last date for technical query submission are available on the IDEX portal
• Technical queries deadline mentioned as tomorrow (relative to the session)

---

Main speakers / sources mentioned

• Nodal officers / representatives from DG Infantry (multiple problem statement presenters)
  • Explicitly noted: DG Infantry 7 for “weaponized hive / robot dogs”
• Colonel Vijay Jiwan (RT 14) — presented counter-drone drone catcher / CUAS related statements
• RT 9 / DGART (implied) — “development of standard GCS for UAS”
• Infantry 5 representatives
  • IC-engine heavy load-carrying drone
  • 360° awareness + night EO + AI detection + driver AR assistance
• Colonel Dasgupta (Army Aviation) — session lead for helicopter-mounted anti-drone statement
• Sanjeev Jeet (DIO) — introduction during aviation segment
• DIO session moderators (general outreach context)

Participating vendor voices (Q&A)

• Aniket (Girnar Precision Technologies)
• Arvind (Optimize Group)
• Prasad (Munitions and Explosives / UTS Hyderabad)
• Roshan Sharma (Zedo Integrated Systems)
• and other participants who asked technical questions within their respective segments