Summary of "DISC 14 and ADITI 4.0 Outreach Session - Indian Army (Mar 23)"
Main ideas / purpose of the session
An Indian Army / IDEX outreach session explains how startups and innovators can engage with defense problem statements under:
- Aditi 4: technology acceleration; larger grants up to ₹25 crore
- DISK 14: specific defense challenges; grants up to ₹1.5 crore
The session proceeds in two phases:
- Technical outreach: nodal officers briefly present each problem statement, then conduct Q&A for innovators.
- General outreach: procedural details about IDEX, the selection process, funding, timelines, and application guidance.
Problem statements covered (technical outreach)
Aditi 4 (4 challenges total)
1) 155 mm Terminally Guided Munition (TGM) / Precision-guided projectile
Objective
- Develop a precision-guided 155 mm terminally guided (or precision-guided) munition.
- Target precision requirement: CEP < 10 m.
Key technical challenge
- Miniaturization of circuitry in sensor heads and integration with any glide/correction mechanisms.
Scope / expectations
- Indigenous guidance solution (optionally GPS/INS, or hybrid).
- Phased compatibility is allowed:
- Initial compatibility with one caliber is acceptable, then spiral development for other calibers.
- High-altitude firing compatibility expected later via phased upgrades.
Quantity scale (as stated)
- Current order-of-magnitude examples: ~10,000 rounds today
- Expected future: ~60,000–80,000 rounds over ~5 years
Guidance vs laser (Q&A clarifications)
- Not seeking “fuse-with-fins” or course-correction fuse.
- Seeking a complete projectile with deployable fins, using guidance control at spin rate.
- Laser bandwidth/details not specified; laser is not the focus at this stage—guidance control and integration are priority.
Engagement / range clarifications
- Example discussion included:
- ~24–26 km for baseline (described as ~85% of standard H-shell fuse performance)
- Potential ~40–50 km if using fin deployment + GPS/glide mechanism (to be deliberated later)
Prototype integration model
- Expected to be consortium-based with multiple vendors covering specializations.
- Access to projectiles may be limited; inventory described as very limited and requires confirmation.
Engagement mode data
- Programming occurs at the breech / race-end via inductive programming before firing (not necessarily at the muzzle).
2) Cognitive Electronic Warfare (EW) system
Concept
- EW using cognitive technology (AI/ML) to sense, adapt, self-learn, and make feedback-based decisions for countermeasures.
System building blocks (as described)
- Antenna(s)
- Receiver
- Processing unit(s)
- A database / knowledge base for intercept/identify/analyze/localize
Required capabilities
- Detect and categorize signals as threatening vs non-threatening
- Support offensive/defensive EW operations:
- Direction finding (DF)
- Location finding / geolocation (using multiple measurements)
- Jamming (barrage/noise jamming and newer cognitive/responsive jamming types)
- Handle a wide variety of electronic environments, including LPI-related bandwidth needs (bandwidth specifics to be shared after technical vetting with stakeholders)
Frequency handling (Q&A clarifications)
- Cognitive EW should include appropriate bandwidth coverage depending on threat signal characteristics.
- Bandwidth requirements will be shared after vetting.
Threat library / knowledge base
- A knowledge-base / pre-fed threats concept was referenced.
- Specific “library access” details depend on what can be shared and will be discussed after receiving queries.
Architecture / deployment style (Q&A)
- Described as an integrated system, not guaranteed to be realizable as a single unit.
- May include control blocks, DF system, jamming across VHF/HF/cellular, and possible satellite/UAV/non-domain integration.
3) Programmable Prefragmented & Proximity Fuse Ammunition
Application
- Engage aerial targets (e.g., drones) with precision/proximity effects.
- Motivation: current gun types include proximity rounds and direct-impact HE, but need programmable + proximity + prefragmented capability.
Core requirements (explicit list)
- Proximity: proximity fuse functionality for air-burst / near target engagement
- Programmable: program fuse behavior (e.g., timing/range-related programming)
- Prefragmented: shell must be prefragmented to break into effective fragments
Platform integration (L70 gun)
- Phase 1 focus: integrate the smart programmable ammunition and programmer with existing L70 guns.
- Minimal/no gun modifications expected:
- Spin stabilization should remain; rifled barrel retained.
- Fire control:
- The electro-optical fire control system (EFCS) is part of separate/upgradable programs, not included in Phase 1 scope.
- Inductive programming occurs at/near the breech/at loading stage (as stated in Q&A).
Range-finder / detector expectations (Q&A clarifications)
- EO/LRF may already exist on upgraded guns.
- The solution should provide the smart ammunition components and integrate with existing systems; LRF redesign not required in the provided clarifications.
Fragmentation guidance (Q&A)
- Existing worldwide prefragmented rounds with fragment sizes in the 2–5 mm range were referenced.
- Suggested approach: leverage existing prefragmented rounds; focus on proximity + programming + electronics in fuse/programmer rather than redesign full fragmentation physics.
Programming rate
- Programming should not affect gun’s rate of fire; rate remains up to ~300 rounds/min.
Programmer/fuse quantities
- Initial prototype quantities described as “adequate for business sense,” but no open-domain numbers provided.
4) Humanoid for Combat / Humanoid Auto System
Operational gap
- Reduce soldier exposure in high-risk high-altitude and combat environments.
- Soldiers carry heavy loads (20–25 kg stated for context).
Challenge goal
- Develop indigenous, combat-capable humanoid system with:
- high dexterity/mobility
- autonomy with human-in-the-loop control
- ability to operate alongside or ahead of soldiers
- modular design and software upgradability
- scalability by capability stage
Required technical domains (as stated)
- Robotics & actuation
- high-torque rugged actuators
- sensors and controls
- Multi-session / multi-modal sensor fusion
- balance, navigation, perception
- AI/ML integration
- reinforcement learning for gait stability and decision-making
Expected outcomes (staged)
- Stage 1: deployable system
- Stage 2: fully functional combat humanoid system assisting soldiers (replacing them in high-risk missions)
- Stage 3: testing & certification; prototype refinement and compliance
Mobility and tasks (Q&A)
- Handle uneven/icy/inclined terrain and weapon/equipment manipulation.
- Full autonomy expected, but early roadmaps may involve tele-operation; organizers indicated questions can be routed for confirmation, though the target is “full autonomous system.”
Exoskeleton vs humanoid
- Staged expectation may include exoskeleton development toward a combat humanoid.
Scope boundaries clarified (Q&A)
- Current problem statement focuses on humanoid-type UGV platform (not other physical form factors) and standardized commodized humanoid platform.
Requirements questions
- Payload: 25 kg and above
- Power/battery specifics: not disclosed during Q&A; to be answered later via follow-up
- Indigenous content: “Make in India category 2” targeted; category 1 acceptable
- Training: closed-loop training required for mission-specific behavior; plan to be defined during prototyping/TRL levels
DISK 14 (2 challenges total) shown during technical outreach
1) Manportable Alien System with ESM capabilities
Objective
- Soldier-portable (static rack-like / tripod mount antenna) ESM system to counter diverse evolving radar/emitters.
Frequency coverage
- 30 MHz to 40 GHz (lower band clarified from an earlier mistaken reading)
Direction finding & localization
- DF capability and geolocation using multiple measurements/techniques.
Key performance targets (Q&A)
- Example sensitivity target: ~ -70 dBm (noted as effective sensitivity over the full band)
- Sensitivity depends on bandwidth; requirement relates to effective operational sensitivity across wide 30 MHz–40 GHz coverage.
Deployment form
- “Manportable” does not necessarily mean backpack form; designed to transport and deploy quickly.
- Antenna mounting via tripod.
- Mast height not explicitly fixed (approx. ~5 m commonly used; not specified as strict).
Quantities
- Pilot project quantity: minimum 10 systems.
Sponsoring directorate
- Mentioned as PM2.
Included functionalities (as stated/clarified)
- Radar / RF fingerprinting
- Basic analytical function
- RF identification/classification approach supporting threat identification
2) Integrated Drone Management System for Monitoring & Decision Support
Operational need
- Drones operate in silos with isolated video feeds; lack unified aggregation/analysis.
Vision / concept
- Centralized command & control and a common operating picture across multiple drones.
- Real-time fusion of aerial/ground data into a unified dashboard.
- AI-driven decision support for commanders at all levels.
Architecture expectations
- Secure, resilient communications
- Interoperability
- Drone & mission management:
- fleet health monitoring
- mission planning
- task allocation
- control
Deployment questions (Q&A clarifications)
- Core integration at headquarters level, with intermediate modules in the tactical battle area (TBA) feeding HQ centrally.
Communication / control mode (Q&A clarifications)
- Hybrid model:
- two-way communication capability for authorized control users (not necessarily all)
- one-way monitoring for others
- Range:
- ballpark TBA-to-HQ coverage ~20–30 km mentioned, but not fixed
- secure and verified channel expected
- Vendor flexibility:
- vendor chooses secure architecture subject to verification/permissions (no confirmed fixed range)
Legacy vs new drones
- Both new and legacy drones should integrate.
- Manufacturer permissions required to alter drone software; organizers did not commit to that.
AI placement
- AI/analytics can be on:
- drone edge,
- server,
- or ground control station
- “One of platforms or all three” discussed.
Demo/requirements around existing systems
- For legacy, custom comm modules may be permissible to connect to HQ/GCS software.
Software integration constraints
- Some details depend on drone manufacturers and permissions.
Methodology / process steps emphasized (general outreach)
Application & selection flow
- After outreach: apply online
- Last date: 4th May (no extensions claimed in the discussion)
Sorting & selection
- Node/agency reviews applications depending on number received
- HPSC (High Power Selection Committee) performs detailed solution review and shortlisting
Winner declaration
- Provisional winners → refinement of PDS/PRU → final acceptance → winner declaration
Project lifecycle / milestones (stated structure)
- Total 6 milestones (Milestone 0 through Milestone 5; milestone numbering discussed informally)
Milestone outline
- Milestone 0: signing contract + initial requirements (including early contribution)
- Milestone 1–3: development of prototype
- Milestone 3: prototype developed
- Milestone 4: testing and certification
- Milestone 5: user trials
After milestone completion:
- composite testing → procurement via RFP stage
Funding / grant structure and matching contribution
Max grant
- DISK: up to ₹1.5 crore
- Aditi: up to ₹25 crore
Matching contribution
- Must be equal to or more than the grant amount.
Example given
- If PDB = ₹2 crore (DISK/Aditi context):
- grant ≈ ₹1 crore
- matching contribution ≈ ₹1 crore (or slightly more)
- If PDB = ₹4 crore:
- grant max up to ₹1.5 crore (DISK)
- remaining comes as matching contribution
Matching contribution payment timing
- Provided in stages.
- Milestone 0 may require early portion (startup side discussed example: ~10% of total PDB).
Application limits (running projects)
- A company can bid for maximum five challenges (application limit).
- Running projects limit:
- cannot run more than 1 Aditi project concurrently
- cannot run more than 5 DISK projects concurrently
- Certain relationships/ownership stakes can count as part of the same entity for limits (as clarified).
Where to submit questions / how responses are handled
- Submit queries to the provided Zoho email ID (spelled during Q&A).
- Responses from nodal officers may be delayed; not all participants get a broadcast response due to practicality.
Speakers / sources featured (as mentioned in subtitles)
Organizers / nodal officers / representatives
- Nodal officer (RT5) – 155 mm Terminally Guided Munition (Aditi 4) briefing
- Nodal officer (PMO Suraj) – Cognitive Electronic Warfare (Aditi 4) briefing (also linked with the manportable alien system in discussion)
- Nodal officer (infantry 7) – Humanoid for combat / Humanoid auto system briefing (some content delivered by another officer; “infantry 7” is stated as nodal)
- Nodal officer (IDEX/ADB staff; host/moderator “ma’am” and “sir”) – sequencing problem statements and general outreach management
- Nodal officer (PM2) – Manportable Alien System with ESM capabilities (DISK 14)
- Nodal officer for Integrated Drone Management System – described via DISK 14 briefing (specific name not clearly stated)
- Director / subject matter expert referenced – “director will give out” (no name)
Startup / innovator participants who asked questions (named)
- Shaavage (Blackstone Tactical) – questions on terminally guided munition
- Mr. Shen – questions during TGM Q&A
- Mr. Raju – questions on direction finding for cognitive EW
- Rohit Chanas (Huso Space Private Limited, Guwahati)
- Kai (MMRfic)
- Pravin Reddi (Astra Microwave)
- Karthik – asked about EW sensors / correlation & corroboration
- Zahir (Big Bang Boom Solutions)
- Vijendra (ADL)
- Sanu (Axelron)
- Anup (iotech world navigation private limited)
- Re (Meridian Data Labs)
- Faridan (General Autonomy)
- Bhanu (General Autonomy)
- Raju (Scient in the technology domain)
- Anil (ADSL)
- Sudar (Le defense system)
- Shakshi – asked about process/status (general outreach Q&A)
- Additional participants were present but some names were not fully legible.
Institution / program references
- IDEX / Innovation for Defence Excellence
- DIO (Defense Innovation Organisation)
- HPSC (High Power Selection Committee)
- DISK / Aditi programs and grant schemes
- Indian Army / stakeholders (as referenced in problem statements)
Category
Educational
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...