9579776_Rev_N_-_Product_Data_Specification.pdf

9579776_N.DOC CAGE CODE 98752

TABLE OF CONTENTS

Paragraph Description

1. Purpose

2. Applicable Documents

3. Quantities, Distribution, and Software Identification

4. Digital Data Delivery (Sample)

5. Digital Data Delivery (Interim and Final)

6. Legacy Data

7. CAD/CAM Product Definition Data

8. Printed Board Artwork Master, Test, and Drill NC Data

9. Software and Memory Device Data

10. Metadata

11. Bill of Materials (BOM)

12. Classified Data

APPENDIX A Special Characters

APPENDIX B Document Types

APPENDIX C Accompanying Document Kinds

Purpose The purpose of this document is to identify the delivery package requirements necessary to acquire compatible formatted digital engineering data into designated Air Force repositories.

1.1 Scope

This document addresses the mandatory requirements for delivery of engineering data that will ensure successful loading, indexing, access, and retrieval of data with the designated digital data repositories for the Air Force. This Digital Data Description Requirement defines the content, format, media, and product definition data files preparation requirements for the digital Technical Data Package (TDP) for electronic storage into the designated digital data repositories. The TDP contains the digital product definition data for end items or products. The TDP data files are resulting products from the work task described in the solicitation.

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

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

c. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Whenever ASME Y14.41 “Digital Product Definition Data Practices” is invoked in the DI-SESS-81000 Data Item Description (DID), any conflicts or duplications between these two documents shall have the requirements herein apply. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained and approved by the contractor, contracting officer, and repository point-of-contact (POC).

2.0 Applicable Documents

2.1 General

The documents listed in this section are needed to meet the requirements defined in this specification. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all requirements cited in this specification.

2.2 Specifications, Standards, and Programs

The following specifications form a part of this document to the extent specified herein.

ASME Y14.1 – “Drawing Sheet Size and Format” ASME Y14.4M – “Pictorial Drawing” ASME Y14.24 – “Types and Applications of Engineering Drawings” ASME Y14.34 – “Associated Lists” ASME Y14.41 – “Digital Product Definition Data Practices”

ANS US PRO/IPO-10001996 (IGES 5) – “Digital Representation for Communication of Product Definition Data” ANSI/EIA-656 – “I/O Buffer Information Specification (IBIS)”

DoDI 5220.22 – “National Industrial Security Program” DoDI 5230.24 – “Distribution Statements on Technical Documents”

RS-274X – “Extension to RS-274-D” – Interchangeable Variable Block Data Format for Positioning, Contouring, and Contouring/Positioning Numerically Controlled Machines”

IEEE Std. 1029.1 – “Standard for Waveform and Vector Exchange to Support Design and Test Verification (WAVES) Language” IEEE Std. 1076 – “VHDL Language Reference Manual”

IPC-2221 – “Generic Standard on Printed Board Design” IPC-D-356 – “Bare Substrate Electrical Test Data Format”

ISO 9660 – “Volume and File Structure of CD-ROM for Information Interchange” ISO 10149 – “Data Interchange on Read-Only 120mm Optical Data Disks (CD-ROM)” ISO 10303 – “Product Data Representation and Exchange” – AP203, AP209, AP210, AP212, AP214, AP219, AP224, AP232, AP233, AP237, AP238, AP239, and AP240 ISO 32000-1 – “Portable Document Format – Part 1: PDF 1.7”

3. Quantities, Distribution, and Software Identification:

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

b. As the contractor determines that a particular software tool will be used to produce CAD/CAM Product Definition Data (see paragraph 7), a notification shall be sent to the acquiring office identified in block 6 of the DD Form 1423.

The notification shall identify the software name, software version, hardware platform, and vendor of the software.

The prime contractor shall obtain the same letter from all of their applicable subcontractors/vendors on this contract.

4. Digital Data Delivery (Sample): The contractor shall submit four (4) representative samples of each digital data format to be submitted for verification of procedures and processing into a government data repository at intervals called out in the DD Form 1423. The representative samples shall include data in the appropriate digital formats (native, neutral, PDF, legacy data, Gerber data, design models, etc. where applicable). The representative samples shall also have traceability among one another with the submitted samples. Since the intent of the sample is for Government review of the file types for compatibility and delivery compliance purposes, it is imperative that any and all file types anticipated to be in the final TDP delivery be included as samples for preliminary review. Samples of the metadata spreadsheet, Bill of Materials (BOM), and Summary Report files shall be included.

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

a. Files for both sample and final drawing deliveries shall have multiple drawing sheets per filename delivered for each unique document or drawing number. The sheets shall be in a single sheet per view format such as worksheets in a spreadsheet file or book pages. The filenames for all digital data formats for the entire delivery shall be unique.

b. A copy of the translation (such as STEP, IGES, or EDIF) processing or error log file created during the generation of the neutral model files (3D/2D mechanical models and electronic design data) shall also be submitted in digital form. This file shall not be reflected in entries in the Metadata Spreadsheet.

c. On digital drawing formats the sheet layout, border, title block, revision block, other contractually imposed format conditions, and other conventions of engineering drawing format including definition and use of explicit scaling factors shall be integral to the digital data file. Filenames for all digital data shall include the appropriate file extensions where practical or appropriate and shall be included in the metadata spreadsheet filename column.

Engineering drawings shall be drawn using a CAD system, except for legacy data according to paragraph 6, and shall conform to the DD Form 1423.

d. All pertinent entities that comprise the final digital file shall be viewable upon opening of the digital data files.

This prevents the user from having to search for layers, to turn on or off in order to view the final drawing and model entities.

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

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

When metric dimensioning is required, the drawings shall define the interface in metric accompanied by a parenthetical equivalent decimal inch dimension.

g. Revisions made to the digital dataset shall accurately and precisely represent the change in dimensions to the geometry of the object or assembly to ensure the share-ability of the represented data.

h. Do not import or paste raster images, such as TIF, GIF, JPG, and Bitmap into CAD-generated vector drawings or document formats. The exception to this requirement is when the following conditions are met: The graphics do not need to be edited at a later time (such as a photograph or diagram), a legible view-only file can be delivered containing the graphics (reference paragraph 7.b view-only delivery format requirements), or they represent drawings delivered according to ASME Y14.4M. These exceptions also require prior approval by the acquiring activity.

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

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

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

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

(1) Prime Contractor Name/CAGE

(2) Contract number

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

6. Legacy Data:

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

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

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

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

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

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

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

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

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

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

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

AND

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

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

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

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

AND

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

AND

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

View Only HPGL Requirements:

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

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

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

(4) Plot origin is at 0.00, 0.00.

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

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

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

Digital models used in the creation of the engineering drawings associated with the models in the same file, due to the characteristics of the CAD system being used, 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. The annotations and attributes per ASME Y14.41 Paragraphs 5 and 6 for the native, neutral, and view-only models are not required if the annotations and attributes are displayed on the drawing and a note on the drawing referencing the model(s) states that the drawing is a standalone document representing the master design and the model files are for reference purposes only.

Model Notes: For each assembly and subassembly model (which the associated drawing is included in the TDP), all applicable subassembly and part files need to be zipped together and delivered (one zip file per end item which the associated drawing is a deliverable). These zipped files are then listed on the metadata spreadsheet. In addition to the assembly requirement, individual end item part files (which their drawings are included in the TDP) are to be delivered unzipped and listed in the metadata spreadsheet. But individual end item part files are zipped if multiple files are needed for the part model.

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. “Tessellation” is the boundary representation of a 3D model by generation of a mesh of 3D surfaces and curves.

Delivery Formats: Native CAD – Any format native to the contractor’s CAD system is acceptable, e.g. CATIA®, or AutoCAD® (preferred), or Intergraph®, or Applicon®, or ComputerVision®, Pro Engineer®, or NX®, etc.

AND

Neutral – Product Data Exchange using STEP (PDES)/Standard for the Exchange of Product data per ISO 10303 Application Protocols (AP) 203 (preferred) ( or AP 214 STEP) Drawing eXchange Format (DXF) for 2-D models, stereolithography (STL) files, or American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher or other STEP APs may be also be delivered.

AND

Viewable – Viewable tessellated model files suitable for use with a 3rd party viewer (e.g.

Lightweight 3D model (UGS Teamcenter) format JT Virtual Reality Model Language (VRML), 3-D PDF (preferred, which includes 3Di (3D Intelligent PDF or I-PDF),), 3D XML, other Lightweight 3D graphic formats, etc.). Stereolithography (STL) files may be delivered instead as viewable only when other viewable formats are not available or producible and a non-STL neutral file is supplied.

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 7.b. 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 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®, NX®, CATIA®, Intergraph®, Applicon®, ComputerVision®, Pro Engineer®

AND

Neutral – Product Data Exchange using STEP (PDES)/Standard for the Exchange of Product data per ISO 10303 Application Protocols (AP) 203 (preferred) or AP 214;

Stereolithography (STL) files or American National Standards Institute (ANSI) Initial Graphics Exchange Specification (IGES) Version 5.0 or higher may also be delivered

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

This applies to the design of the data rather than the delivery of data.

(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) Drawings delivered as searchable PDF files (Adobe Reader compatible) shall have all sheets for the same drawing number and cage code contained in the same PDF file.

(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 ‘zip’ format in order to preserve the original directory structure.

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

(12) The text characters in the 2D neutral drawing CAD files shall be in an editable or searchable form (such as a standard character set) instead of line segments.

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, photo-plotting, 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 paragraphs7.a and 7.b for separate document and drawing requirements for the technical data package and paragraph 7 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.

AND

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, 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, AP210, or AP214), 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® (Extended RS-274X) and PDF for artwork, Excellon® (or other industry standard formats) for drill data, and IPC-D-356 for testing]

8. Printed Board Artwork Master, Test, and Drill NC Data: Reference paragraph 7 notes for the file set encapsulation requirement and paragraph 7.d for general electrical/electronic CAD/CAM Product Data Requirements. PDF images of the master artwork shall be provided as reference data in addition to the Gerber files.

These PDF images shall be generated directly from the Gerber artwork images. The RS-274X format, 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 photo-plotters. 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 “d” 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. 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 10.

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) Date and time each file was last changed

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

(12) Instructions for composite layers, if any

(13) Gerber file format information:

(a) Gerber type Extended RS-274X

(14) Native and 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

(15) Identify the 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.

(16) Identification of the target photo-plotter 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.

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

(18) Special instruction, if any.

(19) Units of measurement

(20) Identify the board test file format with revision such as IPC-D-256B.

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

(1) Gerber Artwork image files (see paragraphs “e” and “f” for details)

(2) Native and neutral drill data files (see paragraph “g” for details)

(3) Neutral PCB test file (see paragraph “h” below for additional information)

(4) PDF Artwork image files

e. The Gerber artwork images shall be properly aligned and the Gerber file set shall 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 un-plated drill holes.

(7) Others, as applicable

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

(1) Board part number

(2) Revision letter of Artwork image

(3) CAGE Code

(4) Layer order number and/or image name

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

(1) Board part number

(2) File revision, if any

(3) CAGE Code

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

(5) Drill tool sizes

(6) Holes x-y coordinates

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

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

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

9. Software and Memory Device Data: See the CAD/CAM Product Definition Data section (Paragraph 7.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. 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.

10. Metadata: Each physical media shall contain a metadata file. For the purposes of this document, the term “metadata” is used to describe the set of identification information (i.e. index data) which identifies data files. A table structure that represents the metadata for each delivery shall be provided in only one of the options below for the three primary Air Force activities, and shall cover only the data to be delivered.

Option 1: (ROBINS A.F.B)

This metadata spreadsheet 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, either native format or ASCII .rst or .dlf format per paragraph 6. 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. The Summary Report file and the BOM file shall not be listed in the metadata spreadsheet.

Content: The Metadata Spreadsheet shall contain a listing of all engineering documentation contained in the shipment. Separate metadata spreadsheets shall be submitted for classified data listings and unclassified data listings on their respective delivery media. The metadata spreadsheet for the unclassified listing shall NOT contain any references to classified data.

The Metadata Spreadsheet shall contain a listing of all engineering documentation contained in the shipment. Each row in the spreadsheet shall represent a unique filename. All fields shall be left justified, except as noted. The data field titles shall be included at the top of the spreadsheet on row 1 only of the delivered spreadsheet.

Accompanying 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 particular accompanying document is against.

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

DATA FIELD MAXIMUM FIELD LENGTH

Filename (including extension & special characters) 30 characters

Document/Product Type 3 characters Drawing Number 32 characters Drawing Title 200 characters CAGE (Original Design Activity) 5 characters

Manufacturer (Design Activity Name) 32 characters Revision 3 characters Date (Basic/Revision) (DD-MMM-YYYY) 11 characters Drawing Sheet Size 1 character Sheet Number 12 characters

Number of Sheets 4 characters Frame Number 4 characters Number of Frames 4 characters

Contract Number 30 characters Distribution Code 1 character Data Rights 1 character Security Level 1 character Foreign Secure 1 character

Control Activity 2 characters Weapon System Code (WSC) (optional) 15 characters System Name 15 characters

Weapon System Model 15 characters Accompanying Document Kind 3 characters Accompanying Document Number 32 characters Accompanying Document CAGE 5 characters Accompanying Document Revision 3 characters Accompanying Document Sheet Number 12 characters Accompanying Document Frame Number 4 characters File Category 20 characters File_Format (with applicable version) 32 characters

SW_Vendor Name 32 characters SW_Name 20 characters SW_Version 10 characters SW_Operating System 30 characters SW_Operating System Version 10 characters

Media Number 2 characters Comments (optional) 40 characters

Export Control 1 character Source Site 15 characters

For Models & Other Engineering Data (Additional Fields):

Part/Assembly or Identifying Number (PIN) 32 characters PIN Revision letter(s) or Version number(s) 3 characters Quantity per Next Higher Assembly Model 3 characters Next Higher Assembly Model 80 characters

For Model and engineering data files, which generally do not include drawing borders and drawing blocks, the Metadata Spreadsheet shall adhere to the following requirements. This requirement includes model files that contain both 3-D model and drawing information. 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 PIN that is associated with or linked to the model or engineering data file.

DATA FIELD MAXIMUM FIELD LENGTH

Part/Assembly or Identifying Number (PIN) 32 characters PIN Revision letter(s) or Version number(s) 3 characters Quantity per Next Higher Assembly Model 3 characters Next Higher Assembly Model 80 characters

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 4 characters are used and up to 6 characters for 3D model files and others that are used to discriminate file types. Special characters that cannot be used in filenames (or in their extensions) that could introduce processing problems include the following: See Appendix A

Multiple periods within the filename also cause processing problems and shall be avoided unless it is a system-generated filename.

Document/Product Type - See Appendix B

Drawing Number - An alphanumeric identifier located within the drawing number block that is unique and is the primary reference for a document.