Media Hub by Drone Federation India

DAP 2026: A Structural Reset for Design-Led Defence Manufacturing

Article

Key Takeaways

• Indigenous Design now requires demonstrable ownership of source code and technical artefacts

• Indigenous Content is tiered, auditable, and linked to enforceable penalties

• TRL banding now determines acquisition route

• Low Cost Capital Acquisition ( LCCA) enables capped, accelerated induction

• Long Term Bulk Acquisition ( LTBA) institutionalises tranche-based scaling with progressive indigenisation

• FDI eligibility is now tied to Indian ownership and control

• Exportability becomes an acquisition objective

Modern war punishes delay. Procurement systems that take years to decide are already obsolete by the time contracts are signed. The conflicts in Ukraine and the Middle East have demonstrated that supply chains can be disrupted, spares withheld, and technologies rendered strategically contingent. Industrial dependency is no longer an economic inconvenience; it is a vulnerability. Against this backdrop, India’s Draft DAP 2026 must be read not as procedural revision, but as a recalibration of strategic posture. It reframes acquisition as an instrument of sovereign readiness.

The earlier emphasis on “Buy Indian” as a preferential pathway has given way to an unmistakable mandate for “Design Indian.” Manufacturing within borders is no longer sufficient. What matters now is architectural control: ownership of source code, custody of critical design data, and the authority to upgrade without external permission. Co-development replaces licensed assembly. Intellectual property is treated as strategic capital, not contractual residue. This is the hard pivot from transactional indigenisation to industrial sovereignty.

That pivot is reinforced through structural mechanisms like Indigenous Content calculation, which is no longer a declaratory percentage but a rigorously computed and auditable metric. It is designed to harden the military-industrial spine by compelling depth in materials, subsystems, and software layers.

Simultaneously, the institutionalisation of spiral development recognises that capability cannot be frozen at the moment of contract. Platforms must evolve in blocks, integrating upgrades across their life cycle. Additionally, the formal adoption of Technology Readiness Level classifications signals institutional maturity, as acquisition decisions are now anchored in demonstrable technological preparedness rather than aspirational claims.

Time discipline is another axis of reform. Digitised workflows, monitored timelines from RFI onward, and compressed decision loops are intended to reduce procedural drag. Crucially, the framework also aligns acquisition with exportability. Indigenous platforms are to be conceived not merely for domestic absorption but for global markets, converting technological competence into strategic depth.

From Transfer of Technology to Design Authority

The shift is explicit: from Transfer of Technology arrangements that permitted assembly within

India, to verified ownership of the underlying technology itself. Under DAP 2020, ToT-heavy structures could qualify as indigenisation even when upgrade authority, source code control, or core design IP remained abroad. DAP 2026 closes that gap. It defines Indigenous Design not as a label, but as demonstrable technical custody. Clause 26.1.1 requires vendors to prove ownership or availability of complete technical artefacts , including design layouts, drawings, circuit diagrams, Gerber files, and source codes for integration software and firmware. Thus, designs merely licensed from foreign third parties no longer qualify. Indigenisation must now survive forensic scrutiny.

The logic is strategic. Platforms increasingly derive combat effectiveness from software, embedded systems, and iterative upgrades rather than static hardware. Without source code retention and upgrade authority, India would remain dependent on foreign OEMs for every modification cycle. By mandating proof of technical ownership and tying compliance to enforceable penalties, DAP 2026 converts intellectual property from a commercial consideration into a sovereign asset.

Control of Code is Control of Capability

Beyond compliance and penalties, Draft DAP 2026 introduces an incentive architecture to actively reward Indigenous Design. Clause 26.7 operationalises this shift by embedding design ownership directly into price discovery. Vendors that meet Indigenous Design requirements for the main system may receive a credit score of up to ten percent in L1 determination , with additional credits for qualifying subsystems and components, subject to a cumulative ceiling. This is not symbolic encouragement, it has potential to materially alter competitive outcomes.

A technically superior, design-owning firm can offset marginal price disadvantages through structured evaluation credits. Crucially, these incentives are conditional upon demonstrable intellectual property protection under Indian law.(registered patents, designs, semiconductor layout registrations, copyrights, trademarks, and trade secrets). The burden of proof rests squarely on the vendor. In turn, Indigenous Design is therefore not self-declared but must be legally defensible and technically auditable. By tying price competitiveness to verifiable IP ownership, the draft converts design depth into a procurement advantage.

Indigenous Content Calculation Becomes Tiered and Structured

Alongside emphasis on design ownership, Draft DAP 2026 undertakes a quiet but consequential rationalisation of Indigenous Content (IC) calculation. What was earlier a percentage benchmark has now been converted into a tiered, structured accounting architecture. The revised formula introduces a new category “C” to capture raw materials, components, sub-systems, LRUs, or software that originate in India but are exported and subsequently re-imported as part of foreign goods. By requiring documented export certificates, re-import records, and a verifiable traceability chain, the revised provision clarifies how such re-imported indigenous inputs are to be treated in IC computation. Rather than relying on broad origin claims, there is recognition of these inputs through documented deduction from foreign content.

Additionally, IC thresholds have simultaneously been recalibrated. The Buy (Indian-IDDM) category now carries a higher indigenous content requirement (from 50% to 60%) , with a new 30% floor at trials stage. While Buy (Global) procurements are no longer exempt from local value obligations, now carry a 30% IC requirement.

The rationalisation extends beyond thresholds to incentives and enforcement for same. Clause 27.9 introduces structured rewards: percentage-linked incentives for use of indigenous military-grade raw materials, domestic manufacture of components and LRUs, and absorption of identified critical technologies. These rewards are capped, cumulative, and subject to verification prior to payment. At the same time, Clause 26.8 tightens compliance. Vendors must submit documentary proof of IC adherence; failure to substantiate claims may result in non-compliance determinations and even forfeiture of earnest money deposits . The burden of proof rests squarely on the bidder.

Thus, the revised IC regime shifts the debate from nominal localisation to verifiable industrial depth. It rewards material integration, technology absorption, and supply-chain consolidation, while penalising cosmetic value addition. Indigenous Content is no longer arithmetic, it is audited industrial capability.

Rationalisation of Acquisition Procedures

Draft DAP 2026 also undertakes a structural rationalisation of acquisition categories, reducing procedural fragmentation and aligning entry routes with technological maturity. The earlier distinction between Buy (Indian) and Buy & Make (Indian) has now been consolidated into a unified “Buy (Indian) and Manufacture in India” category, with a defined indigenous content requirement anchored to the manufacturing portion. This consolidation simplifies the procurement architecture by removing artificial distinctions between outright domestic procurement and phased manufacturing arrangements, while tightening the emphasis on substantive local production. It reflects an institutional recognition that fragmented categories created interpretational ambiguity and diluted accountability.

Procurement Has Become Industrial Policy

More significantly, Draft DAP 2026 embeds Technology Readiness Level (TRL) bands directly into acquisition categorisation . TRL is no longer a peripheral reference confined to development cases. It now functions as a determinant of acquisition route. Products in early TRL bands are channelled into Make or D&D categories, while production-qualified systems fall within Buy or Buy & Manufacture pathways. This alignment ensures that technological maturity, rather than vendor preference, governs category placement.

Prioritisation of TRL banding is also reflected in the Annual Acquisition Plan and its linkage to certification mechanisms such as NETRA/NTRAF. Certification is therefore not advisory, instead it becomes a gatekeeping instrument. By tying acquisition routes to demonstrable readiness levels, the draft reduces discretionary categorisation.

The draft also resets the competition architecture in development cases. In Make-II projects, where fewer than three vendors emerge after feasibility assessment, the Request for Expression of Interest must now be publicly advertised on platforms such as SRIJAN-DEEP . At the same time, a single-respondent case is no longer automatically treated as restrictive, in such a case, the project may proceed if justified. This flexibility reflects that while competitive canvassing is mandated but at the same time there is scope for operational momentum.

This approach to competition finds further expression in Clause 21.2.1 governing the Buy (Indian-IDDM) category. The draft mandates that SHQ recommend IDDM where two or more qualified Indian vendors meet the defining attributes of indigenous design, content, and trial readiness. Yet, even where only a single Indian vendor qualifies, the category does not automatically collapse into a restrictive procurement route. Instead, the acquisition may proceed as an ab-initio single-vendor case , provided the system demonstrates certified technological maturity within the prescribed TRL band. The burden of establishing that maturity rests squarely with the vendor. Where credible domestic capability exists, procedural orthodoxy will not obstruct induction.

Application of Spiral Development Principle

The treatment of spiral development in Draft DAP 2026 marks a structural departure from its earlier articulation in DAP 2020. Under DAP 2020, spiral progression appeared within the Make/iDEX framework as a post-prototype extension mechanism tied to Minimum Pilot Order quantities. It merely functioned as an operational scaling device after initial success.

By contrast, Draft DAP 2026 institutionalises spiral development at the architecture stage of procurement itself. Clause 6 of Chapter III requires that the spiral approach be identified during the Feasibility Study, with PSQRs for all anticipated spiral stages defined upfront and the tentative minimum order quantity articulated at the EoI stage.

More consequentially, Clause 6.2 permits progression to subsequent spiral stages without requiring a fresh Approval-in-Principle, provided operational relevance persists. This procedural compression reduces approval friction and embeds evolutionary capability planning into the acquisition lifecycle ab initio rather than as an afterthought.

Also, successful Development Agencies from the initial stage automatically qualify for subsequent spirals, signalling intent to ensure vendor continuity. Thus, spiral development transitions from a flexible extension tool to a pre-planned capability ladder, preventing capability freeze in an era where technological relevance decays rapidly.

In alignment with the spiral development principle, the introduction of Low Cost Capital Acquisition (LCCA), gives way to a limited-quantity induction pathway. Under LCCA, the Services may place initial orders of up to ₹75 crore per case , within an aggregate annual ceiling of ₹2,000 crore, enabling operational exploitation before committing to scale. If the equipment performs satisfactorily in field conditions, bulk procurement may proceed through regular Chapter II Buy procedures without fresh trials or evaluation after induction. This materially compresses the transition from validation to volume.

The mechanism is further distinguished by its suo motu provision , permitting vendors to directly approach Service Headquarters with product proposals. Such proposals must be published for a 30-day challenge window, and if challengers emerge, quantities may be apportioned. Interestingly, the original proposer retains the right to match the lowest counter-bid. This enables competition while preserving first-mover advantage. Notably, the AoN validity under LCCA is restricted to two months, and contracts are to be concluded within four months of AoN, reinforcing fast-paced decision cycles. LCCA by enabling limited induction, generates operational data, which then enables acquisition at scale.

Draft DAP 2026 simultaneously introduces Long Term Bulk Acquisition (LTBA) as a structured pathway for capital-intensive, high-technology systems requiring sustained induction and periodic upgrades. As defined in Clause 19.1 and elaborated in Clause 93-95 , LTBA enables procurement in multiple tranches long term, with progressive indigenisation and SQR upgrades built into the framework. The first AoN must specify the total long-term requirement, with subsequent tranches drawn from this approved envelope. A full Field Evaluation Trial is conducted only in the first tranche, and later tranches rely on limited validation trials linked to upgraded SQRs. Indigenous Content may be increased tranche-wise. Competitive selection (L1 and L2 with quantity split) occurs in the first tranche, while subsequent tranches are confined to these vendors with commercial bids alone.

Basically, LCCA and LTBA operate at different points of the capability lifecycle. While LCCA accelerates entry through capped, rapid induction, on the other hand, LTBA enables long-term expansion through pre-approved, tranche-based scaling with upgrade and indigenisation logic factored. Thu,s creating a continuum from operational experimentation to sustained strategic depth.

MRO as a Gatekeeping Criterion

The logic of spiral development in Draft DAP 2026 is further bolstered by facilitating lifecycle sustainment. A comparison of DAP 2020 and Draft DAP 2026 reveals a subtle but meaningful elevation of Maintenance, Repair and Overhaul (MRO) from a largely procedural sustainment function to a highlighted component of capital acquisition strategy.

A more precise reading of Draft DAP 2026 shows that the shift in MRO positioning is not merely in OCPP placement, but in Clause 21.1 itself. The newly introduced Categorisation Matrix requires Service Headquarters to assess vendor capability across defined parameters before determining the acquisition route. The parameters include Technology Readiness Levels, Manufacturing Readiness Levels, Indigenous Content deliverability, and MRO infrastructure . This is significant because sustainment capability is no longer a downstream contractual consideration; it now becomes an upstream determinant influencing category selection and feasibility assessment. By embedding MRO infrastructure into pre-AoN categorisation logic, Draft DAP 2026 weaves lifecycle support to indigenisation credibility and acquisition planning.

This shift strengthens the foundations of a self-sufficient defence supply chain by incentivising vendors to build in-country MRO ecosystems at the outset, though it also raises the compliance threshold for firms lacking domestic sustainment infrastructure.

Foreign Investment Policy and Export Orientation

Draft DAP 2026 recasts the FDI-indigenisation balance by tightening the definition of an “Indian vendor” and inserts ownership and control thresholds directly into eligibility criteria. Under DAP 2020, defence manufacturing could attract up to 74% FDI under the broader industrial policy framework, reflecting a “Manufacture in India” orientation that permitted significant foreign equity participation.

The Draft 2026 framework, however, through Clauses 23.1 and 23.2 , restricts effective foreign ownership to a ceiling of 49% and explicitly disallows pyramiding of FDI through layered Indian holding structures. This shift is procedural as eligibility under priority acquisition categories now hinges on demonstrable Indian ownership and control, not merely location of manufacture.

By hard-coding equity caps and control conditions into vendor qualification norms, DAP 2026 narrows the pathway for foreign OEM-dominated subsidiaries to qualify as “Indian” for higher-preference categories, thereby aligning procurement benefits with domestic capital control.

Alongside tighter ownership norms, Draft DAP 2026 moves exportability from an aspirational outcome to an acquisition objective. The Preamble explicitly sets a target of ₹50,000 crore in annual defence exports by 2030 , scaling higher by 2036, and states that “exportability” will become a desirable Qualitative Requirement in the development of new platforms. This is reinforced procedurally through Clause 26.1.2 , which mandates that Indigenous Design must carry unrestricted operational rights to manufacture, sell, upgrade, develop next-generation variants and export (with Government approval) without dependence on foreign OEMs.

Exportability Now Begins at Architecture Stage

Further, Clause 34 catapults export credibility by providing formal certification mechanisms such as “Fit for Indian Military Use,” “Fit as per Vendor Certification,” and “Certificate of Field Trial Outcome”, issued through DGQA or competent authorities. These certificates are designed to enhance confidence among foreign buyers by linking exportable products to verified domestic trials and standards.

Additionally, export outcomes are acknowledged within the Make and Strategic Partnership procedures as part of the broader industrial objective. Together, these provisions convert exportability to a critical factor for acquisition planning, tying ownership, certification, and design control directly to India’s export ambitions.

Unresolved Tensions in the Sovereignty Architecture

Draft DAP 2026 represents a decisive shift toward design ownership, structured indigenisation, and supply chain resilience. Yet several blindspots remain that merit consideration as the policy matures.

First, upstream component sovereignty remains underdeveloped. While the draft tightens Indigenous Content (IC) computation and enforces design ownership, it does not establish a framework for securing critical upstream inputs, such as semiconductors, advanced sensors, or specialised materials. IC verification and progressive indigenisation mechanisms (including tranche-based increases under LTBA) deepen domestic value addition, but they stop short of mandating substitution of import of critical components.

Second, wartime production elasticity lacks formal architecture. The draft includes mechanisms like Fast-Track procedures, Spiral Development, LCCA, and LTBA, each of which can accelerate induction or enable phased scaling. However, there is no explicit production surge doctrine, pre-approved stockpiling model, or capacity reservation mechanism for high-consumption systems.

Third, liability asymmetry persists in foreign OEM participation . The draft sharpens Indigenous Design verification and IC compliance, placing documentary and financial onus squarely on Indian vendors. While this enhances accountability domestically, corresponding enforceable obligations on foreign OEMs participating through Indian entities remain comparatively limited.

Fourth, pre-award IP protection mechanisms are not comprehensively codified. Although ownership, source code retention, and IPR documentation are tightly defined post-award, the framework does not clearly standardise non-disclosure tiers or information access controls at the RFI and vendor interaction stages. This creates residual exposure during exploratory procurement phases.

Fifth, financial access reform is partial. The move toward reimbursable NCNC trials and EMD exemptions signals recognition of capital constraints faced by MSMEs and startups. However, the detailed reimbursement policy remains pending.

Sixth, interoperability standards are not structurally mandated. While TRL/MRL banding and categorisation matrices introduce discipline, the draft does not codify open architecture or interface standards to ensure seamless integration across platforms and command networks.

Finally, industrial licensing friction remains external to acquisition reform. DAP 2026 modernises procurement but does not rationalise licensing thresholds or compliance layering that affect high-technology entrants such as AI-driven autonomous systems developers, semiconductor design firms, electronic warfare startups etc.

Taken together, DAP 2026 strengthens design control and acquisition discipline. The next phase must integrate component resilience, surge capacity and financial support to complete the sovereignty architecture it has begun to build.

What This Means for India’s Drone and Autonomous Systems Ecosystem

The implications of Draft DAP 2026 are particularly significant for software-defined systems such as drones, loitering munitions, counter-UAS platforms, and AI-enabled ISR networks. In these domains, capability is driven less by hardware and more by control over code, firmware, and system architecture. By mandating demonstrable custody of source code and core design artefacts, the draft shifts advantage toward firms that build in India rather than merely assemble. Licensed integration without upgrade authority will carry diminishing strategic value. Design ownership becomes the decisive differentiator.

At the same time, TRL banding, spiral development, and LCCA pathways align closely with the rapid innovation cycles typical of unmanned systems. Limited-quantity induction, iterative upgrades, and structured scaling create a bridge between startup innovation and operational deployment. Coupled with stricter Indigenous Content verification and export-linked design rights, the framework signals that the future of India’s drone ecosystem will rest not on localisation alone, but on demonstrable technological and supply-chain control.

Page: https://www.dronefederation.in/media-hub/dap-2026-a-structural-rest-for-design-led-defence-manufacturing