DID82351A.pdf

DATA ITEM DESCRIPTION

Title: ACQUISITION AND SUSTAINMENT DATA PACKAGE (ASDP)

ENGINEERING DESIGN DATA AND ASSOCIATED LISTS (EDDAL)

Number: DI-SESS-82351A Approval Date: 20230912 AMSC Number: F10423 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/EZSC/LZPE) Project Number: SESS-2023-025 Applicable Forms: N/A

Use/Relationship: The Acquisition and Sustainment Data Package (ASDP) Engineering Design Data and Associated Lists (EDDAL) provide engineering data adequate to serve as an authoritative and complete technical description of an item. This data, when authorized, is adequate to support competitive procurement and maintenance for items, including for substitutability, backward compatibility, and interchangeability with the as-designed and as-delivered assets. The ASDP EDDAL shall provide the design, engineering, manufacturing, and sustainment information to procure or manufacture an item to be identical to the original item.

The product shall be defined to the extent for a competent manufacturer to produce an item that duplicates the physical, interface, and functional characteristics of the original product, as delivered, without additional processing, design engineering effort, or recourse to the design activity. This DID can be used for conceptual, developmental, and product level EDDAL and shall meet the requirements of the applicable TDP level on contract. In addition, this DID can be used for EDDAL for Special Inspection Equipment, special tooling, special packaging instructions, test equipment, support equipment, military systems, and components, including spares.

a. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in MIL-STD-31000, Technical Data Packages, as related to EDDAL. (Copies of this document are available online at quicksearch.dla.mil.) The ASDP EDDAL data contains the digital product definition data for end items or products and is the documented engineering design from the work task described in the solicitation.

b. In the event of a conflict between this DID and the references cited herein, the text of this DID takes precedence. Nothing in this DID, however, supersedes applicable laws and regulations.

c. This DID is related to DI-SESS-81000, Product Engineering Design Data and Associated Lists, but is created to meet specific enterprise PLM business requirements. Other related design data DIDs include: DI-SESS-81001, Conceptual Design Drawings/Models, DI-SESS-81002, Developmental Design Drawings/Models and Associated Lists, DI-SESS-81003, Commercial Engineering Design Data and Associated Lists, DI-SESS-81004, Special Inspection Equipment (SIE) Engineering Design Data and Associated Lists, DI-SESS-81008, Special Tooling (ST) Engineering Design Data and Associated Lists. (Copies of these documents are available online at quicksearch.dla.mil.)

d. This DID supersedes DI-SESS-82351.

1. Requirements:

1.1. Reference documents.

The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be the latest released/published version as of the approval date of this DID, or as specified in the contract. The documents listed in this section are needed to meet the requirements defined in this DID. While every effort has been made to ensure the completeness of this list, this DID in total defines the complete requirement.

ASME Y14.100, Engineering Drawing Practices and Appendices B through F within

Source: https://assist.dla.mil -- Downloaded: 2026-08-25T14:51Z Check the source to verify that this is the current version before use.

https://quicksearch.dla.mil/ https://quicksearch.dla.mil/

DI-SESS-82351A

ASME Y14.1, Drawing Sheet Size and Format ASME Y14.3, Orthographic and Pictorial Views ASME Y14.5, Dimensioning and Tolerancing ASME Y14.8, Castings, Forgings, and Molded Parts ASME Y14.24, Types and Applications of Engineering Drawings ASME Y14.31, Undimensioned Drawings ASME Y14.34, Associated Lists ASME Y14.35, Revision of Engineering Drawings and Associated Documents ASME Y14.36, Surface Texture Symbols ASME Y14.37, Product Definition for Composite Parts ASME Y14.38, Abbreviations and Acronyms for Use in Product Definition and Related Documents ASME Y14.41, Digital Product Definition Data Practices ASME Y14.44, Reference Designations for Electrical and Electronics Parts and Equipment ASME Y14.47, Model Organization Practices

Copies of ASME Y14 documents are available online at www.asme.org.

ANS US PRO/IPO-10001996 (IGES 5), Digital Representation for Communication of Product Definition Data

Copies of ANS US PRO IGES are available at www.uspro.org.

ANSI/EIA-656, I/O Buffer Information Specification (IBIS)

Copies of ANSI/EIA-656 are available at ibis.org/specs/.

DoD 5220.22-M, National Industrial Security Program (NISP) is now 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM)

Copies of 32 CFR Part 117 documents are available at www.ecfr.gov/current/title-32/subtitle- A/chapter-I/subchapter-D/part-117.

DoDI 5220.22, National Industrial Security Program DoDI 5230.24, Distribution Statements on Technical Documents DoDM 5200.01, Volume 2, DoD Information Security Program: Marking of Information

Copies of DoDI documents are available at www.esd.whs.mil.

Drawing Requirements Manual (DRM)

Copies of the DRM are available at ihsmarkit.com/index.html.

The Gerber Layer Format Specification.

Copies of The Gerber Specification are available online at www.ucamco.com/en/ 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

Copies of IEEE documents are available at standards.ieee.org.

IPC-2221, Generic Standard on Printed Board Design IPC-2611, Generic Requirements for Electronic Product Documentation IPC-D-350, Printed Board Description in Digital Form IPC-D-356, Bare Substrate Electrical Test Data Format IPC-T-50, Terms and Definitions for Interconnecting and Packaging Electronic Circuits

Copies of IPC documents are available at shop.ipc.org.

ISO 8601-1, Date and time — Representations for information interchange 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, AP240, and AP242 ISO 14306, Industrial automation systems and integration — JT file format specification for 3D visualization

Source: https://assist.dla.mil -- Downloaded: 2026-08-25T14:51Z Check the source to verify that this is the current version before use.

http://www.asme.org/ https://web.archive.org/web/20120821190122/http:/www.uspro.org/documents/IGES5-3_forDownload.pdf https://ibis.org/specs/ https://www.ecfr.gov/current/title-32/subtitle-A/chapter-I/subchapter-D/part-117 https://www.ecfr.gov/current/title-32/subtitle-A/chapter-I/subchapter-D/part-117 https://www.esd.whs.mil/Directives/issuances/dodi/ https://ihsmarkit.com/index.html http://www.ucamco.com/en/ https://standards.ieee.org/ https://shop.ipc.org/

ISO 14772-1, Information technology - Computer graphics and image processing - The Virtual Reality Modeling Language ISO 32000, Document management - Portable document format

Copies of ISO documents are available at www.iso.org.

JEDMICS C4 Compressed Image File Format Technical Specification

Copies of JEDMICS C4 document are available online at www.jedmics.net/public/open-specs.html.

MIL-HDBK-516, Airworthiness Certification Criteria MIL-HDBK-780, Standard Microcircuit Drawings MIL-PRF-28002, Raster Graphics Representation in Binary Format - INACTIVE MIL-STD-129, Military Marking for Shipment and Storage MIL-STD-130, Identification Marking of U.S. Military Property MIL-STD-31000, Department of Defense Standard Practice Technical Data Packages MIL-STD-882, System Safety

Copies of MIL documents are available online at quicksearch.dla.mil.

RS-274X, Extension to RS-274-D – Interchangeable Variable Block Data Format for Positioning, Contouring, and Contouring/Positioning Numerically Controlled Machines is now The Gerber Layer Format Specification

Copies of this document are available online at www.ucamco.com.

TIFF Revision 6.0

Copies of TIFF Revision 6.0 are available online at www.itu.int/itudoc/itu-t/com16/tiff-fx/docs/tiff6.pdf.

2. Format.

2.1. In addition to the requirements set forth in this DID, the ASDP EDDAL shall be IAW all specifications and standards listed in Section1.1 above. The ASDP EDDAL shall contain product definition data and be the master technical data in the native format. If required by the contract, derivative technical data shall be in neutral format and viewable format. See MIL-STD-31000 for definition of native, neutral, and viewable formats as well as authoritative and derivative technical data. When contractor validation is required by the contract, proof of validation shall be in contractor format. The ASDP EDDAL shall be in the English language.

a. Native, neutral, and viewable formats for Engineering Models and Drawings shall be in accordance with the Option Selection Worksheet attached to the contract.

b. Formats for Digital Electrical/Electronic Product Definition Data not called out in the Option Selection Worksheet shall meet the specifications below.

(1) Native (Binary) – Native CAD format shall be as specified on the TDP Option Selection Worksheet incorporated into the contract or purchase order.

(2) Native (ASCII) (if export capability exists) – shall be in Cadence Allegro®, Mentor Graphics Design Architect®, ABEL®, OrCAD Capture®, OrCAD PCB®, Zuken VISULA®, POWER LOGIC®, POWER PCB®, or as specified on contract.

(3) Neutral (industry standard) –

(a) For CAD design entry and logical circuit design database such as HDLs, RTLs, gate level data, schematics, etc. shall be in 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), or as specified on contract.

Source: https://assist.dla.mil -- Downloaded: 2026-08-25T14:51Z Check the source to verify that this is the current version before use.

https://www.iso.org/standards.html https://www.jedmics.net/public/open-specs.html https://www.jedmics.net/public/open-specs.html https://quicksearch.dla.mil/ https://www.ucamco.com/en/guest/downloads/gerber-format https://www.itu.int/itudoc/itu-t/com16/tiff-fx/docs/tiff6.pdf https://www.itu.int/itudoc/itu-t/com16/tiff-fx/docs/tiff6.pdf

(b) For Simulation and Test data for stimulus-response information, test benches, timing data, test vectors, etc. not specified on the Option Selection Worksheet shall be in WAVES® (Waveform and Vector Exchange Standard, IEEE Std 1029.1), VHDL (IEEE Std 1076), Verilog® HDL, EDIF, or as specified on contract.

(c) For CAD physical product designs data for component placement and connectivity (conductor routing), physical layouts for PBAs, PBs, PLDs, ICs, etc. not specified on the Option Selection Worksheet shall be in GDS II® Stream, EDIF PCA V400, STEP (ISO 10303 –AP210, AP212, or as specified on contract.

(d) For 2D/3D mechanical interface data for PBAs, PLDs, ICs, etc. not specified on the Option Selection Worksheet shall be in STEP (ISO 10303 – AP203, AP210, or AP214), IDF (Intermediate Data File), or as specified on contract.

(e) For Programming data for PLDs not specified on the Option Selection Worksheet shall be in JEDEC Standard (EIA JESD3), ASCII Hex or as specified on contract.

(f) PB Artwork, Drill, and Test data files not specified on the Option Selection Worksheet shall be in Gerber format IAW The Gerber Layer Format Specification and PDF for artwork.

Drill data shall be in Excellon®,. Testing data shall be in IPC-D-356 for testing.

2.2. Formats for Digital Associated Lists and Revision Authorization Documents. Documents shall be the standard “A” [8-1/2” by 11”] or “B” [11” by 17”] drawing size, IAW ASME Y14.1.

a. Native Format: MS Word (*.docx)

b. Neutral Format: Rich Text Format (*.rtf)

c. Viewable Format: PDF (*.pdf)

2.3. The metadata shall be formatted and delivered as a MS Excel populated spreadsheet format IAW Section 3.6.

2.4. IPL shall be formatted and delivered as a MS Excel populated spreadsheet format IAW Section 3.5.

3. Content.

3.1. General.

The ASDP EDDAL shall describe the complete physical and performance characteristics of an item or component in sufficient detail to ensure that an item or component produced IAW this data is identical to the original item or component. The ASDP EDDAL shall consist of Engineering Design Data for end items, elements, and all components, assemblies, and related special test equipment and interface adaptors which shall be provided to define the details for the manufacture, test, inspection, maintenance, operations, and logistic support of the system. The ASDP EDDAL shall:

a. Define the product to the TDP level specified on the TDP Optional Selection Worksheet.

b. Provide the data to permit competitive acquisition, repair, and manufacture of the original item(s).

c. Provide the required tying, linking, and tracing component, subassembly, and assembly information to produce the lowest level design and specification for a digital representation of a physical item.

d. Provide details of any unique processes and specifications (not published or available to industry) utilized to build the end items IAW the contract.

Source: https://assist.dla.mil -- Downloaded: 2026-08-25T14:51Z Check the source to verify that this is the current version before use.

e. Details of unique processes and specifications (i.e., not published or generally available to industry) when essential to manufacture.

f. All dimensional and tolerance data needed to fully define the part or assembly, including GD&T to define and control dependencies and critical interfaces.

g. Company Modeling and Drafting Standards. If a company standard, which is a non-public or non-military standard, is utilized for modeling designs, drafting GD&T, and creating other PMI for drawings and MBD models, just drawings, or just MBD models, then the company standard(s) shall be included in the ASDP EDDAL.

h. Manufacturing processes, specifications, and assembly sequences. If a manufacturing process or specification is required, it shall be clearly annotated in the EDD. Any process or specification referenced within the EDD that is a non-public or non-military standard shall be defined and delivered within the applicable EDD.

i. Tolerance input and output characteristics.

j. Diagrams with vector starting points and dimensional scaling.

k. Mechanical and electrical connections.

l. Physical characteristics, including interface(s), form, finishes, and protective coatings.

m. Details of material characteristics, heat treatments, conditions, coatings and plating, surface finishes and treatments, and all other data to define the material condition for all components and their locations in the assembly.

n. Inspection, test, and evaluation criteria. First Article Acceptance, Lot test plans and procedures, ATP, NDI, and any Military screening shall be referenced and annotated in the EDD.

o. Quality assurance requirements for test, inspection, acceptance, and verification information.

Engineering design data shall reference the information required to test, inspect, accept, and verify quality assurance requirements to the level specified in the contract or purchase order. All QAP shall be clearly annotated identifying any special tests, inspections, measurements, or certifications required to ensure the item being defined meets its intended performance. Any QAP referenced within the engineering data that is a non-public or non-military standard shall be defined and delivered within the applicable engineering design data.

p. All Critical Safety Characteristics, CSI, CSP, Critical Inspection, and critical quality assurance shall be clearly annotated in the EDD. The CSIs shall be flagged in the indentured parts list.

Definition and markings shall be IAW ASME Y14.100, AFI20-106, and AFI 63-101/20-101.

q. All HCI, and HCP shall be clearly annotated in the EDD. Definition and conforming markings shall be IAW ASME Y14.100. HCIs shall be flagged in the indentured parts list.

r. All SCF and SCI shall be clearly annotated in the engineering design data with a pointer to the component that is deemed SCI or SCF. Definitions of SCI and SCF shall be IAW MIL-STD- 882, System Safety, and MIL-HDBK-516, Airworthiness Certification Criteria.

s. MCF or MCI shall be clearly annotated in the engineering design data. MCF and MCI are defined in MIL-HDBK-516, under “Mission Critical”. “MCF” or “MCI” shall be clearly annotated in the engineering design data with a pointer to the component(s) that are deemed MCF or MCI.

t. Hardware Marking Requirements. Engineering design data shall identify the UID and UII marking requirements and methods for identification to be utilized and applied and shall provide the exact location of the marking and the information to be contained within the marking, per MIL- STD-130. For material subject to the marking requirements of other specifications or standards, the EDD shall specify the marking method, location, and content of those markings. EDD containing statements for items, such as, “Government Furnished Property” or “Government

Furnished Equipment” shall also include the contract number providing the government furnished property or equipment to the contractor (for example: “Government Furnished Property under F34601-99-#-####.”).

u. References to requirements for reliability, maintainability, environmental conditioning, shock, and vibration testing, and other operational or functional tests.

v. References to requirements for programming software into devices or assemblies, including a description of the input media and the procedures for validating that the software has been installed correctly.

w. Interconnection diagrams required for wiring harnesses and cable assemblies.

x. STE and SIE to include special test fixtures shall be annotated in the EDD. Equipment calibration requirements shall be identified.

y. Control Drawings and Models. Control drawings and models disclose form, fit, function, and performance requirements for interchangeable purchased items of existing designs or of items to be specially developed by vendors to the control drawing or model requirements. Control drawings or models permit the acquisition of commercial items and vendor-developed items from specialized segments of industry without disclosing details of designs or divulging proprietary vendor data. Control drawings and models shall be IAW ASME Y14.24.

(1) Vendor Item Control Drawings and Models. Vendor item control drawings are also known as vendor item drawings or specification control drawings. Vendor item control drawings and models shall be used to specify the requirements for purchased items when such items have been approved, by the Government, for use in the design and they are used without alteration, selection, or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). Vendor item control drawings and models, when selected in lieu of, or in addition to, control drawings and models for repairable commercial items, shall be included and provide information to permit Government maintenance and modification of the items.

(2) Source Control Drawings and Models. Source control drawings and models shall be included to specify the requirements for purchased items only when such items have been approved by the Government for use in the design and:

(a) The item is for a critical application,

(b) The requirements can be met by an item from one or more sources, and

(c) The application requires source qualification (testing of a critical item prior to procurement action to ensure that it satisfies the specified requirements).

z. Form, fit, and function requirements conforming to the requirements for control data e.g., models, drawings, etc., as defined in ASME Y14.100 and ASME Y14.24 shall be specified for EDD for which the Government does not have unlimited rights.

aa. Distribution Statement. A Distribution statement, IAW the contract, shall be marked on each dataset item IAW ASME Y14.100 and ASME Y14.41. Associated distribution code shall be populated in the metadata spreadsheet for each dataset item, and associated distribution code shall be populated in the attribute for each CAD model. The distribution codes in the metadata shall match the delivered artifact.

bb. Other Markings. Export control warning IAW DoDI 5230.24, authorized and conforming rights legend, or notice of copyright in accordance with DFARS Subpart 252.227, CUI markings in accordance with DoDI 5200.48 Volume 4, and classified markings in accordance with DoDM

5200.01 Volume 2. Annotations shall be used to display all markings. EDD shall not contain unjustified or non-conforming markings per DFARS Subparts 227.71 and 252.227.

cc. Warranty Statements. Warranty statements shall be in the EDD. The statements shall not obliterate, nor obscure, information on the field of the EDD. The warranty statement shall specify the warranty period, all actions that would render it as voided, and include the contractor or agency that shall correct or repair the deficiency. Warranty statements in the EDD shall contain the following information:

(1) “Warranted item until (warranty expiration date using YYMMDD format).”

(2) Contract number (i.e., the contract number that invokes the warranty of the engineering design data).

(3) “Deficiencies in the engineering design data shall be corrected by (enter the contractor and contractor’s address or the agency that shall correct the deficiency).”

3.2. Item Definition.

All parameters required to define each unit, assembly, subassembly, part or component, or material shall be included in the ASDP EDDAL. This shall include the following data:

a. All mechanical dimensions to fully describe fabrication, acceptance, interface, and installation of the item defined.

b. All electrical parameters to fully describe fabrication, acceptance, interface, and installation of the item defined.

c. All other physical parameters to fully describe fabrication, part and material location(s), acceptance, interface, and installation of the item defined (i.e., weight, pressure, viscosity, etc.).

d. All environmental conditions that units, assemblies, subassemblies, parts, and materials must meet to perform effectively in the end item, such that the end item will meet its specification requirements.

3.3. CAD Product Definition Data.

a. Digital MBD Data.

(1) Native CAD Data. Products shall be defined by native 3D models using MBD, without the use of drawing graphic sheets. Native 3D models shall serve as the master technical data source of the products they define and shall be the authoritative technical data to communicate design intent clearly and accurately. Products shall be modeled in accordance with ASME Y14.41, ASME Y14.47, and MIL-STD-31000. Only one native 3D model shall define a given product, and all native 3D models shall be monodetail, legible, and digitally text searchable to the fullest extent possible. When converting a 2D drawing to 3D MBD, the MBD shall require revising to the next sequential revision IAW ASME Y14.35.

(a) Geometry, Attributes, & Annotations. All digital elements of native 3D models shall be in accordance with ASME Y14.41 and ASME Y14.47. Digital elements shall be detailed to meet the requirements of the applicable TDP level on contract.

(1) Dimensioning and tolerancing shall be in accordance with ASME Y14.41 and ASME Y14.5. When metadata values (see Section 3.6) are used in annotations, the tools and procedures corresponding to the respective original authoring CAD software shall be utilized to link and synchronize these values. All annotations can rotate if needed to meet the requirements of this DID.

(b) Presentation States. All content to clearly communicate design intent shall be displayed in presentation states within all native 3D models in accordance with ASME Y14.47. However, Site Map presentation states as described in ASME Y14.47 are not required. The presentation states shall be as described in ASME Y14.47, and as described below:

(1) Default Notice. This presentation state shall be the first presentation state in the native 3D model and shall display all applicable markings including distribution statement, export control warning, destruction notice, rights legend, notice of copyright, CUI markings, and classified markings in accordance with the contract. If space and legibility allow for human-readability, this presentation state shall also display the unannotated model geometry and applicable management data.

(2) Management Data. This presentation state shall display all applicable management data, including the contract number, and shall be the second presentation state in the native 3D model. If space and legibility allow for human-readability, this presentation state shall also display the unannotated model geometry.

This presentation state is not required if the Default Notice presentation state displays all applicable management data.

(3) Model Only. This presentation state shall display the unannotated model geometry.

This presentation state is not required for non-geometric native 3D models.

(4) Notes. The first Notes presentation state shall display all general notes. This view shall also display model geometry (annotated or unannotated) if space and legibility allow for human-readability. This presentation state is not required if a separate notes list is to be used in conjunction with the native 3D model and the notes list is clearly referenced in a presentation state.

(c) Models & Drawing Types. The principles and use-cases outlined in ASME Y14.24 still apply to MBD. When the 3D equivalent of a drawing type defined in ASME Y14.24 is required, the requirements for said drawing type shall be interpreted and implemented to suit the context of a native 3D model. For example, the required notation(s) specified in ASME Y14.24 shall be modified to replace “DRAWING” with “MODEL” (e.g., VENDOR ITEM CONTROL MODEL, SOURCE CONTROL MODEL, ALTERED ITEM MODEL, etc.)

and shall be displayed with management data.

(d) Variable Forms. The tools and procedures corresponding to the respective original authoring CAD software shall be utilized to define and display the various forms of a given product (e.g., flat pattern, alternate design, etc.) within a native 3D model. For example, geometric elements omitted from the alternate representation also known as the alternate design of a product shall be suppressed or hidden in presentation states meant to only display the product’s alternate design.

(e) Applied Items. Geometry may not be necessary or applicable when modeling applied items. In such cases, a non-geometric native 3D model shall be created for the subject item.

(f) Assemblies & Installations.

(1) All native 3D models shall accurately reflect the design intent of the functional and interface constraints to the fullest extent possible without compromising the integrity or function of the model.

(2) Official models shall be used to represent all subcomponents in native 3D assembly models. When modeling assemblies, priority shall be given to depicting an accurate product structure with the native 3D model’s model tree. For example, assemblies shall not be modeled as single entities to better represent weldments, as this would result in the assembly being incorrectly represented in the model tree as a part with no subcomponents. Tool design models with multiple components can be modeled as a single part.

(g) Product Families.

(1) Only one native 3D model dataset shall be created for a given product family, and the customary tools/procedures corresponding to the respective original authoring CAD software shall be utilized to create native 3D models of all family members within the same dataset. The PIN and differentiating properties shall be applied to the parent and each respective child in the native 3D Model. If the parent is not a producible item, then it shall not have a PIN.

(2) All variations between family members shall be annotated and tabulated to communicate the differences between family members. This information shall be displayed in one or more presentation states within the native 3D model. Children shall not be parents of other children within a native 3D model, often called multilevel, hierarchical, or generational families. In other words, a parent can have as many children as required. Children within the associated parent family cannot then be a parent. If a child is to be modified, the resulting new product shall no longer be product of the original family and shall become a separate model. Family members with the same PIN value shall also have the same REV value within their native 3D model.

However, family members shall not have duplicate PIN values within their native 3D assembly model. Native 3D models described in this section are still considered monodetail and are the 3D equivalent of tabulated monodetail drawings outlined in

ASME Y14.24.

(3) Dissimilar Product Definitions.

Products that are dissimilar in geometry or product structure shall not be modeled as a family. Children shall also not be used as a subcomponent of their parent or siblings within a native 3D model. Consequently, when creating an MBD accurate to existing drawing that defines multiple dissimilar products (e.g., multidetail drawing, inseparable assembly drawing, etc.), new and separately revisable MBD shall be created for individual products defined in the existing drawing, but only to meet the requirements previously described. In such cases, new MBD shall have the same ODA CAGE code as the existing drawing they were created from. The PIN of the product that a new MBD defines, shall also serve as that MBD’s Dataset ID. The existing drawing shall be updated to avoid conflict with the content of the new MBD(s). Inseparable assemblies shall be modeled as single parts if the assembly’s subcomponents are not identified by PIN in the existing product structure.

(h) Reference Models.

(1) Reference models shall only be used to represent products for which an official model; cannot be obtained from the subject product’s CDA, does not exist, and cannot be created by the modeling/procuring organization, or cannot be accurately used in the required context. Reference models are separately revisable from the dataset that officially defines the respective product and are most commonly needed for: products defined by industry or military standards, electronic products, and products that must be modeled with different geometry/properties for use in a specific context (e.g., assemblies, contracts, etc.).

(2) When creating a reference model for a product family or product family member, it is not necessary to create reference models for all family members. Reference models shall only be created for family members needed to satisfy the intended purpose.

Reference models can also be modeled as product families themselves, as described in Section 3.3.a(1)(g). However, reference models specifically created for use in different contexts shall not be defined in the same dataset. When reference models are modeled as product families, all family members shall share the same ORMDA.

Family members with the same PIN, ODA CAGE code, ORMDA CAGE code, Context ID, and Instance ID values shall have the same REV value within their native 3D model.

However, family members shall not have duplicate PIN, ODA CAGE code, ORMDA CAGE code, Context ID, and Instance ID values within their native 3D assembly model.

(3) Reference models shall accurately depict products to the level of detail for their intended purpose. All reference models shall clearly display the following note, referencing the authoritative data that defines the subject product:

“REFERENCE MODEL: SEE <identification of authoritative data> FOR OFFICAL

DEFINITION OF THE SUBJECT PRODUCT.”

Note examples:

REFERENCE MODEL: SEE NASM39086 FOR OFFICAL DEFINITION OF THE

SUBJECT PRODUCT.

REFERENCE MODEL: SEE 201646968 CAGE: 98752 AND 201646968PL

CAGE: 98752 FOR OFFICAL DEFINITION OF THE SUBJECT PRODUCT.

(4) Reference models shall be uniquely identifiable by combining the following metadata fields:

PIN | ODA CAGE Code | ORMDA CAGE Code | Context ID | Instance ID

(5) The PIN, ODA CAGE code, and Dataset ID of a given reference model shall match the PIN, ODA CAGE code, and Dataset ID of the product definition data that officially defines the product represented by the reference model. When a PIN is not applicable for a given reference model and would normally be left unpopulated, the PIN shall be populated with the same value as the Dataset ID. Below are examples of the above fields correctly populated IAW Section 3.3. a(1)(h) for reference models created by the USAF representing PIN: MS20995C20 (a wire defined by industry standard NASM20995 with ODA CAGE code 80205).

Reference model with multiple configurations:

Generic:

NASM20995 | 80205 | 98752

Configurations:

MS20995C20 | 80205 | 98752

MS20995C32 | 80205 | 98752

(6) Reference model for a wire with different geometry/properties for use in PIN:

201646968 CAGE: 98752. (The ODA CAGE code can be added to the end of PINs in the CONTEXT ID field, separated by an underscore, to differentiate reference models made for separate assemblies, where the assemblies happen to have the same PIN.):

MS20995C20 | 80205 | 98752 | 201646968

MS20995C20 | 80205 | 98752 | 201646968_98752

MS20995C20 | 80205 | 98752 | 201646968_19200

(7) Multiple reference models for same wire with different geometry/properties for use in PIN: 201646968 CAGE: 98752:

MS20995C20 | 80205 | 98752 | 201646968 | AFT

MS20995C20 | 80205 | 98752 | 201646968 | FORWARD

MS20995C20 | 80205 | 98752 | 201646968 | 1ST

MS20995C20 | 80205 | 98752 | 201646968 | 2ND

MS20995C20 | 80205 | 98752 | 201646968 | 1

MS20995C20 | 80205 | 98752 | 201646968 | 2

MS20995C20 | 80205 | 98752 | 201646968 | A

MS20995C20 | 80205 | 98752 | 201646968 | B

(2) Neutral CAD Data.

(a) Applicable neutral CAD data shall be producible from all native 3D models with no errors, using the customary tools, procedures, or APIs of the corresponding original authoring CAD software. This errorless neutral CAD data shall be demonstrated via the translation log file.

(b) Non-applicable neutral CAD datasets shall not be derived from a given native 3D model. For example, STL datasets shall not be derived from non-geometric native 3D models. All content in a neutral CAD dataset shall be derived from and match the content of its corresponding native 3D model (e.g., geometry, annotations, metadata, etc.). No datasets shall be attached to a neutral CAD dataset.

(3) Viewable CAD Data.

(a) Viewable CAD data shall be producible from all native 3D models with no errors caused by the native 3D model, using the customary tools, procedures, or APIs of the corresponding original authoring CAD software.

(b) A viewable CAD dataset shall be derived from every native 3D model with the exception of reference models. It is not necessary to derive viewable CAD datasets from native 3D models that define children within a product family, if the viewable CAD dataset derived from the native 3D model defining the corresponding parent, clearly communicates the design intent of all family members. With the exception of a viewable CAD dataset’s 3Di Format, all content in a viewable CAD dataset shall be derived from and match the content of its corresponding native 3D model (e.g., geometry, presentation states, metadata, etc.).

(c) All viewable CAD datasets shall be printable without loss of content. Users shall be able to print all content (e.g., pages, presentation states, notes, etc.), both selectively and comprehensively. No datasets shall be attached to a viewable CAD dataset except those to facilitate formatting or functionality. Such datasets are considered part of the 3Di format.

3Di PDF is the preferred viewable CAD dataset format for USAF MBDs.

(d) 3Di PDF. The first page of the 3Di PDF shall contain separate areas which display the selected presentation state, management data, contract number, notes, time, and date of 3Di PDF creation, and identification of the 3Di PDF template. When text exceeds the boundary of a given area, an indicator shall be present to clearly signify that the area contains additional content. Functional scroll bars shall also be present in such areas to ensure all content can be viewed without the use of additional pages. Users shall be able to select which presentation state to view in the presentation state area and shall be able to query the model within this area per ASME Y14.41.

b. Digital Non-MBD Data.

Datasets shall be delivered at the overall revision level for a given document and shall contain all sheets in the respective document revision they represent. Conversely, datasets shall not be delivered containing only a subset of sheets in a given document revision. All sheets within a given dataset shall be in sequential order and digitally text searchable.

(1) Engineering Drawings.

(a) Engineering Drawings shall be made from presentations describing a particular physical/logical entity or process using 2D geometry and textual information for both electrical/electronic and mechanical items. These drawings can also be created from view plane projections of a 3D model or from parametric-based models that will facilitate semi-automatic creation of engineering drawings from the 3D database. The requirements set forth in Section 3.3. a(1)(a) shall apply. Loft surfaces shall also be provided in the aircraft coordinate system to correlate with delivered drawings when loft data drawings are delivered. statements for drawings that appear in one file extension (native, neutral, raster, or viewable) shall appear and contain the same statements on all other file extensions delivered.

(b) Marking note annotations in a PDF drawing are not allowed. PDF drawing deliveries containing raster graphics can be delivered, when the following conditions are met: 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 used for acceptance for each delivery in PDF format. Associated lists such as parts lists, etc. and supplement datasets 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.

(c) Fluid System Schematics. The fluid system schematics shall illustrate and describe all components with symbols and flow designators such that the fluid system can be traced from component to component (such as: pumps, valves, meters, regulators, and filters).

The schematics shall document the range requirements (i.e., flow, temperature, and pressure) for all component external interfaces and line sizes. The placement and arrangement of the components shall follow a logical sequence of presentation to provide a clear description of the flow of fluids in the system.

(2) Geometry and CAD Creation Requirements for 2D Drawings and 3D Models.

(a) 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)). These product data CAD and model requirements are in addition to the above drawing requirements in Section 3.3. b (1).

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

(c) Digital models used in the creation of the engineering drawings associated with the models in the same file 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.

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

(e) Model and mold files shall either contain annotation information 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 for the native, neutral, and viewable 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.

(f) For each assembly and subassembly model of which the associated drawing is included in the ASDP EDDAL, all applicable subassembly and part files need to be zipped together upon delivery (i.e., one zip file per end item for 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 for which their drawings are included in the ASDP EDDAL and are represented with a single file are to be delivered unzipped and listed in the metadata spreadsheet. However, if multiple files are needed for the part model, individual end item part files are zipped with one zip file per end item for which the associated drawing is a deliverable.

(g) Models, mold files, and non-part mold line surface data shall be delivered separately from the drawing files. Filenames for models, tubing, and mold data do not have the same naming restrictions and maximum length for special characters that drawings do.

Metadata spreadsheet information for models, tubing, and mold data shall be annotated as appropriate under the Product Data Type and Document Type columns as applicable.

(h) Loft Data or Surface Definitions. Loft data that are contained in a ASDP EDDAL shall be produced in native format in the latest version available in addition to the drawing requirements stated in Section 3.3.b(1). The loft data shall be delivered by surfaces. A map of the delivered loft surfaces shall also be provided in the applicable aircraft coordinate system to correlate with delivered drawings. Digital loft data shall simplify part production, repair, inspection, and allow for data transfer for spares procurement. Loft data shall allow for the Government to access, analyze, and manipulate loft surfaces for the purpose of extracting geometric surface data for the purpose of transferring to existing government manufacturing systems for use in part design, manufacture, and inspection by the acquiring activity personnel or by outside vendors. Mold line surface data shall be in separate files for each surface and a map(s) that uniquely identifies each discrete surface shall be provided for all configurations.

(3) Data Encapsulation.

(a) Applicability. To enhance manageability, transportability, and usability, applicable native and neutral design files shall be grouped and encapsulated at each item level. This requirements for encapsulated data files shall be applicable to printed board datasets in Section 3.3.c(11)(a); software and memory device data files in Section 3.3.c(12); and Electrical/Electronic CAD product data(s) in Section 3.3.c(1).

(b) Methods. Either Windows compression .zip format or UNIX “TAR” command are acceptable encapsulation methods. Single files that exceed the storage capacity of delivery media e.g., DVD, CD, etc., 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.

c. Digital Electrical/Electronic Product Definition Data.

In addition to the requirements in section 3.3.b, these requirements include product data files for electrical/electronic end products and systems and shall be IAW IPC-D-350, IPC-D-356, IPC- 2221 and IPC-2611. This product data includes designs for IC devices, PLDs, PBs, PBAs, LRUs, electrical wiring cables and harnesses, etc. This product data shall include the following:

(1) Electrical/Electronic Product data shall include CAD 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, 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.), 2D/3D mechanical interface files, machine control files (for drilling, photo-plotting, parts assembly, etc.), and other electrical/electronic product data files.

(2) The electrical/electronic 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 to the usage 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 stored at the root directory level of the media on which the files are delivered.

(3) Deliver both the ASCII and binary file formats of the native design data if the capability exists. The neutral data files shall be optimized for reusability in other CAD systems in compliance with the neutral standard that the native CAD software is exporting.

(4) CID. The CID shall show graphically the arrangement of external electrical cabling that interconnects electrical assemblies and equipment. The CID shall show all cable runs and terminations and each cable shall be identified by a reference designation number.

(5) Electrical System Schematics. Electrical system schematics shall illustrate and describe circuit items with symbols placed such that a circuit can be traced from item to item in the sequence of its function. The placement and arrangement of the circuits shall follow a logical sequence of presentation to provide a clear description of the distribution of power.

(6) Standard Microcircuit Drawings and Models shall be IAW MIL-HDBK-780.

(7) Cable Harness Assembly. Cable harness assembly models or drawings shall meet the requirements of ASME Y14.100 and ASME Y14.24. The DRM can be used for reference in development.

(8) Component Level Documentation. Schematics and wiring lists for components, including interconnecting cable harnesses, shall be provided.

(9) Overall Grounding Documentation. The grounding schematics shall show the details of all grounds and power returns from source to loads. All connections shall be shown.

Documentation shall also show details of all EGSE interconnections to facility and safety grounds. The grounding schematics shall meet the requirements of the DRM.

(10) Printed Board Artwork Master, Test, and Drill NC Data

(11) 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 Gerber format IAW The Gerber Layer Format Specification 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 dataset shall be as follows:

(a) A printed board dataset shall meet latest version of ASME Y14.24 as of the contract date. The printed board dataset information shall be provided as an integral part of the printed board master drawing, which shall include the PIN.

(b) A PIN shall be assigned for each printed board and defined on the printed board dataset or master drawing.

(c) The printed board dataset shall include the following information:

(1) Board document number.

(2) Board dataset REV.

(3) Board PIN.

(4) ODA CAGE Code.

(5) Master Drawing Document Number.

(6) The purpose of the Board dataset.

(7) Used on data (System(s)).

(8) Name of each file in the Board dataset.

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

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

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

(12) Date and time each file was last changed.

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

(14) Instructions for composite layers, if any.

(15) Gerber file format information: Gerber type X1, X2, X3, etc. IAW The Gerber Layer Format Specification.