02c_CDRLs_Exhibit_CX_Signed.pdf

EXHIBIT CA, CB, CC, CD, AND CE

TO

FA8811-18-R-0001

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PHASE 1A

CONTRACT DATA REQUIREMENTS LIST (CDRLs)

31 January 2018

Department of the Air Force

Space and Missile Systems Center

Launch Systems Enterprise Directorate

Los Angeles Air Force Base, California

CDRL General Instructions CDRL Address List CDRL Distribution List CDRLs

CDRL GENERAL INSTRUCTIONS

Exhibit C Mission Organization

Mission Title Exhibit Section

NROL-85 CA

NROL-87 CB

SILENTBARKER CC

SBIRS GEO-5 CD

AFSPC-44 CE

CONTRACT DATA REQUIREMENTS LIST (CDRL)

A list of data requirements authorized for this specific procurement and made a part of this contract. The contractual method is the use of Department of Defense Form (DD Form) 1423s, Contract Data Requirements List (CDRL), which specifies the data to be delivered to the government. For the purpose of this agreement, the “contract” applies for each Launch Vehicle Service order.

DATA ITEM NUMBER

If the Contractor is awarded multiple Launch Vehicle (LV) Service orders, the Contractor shall use a sequential double alpha, single numeric number scheme. For example, Order 1 will have CDRLs AA01–AA11, AB01–AB20, and AC01;

and Order 2 will have CDRLs BA01–BA11, BB01–BB20, and BC01.

DATA ITEM DESCRIPTIONS (DIDs)

The Data Item Description (DID) is a specification for the preparation of data. The DIDs listed on the CDRLs were selected from the Department of Defense (DoD) Index of Specifications and Standards listed on the Acquisition Streamlining and Standardization Information System.

DID TAILORING

DID tailoring is made to either relax format requirements or to tailor the DID to be in consonance with the source document tailoring contained in the Performance Work Statement (PWS). Since contract data requirements are normally a byproduct of some contract task, if the requirements of the DID are in conflict with the tailored application of the source document as reflected in the PWS, the latter takes precedence.

DATA DELIVERY DATES

For Soft Copies, delivery of data is to be construed as the date data is available in the contractors’ data management system and electronic notification is sent to addressees.

For Hard Copies, delivery of data is to be construed as “On Dock” dates at destination. Provision of a 3-day postage handling period from postmark at contractor's facility to “On Dock” delivery at destination meets this requirement, unless otherwise stated in CDRL. The date of government signature at destination, if courier service is used, is to be construed as the “On Dock” date. It shall be the contractor's responsibility to ensure data delivery prior to end of business on the due date if a courier service is used in lieu of the United States (U.S.) Postal Service.

If due date falls on weekend or government holiday, data shall be due on the next scheduled government workday.

DD FORM 250 REQUIREMENTS

Block 7 of the CDRL will indicate whether inspection and acceptance of the data by DD Form 250 is required.

“Draft” copies submitted for advance approval and “Preliminary” copies submitted are exempt from the DD Form 250 requirements.

ADDITIONS TO DISTRIBUTION

If an addressee is added to distribution, or distribution quantities have been increased to an existing addressee, initial submittal to new addressee shall include the basic document and revisions as appropriate.

COMMUNICATIONS

Any correspondence related to requests for data delivery deviations, amendments, additions, or deletions shall be addressed to the Procurement Contracting Office (PCO) with an information copy to the government Data Management Officer (DMO).

For those data items where “LT” (Letter of Transmittal) is indicated in Block 7 of the CDRL, the Contractor shall utilize a Letter of Transmittal (LOT). Each copy submitted shall have an LOT attached. In addition, the contractor shall furnish one copy of each LOT (without data) to the government DMO. Change pages shall indicate updates by a bar in the margin adjacent to the change and encompassing all changed portions.

CDRL ADDRESS LIST AND DATA DISTRIBUTION LIST

The Address List provides the complete mailing address for each addressee and a mailing code.

The Data Distribution List provides information regarding quantities for shipment (normally in Blocks 14 and 15 of the CDRL) to each mailing code. Quantity of Hard deliverables and Soft deliverables will be indicated to the left and right of the “/,” respectively. See CDRL for possible additional format or delivery instructions.

DATA APPROVALS

While all data are subject to government approval, selected data will require advanced approval. Per Block 8 in the CDRL instructions, deliverables are either marked as “N/A” to denote that approval is not required or “A” to denote that approval is required by the Government. Data requiring approval “A” will be reviewed as follows. Initial or draft CDRL submittals shall be reviewed by the Government to transmit feedback to the Contractor as required and will not require government approval. Updates to “A” CDRLs will also be reviewed by the Government to transmit feedback to the Contractor as required; the government may determine that these updates require approval as directed by the PCO. All final data submissions for “A” CDRLs shall require approval by the Government. The approving authority shall be the PCO. Approval indicates agreement or concurrence with the contractor’s furnished data only and shall not be construed as changing any of the terms or conditions of the subject contract. Unless otherwise indicated in the specific CDRL item, the government approval cycle will not be more than thirty (30) CD. The contractor will be notified should the government require additional time. The Contractual Documentation Action (CDA) form, or Contracting Officer’s Letter, is used to document the Government’s position in regard to the approval status of the contractor submitted CDRL item(s). Non-response by the Government to a contractor’s request for approval of a data item is not to be construed as tacit approval of said item.

CODES USED ON THE CDRL

The following codes may be used as described below.

a. Block 7: DD Form 250 requirements

CODE WHEN USED

LT Letter of Transmittal only

b. Block 8: Approval code

CODE WHEN USED

A Approval is required by the government.

N/A Approval is not required.

c. Block 10: Frequency

CODE (Limit to five characters)

DAILY Daily WEKLY Weekly BI-WE Each 2 weeks MTHLY Monthly BI-MO Each 2 months QRTLY Quarterly ANNLY Annually SEMIA Each 6 months OTIME One time ONE/R One time and revisions R/ASR Revisions as required *ASREQ As required DFDEL Deferred delivery DFORD Deferred ordering ONE/P One-time preliminary draft 2TIME Two separate submittals

*When ASREQ is used in items 10, 11, 12, or 13, an explanation of the requirement must be entered in item 16.

d. Blocks 12 and 13: Date of First and subsequent submissions

SDA = Government APPROVAL CDR = Critical Design Review CA = Contract Award IPR = In Process Review CO = Change Order FCA = Functional Configuration Audit SA = Supplemental Agreement PCA = Physical Configuration Audit SRR = System Requirements Review FLT = Flight Test Review SDR = System Design Review CD = Calendar Days PDR = Preliminary Design Review WD = Working Days EOC = End of Contract ATP = Authority to Proceed ILC = Initial Launch DACA = Days After Contract Award*

* For this agreement, Contract Award is the same as Launch Vehicle Services Order

ELECTRONIC DISTRIBUTION

CDRL shall be delivered on the contractors’ data management system(s). The contractor shall enable remote access to these systems by all SPO personnel (Air Force [AF], Aerospace, Systems Engineering and Integration [SE&I], and Advisory and Assistance Services [A&AS]) subject to applicable terms on this contract. An index of addressees to be allowed access to or to be notified of CDRL availability will be provided by government DMO via e-mail notification for contractor’s implementation. Access Lists will be updated, as required, without modification to the contract. The contractor shall use an acceptable electronic format that is compatible with existing government systems, unless a precise format is specified in the CDRL.

CDRL ADDRESS LIST

1. HQ Space & Missile Systems Center (AFSPC) LE

Attn: Launch Systems Directorate 483 North Aviation Blvd.

Los Angeles AFB El Segundo, CA 90245-2808 smc.lrdm@us.af.mil

a. LEE, Bldg. 271 B3-405 (DMO)

b. LEE

c. LEP

d. LEK

e. LEG

f. LEM

NOTE: Submit Hard Copies to 1.a. for distribution, if applicable

2. HQ Space & Missile Systems Center (AFSPC) SAF/SL Attn: SAF/SL, Bldg. A5 483 North Aviation Blvd.

Los Angeles AFB El Segundo, CA 90245-2808

3. 30th Launch Group 30 LCG 4th Space Launch Squadron Directorate of Engineering Attn: Data Desk 1515 Iceland Ave., Suite 222 Bldg. 8500 Vandenberg AFB, CA 93437-5321

4. 45 LCG/45 LCSS 45 LCG

Attn: Data Library 15270 Samuel C. Phillips Parkway (CCAFS) Building 1645 Patrick AFB, FL 32925-2009

5. Defense Cost and Resource Center (DCARC) DCARC 201 12th Street South Suite 220 Arlington, VA 22202

(703) 601-4850

6. Defense Contract Management Agency (DCMA) DCMA

TBD

7. NRO Operations Squadron NOPS

401 Discoverer Ave. Ste 32 Schriever AFB, CO 80912 NOPS_Launch@us.af.mil mailto:NOPS_Launch@us.af.mil

CDRL DISTRIBUTION LIST

CDRL TITLE OFFICE

SYMBOL

QTY

Hard/Soft

CX01 Test Facility Requirements Documents SAF/SL 0/1

** For NRO Missions ^ For Launches from Vandenberg Air Force Base (VAFB) ^^ For Launches from Cape Canaveral Air Force Station (CCAFS) or Kennedy Space Center (KSC)

NOTES: (1) The contractor shall provide electronic access of CDRLs, and notification via e-mail to select addressees, when requested, in accordance with government-provided Access List index. Addressees (for notification purposes only) not listed above may include, for example, Aerospace, DCMA, Patrick AFB, VAFB, SE&I, and A&AS contractors. It is not the responsibility of the Contractor to make actual distribution of either electronic or hard copy CDRLs to these unnamed addressees. Draft documents delivered electronically must be marked “draft.” Notifications for Revisions to required CDRL deliveries shall be provided to all points of contact.

(2) LCG = Launch Group, LEE = Launch Enterprise Engineering Division, LEG = Launch Enterprise Generation and Ops Division, LEM = Launch Enterprise Procurement Division, NOPS = National Reconnaissance Office Operations Squadron, SAF/SL = Secretary of the Air Force, Space Launch

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

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 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:

X003 A X TDP TM OTHER

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

EELV FA8811-18-R-0001

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

CX01 Test Facility Requirements Documents Facility Requirements Document (FRD)

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

DI-FACR-80810A Performance Work Statement, Para 3.4.8.3.4 SAF/SL

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT BLK 16 BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4)

a. Replace 3.1 with “The FRD identifies all of the Contractor’s constraints and requirement for the use of the Payload Processing Facility. These requirements describe the facilities and services necessary to perform Payload Fairing (PLF) offload, PLF cleaning, pre-mate preparations, spacecraft mate to Payload Attach System (PAS), encapsulation, and post-encapsulation preparations for transport to the launch pad by the Contractor. The requirements do not address facilities related to spacecraft processing.”

b. Delete 7.2 and 7.3

c. Replace 10. With:

“10.2 Content. The document shall include the following information:

10.2.1 General requirements to include any requirements for administrative areas as well as any communications requirement needed by the Contractor in order to operate in the PPF.

10.2.2 Hardware Arrival – Description of the general overview of operations and the required facility and service requirements

10.2.3 Flight Hardware Processing Prior to Encapsulation - Description of the general overview of operations and the required facility and service requirements

10.2.4 Integrated Operations and Encapsulation - Description of the general overview of operations and the required facility and service requirements

10.2.5 Transportation Preparation - Description of the general overview of operations and the required facility and service requirements”

2. (BLKs 10, 12, and 13)

a. Submit initial draft by L-18 months.

b. Submit final by L-12 months.

15. TOTAL

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

Electronically Generated PAGE 1 OF 1 PAGES

31 Jan 201831 Jan 2018