02a_Exhibit_A_CDRL_30_Sep_2015.pdf

EXHIBIT A

TO

FA8811-15-R-0001

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PHASE 1A

CONTRACT DATA REQUIREMENTS LIST (CDRLs)

30 September 2015

Department of the Air Force

Space and Missile Systems Center

Launch and Range Systems Directorate

Los Angeles Air Force Base, California

CDRL General Instructions

CDRL Address List

CDRL Distribution List

CDRLs

CDRL GENERAL INSTRUCTIONS

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 Requirement 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 AA01-AA11, AB01-AB20, and AC01; and

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

DATA ITEM DESCRIPTIONS (DIDs)

The 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 (DoDISS) listed on the Acquisition Streamlining and Standardization Information System (ASSIST).

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 Procuring 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 a 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. The letter “A” appearing in Block 8 of the CDRL designates such data. Approval will be required on every submittal (e.g., the Preliminary, Draft, Finals that incorporate government comments, and revisions or change pages, if applicable). The approving authority shall be the PCO. Delivery of the Final data shall be submitted within 30 CD after receipt of government approval of

Draft unless otherwise stated on CDRL.

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 government on all submittals.

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, & revisions

R/ASR Revisions as required *ASREQ As required

DFDEL Deferred delivery DFORD Deferred ordering

ONE/P 1-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 1st 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 all SPO personnel (Air Force, 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.

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:

9001 A TDP TM OTHER X

D SYSTEM / ITEM E CONTRACT / PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

A001 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/LRE

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

Draft Reg Repro

16 REMARKS See Distribution List

1. (BLK 4):

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

b. List is not to include data generated by other CDRLs on contract.

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

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

15 TOTAL 1

G PREPARED BY H DATE I APPROVED BY J DATE

Electronically Generated PAGE 1 OF 1 PAGES

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:

9001 A TDP TM OTHER X

A002 Cost Data Summary Report (DD Form 1921)

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

SMC/LRP

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

BLK 16

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the CAIG Chair approved Cost and Software Reporting (CSDR) Plan provision, the WBS Data Dictionary, and the Contract Cost Data Reporting (CCDR) Manual

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

Defense Cost and Resource Center (DCARC)

201 12th Street South

Suite 220

Arlington, CA 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 deliver 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 SMC/LRP. 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.

15 TOTAL

Electronically Generated PAGE 1 OF 1 PAGES

a. NAME:

Pre-A B X C-FRP

A C-LRIP O&S X

PROGRAM X

X

X

a. CWBS

DICTIONARY

d. DD 1921-2

(PCR)

f. SRDR

FORMATS

X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

DD FORM 2794, MAY 2011 PREVIOUS EDITION IS OBSOLETE

310-653-4715

6c. FAX NUMBER (Include Area Code)

310-653-3151

Launch Vehicle SystemLaunch Vehicle

5. LAST APPROVED PLAN DATE

(YYYYMMDD)

2014051220150814

INITIAL

CHANGE

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

b. PHASE/MILESTONE c. PRIME MISSION PRODUCT

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.

2. WBS SYSTEM TYPE

1. MAJOR PROGRAM EELV - Evolved Expendable Launch Vehicle

3. SUBMISSION TYPE 4. CURRENT SUBMISSION

DATE (YYYYMMDD)

7. PLAN TYPE

CONTRACT (PRIME)

CONTRACT (SUB)

ii. DIVISION

9a. CONTRACTOR NAME/ADDRESS

i. PERFORMING ORGANIZATION

6d. E-MAIL ADDRESS roy.bryson@us af.mil

TBD

6a. POINT OF CONTACT (POC) NAME AND ADDRESS (Include ZIP Code) SMC/LRP Cost Chief 483 N. Aviation Blvd Los Angeles AFB El Segundo CA 90245

RDT&E

PROCUREMENT

O&M

9c. APPROPRIATION

6b. TELEPHONE NUMBER (Include Area Code)

AF-05-C-C14(R)

10. APPROVED PLAN NUMBER

c. DD 1921-1

(FCHR)

e. DD 1921-4

(CSR)

DD 1921-3 (CBDR)

9b. CONTRACT NUMBER

FA811-16-C-000X (TBD)

b. CONTRACT/

SUBCONTRACT

12.

WBS REPORTING ELEMENTS

11. WBS ELEMENT CODE 13. REPORTS REQUIRED

(X if applicable)

a. PROGRAM/

CONTRACT/

SUBCONTRACT

8. PREPARING

ORGANIZATION

AF SMC/LR Program Control

1.01 0

1 8 2.3 1.8 2 3 1 8 2.2 1.8 2 2

b. DD 1921

(CDSR)

XLaunch Vehicle System (GPS III)

Mission Unique Hardware Payload Attach Fitting (Adapter) X

X

X X X

1 8 2.1 1.8 2.1 Payload Fairing X X 1 8 2 1.8 2 Payload Accommodations X 1 8.1.3 1.8.1 3 Solid Rocket Motors X X 1 8.1.2 1.8.1 2 Upper Stage Engine X X 1 8.1.1 1.8.1.1 Booster Engine X X 1 8.1 1.8.1 Propulsion X X 1 8 1.8 Launch Vehicle X X

1.7 6 1.7 6 Propellants (Vehicle) X

1.7 5 1.7 5 Range Operations Services X

1.7.4 1.7.4 Base Support X X

1.7 3.2 1.7 3 2 Other Maintenance X

1.7 3.1 1.7 3.1 Sustainment Propellants X

1.7 3 1.7 3 Site Maintenance X X

1.7 2.2 1.7 2 2 Launch Operations System Engineering X X

1.7 2.1 1.7 2.1 Launch Operations Program Management X X

1.7 2 1.7 2 Launch Operations SEPM X X

1.7.1.2 1.7.1 2 P/L Encapsulation X

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

1.7.1 1.7.1 Launch Support X

1.7 1.7 Launch Operations X 1 6 1.6 Transportation X 1 5.4 1.5.4 Special Studies (by Study) X X 1 5 3 1.5 3 Factory Support X X 1 5 2 1.5 2 System Engineering X X 1 5.1 1.5.1 Program Management X X 1 5 1.5 System Engineering, Integration, Test, Program Management X X

1.4 1.4 Mission Unique Development/Design X 1 3 1.3 Supplier Readiness X 1 2 1.2 Mission Assurance X

1.1 2 1.1 2 Mission Unique Integration X

1.1.1 1.1.1 Mission Standard Integration X

1.1 1.1 Mission Integration X

1 8 3 1.8 3 Core Vehicle X X 1 8 3.1 1.8 3.1 Booster Structure X X

X

a. CWBS

DICTIONARY

d. DD 1921-2

(PCR)

f. SRDR

FORMATS

X X X X X X X X X X X

DD FORM 2794, MAY 2011 PREVIOUS EDITION IS OBSOLETE

11. WBS ELEMENT CODE

12.

WBS REPORTING ELEMENTS

13. REPORTS REQUIRED

(X if applicable)

DD 1921-3 (CBDR)

a. PROGRAM/

CONTRACT/

SUBCONTRACT

b. CONTRACT/

SUBCONTRACT

b. DD 1921

(CDSR)

c. DD 1921-1

(FCHR)

e. DD 1921-4

(CSR)

1 8 3.2 1.8 3 2 Intertank Adapter & Skirts X X

Total Price X

Reporting Contractor Profit/Loss or Fee X

Total Cost X Reporting Contractor FCCM X Reporting Contractor Management Reserve X Reporting Contractor Undistributed Budget X Reporting Contractor G&A X

Subtotal Cost X

1.10 1.10 Other X 1 9 1.9 Training X 1 8.7 1.8.7 Integration, Assembly, Test & Checkout (IAT&C) X X 1 8 6 1.8 6 Guidance and Control (Avionics) X X 1 8 5 1.8 5 Mission Assurance Instrumentation X X 1 8.4.2 1.8.4 2 Interstage Adapters, Stub Adapters, Forward Adapters X X 1 8.4.1 1.8.4.1 Upper Stage Structure X X 1 8.4 1.8.4 Upper Stage X X 1 8 3.4 1.8 3.4 Heat Shield X X 1 8 3.3 1.8 3 3 Aft Transition Structure X X

d. AS OF DATE e. DUE DATE

(YYYYMMDD) (YYYYMMDD)

1 CWBS Dictionary Initial CWBS Submission 20160201 20160502 2 1921, 1921-1 Initial Report - Initial Cost Report (GPS III) 20160201 20160502 3 1921, 1921-1 Final Cost Report (GPS III) 20170201 20180904

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

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.

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

c. Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA. If the document applies to m than three future years, attach additional future year sheets as required. In the absence of these documents, estimates should be provided for three future years.

SPECIAL INSTRUCTIONS:

(1) Only provide an initial report (which will only have initial at completion estimates) and a final report (when actual costs are known) given the period of performance expected for the contract.

(2) Develop a mapping approach to assign production, test, and check out costs / hours to those identified in the CSDR plan's section 1.7 (Launch Vehicle) elements.

(3) Develop a mapping approach to assign engineering costs / hours to those identified in the CSDR plan's section 1.4 (System Engineering, Program Management) elements.

(4) Either build a mapping plan to assign mission integration and launch operations costs / hours to those identified in the CSDR plan's section 1.1 (Mission Integration), section 1.5 (Transportation), and 1.6 (Launch Operations) elements or identify these as costs captured in the overhead costs. Discrete easily identifiable launch costs (specifically telemetry data) you would intend to break out.

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

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

14. CSDR SUBMISSION DATES

15. REMARKS

c.

EVENT

a.

SUBMISSION

b.

FORM(S)

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.

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:

9001 A TDP TM OTHER X

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

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

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the CAIG Chair approved Cost and Software Reporting (CSDR) Plan provision, the WBS Data Dictionary, and the Contract Cost Data Reporting (CCDR) Manual

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

Defense Cost and Resource Center (DCARC)

201 12th Street South

Suite 220

Arlington, CA 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 deliver 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 SMC/LRP. 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

15 TOTAL 1

Electronically Generated PAGE 1 OF 1 PAGES

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:

9001 A TDP TM OTHER X

EELV

A004 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

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the CAIG Chair approved Cost and Software Reporting (CSDR) Plan provision, the WBS Data Dictionary, and the Contract Cost Data Reporting (CCDR) Manual

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

Defense Cost and Resource Center (DCARC)

201 12th Street South

Suite 220

Arlington, CA 22202

c. Prepare Contractor Business Data Report (CBDR) data in electronic format in accordance with the detailed instructions contained in Data Item Description DI-FNCL-81565B. 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 deliver 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 SMC/LRP. 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, 13 & 13): Please reference the latest approved CSDR Plan provided by DCARC for

Electronically Generated PAGE 1 OF 1 PAGES

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:

9001 A TDP TM OTHER X

A005 Contractor Work Breakdown Structure (CWBS)

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

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

A

16 REMARKS See Distribution List

1. (BLK 4):

a. Prepare in accordance with the Contract Cost Data Reporting (CCDR) Manual (DoD 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 DCARC website http://dcarc cape.osd.mil/

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

Defense Cost and Resource Center (DCARC)

201 12th Street South

Suite 220

Arlington, CA 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 CWBS Dictionary. These reports must be submitted by report upload to the

DCARC’s secure website. The DCARC website contains information about deliver 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 SMC/LRP.

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 60 CD after Contract Award.

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 SMC/LRP monthly for Government review and DCARC coordination.

Electronically Generated PAGE 1 OF 1 PAGES

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:

9001 A TDP TM OTHER X

A006 Integrated Program Management Report (IPMR)

Integrated Master Schedule

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

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Only the following DID 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.

b. 2.1.1 Electronic Submission of Data Add the following: The 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 a 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 after contractor’s month end close.

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

f. 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 ATP through contract completion.

g. 3.7.1.3 IMS Content Elements 2nd bullet – Replace with: The IMS shall have traceability to WBS and Performance Work Statement.

h. 3.7.1.3.4.3 Scope Planning Add the following: Planning packages shall be detailed 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.

i. 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. Where durations are longer than

44 working days, rationale shall be provided within the IMS.

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9001 A TDP X TM OTHER

D SYSTEM / ITEM E CONTRACT / PR NO F CONTRACTOR

EELV FA8811-15-R-0001

16 REMARKS

j. 3.7.1.3.5.8 Driving Path – Delete

k. 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 contiguous path through the network) flow from mission 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.

l. 3.7.1.3.5.10 Current Schedule Add the following: Reporting thresholds shall be consistent with the most recent DCMA 14 Point Assessment metrics.

m. 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/activities up to the summary level schedule activities and milestones. The determination of external significant and critical interfaces to be identified within the IMS requires agreement among the contractor(s) and Government and is documented accordingly.

n. Delete 3.7 1 3.6 Schedule Risk Assessment (SRA)

o. Delete 3.7 1 3.6.1 – 3.7 1 3.6 5

p. 3.7.1.3.7.2 Required traceability Replace with: The 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.

q. Delete 3.7 1 3.7 3. Item 4) Earned Value Technique (EVT)

2. (BLK 11) Last day of the contractor’s monthly accounting period

3. (BLK 12) No later than 60 DACA

4. (BLK 13) Electronic copy shall be submitted NLT 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

Electronically Generated PAGE 2 OF 2 PAGES

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:

9001 A X TDP TM OTHER

A007 Training Materials

Launch Vehicle Familiarization

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

SMC/LRG

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

ASREQ

60 DACA

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

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 Vehicle Familiarization 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 Vehicle 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 Vehicle Familiarization training materials shall address the following elements (as appropriate for the Launch Service provided):

1. Launch Vehicle Hardware and Software

a. Booster

i. Structure

1. Propellant Tanks

2. Primary Transition Structure

3. Heat Shields

Electronically Generated PAGE 1 OF 3 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9001 A X TDP TM OTHER

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. SRB Propulsion

1. Solid Rocket Booster

2. Strap-On Attach Hardware

3. CCB/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)

Electronically Generated PAGE 2 OF 3 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9001 A X TDP TM OTHER

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/has 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 13): Updates to the training shall be submitted to reflect the latest United States Government certified/approved launch system configuration.

Electronically Generated PAGE 3 OF 3 PAGES

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:

9001 A TDP X TM OTHER

A008 Program Protection Implementation Plan (PPIP)

DI-ADMN-81306 Performance Work Statement, Para 3.1.11

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):10.1 Content Requirements

a. 10.1.a Replace with “Description detailing how the PPIP aligns with the Government PPP methodology and the defined Program Protection schedule activities/events. Description shall also addresses implementation of Government Program Protection contractual direction

(PWS).”

b. Add “10.1.d Definitions of contractor Criticality Analysis methods to further define

Government PPP Critical Components (CC) detail. CC detail must be provided down to the point where the contractor loses configuration management control of the CC internal components (e.g. COTS hardware). Criticality Analysis results should be provided as modifications/additions to Government PPP content.”

c. Add “10.1.e Definition of contractor identified vulnerabilities and Program Protection incidents and how/when they are reported to the Government.”

d. Add “10.1.f Definition of contractor identified vulnerabilities and Program Protection incidents and how/when they are reported to the Government. Also, describe methods to ensure accountability of all Critical Program Information (CPI) handled by the contractor.”

e. Add “10.1.g For Supply Chain Risk Management countermeasures aspects; provide a detailed set of supplier information for all CCs and components that handle CPI. A supplier can either be a Manufacturer (e.g. Original Equipment Manufacturer) or a Vendor (sells

Manufacturer components). If CCs are purchased from a Vendor, the Manufacturer information must also be provided. Required supplier details include: CC supplied, company name, address, website, type (Manufacturer or Vendor), and CAGE code. These details should be specific to where the component being acquired/manufactured.”

2. (BLK 8): Approval shall be by Contracts letter.

3. (BLK 10, 12, and 13):

a. Draft PPIP shall be submitted 30 CD after receipt of the EELV Program Protection Plan (PPP) with the contractor-specific annex.

b. Final PPIP shall be submitted 30 CD after receipt of Government comments to the Draft PPIP.

c. Updates shall be submitted as significant revision to the PPP are made or by PCO direction.

Electronically Generated PAGE 1 OF 1 PAGES

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:

9001 A TDP TM OTHER X

A009 As Built Configuration List (ABCL)

Launch Vehicle Configuration

DI-CMAN-81516/T Performance Work Statement, Para 3.2.4.

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

ONE/R

45 DACA

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 3.1 with the following:

“3.1 The list shows the launch vehicle configuration and critical ground support equipment specific to the launch service delivered under the contract.”

b. Replace 10.2.1 with the following:

“10.2.1 Part name, part number and revision, next higher assembly part number, software part number and revision as applicable for each serial-number-controlled, assembly, subassembly, part or component installed in the end item at time of launch.”

2. (BLK 13): Revisions shall be ASREQ when a change occurs.

Electronically Generated PAGE 1 OF 1 PAGES

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:

9001 A X TDP TM OTHER

A010 Test Plan

Launch Vehicle Test and Verification Plan

DI-NDTI-80566A Performance Work Statement, Para 3.2.5

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

90 DACA

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 2 with “2. General. The test plan shall document in detail the contractor’s plan for conducting tests and analyzing the test results to show how the system, when fielded, will satisfy the requirements of the applicable design specification and compliance documents. Component, Subsystem and System testing philosophy shall ensure all components or integrated systems are tested under worst case or flight like conditions prior to lift off. Exceptions shall be identified as test like you fly (TLYF) exceptions and submitted to the Government for approval. The Contractor shall execute testing and verification in accordance with this plan.”

b. Replace 3 with “3. Format. The plan shall be in the contractor’s format. The plan shall be printable on standard size paper, e.g. 8 ½ x 11 or A4.”

c. Replace first paragraph of 4.9 with “4.9 Master test list. Lists all launch vehicle and ground support tests to be accomplished in the order they are to be performed including, but not limited to, the following:

1. Flight critical component qualification (test or analysis), unit acceptance test and lot acceptance test environment test requirements including duration, magnitude and tolerance, and trace to requirement origin for all applicable launch vehicle and ground support equipment configurations;

2. Flight critical component failure free minimum retest requirements;

3. Factory, test site & launch site sub-system and system level test and verification requirements;

a) Requirements shall include each phase of testing (e.g., hotfire, wet dress rehearsal, system level high pressure proof test, etc.) and the performance verification requirements during that critical test;

b) System-level retest matrix for flight critical component failures;

4. Flight software test requirements, trace to requirement origin, and verification plan;

5. Test bed, analysis, or modeling/simulation tools to be used for each phase of test, their verification and rationale for credible use in this effort;

a) Test Articles—identify the actual number of all test articles, including key support equipment and technical information required for testing in each phase. Specifically identify when prototype, engineering development, pre-production, or production models will be used.

b) Analysis/Simulation. List all models and simulations to be used for each phase of test and verification; explain the rationale for their credible use, and their verification and validation effort.

c) Special Requirements—discuss requirements for any significant capabilities and resources such as: special data processing/database, unique mapping/charting products, extreme physical environment conditions or restricted/special use air/sea/landscapes.

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9001 A X TDP TM OTHER

16 REMARKS See Distribution List

6. Details on how the contractor will document and perform component and system requirements, test procedures, requirements verification, test readiness review, post-test critique documentation and execution requirements as well as USG team access & participation in noted documentation or reviews.

7. Ground system test requirements and verification plan.

A separate listing for each location shall be provided. Each listing shall include the following:”

d. Replace last paragraph of 4.9 with “Validation procedure. An overview of the procedures that the contractor will use to validate the test results, including details on how the contractor will document and perform component and system requirements, test procedures, requirements verification, test readiness review, post-test critique documentation and execution requirements as well as USG team access and participation in noted documentation or reviews.”

2. (BLKs 10 & 13)

a. Submit test plan for Government approval 90 DACA to be formalized by bi-lateral contract modification.

b. Submit revisions to the Government-approved test plan to reflect the latest launch vehicle configuration, as required, to incorporate changes to the document or upon PCO direction.

Changes will be formalized by bi-lateral contract modification.

3. Where exceptions to compliance documents requirements exist as part of the program baseline, adequate mitigation rationale shall be provided and require approval by the Government.

4. Environmental test and performance requirement shall be based on detailed analysis or flight data and shall be supplied upon request.

5. Component and System testing philosophy shall ensure all components or integrated systems are tested under worst case or flight like conditions prior to lift off. Exceptions shall be identified as test like you fly (TLYF) exceptions and submitted to the government for approval.

Electronically Generated PAGE 2 OF 2 PAGES

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…