Why India's Defence IETMs Are Underused and How AI Is Fixing It
Underused and How AI Is Fixing It Anyone who has worked around India's defence documentation ecosystem has heard some version of the same complaint: technicians keep reaching for the printed manual instead of the digital one. It sounds counterintuitive. Interactive Electronic Technical Manuals, or IETMs, were supposed to replace paper entirely. Yet on many programs, the "smart" system sits unused while engineers flip through binders. The reason isn't that IETMs are a bad idea. It's that most defence platforms are far more complicated than a single IETM was ever designed to handle. Take a naval vessel, a missile system, or an armoured vehicle. None of these are built by one company. A single platform typically pulls together components from dozens sometimes over a hundred original equipment manufacturers. Radar units, hydraulic assemblies, communication CODEANDPIXELS.NET IETM@CODEANDPIXELS.NET 9849527706 Page 2
supplier, and each supplier is often required to deliver its own IETM as part of the contract. The result is a platform that doesn't have one technical manual. It has a hundred of them, none of which talk to each other. Every one of these IETMs is built independently, with its own interface, its own navigation logic, its own database structure, and its own installation process. On paper, this satisfies the documentation requirement. In practice, it creates a serious operational problem. When a technician is troubleshooting a fault that spans multiple subsystems which is common on complex platforms there's no single place to search. They have to open manual after manual, one at a time, hoping the right one has the answer. There's also a cost problem sitting underneath all of this. Converting thousands of pages of technical content into structured, searchable databases is slow and expensive. Industry experience suggests that for large programs running into tens of thousands of pages, database conversion alone can run into the lakhs before any software licensing or implementation cost is added. For a smaller OEM supplying, say, ₹5 lakh worth of equipment, being asked to build a full S1000D style IETM at a comparable cost simply doesn't make business sense. Multiply that friction across a hundred suppliers on one program, and it's easy to see why so many IETMs end up half-used at best. This is the gap that AI-powered IETMs are now being built to close. Rather than treating each subsystem's documentation as an island, the newer generation of platforms such as Quantum Tech Docs PRO from Code and Pixels, built on India's JSG 0852 standard is designed to let engineers search across multiple systems using natural language, the same way they'd ask a question to an assistant rather than hunt through a table of contents. The pitch is straightforward: faster information retrieval, simplified deployment (some platforms claim implementation in as little as five days), and a more connected experience across OEM supplied content, without demanding that every supplier rebuild their documentation from scratch. Whether this fully solves the underlying fragmentation problem across an entire program remains to be proven at scale. But the direction is hard to argue with. Defence maintenance teams increasingly expect to ask a question and get an answer, not navigate a hundred separate applications to find one. As AI capabilities mature, technical documentation that can't keep up with that expectation risks becoming exactly what IETMs were meant to replace: another manual nobody opens. CODEANDPIXELS.NET IETM@CODEANDPIXELS.NET 9849527706 Page 3
IETM@CODEANDPIXELS.NET 9849527706 Page 4
Fleepit Digital © 2021