ATT (6) TDPCR 20-07.pdf

TDPCR No. 20-07

Date: 21 JANUARY 2021

TECHNICAL DATA PACKAGE CONTRACT REQUIREMENTS (TDPCR)

TRAINER TECHNOLOGY UPGRAGE (TTU) CH-53

DEVICE DESIGNATION:

2F174-2 WEAPONS SYSTEMS TRAINER (WST), 2F190-2 AIRCREW

PROCEDURES TRAINER (APT), and 2F239 FLIGHT TRAINING DEVICE

(FTD)

ACQUISITION ACTIVITY:

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION (NAWCTSD)

ON BEHALF OF PMA 205

NAVAL AIR SYSTEMS COMMAND

PATUXENT RIVER, MD 20670

CONTRACTOR:

CONTRACT NUMBER:

Written BY

PENDER.RICKY.

LEE.1042567619

Digitally signed by

PENDER.RICKY.LEE.1042567619

Date: 2021.02.01 13:18:41 -05'00'

REVIEWED BY:

Digitally signed by

WESTBROOK.MICHAEL.T.12056

AEL.T.1205646236 46236

Date: 2021.01.28 08:41:58 -05'00'

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE; DISTRIBUTION IS UNLIMITED.

This document prescribes the Technical Manual format, style, technical content, preparation, and delivery requirements. Instructions and guidance are provided to assist

Technical Manual preparers in the development of accurate, adequate, comprehensible, and usable technical documentation that conforms to and complies with established NAVAIR policy.

This document is effective upon receipt and supersedes all previous information and instructions, regardless of source, related to the preparation of a NAVAIR Technical Manual for the subject equipment. Conformance with the requirements specified are mandatory. No changes or waivers are authorized without the express written NAVAIR approval

NAVAL AIR WARFARE CENTER TRAINING SYSTEM DIVISION GT421

ORLANDO, FL

WESTBROOK.MICH

TDPCR 20-07

TDPCR SUMMARY OF CHANGES

Change No. & Date

Page Paragraph Description Entered By

TABLE OF CONTENTS

TABLE OF CONTENTS

1.0 Scope

2.0 Applicable Documents

2.1 General

2.2 Government Documents

2.2.1 Specifications, Standards, and Handbooks

2.2.2 Other Government Documents, Drawings, and Publications

2.3 Non-Government Publications

2.3.1 American Society of Mechanical Engineers (ASME)

2.3.2 International Organization for Standardization (ISO)

3.0 General Requirements

3.1 Engineering Drawing Practices

3.2 TDP

3.2.1 TDP Contents

3.2.2 TDP Delivery

3.2.3 Data Supplied under Other Government Contracts

3.2.4 Existing Data

3.2.5 Reference Documents

3.2.6 Company Standards

3.3 Legibility and Reproducibility

3.4 Document Markings, Legends, Labels, Notations, and Statements

3.4.1 Security Classification Markings and Notations

3.4.2 Distribution Statements

3.4.3 Restrictive Rights Legends

3.4.4 Item Replacement Notations

3.4.5 Identifying Substitute Parts

3.4.6 Electrostatic Discharge Sensitive Devices (ESD) Marking

3.4.7 Digital Data Marking

3.5 Identification of Contract Numbers

3.5.1 Application of Contract Numbers

3.5.2 Contract Numbers in Data Rights Legends

3.6 Contractor Identification on Documents

3.6.1 Contractor and Government Entity (CAGE) Codes

3.6.2 Contractor Identification on TDP Documents

3.6.3 Original Equipment Manufacturer CAGE info and Part Numbers. P

3.7 Document Identification and Numbering Requirements

3.7.1 CAGE Code

3.7.2 Location

3.7.3 Drawing Number

3.8 Call-out of or Reference to Items and Documents

3.8.1 CAGE Code as a Prefix

3.8.2 Call-out of or Reference to Items

3.8.3 Call-out of or Reference to Documents

3.9 Identification of Materials, Processes, and Protective Treatment

3.10 Other Identification

3.10.1 Bulk Item Identification

3.11 Associated Lists

3.12 Referring to Reference Documents

3.13 Language

3.14 Units of Measure

3.15 Symbols and Abbreviations

3.16 Types and Quantity of Drawing Selections

3.17 Drawing Titles

4.0 Digital Data Delivery (Interim and Final)

5.0 CAD/CAM Product Definition Data

a. Word Processor and Supporting Logistics Documents

b. Engineering Drawings (VECTOR),

c. PDF Notes, see paragraph 5.3;

d. CAD Models, Tubing, Mold, and Loft Data

e. CAD Models, Tubing, Mold, and Loft Data

5.1 Word Processor and Supporting Logistics Documents

5.2 Engineering Drawings (VECTOR)

5.3 PDF Notes

5.4 CAD Models, Tubing, Mold, and Loft Data:

5.3.1 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:

......................................................................................................................................................................................................17 5.5

Electrical/Electronic CAD and CAM Product Data Files:

5.5.1 Product Data:

5.5.2 Product Data Types

6.0 Metadata

7.0 Drawing Repository Parts List Import

7.1 General Information

7.2 Metadata File

8.0 Government Guidance Conference and Reviews

8.1 Government Technical Manual Initial Guidance Conference

8.2 Government Review Process

8.2.1 Deficiency Notification

8.2.2 Time Limit to Correct

8.3 Physical Configuration Audits (PCA)

8.4 Correction of Deficiencies

8.5 Government Acceptance

Appendix A: MetaData

Appendix B: PDAL In-Process Review (IPR) Entry/Exit Criteria

Appendix C: TDP Option Selection Worksheet

1.0 Scope.

This document establishes the mandatory performance and delivery requirements for a Technical Data

Package (TDP) for 2F174-2 WST, 2F190-2 APT, and 2F239 FTD. The

TPDCR requirements contained herein will ensure accurate interpretation by users of the data and ensure adequate interface with Government systems. This TDPCR has been fully prepared to describe the revision of the devices for this effort with the following documentation: The contract Statement of

Work (SOW), Contract Data Requirements List (CDRL), Data Item Descriptions (DIDs) and the TDP requirements defined herein, establish the requirements for preparation and delivery of the TDP for procurement, and engineering and logistics support of the products identified in this contract. This document also provides guidance for Government reviews and audits. The option selection worksheet at the back of TDPCR delineates the requirements for this delivery.

This document defines the content, format, media, and product definition data files preparation requirements for the digital Technical Data Package (TDP). 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.

2.0 Applicable Documents.

2.1 General. The following documents form a part of this contract requirements document to the extent specified herein. The documents listed in this section are needed to meet the requirements specified in this document. While every effort has been made to ensure the completeness of this list, users are cautioned that they must meet all specified requirements documents cited in this specification.

2.2 Government Documents.

2.2.1 Specifications, Standards, and Handbooks.

DoD 5220.22M National Industrial Security Program Operating Manual w/Supplement

DoD Cataloging Handbook H4/H8 Commercial and Government Entity (CAGE) Cataloging Handbook

MIL-PRF-28002 (Inactive) Raster Graphics Representation in Binary Format, Requirements for

MIL-STD-31000B Standard Practices, Technical Data Packages

DI-SESS-81000F Product Engineering Design Data and Associated Lists, dated 17 Apr 2019

DI-SESS-81003F Commercial Engineering Design Data and Associated Lists, dated 17 Apr 2019

(Unless otherwise indicated, copies of the above are available online at http://quicksearch.dla.mil/. Copies of the above are also available from the Defense Printing Service, Standardization Document Order Desk, Building 4D, 700 Robbins Avenue, Philadelphia, PA 19111-5094, phone 215-697-2179. Copies of Cataloging Handbooks H4/H8 are available from the Commander, Defense Logistics Services Center, Battle Creek, MI 49017-3084, phone 616-961-4955 or 4958.)

http://quicksearch.dla.mil/

2.2.2 Other Government Documents, Drawings, and Publications. Unless otherwise specified, the issues are those cited in the solicitation.

DFARS Defense Federal Acquisition Regulation Supplement

H6 Federal Item Name Directory

(Copies of DFARS can be found at www.dcaa.mil/dfars.html) (Copies of H6 Federal Item Name Directory can be found at www.dlis.dla.mil/h6/)

2.3 Non-Government Publications.

2.3.1 American Society of Mechanical Engineers (ASME). (Use current release of each standard.)

ASME Y14.24 Types and Application of Engineering Drawings

ASME Y14.34 Associated Lists

ASME Y14.35M Revision of Engineering Drawings and Associated Documents

ASME Y14.38 Abbreviations and Acronyms

ASME Y14.44 Reference Designations for Electrical and Electronics Parts and

Equipment

ASME Y14.5 Dimensioning and Tolerancing

ASME Y14.100 Engineering Drawing Practices

ASME Y14.41 Digital Product Definition Data Practices

(Application for copies should be addressed to the American Society of Mechanical Engineers, 22 Law Drive, P.O. Box 2900, Fairfield, NJ 07007-2900, Phone 800-843-2763.)

2.3.2 International Organization for Standardization (ISO).

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 Standard for the Exchange of Product Model Data (STEP) (AP203, AP209, AP210, AP212, AP214, AP219, AP224, AP232, AP233, AP237, AP238, AP240, and

AP239)

ISO 32000 Document Management – Portable Document Format

(Application for copies should be addressed to the International Organization for Standardization (ISO), Customer Service Division, 545 Washington Boulevard, Jersey City, NJ 07310-1686, Phone: 1-800- 888-4476.)

3.0 General Requirements. TDPs define the physical and functional characteristics of the accepted configuration of the item and its subordinate assemblies, subassemblies, and all parts thereof. The TDP levels, types, elements and data management products shall be developed in accordance with MIL-STD- 31000E and applicable data item descriptions, as tailored and imposed through the Contract Data Requirements Lists (CDRLs) and the TDP Option Selection Worksheet located in Appendix C of this document. The intended uses of the TDP or components thereof, are for:

a. Competitive procurement of the system or subsystems;

b. Competitive procurement of spares and repair parts;

c. Evaluation and control of physical and functional design interrelationships of interdependent components, equipment, subsystems, or systems;

http://www.dcaa.mil/dfars.html http://www.dlis.dla.mil/h6/

d. Support installation, operation, and maintenance of items, equipment, subsystems, or systems on designated service tests;

e. Identification, description, and cataloging of items of supply; determination of source coding and other provisioning requirements; and differentiation between similar items for standardization purposes;

f. Installation of the system and subsystem;

g. Maintenance at the organizational, intermediate and depot level; and

h. Configuration Management and configuration control.

3.1 Engineering Drawing Practices. Engineering drawing practices for TDP elements are invoked through reference to ASME Y14.100. For acquisition of Production Level engineering drawings/models, ASME Y14.100 and its associated Appendices B through E apply as indicated on the TDP Option Selection Worksheet(s) (Appendix C). Commercial drawings/models supporting the Production Level TDP shall be submitted in accordance with the associated TDP Option Selection Worksheet, in the originator’s format.

3.2 TDP. The TDP consists of all applicable Technical Data such as engineering drawings, models, associated lists, software documentation, specifications, standards, performance requirements, Quality Assurance (QA) provisions, and packaging details. The TDP also includes any referenced explanatory documents, such as documents defining non-standard symbols. An engineering drawing is an engineering document, whether hardcopy or digital data file(s), that discloses directly or by reference, by means of graphic or textual presentations, or combinations of both, the physical and functional requirements of an item. The TDP shall not provide manufacturing process information unless this information is essential to accomplish manufacture of an identical item or for the installation of an item on an assembly.

3.2.1 TDP Contents. The TDP shall include, but shall not be limited to:

a. manufacturing fabrication and assembly sequences;

b. manufacturing fabrication and assembly sequences and the following maintenance type drawings

1) assemblies

2) schematics;

c. block diagrams

1) schematic and block diagram component identification by use of nomenclature, part number, and reference designator

2) wire numbers shall be used to indicate intra and extra connect cabinet wire runs as well as component to component.

3) It is understood that a true unmodified COTS component may not have wire runs identified

d. mechanical and electrical connections

e. digital and analog IO signals and flows

f. drawing tree or tiered hierarchal drawing list

g. assembly drawings

h. parts lists

i. wire lists

j. modified Commercial Off-The-Shelf (COTS) component drawings

k. mirror and projector angle drawings

l. mirror manufacturer and assembly drawings

m. physical trainer locations showing locations of splices (for location of any splices in a cable, wire or fiber wire)

n. component unit locations (utilizing reference designations)

o. physical characteristics (including form and finishes, necessary calibration information, and quality control data.)

3.2.2 TDP Delivery. The TDP shall represent the configuration of the item at the time of final delivery of the TDP. Changes by revision authorization documents shall be incorporated into the affected documents of the TDP.

3.2.3 Data Supplied under Other Government Contracts. Data supplied under other Government contracts, if not supplied as part of new and/or revised data, shall be identified. The applicable Government contract number and the DoD Engineering Data Repository where the data resides shall be included.

3.2.4 Existing Data. When existing data meets the following criteria, or can be modified or revised to meet the following criteria, it shall be used in lieu of preparing new data:

a. It is furnished with rights-in-data consistent with the contract stipulations regarding data rights;

b. It is furnished at a cost to the Government equal to or less than the cost of preparing new data;

c. It meets the legibility and reproducibility requirements for the TDP element of which it is to be a part;

d. It meets the design disclosure requirements of the TDP element of which it is to be a part;

e. It is identified by a Commercial and Government Entity (CAGE) Code, document number, title, and applicable contract number(s). Existing data that uses the term “Federal Supply Code for Manufacturers” or “FSCM” instead of “CAGE Code” need not be updated to reflect the term “CAGE Code”.

3.2.5 Reference Documents. Documents referenced in a TDP document shall be furnished as an integral part of the TDP. When first tier references do not provide the technical information required by the TDP, subordinate reference documents shall be provided until the design disclosure requirements are met.

Technical manuals, procedural manuals, maintenance manuals, and company drafting manuals shall not be considered as referenced documents. When information essential to meeting TDP design disclosure requirements are contained in such documents, that information shall be incorporated in a document acceptable for inclusion in the TDP.

3.2.6 Company Standards. Company standards shall not be referenced on TDP documents or form a part of the TDP, unless it is a unique process that is not covered by a U.S. nationally recognized standardization body or Government standard, and its use is approved by the Government. Use of any company standard shall be approved by NAVAIR Code AIR-6.8.5.

3.3 Legibility and Reproducibility. All documents prepared or submitted shall meet the legibility and reproducibility requirements specified in the specification or standard controlling the media in which the data is to be delivered. As a minimum, all lines, symbols, letters, and numerals shall be readable.

3.4 Document Markings, Legends, Labels, Notations, and Statements. TDP documents shall contain the markings, legends, labels, notations, and statements that follow as applicable.

3.4.1 Security Classification Markings and Notations. TDPs, or parts thereof, containing classified information shall be protected and marked in accordance with the instructions on the Contract Security Classification Specification, DD Form 254. All classified documents shall be marked as required by DoD 5220.22-M, National Industrial Security Program Operating Manual, as implemented by SECNAV M-5510.36, Department of the Navy Information Security Program.

3.4.1.1 Conspicuous Markings. Markings shall be conspicuous so that they will be noticed and recognized by the holder as separate or different from other information or material, and that they will serve to inform and warn of the special requirements necessary for protection of the information.

3.4.2 Distribution Statements. All TDP documents shall contain a Distribution Statement in accordance with DD Form 1423 (Block 9) and applicable supplements thereto. Abbreviated Distribution Statements and export control warning notices may be used only when space limitations prohibit the use of entire notices or Distribution Statements. The Distribution Statement on existing documents shall be the more restrictive of either: (1) the existing Distribution Statement on the document; or (2) the Distribution Statement required by the DD Form 1423.

a. The following statement shall be included on the deliverable and the Government reserves the right to change the Distribution Statement:

DISTRIBUTION STATEMENT D - DISTRIBUTION AUTHORIZED TO DOD AND U.S. DOD

CONTRACTORS ONLY (EXPORT CONTROL) ON (DATE OF DETERMINATION). OTHER

REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO THE COMMANDER, NAVAL AIR

SYSTEMS COMMAND (PMA205), 47123 BUSE ROAD, PATUXENT RIVER, MD 2067.0

b. The following Conditions for Foreign Use (CFFU) statement shall be presented directly below the

Distribution Statement. There shall be no header and the following exact text shall be used:

This information is furnished upon the condition that it or knowledge of its possession will not be disclosed to another nation, and that it will not be used for other than the military purpose for which it is being provided without specific authority from the U.S. Department of the Navy; that individual or corporate proprietary rights contained within, whether patented or not, will be respected; that the information will be provided the same degree of security afforded it by the U.S. Department of Defense. Regardless of any declassification markings, this information may not be downgraded or declassified by a foreign recipient without the written approval of the originating U.S. agency.

c. The following statement shall be included on the deliverable

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.

d. The following statement shall be included on the deliverable:

Destruction Notice – For Classified Documents, Follow The Procedures In DoD 5220.22-M, Industrial Security Manual, Section, 11-19 Or DoD 5200.1-R, Information Security Program Regulation, Chapter IX. For Unclassified, Limited Documents, Destroy By Any Method That Will Prevent Disclosure Of Contents Or Reconstruction Of The Document.

3.4.2.1 Drawings/models and Associated Lists. Distribution Statements shall be included on all drawings/models and associated lists. For multi-sheet drawings, hardcopy and digital, except drawings in book-form, Distribution Statements shall be included on all sheets/images. For drawings in book-form and multi-sheet associated lists, inclusion of Distribution Statements on sheet one will suffice. Marking of associated lists shall be based on the content of the list and not the classification of the drawing.

3.4.2.2 Location on Drawings/models and Associated Lists. In addition to other contractual information regarding location of Distribution Statements the following shall apply. Distribution Statements shall be located on drawings immediately above the title block. Distribution Statements shall be located on lists at the bottom of the first page, immediately above any revision history block. If space does not permit these locations, Distribution Statements are to be located in similarly prominent areas. For Product Models the markings shall be placed on an annotation plane, or equivalent. The annotation plane or equivalent, containing this information, shall be available for display with the model. Reproductions of technical data, or any portions thereof, subject to asserted restrictions, shall also reproduce the asserted restrictions.

When displayed, the security data annotation plane does not rotate with the model.

3.4.2.3 Location of Associated Notices. Export control warning notices required in association with Distribution Statements shall be located in the same general area as the Distribution Statement.

3.4.3 Restrictive Rights Legends. TDP developed under cost of this contract shall be free of restrictive rights or Government purpose rights markings. If LEM approved TDP data is used that was procured or developed with limited rights or Government purpose rights proprietary restrictions, shall be marked on applicable drawing sheets/images, models and other TDP documents with the appropriate approved legend, as prescribed in the DoD Federal Acquisition Regulation Supplement (DFARS). Restrictive rights legends shall be located in a conspicuous location on all TDP documents/images. Legends shall be located in the field of the drawing, within the margins, preferably near the title block.

3.4.4 Item Replacement Notations. When an item is replaced by another item, notations shall be placed on the drawing to identify the interchangeability status.

3.4.5 Identifying Substitute Parts. Substitutes to permit establishment of alternate sources of supply, permit production of parts by alternate methods of manufacture, or permit fabrication of items with substitute parts or materials shall be identified on the separate parts list or drawing as applicable. Substitute or alternate items and parts shall be identified on the parts list. (See paragraph 3.8.2.1 below).

3.4.6 Electrostatic Discharge Sensitive Devices (ESD) Marking. ESD symbols shall be in accordance with U.S.

nationally recognized standards and appropriately defined on the using document.

3.4.7 Digital Data Marking. Reproductions of drawings that are digitally maintained or controlled, or copies derived from data that is stored and maintained digitally, shall identify that reproduction as being reproduced from a digital master, by use of a note beneath the last entry of the revisions block area, or above the title block. Design activities may add additional information to this note to identify in-house peculiar requirements.

3.5 Identification of Contract Numbers. The Government contract number under which the TDP documents are prepared shall appear on the first sheet/image of each original. TDP documents, delivered under a Government contract other than the one under which it was prepared, shall identify both the Government contract number under which it was prepared and the contract number under which it is delivered on the first sheet/image of each document submitted.

3.5.1 Application of Contract Numbers. When TDP documents or copies thereof are to be delivered under a subsequent or other contract, cost effective techniques may be used to apply the delivery contract numbers.

3.5.2 Contract Numbers in Data Rights Legends. This Statement of Work does not alter DFARS, Part 27 requirements for identifying contractors and contract numbers in rights-in-data legends.

3.6 Contractor Identification on Documents

3.6.1 Contractor and Government Entity (CAGE) Codes. CAGE Codes are to be listed on all documents that form a part of the TDP. Only those codes identified in Federal Cataloging Handbook H4/H8 with the Type designation “A” shall be used.

3.6.2 Contractor Identification on TDP Documents. TDP documents prepared by a design activity, other than the one represented by the CAGE code assigned to the document, shall also identify on the document the preparing design activity’s CAGE code, name, and applicable contract numbers. Subcontractors preparing TDP documents shall be identified by CAGE code, name, and subcontract numbers to establish traceability to the applicable Government contract.

3.6.3 Original Equipment Manufacturer CAGE info and Part Numbers. Parts lists shall or other depictions of Original Equipment Manufacturer (OEM) cage numbers and part numbers shall not be replaced by contractor part numbers regardless of company practices. Part numbers shall identify OEM part numbers and not be replaced with contractor part numbers. If contractor is creating new part numbers for OEM equipment or modifying OEM equipment the OEM part number shall be identified and an altered item drawing be created showing the process of altering the OEM item.

3.7 Document Identification and Numbering Requirements. Each document shall have a unique document identifier that shall consist of:

a. The CAGE Code of the design activity, as the first part

b. The document identifying number, as the second part.

3.7.1 CAGE Code. The CAGE Code shall be that of the design activity whose document identifying number is assigned to the document and whose activity name and address appear on the document at the time of assignment.

3.7.2 Location. CAGE Codes shall be entered in the appropriate areas/block of TDP documents (i.e., drawings/models, associated list). Refer to ASME Y14.34 for location on drawings and associated lists.

3.7.3 Drawing Number. The drawing number shall consist of numbers or combinations of letters, numbers, and dashes. The drawing number shall be assigned from numbers controlled by the design activity whose CAGE Code is assigned to the drawing. The design activity shall maintain complete and accurate records of all drawing numbers assigned.

3.7.3.1 Drawing Number Structure. Drawing numbers shall not exceed 32 characters. List prefixes (PL, IL, DL) are not included in the 32-character limit. Characters shall be limited to numbers, letters, and dashes (-) and the following:

a. Letters “I”, “O”, “Q”, “S”, “X” and “Z” shall not be used; however, letters “S”, “X” and “Z” may be used only if they are part of the existing document numbering system. Letters shall be uppercase.

b. Numbers shall be Arabic numerals. Fractions, decimals and roman numerals shall not be used.

c. Blank spaces shall not be used.

d. The CAGE Code, document revision letter, and drawing format size letter are not considered part of the document identifying number.

3.7.3.2 Drawing Identification. The original design activity CAGE Code and the drawing number shall establish unique drawing identification.

a. New Engineering Drawings and Associated Lists. New drawings shall be assigned a CAGE Code, drawing number, and if applicable, a suffix identifier.

1) The CAGE Code for new drawings and associated lists shall be that of the design activity.

2) The CAGE Code and drawing number shall be located in accordance with ASME Y14.100.

3) Associated Lists shall be identified in accordance with ASME Y14.24.

4) Complete and accurate records of all drawing numbers assigned shall be maintained by the design activity and provided as part of the TDP.

b. Existing Drawings and Associated Lists. Existing drawings and associated lists which do not contain a CAGE Code, FSCM, or Code Identification shall be assigned the applicable CAGE Code.

3.8 Call-out of or Reference to Items and Documents. Call-out of or reference to items and documents shall be made in accordance with ASME Y14.24 and ASME Y14.34.

3.8.1 CAGE Code as a Prefix. Documents called out or referenced in the TDP shall be preceded by the CAGE Code of the original design activity except:

a. When the CAGE Code for the item identified or document being referenced is common to the code of the document on which it is listed or referenced; or

b. When the CAGE Code is shown in the parts list, it may be omitted from the part call-out on the face of the drawing.

3.8.2 Call-out of or Reference to Items. Call-out of or reference to items shall be consistent throughout any given drawing/model.

3.8.2.1 Substitute or Alternate Item Identification. An item identified as a substitute or alternate shall be assigned the same find number as the item for which the standard document number may be substituted.

3.8.3 Call-out of or Reference to Documents. Call-out of or reference to documents shall be made by the document’s unique identifying number and CAGE Code.

3.8.3.1 Unique Document Identifier. All documents, other than Government or non- Government standardization documents, called out or referenced on any TDP document shall have a unique document identifier. The design activity is responsible for assigning or obtaining document numbers and CAGE Code for documents used with drawings.

3.8.3.2 Symbols. Symbols other than numbers, letters, and dashes are permitted when referencing existing Government or non-Government standardization documents that use such symbols in the document identifying number.

3.8.3.3 Technical Orders, Pamphlets, and Recordings. Technical orders, pamphlets, and recordings are not considered reference documents, and shall not be referenced on engineering drawings without Government design or procuring activity approval.

3.9 Identification of Materials, Processes, and Protective Treatment. Materials, processes, and protective treatment necessary to meet the design requirements of an item shall be identified in accordance with

ASME Y14.24.

3.10 Other Identification. All parts, materials, processes, and protective treatments used shall be adequately identified to support the requirement of this SOW and the contract.

3.10.1 Bulk Item Identification. Bulk items shall be identified by a discrete identifier in accordance with the item identification requirements and where practicable, the quantity or measurement of material shall be included.

3.11 Associated Lists. Associated lists shall be in accordance with ASME Y14.34 and the additional requirements set forth in Appendix C.

3.12 Referring to Reference Documents. Reference to documents for the purpose of specifying requirements or drawing interpretation shall be specific. Identifiers for identification of specific issues, such as revision level or year of issue, shall be included when referring to reference documents in cases where use of a specific issue is essential for item requirements or drawing interpretation.

3.13 Language. Only U.S. English language shall be used.

3.14 Units of Measure. The measurement system in which the item is designed shall be used in the TDP.

3.15 Symbols and Abbreviations. Reference to the applicable explanatory document shall be made on each document in which a symbol or abbreviation is used.

3.16 Types and Quantity of Drawing Selections. The design activity shall select the number and types of drawings prepared in accordance with ASME Y14.24, as necessary to meet the TDP requirements of this contract.

3.17 Drawing Titles. The drawing title shall be an approved item name form those names listed in Cataloging Handbook H6, Federal Item Name Directory for Supply Cataloging. No word(s), symbols(s), nor any of their possible combination which would disclose information in any of the established security categories shall be used in drawing titles.

4.0 Digital Data Delivery (Interim and Final). Digital data shall be delivered, as updates require for interim delivery for Technical Documentation in-process reviews (TDIPRs) 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 draft and final deliveries shall have one drawing sheet per filename (for drawing deliverables only). The exceptions to this would be when the drawing digital data represent a word processing or PDF document, or the native files are created using a CAD program that allows for the file format to store multiple sheets. In such exception cases, the word processing and PDF documents shall be delivered having all sheets in one word processing or PDF file for each unique document or drawing number. These multiple sheet documents would be listed once per unique filename in the metadata spreadsheet. The native CAD file shall contain multiple sheets for a drawing as a deliverable. The native CAD files shall also have their unique filenames listed in the metadata spreadsheet. The neutral files in such exception cases for the CAD format deliveries should be saved according to one sheet per filename whenever the neutral format cannot allow for multiple sheets in the same file and these unique filenames shall also be listed in the metadata spreadsheet.

b. 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 5, and shall conform to the DD Form 1423.

c. 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’s entities.

d. File layer or level conventions as stated in paragraph 6d, which are used, shall be identified for all data residing in the digital data file.

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

f. Revisions made to the digital database 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.

g. Files shall be delivered in separate subdirectories by product definition data type (such as native, neutral, drawings, documents, etc.) to simplify processing.

h. Hardcopies will be delivered on 11X17 paper in 3-ring binders. Binders shall not be larger than 2.5 inches.

i. 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 media which support a hierarchical data file structure may be used by mutual written agreement between the contractor, contracting officer, and the Logistics/Data Management Specialist.

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

k. Media Markings: All physical disk media shall be marked with the following information below.

1) Prime Contractor Name/CAGE

2) Contract number

3) System

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, and data rights statements and codes shall reflect the highest restriction of any of the data contained on the delivery media.

l. Summary Report File: The contractor shall supply a Summary Report file in digital ASCII text or Adobe Portable Document Format (PDF) format 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, i.e. .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):

i. Type Quantity

ii. Total Number of Files Delivered: 1200

iii. Number of Native DWG Files: 400

iv. Number of DXF Files: 400

v. Number of HPGL Files: 400

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, as necessary, of field headings/data titles 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 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).

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

5.0 CAD/CAM Product Definition Data. CAD/CAM Product Definition Data is grouped in four basic categories below. Definitions and delivery formats are as follows:

a. Word Processor and Supporting Logistics Documents, see paragraph 5.1;

b. Engineering Drawings (VECTOR), see paragraph 5.2;

c. PDF Notes, see paragraph 5.3;

d. CAD Models, Tubing, Mold, and Loft Data see paragraph 5.4;

e. CAD Models, Tubing, Mold, and Loft Data, see paragraph 5.5.

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 MS Windows-based PKZIP (version 2.5 or subsequent to handle long filenames) 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 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 has the same file extension and delivered as a single file per sheet.

5.1 Word Processor and Supporting Logistics Documents: Would consist of 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 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 file shall have the spreadsheet fields populated in the metadata spreadsheet by having the sheet number as “1” and total number of sheets equal to the total number of sheets in the single PDF or Word file. 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 (as practical), rather than scanned images, image plus text, or image-only documents. The actual sheet count for Word documents may be different when viewed on various computers due to the default printer; therefore, the total sheet count in the spreadsheet shall be that of the original authored document as shown in the title block.

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) (version 3.0 or later) or MS Word RTF

5.2 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. In other words, a D-size drawing 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 Y14.1. 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.

5.3 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 should be separated into their own separate PDF file and not included in the drawing PDF file.

Delivery Formats: Native CAD – Any format native to the contractor’s CAD system is acceptable, e.g.

AutoCAD®;

AND

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:

Continuous Acquisition & Lifecycle Support (CALS) Type I, CCITT Group 4 (MIL-PRF-28002) or TIFF Group 3 or 4.

5.4 CAD Models, Tubing, Mold, and Loft Data: 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.

a. 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, shall not have the model information visible when the drawing is viewed or printed.

Similarly, any delivered model files shall not have the drawing data visible when the model is viewed or printed. Digital models that have not been previously delivered by the contractor to the latest version of the current CAD software used to develop the model data or digital models shall be updated by the contractor to the latest version of the current CAD software used to develop the model data for the duration of this contract.

b. Objects or other model data that are not pertinent to the drawing and especially those located outside the drawing borders need to be removed, hidden, or located to an area inside the borders and hidden where they will not interfere with the drawing data.

5.3.1 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: The following are requirements for the creation of 2-D drawings, 2-D or 3-D tubing and mold data, and 2- D and 3-D geometric models, to facilitate the IGES or STEP-based translation of 2-D and 3-D geometry with minimal loss and distortion of data:

a. AutoCAD drawings that contain blocks or block definitions shall be saved using the WBLOCK command. The WBLOCK command shall not be used with AutoCAD Modeling Extension (AME) models.

b. When creating 2-D and 3-D geometry, use only the standard colors specified whenever possible according the colors that are basic to the originating CAD program. Do not use black as the color of any geometric entity. Black color could lead to visualization problems because the default background color used by other CAD systems tends to be black.

1) Avoid assigning the color white to geometric elements unless this color is the default color of the CAD system being used. Many plotters tend to not plot geometric elements with white color.

2) Do not use user-defined or add-in colors or line types beyond the basic CAD system in models and drawings. They tend to cause problems during STEP, IGES or other translations.

c. Special fonts shall not be used. Only the basic font library included with the original CAD software shall be used. Company logos requiring special fonts shall have those redrawn using basic shapes.

Delivered data shall not have embedded raster images or fonts in the native digital data. Delivered data shall also not contain proprietary or copyrighted alphanumeric fonts.

d. Special fonts used in the creation of drawings that are proprietary or copyrighted shall not be used.

This is to enable correct and accurate viewing of the native CAD system drawing and to insure a more complete translation of the original format and details of all delivered drawings. Whenever possible, use the CAD program’s basic fonts in the creation of drawings. If special fonts are used for the creation of CAD drawings, the contractor must notify the acquiring activity at time of delivery.

e. Drawings delivered as searchable PDF files shall have all sheets for the same drawing number and

CAGE code contained in the same PDF file.

f. Native digital drawings and models from CAD systems that create sub-directories as part of their normal file creation process shall be delivered as a single file using the UNIX ‘tar’ or archival ‘zip’ format in order to preserve the original directory structure.

g. The product data files shall be independent of external links or references to other software tools, drawing files, or databases. This requires that the files shall be stand-alone entities.

5.5 Electrical/Electronic CAD and CAM Product Data Files: This requirement includes product data files for:

a. Electrical/Electronic End Products [e.g., Integrated Circuit (IC) devices, Programmable Logic Devices (PLDs), electrical…