Attachment_17_-_Technical_Data_Package.docx

Attachment 17

TECHNICAL DATA PACKAGE

ACV-ATT-02001

Version 1.0

PM AAA

Amphibious Combat Vehicle

DISTRIBUTION A: Approved for public release; distribution unlimited.

Table of Contents

List of Enclosures

Enclosure 1 – JEDMICS PDF Requirements Enclosure 2 – TDP Pricing Sheet Enclosure 3 – Parameter ID and Descriptions

1. SCOPE

This attachment describes the Technical Data Package (TDP) for the Amphibious Combat Vehicle (ACV).

2. APPLICABLE DOCUMENTS

The following documents form a part of the TDP effort to the extent specified herein. Unless otherwise noted, in the event of a conflict between the TDP and the references cited herein (except for related specification sheets) the text of this TDP takes precedence. All second tier and below references cited shall be considered as guidance only. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1. GOVERNMENT DOCUMENTS

MIL-STD-31000 - DEPARTMENT OF DEFENSE, STANDARD PRACTICE, TECHNICAL DATA PACKAGES

(Copies of these documents are available online at http://assist.daps.dla.mil/quicksearch// or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.)

3. REQUIREMENTS

The Contractor shall develop, maintain, deliver, and update as required a complete Technical Data Package (TDP) for the ACV system consisting of Contract Data Requirements List (CDRLs), denoted as TDP on the Form DD-1423s, that provide engineering technical data and Engineering Data for Provisioning (EDFP) to support Operations, Maintenance, Installation and Training (OMIT) of the ACV system throughout its operational life and/or to describe the Form/Fit/Function of all items (systems, subsystems, and hardware/software/firmware components) contained within the ACV system. The Production Level TDP approved at the Physical Configuration Audit represents the complete Product Baseline as managed by the Contractor. Unless otherwise specified herein, the TDP shall conform to the requirements of the latest revision of MIL-STD-31000. The TDP shall be maintained as the complete Product Baseline. The TDP shall be the basis of managing the configuration of the ACV. The TDP is a deliverable, regardless of the level of rights that the Government will receive in that TDP (i.e., with or without the exercise of the option.)

3.1. DEFINITIONS

The following TDP-related definitions apply to this contract.

3.1.1. GENERAL

The Contractor shall provide the technical data having characteristics (e.g., content, format, and delivery medium) necessary for organizational and depot-level maintenance and Type 1 training and development as determined and required by the Government. The Government requirements for such technical data include, but are not limited to, the following:

1. No less information or detail than industry standards, nor less than the Contractor typically requires for the performance of such maintenance or training activities.

2. Additional information or detail necessary for military purposes related to organizational and depot-level maintenance or training systems.

3.1.2. DEPOT-LEVEL MAINTENANCE

Depot-level maintenance includes, but is not limited to, installation, inspection, localization, isolation, disassembly, interchange, repair, reassembly, alignment, checkout and maintenance performed on material requiring repair, major overhaul, or complete rebuild of parts, assemblies, subassemblies, and end items, and including modification, testing, and reclamation. The term “depot-level maintenance” does not include the manufacture of new items.

3.1.3. OPERATION, MAINTENANCE, INSTALLATION, TRAINING

Operation, Maintenance, Installation, and Training (OMIT) is all technical data and EDFP necessary for operation, maintenance, installation, and training purposes (other than detailed manufacturing) pertaining to the ACV system and equipment associated with its life cycle support sustainment. OMIT data includes all technical data required to accomplish Organizational, Intermediate, and Depot levels of maintenance, including Marine Corps Sustainment of the technical data itself.

3.1.4. FORM/FIT/FUNCTION

The terms form, fit, and function are defined below.

1. Form. The shape, size, dimension, mass, weight and other parameters, which uniquely characterize an item.

2. Fit. The ability of an item to interface or interconnect with or become an integral part of another item.

3. Function. The action or actions that an item is designed to perform.

3.1.5. DEPOT-LEVEL MAINTENANCE TECHNICAL DATA

The Contractor shall comprise a complete maintenance related TDP package of all technical data necessary for the Government to perform depot-level maintenance for the entire ACV system and equipment, including all systems, subsystems, and hardware/software/firmware components without exception. This includes technical data necessary for installation and de-installation, and disassembly and reassembly, at the lowest practicable separable level that does not require detailed manufacturing or process information. Examples of technical data that are needed to perform depot-level maintenance include, but are not limited to, the following:

1. Detailed technical data and information regarding all systems.

2. Depot-level maintenance technical data and information regarding all systems, subsystems, and hardware/software/firmware components.

3. Interface Design/Control Documents.

4. Computer software documentation necessary to perform depot-level maintenance on computer programs.

3.1.6. TRAINING SYSTEMS TECHNICAL DATA

Training related TDP items described under Paragraph 3.2.5 of this document shall comprise a complete package of all technical data necessary for the Government to develop new equipment training courses for all the ACV systems, subsystems, and hardware/software components. The Contractor is not required to provide detailed manufacturing or process data.

3.1.7. FORM/FIT/FUNCTION TECHNICAL DATA

Form/Fit/Function related TDP items shall comprise a complete package of all technical data necessary for the Government to understand the physical and functional characteristics of all items (systems; subsystems; and hardware, software, and firmware components) contained within the ACV system and how they interface with one another.

3.2. TECHNICAL DATA PACKAGE

3.2.1. TDP PREPARATION

The TDP shall be prepared in accordance with MIL-STD-31000. The TDP shall contain a technical description of all items suitable for use as a basis for production, installation, modification, engineering support, maintenance, and logistics support of the ACV. The information contained within the TDP shall describe the product design established at the initial Government approved product baseline and include subsequent changes and revisions up to the time of the last submittal. The TDP content shall define the required design configuration or performance requirements, and procedures required to ensure adequacy of item performance. It shall consist of EDFP and applicable technical data such as models, drawings, associated lists, specifications, standards, performance requirements, quality assurance provisions, software and memory device documentation, and packaging details.

3.2.2. UNITS OF MEASURE

The TDP shall use the International System of Units (SI) as the basic unit of measure in accordance with the FED-STD-376, Preferred Metric Units for General Use by the Federal Government and IEEE/ASTM SI 10-2010, IEEE/ASTM American National Standard for Metric Practice.

3.2.3. INDENTURED DATA LISTS

TDP option selection worksheet-product drawings and associated lists identifies in Block 6 (e) a requirement for an indentured data list, (excludes nationally recognized military and industry specifications and standards). This list shall include:

1. A sequence of both part numbers and associated drawing numbers comprising the end item in a lateral and descending family tree/top down breakdown.

2. A top down breakdown of the end item including all lower level items, listing every assembly, subassembly, and part.

3. Every item listed in its relationship to the end item, subassembly, assembly or system of which it is a part.

4. A relationship as shown by means of physical indenture or numeric sequence, with the indenture indicating that the item is a part of the preceding item.

3.2.4. PAINT COLORS WITHIN THE TDP

The Contractor shall develop the TDP in such a manner as to allow flexibility in specifying the paint. The Contractor shall not assign unique part numbers for components based solely on specified paint color. The Contractor shall include a paint/finish drawing at a high level in the TDP in order to allow the Government to order different exterior colored vehicle lots without affecting component drawings and part numbers.

3.2.5. TDP ITEMS

The following CDRLs in this contract constitute the TDP.

A005, A019, A029, A030, A031, A033, A036, A049, A050, A051, A053, A081, A091, A095, A098, A099, A100, A101, A118, A128, A129, A130, A131, A133, A134

3.3. DATA AND LICENSE RIGHTS AND MARKINGS

3.3.1. LICENSE RIGHTS

Pursuant to the contract clauses and regulations governing rights in technical data (e.g., DFARS Subparts 227.71 and 227.72, and DFARS 227.7202, 252.227-7013, 252.227-7014, and 252.227-7015), the Government is granted unlimited rights in OMIT and form/fit/function data.

3.3.2. TECHNICAL DATA PACKAGE/3D SOLID MODELS/2D DRAWINGS MARKINGS

The 3-D model, including metadata, is the master design record. All subsequent data rendering, drawings, and depictions are derived from this 3-D record. The models and all renderings shall be marked IAW DFARS 252.227-7013, DFARS 252.227-7014 and DFARS 252.227-7015.

3.3.3. SECURITY MARKINGS

The Contractor shall apply the applicable DoD Technical Distribution Statement and Export Control Warning required by DoD Instruction 5230.24 and Directive 5230.25 to all technical data produced or delivered. All statements, notices, and data rights markings 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.3.4. DATA RIGHTS MARKINGS ON TECH DATA DELIVERABLES

In accordance with the DFARS, the Government has unlimited rights to technical data for Form, Fit, Function, Operation, Maintenance, Installation, and Training (FFFOMIT), regardless of who paid for the development of the item(s). The Contractor shall correctly mark and deliver all technical data ordered to include items that are purchased with greater rights from the Contracting Officer-approved Assertions List. Delivered FFFOMIT data shall not contain data rights or other Contractor imposed restrictive legends. If FFFOMIT data is commingled in a model, drawing, or document, with data that is limited or restricted, the Contractor shall mark only the specific portions, sheets, or pages of data subject to the limitation or restriction. The Government will require a distribution statement on all technical data delivered, and, if applicable, an export control warning, in accordance with DODI 5230.24.

3.3.5. ITEM UNIQUE IDENTIFICATION MARKING REQUIREMENT

All items requiring Item Unique Identification (IUID) markings in accordance with DFAR 252.211-7003 (paragraph c) shall incorporate labeling or marking information as part of the TDP in accordance with MIL-STD-130. Applicable 2D CAD drawings and 3D CAD solid model TDP shall include IUID marking information. The IUID information in drawings, solid models and associated lists shall indicate method of marking or labeling, label or plate material composition, data matrix location and orientation and other applicable information in accordance with MIL-STD-130.

3.3.6. VALIDATION OF ASSERTED RESTRICTIONS AND RESTRICTIVE MARKINGS

Nothing in this TDP requirement limits or otherwise affects the parties' rights or obligations specified in DFARS 252.227-7019 or DFARS 252.227-7037.

3.3.7. TECHNICAL DATA OF SUBCONTRACTORS AND SUPPLIERS

The Contractor's obligations in Section 3.0 of this attachment shall apply to all technical data, including all technical data developed, delivered, or otherwise provided by Subcontractors or Suppliers at any tier, and regardless of whether the technical data is or relates to commercial items or noncommercial items. The Contractor shall include these requirements in its subcontracts or other contractual or legal instruments with its Subcontractors or Suppliers at any tier.

3.4. TDP STANDARDS AND BEST PRACTICES

The Contractor shall maintain Product Design Drawings electronic files and formatted in accordance with MIL-STD-31000, ASME Y14.100M, ASME Y14.34M, ASME Y14.35M, and ASME Y14.24M. This shall include the Geometric Dimensioning and Tolerancing (GD&T). Contractor’s CAD solid modeling software application is acceptable. The Government’s preference is PTC Creo Parametric CAD modeling software. Version of CAD modeling software used for CAD data delivery will be agreed upon at the TDP Guidance Conference. The Government will provide CAD PTC Creo Parametric start files and PTC Creo Parametric drawing formats upon request by the Contractor.

3.5. TECHNICAL DATA PACKAGE UTILIZATION

The Contractor shall use the approved Product Baseline with associated TDP for all activities related to the manufacture and assembly of the ACV. The Contractor shall not maintain or utilize a separate TDP for the purposes of production unless specific written approval has been given by the Program Contracting Officer (PCO). Prior to the Physical Configuration Audit (PCA), the Contractor shall incorporate all changes to the vehicle design into the TDP through the Contractor’s Configuration Control Process. After the PCA, the Contractor shall incorporate all changes to the vehicle design into the TDP through the Configuration and Change Management Process described in the Government Configuration Management Plan.

3.6. TDP DELIVERABLE FILE FORMATS

1. Parametric 2D and 3D Native CAD Models. All parts/assemblies’ models (other than for standard hardware) shall be parametric, feature-based, dimensioned and include appropriate tolerances, notes, and metadata attributes. The 3D and 2D CAD models shall be associative. Any change in either the 3D or 2D will be automatically updated in the associated files. All Source Control and Supplier Item Control parts shall be modeled with sufficient information for procurement. All CAD files shall include all metadata attributes per Enclosure (3).

2. Neutral CAD Format. The Contractor shall translate all parametric and non-parametric 3D CAD solid models into an ISO 10303 STEP AP203 ed2 or AP214 format. The STEP Neutral files shall include all metadata attributes sourced from 3D CAD models per Eenclosure (3). (to be provided).

3. Envelope Cosmetic Solid Models. All Military and Industry Standard parts shall be modeled for form, fit and function with sufficient envelope, mounting and mating features. Models shall be sufficient to provide adequate visualization, interface characteristics, accurate weight and center of gravity. Associated drawings are not required to be generated for standard hardware.

4. 2D PDF. All 2D CAD drawings shall be exported to PDF with at least 200 dpi resolution.

3.7. ENGINEERING DRAWINGS, PRODUCT DRAWINGS, AND RECORDS

Detailed subassembly and assembly drawings shall be completely delineated, directly or by reference to other documents, engineering requirements and characteristics such as materials, tolerance methods shall be utilized where applicable per ASME 14.5M-2009. Engineering drawings and associated lists shall at a minimum provide the necessary EDFP, design, engineering, manufacturing, and quality assurance information sufficient to procure or manufacture an item that duplicates the physical and performance characteristics of the original prototype, without additional design engineering effort or recourse to the original design activity.

3.8. REFERENCED DOCUMENTS

The Contractor shall furnish all documents referenced in TDP deliverables as required under Section 5.3 of MIL-STD-31000.

3.9. QUALITY CONTROL

Quality Assurance Provisions (QAP) shall be included on the drawings per Section E of this contract. The QAPs shall note the type and frequency of process/product controls or required test for performance/validation/production control purposes. The Contractor shall verify that all TDP elements open without errors before each delivery.

3.10. DATA MANAGEMENT

3.10.1. FILE NAMING CONVENTION

The Contractor shall use the following file naming convention:

CAGE_Part Number_Nomenclature.filextension (For Example: 19207_12345678_EngineInstallation.pdf)

The Nomenclature may be abbreviated. All files associated with the same Part Number shall have the same filename and the file extension shall be consistent with the file type. For example, associated STEP and PDF files shall have the same filename with extension “.stp” and “.pdf.” respectively.

3.10.2. DATA MAINTENANCE

The Contractor shall provide engineering and technical support services and facilities to prepare and maintain 3-D models, drawings, specifications and other technical data comprising the Product Baseline for the ACV throughout the Contract.

3.10.3. DRAWING NUMBER ASSIGNMENT AND REPORT

All product drawings, including Packaging Content and Kit drawings, produced under this contract or to which the design activity responsibility is transferred to the Government shall be identified with a Government CAGE Code and Government drawing numbers. The Contractor shall request drawing numbers by submitting a written request to the designated Government CM Representative specifying the type and quantity of drawings being produced The Contractor shall request additional blocks of numbers as needed via written request to the Government CM representative. Numbers assigned can be used for all design documentation. The allocation of these numbers shall be reported on a frequency specified on the DD Form 1423.

3.10.4. COMPANY STANDARDS

Company standards are not allowed. Refer to 5.3 of MIL-STD-31000.

3.10.5. VERSION CONTROL

The Contractor shall utilize disciplined version control in managing digital data. The terms version and revision as used herein are interchangeable. Each revision shall be a new master, and the Contractor shall retain all approved revisions (versions) of each document and model representation to provide a traceable history in order to access the correct revision when needed. The content of a document and model revision is fixed once approved. Numerical revisions are not allowed. The Contractor shall ensure that all representations (e.g., hard copy, raster, Adobe PDF, CAD, and STEP, etc.) of a single version or revision of data, delivered to the Government for approval and subsequently maintained by the Contractor for the term of this contract, are identical. The revision history description for the TDP shall cite the applicable Change Request with Change Notice or Change Order number for data revised prior to product baseline.

3.10.6. PRODUCT BASELINE AND CHANGES

The Contractor shall define the documentation required for the Product Baseline to a level of detail commensurate with logistics support requirements and procurement strategies. The Product Baseline documentation shall be in the form of product, material, and process specifications, engineering drawings, military specifications, actual software media, and other technical documentation comprising a complete technical data package for the Configuration Item (CI). The Product Baseline documentation shall prescribe the necessary physical and functional characteristics of the CI and the verifications required to demonstrate required performance. The contractor shall version the Product Baseline and shall update the baseline version as Engineering Change Proposals are approved and implemented.

From PCA and beyond, changes to the Product Baseline shall be processed through the Government’s Configuration and Change Management process via Engineering Change Proposals and are only implemented after authorized by the Government Contracting Officer (CO). 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 as the ERR package deliverable.

3.10.7. ORIGINAL EQUIPMENT MANUFACTURER PART NUMBERS

The Contractor shall utilize the Original Equipment Manufacturers (OEM’s) part number and Commercial and Government Entity (CAGE) Code to identify parts that the Contractor does not manufacture in accordance with MIL-STD-31000. The Contractor shall not re-identify or re-mark Supplier or purchased parts or related TDP with his own part number and CAGE. The Contractor shall not use their numbers for items that can be defined by Government/industry standards or specifications. All components other than standard hardware shall be assigned PINs in accordance with ASME Y14.100. The PIN, in combination with the CAGE, establishes unique identification of items in the TDP. The Contractor’s TDP, including Bill of Materials (BOMs), Drawings, Models, Parts Lists, and reports, shall be consistent in calling out the OEM part number and CAGE as the primary part.

The National Stock Number (NSN) for items may be cited in the TDP in addition to the PIN-CAGE; however, NSNs do not establish unique identification and shall not be cited within the TDP in lieu of the PIN-CAGE.

The Contractor shall investigate and convert all purchased components’ part numbers to OEMs or standard part numbers prior to submitting TDP to the Government. The Contractor may utilize the on-line tool called WEBFLIS (http://www.dlis.dla.mil/webflis/) for researching part numbers, or contact the Defense Logistics Agency (DLA) customer service at: http://www.dlis.dla.mil/cust.asp for assistance with web access, accounts, or assistance in finding part numbers for standard items.

3.10.8. SOFTWARE AND FIRMWARE

The Contractor shall assign software as a part number in the assembly breakdown and Product Baseline, and shall be documented in the TDP by application name, version and description referencing the Contractor software code repository. Firmware shall be assigned as a part number in the assembly breakdown and BOM and shall be documented in the TDP by application name and version.

3.11. PREPARATION AND MANAGEMENT RESPONSIBILITY

3.11.1. DRAWING REVISIONS

Revisions to the TDP shall comply with ASME Y14.35M. TDP elements or sub-elements, when found to be defective and/or rejected as unacceptable by the Government, shall not be permitted for use in formal Government technical audits, logistics conferences, or technical manual final inspection.

3.11.2. CONFERENCES, REVIEWS, AND AUDITS

The Contractor shall host and participate in TDP guidance conferences, in-process reviews, and final technical review for digital data.

3.11.2.1. TDP GUIDANCE CONFERENCE

The Contractor shall host the TDP guidance conference 90 days after Full Rate Production (FRP) Lot 3 Option Award at the Contractor’s facility to discuss in detail the TDP requirements. The Contractor shall discuss their approach for the preparation and management of the TDP. The TDP guidance conference will, as a minimum, include the following discussion topics:

· Identification of contract end items, the TDP elements, and associated management data

· Requirements for TDP elements contained in Statement of Work (SOW), Contract Data Requirements Lists (CDRLs), Data Item Descriptions (DIDs), TDPCR, and applicable specifications and standards

· Quality assurance procedures relating to TDP, including control of subcontractor and vendor TDP elements

· TDP review and inspection requirements and schedules

· TDP delivery requirements and schedules

· Review TDP drafting practices and formats

· Review TDP document numbering systems

· TDP rights marking procedures and policies

· Subcontractors or vendors roles in delivering data under the contract

· Distribution statements marking and control

· TDP configuration management system, including methods for releasing TDP elements, TDP validation requirements, approving TDP, and incorporating changes into the data package

· Organization for developing, releasing, and controlling TDP elements

· Control of TDP elements in digital form, include updates and transfer, and identification of exchange protocols required by the contract

· Review of corrective action procedures to arrive at corrected TDP submittal, as outlined in this TDPCR for documented discrepancies

· Establish most efficient media types and initial sample candidates for in-process review and final submittals

· Review of design disclosure criteria and related interface with design compliance documents

· The Government will identify to the Contractor the Name, Cage Code and address of the Organization that will maintain the drawings. The following will added to the sheet 1 of each drawing

CAD MAINTAINED

CHANGES SHALL BE INCORPORATED BY THE CURRENT DESIGN ACTIVITY

CAGE CODE XXXXX

USMC

PROGRAM EXECUTIVE OFFICER - LAND SYSTEMS (PM AAA)

2200 LESTER STREET

QUANTICO, VA 22135-6050

3.11.2.2. IN-PROCESS REVIEWS

Periodic in-process reviews will be conducted during the development of the TDP as agreed upon at the TDP Guidance Conference and specified in the Contractors Master Schedule. These reviews are team meetings during which an evaluation of progress on TDP documentation is held. Reviews may be held at the Contractor’s facility or conducted off-site by the review activity.

3.11.2.3. FINAL TECHNICAL REVIEW FOR DIGITAL DELIVERIES

This review evaluates the final form TDP elements for contract compliance for digital deliveries. The following statements provide verification requirements.

1. When final delivery of the product definition data elements is to be in any other non-standard digital format (identify at guidance conference), the Contractor shall send a sample to the procuring activity along with a hard copy of the data files provided on digital media. This data should contain sample data and drawing files in the formats scheduled for delivery. The procuring activity will verify the sample digital delivery against the hardcopy to verify that the test media accurately depicts the original data files and that the delivery media will work successfully on Government equipment.

2. A Product definition data file containing multiple file formats for defining an item or system shall contain a data index file to catalog and label each separate file format, including an association list to link the file formats together.

3.11.2.4. TDP DISCREPANCY NOTIFICATION AND CORRECTION

Written description and notification of TDP discrepancies uncovered and noted during, or as a result of, formal reviews and audits will be provided by the Government. Documented discrepancies shall be corrected and presented to the Government for comparison prior to the next TDP in-process review or audit.

3.11.2.5. DATA AND EQUIPMENT

The following data and equipment shall be made available for inspection or select item builds to support each conference, review, or audit.

1. Appropriate TDP elements.

2. Engineering Change Notices (ECNs).

3. Deviations and waivers.

4. Hardware items.

5. Quality assurance data.

6. Minutes of previous TDP reviews.

7. Outstanding discrepancies from previous reviews (action items).

8. Subcontractor and Supplier data.

9. Applicable company standards, policies, procedures, and records

Attachment 17 M67854-15-R-0001

ACV-ATT-02001, v1.0 2

Enclosure 1:

JOINT ENGINEERING DATA MANAGEMENT INFORMATION AND CONTROL SYSTEM (JEDMICS)

PORTABLE DOCUMENT FORMAT (PDF) REQUIREMENTS

Technical Data Packages provided in PDF format for use in JEDMICS shall meet the following requirements:

1. All drawings will be limited to five (5) Mega Byte (MB) or less.

2. All sheet numbers for a drawing will be in a single file. The number of drawing sheets is limited by the 5 MB limit. Multiple sheet drawings exceeding 5 MB will be broken down into individual sheet number files for uploading.

3. JEDMICS Compact Disk Engineering Data Exchange (CDEX) file structure and format requirements shall be met to facilitate JEDMICS loading, output and interoperability.

4. JEDMICS metadata criteria for C1/C4 drawings shall be explicitly adhered to, without exception, with regards to the PDF electronic drawings.

The JEDMICS CDEX Specification is available under the JEDMICS link at https://mynatec.navair.navy.mil/

Attachment 17 M67854-15-R-0001 Attachment 17 M67854-15-R-0001Attachment 4, Technical Data Package, Enclosure (4) 12 Nov 2012 Rev1

ACV-ATT-02001, v1.0 1

Enclosure 2: Technical Data Package Pricing Sheet

Enclosure 3: Parameter ID and Descriptions

Parameter ID Number

U - Unlimited Rights. All uses for all purposes, Government and Commercial.

G - Government Purpose Rights. All uses, but only for Government purposes.

L - Limited. Internal Government use for Government purpose with very little else authorized.

R - Restricted Rights. Internal Government use for Government purpose with very little else authorized.

SB - Small Business Innovative Research (SBIR). A special catch-all category (SBIR Rights) and alters the normal use of some of the other legends. When dealing with a SBIR contract, the SBIR data rights clause must be applied.

SL - Special License Rights. As specified by the negotiated contract terms. Often used to alter the default rights under the clauses or agree to an apportionment of rights which does not fit neatly into the default categories.

A (Approved for public release; distribution is unlimited)

B (Distribution authorized to U.S. Government Agencies only)

C (Distribution authorized to U.S. Government Agencies and their contractors)

D (Distribution authorized to the Department of Defense and U.S. DoD contractors only)

E (Distribution authorized to DoD Components only)

F (Further dissemination only as directed)

X (Distribution authorized to U.S. Government Agencies and private individuals or enterprises eligible to obtain export-controlled technical data)

CD (Computer Aided Design (CAD) Document)

D1 (Altered Item)

D7 (Stable Base: Master Pattern)

DA (Interface Control)

DC (Installation)

DD (Inspection)

DE (Inspection Equipment & Maintenance)

DG (Envelope)

DI (Instruction)

DN (Rework)

DO (All Kits)

DP (Product)

DV (On vehicle Equipment/ Basic Issue Item)

DX (Source Control)

DZ (Vendor Item Control)

ED (List of Equipment - Depot Installed)

EM (List of Equipment - Manufacturer Installed)

ET (List of Equipment-Troops Installed)

IM (Inspection Manual/Standard)

PD (Packaging Data Sheet)

PE (Per/Detail Design/Purchase Description)

QF (Final Inspection Record)

QP (Inspection Equipment Supply List)

QS (Supplemental QA Provision)

SC (Schematic)

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

ACV-ATT-02001, v1.0 1 image1.emf

Encl 2 TDP Pricing Sheet.xlsx TDP Pricing Sheet

CDRL #: SOW Paragraph Numbers CDRL: Title of Data item - Block 2 CDRL: Subtitle - Block 3 TDP Cost, US $s

A005 3.3.6.2 Commercial Drawings/Models and Associated Lists N/A

A019 3.3.15.6 Software Product Specification N/A

A029 3.3.4 Technical Report - Study/Services Requirements Management Database

A030 3.3.5 Interface Control Document (ICD) N/A

A031 3.3.6.1 Product Drawings/Models and Associated Lists N/A

A033 3.3.8.2 Technical Report - Study/Services Master Configuration Item (CI) Report List

A036 3.3.9.1 Vehicle Configuration Data "As Designed" N/A

A049 3.3.15.1 Software Requirements Specification N/A

A050 3.3.15.2 Software Version Description (SVD) N/A

A051 3.3.15.2 Software User Manual (SUM) N/A

A053 3.3.15.5 Firmware Support Manual (FSM) N/A

A081 3.4.3 Technical Report - Study/Services Key Characteristics Database and Report

A091 3.6.2 / 3.6.3.1 / 3.6.3.3 / 3.6.7.7 / 3.6.8.1 Logistics Product Data Logistics Product Data (LPD) Including Provisioning Technical Data (PTD)

A095 3.6.4.3 Engineering Data for Provisioning (EDFP) N/A

A098 3.6.6.4 Instructional Performance Requirements Document Part I - Task Data Part II - Learning Analysis Data PART III – Critical Training Task List

A099 3.6.6.5.1 / 3.6.6.6 Test Package Operator Maintenance Training Test Packages

A100 3.6.6.5.4 Course Conduct Support Document Operator Maintenance Course Conduct Information Package

A101 3.6.6.5.2 / 3.6.6.6 Training Conduct Support Document Operator Maintenance Lesson Plans, Student Handouts, Instructional Visual Aids, and Training Materials Change Data

A118 3.3.6.3 Special Tooling (ST) Drawings/Models and Associated Lists N/A

A128 3.6.8.1 / 3.6.8.2 Technical Report - Study/Services Depot Level Technical Information and Asssociated Support and Test Equipment

A129 3.3.6.4 Special Inspection Equipment (SIE) Drawings/Models and Associated Lists N/A

A130 3.6.6.5.1 Test Package Field Level Maintenance Training Test Packages

A131 3.6.6.5.2 Training Conduct Support Document Field Level Maintenance Lesson Plans, Student Handouts, Instructional Visual Aids, and Training Materials Change Data

A133 3.6.6.5.4 Course Conduct Information Package Maintainer Course Conduct Information Package

A134 3.3.34.1 Drawing/Model Number Assignment Report N/A

Total for CLIN 6005 =

&"Times New Roman,Bold"&14Technical Data Package Pricing Sheet

Enclosure 1 to Attachment 17

Sheet2

Sheet3