Documentation standards Vs IETM Standard EED-S-048 |DME 452 |NCD 1470 |JSS 251 |JSG 0852

Technical documentation is a very broad word used in tender documents/Scope Documents. They put the heading as Technical Documentation and in brackets write IETM Level 4 or IETM class 4 mentioning EED-S-048 OR DME 452 OR NCD 1470 JSS 0251 and JSG 0852 standards and ask OEM to deliver in DVDs and some sets of Hard copies.

Some SOTRs may even have Training Aids under Technical documentation.

Steps for Creating Technical Documentation

(step 1&2 is done by OEM and Step 3 is executed by the IETM Software Vendor)

Your Scope or SOTR shared by the Indian Navy to make IETM will have the Standard names i.e. EED-S-048 OR DME 452 OR NCD 1470.

Documentation Standards Vs IETM Standards

EED-S-048, DME 452, and NCD 1470:

are purely standards defined by the Navy guiding OEMs to follow these guidelines while making documentation. These are purely technical stuff, and only Defence scientists or technical teams of OEMs who were involved in the development of equipment/devices can prepare. They need domain expertise.

These are absolutely in no way relevant to IETM development.

By adhering to EED-S-048 OR DME 452 OR NCD 1470 these standards your technical team will make manuals i.e. User handbooks, Technical Manuals, Maintenance manuals, MRSL etc.

The content may be written poorly formatted by the domain experts as, aesthetically arranging and making a table of contents, header, footers etc. is not the work of technical people.

Once this content is written by the experts the documentation team will come to the picture.

These documents are re-arranged and re-formatted as per JSS – 0251 standards.

Following is the Sequence of Contents to Be Followed While Making Document:

• Front/cover page which is printed on thicker paper or laminated
• The title page is the same as the Front-page
• Record of changes
• List of other associated handbooks
• Safety warnings in red colour
• First-aid instructions
• Cautions & Notes
• Demolition instructions
• Change Notice
• List of contents
• List of illustrations
• Text/ content
• The separate card titled Illustrations
• Illustrations
• Sepaarte card titles Appendix “A” , B,C
• Appendix or appendices
• Back Cover Page

Once the document is made available this will be shared with DGQA and other competent authorities i.e. defence labs etc.

Once these documents are fully vetted they enter into to next phase which is IETM.

The approved PDFs will be shared with IETM vendors like us/code and pixels for converting to IETM based on JSG 0852 standard, which is the standard defined to make IETMs.

In short, the work of the IETM service provider starts, once your final manuals are frozen or vetted by the end client.

The IETM service provider is not an expert in the domain, and the IETM team consists of all the software development team like, Angular Java programmers, database engineers, content integrators, and Quality assurance team etc., and they are not experts in the domain hence what whatever manual is made available to the team they simply convert every line into database and creates Database of the manuals.

Article written by

G. Gopi Krishna

Code and Pixels

IETM R&D team