9.5-9.10 CDRL A0005-0010 DID.pdf

NOT MEASUREMENT

SENSITIVE

MIL-STD-31000B

31 October 2018

SUPERSEDING

MIL-STD-31000A

26 February 2013

DEPARTMENT OF DEFENSE

STANDARD PRACTICE

TECHNICAL DATA PACKAGES

This standard is approved for use by all Departments and Agencies of the Department of Defense.

1. 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.

1.2 TDP levels, types, 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”).

Comments, suggestions, or questions on this document should be addressed to: Commander, US Army ARDEC, ATTN: RDAR-EIQ-SA, Picatinny Arsenal, New Jersey 07806-5000 or email to usarmy.picatinny.ardec.list.ardec-stdzn-branch@mail.mil. Since contact information can change, you may want to verify the currency of this address information using the ASSIST online database at https://assist.dla.mil.

AMSC A9092 AREA SESS

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2022-03-09T19:27Z Check the source to verify that this is the current version before use.

MIL-STD-31000B

FIGURE 1. TDP relationships

2. APPLICABLE DOCUMENTS.

2.1 General. The documents listed in this section are specified in sections 3, 4 and 5 of this standard. This section does not include documents listed in other sections or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in sections 3, 4, or 5 of this standard, whether or not they are listed.

2.2 Government documents.

2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

Technical Data Package (TDP)

(includes but is not limited to):

Models Drawings Associated Lists Specifications Standards Quality Assurance Provisions Software Documentation Packaging Details

DEPARTMENT OF DEFENSE STANDARDS.

MIL-STD-961 Defense and Program-unique Specifications Format and Content

MIL-STD-963 Data Item Descriptions (DIDs)

MIL-STD-2073-1 Standard Practice for Military Packaging

DOD-STD-2101 Classification of Characteristics

Copies of these documents are available online at http://quicksearch.dla.mil.

2.2.2 Other Government documents and publications. The following other Government documents and publications form a part of this document to the extent specified herein. Unless otherwise specified, the issues are those cited in the solicitation or contract.

DEPARTMENT OF DEFENSE MANUALS

DoD Manual 4100.39-M Federal Logistics Information System (FLIS) Procedures

DoD Manual 5220.22-M DoD Industrial Security Manual for Safeguarding Classified Information.

DoD Instruction 5230.24 Distribution Statements on Technical Documents

DoD Directive 5230.25 Withholding of Unclassified Technical Data From Public Disclosure

DFARS Part 252 DFAR Supplement for Solicitations, Provisions and Contract Clauses

DFARS 252.227-7013 Rights in Technical Data--Noncommercial Items.

DFARS 252.227-7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.

(Applications for copies of DoD Manual 5520.22-M and DoD Instruction 5230.24 are available from the Defense Technical Information Center (DTIC), http://www.dtic.mil. Copies of DFARS documents are available online at http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html. The federal documents can be found at http://www.dtic.mil/whs/directives/.)

FEDERAL PUBLICATION

Federal Standardization Manual

(Copies of Federal Standardization Manual are available from the General Service Administration, Centralized Mailing List Service (7CAFL), P.O. Box 6477, Ft. Worth, TX 76115 and https://www.gsa.gov/portal/mediaId/215947/fileName/Federal_Standardization_Manual.action.)

2.3 Non-Government publications. The following documents form a part of this standard to the extent specified herein. Unless otherwise specified, the issues of the documents are those cited in the solicitation.

AMERICAN SOCIETY OF MECHANICAL ENGINEERS (ASME)

ASME Y14.1 Decimal Inch Drawing Sheet Size and Format

ASME Y14.1M Metric Drawing Sheet Size and Format

ASME Y14.24 Types and Applications of Engineering Drawings

ASME Y14.34 Associated Lists

ASME Y14.35 Revision of Engineering Drawings and Associated Documents

ASME Y14.41 Digital Product Definition Data Practices

ASME Y14.5 Dimensioning and Tolerancing

ASME Y14.100 Engineering Drawing Practices

(Copies of these documents are available from https://www.asme.org/ or ASME information Central Orders/Inquiries, P.O. Box 2300, Fairfield, NJ 07007-2300)

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

ISO/IEC 12207 System and Software Engineering - Software Lifecycle Processes ISO 32000-1 Document Management - Portable Document Format.

(Copies of this document are available from http://www.ieee.org/index.html, or IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08854-1331.)

AMERICAN NATIONAL STANDARDS INSTITUTE (ANSI)

ISO 10303 Standard for the Exchange of Product model data (STEP)

(Copies of free and purchased parts of the standard are available at: https://www.iso.org/.)

NATIONAL AEROSPACE STANDARDS (NAS)

NAS 3500 Technical Data Package: Composition, Communication, and Application

(Copies of this document are available from the Aerospace Industries Association of America, inc. 1000 WILSON BLVD, ARLINGTON, VA 22209 and http://www.aia-aerospace.org.)

2.4 Order of precedence. Unless otherwise noted herein or in the contract, in the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. DEFINITIONS.

3.1 For the purposes of this standard, the following definitions apply:

3.1.1 3-Dimensional Intelligent (3Di) technical data. A 3-dimensional viewable representation of an item provided in a widely available software format (e.g. ISO 32000-1 Portable Document Format (PDF)). This representation details the complete technical description of the required design configuration to include but not limited to geometry, topology, relationships, tolerances, attributes, metadata and other features necessary to define a component or assembly.

3.1.2 3Di format. The standard arrangement and organization of information within a 3Di viewable representation of an item. This includes such features as the size and arrangement of information blocks (e.g. title blocks), notes, lists, revision information, view states, restriction notices and the use of optional or supplemental blocks (see related term Drawing Format).

3.1.3 Commercial And Government Entity (CAGE) code. A five character alpha-numeric identifier, assigned to commercial and Government activities that manufacture or develop items, or provide services or supplies for the Government. When used with a document number or part number, the CAGE code designates the design activity from whose series the document or part number is assigned.

3.1.4 Commercial engineering design data. Engineering design data prepared by a commercial design activity, in accordance with that activity's documentation standards and practices, to support the development and manufacture of a commercially developed product.

3.1.5 Commercial item. An item that is customarily used by or sold to the general public or by non-governmental entities for purposes other than governmental purposes.

3.1.6 Company standard. A company document, which establishes engineering and technical limitations and applications for items, materials, processes, methods, designs and engineering practices unique to that company. (NOTE: Company standards are not considered to be non-Government standards.)

3.1.7 Competent manufacturer. A manufacturer that has demonstrated the capability to produce similar products at the same state of the art in the same or similar lines of technology.

3.1.8 Computer software. Computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae and related material that would enable the software to be reproduced, recreated, or recompiled. Computer software does not include computer data bases or computer software documentation. (DFARS Clause 252.227-7014)

3.1.9 Computer software documentation. Owner’s manuals, user’s manuals, installation instructions, operating instructions, and other similar items, regardless of storage medium, that explain the capabilities of the computer software or provide instructions for using the software. (DFARS Clause 252.227-7014) ISO/IEC Standard 12207 uses the term “software life cycle data” to address software documentation.

3.1.10 Configuration Item (CI). A product or an aggregation of products that accomplishes an end-use function and is deemed to require separate configuration management documentation and control.

Configuration items are end items or major components of end items, which typically have performance requirements allocated to them and documented in their own specification.

3.1.11 Critical manufacturing process. A process that is the only known manufacturing method that will result in the production of an acceptable item.

3.1.12 Data Item Description (DID). A completed document defining the data deliverables required of a DOD contractor. A DID specifically defines the data content, format and intended use of the data with a primary objective of achieving standardization of data deliverables by the DOD. (MIL-STD-963)

3.1.13 Design activity. An organization that has, or has had, responsibility for the design of an item.

The two types of design activity are:

3.1.13.1 Current Design Activity (CDA). The design activity currently responsible for the design of an item. This may be the original design activity or a design activity to which the design responsibility has been transferred.

3.1.13.2 Original Design Activity (ODA). The design activity originally responsible for the design of an item, and whose design activity identification (CAGE Code) is associated with the part or identifying number (PIN) and are typically shown in the title block of the engineering design data.

3.1.14 Detail specification. A specification that specifies design requirements, such as materials to be used, how a requirement is to be achieved, or how an item is to be fabricated or constructed. (MIL-

STD-961)

3.1.15 Drawing. An engineering document or digital data file(s) that discloses (directly or by reference), by means of graphic or textual presentations, or by combinations of both, the physical or functional requirements of an item. (ASME Y14.100) A drawing is a type of engineering design data.

3.1.16 Drawing format. The arrangement and organization of information within a drawing. This includes such features as the size and arrangement of blocks, notes, lists, revision information, and the use of optional or supplemental blocks. (ASME Y14.1/Y14.1M) (See related term 3Di format)

3.1.17 End product. An end product is an item, such as an individual part or assembly, in its final or completed state. (ASME Y14.24). An end product is also known as an end item.

3.1.18 Engineering design data. Engineering drawings, 3Di viewables, native CAD models, neutral CAD models or a combination of these, which define an item by means of graphic and textual presentations, the physical and/or functional requirements of an item, sufficient to fulfill its TDP element and level requirements. Engineering design data comes in three levels corresponding to its TDP level requirements as defined below:

3.1.18.1 Conceptual design data. Engineering design data which describe the engineering concepts on which a proposed technology or design approach is based.

3.1.18.2 Developmental design data. Engineering design data which describe the physical and/or performance characteristics of a specific design approach to the extent necessary to permit the analytical evaluation of the ability of the design approach to meet specified requirements and enable the development, manufacture and testing of prototype or experimental materiel.

3.1.18.3 Product design data. Engineering design data which describes the complete physical and/or performance characteristics of an item or component in sufficient detail to ensure that an item or component produced in accordance with this data will be essentially identical to the original item or component.

3.1.19 Fully annotated model. A 3D CAD dataset, in which all necessary features to fully define the item (i.e. full design disclosure to include dimensions, tolerances, materials, notes, surface finishes, etc.)

are included in a readily viewable form. (See ASME Y14.41)

3.1.20 Limited design disclosure model. A 3D CAD dataset sufficiently defined to provide a visual understanding of the item, but which does not contain full design disclosure. Generally external interface characteristics and features such as weight and center of gravity will be sufficiently defined for the intended purpose. Sometimes referred to as an envelope model, shrink-wrap model or cosmetic model.

3.1.21 Metadata. Data that provides information about other data. For the purpose of this standard, metadata is defined to be data about a design and/or engineering design documents. (Part number, drawing number, nomenclature, revision, date approved, approved by, used on, etc., are examples of metadata).

Metadata is used by the design and procuring activities to store, manage, and provide access to TDP elements.

3.1.22 Model Based Definition (MBD). The practice of using 3D datasets containing the exact solid representation, associated 3D geometry and 3D annotations of a product’s dimensions, tolerances, materials, finishes and other notes to specify a complete product definition. (See ASME Y14.41)

3.1.23 Non-Government standardization document (a.k.a. Industry Standards). A standardization document developed by a private sector association, organization or technical society which plans, develops, establishes or coordinates standards, specifications, handbooks or related documents. These documents are available for purchase or free of charge to the general public. Company standards are not considered as non-Government standardization documents.

3.1.24 Performance specification. A specification that states requirements in terms of the required results with criteria for verifying compliance, but without stating the methods for achieving the required results. A performance specification defines the functional requirements for the item, the environment in which it must operate, and interface and interchangeability characteristics. (MIL-STD-961)

3.1.25 Procuring activity. The Government or private organization which establishes the requirements for an end item, service or set of data, and is responsible for the issuance of a contract or solicitation for these goods or services.

3.1.26 Product Lifecycle Management (PLM). The process or system used for managing product-related design, production and maintenance information. PLM systems are typically software applications designed for the purpose of lifecycle management of a product.

3.1.27 Quality Assurance Provisions (QAP). Documented requirements, procedures and criteria necessary for demonstrating that products conform to design requirements.

3.1.28 Reference documents. Documents referred to in a TDP element, which contain information necessary to meet the information content requirements of that TDP element.

3.1.29 Software specification. A type of program-unique specification that describes the requirements and verification of requirements for the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. (MIL-STD-961)”

3.1.30 Special Inspection Equipment (SIE). Either single or multi-purpose integrated test units engineered, designed, fabricated or modified to perform special purpose testing of an item in the manufacturing process. It consists of items or assemblies of equipment and associated software that are interconnected and interdependent so as to become a new functional entity for inspection or testing purposes. SIE is also known as special test equipment.

3.1.31 Special Packaging Instruction (SPI). Instructions which document military packaging requirements for an item, as distinct from commercial packaging. These instructions cover methods of preservation to protect materiel against environmentally induced corrosion and deterioration, physical and mechanical damage, and other forms of degradation during storage, multiple handling and shipment of materiel in the defense transportation system. SPI’s will be required and prepared in accordance with Appendix E of MIL-STD-2073-1 and as specified in the contract and Contract Data Requirements List

(CDRL).

3.1.32 Special tooling. Unique tooling which is mandatory for the manufacture of an acceptable item. It differs from tooling designed to increase manufacturing efficiency in that the use of the special tool imparts some characteristic to the item which is necessary for satisfactory performance and cannot be duplicated through other generally available manufacturing methods. Examples of special tooling would be jigs, dies, fixtures, molds, patterns and other equipment or manufacturing aids that absolutely must be used in order to produce a satisfactory item.

3.1.33 Specification. A document that describes essential technical requirements for materiel and the criteria for determining whether those requirements are met. (MIL-STD-961)

3.1.34 Standardization document. A document, such as a specification, standard or handbook, developed for the purpose of standardizing items, materials, processes or procedures.

3.1.35 Supplementary technical data. Data related to or in support of a TDP, but not an inherent part of the TDP, which is provided as reference material or is explanatory in nature. For example, supplementary technical data for a particular item could include manufacturing instructions, simulations, work flow data, inspection equipment or procedures (which are not required as an inherent part of the TDP or TDP element), manufacturing machine code, design studies, analysis studies, test results, safety data sheets, etc.

3.1.36 Technical data. Recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation). The term does not include computer software or data incidental to contract administration, such as financial or management information. (DFARS Clause 252.227-7013).

3.1.37 Technical data CAD format:

3.1.37.1 Native CAD data. CAD data as created in its original authoring software format. In general, only the original authoring software format is capable of reading, editing and interpreting native CAD data. (Examples: CREO, CATIA, Autodesk, SolidWorks, etc.) Generally native CAD data is the only format suitable to serve as master technical data. Native CAD data may also serve as authoritative technical data.

3.1.37.2 Neutral CAD data. CAD data which is derived from the native format and converted into a format which can be imported into other CAD software. Neutral CAD data is created to a widely available national or international standard (e.g. STEP). In general, neutral CAD data cannot serve as master technical data but may serve as either reference or authoritative technical data.

3.1.37.3 Viewable CAD data. CAD data which is derived from the native format and converted into a format which can be displayed by a widely available software and for purposes of defining design intent in a human readable format (e.g. 3Di PDF). In general, viewable CAD data cannot serve as master technical data but may serve as either reference or authoritative technical data.

3.1.38 Technical data origin:

3.1.38.1 Master technical data. A set of technical data which is the controlling source for any subsequent technical data output. All changes to the technical data must originate on the master technical dataset. There can be only one instance of the master technical data which is typically in the native CAD format and maintained by the current design activity.

3.1.38.2 Derivative technical data. A set of technical data generated from master technical data.

Typically derivative technical data is created to change its format to suit a different purpose. For example converting master, native format data to neutral or viewable data (e.g. STEP, PDF, etc.) so as to allow it to be read by a wider range of software applications. Changes to derivative technical data originate on the master technical dataset.

3.1.39 Technical data validation status:

3.1.39.1 Authoritative technical data. A set of technical data which has been released and validated as adequate and complete for its intended purpose.

3.1.39.2 Reference technical data. A set of technical data which is provided for information, but is not necessarily validated as accurate, adequate and complete.

3.1.40 Technical Data Package (TDP). The authoritative technical description of an item. This technical description supports the acquisition, production, inspection, engineering, and logistics support of the item. The description defines the required design configuration and/or performance requirements, and procedures required to ensure adequacy of item performance. It consists of applicable technical data such as models, engineering design data, associated lists, specifications, standards, performance requirements, quality assurance provisions, software documentation and packaging details.

3.1.41 Technical data package data management product. A data product that is used to monitor and control the development and maintenance of the TDP. A TDP data management product contains information about the TDP rather than the item being documented.

3.1.42 Technical data package element (a.k.a. component). A data product that is an actual component of the TDP. A TDP element provides all or part of the information necessary to define the item being documented by the TDP. All TDP elements taken collectively provide a complete Technical Data Package.

3.1.43 Technical Data Package List (TDPL). An index of all documents contained in a technical data package established at a point in time. TDPLs contain a list of all specifications, engineering design data, (i.e. drawings, models, 3Di viewables, etc.), QAPs, inspection documents, packaging documents, or other documents which comprise the TDP listed by nomenclature, document CAGE code, document number, distribution statement, revision, and date.

3.1.44 Verification. All examinations, tests and inspections necessary to verify that an item meets the physical and functional requirements for which it was designed, to verify that a component, part or subassembly will perform satisfactorily in its intended application, or that an item conforms to specified requirements.

4. GENERAL REQUIREMENTS.

4.1 General. The purpose of the TDP is to provide a technical description of an item which is clear, complete and accurate and in a form and format adequate for its intended use. TDPs define the physical and functional characteristics of the accepted configuration of the item and its subordinate assemblies, subassemblies, and parts. To accomplish this purpose, TDPs consist of a level and type and one or more elements as specified in the contract and TDP Option Selection Worksheet. In addition, TDP metadata, supplementary data and TDP data management products may be required to manage and control the TDP development process as specified in the contract and TDP Option Selection Worksheet (Figure 5).

4.2 TDP levels. TDP levels provide for a natural progression of a design from its inception to production. A particular TDP level may be ordered to define a conceptual design, a developmental prototype or limited production design, or full scale production of the item by the original design activity or any other capable manufacturer. TDPs consist of one of three Levels:

(1) Conceptual Level

(2) Developmental Level

(3) Product Level

4.3 TDP types. TDP type describes the form and format of the technical data and shall consist of one or more of the following types:

4.3.1 Type 2D: 2-Dimensional (2D) Technical Data Package.

4.3.2 Type 3D: 3-Dimensional (3D) Technical Data Package. Type 3D will 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.

(3) 3Di pdf viewable data derived from the 3D native models.

(4) Neutral files derived from the 3D native models.

4.4 TDP elements. TDP elements describe the various components of the TDP. TDP elements shall consist of some or all the following as necessary to fulfill its intended purpose and as described in the contract and TDP Option Selection Worksheet.

4.4.1 Engineering design data. The form and format of the engineering design data, whether it be 2D drawings, 3Di viewables, native or neutral CAD data, will be as specified in the TDP Option Selection Worksheet and the contract. The engineering design data may consist of conceptual, developmental or product level engineering design data depending on the TDP level requirements and may be in government or commercial format as stated in the contract and TDP Option Selection Worksheet.

a. Special Inspection Equipment (SIE) engineering design data and associated lists.

b. Specifications.

c. Software documentation.

d. Special Packaging Instruction (SPI) documents, engineering design data and associated lists.

e. Quality assurance provisions (QAP).

f. Special Tooling engineering design data and associated lists.

4.5 TDP data management products. TDP data management products listed below are used by the procuring activity to control and manage the TDP development process and shall be delivered in accordance with the contract and TDP Option Selection Worksheet. Other TDP data management products in addition to those listed below may also be required as stated in the contract.

a. Technical Data Package List (TDPL).

b. Document number assignment report.

c. Proposed critical manufacturing process description.

d. Source control approval request.

e. Engineering drawing tree

4.6 TDP metadata. Metadata consist of data from and about TDP elements and is used by the procuring activity to manage the TDP development process and to better acquire and support the end product defined by the TDP. When metadata is required, it shall be delivered in accordance with the contract.

4.7 Supplementary technical data. TDP supplementary technical data are deliverable data products used by the procuring activity to better acquire and support the end product defined by the TDP. When supplementary technical data is required, it shall be delivered in accordance with the contract.

5. DETAILED REQUIREMENTS.

5.1 General. TDPs define the physical and functional characteristics of the accepted configuration of the item and its subordinate assemblies, subassemblies, and parts. See Appendix A for guidance on selection of TDP elements and data management products.

5.2 TDP levels.

5.2.1 Conceptual level. A conceptual TDP shall consist of those TDP elements necessary to define design concepts, and include the appropriate information required for analysis and evaluation of those concepts. The data will generally consist of simple sketches/models, artist renderings and/or basic textual data. The data may consist of the system performance specification (see 5.4.4) and conceptual design data (see 5.4.1.1) as specified by the contract.

5.2.2 Developmental level. A developmental TDP shall consist of those TDP elements necessary to provide sufficient data to support the analysis of a specific design approach, the fabrication of prototype materiel for test or experimentation, and limited production by the original design activity or with assistance from the original design activity. The data may consist of the unique item specifications (see 5.4.4) for all system Configuration Items (CIs) and developmental design data and any required associated lists (see 5.4.1.2) as specified by the contract.

5.2.3 Product level. A product level TDP shall consist of those TDP elements necessary to provide the design, performance requirements, engineering, manufacturing, inspection, packaging and quality assurance provision information necessary to fully define the item and enable the procurement or manufacture of an item. The product shall be defined to the extent necessary for a competent manufacturer to produce an item, which duplicates the physical, interface, and functional characteristics of the original product, without additional design engineering effort or recourse to the original or current design activity. Product data shall reflect the approved, tested, and accepted configuration of the defined delivered item. The data may consist of product design data with all required associated lists (see 5.4.1.3); SIE design data with all required associated lists (see 5.4.2); special tooling design data 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.

5.4 TDP elements. TDP elements describes the various component parts of the TDP and are defined as follows:

5.4.1 Engineering Design Data. Engineering design data may consist of one or more of the following, dependent on the TDP type and level selected and as defined in the contract: 2D drawings, 3D native CAD models, 3D neutral CAD models or 3Di pdf viewables. The amount of detail will vary based on the TDP level required in the contract and as described below:

5.4.1.1 Conceptual engineering design data. When a level (1) Conceptual TDP is required, conceptual engineering design data shall be prepared to define general design concepts in graphic form, and include appropriate textual information required for analysis and evaluation of those concepts to include:

a. A geometric representation defining the physical shape of the product.

b. Definition of dimensions defining the overall envelope or boundary size of the component.

c. Sufficient metadata to establish ownership, identification and control, to include the following as a minimum: Nomenclature, Document/Drawing Number, Part Number, Contract Number, Design Activity Identification (e.g. CAGE Code(s)), Approved By, Approved Date, Revision Level Identification, Revision Date, and if applicable Export Control/ITAR Statements, Distribution Statements, Destruction Notices, and/or Classification Requirements,.

5.4.1.2 Developmental engineering design data and associated lists. When a level (2) developmental TDP is required, developmental engineering design data and associated lists shall be prepared to provide sufficient data to support the analysis of a specific design approach and the fabrication of prototype material for test or experimentation. Data and lists required to present a design approach may vary from simple sketches to complex engineering design data, or may be a combination of both.

a. A geometric representation defining the physical shape of the product.

b. Definition of dimensions and tolerances defining the item in sufficient detail for engineering analysis and prototype fabrication.

c. Materials, surface finishes, or other manufacturing detail sufficient for engineering analysis and prototype fabrication.

d. Sufficient metadata to establish ownership, identification and control, to include the following as a minimum: Nomenclature, Document/Drawing Number, Part Number, Contract Number, Design Activity Identification (e.g. CAGE Code(s)), Approved By, Approved Date, Revision Level Identification, Revision Date, and if applicable Export Control/ITAR Statements, Distribution Statements, Destruction Notices, and/or Classification Requirements.

5.4.1.3 Product engineering design data and associated lists. When a level (3) Product Level TDP is required, product engineering design data and associated lists shall be prepared to provide the design, engineering, and manufacturing information necessary to enable the procurement or manufacture of an item essentially identical to the original item. The product shall be defined to the extent necessary for a competent manufacturer to produce an item, which duplicates the physical, interface, and functional characteristics of the original product, without additional design engineering effort or recourse to the design activity. This together with other TDP elements forms a Product Level TDP which will be used to manufacture and support the product throughout its lifecycle. Product engineering data shall reflect the approved, tested and accepted configuration of the defined delivered item and shall consists of the following:

a. A geometric representation defining the physical shape of the product.

b. Complete definition of dimensions and tolerances defining the item in detail for full rate manufacturing purposes to include appropriate global Geometric Dimensioning and Tolerancing (GD&T) (see ASME Y14.5).

c. Materials, surface finishes, or other engineering and manufacturing detail sufficient for full rate manufacturing.

d. All notes, references, or other identifying features necessary to fully define the engineering definition of the item and as necessary for full rate manufacturing.

e. Quality assurance information necessary to ensure the item meets its intended performance.

f. Sufficient metadata to establish ownership, identification and control, to include the following as a minimum: Nomenclature, Document/Drawing Number, Part Number, Contract Number, Design Activity Identification (e.g. CAGE Code(s)), Approved By, Approved Date, Revision Level Identification, Revision Date, and if applicable Export Control/ITAR Statements, Distribution Statements, Destruction Notices, and/or Classification Requirements,.

g. Any non-graphical requirements that are needed to unambiguously define the part.

5.4.1.4 Commercial engineering design data and associated lists. Commercial engineering design data and associated lists provide engineering and technical information in support of end products, or designated portions thereof, which are commercially developed items, commercial off-the-shelf items (COTS), or items not developed at Government expense. These data and lists shall be in accordance with the commercial design documentation practices of the contractor or supplier of the item.

5.4.1.4.1 Design disclosure. The degree of design disclosure on commercial engineering design data and associated lists, whether full design disclosure or limited design disclosure, shall be as stated in the contract for each TDP element.

5.4.1.4.2 Data rights. Rights in data for commercial engineering design data and associated list shall be as stated in the contract for each TDP element.

5.4.2 Special Inspection Equipment (SIE) engineering design data and associated lists. SIE engineering design data and associated lists shall be prepared to provide the data required to manufacture or assemble SIE, which is mandatory to successfully produce the item. The SIE shall be defined in detail to the extent necessary for a competent manufacturer to manufacture or assemble SIE, which duplicates the performance characteristics of the original SIE. SIE is also known as special test equipment.

5.4.3 Special tooling engineering design data and associated lists. Special tooling engineering design data and associated lists shall be prepared to provide the data required to manufacture special tooling which is mandatory to successfully produce the item. The special tooling shall be defined in detail to the extent necessary for a competent manufacturer to produce tooling which duplicates the performance characteristics of the original tooling.

5.4.4 Specifications. Specifications shall be prepared as performance specifications or detail specifications as required in the contract.

5.4.4.1 Defense specifications. Defense specifications shall be prepared in accordance with MIL-STD-961 as coordinated, limited or interim specifications.

5.4.4.2 Program-unique specifications. Program-unique specifications shall be prepared in accordance with MIL-STD-961 as item, material, process, software, or system specifications.

5.4.4.3 Commercial Item Descriptions (CIDs). CIDs shall be prepared in accordance with the Federal Standardization Manual to describe, by functional, performance, or essential physical requirements, available commercial products or services.

5.4.5 Software documentation. Software / Firmware documentation

a. Documentation for software CIs defined in the TDP shall be prepared in accordance with

ISO/IEC 12207.

b. Documentation for firmware imbedded in the hardware defined in the TDP or SIE related to the hardware shall be prepared in accordance with ISO/IEC 12207.

5.4.6 Special Packaging Instructions (SPI) engineering design data and associated lists. Special packaging instructions, engineering design data and associated lists shall be prepared to provide the data required to manufacture special packaging which is mandatory to successfully protect, store and transport the item. The special packaging shall be defined in detail to the extent necessary for a competent manufacturer to produce packaging which duplicates the performance characteristics of the original packaging. Packaging requirements and data shall be required for the end item, and any other related item designated for separate storage or transportation (e.g. spare and repair components to the end item) or as specified in the contract.

5.4.7 Quality Assurance Provisions (QAPs). QAPs shall be prepared to identify any special test, inspections, measurements or certifications required to ensure the item being defined meets its intended performance. Form and format of the quality assurance provision shall be as required in the contract.

5.5 Preparation and management.

5.5.1 Use of Government and non-Government standardization documents. TDP documents shall not be prepared or submitted that contain requirements already defined by existing standardization documents, if these standardization documents are available in the Acquisition Streamlining and Standardization Information System (ASSIST) (https://assist.dla.mil/online/start/) or from the independent societies governing the documents. Reference these documents instead. When the requirements in such standardization documents do not completely fulfill the requirements of an item, the standardization document shall be referenced, and the TDP element shall describe the variations necessary to fulfill the requirements.

5.5.1.1 Use of international and foreign standardization documents. International Standardization Organization/International Electro-technical Commission (ISO/IEC) standardization documents adopted by the American National Standards Institute (ANSI) for use in the United States may be used to define requirements on TDP documents. Other national standardization documents of foreign countries shall not be used without the approval of the procuring activity. The use of international and foreign standardization documents in multinational programs subject to a memorandum of understanding between governments shall be governed by the terms of that agreement.

5.5.2 Reference documents. Documents referenced in a TDP element shall be furnished as part of that element, with the exception of those specified in 5.5.2.1. The following types of documents shall not be referenced in a TDP element: technical manuals, procedural manuals, maintenance manuals, company drafting or process manuals, management plans, uncontrolled documents or unreleased documents. When information essential to meeting the content of a TDP element (such as default surface texture values, test procedures, assembly requirements, etc.) is contained within such prohibited documents, that information shall be extracted from the reference document and included in the TDP.

5.5.2.1 ASSIST and non-Government standardization documents. Referenced documents such as Government and non-Government standardization documents which are available in ASSIST or from the issuing non-Government standards body (such as the American Society of Mechanical Engineers (ASME)) do not need to be submitted as part of a TDP element.

5.5.3 Existing data. Existing data shall be used when possible, provided this existing data meets the requirements listed below. For example, existing data may be engineering design data, specifications, standards, or other data already created for other purposes. Use this existing data when:

a. The rights-in-data are consistent with the contract stipulations.

b. It is furnished at a cost equal to or less than creating new data.

c. It is identified by a CAGE code, document number, title, and applicable contract number(s).

d. Any nonstandard symbols, drawing or documentation practices used are explained in the document or in a referenced document.

e. It contains a revision scheme which is compatible with the TDP element of which it will be submitted or can be modified to a compatible revision scheme.

5.5.3.1 Company standards. When the use of company standards is permitted by the contract, company standards shall meet the requirements of 5.5.3 for existing data plus the following:

a. If the company standard defines a vendor item, the standard shall provide the same information as a vendor item control document (or specification control document) for the identification and procurement of an interchangeable item, and

b. All documents referenced in the standard shall also be supplied as required by 5.5.1 and 5.5.2.

5.5.4 Language and clarity. Unless otherwise specified, TDP documents shall be in the English language. Requirements, including explanations of non-standard practices or symbols, shall be delineated clearly, concisely, and without ambiguity so that their correct interpretation is understandable by people knowledgeable in the subject matter presented.

5.6 Protecting classified information. TDPs or parts thereof containing classified information shall be protected and marked in accordance with the Department of Defense Industrial Security Manual for Safeguarding Classified Information, DOD Manual 5220.22-M and FAR Clause 52.204-2. When 3D TDP data is used, the 3D models shall display the classification markings clearly visible when the 3D model is opened or be provided in a location or manner which is clearly identifiable to the user

5.7 Protecting controlled technical information. TDPs or parts thereof, containing unclassified controlled technical information shall be protected by the contractor in accordance with DFARS Clause 252.204-7012.

5.8 Marking of technical data. TDPs or parts thereof, containing information subject to restrictions shall be marked and protected in accordance with the appropriate guidance, contract, policy, regulation or agreement. Requirements for the restriction of access, availability, proprietary data, or use, of all TDP documents prepared by or for the DoD shall be marked by inclusion of the appropriate restriction statements. Examples of restriction statements include: the rights-in-data legends in accordance with DFARS Clauses 252.228-7013 and 7014 and Export Control Warning Label in DoDI 5230.24; a distribution statement and restrictive markings in accordance with DoD Instruction 5230.24 and Directive 5230.25.Care shall be exercised to match the appropriate distribution statement with the appropriate rights-in-data legend. When 3D TDP data is used, the 3D models shall display applicable restriction markings, legends, and statements clearly visible when the 3D model is opened or be provided in a location or manner which is clearly identifiable to the user.

5.9 Contract numbers and contractor identification. When required by the contract, purchase order or applicable data item description, TDP documents shall identify the contractor and contract number under which the document is prepared or delivered, or both. This requirement does not alter current DFARS requirements for identifying contractors and prime contract numbers in rights-in-data legends.

Furthermore, contractor identifications and contract numbers in rights-in-data legends do not satisfy the requirements of this paragraph.

5.10 Inspection of TDP. TDP documents and TDP data management products and the components thereof, including documents prepared by subcontractors, shall be inspected for the following:

a. Inclusion of all data, including sub-tier references, required to meet the information content requirements of the TDP element except those identified in 5.5.2.1.

b. Accuracy of the assignment and identification of classification markings, marking and dissemination statements (for example distribution statements, export control notices, rights-in-data legends, and other special markings.)

c. Completeness and accuracy of the TDP data in describing the design of the item, its subassemblies, and component parts. The design to be described by the TDP documents is that configuration of the item the procuring activity has approved, tested, or accepted.

d. Digital submittals shall open in the appropriate software without regeneration errors.

e. National Aerospace Standard NAS 3500 “Technical Data Package: Composition, Communication, and Application” may be used to facilitate the acceptance and inspection of the TDP if required in the contract or purchase order.

5.11 Legibility and reproducibility. All data prepared or submitted shall meet the legibility and reproducibility requirements of the specification or standard controlling the media in which the data is to be delivered. As a minimum, all lines, symbols, letters, and numerals shall be readable.

5.12 CAGE codes. When CAGE codes are to be applied to documents used in TDPs and TDP elements, only valid codes shall be used. CAGE code assignment and verification shall refer to https://cage.dla.mil/.

5.13 Digital approval systems. TDP elements subject to approval may use signature or approval indicators. Approval indicators may be applied by a digital approval system. Digital approval systems shall satisfy the contracting activity requirements for uniqueness, verifiability, and sole control.

5.14 TDP data management products. When specified in the contract, the following data management products related to the management and control of TDPs shall be prepared.

5.14.1 Technical…