Change Status Data
Total Page:16
File Type:pdf, Size:1020Kb
ATTACHMENT 10 CONTINUATION OF THE TDP OPTION SELECTION WORKSHEET, BLOCK 9 AF Drawing 9579776 9579776_N.DOC CAGE CODE 98752 APPLICATION REVISIONS NEXT ASSY USED ON LTR DESCRIPTION DATE APPROVED L REVISED PER ECO 2013A0011 01 Jul 2013 G.G. M REVISED PER ECO 2015A0001 20150612 G.G. N REVISED PER ECO 2017A0013-R 20170426 B.H. ALL SHEETS ARE REV: N Distribution Statement A. Approved for public release; distribution is unlimited. UNLESS OTHERWISE SPECIFIED SIGNATURES ARE ON FILE U.S. AIR FORCE DIMENSIONS ARE IN INCHES ON AF FORM 2602 IN LGEC TOLERANCES ON ROBINS AFB, GA FRACTIONS DECIMALS ANGLES APPROVALS DATE ± .XX ± ± DRAFTSMAN TITLE Robert Yohe 95/12/08 .XXX ± CHECKER Edwin Bray 95/12/08 MATERIAL ENGINEER Edwin J. Reid 95/12/11 Product Data Specification PROJECT ENGINEER TREATMENT PROJECT AUTHORITY SIZE A.F. CODE IDENT NO. DRAWING NO. Donald Looney 95/12/11 None A 98752 9579776 FINISH RELEASE AUTHORITY SCALE REV SHEET None David Olson 95/12/11 None N 1 of 34 ENGINEERING DRAWING LAYOUT A VERTICAL 1 9579776_N.DOC CAGE CODE 98752 TABLE OF CONTENTS Paragraph Description 1. Purpose 2. Applicable Documents 3. Quantities, Distribution, and Software Identification 4. Digital Data Delivery (Sample) 5. Digital Data Delivery (Interim and Final) 6. Legacy Data 7. CAD/CAM Product Definition Data 8. Printed Board Artwork Master, Test, and Drill NC Data 9. Software and Memory Device Data 10. Metadata 11. Bill of Materials (BOM) 12. Classified Data APPENDIX A Special Characters APPENDIX B Document Types APPENDIX C Accompanying Document Kinds 2 9579776_N.DOC CAGE CODE 98752 Purpose The purpose of this document is to identify the delivery package requirements necessary to acquire compatible formatted digital engineering data into designated Air Force repositories. 1.1 Scope This document addresses the mandatory requirements for delivery of engineering data that will ensure successful loading, indexing, access, and retrieval of data with the designated digital data repositories for the Air Force. This Digital Data Description Requirement defines the content, format, media, and product definition data files preparation requirements for the digital Technical Data Package (TDP) for electronic storage into the designated digital data repositories. The TDP contains the digital product definition data for end items or products. The TDP data files are resulting products from the work task described in the solicitation. a. Product Definition Data denotes the totality of data elements required to completely define a product. Product definition data includes geometry, topology, relationship, tolerances, attributes, and features necessary to completely define a component part or an assembly of parts for the purpose of design, analysis, manufacture, test, simulation, maintenance, and inspection in the support of weapon systems. b. This Digital Data Description Requirement is applicable to acquisitions of military systems, equipment, and components. It is primarily intended for acquiring digital drawings, associated lists, models and other digital data files at the end of the Engineering and Manufacturing Development Phase and during subsequent phases of the Department of Defense (DoD) materiel life cycle. c. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Whenever ASME Y14.41 “Digital Product Definition Data Practices” is invoked in the DI-SESS-81000 Data Item Description (DID), any conflicts or duplications between these two documents shall have the requirements herein apply. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained and approved by the contractor, contracting officer, and repository point-of-contact (POC). 2.0 Applicable Documents 2.1 General The documents listed in this section are needed to meet the requirements defined in this specification. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all requirements cited in this specification. 2.2 Specifications, Standards, and Programs The following specifications form a part of this document to the extent specified herein. ASME Y14.1 – “Drawing Sheet Size and Format” ASME Y14.4M – “Pictorial Drawing” ASME Y14.24 – “Types and Applications of Engineering Drawings” ASME Y14.34 – “Associated Lists” ASME Y14.41 – “Digital Product Definition Data Practices” ANS US PRO/IPO-10001996 (IGES 5) – “Digital Representation for Communication of Product Definition Data” ANSI/EIA-656 – “I/O Buffer Information Specification (IBIS)” DoDI 5220.22 – “National Industrial Security Program” DoDI 5230.24 – “Distribution Statements on Technical Documents” RS-274X – “Extension to RS-274-D” – Interchangeable Variable Block Data Format for Positioning, Contouring, and Contouring/Positioning Numerically Controlled Machines” 3 9579776_N.DOC CAGE CODE 98752 IEEE Std. 1029.1 – “Standard for Waveform and Vector Exchange to Support Design and Test Verification (WAVES) Language” IEEE Std. 1076 – “VHDL Language Reference Manual” IPC-2221 – “Generic Standard on Printed Board Design” IPC-D-356 – “Bare Substrate Electrical Test Data Format” ISO 9660 – “Volume and File Structure of CD-ROM for Information Interchange” ISO 10149 – “Data Interchange on Read-Only 120mm Optical Data Disks (CD-ROM)” ISO 10303 – “Product Data Representation and Exchange” – AP203, AP209, AP210, AP212, AP214, AP219, AP224, AP232, AP233, AP237, AP238, AP239, and AP240 ISO 32000-1 – “Portable Document Format – Part 1: PDF 1.7” 3. Quantities, Distribution, and Software Identification: a. For quantities and distribution, refer to block 14 of the DD Form 1423 that calls out this requirement. b. As the contractor determines that a particular software tool will be used to produce CAD/CAM Product Definition Data (see paragraph 7), a notification shall be sent to the acquiring office identified in block 6 of the DD Form 1423. The notification shall identify the software name, software version, hardware platform, and vendor of the software. The prime contractor shall obtain the same letter from all of their applicable subcontractors/vendors on this contract. 4. Digital Data Delivery (Sample): The contractor shall submit four (4) representative samples of each digital data format to be submitted for verification of procedures and processing into a government data repository at intervals called out in the DD Form 1423. The representative samples shall include data in the appropriate digital formats (native, neutral, PDF, legacy data, Gerber data, design models, etc. where applicable). The representative samples shall also have traceability among one another with the submitted samples. Since the intent of the sample is for Government review of the file types for compatibility and delivery compliance purposes, it is imperative that any and all file types anticipated to be in the final TDP delivery be included as samples for preliminary review. Samples of the metadata spreadsheet, Bill of Materials (BOM), and Summary Report files shall be included. 5. Digital Data Delivery (Sample and Final): Digital data shall be delivered, as updates require for interim delivery and as a final delivery of all updated data, in accordance with the DD Form 1423, which calls out this requirement and as follows: a. Files for both sample and final drawing deliveries shall have multiple drawing sheets per filename delivered for each unique document or drawing number. The sheets shall be in a single sheet per view format such as worksheets in a spreadsheet file or book pages. The filenames for all digital data formats for the entire delivery shall be unique. b. A copy of the translation (such as STEP, IGES, or EDIF) processing or error log file created during the generation of the neutral model files (3D/2D mechanical models and electronic design data) shall also be submitted in digital form. This file shall not be reflected in entries in the Metadata Spreadsheet. c. On digital drawing formats the sheet layout, border, title block, revision block, other contractually imposed format conditions, and other conventions of engineering drawing format including definition and use of explicit scaling factors shall be integral to the digital data file. Filenames for all digital data shall include the appropriate file extensions where practical or appropriate and shall be included in the metadata spreadsheet filename column. Engineering drawings shall be drawn using a CAD system, except for legacy data according to paragraph 6, and shall conform to the DD Form 1423. d. All pertinent entities that comprise the final digital file shall be viewable upon opening of the digital data files. This prevents the user from having to search for layers, to turn on or off in order to view the final drawing and model entities. e. File layer or level conventions as stated in paragraph 5.d., which are used, shall be identified for all data residing in the digital data file. 4 9579776_N.DOC CAGE CODE 98752 f. Metric dimensioning is applicable only when interfacing with existing items that were dimensioned in metric. When metric dimensioning is required, the drawings shall define the interface in metric accompanied by a parenthetical equivalent decimal inch dimension. g. Revisions made to the digital dataset shall accurately and precisely represent the change in dimensions to the geometry of the object or assembly to ensure the share-ability of the represented data. h. Do not import or paste raster images, such as TIF, GIF, JPG, and Bitmap into CAD-generated vector drawings or document formats. The exception to this requirement is when the following conditions are met: The graphics do not need to be edited at a later time (such as a photograph or diagram), a legible view-only file can be delivered containing the graphics (reference paragraph 7.b view-only delivery format requirements), or they represent drawings delivered according to ASME Y14.4M. These exceptions also require prior approval by the acquiring activity. i. Files shall be delivered in separate subdirectories by product definition data type (such as native, neutral, drawings, documents, etc.) to simplify processing.