Logistics product data, explained

Logistics product data (LPD) is the support data a contractor produces through product support analysis during the design, development, and initial fielding of a system, delivered in the format set by the industry standard GEIA-STD-0007. The Department of Defense (DoD) data item description (DID) DI-SESS-81758A, approved May 22, 2013, lists what it covers, from maintenance planning and reliability to initial provisioning and cataloging. The Army's technical manual standard, MIL-STD-40051, at Revision E with Change 1 of July 30, 2025, makes LPD, including the maintenance allocation chart (MAC), the baseline for preparing publications.

From LSAR to GEIA-STD-0007

The standard behind LPD arrived through two cancellations, starting from the logistic support analysis record (LSAR). Notice 2 to MIL-STD-1388-2B, DoD Requirements for a Logistic Support Analysis Record, dated November 26, 1996, canceled the standard and moved its requirements to MIL-PRF-49506, Logistics Management Information. Notice 2 to MIL-PRF-49506, dated March 31, 2011, canceled that specification and named TechAmerica's GEIA-STD-0007, Logistics Product Data, as its replacement. The notice warns that the supersession is valid only as of its date.

SAE International now publishes the standard. The SAE record for GEIA-STD-0007C gives an original issue of August 2007 and Revision C of November 6, 2019, which followed Revision B of May 1, 2013. The issuing committee is Life Cycle Logistics Supportability. The scope says the standard defines LPD generated during requirement definition and design, using Extensible Markup Language (XML) entities and attributes, and gives users a uniform set of data tags. It applies to industry and Government programs alike, and the term contract covers any agreement between organizations.

What LPD contains

DI-SESS-81758A defines LPD as support and support-related engineering and logistics data that the requiring authority needs for its own materiel management. The list is long: maintenance planning, logistics design requirements, reliability and maintainability, system safety, maintenance engineering, support and test equipment, training and training devices, manpower and skills, facilities, transportation, supply support, parts packaging, initial provisioning, cataloging, item management, and in-service feedback.

The data item ties the content to the standard. Content follows Section 2 and Appendix A of GEIA-STD-0007, and delivery uses the XML schemas and file formats in its Appendices C and D, or a format in the contract. An Attribute Selection Sheet, from the companion handbook GEIA-HB-0007, or another tool in the contract picks which data elements are bought. When provisioning data is bought under Appendix D, a second data item, DI-SESS-81874, Engineering Data for Provisioning, is required to support cataloging in the Federal Cataloging System. The DID itself is to be tailored to the contract's minimum needs.

The analysis behind the data

GEIA-STD-0007 defines the data. The analysis that produces it has its own standard, SAE TA-STD-0017. The SAE record for TA-STD-0017A gives an original issue of November 2012 and Revision A of March 1, 2022, and says the standard sets general principles and activities that together make up the product support analysis (PSA) process.

MIL-HDBK-502A, dated March 8, 2013, is the DoD handbook on PSA, for guidance only. The handbook calls LPD the portion of PSA documentation that identifies product support resource requirements. The primary PSA techniques it lists include failure mode, effects and criticality analysis, fault tree analysis, reliability centered maintenance analysis, level of repair analysis, and maintenance task analysis. The handbook names TA-STD-0017 the default standard for acquiring PSA data, with DI-SESS-81758 for the data and DI-SESS-81759 for summaries. Task analysis supplies source data for maintenance plans, MACs, technical manuals, and provisioning documentation, and the handbook warns that skipping it may leave little or no documentation of maintenance procedures.

How LPD reaches the manual and the parts list

MIL-STD-40051E describes the chain. Provisioners and other logistics data specialists develop LPD and output it as reports such as LSAR 030 and LSAR 004. The LSAR 004 report provides MAC data and the LSAR 080 bill of materials provides data for the repair parts and special tools list (RPSTL). Source, maintenance, and recoverability codes are part of the LPD, and the LPD in the RPSTL is used to produce the MAC, so the two must agree. Maintenance work packages, the MAC, and the RPSTL are tied together by functional group codes, and MAC entries are determined by LPD.

The MIL-HDBK-502A sample contract data requirements list shows the same reports from the buyer's side: LSA-004 maintenance allocation chart, LSA-030 indentured parts list, LSA-056 failure modes, effects and criticality analysis, LSA-080 bill of materials, and LSA-151 provisioning parts list index. For engineering data for provisioning, the handbook gives DoD's preference for DI-SESS-81874 and an order of precedence: product engineering drawings first, then drawings in process, then commercial drawings or associated lists.

What to check

• Which revision of GEIA-STD-0007 does the contract cite? SAE lists Revision C of November 6, 2019.
• Does any contract or statement of work still cite MIL-STD-1388-2B or MIL-PRF-49506, both canceled?
• Is there an Attribute Selection Sheet or other tool that says which LPD elements are being bought?
• If provisioning data is bought under Appendix D, is DI-SESS-81874 on contract as well?
• Do the MAC, the RPSTL, and the maintenance work packages agree through the same functional group codes, as MIL-STD-40051E requires?
• Which TA-STD-0017 activities does the statement of work require, and which were tailored out?

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.

Sources

1. 1GEIASTD0007C, Logistics Product Data · SAE International, revised November 6, 2019
2. 2TASTD0017A, Product Support Analysis · SAE International, revised March 1, 2022
3. 3DI-SESS-81758A, Data Item Description: Logistics Product Data · Department of Defense, May 22, 2013, via EverySpec
4. 4MIL-HDBK-502A, Product Support Analysis (PSA) · Department of Defense, March 8, 2013, via EverySpec
5. 5MIL-PRF-49506 (Notice 2), Logistics Management Information · Department of Defense, March 31, 2011, via EverySpec
6. 6MIL-STD-1388-2B (Notice 2), DoD Requirements for a Logistic Support Analysis Record · Department of Defense, November 26, 1996, via EverySpec
7. 7MIL-STD-40051, Preparation of Digital Technical Information for Technical Manuals (TMs) (ASSIST-QuickSearch Document Details) · Defense Logistics Agency, ASSIST-QuickSearch (Revision E with Change 1, July 30, 2025)

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.