What Is IETM Software and Why Has One Platform Handled 125 Defence Projects in India?
If you're new to defence documentation, the acronym IETM might not mean much. But for anyone maintaining missile systems, warships, aircraft, or armoured vehicles, an IETM (Interactive Electronic Technical Manual) is often the difference between a five minutes fix and a five hour one.
Understanding IETM Traditional technical manuals are static: printed books, PDFs, or scanned documents that a technician has to search through manually. An IETM replaces that with an interactive digital format searchable, cross referenced, and often supported by visual diagrams, 3D models, and step by step fault diagnosis logic. In India, IETMs for defence equipment must follow the JSG 0852 standard, which defines four levels of interactivity, with Level 3 and Level 4 being the most advanced including features like linked troubleshooting trees and dynamic content.
Why defence relies on it so heavily Defence hardware is complex by nature. A single missile sub system or naval combat management system can have documentation running into thousands of pages. When something malfunctions, a technician working from paper manuals may need to cross reference multiple binders under time pressure. An IETM condenses that process search a fault code, follow linked steps, view a 3D exploded diagram of the component in question. That directly affects readiness and maintenance turnaround.
A case study in scale: 125 Defence IETM Projects One way to understand what large scale IETM adoption looks like in practice is through the work of Code and Pixels, an Indian company that has completed 125 Defence IETM Projects to date reportedly the highest volume delivered by any single Indian vendor under the JSG 0852 standard. Itβs in house platform, Quantum TechDocs, has been used across missile programs (Akash, Agni, ASTRA, BrahMos, MRSAM), naval shipyards (including Mazagon Dock and Cochin Shipyard), and a wide spread of equipment categories drones, artillery, radar and communication systems, and military vehicles.
What "125 projects" actually represents It's worth unpacking what that number means operationally. Each IETM project typically involves converting an OEM's existing technical documentation often thousands of pages of engineering drawings, maintenance procedures, and parts data into an interactive digital format that meets a specific defence standard, gets validated by the relevant service branch, and then gets deployed across potentially dozens of installation sites. Doing that 125 times, across programs as sensitive as missile systems and submarines, requires both software maturity and a large trained authoring team. In one instance, the team is reported to have produced 25,000 IETM pages in three months for Indian Air Force missile systems an indicator of the throughput such projects can demand.
Why in house, indigenous tooling matters here Much of India's earlier IETM work depended on foreign software or foreign standard formats like S1000D. As defence procurement increasingly favours indigenous solutions, an Indian built, JSG 0852 native platform has an inherent advantage not just on cost, but on data security and long-term support continuity, both of which matter more in defence contexts than in commercial software procurement.
The takeaway IETM software is a niche category, but its role in defence readiness is outsized relative to how little attention it gets outside the industry. The scale of work represented by 125 Defence IETM Projects across missiles, ships, aircraft systems, and vehicles offers a useful window into how much documentation infrastructure sits behind every operational defence platform, and why the software chosen to build it matters as much as the hardware itself.
