Attachment3E-9CDRLPackage7Jun2022.pdf

Section J

Exhibit A

Contract Data Requirements List (CDRL)

FOR

TELEMETRY RELAY SYSTEM

FOR THE E-9A AIRCRAFT

FA8106-22-R-0003

Prepared by:

E-9A Integrated Product Team

Specialized Training Aircraft Branch Program Office Tinker AFB, OK

Revision Revision Summary Date New Basic 9 July 2021

1 Updated each CDRL with specific tailoring

3 Jun 2022

CONTRACT DATA REQUIREMENTS LIST (CDRL)

Table of Contents

CONTRACT DATA REQUIREMENTS LIST (CDRL)

General Instructions CDRL Explanation (DD Form 1423-1) List of Addresses

CONTRACT DATA REQUIREMENTS LIST (CDRL)

General Instructions

The following CDRL General Instructions are applicable to the contract number identified on the Title page. The associated Data Item Description (DID) will be noted in the Statement of Work (SOW) and any deviation to the lower CDRL General Instructions will also be noted in the affected SOW.

1. The Contract Data Requirements List (CDRL) identifies the data deliverables for the related Contract Line Item

Numbers (CLINs) pursuant to the tasks defined in the SOW.

2. Contractually binding instructions for data content and format preparation are in Block 10, “Preparation

Instructions”, of the applicable Data Item Description (DID), and permit the easy segregation of content related to specific efforts. Tailored instructions are on the CDRL or backup sheets that will be attached to the affected Contract Delivery Order. In such cases, a “/T” (tailored) is suffixed to the DID number. The Contractor shall not deviate from the requirements of the DID, tailored or untailored, without receiving prior approval of the Procuring Contracting Officer (PCO).

3. The CDRLs were prepared using the following documents for guidance and information:

a. DoD 5010.12-L, Acquisition Management Systems and Data Requirements Control List (AMSDL), dated 1 October 2000

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

c. DoD Directive 5230.24, Distribution Statements on Technical Documents

4. Unless otherwise specified, the submittal dates for the CDRLs are based on the effective date of the contract.

Submittal dates falling on non-business days (Saturday, Sunday, legal holidays) shall be construed to mean the first business day following such non-business days. All submittal time periods (e.g., “60 days after contract award”, “30 days prior to test”, etc.) shall be calendar counted days. Data that are dependent on events that may not occur during the performance of the contract will be submitted on an “as required” basis.

5. Unless otherwise specified, the submittal date is the date the data is required at the office specified in Block 6 of the

CDRL. Distribution to other recipients of the data shall be made on or about the same date. In the event data is delivered electronically receipt confirmation by this office may be made on line.

6. Data Transmittal Form (DTF) shall contain the Contract number including the Delivery Order (DO) number, the

CDRL sequence number, the date of transmittal, and the Contractor’s reference number. The DTF will identify the data by title and document number, as well as the type of submission (e.g., draft, final, resubmission of draft, change pages, etc.). It shall also include a list showing addressees, distribution made, and number of copies distributed. One information copy of all DTF’s shall be forwarded to addressees identified in Block 14. Receipt acknowledgement by means of endorsement and return at the DTF to the Contractor is required for classified documents only.

7. All correspondence relating to data items shall reference the contract number including the contract number and

CDRL sequence number, and the DID number.

8. Unless otherwise specified, an “A” in Block 8 of the CDRL indicates written approval by the PCO shall be provided before distribution of the final data. The Government will respond within 45 days of receipt of the data, unless a different time period is specified on the CDRL. (NOTE: ECPs, SCNs, RFDs, and RFWs are exempt from this approval cycle.) However, Government failure to respond to the Contractor within this 45-day period does not constitute Government approval of data deliveries and does not construe tacit approval of the initiation of an effort.

Government written responses shall be provided in one of three categories only: (1) Approved as Written; (2) Approved with Comments; or (3) Disapproved. Data that is “Approved with Comments” will be updated by the Contractor to incorporate the comments and resubmitted within 3 business days of receipt of the Government response, unless otherwise directed by the PCO or contract requirements. This resubmitted data shall be considered final and will not require further Government approval if the comments have been incorporated as provided. In the event the Contractor takes exception to any Government comments, these shall be addressed in writing to the Government.

9. In the event that a data submission is disapproved, the PCO will advise the Contractor of the reason(s) for disapproval. Disapproved data items shall be revised to address/include the comments, and shall be resubmitted (or change pages provided) to the Government within the time frame noted above. These re-submittals, or change pages, shall not be regarded as subsequent submittals as specified in Block 13 of the CDRL, unless the next submittal of the CDRL is scheduled such that this would be a duplication of effort. (For example, an item submitted 90 days prior to test, which is disapproved and is due again 30 days prior to test, would be revised to address/include the comments in the next scheduled submittal.) The Government will review the changes the Contractor has made to the data addressing Government comments/disapproval, and will limit subsequent review(s) to address only those changes (with the exception of those instances where comments are incorporated in the next scheduled submittal).

10. In the absence of an “A” in Block 8 of the CDRL, it is understood that the Government has the inherent right to approve/disapprove any data submittal which does not meet the contractual requirements of the DID, tailored or untailored.

11. The Contractor will take care not to unnecessarily duplicate data previously procured by the Government, except to provide required copies to newly established recipients under this contract. Instances of unnecessary duplications should be identified to the Government. The Contractor is encouraged to recommend deletions, additions, substitutions, consolidations, and use of existing Contractor formats for data when such actions will aid the Government in obtaining minimum essential data in a timely and cost effective manner.

12. For delivery orders that have codes DD, DS, SD or SS in Block 7 of the CDRL require the processing of a DD Form

250, Material Inspection and Receiving Report. If none of these codes are present in Block 7 then a DD Form 250 is not required for that data item. The code letter “S” indicates “Source” and refers to the Contractor’s facility; the code letter “D” indicates “Destination”. The first code letter indicates the point of preliminary inspection (for count, style, format, legibility, reproducibility, etc.). The second code letter indicates the point of formal acceptance (on DD Form 250). In cases where draft copies are required, the draft copies shall be provided by a DTF. A DD Form 250 is required only for transmittal of the final copies to the office identified in Block 6 of the CDRL. In addition a final DD Form 250 shall be provided at the completion of all final CDRL deliveries against applicable sub-CLINs.

13. Requirements for periodic revisions to data, where no changes have occurred since the date of last submission, may be satisfied by a DTF stating that “No changes have occurred since the last submission”. Requirements for submittal of data “if changed”, where no change has occurred prior to the submittal requirement, may be satisfied by a DTF stating that “No change has been made to the data to date.” In such cases, the Contractor will identify the data in question, and the reporting period.

14. Distribution Statement requirements are specified in Block 9 of the CDRL. The code letter corresponds to the

Distribution Statement to be marked on the technical data item by the Contractor. An abbreviated form of the Distribution Statement will be placed in Block 16 of the CDRL. The following are the code letters applicable to this CDRL, with the corresponding Distribution Statement (see Block 9 on CDRL Explanation Page).

15. The Contractor will be notified in writing of any of the following changes to Block 14 of the CDRL:

a. Place of delivery

b. Technical office symbol

c. Increase or decrease in addressees

d. Increase or decrease in the number of copies (regular or reproducible) specified for any addressee

The written notification will include redlined CDRLs. The Contractor may use this written notification as its authority until the issuance of a contract modification incorporating the CDRL change. There is no contract price change for changes (a) or (b) above. There may be a contract price change for changes (c) or (d) above, provided that either type of increase or decrease for an individual CDRL is not greater than 50% of what was initially specified.

The Government and Contractor will negotiate any equitable adjustments in the event that the change is greater than 50%.

Questions regarding preparation and content of the CDRLs may be directed to organization listed on Title page.

CDRL Explanation (DD Form 1423-1)

Block 1: Data Item No:

Sequential number that the data will be delivered under.

Block 2: Title of Data Item:

The Title of the DID cited in Block 4.

Block 3: Subtitle:

Subtitle of data item for further definition of data item (optional entry).

Block 4: Authority:

The DID number that defines data content and format requirements for the data item listed in Block 2. All MIL-STDs of MIL-SPECs referenced in a data item description are for guidance only, unless otherwise directed in the DD 1423.

Block 5: Contract Reference:

The specific paragraph number(s) of the TD, specification, standard, or other applicable document that contain the tasking for generating the data requirement.

Block 6: Requiring Office:

The technical office responsible for ensuring adequacy of the data item.

Block 7: DD 250 Req:

The applicable code, designating the requirement for inspection and acceptance of the data item.

DD 250 REQ CODE INSPECTION ACCEPTANCE

SS (1) (2)

DD (3) (4)

SD (1) (4)

DS (3) (5)

LT (6) (7)

NO (8) (8)

(1) Inspection at source

(2) Acceptance at source

(3) No inspection performed at source. Final inspection performed at destination.

(4) Acceptance at destination

(5) Acceptance at source. Acceptance based on written approval from the PCO.

(6) Letter of Transmittal (LT) only

(7) As specified in Block 16 of the DD Form 1423-1

(8) No inspection or acceptance required. No DD form 250 or LT required.

Block 8: App Code:

Data items requiring specific advance written approval before distribution of the final data item will have “A” in this block. If approval of the data item is not required, an “N/A” will be in this block.

Block 9: Dist Statement Required:

The code letter that corresponds to the distribution statement to be marked on the technical data item by the contractor as specified in the Department of Defense Directive Number 5230-24.

DISTRIBUTION

STATEMENT DEFINITION

A Approved for public release; distribution is unlimited.

B Distribution authorized to U.S. Government agencies only (reason) (DATE). Other requests for this document shall be referred to E-9A Program Office, AFLCMC/WLDW.

C Distribution authorized to U.S. Government agencies and their contractors (reason) (DATE). Other requests for this document shall be referred to E-9A Program Office, AFLCMC/WLDW.

D Distribution authorized to the Department of Defense (DOD) and DOD contractors only (reason) (DATE). Other requests for this document shall be referred to E-9A Program Office, AFLCMC/WLDW.

E Distribution authorized to DOD components only (reason) (DATE). Other requests shall be referred to E-9A Program Office, AFLCMC/WLDW.

F Further dissemination only as directed by E-9A Program Office, AFLCMC/WLDW (DATE) or higher DOD authority.

X Distribution authorized to U.S. Government agencies and private individuals or enterprises eligible to obtain export-controlled technical data IAW regulations implementing 10 U.S.C. 140c (DATE). Other requests must be referred to E-9A Program Office, AFLCMC/WLDW.

N/A Not applicable. No distribution marking required.

The Contractor shall apply the following markings to data:

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. Government contractors only, critical technology, (insert contract award date).

Other requests for this document shall be referred to:

E-9A Program Office, AFLCMC/WLDW, 5316 S. Douglas Blvd, Building 8400, Room 105 Oklahoma City, OK 73150.

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

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

GOVERNMENT OWNERSHIP: The U. S. Government has unlimited rights to the information and data contained within this document.

Block 10: Frequency:

The following is a list of typical codes used to specify frequency of Submittals:

ABBREVIATION DEFINITION

MTHLY Monthly ASREQ* As Required BI-WE Every two weeks BI-MO Every two months DAILY Daily DFDEL Deferred delivery ONE/R One time/and revisions OTIME One time QRTLY Quarterly SEMIA Every six months YRLY Once a year

Block 11: As of Date:

If the data will be submitted only once, the “as of date” (the cut-off date) is entered as follows: day/month/year. This is the date for cutting off collection of data. If the data is to be submitted multiple times, the number in the block indicates the number of calendar days before the end of the reporting period, established in Block 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at 15 days before the end of the month, quarter or year depending on the frequency establish in Block 10.

Block 12: Date of First Submission:

The initial data submission is entered as follows: day/month/year. If the submittal is constrained by a specific event or milestone, the event or milestone is identified. If the contract start date is not known, the number of days the data is due after contract start is identified (e.g. 30 DAC).

Block 13: Data of Subsequent Submission:

For data items being submitted more than once, the date(s) of subsequent submissions is identified. If submittal is constrained by a specific event or milestone, this will be explained in Block 16.

Block 14: Distribution:

Block 14 provides for the following particulars:

Block 14a: Addressee:

A listing of who will receive the data item by their component designator or office symbols and/or codes, or unit identification codes. Complete addresses are in the next section of this attachment.

Block 14b: Copies:

The specific number and type of copies to be delivered to each addressee. When the data item requires advance written approval (indicated by an “A” in Block 8), draft copies are required for approval before publication of the final document to the addressees identified.

Block 15: Total:

The total number of draft and final copies required by Block 14.

Block 16: Remarks:

This block provides additional or clarifying information for Blocks 1 through 15, e.g., clarification relative to distribution statements, DID tailoring requirements, use of contractor format, and distribution of the data. If additional space is required, backup sheets, attached to the applicable DD Form 1423-1, will be used.

NOTE: For all references to “email” in Block 16, a list of valid emails will be provided the Post Award Conference.

List of Addresses

System Program Office:

E-9A Program Office, AFLCMC/WLDW, 5316 S. Douglas Blvd, Building 8400, Room 105 Oklahoma City, OK 73150.

Using Community:

82 ATRS

Hanger 4 Tyndall AFB, FL 32403