2. Exh_A_FY24 AGD CDRL Supplemental Instructions with CDRLs.pdf

EXHIBIT A, CONTRACT DATA REQUIREMENTS LIST, SUPPLEMENTAL INSTRUCTIONS

TBD

Upgraded Early Warning Radar (UEWR) FY24 Array Group Driver (AGD) Integration and Test

Contract Data Requirements List Supplemental Instructions

CONTRACT No.: TBD

ORDER NO.: TBD

EXHIBIT A

29 January 2024 Space Systems Command

Strategic Warning and Surveillance Systems Division Hardware Branch

SSC/SZQR

TABLE OF CONTENTS

Page

1.0 EXPLANATION OF CONTRACT DATA REQUIREMENTS LIST

2.0 SUPPLEMENTAL SECTION

3.0 CDRL ADDRESSEE LIST

4.0 ACRONYM LIST

5.0 CLIN, EXHIBIT AND DATA ITEM MATRIX

6.0 CONTRACT DATA REQUIREMENTS LIST VALIDATION

FY24 ARRAY GROUP DRIVER (AGD) INTEGRATION AND TEST

CONTRACT DATA REQUIREMENTS LIST (CDRL)

SUPPLEMENTAL INSTRUCTIONS

EXPLANATION OF CONTRACT DATA REQUIREMENTS LIST

The instructions for completing and/or understanding the Contract Data Requirements List (CDRL) DD Form 1423 can be found in DoD 5010.12-M, Procedures for the Acquisition and Management of Technical Data. The FY 24 contract uses the DD Form 1423-1 for all data items included in each CDRL. The contractor shall reference the appropriate DD Form 1423-1 block in all correspondence. The instructions for preparing each deliverable data item are given in the DD Form 1423-1.

The Government Contracting Officer (CO) may modify the delivery timeline with consensus from the contractor's Contracting Officer.

The contractor shall comply with the security requirements and instructions found in TBD, Attachment 3, DD Form 254, DoD Contract Security Classification Specification, for all CDRLs, to include marking, handling and storage. The contractor shall not use passwords for documents delivered to the Government.

The contractor shall not post any unprotected unclassified, controlled Government information on any system or network directly accessible from the public internet.

The Government selected the data authorities entered in Block 4, Authority, from the Acquisition Streamlining and Standardization Information System (ASSIST) database (available at http://quicksearch.dla.mil/). or from United States Air Force (USAF) Technical Manuals. The applicable issue of data authorities cited in the DD Forms 1423-1, including their approval dates and dates of applicable amendments, notices and revisions, are as represented in ASSIST at the time of the solicitation, or, for non-ASSIST data authorities, as stated in the contract. All comments, explanations and/or limitations on individual data authorities appear in Block 16, Remarks, of the DD Form 1423-1, referenced to Block 4, Authority, or on attached sheets to the DD Form 1423-1, which shall be taken as part of the data item preparation instructions.

2.0 SUPPLEMENTAL SECTION

2.1 The following instructions apply to the AGD Contract and apply to the CDRL data items included in this exhibit:

2.1.1 This CDRL includes a complete list of data deliverables required for the related Contract Line Item Numbers (CLIN). See Section 5 for further instructions on Data Item to CUN mapping.

2.1.2 The Government used the following documents and regulations in preparing the DD Forms 1423-1 and are identified below for guidance and information purposes:

1. ASSIST Online, http://quicksearch.dla.mil/

2. DoD 5010.12-M, Procedures for the Acquisition and Management of Technical Data, dated May 1993

2.1.3 Unless otherwise specified, the contractor shall interpret references to "contract award" as the award date of the Order in which the exhibit is included.

2.1.4 The contractor shall submit data to the identified Distribution Addressees IAW the delivery requirements specified in each DD Form 1423-1. For due dates falling on non-working days, the contractor shall make required deliveries on the next regular working day following such nonworking days. All references to "days" are calendar days unless otherwise specified in the contract requirements.

2.1.5 Data delivery dates are the date by which the contractor shall deliver the data item to all Distribution Addressees identified in Block 14 of the DD Form 1423-1. The contractor shall collect, prepare, publish and distribute the data item to the Addressees and in the quantity and types designated in Block 14 of the DD Form 1423-1. The contractor shall use the most economical method commensurate with the requirements unless otherwise specified in the DD Form 1423-1 or AGD Contract.

2.1.6 When practical, the contractor shall deliver data items via electronic media to the Government; if such delivery is not practical, the contractor shall deliver the data items on digital disc. The contractor shall make data deliveries using normal postal mailing facilities. The contractor shall minimize the use of overnight mail or other expedited handling methods.

Delivery and receipt of items via electronic means constitutes document submittal.

2.1.7 The contractor shall mark all data items IAW the DD Form 1423-1 and the (TBD DD Form 254), DoD Contract Security Classification Specification. When required, the contractor shall identify the "controlling DoD office" as Strategic Warning and Surveillance Systems Acquisition Delta, SSC/SZQK, Building 2025, 1050 E. Stewart Ave, Peterson SFB, CO 80914.

2.1.8 The contractor shall maintain unclassified data items delivered to the Government in an electronically-shared area in the Data Accession List (DAL) for the life of the AGD Contract or when the Government CO determines it is no longer needed. The contractor shall maintain the classified data items delivered to the Government in an electronically shared area in the classified data repository for the life of the AGD Contract or when the Government CO determines it is no longer needed.

2.1.9 Government inspection and acceptance of data items (DD Form 1423-1, Block 7, DD 250 Requirement):

2.1.9.1 The use of codes other than "LT" and "NO" in Block 7 requires inspection and acceptance by the Government Contracting Officer Representative (COR) and a DD Form 250 is required. In these cases, the contractor shall submit a Receiving Report (DD Form 250) in the Invoicing, Receipt, Acceptance and Property Transfer (iRAPT) [formerly the Wide Area Work Flow (WAWF)]. The data item is approved when the Government COR approves the contractor-submitted Receiving Report (DD Form 250).

2.1.9.2 The use of the code "LT" in Block 7 requires inspection and acceptance by the Government COR but a DD Form 250 is not required. In these cases, the contractor shall provide a record of delivery to the Government COR; however, the contractor is not required to submit the DD Form 250.

2.1.9.3 Unless otherwise stated in the contract, the Government shall have thirty (30) calendar days to inspect and accept or reject a data item. If the Government requires additional time, the Government COR will notify the contractor the Government requires additional time.

2.1.9.4 Data items submitted for inspection and acceptance are not automatically accepted without Government COR notification. When applicable, upon completion of the Government's inspection, the Government COR will notify the contractor of the results of the inspection. For data items requiring inspection and acceptance, the Government COR will respond to the data item delivery with one of the following options:

1. The Government inspected the submitted data item and accepts it without comment.

2. The Government inspected the submitted data item and acceptance is pending incorporation of attached comments. In this case, the Government COR will specify if resubmittal is required or whether the next submittal of the data item is sufficient.

3. The Government inspected the submitted data item and acceptance is being withheld pending resolution of attached comments and resubmission of the data item.

4. The Government inspected the submitted data item and rejects the data item based on the attached comments. In this case, the COR will specify if resubmittal is required or whether the next submittal of the data item is sufficient.

5. The Government did not inspect the submitted data item and it is neither accepted nor rejected. If a future inspection of the submitted data item identifies non-conformance with contract requirements, the Government may reject the data item and require resubmittal. If, within the 30-day Government inspection and acceptance period, the COR does not notify the contractor the Government requires additional time, the contractor shall assume this option is the Government's response option.

2.1.9.5 The Government has the inherent right to reject any data item (whether the Government identifies a requirement for inspection and acceptance or not). In the event the Government rejects a data item, the resubmittal requirements in paragraph 2.1.11 apply.

2.1.10 Government approval of data items (DD Form 1423-1, Block 8, Approval Code):

2.1.10.1 An "A" in APP CODE (Block 8) of the Contract Data Requirements List (DD Form 1423-1) indicates that formal written approval of the data item by the Government is required:

this includes draft submittals prior to final publication. The Government shall have thirty (30) calendar days to inspect and accept or reject a data item unless otherwise specified in the DD Form 1423-1. If the Government requires additional time, the COR will notify the contractor that the Government requires additional time. Items requiring approval shall be considered approved if the Government does not respond thirty (30) calendar days after receipt of the submittal or within the Government requested extended review timeline.

2.1.10.2 Unless otherwise stated in the contract, the Government shall have thirty (30) calendar days to approve or disapprove final distribution of the data item. If the Government requires additional time, the Government COR will notify the contractor the Government requires additional time.

2.1.10.3 Data items submitted for approval are not automatically approved without Government COR notification. For data items requiring approval for final distribution, the COR will respond to the data item delivery with one of the following options:

1. The Government reviewed the submitted data item and approves it for final distribution.

2. The Government reviewed the submitted data item and disapproves it for final distribution due to the issues identified in the attached comments.

2.1.11 Resubmission of data items:

2.1.11.1 The Government retains the right to approve/disapprove data delivered which does not meet the requirements of the DID, regardless of the coding of Block 8. Resubmission of disapproved/unaccepted data deliveries shall be submitted within 30 calendar days of receipt of Government comments unless otherwise directed. Upon resubmission of a data item, the Government shall have thirty (30) calendar days to inspect and/or review the submitted data item. If the Government requires additional time, the COR will notify the contractor the Government requires additional time. Items requiring approval shall be considered approved if the Government does not respond thirty (30) calendar days after receipt of the draft or final submittal. This approval direction has precedence over language incorporated into the DD Form 1423-1.

2.1.12 For all data items required to be submitted monthly or bi-monthly, if the Government accepts the submitted data item with comments, the contractor shall incorporate those comments into the next submittal. This approval direction has precedence over language incorporated into the DD Form 1423-1.

2.1.13 The contractor shall submit copies of Letters of Transmittal to the Government COR. The transmittal letter shall indicate the complete distribution of the data item and also state if a partial delivery is submitted. For those data items only requiring delivery to the DAL, as identified by DAL in Block 14 of the DD Form 1423-1, the Letter of Transmittal shall notify the Government the contractor posted the data item to the DAL. The contractor may satisfy the Letter of Transmittal requirement through electronic mail notification to the Government COR. If using electronic mail, the contractor shall include in the electronic mail notification the document title, date of posting to the DAL and details of the document location in the DAL.

2.1.14 Data Item Marking Requirements

2.1.14.1 Unless otherwise specified in the AGD Contract, the contractor shall identify data items it submits with the following elements at a minimum:

1. Contractor's Letter Number (Cite Number)

2. Contract Number

3. Data Item Number

4. Title of the Data Item

5. Subtitle of Data Item (if applicable)

6. Build Number (if applicable)

7. Revision Identification

8. Applicable System Nomenclature

9. Delivery Date

10. Prepared For

11. Prepared By

12. Distribution Statement

13. Destruction Statement

14. Classification Markings (if applicable)

2.1.14.2 When submitting data items via digital discs, the contractor shall mark each disc with elements listed in paragraph 2.1.14.1.

2.1.15 The distribution statement indicated in Block 9, Distribution Statement Required, shall be IAW TBD, DD Form 254, DoD Contract Security Classification Specification. The contractor shall mark distribution statements and export control statements, supplemental to all security markings, on all data to denote the intended audience and to identify requirements for secondary distribution.

2.1.16 During the performance of this contract, the Government CO unilaterally may increase or decrease the number of Distribution Addressees and/or increase or decrease the number of distribution copies specified for Distribution Addressees of data items at no change in the Target Cost or the Target Price, provided the change in the total number of copies for individual data items assigned to a CLIN is not greater than fifty percent.

2.1.17 Where a data item requires posting to the DAL, the contractor shall post a final version of the data item to the unclassified DAL or classified data repository, as appropriate. This shall follow all posting requirements developed for the data repositories and agreed to at the initial Kick-Off Meeting for the Order. For each applicable data item, this will be annotated by DAL as an entry in Block 14, Distribution of the DD Form 1423-1.

2.1.18 The contractor shall deliver data items that are not available via the unclassified DAL to the Product Division (PD) Configuration Manager

2.1.19 The contractor shall deliver data items that are not available via the classified data repository to the PD Government Engineering or Cybersecurity representative.

2.1.20 For revisions to existing data items, the contractor shall issue complete data items by revision number (i.e., the contractor shall not issue revisions to data items via change pages). The contractor shall identify modifications to the data items with changes bars (or other marking methods if change bars are not practicable) when the contractor submits those data items for review or for comparison. Change bars are not required for final submittals, new documents or documents whose changes required an approximate 50% or greater rewrite.

2.1.21 The contractor shall only delivery data items to those agencies specified on the DD Form 1423-1, Block 14, Distribution, Addressees list. The contractor shall refer requests for data items from organizations other than those listed in Block 14 to the Government CO.

2.1.22 The contractor shall maintain reproducible copies, as specified in Block 14, Distribution, in the data item's native editable format unless otherwise stated in the DD Form 1423-1. When providing native editable format versions of data items, the contractor shall also provide a Portable Document Format (PDF) version of the data item. For final data item deliveries, the contractor shall, in addition to the data item itself, provide editable versions of any embedded illustrations, diagrams, figures or graphics, unless they are provided in the main body of the data item. This requirement does not apply to screenshots or other images captured from noneditable sources.

3.0 CDRL ADDRESSEE LIST

3.1 The addressee list is contained in Table 1. The details of addresses and points of contact will be provided by the Government CO at contract award.

Table 1. AGD Contract Associated Agency Offices and Titles

Addressee Office Symbol Address & Point of Contact DAL Not Applicable Not Applicable

4.0 ACRONYM LIST

4.1 The following acronyms are used in the CDRL:

Acronym Meaning ABCL As Built Configuration List ABCL-C As Built Configuration List – Common ACA Associate Contractor Agreement ADLS Advance Distributed Learning System AECA Arms Export Control Act AETC Air Education & Training Command AFB Air Force Base AFMAN Air Force Manual AFTO Air Force Technical Order AGD Array Group Driver AMC Air Mobility Command BEAM BPP Essential System Performance Analysis Model BMEWS Ballistic Missile Early Warning System

BPP BMEWS/PAVE PAWS

CAC Common Access Card CAP Corrective Action Plan CAT Category CCB Configuration Change Board CDR Critical Design Review CFAE/CFE Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment CI Configuration Item CISF Centralized Integration Support Facility CLIN Contract Line Item Number CLSA Combined Logistics Support Agreement CO Contracting Officer CoC Certificates of Conformance COMSEC Communications Security COTS Commercial Off-the-Shelf CPIF Cost Plus Incentive Fee CRO COMSEC Responsible Officer CSCI Computer Software Configuration Item CWBS Contract Work Breakdown Structure CWE Common Weakness Enumeration DAL Data Accession List DBDD Database Design Description DDTC Directorate of Defense Trade Controls DEVDP Development Data Processor DFARS Defense Federal Acquisition Regulations Supplement DID Data Item Description DISA Defense Information Systems Agency DISCO Defense Industrial Security Clearance Office DMTS Digital Module Test Set

Acronym Meaning DMSMS Diminishing Manufacturing Sources and Material Shortages DoD Department of Defense DoDAF DoD Architecture Framework DoDD DoD Directive DPS Data Processing Set DRIP Design Review Information Package DT Development Test DTD Document Type Definition E3 Electromagnetic Environmental Effects E3IAR E3 Integration and Analysis Report EAL Evaluation Assurance Level EBMTLS Enterprise Backup and T-Disk Management System EMI Electromagnetic Interference EMICP EMI Control Procedures EMITP EMI Test Procedures EMITR EMI Test Report EO Executive Order ESLOC Estimated Single Lines of Code ESPTool Essential System Performance Tool ETTS Electronic Tape Transfer System EVMS Earned Value Management System FACAR Failure Analysis and Corrective Action Report FAR Federal Acquisition Regulations FCA Functional Configuration Audit FCT Formal Contractor Test FIPS Federal Information Processing Standard FMHER Funds and Man-Hours Expenditure Report FOSS Free and Open Source Software FPIF Fixed Price Incentive Firm FRD Facilities Requirement Document FSM Firmware Support Manual GBR ground-based radar GIDEP Government-Industry Data Exchange Program GFI DR Government Furnished Information Deficiency Report GOTS Government Off-the-Shelf HOL Higher Order Language IA Information Assurance IATT Interim Authorization To Test IAW in accordance with ICA Internal Controlled Area ICD Interface Control Document ICT information and communications technology IDD Interface Design Description IDE Integrated Data Environment IMS Integrated Master Schedule

IP Internet Protocol IPMR Integrated Program Management Report IPPS ION Pump Power Supply IPR In-Process Review IPT Integrated Product Team IQT Initial Qualification Training IRS Interface Requirements Specification ISSM Information System Security Manager ITT Integrated Test Team ITW/AA Integrated Tactical Warning/Attack Assessment IUID Item Unique Identification JDRS Joint Deficiency Reporting System JPAS Joint Personnel Access System JTR Joint Travel Regulations LAN Local Area Network LRU Line Replaceable Unit M&S Modeling and Simulation MD Missile Defense MDCR Maintenance Data Collection Record MDE Model Driven Engineering MDM Mobile Depot Maintenance MPTO Methods and Procedures Technical Order N/A Not Applicable NAC National Agency Check NACI NAC with Inquiries NACLC NAC with Local Agency Check and Credit Check NAR Network Access Request NDI Non-developmental item NIST National Institute of Standards and Technology NSA National Security Agency OA Operational Acceptance OCD Operational Concept Description OCM Original Component Manufacturer OEM Original Equipment Manufacturer OPSEC Operations Security OSI Office of Special Investigations OT Operational Test PARSE Phase Array Radar Simulation Environment PAWS Phase Array Warning System PCA Physical Configuration Audit PDR Preliminary Design Review PHS&T Packaging, Handling, Storage and Transportation PI Product Increment PMB Performance Measurement Baseline PPL Provisioning Parts List

PPLI PPL Index PRR Production Readiness Review PSM Product Support Manager PSTS Power Supply Test Set PUB Publication RAM Reliability, Availability and Maintainability RCL Radar Controller RDAT Radar Data Analysis Tool ReMR Reuse Management Report RHP Risk Handling Plan RMF Risk Management Framework SAR Safety Assessment Report SCOM Software Center Operation Manual SDD Software Design Description SDP Software Development Plan SDRR Site Deployment Readiness Review SDS Software Development Suite SDSR Software Development Status Report SE/ATS Support Equipment/Automated Test Systems SFR System Functional Review SGEN Scenario Generation SGML Standard Generalized Markup Language SIE Special Inspection Equipment SIEMS Security Information and Event Management Subsystem SIL Systems Integration Laboratory SIOM Software Input/Output Manual SIR Standards/Specification Interface Records SOW Statement of Work SPI Special Packing Instructions SPM System Program Manager SPS Software Product Specification

SRR System Requirements Review SRS Software Requirements Specification SRVM Specification Requirements Verification Matrix SSAct Servicing Security Activity SSBI Single Scope Background Investigation SSDD System/Subsystem Design Description SSN Space Surveillance Network SSS System/Subsystem Specification ST Special Tooling STAMP Strategic and Theater Attack Modeling Process STR Software Trouble Reports SUM Software User Manual SVD Software Version Description

SVR System Verification Review TA Test Assembly TAA Technical Assistance Agreement TBD to be determined TBR to be resolved TBS to be specified TCTO Time Compliance Technical Order TDA Technical Data Assessment TDM Time Division Multiplexing TFRD Test Facility Requirements Document TM Technical Manual TMCR Technical Manual Contract Requirements TO Task Order TODA Technical Order Distribution Account TOMA Technical Order Management Agency TOSS Technical Order Status and Schedule TPM Technical Performance Measure TRD Test Requirements Document TRR Test Readiness Review TRSS Training Support Squadron TSN Trusted Systems and Networks TTA Technical Assistance Agreement UAS UEWR Analysis Suite UEWR Upgraded Early Warning Radar USS UEWR Sustainment String V&V Verification and Validation

5.0 CLIN, EXHIBIT AND DATA MATRIX

5.1 Table 2: CLIN, Exhibit and Data Item Matrix identifies each assigned CDRL to the applicable CLIN(s) for pricing purposes. Block A identifies the specific CLIN, Block B specifies the exhibit the CDRLs are found in, and Block 1 identifies the CDRL numbering system as it relates to the CLIN it is charged against.

Table 2. CLIN, Exhibit and Data

Item Matrix Block A Block B Block 1

CLIN Exhibit Data Item No.

0001 A A001, A003

0002 A N/A

0003 A A002, A004, A005, A006, A007, A008, A009, A00A, A00B, A00C, A00D, A00E, A00F, A00G, A00H, A00J, A00K

6.0 CONTRACT DATA REQUIREMENTS LIST VALIDATION

6.1 Each DD Form 1423-1 in Order TBD, Exhibit A has been validated, prepared and approved by the Government.

TRAVIS J. POND, Maj, USSF

Branch Chief, UEWR Hardware Strategic Warning and Surveillance Systems Division

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

Adobe Professional 8.0

18. ESTIMATED

TOTAL PRICE

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

A

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

Raytheon Technologies (RTX)

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Integrated Program Management Data and Analysis Report

3. SUBTITLE

Integrated Master Schedule

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81861C/T

5. CONTRACT REFERENCE

PWS Paragraph 4.2.3.1

6. REQUIRING OFFICE

SSC/SZQ

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

MTHLY

12. DATE OF FIRST SUBMISSION

See Blk 16

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: DI-MGMT-81861C is tailored as follows.

1. USE/RELATIONSHIP

- Delete paragraphs 1.2.1, 1.2.3, 1.3 (and all sub paragraphs), 1.5, 1.6, 1.6.1, 1.6.1.1, 1.6.3,

1.7 (and all sub paragraphs), and 1.8.1.1.

2. DOCUMENT REQUIREMENTS

- Delete paragraphs 2.1, 2.3 (and all sub paragraphs), 2.4.2.6, 2.4.2.6.2, 2.4.2.7, 2.4.2.8 (and all sub paragraphs), 2.4.2.9, 2.4.2.10, 2.4.2.11, 2.4.2.12 (and all sub paragraphs), 2.2.4.16, 2.4.2.17, 2.4.2.18, 2.4.2.19 (and all sub paragraphs), 2.4.2.20, 2.4.2.21, 2.4.3 (and all sub paragraphs), and 2.5 (and all sub paragraphs).

- Paragraph 2.4.2.6.1 is edited to include only key tasks to create a summary level schedule

- Table 2.1 should only include verbal or e-mail discussion on Critical Path changes. All other elements of Table 2.1 are deleted.

- Table 2.2 is deleted in its entirety.

Block 12: The contractor shall submit the first time 45 business days after contract award.

Block 13: Subsequent updates shall be delivered monthly NLT the 20th calendar day of the following month.

Block 14: All submissions will be delivered via electronic delivery system, to UEWR

Product Division (PD) Configuration Management / Data Management (CM/DM).

SSC/SZQR 0 1 0

15. TOTAL 0 1 0

G. PREPARED BY

Josue C. Garcia, CTR

H. DATE I. APPROVED BY

Travis J. Pond, Maj, USSF

J. DATE

Reset

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

A

C. CATEGORY:

MGMT

TDP TM OTHER

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

Raytheon Technologies (RTX)

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page 2 of 3 Pages

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoD 5010.12-M for detailed instructions.)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

Item I. Signature of CDRL approval authority.

Item J. Date CDRL was approved.

Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort

(production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.

DD FORM 1423-1 (BACK), FEB 2001

18. ESTIMATED

TOTAL PRICE

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

A

C. CATEGORY:

TDP TM OTHER FNCL

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

Raytheon Technologies (RTX)

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Funds and Man-Hours Expenditure Report

3. SUBTITLE

N/A

4. AUTHORITY (Data Acquisition Document No.)

DI-FNCL-80331A/T

5. CONTRACT REFERENCE

PWS paragraph 4.2.3.2

6. REQUIRING OFFICE

SSC/SZQ

7. DD 250 REQ

LT

MTHLY

12. DATE OF FIRST SUBMISSION

8. APP CODE

N/A

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

Block 4: DI-FNCL-80331A is tailored as follows:

1. Paragraph 4.1 is replaced with "Funds and man-hour expenditure summary. This chart shall contain the following data elements."

2. Paragraph 4.1.1 is replaced with "4.1.1 Original negotiated contract. A summary of all cost elements associated with the original negotiated contracts. This is defined as the contractor's original cost proposal, as negotiated and accepted by the

Government. It is that cost as it appears on the original contract document. Items and amounts specified in this entry shall remain constant on successive reports during the term of the contract."

3. Each FMHER contains the required data for the elements technically described in

Contract Work Breakdown Structure (CWBS) (Level 4), as required in the performance of this order.

4. The contractor shall submit the FMHER in HTML and Microsoft Excel

2010-compatible format.

The FMHER format shall be contractor specified but must contain the following elements:

1. Provided itemized man-hour and cost expenditures incurred for the reporting period and total contract at the lowest WBS level

2. For each WBS element required in the performance of this order on the CPIF and FPIF CLINs, as reflected in FA8723-18-D-0001, Section J, Attachment 2, Contract Work Breakdown Structure (CWBS), a CLIN-level summary of the

Direct Labor Fringe/Overhead Rate dollar value relative to paragraphs 4.1.1 through 4.1.6.

3. For each CPFF CLIN required in this order, a CLIN-level summary of indirect costs and

Fee, broken out by element

(General and Administrative - allocated and unallocated, Fee), relative to paragraphs 4.1.1 through 4.1.6.

4. For each CR CLIN required in the performance of this order, relative to paragraphs 4.1.1 through 4.1.6.

5. For each CLIN required in the performance of this order, incremental funding by month and cumulative funding by month.

6. For the CPFF and CR CLINs required in the performance of this order separate graphs showing funds expenditures including

(continued on next page)

Josue C. Garcia, CTR

H. DATE I. APPROVED BY

(1 Data Item)

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

A

C. CATEGORY:

FNCL

TDP TM OTHER

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

Raytheon Technologies (RTX)

16. REMARKS (Continued)

7. For the CPFF CLIN required in the performance of this order, at an order summary level, a graph showing the percent of work completed including actuals and planned.

Block 11: The "As of Date" is the End of Accounting Period (EOAP) for the contractor's monthly accounting period.

Block 12: The contractor shall submit the initial FMHER no later than 20 calendar days after the EOAP for the contractor's first monthly accounting period after start of performance of this order.

Block 13: The contractor shall submit subsequent FMHERs no later then 20 calendar days after EOAP.

Block 14: All submissions will be delivered via electronic delivery system, to UEWR Product Division (PD) Configuration Management / Data

Management (CM/DM).

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data

18. ESTIMATED

TOTAL PRICE

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

A

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

Raytheon Technologies (RTX)

1. DATA ITEM NO.

A003

2. TITLE OF DATA ITEM

Technical Report - Study/Services

3. SUBTITLE

Work Plan

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508B

5. CONTRACT REFERENCE

PWS paragraph 4.3.22.1

6. REQUIRING OFFICE

SSC/SZQ

7. DD 250 REQ

LT

ASREQ

12. DATE OF FIRST SUBMISSION

8. APP CODE

A

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Contractor format is acceptable. Work Plan shall address at a minimum:

- Purpose

- Site visit coordination

- Red time requirements

- Facility drawings

- Tools, equipment, and information

- Program description

- Testing process

- Reference documents

- Safety

- Personal protective equipment

- Electrical Safety

- Lockout/Tag Out Program

- Warning Signs and Barricades

Block 8: The Government SSC/SZQR will respond with approval/disapproval within 5 business days. If no response from the Government within 5 business days, the CDRL shall be considered approved.

Block 9: Mark all CDRL items with the distribution statement as shown above in Block 9 and with the following additional statement: "The U.S. Government retains unlimited data/computer software rights to this item."

Block 12: Date of First Submission: 45 calendar days prior to the beginning of the testing at site.

Block 13: Date of Subsequent Submission: 15 calendar days prior to the beginning of the testing at site.

Josue C. Garcia, CTR

H. DATE I. APPROVED BY

(1 Data Item)

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

A

C. CATEGORY:

TDP TM OTHER

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

Raytheon Technologies (RTX)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data

18. ESTIMATED

TOTAL PRICE

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

A

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO. F. CONTRACTOR

Raytheon Technologies (RTX)

1. DATA ITEM NO.

A004

2. TITLE OF DATA ITEM

Test Plans/Test Procedures

3. SUBTITLE

Test Plan

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-81704

5. CONTRACT REFERENCE

PWS paragraph 4.3.22.2

6. REQUIRING OFFICE

SSC/SZQ

7. DD 250 REQ

LT

ASREQ

12. DATE OF FIRST SUBMISSION

8. APP CODE

A

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

Reg Repro

16. REMARKS

Contractor format is acceptable, provided data item meets all requirements of DID.

This CDRL is applicable to all hardware and software testing for this contract.

Block 8: The Government, SSC/SZQR, will respond with approval/disapproval within 20 business days. If no response from the Government within 20 business days, the data item shall be considered approved.

Block 9: All international (e.g., Great Britain, Canada) releasability and International

Traffic in Arms Regulations (ITAR) document marking restrictions and requirements apply to these data items.

Block 12: 20 business days after contract award.

Block 13: Revisions due within 15 business days following a replan. Final version due at or before last site final Test Readiness Review (TRR) or final Site Deployment Readiness

Review (SDRR), whichever is later.

Josue C. Garcia, CTR

H. DATE I. APPROVED BY

(1 Data Item)

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

A

C. CATEGORY:

SESS

TDP TM OTHER

D. SYSTEM/ITEM

Array Group Driver (AGD)

E. CONTRACT/PR NO. F. CONTRACTOR

Raytheon Technologies (RTX)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of production or development for the Government of that item of…