Technical data packages and MIL-STD-31000, explained

A technical data package (TDP) is the authoritative technical description of an item, written to support its acquisition, production, inspection, engineering, and logistics support. That definition comes from MIL-STD-31000B, the Department of Defense (DoD) standard practice titled Technical Data Packages, dated 31 October 2018. The standard says a TDP has a level and a type, consists of elements, and may carry metadata and supplementary technical data. The Defense Logistics Agency's ASSIST record lists a newer Revision C, dated 3 February 2025, as the active revision. This post reads the Revision B text and notes what Army briefings say Revision C changes.

The standard and its revisions

The ASSIST record lists the U.S. Army Combat Capabilities Development Command (DEVCOM) Armaments Center as the preparing activity. Every entry in its revision history carries Distribution Statement A:

• Base document, 5 November 2009
• Revision A, 26 February 2013
• Revision B, 31 October 2018, with a validation notice dated 21 August 2023
• Revision C, 3 February 2025, 44 pages, next review due 2 February 2030

The 2009 standard replaced MIL-DTL-31000C of 9 July 2004 and the MIL-T-47500 series of 24 March 1989.

The two Army sources do not agree on timing. An April 2025 briefing by the Armaments Center still calls Revision B, released October 2018, the current revision, with Revision C to be released. ASSIST shows Revision C with the February 2025 date.

Revision B describes the TDP as a subset of technical data. The definition lists models, engineering design data, associated lists, specifications, standards, performance requirements, quality assurance provisions (QAPs), software documentation, and packaging details.

Levels, types, and elements

Section 4.2 sets three levels. A conceptual TDP defines design concepts, generally with simple sketches, models, or renderings. A developmental TDP supports prototypes for test and limited production by, or with help from, the original design activity. A product level TDP must define the item well enough for a competent manufacturer to duplicate its physical, interface, and functional characteristics without added design engineering or recourse to the original or current design activity.

Section 4.3 sets two types. A Type 2D package rests on engineering drawings prepared to the American Society of Mechanical Engineers (ASME) Y14.100 series. A Type 3D package rests on product model data.

Section 4.4 lists the elements:

• Engineering design data, as drawings, 3D viewables, or native or neutral computer-aided design (CAD) data
• Special inspection equipment design data and associated lists
• Specifications and software documentation
• Special packaging instruction documents
• QAPs, which identify any special tests, inspections, measurements, or certifications the item needs
• Special tooling design data and associated lists

Data management products, such as the TDP list and the engineering drawing tree, track the package itself. Section 5.5.2 bars a TDP element from referencing technical manuals, maintenance manuals, management plans, or uncontrolled or unreleased documents.

From drawings to models

Revision B defines model based definition (MBD) as using 3D datasets with exact solid geometry and 3D annotations of dimensions, tolerances, materials, finishes, and notes to specify a complete product definition. A Type 3D package may include native models and, derived from them, 2D drawings, 3D Portable Document Format (PDF) viewables, and neutral files in STEP, the ISO 10303 exchange format. Only one master dataset exists, typically in native CAD, held by the current design activity. Section 5.3.2.4 requires that derived data show no conflict with the master model. For product level packages, section 5.3.2.3 bars envelope models and unannotated features unless the contract allows them. Section 5.8 requires restriction markings to be clearly visible when a 3D model is opened, or placed where the user can clearly find them.

An April 2024 Armaments Center briefing notes that the paper drawing was once both master and authoritative. Authoritative data can be built to and inspected to; reference data cannot be inspected to.

DoD Instruction 5000.97, effective December 21, 2023, requires programs started after that date to use digital engineering unless the program's decision authority grants an exception. Program managers must require digital models as contract deliverables, with intellectual property rights in them.

The April 2025 briefing says Revision C adds an Additive Manufacturing Data File (AMDF) as a TDP element, in a proposed STEP or native plus STEP format unless otherwise specified. It renames one process element the Required Manufacturing Process Description and makes it an explicit element.

How a TDP is ordered

Section 1.2 says levels, types, elements, and data management products are imposed through the TDP Option Selection Worksheet or block 16 of the DD Form 1423, the Contract Data Requirements List (CDRL). Section 6.2 says acquisition documents should state the standard's title, number, and date, along with:

• The TDP level, deliverable data products, and elements
• The data management products
• Whether company standards are permitted
• Completed Option Selection Worksheets, backed by statement of work tailoring

Table I lists the data item descriptions (DIDs) to cite on the CDRL, including DI-SESS-80776, Technical Data Package, and DI-SESS-82238, Technical Data Package List. Appendix A makes the worksheet mandatory once it forms part of a contract. Section 6.7 warns that the standard will not be used to circumvent the data rights rules in the Defense Federal Acquisition Regulation Supplement (DFARS).

The DFARS text that DoD contracting officers have used since February 1, 2026, under class deviation 2026-O0036, states a policy to acquire only the data and rights needed, with deliverables priced as separate line items to the extent practicable. The 2024 briefing lists common failures: incomplete worksheets, vague contract language, unstated data rights, and confusion between TDP access and TDP delivery.

What to check

• Which revision of MIL-STD-31000 does the contract cite, by title, number, and date, as section 6.2 asks?
• Is a completed Option Selection Worksheet attached, and does the CDRL cite the matching DID?
• For a 3D package, which file is the master, and do drawings, 3D PDF viewables, and STEP files derive from it without conflict?
• Does a product level package use complete design disclosure models, or envelope models the contract did not allow?
• Do the 3D models show restriction markings when opened?
• Does the contract say whether the TDP is delivered or only made accessible, and which rights come with it?

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. 1MIL-STD-31000 Document Details (ASSIST-QuickSearch) · Defense Logistics Agency, ASSIST database (record read October 22, 2026)
2. 2MIL-STD-31000B, Department of Defense Standard Practice: Technical Data Packages (31 October 2018) · Department of Defense, via EverySpec (Distribution Statement A)
3. 3MIL-STD-31000 Technical Data Packages in Acquisition · U.S. Army DEVCOM Armaments Center briefing, April 2024, hosted by NIST
4. 4MIL-STD-31000 Update to Support Additive Mfg. (AM) · U.S. Army DEVCOM Armaments Center briefing, April 2025, posted by SME
5. 5DoD Instruction 5000.97, Digital Engineering (December 21, 2023) · Office of the Under Secretary of Defense for Research and Engineering
6. 6Class Deviation 2026-O0036, Revolutionary FAR Overhaul Part 27, DFARS Part 227 · Defense Pricing, Contracting, and Acquisition Policy (signed January 21, 2026)

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.
• BABEL, offline multilingual translation and search translates and searches foreign-language documents on-device, every fact tied to its source passage.