Downloaded from https://www.everyspec.com MIL-STD-31000B 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. 19