2023 Update – Author: Jennifer Herron
Traditionally, 2D data (e.g., drawings, static documents, static parts lists) are the authoritative source for technical data used within the government to acquire products from its supply chain. Going beyond 2D data to use 3D data demands sophistication for the exchange and collaboration of 3D data. Since the benefits of using and re-using 3D data are significant, it is important to acknowledge the differences in 2D and 3D data that comprise the Technical Data Package (TDP).
2D TDPs are often defined as a bundle of files with a finite list of file format types prescribed in MIL-STD-31000B. Traditionally, 2D TDPs consist of PDF (Drawings) and Microsoft documents (e.g., Word, Excel). 3D TDPs include 3D file formats (e.g., native CAD, neutral CAD, and data types not yet invented) but may also include the 2D files mentioned previously. Therefore, a single file does not, and will not, define 3D TDPs.
A 3D TDP should consist of digitally connected files that define the product and optimize consumption during fabrication, assembly, inspection, test, and sustainment. The authoring process of such data is called Model-Based Definition (MBD).
Adding 3D TDPs to the DoD Acquisition Process does not preclude 2D TDPs from also being procured. Acquiring 2D TDPs may be the most effective artifact to document products defined using schematics or those having very simple geometry, such as a washer. 3D TDP acquisition should focus on products with complex geometry, complex first article inspection requirements, complex assembly operations, and those products that experience quality escapes due to drawing documentation errors. A rigid binary “all or nothing” 3D acquisition process is not pragmatic.
A 3D TDP should consist of digitally connected files that define the product and optimize consumption during fabrication, assembly, inspection, test, and sustainment. The authoring process of such data is called Model-Based Definition (MBD).
MIL-STD-31000 DOD Standard Practice Technical Data Packages Release History:
- 2009: Initial release, added language to acquire TDPs as 3D Data and includes the TDP Option Selection Worksheet.
- 2013: Rev A, adding Appendix B and C to better define 3D Data acquisition.
- 2018: Rev B, superseding Rev A, moved Appendix B to ASME Y14.47, and eliminated Appendix C, includes the definition of the 3Di Technical Data also known as the 3D PDF.
SCOPE.
1.1 This standard defines the requirements for a technical data package (TDP) and its related TDP data management products. The purpose of the TDP is to provide an authoritative technical description of an item which is clear, complete and accurate, and in a form and format adequate for its intended use. A TDP contains elements, is described by a level and type, and may have associated metadata and supplementary technical data. A TDP is a sub-set of product and technical data as shown in the hierarchical breakdown in Figure 1 (found in the “read more” link below).
1.2 TDP Levels, TDP Types, TDP Elements and TDP data management products will be identified in accordance with this standard and applicable Data Item Descriptions (DID), as tailored and imposed through the TDP Option Selection Worksheet (Figure 5) or as defined in block 16 of the DD1423, Contract Data Requirements Lists (CDRL) in contracts, purchase orders, and Military Interdepartmental Procurement Requests (MIPRs) (hereafter referred to collectively as “the contract”).
Jennifer Herron, CEO of Action Engineering has been involved with the MIL-STD-31000 effort since the first release of revision A that opened up the Department of Defense (DOD) definition of a Technical Data Package (TDP). The initial release of this DOD standard was the first time that government agencies had the ability to ask their contractors to deliver 3D CAD models.
Since 2009 when the new standard was piloted within various government agencies (Navy, Air Force, Army), the community learned from authoring and receiving those TDPs. That learning culminated in the release of revision B. The focus of revision B is to urge a standard format for a 3D PDF and increase the sophistication of the TDP Option Selection worksheet.
Note: Many in the model-based community tend to use the TLA (three letter acronym) TDP far to cavalierly. TDP has very specific contractual definition to a DOD organization and their contractors. When generalizing the “TDP” concept, we should use a DP (Data Package) instead.