Attachment 2 - CDRL Package TACO Cart.pdf

CONTRACT DATA REQUIREMENTS LIST

(CDRL)

GENERAL INSTRUCTIONS

FOR THE

Test And Check Out (TACO) Cart

CONTRACT NUMBER: INSERT CONTRACT NO. FA8689-26-Q-B001

22 April 2026

PREPARED BY: Nathan Larson

AFLCMC/WIIE

WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433

MODIFICATION MATRIX

This matrix identifies the General Instructions and/or CDRL changes as implemented by contract modification.

CONTRACT MOD # DATE

(Y/M/D) DESCRIPTION OF CHANGE

Contract Award (Insert Date)

Table of Contents

1.0 SCOPE

2.0 GENERAL

3.0 DATA DELIVERABLES

3.1 Delivery Dates

3.2 Tailored Data Items

3.3 Document Revisions

3.4 Data Submittal Approvals

3.4.1 CDRL Submittal Disposition Definitions

3.5 Resubmittal of Data

3.6 Final Submittal of Data

3.7 DD Form 250 Requirements

3.8 Classified Data

3.9 Modification of Data Requirements

4.0 ELECTRONIC DATA TRANSMISSION

5.0 LETTERS OF TRANSMITTAL (LT)

6.0 COMMON ABBREVIATIONS in DD Form 1423

7.0 MARKING DOCUMENTATION

7.1 Marking Technical Documentation

7.1.1 Distribution Statement

7.1.2 Export Control Warning

7.1.3 Classified information

7.1.4 Controlled Unclassified Information (CUI)

7.2. Marking Non-Technical Documentation

7.3 Marking Examples

7.4 Intellectual Property/Marking

8.0 REFERENCE DOCUMENTS

9.0 ACRONYMS

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.

2.0 GENERAL

Unless otherwise noted, all deliverables shall be in English language. The Data Item Descriptions (DIDs) specified in Block 4 of the CDRLs are available electronically at the Acquisition Streamlining and Standardization Information System (ASSIST) database website: http://quicksearch.dla.mil/. The order of precedence shall be the CDRL DD Form 1423 and associated continuation sheets, CDRL General Instructions, and then the DID as specified in Block 4 of the CDRL.

3.0 DATA DELIVERABLES

3.1 Delivery Dates

Unless otherwise specified in Block 16 of the CDRL, all references to “days” will refer to calendar days.

If a CDRL delivery date falls on a Saturday, the submittal must be delivered on the Friday prior to the Saturday delivery date.

If the CDRL delivery falls on a Sunday, the submittal must be delivered on the Monday following the Sunday delivery date.

If the CDRL delivery falls on a holiday, the submittal must be delivered on the last business day before the holiday.

Early CDRL delivery is permitted. The contractor must notify the Government (PCO and Configuration/Data Manager) of late CDRL deliveries.

3.2 Tailored Data Items

Tailoring instructions, when applicable, are described in Block 16 of each CDRL. If the data preparation instructions contained in Block 16 of the CDRL are different than the instructions contained in the DID, the CDRL shall govern.

http://quicksearch.dla.mil/

3.3 Document Revisions

The following requirements apply to revisions for CDRL items provided in response to the data requirements specified in the CDRL:

a. Anytime a revision is submitted, the title page of the document shall indicate the number, letter and/or date of that revision. Document number and current revision symbol shall be on every page of the document. The letter of transmittal for each revision shall also reference all previous correspondence specifically relating to the documentation being submitted.

b. Revisions shall be in the form of change pages or reissuance of the completed document or mutually agreed upon form, as requested by the Government.

c. A revisions page shall be provided in the front of each revision that shall contain, as a minimum a brief description of the changes, and the reason for revision, including the applicable authority, e.g., ECP number, change order number, supplemental agreement number, etc.

d. Tracked changes or change bars shall be utilized to obtain Government approval of revised documents; however, final submittal should not contain mark ups.

3.4 Data Submittal Approvals

An "A" designator in Block 8 of the CDRL indicates the Government will formally reply to each data submittal with an approval, approval with comments, or disapproval. The Government will issue a response via a Procuring Contracting Officer Letter (PCOL) to the contractor within thirty (30) calendar days, unless otherwise specified on the DD Form 1423, Block 16. Government non-response beyond thirty (30) calendar days does not constitute approval. If approvals are required, a CDRL submittal is not officially approved until a PCOL is submitted to the contractor. The thirty (30) calendar days schedule does not apply to Engineering Change Proposals (ECPs), Contract Change Proposals (CCPs), and Requests for Variances (RFVs).

NOTE: ECPs will utilize the DD Form 1692 (long form) unless otherwise specified in the DD Form 1423.

If Block 8 of the CDRL contains an "N/A", or an “N” designator, 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. The Government will not provide a formal response back to the contractor when the contractor’s submittal meets all DID and contractual requirements; however, the Government has the right to formally disapprove or acknowledge with comments, any data submittal(s) not in compliance with DID and contract requirements by PCOL for resubmissions. For any data submittal received with incorrect data rights or markings, the contractor shall be notified by PCOL of a resubmittal request.

If a data submittal is approved with Government comments, those comments shall be incorporated in the subsequent submittal. If no subsequent submittal is scheduled e.g.

monthly or quarterly, then the data item shall be resubmitted, with Government comments incorporated, within fifteen (15) calendar days.

The contractor will formally respond to the Government within thirty (30) calendar days after receipt of any data that is disapproved, unless otherwise specified on the CDRL.

Data submittal requirements shall not be considered to have been met until the procuring agency has determined that all contractual requirements have been met regarding the identified data.

Draft submittals are not approval items. The contractor shall formally submit draft data item(s), when required by the CDRL, for review and shall mark them as “draft” (watermark on every page). Draft submissions shall not alter the due date of first formal submission specified in the CDRL.

3.4.1 CDRL Submittal Disposition Definitions

USG Disposition Definition

Approved

The Approved disposition is exclusively for Approval (A-coded) CDRL submittals. It signifies that the deliverable has been reviewed by the Government and is accepted as fully compliant with all contractual requirements, including format, markings, content, and timeliness.

No further action is required from the contractor for this submission.

Approved with Comments

The Approved with Comments disposition is exclusively for Approval (A-coded) CDRL submittals. It indicates the deliverable is accepted, but the Government has provided comments.

These comments may address minor discrepancies, suggest improvements, or request clarifications. The Government's response will specify whether the comments must be incorporated in a subsequent revision.

Rejected

The Rejected disposition signifies that the deliverable is unsatisfactory because it fails to meet contractual requirements for format, markings, or content. This disposition applies to both Approval (A-coded) and Non-Approval (NA-coded) submittals and contractually requires the contractor to correct all identified deficiencies and resubmit the deliverable.

Disapproved

The Disapproved disposition carries the same contractual weight as "Rejected" and signifies that the deliverable is unsatisfactory because it fails to meet contractual requirements. This disposition applies to both Approval (A-coded) and Non-Approval (NA-coded) submittals and contractually requires the contractor to correct all identified deficiencies and resubmit the deliverable.

Information Only

The Information Only disposition is used exclusively for data provided via the Data Accession List (DAL) as Work Products, which are not formal CDRL deliverables.

This disposition serves as an internal acknowledgment of receipt for data provided to support the contractual effort.

Withdrawn

The Withdrawn disposition is used for deliverables submitted by the contractor in error. This includes submissions that were not contractually required or were delivered to the incorrect contract. This disposition effectively nullifies the erroneous submission.

Superseded

The Superseded disposition can apply to both Approval (A-coded) and Non- Approval (NA-coded) CDRL submittals.

It indicates that a deliverable has been officially replaced by a newer or revised version. No further action is required on the superseded data item.

Returned with Comments

The Returned with Comments disposition is exclusively for Non-Approval (NA-coded) CDRL submittals. It indicates that the Government has comments on the deliverable, but the issues identified do not rise to the level of non-compliance that would mandate a resubmittal. A resubmittal is not contractually required for this disposition. The contractor may incorporate the provided feedback into the next scheduled delivery of the data item, if applicable.

Returned for Action The Returned for Action disposition is exclusively for Non-Approval (NA-coded) CDRL submittals where a resubmittal is required. It signifies the deliverable is non-compliant due to issues such as failure to meet contractual requirements, significant content deficiencies, missing data markings, incorrect data rights, or incorrect formatting. The contractor must correct all identified deficiencies and formally resubmit the deliverable.

Closed

The Closed disposition is exclusively for Non-Approval (NA-coded) CDRL submittals that the Government has reviewed and found to be acceptable. This signifies that the deliverable meets the contractual requirements for that submission, and no further action is required from the contractor.

3.5 Resubmittal of Data

Data submittals that are disapproved by the Government shall be revised and resubmitted by the contractor within 30 calendar days (or otherwise agreed to period of time) after receipt of PCOL. If the contractor cannot resubmit within 30 calendar days, the Government shall be notified within 10 calendar days and a new suspense date will be established.

If resubmittal of a CDRL is required, it shall be resubmitted within 30 calendar days after PCO notification, unless otherwise specified. Should the contractor disagree with the resubmittal requirements, they shall submit their comments to the PCO and Configuration/Data Manager within 10 calendar days of notification and a new suspense date will be established.

Data submittals that are approved contingent upon revision will be recommended to be revised and resubmitted within 30 calendar days after receipt of PCOL, unless otherwise specified on the CDRL or within the PCOL. If the contractor cannot resubmit within thirty 30 calendar days, or within the time specified on the CDRL, the Government shall be notified within 10 calendar days, and a new suspense date will be established.

When resubmitting a data submittal, the contractor is required to provide a revised CDRL number sequence suffix to differentiate the new submission from the original. This revised suffix will be used to track and manage the resubmitted data. To ensure clarity and consistency, the contractor shall increment the existing suffix by one, without introducing any additional letters or numbers. For example, if the original CDRL number is A001-001 and corrections are required, the resubmitted CDRL number shall be labeled as A001-002. This sequential numbering system will continue to increment with each subsequent resubmission, such as A001-003, A001-004, and so on. The contractor shall adhere to this convention, using only the numerical suffix starting from -001 and increasing, to maintain a clear and organized record of all resubmissions.

3.6 Final Submittal of Data

For the final delivery of each data item in the contract/delivery order, the contractor shall clearly state “final delivery” in the Letter of Transmittal (LT), as defined in paragraph 5.0, and include “final” in the document title, signifying that this delivery is the last submittal, and that all contractual requirements concerning that data item have been fulfilled.

3.7 DD Form 250 Requirements

Block 7 of the CDRL directs the method of submittal. Individual DD Form 250s are required only if indicated in Block 7. All other submittals shall be accompanied by a LT.

3.8 Classified Data

Classified data shall be submitted in accordance with the requirements established by the DD Form 254, Contract Security Classification Specification. The contractor shall contact the PCO for the mailing address(es) if not specified in Block 14 or 16 of the DD Form 1423.

3.9 Modification of Data Requirements

From time to time during the performance of this contract, the PCO may unilaterally change the place of delivery and the technical office for any line item of the contract exhibits within the DD Form 1423, with no change in contract price, notwithstanding the provision of the contract clause, Section I entitled “Changes”. If there is a change to the place of delivery, the Contractor and the PCO may mutually agree to an extension of the data submittal requirement date.

From time to time during the performance of this contract, the PCO may unilaterally increase or decrease the number of addresses and/or increase or decrease the number of hard copy deliverables (regular or reproducible) specified for any data item.

Unilateral actions pursuant to the above paragraphs shall be by the issuance of a PCOL followed by a Supplemental Agreement to this contract which will reference this exhibit as its authority. Any action directed by this exhibit shall be effected by the contractor beginning with the first submission of the particular data item(s) after receipt by the contractor of PCO direction.

4.0 ELECTRONIC DATA TRANSMISSION

The contractor shall submit all data deliverables in Microsoft Office or Adobe PDF compatible formats. Deliverables shall be submitted in accordance with the distribution instructions indicated in Block 16 of the CDRL. The versions of the software used for electronic data transmission shall remain compatible with current program office software. Where applicable, all electronic data will be delivered using the Microsoft Office product suite and/or Microsoft Project Tools. Any submittals by other means shall require program office approval prior to delivery of data. PDF documents shall be in searchable format and not scanned.

The Government intends to utilize digital methods for CDRL content review and analysis. Thus, where applicable, CDRL content should be delivered in the native application/development tool format. For example, a SysML model should be delivered as an mdzip file. For specialized tools, the CDRL content should be delivered in a neutral format such as Excel with Government concurrence to ensure the data can be used in the Government review process. Use of PDFs for CDRL SysML content delivery is the least desirable format.

Electronic data shall be delivered via Enterprise Data System (EDS) unless otherwise mutually agreed to between the contractor and the government prior to delivery. Medium Altitude UAS authorized EDS is AF-PLM (Teamcenter), alternate is DoD SAFE.

Classified information shall be submitted by SIPRNet. When a classified deliverable is submitted via SIPRNet, an unclassified LOT shall be delivered via EDS

The PCO may direct the contractor to use AF-PLM, DoD SAFE or another alternative.

Any data submitted outside of EDS without written PCO approval shall be considered as non-compliant with the contract unless otherwise noted on the CDRL.

The Government reserves the right to request a disk or CD for a CDRL submission if additional Air Force requirements demand it. The use of disk/CD shall be on an “as needed” basis only.

The contractor shall inform the Government CM representative if any data deliverables cannot comply with the required electronic delivery. In such cases the Government CM representative shall recommend an alternative delivery method.

5.0 LETTERS OF TRANSMITTAL (LT)

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

Contractor Point of Contact (POC) Contractor address LT date Contract number, program name and delivery order (if applicable) Letter number Document control number Document revision level Document date CDRL number including sequence suffix (e.g., CDRL A001-001) Data Title/Subtitle

Reason or frequency of submittal (monthly, draft, final, update, resubmittal, etc.)

List of distribution addressees as identified in Block 14 of the CDRL Note of “Final Delivery” for contractual fulfillment of CDRL item

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

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 in DD Form 1423

Block 7:

DD 250 Code Inspection Acceptance SS Inspection at source. Acceptance at source.

DD No inspection performed at source. Final inspection performed at destination.

Acceptance at destination.

SD Inspection at source. Acceptance at destination.

DS No inspection performed at source. Final inspection performed at destination.

Acceptance at source.

Acceptance based on written approval from the PCO.

LT Letter of transmittal (LOT) only. As specified in block 16 of the DD Form 1423.

*NO No inspection required. No DD Form 250 or LOT required.

No acceptance required. No DD Form 250 or LOT required.

XX Inspection requirements specified elsewhere in the contract.

Acceptance requirements specified elsewhere in the contract.

*Use of the symbol NO is not authorized for data comprising TDPs or TMs.

Block 8: A Approval N/A Approval Not Required BLK16 See Block 16 for further instructions

Blocks 10, 12 & 13: ANNLY Annually ASGEN As Generated

ASREQ As Required BI-MO Bi-Monthly BI-WE Bi-Weekly BLK 16 See Block 16

DAILY Daily DFDEL Deferred Delivery EOC End of Contract EOM End of Month EOQ End of Quarter MTHLY Monthly ONE/P One time preliminary draft ONE/R Once with Revisions OTIME One Time QRTLY Quarterly R/ASR Revisions as Required SEMIA Semi-Annually WEKLY Weekly XDACM X Days after Contract Modification XDADO X Days after Delivery Order XDARC X Days after Receipt of Comments XDARP X Days after Reporting Period XDATC X Days after Test Completion XDPTT X Days prior to Test XTIMES X Times

7.0 MARKING DOCUMENTATION

7.1 Marking Technical Documentation

The contractor shall mark technical information as instructed by the Government program office. Some examples of technical information include research and engineering data, technical reports, blueprints, drawings, technical orders, technical manuals, plans, instructions, catalog-item identifications, process sheets, data sets, models, studies and analyses and related information, computer software, film, technical papers, and photographs.

7.1.1 Distribution Statement

A DoD distribution marking system for technical data is prescribed in DoD Instruction (DoDI) 5230.24, “Distribution Statements on DoD Technical Information”. The intent of the system is to identify the audience approved for secondary distribution of the data in order to stem the flow of military-related technical data to our adversaries, without inhibiting technological growth or appropriate exchange of technical data that is vital to progress and innovation. These markings are in addition to any security classification or other control markings.

The contractor shall mark all technical information, regardless of its medium, with the appropriate distribution statement as prescribed by the controlling DoD office.

Distribution statements are also applied to technical data that contain proprietary information. Per DAFI 61-201, paragraph 3.4.4.1. “Distribution statements are displayed conspicuously on all technical documents regardless of medium or format. For standard written or printed material, the Distribution Statement is shown on all pages to the maximum extent practical and at a minimum on the front cover, title page, and SF 298, where applicable. If the technical information is digitally prepared or in any other medium that does not have a cover or title page, the applicable Distribution Statement is affixed to all physical and digital items by other means in a conspicuous position for ready recognition.” Drawings must display the distribution statement on the first sheet at a minimum.

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.

Certain types of technical data preclude placing the entire notice on the document.

Abbreviated distribution statements must be approved by the program office and are to be used only when space precludes placing the entire statement on the document.

The distribution statement is identified in Block 9 of each CDRL. If the contractor feels that a different statement or defense category is required, the contractor must notify the contracting officer with the recommended statement. The Government will review the request, determine which statement is the most appropriate, and provide the contractor with either an acceptance or rejection of the requested change.

Wording for the distribution statements is shown below. The acceptable “defense categories” for the distribution statements must be chosen from those listed in DoDI 5230.24.

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

AFLCMC/WII

2530 Loop Road West Bldg. 560 Wright-Patterson AFB, OH 45433

DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited.

DISTRIBUTION STATEMENT B. Distribution authorized to U.S. Government agencies [category] [date of determination]. Other requests for this document must be referred to [controlling DoD office].

DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government agencies and their contractors [category] [date of determination]. Other requests for this document must be referred to [controlling DoD office].

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and U.S. DoD contractors only [category] [date of determination]. Other requests for this document must be referred to [controlling DoD office].

DISTRIBUTION STATEMENT E. Distribution authorized to DoD Components only [category] [date of determination]. Other requests for this document must be referred to [controlling DoD office].

DISTRIBUTION STATEMENT F. Further distribution only as directed by [controlling DoD office] [date of determination] or higher DoD authority.

REL TO. Information has been predetermined by the DoD controlling agency, in accordance with established foreign disclosure policies, to be releasable through established foreign disclosure procedures and channels, to the foreign country and international organization indicated.

CATEGORY A B C D E

PUBLIC RELEASE X

CTI X X X X

CONTRACTOR PERFORMANCE EVALUATION X X

CRITICAL TECHNOLOGY X X X X

DIRECT MILITARY SUPPORT X

EXPORT CONTROLLED X X X X

FOREIGN GOVERNMENT INFORMATION X X X X

IAs X X X X

OPERATIONS SECURITY X X

PATENTS AND INVENTIONS X X

PROPRIETARY BUSINESS INFORMATION X X

SBIR X X

SOFTWARE DOCUMENTATION X X X X

TEST AND EVALUATION X X

VULNERABILITY INFORMATION X X X X

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.1.2 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 Control Reform Act of 2018 or the Arms Export Control Act (AECA) (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 Export Administration Regulations

(EAR) (15 CFR 730-774).

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 5 of DoDD 5230.25. For assistance in determining what is export controlled, consult the controlling DoD office. The Export Control Warning 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.

7.1.3 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.1.4 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/Dissemination Control 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.

7.2. 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;

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

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

7.3 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:

Marking example for technical CUI:

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

POC: Gov POC name and email

CUI Designation Indicator IAW DoDI 5200.48

CUI

CUI Mark Top of Page

Mark Bottom of Page https://www.archives.gov/cui/registry/limited-dissemination https://www.dodcui.mil/Home/DoD-CUI-Registry/

Marking example for export-controlled technical CUI:

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

Complete DoDI 5230.24 Distribution Statement

DISTRIBUTION STATEMENT E. Distribution authorized to DoD components only; Controlled Technical Information; 27 August 2021. Other requests for this document shall be referred to AFLCMC/XXXX, Gov address.

Controlled by: USAF/AFMC Controlled by AFLCMC/XXXX CUI Category: Controlled Technical Information Distribution/Dissemination Control: E POC: Gov POC name and email

CUI Designation Indicator IAW DoDI 5200.48

Complete DoDI 5230.24 Distribution Statement

DISTRIBUTION STATEMENT E. Distribution authorized to DoD components only; Critical Technology, Export Controlled; 27 August 2021.

Other requests for this document shall be referred to AFLCMC/XXXX, Gov address.

Controlled by: USAF/AFMC Controlled by AFLCMC/XXXX CUI Category: Controlled Technical Information Distribution/Dissemination Control: E POC: Gov POC name and email

CUI Designation Indicator IAW DoDI 5200.48

CUI

DODI 5230.24 Export Control Warning

CU

7.4 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 REFERENCE DOCUMENTS

DAFI 61-201 Management of Scientific and Technical Information (STINFO) DFARS 227.71 Rights in Technical Data DFARS 227.72 Rights in Computer Software & Computer Software Documentation DoD 5010.12-M Procedures for the Acquisition and Management of Technical Data DoDD 5230.09 Clearance of DoD Information for Public Release DoDD 5230.25 Withholding of Unclassified Technical Data from Public Disclosure DoDD 5400.07 DoD Freedom of Information Act (FOIA) Program DoDI 2040.02 International Transfer of Technology, Articles, and Services DoDI 5200.48 Controlled Unclassified Information (CUI) DoDI 5230.24 Distribution Statements on DoD Technical Information DoDM 5200.01v1 DoD Information Security Program: Overview, Classification, and

Declassification DoDM 5200.01v2 DoD Information Security Program: Marking of Information DoDM 5200.01v3 DoD Information Security Program: Protection of Classified Information

9.0 ACRONYMS

CCP Contract Change Proposal CDRL Contract Data Requirements List CUI Controlled Unclassified Information DID Data Item Description EAR Export Administration Regulations ECP Engineering Change Proposal EDS Enterprise Data System ITAR International Traffic in Arms Regulations LDC Limited Dissemination Control LT Letter of Transmittal PCO Procuring Contracting Officer PCOL Procuring Contracting Officer Letter POC Point of Contact USML United States Munitions List

CDRL PACKAGE TABLE OF CONTENTS

Generated by AFPLM on: 2026-04-22 19:39:52 GMT

PROGRAM: MQ-9 SYSTEM ITEM: TACO Cart

CONTRACT

INDEX

CONTRACT # CONTRACTOR CONTRACT

STATUS

# CDRLS

INCLUDED

# CDRLS

TOTAL

C1 FA8689-26-Q-B001 TBD OPEN 13 13

DATA ITEM

Contract/ CDRL Set

REQUIRING

OFFICE

AUTHORITY

TITLE

SUBTITLE

SOW/PWS PARA

Attachments A001 C1

AFLCMC/WIIP DI-MGMT-80368A/T

Status Report

SOW PARA 3.3,

3.4, 6, & 10.3

A002 C1

AFLCMC/WIIE DI-SESS-80858D/T

Technical Report-Study/Services Configuration Management Approach

SOW PARA 3.2

A003 C1

AFLCMC/WIIL DI-PSSS-80134B/T

Proposed Spare Parts List

SOW PARA 8.1

A004 C1

AFLCMC/WIIE DI-SESS-81000F/T

Product Engineering Design Data and Associated Lists

Product Drawing/Model Package

SOW PARA 3.1.2

A005 C1

AFLCMC/WIIE DI-MISC-80508B/T

Technical Report - Study/Services Test/Inspection Report (FAT Results)

SOW PARA 7.2

A006 C1

AFLCMC/WIIE DI-MISC-80711A

Scientific and Technical Reports Electromagnetic Capability Compliance Data

SOW PARA 7.3

A007 C1

AFLCMC/WIIP DI-MGMT-81453C

Data Accession List (DAL)

SOW PARA 3.5

A008 C1

AFLCMC/WIIL DI-PSSS-81656B/T

Bill of Materials (BOM) for Logistics and Supply Chain Risk Management

SOW PARA 4

A009 C1

AFLCMC/WIIL DI-ADMN-81373/T

Presentation Material

SOW PARA 8.3

A010 C1

AFLCMC/WIIL DI-IPSC-81947B/T

Government Furnished Property Inventory and Forecasting Report

SOW PARA 8.6

A011 C1

AFLCMC/WIIE DI-SAFT-80102D/T

Safety Assessment Report (SAR)

SOW PARA 7.1

A012 C1

AFLCMC/WIIV DI-MGMT-82001A/T

DOD Risk Management Framework (RMF) Package Deliverables

SOW PARA 10.1

A013 C1

AFLCMC/WIIV DI-IPSC-82249A

Software Assurance Evaluation Report (SAER)

SOW PARA 10.2

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

PREVIOUS EDITION MAY BE USED.

A. CONTRACT LINE ITEM NO.

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER MGMT

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Status Report

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80368A/T

5. CONTRACT REFERENCE

SOW PARA 3.3, 3.4, 6, & 10.3

6. REQUIRING OFFICE

AFLCMC/WIIP

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

MTHLY

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

NA

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

Draft

Final

Reg Repro

16. REMARKS

Block 4:

a. The requirements of DI-MGMT-80368A are tailored. The following paragraphs are deleted and not required: 3.2.1.b, 3.2.1.d, 3.2.1.e, 3.2.1.h, 3.2.1.i, 3.2.2, and 3.2.4.

b. As an attachment, the contractor shall provide an Integrated Master Schedule (IMS). The initial IMS submission, and all subsequent updates, must incorporate the following key program milestones as the contractual baseline: System Requirements Review (SRR) at T+30 Days, Preliminary Design Review (PDR) at T+90 Days, Critical Design Review (CDR) at T+150 Days, Factory Acceptance Test (FAT) at T+300 Days, System Delivery at T+330 Days, Site Acceptance Test (SAT) at T+345 Days, and Operator Training at T+355 Days.

Block 9: See General Instructions for Distribution Statement.

Blocks 10 - 13:

a. First submission is due no later than 45 days after contract award (DAC).

b. Subsequent submissions are due monthly, no later than the 15th calendar day of the month following the reporting period.

c. A final report is required upon completion of the last major deliverable.

Block 14:

a. Contractor shall submit via current Enterprise Data System.

b. The text-based report shall be compatible with Microsoft Word or Adobe PDF. The Integrated Master Schedule (IMS) shall be delivered in its native file format (e.g., Microsoft Project).

AFLCMC/WIIP 1

BLK16 1

15.TOTAL 0 2 0

G. PREPARED BY

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelly, Tyler 2d Lt

J. SIGNATURE

22-Apr-2026 04:00

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER SESS

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Technical Report-Study/Services

3. SUBTITLE

Configuration Management Approach

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80858D/T

5. CONTRACT REFERENCE

SOW PARA 3.2

6. REQUIRING OFFICE

AFLCMC/WIIE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

ONE/R

12. DATE OF FIRST SUBMISSION

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4:

a. The requirements of DI-SESS-80858D are tailored. The following paragraphs are deleted and not required: 3.a, 3.c, and 3.e.

b. The document shall describe the contractor's straightforward approach for identifying the initial hardware/software baseline (DID para 3.b) and for tracking and reporting the "as-built" and final "as-delivered" configuration (DID para 3.d).

Block 9: See General Instructions for Distribution Statement.

Blocks 11 - 13: A draft is due for review no later than 30 days after contract award. The final version is due 14 days after receipt of Government comments.

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. The document shall be submitted in a format compatible with Microsoft Word or Adobe PDF.

AFLCMC/WIIE 1

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER PSSS

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A003

2. TITLE OF DATA ITEM

Proposed Spare Parts List

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-PSSS-80134B/T

5. CONTRACT REFERENCE

SOW PARA 8.1

6. REQUIRING OFFICE

AFLCMC/WIIL

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4:

a. Per SOW 8.1, this deliverable shall be a simplified list, not a formal analysis report. The DID is tailored to remove all requirements for analytical data.

b. The requirement in the DID introduction to explain "assumptions, formulas, or models" is deleted.

c. The following DID paragraphs are deleted and not required: 3.c, 3.d, 3.e, 3.j, 3.k, 3.l, and 3.m.

Block 9: See General Instructions for Distribution Statement.

Blocks 11 - 13: The list shall be delivered with the equipment.

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. Electronics deliverables shall be submitted in a machine-readable format compatible with Microsoft Excel.

AFLCMC/WIIL 1

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

PREVIOUS EDITION MAY BE USED.

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER SESS

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A004

2. TITLE OF DATA ITEM

Product Engineering Design Data and Associated Lists

3. SUBTITLE

Product Drawing/Model Package

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-81000F/T

5. CONTRACT REFERENCE

SOW PARA 3.1.2

6. REQUIRING OFFICE

AFLCMC/WIIE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft Final

Reg Repro

16. REMARKS

Block 4:

a. This Technical Data Package (TDP) shall be tailored to document the "as-built" configuration for organic maintenance and future modification only.

b. The following paragraphs of DI-SESS-81000F are deleted and not required: 4.a, 4.b, 4.d, 4.e, 4.j, 4.k, 4.l, 4.n, 4.o, 4.q, 7.1, 7.2, and 7.3.

c. The 2D drawing set shall include installation/assembly drawings, fabrication drawings for all custom parts (e.g., enclosure, patch panels), and all schematic/interconnect wiring diagrams.

e. Per SOW footnote 3.a, proprietary design data for Commercial- Off-The-Shelf (COTS) items is not required. COTS items shall be identified by part number in the Bill of Materials (CDRL A009).

Block 9: See General Instructions for Distribution Statement.

Blocks 11 - 13:

a. A Preliminary TDP shall be delivered for review no later than 14 days after the Critical Design Review (CDR).

b. The Final "As-Built" TDP shall be delivered no later than 15 days after successful completion of the Site Acceptance Test (SAT).

Block 14: All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

BLK16 1

AFLCMC/WIIE 1

15.TOTAL 0 2 0

G. PREPARED BY

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER MISC

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A005

2. TITLE OF DATA ITEM

Technical Report - Study/Services

3. SUBTITLE

Test/Inspection Report (FAT Results)

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508B/T

5. CONTRACT REFERENCE

SOW PARA 7.2

6. REQUIRING OFFICE

AFLCMC/WIIE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

8. APP CODE

NA

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4: DID is tailored as follows:

a. The report shall document the results of the Factory Acceptance Test (FAT) as required by SOW 7.2.

b. DID Section I shall serve as an Executive Summary, stating the overall pass/fail result.

c. DID Section II shall consist of a completed copy of the Government-approved FAT Procedure, showing the recorded result of each step.

Block 9: See General Instructions for Distribution Statement.

Blocks 11 - 13: The report shall be delivered with the equipment

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. The deliverable shall be submitted in a format compatible with Adobe PDF.

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER MISC

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A006

2. TITLE OF DATA ITEM

Scientific and Technical Reports

3. SUBTITLE

Electromagnetic Capability Compliance Data

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80711A

5. CONTRACT REFERENCE

SOW PARA 7.3

6. REQUIRING OFFICE

AFLCMC/WIIE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

SEE BLOCK 16

12. DATE OF FIRST SUBMISSION

8. APP CODE

NA

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4:

a. This deliverable shall be a data package compiling existing manufacturer data, not a formal scientific report.

b. The requirement in DID paragraph 10.2 to format the report in accordance with ANSI/NISO Z39.18 is deleted.

c. The content shall consist of all available Original Component Manufacturer (OCM) compliance data for the commercial items used in the system, specifically addressing MIL-STD-461, HERP, HERF, and HERO, as required by SOW 7.3.

d. The submission shall be a single package (e.g., a consolidated PDF) containing a cover page and all collected OCM documents in their original format.

Block 9: See General Instructions for Distribution Statement.

Blocks 10 - 13: The package is due 90 days after contract award

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. The deliverable shall be submitted as a consolidated package (e.g., a single PDF).

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

CUI Category:

Distribution/Dissemination Control:

POC:

Page 1 of

DD FORM 1423, FEB 2024 CUI Controlled By:

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER MGMT

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A007

2. TITLE OF DATA ITEM

Data Accession List (DAL)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81453C

5. CONTRACT REFERENCE

SOW PARA 3.5

6. REQUIRING OFFICE

AFLCMC/WIIP

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

QRTLY

12. DATE OF FIRST SUBMISSION

8. APP CODE

NA

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4:

a. Per SOW 3.5, this list shall identify all technical data generated by the contractor or its subcontractors that is not otherwise specified for delivery on the DD Form 1423.

b. The list shall be cumulative.

c. The list shall contain, at a minimum, the following data fields for each item: a unique item number, a descriptive title, the date of creation/finalization, and the native file format.

Block 9: See General Instructions for Distribution Statement.

Blocks 10 - 13:

a. The initial submission is due no later than 20 days after the end of the first calendar quarter following contract award.

b. Subsequent submissions are due quarterly, no later than 20 days after the end of each calendar quarter.

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. The deliverable shall be submitted in a machine-readable format compatible with Microsoft Excel.

AFLCMC/WIIP 1

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER PSSS

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A008

2. TITLE OF DATA ITEM

Bill of Materials (BOM) for Logistics and Supply Chain Risk Management

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-PSSS-81656B/T

5. CONTRACT REFERENCE

SOW PARA 4

6. REQUIRING OFFICE

AFLCMC/WIIL

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

SEE BLOCK 16

12. DATE OF FIRST SUBMISSION

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4:

a. Per SOW 4, this BOM shall document the final "as-delivered" configuration of the TACO Cart and shall serve as the project's Software Version Description (SVD).

b. For the purposes of this deliverable, the "OEM" is defined as the Original Component Manufacturer (OCM) of a given part (e.g., Keysight, AMPEX). The duplicative "Manufacturer's" data fields are deleted.

c. The following additional DID fields are deleted and not required: OEM’s Facility Clearance Level, COG, Alternate For, and Service Bulletin Applicability.

d. The BOM indenture level shall be limited to the major integrated components. The contractor is not required to provide data for items internal to the COTS components.

e. All software and firmware version numbers must be documented as required by SOW 4.

Block 9: See General Instructions for Distribution Statement.

Blocks 10 - 13: The final "as-delivered" BOM is due no later than 10 days after successful completion of the Site Acceptance Test (SAT), as required by SOW 4.

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. The deliverable shall be provided as an electronically editable, machine-readable, Comma Separated Values (CSV) text file as required by the DID.

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER ADMN

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A009

2. TITLE OF DATA ITEM

Presentation Material

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-ADMN-81373/T

5. CONTRACT REFERENCE

SOW PARA 8.3

6. REQUIRING OFFICE

AFLCMC/WIIL

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

SEE BLOCK 16

12. DATE OF FIRST SUBMISSION

8. APP CODE

NA

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Block 4:

a. Per SOW 8.3, the deliverable shall consist only of a copy of the presentation file(s) (e.g., Microsoft PowerPoint, PDF) used during the hands-on operator training to supplement the commercial manuals.

b. The requirements of DID paragraph 10.2 are deleted. The contractor is not required to provide a text of the accompanying verbal material or include a disclaimer.

Block 9: See General Instructions for Distribution Statement.

Blocks 10 - 13: The material is due no later than 5 days after completion of the training event.

Block 14:

a. All submissions shall be made via the Government's AF-PLM instance of Teamcenter.

b. The deliverable shall be submitted in its native format (e.g., Microsoft PowerPoint) or Adobe PDF.

Larson, Nathan

H. SIGNATURE

22-Apr-2026 04:00

I. APPROVED BY

Kelley, Tyler 2d Lt

Controlled By:

CUI Category:

Distribution/Dissemination Control:

POC:

DD FORM 1423, FEB 2024 CUI

PREVIOUS EDITION MAY BE USED.

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM ■ OTHER IPSC

D. SYSTEM/ITEM

TACO Cart

E. CONTRACT/PR NO.

FA8689-26-Q-B001

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A010

2. TITLE OF DATA ITEM

Government Furnished Property Inventory and Forecasting Report

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-IPSC-81947B/T

5. CONTRACT REFERENCE

SOW PARA 8.6

6. REQUIRING OFFICE

AFLCMC/WIIL

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

ANNLY

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b…