02a_CDRLs_Exhibit_AX_Signed.pdf

EXHIBIT AA, AB, AC, AD AND AE

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 A ORGANIZATION

Mission Title Exhibit Section

NROL-85 AA

NROL-87 AB

SILENTBARKER AC

SBIRS GEO-5 AD

AFSPC-44 AE

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 (DoD) Form (DD Form) 1423s, Contract Data Requirements List (CDRL), which specifies the data which is required 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 Contract is awarded multiple Launch Vehicle Service orders, the Contractor shall use a sequential double alpha, single numeric number scheme. For example, Order 1 will have CDRLs AAX1-AA11, AB01-AB20, and AC01; and Order 2 will have CDRLs BAX1-BA11, BB01-BB20, and BC01.

DATA ITEM DESCRIPTIONS (DID)

The DID is a specification for the preparation of data. The DID listed on the CDRL were selected from the 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 by-product 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 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 and “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

CDRLs shall be delivered on the contractors’ data management system(s). The contractor shall enable remote access to these systems by Government personnel (Air Force, Defense Contract Management Agency [DCMA], Aerospace, Systems Engineering and Integration [SE&I], and Systems Engineering and Technical Assistance [SETA]) 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. LES 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

CDRL DISTRIBUTION LIST

CDRL TITLE OFFICE

SYMBOL

QTY

Hard/Soft

AX01 Data Accession List (DAL) LEE 0/1

AX02 “Cost Data Summary Report” (DD Form 1921)

LEP

DCARC

SAF/SL**

0/1 0/1

AX03 “Functional Cost-Hour Report” (DD Form 1921-1)

LEP

DCARC

SAF/SL**

0/1 0/1

AX04 Contractor Business Data Report (DD Form 1921-3)

LEP

DCARC

SAF/SL**

0/1 0/1

AX05 Contract Work Breakdown Structure (CWBS)

LEP

DCARC

DCMA

SAF/SL**

0/1 0/1 0/1

AX06 Integrated Program Management Report (IPMR) - Integrated Master Schedule (IMS)

DCARC

LEP

SAF/SL**

0/1 0/1 0/1

AX07 Training Materials - Launch Vehicle Familiarization Training

LEG

SAF/SL

30 LCG^

45 LCG^^

0/1 0/1 0/1 0/1

AX08 Program Protection Implementation Plan (PPIP) LEE

SAF/SL**

0/1 0/1

AX09 As Designed Configuration List (ADCL) - Launch Vehicle Configuration

LEE

LEG

SAF/SL**

0/1 0/1 0/1

AX10 Test Plan - Launch Vehicle Test and Verification Plan

(LVTVP)

LEG

LEE

SAF/SL**

0/1 0/1 0/1

AX11 Test Procedure - Flight Hardware Interface Checks LEG

SAF/SL**

0/1 0/1

AX12 As-Built Configuration List (ABCL) LEE

SAF/SL**

0/1 0/1

AX13 As-Built Configuration List (ABCL) for Fleet Insight LEE

SAF/SL**

0/1 0/1

AX14 Small Business Utilization Report LEM 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, Defense Contract Management Agency (DCMA), Patrick Air Force Base (AFB), Vandenberg AFB, SE&I, and SETA 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 POCs.

(2) DCARC = Defense Cost and Resource Center, DCMA = Defense Contract Management Agency, DD Form = Department of Defense Form, LCG = Launch Group, LEE = Launch Enterprise Engineering Division, LEG = Launch Enterprise Generation and Ops Division, SAF = Secretary of the Air Force, SL = 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:

X001 A TDP TM OTHER X

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

AX01 Data Accession List (DAL)

4. AUTHORITY (Data Acquisition Document No.)

5. CONTRACT REFERENCE 6. REQUIRING OFFICE

DI-MGMT-81453A/T Performance Work Statement, Para 3.1.3 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT MTHLY 30 DACA b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A N/A MTHLY Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Data Accession List (DAL) shall be cumulative.

b. The DAL List should not include data generated by other CDRLs on contract.

c. The DAL shall contain pointers (links) to the contractor’s electronic data system’s file names or document location in the online database.

2. (BLK 13): Technical data shall be added to the online dataset within 10 working days after release

3. The Government will review each submission and provide feedback within 15 calendar days to the maximum extent possible.

15. TOTAL 1

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

31 Jan 2018 31 Jan 2018

Electronically Generated PAGE 1 OF 1 PAGES

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

X001 A TDP TM OTHER X

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

AX02 Cost Data Summary Report (DD Form 1921)

DI-FNCL-81565C/T Performance Work Statement, Para 3.1.4 SMC/LEP

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 BLK 16 BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the Cost Analysis Improvement Group Chair-approved Cost and Software Reporting (CSDR) Plan provision, the Work Breakdown Structure (WBS) Data Dictionary, and the Contract Cost Data Reporting (CCDR) Manual (Department of Defense

5000.4 M-1). Use the latest revisions of the CSDR Plan and the WBS Dictionary. The CCDR Manual is available from the Defense Cost and Resource Center (DCARC) website at http://dcarc.cape.osd.mil/

b. The responsible DoD office for receiving and storing all CCDR-related formats is:

DCARC

201 12th Street South

Suite 220

Arlington, VA 22202

c. Prepare CCDR data in electronic format in accordance with the detailed instructions contained in Data Item Description DI-FNCL-81565C. The required file format is Microsoft Excel-compatible spreadsheet. PDF format is not acceptable. These reports must be submitted by report upload to the DCARC’s secure website. The DCARC website contains information about delivery methods and submission instructions.

d. Prime contractors are responsible for flowing down CCDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds. This includes requiring subcontractors to electronically report directly to DCARC and Space and Missile Systems Center/Launch Enterprise Program Control (SMC/LEP). If the subcontractor agrees, a copy of the report may be provided concurrently to the prime or higher tier contractor.

e. Contractor shall identify major subcontractor names, values, and corresponding WBS elements in the remarks sections of the DD Form 1921.

2. (BLK 10, 11, 12 & 13): Please reference the latest approved CSDR Plan provided by DCARC for current submission events and due dates.

3. The Government will review each submission and provide feedback within 30 calendar days to the maximum extent possible.

15. TOTAL

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

COST AND SOFTWARE DATA REPORTING PLAN Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 8 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 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 COMPLETED FORM TO THE ABOVE ORGANIZATION.

1. MAJOR

PROGRAM

a. NAME: EELV - Evolved Expendable Launch Vehicle

b. PHASE/MILESTONE c. PRIME MISSION

PRODUCT

2. WBS SYSTEM

TYPE

3.

SUBMISSIO

N TYPE

4. CURRENT

SUBMISSION

DATE

(YYYYMMDD

5. LAST

APPROVED PLAN

DATE

(YYYYMMDD) Pre-A B X C-FRP Launch Vehicle System Launch Vehicle

System

X INITIAL

A C-LRIP O&S CHANG

E

6a. POINT OF CONTACT (POC) NAME AND ADDRESS (Include ZIP Code)

6b. TELEPHONE NUMBER (Include

Area Code)

6c. FAX NUMBER (Include Area Code)

6d. E-MAIL ADDRESS

SMC/LEP Cost Chief 483 N. Aviation Blvd

Los Angeles AFB El Segundo, CA 90245

310-653-4715 310-653-3151 roy.bryson@us.af.mil

7. PLAN TYPE 8. PREPARING

ORGANIZATI

ON

9a. CONTRACTOR

NAME/ADDRESS

9b. CONTRACT

NUMBER

9c.

APPROPRIATION

10. APPROVED

PLAN NUMBER

PROGRAM X CONTRACT

(PRIME)

i.

PERFORMING

ORGANIZATI

ON

ii. DIVISION FA811-16-R-0007 RDT&E AF-15-K-C3

CONTRACT

(SUB)

AF SMC/LE

Program Control

TBD TBD X PROCUREME

NT

O&M

11. WBS ELEMENT CODE 12. WBS REPORTING ELEMENTS 13. REPORTS REQUIRED

(X if applicable)

DD 1921-3

(CBDR): X

a. PROGRAM/

CONTRACT/

SUBCONTRA

CT

b.

CONTRACT/

SUBCONTRA

CT

a. CWBS

DICTIONA

RY

b. DD

(CDSR

c. DD 1921-

(FCHR)

d. DD 1921-2

(PCR)

e. DD 1921-4

(CSR)

f. SRDR

FORMA

TS

1.0 1.0 Launch Vehicle System X X X

1.1 1.1 Mission Integration X X

1.1.1 1.1.1 Mission Standard Integration X X

1.1.2 1.1.2 Mission Unique Integration X X

1.2 1.2 Mission Assurance X X X

1.3 1.3 Supplier Readiness X X

1.4 1.4 Mission Unique Development/Design X X

1.5 1.5 System Engineering, Integration, Test, Program Management

X X X

1.5.1 1.5.1 Program Management X X X

1.5.2 1.5.2 System Engineering X X X

1.5.3 1.5.3 Factory Support X X X

1.5.4 1.5.4 Special Studies X X X

1.6 1.6 Transportation X X

1.7 1.7 Launch Operations X X X

1.7.1 1.7.1 Launch Support X X X

1.7.1.1 1.7.1.1 Launch Crew (mate, checkout, launch) X X

1.7.1.2 1.7.1.2 P/L Encapsulation X X

1.7.2 1.7.2 Launch Operations Systems Engineering and Program Management (SEPM)

X X X

1.7.2.1 1.7.2.1 Launch Operations Program Management X X X

1.7.2.2 1.7.2.2 Launch Operations System Engineering X X X

1.7.3 1.7.3 Site Maintenance X X X

1.7.3.1 1.7.3.1 Sustainment Propellants X X

1.7.3.2 1.7.3.2 Other Maintenance X X

1.7.4 1.7.4 Base Support X X X

1.7.5 1.7.5 Range Operations Services X X X

1.7.6 1.7.6 Propellants (Vehicle) X X X

1.8 1.8 Launch Vehicle X X X

1.8.1 1.8.1 Propulsion X X X

1.8.1.1 1.8.1.1 Booster Engine X X X

1.8.1.2 1.8.1.2 Upper Stage Engine X X X

1.8.1.3 1.8.1.3 Solid Rocket Motors X X X

1.8.2 1.8.2 Payload Accommodations X X

1.8.2.1 1.8.2.1 Payload Fairing X X X

1.8.2.2 1.8.2.2 Payload Attach Fitting (Adapter) X X X

1.8.2.3 1.8.2.3 Mission Unique Hardware X X X

1.8.3 1.8.3 Core Vehicle X X X

1.8.3.1 1.8.3.1 Booster Structure X X X

1.8.3.2 1.8.3.2 Intertank Adapter & Skirts X X X

1.8.3.3 1.8.3.3 Aft Transition Structure X X X

1.8.3.4 1.8.3.4 Heat Shield X X X

1.8.4 1.8.4 Upper Stage X X X

1.8.4.1 1.8.4.1 Upper Stage Structure X X X

1.8.4.2 1.8.4.2 Interstage Adapters, Stub Adapters, Forward Adapters

X X X

1.8.5 1.8.5 Mission Assurance Instrumentation X X X

1.8.6 1.8.6 Guidance and Control (Avionics) X X X

1.8.7 1.8.7 Integration, Assembly, Test, and Checkout ( X X X

1.9 1.9 Training X X

1.10 1.10 Other X X

Subtotal Cost X

Reporting Contractor General and Administrative X

Reporting Contractor Undistributed Budget X

Reporting Contractor Management Reserve X

Reporting Contractor FCCM X

Total Cost X

Reporting Contractor Profit/Loss or Fee X

Total Price X

DD FORM 2794, MAY 2011 PREVIOUS

EDITION IS

OBSOLETE

14. CSDR SUBMISSION DATES

a.

SUBMISSION

b.

FORM(S)

c.

EVENT

d. AS OF

DATE

e. DUE DATE

(YYYYMMDD

(YYYYMMDD

1 Contract Work Breakdown Structure (CWBS) Dictionary

Initial CWBS Submission

2 1921, 1921-1 Initial Report - Initial Cost Report

3 1921, 1921-1 Final Cost Report

15. REMARKS

NON-RECURRING/RECURRING DEFINITIONS:

There are no refinements or expansions to these definitions warranted.

COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT DIFFERENCES:

Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable.

1921-3 CONTRACTOR BUSINESS DATA REPORT:

a. The Contractor Business Data Report is prepared by and for the business entity (e,g., business unit, segment, or site) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government, if applicable.

b. Reports are submitted annually at the end of the contractor's fiscal year.

c. An alternative to completing 1921-3 is complete Blocks 1 through 11, on Page 1 (Sections A - F are not required) and REMARKS section must include "Headcount by Department" on a monthly basis.

SPECIAL INSTRUCTIONS: (1) Only provide an initial report (which will only have initial at completion estimates), end of year reports as applicable and a final report (when actual costs are known) given the period of performance for the contract.

(2) On the 1921-1s for 1.2 (Mission Assurance), 1.5 (System, Engineering, Integration, Test, Program Management), and 1.7 (Launch Operations), describe in detail the mapping or allocation approach. If an allocation approach is used, use the 1921-1 Non-Recurring category to either identify the enterprise's total (common) costs and hours for the period in that specific WBS element or provide the total company headcount on a monthly basis for the departments utilized in the performance of

1.2 (Mission Assurance), 1.5 (System, Engineering, Integration, Test, Program Management), and 1.7 (Launch Operations). (This total enterprise (common) cost will NOT be included in the cost of this launch) and the 1921-1 Recurring category to list the costs and hours attributed to this specific mission (common share and unique) for the period in that specific WBS element. Alternatively, provide the data and document the mapping/allocation procedure in a supplemental excel table or other suitable format.

(3) Use the notes section in the form(s) to document your assumptions, allocations, mappings, etc.

(4) For WBS 1.10 "Other" category, specifically define what these costs are in Remarks' section.

DD FORM 2794 (PAGE 2), MAY 2011 PREVIOUS EDITION IS OBSOLETE

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

X001 A TDP TM OTHER X

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

AX03 Functional Cost-Hour Report (DD Form 1921-1)

DI-FNCL-81566C/T Performance Work Statement, Para 3.1.4 SMC/LEP

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 BLK 16 BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the Cost Analysis Improvement Group Chair-approved Cost and Software Reporting (CSDR) Plan provision, the Work Breakdown Structure (WBS) Data Dictionary, and the Contract Cost Data Reporting (CCDR) Manual (Department of Defense

5000.4 M-1). Use the latest revisions of the CSDR Plan and the WBS Dictionary. The CCDR Manual is available from the Defense Cost and resource Center (DCARC) website at http://dcarc.cape.osd.mil/

b. The responsible DoD office for receiving and storing all CCDR related formats is:

DCARC

201 12th Street South

Suite 220

Arlington, VA 22202

c. Prepare CCDR data in electronic format in accordance with the detailed instructions contained in Data Item Description DI-FNCL-81566C. The required file format is Microsoft Excel-compatible spreadsheet. PDF format is not acceptable. These reports must be submitted by report upload to the DCARC’s secure website. The DCARC website contains information about delivery methods and submission instructions.

d. Prime contractors are responsible for flowing down CCDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds. This includes requiring subcontractors to electronically report directly to DCARC and Space and Missile Systems Center/Launch Enterprise Program Control (LEP). If the subcontractor agrees, a copy of the report may be provided concurrently to the prime or higher-tier contractor.

e. Contractor shall identify major subcontractor names, values, and corresponding WBS elements in the remarks sections of the Department of Defense Form 1921.

2. (BLK 10, 11, 12 & 13): Please reference the latest approved CSDR Plan provided by DCARC for current submission events and due dates.

3. The Government will review each submission and provide feedback within 30 calendar days to the maximum extent possible.

15. TOTAL 1

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

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

X001 A TDP TM OTHER X

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

EELV

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

AX04 Contractor Business Data Report (DD Form 1921-3)

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

DI-FNCL-81765B/T Performance Work Statement, Para 3.1.4 SMC/LEP

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 BLK 16 BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. A(BLK 4):

a. Prepare in accordance with the Cost Analysis Improvement Group Chair-approved Cost and Software Reporting (CSDR) Plan provision, the Work Breakdown Structure Data Dictionary, and the Contract Cost Data Reporting (CCDR) Manual (Department of Defense 5000.4 M-1). Use the latest revisions of the CSDR Plan and the WBS Dictionary. The CCDR Manual is available from the Defense Cost and Resource Center (DCARC) website at http://dcarc.cape.osd.mil/

b. The responsible DoD office for receiving and storing all CCDR related formats is:

DCARC

201 12th Street South

Suite 220

Arlington, VA 22202

c. Prepare Contractor Business Data Report data in electronic format in accordance with the detailed instructions contained in Data Item Description DI-FNCL-81765B. The required file format is Microsoft Excel-compatible spreadsheet. PDF format is not acceptable. These reports must be submitted by report upload to the DCARC’s secure website. The DCARC website contains information about delivery methods and submission instructions.

d. Prime contractors are responsible for flowing down CCDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds. This includes requiring subcontractors to electronically report directly to DCARC and Space and Missile Systems Center/Launch Enterprise Program Control (LEP). If the subcontractor agrees, a copy of the report may be provided concurrently to the prime or higher tier contractor.

e. Contractor shall identify major subcontractor names, values, and corresponding WBS elements in the remarks sections of the Department of Defense Form 1921.

2. (BLK 10, 11, 12 & 13): Please reference the latest approved CSDR Plan provided by DCARC for current submission events and due dates.

3. The Government will review each submission and provide feedback within 30 calendar days to the maximum extent possible.

15. TOTAL

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

31 Jan 2018 31 Jan 2018

FA8811-18-R-0001

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

X001 A TDP TM OTHER X

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

AX05 Contractor Work Breakdown Structure (CWBS)

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

DI-MGMT-81334D/T Performance Work Statement, Para 3.1.4 SMC/LEP

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 BLK 16 BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the Contract Cost Data Reporting (CCDR) Manual (Department of Defense 5000.4-M-1) and the guidance in Military Standard 881C, “Work Breakdown Structures for Defense Material Items,” Appendix J (T), “Launch Vehicle Systems work Breakdown Structure and Definitions.” The CCDR Manual is available at the Defense Cost and Resource Center (DCARC) website http://dcarc.cape.osd.mil/

b. The responsible DoD office for receiving and storing all CCDR related formats is:

DCARC

201 12th Street South

Suite 220

Arlington, VA 22202

c. Prepare CCDR data in electronic format in accordance with the detailed instructions contained in Data Item Description DI-MGMT-81334D. The required file format is Microsoft Excel-compatible spreadsheet. PDF format is not acceptable. Microsoft Word is an acceptable format for submission of the Contract Work Breakdown Structure (CWBS) Dictionary. These reports must be submitted by report upload to the DCARC’s secure website. The DCARC website contains information about delivery methods and submission instructions.

d. Prime contractors are responsible for flowing down CCDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds. This includes requiring subcontractors to electronically report directly to DCARC and Space and Missile Systems Center/Launch Enterprise Program Control (LEP).

e. The CWBS shall include up to Level 4 of indenture. Contractor shall provide reporting for Levels 1 through 4 of the Program WBS. Any differences between the CWBS and Program WBS shall be identified.

2. (BLK 10, 11, 12 & 13):

a. CWBS and CWBS Dictionary date of first submission is 30 calendar days (CD) after Contract Award for this data item addition.

b. Subsequent submissions 30 CD after Fiscal Year end (Sep 30).

c. Please reference the latest approved CSDR plan provided by DCARC for current submission events and due dates.

d. Any redlines to the CWBS dictionary after first submittal shall be provided to Space and Missile Systems Center/Launch Enterprise Program Control (LEP) monthly for Government review and DCARC coordination. 15. TOTAL

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

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

X001 A TDP TM OTHER X

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

AX06 Integrated Program Management Report (IPMR) Integrated Master Schedule

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

DI-MGMT-81861A/T Performance Work Statement, Para 3.1.4 SMC/LEP

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT MTHLY BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A BLK 16 BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Only the following Data Item Descriptions sections and their sub-sections (omitting references to Formats 1–5 or 7) are applicable: 1.3, 1.5, 2.1.1, 2.1.1.2, 2.2.5, 2.3, 2.5.1, 2.6.1, 2.7, 3.6.7, and

3.7 as tailored below; and exclude 6.2.1.1.6.

b. 2.1.1 Electronic Submission of Data Add the following: The Integrated Master Schedule (IMS) shall be submitted electronically using the contractor’s schedule tool and only in a PDF file format when specifically requested by the Government.

c. 2.2.5 Native Schedule Format Add the following: The IMS shall be created using a network-capable scheduling software application of the contractor’s choice. The IMS shall be configured to allow sorting and filtering by key events and to allow filtering for various views; for example, top-level summary view, mid-level summary view, critical path for each mission, and a complete detail view.

d. 2.6.1 Submission Requirements. Replace with: Format 6 shall be submitted to the procuring activity no later than 14 federal working days (WD) after contractor’s month end close.

e. 3.6.7.1 Critical/Driving Paths Delete all references to Driving Paths in the title and body of the requirement.

f. 3.7.1 IMS Requirements Delete all references to the Integrated Master Plan (IMP). An IMP is not required.

g. 3.7.1.1.1 Production Contract IMS Add the following: Production key events/milestones shall be incorporated at the summary level and networked to their associated activities within the IMS.

The interrelationships/interdependencies shall be identified with sufficient detailed activities through the use of network logic that provide a clear picture of the mission’s progress from Authority to Proceed (ATP) through contract completion.

h. 3.7.1.3 IMS Content Elements Second bullet – Replace with: The IMS shall have traceability to WBS and Performance Work Statement. The IMS shall include Mission Integration Schedule (MIS) requirements as specified in the PWS Paragraph 3.4.3.1 and Sub Paragraphs.

i. 3.7.1.3.4.3 Scope Planning Add the following: Planning packages shall be detailed and planned into discrete work packages, or apportioned tasks (as appropriate) no later than one accounting period prior to the schedule start of the planning package. Planning package plans shall reflect the manner in which the work is to be performed.

j. 3.7.1.3.5.3 Duration Add the following: Discrete/measureable activities shall be baselined in accordance with the contractor’s System Description Document (as applicable). Where durations are longer than 44 WD, rationale shall be provided within the IMS.

15. TOTAL

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

Electronically Generated PAGE 1 OF 2 PAGES

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

X001 A TDP X TM OTHER

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

EELV FA8811-18-R-0001

16. REMARKS

k. 3.7.1.3.5.8 Driving Path – Delete

l. 3.7.1.3.5.9 Critical Path Add the following: Each mission’s critical path shall show clear network logic through the launch operation schedule of activities. The launch operations data shall be provided to the Government using existing contractor schedule and format on a monthly basis. At the mission level, the critical path follows the standard definition (a critical path being the longest continuous path through the network) flow from mission Authority to Proceed (ATP) through launch, providing a clear network of logic of all tasks along the critical path. As a mission progresses, the critical path shall also include activities that have negative float. Where critical path is not calculated based on the longest path, but based on risk and development of known delivery problems, the critical path shall explain the deviation from the standard derived critical path.

m. 3.7.1.3.5.10 Current Schedule Add the following: Reporting thresholds shall be consistent with the Defense Contract Management Agency (DCMA) 14 Point Assessment metrics version 3.2.0.

n. 3.7.1.3.5.15 External Dependencies Add the following: A network schedule for each mission shall clearly identify activities, product hand-offs, and deliverables from external interfaces, from the lowest level of contract tasks and activities up to the summary-level schedule activities and milestones. The determination of external significant and critical interfaces to be identified within the Integrated Master Schedule (IMS) requires agreement among the contractor(s) and Government and is documented accordingly.

o. Delete 3.7.1.3.6 Schedule Risk Assessment (SRA)

p. Delete 3.7.1.3.6.1–3.7.1.3.6.5

q. 3.7.1.3.7.2 Required traceability – Replace with: The Work Breakdown Structure (WBS) must be traceable for all discrete work in the IMS. Traceability may be met with a field in the IMS or via other means as long as discrete work reconciles.

r. Delete 3.7.1.3.7.3 Item 4) Earned Value Technique (EVT), Item 6) Critical Paths and Driving Paths. Delete all references to Driving Paths in the title and body of the requirement.

s. 3.7.1.3.9 Retention of Historical Performance – Remove “and the three-point estimates that were used before the task/activity started.”

t. 3.7.2.1 Schedule Visibility Task (SVT) – Deleted.

2. (BLK 11) The contractor’s month end close.

3. (BLK 12) The proposed IMS, in response to the RFP, shall be the first submission. An updated IMS shall be provided 30 days after contract award for Government approval.

4. (BLK 13) Electronic copy shall be submitted no later than 14 federal working days after contractor’s month end close.

5. (BLK 14) All IMS related forms must be electronically submitted to the central repository at the DCARC website at https://service.dcarc.cape.osd.mil/DCARCPortal/site/login.asox

6. The Government will review each submission and provide feedback within 15 calendar days to the maximum extent possible.

Electronically Generated PAGE 2 OF 2 PAGES https://service.dcarc.cape.osd.mil/DCARCPortal/site/login.asox

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

X001 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

AX07 Training Materials Launch System Familiarization Course

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

DI-ILSS-80872/T Performance Work Statement, Para 3.1.10 SMC/LEG

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT ASREQ 60 DACA b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Replace 10.1 with “10.1 Format. The material provided shall be in the contractor’s own format.

The material shall be printable on standard size paper, e.g., 8 ½ x 11 or A4; foldouts are allowed.”

b. Delete 10.1.1

c. Replace 10.2 with “10.2 Contents. The Launch System Familiarization Course training materials shall consist of text, supplemental written and audio-visual material used to support the Launch Vehicle Familiarization class.”

d. Replace 10.2.1 with

“10.2.1 The Launch System hardware, software, and ground interface sections shall include the following elements:

A. Overall review of hardware or software element function and construction

B. Basic performance requirements and interfaces

C. Qualification approach

D. Fault tolerance

E. Test questions for the student

F. Change summary showing changes to the material between versions”

e. Delete 10.2.1.1–10.2.1.7

f. Replace 10.2.2 with

“10.2.2 Required Material. The Launch System Familiarization Course training materials shall address the following elements (as appropriate for the Launch Service provided):

1. Launch System Hardware and Software

a. Booster

i. Structure

1. Propellant Tanks

2. Primary Transition Structure

3. Heat Shields

15. TOTAL

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

Electronically Generated PAGE 1 OF 3 PAGES

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

X001 A X TDP TM OTHER

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

EELV FA8811-18-R-0001

16. REMARKS

4. Propellant Feed Subsystems

5. Avionics Structure

6. Fairings

ii. Booster Systems

1. Booster Tank Pressurization

2. Propellant Level Control Systems

3. Propellant Utilization System

4. Propellant Depletion System

5. Retro-Rockets

6. Separation and Ordnance Systems

iii. Booster Propulsion

1. Main engine

2. Main engine hydraulics

iv. Solid Rocket Boosters (SRB) Propulsion

1. Solid Rocket Booster

2. Strap-On Attach Hardware

3. Configuration Control Board/SRB Umbilicals

b. Upper Stage

i. Structure

1. Tanks

2. Avionics Panels

ii. Upper Stage System

1. Propellant Level System

2. Propellant Utilization System

3. Pressurization and Venting System

4. Helium System

5. Reaction Control Thrusters

iii. Upper Stage Engine

c. Payload Fairings and Payload Adapters

d. Avionics and Electrical Systems

i. Electrical Power Subsystem (EPS)

ii. Guidance, Navigation, and Control (GNC) Subsystem

1. Navigation Unit

2. Flight Software

3. Remote Command and Control Units

iii. Ordnance Control Units

iv. Batteries

v. Data Acquisition System (DAS) Telemetry Data Transmission System (TDTS)

vi. Tracking System

vii. Flight Termination System (FTS)

e. Rideshare Capabilities

Electronically Generated PAGE 2 OF 3 PAGES

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

X001 A X TDP TM OTHER

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

EELV FA8811-18-R-0001

16. REMARKS

2. Ground Systems

a. Ground Command, Control Communications

b. Launch Mount and Umbilical System

c. Range Interface

d. Facility systems and capabilities

e. Launch site critical ground mechanical, structural, and fluid/gas systems

f. Ground electrical systems

3. Launch Vehicle Processing

a. Manufacturing Facility

b. Factory Checkout and Test

c. Transportation

d. Receive and Inspection, Checkout and Test

e. Integrated Systems Test

f. Payload processing and Integration

g. Launch Vehicle and Facility Walkdown process

h. Launch Countdown and Launch

4. Launch Vehicle System and Systems Engineering

a. Mission Profiles and Vehicle Capability

b. Requirements and Verification

c. Standard analyses performed by all disciplines during each mission integration cycle

i. Analysis Scope

ii. Tools Utilized

d. Risk Identification, Tracking, and Resolution criteria/process

e. Types of Contractor Work Authorization Documents

5. Contractor organizational structure, roles and responsibilities”

2. (BLKs 12): The Contractor shall provide a self-study guide report to accompany the training course consisting of the training materials, test questions, and answers.

Initial submittal (draft) training materials shall be delivered no later 60 days after contract award. The level of detail covered by the Familiarization (flight) (FAM) Course training materials shall be provided by the Contractor in the initial submittal and approved by the Government for the final contract data requirements list submittal prior to conducting the FAM Course. Final training materials shall be delivered 15 calendar days (CD) following receipt of Government comments. All FAM Course training materials shall be finalized and approved by the Government prior to the FAM Course.

3. (BLKs 13): Updates to the written training materials shall be submitted to reflect the latest United States Government certified/approved launch system configuration.

4. The Government will review each submission and provide feedback within 30 CD to the maximum extent possible.

Electronically Generated PAGE 3 OF 3 PAGES

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

X001 A TDP X 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

AX08 Program Protection Implementation Plan (PPIP)

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

DI-ADMN-81306 Performance Work Statement, Para 3.1.11 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT ASREQ 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…