2755666_ATTACH.pdf

Attachment 1

Continuation of DD Form 1423-1, Block 16

1. Blk 7:

a. "SD" for the final delivery of TDP compact disk.

b. "LT" for the delivery of a sample compact disk for government verification testing.

2. Blk 9:

a. Distribution Statement

1. Unlimited Rights: Data shall be marked with Distribution D, as appropriate in accordance with DODI 5230.24. The statement shall be applied within the border, to the first page of each Technical Data Package (TDP) document prior to delivery of documents to AFLCMC/LZPEM. Distribution statements on existing drawings and associated lists requiring delivery under this contract need not be changed unless otherwise specified in the contract or order.

2. Limited Rights (Proprietary): Data shall be marked with Distribution B, as appropriate in accordance with DODI 5230.24. The statement shall be applied within the border, to the first page of each TDP document prior to delivery of documents to AFLCMC/LZPEM. Distribution statements on existing drawings and associated lists requiring delivery under this contract need not be changed unless otherwise specified in the contract or order.

NOTE: An abbreviated version of the Distribution Statement is not acceptable. A reason for the assigned statement must be included as well as date (could use the Date, of the contract) and the controlling office symbol.

b. The following export control notice, in accordance with DODI 5230.24, shall be affixed to 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. The following destruction notice shall be affixed to 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 documents”.

3. Blk 10:

a. Copies of TDP’s shall be provided to support reviews and audits. Digital TDP documentation shall be submitted in lieu of paper copy. Re-submittals to AFLCMC/LZPEM shall be required for each deficient document until deficiencies identified are corrected to the satisfaction of AFLCMC/LZPEM.

b. Shipping list(s) are required for each shipment.

c. Deliver TDP documentation NOT LATER THAN 60 calendar days after

Government approval for final delivery of the hardware.

d. Re-submission is required for deficient, improperly formatted, illegible data and missing data. All data re-submittals shall include an Index.rst file along with the corrected data. Correct and resubmit NOT LATER THAN 30 calendar days after Government notification to the contractor of deficiencies.

4. Blk 11, 12, AND 13:

a. TDP documentation is required for each IPR, audit or review. The contractor shall resubmit corrected TDP documents for government review NOT LATER THAN 30 calendar days after each government review.

b. Deliver TDP documentation NOT LATER THAN 60 calendar days after

Government approval for final delivery of the engineering data. Resubmission is required for deficient, improperly formatted, or illegible data as determined by AFLCMC/LZPEM. Correct and resubmit corrected data NOT LATER THAN 30 calendar days after Government notification to the contractor of the deficient delivery.

c. Deliver shipping list(s) with each TDP shipment.

d. Deliver TDP updates/revisions 30 days prior to last hardware delivery.

e. Deliver formatted sample compact disk NOT LATER THAN 120 calendar days after contract award.

5. Blk 14:

TDP DOCUMENTATION CD Delivery

AFLCMC/LZPEM

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

REVIEW/AUDIT

SHIPPING LIST(S) 1

SAMPLE COMPACT DISK 1

COMPACT DISK 1

6. Blk 15 Total (example) 4

MIL-STD-31000A

TDP OPTION SELECTION WORKSHEET

SYSTEM: DATE PREPARED:

A. CONTRACT NO.

B. EXHIBIT/ATTACHMENT NO.

C. CLIN

D. CDRL DATA ITEM NO(s)

1. TDP LIFECYCLE Level (CHOOSE ONLY ONE PER WORKSHEET) Note: The Level must coincide with the requirements of the elements selected in Block 5.

A. CONCEPTUAL LEVEL

DEVELOPMENTAL LEVEL

PRODUCTION LEVEL

B. REMARKS:

2. DELIVERABLE DATA PRODUCTS (X ALL THAT APPLY AND COMPLETE AS APPLICABLE)

TYPE FORMAT

A. 2D DRAWINGS

NATIVE CAD ISO 32000 PDF HARD COPY

OTHER FORMAT (SPECIFY) __________________________________

B. 3D MODELS:

TYPE 3D: 3D MODEL ONLY

TYPE 3D: 3D MODELS W/

ASSOCIATED 2D

DRAWINGS

NATIVE CAD (Specify level of annotation) ___Example “CATIA version 5.0” or AutoCAD_____ MODEL ORGANIZATION SCHEMA (Specify Appendix B or other) _____________

NEUTRAL FORMAT (SPECIFY, e.g., ISO 10303 APxxx) _STEP ISO 10303 AP203, AP214 or AP238 OTHER FORMAT (SPECIFY, e.g., 3D PDF, JT) 3D PDF or Drawing eXchange Format (DXF) (preferred)

C. METADATA

(Specify in Section 9)

ASCII TEXT-PIPE DELIMITED ISO 10303 (SPECIFY, e.g., ISO 10303 APxxx &

DEX)____

JEDMICS (DLF) OTHER FORMAT (SPECIFY) ___JEDMICS (RST)_____

D. ASSOCIATED

LIST (See Sect 7)

NATIVE FORMAT ISO 32000 PDF HARD COPY

OTHER FORMAT (SPECIFY) __________________________________

E. SUPPLEMENTAL

TECHNICAL DATA

(Specify in Section 9)

NATIVE __Native 3D CAD capable of being exported to ISO 10303 STEP format

NEUTRAL (SPECIFY e.g., STEP AP238, 240, DEX, OTHER) __STEP AP203, or AP214 or AP238_

OTHER (SPECIFY e.g., PDF) ___ ISO 32000 PDF ___________________________________________

3. CAGE CODE & DOCUMENT

NUMBERS

A. CONTRACTOR CAGE AND DOCUMENT NUMBERS

GOVERNMENT CAGE (COMPLETE 3B & 3C OR 3D)

B. USE CAGE CODE C. USE DOCUMENT NUMBERS: D. To Be Assigned By:

4. DRAWING FORMATS (X ONE AND COMPLETE AS APPLICABLE)

CONTRACTOR FORMAT. GOVERNMENT FORMAT.

REMARKS: _________________________________________________________________________________________

5. TDP ELEMENTS REQUIRED (X ALL THAT APPLY)

CONCEPTUAL DESIGN DRAWINGS / MODELS

DEVELOPMENTAL DESIGN DRAWINGS / MODELS AND ASSOCIATED LISTS

PRODUCT DRAWINGS / MODELS AND ASSOCIATED LIST

SPECIAL INSPECTION EQUIPMENT (SIE) DRAWINGS, MODELS AND ASSOCIATED LISTS

SPECIAL TOOLING (ST) DRAWINGS, MODELS AND ASSOCIATED LISTS

SPECIAL PACKAGING INSTRUCTIONS (SPI) DRAWINGS, MODELS AND ASSOCIATED LIST

SPECIFICATIONS AND/OR STANDARDS (SPECIFY) ____________________________________________________________ SOFTWARE DOCUMENTATION (SPECIFY) ____________________________________________________________________ QUALITY ASSURANCE PROVISIONS (QAP) (SEPCIFY) __________________________________________________________ METADATA (SPECIFY) ______________________________________________________________________________________ SUPPLEMENTARY TECHNICAL DATA (SPECIFY) ______________________________________________________________

FIGURE 2: TDP Option Selection Worksheet

MIL-STD-31000A

6. TDP DATA MANAGEMENT PRODUCTS

SOURCE CONTROL DRAWING (SOCD) APPROVAL REQUEST

DRAWING NUMBER ASSIGNMENT REPORT

PROPOSED CRITICAL MANUFACTURING PROCESS DESCRIPTION

7. ASSOCIATED LISTS (X 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 REQUIRED (Specify Levels of Assy) __________________________________________________

E. APPLICATION LISTS (1) INTEGRAL (2) SEPARATE (3) CONTRACTOR SELECT

F. OTHER REQUIRED (SPECIFY) ___ INDENTURED DATA LISTS________________________________

8. APPLICABILITY OF STANDARDS. THE FOLLOWING STANDARDS APPLY: (X AS APPLICABLE)

ASME Y14.100

ENGINEERING DRAWING

PRACTICES

WITH APPENDICES

B C D E

ASME Y14.24 TYPES AND APPLICATIONS OF

ENGINEERING DRAWINGS

ASME Y14.34 ASSOCIATED LIST

ASME Y14.35M REVISION OF ENGINEERING

DRAWINGS AND ASSOCIATED LIST

ASME Y14.41 DIGITAL PRODUCT DEFINITION DATA

PRACTICES

ASME Y14.5 DIMENSIONING AND TOLERANCES

OTHER STANDARDS

APPLY AS DESCRIBED:

COMPANY STANDARDS

PERMITTED:

YES NO

9. OTHER TAILORING (ATTACH ADDITIONAL SHEETS AS NECESSARY)

See attachments 2, 3, 4, 5, 6, 7, 8, 9, 10 to the TDP Option Selection Worksheet

FIGURE 2: TDP Option Selection Worksheet (cont.)

ATTACHMENT 2

CONTINUATION OF TDP OPTION SELECTION WORKSHEET, BLOCK 9

ADDITIONAL MATERIAL REQUIREMENTS/INSTRUCTIONS

1. Copies of the Technical Data Package (TDP) to support reviews and audits shall be the least costly media that meets the stated requirements. Alternate proposals that would satisfy this requirement may be submitted for consideration/approval to AFLCMC/LZPEM.

Paper media review requirements shall be satisfied when TDP documents are provided in digitized format through remote and/or local access terminals from contractor files.

Training and assistance shall be provided to government personnel accessing digital TDP documents. TDP documents prepared by automated equipment, i.e., Computer Aided Design (CAD), may contain printed names in the title block in lieu of signatures, providing the signatures of the approving officials are recorded on an engineering document release record. Approval indicators may also be used if applied by a Digital Approval System which shall satisfy the contracting activity requirements for uniqueness, verifiability and sole control.

2. Each TDP document delivered shall be identified with Weapons System Code ‘__’. This code shall be entered in each TDP document, the shipping list, and the DD Form 250 accompanying each digital TDP delivery. If there is no code for the Weapons System then leave blank.

3. 3D Solid Models and 2D data based on 3D Models shall be delivered in accordance with

MIL-STD-31000A, Air Force Drawing 9579776 Rev N (option 3), and ISO 10303 (STEP).

4. Classified Data shall be delivered digitally on ISO-10149 compliant Compact Disk (CD).

CD's bearing classified information must be marked with the highest level of classification stored on it as well as any special control notices that apply to the information using one of the labels specified in DODI 5200.01. The label may be affixed to the sleeve or container in which the CD is stored.

5. Acceptance test procedures shall be provided to verify proper performance of separately procurable circuit cards, wiring harnesses and cable assemblies, modules, and other items which perform an electronic or electromechanical function. Whenever economically feasible with respect to the government's life cycle use of the item and requirement to compete spare parts, the procedures will test the unit independently of its next higher assembly. When possible, standard test equipment and methods shall be specified.

6. Acceptance test procedures that require special test fixtures will provide sufficient description in company format to fabricate the test fixtures.

7. Other TDP documentation requirements imposed by the following specifications, standards or work tasks by the contract or order shall be applied to or referenced on the applicable TDP documents.

8. 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. For materiel subject to the marking requirements of other specifications or standards, the TDP elements shall specify the marking method, location, and content of those requirements.

9. When Portable Document Files PDF files are required, they shall be in accordance with

AF Drawing 9579776 Rev N.

10. Selected item drawings are required for all items and assemblies that require the application of Environmental Stress Screening (ESS) selection criteria to meet system requirements. The TDP element shall define, directly or by reference, the ESS selection criteria applied to the item or assembly identified.

11. Incoming ESS inspection procedures used on materiel/items which do not require selected item drawing delineation shall be required directly or by reference on the TDP element identifying that materiel/item.

12. Any ESS utilized during manufacturing/production in addition to the selected item ESS or incoming inspection criteria, shall be required either directly or by reference on applicable TDP documents.

13. Existing multi-detail drawings and associated lists developed using contractors standard drawing practices may be acceptable when the contractors drawing practice provides traceability of part number designations to the drawing on which it is defined. The CAGE Code, TDP Document Number, and Part Number for an item depicted on a new or existing document shall meet the requirements of ASME Y14.100, Chapter 6 and Appendix D.

Parts Lists are required for each assembled item. Drawings, associated lists, and other engineering data shall be such that their intent and interpretation are clear and unambiguous.

14. Government and Industry Association (ANSI, ASME ISO, etc) documents shall not be submitted.

15. Except as stated herein, use of drawing types and lists not specified in ASME Y14.100 and ASME Y14.24 require government approval prior to selection. When required to document the item design, the drawing types in ASME Y14.100 and ASME Y14.24, as applicable shall be incorporated in the TDPs.

16. Modification Drawing. Modification drawings shall be used only for their intended purpose, which is to show how to modify delivered items, assemblies, installations, or systems.

Modification drawing information shall be incorporated into TDP design documentation by means of revision.

17. Control Drawings. Unlimited rights control drawings (vendor item control or source control) or unlimited rights company standards meeting the form, fit, function, and performance requirements for control drawings shall be provided for commercial items whenever the vendor items are non-reparable or determined non-reparable by government provisioning.

(See MIL-STD-31000A for definition of “commercial item”). Control drawings are not required for the commercial item when government provisioning has determined the item to be reparable. In the latter case, the vendor drawings are required for delivery to the government.

18. Vendor Item Control Drawings. Vendor Item Control Drawings, when selected in lieu of or in addition to control drawings for repairable commercial items, shall provide sufficient information to permit Government maintenance and modification of the items.

19. Tube Bend Drawings. Tube bend drawings shall contain the elements of data required by

ASME Y14.24 using the X, Y, Z coordinate system for the establishment of the endpoints and centerline intersections. The columnar systems of MIL-D-9898C and ASME Y14.24 shall not be used, but may be used as supplementary reference information.

20. Altered item drawings additionally require that data be provided for the items which are to be altered.

21. Interchangeability Control Part Numbers shall be established to control, under a single control number, interchangeable source control part numbers under the following conditions. This number is used to select from source control part number candidates those items which have been qualified for use in specific applications. The number is cited in parts lists in lieu of the source control part numbers. It does not re-identify source control part numbers. When this system is used, each source control part number has but one approved vendor and vendor design.

22. Repairable Source Control Part Numbers. An Interchangeability Control Part Number shall be used to identify, under a single control number, two or more repairable source control part numbers used interchangeably in a specific application. The Interchangeability Control part number will be cited in parts lists.

23. Source Control Part Numbers on Aerospace Propulsion Systems. On Aerospace

Propulsion System applications, an Interchangeability Control Part Number shall be used to select and identify, from two or more possible candidates, specific source control part numbers which are approved for the application cited by the Interchangeability Control Drawing.

24. Company standards and specifications selected in accordance with the cancelled MIL-

STD-970 may be acceptable but shall not be prepared in lieu of control drawings required in accordance with ASME Y14.24.

25. Standardized Microcircuit Drawings (SMDs) to the extent specified by the Parts Control

Program and as directed by the Military Parts Control Advisory Group (MPCAG) (see MIL- HDBK-780) are required for microcircuits.

26. Product drawings (non-modification and non-installation) are required to define end items.

27. Impacted production installation drawings shall be revised to contain ECP traceability notes and prior ECPs.

28. Impacted production detail and assembly drawings shall be revised to include prior changes to reflect delivered item configuration.

29. Duplicate data should 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 the repository at Tinker AFB, unless requested by AFLCMC/LZPEM. When a document of current issue indicates limited rights and the previous issue indicated unlimited rights, both issues shall be submitted.

30. Engineering data covered by this CDRL must be, or have been, delivered to the Air Force engineering data repository (AFLCMC/LZPEM) at Tinker AFB, OK. Engineering data delivered to any other destination does not satisfy the requirement for delivery to a repository under this CDRL. For example, copies of drawings sent to engineering offices or placed in Time Compliance Technical Order (TCTO) hardware kits and sent to a government destination do not satisfy the repository delivery requirements of this CDRL.

Conversely, unless otherwise specified, delivery of engineering data to an Air Force repository would not satisfy a required task of placing drawing copies in the TCTO kit or delivery to another location.

31. Unless otherwise specified in the contract, all engineering data shall be prepared in the

English language in accordance with FAR 52.214-34

32. Sequencing. Regardless of media, delivered engineering data documents shall be in numerical drawing or document sequence and all images for each drawing or document shall be in drawing sheet sequence. The contractor shall sequence complete drawings as well as their accompanying documents and associated lists together on a single compact disk in alphanumeric sequence. The leading edge of the documents shall start with sheet 1 in sequentially numbered sheets or pages with the title block being the first frame of each document. Engineering drawing sheets requiring multiple image representation shall have the image that contains the title block appear first with successive images appearing in order until the opposite end of the drawing sheet is represented. Multi frame sheets shall be prepared with all frames the same size. There shall be a 4” minimum overlap. This same sequencing requirement applies for multiple CD delivery on the same shipment from the first CD to the last CD.

33. Multi-sheet documents shall be prepared with all sheets the same size.

34. For newly prepared documents, only one document number shall appear in the document number block.

35. Sheet Numbering: The first sheet shall state the total number of sheets in accordance with

ASME Y14.1, Figure 10 (Sheet 1 of 3, for documents having 3 total sheets). "Pages of sheets" or "sheets of pages" are not permitted for newly developed data.

36. Zone Numbers: Formats, except for A and B size drawings, shall include zones for reference purposes. For A and B size drawings, zoning shall be optional. Zones shall be indicated by alphabetical and numerical entries in format margins as well as by sub-divisions or multiples thereof.

a. Zones shall be sequentially numbered with each sheet, i.e., sht 1 zones 1-8, sht 2 zones 9-16, sht 3 zones 17-24, etc.

b. Zone sizes shall be equal, and no less than 1 inch and no more than 5.5 inches.

37. Engineering data delivered to the government repositories as final delivery shall have all outstanding changes incorporated into the data.

38. Each engineering data document shall be marked with its Department of Defense (DOD)

Distribution Statement and, when applicable, appropriate documents shall also be marked with the DOD Rights in Data information or other legends/information such as contract numbers that are applicable to the document. If not preprinted, these statements and legends can be machine printed, hand stamped or applied by the overlay method. The words shall be placed in an open area of each document or each segment for documents that require multi-frame filming.

39. Application Data: Application data with “Next Assembly” and “Used On” columns are required for drawings whose detail part or assembly depicted thereon is for an element of a larger item. The Next Assembly (“NEXT ASSY”) column shall show the drawing numbers(s) of the next higher assembly to which the drawing applies. The Used On (“USED ON”) column shall show the model number or equivalent designator of the assembled unit(s) of which the part is an element. Application Data is not required for source control drawings, specification control drawings, vendor item control drawings, company standards, and commercial products (as defined by MIL-STD-31000A). The Application Data shall be located near the Title Block on sheet 1, or placed on a separate reference 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 application data is included on a separate Parts List, the note required by ASME Y14.34 shall be expanded to read “SEE SEPARATE PARTS LIST FOR PARTS AND

APPLICATION DATA”.

40. Interconnection diagrams are required for wiring harnesses and cable assemblies, except for coaxial cable assemblies

41. Section lining for cut surfaces is required and shall be in accordance with ASME Y14.2.

42. 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, such as “Government Furnished Property under F34601-99-x-xxxx.”

43. Warranty Statements. When required by the contract or purchase order, warranty statements shall be affixed to or entered on each drawing. The statement shall not obliterate nor obscure information on the field of the drawing. The warranty statement shall specify the warranty period and include the contractor or agency that shall correct or repair the deficiency. Warranty statements entered on TDP documents shall contain, as a minimum, the following information:

a. Warranted item until (Enter warranty expiration date YYMMDD format).

b. Contract number. (Enter the contract number that invokes warranty of TDP documents).

c. Deficiencies in this TDP document shall be corrected by (Enter the contractor and address of the agency that shall correct the deficiency)

44. When required by the contract or purchase order Government Purpose Rights Legends

(GPRL) legends or statements shall be affixed to or entered on each applicable TDP document. Legends shall not obliterate nor obscure information on the field of the drawing.

a. General Marking Instructions: The contractor, its subcontractors or suppliers, shall conspicuously and legibly mark the appropriate legend on all technical data that qualify for such markings. The authorized legends shall be placed on the transmittal document or storage container and, for printed material, each page of the printed material containing technical data for which restrictions are asserted. When only portions of a page of printed material are subject to the asserted restrictions, such portions shall be identified by circling, underscoring, with a note or other appropriate identifier. Technical data transmitted directly from one computer or computer terminal to another shall contain a notice of asserted restrictions. Reproductions of technical data or any portions thereof subject to asserted restrictions shall also reproduce the asserted restrictions.

b. The following 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

ATTACHMENT 3

CONTINUATION OF THE TDP OPTION SELECTION WORKSHEET, BLOCK 9

ASME Y14.100-2013 & Appendices B,C,D,E Engineering Drawing Practices

1. Each section of ASME Y14.100 and Appendices B, C, D, E is applicable and as tailored by the following:

a. SCOPE. Para 1.1 Change paragraph to read “This standard and Appendices B, C, D, E and F establish the essential requirements and reference documents applicable to the preparation and revision of engineering drawings and associated lists. Past versions of MIL/DOD-STD-100 and previous editions of ASME Y14.100, which were contractually invoked for the delivery of drawings shall continue to apply.”

b. Paragraph 4.5.1 Add “if required.” after ASME Y14.1M. Add as new sentence, “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 decimal inch dimension.”

c. Paragraph 4.20 Graphic Symbols, Designations, Letter Symbols, and Abbreviations.

Add as new sentence after sentence one, “When applicable, Section Line representation shall be depicted on drawings.”

d. Non-Mandatory Appendix A. Delete Non-mandatory Appendix A “Tailoring”.

e. Appendix B, Paragraph B-5.2, Digital Data. Add new sentence, “All pertinent drawing information required shall be inside the drawing border. Lettering less than 5/32 inches or metric equivalent is not allowed. Use of lettering less than 5/32 inches or metric equivalent requires approval by the government acquiring activity”.

f. Appendix B, Paragraph B-5.2, Digital Data. Add new sub-paragraph B-5.2.1, “Documents extracted from Computer Aided Design (CAD) platforms or scanned into raster images, shall meet thick and thin line convention density criteria recommended in Figure 3.1, ASME Y14.2 (Thick line - 0.032 inches: Thin line - 0.016 inches).”

g. Appendix B, Change existing paragraph B-5.2.1 Plotters to “B-5.2.2 Plotters”.

h. Appendix B, Paragraph B-7, Printed Board Assemblies. After last sentence add, “Printed wiring assembly drawings shall contain a note that specifies the item shall be manufactured in accordance with MIL-PRF-31032B.”

i. Appendix B, Add new Paragraph 10, “Zoning. Except for A, A4, B, C or D size

Drawings, zoning references shall be used and shall be reflected in the revision block.”

ATTACHMENT 4

REQUIREMENTS FOR PRINTED WIRING BOARD DIGITAL DATA

1. Printed Wiring Board (PWB) Description shall be in digital form in accordance with

IPC-D-350.

a. Delivery media shall have CONTENTS.TXT file in ASCII format listing files on the delivery media, drawing number, part numbers(s), assigned CAGE code(s), rights, size of each file in uncompressed form, application data, used on data, revision level of the file, revision level of the used on data drawing, and the purpose of the file.

b. Delivery media containing more than one printed wiring board assembly shall contain directories for each printed wiring board.

c. Delivery media with compressed files shall also contain decompression software.

d. Delivery media shall be free of limited rights or shall be accompanied by documentation giving the Air Force unrestricted use of all files and software contained on the media.

e. All compact disk transfer media shall have identification information printed upon it identifying the contents of the media. The markings shall be accomplished using indelible ink. Gummed labels shall not be used. As a minimum, the information shall include Contract Number, Contractor Name, EA Number if Applicable, Vol. ID and Date. Other transfer media shall be marked IN ACCORDANCE WITH agreements made by the contractor, contracting officer and the repository POC.

f. PWB data shall:

1. Comply with IPC D-350

2. Be written in ASCII

3. Contain format statement. Example "FSLAN4X43Y43"

4. Identify CAD platform and software used to develop Gerber file.

g. Drill data shall be provided on CD in accordance with ISO 9660

h. Establish document identification for each dataset in a manner that can be identified on using drawings, and used for accurate identification, storage, and recovery in manual and digital repositories.

i. Board file sets shall include the following files as a minimum:

1. Revision letter of file

2. Identify board part number

3. CAGE code

4. Column headings shall identify horizontal (width) and vertical (height) dimensions which correspond to “X” and “Y” coordinates, respectively, for proper orientation of shapes.

5. Units of measurement (mils, millimeters, etc.)

j. The files shall be properly aligned and include the following images:

1. Circuit layers

2. Board outlines

3. Silk screen of component reference designations

4. Silk screen of component’s outlines as they appear on the PCB

5. Solder mask

6. Plated and un-plated drill holes

k. Each of the above image files shall include the following information as a minimum:

1. Board part number

2. Revision letter of image

3. CAGE Code

4. Layer order number and/or image name

5. Vertical and horizontal register marks with x-y coordinate dimensions and tolerances

l. The drill data file set shall contain the following information:

1. Board part number

2. File revision

3. CAGE Code

4. File type (Plain ASCII Text, etc.)

5. Drill tool sizes

6. Holes x-y coordinates

7. Drill tool (bit) used at each x-y location

8. Identify plated and un-plated holes, if not identified on the master drawing

ATTACHMENT 5

SOFTWARE AND FIRMWARE DATA

1. This data shall be delivered as follows:

a. Software and firmware data. Drawings defining software that will be or are intended as resident in a firmware device shall be prepared as Software Drawings for the master media and Altered Item Drawings for the firmware.

b. Software drawing. A software drawing describes the characteristics of the software and its master media, used for programming each applicable device or assembly. Software programs will not be defined as truth tables but rather identified as to be supplied as a duplicate of the master media in digital form.

c. Software drawing requirements. The drawing shall specify the type of media (for example, CD), media PIN, and version identification of the software. In addition, the media characteristics (for example, type, number of tracks, density and size) and the characteristics and formats of the information stored on the media shall be fully described. Any other information necessary to completely describe how the master media is to be used shall also be included. The PIN of the master media shall be shown as a suffixed identifier of the software drawing. If more than one version of the software is to be installed or used, the drawing shall provide separate suffixes for each version. The notation SOFTWARE DRAWING shall be placed above the title block.

d. Firmware information. For software resident in a programmable device

(firmware), both Software Drawings and Firmware Drawings shall be required.

Circuit boards with one or more devices that require programming at that level will be prepared as an assembly drawing. Devices assembled at that level will be supported by appropriate specifications or drawings that specify requirements prior to programming.

e. Firmware drawing. The drawing describing the programming requirements of a single programmed device will be prepared as an Altered Item Drawing. The notation ALTERED ITEM DRAWING shall be placed above the title block.

f. Firmware drawing requirements.

1. The firmware drawing shall define the requirements of the device prior to programming either on this drawing (by referencing the original vendor's Part Identification Number (PIN) or providing complete description of the item) or by vendor item or source control drawing if a Military specification or standardized military drawing item is not available. In addition, the requirements for programming (bit pattern downloading) of the device shall be included. The firmware drawing shall indicate the name and version number of the software being impressed.

2. The same type of requirements shall be included on drawings for circuit boards with multiple devices programmed at the same time. Inspection requirements for the programmed device shall also be included. If more than one version of the programmed device is to be installed or used, the drawing shall provide a PIN for each version. The drawing shall also include an application chart or table that will cross-reference the master media for each version to each applicable programmed part by their respective PINs.

g. Software source information. The master media for programming the device shall be identified by reference to the appropriate Software Drawing and PIN.

ATTACHMENT 6

SHIPPING LIST REQUIREMENTS

1. A shipping list shall be prepared in accordance with the following:

a. Block 14 of CDRL: Deliverable engineering data (documents/drawings) includes that of subcontractors and vendors, in addition to contractor engineering data.

b. Blocks 7,10,11,12 and 13 of CDRL: To be delivered concurrent with TDP delivery.

2. Data shall be delivered on CD Rom and save as (ShipList.dlf) containing 11 fields with each field separated with a (|) delimited character in the following order.

3. Do not enter more than one carriage return at the end of the last record.

4. Sample DLF File:

F34601-03-C-XXXX|CONTRACTOR NAME|12345|SUB CONTRACTOR NAME|123456|PL|0001|0001|U|A

Seq DATA

ELEMENT

Data size/type

Mandatory Notes Description

1 Contract Number 16 bytes x Contract Number. Enter the contract number applicable to the respective drawing.

2 Prime Contractor 60 bytes x Prime Contractor Name.

3 Prime Cage 5 bytes x Prime Cage. Cage code of prime contractor.

4 Vendor Cage 5 bytes A/N x 13 Vendor Cage 5 Vendor Name 60 bytes x Vendor Activity Name.

6 Drawing Number 32 bytes A/N x 13

Document Number. Unique identifier for a drawing or other document as assigned by the organization identified by the document CAGE. Document Numbers shall reflect what is in the drawing title block

7 Document Type 2 bytes A/N x 4,13 Document Type. If record describes an Accompanying Document, this field shall contain the Base Document Type. If document does not have a document type, leave blank.

Number Of Sheets 4 bytes N x 15 Number of Sheets. Total number of sheets contained in the drawing.

9 Sheet Number 12 bytes A/N x Sheet Number. Enter the sheet number applicable to the respective sheet within the drawing.

10 Sheet Rights Code 1 byte A x Rights. Value shall be one of the following:

U Unlimited Rights L Limited Rights K Rights Guard Do NOT leave blank.

11 Sheet Revision 2 bytes A/N x 4,11,13 Sheet Revision. If record describes an Accompanying Document, this field shall contain the Base Document Revision. The following Document Revisions are invalid: I, O, Q, S, X and Z. A blank or null shall be used to reflect no revisions.

ATTACHMENT 7

Current Editions of Applicable Specifications, Standards, Regulations, Directives Form a Part of This CDRL

In Their Entirety and as Tailored Herein

Military Spec/Std Title MIL-STD-130 Identification Marking of U.S. Military Property MIL-STD-1840C & Not 1 Automated Interchange of Technical Information MIL-PRF-28002C & Not 1 Raster Graphics Representation in Binary Format, Requirements for MIL-STD-31000A Technical Data Packages

MIL-PRF-31032B &

Supplements

Printed Circuit Board/Printed Wiring Board, General Specification For

MIL-PRF-5480G Data, Engineering and Technical Reproduction MIL-D-9898C & Not 2 Drawings, Tube Bend MIL-HDBK-59B & Not 1 CALS Implementation Guide MIL-HDBK-288B Review and Acceptance of Engineering Drawing

Packages

MIL-HDBK-780D

w/Change 1

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

DODI 5230.24

DODD 5230.25

Distribution Statements on Technical Documents Withholding of Classified Data From Public Disclosure

Industry Specs/Stds

Title

ASME Y14.1 Drawing Sheet Size and Format ASME Y14.2 Line Conventions and Lettering ASME Y14.3 Multi and Sectional View Drawing ASME Y14.5 Dimensioning and Tolerancing ASME Y14.8 Casting and Forging Drawings ASME Y14.24 Types and Application of Engineering Drawings

ASME Y14.31

ASME Y14.34

Undimensioned Drawings Associated Lists

ASME Y14.35 Revisions of Engr Dwgs and Assoc Lists

ASME Y14.38

ASME Y14.41

Abbreviations and Acronyms Digital Product Definition Data Practices

ASME Y14.100 Engineering Drawing Practices, Appendices B, C, D, E ASME B46.1 Surface Texture (Surface Roughness, Waviness, and Lay) IPC D-350 Reference Printed Board Description in Digital Form IPC 6011 Reference Generic Performance Specification for Printed Boards

ISO 9660 & AMD 1 Reference 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)

ISO 10303

RS-274X

Reference

Reference

STandard for the Exchange of Product (STEP) Model Data Gerber Format Users Guide

ATTACHMENT 8

MEETINGS/REVIEWS/AUDITS

Meetings. The Contractor or the Government may request informal, unscheduled meetings, briefings, conferences, reviews or Technical Interchange Meetings (TIM).

The Contractor shall attend and participate at any foregoing sessions where support may be required when authorized by the Program Office.

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 may be held in two phases, hosted by the contractor, a contract phase, held as part of the kickoff meeting and a technical phase approximately 60 days after contract award. The Contractor shall submit an agenda and presentation material prior to each conference phase.

Review of Technical Data Packages. When applicable 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.

Formal Audits. The contractor shall be responsible for conducting audits in accordance with the following requirements except as amended by the contract. The contractor shall be responsible for insuring that sub-contractors, vendors and suppliers participate in formal audits. Unless otherwise specified in the Statement of Work, the audits shall be conducted at the contractor’s facility or at a designated subcontractor facility. 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 FCA to verify that the designated configuration item “as built” conforms to the technical documentation which defines the item.

ATTACHMENT 9

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 continuation sheets.

b. TDP OPTION SELECTION WORKSHEET and continuation sheets.

2. The following clauses should be considered for inclusion in solicitations and contracts in accordance Federal Defense Regulations (FAR), Defense Federal Acquisition Regulation Supplements (DFARS).

FAR Paragraph Title

52.214-34 English Language Requirement

DFARS Paragraph Title

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