Exhibit G CDRL A007 Product Engineering Design Data and Associated Lists.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved QMB No. 0704-0188

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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. 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.

A CONTRACT LINE ITEM NO. C. CATEGORY:B. EXHIBIT

G TDP __X___ TM _____ OTHER _____

D SYSTEM / ITEM E. CONTRACT / PR NO. F. CONTRACTOR

AN/MPN-14K, A-Box

1 DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

A007 Product Engineering Design Data and Associated List

AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

DI-SESS-81000F/T SOW Para 10 AFLCMC/HBAA

DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT ASREQ SEE BLK 16 b. COPIES

APP CODE See BLK 16 11. AS OF DATE 13. DATE OF

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A See BLK 16 ASREQ Draft Reg Repro

16. REMARKS See Block 16 The Contractor shall invoke these same requirements with its subcontractors or vendors at any tier requiring the delivery of technical data, except contractual instruments for commercial items or commercial components. This shall include pre-notification of rights in data and shall ensure that subcontractors and vendors are required to provide the same depth of data that the prime is obligated to provide to the Government. Subcontractor or vendor data may be provided directly to the Government if rights limitations preclude their being provided by way of the prime contractor.

The Metadata File (Index.rst file) shall be in accordance with the Product Data Specification, 9579776 paragraph 10 option 3. Failure of the Index.rst file too successfully export data to the Joint Engineering Data Management Information Computer System (JEDMICS) data fields correctly shall be cause for rejection.

Native CAD data and Neutral CAD data along with Viewable/Raster data in PDF format shall be delivered, in accordance with the Product Data Specification, 9579776.

The files shall not be Write Protected or Password Protected. The image density/resolution for PDF files shall be 200 dots per inch (dpi).

Undimensioned drawings provided by the contractor shall be dimensionally accurate Digital images shall be in accordance with ASME Y14.31. The dimensionally accurate Digital images shall be in Tagged Image File Format (TIFF), Compression shall be CCITT Group 4 and the image density/resolution shall be 200 dots per inch (dpi). The files shall not be Write Protected or Password Protected. The image shall also be delivered in raster PDF format. The dimensionally accurate Digital images shall have the following statement placed on each Digital image as recommended in ASME Y14.31.

“FOR MANUFACTURING AND INSPECTION PURPOSES, THIS DRAWING SHALL

BE REPRODUCED ON STABLE BASE MATERIAL”

For requirement details, see the Continuation Sheets of DD FORM 1423-1 for BLOCK 16.

AFLCMC/LZPEM

3001 Staff Dr., Ste 1AB82A Tinker AFB, OK 73145-3041

15. TOTAL 1

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

13 Jun 22 13 Jun 22ALEXANDER.EMB

ER.LAUREN.12557

65830

Digitally signed by

ALEXANDER.EMBER.LAUREN.

1255765830 Date: 2022.06.13 15:10:48 -05'00'

WILLIAMS.SAMU

EL.M.1114583274

Digitally signed by

WILLIAMS.SAMUEL.M.1114583274

Date: 2022.06.13 15:36:57 -05'00'

CONTINUATION SHEETS OF DD FORM 1423-1 FOR BLOCK 16

1. Blk 4: (Enter the DID number)

a. See the Technical Data Package (TDP) Option Selection Worksheet and the continuation sheets for specific tailoring requirements.

2. Blk 7: (Specify requirement for inspection/acceptance of the data item for the government.)

a. "SD" for the final delivery of TDP on compact disk (CD).

b. "LT" for the TDP document packages selected for completeness, evaluation by the government.

3. Blk 9: (For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data. (ref. DoDI 5230.24).)

a. Distribution Statements shall be as specified by the Controlling DoD Office (CDO) in accordance with DoDI 5230.24. The Distribution Statement shall be applied to the first page of each engineering drawing and associated lists, near the title block. At the discretion of the Controlling DoD office, for purposes of clarification, distribution statements B, C, D, and E may begin with the word “Secondary” and the following text may precede the statements: “The [Controlling DoD Office] authorizes secondary distribution, release, and dissemination to the extent permitted by this distribution statement without additional approvals or authorizations.”

1. For Unlimited Rights (critical technology/administration or operational use) use:

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (fill in reason) (date of determination). Other requests shall be referred to (insert CDO).

2. Limited Rights (Proprietary) use:

DISTRIBUTION STATEMENT B. Distribution authorized to U.S. Government agencies only (fill in reason) (date of determination). Other requests for this document shall be referred to (insert

CDO).

b. The following export control notice, in accordance with DODI 5230.24, shall be marked on the engineering drawings and associated lists as an added paragraph below the distribution statement:

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

c. For Unclassified documents the following destruction notice, in accordance with DODI

5230.24, shall be marked on the engineering drawings and associated lists as an added paragraph below the distribution statement:

“DESTRUCTION NOTICE. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

4. Blk 10: (Specify number of times data items are to be delivered.)

a. TDP submittals shall be in digital format; paper copies are no longer accepted.

b. TDP submittals must contain a digital delivery letter and a digital shipping list in Portable Document Format (PDF). The letter shall contain at a minimum the Contractor Name, contract number, delivery order. The shipping list shall include as a minimum, the Document Type, Drawing Number, Revision, Cage, Sheet Number and Weapon System.

c. TDP submittals shall be in digital format for each IPR, Audit and/or Review in lieu of paper copies.

d. Re-submission is required for improperly formatted, illegible data and/or missing data as determined by AFLCMC/LZPEM. Deficiencies identified above shall be corrected per the contractual requirements.

5. Blk 11, 12, and 13: Block 11 - (Specify as/of date for data item, when applicable) (Block 12 –

Specify when first submittal is required; Block 13 – Specify when subsequent submittals are required, when applicable.)

a. The contractor shall submit Digital TDP documents for government review NOT LATER THAN

30 calendar days before each government review.

b. Deliver the Digital TDP documentation NOT LATER THAN 60 calendar days after Government approval for final delivery of the engineering data.

c. Deliver the Digital TDP updates/revisions 30 days prior to last hardware delivery.

d. Deliver sample Digital Data, NOT LATER THAN 30 calendar days after the engineering data guidance conference or 120 calendar days after contract award.

e. Resubmission of the Digital TDP documentation is required for deficient, improperly formatted, or illegible data NOT LATER THAN 30 calendar days after Government notification to the contractor of the deficient delivery.

6. Blk 14: (Enter addressees and number of draft/final copies to be delivered to each addressee):

a. Classified Data shall be delivered to the government acquiring activity and not to the AFLCMC/LZPEM (JEDMICS) Office at Tinker AFB.

CONTINUATION SHEETS OF THE TDP OPTION SELECTION WORKSHEET FOR BLOCK 11

A. Additional Material Requirements and Instructions:

1. The Digital Technical Data Package (TDP) deliveries and data to support reviews and audits shall be provided on CD/DVD. Alternate proposals that would satisfy this requirement i.e. Electronic Download or encrypted email, may be submitted for consideration and approval to AFLCMC/LZPEM. Training and assistance shall be provided to government personnel accessing digital TDP documents.

2. The TDP documents delivered to JEDMICS, as final delivery, shall have all outstanding changes incorporated into the data and the contractor shall sequence complete drawings as well as their accompanying documents and associated lists together in the same delivery.

3. Each TDP document delivered shall be identified with a two Digit Weapons System Code

‘__’. This code shall be entered, on the shipping list and the Meta Data file (Index.rst), accompanying each digital TDP delivery. If unknown Leave Blank.

4. Product Data Specification, Revision N, page 26, Column 7, change the “Document

Revision Date” from Required Field “NO” to Required Field “YES”.

5. Use of drawing types not specified in ASME Y14.100 and ASME Y14.24 requires approval by the government acquiring activity.

6. Classified Data shall be delivered in accordance with the Product Data Specification, 9579776.

7. TDP elements for materiel subject to MIL-STD-130 marking shall specify the marking method, location, and content in accordance with the specific item marking requirements based on criteria provided in the current edition of MIL-STD-130.

8. For compression software, the compression ZIP format shall be the encapsulation method.

If this method is not used, i.e. TAR files, the government acquiring activity must approve the alternate method, before data delivery.

9. TDP documents covered by this CDRL must be, or have been, delivered to the Air Force engineering data repository known as JEDMICS. TDP documents delivered to any other destination does not satisfy the requirement for delivery to JEDMICS under this CDRL.

10. Duplicate data shall not be submitted when a current issue of a TDP document, meeting the requirements herein, has been previously submitted as the result of a government contract to JEDMICS.

11. Application Data is not required for source control drawings, specification control drawings, vendor item control drawings and company standards.

12. When a document of current issue indicates limited rights and the previous issue indicated unlimited rights, both issues shall be submitted.

13. Newly created Engineering drawings shall not be segmented. Legacy data that is already segmented, the drawing sheets shall have the image that contains the title block appear first with successive images appearing in order in a single PDF file, until the opposite end of the drawing sheet is represented. Segmented sheets shall be prepared with all frames the same size. There shall be a 4” minimum overlap.

14. Size and format of drawings shall be Decimal Inch in accordance with ASME Y14.1.

15. Dimensioning and Tolerancing shall be Decimal Inch in accordance with ASME Y14.5.

16. Metric dimensioning is applicable, only when interfacing with existing items that were dimensioned in metric.

17. Use of lettering less than .12 inches recommended in ASME Y14.2 requires approval by the government acquiring activity.

18. Printed wiring assembly drawings shall contain a note that specifies the item shall be manufactured in accordance with MIL-PRF-31032.

19. The TDP documents shall be marked with a Department of Defense (DOD) Distribution Statement, Contract Number(s) and other Markings/Rights Legends that are applicable to the document. These Markings shall not obliterate nor obscure any information on the field of the drawing and shall be placed inside the border near the title block if possible.

20. The Government contract number under which a TDP is prepared shall appear on the first sheet of the document. When a TDP document is delivered under a different Government contract that Government contract number shall also appear.

21. Drawings, which contain statements for items such as “Government Furnished Property” or “Government Furnished Equipment”, must also include the contract, which provided the property or equipment to the contractor.

22. Only the following Rights Legends are authorized under this contract.

1. Government Purpose Rights legend

2. Limited Rights Legend

3. Special License Rights legend

4. Notice of Copyright as prescribed by 17 USC 401 or 402

B. Meetings, IPR’s Audits and Reviews:

1. Meetings: The Contractor or the Government may request informal, unscheduled meetings, briefings, conferences or reviews. When determined to be within scope and existing funding, the Contractor shall attend and participate at any foregoing sessions where support may be required when authorized by the Program Office.

2. Post Award Guidance Conference: The purpose of this conference will be to review all contract documentation to assure precise understanding of all contract requirements and to review detailed plans on Contractor implementation. The conference maybe held in two phases, hosted by the contractor, a contract phase, held as part of the kickoff meeting and a technical phase. The Contractor shall submit an agenda and presentation material prior to each conference phase.

3. Review of Technical Data Package (TDP): The Contractor shall support In-Process Reviews

(IPR) of the technical data. The drawing IPRs may be scheduled in conjunction with other meetings/reviews/audits. Additional IPRs will be conducted at the discretion of the Government when data deficiencies are found extensive. The Contractor shall correct data deficiencies noted during IPRs as well as to ensure all technical data containing similar deficiencies are also corrected. Minutes shall be delivered to the government for review and approval from all IPRs.

4. Formal Audits: The contractor shall be responsible for conducting audits in accordance with the Statement of Work, except as amended by the contract. The contractor shall be responsible for insuring that sub-contractors, vendors and suppliers participate in formal audits specified in the Statement of Work (SOW) or the Statement of Objectives (SOO). A formal Functional Configuration Audit (FCA) will be held to validate that the development of a configuration item has been completed satisfactorily. All support documents shall be reviewed. A Physical Configuration Audit (PCA) will be held concurrently with the First Article Inspection (FAI) or FCA to verify that the designated configuration item “as built” conforms to the technical documentation, which defines the item.

C. Current Editions of Applicable Specifications, Standards, Regulations and Directives form a part of this CDRL:

Military Spec/Std Title MIL-STD-130N w/Change 1 Identification Marking of U.S. Military Property MIL-STD-883K w/Change 3 Test Method Standard Microcircuits MIL-STD-31000B Technical Data Packages MIL-PRF-31032C /Amendment Printed Circuit Board/Printed Wiring Board MIL-I-8500D & Notice 2 Interchangeability and Replaceability of Component Parts for Aerospace Vehicles MIL-PRF-5480H Data, Engineering and Technical Reproduction MIL-STD-1840C & Notice 1 Reference Automated Interchange of Technical Information MIL-PRF-28002C & Notice 1 Reference Raster Graphics Representation in Binary Format MIL-D-9898C & Notice 2 Reference Drawings, Tube Bend MIL-HDBK-288B Reference Review and Acceptance of Engineering Dwg Pkgs MIL-HDBK-2164A Reference Environmental Stress Screening MIL-HDBK-780D w/Change 2 Reference Standard Microcircuit Drawings

DoD Directives/Regulations Title DoDD 5000.01 The Defense Acquisition System DoDI 5000. 02 Operation of the Defense Acquisition System DoD 5010.12-M Procedures for the Acquisition of Technical Data DoDM 5200.01 Vol 1-4 Information Security Program DoD 5220.22-M National Industrial Security Program Operating

Manual (NISPOM) DoDI 5230.24 Distribution Statements on Technical Documents DoDD 5230.25 Withholding of Classified Data from Public Disclosure

ASME Stds Title

ASME Y14.1 Decimal inch Drawing Sheet Size and Format ASME Y14.2 Line Conventions and Lettering ASME Y14.3 Orthographic and Pictorial Views ASME Y14.5 Dimensioning and Tolerancing ASME Y14.8 Castings, Forgings, and Molded Parts ASME Y14.24 Types and Application of Engineering Drawings ASME Y14.31 Undimensioned Drawings ASME Y14.34 Associated Lists ASME Y14.35 Revisions of Engineering Dwgs and Assoc Lists ASME Y14.36 Surface Texture Symbols ASME Y14.38 Abbreviations and Acronyms for Use on Drawings ASME Y14.41 Digital Product Definition Data Practices ASME Y14.47 Model Organization Practices ASME Y14.100 Engineering Drawing Practices, Appendices B, C, D, E ASME B46.1 Surface Texture (Surface Roughness, Waviness, & Lay)

Specs/Stds Title IPC D-350D Reference Printed Board Description in Digital Form IPC-2221B Reference Generic Standard on Printed Board Design IPC D-325A Reference Documentation Requirements for Printed Boards, Assemblies and Support Drawings IPC 6011 Reference Generic Performance Specification for Printed Bds ISO 9660 & AMD 1 Information Processing - Volume and File Structure of

CD-ROM for Information Interchange First Edition ISO/IEC 10149 Information Technology - Data Interchange on Read-only 120mm Optical Disks (CD-ROM) – 2nd Edition ISO 10303 STandard for the Exchange of Product (STEP) Model

Data

D. Notes to Buyer:

1. The following listed documents have been developed and provided to the Program Office for the acquisition of Technical Data Packages (TDPs).

a. DD Form 1423-1 and the continuation sheets.

b. TDP Option Selection Worksheet.

c. Product Data Specification.

2. The following clauses should be considered for inclusion in the Contract in accordance Federal

Defense Regulations (FAR), Defense Federal Acquisition Regulation Supplements (DFARS).

FAR Paragraph Title 52.214-34 English Language Requirement

DFARS Paragraph Title

227.7102 Commercial items, components, or processes

227.7103 Noncommercial items or processes

252.225-7041 Correspondence in English 252.227-7000 Non Estoppel 252.227-7001 Release of Past Infringement

252.227-7013 Rights in Technical Data – Non-Commercial Items 252.227-7014

Rights in Non-commercial Computer Software and Non-Commercial Computer Software Documentation

252.227-7015 Technical Data – Commercial Items 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions 252.227-7018 Rights in Non-Commercial Technical Data and Computer Software –

Small Business Innovation Research (SBIR) Program 252.227-7019 Validation of Asserted Restrictions – Computer Software 252.227-7020 Rights in Special Works 252.227-7021 Rights in Data – Existing Works 252.227-7022 Government Rights (Unlimited) 252.227-7023 Drawings and Other Data to Become Property of the Government 252.227-7025 Limitations on the Use or Disclosure of Government

Furnished Information Marked With Restrictive Legends 252.227-7026 Deferred Delivery of Technical Data or Computer Software 252.227-7027 Deferred Ordering of Technical Data or Computer Software 252.227-7028 Technical Data or Computer Software Previously Delivered to the

Government 252.227-7030 Technical Data – Withholding of Payment 252.227-7032 Rights in Technical Data and Computer Software (Foreign) 252.227-7037 Validation of Restrictive Markings on Technical Data 252.246-7001 Warranty of Data

252-211-7003 Item Unique Identification and Valuation

MIL-STD-31000B

TDP OPTION SELECTION WORKSHEET

SYSTEM: DATE PREPARED:

A. CONTRACT NO. B. EXHIBIT/ATTACHMENT

NO.

C. CLIN D. CDRL DATA ITEM NO.

1. TDP LEVEL (CHOOSE ONLY ONE PER WORKSHEET). Note: The level selected must coincide with the requirements of the elements selected in block 5.

A. CONCEPTUAL LEVEL

DEVELOPMENTAL LEVEL

PRODUCT LEVEL

B. REMARKS:

2. TYPE AND FORMAT (X all that apply and complete as applicable.)

A. TYPE 2D: 2D DRAWINGS(describe in detail in remarks below or in block 11):

NATIVE 2D CAD (SPECIFY TYPE): ____________________________________________________________

ISO 32000 PDF

HARD COPY

OTHER FORMAT (SPECIFY TYPE): ____________________________________________________________

REMARKS :

B. TYPE 3D: 3D MODEL BASED (describe in detail in remarks below or in block 11):

NATIVE 3D CAD (SPECIFY TYPE): _____________________________________________________________ 3Di VIEWABLE* FORMAT DERIVED FROM 3D NATIVE MODELS (Specify type, i.e. ISO 32000 PDF etc.).

NEUTRAL FORMAT DERIVED FROM 3D NATIVE MODELS (Specify type, i.e. STEP AP203, AP 214 etc.).

2D DRAWINGS DERIVED FROM 3D NATIVE MODELS (Specify type, i.e. ISO 32000 PDF etc.).

OTHER FORMAT (SPECIFY TYPE): _____________________________________________________________

*NOTE: 3Di viewable will be in ISO 32000 pdf format unless otherwise specified.

REMARKS :

3. CAGE CODE AND

DOCUMENT NUMBERS

A. CONTRACTOR CAGE & DOCUMENT NUMBERS

GOVERNMENT CAGE & DOCUMENT NO. (COMPLETE 3B, 3C, AND 3D)

B. USE CAGE CODE: C. USE DOCUMENT NUMBERS: D. TO BE ASSIGNED BY:

4. DRAWING FORMATS AND/OR 3Di PDF FORMAT (X one and complete as applicable)

CONTRACTOR FORMAT GOVERNMENT FORMAT

REMARKS:

5. TDP ELEMENTS REQUIRED (X all that apply )

ELEMENTS REQUIRED TO BE DETERMINED BY CONTRACTOR

OR THE FOLLOWING ARE REQUIRED:

CONCEPTUAL ENGINEERING DESIGN DATA

DEVELOPMENTAL ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

PRODUCT ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

COMMERCIAL ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

SPECIAL INSPECTION EQUIPMENT (SIE) ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

SPECIAL TOOLING ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

SPECIFICATIONS

SOFTWARE DOCUMENTATION

SPECIAL PACKAGING INSTRUCTIONS (SPI) ENGINEERING DESIGN DATA AND ASSOCIATED LISTS QUALITY ASSURANCE PROVISIONS (QAPs)

6. APPLICABILITY OF STANDARDS. The following Standards apply: (X as applicable)

ASME Y14.100

ENGINEERING DRAWING

PRACTICES

WITH APPENDICES:

B C D E

Company stds permitted? Y/N

ASME Y14.24 TYPES AND APPLICATIONS OF

ENGINEERING DRAWINGS

ASME Y14.34 ASSOCIATED LISTS

ASME Y14.35 REVISION OF ENGINEERING

DRAWINGS AND ASSOCIATED DOCUMENTS

ASME Y14.41 DIGITAL PRODUCT DEFINITION

DATA PRACTICES

ASME Y14.5 DIMENSIONING AND TOLERANCING

OTHER STANDARDS APPLY AS

DESCRIBED:

MIL-STD-31000B

TDP OPTION SELECTION WORKSHEET

A. CONTRACT NO. B. EXHIBIT/ATTACHMENT

NO.

C. CLIN D. CDRL DATA ITEM NO.

7. ASSOCIATED LISTS (X all that apply and complete as applicable.)

A. PARTS LISTS (X ONE)* (1) INTEGRAL (2) SEPARATE (3) CONTRACTOR SELECT

B. DATA LISTS REQUIRED (Specify Levels of ASSY) __________________________________

C. INDEX LISTS REQUIRED (Specify Levels of ASSY) __________________________________

D. WIRING LISTS (1) INTEGRAL (2) SEPARATE (3) CONTRACTOR SELECT

E. APPLICATION LISTS (1) INTEGRAL (2) SEPARATE

(3) PLM

MAINTAINED

(4) CONTRACTOR SELECT

F. OTHER REQUIRED(Specify Levels of ASSY) __________________________________

*NOTE: USE OF SEPARATE PARTS OR WIRING LISTS ARE NOT RECOMMENDED ESPECIALLY WITH TYPE 3D TDPS.

8. TDP DATA MANAGEMENT PRODUCTS

A. TECHNICAL DATA PACKAGE LIST (TDPL)

SOURCE CONTROL APPROVAL REQUEST

DOCUMENT NUMBER ASSIGNMENT REPORT

PROPOSED CRITICAL MANUFACTURING PROCESS DESCRIPTION

ENGINEERING DRAWING TREE

TO LOWEST REPAIRABLE UNIT (LRU) LEVEL

TO LOWEST COMPONENT LEVEL

OTHER (DESCRIBE):_______________________________________

B. REMARKS:

9. TDP METADATA

TDP METADATA REQUIRED (describe requirements):

10. TDP SUPPLEMENTARY DATA

TDP SUPPLEMENTARY DATA REQUIRED (describe requirements):

11. OTHER TAILORING (Attach additional sheets as necessary

12. PROCURING ACTIVITY TITLE, SIGNATURE AND DATE

TITLE: SIGNATURE: DATE:

11.0.1.20130826.2.901444

TextField1: A007

TextField1: Example: “CATIA version 5.0” or AutoCAD

TextField1: Example: Drawing eXchange Format (DXF) (preferred)

TextField1: NEUTRAL FORMAT USE STEP ISO 10303 AP203, AP214 or AP238 OTHER FORMAT USE Drawing eXchange Format (DXF)

TextField1: See Block 11

TextField1: AN/MPN-14K

TextField1: 13 Jun 22

TextField1: INDENTURED DATA LISTS

TextField1: See attachment 2, Product Data Specification,9579776, paragraph 10 Option 3.

TextField1:

For requirement details, see the Continuation Sheets of the TDP Option Selection Worksheet for BLOCK 11.

CheckBox1: 0

CheckBox1: 0

DateTimeField1:

SignatureField1:

ATTACHMENT 2

CONTINUATION OF THE TDP OPTION SELECTION WORKSHEET

BLOCK 11

PRODUCT DATA SPECIFICATION

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

DIMENSIONS ARE IN INCHES

TOLERANCES ON

FRACTIONS DECIMALS ANGLES

SIGNATURES ARE ON FILE

ON AF FORM 2602 IN LGEC

APPROVALS DATE

U.S. AIR FORCE

ROBINS AFB, GA

± .XX ± ± DRAFTSMAN

Robert Yohe 95/12/08

TITLE

.XXX ± CHECKER

Edwin Bray 95/12/08

MATERIAL ENGINEER

Edwin J. Reid 95/12/11 Product Data Specification

PROJECT ENGINEER

TREATMENT

None

PROJECT AUTHORITY

Donald Looney 95/12/11

SIZE

A

A.F. CODE IDENT NO.

98752

DRAWING NO.

9579776

FINISH

RELEASE AUTHORITY

David Olson 95/12/11

SCALE

REV

N

SHEET

ENGINEERING DRAWING LAYOUT A VERTICAL

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

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”

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.

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.

j. Delivery of Physical Media Requirements: Digital data shall be delivered either on Compact Disk CD-R or DVD+/-R in accordance with ISO 9660 and ISO 10149 or Joliet format, which defines the directory naming, file naming, and data structure requirements. Filenames are allowed to be up to 30 characters including extensions and are not restricted to the eight characters with a three-character extension per ISO-9660. Use of read/write CD-RW and DVD+/-RW media shall not be used due to potential software read compatibility and data integrity problems. In order to take advantage of the latest in digital media technology, other media not listed may be approved by the acquiring office identified in block 6 of the DD Form 1423 which calls out this requirement. Other physical may be used by mutual written agreement between the contractor, contracting officer, and the Engineering Data Management Specialist (EDMS).

k. Recording Mode: CD and DVD deliverable media shall be recorded using mode one and closed session settings and preferably at 16X CD speed to insure readability by most CD and DVD drives.

l. Media Markings: All physical disk media shall be marked with the following information below. The markings shall be accomplished using indelible ink. Other transfer media shall be marked in accordance with agreements made by the contractor, contracting officer, and the EDMS.

(1) Prime Contractor Name/CAGE

(2) Contract number

(3) System / Engineering Data Acquisition Tracking System (EDATS) Number (as applicable)

(4) The physical media shall be numbered sequentially (e.g., "Disk 1 of 3"), regardless of the type of media.

(5) Range of document numbers included on the disk labels, if more than one disk is used. The document numbers information may include ranges of document numbers containing gaps in numbering, where space is needed on the media.

(6) The appropriate Distribution Statement Code letter and Export Control Notice shall be listed in accordance with the DD Form 1423, which calls out this requirement.

(7) A classified data marking shall be on the media, if applicable.

(8) The security classification, distribution statements, data rights statements and codes shall reflect the highest restriction of any of the data contained on the delivery media.

m. Summary Report File: The contractor shall supply a Summary Report file in digital ASCII text or in Adobe

Portable Document Format (PDF) that provides general information concerning the data delivered. This file shall include:

(1) The name, version, and applicable raster data format or raster compression type of the file or software utilized in the creation of the native, neutral, legacy, and document files included in the delivery, such as type of software with the extension, e.g. .doc for MS Word.

(2) The type and quantity of files included in the delivery. For example, information similar to the following might be used (this example is for the delivery of AutoCAD formatted files):

Type Quantity Total Number of Files Delivered: 1200 Number of Native DWG Files: 400 Number of DXF Files: 400 Number of PDF Files: 400

(The DXF files delivered are representative neutral files of the native drawing files. The PDF files are representative view-only files of the native drawing files.)

(3) The name, phone number, and e-mail address of the contractor's sender activity and sender or technical data point of contact (a person familiar with processes used to create and archive data).

(4) The operating system and version, and the command (e.g., UNIX tar) and command switches used to archive the delivered data.

(5) Explanation of exceptions, as necessary, to headings or field data used in the metadata spreadsheet.

(6) Any other information pertinent to the data delivery and the usage of the software packages, including the document, drawing, design, and associated files shall be stated. This includes special instructions for the proper setup of the CAD software package to import the native files.

(7) Identify approved deviations from the applicable CAD/CAM Product Definition Data file formats (See paragraph 7).

(8) Identify special restrictions (beyond the control of the data rights or distribution limitations) on use or distribution of the CAD files (e.g. Intellectual Properties (IP) database or license files).

(9) specify the Data Exchange Specification (DEX) if AP239 data is delivered.

6. Legacy Data:

a. Raster drawings and any type of document developed in a non-electronic format or no longer available in a digital format (e.g., manual drafting board or scanned formats) and have not been previously delivered to the government, shall be considered as “legacy data.” Raster data that is already in a government repository and raster data that is cited by reference in new data is also considered legacy data. This data shall be delivered in digital form in the following standardized formats: PDF format (Adobe Reader compatible), JEDMICS C4 specification, Continuous Acquisition and Lifecycle Support (CALS) TYPE 1, CCITT Group 4 or Tagged Image File Format (TIFF). Compression shall be CCITT Group 4 and non-wrap format. The image density or resolution for raster images shall be 200 dots per inch (dpi), including raster PDF documents. For stable base drawing media requirements, see paragraph

b. Un-dimensioned Mylar drawings shall be prepared, precisely processed, and scanned with the appropriate process to maintain the dimensional accuracy required by the drawings.

After scanning, tests shall be done by overlaying prints of the scanned image over the original Mylar checking for exact overlay and matches of grid lines, curves, other drawing details, and possible distortion and deviation. As an acceptance criterion, an exact overlay and match to the original without distortion and deviation is required.

7. CAD/CAM Product Definition Data: CAD/CAM Product Definition Data is grouped in four basic categories (a through d) below. Definitions and delivery formats are as follows: For word processor documents, see paragraph 7.a; for drawings see paragraph 7.b; for CAD models, tubing, mold, and loft data see paragraph 7.c; and for electronic design data files, see paragraph 7.d.

Note: To enhance manageability, transportability, and usability, applicable native and neutral design model files shall be efficiently grouped and encapsulated at each appropriate item level. The encapsulated data files shall include design data such as schematics, printed circuit board assemblies, mechanical item models, 3-D models, parts libraries, link files, configuration files, attribute files, and other associated files required to regenerate the complete design in any CAD environment that has the native or other suitable design software package. Also, the above requirement applies to machine control data (such as Gerber, drilling, etc) and software data files. Either Windows compression .zip format or UNIX’s “TAR” command is the preferred encapsulation methods. If these preferred methods are not used, an alternate method must be approved by the acquiring activity before data delivery. Single files that exceed the capacity of a CD or DVD shall use a file splitter program that creates a *.BAT file that can be used to reconstruct the parts of the split files after delivery.

The above encapsulation requirement also applies to native drawing sheet files (for the same drawing number) which have different file extensions such as 5897.1 (for sheet 1), 5897.2 (for sheet 2), 5897.3, 5897.4, etc. They shall not be zipped if each sheet is delivered as a single file per sheet.

a. Word Processor and Supporting Logistics Documents: Documents created using a word processor that can be delivered and interpreted on the majority of word processing systems including those widely used in the DoD, such as Microsoft Word® (preferable). Document requirements are separate from drawing requirements for the purposes of this Air Force document. Test Methods and Procedures, Associated Lists, Acceptance Testing Criteria, Configuration Item Specifications, Engineering Analysis results, Parts Lists, Data Lists, Wire Lists, and company specifications and standards are all examples of these documents. The native and neutral document files shall be stand-alone entities. These data files shall be independent of external links to other software tools, databases, or other files. Documents delivered shall be the standard 8-1/2 by 11 inch or equivalent “A” or “B” [11” by 17”] drawing size. Word processing documents shall have one filename provided on the digital data media to cover all sheets for each document number submitted. For the final delivery, all approved changes need to be incorporated and the track changes information shall be hidden when the documents are saved. All documents shall be saved in their final form or official appearance so the users do not have to make any viewing adjustments.

A PDF or MS Word document delivered as a single composite file shall have the spreadsheet fields populated in the metadata spreadsheet by having the sheet number as “1” and total number of sheets also equal to “1.” All sheets within the PDF or Word file shall be in numerical order when the document is viewed. The PDF documents shall be delivered with full text-searchable capability, rather than scanned images, image plus text, or image-only documents.

The PDF documents shall also be saved in black and white format instead of color or color compression format. This does not include changing color pictures or diagrams.

NOTE: Government CAGE coded documents shall be delivered in Microsoft Word® for the native format, or shall be saved in MS-Word format and delivered as a .DOC file.

Delivery Format: Native Document – MS-Word®, WordPerfect®, or others

AND

Neutral Format – Portable Document Format (PDF) (Adobe Reader compatible) or MS Word RTF

b. Engineering Drawings (VECTOR): Drawings shall be delivered that are made from presentations describing a particular physical/logical entity or process using 2-dimensional geometry and textual information for both electrical/electronic and mechanical items. These drawings may also be created from view plane projections of a 3-D model, but parametric-based systems exist that will facilitate semi-automatic creation of engineering drawings from the 3-D database. Drawings shall be delivered in all formats below where the scale of the drawing form is 1-to-1. D-size drawings shall measure 22 inches high by 34 inches wide, no matter what scale factor is called out (if any) in the title block of that drawing, per ASME Y 14.1. The requirements set forth in paragraph 7.c, “Geometry and CAD Creation Requirements for 2-D Drawings, 2-D and 3-D Tubing and Mold Data, and 2-D and 3-D Models” for 3-D Models shall apply. Loft surfaces shall also be provided in the aircraft coordinate system to correlate with delivered drawings, when loft data drawings are delivered. All distribution statements, export control notices, current design activity code blocks, destruction notices, and other statements for drawings that appear in one file extension (native, neutral, raster, or view-only) shall appear and contain the same statements on all other file extensions delivered, except for 3D model files which are delivered under contractual ASME standards.

PDF Notes: All sheets shall be contained in a PDF file per drawing number. Marking note annotations in a PDF drawing are not allowed. PDF drawing deliveries containing raster graphics may be delivered, when approved, according to all of the following conditions: when it is determined the native drawing contains graphics that shall not need to be edited at a later time (such as a photograph) and the raster images are embedded within the PDF pages whereby the graphics are visible for that sheet on paper. Contractual ASME specifications allow for picture drawings that shall be reviewed for acceptance for each delivery in PDF format. Associated lists such as parts lists, etc. and accompanying documents shall be separated into their own separate PDF file and not included in the drawing PDF file. This PDF File shall not be Write Protected or Password Protected, unless approved by the acquiring activity before data delivery.

Delivery Formats: Native CAD – Any format native to the contractor’s CAD system is acceptable, e.g. AutoCAD® (preferred), CATIA®, Intergraph®, Applicon®, Computervision®, Pro Engineer®, PTC CREO® Mentor Graphics®, NX®, and others

Neutral – Drawing eXchange Format (DXF) (preferred), American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher shall be delivered or Product Data Exchange using STEP (PDES)/Standard for the Exchange of Product data per ISO 10303 Application Protocol (AP) 203 (preferred) or

View only – Searchable PDF drawings shall be delivered as full sized drawings based on the applicable drawing size. However, if PDF files cannot be produced from the CAD system, the following may be substituted upon obtaining approval and format from the acquiring activity: Hewlett Packard Graphics Language® (HPGL) shall be delivered per HPGL Creation Requirements below, Continuous Acquisition & Lifecycle Support (CALS) Type I, or TIFF Group 3 or 4

View Only HPGL Requirements:

(1)HP 7586 (or other compatible plotter) or HPGL/2 format

(2) HPGL files shall be generated from the native drawing CAD program.

(3) The drawing form shall be preserved at a scale of 1-to-1. For example, a D-size drawing shall measure 22 inches high by 34 inches wide, no matter what scale factor is called out in the title block. The contents on the drawing shall be scaled to the scale factor as stated in the title block. Note: The Computer Aided Design (CAD) definition is the apparent size of objects in a view with respect to a drawing sheet/form.

(4) Plot origin is at 0.00, 0.00.

(5) Multiple drawing sheets or plotter files within the same HPGL filename are not acceptable for delivery.

c. Geometry and CAD Creation Requirements for 2-D Drawings, 2-D and 3-D Tubing and Mold Data, and 2-D and 3-D Models: Geometric representation of a physical detailed part, assembly, surface, or system in either two or three dimensions created using CAD tools that consist of elemental (wireframe using lines and points like drafting), surfaces, and solids (swept, constructive solid geometry (CSG), and boundary representation (Brep)). Engineering models required for delivery are used not only to produce 2-D drawings, but also serve as a basis for Numerical Control (NC) machining, obtaining engineering properties, finite element and computational analysis, simulations, etc. These product data CAD and model requirements are in addition to the above drawing requirements.

Solid, wireframe, Brep, and other formats delivered as the native 3-D model format shall only be done when the original 3-D models were made in these formats.

Digital models used in the creation of the engineering drawings associated with the models in the same file, due to the characteristics of the CAD system being used,…