FA811726R0006_Attachment_1_Exhibit_A.pdf

Exhibit A

FA811726R0006

F-15C/D Control Indicator Repair

PWS Appendix 1

Contract Data Requirements List (CDRL)

CDRL DID Description Frequency A001 DI-PSSS-81534B Teardown Deficiency Report See PWS

A002 DI-MGMT-81803A Item Unique Identification (IUID) Marking Plan

30 days after contract award

A003 DI-MGMT-80969 Production Surge Plan See PWS A004 DI-SESS-80639E Engineering Change Proposal (ECP) As Required A005 DI-MGMT-82256A/T Supply Chain Risk Management (SCRM) Plan See PWS A006 DI-MGMT-80368A/T Status Report See PWS A007 DI-MGMT-80441D/T Government Property (GP) Inventory Report See PWS

A008 DI-MGMT-81838 Commercial Asset Visibility Air Force (CAV/AF) Reporting See PWS

A009 DI-MGMT-81634C (CAV/AF) Government Furnished Material Report See PWS

A010 DI-MISC-81832 Counterfeit Prevention Plan See PWS

A011 DI-PSSS-81995A/T Contract Depot Maintenance (CDM) Monthly Production Report Monthly

CONTRACT DATA REQUIREMENTS LIST Form Approved

(1 Data Item) OMB No. 0704-0188

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 thus burden estimate or any other aspect of this collection o f information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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:

0009/1009/2009/3009/4009 A/B/C/D/E TDP TM OTHER:

PSSS

D. SYSTEM ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Multiple Systems FD2060-26-00154 BAE Systems

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A/B/C/D/E

Acquisition and Sustainment Data Package (ASDP) Teardown Deficiency Report

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-PSSS-81534B PWS para 4.3.3 See Block 16

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT See BLK 16 See BLK 16 b. COPIES

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE DRAFT FINAL

N/A See BLK 16 See BLK 16 Reg Repr o

16. REMARKS See Block 16 0 1 0 CLIN Exhibit Data Item No Period of Performance 0009 A A001 Base Year Period 1009 B B001 Ordering Period 1 2009 C C001 Ordering Period 2 3009 D D001 Ordering Period 3 4009 E E001 Ordering Period 4

Block 4: Contractor format is acceptable.

Block 6: Requiring Activity to be cited on each individual order.

Block 9: Distribution authorized to the Department of Defense and U.S. DoD contractors only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting capabilities vital to National Security that are otherwise not publicly available (Vulnerability of Information) (27 September 2023). Other requests for this document shall be referred to the Procuring Contracting Officer (PCO)/Ordering Procuring Contracting Officer (OPCO).

Blocks 10-13: Frequency and submission dates to be cited by the requiring activity on each individual order.

Block 14: Distribution to be cited by the requiring activity on each individual order. Report deliveries shall be submitted electronically via email to the applicable Government personnel identified by the requiring activity on each individual order.

Note: The contractor shall notify the Government Procurement Contracting Officer (PCO) if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date via electronic mail. This report does not serve as official notification to the requiring activity and/or PCO. 15. Total 0 1 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

DD FORM 1423-1, Feb 2001 Previous editions are obsolete Page of Pages

18 Nov 2025 18 Nov 2025

DATA ITEM DESCRIPTION

Title: Acquisition and Sustainment Data Package (ASDP) Teardown Deficiency Report

Number: DI-PSSS-81534B Approved Date: 20220809 AMSC Number: F10348 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/EZSC) Project Number: PSSS-2022-004 Applicable Forms: N/A

Use/Relationship: The Acquisition and Sustainment Data Package (ASDP) Teardown Deficiency Report provides a factual narrative analysis of a deficiency which has been noted on equipment.

a. This Data Item Description (DID) is applicable when contractors are responsible for maintaining custodial records for government property being repaired, or, when detailed analysis is required for components undergoing a teardown investigation.

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

c. This DID supersedes DI-PSSS-81534A.

Requirements:

1. Reference documents. None.

2. Format. The ASDP Teardown Deficiency Report shall be in a text searchable format. If a model (e.g., Cameo, CAD, etc.) is used for the analysis or resolution of problems, the model shall be embedded in its native format. The Data Objects/Attributes and Associated Metadata (DOAM) listing shall be in Microsoft Excel spreadsheet format in accordance with the template provided in the DOAM Specification attached to the contract. All data shall be in the English language.

3. Content. The Teardown Deficiency Report shall include an analysis of the deficiency which includes cause of failure, recommended corrective action and recommendations for actions to prevent recurrence of the failure/deficiency, and the applicable category of the failure defined as follows:

a. Workmanship and non-conformance. Any deficiency (e.g., physical, chemical, electrical, functional) noted in materiel which is attributed to non-conformance to applicable specifications, drawing, standards, or Technical Order (TO); or workmanship during manufacture, repair modification or maintenance.

b. Material failure. The failure of an end item which was attributable to neither the repair nor the manufacturing process, but was due to an unpredictable failure of an internal component or sub-assembly.

c. No defect found/could not duplicate: Investigation of the exhibit revealed no deficiency.

Equipment conforms to specifications and TO standards and procedures.

d. Technical data, deficiency: Technical data (including TOs, drawings, and work specifications) was deficient or inadequate so as to cause the deficiency/failure on the item.

DI-PSSS-81534B

e. Field induced deficiency. Deficiency confirmed by the investigation to have been caused by operator error, i.e., wrong voltage applied, misaligned, maladjusted, mishandling, or not used for intended purpose.

f. Maintenance deficiency. An unfavorable characteristic of an item that impedes the accomplishment of maintenance operations which results in excessive maintenance operations and/or in excessive maintenance man-hour consumption.

g. Design deficiency. A condition that limits or prevents the use of material for purpose intended or required where the material meets all other specifications.

h. Handling or shipping deficiency. A deficiency induced by improper handling or shipping, i.e., improper packaging, which prohibits the use for intended purpose.

i. Packaging specifications inadequate - not complied with. Unsatisfactory conditions including item damage resulting from improper packaging.

3.1 DOAM. The completed Teardown Deficiency Report template, provided in the DOAM Specification attached to the contract, shall comply with the format requirements (see 2. above) so that it can be ingestible into a Product Lifecycle Management (PLM) solution to ensure proper tying, tracing, and linking to the lowest component of the end item to which the delivered Teardown Deficiency Report Information is applicable. Any field that is not applicable shall be

End of DI-PSSS-81534B.

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 thus burden estimate or any other aspect of this collection o f information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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:

0009/1009/2009/3009/4009 A/B/C/D/E TDP TM OTHER:

MGMT

D. SYSTEM ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Multiple Systems FD2060-26-00154 BAE Systems

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A/B/C/D/E

Item Unique Identification (IUID) Marking Plan

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MGMT-81803A PWS para 4.3.4.1 See Block 16

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT See BLK 16 See BLK 16 b. COPIES Final

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE DRAFT FINAL

A See BLK 16 See BLK 16 Reg Repr o

16. REMARKS See Block 16 0 1 0 CLIN Exhibit Data Item No Period of Performance 0009 A A002 Base Year Period 1009 B B002 Ordering Period 1 2009 C C002 Ordering Period 2 3009 D D002 Ordering Period 3 4009 E E002 Ordering Period 4

Block 6: Requiring activity to be cited on each individual order.

Block 8: The Government shall provide approval, comments, corrections 30 calendar days after receipt of document. The contractor then has 30 calendar days to correct and resubmit.

Block 9: Distribution authorized to the Department of Defense and U.S. DoD contractors only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting capabilities vital to National Security that are otherwise not publicly available (Vulnerability of Information) (27 September 2023). Other requests for this document shall be referred to the Procuring Contracting Officer (PCO)/Ordering Procuring Contracting Officer (OPCO).

Blocks 10-12: The Contractor shall provide the IUID Marking Plan to the PM/LM and the EN electronically via e-mail, 30 calendar days after contract award.

Block 13: If, during performance of this contract, changes to the IUID Marking Plan are required, re-submit the revised IUID Marking Plan. Procedures identified for blocks 8, 10- 12 will apply.

Note: The contractor shall notify the Government Procurement Contracting Officer (PCO) if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date via electronic mail. This report does not serve as official notification to the requiring activity and/or PCO.

15. Total 0 1 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Title: ITEM UNIQUE IDENTIFICATION (IUID) MARKING PLAN

Number: DI-MGMT-81803A Approval Date: 20200311 AMSC Number: F10164 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 16 (AFMC/A4NL) Project Number: MGMT-2019-028 Applicable Forms: N/A

Use/Relationship: The Item Unique Identification (IUID) Marking Plan details the Contractor’s strategy to execute marking requirements identified in the Government contract document(s) and Defense Federal Acquisition Regulation Supplement (DFARS).

The purpose of the IUID Marking Plan is for the Contractor to identify and define, in detail, their IUID marking process and procedures to meet Government contract requirements in accordance with Military Standard (MIL- STD) -130, Identification Marking of U.S. Military Property, for item marking; MIL-STD-129, Military Marking for Shipment and Storage, for packaging marking; and the DoD Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property. (Copies of MIL-STD-130 and MIL-STD-129 are available online at: https://quicksearch.dla.mil/qsSearch.aspx, and a copy of the Department of Defense (DoD) Guide is available online at https://dodprocurementtoolbox.com/site-pages/overview-implementation.)

The IUID Marking Plan shall include item and packaging marking requirements and methodology, encoding correct data, data management, facilities use, marking equipment, data carrier symbols, registration, quality assurance, validation, verification, registration of items being marked, and a master schedule to help the Contractor manage marking activities in a cost effective and timely manner.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract document(s).

b. This DID is used on any contract that requires delivery of an IUID Marking Plan to the Government.

c. This DID supersedes DI-MGMT-81803.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, or revisions, shall be as specified in the contract.

2. Format. The IUID Marking Plan shall be in contractor-developed, Government-approved format. Spreadsheet format shall be used when marking multiple items with IUID.

3. Content. The IUID Marking Plan shall include the following, except when the data matrix mark containing IUID data is embedded in a data label or plate and is already documented in an approved drawing. In such cases, the requirements indicated with an asterisk (*) shall be omitted when describing the label or plate marking:

3.1 List the applicable reference document(s).

3.2 List the end items and components marked with IUID under the requirements of the contract document(s), including DFARS 252.211-7003. (Copies of DFARS clause 252.211-7003 can be obtained online at:

https://www.acquisition.gov/content/regulations.)

DI-MGMT-81803A

3.3 Describe the marking methodology, which shall include the following:

3.3.1* Marking method used for each item to be marked (e.g., by direct marking on the item’s surface, or by indirect marking on a plate or label attached to the item). The marking method may differ for each item.

3.3.1.1* When direct part marking is used, describe the methods used to apply the direct part mark.

3.3.2 Item Marking Specifications:

3.3.2.1 When engineering drawings incorporating the IUID marking requirement exist, list and associate each drawing with the items requiring IUID marking. If not, enter “N/A.”

3.3.2.2 Describe the following aspects of Machine Readable Mark generation:

3.3.2.2.1 IUID construct to be encoded in the data matrix. (e.g., Construct 1, Construct 2, or a specific, DoD-recognized IUID equivalent, which can be found at:

http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html)

3.3.2.2.1.1 When using Construct 1, state whether the item’s Original Equipment Manufacturer (OEM) serial number is part of the Unique Item Identifier (UII), and, if not, how the serial number component of the UII is established.

3.3.2.2.2 Type of Enterprise Identifier (EID) in the mark. (e.g., Commercial and Government Entity (CAGE) code, Data Universal Numbering System (DUNS), DoD Activity Address Code (DoDAAC), or Global Standards One (GS1)).

3.3.2.2.3 The data elements to be encoded in the data matrix symbol, other than those from which the UII is derived, if any.

3.3.2.3* Describe the characteristics of the label or data plate:

3.3.2.3.1* Type of material used for the label or plate. (e.g., aluminum, polyacrylic, metal foil, polyester, polyvinyl, aluminum foil, stainless steel, etc.)

3.3.2.3.2* Method used to mark the data on the label or plate for each item to be marked. (e.g., laser etching, thermal transfer on polyester label stock, photo anodized aluminum plate, etc.)

3.3.2.3.3* Size of the label or plate, including units. (e.g., length, width, thickness, etc.)

3.3.2.3.4* Shape of the label or plate. (e.g., circle, square, rectangle, rounded corners, etc.)

3.3.2.3.5 Illustrate the label or plate to show the Human Readable Information (HRI) and the location of the data matrix.

3.3.2.3.6* Location of the label or plate on the item, include an illustration or photo, if possible.

3.3.2.3.7* Human readable lettering. (e.g., serif, font, font size, color, etc.)

3.3.2.3.8* Attachment method. (e.g., adhesive, screws, rivets, etc.)

3.3.2.3.9* Type of adhesive used, if applicable.

3.3.3 The process for marking legacy parts and Government Furnished Property (GFP).

3.3.4 How Unit Packs, Intermediate Containers, and Exterior Containers shall be marked in compliance with the DFARS 252.211-7003; MIL-STD-129; International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 15434, Information Technology – Automatic Identification and data capture techniques – Syntax for high-capacity ADS media; and American National Standards Institute (ANSI) MH10.8.2, Data Identifier and Application Identifier Standard. (Copies of ISO/IEC 15434 can be obtained at:

https://www.iso.org. Copies of ANSI MH10.8.2 can be obtained at: https://webstore.ansi.org.):

3.3.4.1 Portable Data File (PDF) 417 two (2) dimensional (2D) stacked linear barcode symbol format.

3.3.4.1.1 For data elements encoded in a PDF417 on a unit pack’s packaging, the actual item’s data shall be provided, when possible. State the data elements to be encoded in the mark. Include a readable PDF417 barcode with the data encoded correctly; specify the data string encoded in the mark, including control characters; or both.

3.3.4.1.2 For data elements encoded in a PDF417 barcode on an Exterior Container, state the data elements to be encoded in the mark. Include a readable PDF417 barcode with correctly encoded data;

specify the data string encoded in the mark, including control characters; or both. The actual item’s data shall be provided, when possible.

3.3.5 The Quality Assurance (QA) processes for the item mark, which ensure the item’s Machine Readable Information (MRI) complies with MIL-STD-130.

3.3.5.1 Validation and verification. Include a description of the specific equipment used to perform validation and verification, and the sampling technique when 100% verification and validation is not planned.

3.3.5.2 Format and frequency. Identify a format and frequency for contractually-required reporting of validation and verification results, to include a pass or fail rating for each mark verified and each mark validated.

3.3.5.3 State where validation and verification is to be performed (i.e., contractor facility or sub-contractor facility).

3.3.5.4 Describe the process used for replacing any marks that fail a QA check.

3.3.5.5 State contract data item numbers from the Contract Data Requirements List (CDRL) that pertain to QA on IUID marks.

3.3.6 The packaging mark QA processes:

3.3.6.1 Describe packaging mark validation. In the absence of packaging mark validation software, a manual comparison of the encoded data string to the requirements of MIL-STD-129 shall be included.

3.3.7 Facilities and marking equipment to be employed:

3.3.7.1 State where item labels or plates are created (i.e., contractor or sub-contractor facility).

3.3.7.2 Describe marking equipment used, to include any potential environmental impacts of the marking process and procedures designed to mitigate the risks of potential environmental impacts.

3.4 Describe data management processes:

3.4.1 Identify the actions required to register the pedigree data for the items marked with IUID in the DoD IUID Registry, in accordance with DFARS 252.211-7003.

3.4.2 When the contract requires non-warranty repair of items designated for IUID, describe the processes to:

3.4.2.1 Assess the readability of the data matrix marks on the items received that are marked with a data matrix.

3.4.2.1.1 Re-mark items with unreadable data matrix marks, which encode the original UIIs. The descriptions shall address the following: Will the complete data plate be remade? Will an additive label be applied? Will the original data matrix be obliterated?

3.4.2.2 Determine whether unmarked items were previously assigned a UII, and, if the mark is detached from the item, ensure that the remarked item uses the original UII.

3.4.2.3 Assign and mark a UII on DoD-owned items requiring IUID, but not previously assigned a UII.

3.4.2.3.1 Register new UIIs using the Repairable Receiving Report in Wide Area Work Flow (WAWF).

3.5 Provide the Master Schedule for IUID marking, to include:

3.5.1 Target dates for:

3.5.1.1 First submission of the marking plan.

3.5.1.2 Government approval of the IUID marking plan.

3.5.1.3 Commencement of marking (first item).

3.5.1.4 First item acceptance by Government.

3.5.1.5 Any other key events.

3.5.2 When marking is contingent on non-recurring engineering actions or is to be sub-contracted, state the projected schedules related to those processes.

End of DI-MGMT-81803A

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 thus burden estimate or any other aspect of this collection o f information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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:

0009/1009/2009/3009/4009 A/B/C/D/E TDP TM OTHER:

NDTI

D. SYSTEM ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Multiple Systems FD2060-26-00154 BAE Systems

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A/B/C/D/E

Production Surge Plan

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MGMT-80969 PWS Para 4.3.11, 5.11 See Block 16

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT See BLK 16 See BLK 16 b. COPIES

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE DRAFT FINAL

A See BLK 16 See BLK 16 Reg Repr o

16. REMARK See Block 16 0 1 0 CLIN Exhibit Data Item No Period of Performance 0009 A A003 Base Year Period 1009 B B003 Ordering Period 1 2009 C C003 Ordering Period 2 3009 D D003 Ordering Period 3 4009 E E003 Ordering Period 4

Block 6: Requiring activity to be cited on each individual order.

Block 8: The length of time required for government approval and/or disapproval and subsequent turn-around time for the contractor to resubmit the data after Government approval and/or disapproval has been issued will be cited on each delivery/task order.

Block 9: Distribution authorized to the Department of Defense and U.S. DoD contractors only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting capabilities vital to National Security that are otherwise not publicly available (Vulnerability of Information) (27 September 2023). Other requests for this document shall be referred to the Procuring Contracting Officer (PCO)/Ordering Procuring Contracting Officer (OPCO).

Blocks 10-13: Frequency and submission dates to be cited by the requiring activity on each individual order.

Block 14: Distribution to be cited by the requiring activity on each individual order.

Report deliveries shall be submitted electronically via email to the applicable Government personnel identified by the requiring activity on each individual order.

Note: The contractor shall notify the Government Procurement Contracting Officer (PCO) if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date via electronic mail. This report does not serve as official notification to the requirements activity and/or PCO.

15. Total 0 1 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

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 thus burden estimate or any other aspect of this collection o f information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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:

0009/1009/2009/3009/4009 A/B/C/D/E TDP TM OTHER

SESS

D. SYSTEM ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Multiple Systems FD2060-26-00154 BAE Systems

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A/B/C/D/E

Engineering Change Proposal (ECP)

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-SESS-80639E PWS para 4.5.1.2, 4.5.1.2.1, 4.5.1.2.2

See Block 16

7. DD 250 REQ 9. DIST

STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT See BLK 16 See BLK 16 b. COPIES

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE DRAFT FINAL

A See BLK 16 See BLK 16 Reg Repr o

16. REMARKS See Block 16 0 1 0 CLIN Exhibit Data Item No Period of Performance 0009 A A004 Base Year Period 1009 B B004 Ordering Period 1 2009 C C004 Ordering Period 2 3009 D D004 Ordering Period 3 4009 E E004 Ordering Period 4

Block 6: Requiring activity to be cited on each individual order.

Block 8: The length of time required for government approval and/or disapproval and subsequent turn-around time for the contractor to resubmit the data after Government approval and/or disapproval has been issued will be cited on each delivery/task order.

Block 9: Distribution authorized to the Department of Defense and U.S. DoD contractors only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting capabilities vital to National Security that are otherwise not publicly available (Vulnerability of Information) (27 September 2023). Other requests for this document shall be referred to the requiring

Blocks 10-13: Engineering Change Proposals (ECPs) shall be submitted as required by the contractor.

Block 14: ECPs shall be delivered electronically via e-mail. Action concerning the enforcement of CDRLs will be executed by the Ordering Procurement Contracting Officer (OPCO) and distribution will be delineated under individual orders issued hereunder.

Note: The contractor shall notify the Government Procurement Contracting Officer (PCO) if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date via electronic mail. This report does not serve as official notification to the requirements activity and/or PCO.

15. Total 0 1 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Title: ENGINEERING CHANGE PROPOSAL (ECP)

Number: DI-SESS-80639E Approval Date: 20200211 AMSC Number: N10140 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: NM Project Number: SESS-2020-003 Applicable Forms: DD Form 1692, Engineering Change Proposal (ECP)

Use/relationship: An Engineering Change Proposal (ECP) provides the documentation in which the engineering change is described and specifies how the proposed change will be implemented.

a. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in EIA-649-1 and the principles of EIA-649 (Copies of these standards are available online at www.sae.org or from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel 877-606-7323 [inside USA and Canada] or 724-776-4970 [outside

USA]).

b. This DID may be used in conjunction with DI-SESS-80642, Notice of Revision (NOR). A requirement for NORs and Specification Change Notices (SCN) should be contractually imposed in conjunction with this DID.

c. This DID supersedes DI-SESS-80639D.

d. An electronic version of DD Form 1692, Engineering Change Proposal (ECP), is available online at https://www.esd.whs.mil/dd/.

Requirements:

1. Reference Documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2. Format. The ECP shall be in one of the following formats:

a. DD Form 1692, Engineering Change Proposal (ECP),

b. or

c. format.

3. Content. The ECP shall contain all the information required by DD Form 1692.

End of DI-SESS-80639E

DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.

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 thus burden estimate or any other aspect of this collection o f information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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:

0009/1009/2009/3009/4009 A/B/C/D/E TDP TM OTHER:

MGMT

D. SYSTEM ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Multiple Systems See Block 16 BAE Systems

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A/B/C/D/E

Supply Chain Risk Management (SCRM) Plan

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18.

ESTIMATED

TOTAL

PRICE

DI-MGMT-82256A/T PWS para 4.5.2, 4.7 See Block 16

7. DD 250 REQ 9. DIST

STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT See BLK 16 See BLK 16 b. COPIES Final

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE DRAFT FINAL

A See BLK 16 See BLK 16 Reg Repr

16. REMARKS See Block 16 0 1 0 CLIN Exhibit Data Item No Period of Performance 0009 A A005 Base Year Period 1009 B B005 Ordering Period 1 2009 C C005 Ordering Period 2 3009 D D005 Ordering Period 3 4009 E E005 Ordering Period 4

Block 4: Contractor format is acceptable. DID reference, Section 3.4, f (5) and h (2): Any changes to the SCRM Plan or Risk Register will be submitted to the Government within 30 calendar days after revision.

Block 6: Requiring activity to be cited on each individual order.

Block 8: For the SCRM Plan and Risk Register, the Government has 15 calendar days to review the preliminary draft. Comments will be provided. Contractor shall incorporate Government comments into the final document. Acceptance is based on technical content.

Final report is due 15 calendar days after receipt of Government comments.

Block 9: Distribution authorized to the Department of Defense and U.S. DoD contractors only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting capabilities vital to National Security that are otherwise not publicly available (Vulnerability of Information) (27 September 2023). Other requests for this document shall be referred to the Procuring Contracting Officer (PCO)/Ordering Procuring Contracting Officer (OPCO).

Blocks 10-12: The contractor shall submit an initial SCRM Plan and Risk Register to the PM/LM and the PCO electronically via e-mail.

a. SCRM Plan:

i. If creating an initial plan for a 5 year time period, then provide 90 calendar days after contract award.

ii. If a current 5 year plan is available, then provide within 10 calendar days of contract award.

b. Risk Register: Initial report shall be provided within 90 calendar days after contract award.

Block 13: Any changes to the SCRM Plan or Risk Register will be submitted to the Government within 30 calendar days after revision.

Note: The contractor shall notify the Government Procurement Contracting Officer (PCO) if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date via electronic mail. This report does not serve as official notification to the requirements activity and/or PCO.

15. Total 0 1 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Title: SUPPLY CHAIN RISK MANAGEMENT (SCRM) PLAN

Number: DI-MGMT-82256A Approval Date: 20230203 AMSC Number: F10374 Limitation: N/A DTIC Applicable: No GIDEP Applicable: Yes Preparing Activity: 11 (AFLCMC/LZS) Project Number: MGMT-2022-030 Applicable Forms: N/A

Use/Relationship: The Supply Chain Risk Management (SCRM) Plan defines the structured, contractor-proposed SCRM strategy relative to the products and services to be provided by the prime, its suppliers, and subcontractors. The SCRM plan will include a systematic process used to identify, assess, handle, and monitor supply chain risks associated with the product or service to be provided. This information will be used by the Government to maintain oversight of the contractor’s holistic SCRM Plan to effectively handle risks within the supply chain.

This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

This DID supersedes DI-MGMT-82256.

Requirements:

1. Reference documents. DI-MGMT-82255A, DoDI 5000.90, DoDM 4140.01. Copies of the DoD

Directives can be found at https://www.esd.whs.mil/DD/.

2. Format. Government directed electronic format shall be used to the fullest extent possible;

however, if none identified, the contractor’s electronic format, Microsoft Word® version .docx, is acceptable.

3. Content. The SCRM plan shall contain the following:

3.1 Cover and Title Page. This page shall identify the following:

a. SCRM Plan date of issue;

b. SCRM Plan document number;

c. Contract number;

d. Contractor’s name and address;

e. Title of plan;

f. Program title;

g. Security classification;

h. USD(R&E) Critical Technology List (if applicable);

i. Distribution statement; and

j. Destruction notice, if applicable.

k. Cybersecurity Maturity Model Certification (CMMC) certification level (Note: DoDI 5000.90

3.4.a)

DI-MGMT-82256A

3.2 Revision Control. The SCRM plan shall contain a list of all revisions identifying the following information:

a. Each revision number;

b. Date of each revision;

c. Pages affected by each revision; and

d. Summary of major content changes.

3.3 Table of Contents. The table of contents shall identify each major section title, paragraph number, and starting page number for each major section.

3.4 Section Contents. The SCRM Plan shall address each major section identified below:

a. Scope. This section shall include:

(1) Defining SCRM applicability to the prime and all suppliers, subcontractors, associated integrators, and vendors;

(2) Defining SCRM as the coordinated, holistic approach, involving all supply chain stakeholders, which identifies, assesses, handles, and monitors supply chain risks associated with weaknesses, vulnerabilities, and threats, addressing both services and products; and

(3) Defining the supply chain as the linked activities associated with providing materiel from a raw material stage to an end user as a finished product.

b. SCRM Strategy. This section shall provide an overview of the contractor’s overall SCRM strategy. It will include how the contractor plans to identify, assess, handle, and monitor risks in the lifecycle supply chain that have the potential to jeopardize the integrity of assets, compromise related intellectual property, disrupt the flow of critical goods or services needed for continued Department of Defense (DoD) operations, unexpectedly drive materiel cost increases to programs, or compromise national security.

c. Responsible Organizational Component. This section shall include:

(1) Contractor’s organizational SCRM construct; and

(2) Contractor’s primary and alternate focal points’ contact information to include names, duty titles, addresses, telephone numbers, and email addresses.

d. SCRM Processes and Procedures. This section shall describe:

(1) Processes for: Protecting products and services throughout the entire lifecycle; identifying, assessing, handling, and monitoring potential supply chain threats, weaknesses, and vulnerabilities; and analyzing identified potential disruptions for the program’s supply chain, suppliers, products, technologies, and services; and

(2) Process for revising the SCRM Plan in accordance with government guidelines during the lifecycle of the program, and for providing a copy of the SCRM plan to the Government Product Support Manager or Program

Manager.

e. Supply Chain Risk Identification. This section shall describe in detail:

(1) Processes and tools utilized to identify supply chain risks and associated root causes as early as possible;

(2) Intelligence-based and counter-intelligence-based techniques and commercial business tradecrafts employed to uncover and map supplier networks; and

(3) Process for communicating supply chain risks to affected stakeholders and the Government Program Support Manager or Program Manager.

f. Supply Chain Risk Assessment. This section shall include:

(1) Process to scan the contractor’s supply chain network (to include sub-tier suppliers), applying risk categories, to identify and assess supply chain risks that could impact the Government’s program;

(2) Contractor’s methodology for assessing all vendors or sources of supply to identify potential threats and vulnerabilities;

(3) Processes for analyzing root causes and assigning a risk rating by assessing the likelihood of occurrence; and determining severity of impact to the contractor’s supply chain.

As proscribed in DoDM 4140.01 Supply Chain Materiel Management Policy, SCRM owners assess supply chain risk by determining the severity of impacts to 1.) integrity of goods and services; 2.) assurance of supply; and 3.) economic efficiency to the contractor’s supply chain.

Processes for assessing SCRM risk impacts are specific to risks originating from the supply chain and do not encompass all enterprise or program risks.

However, successful supply chain risk management does enable Program Managers to proactively manage risks associated with cost (economic efficiency), schedule (assurance of supply), and performance (integrity of products or services).

(4) Process to focus attention on critical risks and document in the Supply Chain Risk Register; and

(5) Process to report the Supply Chain Risk Register to the Government Product Support Manager or Program Manager on a quarterly basis.

g. Supply Chain Risk Handling. This section shall include:

(1) Supply chain risk handling plans to combat identified and potential supply chain risks. It shall include:

(a) A descriptive title for each supply chain risk;

(b) Root cause or trigger of each risk;

(c) Possible risk handling plan to alleviate each risk; and

(d) Description of events and activities intended to accept, avoid, mitigate, or transfer the risk, success criteria for each planned event, and residual risk rating (acceptable level of risk). Reference DI- MGMT-82255A Supply Chain Risk Register.

(2) Methodology to prioritize potential supply chain risks;

(3) Process to capture risks and associated details, relative to the products and services to be provided, in a risk register.

h. Supply Chain Risk Monitoring. This section shall include:

(1) Process for the persistent and comprehensive monitoring and re-evaluation of supply chain risks and corresponding risk handling plans;

(2) Process for reporting risk monitoring information to the Government Product Support Manager or Program Manager quarterly; and

(3) The Supply Chain Risk Register will include a unique risk identifier, risk category and description, risk rating, risk handling response, responsible POC, expiration date, and current status. Reference DI-MGMT-82255A Supply Chain Risk Register.

i. SCRM Training. This section shall describe in detail:

(1) SCRM training that promotes an understanding of the basics of SCRM as a practice, the nature of risks facing supply chains, and the recommended approaches;

(2) SCRM-related course numbers, titles, sources, and descriptions;

(3) Number of personnel trained in each of the aforementioned courses; and

(4) Duty titles of personnel trained.

End of DI-MGMT-82256A.

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 thus burden estimate or any other aspect of this collection o f information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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:

0009/1009/2009/3009/4009 A/B/C/D/E TDP TM OTHER:

MGMT

D. SYSTEM ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Multiple Systems FD2060-26-00154 BAE Systems

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A/B/C/D/E

Status Report

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MGMT-80368A/T PWS para 4.3.13, 4.3.13.3, 4.3.13.4, 4.5.1

See Block 16

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT See BLK 16 See BLK 16 b. COPIES

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE DRAFT FINAL

N/A See BLK 16 See BLK 16 Reg Repr o

16. REMARKS See Block 16 0 1 0

CLIN Exhibit Data Item No Period of Performance 0009 A A006 Base Year Period 1009 B B006 Ordering Period 1 2009 C C006 Ordering Period 2 3009 D D006 Ordering Period 3 4009 E E006 Ordering Period 4

Block 4: Contractor format is acceptable. DID reference, Section 3.2.3: Contractor is not required to provide cost or financial data on FFP.

Block 6: Requiring activity to be cited on each individual order.

Block 9: Distribution authorized to the Department of Defense and U.S. DoD contractors only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting capabilities vital to National Security that are otherwise not publicly available (Vulnerability of Information) (27 September 2023). Other requests for this document shall be referred to the Procuring Contracting Officer (PCO)/Ordering Procuring Contracting Officer (OPCO).

Blocks 10-13: The first report shall be submitted to the Government PM/LM and EN electronically via e-mail, after the first full month of the contract. Government comments will be provided within 10 business days after submittal. Errors shall be corrected and the report shall be resubmitted within 10 business days after receipt of Government comments. Reporting shall continue on a monthly basis.

The contractor shall notify the Government Procurement Contracting Officer (PCO) if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date via electronic mail. Note: This report does not serve as official notification to the requirements activity and/or PCO.

15. Total 0 1 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Title: Status Report

Number: DI-MGMT-80368A Approval Date: 30 OCT 2006 AMSC Number: 7619 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship:

The Status Report documents the status of contractor effort towards achieving contract objectives. It identifies accomplishments to date and difficulties encountered, and compare the status achieved to planned goals and the resources expended. It is used by the Government to monitor and evaluate contractor performance.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

It is not intended that all requirements herein should be applied to every program.

Portions of the DID are subject to tailoring by deletion depending on the specific status reporting requirements of the project.

This DID is related to DI-FNCL-80331, Funds and Man-Hour Expenditure Report which can be used in conjunction with this report if paragraph 3.2.3 below is deleted.

This DID supersede DI-MGMT-80368.

Requirements:

1. Reference documents. None.

2. Format. The Status Report shall be in contractor format.

2.1 Identification. The data indicated below shall be contained on a title page or on the first page of the report.

a. Title/identification of the system/component/program/project.

DI-MGMT-80368A

b. Type of report (e.g., monthly, interim, final).

c. Period covered by the report.

d. Contract number.

e. Preparing activity or contractor’s title.

f. Security classification, when required.

g. Distribution Statement.

2.2 Page size. The report shall be on 8 ½ by 11 inch (metric A4) paper.

3. Content. The report shall contain the following:

3.1 Summary. The summary shall include a brief statement of the overall project status , covering the accomplished technical activities and development, objectives of efforts, summary results of efforts, identification of major problems/deficiencies with impact, and recommended solutions.

3.2 Body of report. The Status Report shall contain the following items, where applicable:

3.2.1 Milestone/task status. The status of each milestone/task as defined by the statement of work or contract, as applicable:

a. A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include an overall status of each milestone, task, or unit of work. Include update schedule sheets, milestone charts, or task synopsis sheets identifying phase of task and percentage of completion of each task, technical instruction, or order.

b. A comparison of achieved end-product performance capabilities projected against contract baseline values, requirements, or allocations.

c. Effort expended on each task to date, and a brief description of technical developments and accomplishments.

d. Key dates in any testing program and description of tests performed and significant test results. If applicable, a description of the amount and type of down time on the equipment or system under test.

e. A list of all designs completed and a brief description of each item. For designs in process, provide estimated dates for design and drawing completion.

f. A narrative of outstanding problems existing as of the previous status report, and their resolution status. 2

DI-MGMT-80368A

g. New problem areas encountered or anticipated, their effect on the overall work effort/project and steps being taken to remedy problem situations.

h. Significant results of conferences, trips, or directives for the Contracting officer’s representatives.

i. Any other information which may cause significant changes in the program schedule.

3.2.2 Future plans. Summary of future plans, recommendations and proposals both for the next reporting period and for any long term plans.

3.2.3 Itemized man-hours and costs. Itemized man-hour and cost expenditure incurred for the reporting period by category and task, total contractual expenditures, and funds remaining as of the reporting date.

3.2.4 Contract deliveries status. The status of each deliverable end item, including data deliverables, as required by the contract. Provide item and contract identification, shipping/transmittal data, acceptance status, security classification, and schedule due date information.

3.2.5 Report preparer. Name of person(s) preparing report and telephone number(s).

3.3 Appendices. Appendices where applicable, for tables, references, charts, or other descriptive material. Each appendix shall be identified and referenced in the appropriate area of the report.

4. END OF DI-MGMT-80368A

Public reporting burden for this collection of information is estimated to…