9579776G.doc

APPLICATION

REVISIONS

REV

SHEET

Distribution Statement A. Approved for public release; distribution is unlimited.

UNLESS OTHERWISE SPECIFIED

DIMENSIONS ARE IN INCHES

TOLERANCES ON

FRACTIONS

DECIMALS

ANGLES

SIGNATURES ARE ON FILE

ON AF FORM 2602 IN LGEC

APPROVALS

DATE

U.S. AIR FORCE

ROBINS AFB, GA

.XX

DRAFTSMAN

Robert Yohe 12/08/95

TITLE

.XXX (

CHECKER

Edwin Bray 12/08/95 Digital Data Description

MATERIAL ENGINEER

Edwin J. Reid 12/11/95 Requirement

PROJECT ENGINEER

TREATMENT

None

PROJECT AUTHORITY

Donald Looney 12/11/95

SIZE

A

A.F. CODE IDENT NO.

98752

DRAWING NO.

9579776

FINISH

None

RELEASE AUTHORITY

David Olson 12/11/95

SCALE

None

OF

ENGINEERING DRAWING LAYOUT A VERTICAL

TABLE OF CONTENTS

Paragraph

Description

1.

Scope

2.

Quantities, Distribution, and Software Identification

3.

Digital Data Delivery (Sample)

4.

Digital Data Delivery (Final)

5.

Legacy Data

6.

Product Definition Data 7.

Printed Board Artwork Master, Test, and Drill NC Data

8.

Software and Memory Device Data 9.

Metadata Spreadsheet

10.

Indentured Data List (IDL)

11.

Classified Data

1. Scope:

This Digital Data Description Requirement defines the content, format, media, and product definition data files preparation requirements for the digital Technical Data Package (TDP) for electronic storage into the designated digital data repositories. The TDP contains the digital product definition data for end items or products. The TDP data files are resulting products from the work task described in the solicitation.

a. Product Definition Data denotes the totality of data elements required to completely define a product. Product definition data includes geometry, topology, relationship, tolerances, attributes, and features necessary to completely define a component part or an assembly of parts for the purpose of design, analysis, manufacture, test, simulation, and inspection in the support of weapon systems.

b. This Digital Data Description Requirement is applicable to acquisitions of military systems, equipment, and components. It is primarily intended for acquiring digital drawings, associated lists, models and other digital data files at the end of the Engineering and Manufacturing Development Phase and during subsequent phases of the Department of Defense (DOD) materiel life cycle.

NOTE: Whenever ASME Y14.41 “Digital Product Definition Data Practices” is invoked in the DI-SESS-81000 Data Item Description (DID), any conflicts or duplications between these two documents shall have the requirements herein apply.

2. Quantities, Distribution, and Software Identification:

a. For quantities and distribution, refer to block 14 of the DD Form 1423 that calls out this requirement.

b. As the contractor determines that a particular software tool will be used to produce Product Definition Data (see paragraph 6), a letter shall be sent to the requiring office identified in block 6 of the DD Form 1423. The letter shall identify the software name, software version, hardware platform, and vendor of the software. The prime contractor shall obtain the same letter from all of their applicable subcontractors/vendors on this contract.

3. Digital Data Delivery (Sample): The contractor shall submit four (4) representative samples of each digital data format to be submitted for verification of procedures and processing into a government data repository into the development process at intervals called out in the DD Form 1423. The representative samples shall include data in the appropriate digital formats (native, neutral, HPGL, legacy data, Gerber data, design models, metadata spreadsheet, IDL, etc. 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. Do not use paper labels on the media. The contractor shall submit a digital sample representative of the final delivery files delivered in the format described in paragraph 6 of this document.

4. Digital Data Delivery (Interim and Final): Digital data shall be delivered, as updates require for interim delivery and as a final delivery of all updated data, in accordance with the DD Form 1423 which calls out this requirement and as follows:

a. Files for both sample and final 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, so long as the View-Only HPGL files are provided as one sheet per filename and listed per unique filename as individual HPGL sheets in the metadata spreadsheet. 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. A copy of the translation (such as IGES, DXF, or EDIF) processing or error log file created during the generation of the neutral files shall also be submitted in digital form. This file shall not be reflected in entries in the Metadata Spreadsheet.

c. On digital drawing formats the sheet layout, border, title block, revision block, other contractually imposed format conditions, and other conventions of engineering drawing format including definition and use of explicit scaling factors shall be integral to the digital data file. Filenames for all digital data shall include the appropriate file extensions where practical or appropriate and shall be included in the metadata spreadsheet filename column. Engineering drawings shall be drawn using a CAD system, except for legacy data according to paragraph 5, and shall conform to the DD Form 1423.

d. All pertinent entities that comprise the final digital file shall be viewable upon opening of the digital data files. This prevents the user from having to search for layers, to turn on or off in order to view the final drawing’s entities.

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

f. Metric dimensioning is applicable only when interfacing with existing items that were dimensioned in metric. When metric dimensioning is required, the drawings shall define the interface in metric accompanied by a parenthetical equivalent decimal inch dimension.

g. Revisions made to the digital database shall accurately and precisely represent the change in dimensions to the geometry of the object or assembly to ensure the shareability of the represented data.

h. Do not import or paste raster images, such as TIF, GIF, JPG, and Bitmap into CAD-generated vector drawings or document formats. The exception to this requirement is when the following conditions are met: The graphics do not need to be edited at a later time (such as a photograph or diagram), the delivered files are government CAGE coded according to paragraph 6.a, a legible view-only file can be delivered containing the graphics (reference paragraph 6.b view-only delivery format requirements), and the graphics are embedded within the CAD native drawing files having no external links. This exception also requires prior approval by the acquiring activity.

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

j. Delivery Media Requirements: Digital data shall be delivered either on Compact Disk CD-R (IAW ISO 9660 or Joliet format) or DVD+/-R. Use of CD-RW and DVD+/-RW shall not be used due to potential software compatibility 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.

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

l. Physical media shall be labeled with the following information; paper labels shall not be permitted:

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

m. README.TXT File: The contractor shall supply a README.TXT file in ASCII text format. 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):

Type Quantity

Total Number of Files Delivered:

Number of Native DWG Files:

Number of DXF Files:

Number of HPGL Files:

(The DXF files delivered are representative neutral files of the native drawing files. The HPGL files are representative view-only files of the native drawing 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 (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 approved deviations from the applicable CAD/CAM Product Definition Data file formats (See paragraph 6).

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

5. Legacy Data:

a. Raster drawings and any type of document developed in a non-electronic format or no longer available in a digital format (e.g., manual drafting board or scanned formats) and have not been previously delivered to the government, shall be considered as “legacy data.” Raster data that is already in a government repository and raster data that is cited by reference in new data is also considered legacy data. This data shall be delivered in digital form in a standardized format, such as JEDMICS C4 per MIL-PRF-28002, Continuous Acquisition and Lifecycle Support (CALS) TYPE 1, CCITT Group 4 (using MIL-STD-1840B or later format) or Tagged Image File Format (TIFF) Group 4. The minimum resolution for raster images shall be 200 dots per inch (dpi), including raster PDF documents.

When legacy files in MIL-STD-1840B format or later are provided, the header information shall include additional fields for each individual header file, which may not normally be covered by the military or other standard these files are delivered under. These additional fields per drawing or document number are DATE (release date), DOCUMENT TITLE, and TOTAL NUMBER OF SHEETS. These additional fields shall be delivered separately from other required digital data formats in an Excel spreadsheet.

NOTE: Some raster image viewers do not always recognize the correct polarity of a black and white TIFF or other raster image types. Because of this fact, in order for the government to receive the correct polarity files, sample legacy files that cannot be viewed in the proper polarity by contractor viewer software shall be saved (by the contractor) in both negative and positive polarity, before delivery to the government, in order to compare file sizes and proper polarity in government viewing software. In most cases, the smaller file size for each test digital file saved indicates a white background with black data information, which is the correct polarity needed by the government. Some artwork legacy files may have larger file sizes, whenever the contractor provides the correct polarity, since the majority foreground information will be black.

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 manufacturing purposes. 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 B or later revision) by Gerber Systems Corp and shall not contain data that will restrict its usage as a neutral file format for laser photoplotters.

(1) The resulting files shall be quality checked for compliance with the design requirements specified in the technical data package, which includes the stable based drawings. This will ensure that the integrity of the design is maintained after the digitizing process.

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

“THIS GERBER IMAGE WAS PRODUCED BY DIGITIZING AN IMAGE FROM A STABLE BASED MATERIAL”

c. Undimensioned Mylar drawings for mechanical related items (flat patterns, loft, etc.) and applicable electrical items (non-artwork types such as electrical cables) shall be prepared, precisely processed, and scanned with the appropriate process to maintain the dimensional accuracy required by the drawings. A government inspection of this process is required.

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

6. CAD/CAM Product Definition Data: CAD/CAM Product Definition Data is grouped in four basic categories (a through d) below. Definitions and delivery formats are as follows:

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

a. Word Processor and Supporting Logistics 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®. Test Methods and Procedures, Associated Lists, Acceptance Testing Criteria, Configuration Item Specs, and Engineering Analysis results are 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 on the data media to cover all sheets for each document number submitted.

A PDF document delivered as a single file shall have the spreadsheet fields populated by having the sheet number as “1” and total number of sheets equal to the total number of sheets in the single PDF file. A PDF document delivered that is split into two or more separate files shall have the starting sheet number of the file as the sheet number field and have the total number of sheets as the total number of sheets field that make up all of the combined PDF files. All sheets within the PDF file shall be in numerical order when the document is viewed. The preference is to have the PDF documents delivered with full text-searchable capability, rather than scanned images, image plus text, or image-only documents. If Optical Character Recognition (OCR) must be used to make a PDF document text-searchable, then these files are not acceptable for PDF document deliveries.

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

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

AND

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

b. Engineering Drawings (VECTOR): Drawings shall be delivered that are made from presentations describing a particular physical/logical entity or process using 2-dimensional geometry and textual information for both electrical/electronic and mechanical items. These drawings may also be created from view plane projections of a 3-D model, but parametric-based systems exist that will facilitate semi-automatic creation of engineering drawings from the 3-D database. Drawings shall be delivered in all formats below where the scale of the drawing form is 1-to-1. 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 Y 14.1. The requirements set forth in paragraph 6(c), Mechanical Engineering Models of the Geometry Creation Requirements for 3-D Models shall apply. A map of delivered loft surfaces shall also be provided in the aircraft coordinate system to correlate with delivered drawings, when loft data drawings are delivered.

NOTE: Government CAGE code drawings and models shall be delivered in native AutoCAD and view-only HPGL format according to Air Force document 9626025 CAGE 98752. They shall not have drawings delivered containing a mix of vector and raster images, nor contain any grouped text attributes and all entities shall be present on layer zero and in model space. Whenever the native authoring CAD software used for producing government CAGE coded drawings is not AutoCAD, the authoring software or contractor shall have the capability to save the deliverable files in an AutoCAD (*.DWG) format with no significant loss of entities or data that can result from standard CAD file translation procedures. All .DWG files submitted must be able to be manipulated using standard AutoCAD drafting procedures.

Delivery Format: Native CAD – Any format native to the contractor’s CAD system is acceptable, e.g. AutoCAD® (preferred), Catia®, Intergraph®, Cadkey®, Applicon®, Computervision®, SDRC Ideas®, or Mentor Graphics®, Unigraphics®, and others.

Neutral – Product Data Exchange using STEP (PDES)/STandard for the Exchange of Product data per ISO 10303 Application Protocols (AP) 201 through 206, 209 and 210 is mandatory for delivery. Drawing eXchange Format (DXF), or American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher may be delivered instead only when approved by the acquiring office identified in block 6 of the DD Form 1423 which calls out this requirement.

AND

View only - Hewlett Packard Graphics Language® (HPGL) shall be delivered per HPGL Creation Requirements below. However, if HPGL 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. PDF drawing files shall not be allowed as a substitute view-only format for drawing deliveries, unless prior approval is given by the acquiring activity. PDF drawing deliveries containing 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), a legible PDF file is delivered containing the graphics, and the raster images are embedded within the CAD native drawing files where the graphics are visible on paper printouts (if this is not possible, then the graphics shall be encapsulated with each applicable drawing sheet).

View Only HPGL Requirements:

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

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

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

(4) Plot origin is at 0.00, 0.00.

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

c. 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 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 analysis, etc. These product data CAD and model requirements are in addition to the above drawing requirements.

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

Digital models used in the creation of the engineering drawings associated with the models in the same file, due to the characteristics of the CAD system being used, 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.

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.

Model and mold files shall either contain annotation information sufficient to determine critical dimensions and surfaces, notes, materials, etc. or have this information delivered separately in files packaged with the model or mold files. Models and mold files shall be delivered separately from the drawing files according to the formats listed below. Non-part mold line surface data shall also be delivered according to the formats listed below. Filenames for models, tubing, and mold data do not have the same naming restrictions and maximum length for special characters that drawings do. Spreadsheet information for models, tubing, and mold data shall be annotated as appropriate under the Product Data Type and Document Type columns as applicable.

Tubing data that are part of the data package shall be delivered in the formats listed below and separately from the drawing files.

The 3-D CAD Models, Tubing, and Mold data shall be produced and delivered in accordance with the formats and Geometry Creation Requirements and Delivery Formats below.

Delivery Formats: Native CAD - Any format native to the contractor’s CAD system is acceptable, e.g. CATIA®, or AutoCAD® (preferred), or

Intergraph®, or Cadkey®, or Applicon®, or ComputerVision®, or SDRC Ideas®, or Unigraphics®, etc.

Neutral – Product Data Exchange using STEP (PDES)/STandard for the Exchange of Product data per ISO 10303 Application Protocols (AP) 201 through 206, 209 and 210 is mandatory for delivery. Drawing eXchange Format (DXF), stereolithography (STL) files, or American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher may be delivered instead only when approved by the acquiring office identified in block 6 of the DD Form 1423 which calls out this requirement.

Viewable – Viewable tessellated model files suitable for use with a 3rd party viewer (e.g. Virtual Reality Model Language (VRML) or JT format) Loft Data or Surface Definitions - Loft data that are contained in a digital data delivery shall be delivered in native format in the latest version available in addition to the drawing requirements stated in paragraph 6b. The loft data shall be delivered preferably by surfaces. A map of the delivered loft surfaces shall also be provided in the applicable aircraft coordinate system to correlate with delivered drawings. The objective is to obtain access to loft digital data to simplify part production, repair, inspection, and to transfer data for spares procurement. There is a need to access, analyze, and manipulate loft surfaces for the purpose of extracting geometric surface data for the purpose of transfer to existing WR-ALC CAD/CAM systems for use in part design, manufacture, and inspection by the acquiring activity personnel or by outside vendors. Mold line surface data shall be delivered in separate files for each surface in the formats below and a map(s) that uniquely identifies each discrete surface shall be provided for all configurations.

Delivery Format:

Native files – Any format native to the contractor’s CAD system is acceptable, e.g. AutoCAD®, Unigraphics®, CATIA®, Intergraph®, Cadkey®, Applicon®, ComputerVision®, or SDRC Ideas® and others

Neutral - Product Data Exchange using STEP (PDES)/STandard for the Exchange of Product data per ISO 10303 Application Protocols (AP) 201 through 206, 209 and 210 is mandatory for delivery. Stereolithography files or American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher may be delivered instead only when approved by the acquiring office identified in block 6 of the DD Form 1423 which calls out this requirement.

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:

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

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

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

(3) When delivering 3-D geometry, use only the simple, fixed text fonts for the purpose of textual annotation. Note that this requirement is for annotations of 3-D geometry and not an engineering drawing or electronic schematic.

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

(5) If the CAD system for the native digital data used allows a choice for the algebraic type of the spline curve or surface, it is preferred to have the Non Uniform Rational B-Spline Surface (NURBS) representation over the Parametric Spline curves.

(6) The part geometry stored within a CAD model should be self-contained. This means models shall not have external references or pointers to entities outside of the database or model space environment. If geometry must be used from outside the database (a library of standard bolts, for example), physically incorporate the geometry to the database or model space environment for delivered digital data.

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

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

(9) Digital Data Drawings that are delivered shall have one drawing sheet per filename. This means that only one sheet number shall be placed on a drawing per filename. This also means that a CAD file shall not have multiple layers or have multiple sheets in the same view containing different sheets of the same document (or drawing) number. Word processing or Adobe PDF documents, when allowed for delivery, of engineering drawings delivered in raster graphics formats shall have each page saved as a unique filename.

(10) 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 format in order to preserve the original directory structure.

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

d. Electrical/Electronic CAD and CAM Product Data Files: This requirement includes product data files for electrical/electronic end products [e.g., Integrated Circuit (IC) devices, Programmable Logic Devices (PLDs), electrical wiring (cables, harnesses, etc), Printed Circuit Boards (PCBs), Printed Circuit Assemblies (PCAs), Line Replaceable Units (LRUs), etc)] and systems.

Product data shall include Computer-Aided Design (CAD) and Computer-Aided Manufacturing (CAM) files to provide design, simulation, testing, assembly, and manufacturing information. Data files shall be delivered for all applicable design levels [e.g. high-level behavioral and structure levels, Register-Transfer Level (RTL), and gate-level designs]. Product data files shall include (as applicable) source files (e.g., for schematics, truth tables, bubble diagrams, state diagrams, other design entry methodologies, and printed circuit assemblies), compiled files, object files, design models (such as those used in logical circuit designs, design simulations, and physical product designs), netlists (both flatten and hierarchical types for the logical circuit and physical product designs), component placement and connectivity (conductor routing), physical layouts, programming data, simulation and test files (stimulus-response data, test benches, timing data, test vectors, etc), 2-D/3-D mechanical interface files, machine control files (for drilling, photoplotting, parts assembly, etc), and other product data files.

The product data types or entities shall be independent of external links to other software tools or databases. The file(s) shall provide stand-alone design or logistic support disclosure information. Any restriction (that is not controlled by the applicable distribution statement code) to the usage or distribution of the product data files shall be detailed in an ASCII text file named “README - RESTRICTIONS.TXT.” Identify the affected files, and explain the type of and reason for the additional restriction(s). This file shall be stored with the applicable encapsulated files and also stored at the root directory level of the media that the files are delivered.

Deliver both the ASCII and binary file formats of the native design data if the capability exists.

The industry standard neutral data files shall be optimized for reusability in other CAD or CAM systems in compliance with the neutral standard that the native CAD/CAM software is exporting.

NOTES: 1. See above paragraphs 6.a. and 6.b. for separate document and drawing requirements for the technical data package and paragraph 6 notes for the file set encapsulation requirement.

Delivery Formats: Native (Binary) - Native CAD e.g., Cadence Allegro®, Mentor Graphics Design Architect®, ABEL®, OrCAD Capture®, OrCAD PCB®, Zuken VISULA®, POWER LOGIC®, POWER PCB®, others.

Native (ASCII) (if export capability exist) - Native CAD e.g., Cadence Allegro®, Mentor Graphics Design Architect®, ABEL®, OrCAD Capture®, OrCAD PCB®, Zuken VISULA®, POWER LOGIC®, POWER PCB®, others.

AND

Neutral (industry standard) - (1) For CAD design entry and logical circuit design database such as high level languages (HDLs), RTLs, gate level data, schematics, etc. [Electronic Design Interchange Format (EDIF), Verilog® HDL, VHDL (VHSIC Hardware Description Language) (IEEE Std 1076), OSCI SystemC, IGES per MIL-PRF-28000 (Class 6), STEP (ISO 10303 –AP210, AP212), Truth Tables (ASCII), IBIS® (I/O Buffer Information Specification, ANSI/EIA-656), Berkeley’s OPEN-PLA® (Programmable Logic Array), Berkeley’s SPICE®, Boolean Equations (ASCII), etc.]

(2) For Simulation and Test data for stimulus-response information, test benches, timing data, test vectors, etc [WAVES® (Waveform and Vector

Exchange Standard, IEEE Std 1029.1), VHDL (IEEE Std 1076), Verilog® HDL, EDIF, etc.]

(3) For CAD physical product designs data for component placement and connectivity (conductor routing), physical layouts, etc for PCAs, PCBs, PLDs, ICs, etc [GDS II® Stream, EDIF PCA V400, STEP (ISO 10303 –AP210, AP212), etc.]

(4) For 2-D/3-D mechanical interface data for PCAs, PLDs, ICs, etc [STEP (ISO 10303 – AP203, IDF (Intermediate Data File), etc.]

(5) For Programming data for PLDs, etc [JEDEC Standard (EIA JESD3), ASCII Hex, etc.]

(6) For CAM data for parts assembly and testing for PCAs, PLDs, ICs, etc [Valor® ODB++®, GenCAM® (IPC 2510), GDS II® Stream, STEP (ISO 10303 –AP210, AP212), etc.]

(7) For PCB Artwork, Drill, and Test data files [Gerber® (Standard RS-274 or Extended RS-274X) for artwork, Excellon® (or other industry standard formats) for drill data, and IPC-D-356 for testing]

7. Printed Board Artwork Master, Test, and Drill NC Data: Reference paragraph 6 notes for the file set encapsulation requirement and paragraph 6.d for general electrical/electronic CAD/CAM Product Data Requirements. View-only images (in HPGL, PDF, TIF Group 3 or 4, Windows Bitmap, JPEG, or other acceptable format) of the master artwork shall be provided as reference data in addition to the Gerber files. Printed Board Artwork Master per ASME Y14.24 and IPC-2221 shall be in Gerber format (Standard RS-274 or Extended Gerber RS-274X). The RS-274X format, if used, shall be in compliance with the current or subsequent later revision of the 'Gerber RS-274X Format User's Guide' (Part # 414-100-014 Rev B or later) by Gerber Systems Corp and shall not contain data that would restrict its usage as a neutral file for laser photoplotters. The content, format, and configuration control requirements for the printed board file set shall be as follows:

a. A printed board file set document (that meets the requirements of document or drawing standards and practices, such as the latest version of ASME Y14.24 as of the contract date, which entails approved names, title, CAGE, document number, dates, revision data, etc.) shall be developed for each board file set (see paragraph “e” below) to provide configuration control, content, and format information. The standard for engineering drawing practices format listed in CDRL DD Form 1423 Technical Data Package (TDP) shall apply. When a DD Form 1423 for TDP’s does not exist, the acquiring activity shall be contacted for the drawing format practice that shall apply. ASME Y 14.1 is tailored as follows: in Paragraph 6.2 Block L add: “Sheets shall be numbered beginning with one (1) and continue, using consecutive whole integers.” This document shall be referenced on the master board drawing (ASME Y14.24). As an alternative to this document, the printed board file set information may be provided as an integral part of the printed board master drawing, which shall include the file set PIN number and PIN revision data.

b. A unique printed board file set part or identifying number (PIN), preferably the dash number or prefix of the above printed board file set document or printed board master drawing, shall be assigned for each printed board file set and referenced with revision on the printed board file set document or master drawing. One board file set shall be submitted for each printed board.

NOTE: The PIN shall be in compliance with its definition and requirements stated in paragraph 9.

c. The printed board file set document shall include the following information:

(1) Board file set PIN

(2) Board file set PIN Revision

(3) Board Part Number

(4) Master Drawing Document Number

(5)The purpose of the Board file set

(6) Used on data (System(s))

(7) Name of each file in the Board file set

(8) Description of each file in the Board file set (such as for silk screen, component layer, solder mask, etc.)

(9) Artwork image revision letter of each image produced by the image file

(10) Revision letter of each file, if any

(11) Date and time each file was last changed

(12) Size of each file in uncompressed form

(13) Polarity of each image (positive or negative)

(14) Instructions for composite layers, if any

(15) Gerber file format information:

(a) Gerber type (RS-274 or Extended RS-274X)

(b) Data units of measurement (inches, millimeters, etc.)

(c) Dimension word type (coordinate/absolute or incremental)

(d) Number of integer and decimal digits

(e) Zero suppression (leading, trailing, or none)

(f) Zero offset dimensions

(16) Native and/or neutral drill file format information:

(a) Drill file character set (such as EIA, ASCII, and EBCDIC)

(b) Native type with version (such as Excellon, Sieb & Meyer 3000, Trudrill, etc.)

(c) Neutral type with revision (such as Plain ASCII Text, ACL (ANSI/EIA 494), etc.)

(d) Data unit of measurement (inches, millimeters, etc.)

(e) Mode type (absolute or incremental)

(f) Unit scale factor

(g) Zero suppression type (leading, trailing, or none)

(h) Number of integer and decimal digits

(i) Drill rotation angle

(j) Drill x-y offset dimensions

(17) Identify the CAD system hardware platform, operating system with version, vendor of the printed circuit board (PCB) design software, and name of the PCB design software (with version) used to produce the Gerber and drill files.

(18) Identification of the target photoplotter model, manufacturer, type (laser, vector, etc.), and controller model, including any required special controller software configuration or processing packages, for the Gerber data, as applicable.

(19) Identification of the target NC drill machine and controller software with version for the native drill file.

(20) Special instruction, if any.

d. Delivery media containing board data files for more than one PCB shall contain a separate directory for each board or establish a file naming convention that would unambiguously distinguish the different board filesets.

e. Board file set shall include the following files as a minimum:

(1) Aperture D-code table file(s) (see paragraph “f” below for details) (for Standard RS-274 files)

(2) Gerber Artwork image files (see paragraphs “g” and “h” for details)

(3) Native and/or neutral drill data files (see paragraph “k” for details)

(4) Neutral PCB test file (see paragraph “j” below for additional information)

f. Aperture D-code table file shall (for Standard RS-274 files):

(1) Record the date and time that the aperture file was last changed.

(2) Revision letter of aperture file, if any

(3) Correlate aperture position numbers with D-code numbers

(4) Define D-code/aperture shapes using only standard shapes (which are standard circle, square, and rectangle) if practical. If custom shapes, such as thermals, octagons, etc are used, they shall be defined with dimensioned illustrations to capture their true shapes and sizes. Also, the custom D-code macro file shall be provided.

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

(6) State units of measurement (mils, millimeters, etc.)

g. The Gerber files shall be properly aligned and include the following Artwork images:

(1)Circuit layers

(2) Board outline

(3) Silk screen of component reference designations

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

(5) Solder masks (Top and Bottom of board)

(6) Plated and unplated drill holes.

(7) Others, as applicable

h. Each of the above Gerber Artwork image files (paragraph “i”) shall include the following information as a minimum:

(1) Date and time the Artwork image was last changed

(2) Board part number

(3) Revision letter of Artwork image

(4) CAGE Code

(5) Layer order number and/or image name

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

(1) Date and time the drill file(s) were last changed

(2) Board part number

(3) File revision, if any

(4) CAGE Code

(5) File type (Excellon, Plain ASCII Text, etc.)

(6) Drill tool sizes

(7) Holes x-y coordinates

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

(9) Identify plated and unplated holes, if not identified on the master drawing

j. Test data files for PCBs shall be delivered as IPC-D-356 or other acceptable industry standard format.

8. Software and Memory Device Data: See the Electronic Design Data section (Paragraph 6.d) for the delivery of design and programming files for programmable devices (such as PALs, PROMs, etc.). The software and memory device documentation is defined by the drawing requirements for the technical data package. Generally, the requirements include documenting the PIN and PIN revision for the programming data file (burn data), source and programming data filenames, file formats, file format versions, etc on the appropriate drawing such as the Altered Item or Software Installation drawing.

9. Metadata Spreadsheet: A spreadsheet table structure that covers only the data to be delivered are required for each delivery, that is not based on the MIL-STD-1840 format or to a PDM AP 203 Interface and has the structure defined below. The Metadata Spreadsheet shall be delivered in Microsoft Excel digital format and may be delivered on the same media as the digital data. If the metadata spreadsheet cannot be delivered using Microsoft Excel, the following may be substituted upon approval from the acquiring activity, identified in block 6 of the DD Form 1423 which calls this requirement, either native format or ASCII. The spreadsheet information used in conjunction with the digital data is used to provide information and search content to retrieve data from the Digital Data Repository.

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

Each row in the spreadsheet shall represent a distinct sheet number, unless covered by the exceptions below. All fields shall be left justified. The data field titles shall be included at the top of the spreadsheet on row 1only of the delivered spreadsheet.

Exception: 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.

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

Accompany document data fields (in addition to the other fields for these files) shall be populated for documents such as attachments, NOR, and ECOs. The ‘Revision’, ‘Drawing Number’, ‘CAGE’, and ‘Frame Number’ fields shall be populated with drawing information that the applicable Accompany Documents for that particular accompanying document are against.

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

DATA FIELD

FIXED FIELD LENGTH

Filename (including extension & special characters) 30 characters

Document Type

02 characters

Drawing Number

32 characters

Drawing Title

40 characters

CAGE (Design Activity)

05 characters

Manufacturer (Design Activity Name)

Revision

Date (Basic/Revision) (DD-MMM-YYYY)

11 characters

Sheet Number

04 characters

Number of Sheets

Frame Number

Number of Frames

Drawing Sheet Size

01 character

Distribution Code

Data Rights

Security Level

Product Data Type

20 characters

File_Format (with applicable version)

SW_Vendor Name

SW_Name

20 characters

SW_Version

10 characters

SW_Operating System

SW_Operating System Version

10 characters

Weapon System Name

15 characters

Weapon System Model

Contract Number

Control Activity

Accompanying Document Kind

Accompanying Document Number

Accompanying Document Revision

Accompanying Document CAGE

Accompanying Document Sheet Number

Accompanying Document Frame Number

Media Number

Weapon System Code (WSC) (optional)

Comments (optional)

Export Control

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:

Drawing Sheet Size

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:

Part/Assembly or Identifying Number (PIN)

PIN Revision letter(s) or Version number(s)

Quantity of Usage per Next Higher Assembly

03 characters

Effectivity

Definitions:

Filename - Specify a file naming convention that provides up to 30-character unique file names for the entire delivery. File extensions of up to 3 characters are used to discriminate file types. Use of character extensions greater than 3 must be approved by the acquiring activity before data delivery. Special characters that cannot be used in filenames (or in their extensions) due to processing problems include the following:

Multiple periods within the filename also cause processing problems and shall not be used. If DOS files must be accommodated, use a file naming convention of up to only 8 characters.

Document Title - Enter the document title. This is text that is the complete descriptive name of a drawing or document.

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

CAGE - Enter the CAGE Code currently assigned to…