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