IDDM certification is issued by DDP / DPIIT. Always verify current Indigenous Content thresholds at ddpmod.gov.in. Buy (Indian-IDDM): highest-priority category under DAP 2020  ·  Made in India ≠ IDDM IDDM certification is issued by DDP / DPIIT. Always verify current Indigenous Content thresholds at ddpmod.gov.in. Buy (Indian-IDDM): highest-priority category under DAP 2020  ·  Made in India ≠ IDDM
Consultant's Ready Reckoner

IDDM

A Practical Guide to Buy (Indian–IDDM)

For defence startups, MSMEs, system integrators and OEMs. Fifty myths, a decision tree, worked examples and role-based checklists — built to keep you out of the gaps that stall most applications.

← DAP 2020 Procurement Guide DDP / IDDM Certification →
Foundation

What Is IDDM?

📘

IDDM (Indigenously Designed, Developed & Manufactured) is the highest-priority procurement category under India's Defence Acquisition Procedure (DAP). A product generally qualifies only when all four conditions below are met together — not any one of them in isolation. Remember: Made in India ≠ IDDM. Assembly alone does not constitute indigenous design.

01
Designed
In India — engineering ownership of architecture, not CAD files alone
02
Developed
In India — the prototype-to-qualification path runs domestically
03
Manufactured
In India — production, not just final assembly of imported kits
04
IC Threshold
Met — Indigenous Content requirements under applicable DAP provisions
Where first-time applicants go wrong

Stated vs. Actual — 12 of the 50 Myths

⚠️

The full handbook logs fifty myths. These twelve trip up the most first-time applicants — spanning design ownership, software IP, and procurement sequencing.

❌ What People Assume
1

Made in India means IDDM.

2

PCB fabrication counts as design.

3

Buying IP transfers design ownership.

4

Imported FPGA bitstreams are fine as-is.

5

iDEX winners get procurement orders automatically.

6

TRL-6 means production ready.

7

Foreign transfer of technology creates indigenous design.

8

Source code doesn't need configuration control.

9

GitHub code is free to commercialise.

10

The BOM alone proves indigenous content.

11

Any imported chip disqualifies the product.

12

Once compliant, future products auto-qualify.

✅ What Actually Holds
1

Manufacturing alone is insufficient.

2

PCB fabrication is manufacturing, not design.

3

Only if the IP is legally assigned.

4

Bitstream ownership is critical to the assessment.

5

Prototype success is not the same as procurement.

6

It is not — qualification still lies ahead.

7

Usually it does not.

8

Configuration control is mandatory.

9

Licences can impose real obligations.

10

Supporting evidence is required beyond the BOM.

11

Not necessarily — supply-chain realism is recognised.

12

Every product is evaluated independently.

One "no" collapses the case

The IDDM Decision Tree

🚨

This is a conjunction, not a checklist you can partially satisfy — a single "no" at any gate below ends the case for IDDM at that point.

1

Is the core design created in India?

Gate 1 · Engineering Ownership

If not, probability of IDDM qualification is low from the outset — this is the foundational gate.

2

Is the IP owned outright?

Gate 2 · Legal Ownership

Design created in-house means little if the underlying IP has not been legally assigned to your entity.

3

Is it developed in India?

Gate 3 · Development Path

The prototype-to-qualification journey — trials, iteration, engineering improvements — runs domestically.

4

Is it manufactured in India?

Gate 4 · Production

Production, not final assembly of an imported kit.

5

Is the required Indigenous Content achieved?

Gate 5 · IC Threshold

Meeting the prescribed IC% under applicable DAP provisions, with supporting evidence beyond the BOM.

🏆

Clear all five gates and the product becomes a likely candidate for Buy (Indian–IDDM) — India's highest-priority procurement category.

From idea to production

Roadmap: iDEX Idea → Buy (Indian–IDDM)

1

Identify Defence Need & Submit iDEX Proposal

Operational Need → Problem Statement

Every credible IDDM case starts with a validated operational need, not a technology looking for a buyer.

2

Selection, Grant & Concept Design

iDEX / Make / Internal R&D

Concept design work begins under the chosen funding route — grant-backed, industry-funded, or self-financed.

3

Prototype & Technology Demonstration

Prototype Development

A working prototype is built and demonstrated — the first real test of design and integration choices.

4

User Feedback & Field Trials

User Evaluation → Field Trials

Operational users test the prototype directly; feedback here shapes the next round of engineering.

5

Engineering Improvements

Design Improvements

Findings from trials are engineered back into the product — expect more than one iteration.

6

Environmental & EMI/EMC Qualification

Qualification

Certification is frequently a major schedule driver, not a formality — plan for it early.

7

Production & Manufacturing Readiness

Production Readiness

Manufacturing SOPs, supplier qualification and quality systems are proven out ahead of volume production.

8

Indigenous Content Verification & Procurement Engagement

Procurement Category Selection

IC% is verified against evidence, and the procurement category — ideally Buy (Indian-IDDM) — is confirmed.

9

Production, Acceptance & Lifecycle Support

Buy (Indian–IDDM) → Exports

Contracted production begins, followed by acceptance, warranty support, and — for many products — export potential.

Where the indigenous value actually sits

Worked Examples

💡

Across categories, the pattern repeats: imported RF/analog components paired with indigenous architecture and software. The competitive advantage rarely sits in the silicon.

Example 1

Software-Defined Radio

Strong IDDM potential
Imported
RFICFPGA
Indian
PCB designDSP algorithmsWaveformsIntegration
Example 2

Radar System

High indigenous value
Imported
ADCFPGARF amplifiers
Indian
AntennaSignal processingTracking softwareECCM algorithms
Example 3

Drone Platform

Conditional — evidence required
Imported
MotorsESCIMU
Indian
Flight controller SWMission computerAI navigationPayload integration

Potentially IDDM if indigenous design ownership and content requirements are demonstrated — not automatic.

Example 4

Electronic Warfare Receiver

High-value IP in software
Imported
RF components
Indian
Receiver architectureThreat libraryDetection algorithmsSignal classifier
Example 5

AI Surveillance System

Strong indigenous software content
Imported
CamerasGPU
Indian
AI modelsDatasetInference engineCommand software
Example 6

Tactical Communication Radio

Architecture-led indigenous value
Imported
RF front end
Indian
WaveformsEncryption*Network stackControl software

*Subject to applicable approvals.

Ten questions before you spend a rupee

Consultant's Go / No-Go Matrix

Do we own the design?YN
Do we own the software?YN
Do we own the firmware?YN
Is manufacturing in India?YN
Can we demonstrate indigenous content?YN
Is documentation complete?YN
Is configuration controlled?YN
Has qualification planning started?YN
Can we support lifecycle maintenance?YN
Can we defend our IP ownership?YN
9–10
Yes
Strong IDDM candidate
7–8
Yes
Address identified gaps before pursuing procurement
5–6
Yes
Significant technical and documentation work required
<5
Yes
Revisit product strategy before targeting Buy (Indian–IDDM)
Readiness by role

Checklists — Startup, MSME & OEM

🚀

Startup Checklist

Early-stage readiness

Problem statement validated

Customer identified

IP ownership documented

Design files controlled

Source code repository established

Cybersecurity incorporated

Indigenous supply chain mapped

Test plan created

Manufacturing partner identified

Financial sustainability assessed

🏭

MSME Checklist

Manufacturing & quality readiness

Configuration management

Approved BOM

Supplier qualification

Design documentation

Manufacturing SOPs

Quality Management System

Traceability

Environmental testing

EMI/EMC testing

Indigenous Content records

Warranty & support plan

⚙️

OEM Checklist

Systems & lifecycle readiness

System architecture

Safety analysis

Reliability engineering

Lifecycle costing

Obsolescence management

Supply chain resilience

Secure software development

Export compliance

Configuration audits

Product support ecosystem

Where applications stall

Common Roadblocks

Weak documentation Poor IP ownership Imported critical technology No configuration control Weak quality systems Insufficient testing Lack of user engagement Supply chain dependency Funding gaps Long procurement cycles Certification delays Unrealistic timelines
The essentials

Key Takeaways

🎯 Sovereign capability, not assembly

IDDM is about creating sovereign capability, not merely assembling products.

🏗️ Where the value actually sits

The greatest competitive advantage lies in owning system architecture, software, firmware, algorithms and integration know-how.

📋 Documentation is not bureaucracy

Documentation, configuration management, quality systems and traceability matter as much as engineering excellence.

⏱️ Align early, not at RFP time

Success requires aligning technology development with procurement policy from the earliest design stages.

🛤️ A journey, not a checkbox

Startups and MSMEs should treat IDDM as a long-term capability-building journey rather than a one-time compliance exercise.