Attachment 7 - Contract Data Requirements List (CDRL) General Instructions for the CRONUS A3R.docx

DOCX document 132 KB Posted

Attached to
Automated Air-to-Air Refueling
Solicitation number
FA2385-25-S-9761
Issued by

About this file

This document is a Contract Data Requirements List (CDRL) General Instructions for the CRONUS A3R RelNav and Boom Automation Efforts, associated with solicitation FA2385-25-S-9761 for the Air Force Research Laboratory. The CDRL establishes comprehensive instructions for data deliverables, including submission requirements, electronic transmission protocols, document marking guidelines, and distribution statements for technical data related to an automated air-to-air refueling project.

The primary objective of the CRONUS A3R program is to develop advanced boom automation technologies for potential future uncrewed tanker aircraft, focusing on autonomous control and manned-unmanned teaming. Key technical goals include defining models and logic for refueling operations, extending system reliability to eliminate operator monitoring, developing analysis techniques for system certification, and identifying contingency event resolution strategies. The acquisition approach emphasizes platform-agnostic capabilities, open architecture, and interface standards to prevent vendor lock scenarios, with specific attention to operating in GPS-denied environments.

View the file

Other files

Show all 13

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

CONTRACT DATA REQUIREMENTS LIST

(CDRL) GENERAL INSTRUCTIONS

FOR THE

CRONUS A3R

RelNav and Boom Automation Efforts

Dated:

18 December 2024

PREPARED BY: CRONUS A3R – AFRL/RST

WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-7249

Attachment 7
FA2385-25-S-9761

CDRL MODIFICATION MATRIX

This matrix identifies the CDRL changes as implemented by contract modification.

PROPOSAL NO.
CDRL REV
DATE
CDRLS/PAGES REVISED
Contract Award
Original
2024 DEC
A3R General Instructions and CDRL

TABLE OF CONTENT

1.0 SCOPE

2.0 REFERENCE DOCUMENTS

3.0 DATA DELIVERABLES

3.1 Delivery Dates

3.2 Tailored Data items

3.3 Approval of Data

3.4 Resubmittal of Data

3.5 Final Submittal of Data

3.6 DD Form 250 Requirements

3.7 Classified Data

4.0 ELECTRONIC DATA TRANSMISSION

4.1 Submission

4.2 Delivery Non-Compliance

4.3 Financial Information Format

5.0 LETTERS OF TRANSMITTAL (LT)

6.0 COMMON ABBREVIATIONS

7.0 MARKING DOCUMENTATION

7.1 Distribution Marking System

7.2 Marking Technical Data

7.3 Distribution Statements

7.4 Controlling Office

7.5 Export Control Warning

7.6 Destruction Notice

7.7 Classified Information

7.8 Controlled Unclassified Information

7.9 Marking Non-Technical Documentation

7.10 Marking Example

7.11 Intellectual Property Marking

8.0 MAILING LISTS

9.0 REFERENCE DOCUMENTS

10.0 ACRONYM

1.0 SCOPE

The Contract Data Requirements List (CDRL) establishes the data to be delivered by the contractor, including the submittal, approval and distribution requirements. This document provides instructions and clarifications which apply to all of the CDRLs within the applicable contract, unless otherwise noted. CDRLs are accomplished on DD Form 1423-1.

2.0 REFERENCE DOCUMENTS

32 C.F.R. §117.15
National Industrial Security Program Operating Manual

(NIPSCOM)

DoDD 5230.25
Withholding of Unclassified Technical Data From Public Disclosure
DoD 5010.12-M
Procedures for the Acquisition and Management of Technical Data
DoDI 5230.24
Distribution Statements on Technical Documents
DoDM 5200.01
DoD Information Security Program: Protection:

Overview, Classification, and Declassification

DoDI 5200.48
Controlled Unclassified Information (CUI)
EIA 649-1
Configuration Management Requirements for Defense Contracts
DAFI 61-201
Management of Scientific and Technical Information

(STINFO)

DoDD 5230.9
Clearance of DoD Information for Public Release
DoD 5400.7-R
DoD Freedom of Information Act Program
DoD 5220.22-M
National Industrial Security Program Operating Manual
DFARS 227.71
Rights to Technical Data
DFARS 227.72
Right to Computer Software & Computer Software

Documentation

3.0 DATA DELIVERIES

The CDRL establishes the data to be delivered by the contractor. The CDRL also identifies the submittal, inspection, approval, acceptance, and distribution requirements of all the CDRL data items contained herein.

3.1 Delivery Dates

In the event a CDRL delivery date falls on a Saturday or Sunday, the delivery will be made by the next business day to be counted as an on-time delivery. Unless otherwise specified in Block 16 of the CDRL.

3.2 Tailored Data Items

Tailoring instructions are as described in Block 16 of each effected CDRL. If the data preparation instructions or requirements contained in Block 16 of the CDRL are different than the DID, the CDRL Block 16 shall govern.

3.3 Approval of Data

a. An "A" designator in Block 8 of the CDRL indicates the government will respond NLT 30 calendar days, unless otherwise specified on the CDRL, Block 16.

b. If a CDRL is “Approved with comments”; the government will provide guidance for comment adjudication, to include re-submission requirements.

c. If a CDRL is “Rejected”; the government will provide guidance for resubmission, to include re-submission requirements.

d. In the event the Government requires additional time to review a CDRL, the Contracting Officer will notify the contactor via e-mail specifying a date. The Contractor shall not assume a CDRL is approved if the Government does not respond.

e. For those CDRLs with an "N/A" in Block 8, government approval of the content is not required; however, compliance with data item format and content requirements as specified in the DID, and as tailored in Block 16 of the CDRL, is mandatory. However, the government may not provide a formal response back to the contractor. The government has the right to direct changes / approve / reject / disapprove any data submittal(s) not in compliance with contract requirements.

3.4 Re-submittal of Data

If re-submittal of a CDRL is required, it shall be re-submitted IAW guidance provided for each government CDRL response. Should the contractor disagree with the re-submittal timeline/requirements, they shall request submission relief within 5 calendars on receipt of “rejected” or “approved with comments” government response to the program CO. Each page of a re-submittal shall have changes indicated by a vertical line down the outer right margin designating those areas that have been revised. The document revision shall be indicated on the title page of the data item, each page, and a summary of document changes section contained within the document.

3.5 Final Submittal of Data

For the final delivery of each data item in the contract or delivery order, the contractor shall clearly state in the letter of transmittal (LOT), as defined in paragraph 5.0, when it is the last submittal being made, and that all contractual requirements concerning that data item have been fulfilled.

3.6 DD Form 250 Requirements

Block 7 of the CDRL directs the inspection and acceptance of the submittal. Individual DD Form 250s are required only if indicated in Block 7. All other submittals shall be accompanied by a Letter of Transmittal (LOT).

3.7 Classified Data

Classified data shall be submitted in accordance with the requirements established by the DD Form 254. The contractor shall contact the CO for the mailing addresses for classified data.

4.0 ELECTRONIC DATA TRANSMISSION

4.1 Submission

a. The contractor shall submit all data deliverables in accordance with the specific submittal instructions indicated in Block 16 of each CDRL. The versions of the software used shall remain compatible with current program office software. Any submittals by other means shall require program office approval prior to delivery of data. Data to be submitted by Electronic Data Transmission (EDT) shall be identified in “Block 14.b. Copies, Final, Repro” of the CDRL

b. Electronic Delivery includes delivery or availability of data files via Government- approved website, web page, server, or via attachment of electronic files, as mutually agreed to between the Government and the contractor. Electronic data delivery and access is subject to Government protection and security requirements.

NOTE: The contractor and their sub-contractors shall not use special characters in the document filename with the following exceptions: dash or an underscore.

4.2 Delivery Non-Compliance

The contractor shall inform the program office if any of their data deliverables cannot comply with the required electronic formats. In such cases the contractor shall recommend, for program office approval, an alternative delivery format(s).

4.3 Financial Information Format

Financial information provided in Excel spreadsheets should be able to be manipulated.

5.0 LETTERS OF TRANSMITTAL (LOT)

All data deliveries shall include a LOT. The LOT,( "LT" Blk 7 of DD1423), may be in the form of a letter or e-mail from the designated contractor representative. At a minimum, the LOT shall contain:

Contractor Point of Contact (POC) Contractor address Date Contract number and program name Letter control number Document control number Document revision level Document date CDRL sequence number DID Number Data Title/Subtitle Reason or frequency of submittal (monthly, draft, final, update, etc.)

b. If a paper copy of the LOT is prepared, a complete list of addressees shall be placed at the end of the LOT, annotating the recipients (as identified on the DD Forms 1423, Block 14) including the transmittal-letter-only recipients.

c. If submittal is made via e-mail, the list of addressees in the “TO” line shall include the complete list of addressees and shall be considered sufficient.

6.0 COMMON ABBREVIATIONS

Table: Common Abbreviations

Block 8:
A
Approval
N/A
Approval Not Required
BLK16
See Block 16 for further instructions
Blocks 10, 11, 12, and 13
ANNLY
Annually
ASREQ
As Required
BLK16
See Block 16 for further instructions
MTHLY
Monthly
N/A
Not Applicable
QTRLY
Quarterly
xx DAC
xx Days after Contract Award

7.0 MARKING DOCUMENTATION

7.1 Distribution Marking System:

a. In accordance with Section 1.30 of Title 10, “United States Code” a DoD distribution marking system for technical data has been established by DoD Instruction 5230.24, “Distribution Statements on Technical Documents.” The intent of the system is to stem the flow of military-related technical data to our adversaries, without inhibiting technological growth or blocking the exchange of technical data that is vital to progress and innovation. The contractor shall mark all distribution statements and export-control statements, supplemental to any security markings, on all technical data to denote the extent of its availability for secondary distribution, release, and disclosure without need for additional approvals and authorizations from the controlling DoD office.

b. Required distribution statements are annotated in Block 9 of each CDRL. If the contractor feels that a different statement is required, it must notify the contracting officer with the recommended statement. The Government will review the request and determine which statement is the most appropriate and provide the contractor with an acceptance of the change or reason for not accepting the contractor’s request for change.

7.2 Marking Technical Data

a. The contractor shall mark all requested technical information, regardless of its medium, with a distribution statement. This includes technical reports, blueprints, drawings, technical orders, technical manuals, plans, instructions, computer software, viewgraphs, film, technical papers, photographs, etc. If the document contains export-controlled technical data, it also must be marked with an export control warning statement. Distribution statements can be applied to technical data that contain or reveal proprietary information used.

b. Technical data categorized as cryptographic/communications security, communications/electronic intelligence, and similar categories as may be designated by the Director, National Security Agency, whose distribution is limited through alternate methods, are exempt from these marking provisions.

c. The contractor shall mark Controlled Unclassified Information (CUI) in accordance with DoDI 5200.48, paragraph 3.4.

7.3 Distribution Statements

Table: Distribution Statement Summary DISTRIBUTION STATEMENT A: Approved for public release. Distribution is unlimited.

DISTRIBUTION STATEMENT B: Distribution authorized to U.S. Government agencies only (fill in reason) (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (fill in reason) (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only (fill in reason) (date of contract award).

Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT E: Distribution authorized to DoD Components only (fill in reason) (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT F: Further dissemination only as directed by (insert controlling DoD office) (date of contract award)) or higher DoD authority.

DFARS Subparts 227.71 and 227.72 stipulate control procedures for contractor controlled technical information in which the Government has limited rights. These procedures shall be followed as described in DoDI 5230.24.

7.4 Controlling Office

The following address will be used on all documentation for the “controlling DoD office” for this program:

CRONUS

Air Force Research Laboratory (AFRL) Bldg 190, 2698 G Street Wright-Patterson AFB, OH 45433

7.5 Export Control Warning

Authority to withhold and control the export of certain technical data with military or space application is determined in accordance with Title 10, United States Code section 130, “Authority to withhold from public disclosure certain technical data”, and implemented by DoDD 5230.25, if such data may not be exported lawfully outside the United States without an approval, authorization, or license under the Export Administration Act of 1979 or the Arms Export Control Act (both cited in the Export Control Warning). Such withholding and export control applies to Defense items listed in the United States Munitions List (USML), (which is part of the “International Traffic in Arms Regulations (ITAR),”—22 CFR 120-130); and 15 CFR 730-774 (the “Export Administration Regulations (EAR)”).

If a technical document, whether printed or electronic/digital, contains export-controlled technical data, it shall be marked with the export control warning statement prescribed in DoDI 5230.24 and shown below. When it is not feasible to use the entire statement, the abbreviated warning may be used, and a copy of the full warning added to the “Notice to Accompany the Dissemination of Export-Controlled Technical Data,” which is Enclosure E5 of DoDD 5230.25. For assistance in determining what is export controlled, consult the controlling DoD office. The warning notice may be used in conjunction with distribution statements B, C, D, E, and F. Distribution statement A, which denotes public release, cannot be used in conjunction with the export-control warning notice.

"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 the provisions of DoDD 5230.25.

7.6 Destruction Notice

All unclassified technical data marked with distribution statements B, C, D, E or F shall be marked with the following Destruction Notice:

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Classified data, including classified controlled technical data, shall be handled and destroyed in accordance with the procedures in DoDM 5200.01, Volume 3_AFMAN 16- 1404, Volume 3 and DoDM 5220.22_AFMAN 16-1406 Volume 2.

Destruction Notice for classified technical information:

DESTRUCTION NOTICE: Follow the procedures in DoDM 5200.01, Volume 3_AFMAN 16-1404, Volume 3, Information Security Program: Protection of Classified Information and DoDM 5220.22_AFMAN 16-1406, Volume 2, National Industrial Security Program: Industrial Security Procedures for Government Activities.

7.7 Classified Information

Documents containing classified information will be marked in accordance with DoDM 5200.01, Volume 2, “DoD Information Security Program: Marking of Information”.

7.8 Controlled Unclassified Information (CUI)

Unclassified information associated with a law, regulation, or government-wide policy and identified as needing safeguarding is considered CUI. CUI requires access control, handling, marking, dissemination controls, and other protective measures for safeguarding. Per DoDI 5200.48, mark these documents with “Controlled Unclassified Information (CUI)” or at a minimum “CUI” at the top and bottom of each page. Include a CUI Designation Indicator on the bottom right of the first page of CUI documents as shown below:

Line 1: Name of the DoD Component Line 2: Identification of the office creating the document Line 3: Identification of the categories contained in the document--see DoD CUI Registry for applicable category (multiple categories can be listed, if applicable) Line 4: Distribution Statement Line 5: Name, phone number or email of POC

When CUI is comingled with classified information, mark and protect classified materials according to DoDM 5200.01, Volumes 1-3_AFMAN 16-1404, Volumes 1-3.

7.9 Marking Non-Technical Documentation

Non-technical documentation that is associated with a law, regulation, or government- wide policy, and identified as needing safeguarding, is considered CUI and must be marked as such. Distribution statements are not used on non-technical documentation;

however, a Limited Dissemination Control (LDC) will apply in most cases. Contact the program office to make this determination. Reference the following link for a current listing:

CUI Registry: Limited Dissemination Controls | National Archives

Some examples of CUI categories that may pertain to non-technical data include: General Proprietary Business Information, General Procurement and Acquisition, and Source Selection. A complete CUI Registry list of CUI categories can be found at: https://www.dodcui.mil/Home/DoD-CUI-Registry/

Per DoDI 5200.48, mark these documents with “Controlled Unclassified Information (CUI)” or at a minimum “CUI” at the top and bottom of each page. Include a CUI Designation Indicator on the bottom right of the first page of CUI documents, as follows:

Line 1: Name of the DoD Component Line 2: Identification of the office creating the document Line 3: Identification of the categories contained in the document--see DoD CUI Registry for applicable category (multiple categories can be listed, if applicable) Line 4: For non-technical documentation enter either N/A or the appropriate LDC Line 5: Name, phone number or email of POC

CUI must be marked with the following Destruction Notice:

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

7.10 Marking Examples

The marking examples below are for reference. Specific information within the distribution statements and the CUI Designation Indicator will depend upon each individual case.

Marking example for non-technical CUI:

CUIMark Top of Page

DESTRUCTION NOTICE—Destroy by any method that will prevent disclosure of contents or reconstruction of the document.Page 12 of 15

Destruction Notice for Controlled Unclassified Information (CUI)

Controlled by: USAF/AFMC Controlled by: AFRL/XXXX CUI Category: General Proprietary Business Information Distribution Statement: IAW DoDI 5200.48 Limited Dissemination Controls are mandatory for non- technical CUI.

POC: Gov POC name and email

CUIMark Bottom of Page

CUI Designation Indicator IAW DoDI 5200.48, 6 Mar 2020

Marking example for technical CUI:

DISTRIBUTION STATEMENT E. Distribution authorized to DoD components only; Administrative or Operational Use; 27 August 2021. Other requests for this document shall be referred to AFRL/XXXX, Gov address.Destruction Notice for Controlled Unclassified Information (CUI) Complete DoDI 5230.24 Distribution Statement

DESTRUCTION NOTICE—Destroy by any method that will prevent disclosure of contents or reconstruction of the document.CUI Designation Indicator IAW DoDI 5200.48, 6 Mar

Controlled by: USAF/AFMC Controlled by AFRL/XXXX CUI Category: Controlled Technical Information Distribution Statement: E

Marking example for export-controlled technical CUI:

DISTRIBUTION STATEMENT E. Distribution authorized to DoD components only; Administrative or Operational Use; 27 August 2021. Other requests for this document shall be referred to AFRL/XXXX, Gov address.Destruction Notice for Controlled Unclassified Information (CUI) DODI 5230.24 Export Control Warning 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 the provisions of DoDD 5230.25.

Complete DoDI 5230.24 Distribution Statement

DESTRUCTION NOTICE—Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Controlled by: USAF/AFMC Controlled by AFRL/XXXX CUI Category: Controlled Technical InformationCUI Designation Indicator IAW DoDI 5200.48, 6 Mar

Distribution Statement: E

7.11 Intellectual Property/Marking

Any markings that are added to documents for review purposes must be removed prior to formal submittal. If a document still requires a marking (i.e., proprietary) not addressed in the contract, the contractor must provide a justification for the marking.

8.0 MAILING LISTS

The Government will provide the following information for each recipient identified in Block 14: mailing address, office symbol, and point of contact e-mail address.

Mailing Address
Office Symbol
Point of Contact

Air Force Research Laboratory (AFRL) CRONUS AFRL/RST Bldg 190, 2698 G Street Wright-Patterson AFB, OH 45433

AFRL/RST
afrl.rste.cronus-configuration@us.af.mil

9.0 ACRONYMS

CDRLContract Data Requirements List
CUIControlled Unclassified Information
DIDData Item Description
EARExport Administration Regulations
ITARInternational Traffic in Arms Regulations
LDCLimited Dissemination Control
LOTLetter of Transmittal
PCOProcuring Contracting Officer
POCPoint of Contact

LETTER OF TRANSMITTAL AND SHIPMENT NOTICE

Ship to: AFRL/RST, Transformational Capabilities Office (TCO)Page:1 of 1
1865 4th Street, Bldg 14 CPDate:1 May 2023
Wright Patterson AFB, OH 45433LTSN No. B004 – 23-C- 000?

Email / DoD Safe:

Subject: Contract Data Requirements List (CDRL) Data Submittal Program:

References: (a) Contract Number: FA2391-25-C-B0XX

(b) SOW Para:???

1. CDRL Sequence Number: A00?

2. Data Item Description: DI-XXXX-XXXXX?

3. Data Item Title: ??

4. Submitted:ApprovalOR Non approval
6. Document Number:N/A

7. Submittal Version: ???

8. CDRL Point of Contact: E N

Signature:

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoD 5010.12-M for detailed instructions.)

FOR GOVERNMENT PERSONNEL
FOR THE CONTRACTOR
Item A. Self-explanatory.
Item 17. Specify appropriate price group from one of the following
Item B. Self-explanatory.
groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

Item C. Mark (X) appropriate category: TDP - Technical Data Package; TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort

Item D. Enter name of system/item being acquired that data will support.
(production, development, testing, and administration) but which is required by DD Form 1423.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).
Estimated Price - Costs to be included under Group I are
Item G. Signature of preparer of CDRL.
those applicable to preparing and assembling the data item in conformancewithGovernmentrequirements,andthe
Item H. Date CDRL was prepared.
administration and other expenses related to reproducing and delivering such data items to the Government.

Item I. Signature of CDRL approval authority.

Item J. Date CDRL was approved.
b.Group II.Definition - Data which is essential to the

performance of the primary contracted effort but the contractor is

Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.
required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of
Item 2. Enter title as it appears on data acquisition document cited in Item 4.
submittal, preparation, control, or quality of the data item.
Item 3. Enter subtitle of data item for further definition of data item (optional entry).
Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item

without conforming to Government requirements, and the

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one- time DID number, that defines data content and format requirements.
administrative and other expenses related to reproducing and delivering such data item to the Government.
Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).
c.Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary
Item 6. Enter technical office responsible for ensuring adequacy of the data item.
contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of

content, format, frequency of submittal, preparation, control, and

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.
quality of the data item.
Item 8. Specify requirement for approval of a draft before preparation of the final data item.
Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and
Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).
delivering such data item to the Government.
Item 10. Specify number of times data items are to be delivered.
d.Group IV.Definition - Data which is developed by the
Item 11. Specify as-of date of data item, when applicable.
contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.
Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15. Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.
production or development for the Government of that item of data. These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would

otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.

DD FORM 1423-1 (BACK), FEB 2001

File details come from the government source that posted it. Updated .