Downloaded from https://www.everyspec.com MIL-STD-31000B 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 Data Package List (TDPL). A TDPL shall be prepared as an index to identify all documents contained in the TDP. The TDPL format shall be as described in the contract (reference DID- SESS-82238), but as a minimum shall list all documents in the TDP by nomenclature, document number and CAGE code, document revision and date. 5.14.2 Source control document approval request. Source control document approval request shall be prepared and submitted to the procuring activity specified in the contract as having approval authority.
Each potential source control item shall be approved by the procuring activity prior to inclusion of the 20