Attachment_0011_Developmental_Level_TDP_Instructions.docx

APPENDIX D

Attachment 0011 Developmental Level Technical Data Package (TDP) Instructions

Solicitation No.: W56HZV-22-R-0026 Date: 29 March 2022

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

Table of Contents

Appendix A: MI-STD- 31000B TDP OPTION SELECTION WORKSHEET ……………………………………………………………………………………….. 15 Appendix B: ASME Y14.100 TAILORING CHECKLIST ………………………………………………………………………………………………………………… 18 Appendix C: US Army - TACOM/GVSC Minimum Required Parameters List in Developmental CAD Models …………………………… 21 Appendix D: US Army - TACOM/GVSC Minimum Required Parameters List in Commercial CAD Models ……………………………….. 24

1. Introduction This document defines the requirements for a Model-based Developmental Level Technical Data Package acquired under contract W56HZV-22-R-0026.

Implementing a Model Based Definition (MBD) TDP involves the concept that a product is fully defined within its 3D solid model without the need of the associated 2D viewable information (i.e. drawing). It also requires the 3D solid models be fully annotated. Therefore, the model contains and displays, as annotations, all dimensions, tolerances, notes, and symbols necessary for fully defining the model. The model is organized into a variety of feature-based Combined Views, with each annotation displayed on its appropriate Combined View. True MBD is both human readable and machine readable.

The contractor’s developmental level Model-based TDP shall consist of TDP elements necessary to provide sufficient data to support the analysis of the OMFV design approach, the fabrication of prototype materiel for test and experimentation, and limited production by the original design activity or with assistance from the original design activity. The data shall also consist of the specifications for all system Configuration Items (CIs) and developmental design data and any required associated lists as specified by the contract.

The contractor shall develop the TDP in accordance with MIL-STD-31000B, the TDP Option Selection Worksheet (Appendix A) and tailoring worksheet (Appendix B), instructions detailed in this attachment (0011) and Department of Defense (DoD) adopted ASME industry latest standards at time of contract award including but not limited to: Y14.100, Y14.1 or 14.1M, Y14.2, Y14.24, Y14.3, Y14.34, Y14.35, Y14.36, Y14.38, Y14.41 and Y14.5. The TDP shall also contain the documentation listed in Table 1 and sections a through n:

TABLE 1: TDP Documentation

TECHNICAL DATA PACKAGE (TDP) ELEMENTS

a. Developmental Design Drawings/Models and Associated Lists

b. Commercial engineering design data and associated lists - Full design disclosure or limited design disclosure, shall be as stated in the contract for each TDP element. Rights in data for commercial engineering design data and associated list shall be as stated in the contract for each TDP element.

c. Special Packaging Instructions (SPI).

d. Specifications. The contractor shall develop the following technical specifications IAW MIL-STD-961E(4) and IAW the contract requirements:

1. Performance Specification Documents IAW DI-SDMP-81465A

2. Detail Specification Documents IAW DI-SDMP-81464A

3. Program-Unique Specification Documents IAW DI-SDMP-81493A

4. System/Sub-System Specification (SSS) IAW DI-IPSC-81431A

e. Specification Tree.

f. Interface Control Documents - The Contractor’s ICD shall contain records of all interface information that establishes the mechanical and electrical interface requirements and procedures necessary to install and integrate in vehicle.

g. Software/Firmware Documentation – See Table 2.

1. Requirements Documentation – The contractor shall deliver software and/or firmware requirements documentation that documents the design, constraints and the functional and performance characteristics of all software products and components. The requirements documentation for Software/firmware shall include the Software Requirements Specification (SRS) and the Interface Requirement Specification (IRS).

2. Architectural and Design Documentation - The contractor shall deliver the architectural and design documentation that defines and records the design of the software. This includes, but is not limited to, 1) the identity of the software product components, 2) their interfaces, 3) the concept of execution among the components, 4) a traceability matrix showing traceability between the software components and the software requirements and 5) the interaction of all software product components with their respective hardware and other software product components. The architectural and design documentation shall include the Software Architecture Description (SAD), Interface Design Description (IDD), and the Database Design Description (DBDD).

3. Technical Documentation - The contractor shall deliver the software technical documentation used in the development, maintenance and modification of all software products. This software technical documentation shall include the Software Design Description (SDD), object description models or “as built” documentation, as well as the Software Product Specification (SPS) and the Software Version Description (SVD).

4. User Documentation - The contractor shall develop and deliver the user documents describing how the software product is to be used in its operational environment. This includes, but is not limited to the runtime environment and the deployed operational environment. The contractor shall ensure that the user documentation clearly and concisely describes each feature of the program in order to adequately assist the user in understanding these features and provide troubleshooting assistance as applicable. The software user documentation shall include the Software User Manual and the Software Product Package (SPP).

TABLE 2: Software Documentation List

5. Commercial/Commercial off the Shelf (COTs) Software - The contractor shall deliver COTs licenses for all software product deliverables consisting of any COTs and enterprise-developed software code with the TDP. The contractor shall provide the following licensing information related to the specific version of the final software product for all COTs software products controlled by a license key or license agreement:

a. Product version,

b. Product license key(s),

c. Number of licenses for the product,

d. Customer hostname,

e. Customer host Id,

f. Customer username,

g. Customer password,

h. Customer license expiration date,

i. Number of COTS licenses,

j. COTS license key,

k. COTS license expiration date

h. Engineering Drawing Tree IAW DI-DRPR-81961B. The engineering drawing tree shall be prepared to identify the interrelationships of engineering design data and associated lists that comprise the TDP. The drawing tree shall be in a top-down, breakdown, block diagram format that identifies all system, subsystem, and component documents to be delivered as part of the TDP. The tree shall be broken down to both the lowest level of assembly (lowest repairable unit) and to the lowest component or piece part, as applicable.

i. Technical Data Package List (TDPL) IAW DI-SESS-82238A. A TDPL shall be prepared as an index to identify all documents contained in the TDP.

j. Engineering Design Document Number Assignment Report IAW DI-SESS-81011F. An engineering design document number assignment report shall be prepared to identify and describe the use of Government document numbers by the contractor.

k. Metadata IAW the Parameters List in Appendix C.

l. Other TDP Data Items – The contractor shall ensure the following ASME Y14.24 Types of Drawings shall be viewable and printable without loss of content and be included in the TDP as necessary to meet TDP requirements:

· Layout Drawings

· Detail Drawings

· Assembly Drawings

· Installation Drawings

· Modifying Drawings

· Arrangement Drawings

· Control Drawings

· Interface Drawings

· Identification Cross-Reference Drawing

· Mechanical Schematic Diagram

· Electrical/Electronic Diagrams

· Special Application Drawings

2. Model-based Technical Data Package (TDP) Requirements

2.1 Definitions:

2.1.1 Model-based Technical Data Package (MTDP): A TDP that defines a product via MBD without the use of Drawing Graphic Sheets, and who’s Master Technical Data is a Native 3D Model.

2.1.2 Model-Based Definition (MBD): An Annotated Model and its associated data elements that define the product in a manner that can be used effectively without a Drawing Graphic Sheet. (See ASME Y14.47-2019).

2.1.3 Master Technical Data: A set of technical data which is the controlling source for any subsequent technical data output. All changes to the technical data must originate on the master technical dataset. There can be only one instance of the Master Technical Data which is typically in the native CAD format and maintained by the CDA. (See MIL-STD-31000B)

2.2 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 of the products they define, and shall clearly and accurately communicate design intent. Products shall be modeled in accordance with ASME Y14.41-2012, ASME Y14.47-2019, and MIL-STD- 31000B. Only one native 3D model shall define a given product, and all native 3D models shall be: monodetail, in the English language, legible, and digitally text searchable to the fullest extent possible.

2.1.1 Geometry, Attributes, & Annotations: All digital elements of native 3D models (e.g. geometry, attributes, annotations, etc.) shall be in accordance with ASME Y14.41-2012 and ASME Y14.47-2019. Digital elements shall be detailed to the extent necessary to meet the requirements of the applicable TDP level. Native 3D models for product level TDPs shall be fully annotated models.

2.2.1.1 All native 3D models shall be marked with: distribution statement and export control warning in accordance with DoDI 5230.24, authorized and conforming rights legend and/or notice of copyright in accordance with DFARS Subpart 252.227, CUI markings in accordance with DoDM 5200.01 Volume 4, and classified markings in accordance with DoDM 5200.01 Volume 2. Annotations shall be used to display all aforementioned markings. Native 3D models shall not contain unjustified or non-conforming markings per DFARS Subparts 227.71 and 252.227.

2.2.1.2 Dimensioning and tolerancing shall be in accordance with ASME Y14.41-2012 and the applicable version of ASME Y14.5. When metadata values (Appendix C) are used in annotations, the customary tools/procedures corresponding to the respective original authoring CAD software shall be utilized to link and synchronize these values. All annotations may rotate if needed to meet the requirements of this document.

2.2.2 Standard Presentation States: All content necessary to clearly communicate design intent shall be displayed in presentation states within all native 3D models in accordance with ASME Y14.47-2019. However, Site Map presentation states as described in ASME Y14.47-2019 are not required. Presentation states shall display all relevant content and shall be configured to maximize content legibility while minimizing empty space. At a minimum, the presentation states described in ASME Y14.47-2019, and further expanded upon below, shall be required:

Default Notice: This presentation state shall be the first presentation state in the native 3D model and shall display the applicable distribution statement, export control warning, destruction notice, rights legend, notice of copyright, CUI markings, and classified markings. If space and legibility allow, this presentation state shall also display the unannotated model geometry and applicable management data.

Management Data: This presentation state shall display all applicable management data and shall be the second presentation state in the native 3D model. If space and legibility allow, 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.

Model Only: This presentation state shall display the unannotated model geometry. This presentation state is not required for non-geometric native 3D models.

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.

2.2.3 Models & Drawing Types: The principles and use-cases outlined in ASME Y14.24-2012 still apply to MTDPs. When the 3D equivalent of a drawing type defined in ASME Y14.24-2012 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-2012 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.

2.2.4 Variable Forms: The customary tools/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 design of a product shall be suppressed/hidden in presentation states meant to only display the product’s alternate design.

2.2.5 Applied Items: Due to their inherit nature and/or method of application, 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.

2.2.6 Assemblies & Installations: The Parts List/Bill of Materials (PL/BOM) and native 3D model for a given product shall not be separately revisable from one another. Consequently, PLs/BoMs shall be integrated with native 3D models and shall be fully displayed in a presentation state. Exploded views shall also be displayed in presentation states, as necessary to clearly identify all subcomponents or communicate design intent. All native 3D models shall accurately reflect true-to-life functional and interface constraints to the fullest extent possible. For example, models of subcomponents within a native 3D assembly/installation model shall be constrained to allow or disallow movement consistent with real-world range of motion.

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.

2.2.6.1 Separate PL/BoM Integration: When creating an MTDP from an existing TDP with a separately revisable PL/BoM, the following procedure shall be followed to integrate the content of the existing TDPs (e.g. PL, BoM, drawing, etc.), with the native 3D model:

2.2.6.1.1 Existing TDP(s) shall be revised and readily display the following note while still accurately defining the respective product:

THE CONTENT OF THIS DATASET HAS BEEN INTEGRATED WITH <identification of native 3D model with revision>, SEE THE LATEST REVISION OF <identification of native 3D model without revision> FOR CURRENT DEFINITION.

The native 3D model shall have a REV one increment higher than the highest REV of the revised TDP(s). The native 3D model shall be identified with the base Dataset ID of the existing TDPs, and the existing TDPs shall no longer be updated. Below are examples of the previously described procedure:

Existing TDP:

PL: 123ABC CAGE: 98752 Rev: A Revised TDPs and Native 3D Model:

PL: 123ABC CAGE: 98752 Rev: B Native 3D Model: 123ABC CAGE: 98752 Rev: C Revised PL Note:

THE CONTENT OF THIS DATASET HAS BEEN INTEGRATED WITH DATASET 123ABC CAGE: 98752 REV: C, SEE THE LATEST REVISION OF DATASET

123ABC CAGE: 98752 FOR CURRENT DEFINITION.

Existing TDPs:

Drawing: 123ABC CAGE: 98752 Rev: B PL: PL123ABC CAGE: 98752 Rev: - Revised TDPs and Native 3D Model: Drawing: 123ABC CAGE: 98752 Rev: C PL: PL123ABC CAGE: 98752 Rev: A Native 3D Model: 123ABC CAGE: 98752 Rev: D Revised Drawing and PL Note:

THE CONTENT OF THIS DATASET HAS BEEN INTEGRATED WITH DATASET 123ABC CAGE: 98752 REV: D, SEE THE LATEST REVISION OF DATASET

123ABC CAGE: 98752 FOR CURRENT DEFINITION.

Existing TDPs:

Drawing: 123ABC CAGE: 98752 Rev: B Native 3D Model: 123ABC CAGE: 98752 Rev: B PL: 123ABCPL CAGE: 98752 Rev: C Revised TDPs and Native 3D Model: Drawing: 123ABC CAGE: 98752 Rev: C PL: 123ABCPL CAGE: 98752 Rev:D Native 3D Model: 123ABC CAGE: 98752 Rev: E Revised Drawing and PL Note:

THE CONTENT OF THIS DATASET HAS BEEN INTEGRATED WITH DATASET 123ABC CAGE: 98752 REV: E, SEE THE LATEST REVISION OF DATASET

123ABC CAGE: 98752 FOR CURRENT DEFINITION.

2.2.7 Product Families: 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 appropriate Part or Identifying Number (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.

1.1.1.1. All variations between family members shall be annotated and tabulated to clearly 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 or generational families. 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-2012.

1.1.1.2. Multi-detail and Inseparable Assemblies: Products that are dissimilar in geometry and 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 MTDP accurate to an existing TDP that defines multiple products (e.g. multidetail drawing, inseparable assembly drawing, etc.), new and separately revisable MTDPs shall be created for individual products defined in the existing TDP, but only as necessary to meet the requirements previously described.

1.1.1.2.1. In such cases, new MTDPs shall have the same Original Design Authority (ODA) as the existing TDP they were created from. The PIN of the product a new MTDP defines, shall also serve as that MTDP’s Dataset ID. The existing TDP shall be updated to avoid conflict with the content of the new MTDP(s) (e.g. remove/change technical content that is now present in the new MTDP: remove annotations, change basic dimensions to reference dimensions, etc.).

2.2.8 Reference Models: Reference models shall only be used to represent products for which an official model: cannot be obtained from the subject product’s Current Design Authority (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.2.9 Metadata: Appendix C lists metadata fields that shall be populated within native 3D models using the customary tools/procedures corresponding to the respective original authoring CAD software:

2.3 Neutral CAD Data: Applicable neutral CAD data shall be producible from all native 3D models with no errors, using the customary tools, procedures, and/or APIs of the corresponding original authoring CAD software. All neutral CAD data shall be in the English language, legible, and digitally text searchable to the fullest extent possible.

2.3.1 Non-Applicable Neutral CAD Data: 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.

2.4 Viewable CAD Data: Viewable CAD data shall be producible from all native 3D models with no errors, using the customary tools, procedures, and/or APIs of the corresponding original authoring CAD software. All viewable CAD data shall be in the English language, legible, and digitally text searchable to the fullest extent possible.

A viewable CAD dataset shall be derived from every native 3D model with the exception of reference models. Also, it may not be 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 elements intrinsic to the viewable CAD dataset (e.g. logos, headings, 3Di format, etc.), all content in the viewable CAD dataset shall be derived from and match the content of its corresponding native 3D model (e.g. geometry, presentation states, metadata, etc.).

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, via a simple command. No datasets shall be attached to a viewable CAD dataset except those necessary to facilitate formatting and/or functionality. Such datasets are considered part of the 3Di format.

2.4.1 3Di PDF: At a minimum, the first page of the 3Di PDF shall contain separate areas which display the selected presentation state, applicable management data, revision history, 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-2012. An example of a 3Di PDF can be found in MIL-STD- 31000B.

3. Other TDP Requirements and Part Modeling Best Practices If the part is a Source Controlled Drawing or Vendor Item Drawing, CAD files from the vendor will be requested. If the CAD file is unavailable, all interface dimensions shown on the drawing will be included and the basic dimensions and geometry will be modeled. Source Control and Vendor Item Control parts shall be modeled with sufficient information for procurement. The contractor shall assign Army Ordnance Part Numbers (AOPNs) to these components.

3D Models shall be valid at all material conditions. The model must be able to regenerate without error when set to min, mid and max material conditions. Dim bound tables can be used to preset the material conditions.

When possible, dimensions on models shall be from datums or surfaces, not edges or tangency points. When this is not possible, datum curve(s) or point (s) should be inserted to avoid parent/child related failures if the edge is broken or rounded. When creating a feature, sketch references should be chosen from the base feature or primary datums. This will help reduce unnecessary parent/child relationships.

Rounds, fillets, and chamfers should be created towards the end of the modeling process. When performing a Finite Element Analysis (FEA), rounds and chamfers are occasionally suppressed to enable more efficient analysis. Creating rounds and chamfers towards the end of the modeling process allows the rounds and chamfers to be suppressed without causing the model to fail. Also, rounds and chamfers should be created separately and not included with a larger sketched feature, unless the round or chamfer is substantial and needed to define the sketch.

Family Tables are table-driven and should only be used for items where changes in feature sizes can be set within a table. On the other hand, flexibility should be used for deformed parts, such as rivets and springs, or when dimensions would change when placed in an assembly.

When converting from 2-D drawings to 3-D models, features will be created using the existing dimensioning scheme contained in the drawings. If insufficient dimensioning is encountered in the current drawings, dimensions may be taken from another source to complete the model. Any such deficiencies will be noted so that the change can be incorporated in the ECP for that item. Changing the dimensioning scheme, or deriving dimensions will not be done unless absolutely necessary. If the dimensioning scheme is to change it must be detailed in advance with proper documentation from the engineer/agency responsible for the part. Problems with tolerance stacking, checking, part interference validation, etc. make changing the dimensioning scheme without a full engineering review is unacceptable.

3.1. Material Assignment in CAD Models

All parts shall be assigned material files in the native CAD models. The material files used on the part shall match the material called out in the notes and be the same applied to 2D drawings. Alternate material files shall be included in the CAD file and noted on drawings.

3.2. Item Number Assignment: Army Ordnance Part Numbers (AOPNs) For newly assigned part numbers for components other than standard hardware and commercial items, shall be assigned Government-issued AOPNs (See under “File Naming Convention”). Components identified as vendor item control or source control drawings shall be assigned AOPNs that are called out on higher up assemblies. The contractor shall request AOPNs from the designated Government engineering representative. The contractor shall request additional blocks of numbers on an as needed basis via e-mail to the Government engineering representative. AOPNs will be assigned based on the following:

a) End Item/Top Assembly: 87Txxxx

b) Kits : 57Kxxxx

c) All others Parts and Assemblies, Instructions, BII, Installations, etc.: 1xxxxxxx

3.1.1. File Naming Convention

Newly developed, modified or legacy items with Army Ordinance Part Numbers or commercial/standard part numbers shall be named using the following convention:

CAGE_Part Number.prt, i.e. 19207_12345678.prt, 39428_4464k13.prt, etc.

3.3. True Manufacturer Part Numbers

The contractor shall utilize the true manufacturer’s part number and CAGE to identify parts that the contractor does not manufacture (such as commercial, standard or COTS).

a. The Contractor may utilize WebFLIS or FEDLOG CD/DVD subscription.

b. These parts shall have 3D CAD models for space claim in new or modified TDPs.

3.4. Standard Parts

Contractor shall use Government Standard Parts Library for 3D CAD models that are compliant hardware to ASME B18.24.

3.5. Item Identification Traceability

The Contractor shall prepare the technical data so all applicable product definition documents and part identifying numbers (PIN), i.e. associated lists, test criteria, program-unique and process specifications, standard parts, etc., are referenced (top to lowest part item level) within the TDP for traceability.

3.6. Security Markings

The contractor shall apply the applicable DoD Technical Distribution Statement and Export Control Warning to all technical data produced or delivered in accordance with DODI 5230.24, as required by the contract. All statements, notices, and data rights legends shall be applied to all drawings on each sheet, directly above or adjacent to the title block. Associated lists and other related documents that are primarily of a textual nature shall have markings applied to each page. On models, all markings shall be applied to initial layer at opening.

3.7. CUI Markings

Controlled Unclassified Information (CUI) marking shall be added and displayed per CAD drawing formats provided by USG. “CUI” parameter shall be populated with “CUI”. Distribution statements with a code other than “A,” shall include “CONTROLLED BY”, “CUI CATEGORY”, and “POC”.

3.8. Data Rights Markings on Tech Data Deliverables

Data rights markings on technical data deliverables shall be per DFARS in this contract.

Engineering drawings, models, associated lists or other reference type documents that are being prepared for or assembled into a Technical Data Package, shall be marked with an appropriate Distribution Statement and, as applicable, the Export Control Notice, prior to distribution, regardless of media per these requirements.

All statements and notices shall be applied on drawing sheets, directly above or adjacent to the title block. Associated lists and other related documents that are primarily of a textual nature shall have notices applied to sheet/page one.

On models, all statements and notices shall be populated in the appropriate parameter field and in notes. Data Rights notes shall be displayed flat to screen on opening models. The ERR form shall be marked based on the most restrictive distribution statement of the data contained within the ERR package. Include the Export Control warning when applicable Distribution statements and proper Export Control notice assignment will be provided to contractor.

There shall be no Intellectual Property, FOUO, or FOIA-related markings on the submittal. "ITAR" shall not appear on the submittal, as the ITAR falls under the Arms Export Control Act already stated in the export control warning.

3.9. Marking for Critical Safety Items

All engineering design data describing any hardware or software item that has been determined to contribute to a hazard with Catastrophic or Critical mishap potential, or that may be implemented to mitigate a hazard with Catastrophic or Critical mishap potential shall be marked as a Critical Safety Item. (MIL-STD-882E)

3.10. Marking for Item Identification

All items to be provisioned shall incorporate labeling or marking note in accordance with MIL-STD-130N(1). Add a note in 3D models and associated drawings:

3.10. Referenced Documents

The contractor shall provide access to all documents referenced in TDP deliverables as required by of MIL-STD-31000B. For ECPs, the contractor shall furnish all referenced drawings.

3.11. Contractor Standards

Limited rights contractor standards are not allowed to be referenced in drawings that the Government currently has Government purpose or unlimited rights for new or Modified designs by the Contractor unless otherwise specified or approved by Government. New designs include modified designs impacting form, fit or function requiring a part number change. (MIL-STD-31000B).

3.12. Product Baseline Changes

Attachment 0011 – Developmental Level TDP Instructions Solicitation No.: W56HZV-22-R-0026

At establishment of the final Product Baseline and beyond, revised data shall cite the Engineering Release Record (ERR) Number in the description of change block or applicable CAD parameter as authorization to release the data, and shall be married to the ERR package.

MI-STD-31000B TDP OPTION SELECTION WORKSHEET

Complete Block 11. OTHER TAILORING (Attach additional sheets as necessary) Solid Model Geometric Validation Proprieties (GVP) Checks. Contractor shall conduct geometric validation properties checks on all Government native (fully defined feature based parametric) part and assembly solid models. Disregard manufacturing process models. The minimum 3-D Component Geometry, Assembly Construction, Validation Checks are:

3-D Component Geometry

1) Each model must contain only one (1) solid.

2) Models are single part files consisting of modeling entities and attributes.

3) Models contain drafting entities necessary to present geometrical dimensioning and tolerancing information.

4) Models are generated for every part number that is production intent, production related, or to be prototyped.

5) No reference geometry models reside within the model.

6) Models contain no surface data (non-commercial components).

7) Parameters (attributes) are present and contain acceptable values.

8) Models contain proper density

9) Layers contain correct objects.

10) Models contain coordinate system.

11) Models that are positioned in more than one location on the vehicle end-item shall be designated at the absolute coordinated system and located in the vehicle end-item position in the assembly. All other models shall be designated in this vehicle position.

12) Models are saved in an isometric view.

13) Models and views not used are deleted.

14) All corner and fillet radii are modeled

15) All unnecessary wireframes are deleted.

16) Models passed all native CAD system (design software) solid model validation checks.

17) Models passed all interference checks (bolt/nut and gasket is ok).

18) Models contain no tiny objects or tiny edges.

19) Modeling tolerances applied in accordance with Contractor’s geometry and CAD creation standard. A default tolerance value shall be indicated in standard.

20) Model does not have any unnecessary parent/child relationships.

3-D Assembly Construction

21) Assembly contains CSYS/WCS displayed in absolute zero (x=0, y=0, z=0).

22) Assembly in body position.

23) Assembly can contain standard parts; however, standard parts must be UNMODIFIED from original.

24) Assembly is fully constrained.

3-D Component and Assembly in Explicit Non-Parametric Merged Solid Shrink-Wrap Format

25) Part and assemblies in merged solid format.

26) Complete with sufficient envelope.

27) Accurate mounting and mating dimensions (intefaces to Governent baseline configuraiton items).

28) Body position in accordance with absolute coordinate system.

29) Includes applicable interface characteristics.

30) Current mass proprieties, weight, center of gravity and inertia information.

31) Incorporation of user-defined TDP metadata attributes.

32) Quality level at highest reasonable selection.

33) Skeletons, quilts, and small surfaces removed.

34) Real colors not gray-neutral colors presented

Appendix A

A. Drawing Media (Choose all that apply)

(1) Non-digital (Specify )

(2) Digital Data (3D Native, 2D neutral CAD Adobe PDF, Word, etc., IAW DI-SESS-81000C)

(3) Other (Specify)

B. Drawing Format (Choose One)

(1) Contractor

(2) Government (forms supplied by the Government)

(3) Government (forms supplied by the Contractor)

C. Drawing Sheet Size and Format (Choose One)

(1) ASME Y14.1

(2) ASME Y14.1M

D. Application Data (Choose all that apply)

(1) Contractor option

(2) Required

(a) On drawing

(b) By reference (Specify )

(c) Contractor option

(3) General use or multi-use notations

(a) allowed

(b) not allowed

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

(1) Monodetail

(2) Multidetail

(3) Tabulated

F. Dimensioning and Tolerancing (Choose all that apply)

(1) Metric

(2) Decimal-inch

(3) Application of ASME Y14.5

(a) Specific issue (revision) required (Specify issue )

(b) Issue in effect (ASME Y14.5-2018 )

G. Drawing Notes (Choose One)

(1) On drawing

(2) By reference (Specify )

(3) Contractors option

H. Types of Drawings (ASME Y14.24) (both, as needed)

(1) Contractor selects (as needed)

(2) Government selects (as needed)

APPENDIX B

ASME Y14.100 TAILORING CHECKLIST – SHEET 1

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

(1) Drawing revision level (DOD preferred)

(2) All sheets same revision level

(3) Sheet revision level

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

(1) Advance revision level

(2) Revision level is not advanced

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

(1) Contractor option

(2) Optional methods

(a) Remove one or more revision record as required

(b) Remove all previous revision history

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

(d) Remove all except revision preceding current

(e) Maintain revision history in its entirety

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

4 Contractor option 5 Optional methods

5.1 Renumber sheets using consecutive whole numbers

5.2 Number added sheets in decimal-number sequence

5.3 Number added sheets in alpha-numeric sequence

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

(1) Contractor option

(2) Optional methods

(a) Renumber all affected remaining sheets

(b) Affected remaining sheets not renumbered (revision status of sheets block is updated with notations such as CANC or DEL)

N. Markings on Engineering Drawings (Choose one)

(1) Special items and processes apply

(a) Applicable symbols ()

(b) Applicable special notes (Specify )

(2) Special items and processes do not apply

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

(1) Non-digital (Specify )

(2) Digital Data (Native CAD Models, Drawings, and PDF)

(3) Other (Specify )

APPENDIX B

ASME Y14.100 TAILORING CHECKLIST – SHEET 20

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

(1) Parts Lists

(a) Integral

(b) Separate

(c) Contractors option

(2) Application List (on drawing)

(3) Data Lists

(4) Index Lists

(5) Indentured Data List

(6) Wire List (as needed)

(7) Other (Specify )

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

(1) 3rd Angle

(2) 1st Angle

R. Language (Choose one )

(1) English required

(2) Other (Specify )

S. Applicability of Appendices

(1) Appendix B

(a) as detailed herein

(b) as modified

(2) Appendix C

(a) as detailed herein

(b) as modified

(3) Appendix D

(a) as detailed herein

(b) as modified

(4) Appendix E

(a) as detailed herein

(b) as modified

APPENDIX C

image3.png image4.png image5.png image40.png image6.png image60.png image7.png image8.png image9.png image10.png image11.png image12.png image13.png image14.png image15.png image16.png image17.png image18.png image19.png image20.png image19.emf image20.emf image21.emf image22.jpeg image1.png image2.png