Exhibit_B_CDRL_Abrams_EDTT_3-May-16.pdf

Annex to Exhibits B

TDP OPTION SELECTION WORKSHEET

PRODUCT DRAWINGS AND ASSOCIATED LISTS

A. CONTRACT NO. B. EXHIBIT/ATTACHMENT NO. C. CLIN

D. CDRL DATA ITEM NO.

1. DELIVERABLE PRODUCT (X and complete as applicable.)

a. ORIGINALS (Specify current design activity's full size reproducible drawing or digital data file(s) on which is kept the revision record recognized as official) (Identify specification, type, grade and class, etc.)

b. REPRODUCTIONS (Identify specifications, type, grade and class, etc., and quantity of each)

X c. DIGITAL DATA (Identify specification, exchange media, etc. and specify original (master) or copy) - MASTER Product data, engineering design and manufacturing data (CAD/CAM/CAE), 3-D vecotr data, and product model data shall be delivered in a data definition format for neutral file exchange. Standard for the Exchange of Product Model Data STEP(ISO 10303) is the preferred format for Product and CAD data in those areas for which a STEP application protocol (AP) is defined. Initial Graphics Exchange Specification (IGES) in accordance with MIL- PRF-28000B or, where MIL-PRF-28000B is not applicable, ANS US PRO/IPO100 is acceptable if a STEP AP is not defined. The product data and CAD data in the native CAD formats shall also be delivered. Delivery media shall be CD-ROM in accordance with ISO 9660. See Appendix A

2. CAGE CODE AND DOCUMENT NUMBERS (X ONE)

a. CONTRACTOR

X b. GOVERNMENT Complete (1) and (2) or (3) c.

(1) Use CAGE Code

57039

(2) Use Document Numbers (3) To Be Assigned By: PEO STRI

Letter referencing Contract # must be submitted through the Government contracting officer to SFAE-STRI-PS-E (Attn: B.

Thurman ) requesting Drawing Numbers

3. DRAWING FORMATS AND DRAWING FORMS (X one and complete as applicable) x a. CONTRACTOR FORMATS. Forms to be supplied by contractor.

b. GOVERNMENT FORMATS. Forms to be supplied by contractor.

Samples supplied by (Specify)

e. GOVERNMENT FORMATS. Forms to be supplied as

Government Furnished Material by (Specify) Contractor native CAD format is acceptable provided it meets the requirements of ASME Y14.1-1995.

Signature blocks must comply with paragrapg 6 of ASME Y14.1-1995 with block G used for the governmant release authority. Names shall be printed on drawing forms but no signatures should appear. Release authority shall be U.S. Government and name shall be requested from contracting officer.

The contractor shall provide a list of applicable drawings for the project and release authority signature at the time of PEO STRI acceptance of the product baseline.

4. TYPES OF DRAWINGS SELECTION (X one) X a. CONTRACTOR SELECTS b. GOVERNMENT

5. ASSOCIATED LISTS (X and complete as applicable) X a. PARTS LISTS (X one) X (1) lnteqral X (2) Separate See Appendix A

b. DATA LISTS (X one) X (1) Not Required (2) Required (Specify levels of assembly)

c. INDEX LISTS (X one) X (1) Not Required (2) Required (Specify levels of assembly)

X d. WIRING LISTS (X one) (1) Not Required X (2) Required (Specify levels of assembly) Wiring lists shall be provided when assemblies require interconnection See Appendix A

X e. INDENTURED DATA LISTS (X one)

(1) Not Required X (2) Required (Specify levels of assembly) See Appendix A

X f. APPLICATION LISTS (X one) (1) Not Required X (2) Required (Specify levels of assembly) Application data shall be displayed on individual drawings. When a part or assembly has multiple uses at the next level, the application block on the drawing shall specify "multiple usage" or a comparable statement.

6. DETAILS (X one) X a. MULTIDETAIL DRAWINGS PERMITTED Shall be IAW ASME

Y14.24-1999

b. MONODETAIL DRAWINGS MANDATORY

7. VENDOR SUBSTANTIATION DATA (X one) X a. NOT REQUIRED b. REQUIRED

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

X a. ASMEY14.100, ENGINEERING

DRAWING

PRACTICES

(COMMERCIAL)

See Appendix B

B. X b. ASME Y14.100, WITH APPENDICES

B, C, D, E

X c. ASME Y14.34M

ASSOCIATED LISTS

d. EXISTING STANDARDS

DO NOT APPLY

C. X

D. X

E. X

9. OTHER TAILORING (Attach additional sheets as necessary) See Appendix B, and C for Other Tailoring

APPENDIX A

This Appendix provides supplemental information for the TDP Option Selection Worksheet for Product Drawings and Associated Lists

Block 1.c.: Electronic on-line access to a FTP web site for reviewing the digital data generated or retained by the current design activity data is required. The term “current design activity” is defined as “The design activity currently responsible for the design of an item. This may be the original design activity or a design activity to which the design responsibility has been transferred.” Two dimensional (2D) drawings shall be derived from three dimensional (3D) solid models, if utilized, using a Computer-Aided Design (CAD) system compatible with Autodesk Inventor 7 capabilities. Two and three dimensional product data including models, drawings, schematics, illustrations and Computer Aided Design (CAD), Computer Aided Manufacturing (CAM), and computer Aided Engineering (CAE) product data shall be delivered in both

• The native CAD format

And also

• A data definition format for neutral file exchange in accordance with either Standard for the Exchange of Product Model Data (STEP), ISO 10303, or Initial Graphics Exchange Specification (IGES), in accordance with MIL- PRF-28000 DFX is a suitable neutral file/substitute for IGES.

Two dimensional drawings, illustrations and schematics shall be delivered in accordance with STEP AP 201 (Explicit Draughting) or AP 202 (associative Draughting) or MIL- PRF-28000, Class II.

All two dimensional drawings, illustrations and schematics shall be delivered with complete and accurate indexing data. Indexing data are identifiers and attributes that allow the receiver of the images to associate each with complete documents, and to associate documents with one another and with the correct material item.

Access to a contractor FTP site shall be provided, for the capture and review of digital data. Solid models and drawings shall be released to and retained in digital format in an Integrated Development Environment (IDE). Electronic drawing files, whether created by the prime contractor, a subcontractor or a vendor, shall be entered into the IDE database in conjunction with the initial preparation.

Existing drawings that are compatible with requirements defined herein, or those that define Commercial-Off-The-Shelf items or existing drawing in paper media that are not changed or altered, or paper drawings with "Red Lines" incorporated (as long as the "Red Lines" are readable), may be electronically scanned and released without modification.

The 2D drawing representations for arrangement drawings and installation sequence drawings may be electronically scanned and released into the FTP as Portable Document Format (PDF) files.

Block 2.c (1): The following CAGE Code, 57039, will be incorporated in all NEW or electronically modified drawings.

Block 2.c (3): The Government will provide all drawing numbers for this program. No prefixes or suffixes will be added to the Government numbers.

Block 3.a: Drawing format templates residing in the Prime Contractors CAD database shall be used for creating 2D drawings. Autodesk Inventor 7 drawing templates shall be accessed via the FTP site database and electronic copies shall be made available to subcontractors and vendors upon request.

Block 4.a: The design activity shall select the types of drawings to be prepared using the following sections of ASME Y14.24-1999. As a minimum, these types of drawings shall be prepared based on contractor’s standard drawing practices.

ASME Y14.24-1999 Section/Title:

3 Detail Drawings (fully assembled product representation) 4 Assembly Drawings (sequence or end item representation 5 Installation Drawings (assembly sequence representation) 6 Modifying Drawings (Altered Item Drawing) 7 Arrangement Drawings (top level end item Product drawings) 8 Control Drawings 9 Interface Drawing 11 Mechanical Schematic Diagrams 12 Electrical/Electronic Diagrams 13 Special Application Drawings

Block 5.a.: Parts lists may be integral or separate. Parts Lists may be presented in a MS EXEL format. ASME Y14.34M-1996, Section 5, shall be used for the preparation of parts lists.

Block 5.d: Wiring lists shall be provided when assemblies require interconnection. Wire Lists may be presented in a MS EXEL format. ASME Y14.24M-1996, paragraph 10, shall be used to establish the requirements for the preparation of wiring lists.

Block 5.e: Data stored on the FTP shall be utilized to create an indented data list for each simulator type and serialized top level end item.

Block 5.f: Application data shall be displayed on individual drawings as a “Next Higher Assembly" table in the drawing title block. When a part or assembly has multiple uses at the next level, the application block on the drawing shall specify “multiple usage” or a comparable statement.

Appendix B

ASME Y14.100-2000

TAILORING CHECKLIST

A. Drawing Media (Choose all that apply)

(1) Non-digital (Specify)

(2) Digital Data ((Specify) FTP

(3) Other (Specify) If hardcopy is all that is available, then scan in the hardcopy to a PDF format, if hardcopy has "Red Lines" they must be readable after scanning or redrawn as a CAD drawing

B. Drawing Format (Choose One)

(1) Contractor

(2) Government (forms supplied by the Government) Digital Paper

(3) Government (forms supplied by the Contractor)

C. Drawing Sheet Size and Format (Choose One)

(1) ASME Y14.1

(2) ASME Y14.1M

D. Application Data (Choose all that apply)

(1) Contractor Option

(2) Required

(a) On Drawing

(b) By Reference (Specify) Drawings shall have an application block listing the drawing number of the next higher assembly in the "Next Assembly" column and the nomenclature or equivalent designator of the asembled units(s), which the drawing applies in the "used on" column.

(c) Contractor Option

(3) General Use or multi-use notations

(a) Allowed

(b) Not Allowed

E. Drawing Detail (ASME Y14.24) (Choose all that apply)

(1) Mono-detail

(2) Multi-detail

(3) Tabulated

F. Dimensioning and Tolerancing (Choose all that apply)

(1) Metric

(2) Decimal-inch

(3) Application of ASME Y14.5M

(a) Specific Issue (revision) required (Specify Issue) 1994

(b) Issue in effect (Specify Issue)

G. Drawing Notes (Choose One)

(1) On Drawing

X

(2) By Reference (Specify)

(3) Contractors Option

H. Types of Drawings (ASME Y14.24) (Choose One)

(1) Contractor Selects

(2) Government Selects

I. Maintenance of Multi-sheet Drawings (ASME Y14.35M) (Choose all that apply)

(1) Drawing Revision Level (DOD Preferred)

(2) All sheets same revision level

(3) Sheet revision level

J. Redrawn Drawings (redrawing without change) (ASME Y14.35M) (Choose One)

(1) Advance revision level

(2) Revision level is not advanced

K. Maintenance of Revision History (Choose all that apply)

(1) Contractor option

(2) Optional methods

(a) Remove one or more revision record as required

(b) Remove all previous revision history

(c) Remove all revision history but retain line entry for revision authorization and date of revision

(d) Remove all except revision preceding current

(e) Maintain revision history in its entirety

L. Adding Sheets (ASME Y14.35M) (Choose all that apply)

(a) Renumber sheets using consecutive whole numbers

(b) Number added sheets in decimal-number sequence

(c) Number added sheets in alpha-numeric sequence

M. Deleting Sheets (ASME Y14.35M) (Choose all that apply)

(a) Renumber all affected remaining sheets

(b) Affected remaining sheets not renumbered (revision status block annotated;

CANC or DEL)

N. Markings on Engineering Drawings (Choose One)

(1) Special items and processes apply

(a) Applicable symbols (Specify)

(b) Applicable special notes (Specify) See ASME Y14.100-2000 Appendix E, Paragraph E6 and E7

(2) Special Items and processes do not apply

O. Associated Lists (ASME Y14.34M) (Choose all that apply)

(1) Non-digital (Specify)

(2) Digital Data (Specify) Micro-Soft Office 2003 Compatatible

(3) Other (Specify) If hardcopy is all that is available, then scan in the hardcopy to a

PDF format. If hardcopy has "Red Lines” they must be readable after scanning or reentered.

P. Types of Associated Lists (ASME Y14.34M) (Choose all that apply)

(1) Parts List

(a) Integral

(b) Separate

(c) Contractors Option

(2) Application List

(3) Data Lists

(4) Index Lists

(5) Indentured Data List

(6) Wire List

(7) Other (Specify) MS Office 2003

Q. Angle of Projection (ASME Y14.3M) (Choose One)

(1) 3rd Angle (US preferred)

(2) 1st Angle

R. Language (Choose One)

(1) English Required

(2) Other (Specify)

S. Applicability of Appendices (ASME Y14.100-2000)

(1) Appendix B

(a) As detailed herein

(b) As modified by (Specify) See Appendix A and C

(2) Appendix C

(b) As modified by (Specify)

(3) Appendix D

(4) Appendix E

Appendix C

Digital Data Description Requirement

1. Digital Data Delivery (Sample): You shall submit four (4) representative samples of each digital data format to be submitted as early as possible. These samples will be used for verification of procedures and processing into a life cycle data repository. Each supplier shall also submit the required representative samples. The representative samples shall include data in the appropriate digital formats (native, neutral, and legacy data where applicable). The representative samples shall identify the computer system (including operating system with its version), computer software application used to archive the data and version used, respectively, of the system originating the data on the media label. The supplier shall also submit a digital sample of the Metadata Spreadsheet representative of the sample files delivered in the format described in paragraph 5 of this Appendix. See Table 1 for acceptable media.

a. For IGES/DXF, a copy of the processing/error log file created during the generation of the sample IGES/DXF files shall also be submitted in digital form.

b. Sample files shall be accompanied by a technical point of contact (POC) (name, phone number, FAX number, and e-mail address if available) stated in an ASCII text file, preferably on a CD-ROM for sample data only. This will enable any problem which may be evident in the sample delivery to be resolved in a timely manner prior to final digital data delivery.

c. Sample drawings file will contain one drawing. For multiple sheet drawings, each sheet will be on a separate tab within the drawing file.

2. Digital Data Delivery (Final): Digital data shall be delivered, in accordance with the continuation sheet to the DD Form 1423 and as follows:

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

b. All pertinent entities that comprise the final digital file should be viewable upon opening of the digital data files. If they cannot be viewable without the user being required to change layers or levels, then file layer or level conventions shall be identified for all data residing in the digital data file. The user should not have to search for layers which should be turned on or off in order to view the final drawing’s entities.

c. File layer or level conventions which are used, shall be identified for all data residing in the digital data file.

d. Revisions made to the digital data base 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.

e. Raster images, such as TIF, GIF, JPEG, and Bitmap may be imported or pasted into a CAD generated vector drawing format to support installation drawings. Raster images, such as TIF, GIF, JPEG and Bitmap of drawings shall not be imported or pasted into a CAD generated vector drawing to present fabrication or dimensioned drawings or associated lists.

f. Files shall be stored in separate subdirectories by product definition data type (such as native document, neutral document, native drawings, etc) to enhance processing.

g. Delivery Media Requirements: Media requirements (physical and file copy format) of the following types are listed in order of preference for delivery of digital data. In order to take advantage of the latest in digital media technology, other media not listed shall be approved by the requiring office identified in block 6 of the DD Form 1423. See Table 1 for acceptable media and other pertinent information:

TABLE 1

ACCEPTABLE MEDIA FOR DELIVERABLES (Sample & Final)

Type Acceptable

Format Max

Length Max Size Max Speed Requirements**

CD+/-ROM* ISO 9660 80 minute 700 Megabyte 52X Multi speed DVD+/-ROM* UDF 120 minutes 4.7 Gigabyte 16X Multi speed Portable Hard Drive NTFS 3 TB USB 3.0 USB cord Internet connection ftp 20 MB or smaller per data set.

Internet connection WEB accessible Direct connection

* Paper labels shall not be used on CD-ROMs ** Files delivered must be uncompressed unless also delivered with decompression software.

NOTES:

1. “ISO 9660” and Universal Disk Format (UDF) are the preferred options. Files and directories recorded to DVD/CD based on the ISO 9660 or UDF standards must meet the following (8+3) requirements: A file name may not contain more than eight alphanumeric characters and the underscore symbol “_”. A file name extension may not contain more than three alphanumeric characters. A directory name may not contain more than eight alphanumeric characters and the underscore symbol “_”. The CD/DVDs shall be recorded using mode one, level one, and single session media.

2. “Joliet” is an alternate acceptable format option. Joliet formatting allows for filename length greater than the (8+3) format. The maximum filename length shall not exceed 24, including periods or other special characters. [Joliet also records the associated MSDOS-standard name (8+3 characters) for each file so that the CD/DVD may be read on

MSDOS systems, Windows, or earlier versions of Windows.] The CD/DVDs shall be recorded using mode one, single session media.

i. Physical media shall be labeled with the following information:

(1) Prime Contractor Name/CAGE

(2) Contract number

(3) System

(4) The physical media (CD, disk, etc.) shall be numbered sequentially (i.e., "Disk 2 of 3"), regardless of the type of media.

(5) Range of document numbers included on the disk.

(6) For CDs, list the archiving method used to create the CD (ISO 9660/Joliet).

(7) The appropriate Distribution Statement and Export Control Notice shall be listed in accordance with the DD Form 1423.

j. README.TXT File: On a separate 3-1/2 inch floppy disk, formatted via MSDOS or Windows, the contractor shall supply a README.TXT file in ASCII text format.

This file shall include:

(1) The name and version of the software utilized in creation of the native files included in the delivery.

(2) The type and number of files included in the delivery. For example, a statement similar to the following might be used:

Total Number of Files Delivered: 1200 Number of Native AutoCAD 2002 Files: 400 Number of IGES Files: 400

(The IGES files delivered are representative neutral files of the native AutoCAD 2002 files.)

(3) The name, phone number, and e-mail address of the contractor's 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 (i.e., 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) Each disk or CD/DVD must be scanned for virus.

3. Legacy Data:

a. Drawings/Documents which were developed in a non-electronic format (i.e., manual drafting board or scanned) and have not been previously delivered to the government, shall be delivered in digital form in an industry standard format, such as TIFF (CCITT) Group 3 or 4, or using MIL-STD-1840C or later format.

NOTE: Some raster image viewers do not always recognize the correct polarity of a black and white TIFF image. Because of this fact, in order for the government to receive the correct polarity files, some sample legacy files should be saved (by the contractor) both negative and positive polarity before delivery to the government in order to compare file sizes. The smaller file size (for black and white TIFF images) for each test file saved indicates a white background with black data information, which is the correct positive polarity needed by the government.

b. Electrical/Electronic Product Related Drawings produced on stable based drawing media (such as undimensioned, master pattern, etc) shall be digitized into a Gerber file format (RS-274 or Extended Gerber RS-274X) for purposes identified in the Machine Control Data section (paragraph 6d, Machine Control Data). The RS-274X format, if used, shall be in compliance with the current version of the 'Gerber RS-274X Format User's Guide' (Part # 414-100-014 Rev D or later revision) by Gerber Systems Corp and shall not contain data that would restrict its usage as a neutral file for laser photoplotters.

c. The resulting files shall be quality checked for compliance with the design requirements specified in the product definition data, which includes the stable based drawings. This will ensure that the integrity of the design is maintained after the digitization process. (If the capability to digitize does not exist, the undimensioned and master pattern drawings shall be delivered on stable based media ( Mylar® per IPC-D- 275).

d. The Gerber images shall contain the following note (at a location where it will not interfere with the artwork layer images):

“THIS GERBER IMAGE WAS PRODUCED BY DIGITIZING AN IMAGE FROM

STABLE BASED MEDIA.”

e. Stable based drawings of non-performance related information such as decals/labels may be exempt from the Gerber format requirement and an acceptable substitute (i.e., TIFF) may be used.

4. Product Definition Data: Product Definition Data is grouped in five basic categories. Definitions and delivery formats are as follows:

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 model files shall include design data such as schematics, 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. MS-Windows based PKZIP (version 8.0 or subsequent to handle long filenames) or UNIX’s TAR command is the preferred encapsulation method. If a preferred method is not used, an alternate method must be approved by the contracting officer before data delivery.

a. Word Processor Documents: Documents created on a word processor can be delivered and interpreted on the majority of word processing systems including those widely used in the DoD, such as Microsoft Word® (preferable), and WordPerfect®.

Software other than these require prior approval by the contracting officer. Test Methods and Procedures, Associated Lists, Acceptance Testing Criteria, Configuration Item Specs, and Engineering Analysis results are examples of these documents. Illustrations and graphics shall not be delivered inside of a word processing, desktop publishing, or spreadsheet formatted document unless a single copy of the program(s) used to produce the embedded objects is (are) provided to the government as a part of the cost of providing a particular digital data package. Figures containing images such as a simple flow chart depicting a test set layout are acceptable, however illustrations/graphics shall be referenced within the document for traceability and shall be delivered along with the documents. Documents delivered shall have the page size set to be the standard 8-1/2 by 11 inch or equivalent “A” drawing size. NOTE: Government CAGE code deliverables shall be delivered in Microsoft Word®.

Word processing documents shall have one filename to cover all sheets for each document number submitted.

Delivery Format: Native Document - MS-Word® or WordPerfect®

AND

Neutral Format – RTF ASCII text or Portable Document Format

(PDF)

b. Engineering Drawings (VECTOR): Drawings shall be delivered that are made from presentations describing a particular physical/logical entity or process using 2-dimensional geometry and textual information for both electrical/electronic and mechanical items. These drawings may also be created from view plane projections of a 3-D model, but parametric-based systems may be used to facilitate semi-automatic creation of engineering drawings from the 3-D database. The requirements set forth in paragraph 4c, Mechanical Engineering Models, sub-paragraphs (1) through (3) of the Geometry Creation Requirements for 3-D Models shall apply. Drawings delivered that are cage code 57039 shall not contain any grouped text attributes and all entities shall be present on layer zero.

NOTE: Government CAGE code deliverables shall be delivered in native CAD and neutral format.

Delivery Format: Native CAD - any format native to the contractor’s CAD system is acceptable, e.g. Catia®, or AutoCAD® (preferred), or Intergraph®, or Cadkey®, or Solidworks, or Pro/ENGINEER®, or SDRC I-DEAS®, or Mentor Graphics® and others.

AND

Neutral - American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher (DXF is a suitable neutral file/substitute for IGES) or Product Data Exchange using STEP (PDES)/Standard for the Exchange of Product model data per ISO 10303 Application Protocols (APs) 201 through 210 and 232.

AutoCAD Systems and non-AutoCAD Systems Requirements:

(1) Do not mix paper and model space entities within the same drawing file.

(2) Special fonts used in the creation of drawings that are not part of the normal CAD system basic package and that are not proprietary or copyrighted shall be delivered with the digital data delivery. This is to enable the correct native CAD system viewing and a more complete translation of the original format and details of all delivered drawings.

(3) Digital drawings that are delivered shall have one drawing sheet per filename.

This means that each drawing file will contain one drawing. For multiple sheet drawings, each sheet will be on a separate tab within the drawing file. Word processing documents of engineering drawings delivered in raster graphics formats shall have each page saved as a unique filename.

(4) Digital drawings 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’ format in order to preserve the original directory structure. A zip utility may be used for PC-based systems as long as options are employed to ensure integrity of the directory structure.

(5) Plot files created from other CAD systems shall use the same settings as the native files (not from converted IGES files). Drawings created on a CAD system larger or smaller than a ratio of 1:1 when compared to standard drawing sizes (such as C size at 17” x 22”), shall be scaled to the standard drawing sizes (when measured across its length and width) whenever plot files are to be produced for delivery to the government.

(6) J-sized drawings (34" x 55"-176") shall have multiple plot files made with a minimum of a 10" inch overlap by choosing appropriate window option settings using E size dimensions (34" x 44"). The multiple plot files shall be listed with multiple frame numbers in the spreadsheet data in a separate column. Any other size drawings larger than E size (for example, K size, 40" x 55"-143") must have multiple E size plots created similarly to a J size drawing.

c. Mechanical Engineering Models: Geometric representation of a physical detailed part, assembly, loft surface, or system in 3-dimensions created using CAD tools.

Engineering models are used as a basis for Numerical Control (NC) Machining, Engineering Analysis, etc. Digital models that do contain 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. See Geometry Creation Requirements for 3D Models below:

Delivery Format: Native CAD - any format native to the contractor’s CAD system is acceptable, e.g. Catia®, or AutoCAD® (preferred), or Intergraph®, or Cadkey®, or Solidworks, or Pro/ENGINEER®, or SDRC I-DEAS®, and others

Neutral – IGES, Version 5.0 or higher (DXF is a suitable neutral file substitute for IGES) or PDES/STEP per ISO 10303, Application Protocols (APs) 201 through 210 and 232.

Geometry Creation Requirements for 2-D Drawings and 3-D Models

The following are requirements for the creation of both 2-D drawings and fully 3-D geometric models, to facilitate the IGES-based translation of 2-D and 3-D geometry with minimal loss and distortion of data:

(1) AutoCAD drawings that contain blocks or block definitions shall be saved using the WBLOCK command. The WBLOCK command should not be used with AME models unless they are converted from R12 to AutoCAD R14 or 2002 editable solids.

(2) When creating 2-D and 3-D geometry, use only the standard colors specified whenever possible according to the IGES standard. 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.

(a) 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.

(b) The following colors are acceptable: Red, Green, Blue, Yellow, Magenta, and Cyan. Do not use user defined colors in the creation of geometric models and 2-D drawings. (They tend to cause problems during IGES-based transfer.)

(3) When creating 3-D geometry, use only the simple, fixed text fonts for the purpose of textual annotation. Note that we are talking about annotations of 3-D geometry and NOT an engineering drawing, or electronic schematic. If special fonts are to be used in 2-D drawings, limit their use to simple, easily readable fonts and provide these fonts (which are not copyrighted) along with the drawings.

(a) The objective is to convert all textual annotations in a 3-D model to IGES element 212. Use only the following font numbers for element 212: 1 and/or 2.

(b) Please refer to CAD system documentation for the various text fonts native to CAD systems that translate to IGES font numbers 1 and 2.

(4) When creating 2-D and 3-D geometry, use the standard line fonts specified by IGES. They are: SOLID, DASHED, CENTER, PHANTOM, and DOTTED.

(a) User-defined line fonts tend to cause problems during IGES-based data transfer. They shall not be used. Do not use proprietary or copyrighted alphanumeric fonts.

(5) When creating the IGES file for a 3-D geometric model, view information shall not be used. View information is irrelevant for a fully 3-D geometric model. Once the model is available in any CAD system, the internal capabilities of the CAD system will be used to orient the model in any given direction. The objective of this recommendation is to avoid the presence of independent view elements (#410) in the IGES file. If independent view information is present, they are inconsistently interpreted by the various CAD systems.

(6) If the CAD system you are using allows you to choose the algebraic type of the spline curve/surface, choose the Non Uniform Rational B-Spline Surface (NURBS) representation over the PARAMETRIC SPLINE curves.

(7) Be aware of the various surface creation operations in your CAD system that lead to indirect surfaces. A typical example is the surface trimming operation. As a general rule, avoid the creation of indirect surfaces (use of those operations that lead to indirect surfaces) whenever possible.

(a) There will be plenty of situations when indirect surfaces cannot be avoided. If your IGES processor can choose between trimmed surfaces (#144) and bounded surfaces (#143), choose trimmed surfaces instead of bounded surfaces. At the present time, CAD systems that can process indirect surfaces tend to support trimmed surfaces.

(8) When creating complex surfaces, exercise care not to develop non-simply (with internal holes) connected or multiple-connected (with multiple internal holes) surfaces.

Such surfaces tend to have one or more internal boundary curves and tend to cause precision problems during IGES based transfer.

(a) If possible, model non-simply connected surfaces as adjacent, multiple, simply connected surfaces. Keep the geometry and topology simple.

(b) If possible, breakup a multiply connected surface into multiple simply connected surfaces.

(9) The part geometry stored inside a CAD model should be self-contained. It shall not have references or pointers to entities outside of the data base. If you have to use geometry from outside the data base (a library of standard bolts for example), physically transfer the geometry to the data base. Do not use the reference approach. Instantiate the geometry in the data base. These requirements are not intended to recommend that the developer not use libraries internally, but instead recommend delivery of self-contained models to the Government.

(10) Disregard the above requirements dealing with lines and surfaces when solid modeling, or parametric (feature-based) modeling is used to create 3-D geometry. Use these requirements only as appropriate and applicable.

d. Machine Control Data: Instruction statements to drive numerically controlled machine tools such as tube benders, milling machines, drilling machines, parts/devices insertion machines, photoplotters, lathes, etc. These files shall be post processed into machine specific instructions and represented using standards as follows (See paragraph 7 for detailed requirements for Printed Board Artwork Master and Drill Data Files.):

Delivery Format: Native Machine Language - Cincinnati Milicron®, or Teledyne Pines®, or Eaton Leonard®, Excellon®, or others.

Neutral- Binary Cutter Locator (BCL), or Automatic Programmed Tool (APT), or Excellon®, or Gerber® (Standard RS-274 or Extended RS-274X)

e. Electrical/Electronic Design Models and Associated Files: This requirement includes product data files for electrical/electronic items, assemblies, and systems. These data files shall include source files (schematics and other design entry methodologies), compiled files, object files, design models (such as those used in logical circuit design, design simulation, and physical parts design), netlists (logical circuit and physical item designs), component placement and connectivity (conductor routing), physical layouts, programmable logic devices (PLDs) programming data, simulation files, test files, geometries (such as printed board description), and other product data files. (Note: See above paragraphs 4.a and b. for separate document and drawing requirements for the product definition data and paragraph 4 Note for the fileset encapsulation requirement.)

Delivery Format: Native files - Native CAD e.g., Cadence®, Mentor Graphics®, Racal-Redac®, Intergraph®, ABEL®, CUPL®, VERIBEST®, Viewlogic®, or others.

Neutral - e.g., Electronic Design Interchange Format (EDIF), IPC- D-35x Series (D350, D356, etc.), VHDL (VHSIC Hardware Description Language) (IEEE Std 1 076), IGES version 5.0 or 0higher (DXF is a suitable neutral file substitute for IGES) MIL- D-28000 (Class III), GDS II® Stream, Berkeley’s OPEN-PLA® (Programmable Logic Array), JEDEC Standard (EIA JESD3), State Diagrams, Berkeley’s SPICE®, STEP (STandard for the Exchange of Product model data) (ISO 10303), etc

5. Metadata Spreadsheet: A spreadsheet table structure that covers only the data to be delivered is required for each delivery. The Metadata Spreadsheet shall be delivered in Microsoft Excel digital format. If the Metadata Spreadsheet cannot be delivered using Microsoft Excel, the following may be substituted upon approval from the requesting office, identified in block 6 of the DD Form 1423. Native format or ASCII. NOTE:

The header information from this spreadsheet is used along with the delivered digital data files to load data into the Digital Data Repository.

Content: The Metadata Spreadsheet shall contain a listing of all engineering documentation contained in the shipment.

Structure: Each row in the spreadsheet shall represent a distinct sheet number, unless covered by the exceptions below. All fields are left justified, except Sheet Number, Number of Sheets, Frame Number of a document number, Number of Frames, Revision Letter and Accompanying Document Revision (see definitions below). The data field titles shall be included at the top of the spreadsheet on row 1only of the delivered spreadsheet. PIN and PIN revision fields shall be filled for all design model and engineering data files that do not include borders and drawing blocks. For spreadsheets delivered that exceed one thousand rows, the spreadsheet shall be divided into separate spreadsheet files on the delivered media. This division of spreadsheets should not cause the referenced documents listing or the indentured levels set listing that applies to a certain document number to be divided into separate spreadsheets.

Exception 1: For word processing documents, enter one row for each submission of the native document number delivered. The filename, document number, and all other applicable columns shall be filled.

Exception 2: For design model and engineering data files that do not include borders and drawing blocks, the sheet number is not applicable.

The fields in the spreadsheet table structure shall be entered in sequence as follows:

DATA FIELD FIXED FIELD LENGTH

Filename (including extension & special characters) 24 characters Document Title 40 characters Manufacturer (Design Activity Name) 32 characters CAGE (Current Design Activity) 05 characters Drawing Sheet Size 01 character Sheet Number 04 characters Number of sheets 04 characters Distribution Code 01 character Weapon System Model 15 characters Revision letter 02 characters Basic/Revision Date (DD-MMM-YYYY) 11 characters SW_Name 20 characters SW_Vendor Name 32 characters SW_Version 10 characters SW_Operating System 30 characters SW_Operating System Version 10 characters File_Type 20 characters File_Format (with applicable version) 32 characters Data rights 01 character Document Number 32 characters

Frame Number 04 characters Number of Frames 04 characters Control Activity 02 characters Accompanying Document Kind 02 characters Accompanying Document Number 32 characters Accompanying Document Revision 02 characters Security Level 01 character Media Number 02 characters

For Model and engineering data files that do not include drawing borders and drawing blocks, the Metadata Spreadsheet shall adhere to the following requirements. The document number and part or identifying number (PIN) shall be listed for use in indexing and traceability. These numbers shall reflect the closest document and P/N that is associated with or linked to the model or engineering data file.

Use all of the above spreadsheet data fields except for the following fields:

Sheet Number Number of Sheets Frame Number Number of Frames Accompanying Document Kind Accompanying Document Number Accompanying Document Revision

-and add the following spreadsheet data fields:

DATA FIELD FIXED FIELD LENGTH

Part or Identifying Number (PIN) 32 characters PIN Revision letter 02 characters

Definitions:

Filename - Specify a file naming convention that provides up to 20 character unique file names. File extensions of up to 3 characters are used to discriminate file types. If DOS files must be accommodated, use a file naming convention of up to only 8 characters.

List all file types to be delivered.

Document Title - Enter document title. Enter text that is the complete descriptive name or title of an item or document.

Manufacturer (Design Activity) - Enter the name of the design activity whose CAGE is assigned to the document.

CAGE - Enter the CAGE Code currently assigned to the vendor/manufacturer identified in this record. The CAGE Code is required for all contractor, subcontractor, vendor, and supplier data.

Drawing Sheet Size - Enter the character that identifies the drawing size of the document identified in this record.

Sheet Number – Enter the individual sheet number of a multiple page document or drawing. Enter the number of the sheet (right justified with leading zeros) associated with the document number identified in this record. If the total number of sheets exceeds 9999, contact the requiring office identified in block 6 of the DD Form 1423 for which calls out this requirement.

Number of Sheets - A number that identifies the total count of sheets or pages in a document. Enter the total number of sheets contained in the document identified in this record. If the total number of sheets exceeds 9999, contact the requiring office identified in block 6 of the DD Form 1423, which calls out this requirement.

Distribution Code - Enter the distribution statement code letter (A, B, C, D, E, F, or X) of the document identified in this record. This code letter in the spreadsheet corresponds with the same code letter used in the distribution statement paragraph that appears on the drawing (for each sheet number).

System Model Number - Enter if this file is unique to a weapon system model. For example, enter CCTT 71-02, AH-64 CMS 01-137, 01-144, etc., if the file applies to one of these systems. Leave blank if the file does not apply to a single designated system.

Revision Letter - The revision level assigned to a document or a specific sheet of a released document. Enter revision letter(s) applicable to the document number and specifically as applicable to each sheet number. A one-character entry will be alpha, right justified, with blank padding. For initial issue documents, the entry shall be blank.

Basic/Revision Date - The date when the document was approved for initial (original) release, or the date the revision of a document was approved. The latest date of the document (either the date of the basic approval or the date of the revision, whichever is later) shall be used. (EXAMPLE 26 MAR 2002)

SW Name - Enter the name of the native software CAD program used to generate the vector file.

SW_Vendor_Name – Enter the vendor of the native CAD software program.

SW_Version – Enter the version number and/or letters of the native software CAD program used to generate the file.

SW_Operating System - Enter the computer operating system for the CAD software.

SW_Operating System Version - Enter the version of the computer operating system for the CAD software.

File Type - Enter the appropriate file type, i.e., vector, ASCII text, raster, firmware, Gerber, etc.

File Format - Enter the specific file format with version, i.e., RS-274X, DXF r14, EDIF 400 Schematic, Intel Hex-32, etc.

Data Rights- Enter the code which identifies the rights status of the information on the document or contained in the file identified by this record. All contractor, subcontractor, vendor, and supplier data shall have the rights status entered in this data field. The rights status codes are as follows:

a. "U" signifies that the Government has unlimited rights to use the document or file so coded.

b. "L" signifies that the Government has only limited rights to use the document or file so coded or has obtained Government Purpose License Rights (GPLR) to the data.

Document Number - An alphanumeric identifier located within the drawing number block that is unique and is the primary reference for a document. Enter the document number (drawing, list, specification, etc.) identified in this record, followed by blanks. If the number is an associated document and is prefixed with alphas i.e. PL, DL, identifying the document as a specific type of associated document, the prefix shall stay intact as part of the document number and not stripped off. The same practice shall apply to any suffixes to the document identifying number by the originating organization. For models and engineering data files that do not include drawing borders and drawing blocks, the document number shall be listed for use in indexing and traceability. This number shall reflect the closest document that is associated with or linked to the model or data file.

Frame Number - Enter the number of the frame, right justified with leading zeros. Entry will be 0001 for all files, with the following exception:

Number of Frames - Enter the total number of frames required for this sheet (right justified with leading zeros). Entry will be 0001 for all files, with the exception of the scenario discussed in frame number, above. For this exception:

Control Activity - Enter the applicable code, as follows:

LOGISTICS ACTIVITY CODE

PEO STRI PT

Accompanying Document Kind - When an accompanying document is delivered, enter the appropriate code from the following table. This is a required entry if a value is contained in the Accompanying Document Number column.

Code Document AD Addendum AM Amendment AN Annex AP Appendix

AR Article AT Attachment EX Exhibit NT Notice (safety, engineering, ECPs, ECOs, etc.)

SP Specification (slash sheet or other similar types of associated specifications) SU Supplement VR Version 1N Revision Notice

Accompanying Document Number - When an accompanying document identified is delivered, as shown in the Accompanying Document Kind table above, enter the accompanying document number, followed by blanks. This is a required entry if a value is contained in the Accompanying Document Kind column.

Accompanying Document Revision - When an accompanying document identified is delivered, as shown in the Accompanying Document Kind table above, enter the accompanying document revision letter (alpha). Right justified, with blank padding.

Security Level - Enter the code that identifies the classification of the digital data according to the following:

Code Classification N Unclassified C Confidential S Secret

T Top Secret

Media Number – Enter the consecutively numbered figure that matches the label number for each media type delivered.

Part or Identifying Number (PIN) – For models and engineering data files that do not include drawing borders and drawing blocks, an alphanumeric control number assigned to identify a specific item. The PIN is an identifier assigned by the responsible design activity or by the controlling nationally recognized standard, which uniquely identifies (relative to that design activity) a specific item. The PIN generally includes the controlling drawing or document number and optional suffix. The PIN identifier shall meet the same structure requirements as those for the drawing number. The PIN does not include the drawing revision identifier, drawing size, or CAGE Code. If the file is not directly part of or an integral part of a PIN, then this number shall reflect the closest part or item that is associated with or linked to the model or data file. PINs are assigned to product data files (such as those for printed circuit board artwork and programmable logic devices (PLDs)), materials, parts, assemblies, equipment, accessories, and computer software.

PIN Revision Letter – The revision level assigned to a PIN. Enter revision letter(s) applicable to the PIN. A one-character entry will be alpha, right justified, with blank padding. For initial issue PINs, the entry shall be blank.

6. Indentured Data List (IDL): A spreadsheet table structure (separate from the metadata spreadsheet) representing the indentured level of the digital data delivery is required for each delivery. The IDL shall be delivered in Microsoft Excel format. If the IDL cannot be delivered using Microsoft Excel, native format or ASCII may be substituted upon obtaining approval from the requesting office identified in block 6 of the DD Form 1423.

Content: The IDL shall contain a listing of all engineering documentation related to the contract end item as developed, produced, and/or modified for this contract. The IDL shall include all reference documents, which are not part of the delivery, at the appropriate levels. The IDL shall include indenture levels that apply to the delivered document numbers.

Structure: All fields are left justified, except Revision Letter. The data field titles shall be included at the top of the spreadsheet on row one (1) only of the delivered spreadsheet.

The fields in the spreadsheet table structure shall be entered in sequence as follows:

DATA FIELD FIXED FIELD LENGTH

Indenture Level 02 characters Document Number 32 characters Document Title 40 characters Revision Letter 02 characters CAGE (Current Design Activity) 05 characters

Definitions:

Indenture Level - Enter the indenture level applicable. The indenture level shall indicate the relationship of a document/drawing to the next, and shall be indicated by a two digit number. Begin with "00" for the system/top assembly drawing/document, increase by 1 ("01", "02", etc.) for each lower tier. Go down each "leg" of the tier until there is no lower drawing/document in that "leg". Go backwards up that same "leg", until finding a tier containing a second or subsequent unlisted drawing/document.