CDRL_A001_Product_Drawings-Models_and_Associated_Lists.pdf

PR: FD2060-19-30512 PWS REVISION: 0

Distribution Statement: C

DEPARTMENT OF THE AIR FORCE

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE GEORGIA

2019/02/15

MEMORANDUM FOR AFMC AFLCMC/WN-SEV

ATTENTION: Natalia Spangenberg

FROM: AFLCMC/LZPEM

285 Cochran Street Robins AFB GA 31098-1669

SUBJECT: Response to Data Call, This document defines the tasks associated with the procurement of modernize drawings/Technical Data Packages (TDPs) for equipment managed by the Support Equipment and Vehicles (SE&V) Program Office located at Robins AFB, GA. As described by the PWS and purchase request FD2060-19-30512.

1. Performance work statement (PWS) has been reviewed by this office. Request the PWS for Technical Data Package (TDP) Modernization be amended as follows:

4.3 Engineering data. When a TDP is required by a task order, the Contractor shall develop/produce/maintain and deliver a TDP that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s).

This shall include software and all test requirement documentation data required to test systems, subsystems and/or components. Vendor Item Control Drawings per ASME Y14.24 shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, 3D data, Gerber data, and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights excluding existing proprietary data. The TDP delivery and format shall be in accordance with CDRL A001. (A001, DI-SESS-81000E/T, Product Drawings/Models and Associated Lists).

One Government directed revision per drawing is allowed. The Contractor’s final product shall be 100% accurate and comply with all applicable CDRLrequirements.

4.3.1 Model-based TDP (MTDP). When requested in an individual task order, the Contractor shall provide a Model-based TDP for the respective system, subsystem, assembly, subassembly, or part pertaining to SE&V equipment. Items with an existing TDP shall have their TDP revised/updated and converted to a MTDP. All referenced specifications/standards shall be updated to the most current version. If a specification is cancelled, superseded, or obsolete, a replacement specification that meets the design requirements shall be identified and used. Marking notes shall be updated to specifically address the complete marking instructions in MIL-STD-130.

The new MTDP shall also incorporate any outstanding Change Orders against the existing TDP.

Existing TDPs for which the USAF is not the current design activity shall not be revised unless otherwise directed by the Government. The Contractor’s final product shall be 100% accurate and comply with this PWS and all CDRLrequirements.

MTDPs shall consist of a fully annotated (see MIL-STD-31000B) native model created in SolidWorks 2017, a fully annotated 3D iPDF derived from the native model, and a .stp file derived from the native model. The native model file (.sldprt, .sldasm, etc.) created in SolidWorks 2017 shall serve as the master from which all neutral files (e.g. STEP, IGS, JT, STL, PRC, PDF, etc.)

are derived. MTDPs shall not include 2D drawings unless specifically authorized by the Government.

4.3.1.1 3D models. Native 3D models created for items with an existing TDP shall be accurate to, and contain no-less than, the information present in the existing TDP. At a minimum, neutral file formats (e.g. STEP, IGS, JT, STL, PRC, PDF, etc.) shall be produced/producible from all native 3D models with no errors. Native 3D models shall accurately depict the items they define in both product structure, geometry, metadata, and management information. All 3D models shall be mono-detail. For any existing drawings containing insufficient information to fully define the part, a 3D model shall be created that captures the: envelope boundaries of the part or assembly, any interface requirements, and all other information from the originaldrawing.

4.3.1.2 Notes and dimensions. Native 3D models shall be dimensioned and fully annotated (see MIL-STD-31000B) in accordance with ASME Y14.5 and ASME Y14.41. All notes within native 3D models shall be in accordance with ASME Y14.100. However, terms that refer to 2D mediums (e.g. DRAWING, PARTS LIST, etc.) shall be replaced with “MODEL”, as needed, to translate any standard notes for use in the context of 3D models. Instructions within these standards and any articles they reference that are only applicable in the context of 2D drawings are not required.

4.3.1.3 Material. The correct material shall be assigned to all native 3D models. The properties of the assigned material shall be accurate and at a minimum, shall include the density of the material.

4.3.1.4 Standard views. All dimensions, tolerances, notes, lists, tables, figures, annotations, and other information necessary to define an item to the appropriate level shall be presented in various views within the native 3D model in accordance with ASME Y14.41. The default state of a given view shall display all relevant content, and shall be configured to maximize content legibility and minimize empty space. All displayed content may rotate if needed to meet the requirements defined in this document.

The first view shall display all applicable restrictive legends (e.g. Distribution Statement, Export Control Notice, Destruction Notice, Proprietary Statement, etc.), the second view shall display all applicable management information (e.g. management data (see ASME Y14.41), contract number, data rights, and control marking), the third view shall only display the unannotated model in an axonometric position, the fourth view shall display all notes (e.g. general notes, flag notes, special notations, material, treatment, finish, tolerances, mass/weight, units, scale, etc.), and the fifth view shall display the Parts List (PL) or Bill of Materials (BoM) if applicable. The first and second views shall also display the unannotated model in an axonometric position, if space and legibility allow. The fourth view shall also display the model, unannotated or annotated with flag notes, if space and legibility allow. Subsequent view(s) shall display figures, lists, tables, dimensions, annotations, sections, details, product manufacturing information, and any other necessary information.

The first view, which displays restrictive legends, shall function as the default view for the model and shall display when the model is initially opened. All views shall be identified with a name that corresponds to the view’s content and/or perspective, and an alphanumeric prefix that corresponds to the view order (e.g. 1-Restrictive Legends, 2-Management Information, 3- Axonometric, 4- Notes, 5-Parts List, 6-Exploded, 7-Figure 1, 8-Datums, 9-Section A 10-Gear Dimensions, etc.). It may not be possible to change the identification of the default view, in which case, the default view is excluded from the view identificationrequirements.

4.3.1.5 Assemblies. All native 3D models of assemblies shall accurately reflect true-to-life functional and interface constraints to the fullest extent possible. Exploded views shall be presented in all native 3D models as necessary to clearly identify all subcomponents within a given assembly. The functional motion of a given assembly shall be represented in that assembly’s native 3D model unless otherwise directed by the Government. For example, if an assembly’s function requires motion (e.g. springs, bearings, gears, linkages, etc.), the motion shall be represented in the native 3D model either by animation or user interaction. The functional motion of a given sub-assembly shall be represented in the native 3D model of the next-higher assembly as well, continuing to the top level assembly.

When modeling assemblies, priority shall be given to depicting an accurate product structure with the native 3D model’s model tree, unless otherwise directed by the Government. For example, assemblies shall not be modeled as single entities (merged or unmerged) to better represent weldments, as this would result in the assembly being incorrectly represented in the model tree as a piece-part with no subcomponents/subassemblies. All PLs/BoMs shall be integrated with their corresponding native 3D model and shall be displayed in the model’s fifth view (see 4.3.1.4).

PLs/BoMs shall not exist as separate documents and shall not be separately revisable from their native 3D model.

4.3.1.5.1 Parts List/Bill of Materials Integration. When converting an existing TDP with a separate PL/BoM to an MTDP, the following procedure shall be followed to integrate the PL/BoM with the native 3D model. Both the existing PL/BoM and Drawing/Model shall be revised and shall readily display the following note: THIS DATASET HAS BEEN INTEGRATED WITH <identify corresponding integrating dataset>, SEE <identify integrated MTDP> REV: <revision ID of integrated MTDP> FOR INTEGRATED DEFINITION. The integrated MTDP shall be created with a Revision ID, one increment higher than the highest revision between the revised PL/BoM and Drawing/Model. The MTDP shall be identified with the base Document/Drawing

Number, Dataset ID, and Title (see ASME Y14.100 and 4.3.1.11) of the existing Drawing/Model.

The existing PL/BoM and Drawing/Model shall no longer be updated or revised. Below are examples of the previously described procedure:

Existing TDPs:

Drawing: 123ABC CAGE: 98752 Rev: B PL: 123ABC CAGE: 98752 Rev: -

Revised TDPs and Integrated MTDP:

Drawing: 123ABC CAGE: 98752 Rev: C PL: 123ABC CAGE: 98752 Rev: A MTDP: 123ABC CAGE: 98752 Rev: D

Revised Drawing Note:

THIS DATASET HAS BEEN INTEGRATED WITH PARTS LIST 123ABC CAGE: 98752, SEE

123ABC CAGE: 98752 REV: D FOR INTEGRATED DEFINITION.

Revised PL Note:

THIS DATASET HAS BEEN INTEGRATED WITH DRAWING 123ABC CAGE: 98752, SEE

123ABC CAGE: 98752 REV: D FOR INTEGRATED DEFINITION.

Drawing: DWG123ABC CAGE: 98752 Rev: B PL: 123ABCPL CAGE: 98752 Rev: C

Drawing: DWG123ABC CAGE: 98752 Rev: C PL: 123ABCPL CAGE: 98752 Rev: D MTDP: 123ABC CAGE: 98752 Rev: E

Revised Drawing Note:

THIS DATASET HAS BEEN INTEGRATED WITH 123ABCPL CAGE: 98752, SEE 123ABC

CAGE: 98752 REV: E FOR INTEGRATED DEFINITION.

Revised PL Note:

THIS DATASET HAS BEEN INTEGRATED WITH DWG123ABC CAGE: 98752, SEE

123ABC CAGE: 98752 REV: E FOR INTEGRATED DEFINITION.

Model: 123ABC-3D CAGE: 98752 Rev: H BoM: 123ABC CAGE: 98752 Rev: W

Model: 123ABC-3D CAGE: 98752 Rev: J BoM: 123ABC CAGE: 98752 Rev: Y MTDP: 123ABC CAGE: 98752 Rev: AA

Revised Model Note:

THIS DATASET HAS BEEN INTEGRATED WITH BOM 123ABC CAGE: 98752, SEE

123ABC CAGE: 98752 REV: AA FOR INTEGRATED DEFINITION.

Revised BoM Note:

THIS DATASET HAS BEEN INTEGRATED WITH 123ABC-3D CAGE: 98752, SEE 123ABC

CAGE: 98752 REV: AA FOR INTEGRATED DEFINITION.

4.3.1.6 Applied items and non-geometric models. Applied items, also called bulk items, are items that are applied to parts and/or assemblies, rather than installed. Applied items usuallyexist in a non-solid form that may or may not cure to a solid after application. Common examples of applied items include lubricants, adhesives, and coatings. Due to their inherit nature and/or method of application, geometry may not be applicable when modeling such items. When geometry is not applicable, a native 3D model with no geometry (non-geometric) shall be created for the subject item, unless otherwise directed by the Government. Also, with the exception of 3D iPDFs, neutral files shall not be created from non-geometric native 3D models, unless otherwise directed by the Government.

4.3.1.7 Multiple configurations. Items with multiple configurations, often called part families or tabulated parts, are groups of items with common properties and features that differ across variations of a given item. Examples of common differences between part family members are:

variations in color/material, inclusion/omission of simple features and/or subcomponents, variations in size of common features, and mirrored geometry. Part families consist of a parent and children, where the parent serves as the generic, and each child represents a configuration. All family members are defined in the same document/dataset and share a base PIN. For example, if parent part ABCDEF has two children: ABCDEF-1 and ABCDEF-2, ABCDEF is the generic, ABCDEF-1 and ABCDEF-2 are the configurations, and “ABCDEF” is the base PIN. Part family members are not separately revisable from one another.

Only one native 3D model file shall be created for a given part family, and the customary tools/procedures corresponding to the respective native CAD software shall be utilized to create all family members within the same file. The appropriate 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. Children shall not be created from existing children within a native 3D model, often called multilevel or generational families. Part families modeled as described above are still considered mono-detailed and are similar to tabulated mono-detail drawings described in ASME Y14.24.

4.3.1.7.1 Multi-detail and inseparable assemblies. Items that are not similar 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 converting an existing TDP that defines multiple items (e.g. multi-detail drawing, inseparable assembly drawing, etc.) to an MTDP, it may be necessary to create separate MTDPs for the individual items defined in the existing TDP. In such cases, the PIN of an item requiring a separate MTDP shall serve as the new MTDP’s Document Number. New separate MTDPs shall also have the same Original Design Activity (ODA) as their existing TDP. The existing TDP shall be updated to avoid conflict with the content of the new separate MTDP(s) (e.g. removal of technical content that is now present in the new MTDP, changing basic dimensions that are now present in the new MTDP to reference dimensions, etc.).

4.3.1.8 Reference models. 3D models that do not serve as the official definition of a subject item are called “reference models”. Reference models shall be created for items when an official 3D model: cannot be obtained from the subject item’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 data that officially defines the respective item, and are most commonly needed for: items defined by industry or military standards, commercial-off-the-shelf (COTS) items, items that must be modeled with different geometry/properties for use in a specific context (e.g. assemblies, contracts, etc.), and subcomponents that do not have assigned PINs and are only defined at the assembly level. Reference models shall accurately depict items to the level of detail needed for the required context(s) and shall be devoid of notes that communicate technical information. Reference models shall not be annotated, and only views one through four defined in 4.3.1.4 are required. All requirements in 4.3.1.3 shall also apply. Derived neutral files shall not be created from reference models.

All reference models shall have the following note, referencing the article(s) that serves as the official definition for the subject item: “REFERENCE MODEL: SEE <REFERENCE> FOR OFFICAL DEFINITION OF THE SUBJECT ITEM.”, where <REFERENCE> is the identification number(s) of the referenced article(s).

Examples:

REFERENCE MODEL: SEE NASM39086 FOR OFFICAL DEFINITION OF THE SUBJECT

ITEM.

REFERENCE MODEL: SEE 201646960 CAGE: 98752 FOR OFFICAL DEFINITION OF THE

SUBJECT ITEM.

REFERENCE MODEL: SEE 201646968 CAGE: 98752 AND 201646968PL CAGE: 98752 FOR

OFFICAL DEFINITION OF THE SUBJECT ITEM.

REFERENCE MODEL: SEE ASME Y14.41-2012 FOR OFFICAL DEFINITION OF THE

SUBJECT ITEM.

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

PIN | ODA_CAGE | MDA_CAGE | CONTEXT_ID | INSTANCE_PREFIX

When a PIN is not applicable for a given reference model and would normally be left blank, the PIN shall be populated with the same value as the DOCUMENT_NUMBER. Below are examples for correctly populating these fields for reference models created by the USAF for PIN:

MS20995C20; a wire defined by industry standard NASM20995.

Reference model with multiple configurations:

Generic:

NASM20995 | 80205 | 98752

Configurations:

MS20995C20 | 80205 | 98752

MS20995C32 | 80205 | 98752

Reference model for wire with different geometry/properties for use in PIN: 201646968 CAGE:

98752 (The Original Design Activity (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. However, this is an extremely rare occurrence and is usually unnecessary.):

MS20995C20 | 80205 | 98752 | 201646968

MS20995C20 | 80205 | 98752 | 201646968_98752

MS20995C20 | 80205 | 98752 | 201646968_19200

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

4.3.1.9 3D Intelligent PDFs (3D iPDFs) 3D iPDFs shall be created from all native 3D models, excluding reference models. With the exception of elements intrinsic to the 3D iPDF (i.e. title block, logo, headings, frame, etc.), all content represented in the 3D iPDF shall be derived from and match the content of the corresponding native 3D model. All 3D iPDF content shall be digitally text searchable to the fullest extent possible. The Contractor shall utilize the latestUSAF 3D iPDF template and Anark software to create 3D iPDF. The USAF 3D iPDF template shall not be modified unless otherwise directed by the Government. The Contractor shall also provide all supporting files (e.g. Anark recipes) and documentation necessary to convert the delivered native 3D models to the delivered 3D iPDF. The supporting files and documentation shall be provided to the Government with unlimited rights.

4.3.1.10 File names.

4.3.1.10.1 USAF native files. All native files under the design control of the USAF that are not reference models or format/template files, shall follow the standard namingconvention:

Document Number_ODA CAGE_Title.xxx

Example:

201646968_98752_USAF LOGO.asm

4.3.1.10.2 Reference model files. All reference model files shall follow the standard naming convention:

PIN_ODA CAGE_MDA CAGE_Context ID_Instance Prefix_Title.xxx

Examples:

MS20995C20_80205_98752_201646968_AFT_WIRE.prt MS20995C20_80205_98752_WIRE.prt

If a field is not applicable, then it shall be left blank and extra separators removed, as shown in the second example above. If filename size restrictions prevent population of all fields, then the following actions shall be taken in the order presented until an acceptable filename iscreated:

1. Abbreviate/Shorten Title

2. Remove Title

3. Remove MDA CAGE

4. Remove ODA CAGE

5. Shorten Instance Prefix

6. Shorten Context ID

If these actions still result in an invalid filename, the modeling organization shall contact the Government for direction on how to name the file.

4.3.1.10.3 Derived neutral files. All filenames for derived neutral files shall match their corresponding native file’s name, but shall also include the Revision ID before theTitle:

Document Number/PIN_ODA CAGE_Revision ID_Title.xxx

Examples:

201646968_98752_-_USAF LOGO.stp 201646968_98752_A_USAF LOGO.stl 201646968-2_98752_A_USAF LOGO.igs 201646968_98752_B.pdf

However, if a neutral file is created from a native file for a single child in a part family, as described in 4.3.1.7, then the PIN shall be used instead of the Document Number for the first field, as shown in the third example above. The Title shall be abbreviated/eliminated as needed to satisfy file name length restrictions, as shown in the fourth example above.

4.3.1.10.4 Other files. The naming convention used for files not under the design control of the USAF shall be at the discretion of the current design activity, subject to the approval of the Government. However, all native CAD files that define items shall include the Document Number/PIN, filenames for derived neutral files shall include the Document Number/PIN and Revision ID, and filenames for format/template files shall include the ODA CAGE code assigned to the respective file. All filenames shall be unique with respect to theODA.

4.3.1.11 Metadata. The following table lists metadata fields that shall be present within all native 3D models.

TABLE III. Metadata Fields Name Type Format/Values Description USAF_TEAMCENTER_ITEM_TYPE String CAD Template

Master Part Reference Model TDP Document

The item type of the dataset in the USAF’s Teamcenter system.

PIN String All Uppercase Part or Identifying Number (See ASME Y14.100).

DOCUMENT_NUMBER String All Uppercase Drawing/Document Number (See Y14.100) or Dataset ID (See ASME Y14.41).

DOCUMENT_TYPE String 3D Model Always "3D Model".

ODA_CAGE_CODE String Five characters

All uppercase CAGE code of the original design activity.

ODA_NAME String Name of the original design activity.

ODA_ADDRESS String Address of the original design activity.

TITLE String All Uppercase Drawing/Dataset title (See ASME Y14.100 and ASME Y14.41) CDA_CAGE_CODE String Five characters

All uppercase CAGE code of the current design activity.

CDA_NAME String Name of the current design activity.

CDA_ADDRESS String Address of the current design activity.

MDA_CAGE_CODE String Five characters

All uppercase CAGE code of the reference model’s original design activity.

CONTEXT_ID String All Uppercase ID of the context the reference model was specifically created for (e.g. contract number, next higher assembly PIN, etc.).

INSTANCE_PREFIX String All Uppercase ID needed to differentiate reference models of the same item created for the same context.

Name Type Format/Values Description REVISION_ID String All Uppercase ID of the revision (e.g. -, A, MZ, 1, 3.2, 1A, B4, etc.)

REVISION_DATE String/

Date ISO 8601 extended format Date of the revision.

REVISION_DESCRIPTION String Description of what changed in the revision compared to the previous revision.

REVISION_APPROVAL String Name of the person who approved the revision.

SECURITY_LEVEL String Confidential Secret Top Secret Unclassified

Security level of the dataset.

DATA_RIGHTS String Government Purpose Limited Negotiated Unlimited

The data rights the government has to the dataset.

DISTRIBUTION_CODE String A B C D E F

The distribution code assigned to the dataset.

EXPORT_CONTROLLED Boolean Indicates whether or not the dataset has an export control notice.

FOREIGN_SECURE Boolean Indicates whether or not the export control notice contains an ITAR or EAR statement?

CONTRACT_NUMBER String All Uppercase Contract Number that the dataset was created under.

CONTROL_MARKING String All Uppercase Control drawing/model type (e.g. vendor item control, source control, etc.) (See

ASME Y14.24).

CRITICAL_SAFETY_ITEM Boolean Indicates whether or not the dataset depicts a critical safety item (See ASME Y14.100).

CRITICAL_SAFETY_PROCESS Boolean Indicates whether or not the dataset depicts a critical safety process (See Y14.100).

ELECTROSTATIC_SENSITIVE_DEVICE Boolean Indicates whether or not the dataset depicts an electrostatic sensitive device (See

ASME Y14.100).

ENVIRONMENTAL_IMPACT Boolean Indicates whether or not the dataset depicts an entity with adverse environmental impact (See ASME Y14.100).

ENVIRONMENTAL_STRESS_SCREENING Boolean Indicates whether or not the dataset depicts an item that requires environmental stress screening (See ASME Y14.100).

HARDNESS_CRITICAL_ITEM Boolean Indicates whether or not the dataset depicts a hardness critical item (See ASME Y14.100).

HARDNESS_CRITICAL_PROCESS Boolean Indicates whether or not the dataset depicts a hardness critical process (See ASME Y14.100).

HAZARDOUS Boolean Indicates whether or not the dataset depicts a hazardous entity (See ASME Y14.100).

INTERFACE_CONTROL Boolean Indicates whether or not the dataset defines or controls an interface to a system (See

ASME Y14.100).

OBSERVABLE_CRITICAL_ITEM Boolean Indicates whether or not the dataset depicts an observable critical item (See ASME Y14.100).

OBSERVABLE_CRITICAL_PROCESS Boolean Indicates whether or not the dataset depicts an observable critical process (See ASME Y14.100).

OZONE-DEPLETING CHEMICAL Boolean Indicates whether or not the dataset depicts an ozone-depleting chemical (See ASME Y14.100).

OZONE-DEPLETING SUBSTANCE Boolean Indicates whether or not the dataset depicts an ozone-depleting substance (See ASME Y14.100).

MODELED_NAME String Name of modeler.

MODELED_DATE String/

Date ISO 8601 extended format Date modeler approved dataset.

CHECKED_NAME String Name of checker.

CHECKED_DATE String/

Date ISO 8601 extended format Date checker approved dataset.

ENGINEERING_NAME String Name of engineering reviewer.

ENGINEERING_DATE String/

Date ISO 8601 extended format Date engineering reviewer approved dataset.

MANUFACTURING_NAME String Name of manufacturing reviewer.

MANUFACTURING_DATE String/

Date ISO 8601 extended format Date manufacturing reviewer approved dataset.

CORROSION_NAME String Name of corrosion reviewer.

CORROSION_DATE String/

Date ISO 8601 extended format Date corrosion reviewer approved dataset.

SUPPLY_CHAIN_NAME String Name of supply chain reviewer.

SUPPLY_CHAIN_DATE String/

Date ISO 8601 extended format Date supply chain reviewer approved dataset.

QUALITY_NAME String Name of quality reviewer.

QUALITY_DATE String/

Date ISO 8601 extended format Date quality reviewer approved dataset.

APPROVED_NAME String Name of approver.

APPROVED_DATE String/

Date ISO 8601 extended format Date approver approved dataset.

USAF_AUTHENTICATION_NAME String Name of USAF authenticator.

USAF_AUTHENTICATION_DATE String/

Date ISO 8601 extended format Date USAF authenticator approved dataset.

USAF_RELEASE_NAME String Name of USAF release authority.

USAF_RELEASE_DATE String/

Date ISO 8601 extended format Date USAF release authority approved and released dataset.

REFERENCE_* String All Uppercase ID of any article referenced in the dataset.

(When more than one reference is used, append “_*” to the name where a number or letter is substituted for “*”.)

REFERENCE_*_CAGE String Five characters All uppercase

CAGE code of the original design activity of a corresponding reference. (Leave blank if not applicable for a given reference.)

UDF_USAF_CDA Boolean Indicates whether or not the USAF is the current design activity.

UDF_ACCURATE_MODEL_TREE Boolean Indicates whether or not the model tree of an assembly model accurately depicts the assembly’s product structure (e.g. parts list or bill of materials).

4.3.2 Verification and validation. All models generated from existing 2D drawings shall be validated through a line check comparison conducted between the original drawing and the new model’s axonometric and/or orthographic views unless otherwise directed by the Government. A static interference analysis shall be accomplished at each assembly level to ensure no dimensional interferences occur. A functional interference analysis shall also be accomplished at each assembly level as directed by the Government to ensure no dimensional interferences occur. In addition, one of the following options shall be pursued for final verification of the MTDP at the discretion of the Government:

a. Reverse First Article - the new MTDP shall be used to dimensionally check existing parts made to the previous TDP. All discrepancies shall be identified andresolved.

b. New Production to Previous Drawing Check - the new MTDP shall be used to create a new part and checked against the previous TDP.

c. New Production to Functional Check - the new MTDP shall be used to create a new part which shall be substituted into an existing system for a functional and/or live fire check out.

d. Rapid Prototyping - the new MTDP shall be used to create a rapid prototype of the new part and compared dimensionally or through a functional check to an existingpart.

As MTDPs are created and problems are found that prevent the MTDPs from conforming to the exact requirements of the original drawing, each issue and resolution shall be documented and reported to the Government. MTDPs shall not be accepted until they have been reviewed and approved by the Government for compliance with the requirements of this PWS andDI-SESS-81000E/T.

4.3.3 Engineering Data Guidance Conference: The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

(A002, DI-ADMN-81249B, Conference Agenda; A003, DI-ADMN-81250B, Conference Minutes)

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

e. The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Note: Guidance Conference may be held in conjunction with other meetings or conferences.

4.3.4 In-Process Review (IPR) of the TDP: The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included inthe TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR).

Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), These shall consist of the Native, Neutral, Word Searchable PDF, HPGL, Metadata Spreadsheet, BOM, Gerber Data, and Software/memory Device Data. Additionally, the contractor shall submit sample solid modeling data in SolidWorks 2017 and a fully annotated 3D iPDF derived from the solid model with an embedded .stp file also derived from the solid model.

The contractor shall notify AFLCMC/LZPEM a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility.

(A004, DI-ADMN-81249B, Conference Agenda; A005, DI-ADMN-81250B, Conference Minutes)

4.3.5 Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.3.6 Engineering Data Updates and Revisions: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with thefollowing:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or atintervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

2. Request the Contracting Officer (CO) assure that the following actions occur:

a. Insure that each solicitation and contract is structured IAW DFARS 227-7103-1(b)(3)and CHAPTER 5 of DoD5010.12-M as noted:

(1) Paragraph C5.2.1 states “The contractor will have to prepare certain data as a natural consequence of contract performance. Design, development, testing, andproduction tasks will generate certain data, whether or not a requirement is identified in a DD Form 1423-1and delivery is requested. This factor is the basis for what is called the "over and above concept" for pricing data; the price paid for a data item will be based on what it costs the contractor to furnish that item, over and above the costs the contractor would incur if it were not required at all.”

(2) Para. C5.1.2 states ".....contracting officers, program managers, and technical data management personnel are encouraged to require contractors to separately priceeach requirement for technical data."

b. Request the contracting office review the solicitation and resulting contract for compliancewith the following clauses in accordance with DFARS 227.4:

DFARS TITLE

227.7102 Commercial items, components, or processes

227.7102-1 Policy

227.7102-2 Rights in technical data

227.7103-1 Policy

227.7103-2 Acquisition of technical data

227.7103-3 Early identification of technical data to be furnished to the Government with restrictions on use, reproduction or disclosure

227.72 Rights in computer software and computer software documentation

227.7202 Commercial computer software and commercial computer software documentation.

(1). Request that the following clauses are incorporated into the contract:

252.227-7013 Rights in Technical Data - Non Commercial Items (Per 227.7103-6(a)

252.227-7014 Rights in Noncommercial Computer Software and Noncommercial

Computer Software Documentation. (Per 227.7203-6(a) (1))

252.227-7015 Technical Data – Commercial Items

252.227-7016 Rights in Bid or Proposal Information

252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions

252.227-7019 Validation of Asserted Restrictions – Computer Software

252.227-7030 Technical Data - Withholding of Payment

252.227-7037 Validation of Restrictive Markings on Technical Data

252.227-7028 Technical Data or Computer Software Previously Delivered To the Government

252.246.7001 Warranty of Data

52.227-21 (a and b) FAR Clause - Technical Data, Declaration, Revision, and

Withholding of Payment- Major Systems

c. Request that a copy of the solicitation/contract be forwarded to AFLCMC/LZPEM.

3. Request the Contracting Officer (CO) prohibit the use of Single Process Initiatives (SPI) to include Core Business Manuals (CBM) or any common processes which pertain to the development and delivery of a Technical Data Package(TDP):

Request the CO assure that the contract does not invoke the use of SPI's, CBMs, or any internal contractor common processes in lieu of ASME Standards and Military Standards which pertain to the development and delivery of a TDP. The SPI’s and CBM’s consolidate or eliminate necessary specifications and standards in TDP’s thus prohibiting future competitive acquisitions.

4. The data required by the tasking wording and DD Form 1423-1 will be utilized for logistic support purposes, to include competitive re-procurement in the acquisition of spares. This datawill be utilized by logistics personnel, to include data managers, system engineers, equipment specialists, item managers and logistics managers. If this data is not procured, logistic support may be adversely affected. Requirements for engineering data are driven by the following:

a. AFI 63-101/20-101 (07 March 2013 Incorporating Changes, 16 September 2016), paragraph 6.12 states:

6.12. Data and Data Rights. The PM shall assess long term data and data rights requirements and corresponding acquisition strategies prior to initiating a RFP to acquire systems, subsystems, or end-items to ensure they provide for rights, access, or delivery of data that the Governmentrequires for systems sustainment and to maintain competition throughout the life cycle. The PM shall address the data rights strategy including the rationale for acquisition and\or non-acquisition of data and data rights at milestones, ASPs, and reviews and shall document the strategy in the Technical Data Rights Strategy and associated data planning documents. The Technical Data Rights Strategy is integrated within the AS and is required for all ACAT programs. Source selections shall consider Government rights to data and include pricing options that correspond to the data and data rights recommended as part of the data strategy. The burden of proof that data is proprietary lies with the contractor. If not acquiring technical data, computer software licenses, or associated intellectual property rights necessary for organic support, a summary of the business case analysis justifying that decision must be approved by the MDA. The PM shall obtain legal counsel when addressing Data Rights or Intellectual Property issues. The PM shall review the government requirement for technical data throughout the life cycle of the system.

6.12.1. The PM shall ensure the program data rights strategy, including the performance work statement (PWS) or SOW for development, production, deployment, and sustainment (for all applicable phases) includes appropriate data rights requirements, access, and necessarydeliverables, or options for data and equipment deliverables required to support:

6.12.1.1. Organic source of repair and/or supply decisions.

6.12.1.2. Government Core depot maintenance capability requirements.

6.12.1.3. Expeditionary logistics footprint requirements.

6.12.1.4. Engineering data requirements needed for such activities as OSS&E assurance, integrity programs, sustaining engineering, reliability management, and configurationmanagement.

6.12.1.5. Technical orders (TOs).

6.12.1.6. Re-procurement/modification/upgrade.

6.12.1.7. Demilitarization/Disposal.

6.12.1.8. Open architecture.

6.12.1.9. Cybersecurity strategies.

6.12.1.10. Technology refreshment or enhancement.

6.12.1.11. Training and training program information.

6.12.1.12. Spare parts procurement

6.12.1.13. Testing and Evaluation

6.12.1.14. Intelligence Mission Data production

6.12.1.15. Contractor Logistics Support

b. AFI 23-101 (12 December 2016) Section 2K, Spare Parts Breakout Program, paragraph 2.11.2.3 states AFMC will:

(1) 2.11.2.3.3. Determine the complete data needs, including re-procurement data for inclusion in contracts.

(2) 2.11.2.3.4. Give written notification, with rationale, to affected organizations when contracts do not include data requirements.

(3) 2.11.2.3.5. Conduct data calls and in-process reviews to ensure that correct and complete data requirements, including re-procurement data, appear in the Engineering, Manufacturing and Development (EMD) or production contract.

(4) 2.11.2.3.6. Identify, select, and, develop data item descriptions for inclusion in the EMD or production contract.

(5) 2.11.2.3.7. Make sure that contracts properly define data requirements and manage the acquisition according to AFI 21-103, Equipment Inventory, Status and Utilization Reporting,

(6) 2.11.2.3.8. Schedule periodic engineering and procurement data reviews to ensure that the contractor is complying with contractual data requirements in supporting the AFSPBP.

These reviews should coincide with existing engineering or datareviews.

c. The Competition in Contracting Act (CICA) of 1984 requires the Government to address and plan for competition of future acquisitions and of spares during acquisition of the system. The law (10 USC 2304(f)(4)) states, “In no case may the head of an agency enter into a contract for property or services using procedures other than competitive procedures on the basis of the lack of advance planning or concerns related to the amount of funds available to the agency for procurement functions.”

This does not mean we must buy re-procurement engineering data (Product Drawings/Models and Associated Lists); However, we must address, support, and document any decision not to buy this engineering data.

d. For these reasons, do not make any changes to the DD Form 1423-1 originated by AFLCMC/LZPEM without coordinating with WilliamKnight.

5. Data requirements are set forth on DD FORM 1423-1 attached hereto.

6. Please reference LZPEM’s control number 2019 - 24 on all correspondence relating to this subject. Point of contact is William Knight 472-3066.

X Ken McKinley signing for

Signed by: MCKINLEY.NORMAN.K.1229939706 MICHAEL E. WILLS, Chief Engineering Data Management, Acquisition and Inspection

AFLCMC/LZPEM

Attachment:

DD FORM 1423-1, Product Drawings/Models And Associated Lists, 2019/02/15 cc: AFLCMC/WNZ / Natalia Spangenberg

AFLCMC/WNKAC/ Oya Harrison

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved QMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188), Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP XXXX TM OTHER

D. SYSTEM / ITEM E. CONTRACT / PR NO. F. CONTRACTOR

Support Equipment and Vehicles (SE&V) FD2060-19-30512

1. DATA ITEM NO. 2. TITLE OF DATA ITE 3. SUBTITLE

PRODUCT DRAWINGS/MODELS AND ASSOCIATED LISTS

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

DI-SESS-81000E/T PARA: 4.3 AFLCMC/LZPEM

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DI TRIBUTION

DD QRTLY SEE BLK 16

8. APP CODE SEE BLOCK 16 11. AS OF DATE 13. DATE OF

SUBSEQUENT

SUBMISSION

a. ADDRESSEE

b. COPIES

FINAL

A SEE BLOCK

SEE BLK 16 Draft Reg Repro

16. REMARKS AFLCMC/LZPEM

285 Cochran Street

1. Air Force drawings 9626025 rev G, 9579776 rev N and 9579777 rev B (CAGE 98752) are a part of this CDRL ROBINS AFB, GA.

A copy of the drawings may be requested through the Procurement Contracting officer. 31098-1669

2. METADATA SHALL BE IN ACCORDANCE WITH 9579776 PARAGRAPH 10 OPTION

ONE

3. Please reference EDATS control number2019 - 24 on all correspondence related to this effort.

PAPER COPY

SEE CONTINUATION SHEETS DIGITAL DATA 1 1 1

Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). Reference paragraph 7.1 of DI-SESS-81000E.

(CLASSIFIED)

DIGITAL 1

15. TOTAL 2 0 2

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

William Knight 2019/02/15

DD Form 1423-1, Feb 2001 STRAWMAN Revision 3 Dec 2014 PAGE 1_ OF 9 PAGES EDATS 2019 - 24

A001

CONTINUATION OF DD FORM 1423-1 (DI-SESS-81000E/T) Dtd 2019/02/15, EDATS 2019 - 24

BLOCK 4: DI-SESS-81000E is tailored as follows:

Requirements: (the below paragraph numbering corresponds with the numbering in the DID)

1. Reference Documents. Delete paragraph 1. in its entirety and replace with “1. Reference

Documents. The documents apply as cited in the DD Form 1423-1 and continuation sheets. Unless otherwise noted, the latest revision of the ASME Standard at the time of solicitation shall apply.”

3. Format. Delete in its entirety and replace with “3. Format. Product Drawings/Models and

Associated Lists shall be in the format as specified on this DD Form 1423-1 and continuation sheets, and shall meet the requirements of ASME Y14.1."

4. Content. Delete in its entirety and replace with “4. Content. Product Drawings/Models and

Associated Lists shall conform to the requirements of ASME Y14.100-2017, Appendix B, sections B6 through B9.1 and Appendices C,D, E, and F in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41. They shall document directly or by reference the following (items a through q), as applicable:”

6. CAGE code. Delete “TDP Option Selection Work Sheet incorporated in the contract or purchase order.” and replace with “DD Form 1423-1 and continuation sheets.”

7. Selection of drawings. Delete “The TDP Option Selection Work Sheet incorporated in the contract or purchase order will specify whether the contractor or the Government is responsible for selecting the types of drawings and associated lists.” and replace with “The contractor shall comply with ASME Y14.24, Types and Applications of Engineering Drawings”.

BLOCK 7:

“D”—Inspection is at destination and is to ensure this product meets this CDRL and its tasking document.

Shipping list must accurately reflect the shipped product.

“D”—Acceptance is at destination. Acceptance of final data will be by approval of the Engineering Data Management Specialists.

BLOCK 9:

DISTRIBUTION STATEMENT. Distribution statements shall be in accordance with DoD Instruction

5230.24 and included on the first sheet of each drawing near the title block, and shall be as follows:

"DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government Agencies and their contractors (critical technology) (10 September, 2018).

Other requests for this document shall be referred to (AFMC AFLCMC/WNZ)."

EXPORT CONTROL WARNING LABEL. All engineering data shall be marked with Export Control Warning Labels in accordance with DoD Instruction 5230.24, dated August 23, 2012 as follows:

“WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.”

DESTRUCTION NOTICE. Mark documents with one of the following:

a. For unclassified limited documents: “DESTRUCTION NOTICE. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

b. For classified documents: “DESTRUCTION NOTICE. Follow the procedures in DoD 5220.22- M, National Industrial Security Program Operating Manual, Chapter 5, Section 7, or DoD 5200.1R, Information Security Program, Chapter 6.”

BLOCK 10: Revisions/changes to the final delivered data shall be furnished quarterly, commencing the first quarter after destination acceptance of the final reproducible data and continue until the contract is closed. Quarterly updates shall include an updated BOM, reference A.F. Drawing 9579776. Negative reports shall be submitted to AFLCMC/LZPEM.

BLOCK 11: 15 days before end of quarter.

BLOCKS 12 & 13:

1a. SAMPLE SUBMITTALS: As early as possible, but no later than 50% of TDP creation, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), (Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/Memory Device…