Defence manufacturing is not ordinary manufacturing with extra paperwork. It is a discipline where a single missing airworthiness record can ground a fleet, where an export-control slip can trigger criminal liability, and where a programme worth hundreds of crores is billed against milestones an auditor will scrutinise line by line. An ERP built for automotive or generic discrete manufacturing simply does not carry the DNA for this. In more than a decade of implementing systems for aerospace and defence suppliers across the Bengaluru corridor and the wider Indian defence ecosystem, we have seen the same pattern repeat: the features that look optional on a sales slide are the ones that decide whether an audit passes or a delivery slips.
This guide walks through the ERP capabilities that genuinely matter for a defence manufacturer. For each one we explain what it is, why defence specifically needs it, and what to look for when you evaluate a platform. There are no invented benchmarks here, only the practical checklist we use with our own clients.
Why defence manufacturing breaks generic ERP
The defence supply chain sits at the intersection of three unforgiving worlds: airworthiness regulation, national security controls, and long-cycle programme finance. A part is not simply made and shipped. It is designed against a controlled configuration, manufactured through qualified special processes, inspected against a first-article baseline, traced by serial number for its entire service life, and eventually returned for maintenance decades later. Meanwhile the money attached to it flows through earned-value milestones, offset obligations and indigenous-content certificates that regulators and prime contractors verify independently.
Generic ERP handles inventory, purchasing and accounting competently. Where it fails a defence manufacturer is in the connective tissue: the ability to tie a financial milestone to a physical inspection, to lock a document behind an export-control flag, or to reconstruct the exact as-built configuration of a serial number shipped seven years ago. The features below are precisely that connective tissue. If you want the broader selection framework, our guide on how to choose ERP for aerospace and defence manufacturing sets the context; this article goes deep on the capabilities themselves.
Programme management with earned value (EVM) and milestone billing
Earned value management is the discipline of measuring project performance by comparing the value of work actually completed against what was planned and what was spent. In defence, contracts with the Ministry of Defence, DRDO labs and prime contractors are frequently structured around milestones and progress payments rather than a single delivery date.
Why defence needs it
A defence programme can run for years across dozens of work packages. Without EVM you are guessing at schedule and cost health until it is too late to recover. Milestone billing means revenue recognition and cash flow are tied to physical progress that a customer or auditor can independently verify. When a prime contractor disputes a progress claim, your ERP must produce the earned-value evidence that supports the invoice.
What to look for
Look for native work-breakdown-structure planning, the ability to define control accounts and work packages, and automatic calculation of the core indices: budgeted cost of work scheduled, budgeted cost of work performed, and actual cost of work performed. The system should generate schedule and cost variance and performance indices without a spreadsheet in the loop, and it should connect milestone completion directly to invoicing. Our aerospace programme management with EVM module is built precisely around this loop so that a completed milestone triggers a compliant, evidence-backed claim.
Offset and indigenisation content tracking
Under India's defence procurement policy, offset obligations require foreign vendors to reinvest a portion of contract value into the domestic industry, and indigenous-content thresholds under the various Make and Buy categories determine eligibility and pricing. Tracking these is a contractual and legal obligation, not a nicety.
Why defence needs it
Indigenous content percentage is calculated on the value of inputs, and it must be substantiated with supplier declarations, bills of material and cost breakdowns. If you cannot prove your indigenous content, you can lose eligibility or face penalties. Offset discharge has to be reported and banked against a schedule. This is finance, procurement and engineering data combined, and it lives naturally inside the ERP that already holds all three.
What to look for
Look for the ability to tag each purchased and manufactured item with its origin and value classification, roll indigenous content up through a multi-level bill of materials automatically, and generate the certificates and reports procurement authorities expect. The system should maintain an audit trail of supplier declarations so that a claimed percentage can be defended item by item. Suppliers to public-sector units will find this especially relevant; see our notes on ERP for defence PSU suppliers.
DGAQA and CEMILAC airworthiness records
The Directorate General of Aeronautical Quality Assurance and the Centre for Military Airworthiness and Certification are the twin pillars of Indian military airworthiness. DGAQA handles quality assurance and acceptance; CEMILAC handles design certification. Both demand a documented, retrievable trail of records for every airworthiness-critical item.
Why defence needs it
Airworthiness records are not filed and forgotten. During acceptance, and again during any incident investigation, an inspector will ask you to produce the material certifications, process records, inspection reports and concessions for a specific part or serial number. If the records are scattered across shared drives and email, you will fail. The ERP has to be the single system of record where a certificate of conformance is generated from the same data that governed manufacture.
What to look for
Look for structured document management linked to parts, orders and serial numbers, controlled concession and deviation workflows, and the ability to assemble a complete document package for a delivery on demand. Electronic signatures and a tamper-evident audit trail matter here. Our DGAQA and CEMILAC compliance software is designed so the airworthiness pack is a by-product of normal operations rather than a scramble before an audit.
Export control (ITAR and EAR) and role-based access security
Many defence components and their technical data are controlled under the United States International Traffic in Arms Regulations and Export Administration Regulations, alongside India's own SCOMET controls. Controlled technical data must never reach an unauthorised person, whether foreign national or unlicensed employee.
Why defence needs it
An export-control violation is not a commercial dispute; it can be a criminal matter and can bar you from future contracts. The obligation is continuous: drawings, specifications and even certain emails are controlled, and access must be restricted by nationality and need-to-know. Bolting this onto a system after the fact is fragile. It has to be enforced at the data layer.
What to look for
Look for granular role-based access control, the ability to flag items, documents and even individual fields as controlled, and enforcement that follows the data wherever it is viewed. Segregation by citizenship or clearance, full access logging, and integration with your document vault are essential. Our aerospace export-control ERP approach treats classification as a first-class attribute of every record.
Multi-level bill of materials and configuration control
A defence assembly is a deep, multi-level bill of materials, and it changes over its life through engineering change orders. Configuration control is the discipline of knowing exactly which revision of which part went into which serial number.
Why defence needs it
Interchangeability and safety depend on configuration integrity. When a design change is mandated, you must know every affected serial number in service, and you must be able to show the as-designed, as-built and as-maintained configurations distinctly. A generic single-level BOM cannot represent this, and a spreadsheet cannot enforce it.
What to look for
Look for effectivity-driven multi-level BOMs, engineering change management with impact analysis, and the ability to separate the as-designed baseline from the as-built record captured at manufacture. The system should answer, instantly, which serials contain a given revision. This is foundational, and it feeds nearly every other feature in this list.
AS9100 quality management and AS9102 first article inspection
AS9100 is the aerospace and defence quality management standard, built on ISO 9001 with additional requirements for risk, configuration, counterfeit-part prevention and product safety. AS9102 defines the first article inspection report, the formal verification that a production process yields a part matching every drawing characteristic.
Why defence needs it
AS9100 certification is frequently a contractual prerequisite. The standard demands closed-loop control of nonconformances, corrective actions and supplier quality, and it wants that control demonstrable through records. First article inspection is the gate that proves a new or changed process is capable before series production begins.
What to look for
Look for embedded nonconformance and corrective-action workflows, supplier quality management, and a structured AS9102 first-article module that captures every characteristic against its drawing balloon. Reusing quality data across the record rather than re-keying it is the mark of a mature system. See our AS9100 ERP software and the deeper walkthrough in AS9100 first article inspection and ERP compliance.
NADCAP special-process control
NADCAP is the industry accreditation for special processes such as heat treatment, welding, non-destructive testing, chemical processing and surface treatment. A special process is one whose result cannot be fully verified by later inspection, so the process itself must be tightly controlled.
Why defence needs it
Primes and airworthiness authorities increasingly require NADCAP accreditation for special processes, whether performed in-house or at a supplier. Control means qualified operators, calibrated equipment, validated parameters and complete process records for every part. Losing traceability of a heat-treatment cycle can scrap an entire batch.
What to look for
Look for the ability to define special-process specifications, enforce operator and equipment qualification at the point of work, capture process parameters and records against the part and serial, and manage the supplier accreditations for outsourced processing. Our NADCAP special-process control module ties each process record back to the traveller so nothing proceeds on an expired qualification.
Serial and lot traceability
Traceability is the ability to follow a part backward to its raw material and forward to the assembly and aircraft it serves. In defence this is genealogy, not a batch number on a label.
Why defence needs it
When a material defect or a counterfeit part is discovered, you must contain it precisely: which heats, which lots, which serials, in which assemblies, at which customers. Full bidirectional traceability turns a fleet-wide grounding into a targeted recall. It is also a direct AS9100 and airworthiness expectation.
What to look for
Look for serial and lot capture at every operation, raw-material heat and certificate linkage, and a genealogy view that spans from mill certificate to delivered assembly. The traceability data should be queryable in both directions in seconds. Explore our dedicated aerospace traceability software for how this is captured on the shop floor.
MRO and life-limited parts management
Maintenance, repair and overhaul is where a defence product spends most of its life. Life-limited parts have a mandated retirement based on flight hours, cycles or calendar time, and they must be tracked continuously.
Why defence needs it
A life-limited part flown beyond its limit is a safety and legal failure. MRO also demands the as-maintained configuration: every replacement, repair and modification recorded against the serial so the current build state is always known. This closes the loop from manufacturing traceability into decades of service.
What to look for
Look for life accumulation tracking against hours, cycles and calendar, automatic alerts before limits, and a maintenance record that updates the as-maintained configuration. Rotable pool management and repair-order workflows round out a capable module. Our aviation MRO software keeps the service history continuous with the original build record.
GST e-invoice and Indian tax compliance
Beyond the specialised controls, a defence manufacturer operating in India must still meet everyday statutory obligations, and GST e-invoicing is now mandatory above the notified turnover threshold.
Why defence needs it
Milestone billing, offset banking and progress payments all have to reconcile with valid, government-registered e-invoices. Getting this wrong stalls collections. Because defence invoicing is tied to earned-value milestones, the e-invoice must flow directly from the same programme and billing engine rather than a disconnected accounting tool.
What to look for
Look for native e-invoice generation with Invoice Registration Portal integration, e-way bill support, and seamless linkage from milestone completion to a compliant tax invoice. On a unified platform such as Zoho, this statutory layer sits alongside the programme and manufacturing modules rather than in a separate silo.
Defence ERP feature checklist
| Feature | Primary compliance or business driver | Key capability to verify |
|---|---|---|
| Programme management with EVM | Milestone billing, MoD and prime contracts | WBS, cost and schedule variance, milestone-to-invoice link |
| Offset and indigenisation tracking | Defence procurement policy | BOM-level content rollup and certificate generation |
| DGAQA and CEMILAC records | Military airworthiness | Serial-linked document packs and concession workflows |
| Export control and access security | ITAR, EAR, SCOMET | Role and nationality-based access, data-level flags, logging |
| Multi-level BOM and configuration | Interchangeability and safety | Effectivity, as-designed vs as-built, change impact analysis |
| AS9100 quality and AS9102 FAI | Quality certification | Closed-loop NCR and CAPA, ballooned first-article capture |
| NADCAP special-process control | Special-process integrity | Operator and equipment qualification, parameter records |
| Serial and lot traceability | Containment and recall | Bidirectional genealogy from heat to assembly |
| MRO and life-limited parts | In-service safety | Life accumulation alerts and as-maintained configuration |
| GST e-invoice | Indian tax statute | IRP integration linked to milestone billing |
How the features work together
The reason these capabilities belong in one ERP rather than ten point tools is that they share data. The multi-level BOM feeds indigenous-content rollup and configuration control. Serial traceability captured on the shop floor becomes the airworthiness record DGAQA asks for and the as-built baseline MRO maintains for decades. A completed EVM milestone triggers both revenue recognition and a GST e-invoice. Export-control flags ride on the same item master everyone already uses. When these live in separate systems, the joins fail exactly when an auditor is watching.
This is why we build defence solutions on a configured Zoho core extended with custom AWS services for the security-sensitive and airworthiness-critical requirements. It gives suppliers a unified backbone without forcing a rigid, foreign-hosted monolith. If you want to map these features against your own programmes, our overview of defence manufacturing ERP software and the broader aerospace and defence ERP software platform are the right starting points, and the aerospace ERP buying checklist turns this into a scorecard you can take into vendor demos.
Key Takeaways
- Generic ERP fails defence manufacturers in the connective tissue: linking financial milestones to physical inspections, locking data behind export-control flags, and reconstructing the as-built configuration of any serial number.
- The ten must-have capabilities are EVM programme management, offset and indigenisation tracking, DGAQA and CEMILAC records, export control with role-based security, multi-level BOM and configuration control, AS9100 with AS9102, NADCAP, serial and lot traceability, MRO with life-limited parts, and GST e-invoicing.
- These features matter because they share data: the BOM feeds content rollup and configuration, shop-floor traceability becomes the airworthiness record and the MRO baseline, and a completed milestone triggers both revenue and a compliant e-invoice.
- When evaluating a platform, verify enforcement at the data layer for export control, effectivity-driven multi-level BOMs, ballooned AS9102 capture, and bidirectional genealogy that queries in seconds.
- A unified backbone, such as a configured Zoho core extended with custom AWS services, gives suppliers integrated compliance without a rigid, foreign-hosted monolith.
Frequently Asked Questions
The essentials are programme management with earned value and milestone billing, offset and indigenisation content tracking, DGAQA and CEMILAC airworthiness records, export control with role-based security, multi-level BOM and configuration control, AS9100 quality with AS9102 first article inspection, NADCAP special-process control, serial and lot traceability, MRO with life-limited parts, and GST e-invoicing. These features share data, which is why they belong in one integrated ERP.
Yes. A defence-grade ERP becomes the single system of record for airworthiness. It links material certifications, process records, inspection reports and concessions to specific parts and serial numbers, so a complete document package can be assembled on demand during acceptance or an investigation. Electronic signatures and a tamper-evident audit trail make the records defensible.
Through granular role-based access control and data-level classification. Items, documents and even individual fields can be flagged as controlled, and access is restricted by need-to-know and, where required, by nationality. All access is logged. Enforcement happens at the data layer so the control follows the information wherever it is viewed, rather than being bolted on afterwards.
Earned value management measures project performance by comparing the value of completed work against the planned budget and the actual cost. A defence ERP uses a work breakdown structure to calculate schedule and cost variance and performance indices, then links milestone completion directly to invoicing. This gives auditable evidence for progress payments on long-cycle contracts.
The ERP tags each purchased and manufactured item with its origin and value, then rolls indigenous content up through the multi-level bill of materials automatically. It stores supplier declarations as an audit trail and generates the certificates procurement authorities expect, so a claimed indigenous-content percentage can be substantiated item by item.
Because interchangeability and safety depend on knowing exactly which revision of which part went into which serial number. Configuration control separates the as-designed baseline from the as-built and as-maintained records, and when a design change is mandated it identifies every affected serial in service. A single-level BOM or spreadsheet cannot enforce this.
For most defence contracts, yes. AS9100 is the aerospace and defence quality standard and is often a contractual prerequisite, demanding closed-loop control of nonconformances, corrective actions and supplier quality. AS9102 first article inspection formally verifies that a process produces a part matching every drawing characteristic before series production begins.
NADCAP accredits special processes such as heat treatment, welding and non-destructive testing, whose results cannot be fully verified by later inspection. The ERP enforces operator and equipment qualification at the point of work, captures process parameters against the part and serial, and manages supplier accreditations, so nothing proceeds on an expired qualification.
Traceability in defence is full genealogy, not just a batch label. It links raw-material heats and certificates forward through every operation to the assembly and aircraft, and backward from any serial. When a defect or counterfeit part is found, this bidirectional trace turns a fleet-wide grounding into a precisely targeted recall.
The ERP tracks life accumulation against flight hours, cycles and calendar time, alerts before a limit is reached, and records every replacement and repair against the serial to keep the as-maintained configuration current. This closes the loop from original manufacturing traceability into decades of in-service maintenance.
Yes, and it should. Because defence invoicing is tied to earned-value milestones, the GST e-invoice must flow from the same programme and billing engine, with Invoice Registration Portal and e-way bill integration. On a unified platform the statutory tax layer sits alongside the programme and manufacturing modules rather than in a disconnected accounting silo.
Suppliers to public-sector units like HAL, BEL and BDL face the same airworthiness, traceability and indigenous-content demands as the primes, often with tighter documentation expectations. A specialised defence ERP lets them meet these obligations without a large in-house compliance team, and integrates the offset and content reporting their customers require.
Conclusion
Choosing an ERP for defence manufacturing is really a decision about evidence: can the system produce, on demand, the earned-value claim, the airworthiness pack, the indigenous-content certificate and the serial genealogy that a regulator, a prime contractor or an auditor will ask to see? The features in this checklist are not a wish list; they are the operational reality of building for the armed forces, and the ones that look optional are usually the ones that decide an audit. Evaluate every platform against how these capabilities share data rather than how they demo in isolation, because the joins between modules are exactly where compliance is won or lost. If you would like to map these features against your own programmes and shop floor, the team at Elite Tech Corporation works with aerospace and defence suppliers every day and would be glad to help you build a scorecard that fits your contracts.Ready to run your A&D plant on one platform?
Talk to our Bangalore team, or book a free demo and see it on your own BOM.