CDRL_A001_RDS_(Product_Drawings).docx

DEPARTMENT OF THE AIR FORCE

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

WRIGHT-PATTERSON AIR FORCE BASE OHIO

27 January 2017

MEMORANDUM FOR AFMC/WLNCC

ATTENTION: Megan Hilderbrand

FROM: AFLCMC/LZPEM

285 Cochran Street Robins AFB GA 31098-1669

SUBJECT: Response to Email Request for an engineering data CDRL, System HC-130H Retardant Delivery System, EDATS- 2014-39.

1. The subject Statement of Work has been reviewed by this office. Request the SOW document be amended as follows:

9.0 Engineering Data: The contractor shall develop/produce/maintain and delivers a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision M (CAGE 98752), reference attached DD Form 1423 Block 16.

[DI-SESS-81000E/T]

2. Request the Contracting Officer (CO) assure that the following actions occur:

a. Insure that each solicitation and contract is structured IAW DFARS 227-7103-1(b)(3) and CHAPTER 5 of DoD5010.12-M as noted:

(1) Paragraph C5.2.1 states “The contractor will have to prepare certain data as a natural consequence of contract performance. Design, development, testing, and production tasks will generate certain data; whether or not a requirement is identified in a DD Form 1423-1and delivery is requested. This factor is the basis for what is called the "over and above concept" for pricing data; the price paid for a data item will be based on what it costs the contractor to furnish that item, over and above the costs the contractor would incur if it were not required at all.”

(2) Para. C5.1.2 states ".....contracting officers, program managers, and technical data management personnel are encouraged to require contractors to separately price each requirement for technical data."

b. Request the contracting office review the solicitation and resulting contract for compliance with the following clauses in accordance with DFARS 227.4:

DFARS TITLE

227.7102 Commercial items, components, or processes

227.7102-1 Policy

227.7102-2 Rights in technical data

227.7103-1 Policy

227.7103-2 Acquisition of technical data

227.7103-3 Early identification of technical data to be furnished to the Government with restrictions on use, reproduction or disclosure

227.72 Rights in computer software and computer software documentation

227.7202 Commercial computer software and commercial computer software documentation.

(1). Request that the following clauses are incorporated into the contract:

252.227-7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.(Per 227.7203-6(a)(1))

252.227-7015 Technical Data – Commercial Items

252.227-7016 Rights in Bid or Proposal Information

252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions

252.227-7019 Validation of Asserted Restrictions – Computer Software

252.227-7030 Technical Data - Withholding of Payment

252.227-7037 Validation of Restrictive Markings on Technical Data

252.246.7001 Warranty of Data

52.227-21 (a and b) FAR Clause - Technical Data, Declaration, Revision, and Withholding of Payment- Major Systems

c. Request that a copy of the solicitation/contract be forwarded to AFLCMC/LZPEM.

3. Request the Contracting Officer (CO) prohibit the use of Single Process Initiatives (SPI) to include Core Business Manuals (CBM) or any common processes which pertain to the development and delivery of a Technical Data Package (TDP):

Request the CO assure that the contract does not invoke the use of SPI's, CBMs, or any internal contractor common processes in lieu of ASME Standards and Military Standards which pertain to the development and delivery of a TDP. The SPI’s and CBM’s consolidate or eliminate necessary specifications and standards in TDP’s thus prohibiting future competitive acquisitions.

4. The data required by the tasking wording and DD Form 1423-1 will be utilized for logistic support purposes, to include competitive reprocurement in the acquisition of spares. This data will be utilized by logistics personnel, to include data managers, system engineers, equipment specialists, item managers and logistics managers. If this data is not procured, logistic support may be adversely affected. Requirements for engineering data are driven by the following:

a. AF Policy Directive 63-1/AFPD20-1 paragraphs 3.22 and 3.33 state:

(1) “Prior to issuance of a contract solicitation for acquisition of a system, subsystem, or end-item, the SPM/PM/PGM shall assess Air Force long-term technical data needs for the life cycle and provide for technical data rights to meet Air Force acquisition and sustainment strategies. Sufficient technical data, to support life cycle strategies, shall be acquired and maintained to produce, reprocure, maintain, repair, test, or modify weapon systems, systems, subsystems, and end-items.”

(2) “SPM/PMs shall establish requirements addressing quality and manage the quality of their assigned product(s). All programs shall ensure that effective quality management system requirements flow down to all levels of the supply chain to ensure product quality (including design, manufacturing, performance, reliability, maintainability, and deficiency reporting) throughout the life cycle.”

b. AFI 63-101/20-101 paragraph 6.12 states:

(1) Data and Data Rights. The PM shall assess long term data and data rights requirements and corresponding acquisition strategies prior to initiating a RFP to acquire systems, subsystems, or end-items to ensure they provide for rights, access, or delivery of data that the Government requires for systems sustainment and to maintain competition throughout the life cycle. The PM shall address the data rights strategy including the rationale for acquisition and\or non-acquisition of data and data rights at milestones, ASPs, and reviews and shall document the strategy in the Technical Data Rights Strategy and associated data planning documents. The Technical Data Rights Strategy is integrated within the AS and is required for all ACAT programs. Source selections shall consider Government rights to data and include pricing options that correspond to the data and data rights recommended as part of the data strategy. The burden of proof that data is proprietary lies with the contractor. If not acquiring technical data, computer software licenses, or associated intellectual property rights necessary for organic support, a summary of the business case analysis justifying that decision must be approved by the MDA. The PM shall obtain legal counsel when addressing Data Rights or Intellectual Property issues.

6.12.1 The PM shall ensure the program data rights strategy, including the performance work statement (PWS) or SOW for development, production, deployment, and sustainment (for all applicable phases) includes appropriate data rights requirements, access, and necessary deliverables, or options for data and equipment deliverables required to support:

6.12.1.1. Organic source of repair and/or supply decisions.

6.12.1.2. Government Core depot maintenance capability requirements.

6.12.1.3. Expeditionary logistics footprint requirements.

6.12.1.4. Engineering data requirements needed for such activities as OSS&E assurance, integrity programs, sustaining engineering, reliability management, and configuration management.

6.12.1.5. Technical orders (TOs).

6.12.1.6. Reprocurement/modification/upgrade.

6.12.1.7. Demilitarization/Disposal.

6.12.1.8. Open architecture.

6.12.1.9. Information assurance strategies.

6.12.1.10. Technology refreshment or enhancement.

6.12.1.11. Training and training program information.

6.12.1.12. Spare parts procurement

6.12.1.13. Testing and Evaluation

6.12.1.14. Intelligence Mission Data production

6.12.1.15. Contractor Logistics Support

c. AFI 23-105, Spares Breakout Program, paragraph 5.3 states Program Offices:

(1) 5.3.1. Determine the complete data needs, including reprocurement data for inclusion in contracts.

(2) 5.3.2. Give written notification, with rationale, to affected organizations when contracts do not include data requirements.

(3) 5.3.3. Conduct data calls and in-process reviews to ensure that correct and complete data requirements, including reprocurement data, appear in the Engineering, Manufacturing and Development (EMD) or production contract.

(4) 5.3.6. Schedule periodic engineering and procurement data reviews to be sure that the contractor is complying with the contractual data requirements in supporting the Spare Parts Breakout Program.

d. The Competition in Contracting Act (CICA) of 1984 requires the Government to address and plan for competition of future acquisitions and of spares during acquisition of the system. The law (10 USC 2304(f)(4)) states, “In no case may the head of an agency enter into a contract for property or services using procedures other than competitive procedures on the basis of the lack of advance planning or concerns related to the amount of funds available to the agency for procurement functions.” This does not mean we must buy reprocurement engineering data (Product Drawings/Models and Associated Lists);

however, we must address, support, and document any decision not to buy this engineering data.

e. For these reasons, do not make any changes to the DD Form 1423-1 originated by AFLCMC/LZPEM without coordinating with Gary Jenson.

5. Data requirements are set forth on DD FORM 1423-1 attached hereto.

6. Please reference LZPEM’s control number 2014-39 on all correspondence relating to this subject. Point of contact is Gary Jenson 478-222-3065.

MICHAEL E. WILLS, Chief Engineering Data Management, Acquisition and Inspection

AFLCMC/LZPEM

Attachment:

DD FORM 1423-1, Product Drawings/Models and Associated Lists, 3/31/2014 cc: AFMC-WLNEB /Christopher Beasman AFLCMC/WLKCA/Cheryl Janssen

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item) Form Approved QMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188), Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting Officer for the Contract/PR No. listed in Block E.

HC-130H Retardant Delivery System

FD2060-14-31382

A001

PRODUCT DRAWINGS/MODELS AND ASSOCIATED LISTS

DI-SESS-81000E/T

(SOW) 6.1, 9.0 ,9.9 ,12.4 & 18.10

AFLCMC/LZPEM

DD

QRTLY

SEE BLK 16

b. COPIES

FINAL

A

SEE BLOCK 16

SEE BLK 16

285 Cochran Street

2. METADATA SHALL BE IN ACCORDANCE WITH 9579776 PARAGRAPH 10 OPTION

ONE

3. Please reference EDATS control number 2014-39 on all correspondence related to this effort.

DD Form 1423-1, Feb 2001 STRAWMAN Revision 24 December 2013 PAGE___1_ OF __8___ PAGES EDATS 2014-39

CONTINUATION OF DD FORM 1423-1 (DI-SESS-81000E/T) Dtd 01/27/2017, EDATS 2014-39

BLOCK 4: DI-SESS-81000E is tailored as follows:

Requirements: (the below paragraph numbering corresponds with the numbering in the DID)

1. Reference Documents. Delete paragraph 1. in its entirety and replace with “1. Reference Documents. The documents apply as cited in the DD Form 1423-1 and continuation sheets. Unless otherwise noted, the latest revision of the ASME Standard at the time of solicitation shall apply.”

3. Format. Delete in its entirety and replace with “3. Format. Product Drawings/Models and Associated Lists shall be in the format as specified on this DD Form 1423-1 and continuation sheets, and shall meet the requirements of ASME Y14.1."

4. Content. Delete in its entirety and replace with “4. Content. Product Drawings/Models and Associated Lists shall conform to the requirements of ASME Y14.100-2013, Appendix B, sections B6 through B9.1 and Appendices C,D, E, and F (F-3.5, F-3.6, F-3.7) in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35M and ASME Y14.41. They shall document directly or by reference the following (items a through q), as applicable:”

6. CAGE code. Delete “TDP Option Selection Work Sheet incorporated in the contract or purchase order.” and replace with “DD Form 1423-1 and continuation sheets.”

7. Selection of drawings. Delete “The TDP Option Selection Work Sheet incorporated in the contract or purchase order will specify whether the contractor or the Government is responsible for selecting the types of drawings and associated lists.” and replace with “The contractor shall comply with ASME Y14.24, Types and Applications of Engineering Drawings”.

BLOCK 7:

“D”—Inspection is at destination and is to ensure this product meets this CDRL and its tasking document. Shipping list must accurately reflect the shipped product.

“D”—Acceptance is at destination. Acceptance of final data will be by approval of the Engineering Data Management Specialists.

BLOCK 9:

DISTRIBUTION STATEMENT. Distribution statements shall be in accordance with DoD Instruction 5230.24 and included on the first sheet of each drawing near the title block, and shall be as follows:

“DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government Agencies and their contractors critical technology, 27 Jan. 2017. Other requests for this document shall be referred to AFMC/WLNCC.”

EXPORT CONTROL WARNING LABEL. All engineering data shall be marked with Export Control Warning Labels in accordance with DoD Instruction 5230.24, dated August 23, 2012 as follows:

“WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.”

DESTRUCTION NOTICE. Mark documents with one of the following:

a. For unclassified limited documents: “DESTRUCTION NOTICE. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

b. For classified documents: “DESTRUCTION NOTICE. Follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual, Chapter 5, Section 7, or DoD 5200.1R, Information Security Program, Chapter 6.”

BLOCK 10: Revisions/changes to the final delivered data shall be furnished quarterly, commencing the first quarter after destination acceptance of the final reproducible data and continue until the contract is closed. Quarterly updates shall include an updated BOM, reference A.F. Drawing 9579776. Negative reports shall be submitted to AFLCMC/LZPEM.

BLOCK 11: 15 days before end of quarter.

BLOCKS 12 AND 13:

1. All data submittals shall contain a delivery letter and a shipping list. The letter shall contain at a minimum the contract number, delivery order, CLIN, and EDATS number (located on the bottom right corner of the DD Form 1423). The shipping list shall include as a minimum, the document number, revision level, and number of sheets/pages. The data delivered shall be in the same sequence as the shipping list. Shipments of data must be for a complete Technical Data Package (TDP) that accurately depicts the final product as defined in the tasking document (SOW, PWS, etc.). Shipping list shall specify whether the shipment is updates, final or make-up.

2. When a specific revision of an engineering document has been previously furnished and approved by a USAF Engineering Data Repository in digital form as a result of a government contract, and is required by this DD Form 1423-1, the same revision data shall not be resubmitted providing it meets the requirements in the DD Form 1423-1 for existing data, unless the data is currently available in a single text searchable document. Previously delivered data shall be identified as having been submitted and approved and shall include the document number, revision, and contract number under which the data were submitted. The receiving USAF Engineering Data Repository shall be identified. This action is required concurrent with all submittals.

3. Within 90 days after successful government verification of the install, a Bill of Materials (BOM) in accordance with Air Force drawing 9579776 (CAGE 98752) shall be delivered.

4. Within 90 days after successful government verification of the install, one set of paper copies of all "final reproducible data" (reference Block 14 of the DD 1423-1) shall be delivered. A letter of transmittal shall accompany submittal. Paper copy submittal will be reviewed within 120 days after receipt of data, unless additional time is required, at which time the contractor will be notified. When the submittal does not meet the contractual requirements a discrepancy letter will be submitted through Government Contracting Officer with a suspense date for the contractor to resubmit the TDP with corrections incorporated.

a. Submittal of programming files, in accordance with Air Force drawing 9579776 (CAGE 98752), Software and memory Device Data is not required for this (paper) submission.

b. Concurrent with the paper copies the contractor shall submit representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), (Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/Memory Device Data, etc.).

5. Within 60 days after approval of paper copy, one set of all “final reproducible digital data” to include Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/Memory Device Data, etc. (reference Block 14 of the DD 1423-1) shall be delivered to AFLCMC/LZPEM, 450 Third Street, Bldg. 323, Robins AFB GA 31098-1813. If changes have been required to the BOM since delivery in paragraph 3 above, resubmittal shall be required. The final digital submittal will be reviewed within 60 days after receipt of data, unless additional time is required, at which time the contractor will be notified. In the event the submittal does not meet the contractual requirements, a discrepancy letter will be submitted through the Government Contracting Officer with a suspense date for the contractor to resubmit the final digital TDP with corrections incorporated.

BLOCK 16:

1. Contractor Activity and Part Identification: The contractor shall use its own design activity identifier (CAGE) and shall assign its own design activity drawing numbers. This number shall be or shall include the drawing number on which the item is described. Where more than one item is described on a drawing, unique identification shall be provided by the addition of a suffixed dash number with the following limitations:

a. The total length of the part number including dash numbers and spaces shall not exceed 32 characters.

b. The dash number shall have the same characteristics as drawing numbers and may be composed of numbers, letters, or any combination thereof.

c. Part numbers shall not include the drawing revision letter, the contractor CAGE, or the drawing format size letter.

2. Content, format, and media requirements for delivery of Digital Engineering Data: The contractor shall comply with Air Force drawing 9579776 (CAGE 98752).

3. Product Drawings/Models and Associated Lists: Product drawings/models and associated lists shall be prepared to provide the design, engineering, and manufacturing information necessary to enable the procurement or manufacture of an item essentially identical to the original item. The product shall be defined to the extent necessary for a competent manufacturer to produce an item, which duplicates the physical, interface, and functional characteristics of the original product, without additional design engineering effort or recourse to the current design activity. Product data shall reflect the approved, tested and accepted configuration of the defined delivered item. This includes but is not limited to special tooling, interface hardware, special test equipment, and support equipment.

4. Engineering Drawing Practices: The contractor shall use the practices described in ASME Y14.100-2013. For clarification, the documents listed in section 2 of ASME Y14.100-2013 shall be considered first tier and shall apply. The contractor may find it useful to incorporate the concepts of MIL-HDBK-288 into the preparation of the TDP. MIL-HDBK-288 refers to Engineering Drawing Package (EDP); this term shall be considered synonymous with TDP. In instances where the ASME standards do not fully define requirements concerning preparation of engineering drawings, the contractor may use the guidance provided in the Drawing Requirements Manual (DRM) 11th Edition available from IHS, Inc. copyright 2008.

5. Commercial Off-the-Shelf (COTS): Definition for a COTS item can be found in the Federal Acquisition Regulation (FAR SUBPART 2.1-Definitions) Part 2.101 and (FAR) Part 12. The technical data requirement for commercial items is at DFARS 252.227-7015. For clarification of this effort, any modification/tailoring of the COTS item shall require a modifying drawing be prepared and delivered to the Air Force documenting the comparison of the COTS item and the item after modification.

6. Control Drawings: Control drawings shall be created in accordance with DI-SESS-81000E and ASME Y14.24-2012 to depict engineering criteria used in selecting purchased or vendor developed items. Control drawings shall disclose engineering form, fit, function and performance requirements for the acquisition of interchangeable purchased items of existing designs, or of items specially developed by vendors to the control drawing requirements. When COTS/purchased items are used by the contractor and are part of this effort as defined in the tasking document (SOW, PWS, etc.), control drawings shall be developed and delivered. Control drawings not developed for this contract that are part of the deliverable TDP shall be updated, to show current information (i.e., performance/qualification requirements, vendors/sources names and part numbers.)

6.1. Control drawings are not required for items which are Government directed purchases or for Government Furnished Material/Government Furnished Equipment (GFM/GFE). Such items shall be identified using the GFE/GFM notation on the parts list, etc. The use of a flag note is acceptable.

7. Contract Numbers: When a TDP document is prepared under a Government contract, the Government contract number under which it is prepared shall appear on the first sheet of the document original. When a TDP document is delivered under a Government contract other than the one under which it was prepared, the Government contract number under which it is delivered shall also appear on the first sheet of each copy submitted. If the document is prepared and submitted under the same contract, only the entry for the contract under which it is prepared is required.

8. Application Data: All new and revised drawings shall contain Application Data. The Application Data is mandatory for all drawings. The Application Data shall show the “Next Assembly” and “Used On”. The application data shall be located near the title block on sheet 1, placed on a separate referenced document, or provided on a separate parts list. When the application data appears on a separate referenced document, a cross reference note shall be included on each parent drawing to indicate that a separate referenced document is available. When an item is used in more than three applications, the entry “general usage” may be entered in the “Used On” column.

9. Reference Documents: Documents referenced in a TDP shall be furnished as part of the TDP with the exception of those specified in referenced documents available in Acquisition Streamlining and Standardization Information System (ASSIST) and non-Government standardization documents available from the issuing non-Government standards body, such as the American Society of Mechanical Engineers (ASME). The following types of documents shall not be referenced in a TDP: technical manuals, procedural manuals, maintenance manuals, company drafting manuals, management plans, uncontrolled documents or unreleased documents. However, when information essential to meeting the content of a TDP (such as default surface texture values) is contained within such prohibited documents, that information shall be extracted from the reference document and included in the TDP.

9.1 Prohibited Documents, References, and Phrases: Technical Orders (TOs), Time Compliance Technical Orders (TCTO), pamphlets, recordings, National Stock Numbers (NSNs), To Be Determined (TBD), Statement of Work ((TASKING DOCUMENT)), Performance Work Statement (PWS), Statement of Objectives (SOO), and Contract Data Requirements List (CDRL), shall not be referenced within the TDP.

10. Traceability: The contractor shall prepare the TDP in such a manner to insure that all applicable documents and part or identifying numbers (PINS) i.e., Artwork, Schematics, Software/Programming Data, Test Criteria, etc., are referenced within the TDP for traceability.

10.1 If the contractor is the original equipment manufacturer (OEM), impacted engineering data that are part of the effort as defined in the tasking document (SOW, PWS, etc.) shall be revised to include changes to reflect the delivered item’s configuration.

10.2 If the contractor is not the OEM, the contractor shall ensure impacted engineering data that are part of the effort as defined in the tasking document (SOW, PWS, etc.) are updated and delivered to reflect the delivered items configuration.

11. Preparation Method: American English language shall be used in the preparation of this TDP. Dimensioning and Tolerancing shall be Decimal Inch in accordance with ASME Y14.5-2009. Size and format of drawings shall be Decimal Inch per ASME Y14.1. All drawings shall be prepared using Third Angle Orthographic Projection method of presentation. The symbol for angle of projection shall be delineated in the Title Block of newly prepared or revised engineering data. (ASME Y14.3-2003 figure 2)

12. TDP Validation: The contractor shall validate that the TDP conforms to the contractual requirements, and that they accurately depict the item(s) developed, modified, or produced under the contract.

13. Clarification of Detailed Test Criteria for Electrical and Avionics Items: Test criteria for items designed or developed with Government funds is an inherent part of the TDP. Test criteria shall be incorporated, either directly on each TDP document or by reference, for each end item, top assembly item, configured item, and lowest assembled item IAW Air Force drawing 9579777 (CAGE 98752), titled “Clarification of Detailed Test Criteria for Electrical and Avionics Items.”

14. Associated Lists: Parts Lists per ASME Y14.34 are required. Parts Lists are required at assembly level. Parts Lists for Contractor Activity identifier CAGE code may be an integral part of a document or it may be a separate document. The identification and quantity of parts shown on the assembly drawing shall agree with the parts list.

15. Marking: Drawings shall specify requirement for marking part number identification on items as required by MIL-STD-130 and other applicable documents referenced therein. Item unique identification (IUID) marking is mandatory for applicable items as determined by the Program Office. (See DFARS 252.211-7003 Item Identification and Valuation) The drawings shall identify the content, method of application, material and location of marking on the part.

16. Printed Board Artwork Master Drawing. The printed board artwork master drawing shall include images of all artwork required to manufacture the printed board. These images will serve as a reference to those images produced from the Gerber data files IAW Air Force drawing 9579776 (CAGE 98752) titled “Product Data Specification”. Also, this drawing shall reference a unique part or identifying number (PIN) with revision data for the digital file set which includes the Gerber, test, and drill data files. The PIN number format structure and characters shall meet the same requirements as for the part number. These requirements are in addition to those in ASME Y14.24 and other related standards.

17. Printed Board Artwork Master, Test, and Drill NC Data. The printed board artwork master, test, and NC drill data shall be delivered IAW Air Force drawing 9579776 (Cage 98752). These requirements are in addition to those in ASME Y14.24 and other related standards.

18. Legacy Stable Base Media (Mylars, undimensioned drawings, master patterns, etc.). Data originally produced on stable base drawing media that has been redrawn/converted/reproduced in a digital format or developed on a CAD platform shall be delivered.

19. Existing data: Use existing data when possible, provided it meets the following requirements:

20. Legibility and Reproducibility: All documents 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.

21. Protecting Classified Information: TDPs or parts thereof, containing classified information shall be protected and marked in accordance with the Department of Defense National Industrial Security Program Operating Manual for Safeguarding Classified Information, DoD Manual 5220.22-M. When 3D TDP data is used, the solid models shall display classification marking clearly visible when the solid model is first opened.

22. Software and Memory Device Data: Software and Memory Device drawings shall be selected per ASME Y14.24 and CAD/CAM data files shall be delivered per Air Force drawing 9579776 (CAGE 98752).

23. Inspection of TDP: The TDP shall be inspected for the following:

a. Compliance with the requirements of this contract.

b. Inclusion of all documents, including sub-tier references, required to meet the design disclosure requirements of the TDP.

c. 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.

d. Inclusion of contract numbers and contractor identifications.

e. Legibility and reproducibility.

f. TDP components have not been prepared for requirements, which could be met by existing standardization documents.

g. Completeness and accuracy of the TDP documents, including required quality assurance information, in describing 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 Government has approved, tested, or accepted.

h. Both Type 2D and Type 3D TDPs shall open in the appropriate software without regeneration errors or warnings.

24. Source Control Drawing (SOCD) Approval Request. Source control drawing approval requests (as referenced in MIL-STD-31000A and corresponding Appendix A) shall be prepared and submitted to the requiring office in Block 6 of this DD Form 1423-1 prior to the preparation or use of a source control drawing. Each potential source control item shall be approved by the Air Force System Engineer prior to inclusion of the source control drawing in the TDP. SOCD approval requests are used to ensure that only valid source qualification requirements are included in the TDP. Under Public Law, the Government will actively seek multiple sources for any item for which source qualification is a requirement. Air Force engineering will evaluate each request and notice will be promptly given regarding approval/disapproval. Requests shall be by letter and shall be prepared and submitted as follows:

a. Format - The Source Control Drawing Approval Request shall be in the contractor’s format.

b. Content - The request shall specify the following:

(1) Nomenclature and description of the item.

(2) The critical application(s) for which the item is to be used.

(3) Number of applications per end item.

(4) System performance requirements requiring source qualification.

(5) Procedures and criteria required to qualify a source.

(6) Sources of supply and manufacturers’ part numbers.

(7) Cost of the item involved.

(8) Estimated cost to qualify a source.

image1.png image2.emf