Attachment_4_-_MIL-STD-31000A.pdf

NOT MEASUREMENT

SENSITIVE

MIL-STD-31000A

26 February 2013

SUPERSEDING

MIL-STD-31000

05 November 2009

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 provides requirements for the deliverable data products associated with a technical data package (TDP) and its related TDP data management products. A TDP contains elements, is described by a level and type, and may have associated metadata and supplementary technical data. TDP contains a sub-set of product data and product data is a sub-set of technical data. These relationships are shown in the hierarchical breakdown of data in Figure 1.

Comments, suggestions, or questions on this document should be addressed to: Commander, US

Army ARDEC, ATTN: RDAR-QES-E, 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 9341 AREA SESS

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

Source: https://assist.dla.mil -- Downloaded: 2018-08-30T16:06Z Check the source to verify that this is the current version before use.

mailto:usarmy.picatinny.ardec.list.ardec-stdzn-branch@mail.mil https://assist.dla.mil./

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.

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.

Source: https://assist.dla.mil -- Downloaded: 2018-08-30T16:06Z Check the source to verify that this is the current version before use.

FEDERAL STANDARDS.

FED-STD-376 Preferred Metric Units for General Use by the Federal Government

DEPARTMENT OF DEFENSE STANDARDS.

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

MIL-STD-963 Data Item Descriptions (DID)

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 or from the

Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-

5094.)

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.39M Federal Logistics Information System (FLIS) Procedures

Manual

DoD Manual 5220.22-M Department of Defense Industrial Security Manual for

Safeguarding Classified Information.

DoD Directive 5230.24 Distribution Statements on Technical Documents

DoD Directive 5230.25 Withholding of Unclassified Technical Data From Public

Disclosure

DoD 5010.12-M Procedures for the Acquisition of Technical Data

DFARS Part 211 Defense Federal Acquisition Regulation Supplement for Describing

Agency Needs

DFARS Part 227 Defense Federal Acquisition Regulation Supplement for

Patents, Data and Copyrights

DFARS Part 252 Defense Federal Acquisition Regulation Supplement for

Solicitations, Provisions and Contract Clauses

FAR 11.001 Federal Acquisition Regulation, Describing Agency Needs, Definitions

Federal Cataloging Commercial and Government Entity (CAGE)

Handbook H4/H8 Codes

Source: https://assist.dla.mil -- Downloaded: 2018-08-30T16:06Z http://quicksearch.dla.mil/

(Applications for copies of DoD Manual 5520.22-M and DoD Directive 5230.24 are available from the

Defense Technical Information Center (DTIC), http://www.dtic.mil. The Federal Cataloging Handbook

H4/H8 is available from the Commander, Defense Logistics Services Center, and Battle Creek, MI

49037-3084 at http://www.dlis.dla.mil/hseries.asp. 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.)

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.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 http://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/portal/site, or IEEE Service Center, 445

Hoes Lane, P.O. Box 1331, Piscataway, NJ 08854-1331.)

AMERICAN NATIONAL STANDARDS INSTITUTE

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

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

Check the source to verify that this is the current version before use.

http://www.dtic.mil/ http://www.dlis.dla.mil/hseries.asp http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html http://www.dtic.mil/whs/directives/.)

http://www.asme.org/ http://www.ieee.org/portal/site http://www.ansi.org/

NATIONAL AEROSPACE STANDARDS

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)

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 Associated list. A tabulation of engineering information pertaining to an item depicted on an engineering drawing or on a set of drawings. For example: parts list, data list, and index list. (See ASME

Y14.24).

3.1.2 Commercial And Government Entity (CAGE) code. A five character code listed in Cataloging

Handbook H4/H8, Commercial and Government Entity Code, which is assigned to commercial and

Government activities that manufacture or develop items, or provide services or supplies for the

Government. When used with a drawing number or part number, the CAGE Code designates the design activity from whose series the drawing or part number is assigned. The CAGE Code was previously called manufacturer's code, code identification number or Federal Supply Code for Manufacturers

(FSCM).

3.1.3 Commercial drawings. Drawings 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.4 Commercial item. A product, material, code, component, subsystem, or system sold or traded to the general public in the course of normal business operations at prices based on established catalog or market prices. (FAR 11.001, definition of Commercial Product)

3.1.5 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.6 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.7 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.8 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.9 Conceptual design data. Data such as drawings or 3-Dimensional (3D) digital models, which describe the engineering concepts on which a proposed technology or design approach is based.

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

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

3.1.12 Data Item Description (DID). A completed document that defines the data required of a contractor. The document specifically defines the data content, format, and intended use.

(MIL-STD-963)

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

3.1.13.1 Current Design Activity. 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. The design activity originally responsible for the design and identification of an item whose drawing number and activity identification is shown in the title block of the drawings and associated documents.

3.1.14 Design maturity. The extent to which the final design or configuration of an item has been defined by the engineering process. For example, the design of a sheet metal cover having all holes in its mounting hole pattern fully dimensioned and toleranced for final size, location and orientation would be considered to be more mature than the design of a similar cover having its mounting hole pattern defined as “Drill at assembly".

3.1.15 Detailed design data. Technical data that describes the physical configuration and performance characteristics of an item or component in sufficient detail to ensure that an item or component produced in accordance with the technical data will be essentially identical to the original item or component.

3.1.16 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. A specification that contains both performance and detailed requirements is still considered a detail specification. Both defense specifications and program-unique specifications may be designated as a detail specification. (MIL-STD-961)

3.1.17 Developmental design data. Data which describe the physical and functional 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 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)

3.1.19 Drawing format. The arrangement and organization of information within a drawing is called drawing format. 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)

3.1.20 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.21 Limited design disclosure model. A Computer Aided Design (CAD) 3-Dimensional model sufficiently defined to provide a visual understanding of the item, but which does not contain full design disclosure. Generally key interface characteristics and features such as weight and center of gravity will be sufficiently defined for the intended purpose. Sometimes referred to as a shrink-wrap, visualization, or cosmetic model.

3.1.22 Metadata. Metadata is generally defined to be data about data. For the purpose of this standard, Metadata is defined to be data about a design and its defining documents/models.

Metadata is used by the Procuring Activity to store, manage, and provide access to TDP elements.

3.1.23 Non-Government standardization document. 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. 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. Both defense specifications and program-unique specifications may be designated as a performance specification. (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 drawings. Engineering drawings which provide the design, engineering, manufacturing and quality support information necessary to permit a competent manufacturer to produce an interchangeable item which duplicates the physical and performance characteristics of the original design without additional design engineering or recourse to the design activity.

3.1.27 Product model data. A 3 dimensional (3D) geometric representation of a design that includes digital information required for full product definition.

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

3.1.29 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.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 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 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 (ST). Unique tooling which is mandatory to 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 ST 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 prepared to support acquisition 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 configuration 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 Package (TDP). A technical description of an item adequate for supporting an acquisition, production, engineering, and logistics support (e.g. Engineering Data for Provisioning, Training, and Technical Manuals). The description defines the required design configuration or performance requirements, and procedures required to ensure adequacy of item performance. It consists of applicable technical data such as models, drawings, associated lists, specifications, standards, performance requirements, QAP, software documentation and packaging details.

3.1.38 Technical data package document. A document that is part of a TDP element.

3.1.39 Technical data package element. 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.

3.1.40 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.41 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. This section covers general requirements for Technical Data Packages. TDPs define the physical and functional characteristics of the accepted configuration of the item and its subordinate assemblies, subassemblies, and parts thereof. TDP levels, types, elements and TDP data management products shall be identified in accordance with this standard and applicable

Data Item Descriptions (DID), as tailored and imposed through the TDP Option Selection

Worksheet (Figure 2) or as defined in block 16 of the 1423, Contract Data Requirements Lists

(CDRL) in contracts, purchase orders, and Military Interdepartmental Procurement Requests

(MIPRs).In addition, provisions for the inclusion of minimum software version(s) required to view / open the TDP data set and label the file(s) / media accordingly for usability / accessibility shall be made. See Appendix A for guidance on selection of TDP elements and data management products.

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 the highest type of engineering drawing/model required for quantity production of the item or system by the original developer or any other capable producer. TDPs shall consist of one of three Levels:

(1) Conceptual Level

(2) Developmental Level

(3) Production Level

4.3 TDP types. TDP Types describe 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 comes in one of the following type subsets:

a. 3D digital models only

b. 3D digital models with associated 2D drawings

4.4 TDP elements. TDP Elements describe the various component parts of the TDP.

a. Conceptual design drawings/models.

b. Developmental design drawings/models and associated lists. c. Production drawings/models and associated lists.

d. Commercial drawings/models and associated lists.

e. Special Inspection Equipment (SIE) drawings/models and associated lists. f. Special

Tooling (ST) drawings/models and associated lists.

g. Specifications.

h. Software documentation.

i. Special Packaging Instruction (SPI) documents, drawings/models and associated lists.

j. Quality assurance provisions (QAP).

4.5 TDP metadata and supplementary technical data. TDP metadata and supplementary technical data are deliverable data products used by the Procuring Activity to better acquire and support the end product defined by the TDP.

4.5.1 Metadata. When Metadata is required, it shall be delivered in accordance with the contract. Metadata consist of data from and data about TDP elements. The Metadata is used by the Procuring Activity to store, manage, manipulate, and provide access to TDP elements.

4.5.2 Supplementary technical data. When supplementary technical data is required, it shall be delivered in accordance with the contract.

4.6 TDP data management products. TDP Data Management Products are used by the

Procuring Activity to control and manage the TDP creation process.

a. Source control drawing/model approval request.

b. Drawing/model number assignment report.

c. Proposed critical manufacturing process description.

4.7 Preparation and management.

4.7.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) (http://assist.daps.dla.mil) 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.

4.7.1.1 Use of international and foreign standardization documents. International

Standardization Organization / International Electrotechnical 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.

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

4.7.2.1 ASSIST and non-Government standardization documents. Referenced documents available in ASSIST and non-Government standardization documents available 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.

4.7.3 Existing data. Use existing data when possible, provided it meets the following requirements:

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.

4.7.3.1 Company standards. When the use of company standards is permitted by the contract or purchase order, company standards shall meet the requirements of 4.7.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 drawing (or specification control drawing) for the identification and procurement of an interchangeable item, and

b. All documents referenced in the standard shall also be supplied as required by 4.7.3.1.

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

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

When 3D TDP data is used, the 3D digital models shall display classification marking clearly visible when the 3D digital model is first opened.

4.9 Marking of technical data. TDPs or parts thereof, containing information subject to restrictions shall be protected in accordance with the appropriate guidance, contract, 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; a distribution statement in accordance with DoD

Directive 5230.24 and 5230.25; and export control notice. 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 digital models shall display applicable restriction markings, legends, and statements clearly visible when the 3D digital model is opened or be provided in a location or manner which is clearly identifiable to the user.

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

4.10.1 Application of contract numbers and contractor identification. When contract numbers and contract identifications are required on TDP documents, they shall meet the legibility and reproducibility requirements applicable to the document and be within the prescribed borders or margins of the document or be clearly identified within the electronic dataset or model.

4.11 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 4.7.2.1.

b. Accuracy of the assignment and identification of security markings, restriction 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. Electronic submittals shall open in the appropriate software without regeneration errors.

e. The use of 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.

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

4.13 CAGE codes. When CAGE Codes are to be applied to documents used in TDPs and

TDP elements, only valid codes identified in the Federal Cataloging Handbook H4/H8 shall be used.

4.13.1 Type CAGE codes. Type “A" or “E” codes shall be used to identify design activities and vendors' part or identifying numbers and sources of supply except when industry marketing customs dictate otherwise. When the design activity or vendor of a specific item customarily licenses a distributor to perform the final steps of manufacture exclusively, the Type F code for the distributor may be used (DOD 4100.39, Vol 10 Table 90).

4.14 Metric documents. When the contract or purchase order specifies the use of the metric system (SI), TDP documents shall be identified as metric documents and conform to FED-STD-

376.

4.15 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. DETAILED REQUIREMEMENTS.

5.1 General. This section covers the requirements for technical data packages which may include 2D drawings, 2D drawings based on 3D digital models, or standalone 3D digital models and their formats.

5.2 Requirements for 3D TDPs. When 3-dimensional models are required for a production level TDP, the models shall be a complete, accurate, fully defined representation of the item and contain every feature the item being represented is intended to contain. All information necessary to adequately define the item shall be contained in, or associated with, the 3D digital model to include but not limited to dimensions, materials, tolerances, datums, drawing notes, revision data, etc.

5.2.1 2D drawings based on 3D digital models. Data on 2D drawings based on the 3D digital models shall be sourced to the maximum extent possible from the 3D digital model. There shall be no conflict in data between the 3D digital model and its associated 2D drawing.

5.2.2 Format of 3D TDP. Format of the 3D TDP based models shall be as directed by the contract or purchase order. In general, 3D digital models shall be in accordance with (ISO) 10303

Standard for the Exchange of Product model data (STEP), or in a native 3D CAD format capable of being exported to ISO

10303 STEP format.

5.2.3 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, etc.), a 3D digital model of the subcomponent shall be provided. The subcomponent’s 3D digital model need not be fully defined, but shall be sufficient to provide adequate visualization, interface characteristics, accurate weight and center of gravity information as required (i.e.

cosmetic model) (see para 3.1.21).

5.2.4 Model Organization Schema: When a 3D TDP is provided in accordance with 5.3.2.2, then all annotations and views contained within the model shall be done in accordance with a

Model Organization Schema that is compliant with or can be mapped to the one defined in

Appendix B of this document. If a different Model Organization Schema is used, a document defining the mapping of the elements of that schema to the one referenced in Appendix B should be required.

5.3 TDP levels, types, elements and associated data. TDPs shall consist of one or more of the following TDP levels, types and elements as specified in the contract or purchase order and

TDP Option Selection Worksheet.

5.3.1 TDP Levels.

5.3.1.1 Conceptual level. - A conceptual design TDP shall consist of those TDP elements necessary to define design concepts in graphic form, and include appropriate textual 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.3.3.7) and can be supported by Conceptual design drawings and/or models (see 5.3.3.1) as specified by the contract.

5.3.1.2 Developmental level. - A developmental prototype 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 organization or with assistance from the original design organization. The data may consist of the unique item specifications (see 5.3.3.7). for all system component

Configuration Items (CIs) and can be supported by developmental design drawings and/or models along with any required associated lists (see 5.3.3.2) as specified by the contract.

5.3.1.3 Production level. - A production level TDP shall consist of those TDP elements necessary to provide the design, engineering, manufacturing, inspection, packaging and quality assurance provisions information necessary to 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 current design activity.

Production data shall reflect the approved, tested, and accepted configuration of the defined delivered item. The data may consist of product drawings and/or models along with all required associated lists (see 5.3.3.3); SIE drawings and/or models along with all required associated lists

(see 5.3.3.5); ST drawings and/or models along with all required associated lists (see 5.3.3.6);

specifications (see 5.3.3.7); software documentation (see 5.3.3.8); SPI drawings and/or models along with all required associated lists (see 5.3.3.9); and QAP(see 5.3.3.10) as specified by the contract.

5.3.2 TDP types. TDP Type describes the form and format of the data as imposed by the applicable data item descriptions, TDP Option Selection Worksheet (Figure 2) and Contract Data

Requirements Lists (CDRL) in the contract, purchase orders, and Military Interdepartmental

Procurement Requests (MIPRs).

5.3.2.1 Type 2D: 2-Dimensional Technical Data Package (2D TDP) – A 2D TDP is based on

2 dimensional engineering drawings. 2D engineering drawings can be manually generated, or generated in a digital form.

5.3.2.2 Type 3D: 3-Dimensional Technical Data Package (3D TDP)- A 3D TDP is based on computer based 3–dimensional models that are capable of generating, when required, 2D engineering drawings. Type 3D TDPs shall consist of one of the following type subsets:

a. 3D digital models only

b. 3D digital models with associated 2D drawings

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

5.3.3.1 Conceptual design drawings/models. Conceptual design data shall be prepared to define design concepts in graphic form, and include appropriate textual information required for analysis and evaluation of those concepts. If 3D CAD Models form the design definition without 2D drawings they shall include the following information:

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

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

c) Annotated note that defines all default tolerances or appropriate global Geometric Dimensioning and Tolerancing (GD&T) as it applies to the product at the design level.

d) All material information that is known at the level shall be called out in either a general annotated note and/or in the system parameters of the model.

e) Finish requirements should be called out in a general annotated note.

f) Information typically referred to as “title block” information shall be noted in the product definition. This information should include the following as a minimum; Part

Number, Contract Number, Design Authority CAGE Code, Drawn By, Approved By, ITAR statements, Distribution statements, Classification requirements, Revision Level and Revision Date.

5.3.3.2 Developmental design drawings/models and associated lists. Developmental design drawings/models 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 drawings, or may be a combination of both. If 3D CAD Models are required at the Developmental Level they shall include the following information:

Elements “a” through “f” of section 5.3.3.1

a) All nonstandard, key and critical items that are non-graphical in nature shall be called out in a product definition.

b) All nonstandard, key and critical dimensions shall be called out in the product definition.

5.3.3.3 Product drawings/models and associated lists. Product drawings/models 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 current design activity. Product data shall reflect the approved, tested and accepted configuration of the defined delivered item. This together with other TDP elements forms a

Production Level TDP which will be used to support the product throughout its lifecycle. If 3D

CAD Models are required they shall include the following information:

Elements “a” through “f” of section 5.3.3.1

a) All non-graphical requirements that are needed to unambiguously define the part shall be called out in the product definition.

b) All dimensions needed to unambiguously define the product shall be called out in the product definition.

5.3.3.4 Commercial drawings/models and associated lists. Commercial drawings/models 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.3.3.4.1 Design disclosure. The degree of design disclosure on commercial drawings/models and associated lists, whether full design disclosure or limited design disclosure, shall be as stated in the contract or purchase order.

5.3.3.4.2 Data rights. Rights in data for commercial drawings/models and associated list shall be as stated in the contract or purchase order.

5.3.3.5 Special Inspection Equipment (SIE) drawings/models and associated lists. SIE drawings/models 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.3.3.6 Special Tooling (ST) drawings/models and associated lists. ST drawings/models and associated lists shall be prepared to provide the data required to manufacture special tooling which is mandatory to successfully produce the item. The ST 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.3.3.7 Specifications. Specifications shall be prepared as performance specifications or detail specifications as required in the contract or purchase order.

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

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

5.3.3.7.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.3.3.8 Software documentation. Software / Firmware documentation

a) Documentation for software CIs defined in the TDP shall be prepared in accordance with ASME Y14.24.

b) Documentation for firmware imbedded in the hardware defined in the TDP or

SIE related to the hardware shall be prepared in accordance with ASME Y14.24.

5.3.3.9 Special Packaging Instructions (SPI) drawings/models and associated lists. Packaging requirements and data shall be as specified in the contract or order. Special packaging instructions, drawings/models 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.

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

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

5.4.1 Source Control Drawing approval request. Source control drawing approval request shall be prepared and submitted to the Procuring Activity specified in the contract or purchase order as having approval authority. Each potential source control item shall be approved by the

Procuring Activity prior to inclusion of the source control drawing in the TDP.

5.4.2 Drawing/Model number assignment report. A drawing/Model number assignment report shall be prepared to identify and describe the use of Government drawing/Model numbers by the contractor.

5.4.3 Proposed critical manufacturing process description. Proposed critical manufacturing process descriptions shall be prepared to describe manufacturing processes, which are critical to meeting the design requirements of the item. The process shall be approved as critical by the

Procuring Activity cited in the contract or purchase order as having approval authority before it is designated as mandatory in TDP documents.

6. NOTES.

(This section contains information of a general or explanatory nature, which may be helpful, but is not mandatory.)

6.1 Intended use. TDP elements procurable under this standard are intended for use in a wide variety of functions in the life cycle of materiel developed for the Department of Defense. Some examples of these functions are design evaluation, design development, provisioning, procurement (competitive and non-competitive), manufacture, transportation, installation, maintenance, modification, and engineering and logistics support. TDP data management products are intended for use by the Procuring Activity in ensuring that TDP elements acquired under this standard conform to contractual requirements.

6.2 Acquisition requirements. Acquisition documents should specify the following:

a. Title, number, and date of this standard.

b. If required, the specific issue of individual documents referenced. (See 2.0) and 4.4)

c. The TDP level, deliverable data products and elements to be supplied. (See 4.2, 4.3

d. The TDP data management products to be supplied. (See 4.5 and

Appendix A)

e. Whether or not company standards are permitted. (See 4.7.3.1)

f. Completed TDP Option Selection Worksheet(s). The TDP Option Selection

Worksheet(s) are used to specify options and tailoring for models, drawings and specifications being acquired as TDP elements.

g. Whether or not subcontractor identifications and subcontract numbers are required in accordance with 4.10; and if so, the location and method of application.

6.3 Data requirements. This standard has been assigned an Acquisition Management

Systems Control number authorizing it as the source document for the following DIDs. When it is necessary to obtain the data, the applicable DIDs should be listed on the Contract Data

Requirements List (DD Form 1423).

TABLE 1. Data requirements.

DID Number DID Title Suggested

Tailoring

Reference

Paragraph

DI-SESS-81001E Conceptual Design Drawings/Models Appendix A A.2.4.1

DI-SESS-81002F Developmental Design Drawings/Models and

Associated Lists

Appendix A A.2.4.2

DI-SESS-81000E Product Drawings/Models and Associated Lists Appendix A A.2.4.3

DI-SESS-81003E Commercial Drawings/Models and Associated

Lists

Appendix A A.2.4.4

DI-SESS-81004E Special Inspection Equipment Drawings/Models and Associated Lists

Appendix A A.2.4.5

DI-SESS-81008E Special Tooling Drawings/Models and Associated

Lists

Appendix A A.2.4.6

DI-SESS-81010E Source Control Drawing Approval Request Appendix A A.2.5.1.b

DI-SESS-81011E Drawing/Model Number Assignment Report Appendix A A.2.5.2.b

DI-SESS-81012E Proposed Critical Manufacturing Process Description

Appendix A A.2.5.3.b

DI-CMAN

80776A

Technical Data Package Appendix A A.2.4.3

The above DID's were current as of the date of this standard. The ASSIST database should be researched at http://quicksearch.dla.mil to ensure that only current and approved DID's are cited on DD Form 1423.

6.3.1 DIDs for specifications. Applicable DIDs and tailoring instructions for acquiring performance, detailed, and program-unique specifications are specified in MIL-STD-961.

6.3.2 DIDs for software documentation. Applicable “Information items” (a commercial equivalent to a DID) for acquiring software documentation (also known as software lifecycle data) are specified in ISO/IEC 12207.

6.3.3 DIDs for packaging data. Applicable DIDs and tailoring instructions for acquiring packaging data are specified in MIL-STD-2073-1.

6.3.4 DID for Metadata and supplementary technical data. Since the specific data content and format for Metadata and supplementary technical data are site or program specific, the Procuring

Activity will need to specify what they require. See MIL-STD-963 for instructions concerning the preparation of DIDs.

6.4 Supersession history. MIL-STD-31000, dated 5 November 2009 replaced MIL-DTL-

31000C, dated 9 July 2004; MIL-T-47500(MI) dated 24 March 1989; MIL-T-47500/1(MI) dated 24 March 1989; MIL-T-47500/2(MI) dated 24 March 1989; MIL-T-47500/3(MI) dated 24 March

1989; MIL-T-47500/4(MI) dated 24 March 1989; MIL-T-47500/5(MI) dated 24 March 1989; and

MIL-T-47500/6(MI) dated 24 March 1989.

6.5 Basic engineering…