U.S. Department of Defense MIL-STD-31000B — MIL-STD-31000B Technical Data Packages — DoD Standard Manual PDF

Downloaded from https://www.everyspec.com MIL-STD-31000B APPENDIX A 4.0), STEP AP 203 E2, 3D PDF with PRC (ISO 14739), or other unambiguous digital format specifications. Other format details should be provided as required in Block 6. Applicability of Standards—for example, specifying ASME Y14.5 and ASME Y14.41, for fully annotated 3D models. A.3.2.3 Block 3. CAGE code and document numbers. When contractor CAGE code and document numbers are specified, the documents will be identified with the CAGE code and document numbers of the contractor or subcontractor having design activity responsibility.

Usually the Government will not be able to assume control of the engineering design data originals (masters), except through a subsequent data acquisition action. If the Government intends to take delivery of the engineering design data originals and to assume design activity responsibility at some time in the future, then the documents should be identified with a Government CAGE code and Government document numbers. If the procuring activity has already determined the CAGE code and Government document numbers to be used, the CAGE code should be entered in the “USE CAGE CODE” block and the range of document numbers entered in the “USE DOCUMENT NUMBERS” block.

If the procuring activity has not determined the Government CAGE code and Government document numbers which are to be used, then the Government activity that will specify this information should be identified in the “TO BE ASSIGNED BY:” block. A.3.2.4 Block 4. Drawing formats and/or 3Di viewable format. These options specify the drawing or 3Di viewable format to be used. A.3.2.5 Block 5. TDP elements required.

This option determines the elements of the TDP used to fulfill the design disclosure requirements of the TDP element to be delivered and gives the procuring activity the authority to direct the contractor as to which types of element(s) to use by the individual selection of each element. This may be further tailored for each component, subassembly or part. A.3.2.6 Block 6. Applicability of Standards. This block is used to indicate the applicability of ASME standards. A.3.2.7 Block 7. Associated list. This block is used to define the Government’s requirements for associated lists as defined in ASME Y14.34. A.3.2.7.1 Parts lists.

Either “INTEGRAL” or “SEPARATE” or “CONTRACTOR SELECT” should be selected. This option requires the contractor to use either an integral or separate parts list for the specific item or part being documented. Use of separate parts lists is not recommended, especially with type 3D TDPs. A.3.2.7.2 Data lists. Select “REQUIRED” if applicable. Data lists aid in assembling larger sets of design data. Therefore, data lists should be required on most acquisitions of complex items. When data lists are required, the contractor will be given guidance as to the levels of assembly at which they are required.

For example, an electronic system composed of input and output sections made up of equipment racks containing replaceable drawers may require data lists at the drawer, rack, section and system (or end-item) level. Other terms for the required levels may be used. A.3.2.7.3 Index lists. Select “REQUIRED” if applicable. The assembly level at which index lists are required should be specified. A.3.2.7.4 Wiring lists. A wiring list is prepared to provide information necessary for making wire connections. A wire list may be prepared for one or more related assemblies. Either “INTEGRAL”, “SEPARATE” or “CONTRACTOR SELECT” should be selected.

This option identifies the type wiring lists for the specific item or part being documented. Use of separate wiring lists is not recommended, especially with type 3D TDPs. A.3.2.7.5 Application lists. Select either “INTEGRAL”, “SEPARATE”, “PLM MAINTAINED” or “CONTRACTOR SELECT” if applicable. This option identifies the type application lists for the specific item or part being documented, or that the application will be maintained is a PLM system. 31