02_EELV_Phase2_CDRLs_Exhibit_A_DRAFT_PWS.docx

EXHIBIT A

TO

FA8811-19-R-0002

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PHASE 2

CONTRACT DATA REQUIREMENTS LIST (CDRLs)

18 February 2019

Department of the Air Force Space and Missile Systems Center Launch Enterprise 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-AA46; and Order 2 will have CDRLs BA01-BA46

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

b. Block 8: Approval code

c. Block 10: Frequency

CODE (Limit to five characters)

*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

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.

CDRL ADDRESS LIST

1. HQ Space & Missile Systems Center (AFSPC) LE Launch Enterprise Systems Directorate Attn: LE Data Management Office 483 North Aviation Blvd.

Los Angeles AFB El Segundo, CA 90245-2808 SMC.LE.CMDM@us.af.mil

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 Operations Group 30 OG Attn: Data Desk 806 13th St, Room 285

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. DCMA, TBD DCMA

7. NRO Operations Squadron NOPS 401 Discoverer Ave. Ste 32 Schriever AFB, CO 80912 NOPS_Launch@us.af.mil

CDRL DISTRIBUTION LIST

SYMBOL

QTY

Hard/Soft

(DD Form 1921)

LE

DCARC

0/1 0/1

(DD Form 1921-1)

LE

DCARC

0/1 0/1

(DD Form 1921-3)

LE

DCARC

0/1 0/1

DCARC

DCMA

0/1 0/1 0/1

DCARC

0/1 0/1

(HMMP) Plan

SAF/SL

30 LCG

45 LCG

0/1

SAF/SL

0/1 0/1

NOPS

NOPS

0/1 0/1 0/1

45 LCG^^

0/1 0/1

Assessment Report

^ For Launches from Vandenberg Air Force Base (VAFB) ^^ For Launches from Cape Canaveral Air Force Station (CCAFS) or Kennedy Space Center (KSC) NOTE: 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.

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

TDP

TM

EELV

FA8811-19-R-0002

A001

Data Accession List (DAL)

DI-MGMT-81453B/T

Performance Work Statement, Para 3.1.4.5

SMC/LE DMO

LT

BLOCK 16

30 DACA

b. COPIES

FINAL

N/A

N/A

BLOCK 16

1. (BLK 4):

a. Data Accession List (DAL) is cumulative.

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

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

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

3. DAL listing not provided on demand via IDE or equivalent, must be provided in monthly submittal. The Government will review submission and provide feedback within 30 calendar days (CD) to the maximum extent possible.

15. TOTAL

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

OTHER

EELV

FA8811-19-R-0002

A002

IDE Software Design

IDE Database Design Description

DI-IPSC-81437A

Performance Work Statement, Para 3.1.4.2, 3.1.4.3, 3.1.4.4

SMC/LEE

LT

ASREQ

BLK 16

b. COPIES

FINAL

A

N/A

BLK 16

1. (BLK 4) Section 3: Contractor format is acceptable.

a. Identify any software and/or license that USG would require to access IDE from USG location. Identify any customization to COTS products that would be necessary for IDE access.

b. Provide a snapshot of hierarchy and/or structure so that the USG can navigate the IDE to review required data.

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

a. IDE Draft Database Design Description (DBDD) shall be submitted 90 DACA.

b. Final IDE Database Design Description shall be submitted 30 CD after receipt of Government comments to the Draft Database Design Description.

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

15. TOTAL

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

TDP

TM

EELV

FA8811-19-R-0002

A003

Cost Data Summary Report (DD Form 1921)

DI-FNCL-81565C/T

Performance Work Statement, Para 3.1.6

SMC/LEP

LT

BLK 16

BLK 16

b. COPIES

FINAL

N/A

BLK 16

BLK 16

1. (Blocks 10 – 13):

Prepare the Cost Data Summary Report (CDSR) in accordance with DI-FNCL-81565C (or the most recently approved version) and the OSD Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-FNCL-81565C, is available from the Defense Cost and Resource Center (DCARC) website at http://cade.osd.mil/csdr/FormsReporting.aspx#DIDs. The CSDR Plan is included as a contract attachment.

Contractors shall be required to submit the Contractor Cost Data Reports (CCDRs) at frequencies specified in the OSD DDCA-approved CSDR plan and in the contract. The contract CSDR plan uses the event field as the driver for the submission of the reports, not the "as of date." If the event slips, the contractor must notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a request for change in the event-driven date for reporting through the CSDR Submit-Review system for DCARC approval before the date reflected in the OSD DDCA-approved CSDR Plan.

All CCDRs shall be submitted electronically using the CSDR Submit-Review System. The required form and file type for each CCDR is specified in its Data Item Description (DID). Data submitters must register through the DCARC website and possess a DoD-approved ECA digital certificate or DoD-issued CAC to obtain a DCARC Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the DCARC Portal and requesting a CSDR submitter user role. After the registration information has been verified, the DCARC shall authorize the user account and requested roles. All DCARC Portal accounts need to be renewed at least annually.

Contractors shall submit CDSRs for two separate CSDR Plans: One Plan for Launch Services (by Mission) and one plan for Launch Service Support-LSS (Annually). Refer to the CSDR Plans for Special Instructions (Block 15. Remarks) on preparing the report.

Subcontractor Reporting: Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in the DoDI 5000.02, or as required by the CWIPT. This includes requiring subcontractors to electronically report directly to the DCARC using the CSDR Submit-Review System.

The prime contractor shall be required to work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to the DCARC for DDCA approval.

15. TOTAL

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

TDP

TM

EELV

FA8811-19-R-0002

A004

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

DI-FNCL-81566C/T

Performance Work Statement, Para 3.1.6

SMC/LEP

LT

BLK 16

BLK 16

b. COPIES

FINAL

N/A

BLK 16

BLK 16

1. (Blocks 10 – 13):

Prepare the Functional Cost Hour Report (FCHR) in accordance with DI-FNCL-81566C (or the most recently approved version) and the OSD Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-FNCL-81566C, is available from the Defense Cost and Resource Center (DCARC) website at http://cade.osd.mil/csdr/FormsReporting.aspx#DIDs. The CSDR Plan is included as a contract attachment.

Contractors shall be required to submit the Contractor Cost Data Reports (CCDRs) at frequencies specified in the OSD DDCA-approved CSDR plan and in the contract. The contract CSDR plan uses the event field as the driver for the submission of the reports, not the "as of date." If the event slips, the contractor must notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a request for change in the event-driven date for reporting through the CSDR Submit-Review system for DCARC approval before the date reflected in the OSD DDCA-approved CSDR Plan

All CCDRs shall be submitted electronically using the CSDR Submit-Review System. The required form and file type for each CCDR is specified in its Data Item Description (DID). Data submitters must register through the DCARC website and possess a DoD-approved ECA digital certificate or DoD-issued CAC to obtain a DCARC Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the DCARC Portal and requesting a CSDR submitter user role. After the registration information has been verified, the DCARC shall authorize the user account and requested roles. All DCARC Portal accounts need to be renewed at least annually.

Contractors shall submit FCHRs for two separate CSDR Plans: One Plan for Launch Services (by Mission) and one plan for Launch Service Support-LSS (Annually). ). Refer to the CSDR Plans for Special Instructions (Block 15. Remarks) on preparing the report.

Subcontractor Reporting: Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in the DoDI 5000.02, or as required by the CWIPT. This includes requiring subcontractors to electronically report directly to the DCARC using the CSDR Submit-Review System.

The prime contractor shall be required to work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to the DCARC for DDCA approval.

15. TOTAL

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

TDP

EELV

FA8811-19-R-0002

A005

Contractor Business Data Report (DD Form 1921-3)

DI-FNCL-81765/T

Performance Work Statement, Para 3.1.6

SMC/LEP

LT

BLK 16

BLK 16

b. COPIES

FINAL

N/A

BLK 16

BLK 16

Contractors shall be required to submit 1921-3 Contractor Business Data Report on an annual basis within 60 calendar days subsequent to the end of the contractor's fiscal year for the life of the contract in accordance with DI-FNCL-81765 (or most recently approved version). Only one report is required to be completed and submitted by each FPR (Forward Pricing Rate) unit (e.g., plant, site, business unit) per year, independent of the number of contracts within the FPR unit which contain this CDRL item. The Contractor Business Data Report is to be prepared by and for the business entity (e.g., plant, site, or business unit) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government. In the absence of a FPR requirement, the term “FPR unit” should be interpreted for reporting purposes as “business unit” as defined in the FAR.

Reports are to be submitted annually, as of the end of the business entity’s fiscal year. The reports are due 60 days subsequent to the end of the contractor's fiscal year.

The Defense Cost and Resource Center (DCARC) is responsible for administration of this requirement. The DCARC website is located at http://cade.osd.mil/csdr.

All 1921-3 reports shall be submitted electronically using the 1921-3 & FPR Submit-Review System. The required form and file type for each 1921-3 report is specified in its Data Item Description (DID). Data submitters must register through the DCARC website and possess a DoD-approved ECA digital certificate or DoD-issued CAC to obtain a DCARC Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the DCARC Portal and requesting a CSDR submitter user role. After the registration information has been verified, the DCARC shall authorize the user account and requested roles. All DCARC Portal accounts need to be renewed at least annually.

15. TOTAL

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

TDP

TM

EELV

FA8811-19-R-0002

A006

Contractor Work Breakdown Structure (CWBS)

DI-MGMT-81334D/T

Performance Work Statement, Para 3.1.6

SMC/LEP

LT

BLK 16

BLK 16

b. COPIES

FINAL

N/A

BLK 16

BLK 16

1. (Blocks 10 – 13):

Prepare the CWBS in accordance with DI-MGMT-81334D (or the most recently approved version) and the OSD Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-MGMT-81334D, is available from the Defense Cost and Resource Center (DCARC) website at http://cade.osd.mil/csdr/FormsReporting.aspx#DIDs. The CSDR Plan is included as a contract attachment.

Contractors shall be required to submit the CWBS Dictionary at frequencies specified in the OSD DDCA-approved contract CSDR plan and in the contract. The contract CSDR plan uses the event field as the driver for the submission of the reports, not the "as of date." If the event slips, the contractor must notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a request for change in the event-driven date for reporting through the CSDR Submit-Review system for DCARC approval before the date reflected in the OSD DDCA-approved CSDR Plan.

The CWBS Dictionary shall be submitted electronically using the CSDR Submit-Review System. Data submitters must register through the DCARC website and possess a DoD-approved ECA digital certificate or a DoD-issued CAC to obtain a DCARC Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the DCARC Portal and requesting a CSDR submitter user role. After the registration information has been verified, the DCARC shall authorize the user account and requested role. All DCARC Portal accounts need to be renewed at least annually.

Subcontractor Reporting. Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in the DoDI 5000.02, or as required by the CWIPT. This includes requiring subcontractors to electronically report directly to the DCARC using the CSDR Submit-Review System.

The prime contractor shall be required to work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to the DCARC for DDCA approval.

15. TOTAL

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

OTHER

EELV

FA8811-19-R-0002

A007

Small Business Utilization Report

DI-MGMT-82041

Performance Work Statement, Para 3.1.6

SMC/LE

LT

SEMIA

BLK 16

b. COPIES

FINAL

A

N/A

BLK 16

1. (BLK 4): Contractor format is acceptable.

a. Draft reports shall be coordinated with SMC/SB at least five (5) working days (WD) prior to the due dates (April 30 and October 30) to allow subsequent turn-around time for the contractor to resubmit (if applicable) after government's acceptability determination has been issued.

b. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

c. Small Business Utilization Report shall be in contractor format or as specified in the contract, and briefly describe the subcontractor(s) efforts performed.

d. The contractor shall report actual achievements relative to proposed small business utilization in performance of the contract (including subcontracting dollars/percentages relative to total contract value / total subcontracting), and the results of efforts to:

1) Expand the pool of qualified small businesses through increased competition for acquisition of components, parts (includes hardware and software), and/or to perform sustainability or support services.

2) Engage small businesses to serve as alternative sources in order to mitigate the risks of single point failures in the supply chain and increase the quality of supplies or services.

e. Under no circumstances shall technical data or computer software to be delivered under or in conjunction with this CDRL, be marked "Proprietary" (or similar Nonconforming marking(s)).

f. (BLK 9): Distribution Statement E: Distribution authorized to DoD Components only (Proprietary Information). Other requests shall be referred to (SMC/SB)

2. (BLK 12, 13): The semiannual report shall be submitted for the six months ending March 31 and the twelve months ending September 30. Reports are due 30 calendar days after the close of each reporting period and within 30 calendar days of contract completion.

a. Government review and approval (or disapproval) and comments will be provided within 30 calendar days after receipt of each submittal or revision unless otherwise specified. If the Government provides any comments, submit an update incorporating Government comments within 15 calendar days after receipt of Government comments unless otherwise specified.

15. TOTAL

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

TDP

TM

EELV

FA8811-19-R-0002

A008

Integrated Program Management Report (IPMR)

Integrated Master Schedule (IMS)

DI-MGMT-81861A/T

Performance Work Statement, Para 3.1.6

SMC/LEP

LT

MTHLY

BLK 16

b. COPIES

FINAL

N/A

BLK 16

BLK 16

1. (BLK 4):

a. Only the following DID sections and their sub-sections (omitting references to Formats 1-5 and 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 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 (WD) after contractor’s month end close.

e. 2.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.

i. 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.

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. Where durations are longer than 44 working days, rationale shall be provided within the IMS.

15. TOTAL

Electronically Generated PAGE 1 OF 2 PAGES

A

OTHER

EELV

FA8811-19-R-0002

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

m. 3.7.1.3.5.10 Current Schedule Add the following: Reporting thresholds shall be consistent with the most recent 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/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 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 Path in the title and the requirement.

s. 3.7.1.3.9 Retention of Historic 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) First submission of the initial draft shall be 30 DACA for Government review. Contractor shall submit updated IMS for each launch task order for Government acceptance. .

4. (BLK 13) Electronic copy shall be submitted no later than (NLT) 12 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 CD to the maximum extent possible.

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

TDP

TM

EELV

FA8811-19-R-0002

A009

Integrated Program Management Report (IPMR)

Mission Integration Schedule (MIS)

DI-MGMT-81861A/T

Performance Work Statement, Para 3.4.2.1, 3.4.2.4

SMC/LE GMIM

LT

BI-MO

BLK 16

b. COPIES

FINAL

N/A

BLK 16

BLK 16

1. (BLK 4): MIS schedule will be a subset of the IMS submitted for each NSS Launch Task Order. DID subsection 6 is applicable in accordance with CDRL A008 approved format.

a. The MIS may be used to coordinate Mission Integration activity and SV schedule for integration purposes. The MIS may be CDRL A008 submittal that is filtered for content appropriately.

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

3. (BLK 12) Submittal of MIS will be provided to the Government for each Launch Task Order, with initial submitted no later than 60 calendar days (CD) after task order.

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

15. TOTAL

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

TM

OTHER

EELV

FA8811-19-R-0002

A010

Work Management Plan

Mission Integration Management Plan

DI-MGMT-81911/T

Performance Work Statement, Para 3.1.8, 3.4.2.4, 3.4.6.1, and 3.8.17.8 .8

SMC/LE GMIM

LT

ASREQ

BLK 16

b. COPIES

FINAL

N/A

N/A

BLK 16

1. (BLK 4):

a. Replace 1 with “1. 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.”

b. Replace 3 with “The Mission Integration management Plan describes the contractor’s mission integration services and process flow. The Plan shall contain the following sections:

1.0 Introduction

2.0 Integration Management

2.1 Standard Mission Integration Plan. Provide an overview of the mission integration processes/tasks, citing applicable Performance Work Statement (PWS) paragraphs for reference.

2.2 Integration Schedules. Provide the Mission Integration Schedule and associated schedules used in the Mission Integration process.

2.3 Action Items: Provide an overview of the contractor’s process and tracking system used to ensure action item closure.

3.0 Organizational Responsibilities. For the following organizations describe the organization responsibilities in the Contractor’s Mission Integration process. Provide a graphical representation of the corresponding connections and Points of Contacts between the different organizations.

3.1 Government Organizations

3.1.1 Launch Vehicle Program Office (SMC/LE)

3.1.2 Space Vehicle Program Office (For USAF Missions)

3.1.3 USAF Space Wing(s)

3.2 Contractor Organizations

3.2.1 Launch Vehicle Contractor (LVC)

3.2.2 Satellite Vehicle Contractor (SVC) (For USAF Missions)

15. TOTAL

Electronically Generated PAGE 1 OF 2 PAGES

A

TM

OTHER

EELV

FA8811-19-R-0002

4.0 Key Integration Meetings. Provide the detail description purpose/objectives and composition of the following Contractor meetings:

4.1 Mission Integration Kick-off meeting (Four-party meeting to introduce the mission and integration plan)

4.2 Mission Design Review (MDR) (Preliminary design review for mission integration)

4.3 Mission Verification Review (MVDR) (Critical design review for mission integration)

4.4 Ground Operations Readiness Review (GORR) (For USAF missions) (Launch site readiness for ground operations to integrate spacecraft onto the launch vehicle)

4.5 Pre-Vehicle Ship Review (Verify readiness to ship flight hardware to the launch site)

4.6 Component and Subsystem Readiness Review (CSRR) (Assessment of mission and launch vehicle design and analysis)

4.7 Integrated Operation Readiness Review (IORR) (Review and demonstrate launch site and launch vehicle readiness for integrated ops)

4.8 Space Flight Worthiness Certification Review (SCR) (Establishes readiness of launch system to proceed into countdown operations)

4.9 Launch Readiness Review (LRR) (Final Contractor’s readiness review for launch)

4.10 Other Contractor Mission Readiness Reviews (Any other readiness reviews necessary due to the nature of the mission)

4.11 Launch System Program Level Reviews (Contractual or hardware reviews which the integration team should support)

5.0 Customer Reviews and Rehearsals. Provide description and summarization of level of support to be provided for the following meetings:

5.1 Mission Rehearsals (including academics)

5.2 Spacecraft Mission Readiness Review (MRR)

5.3 Flight Readiness Review (FRR)

5.4 Ground Operations Readiness Review (GORR)

6.0 Integration Working Groups. Provide a description of the nature and composition of the working groups below.

6.1 Management Working Group (MWG)

6.2 Ground Operations Working Group (GOWG)

6.3 Day-of-Launch Working Group (DOLWG)

6.4 Ascent Operations Working Group (AOWG)

6.5 Rehearsal Working Group (RWG)

6.6 Other Contractor Mission related working group (Any other working group necessary due to the nature of…