Updated Signed HSES CDRL Package_05302025_- JA4June2025 (002).pdf

CUI

CONTRACT DATA REQUIREMENTS LIST

(CDRL)

GENERAL INSTRUCTIONS

FOR THE:

C-5M SUPER GALAXY

Honeywell Software and Engineering Support (HSES) Program

CONTRACT/PR NUMBER: FD2060-24-31731

DATED: May 30, 2025

Company Awarded to:

HONEYWELL INTERNATIONAL, INC. EXHIBIT A-F

To Include: CDRL INSTRUCTIONS

ADDRESS LIST

CDRL TABLE OF

CONTENTS DD FORMS 1423-1

Prepared by C-5M Super Galaxy Division (WLS)

Air Force Life Cycle Management Center (AFLCMC) Robins Air Force Base (RAFB), GA 31098

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

Controlled by: USAF.

Controlled by: AFLCMC/WLS CUI Categories: CTI, EXPORT, Operations Security Information Distribution/Dissemination Controls: Distribution Statement D POC: Greg Purnell

CUI Page 2 of 15

CONTRACT DATA REQUIREMENTS LIST (CDRL) MODIFICATION MATRIX

This matrix identifies the Contract Data Requirements List (CDRL) changes as implemented by contract modification.

Change

Authority (ECP No., Mod

No., Proposal No., etc.)

CDRL

Revision

CDRL

Number

Date

Action/CDRL/Pages

Contract Award All (Insert date)

CCP ##### A ####, #### (Insert date) Updated Delivery Frequency

CUI Page 3 of 15

TABLE OF CONTENTS

Table of Contents

Prepared by:

CONTRACT DATA REQUIREMENTS LIST (CDRL) MODIFICATION MATRIX

TABLE OF CONTENTS

1 SCOPE

2 APPLICABLE DOCUMENTS

3 REFERENCE DOCUMENTS

4 DATA DELIVERIES

4.1 English Language

4.1 Delivery Dates and Times

4.2 Tailored Data Items

4.3 Data Submittal Approvals

4.4 Resubmittal of Data

4.5 Final Submittal of Data Deliveries

4.5 DD Form 250, Material Inspection and Receiving Report Requirements

4.6 Classified Data

5 ELECTRONIC DATA TRANSMISSION

5.1 Electronic Delivery

5.2 Alternative Delivery Formats

5.3 Editable Format Requirements

6 LETTER OF TRANSMITTAL

6.1 Required Format (General)

6.2 Required Format (Paper)

6.1 Required Format (Email)

7 COMMON ABBREVIATIONS IN DD FORM 1423-1

CUI Page 4 of 15

8 MODIFICATION OF DATA REQUIREMENTS

8.1 CDRL Changes

8.2 Changes to Contract Price (Limits & Conditions)

8.3 Subsequent Submittal

9 MARKING TECHNICAL DOCUMENTATION

9 Marking of Controlled Unclassified Information (CUI) and Technical Documentation.10

9.1 Controlled Unclassified Information

9.2 Distribution Marking System

9.3 Marking Technical Data

9.4 Distribution Statements for the Use on Technical Documents

9.5 Marking Non-Technical Documentation

9.6 Controlling Office

9.7 Export-Controlled Warning Statement

9.8 Destruction Notice

10 INTELLECTUAL PROPERTY/MARKINGS

12 CORRESPONDENCE FOR DATA/LETTER OF TRANSMITTALS

CUI Page 5 of 15

1 SCOPE

The Contract Data Requirements List (CDRL – DD Form 1423-1) establishes the data to be delivered by the Contractor to include the submittal, approval, and distribution requirements of all of the CDRL data items contained within. The data requirements are listed on the enclosed copies of the Department of Defense (DD) Forms 1423-1, Contract Data Requirements List. The Contractor is legally obligated to meet these requirements because the CDRL is a contractual document and, as such, is, therefore, binding in and of itself.

2 APPLICABLE DOCUMENTS

The order of precedence shall be the DD Form 1423-1 and associated continuation sheets, CDRL Instructions, and then the DIDs specified in Block 4 of the DD Form 1423-1. Tailored instructions are as described in Block 16 of each CDRL. If the data preparation instruction contained in Block 16 of the DD Form 1423-1 is different than the instruction contained in the DID (Block 4 of the DD Form 1423-1), the CDRL shall govern. Unless otherwise noted, all deliverables shall be in English language. The Data Item Descriptions (DIDs) specified in the CDRL are available electronically at the Acquisition Streamlining and Standardization Information System (ASSIST) database link noted below or by contacting the Contracting Officer (CO).

http://quicksearch.dla.mil/.

3 REFERENCE DOCUMENTS

DoD 5220.22-M, National Industrial Security Program (NISP) Manual (now Part 117 of Title 32, Code of Federal Regulations) DoD 5010.12-M, Procedures for the Acquisition and Management of Technical Data DoDI 5230.09, Clearance of DoD Information for Public Release DoDI 5230.24, Distribution Statements on DoD Technical Information DoDD 5230.25, Withholding of Unclassified Technical Data From Public Disclosure DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program DoDM 5200.01, Volume 1, Information Security Program: Overview, Classification, and Declassification DoDM 5200.01, Volume 2, DoD Information Security Program: Marking of Information DoDM 5200.01, Volume 3, DoD Information Security Program: Protection of Classified Information DoDI 5200.48, Controlled Unclassified Information (CUI) DAFI61-201, Management of Scientific and Technical Information

4 DATA DELIVERABLES

4.1.1 English Language

The Contractor Submission of Offer shall be in the English language. Offers received in other than English shall be rejected.

4.1.2 Delivery Dates and Times

The Contractor shall submit CDRL deliverables IAW with blocks 10, 11, 12, 13,14, and 16 of each CDRL as a minimum. In addition, the Contractor shall submit out-of-cycle updates whenever an update is required due to the program activities.

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

http://quicksearch.dla.mil/

KASPEREK-SAID, MICHELLE M CIV USAF AFMC 78 ABW/JA

This FAR clause is not applicable to the submission of CDRLs. Delete the FAR reference.

JOHNSON, WILLIAM D CTR AFMC AFLCMC/WLS

deleted

4.1.4 Timeliness of CDRL deliverables:

a. If the CDRL delivery date falls on a Saturday, the submittal must be delivered on the Friday prior to the Saturday delivery date, to be counted as an on-time delivery.

b. If the CDRL delivery date falls on a Sunday, the submittal must be delivered on the Monday following the Sunday delivery date, to be counted as an on-time delivery.

c. If the CDRL delivery falls on a federal holiday, the submittal must be delivered on the last workday before the federal holiday or the day after the federal holiday, to be counted as an on-time delivery.

d. Early CDRL delivery is permitted. The Contractor shall notify the Government when delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. There shall be no more than one late submission of deliverables per quarter. The Contractor shall deliver the revised data/document by the revised delivery date acceptable to the Government.

e.

4.2 Tailored Data Items

4.2.1 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.

4.3 Data Submittal Approvals

The following definitions apply to Block 8 of the DD Form 1423-1

4.3.1 An "A" designator in Block 8 of the CDRL indicates the Government will formally reply to each data submittal with (1) an approval, (2) approval with comments, (3) rejection, or (4) disapproval to ensure that contractor is in compliance with the DID and CDRL requirements. The Government will issue a response via a Procuring Contracting Officer (PCO) letter (PCOL) to the contractor within thirty (30) calendar days, unless otherwise specified on the DD Form 1423-1, Block 16. The Government will approve or reject the data/document within 45 calendar days from the Contractor delivery date. If the Government does not approve or reject the data/document within 45 calendar days from the Contractor delivery date, the Contractor can assume the Government approved the data/document and the Contractor can mark the data/document “approved.” This does not apply to Engineering Change Proposals (ECPs) and Contract Change Proposals (CCPs).

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

4.3.2 The Government will approve a data delivery with comments if there is a reasonable expectation the document can be corrected to meet the requirements. The Government will reject a data delivery if it is determined to be incomplete or inadequate to the point where a comprehensive review cannot occur. The Government will disapprove a data delivery if, after a comprehensive review, it is determined the document is not acceptable as prepared.

4.3.3 The forty-five (45) calendar days response time does not apply to Engineering Change Proposals (ECPs), or Contract Change Proposals (CCPs), or Requests for Variance (RFV). Any ECP, CCP, or RFV will be reviewed and briefed to the Government Configuration Control Board (CCB) for disposition. After the CCB, notice will be sent apprising the Contractor of the action taken, followed by a contract modification to implement the change.

4.3.4 For those CDRLs with an “N” or 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 the DID, and as tailored in block 16 of the DD Form 1423-1, are mandatory. All data submissions are subject to review and approval by the Government. If there is an “N” or an “N/A” in block 8, the Government will not provide a formal response back to the Contractor; however, the Government has the right to reject or disapprove any data submittal(s) through the PCO via a PCOL that are not in compliance with DID as well as the contract requirements.

KASPEREK-SAID, MICHELLE M CIV USAF AFMC 78 ABW/JA

The PWS, 4.2.2 states “The contractor shall notify the government if the CDRL does not meet the scheduled date and request a revised delivery date.” Recommend using the same language here.

JOHNSON, WILLIAM D CTR AFMC AFLCMC/WLS

Added language from 4.2.2 in the PWS

KASPEREK-SAID, MICHELLE M CIV USAF AFMC 78 ABW/JA

This language does not match up with 4.2.2 as drafted, “The Government shall approve or reject the data/document within 45 days of delivery date or the data/document can be marked approved by the contractor.”

JOHNSON, WILLIAM D CTR AFMC AFLCMC/WLS

Updated to match the PWS

KASPEREK-SAID, MICHELLE M CIV USAF AFMC 78 ABW/JA

PWS 4.2.2 provides for 45 days.

Updated to match the PWS

4.3.5 Draft submittals are not approval items. The contractor shall formally submit draft data item(s)

(when CUI Page 6 of 15

Page 7 of 15 CUI required by the DD Form 1423-1) for review and shall be marked as “draft.” However, draft submissions shall not alter the due date of first formal submission specified in CDRL or the CDRL remarks section respectively.

4.4 Resubmittals of Data

4.4.1 Unless otherwise specified, data submittals that are disapproved by the Government, shall be revised and resubmitted by the contractor within thirty (30) calendar days after receipt of PCOL. If the contractor cannot resubmit within fifteen (15) calendar days, the Government shall be notified within fifteen (15) calendar days, and a new suspense date will be mutually agreed upon.

4.4.2 When resubmission of data is directed, complete documents shall be submitted unless otherwise specified in the PCO letter. Each page of a resubmittal shall have changes indicated by a vertical line down the outer right margin to designate any areas of the document (including figures and tables) that have been revised. The document revision number shall be indicated both on the title page of the data delivery and in the header of each page of the data delivery.

4.4.3 The Contractor shall insert a “revision” page in each data delivery resubmitted. The revision page shall provide a history of changes made to the document. The page shall include the following, as a minimum:

• The reason for the revision (i.e., proposal number, modification number),

• A brief description of the changes made, and

• Revision identification letter or number and revision date

4.5 Final Submittal of Data Deliveries

4.5.1 For the final delivery against each data item in the contract/delivery order, the Contractor shall clearly state in its Letter of Transmittal (LT) that the last submittal is being made and that all contractual requirements concerning that data item have been fulfilled. The proper format and required information for the Contractor’s LTs is covered in section 6 below.

4.5.2 DD Form 250, Material Inspection and Receiving Report Requirements - Block 7 of the DD

Form 1423-1 directs the method of submittal. Individual DD Form 250s are required only if indicated in block 7. Otherwise, a Letter of Transmittal shall accompany all CDRL deliverables.

4.6 Classified Data

4.6.1 In the event a data delivery containing classified data shall be submitted, the Contractor shall submit the document to the classified email address provided on the DD Form 1423-1 or contact the Procuring Contracting Offer (PCO) for the correct mailing address(es). The Contractor shall submit the data delivery in accordance with the requirements established in the DD Form 254, Contract Security Classification Specification. Classified information shall be submitted by Secret Internet Protocol Router Network (SIPRNet) with a LT on the data delivery. In addition, the Contractor shall submit an unclassified copy of the transmittal letter.

5 Electronic Data Transmission

5.1 Electronic Delivery

5.1.1 The Contractor shall submit all CDRL deliverables in accordance with the specific submittal instructions indicated in Block 14 and 16 if each DD Form 1423-1 in electronic format via Multi-user ECP Automated Review System (MEARS). The Contractor shall ensure versions of the software used for data deliverables remain compatible with current C-5M Program Office software.

Electronically via MEARS (Multi-user ECP Automated Review System)

KASPEREK-SAID, MICHELLE M CIV USAF AFMC 78 ABW/JA

This is an incomplete sentence.

CUI Page 8 of 15 https://mears1.redstone.army.mil/mears/defualts.aspx.

5.2 Alternative Delivery Formats

5.2.1 The Contractor shall inform the C-5M Program Office in writing 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). A request for an alternative delivery format should not be considered an automatic approval for late delivery of the data.

5.3 Editable Format Requirements

5.3.1 When the Contractor is required to make deliveries in Microsoft Excel or in Microsoft Project Tools, the Contractor may 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 and shall be in searchable format and not scanned.

6 Letters of Transmittal

6.1 Required Format (General)

6.1.1 The Contractor shall include a Letter of Transmittal (LT) with all data deliverables. The LT may be in the form of a letter or email form the designated contractor representative. As a minimum, the LT shall contain:

• Letter date and control number

• Contractor’s address and Point of Contact (POC)

• Contract number, delivery order, CLIN and program name

• Document date, letter control number, and revision level

• DID number

• Data title/subtitle

• CDRL sequence number (dash sequence number to represent submission number, e.g. (CDRL A001-101)

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

• Reference to previous/pertinent correspondence relating to the submittal

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

• Note of “Final delivery” for Contractual Fulfillment of CDRL Item.

6.2 Required Format (Paper)

6.2.1 If a paper copy of the data delivery must be prepared, a complete list of addressees shall be placed at the end of the LT, annotating the recipients (as identified on the DD Form 1423, Block 14), including the transmittal-letter-only recipients. Paper copies shall be prepared and submitted on standard 8 ½ x 11-inch document size bond paper. Fold-outs are permissible for large tables/flow-charts.

6.3 Required Format (Email)

6.3.1 If submittal is granted from the Government via e-mail, the list of addressees in the “To” line shall include the complete list of addressees and shall be considered sufficient.

CUI Page 9 of 15

7 Common Abbreviations in DD FORM 1423-1

Block 7:

SS-Source (ACO); Source (ACO) SD - Source (ACO) Destination (PCO) DD-Destination (POC); Destination (PCO) LT-Letter of Transmittal

Block 8:

A-Approval N/A-Not Applicable 16-See Block 16 for further instructions

Blocks 10, 12, & 13:

ANNLY Annually ASGEN As Generated ASREQ As Required BI-WE Bi-Weekly BI-MO Bi-Monthly 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

8 Modification of Data Requirements

8.1 CDRL Changes

CUI Page 10 of 15

8.1.1 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 XX 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 preceding two paragraphs shall be by the issuance of a PCO letter 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.

8.2 Changes to Contract Price (Limits & Conditions)

8.2.1 Any amendment to data deliverables shall be made at no change in contract price, provided the increase for an individual line item of data is not greater than 150 percent (150%) nor a decrease to less than 50 percent (50%) in the total number of copies initially specified in the CDRL. In the event of an increase greater than 150 percent or of a decrease to less than 50 percent, the parties will negotiate any equitable adjustment.

8.2.2 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. Unilateral action shall be by the issuance of a PCO's letter, which will reference this paragraph as its authority. The Contractor shall notify the PCO of the estimated cost if the changes impact the contract price.

8.3 Subsequent Submittals

8.3.1 Action directed by these paragraphs shall be put in place by the Contractor beginning with the first submission of the particular data item or items after receipt by the Contractor of the PCO’s direction.

9 Marking of Controlled Unclassified Information (CUI) and Technical Documentation

9.1 Controlled Unclassified Information:

a. Designation – The originator of a document or material is responsible for determining, at the time of creation, whether the information in a document or material is CUI. If so, the author is responsible for applying CUI markings and dissemination instructions accordingly.

b. The Contractor will NOT use unofficial or personal (e.g. .net; .com) e-mail accounts, messaging systems, or other non-DoD information systems, except approved or authorized government contractor systems, to conduct official business involving CUI and information must be encrypted. This is necessary to ensure proper accountability for Federal records and to facilitate data spill remediation in accordance with Public Law 113-187 and the January 16, 2018 Deputy Secretary of Defense memorandum.

c. The Contractor shall use DoD Safe (Secure Access File Exchange) to encrypt and exchange information when encryption capabilities are not available through email.

d. Controlled Unclassified Information is any information that law, regulation, or government wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

e. The National Archives and Records Administration (NARA) CUI Registry

CUI Page 11 of 15

(http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.

f. The Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information, DoDM 5200.01V1_AFMAN 16-1404V1, Information Security Program: Overview, Classification and Declassification, DoDM 5200.01V2 AFMAN 16-1404V2, Information Security Program: Marking of Classified Information, and DoDM 5200.01V3_DAFMAN 16-1404V3, Information Security Program: Protection of Classified Information, and DoDI 5200.28_DAFI 16-1403, Controlled Unclassified Information (CUI). The Contractor will consult the applicable security classification guide, if required, to monitor CUI aggregation for potentially generating classified information by compilation.

g. The Contractor shall comply with DoDM 5400.07 AFMAN 33‑302, DoD Freedom of Information Act (FOIA) Program, requirements.

h. The Contractor shall ensure that CUI and unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems must be protected using the guidelines set forth in NIST Special Publication 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

i. The Contractor shall comply with DFARS 252.204-7012 Safeguard Covered Defense

Information and Cyber Incident Reporting (May 2024 and subsequent updates). This subpart applies to contracts and subcontracts requiring contractors and subcontractors to safeguard covered defense information that resides in or transits through covered contractor information systems by applying specified network security controls. It also requires reporting of cyber incidents. The subpart does not abrogate any existing contractor physical, personnel, or general administrative security operations governing the protection of unclassified DoD information, nor does it impact requirements of the National Industrial Security Program.

9.2 Distribution Marking System

9.2.1 CUI information may be disseminated within the DoD Components and between DoD Component officials and DoD contractors, consultants, and grantees to conduct official Business for the DoD, provided dissemination is consistent with controls imposed by a distribution statement or limited dissemination controls (LDC).

9.2.2 CUI export controlled technical information or other scientific, technical, and engineering information will still use distribution statements. Export controlled information must also be marked with an export control warning as directed in DoDI 5230.24, DoDD 5230.25, and Part 250 of Title 32, CFR.

9.2.3 A DoD distribution marking system for technical documentation is prescribed in DoD Instruction 5230.24, “Distribution Statements on Technical Information,” 10 January 2023. 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. In addition, 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 and implemented by DoDD 5230.25. The contractor shall mark technical data as instructed by the Government Program Office with the appropriate distribution statement and the export-control warning, as appropriate, on all technical data to denote the extent of its availability for secondary distribution, release and http://www.archives.gov/cui/registry/category-list.html

CUI Page 12 of 15 disclosure without need for additional approvals and authorizations from the controlling DoD office.

These markings are in addition to any security classification or other control markings.

9.2.4 Distribution statements have been annotated in Block 9 of each CDRL and defined in paragraph 8.6 below. If the Contractor feels that a different statement or reason is required, the Contractor shall notify the PCO 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.

9.3 Marking Technical Data

9.3.1 The Contractor shall mark all technical information, regardless of its medium, with the appropriate distribution statement as prescribed by the controlling DoD office. This includes technical reports, blueprints, drawings, technical orders, technical manuals, plans, instructions, computer software, film, technical papers, photographs, etc.

9.3.2 If the document contains export-controlled technical data, the Contractor shall also mark the document with the export control warning statement prescribed in DoDI 5230.24. The Contractor shall also apply distribution statements to technical data that contain proprietary information.

9.3.3 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. 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 paragraphs.

9.3.4 The Contractor is not authorized to provide copies of any data on the CDRL to entities who are not specifically identified in the distribution block of the CDRL without written Government approval from CO.

9.3.5 Contractor Imposed Distribution Statements. DFARS Subpart 227.4 stipulates 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.

9.3.6 When appropriate, the Contractor shall include “CUI” marking at top and bottom of each page. Additionally, Contractor shall apply the appropriate releasability control measure.

9.3.7 When appropriate, the Contractor shall include “SECRET//NOFORN” marking at top and bottom of each page. Additionally, contractor shall apply the appropriate releasability control measure.

9.4 Distribution Statements for Use on Technical Documents

9.4.1 The Contractor shall place one of the following DoDI 5230.24 distribution statements, in accordance with block 9 of the DD Form 1423-1, shall appear on the front, self-cover and/or title page of each document submitted, including the first sheet of each drawing.

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

DISTRIBUTION STATEMENT B: Distribution authorized to U.S. Government agencies only;

(reason); (date of determination). Other requests for this document shall be referred to C-5M Super Galaxy Division, AFLCMC/WLSE, 235 Byron St., Suite 19A, Robins AFB, GA 31098 DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors; (reason); (date of determination). Other requests for this document shall be referred to C-5M Super Galaxy Division, AFLCMC/WLSE, 235 Byron St., Suite 19A, Robins

AFB, GA 31098

CUI Page 13 of 15

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DOD) and U.S. DOD Contractors only; (administrative or operational); (31 Jan 2026). Other requests for this document shall be referred to C-5M Super Galaxy Division, AFLCMC/WLSE, 235 Byron St., Suite 19A, Robins AFB, GA 31098 DISTRIBUTION STATEMENT E: Distribution authorized to DoD Components only; (reason); (date of determination). Other requests for this document shall be referred to C-5M Super Galaxy Division, AFLCMC/WLSE, 235 Byron St., Suite 19A, Robins AFB, GA 31098

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

9.5 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 the Contractor shall mark such documentation as CUI in accordance with DoDI 5200.48, Controlled Unclassified Information (CUI). Distribution statements are not to be used on non-technical documentation; however, limited dissemination controls (LDCs) and LDC markings will apply in most cases. The Contractor shall 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.

http://www.dodcui.mil/Home/DoD-CUI-Registry/

KASPEREK-SAID, MICHELLE M CIV USAF AFMC 78 ABW/JA

Where is this language/guidance from?

Because they both have the same first sentence it is confusing.

Updated to one paragraph

CUI Page 14 of 15

9.6 Controlling DoD Office

9.6.1 The Contractor shall use the following address on all documentation for the “controlling office” of this program:

AFLCMC/WLS

C-5M Super Galaxy Division

235 Byron St., Suite 19A, Robins AFB, GA 31098

9.7 Export-Controlled Warning Statement

9.7.1 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).

9.7.2 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.

9.8 Destruction Notice

9.8.1 All The Contractor shall ensure that all unclassified technical data marked with distribution statements B, C, D, or F shall be handled and destroyed as "DoDI 5200.48 Controlled Unclassified Information (CUI)."

9.8.2 The Contractor shall use the following Destruction Notice for unclassified, controlled-distribution technical information (i.e. marked with Distribution Statement B, C, D, E, or F):

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.

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

9.8.3 The Contractor shall ensure that classified data, including classified controlled technical data, shall be handled and destroyed in accordance with the procedures in DoD Manual 5200.01, Volume 3, “DoD Information Security Program: Protection of Classified Information” or follow the procedures in DoD 5220.22-M, “National Industrial Security Program Operating Manual (NISPOM), Part 117 of Title 32, Code of Federal Regulations.”

9.8.4 The Contractor shall use the following Destruction Notice for classified technical information:

10 Intellectual Property/Markings

10.1 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, including these instructions, the Contractor shall provide a justification for the markings.

DESTRUCTION NOTICE: Follow the procedures in 32 C.F.R. §117.15, National Industrial Security Program Operating Manual (NISPOM) or DoDM 5200.01, Vol 3— Information Security Program: Protection of Classified Information.

Signed HSES CDRL Package_05292025 5/29/2025 12:31:16 PM EDT CDRL Table of Contents

CONTRACT #: FD2060-24-31731

CONTRACTOR: HONEYWELL INTERNATIONAL,

INC.

SET NAME: C-5M HSES SYSTEM ITEM: C-5M

PROGRAM: C-5M Honeywell Software MX

DATA ITEM REQUIRING OFFICE AUTHORITY/TITLE/SUBTITLE SOW PARAGRAPH

A001 AFLCMC/WLSP DI-SAFT-81563 See PWS Para. 5.8.2 Accident/Incident Report

Mishap Notification Reporting

A002 AFLCMC/WLSP DI-SESS-80858D See PWS para. 4.7.13.

Supplier's Configuration Management Plan

Configuration Management Plan (CMP)

A003 AFLCMC/WLSP 000-00-000

Reserved CDRL

A004 AFLCMC/WLSP DI-ADMN-81401C/T See PWS Para 4.11.5 Contract Change Proposal (CCP)

A005 AFLCMC/WLSP DI-ILSS-80872/T See PWS Para 4.7.16.

Training Materials

A006 AFLCMC/WLSP DI-SESS-80639E/T See PWS Para. 4.5.3, 4.11.2, 4.11.5, 4.13.5

Engineering Change Proposal (ECP)

A007 AFLCMC/WLSP DI-SESS-80640D/T See PWS Para. 4.11.5.

Request for Variance (RFV)

A008 AFLCMC/WLSP DI-MGMT-81749B See PWS Para. 1.0.

Distribution of Department of Defense (DoD) Depot

Maintenance Workload (50/50) Report

10 USC 2466 (50/50) Requirements Report

A009 AFLCMC/WLSP DI-MGMT-80441D See PWS para. 3.2.

Government Property Inventory Report

A00A AFLCMC/WLSP DI-ADMN-81250C See PWS Paras 4.3.2, 4.3.4, 4.6.6, 4.7.18

Meeting Minutes

Conference Minutes

A00B AFLCMC/WLSP DI-MGMT-80368A/T See PWS Paras. 3.2, 4.3.2, 4.6.3, 4.6.4, Status Report 4.6.6, 4.7.2.2, 4.7.17.

Monthly Status Report

A00C AFLCMC/WLSP DI-SAFT-82313 See PWS Para. 5.8.1 Environmental, Safety, and Occupational Health (ESOH)

Plan

A00D AFLCMC/WLSP DI-MGMT-81453C See PWS Paras. 4.4.9, 4.6.2, 4.6.6,

4.7.2.2 Data Accession List 4.7.8, 4.10.

A00E AFLCMC/WLSP DI-MGMT-81861C/T See PWS Paras. 4.3.3, 4.4.1, 4.6.6, 4.7.18, Integrated Program Management Data and Analysis Report

(IPMDAR))

5.6.

IMS

A00F AFLCMC/WLSP DI-MGMT-81580 See PWS Para. 5.8.1 Contractor’s Standard Operating Procedures

Company Safety Plan

A00G AFLCMC/WLSP DI-MGMT-81334D See PWS Para. 4.4.2 Contract Work Breakdown Structure (CWBS)

A00H AFLCMC/WLSP DI-ADMN-81249C See PWS Paras. 4.3.2, 4.3.4, 4.4.4, 4.6.6, Conference Agenda 4.7.2.1, 4.7.6, 4.7.18, 5.7.1.

Meeting Agenda

A00J AFLCMC/WLSP DI-ENVR-81375/T See PWS Paras. 4.7.8, 5.2, 5.8.1.1.

Environmental Health and Safety Plan

A00K AFLCMC/WLSP 00-00-000

Reserved CDRL

A00L AFLCMC/WLSP DI-SESS-81000F/T See PWS Paras. 4.5.3, 4.6.2, 4.11.2, Product Engineering Design Data and Associated Lists 4.13.2, 4.13.3.

A00M AFLCMC/WLSP DI-HFAC-80747C/T See PWS Paras. 4.5.3, 4.7.2.2, 4.13.2 Human Engineering Design Approach Document -

Maintainer

A00N AFLCMC/WLSP DI-SESS-81757A/T See PWS Paras. 4.4.4, 4.5.3, 4.6.2, 4.7.3.1

Design Review Information Package (DRIP) 4.7.5, 4.7.18, 4.13.2, 4.13.3.

PDR, CDR, SRR,

A00P AFLCMC/WLSP DI-IPSC-81442A See PWS Paras. 4.6.2.1, 4.6.7, 4.7.3.5, Software Version Description (SVD) 4.13.2, 4.13.3.

See Blk 16

A00Q AFLCMC/WLSP DI-MISC-80711A See Blk 16 Scientific and Technical Reports

See Blk 16

A00R AFLCMC/WLSP DI-SESS-81646B/T See PWS Paras 4.7.3, 4.7.5.

Configuration Audit Plan

A00S AFLCMC/WSLP DI-MGMT-81845/T See PWS Para 4.7.3.1

Information Assurance (IA) Design Review Information

Package (DRIP)

See Blk 16

A00T AFLCMC/WLSP DI-MGMT-81844/T See PWS Paras 4.5.3, 4.7.3.1, 4.7.8, Information Assurance (IA) Test Plan 4.13.2, 4.13.3.

See Blk 16

A00U AFLCMC/WLSP DI-MGMT-81843/T See PWS Paras 4.5.3, 4.7.3.1, 4.7.8, Information Assurance (IA) Test Report 4.13.2, 4.13.3 See Blk 16

A00V AFLCMC/WLSP DI-SDMP-81465A/T See PWS Paras 4.5.3, 4.7.2.2, 4.7.2.3, Performance Specification Documents 4.13.2, 4.13.3.

Air Vehicle Specification

A00W AFLCMC/WLSP DI-IPSC-81431A/T See PWS Paras 4.5.3, 4.7.2.2, 4.7.2.3, System/Subsystem Specification (SSS) 4.13.2, 4.13.3, See Blk 16

A00X AFLCMC/WLSP DI-IPSC-81432A/T See PWS Paras 4.5.3, 4.13.2, 4.13.3.

System/Subsystem Design Description (SSDD)

See Blk 16

A00Y AFLCMC/WLSP DI-IPSC-81435B See PWS Paras 4.5.3, 4.7.3.1, 4.13.2, Software Design Document 4.13.3.

See Blk 16

A00Z AFLCMC/WLSP DI-SDMP-81465A/T See PWS Paras 4.5.3, 4.7.2.2, 4.7.2.3, Performance Specification Documents 4.13.2, 4.13.3.

Weapon System Specification

A010 AFLCMC/WLSP DI-EDRS-81729 See PWS Paras 4.5.3, 4.7.3.1, 4.13.2, VHSIC Hardware Description Language (VHDL)

Documentation 4.13.3.

A011 AFLCMC/WLSP DI-SDMP-81465A/T See PWS Paras 4.5.3, 4.7.2.2, 4.13.2, Performance Specification Documents 4.13.3.

A012 AFLCMC/WLSP DI-MISC-80508B/T See PWS Paras 4.3.2.1, 4.5.3, 4.13.2, Technical Report - Study/Services 4.13.3 See Blk 16

A013 AFLCMC/WLSP DI-SESS-80198B See PWS Paras 4.3.2.1, 4.5.3, 4.13.2, Internal Loads and Static Strength Analysis Report

(ILSSAR)

4.13.3

See Blk 16

A014 AFLCMC/WLSP DI-EMCS-81540B See PWS Paras 4.5.3, 4.13.2, 4.13.3.

Electromagnetic Environmental Effects (E3) Integration and

A015

AFLCMC/WLSP

Analysis Report (E31AR)

DI-IPSC-81441A/T

See PWS Paras 4.5.3, 4.7.3.1, 4.13.2, Software Product Specification (SPS) 4.13.3

A016 AFLCMC/WLSP DI-IPSC-81433A/T See PWS Paras 4.5.3, 4.7.2.2, 4.7.3.1, Software Requirements Specification (SRS) 4.7.8, 4.13.2, 4.13.3.

See Blk 16

A017 AFLCMC/WLSP DI-IPSC-81434A/T See PWS Paras 4.5.3, 4.7.2.2, 4.7.3.1, Interface Requirements Specification (IRS) 4.7.18, 4.13.2, 4.13.3.

See Blk 16

A018 AFLCMC/WLSP DI-SESS-81248B See PWS Paras 4.4.7, 4.5.3, 4.7.2.2, Interface Control Document (ICD) 4.7.3.1, 4.7.18, 4.13.2, 4.13.3.

See Blk 16

A019 AFLCMC/WLSP DI-SAFT-80101C See PWS Paras 4.5.3, 4.7.2.2, 4.7.3.1, System Safety Hazard Analysis Report (SSHAR) 4.7.14, 4.7.14.1, 4.13.2, 4.13.3

A01C AFLCMC/WLSP DI-SESS-81766A See PWS Paras 4.5.3, 4.7.9, 4.13.2, 4.13.3

Airworthiness Specification

See Blk 16

A01D AFLCMC/WLSP DI-HFAC-80746C/T See PWS Paras 4.5.3, 4.7.2.2, 4.13.2, Human Engineering Design Approach Document - Operator 4.13.3

A01E AFLCMC/WLSP DI-AVCS-80700A/T See PWS Paras 4.5.3, 4.6.6, 4.7.3.1, Computer Software Product End Item – Compiled Loadable

Image 4.7.3.5, 4.13.2, 4.13.3.

A01F AFLCMC/WLSP DI-IPSC-81488/T See PWS Paras 4.6.6, 4.7.3.1, 4.7.3.1, Computer Software Product 4.7.3.2, 4.7.3.3, 4.13.2, 4.13.3.

See Blk 16

A01G AFLCMC/WLSP DI-IPSC-81488A/T See PWS Paras 4.4.8, 4.5.3, 4.6.6, Computer Software Product 4.7.3.1, 4.7.3.2, 4.7.3.3, 4.13.2, 4.13.3 Source Code-Test Scripts

A01H AFLCMC/WLSP DI-AVCS-80700A/T See PWS Paras 4.5.3, 4.6.6, 4.7.3.1.

Computer Software Product End Items 4.13.3.

See Blk 16

A01J AFLCMC/WLSP DI-AVCS-80700A/T See PWS Paras 4.5.3, 4.6.6, 4.7.3.1, 4.13.3

Computer Software Product End Items

A01K AFLCMC/WLSP DI-IPSC-81429A/T See PWS Paras 44.5.3, 4.7.3.1, 4.13.2, Software Transition Plan (STRP) 4.13.3.

See Blk 16

A01L AFLCMC/WLSP DI-IPSC-81488/T See PWS Paras 4.4.8, 4.5.3, 4.6.6, Computer Software Product 4.4.8, 4.5.3, 4.6.6.

General Test Scripts

A01M AFLCMC/WLSP DI-QCIC-81890 See PWS Paras 4, 4.13.2, 4.13.3.

Qualification Test Report

See Blk 16

A01N AFLCMC/WLSP DI-NDTI-81307A See PWS Paras 4.5.3, 4.13.2, 4.13.3.

First Article Qualification Test Plan and Procedures

See Blk 16

A01Q AFLCMC/WLSP DI-EMCS-80200C See PWS Paras 4.5.3, 4.13.2, 4.13.3.

Electromagnetic Interference Test Report (EMITR)

See Blk 16

A01R AFLCMC/WLSP DI-NDTI-80809B/T See PWS Paras 4.5.3, 4.5.4, 4.7.3.2, Test/Inspection Report 4.7.3.3, 4.7.3.4, 4.7.3.5, 4.13.2, 4.13.3

A01S AFLCMC/WLSP DI-NDTI-80566A/T See PWS Paras 4.5.3, 4.6.6, 4.7.3.5 Test Plan 4.13.2, 4.13.3.

A01T AFLCMC/WSLP DI-QCIC-81536A/T See PWS Paras 4.4.8, 4.5.3, 4.5.4, 4.7.3.1, Test Information Sheet (TIS) 4.13.2, 4.13.3.

See Blk 16

A01U AFLCMC/WLSP DI-QCIC-81536A See PWS Paras 4.4.8, 4.5.3, 4.5.4.3.1.

Test Information Sheet (TIS) 4.7.3.2, 4.7.3.4, 4.7.3.5, 4.13.3.

Verification Test Information Sheets

A01V AFLCMC/WLSP DI-QCIC-81536A/T See PWS Paras 4.4.8, 4.5.3, 4.5.4, 4.7.3.1

Test Information Sheet (TIS) 7.3.2, 4.7.3.4, 4.7.3.5, 4.13.3.

Integration Test Information Sheets – Development

A01W AFLCMC/WLSP DI-IPSC-81440A See PWS Paras 4.5.3, 4.6.6, 4.7.3.1, Software Test Report (STR) 4.13.2, 4.13.3.

A01X AFLCMC/WLSP DI-IPSC-81438A See PWS Paras 4.5.3, 4.6.6, 4.7.3.1, Software Test Plan 4.13.2, 4.13.3.

A01Y AFLCMC/WLSP DI-IPSC-81439A See PWS Paras 4.5.3, 4.6.6, 4.7.3.1, Software Test Description 4.13.2, 4.13.3.

A020 AFLCMC/WLSP DI-QCIC-81722 See PWS Para. 5.12

Quality Program Plan (QPP)

A021 AFLCMC/WLSP DI-QCIC-80553A See PWS Paras 4.53, 4.6.5, 4.13.3.

Acceptance Test Plan

A022 AFLCMC/WLSP DI-IPSC-81427B See PWS Paras 4.5.3, 4.6.2, 4.7.3.1, Software Development Plan 4.13.2, 4.13.3.

Signed HSES CDRL Package_05292025

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

(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.

See BLK 16

B. EXHIBIT

A/B/C/D/E/F

C. CATEGORY:

TDP TM OTHER SAFT

D. SYSTEM/ITEM

C-5M

E. CONTRACT/PR NO.

FD2060-24-31731

F. CONTRACTOR

HONEYWELL INTERNATIONAL, INC.

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Accident/Incident Report

3. SUBTITLE

Mishap Notification Reporting

4. AUTHORITY (Data Acquisition Document No.)

DI-SAFT-81563

5. CONTRACT REFERENCE

See PWS Para. 5.8.2

6. REQUIRING OFFICE

AFLCMC/WLSP

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

ASREQ

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

N/A

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

Draft

Final

Reg Repro

16. REMARKS

BLOCK 4: The Contractor shall report all mishaps, damage to DoD property, and employee injury to the Installation Safety Office telephonically within four (4) hours after initial notification.

Written report shall be submitted within three (3) calendar days of mishap. Electronic submissions are acceptable. Information that is not available at the time of the initial notification shall be provided within 20 calendar days after the mishap.

BLOCK 7: The contractor shall submit a letter of transmittal through MEARS for all submittals.

BLOCK 9: Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only, for (administrative or operational); (31 Jan 2026). Other requests for this document must be referred to the C-5M Galaxy Division, AFLCMC/WLS, 235 Byron Street, Suite 19A, Robins AFB, GA 31098.

BLOCKS 10, 12, &13: The Contractor shall submit Accident/Incident Report as required by this contract within three (3) calendar days of mishap.

BLOCK 14: Each submission shall be delivered electronically to the Government via MEARS in accordance with the CDRL/PWS. Reports shall be submitted as searchable Indexed Portable Data Format (IPDF) files.

Submission shall also include native formats used in the creation of the Report (e.g., MS Word, MS Project, etc.).

BLOCKS A, B, and 1: The contractor SHALL NOT generate data in support of an option period/task until receipt of a contract modification that exercises the option period/task and obligates additional funding.

CLIN Exhibit Data Item No. Performance Period

0003 A A001 Base Year Pd

1003 B B001 Option Period 1

2003 C C001 Option Period 2

3003 D D001 Option Period 3

4003 E E001 Option Period 4

5003 F F001 Option Period 5

MEARS 0 1 0

15. TOTAL 0 1 0

G. PREPARED BY

IGIEKHUME.PHILLIPA.A.1503314734

AFLCMC/WLSE Configuration Manager

H. DATE

2025/05/29

I. APPROVED BY

PURNELL.GREG.M.1067036537

AFLCMC/WLS Program Manager

J. DATE

2025/05/29

18. ESTIMATED

TOTAL PRICE

17. PRICE GROUP

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.

See BLK 16

B. EXHIBIT

A/B/C/D/E/F

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

C-5M

E. CONTRACT/PR NO.

FD2060-24-31731

F. CONTRACTOR

HONEYWELL INTERNATIONAL, INC.

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Supplier's Configuration Management Plan

3. SUBTITLE

Configuration Management Plan (CMP)

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80858D

5. CONTRACT REFERENCE

See PWS para. 4.7.13.

6. REQUIRING OFFICE

AFLCMC/WLSP

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

N/A

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

(administrative or operational); (31 Jan 2026). Other requests for

BLOCK 10-13: The first submittal shall be delivered for Government review NLT 15 calendar days after the completion of the first full calendar month of this effort or IAW a Government approved schedule.

The Government will provide comments NLT 15 calendar days after receipt. In instances where comments are provided, the Contractor shall provide an updated submittal NLT 15 calendar days after transmission of PCO/ACO response letter or IAW a Government approved schedule. In the event of no Government response the Contractor shall notify the PCO/ACO for approval. Delivery information shall be reflected on the Government approved baseline Integrated Master Schedule (IMS).

be submitted as searchable Indexed Portable Data Format (IPDF) files.

0003 A A002 Base Year Pd

1003 B B002 Option Period 1

2003 C C002 Option Period 2

3003 D D002 Option Period 3

4003 E E002 Option Period 4

5003 F F002 Option Period 5

MEARS 1 1

15. TOTAL 1 1 0

IGIEKHUME.PHILLIPA.A.1503314734

AFLCMC/WLSE Configuration Manager

H. DATE

2025/05/29

I. APPROVED BY

PURNELL.GREG.M.1067036537

AFLCMC/WLS Program Manager

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).