Draft_CDRL_Package_B52_Crypto_Mod_Group_A_Kit_Production.pdf

PDF 1 MB Posted Jul 29, 2026

Attached to: B-52H Cryptographic Modernization Program, Request For Information (RFI) For Producing (Manufacture and Assemble) and Delivering B-52H Cryptographic Modernization Production Kits
Solicitation number: FA8628-2X-X-00XX
Issued by: Department of the Air Force Materiel Command Lifecycle Management Center

About this file

Written by GovTribe AI · Jul 29, 2026

This document is a Contract Data Requirements List (CDRL) General Instructions for the Crypto Group A Kit Production Program, prepared by the Air Force Life Cycle Management Center (AFLCMC), Bombers Directorate, dated April 20, 2026. The CDRL establishes data deliverables required from the contractor and specifies submittal, inspection, approval, acceptance, and distribution requirements. Data must be delivered to the LCMP tool or other government-designated configuration management/data management systems.

The CDRL includes 23 data items with specific delivery requirements across multiple categories. Key deliverables include specification change notices, status reports on kit production and deliveries, meeting agendas and minutes, configuration audit reports, engineering and contract change proposals, management plans, risk management reports, supply chain risk management documentation, counterfeit prevention plans, bill of materials, obsolescence alerts, and program protection implementation plans. Delivery dates are tailored to each item, with frequencies ranging from as-required to monthly submissions. For items requiring government approval (designated "A"), the government will respond within 45 calendar days via LCMP or contracting officer letter. Resubmittals must be completed within 30 days of notification, with changes marked by vertical lines and documented in revision summaries. Draft submittals must be marked "DRAFT" and changed to "FINAL" upon approval. All data must comply with specific marking requirements including distribution statements (D or E), CUI markings, export-controlled warning statements, and destruction notices. Electronic submissions must follow file naming conventions with metadata populated in document properties, and CAD files must be delivered in native format plus STEP format per ISO 10303:242-2022.

View the file

Other files

File	Type	Posted
RFI_B-52_Cryptographic_Modernization_Program_Rev1_07.30.26.docx	DOCX document	Aug 4, 2026
RFI_B-52_Cryptographic_Modernization_Program_Rev1.docx	DOCX document	Jul 30, 2026
RFI_B-52_Cryptographic_Modernization_Program.docx	DOCX document	Jul 29, 2026
Draft_ SOW_B52_Crypto_Mod_Group_A_Kit_Production_7-15-26.docx	DOCX document	Jul 29, 2026
SOW_Appendix_1_Crypto Group A Kit_Spares List_25 Apr 25.docx	DOCX document	Jul 29, 2026

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Contract Data Requirements List (CDRL)

General Instructions for the

Crypto Group A Kit Production Program

April 20, 2026

CONTRACT NUMBER:

DELIVERY ORDER:

Prepared by:

Bombers Directorate (AFLCMC/WB) B-52 Program Office, B-52 Division (AFLCMC/WBD) Air Force Life Cycle Management Center (AFLCMC)

WPAFB, OH 45433-7148

CDRL MODIFICATION MATRIX

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

PROPOSAL NO. CDRL REV

DATE CDRL/PAGES REVISED

Contract Award Original

P00001 DD-MMM-YYYY

TABLE OF CONTENTS

1. APPLICABLE DOCUMENTS

2. REFERENCE DOCUMENTS

3. DATA DELIVERIES

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. ELECTRONIC DATA TRANSMISSION

4.1. Submission

4.2. Delivery Non-Compliance

4.3. Editable Format Requirements

5. LETTERS OF TRANSMITTAL (LT)

6. MODIFICATION OF DATA REQUIREMENTS

7. COMMON ABBREVIATIONS

8. MARKING TECHNICAL DOCUMENTATION

8.1. Distribution Marking System

8.2. Marking Technical Data

8.3. Distribution Statements

8.4. Controlling Office

8.5. Export-Controlled Warning Statement

8.6. Destruction Notice

9. MAILING LISTS

1. APPLICABLE DOCUMENTS

Data Item Descriptions (DIDs)/DD Forms 1664, are identified in Block 4 of the individual Contract Data Requirements List (CDRL)/DD Form 1423. All DIDs are available to the contractor at the following website: http://quicksearch.dla.mil/

2. REFERENCE DOCUMENTS

DoD 5220.22-M National Industrial Security Program Operating Manual

DoD Manual

5200.01 Vols 1- 4

DoD Information Security Program and Protection of Sensitive Compartmented Information (SCI)

DoDD 5230.24 Distribution Statements on Technical Documents DoDD 5230.25 Unclassified Technical Data Disclosure DoD 5010.12-M Procedures for the Acquisition and Management of

Technical Data

3. 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. The Contractor delivers data to the LCMP tool or other Government designated configuration management/data management (CM/DM) delivery system.

3.1. DELIVERY DATES

In the event a CDRL delivery date falls on a Saturday or Sunday, the delivery will be made by Friday to be counted as an on-time delivery. Unless otherwise specified in Block 16 of the CDRL, all references to “days” will refer to calendar days.

3.2. TAILORED DATA ITEMS

Tailoring instructions are as described in Block 16 of each affected 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.

3.3. APPROVAL OF DATA

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 respond via LCMP; or by issuing a Contracting Officer (CO) letter or email to the contractor within 45 calendar days, unless otherwise specified on the CDRL, Block 16. This does not apply to Engineering Change Proposals (ECPs) or Specification Change Notices (SCNs). Any ECP will be reviewed and briefed to the Government Configuration Control Board (CCB) for disposition. Approval will be by contract modification. SCNs will be briefed to and reviewed by the Government for disposition. Approval of the SCN will be via CO letter and incorporated via a future contract modification.

http://quicksearch.dla.mil/

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. The Government has the right to disapprove any data submittal(s) not in compliance with contract requirements.

3.4. RESUBMITTAL OF DATA

If resubmittal of a CDRL is required, it shall be resubmitted within 30 calendar days after CO notification, unless otherwise specified. Should the contractor disagree with the resubmittal requirements, they shall submit their comments to the CO within 30 calendar days of notification. Each page of a resubmittal 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. This summary shall include as a minimum:

• Reason for the revision

• Brief description of the changes made

• Revision identification letter or number and revision date

NOTE: The 1423 takes precedence.

3.5. FINAL SUBMITTAL OF DATA

For the final delivery of each data item in the contract/delivery order, the contractor shall clearly state in the Letter of Transmittal (LT), 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 method of submittal - individual DD Form 250s are required only if indicated in Block 7. All other submittals shall be via a LT.

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. No classified data is ever sent or uploaded via the CM/DM system or normal e-mail channels. The contractor shall submit classified data via SIPR or a non-executable password encrypted disc.

4. ELECTRONIC DATA TRANSMISSION

4.1. SUBMISSION

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 Repro” of the CDRL. Draft submittals shall be marked “DRAFT”. Upon approval of final version all “DRAFT” markings shall be removed and “FINAL” shall be placed on the front cover.

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. EDITABLE FORMAT REQUIREMENTS

When the Contractor is required to make deliveries in Microsoft (MS) Excel or in MS Project, the Contractor shall submit a second, duplicate copy in a .pdf format. The two copies shall be identical and shall be submitted together. The .pdf file will be documented as the formal data delivery. Financial information provided in excel spreadsheets should be able to be manipulated.

All plots and graphs shall be accompanied by the data points and/or equations used to generate them.

For plots of discrete data points, the data points shall be included in a table either in the body of the document or as an attachment/appendix. Tables longer than half a page should be placed in an attachment/appendix. For data sets more than two pages, the data may be delivered in a separate file, either as a Microsoft Excel workbook (.xlsx) or as a comma separated values (.csv) file instead of being embedded in the main document. For all cases, the data points shall show the full precision used to generate the plots.

For graphs generated from equations, the equations shall be provided in the document along with definitions and values of all parameters. The individual data points are not required for equation-based graphs. The document shall include an explanation of how the equation was determined. Long explanations or mathematical derivations may be placed in an appendix instead of in the body of the document.

4.3.1 FILE NAMING CONVENTIONS

<Document Number> <Revision> <Program> <Document Title> <Draft> <Date>.<ext> <Document Number> The document number from the title page <Revision>: Omit for new documents, otherwise like "Rev A" <Program>: "B-52" for platform level documents; the program acronym/short name otherwise <Document Title>: As printed on the document title page, abbreviations/acronyms permitted.

<Draft>: only for draft documents, omit for released documents <Date>: YYYYMMDD format; release date for final versions, submission date for drafts <ext>: The file extension applied by the application used to create the file Filename elements shall be separated by spaces

4.3.2 METADATA

Electronic deliveries shall have the following metadata/document properties fields populated.

The "date" field shall be the release date for final versions or the submission date for drafts.

PDF Document Properties fields:

Title - fully spelled out, no acronyms Author - Optional Subject - Program name, fully spelled out Key Words: B-52, program short name/acronym, relevant terms and acronyms Custom Fields: Document Number, Date, Revision (Draft, New, A…), Distribution (D, E, FEDCON, etc), Contract Number, DO Number

Word/PowerPoint/Excel metadata fields (may need to select "Show All Properties") Title - Fully spelled out, no acronyms Tags - B-52, program short name/acronym, relevant document key words/acronyms Comments - Optional Status - Draft, Rev New, Rev A…, and date Categories - B-52

Subject - Program Name-fully spelled out Company – Optional

4.3.3 CAD FILES:

CAD files shall be delivered in the native format of the tool used to create them. In addition, CAD files shall be delivered in STEP file format adhering to ISO 10303:242-2022 or later.

5. LETTERS OF TRANSMITTAL (LT)

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

• Contractor’s POC, Contractor’s address, date of letter

• Contract number, delivery order, CLIN, and program name letter control number

• Document control number, document revision level, and document date

• CDRL sequence number and DID Number

• Data Title/Subtitle

• Reason/frequency of submittal (monthly, draft, final, update, etc.)

• List of distribution addressees as identified in Block 14 of the CDRL

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. MODIFICATION OF DATA REQUIREMENTS

During the performance of this contract, the CO may unilaterally increase or decrease the number of addressees and/or number of copies the technical office requires, or may make other administrative or clarification changes to the CDRL. Modifications to the CDRL package shall be incorporated into the contract via contract modification.

The amendment shall be at no change in contract price provided the increase for an individual line item of data is not greater than 150% nor a decrease of less than 50% in the total number of copies initially specified in the CDRL. In the event of an increase greater than 150% or of a decrease greater than 50%, the parties will negotiate any equitable adjustment in accordance with the procedures of the “Changes” clause.

The CO may unilaterally make other administrative and/or clarification changes to the CDRLs.

The contract price will constitute full satisfaction of any entitlement of equitable adjustment under the “Changes” clause provided the contractor agrees to accept such change at no change in contract price.

7. COMMON ABBREVIATIONS

Block 7 LT Letter of Transmittal Block 8 A Approval

N/A Approval Not Required BLK 16 See Block 16 for further instructions

Blocks 10, 12 & 13 ANNLY Annually ASREQ As Required BLK 16 See Block 16 for further instructions EOC End of Contract MTHLY Monthly ONE/R Once with Revisions QRTLY Quarterly R/ASR Revisions as Required SEMIA Semi-Annually

8. MARKING TECHNICAL DOCUMENTATION

8.1. DISTRIBUTION MARKING SYSTEM

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 Instructions 5230.24, Distribution Statements on Technical Documents - Change 1, 28 April 2016. 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.

Distribution statements have been annotated in Block 9 of each CDRL and defined in the following paragraph 8.3. 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.

8.2. MARKING TECHNICAL DATA

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.

Any documents provided to the government with STINFO Distribution Statement C or D on the cover or title page will be assumed to contain only information that is releasable to government or DoD contractors as authorized by the distribution statement. Any proprietary markings within the document, including but not limited to headers, footers, or figures, will be ignored and may be removed by the program office.

Certain types of technical data preclude placing the entire notice on the document. To accommodate this problem, each distribution statement contains an authorized abbreviation form. Abbreviated distribution statements are to be used only when space precludes placing the entire notice on the document. The use and wording of these statements are described in the following paragraph.

8.3. DISTRIBUTION STATEMENTS

The appropriate distribution must appear on the cover and title page of each document submitted, including the first sheet of each drawing. The distribution statement must be IAW Block 9 of the CDRL. Below are two examples:

DISTRIBUTION STATEMENT D

DISTRIBUTION IS AUTHORIZED TO THE DEPARTMENT OF DEFENSE AND U.S.

DOD CONTRACTORS ONLY; REASON (EXPORT-CONTROLLED/CTI-EXAMPLE),

(DATE OF DETERMINATION-DD/MM/YY). OTHER REQUESTS FOR THIS

DOCUMENT SHALL BE REFERRED TO THE B-52 PROGRAM OFFICE, B-52

DIVISION (AFLCMC/WBD) WPAFB, OH 45433-7148,

AFLCMC.WBD.Coordination@us.af.mil

The abbreviated form is: “Distribution Statement D, Gov’t and Contractors, AFLCMC/WBD, WPAFB, OH”

DISTRIBUTION STATEMENT E

DISTRIBUTION AUTHORIZED TO DOD COMPONENTS ONLY; REASON

(EXPORT-CONTROLLED/CTI-EXAMPLE), (DATE OF DETERMINATION-

DD/MMM/YYYY). OTHER REQUESTS FOR THIS DOCUMENT SHALL BE

REFERRED TO THE B-52 PROGRAM OFFICE, B-52 DIVISION (AFLCMC/WBD)

WPAFB, OH 45433-7148, AFLCMC.WBD.Coordination@us.af.mil mailto:AFLCMC.WBD.Coordination@us.af.mil

In accordance with DOD Instruction 5200.48, Controlled Unclassified Information (CUI) guidelines for documents, the Contractor shall submit documentation to the Government with the CUI markings.

8.4. CONTROLLING OFFICE

The cover pages for documents being submitted shall now include the following statement:

Header: CUI Footer: CUI

8.5. EXPORT-CONTROLLED WARNING STATEMENT

In addition to the distribution statement, the marking system also requires the use of a warning notice on all documents that contain export-controlled technical data. The notice is to be used in conjunction with the distribution statement.

"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 Control Reform Act of 2018 (Title 50, U.S.C., Chapter 58, Sec. 4801-4852). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with the provisions of DoD Directive 5230.25."

8.6 Destruction Notice

Destruction Notice for Unclassified Documents: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

In addition to the distribution statement, the marking system also requires the use of a warning notice on all documents which contain export-controlled technical data. The notice is to be used in conjunction with the distribution statement.

9. MAILING LISTS

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

Controlled by: US Air Force Controlled by: AFLCMC/WBD CUI Category: CUI Distribution Statement: X

POC: AFLCMC/WBD

AFLCMC/WBD

Attn: B-52 CM/DM 2690 Loop Road West

WPAFB OH 45433

DCMA AIMO Oklahoma City 6201 S Air Depot Blvd Oklahoma City, OK 73135-5914

DCMA AIMO Oklahoma City Attn: Larry Dupree larry.w.dupree.civ@mail.mil

(405) 763-8659 mailto:larry.w.dupree.civ@mail.mil

4/20/2026 9:59:36 AM EDT CDRL Table of Contents

CONTRACT #:

CONTRACTOR: TBD

SET NAME: B-52 CM/MUOS Group A Kit SYSTEM ITEM: B-52 Crypto Group A Production Kit

PROGRAM: B-52 Crypto

DATA ITEM REQUIRING OFFICE AUTHORITY/TITLE/SUBTITLE SOW PARAGRAPH

A018 AFLCMC/WBD (CM) DI-SESS-80643E SOW 3.5.1

Specification Change Notice (SCN)

A022 AFLCMC/WBD (PM) DI-MGMT-80368A SOW 3.1, 3.3.2

Status Report

Kit Production Status Delivery

A056 AFLCMC/WBD (PM) DI-ADMN-81249C SOW 3.1, 3.1.6, 3.3.6.1

Meeting Agenda

A057 AFLCMC/WBD (PM) DI-ADMN-81250C SOW 3.1, 3.1.6

Meeting Minutes

A058 AFLCMC/WBD (CM) DI-SESS-81022E SOW Para 3.3.6.1

Configuration Audit Summary Report and Certification

A061 AFLCMC/WBD (CM) DI-ADMN-81401C SOW 3.5.1

Contract Change Proposal (CCP)

A068 AFLCMC/WBD (CM) DI-MGMT-81453B SOW 3.5.2.1

Data Accession List (DAL)

A073 AFLCMC/WBD (CM) DI-SESS-80639E SOW 3.5.1

Engineering Change Proposal (ECP)

A094 AFLCMC/WBD (PM) DI-MGMT-80004A SOW 3.1.1

Management Plan

Program Management Plan

A095 AFLCMC/WBD (EN) DI-MGMT-80258C SOW 3.5.4

Acquisition and Sustainment Data Package (ASDP) Material Improvement Project (MIP) Report

Deficiency Report

A111 AFLCMC/WBD (CM) DI-SESS-80640E SOW 3.5.1

Request for Variance (RFV)

A121 AFLCMC/WBD (LG) DI-MGMT-81948 SOW 3.5.3

Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

A124A AFLCMC/WBD (PM) DI-MGMT-81809 SOW 3.1.3

Risk Management Status Report

Program Risk Management Status Report

4/20/2026 9:59:36 AM EDT CDRL Table of Contents

A124B AFLCMC/WBD (PM) DI-MGMT-81809 SOW Para 3.1.5

Risk Management Status Report

SCRM Report

A141A AFLCMC/WBD (PM) DI-MGMT-81861C SOW Para. 3.1.2

Integrated Program Management Data and Analysis Report

IPMDAR

A146 AFLCMC/WBD (WP) DI-MISC-81832 SOW Para. 3.8.1

Counterfeit Prevention Plan

A156 AFLCMC/WBD (LG) DI-PSSS-81656B SOW 3.2.2

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

A157 AFLCMC/WBD (LG) DI-MGMT-81941 SOW 3.5.3

Obsolescence Alert Notice

A160 AFLCMC/WBD (LG) DI-MGMT-82256 SOW 3.1.4

Supply Chain Risk Management (SCRM) Plan

A205 AFLCMC/WBD (LG) DI-MGMT-81804A SOW 3.2.1

Item Unique Identification (IUID) Marking Activity, Validation and Verification Report

A216 AFLCMC/WBD (CYBER) DI-MGMT-82144A SOW 3.8

Program Protection Implementation Plan

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

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

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A018

2. TITLE OF DATA ITEM

Specification Change Notice (SCN)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80643E

5. CONTRACT REFERENCE

SOW 3.5.1

6. REQUIRING OFFICE

AFLCMC/WBD (CM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLK 4: Either DD Form 1696 SCN or contractor format is acceptable.

BLKs 10, 12, and 13: Submittal of SCN is tied to the submittal, approval and completion of ECPs. Draft version of the SCN should be submitted with ECPs and final version 30 days after Government notification of approval. Government comments to be submitted within 30 days of receipt. Contractor shall incorporate comments and resubmit within 30 days after receipt of Government comments.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

DCMA 1 1

AFLCMC/WBD 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 1 of 1 Pages

17. PRICE GROUP

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A022

2. TITLE OF DATA ITEM

Status Report

3. SUBTITLE

Kit Production Status Delivery

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80368A

5. CONTRACT REFERENCE

SOW 3.1, 3.3.2

6. REQUIRING OFFICE

AFLCMC/WBD (PM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

N/A

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLK 4: This DID is tailored as follows:

The following information should be contained within the report:

a.) The status of ordered parts, actual and projected b.) The status of kit builds, actual and projected c.) The status of kit deliveries to the Government, actual and projected d.) Accomplishments to date e.) Difficulties encountered f.) Status achieved to planned goals g.) The resources expended

Delete Paragraph 3.2.3

BLKS: 10, 12 and 13: The Contractor shall submit the first report NLT 60 days after contract award. The Contractor shall submit monthly thereafter until all kits are delivered. The Contractor shall submit NLT the 15th of the month.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER ADMN

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A056

2. TITLE OF DATA ITEM

Meeting Agenda

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-ADMN-81249C

5. CONTRACT REFERENCE

SOW 3.1, 3.1.6, 3.3.6.1

6. REQUIRING OFFICE

AFLCMC/WBD (PM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

N/A

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

BLK 5/10: SOW Para 3.1 (Contract Kick-Off Meeting): 1 time deliverable SOW Para 3.1.6 (Program Management Review): 2 deliverables per year SOW Para 3.3.6.1 (Kit Configuration Audit): 1 time deliverable

BLKS 10, 12 and 13: The Contractor shall submit agendas and presentation materials 7 days prior to the meeting.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER ADMN

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A057

2. TITLE OF DATA ITEM

Meeting Minutes

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-ADMN-81250C

5. CONTRACT REFERENCE

SOW 3.1, 3.1.6

6. REQUIRING OFFICE

AFLCMC/WBD (PM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

BLK 5/10: SOW Para 3.1 (Contract Kick-Off Meeting): 1 time deliverable SOW Para 3.1.6 (Program Management Review): 2 deliverables per year

BLKs: 10, 12 and 13: The contractor shall submit 7 days after completion of each meeting.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO.

TDB

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A058

2. TITLE OF DATA ITEM

Configuration Audit Summary Report and Certification

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-81022E

5. CONTRACT REFERENCE

SOW Para 3.3.6.1

6. REQUIRING OFFICE

AFLCMC/WBD (CM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

Draft

Final

Reg Repro

16. REMARKS

BLKs 10, 11, 12:

The Contractor shall deliver NLT 30 days after the Audit has been closed.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

DCMA 1 1

AFLCMC/WBD 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER ADMIN

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A061

2. TITLE OF DATA ITEM

Contract Change Proposal (CCP)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-ADMN-81401C

5. CONTRACT REFERENCE

SOW 3.5.1

6. REQUIRING OFFICE

AFLCMC/WBD (CM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLK 8: Approval will be via the Government Configuration Control Board decision/Contract Modification.

BLK 9: See General Instructions for detailed requirements.

BLKs 10, 12 & 13:

a. The Contractor shall submit CCPs upon written request from the contracting officer. The Contractor's price shall be valid for the time specified on the Delivery Order.

b. The Contractor shall submit CCPs in two volumes as follows:

1. Technical volume

2. Cost volume

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A068

2. TITLE OF DATA ITEM

Data Accession List (DAL)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81453B

5. CONTRACT REFERENCE

SOW 3.5.2.1

6. REQUIRING OFFICE

AFLCMC/WBD (CM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

N/A

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLKs 10, 12 and 13: Submit 90 days after contract award and quarterly thereafter. The DAL will contain data not contractually delivered as a CDRL and is generated to meet the requirements of this contract, and under configuration control (such as CMPro, Clear Case, DOORS, and/or equivalent systems) by the Contractor. The DAL will be updated and delivered quarterly throughout the contract period.

The Contractor shall submit the requested data within 10 working days.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A073

2. TITLE OF DATA ITEM

Engineering Change Proposal (ECP)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80639E

5. CONTRACT REFERENCE

SOW 3.5.1

6. REQUIRING OFFICE

AFLCMC/WBD (CM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: The Contractor shall include a plan and a price for the update of the BOM and the IPB.

With each ECP that affects any baseline specification, an SCN shall be submitted. Once the ECP has been approved, as part of the contract modification, a new revision to that specification shall be provided in accordance with the specification CDRL.

Block 8: Approval will be via Configuration Control Board (CCB) Contract notification.

Block 10, 12 & 13:

a. The Contractor shall submit ECPs upon written request from the Contracting Officer.

b. The Contractor shall submit ECPs in two volumes as follows:

1. Technical volume

2. Cost volume

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A094

2. TITLE OF DATA ITEM

Management Plan

3. SUBTITLE

Program Management Plan

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80004A

5. CONTRACT REFERENCE

SOW 3.1.1

6. REQUIRING OFFICE

AFLCMC/WBD (PM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLKS 10, 12, and 13:

The Contractor shall submit the draft 10 days prior to Contract Kick Off Meeting. The Contractor shall submit a final NLT 60 days after receipt of government comments. The Contractor shall submit annual updates. In the event there are no changes to the plan, the Contractor shall submit a letter stating there are no changes to the most recent submittal.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A095

2. TITLE OF DATA ITEM

Acquisition and Sustainment Data Package (ASDP) Material Improvement Project (MIP) Report

3. SUBTITLE

Deficiency Report

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80258C

5. CONTRACT REFERENCE

SOW 3.5.4

6. REQUIRING OFFICE

AFLCMC/WBD (EN)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLKs 4, 10, 12 and 13: This DID is tailored as follows:

The submittal of initial reports, interim and final reports shall be in accordance with TO 00-35D-54.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

DCMA 1 1

TINKER 1 1

AFLCMC/WBD (WP) 1 1

15. TOTAL 3 3 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A111

2. TITLE OF DATA ITEM

Request for Variance (RFV)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80640E

5. CONTRACT REFERENCE

SOW 3.5.1

6. REQUIRING OFFICE

AFLCMC/WBD (CM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: This DID is tailored as follows: Include a Corrective Action Plan for each Major RFV.

BLK 8: Completed RFV package requires approval by the CCB and Contractor notification will be provided via PCOL.

BLKs 12 and 13: Submission due 30 days after identification of need for variance. The Contractor shall submit the final RFV 30 days after Government response to draft RFV.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A121

2. TITLE OF DATA ITEM

Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81948

5. CONTRACT REFERENCE

SOW 3.5.3

6. REQUIRING OFFICE

AFLCMC/WBD (LG)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLK 2: The Title of the Data Item: Diminishing Manufacturing Sources and Material Shortages Management Plan.

BLKs 10, 12 and 13: The Contractor shall submit initial 60 days after contract award. The Contractor shall submit an updated plan every 12 months.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A124A

2. TITLE OF DATA ITEM

Risk Management Status Report

3. SUBTITLE

Program Risk Management Status Report

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81809

5. CONTRACT REFERENCE

SOW 3.1.3

6. REQUIRING OFFICE

AFLCMC/WBD (PM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

N/A

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

BLKs 12 and 13: Program status report initial submission due 90 days after contract award. Subsequent submission monthly. The report is due on the 15th of the month.

BLK 14: Submit data to the B-52 LCMP tool via LCMP Submit On-Demand CDRL Portal.

AFLCMC/WBD (WP) 1 1

DCMA 1 1

15. TOTAL 2 2 0

G. PREPARED BY

Jarrett Eckhardt Configuration/Data Manager

H. DATE

2026/04/20

I. APPROVED BY

Lisa Myers Program Manager

J. DATE

2026/04/20

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

B-52 Crypto Group A Production Kit

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A124B

2. TITLE OF DATA ITEM

Risk Management Status Report

3. SUBTITLE

SCRM Report

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81809

5. CONTRACT REFERENCE

SOW Para 3.1.5

6. REQUIRING OFFICE

AFLCMC/WBD (PM)

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10.…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Jul 29, 2026.