Downloaded from https://www.everyspec.com MIL-STD-31000B with all required associated lists (see 5.4.3); specifications (see 5.4.4); software documentation (see 5.4.5); SPI design data with all required associated lists (see 5.4.6); and QAPs (see 5.4.7) as specified by the contract. 5.3 TDP types. TDP Type describes the form and format of the data as imposed by the contract and TDP Option Selection Worksheet. 5.3.1 Type 2D: 2-Dimensional Technical Data Package (2D TDP). A 2D TDP is based on 2 dimensional engineering drawings in accordance with ASME Y14.100 series standards (e.g. figure 2). 5.3.2 Type 3D: 3-Dimensional Technical Data Package (3D TDP).
A 3D TDP is based on product model data that is capable of generating derivative products including but not limited to 2D TDP, 3D lightweight graphical representations, and neutral data formats. Type 3D shall include one or more of the below as specified in the contract and TDP Option Selection Worksheet: (1) 3D native models. (2) 2D drawings derived from the 3D native models (e.g. figure 3). (3) 3Di pdf viewable data derived from the 3D native models (e.g. figure 4 and Appendix B). (4) Neutral files derived from the 3D native models. 5.3.2.3 Requirements for Type 3D TDPs.
When 3-dimensional models are used in a product level TDP, the models shall be complete design disclosure models, except as stated in para 5.3.2.5. Complete design disclosure includes all necessary information to adequately define the item including, but not necessarily limited to, full design disclosure (via annotations or other means) of all features and geometry, dimensions, tolerances, materials, specifications, notes, or other information fully included in the 3D native CAD model. For product level TDPs, use of envelope models, un-annotated or un-defined features, and/or global profile tolerancing is not allowed unless specifically stated in the contract.
5.3.2.4 Derived data based on 3D models. Engineering design data including but not limited to 2D TDP, 3D lightweight graphical representation, and neutral data formats shall be based on, and derived from the master native 3D models. There shall be no conflict in data between the master 3D native model and its derived engineering design data. 5.3.2.5 Limited design disclosure models. When a 3D TDP is required and a subcomponent to the end item does not require complete design disclosure, (such as a commercial item, purchased item, item controlled by a standardization document, etc.) a 3D model of the subcomponent shall be provided.
The subcomponent s 3D model need not be fully defined but shall be sufficient to visualize the shape, interface characteristics, and describe form, fit, and function as required. 13