AT-6 THAILAND BPC Gen Instr and CDRLs.pdf

CUI

CUI

CONTRACT DATA

REQUIREMENTS LIST (CDRL)

GENERAL INSTRUCTIONS

for

AT-6 Thailand Building Partner Capacity Program FY23

Contract #

07/25/2023 To Include:

CDRL INSTRUCTIONS

ADDRESS LIST

CDRL TABLE OF CONTENTS

DD FORMS 1423-1

PREPARED BY

AIR FORCE LIFE CYCLE MANAGEMENT CENTER (AFLCMC/WID)

2690 West Loop Road, Area B, Building 556 Wright-Patterson Air Force Base, OH 45433-7211

Distribution Statement D: Distribution authorized to U.S. Government agencies and their contractors only; critical technology, administrative or operational use, export controlled information: 12/09/2022.

Other requests shall be referred to AFLCMC/WID Wright-Patterson AFB OH 45433.

Reproduction, disclosure, or dissemination of this document in whole or part, is prohibited except with permission of ISR/SOF Directorate, Attack Systems Division.

WARNING: This document contains technical data whose export is restricted by the Arm Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C. App. 2401 et seq.), as amended. Violations of these export laws are subject to sever criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

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

Controlled by: AFLCMC/WI Controlled by: AFLCMC/WID CUI Categories: CTI, EXPORT, Operations Security Information Distribution C

Table of Contents

1.0 Scope

2.0 General

3.0 Data Deliverables

3.1 Delivery Dates

3.2 Data Submittal Approvals

3.3 Resubmittals of Data

3.4 Final Submittal of Deliveries

3.5 DD Form 250, Material Inspection and Receiving Report

3.6 Classified Data

3.7 Modification of Data Requirements

4.0 Electronic Data Transmission

5.0 Document Revisions

6.0 Letters of Transmittal

7.0 Common Abbreviations in DD Form 1423-1

8.0 Marking Technical and Non-Technical Documentation

8.1 Distribution Marking System

8.2 Marking Technical Data

8.3 Distribution Statements for Use on Technical Documents

8.4 Controlling DoD Office

8.5 Export-Controlled Warning Statement

8.6 Destruction Notice

8.7 Intellectual Property Marking

9.0 Reference Documents

10.0 Correspondence for Data/Letter of Transmittals

CDRL INSTRUCTIONS

1.0 Scope.

This Contract Data Requirements List (CDRL - DD Form 1423-1) establishes the data to be delivered by the contractor and the submittal, approval and distribution requirements of all the CDRL data items contained herein.

2.0 General.

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.0 Data Deliverables.

3.1 Delivery Dates

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

a. If the CDRL delivery date falls on a Saturday, the submittal must be delivered on the business day immediately preceeding the Saturday of delivery date.

b. If the CDRL delivery date falls on a Sunday, the submittal must be delivered on the business day immediately following the Sunday delivery date.

c. If the CDRL delivery falls on a holiday, the submittal must be delivered on the business day immediately preceeding the holiday.

d. Early CDRL delivery is permitted. The Contractor must notify the Government of late CDRL deliveries.

3.2 Data Submittal Approvals.

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

a. The use of an "A" in Block 8 indicates the Government will formally reply to each data submittal with either an approval, approval with comments or disapproval to ensure that the contractor is in compliance with the DID and CDRL requirements. The Government will issue a response via a Procuring Contracting Officer Letter (PCOL)or email to the contractor within forty-five (45) calendar days, unless otherwise specified on the DD Form 1423-1, Block 16.

Government non-response beyond forty-five calendar days does not constitute approval. If approvals are required, a CDRL submittal is not officially approved until a PCOL is formally submitted to the contractor. The forty-five (45) calendar day response does not apply to Engineering Change Proposals (ECPs) and Contract Change Proposals (CCPs). Note: ECPs will utilize the DD Form 1692 (long form).

b. If Block 8 contains an “N” or an “N/A”, 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 DD Form 1423-1, are mandatory. All data submissions are subject to review and approval by the Government. The Government has the right to disapprove any data submittal(s) through the Contracting Officer via a PCOL that are not in compliance with the DID as well as the contract requirements.

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

d. Draft submittals are not approval items. The contractor shall formally submit draft data item(s) (when required by the 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.

3.3 Resubmittals of Data

a. 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 thirty (30) calendar days, the Government shall be notified within thirty (30) calendar days and a new suspense date will be mutually agreed upon.

b. Data submittals that are approved with Government comments shall be incorporated in the next subsequent submittal unless specified otherwise in the PCOL. If no subsequent submittal is scheduled e.g. monthly or quarterly, then the data item shall be resubmitted within thirty (30) calendar days.

3.4 Final Submittal of Deliveries.

For the final delivery of each data item in the contract/delivery order, the contractor shall clearly state final delivery in the Letter of Transmittal (LT) as defined in paragraph 6.0. and that all contractual requirements concerning the data item have been fulfilled.

3.5 DD Form 250, Material Inspection and Receiving Report.

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.

3.6. Classified Data.

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

3.7 Modification of Data Requirements.

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

b. From time to time during the performance of the contract, the PCO may unilaterally increase or decrease the specified number of addresses or the number of hard copy deliverables (regular or reproducible) for any data item of the DD 1423-1 with no change in price.

c. Unilateral actions pursuant to the above (a) and (b) 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 produced by the contractor beginning with the first submission of the particular data item or items after receipt by the contractor and PCO’s direction.

4.0 Electronic Data Transmission.

a. The contractor shall submit all data deliverables electronically via MEARS (Multi-User ECP Automated Review System). The versions for the software used for electronic data transmission shall remain compatible with current program office software. Where applicable, all electronic data shall be delivered using the Microsoft Office product suite and/or Microsoft Project Tools. 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 shall be in searchable format, not scanned and will be documented as the formal data delivery. Financial information provided in excel spreadsheets should be able to be manipulated.

Any submittals by other means shall require program office approval prior to delivery of data.

1. Electronically via MEARS (Multi-user ECP Automated Review System) https://mears1.redstone.army.mil/mears/defaults.aspx.

2. Contact the program office Configuration Data Manager for assistance in licensing and setup.

https://mears1.redstone.army.mil/mears/defaults.aspx

Electronic delivery includes delivery and availability of data files via the MEARS system.

b. The contractor shall inform the program office if any of data deliverables cannot comply with the required electronic formats and shall propose alternate formats. In such cases, the Government shall approve any format(s) apart from the required electronic format.

c. MEARS is the only authorized method of delivery. If a delivery cannot be made into MEARS due to technical issues the Government CM respresentative must be notified immediately. If the Government CM representative cannot resolve the technical issue, the contractor will be notified of an alternate method of delivery. Unless otherwise specified, all final reports and documents that are in paper shall be prepared on standard 8 ½ x 11-inch document size: 3-hole punched, bound bond paper and shall be sufficiently legible to be suitable for reproduction of a direct copying machine.

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

e. MEARS is for unclassified data. The user is to ensure that all data or documentation marked classified in NOT uploaded into MEARS. All unclassified documents are to be properly marked.

5.0 Document Revisions.

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

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

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

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

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

6.0 Letters of Transmittal.

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

1. Contractor POC

2. Contractor address

3. Date

4. Contract number, program name and delivery order (if applicable)

5. Letter control number

6. Document number, revision level and/or date

7. DID Number and Revision

8. Data title/subtitle

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

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

11. List of distribution addresses as identified in Block 14 of the CDRL

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

13. Approval/Non Approval of CDRL

b. 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 Form 1423, Block 14) including the transmittal-letter-only recipients.

c. If approval 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.

7.0 Common Abbreviations in DD Form 1423-1.

Block 7:

SS - Source (ACO) Source (ACO)

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

Block 8:

A - Approval N/A - Not applicable (approval not required) 16 - See Block 16 for further instructions

Blocks 10, 12, and 13

ANNLY - Annually ASGEN - As Generated ASREQ - As Required BI-MO - Bi-Monthly BI-WE - Bi-Weekly BLK 16 - See Block 16 DAILY - Daily DFDEL - Deferred Delivery EOC - End of Contract EOM - End of Month EOQ - End of Quarter MTHLY - Monthly

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

8.0 Marking Technical and Non-Technical Documentation. Marking of documentation falls into 2 broad categories: Technical and Non-Technical documentation. For the purposes of this document, these 2 categories require specific marking when the documentation falls within the purview of “Controlled Unclassified Information (CUI)” as prescribed in DoDI 5200.48, “Controlled Unclassified Information”. These markings are in addition to any security classification or other control markings required per the contract.

8.1 Distribution Marking System. A DoD distribution marking system for technical documentation is prescribed in DoD Instruction 5230.24, “Distribution Statements on Technical Documents”. 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 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.

Distribution statements have been annotated in Block 9 of each CDRL and defined in paragraph 8.3 below. If the contractor feels that a different statement or reason is required, the contractor shall 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 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. If the document contains export-controlled technical data, it shall also be marked with the export control warning statement prescribed in DODI 5230.24. Distribution statements are also applied to technical data that contain proprietary information used.

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.

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.

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.

The term Controlled Unclassified Information (CUI) is now to be used and replaces the term For Official use Only (FOUO) for any new documents dated after 6 March 2020 when DoDI 5200.48 was published; legacy documents do not have to be re-marked, but CUI should be applied if/when content is being revised/modified. At minimum CUI markings for unclassified DoD documents will include the acronym “CUI” in the banner and the footer of the document, or it may say the following:

“UNCLASSIFIED//CONTROLLED INFORMATION” marking at top and bottom of each page.

Additionally, contractor shall apply the appropriate releasability control measure.

CUI markings in classified documents will appear in paragraphs or subparagraphs known to contain only CUI and must be portion marked with “(CUI).” “CUI” will not appear in the banner or footer. (1) There will be an acknowledgement added to the warning box on the first page of multi-page documents to alert readers to the presence of CUI in a classified DoD document, as shown in Figure 1.

Figure 1. CUI Warning Box for Classified Material

This content is classified at the [insert highest classification level of the source data] level and may contain elements of controlled unclassified information (CUI), unclassified, or information classified at a lower level than the overall classification displayed. This content shall not be used as a source of derivative classification;

refer instead to [cite specific reference, where possible, or state “the applicable classification guide(s)”]. It must be reviewed for both Classified National Security Information (CNSI) and CUI in accordance with DoDI 5230.09 prior to public release. [Add a point of contact when needed.]

The first page or cover of any document or material containing CUI, including a document with commingled classified information, will include a CUI designation indicator, as shown in Figure 2.

Documents and materials containing CUI will require a generic “CUI” marking at the top and bottom of each page.

Figure 2. CUI Designation Indicator for All Documents and Material Controlled by: [Name of DoD Component] (Only if not on letterhead) Controlled by: [Name of Office] CUI Category: (List category or categories of CUI) Distribution/Dissemination Control:

POC: [Org phone or Org email address]

8.3 Distribution Statements for Use on Technical Documents.

AFI 61-201, paragraph 2.3.4.1. “Distribution statements are displayed conspicuously on all technical documents regardless of media or format. For standard written or printed material the Distribution Statement is shown on all pages to the maximum extent practical and at a minimum on the front cover, title page, and SF 298, where applicable. If the technical information is digitally prepared or in any other medium that does not have a cover or title page, the applicable Distribution Statement is affixed to all physical and digital items by other means in a conspicuous position for ready recognition

One of the following distribution statements, IAW Block 9 of the DD Form 1423-1, shall appear on the front, self-cover and/or title page of each technical 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:

(fill in reason); (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

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

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD contractors only; (reason- Foreign Government Information); (date of determination-DATE of CONTRACT/DELIVERY/TASK ORDER AWARD). Other requests shall be referred to (insert controlling DoD office).

8.4 Controlling DoD Office

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

AFLCMC/WID

AT-6 Thailand BPC 2690 West Loop Road, Area B, Building 556

Wright-Patterson Air Force Base, OH 45433-7211

8.5 Export-Controlled Warning Statement

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

Export Controlled technical documents, printed, electronic, and digital, that contain export-controlled technical data shall be marked with the Export Control Warning provided in the box below. When it is infeasible to use the entire statement, the abbreviated warning may be used, and a copy of the full warning added to the “Notice to Accompany the Dissemination of Export-Controlled Technical Data,” which is Enclosure E5 of DoDD 5230.25. For assistance in determining what is export controlled, you may consult the local Government agency’s Foreign Disclosure Office.

In addition to a distribution statement, the marking system also requires the use of a warning notice on all documents that contain export-controlled technical data in accordance with DODD 5230.25. The notice may be used in conjunction with the five controlled distribution statements (B, C, D, E, and F).

Statement A, which denotes public release, cannot be used in conjunction with the export-control warning notice.

DISTRIBUTION STATEMENT E: Distribution authorized to DoD components only; (reason- Proprietary Information); (date of determination-DATE of CONTRACT/DELIVERY/TASK ORDER AWARD). Other requests shall be referred to (insert controlling DoD office) and Contractor will be notified and approval requested.

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

8.6

Destruction Notice All unclassified technical data marked with distribution statements B, C, D, E or F shall be handled and destroyed as “Controlled Unclassified Information (CUI) documents, in accordance with DoDI

5200.48 Controlled Unclassified Information (CUI)

Destruction Notice for CUI distribution technical information (i.e., marked with Distribution Statement B, C, D, E, or F):

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

Classified data, including classified controlled technical data, shall be handled and destroyed in accordance with the procedures in 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), Section 5-705.”

Destruction Notice for classified technical information:

DESTRUCTION NOTICE: Follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), Section 5-705, or DoD 5200.01M, Information Security Program, Vol 3, Protection of Classified Information.

8.7 Intellectual Property/Marking

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

9. Reference Documents

DoDD 5230.9 Clearance of DoD Information for Public Release DoDD 5230.25 Withholding of Unclassified Technical Data from Public Disclosure DoDI 5230.24 Distribution statements on Technical Documents DoD 5400.7-R DoD Freedom of Information Act Program DoD 5010.12-M Procedures for the Acquisition and Management of Technical Data DoDI 5200.48 Controlled Unclassified Information DoD 5220.22-M National Industrial Security Program Operating Manual AFI 61-201 Management of Scientific and Technical Information

"WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C. App. 2401, et seq.), as amended.

Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with the provisions of DoDD 5230.25.

10.0 Correspondence for Data/Letter of Transmittals

Data shall be submitted via MEARs, however, correspondence regarding data and/or letter of transmittal and any classified data shall be addressed to:

Office Symbol Mailing Address E-mail Address

AFLCMC/WID AFLCMC/WID

2690 West Loop Road Area B, Bldg 556

WPAFB, OH 45433-7211

(Program Mgr.) Maureen Robinson maureen.robinson.3@us.af.mil (Deputy PM) Kathyrn Hovis Kathyrn.hovis@us.af.mil

(Logistics Mgr.) David Lewis david.lewis.58@us.af.mil (Logistics) Natalie Engman natalie.engman.1@us.af.mil

(Engineering) Ryan Brenner ryan.brenner.3@us.af.mil

(Config. Data Mgr.) Ruby Hughes ruby.hughes.1@us.af.mil

(PCO) Nicholas Costides nicholas.costides@us.af.mil (Contracting) Richard Goode Richard.goode.6@us.af.mil

(Finance) Jennifer Woodruff jennifer.woodruff@us.af.mil

8/7/2023 9:08:40 AM CDT CDRL Table of Contents

CONTRACT #:

CONTRACTOR:

SET NAME: Thailand FY23 BPC SYSTEM ITEM: Thailand FY23 Building Partner Capacity (BPC) Program

PROGRAM: LAA - USAF

DATA ITEM REQUIRING OFFICE AUTHORITY/TITLE/SUBTITLE SOW PARAGRAPH

A001 AFLCMC/WAB (PM) DI-MGMT-81861A SOW PARA 3.1.9, 3.5.3, 5.0

INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

INTEGRATED MASTER SCHEDULE (IMS)

A002 AFLCMC/WAB (PM)

(LG)

DI-MGMT-80368A SOW 3.1.10, 3.5.3. 5.0

STATUS REPORT

MONTHLY STATUS REPORT

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 OTHER

D. SYSTEM/ITEM

Thailand FY23 Building Partner Capacity (BPC) Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

3. SUBTITLE

INTEGRATED MASTER SCHEDULE (IMS)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81861A

5. CONTRACT REFERENCE

SOW PARA 3.1.9, 3.5.3, 5.0

6. REQUIRING OFFICE

AFLCMC/WAB (PM)

7. DD 250 REQ

NA

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

OTIME

12. DATE OF FIRST SUBMISSION

30DACA

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

N/A Draft

Final

Reg Repro

16. REMARKS

BLK 10: Submit One Time.

BLK 12: 30 Days After Contract award.

BLK 4: DID-DI-MGMT-81861A is tailored as follows:

1. 2.0 Common IPMR Requirements:

Para 2.2.5 Native Schedule Format: Format 6 shall be submitted in Contractor Format utilizing Microsoft Office Suite (Project, Excel, Word)

2. The following paragraphs are deleted:

a. 3.2 Format 1

b. 3.3 Format 2

c. 3.4 Format 3

d. 3.5 Format 4

e. 3.6 Format 5

f. 3.8 Format 7

3. 3.7 Format 6

Para 3.7.1.1 IMS Content Required: The IMS shall include, at a minimum, task/activities as outlined in Section 3.1.9 of the SOW.

The following 3.7 Format 6 paragraphs are omitted:

3.7.1.1.1 Production Contract IMS

3.7.1.1.2 Subcontractor Flowdown

3.7.1.2 IMS Status

3.7.1.3.6.1 through .4: Most Likely Durations; Best/Worst Durations;

SRA Results; SRA Reporting Frequency

3.7.1.3.4.1 through .3: IBR; OTB/OTS; Single Point Adjustment

3.7.1.3.6.5 Milestone Target

3.7.1.6.6.4 and all sub paragraphs

ACO

AFLCMC/WID (LG)

PCO

AFLCMC/WID (PM)

15. TOTAL 0 0 0

G. PREPARED BY

Ruby Hughes

H. DATE

2023/08/07

I. APPROVED BY

Maureen Robinson

J. DATE

2023/08/07

18. ESTIMATED

TOTAL PRICE

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

17. PRICE GROUP

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 OTHER

D. SYSTEM/ITEM

Thailand FY23 Building Partner Capacity (BPC) Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

STATUS REPORT

3. SUBTITLE

MONTHLY STATUS REPORT

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80368A

5. CONTRACT REFERENCE

SOW 3.1.10, 3.5.3. 5.0

6. REQUIRING OFFICE

AFLCMC/WAB (PM) (LG)

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

BLK6

12. DATE OF FIRST SUBMISSION

30DACA

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

Contract Award

13. DATE OF SUBSEQUENT

SUBMISSION

EOM

Draft

Final

Reg Repro

16. REMARKS

BLK 10, 12, 13: Initial report will be submitted 30 Days After Contract award. Subsequent Submittals will be based on End of Month status, and will be received NLT the 15th of the following month.

This report is required until all contract line items have been adequately verified as delivered.

The following DI-MGMT-80368A sections ONLY apply:

3.2.1, para a, b, c, f, g, h and i 3.2.2; 3.2.4; 3.2.5 and 3.3

Per DI-MGMT-80368A, Section 3.2.1 Milestone/task status shall contain the following, where applicable: The status of each milestone/task as defined by the Statement of Work or contract as applicable.

Per DI-MGMT-80368A, Section 3.2.1 as identified above, this report will include data as outlined specifically in Section 3.1, paragraph

3.1.10 of the Statement of Work.

PCO

ACO

AFLCMC/WID (FM)

AFLCMC/WID (LG)

AFLCMC/WID (PM)

15. TOTAL 0 0 0

G. PREPARED BY

Ruby Hughes

H. DATE

2023/08/07

I. APPROVED BY

Maureen Robinson

J. DATE

2023/08/07

18. ESTIMATED

TOTAL PRICE

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

17. PRICE GROUP

AT-6 THAILAND BPC FY23 CDRLs 08_07_23