ATTACHMENT 10 CONTINUATION OF THE TDP OPTION SELECTION WORKSHEET, BLOCK 9 AF Drawing 9579776
9579776_N.DOC CAGE CODE 98752
APPLICATION REVISIONS NEXT ASSY USED ON LTR DESCRIPTION DATE APPROVED L REVISED PER ECO 2013A0011 01 Jul 2013 G.G. M REVISED PER ECO 2015A0001 20150612 G.G. N REVISED PER ECO 2017A0013-R 20170426 B.H.
ALL SHEETS ARE REV: N
Distribution Statement A. Approved for public release; distribution is unlimited.
UNLESS OTHERWISE SPECIFIED SIGNATURES ARE ON FILE U.S. AIR FORCE DIMENSIONS ARE IN INCHES ON AF FORM 2602 IN LGEC TOLERANCES ON ROBINS AFB, GA FRACTIONS DECIMALS ANGLES APPROVALS DATE ± .XX ± ± DRAFTSMAN TITLE Robert Yohe 95/12/08 .XXX ± CHECKER Edwin Bray 95/12/08 MATERIAL ENGINEER Edwin J. Reid 95/12/11 Product Data Specification
PROJECT ENGINEER
TREATMENT PROJECT AUTHORITY SIZE A.F. CODE IDENT NO. DRAWING NO. Donald Looney 95/12/11 None A 98752 9579776 FINISH RELEASE AUTHORITY SCALE REV SHEET None David Olson 95/12/11 None N 1 of 34 ENGINEERING DRAWING LAYOUT A VERTICAL
1
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
2
9579776_N.DOC CAGE CODE 98752
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”
3
9579776_N.DOC CAGE CODE 98752
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.
4
9579776_N.DOC CAGE CODE 98752
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
5
9579776_N.DOC CAGE CODE 98752
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.
6
9579776_N.DOC CAGE CODE 98752
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
7
9579776_N.DOC CAGE CODE 98752
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 214 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.
8
9579776_N.DOC CAGE CODE 98752
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
9
9579776_N.DOC CAGE CODE 98752
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.
10
9579776_N.DOC CAGE CODE 98752
(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.
11
9579776_N.DOC CAGE CODE 98752
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]
12
9579776_N.DOC CAGE CODE 98752
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
13
9579776_N.DOC CAGE CODE 98752
(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
14
9579776_N.DOC CAGE CODE 98752
(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
15
9579776_N.DOC CAGE CODE 98752
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
16
9579776_N.DOC CAGE CODE 98752
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. Enter the document number (drawing, list, specification, etc.) identified in this record, followed by blanks. If the number is an associated document and is prefixed with alphas e.g. PL, DL, identifying the document as a specific type of associated document, the prefix shall stay intact as part of the document number and not stripped off. The same practice shall apply to any suffixes to the document identifying number by the originating organization. For models and engineering data files that do not include drawing borders and drawing blocks, the document number shall be listed for use in indexing and traceability. This number shall reflect the closest document that is associated with or linked to the model or data file.
Drawing Title - Enter the document title. This is text that is the complete descriptive name of a drawing or document titles for the spreadsheet shall match the exact title as depicted on the document. Symbols and hot keys shall not be used.
17
9579776_N.DOC CAGE CODE 98752
CAGE - Enter the CAGE Code of the original design activity. The CAGE Code is required for all contractor, subcontractor, vendor, and supplier data. (This code was formerly known as the Federal Supply Code for Manufacturers (FSCM) and Code Identification).
Manufacturer (Design Activity) - Enter the name of the design activity whose CAGE is the original design activity assigned to the drawing or document.
Revision - The revision level assigned to a document or a specific sheet of a released document. Enter revision letter(s) applicable to the document number and specifically as applicable to each sheet number. This entry shall be alpha, right justified. For initial issue documents, the entry shall be blank.
Basic/Revision Date - The date when the document was approved for initial (original) release, or the date the revision of a document was approved. The latest date of the document (either the date of the basic approval or the date of the revision, whichever is later) shall be used. (EXAMPLE: 26-MAR-2010)
Drawing Sheet Size - Enter the character that identifies the drawing size of the document identified in this record.
Sheet Number – Enter the individual sheet number of a multiple page document or drawing. But for composite documents or drawings, enter default value “1” for the sheet number. Enter the number of the sheet (right justified) associated with the document number identified in this record. Always use four characters with the decimal in the 5th position, as applicable when using decimal sheet numbers and whenever zero padding is used with the sheet number to fill four character positions.
Number of Sheets - A number that identifies the total count of sheets or pages in a drawing. Enter the total number of sheets as “1” for composite PDF and Word documents. If the total number of drawing sheets exceeds 9999, contact the acquiring office, which calls out this requirement.
Frame Number - Enter the number of the frame, right justified. If the sheet has only one frame, enter “1”. Multiple frames are used to separate a single sheet into multiple sheets.
Number of Frames - Enter the total number of frames required for this sheet (right justified).
Contract Number – Enter the contract number for the digital data delivery.
Distribution Code - Enter the distribution statement code letter (A, B, C, D, E, or F) of the document identified in this record. This code letter in the spreadsheet corresponds with the same code letter used in the distribution statement paragraph that appears on the drawing (for each sheet number).
Data Rights- Enter the code, which identifies the rights status of the information on the document or contained in the file identified by this record. All contractor, subcontractor, vendor, and supplier data shall have the rights status entered in this data field. The rights status codes are as follows:
a. "U" signifies that the Government has unlimited rights to use the data.
b. "L" signifies that the Government has only limited rights to use the data.
c. "K" signifies that the Government has rights to use the data for government purposes only, including competitive procurement, Government Purpose Rights (GPR), or special license rights. A statement on the drawings or in the Summary Report file (in addition to the distribution statement code) shall provide information on how the affected drawings are to be used. Approval from the acquiring office is required before using this code.
Security Level - Enter the code that identifies the classification of the digital data according to the following:
Code Classification N Unclassified297742
18
9579776_N.DOC CAGE CODE 98752
C Confidential S Secret T Top Secret
Foreign Secure – Enter “N” for Distribution code “A”. Enter “Y” for distribution codes B, C, D, E and F. (“N” means the data can go to foreign nationals and “Y” means the data cannot go to Foreign Nationals).
Control Activity - Enter the applicable code, as follows:
LOGISTICS ACTIVITY CODE
OC-ALC (Tinker AFB, OK) MF OO-ALC (Hill AFB, UT) ME WR-ALC (Robins AFB, GA) MG
Weapon System Code (WSC) (optional) – Enter the appropriate weapon system code. In cases where there are many weapon systems code values per drawing number, list for each drawing sheet in the spreadsheet all applicable WSCs in this field separated by commas.
System Name - Enter the system name that the product data is applicable to. For example, enter ALE-47, APQ-170, ALM-233, C-130, etc. Enter ‘Various’ for files that are for multiple systems.
Weapon System Model - Enter if this file is unique to a weapon system model. For example, enter C17A, F15C/D/E, C130H, etc., if the file applies to one of these weapon systems. Leave blank if the file does not apply to a single designated weapon system.
Accompanying Document Kind – See Appendix C
Accompanying Document Number - When an accompanying document identified is delivered, as shown in the Accompanying Document Kind table above, enter the accompanying document number. This is a required entry if a value is contained in the Accompanying Document Kind column.
Accompanying Document CAGE (Commercial and Government Entity) - Enter the CAGE Code of the original design activity. The CAGE Code is required for all contractor, subcontractor, vendor, and supplier data. (This code was formerly known as the Federal Supply Code for Manufacturers (FSCM) and Code Identification).
Accompanying Document Revision - When an accompanying document identified is delivered, as shown in the Accompanying Document Kind table above, enter the accompanying document revision letter (alpha). Right justified.
Accompanying Document Sheet Number - The individual sheet number of a multiple page document or drawing. Enter the number of the sheet associated with the document number identified in this record. Always use four characters with the decimal in the 5th position, as applicable when using decimal sheet numbers and whenever zero padding is used with the sheet number to fill four character positions.
Accompanying Document Frame Number - Enter the number of the frame.
File Category - Enter the appropriate file category type, e.g., native drawing, neutral drawing, view only image drawing, legacy drawing, native 3D model, neutral 3D model, view-only 3D model, native loft data, neutral programming data file, native tubing data, neutral artwork data, etc.
File Format (with applicable version) - Enter the specific product data file format with version, e.g., HP 7586, TIFF Group 4, RS-274X, AutoCAD 2000, STEP AP203, CATIA V5.0, EDIF 400 Schematic, Intel Hex-32, etc. No version needs to appear for DXF or JT files since many conversion programs do not specify the versioning.
19
9579776_N.DOC CAGE CODE 98752
SW_Vendor_Name – Enter the vendor of the native CAD software program. For ‘ZIP’ files, enter the software information for the dominant data file contained in the ‘ZIP’ files and not the software tool used to zip the files.
SW_Name - Enter the name of the native software CAD program used to generate the file.
SW_Version – Enter the version number and/or letters of the native software CAD program used to generate the file.
SW_Operating System - Enter the computer operating system for the CAD software.
SW_Operating System Version - Enter the version of the computer operating system for the CAD software.
Media Number – Enter the numbered figure that matches the label number for each consecutively numbered media type delivered. For example, if multiple CDs or DVDs are delivered, they shall be numbered consecutively and properly annotated in the metadata spreadsheet.
Comments (optional) – Enter additional information.
Export Control – Enter a value of “Y” (without the quotes) for product definition data such as drawings, models, etc. subject to the Arms Control Act containing an export control notice. This also applies to any product definition data having any sheets or pages with an export control notice. Distribution Code “A” designated for a product definition data file shall have the value of “N” (without the quotes) and all other product definition data files shall have this field populated as “Y.”
Source Site – Enter the site code for the site responsible for managing the data: “HAFB” for Hill AFB, “RAFB” for Robins AFB and “TAFB” for Tinker AFB.
Part or Identifying Number (PIN) – For models and engineering data files that generally do not include drawing borders and drawing blocks, an alphanumeric control number assigned to identify a specific item. The PIN is an identifier assigned by the responsible design activity or by the controlling nationally recognized standard, which uniquely identifies (relative to that design activity) a specific item. The PIN generally includes the controlling drawing or document number and optional suffix. The PIN identifier shall meet the same structure and character requirements as those for the drawing number. The PIN does not include the drawing revision identifier, drawing size, or CAGE Code. If the file is not directly part of or an integral part of a PIN, then this number shall reflect the closest part or item that is associated with or linked to the model or data file. PINs are assigned to product data files (such as those for printed circuit board artwork and programmable logic devices (PLDs)), materials, parts, assemblies, equipment, accessories, and computer software.
PIN Revision Letter – The revision level assigned to a PIN. Enter revision letter(s) applicable to the PIN. The character(s) entry will be alpha, right justified. For initial issue PINs, the entry shall be blank.
Quantity per Next Higher Assembly Model – Enter the number of items necessary for the next higher assembly model for this delivery’s assembly. Use commas to separate multiple entries. This field can be left blank for any model file where no model is associated with a higher assembly.
Next Higher Assembly Model – A reference to the next higher assembly assigned to the component model part for which the model is used on. Use commas to separate multiple entries. This field can be left blank for any model file where no model is associated with a higher assembly.
Option 2: (HILL A.F.B)
A spreadsheet table structure that covers only the data to be delivered is required for each delivery. The Metadata spreadsheet shall be delivered in Microsoft Access 2007 digital format. Header information from this spreadsheet is used along with the delivered digital data files to load data into a government Digital Data Repository.
20
9579776_N.DOC CAGE CODE 98752
(a) For word processing documents, enter one row for each file of the native document number delivered. The filename, document number, and all other applicable columns shall be filled. (b) For design model and engineering data files that do not include borders and drawing blocks, the sheet number is not applicable. (leave blank) (c) All letters to be uppercase. (d) Filename – Specify a file naming convention that provides up to 15-character unique filenames for the entire delivery. File extensions of up to 3 characters are used to discriminate file types. 3D Model files that require 6 characters may be used only when approved by the engineering data service center. Special characters that cannot be used in filenames (or their extensions) due to processing problems include the following: See Appendix A. (e) If Data input is not required per the following table, then the spreadsheet column is left blank. (f) Only one image is allowed in a TIF file. The single image shall show a single sheet. (g) Files for B, C, D or E size drawings can be any approved file format except Word. (h) For PDF formats, all size drawings shall be submitted as a single file. The size of drawing must comply with ASME Y14.1 The Air Force JEDMICS viewer opens Adobe Acrobat or Microsoft Word so that the drawing may be viewed. Enter sheet number exactly as indicated on document, always using 4 characters with decimal for 5th place where applicable. (i) TIF images are converted to C4 format before they are imported into JEDMICS. In order for this conversion to be successful the TIF files must not exceed 9216 pixels wide by 7168 pixels high. Drawing size and resolution are what determine the number of pixels in the image. It is recommended that TIF images be saved at 200 dpi. At this resolution the maximum dimension of the original image would be 46.08 inches wide and 35.84 inches high, large enough for a standard E size drawing. A standard font must be used in order to be converted to C-4 format. (j) Gerber file must be zipped and submitted along with the C4 image. (k) All fields on Metadata spreadsheet must remain even if no information is entered in field also no extra columns may be created. (l) Header Columns cannot be changed or deleted.
The fields in the spreadsheet table structure shall be entered in sequence as follows:
Max Header number column Name Required Field Characters Descriptions Row 1 Format Yes 5 Shall always be "IMAGE" This is primary document number as it appears in the title block. If the document number in the title block includes the dash in the number, include it in this column as well. For EO's this is the number of the Document primary drawing the accompanying 2 # Yes 32 document is applicable to. 5 digit Cage Code listed in the title 3 Cage Yes 5 block of document being submitted Type of document being submitted. For example for parts list use PL for wire list use WL for Gerber data use GR etc. For IGES use IGS. (refer to 4 Doc Type No 3 Appendix B for a complete list) The size of the document being submitted. A,B,C,D, E, G or J 5 Doc Size Yes 1
21
9579776_N.DOC CAGE CODE 98752
6 Doc Rev Yes 3 Shall be the same as Sheet Revision Doc Rev DD-MMM-YYYY (e.g.: 10-MAY-2010) 7 Date Yes 11 (revision or approval date) Title of document being submitted. Spaces and Dashes are allowed. Do not use apostrophes, backslashes, percents, pipes, pluses or 8 Doc Title Yes 200 underscores Enter sheet number exactly as indicated on document, always using 4 characters, with decimal for 5th 9 Sheet # Yes 12 place where applicable. Enter total number of sheets exactly as indicated on document, always 10 # of sheets Yes 4 using 4 characters. Sheet revision letter, Leave blank if 11 Sheet Rev Yes 3 new release
All shall be 0001 except roll-sized 12 Frame Yes 4 drawings (G & J sizes). Enter total # of frames for roll-sized drawings (G & J sizes). If sheet has 13 # of frames Yes 4 no frames, enter 0001. Most common types: Enter 441 for PDF files. 741 for Word documents. 713 for Excel spread sheets. 306 for Gerber data. 694 for AutoCAD native. 14 File Type Yes 5 195 for IGES. Enter DOC for PDF files and Word documents. SPRD for Excel spreadsheets. GERBER for Gerber File Type data. CAD for AutoCAD native VCTR 15 Format Yes 20 for IGES. Enter PDF for PDF files. WORD for word documents. EXCEL for Excel spreadsheets GERBER for Gerber File Type data, ACAD for AutoCAD native, IGES 16 Src Fla Yes 22 for IGES data. Enter PDF for PDF file, V2003 for Word and Excel files, 274X for File Type Gerber. 2006 for AutoCAD.V5.2 for 17 Dest Fla Yes 22 IGES File Type Leave blank. Unless for Gerber use 18 Content No 22 ZIP. AutoCAD and IGES use NATIVE File Type 19 Version No 14 Shall always be BLANK 20 Site Code No 5 Shall always be BLANK Unique file names specified for each 21 File Name Yes 15 document file without the extension
22
9579776_N.DOC CAGE CODE 98752
Enter extension of file described by this row, For PDF, DWG, XLS, Word and C4 files this is the actual extension of the file (case sensitive). ZIP for Gerber. IGS for IGES. 22 File Ext Yes 6 For all other approved formats, C4. 23 File Path Yes 2 Shall always be “zero zero”= “00” 24 Field 24 No Shall always be BLANK 25 Field 25 No Shall always be BLANK 26 Field 26 No Shall always be BLANK Security 27 Level Yes 1 Shall always be “N” “U” signifies unlimited rights “L” 28 Rights Yes 1 signifies limited rights Enter “N” for Distribution code “A”. Enter “Y” for distribution codes B, C, D, E and F. (“N” means the data can go to foreign nationals and “Y” Foreign means the data cannot go to Foreign 29 Security Yes 1 Nationals). 30 Nuclear Yes 1 Shall always be “N” 31 Subsafe Yes 1 Shall always be “N” 32 Field 32 No Shall always be BLANK 33 Field 33 No Shall always be BLANK 34 Field 34 No Shall always be BLANK Control 35 Code Yes 2 Enter Value = ME 36 Field 36 No Shall always be BLANK 37 Field 37 No Shall always be BLANK 38 Field 38 No Shall always be BLANK 39 Field 39 No Shall always be BLANK 40 Field 40 No Shall always be BLANK 41 Field 41 No Shall always be BLANK 42 Field 42 No Shall always be BLANK 43 Field 43 No Shall always be BLANK 44 Field 44 No Shall always be BLANK 45 Field 45 No Shall always be BLANK 46 Field 46 No Shall always be BLANK 47 Field 47 No Shall always be BLANK
48 Subsheet No 11 Shall always be BLANK 49 Field 49 No Shall always be BLANK List the Applicable distribution 50 Dist Stmt Yes 2 statement A,B,C, D, E, and F Leave blank unless this data is an Acc Doc accompanying document. See 51 Kind No 3 Appendix C for a complete list. Leave Blank unless this data is an accompanying document. Number assigned to accompanying 52 Acc Doc # No 32 document. 53 Field 53 No Shall always be BLANK
23
9579776_N.DOC CAGE CODE 98752
Leave blank unless this data is an Acc Doc accompanying document. Revision 54 Rev No 3 letter of accompanying document. 55 Field 55 No 12 Shall always be BLANK 56 Field 56 No 4 Shall always be BLANK Enter appropriate WSC or description of associated weapons system. Weapon Separate with commas when entering 57 Sys Code Yes 15 multiple WSCs. Source 58 Site Yes 15 HAFB
59 Rev Order No 6 Shall always be BLANK Acc Rev 60 Order No 6 Shall always be BLANK
61 QA Status Yes 1 Shall always be BLANK
62 TDAC No 1 Shall always be ‘A’
63 Comments No 40 Shall always be blank Enter value of 'Y' for all documents that contain an export control notice. Enter value of 'N' for all documents containing distribution statement A. 64 Export Yes 1 All else shall always be blank Record 65 End No Indicates End of Record
Option 3: (TINKER A.F.B.)
4.0 Metadata / Index Data (Generic Input Service (GIS) Utility; Index File (.rst) Format Definitions) 4.1. General Information. For each GIS Index File Row Type, a table is provided that lists the elements of the row and the sequence in which those elements must appear in the row. 4.2 The Column value indicates the order in which the row type fields must appear. If a field does not have a value set, then it is represented as a null value (i.e. ‘||’). 4.3 The Header Name listed for each element is provided as a mnemonic aid only; the value of the Header Name for each element is not significant and does not appear within the GIS Index File. 4.4 The Required Field indicates that the field shall be populated if the sheet contains the needed Information 4.5 The Field Width value indicates the maximum length of the value assigned to that row type field. The A indicates the field is Alpha only, the N indicates the field is Numeric only and AN indicates that the field is alphanumeric. 4.6 The Descriptions listed for each element is provided as a mnemonic aid only and gives a more information of each field. 4.7. Metadata File all Deliveries shall contain a metadata file with filename of INDEX.RST. The metadata file shall be located at the root level of the file structure. The metadata file shall contain one metadata record entry for each binary data file contained on the media. Each file, except PDF and C4 Raster, shall be placed in its own folder and each folder shall have its own .RST file.
24
9579776_N.DOC CAGE CODE 98752
4.8. Metadata Record - The values of the data fields in the metadata record are used to populate the government’s JEDMICS system database. The Metadata Record format shall be provided as described.
Notes: 1. The Data File Index Structure (DFIS) is a character delimited ASCII text file with one Image Row Entry (Record) per image referencing a data file in a hierarchical directory structure. The file and hierarchical directory structure naming convention is not pre-defined. Each image row entry contains a sequence series of predefined standard data elements (fields) separated by the pipe bar character “|”. Image row entries are separated by a carriage return/line feed (CR/LF). There shall be no blank lines, or lines that do not conform to an image row entry description. 2. Data elements sizes defined indicate the maximum size allowed. Padding of data elements is not required (i.e. Sheet 1 can be entered as “|1|” and does not require an entry of “|000000000001|”. All entries in data elements shall be Uppercase. Leading and trailing spaces within the data elements are ignored (i.e. “| 1 |” will be interpreted the same as “|1|”. Null entries may be represented by “||”. 3. Mandatory data element where “Space or Blank” is a valid entry. “Null or Empty” is not a valid entry (i.e. “| |” is valid, “||” is invalid). 4. File Path shall not include more than eight (8) levels in a directory hierarchy. Corresponding file paths on the media to the data files shall also conform to the aforementioned. 5. File type is the JEDMCIS file type code that indicates the file format of the image file. (e.g. CALS Type 1 raster, etc.). A listing of current JEDMICS values must be obtained to properly fill out this data element. 6. JEDMCIS stores only one revision for an individual sheet of a document, sheet revision. This value is stored in both the document revision and sheet revision database fields within JEDMICS. The drawing revision is calculated by JEDMCIS during execution, using the drawing book algorithm. For this reason, both the document revision and sheet revision database fields within JEDMICS will be populated with the same DFIS data element, sheet revision. 7. Dates will be expressed in the following format: DD-MMM-YYYY: where DD is the Day, MMM is the Month, YYYY is the Year, Examples include “27-JUN-2005”. 8. Within JEDMICS, an accompanying document is associated with a base document’s revision.. 9. The accompanying document CAGE code in JEDMICS is assumed to be the same as the base document CAGE code.
25
9579776_N.DOC CAGE CODE 98752
Required Column Header Name Field Field Width Descriptions 1 Row Type Yes 10 AN Shall always be "IMAGE" Unique Identifier for a drawing or other document as assigned by the organization identified by the document CAGE. Document Numbers shall reflect what is in the drawing title block. If record describes an Accompanying Document Document this field shall contain the 2 Number Yes 32 AN Base Document’s Document Number. Commercial and Government Entity (CAGE) Code. If record describes an Accompanying Document this field shall Document contain the Base Document’s Cage 3 CAGE Yes 5 AN Code. The value of the base Document shall be a value from Appendix B, Document Type Listing. If record describes an Accompanying Document, this field shall contain the Base Document Type. Document If document does not have a document 4 Type Yes 3 AN type, leave Blank. Value shall be one of the following: A, B, C, D, E, F, G, H, J and K as defined by 5 Document Size Yes 2 AN ASME Y14.1 Document 6 Revision Yes 3 AN Shall be the same as Sheet Revision. Revision Date Format. DD-MMM-YYYY Document (eg: 10-MAY-2010). Enter the revision or 7 Revision Date No 11 AN approval date. Document Document Title. Human readable short 8 Title Yes 200 AN description of the document Enter the sheet number applicable to the respective sheet within the drawing. Format is using 4 characters, with decimal for 5th place where applicable. 9 Sheet Number Yes 12 AN i.e. 0001.A Number of Total Number of sheets contained in the 10 Sheets Yes 4 N drawing. Leave blank if no revision. If record describes an Accompanying Document, this field shall contain the Base 11 Sheet Revision Yes 3 AN Document’s revision. Number assigned to the Frame. If Sheet 12 Frame Number Yes 4 N has only one frame, enter “0001”. Number of Total Number of Frames for a Sheet. If 13 Frames Yes 4 N Sheet has no frames, enter “0001”. Designator for the Data Format Type of File. Contact the Repository POC for this 14 File Type Yes 5 N information. (C4=1, Cal=8, PDF=29)
26
9579776_N.DOC CAGE CODE 98752
File Type 15 Format No 20 AN Shall always be BLANK File Type 16 Source Flavor No 20 AN Shall always be BLANK File Type Destination 17 Flavor No 20 AN Shall always be BLANK File Type Leave blank. Unless for Gerber use ZIP. 18 Content No 20 AN AutoCAD and IGES use NATIVE File Type 19 Version No 14 AN Shall always be BLANK 20 Site Code No 5 AN Shall always be BLANK Name of the Image File (without the 21 File Name Yes 15 AN extension) corresponding to this record. Extension of the Image File 22 File Extension Yes 3 AN corresponding to this record Where the Image File is Located. This path is relative to the location of this 23 File Path Yes 242 AN RST File. 24
27
9579776_N.DOC CAGE CODE 98752
39 System No 32 AN Shall always be BLANK 40 Nomenclature No 20 AN Shall always be BLANK 41 Ship Class No 4 AN Shall always be BLANK Ship Type Hull No 42 Number 9 AN Shall always be BLANK Master No 43 Location 30 AN Shall always be BLANK Offline No 44 Location 80 AN Shall always be BLANK 45
48 Subsheet No 11 AN Shall always be BLANK 49 Succeeding No 20 AN Shall always be BLANK List the Applicable distribution Distribution statement A, B, C, D, E, and F in 50 Statement Yes 2 AN accordance with DODI 5230.24 Accompanying The value of the base Document shall be Document a value from Appendix C, Accompanying 51 Kind No 2 AN Document Kind/Type Listing. Accompanying Document Number assigned to accompanying 52 Number No 32 AN document. 53
61 QA Status No 1 A Shall always be BLANK Technical Document Availability Code System defaulted to “A” 62 TDAC No 1 A Shall always be ‘A’ 63 Comment No 40 A Shall always be BLANK 64 Export Control No 1 A Make Y (YES), N (No) or leave Blank 65 Record End Yes Indicates End of Record CR/LF
28
9579776_N.DOC CAGE CODE 98752
11. Bill of Materials (BOM): A spreadsheet table structure (separate from the metadata spreadsheet) representing the indentured level of the parts/assemblies is required for each delivery. The intent of the BOM is to establish the item master Bill of Material (BOM). Definitions 1 through 16 below shall be repeated for each variant of the item configuration.
Content: The BOM shall contain a listing of all parts related to the contract end item as developed, produced, and/or modified for this contract. This is a complete top-down breakdown of the end item. For items controlled by control drawings (vendor, source, altered item, etc.) and government and industry standard specifications, the applicable manufacturer part numbers shall be included at an indentured level under the administrative, source, or other control number (s) which are identified on these specifications/drawings. The control numbers are normally the drawing number with the suffix dash number (s) if applicable. For purposes of the BOM, vendor item parts listed on a drawing under a suggested source of supply table should not be considered as alternate or substitute parts.
BOM Notes: Drawings such as modification, kit, installation, and drawing tree shall not be listed on the BOM. The BOM is for documenting assemblies and parts defined on the TDP design drawings such as assembly, detail, control drawings, specifications, etc. These drawings may be listed on modification or kit type drawings.
Structure: All fields are left justified when placed in a spreadsheet. Data field titles shall be included at the top of the spreadsheet on row one only of the delivered spreadsheet. The BOM shall be delivered in a pipe delimited ASCII text file, Microsoft Excel spreadsheet format, or xml format and these formats shall be delivered in a separate file for each BOM structure.
The fields in the spreadsheet table structure shall be entered in sequence as follows:
DATA FIELD MAXIMUM FIELD LENGTH Indenture Level 2 numeric Part/Assembly Number or Identifying Number 80 characters Cage code of Part/Assembly Number 5 characters Part Description/Nomenclature 500 characters Quantity per Assembly (QPA) 10 numeric Unit of Measure 10 characters NHA Part Number 80 characters NHA Part Number Cage Code 5 characters Drawing/Specification Number 32 characters Drawing/Specification Cage Code 5 characters Effectivity 100 characters Effective Part Number 80 characters Effective Part Number Cage Code 5 characters IUID 1 character Data Rights 1 character Alternate/Substitute Part 1 characters
Definitions:
1. Indenture Level - Enter the indenture level applicable. The indenture level shall indicate the relationship of a part to the next, and shall be indicated by a two-digit number. Begin with "00" for the system/top assembly part, increase by 1 ("01", "02", etc.) for each lower tier. Go down each "leg” of the tier until there is no lower part in that” leg”. Go backwards up that same "leg", until finding a tier containing a second or subsequent unlisted part. Begin down this new "leg" until there is no lower part. Repeat this process until all parts have been listed. Example follows.
00 System/Top Assembly Part 01 Documentation and first subassembly part applicable to or referenced on 00 part 02 Documentation and first subassembly part applicable to or referenced on 01 part immediately above 03 Documentation and first subassembly part applicable to or referenced on 02 part immediately above 02 Next subassembly part applicable to or referenced on 01 part above
29
9579776_N.DOC CAGE CODE 98752
03 Documentation and first subassembly part applicable to or referenced on 02 part immediately above 03 Next subassembly part applicable to or referenced on last 02 part above 03 Next subassembly part applicable to or referenced on last 02 part above 04 Documentation and first subassembly part applicable to or referenced on 03 part immediately above 02 Next subassembly part applicable to or referenced on last 01 part above 03 Documentation and first subassembly part applicable to or referenced on 02 part immediately above 03 Next subassembly part applicable to or referenced on last 02 part above 01 Next subassembly part applicable to or referenced on 00 part above 02 Documentation and first subassembly part applicable to or referenced on 01 part immediately above 03 Documentation and first subassembly part applicable to or referenced on 02 part immediately above
2. Part/Assembly Number or Identifying Number: The Part or Identifying Number (PIN) is an identification assigned by the original design activity or by the controlling nationally recognized standard for the purpose of uniquely identifying a specific item. A PIN is the same as, or is based on, the controlling drawing number. The PIN does not include the drawing revision identifier, drawing size, or activity identification. Government and industry specification parts shall comply with these same requirements.
3. CAGE Code of Part/Assembly Number or Identifying Number: Commercial and Government Entity (CAGE) Code is a five-character code that provides a unique activity identifier used by the government for activity identification.
4. Part Description/Nomenclature: The name or description which the part or item is known.
5. Quantity per Assembly (QPA): Denotes the quantity required for each item in the assembly. This shall be in numeric values only. Data that are deemed “as required” shall have the numeric average quantity consumed entered as “AR/” followed by the average quantity, if known. The QPA for Alternate / Substitute Parts or Manufacturer/Vendor shall be ‘0’ (zero).
6. Unit of Measure: Denotes the unit of measure required for each quantity per assembly established for the part. For items that are not applicable, leave this field blank, unless it is a component, then use “EACH” for the component.
7. Next Higher Assembly (NHA) Part Number: Enter the part or identifying number (PIN) of the next higher assembly (or assemblies) to which the part number applies. This is the indenture level for the BOM as a parent/child relationship. Only a single entry per data field is allowed.
8. Next Higher Assembly (NHA) Part Number CAGE Code: The Commercial and Government Entity (CAGE) Code of the NHA that is a five-character code that provides a unique activity identifier used by the government for activity identification.
9. Drawing/Specification Number: The drawing or specification number for the part listed in the first data field. The latest revision nomenclature needs to be listed whenever a military specification is listed.
10. Drawing/Specification CAGE Code: The Commercial and Government Entity (CAGE) Code of the product data that is a five-character code that provides a unique activity identifier used by the government for activity identification. When this number field is populated with a specification, the field shall reflect the specification’s CAGE.
11. Effectivity: The serial number(s) or lot number(s) of the associated effective part number. If not applicable, this field can be left blank and the rationale documented in the “Summary Report” file that is required per paragraph 5.m. Multiple values shall be separated by commas. A range of consecutive serial or consecutive lot numbers can be listed
30
9579776_N.DOC CAGE CODE 98752
using the first and last number of the range and separated by a dash. More than one range can also be listed and separated by commas. Aircraft tail number may also be used for the effectivity data.
12. Effective Part Number - The part number which the effectivity data represents. For aircraft tail number effectivity, the effective part number shall be the Mission Design Series (MDS).
13. Effective Part Number Cage Code – The CAGE code of the effective part number.
14. IUID: Enter “Y” or “N” showing whether an Item Unique Identification (IUID) is required for each item.
15. Data Rights- Enter the code, which identifies the rights status of the information on the document or contained in the file identified by this record. All contractor, subcontractor, vendor, and supplier data shall have the rights status entered in this data field. The rights status codes are as follows:
a. "U" signifies that the Government has unlimited rights to use the data.
b. "L" signifies that the Government has only limited rights to use the data.
c. "K" signifies that the Government has rights to use the data for government purposes only, including competitive procurement, Government Purpose Rights (GPR), or special license rights. A statement on the drawings or in the Summary Report file (in addition to the distribution statement code) shall provide information on how the affected drawings are to be used. Approval from the acquiring office is required before using this code.
16. Alternate / Substitute Part – Enter “N” (without quotes) if this is not a substitute or alternate part and “Y” (without quotes) if this is a substitute or alternate part. Alternate or substitute parts from a drawing parts list perspective, rather than from vendor item parts and shall be listed in their own row(s). These items shall be populated with the same data as the primary part number except for the differences in the 'QPA', 'Drawing/Specification Number', 'Drawing/Specification CAGE', 'Data Rights', and 'Alternate/Substitute Part' data. The QPA field shall be populated as zero (“0”) (without quotes) for alternate or substitute parts. Alternate or substitute parts shall be listed immediately following the primary (preferred) part.
12. Classified Data:
a. For quantities and distribution, refer to DD Form 1423, Block 14 of the contract.
b. Classified digital data shall be delivered either on Compact Disk (IAW ISO 9660 or Joliet format) or DVD. The contractor, based on file sizes and overall number of files delivered, will make this choice of media. A separate spreadsheet prepared in accordance with Paragraph 10 Option 1 containing the contents of the classified digital data delivery shall also be delivered and shall have the words “CLASSIFIED DATA” as the contents of the file.
c. When a set of data requires both classified and unclassified data deliveries, the shipment of classified data shall contain a reference in the Summary Report file in the package to identify the unclassified data shipment, and the unclassified shipment shall contain a reference in the Summary Report file that package to identify the classified data shipment. Classified and unclassified data shall NOT be intermingled in a shipment, but instead they shall be packaged and shipped separately. Contract requirements for protection of classified data shall apply.
d. Physical media shall be labeled with the following information:
(1) CLASSIFIED DATA
(2) The Contractor name/CAGE
(3) The Contract number
31
9579776_N.DOC CAGE CODE 98752
(4) System
(5) The appropriate disk number of the total (e.g., "Disk 1 of 3")
(6) 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, where space is needed on the media.
(7) List the operating system command (e.g., UNIX® tar) used to archive the data. If space precludes placing this information on the label, provide the information on a separate sheet of paper packaged with the disk or tape.
(8) The appropriate Distribution Statement Code and Export Control Notice shall be included in accordance with DD Form 1423, which calls out this requirement.
Classified Data Deliveries. Classified markings shall be in accordance with DOD 5220.22-M. Classified and unclassified data including metadata, BOM, data file deliveries, and the Summary Report file shall NOT be intermingled in a shipment, but instead they shall be packaged and shipped separately. Contract requirements for protection of classified data shall apply.
APPENDIX A Special Characters:
accent ` ampersand @ apostrophe ‘ asterisk * backslash \ carat ^ comma , curly brackets or braces{} dollar sign $ double quote “ exclamation ! forward slash / parentheses () percent % periods . (More than one) pipe | plus + pound # question mark ? single quote ‘ square or box brackets [ ] tilde ~
APPENDIX B
Document/Product Type - A code entered that identifies the class or type of engineering document or product definition data (e.g. product drawing, parts list, wire list, safety data sheet, models, artwork, programming data, etc.). Enter the code in accordance with the following below: (For engineering drawings with no specific document type, this field shall be not be populated.) References to the appropriate ASME specifications are given below.
32
9579776_N.DOC CAGE CODE 98752
CODE DEFINITION DESCRIPTION
4L Data Package List Data Package List
AL Application List Application data presented in a separate associated list (ASME Y14.34)
AW Artwork An accurately scaled configuration that is used to produce the artwork master, production master, or master pattern drawing (ASME Y14.24). Generally this is related to electronic items such as printed circuit boards and integrated circuit devices.
BM Bill of Materials Bill of Materials
CL Cable List Cable List
D7 Un-dimensioned Dwg An un-dimensioned drawing defines the shape and other design features of an object at a precise scale predominantly without dimensions. It provides an accurate pattern of the feature or features of an item (ASME Y14.24). DL Data List A tabulation of all engineering drawings, associated lists, specifications, standards, and subordinate data lists pertaining to the item to which the data list applies and essential in-house documents necessary to meet the technical design disclosure requirements except for those in-house documents referenced parenthetically (ASME Y14.34). EL Equipment List Equipment List
GL Gauge List Gauge List
IL Index List A tabulation of data lists and subordinate index lists pertaining to the item to which the index list applies (ASME Y14.34).
LF Loft File Loft data file for un-dimensioned information such as surface contours (ASME Y14.24).
MF Model File(s) A combination of design model, annotation and attributes that describes a product (ASME Y14.41 and other CAD database model files); This code is used for source electronic design files, native drawings with embedded 3D models, 3Di or I-PDF files having 3D model file attachments, master models (master instead of the drawings), and other models suitable for use in manufacturing parts.
ML Material List Material List
MY Mylar (Scanned Dwg.) Un-dimensioned drawings on stable base material digitized by a precision scanning process NC Numerical Control Data Data file(s) for controlling equipment used in manufacturing parts.
NL Notes List A tabulation of all notes pertaining to a specific drawing.
PF Programming Data File Software installation file(s) used to program PL Parts List A tabulation of all parts and bulk materials, except those materials that support a process and are not retained, such as cleaning solvents and masking materials, used in the item. (ASME Y14.34)
QA Quality Assurance Supplementary Quality Assurance Provision (SQAP)
33
9579776_N.DOC CAGE CODE 98752
RF Reference File (Model) Used for 3D Model (where the drawing is the master design) 3Di PDF (or I-PDF files with no 3D model file attachments), and other model type data files that do not meet the criteria for document type code “MF”.
RL Running List Running List
TD Tool Drawing Tool Drawing or List
TF Test Data File(s) Data file(s) for direct input into the test setup equipment for the system, sub-system, part, etc.
TP Test Procedure Test Procedure
WD Wire Diagram A wire diagram showing the relations between the parts.
WH Wiring Harness Wiring Harness WL Wiring List A list of tabular data and instructions necessary to establish wiring connections (ASME Y14.34)
APPENDIX C
Accompanying Document Kind - When an accompanying document is delivered, enter the appropriate code from the following table. This is a required entry if a value is contained in the Accompanying Document Number column.
Code Document AD Addendum AM Amendment AN Annex AP Appendix AR Article AT Attachment EX Exhibit NT Notice (safety, engineering, ECPs, ECOs, etc.) SP Specification (slash sheet or other similar types of associated specifications) SU Supplement VR Version 1N Revision Notice
34