MIL-STD-40051-1, explained

MIL-STD-40051-1 was the Army's standard for Interactive Electronic Technical Manuals (IETMs), Part 1 of the two-part MIL-STD-40051. The ASSIST-QuickSearch record kept by the Defense Logistics Agency titles it Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs), gives a base date of October 15, 2004, and shows it canceled on March 25, 2025 and superseded by MIL-STD-40051E. For twenty years the standard said what an Army or Marine Corps IETM had to contain, how it was divided into work packages, how its data was tagged in Extensible Markup Language (XML), and, through a functionality matrix in Appendix A, which interactive features a program was buying. Searchers type "mil-std 40051 ietm", "army ietm standard", and "40051-1d"; this post covers the scope and sections, the work package concept, the functionality matrix and its complexity factors, the XML and Document Type Definition (DTD) requirements, the revision history from the 2004 base through Revision D, the cancellation, and what someone holding a contract that cites 40051-1 should check. The companion post on the U.S. technical manual standards places the standard among MIL-STD-3001, MIL-STD-38784, and S1000D.

What MIL-STD-40051-1 covered

The ASSIST scope says the standard established technical content, style, format, and functionality requirements for IETMs for major weapon systems and their related systems, subsystems, equipment, assemblies, components, shop replaceable units, and line replaceable units. The list of publication types is long: operator and maintenance manuals, Depot Maintenance Work Requirements (DMWRs) and National Maintenance Work Requirements (NMWRs), preventive maintenance checklists and services, phased maintenance inspections, lubrication orders, battle damage assessment and repair manuals, software manuals, hand receipts, ammunition data sheets, and technical bulletins. The requirements applied at all maintenance levels through depot overhaul. The scope also points to MIL-HDBK-1222G for preferred style and format, to be followed unless it conflicts with the standard. ASSIST places the document in the TMSS area for technical manual specifications and standards, with the Army Materiel Command, Life Cycle Sustainment Division as preparing activity, lead standardization activity, and Army custodian, and coordination level Limited.

The text of Revision B, dated November 30, 2012 and hosted by EverySpec, is the version quoted in this post. The foreword says the standard is approved for the Department of the Army and the United States Marine Corps and available to all departments and agencies of the Department of Defense (DoD), and that the terms technical manual and equipment publication are synonymous. Paragraph 1.2 explains the service prefixes that run through the document: (A) Army, (N) Navy, (MC) Marine Corps only, and (F) Air Force, with unprefixed text applying to all. Paragraph 1.3 adds that technical information prepared under the standard and MIL-STD-3008 can feed external systems that collect operations, maintenance, and parts requisition data.

Section 4 lays out the structure. Paragraph 4.1 puts IETM functionality requirements in 4.7, style and format in 4.9, and technical content in eleven appendixes: Appendix B for general information, equipment description, and theory of operation; C for operator instructions, except aviation; D for troubleshooting procedures; E for maintenance instructions; F for parts information; G for supporting information; H for destruction of Army materiel to prevent enemy use; I for battle damage assessment and repair; J for the preventive maintenance checklist; K for lubrication orders; and L for the DMWR for maintenance and demilitarization of ammunition. Appendix A, discussed below, holds the functionality requirements and the content selection matrixes that tailor the rest. Paragraph 4.3 makes selective application and tailoring the acquiring activity's responsibility and says it shall be done through Appendix A.

The work package concept

The work package is the unit of an Army technical manual, in paper or on a screen. Paragraph 3.156 of Revision B defines a work package as information functionally divided into tasks in the logical order of work sequence; work packages should stand alone and may contain one or more tasks. If a program such as Condition Based Maintenance needs to capture individual task times or personnel, a maintenance work package must contain only one task. The definition then lists the work package types the standard covers, which match the appendixes: general information, operator instructions, troubleshooting procedures, maintenance instructions, parts information, supporting information, destruction, battle damage assessment and repair, and the rest.

Paragraph 4.9.1 says the style and format rules exist to support the work package concept, which it defines as "a logical combination of requirements and improved presentation techniques" designed to enhance the digital display of frame-formatted pages. A work package IETM supports individual functional information, including troubleshooting and maintenance tasks, for a weapon system or equipment. Paragraph 4.9.2 gives the hierarchy: an IETM consists of introductory matter, planning data, and a series of work packages holding descriptive information and principles of operation, troubleshooting information, procedural information for operator and maintenance tasks, parts information, and supporting information. Paragraph 4.9.2.1 repeats that work packages may contain one or more tasks, that tasks with different initial setups shall not be grouped, and that MIL-HDBK-1222 gives further guidance on work package development.

Every work package gets a permanent identifier. Paragraph 4.9.6.1 requires a unique work package identification number, assigned when the document instance is prepared under the DTD and never changed through the life of the work package, even when it is reused in another manual. The number has three parts: an alpha designator for the type of information, a five-digit block number assigned by the acquiring activity, and the IETM number without its maintenance level dash numbers. The designators are G for general information, O for operator instructions, T for troubleshooting procedures, M for maintenance instructions, R for parts information, and S for supporting information. The identifier may appear on the user's viewer and may be used for database retrieval; the IETM number inside it serves only to make the identifier unique and, the standard says, has no other significance.

The same concept appears in the page-based part, where work packages begin on a right-hand page and are limited in length; the differences are covered in the post on MIL-STD-40051-2. What the IETM part adds is a set of display rules. Paragraph 4.9.4 says an alert shall be a warning or a caution, used only in tasks, procedures, and steps, and displayed inline as a message dialog box or as a pop-up dialog box whose only button is OK. Paragraph 4.9.4.1 defines a warning as identifying a clear danger of injury or death and 4.9.4.2 a caution as identifying risk of damage to equipment. When several apply, warnings come first, then cautions, then notes.

The functionality matrix and complexity factors

Appendix A is the part of MIL-STD-40051-1 that has no counterpart in the page-based standard. Paragraph A.1.1 says the appendix covers IETM functionality and data display, which it calls look and feel, and provides the technical content selection for all major weapon systems and equipment, and that it is a mandatory part of the standard. Paragraph A.4.2 sets the physical screen layout: an inner shell, the client application display area that the manual author controls, and an optional outer shell that surrounds it, which the author should not attempt to modify unless the acquiring activity requires an outer shell, though the title bar shall be modifiable. A.3 defines the vocabulary the matrix uses, from annotations and audit trails through context filtering, hotspots, logic engine, portable maintenance aid, and session control.

Paragraph A.5.2 introduces the functionality matrix, TABLE A-XVII, as a way to let IETM programs define their requirements "in language that is accepted and understood by industry." Paragraph A.5.2.1 explains the pricing strategy behind it: in a competitive bid, bidders price against the matrix the acquiring activity filled out, or return a completed matrix with prices, so that the acquisition officer can compare bids feature by feature and trade higher-cost functionality against lower-cost options. Paragraph A.5.2.2 names the columns: complexity factor, category, functionality, requirement, and paragraph reference. In the requirement column the acquiring activity enters R for required, NR for not required, or O for optional content that may be required later but cannot be determined at contract time.

The complexity factor is defined in A.5.2.2.1 as a relatively weighted number assigned to each feature within a functionality category to indicate its abstracted complexity compared with the other features in that category. A factor of 1 is the baseline, and every other value is a projected complexity that many times greater than 1. The standard's own example is that Full Word Search in the Navigational category is a 1 while Key Word Search is a 2, so Key Word Search is considered twice as difficult to develop. The paragraph then warns that Local Data Annotation, also a 2, cannot be compared with either search feature because it sits in the Annotation category. Paragraphs A.5.2.2.1.1 and A.5.2.2.1.2 give separate factors for linear and non-linear IETMs: a fully formatted book version is less complex for a linear IETM, Filter by Model Series is less complex for a non-linear one, and some features are marked NA where a linear IETM cannot perform them.

TABLE A-XVI lists twelve categories by code: Ac Access, An Annotation, DD Delivery and Distribution, DP Diagnostics and Prognostics, E External Processes, G Graphics, L Linking, N Navigation and Tracking, P Printing, S Special Content, U Updates, and Uo User Operation Mode. A sample of TABLE A-XVII shows how the factors run: Suspend and Restart 1 and 1, Login 3 and 3, Redlining Graphics 3 and 3, Network Distribution 2 and 2, Dynamic Diagnostics NA and 5, Prognostics NA and 5, System Simulation 4 and 4, 3-D Modeling 4 and 4, and the five Filter features 2 for linear and 1 for non-linear. A few rows carry an R in the requirement column before any tailoring, among them Deficiency Report, Parts Ordering, Table of Contents, and Exit. Section 6.2 closes the loop: an acquisition document should cite the standard, MIL-HDBK-1222, MIL-STD-2361 and MIL-HDBK-2361, a filled-out functionality selection matrix, and a filled-out content selection matrix. How the matrix displaced the older IETM class and level labels is covered in the post on what an IETM is.

XML, DTDs, and MIL-STD-2361

The data behind an Army IETM is tagged text. Paragraph 4.4 of Revision B says data prepared and delivered digitally under the standard shall be XML tagged using the DTD in accordance with MIL-STD-2361, and that stylesheets may be prepared in Extensible Stylesheet Language (XSL) or another language the acquiring activity specifies, with Army-developed stylesheets used where available. The XML tags appear throughout the text in bracketed bold characters, such as the descriptive work package tag, so that authors use them correctly when building a document instance. Paragraph 4.5 says the DTD interprets the technical content and structure for the standard's functional requirements and that its use is mandatory; IETMs are developed through the standard, the DTD, and the guidance in MIL-HDBK-1222, which applies unless it conflicts with the standard.

Paragraph 4.6 says the DTD, stylesheets, and tag and attribute descriptions may be obtained from the Army SGML Registry and Library, named for the Standard Generalized Markup Language that preceded XML, through the methods in MIL-STD-2361, including the registry's website or a mailed disc from the Army Publishing Directorate. Paragraph 4.7 ties functionality back to the matrix: the level of functionality and user interaction shall follow the functionality matrices in Appendix A, which supplement the content requirements of Appendixes B through L and apply to presentation in a frame-based format on a computer display. Paragraph 4.8 settles conflicts between the standard's examples and its text in favor of the text.

The SGML history shows in the files EverySpec carries under the oldest entries. The file posted for the October 15, 2004 base document is 338.75 kilobytes, and its text is titled Technical Manuals, General Preparation and Assembly Information, describes itself as part of an 8-part standard, and calls for SGML tagging with DTDs and Formatting Output Specification Instances developed under MIL-PRF-28001 and ISO 8879. ASSIST, by contrast, lists the 2004 base of Part 1 at 386 pages. The short file is the older multi-part Part 1, not the two-part base document, so anyone who needs the 2004 IETM text should read it on ASSIST.

Revision history from 2004 to Revision D

The ASSIST record lists ten entries. The base document is dated October 15, 2004 at 386 pages. Three changes followed, each incorporating the earlier ones: Change 1 on May 12, 2006 at 368 pages, Change 2 on July 30, 2007 at 383 pages, and Change 3 on March 21, 2008 at 390 pages. Revision A came on July 21, 2010 at 433 pages, Revision B on November 30, 2012 at 475 pages, Revision C on December 15, 2015 at 560 pages, Revision D on March 1, 2021 at 555 pages, and Revision D Change Notice 1 on November 22, 2021 at 581 pages. The last entry is the Revision D Notice 1 cancellation of March 25, 2025, one page. Every entry carries Distribution Statement A.

The EverySpec copies fill in what the record does not say. The header of the Change 1 text of May 12, 2006 states that it supersedes MIL-STD-40051-1(TM) of October 15, 2004 and MIL-PRF-63042D(TM) of April 20, 1998, which places the IETM part in a line of Army performance specifications. The same 2006 text already contains Appendix A paragraph A.5.2, Functionality matrix, with the complexity factor at A.5.2.2.1 and TABLES A-XVI and A-XVII, so the matrix was part of the standard from its first change rather than an addition of a later revision. The header of Revision A, July 21, 2010, carries the same two-part foreword as the later revisions. The Revision B revision summary lists its general changes: it clarified the terms task, procedure, function, and instruction, with function and task synonymous and procedure and instruction synonymous; changed CD to disc or CD/DVD; corrected paragraph caveats to refer to maintenance classes rather than levels; added service identifiers for service-unique requirements; and added three content selection matrixes for ammunition. The Revision C page on EverySpec, dated December 15, 2015 with a 29.30 megabyte file, still shows the status Active, which is one reason to confirm status on ASSIST rather than on a mirror.

MIL-HDBK-1222 moved in step. The ASSIST record for the handbook lists Revision C on October 15, 2004 with the same three change dates as the standard, Revision D on July 21, 2010, Revision E on November 30, 2012, Revision F on December 15, 2015, and Revision G on March 1, 2021, each matching a revision of Part 1. The handbook record says it provides non-regulatory guidance, with Appendix A covering IETMs and Appendix B page-based manuals, that it is meant to be used with MIL-STD-40051-1 and -2 Revision D, and that it "cannot be cited as a requirement." Revision G is still active, with a next review date of February 28, 2026 that had passed when the record was checked.

Cancellation and supersession by MIL-STD-40051E

The ASSIST title for Part 1 now ends with S/S by MIL-STD-40051E, the record status reads Canceled, and the cancellation date is March 25, 2025. The record for Part 2 shows the same date, the same one-page Revision D Notice 1, and the same supersession, so both parts ended together.

The ASSIST record for MIL-STD-40051, the single-document standard, shows Revision E dated March 25, 2025 at 782 pages and Revision E Change 1 dated July 30, 2025 at 784 pages, status Active, project number TMSS-2025-020, full coordination, and a next review due July 29, 2030. The preparing activity and lead standardization activity are still the Army Materiel Command, Life Cycle Sustainment Division, and the United States Marine Corps is listed as Navy custodian. The scope says Revision E should be used to develop maintenance technical and equipment publications regardless of output format, and that the terms IETM and ETM, for Electronic Technical Manual, denote output-specific requirements while requirements not labeled for either apply to both. That is how the two parts were folded into one: the IETM-only rules of the former Part 1 now sit in the same document as the page rules of the former Part 2, each flagged by output. The same record shows the earlier single-document history, from a base dated July 31, 1996 through Revision B of January 31, 2003, inactivated by Notice 2 on October 15, 2004 when the two parts were issued and canceled on June 8, 2016, so Revision E returns the standard to the shape it had before 2004.

What to check

• Which revision does the contract cite, and does the citation include a date? The last revision of Part 1 is Revision D Change Notice 1 of November 22, 2021, and the base of October 15, 2004 and Revisions A through C are all earlier texts with different page counts.
• Has the acquiring activity said whether deliveries continue under the canceled 40051-1 or move to MIL-STD-40051E, whose IETM requirements are labeled by output rather than split into a separate part?
• Is a filled-out functionality matrix and a filled-out content selection matrix attached to the contract, as paragraph 6.2 of Revision B expects, and do the R, NR, and O entries match what the viewer delivers?
• Are the deliverables XML tagged to the DTD under MIL-STD-2361, and does each work package carry an identification number with the right alpha designator and block number?
• Is MIL-HDBK-1222 cited as a requirement? The ASSIST record says it is guidance only, and Revision G is matched to Revision D of the parts.
• Was the status of the standard confirmed on ASSIST, where it shows Canceled, or on a mirror that still shows Revision C as Active?

Azcuna's TRACE is one offline viewer for S1000D, MIL-STD-3001 XML, and PDF technical manuals. It keeps the source location and the markings of everything it shows and never modifies the source. It was proposed to NAVAIR under Navy SBIR Phase I topic DON26BZ05-NV078, and the proposal was submitted on September 23, 2026.

Questions people ask

What is MIL-STD-40051-1?

MIL-STD-40051-1 was Part 1 of the Army's two-part technical manual standard, titled Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs). The ASSIST record says it set technical content, style, format, and functionality requirements for IETMs covering major weapon systems and their equipment at all maintenance levels through depot overhaul. The base document is dated October 15, 2004. ASSIST lists it as canceled on March 25, 2025 and superseded by MIL-STD-40051E.

Is MIL-STD-40051-1 still active?

No. The ASSIST record kept by the Defense Logistics Agency shows MIL-STD-40051-1 with status Canceled, a Revision D Notice 1 cancellation dated March 25, 2025, and the title suffix S/S by MIL-STD-40051E. The replacement, MIL-STD-40051 Revision E, is active and dated the same day, with Change 1 dated July 30, 2025. A contract that still cites 40051-1 is citing a canceled document, and the acquiring activity decides whether to leave the citation or move to Revision E.

What is MIL-STD-40051-1D?

Revision D is the last revision of Part 1. ASSIST lists Revision D dated March 1, 2021 at 555 pages, and Revision D Change Notice 1 dated November 22, 2021 at 581 pages. MIL-HDBK-1222 Revision G, dated the same March 1, 2021, is the non-regulatory style guide ASSIST says is meant to be used with MIL-STD-40051-1 and -2 Revision D. Revision D was canceled by Notice 1 on March 25, 2025.

What is the IETM functionality matrix in MIL-STD-40051-1?

Appendix A of MIL-STD-40051-1 contains a functionality matrix, TABLE A-XVII, that lists IETM features by category and lets the acquiring activity mark each one R for required, NR for not required, or O for optional. Paragraph A.5.2 of Revision B says the matrix lets IETM programs define their requirements in language industry accepts. Paragraph 6.2 says the acquisition document should cite the filled-out matrix, and paragraph A.5.2.1 describes bidders pricing against it.

What is a complexity factor in MIL-STD-40051-1?

Paragraph A.5.2.2.1 of Revision B defines the complexity factor as a relatively weighted number assigned to each feature within a functionality category. A factor of 1 is the baseline, and other values are that many times more complex. The example given is Full Word Search at 1 and Key Word Search at 2, meaning Key Word Search is twice as difficult to develop. Factors are only comparable within one category, and the matrix gives separate linear and non-linear values.

What is a work package in MIL-STD-40051-1?

Paragraph 3.156 of Revision B defines a work package as a presentation of information functionally divided into tasks in the logical order of work sequence, stand-alone, containing one or more tasks. Paragraph 4.9.2 says an IETM consists of introductory matter, planning data, and a series of work packages holding descriptive, troubleshooting, procedural, parts, and supporting information. Each work package carries an identification number built from an alpha designator, a five-digit block number, and the IETM number.

Does MIL-STD-40051-1 require XML?

Yes. Paragraph 4.4 of Revision B says data prepared and delivered digitally under the standard shall be Extensible Markup Language tagged using the Document Type Definition in accordance with MIL-STD-2361, with stylesheets in Extensible Stylesheet Language or another language the acquiring activity specifies. Paragraph 4.5 says use of the DTD is mandatory, and paragraph 4.6 says the DTD and stylesheets come from the Army SGML Registry and Library.

What replaced MIL-STD-40051-1 and MIL-STD-40051-2?

MIL-STD-40051 Revision E, dated March 25, 2025, with Change 1 dated July 30, 2025. The ASSIST record for Revision E says it should be used to develop maintenance technical and equipment publications regardless of output format, and that the terms IETM and ETM mark output-specific requirements while requirements not labeled for either apply to both. Revision E Change 1 runs 784 pages and the next review is due July 29, 2030.

Who prepared MIL-STD-40051-1?

ASSIST lists the Army Materiel Command, Life Cycle Sustainment Division, standardization code TM, as preparing activity, lead standardization activity, and Army custodian, with coordination level Limited. The foreword of Revision B says the standard is approved for the Department of the Army and the United States Marine Corps and available to all DoD departments and agencies, and directs comments to the USAMC Logistics Support Activity at Redstone Arsenal, Alabama.

What is the difference between MIL-STD-40051-1 and MIL-STD-40051-2?

Both parts shared the same content appendixes and the same work package structure, and both were issued October 15, 2004 and canceled March 25, 2025. Part 1 covered IETMs and added functionality requirements: the Appendix A functionality matrix, inner and outer screen shells, and alerts displayed as dialog boxes. Part 2 covered page-based manuals and carried the page layout rules, front matter, and rear matter. ASSIST says Part 2 treats electronic technical manual as synonymous with page-based manual.

Sources

1. 1MIL-STD-40051, Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) (S/S by MIL-STD-40051E) (ASSIST-QuickSearch Document Details) · Defense Logistics Agency, ASSIST-QuickSearch
2. 2MIL-STD-40051, Preparation of Digital Technical Information for Technical Manuals (TMs) (ASSIST-QuickSearch Document Details) · Defense Logistics Agency, ASSIST-QuickSearch
3. 3MIL-STD-40051, Part 2, Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs) (ASSIST-QuickSearch Document Details) · Defense Logistics Agency, ASSIST-QuickSearch
4. 4MIL-HDBK-1222, Guide to the General Style and Format of U.S. Army Work Package Technical Manuals (ASSIST-QuickSearch Document Details) · Defense Logistics Agency, ASSIST-QuickSearch
5. 5MIL-STD-40051/1B, Department of Defense Standard Practice: Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) · Department of Defense, November 30, 2012, via EverySpec
6. 6MIL-STD-40051/1C, Department of Defense Standard Practice: Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) · Department of Defense, December 15, 2015, via EverySpec
7. 7MIL-STD-40051/1A, Department of Defense Standard Practice: Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) · Department of Defense, July 21, 2010, via EverySpec
8. 8MIL-STD-40051/1 (w/Change 1), Department of Defense Standard Practice: Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) · Department of Defense, May 12, 2006, via EverySpec
9. 9MIL-STD-40051/1, Department of Defense Standard Practice: Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs) · Department of Defense, October 15, 2004, via EverySpec

Where this shows up in our work

• TRACE, the offline S1000D and IETM viewer opens S1000D, MIL-STD-3001 and PDF technical manuals on a tablet with every marking intact.
• ELLMENT, the offline LLM for E-2D crews answers a crew's question from the aircraft's own manuals and cites the page, with no network.