02b_CDRLs_Exhibit_BX_Signed.pdf

EXHIBIT BA, BB, BC, BD, AND BE

TO

FA8811-18-R-0001

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PHASE 1A

CONTRACT DATA REQUIREMENTS LIST (CDRLs)

31 January 2018

Department of the Air Force

Space and Missile Systems Center

Launch Systems Enterprise Directorate

Los Angeles Air Force Base, California

CDRL General Instructions CDRL Address List CDRL Distribution List CDRLs

CDRL GENERAL INSTRUCTIONS

EXHIBIT B ORGANIZATION

Mission Title Exhibit Section

NROL-85 BA

NROL-87 BB

SILENTBARKER BC

SBIRS GEO-5 BD

AFSPC-44 BE

CONTRACT DATA REQUIREMENTS LIST (CDRL)

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

DATA ITEM NUMBER

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

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

DATA ITEM DESCRIPTIONS (DIDs)

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

DID TAILORING

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

DATA DELIVERY DATES

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

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

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

DD FORM 250 REQUIREMENTS

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

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

ADDITIONS TO DISTRIBUTION

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

COMMUNICATIONS

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

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

CDRL ADDRESS LIST AND DATA DISTRIBUTION LIST

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

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

DATA APPROVALS

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

CODES USED ON THE CDRL

The following codes may be used as described below.

a. Block 7: DD Form 250 requirements

CODE WHEN USED

LT Letter of Transmittal only

b. Block 8: Approval code

CODE WHEN USED

A Approval is required by the government.

N/A Approval is not required.

c. Block 10: Frequency

CODE (Limit to five characters)

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

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

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

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

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

ELECTRONIC DISTRIBUTION

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

CDRL ADDRESS LIST

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

Attn: Launch Systems Directorate 483 North Aviation Blvd.

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

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

b. LEE

c. LEP

d. LEK

e. LEG

f. LEM

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

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

Los Angeles AFB El Segundo, CA 90245-2808

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

4. 45 LCG/45 LCSS 45 LCG

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

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

(703) 601-4850

6. Defense Contract Management Agency (DCMA) DCMA

TBD

7. NRO Operations Squadron NOPS

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

CDRL DISTRIBUTION LIST

CDRL TITLE OFFICE

SYMBOL

QTY

Hard/Soft

BX01 Technical Report – Launch Slot/Date Recommendation LEG

SAF/SL**

0/1 0/1

BX02 System Safety Program Plan (SSPP) LEE

SAF/SL**

0/1 0/1

BX03 Safety Assessment Report LEE

SAF/SL**

0/1 0/1

BX04 Hazardous Materials Management Program (HMMP) Plan

LEE

SAF/SL**

0/1 0/1

BX05 Contractor’s Standard Operating Procedures – Compliance Document Tailoring

LEE

LEG

SAF/SL**

0/1 0/1 0/1

BX06 Test/Inspection Report – Post-Flight Assessment Report

LEE

LEG

SAF/SL**

0/1 0/1 0/1

BX07 Design Data and Calculations – Performance Capabilities Guide

LEE

LEG

SAF/SL**

0/1

0/1

BX08 Work Management Plan – Mission Integration Management Plan

LEG

SAF/SL**

0/1 0/1

BX09 System/Segment Interface Control Specification – Mission- Specific Interface Control Document (ICD)

LEG

SAF/SL**

0/1 0/1

BX10 Design Data and Calculations – Mission Assurance Independent Assessment Data

LEG

SAF/SL**

0/1 0/1

BX11 Specification Requirement Verification Matrix – Verification Planning Matrix (VPM)

LEG

SAF/SL**

0/1 0/1

BX12 Specification Requirement Verification Matrix – Verification Evidence Record (VER)

LEG

SAF/SL**

0/1 0/1

BX13 Design Data and Calculations – Space Safety Collision Avoidance

LEG

SAF/SL**

0/1 0/1

BX14 Design Data and Calculations – Radio Frequency Power Impingement Data

LEG

SAF/SL**

0/1 0/1

BX15 Contractor’s Standard Operating Procedures – Work Authorizing Documents List

30 LCG^

45 LCG^^

SAF/SL**

0/1 0/1 0/1

BX16 Work Management Plan – Integration and Operations Plan

LEG

LEE

SAF/SL**

0/1 0/1 0/1

BX17 Design Data and Calculations – Prelaunch Data and Documentation Supporting Launch Operations

LEE

LEG

NOPS

SAF/SL**

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

BX18 Critical Items List – Flight Critical Hardware List LEG

SAF/SL**

0/1 0/1

BX19 Conference Agenda – Pedigree Notification Package LEG

SAF/SL**

BX20

Work Management Plan – Launch Service Provider Space Flight Worthiness Non-Recurring Design Validation Work Closure Plan

LEE

LEG

LEM

SAF/SL**

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

BX21 Acceptance Test Plan – Mission Unique Hardware Test Plan LEG

SAF/SL**

0/1 0/1

BX22 Acceptance Test Report – Mission Unique Hardware Qualification and Acceptance Test Report

LEG

SAF/SL**

0/1 0/1

BX23 Technical Data Package – Mission Unique Hardware Drawings LEG

SAF/SL**

0/1 0/1

BX24 RESERVED

BX25 Technical Report – Study/Service

LEM

LEE

LEG

SAF/SL**

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

BX26 Secondary Objectives Do No Harm Analysis

SMC/LEE

SAF/SL

SAF/SL**

0/1 0/1 0/1

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

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

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

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP TM OTHER X

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

EELV FA8811-18-R-0001

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

BX01 Technical Report Launch Schedule/Date Recommendation

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

DI-MISC-80508/T Performance Work Statement, Para 3.1.6.2 SMC/LEG

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT BLK 16 BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A BLK 16 BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Replace 2 with: Contractor Format.

b. Replace 3 with:

i. The Contractor shall provide a Launch Slot Recommendation (LSR) for each launch order identifying the following:

1. A Launch Slot within the previously assigned Launch Period

2. Additional supplemental hardware or capability when required

3. A decision date for Government concurrence. If not specified, need date is fifteen (15) calendar days (CD) after Government receipt of LSR.

ii. The Contractor shall provide a Launch Date Recommendation (LDR) for each launch order identifying the following:

1. Specific Launch Date within the previously authorized Launch Slot

2. Assigned launch site

3. Deadline for Government-provided payload/spacecraft ready for Launch Vehicle mate

4. Decision date for Government concurrence. If not specified, need date is fifteen (15) CD after Government receipt of LDR.

2. (BLKs 10, 11,12,13)

a. The Contractor shall provide the LSR no later than 405 CDs (approximately 13 and a half [13.5] months) prior to the beginning of the Launch Period.

b. The Contractor shall provide the LDR no later than 225 CDs (approximately seven and a half [7.5] months) prior to the beginning of the Launch Slot.

15. TOTAL

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

31 Jan 2018 31 Jan 2018

Electronically Generated PAGE 1 OF 1 PAGES

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP TM OTHER X

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

EELV FA8811-18-R-0001

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

BX02 System Safety Program Plan (SSPP)

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

DI-SAFT-81626 Performance Work Statement, Para 3.1.7 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT BLK 16 BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A CA BLK16 Draft Reg Repro

16. REMARKS See Distribution List

(BLK 4)

The Safety Program Plan (SSPP) shall implement the following MIL-STD-882E safety activities and produce specified results throughout the program life-cycle. 102.2.4 Milestones. The SSPP shall provide a schedule of system safety activities including required inputs and outputs, and start and completion dates that support the SE process IAW MIL-STD-882E, 102.2.4.a :

(i) TASK 101 HAZARD IDENTIFICATION AND MITIGATION EFFORT

USING THE SYSTEM SAFETY METHODOLOGY ****

(ii) TASK 102 SYSTEM SAFETY PROGRAM PLAN

(iii) TASK 104 SUPPORT OF GOVERNMENT REVIEWS/AUDITS

(iv) TASK 106 HAZARD TRACKING SYSTEM ***

(v) TASK 108 HAZARDOUS MATERIALS MANAGEMENT PLAN

(vi) TASK 202 PRELIMINARY HAZARD ANALYSIS *

(vii) TASK 204 SUBSYSTEM HAZARD ANALYSIS *

(viii) TASK 205 SYSTEM HAZARD ANALYSIS * **

(ix) TASK 208 FUNCTIONAL HAZARD ANALYSIS

(x) TASK 304 REVIEW OF ENGINEERING CHANGE PROPOSALS, CHANGE NOTICES, DEFICIENCY REPORTS, MISHAPS, AND

REQUESTS FOR DEVIATION/WAIVER

(xi) TASK 401 SAFETY VERIFICATION

(BLKs 10, 11,12,13)

a. Draft System Safety Program Plan (SSPP) shall be submitted 90 calendar days (CD) after contract award.

b. Final SSPP shall be submitted 60 CD after receipt of Government comments to the Draft SSPP. If there are no Government comments, the Draft shall be considered the final submittal.

c. Updates shall be submitted 30 CD after revisions to the SSPP are made or by Procurement Contracting Office direction.

15. TOTAL

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

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP TM OTHER X

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

EELV FA8811-18-R-0001

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

BX03 Safety Assessment Report (SAR)

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

DI-SAFT-80102C/T Performance Work Statement, Para 3.1.7 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT R/ASR 60 DACA b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A CA R/ASR Draft Reg Repro

16. REMARKS See Distribution List

(BLK 4):

1. Delete paragraph 3.2b

2. Modify paragraph 3.2c as “A brief description of the system and its major subsystems and components. Software and its roles shall be included in this description. ”

3. Modify 3.3 to include "This section may be developed by referencing other program documentation."

4. Replace 3.4 with “3.4 System Safety engineering. This section may be developed by referencing other program documentation and shall include the following:

a. The specific Severity categories matrix, Probability level matrix and risk assessment matrix used to classify hardware/software/human system integration hazards

b. The results of analyses and tests performed to identify hazards, assess risks, and verify/validate effectiveness of mitigation measures.

c. A list of software functions that are safety critical as defined by AFSPC Manual 91-710 paragraph 3.16.2.

d. Hazard Tracking System (HTS) data

e. A summary of risks for each identified hazard

5. Replace 3.5 with "3.5 Elevated Risks

a. Identify any residual risks classified as High or serious in accordance with the MIL-STD-882E Risk Index".

6. Modify paragraph 3.6 as “Reference. List all pertinent references, including (but not limited to) test and analysis reports, standards and regulations, drawings, Qual test reports, specifications and requirements documents, operating manuals, and maintenance manuals.”

15. TOTAL

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

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

BX04 Hazardous Materials Management Program (HMMP) Plan

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

DI-MGMT-81398C Performance Work Statement, Para 3.1.15 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT ASREQ 30 DACA b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

(BLK 13): Updates shall be submitted 30 calendar days after revisions to the plan are made or by Procurement Contracting Office direction.

15. TOTAL

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

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

BX05 Contractor’s Standard Operating Procedures Compliance Document Tailoring

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

DI-MGMT-81580/T Performance Work Statement, Para 3.2.11.2 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT BLK 16 90 DACA b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4): Replace 3. Content. with :

“3. Content.

a. For the following compliance documents, the contractor shall submit either

1) Tailoring to the standard as a redlined document and a listing of the tailored items and rationale for each change (Word or Excel) or

2) Contractor’s command media documentation that meets the intent of the standard and a mapping of the requirements of the standard to the command media (Word or Excel) (no mapping required if command media was previously assessed and agreed upon in writing by the Government).

Compliance Documents:

American Institute of Aeronautics and Astronautics (AIAA) S-080-1998, Space Systems, Metallic Pressure Vessels, Pressurized Structures, and Pressure Components

AIAA S-081A-2006, Space Systems – Composite Overwrapped Pressure Vessels (COPV)

AIAA S-110-2005, Space Systems – Structures, Structural Components, and Structural Assemblies

AIAA S-113-2005, Criteria for Explosive Systems and Devices Used on Space and Launch Vehicles

AIAA S-114-2005, Moving Mechanical Assemblies for Space and Launch Vehicles

AIAA S-120-2006, Mass Properties Control for Space Systems, to include Tailoring Instructions for AIAA S-120-2006 in SMC-T-002 (2013)

Committee on National Security Systems Directive (CNSSD) No. 505, Committee on National Security Systems Directive 505, Supply Chain Risk Management

Chemical Propulsion Information Analysis (CPIA) 655, Guidelines for Combustion Stability Specifications and Verification Procedures for Liquid Propellant Rocket Engines (January 1997)

ISO 17666, Space Systems – Risk Management

Military Standard (MIL-STD)-461F, Electromagnetic, Emissions, and Susceptibility, Requirements for the Control of Electromagnetic Interference

MIL-STD-882E, System Safety Program Requirements IAW the PWS, to include Tailoring Instructions for MIL-STD-882E in SMC-T-004 (2012) (T)

15. TOTAL

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

Electronically Generated PAGE 1 OF 2 PAGES

(1 Data Item)

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

16. REMARKS See Distribution List

MIL-STD-1528A, Production Management

MIL-STD-1542B, Electromagnetic Compatibility Grounding Requirements for Space System Facilities

National Aerospace Standards (NAS) 412, Foreign Object Damage/Foreign Object Debris (FOD) Prevention

National Aeronautics and Space Administration (NASA)-STD-5012 (A or B), Strength and Life Assessment Requirements for Liquid Fueled Space Propulsion System Engines

NASA-STD-5019A, Fracture Control Requirements for Spaceflight Hardware

NASA-STD-5020, Requirements for Threaded Fastening Systems in Spaceflight Hardware

SAE AS9100 (Current Version), Quality Management Systems – Requirements for Aviation, Space and Defense Organization

Space and Missile Systems Center (SMC)-S-001, Systems Engineering Requirements and Products to include SMC-T-005 (LE revision), Tailoring Of Risk Management Requirements in SMC-S-001 (2013) (T)

SMC-S-002, Configuration Management

SMC-S-003 (T), Quality Assurance for Space and Launch Vehicle

SMC-S-005, Space Systems – Flight Pressurized Systems

SMC-S-006, Solid Rocket Motor Case Design and Test Requirements

SMC-S-008, Electromagnetic Compatibility Requirements for Space Equipment and Systems

SMC-S-011, Part, Materials and Processes Control Program for Expendable Launch Vehicles

SMC-S-012, Software Development for Space Systems

SMC-S-013, Reliability Program for Space Systems

SMC-S-016, Test Requirements For Launch, Upper-Stage, and Space Vehicles

SMC-S-018, Lithium Ion Battery for Launch Vehicle Application

SMC-S-020, Technical Requirements for Wiring Harness, Space Vehicles

SMC-S-021, Volume 1: Technical Reviews and Audits for Systems, Equipment, and Computer Software

b. For Air Force Space Command Manual (AFSPCMAN) 91-710 (Vol 1-7), Range Safety User Requirements and RCC 319-10, Range Commander’s Council (RCC) Flight Termination Systems Commonality Standard, the contract shall submit the Range-approved tailoring.”

2. (BLKs 10, 11, 12, and 13)

a. Submit initial draft 90 days after contract award for Government review and comment. No

Government approval is required.

b. Submit final tailoring/command media for Government approval 30 calendar days (CD) after receipt of Government comments to be formalized by bi-lateral contract modification.

c. If Contractor makes changes to command media elements, and wishes for these changes to apply to this contract, then the Contractor shall submit an update within 30 CD of change or by Procurement Contracting Officer direction, within 30 CD PCO direction. Changes will be formalized by bi-lateral contract modification.

15. TOTAL

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

Electronically Generated PAGE 2 OF 2 PAGES

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

BX06 Test/Inspection Report Post Flight Assessment Report

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

DI-NDTI-80809B/T Performance Work Statement, Para 3.2.8.2 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT ASREQ BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

A. Replace 10.2 with the following:

i. The Post-Flight Assessment Report shall include but not be limited to:

1. Assessment of achieved orbital parameters

2. Identification of known Interface Control Document (ICD) violations

3. Identification of anomalies

4. Assessment of system and sub-system performance to include flight performance, guidance and navigation analysis and flight control for core vehicle and upper stage hardware (solid rocket motors, liquid engines, propulsion, structures, and mechanical systems), payload accommodations (payload adapter fitting and payload fairing), avionics (guidance and navigation control systems, electrical, telemetry and instrumentation, and flight termination system), flight software, ordnance and separation systems, and launch support systems (ground systems, debris analysis, and visual data products)

5. Assessment of the spacecraft flight environment to include loads and dynamics, vibration acoustics and shock, and aero and thermal environments

6. Separation assessment

7. Corrective action plans for all anomalies and anomaly resolution

8. Identification of out-of-family observations

9. Any other observation

ii. Data reduction and the post-flight assessment shall address all data obtained from the launch for standard flight instrumentations, special flight instrumentation (if such instrumentation is installed), and ground system data.

15. TOTAL

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

(1 Data Item)

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

16. REMARKS See Distribution List

iii. Upper stage disposal data

a. The Launch Vehicle Contractor (LVC) shall identify which upper stage disposal method was planned and flown (random atmospheric reentry, controlled atmospheric reentry, maneuvering to a storage orbit, direct retrieval).

b. The LVC shall provide telemetry data confirming the depletion of propellant by blowdown or depletion burn and the release of compressed gases.

c. The LVC shall provide the following information appropriate to the selected method of disposal for the as-flown upper stage:

1. Random atmospheric reentry. Value for risk of human casualty, state vector for end of mission upper stage disposal orbit, disposal orbit lifetime for upper stage based on as-flown end of mission, description of analysis that produced the upper stage disposal orbit lifetime value.

2. Controlled atmospheric reentry. Latitude and longitude of upper stage reentry impact location and comparison to Notice to Airmen and Mariners (NOTAM) box.

3. Maneuvering to storage orbit. Orbital elements at end of mission for as flown upper stage.

4. Direct retrieval. Description of retrieval operation. Time after end of mission when upper stage will be removed.

B. Replace 10.3 with the following: Document content shall be clearly written and describe accomplishments and other facts adequately with no technical errors.

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

A. Initial Post-Flight Assessment Report (covering Items i1-i3 above) shall be submitted within 10 CD following Contractor’s receipt of launch vehicle telemetry data.

B. Identify the upper stage disposal method that was planned and flown to demonstrate compliance with upper stage disposal requirements no later than (NLT) L+2 months (Milestone #10).

C. Final Post-Flight Assessment Report shall be submitted for Government approval NLT L+2 months (Milestone #11).

15. TOTAL

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

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

BX07 Design Data and Calculations Performance Capabilities Guide

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

DI-GDRQ-80650/T Performance Work Statement, Para 3.2.10 SMC/LEE

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT SEMIA BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

N/A N/A SEMIA Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. Contractor format is acceptable

b. Delete 10.2, Replace with the following:

i. For each reference orbit mission listed in the Systems Performance Requirements Document (SPRD) and for representative Contractor’s United States Government certified/approved launch vehicle configurations, a report will be submitted describing the launch vehicles’ performance capability and compliance with the associated SPRD mass-to-orbit performance, performance margin, and flight performance reserve requirements.

ii. All performance threats, liens, ground rules, and assumptions used for these calculations will be included.

c. Delete 10.3

2. (BLKs 10 and 12): Submission shall occur twice per year, 31 March and 30 September; second semiannual submission not required if capabilities remain unchanged.

15. TOTAL

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

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting officer for the Contract/PR No. listed in Block E.

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

X002 B X TDP TM OTHER

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

EELV FA8811-18-R-0001

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

BX08 Work Management Plan Mission Integration Management Plan

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

DI-MGMT-81911/T Performance Work Statement, Para 3.4.3 SMC/LEG

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT ASREQ BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

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. For rideshare missions, this plan should include mission integration processes/tasks for integration of the Integrated Payload Stack (IPS) and Aft Payload Stack (APS).

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 U.S. Air Force [USAF] Missions)

3.1.3 National Reconnaissance Office (NRO)/Office of Space Launch (For NRO Missions)

3.1.1 USAF Space Wing(s)

3.2 Contractor Organizations

3.2.1 Launch Vehicle Contractor (LVC)

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

3.2.3 Launch System Integration Contractor (LSIC) (For NRO Missions)

15. TOTAL

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

(1 Data Item)

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

X002 B X TDP TM OTHER

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

EELV FA8811-18-R-0001

16. REMARKS

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 For NRO Missions: Mission Integration Requirements Review (MIRR) (Review the mission requirements and establish the verification plan)

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

4.4 Mission Verification Review (MVR) (Critical design review for mission integration)

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

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

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

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

4.9 Pre-Launch Readiness Review (Establishes readiness of launch system to proceed into countdown operations)

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

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

4.12 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) (For NRO missions) (Launch site readiness for ground operation to integrate spacecraft onto the launch vehicle)

5.5 Other Mission-related working groups per the PWS (e.g. Wing LRR, IRR, etc)

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 Rehearsal Anomaly Team (RAT)

6.7 Other Contractor Mission-related working groups (Any other working group necessary due to the nature of the mission)

7.0 Integration Tasks and Responsibilities

7.1 Space Vehicle (SV) Information. Provide a chronological tabular listing of data required from the Space Vehicle Contractor by the LVC; examples include SV interface requirements, SV computer-aided design /loads models, analyses results required for input to integrated analyses.

7.2 Launch Vehicle Information. Provide a chronological tabular listing of the information/reports developed during the mission integration process. (Key products including analyses, reports, requests, schedule, and other documentation or data. May require two Couple Loads Analyses at different times.)

7.3 Mission Integration Control Documents. Provide the list of mission integration control documents the contractor is responsible for preparation, distribution, and maintenance of. Provide the process/plan for maintaining configuration control of these documents.

7.4 Interface Control Document (ICD) and Verification Process. Provide a description of the ICD, the Contractor’s process for development, and verification of the ICD.

Appendix A: Entry/Exit Criteria for Key Integration Meetings Appendices as needed for Definitions, Terms, Abbreviations and Acronyms”

c. Delete 5. Media Requirements.

2. (BLKs 12 and 13)

a. Submit draft 90 days after contract award (Milestone #3) for Government review and comment.

b. Submit final 30 calendar days after receipt of Government comments for Government approval.

c. Submit updates to incorporate changes to the document process or upon Procurement Contracting Office direction for Government approval.

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

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

BX09 System/Segment Interface Control Specification Mission Interface Control Document (ICD)

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

DI-SESS-81314A/T Performance Work Statement, Para 3.4.5 SMC/LEG

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT BLK 16 BLK 16 b. COPIES

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

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A N/A BLK 16 Draft Reg Repro

16. REMARKS See Distribution List

1. (BLK 4):

a. 2. Format, Replace first two sentences with “The interface specification shall be prepared in an electronic format and printable on 8 ½ x 11” paper (metric size A4). It may be a multi-part electronic document.”

b. Replace 2.1.1 with “2.1.1 Document number. The document number shall appear on the title page.”

c. Replace 2.1.2 with “2.1.2 Date. The document issue data (Baseline/Revision Number and Issue Date) shall appear on the title page.”

d. Replace 2.1.3 with “2.1.3 Title. The document title shall appear on the title page stating the nomenclature of the interfacing items.”

e. Delete 2.1.4.

f. Delete 2.2.1.

g. Replace 2.4 with:

“Section 3.0, Requirements. This section provides the detailed description of the interface requirements. Each interface shall be separately covered in its own subsection, and include:

a. Space Vehicle (SV) Configuration (For U.S. Air Force [USAF] Missions)

b. Mission Parameters

c. Launch Vehicle (LV) Configuration

d. SV/LV Interface Requirements

e. Space Vehicle Handling and Processing Requirements

Include mission-specific payload systems weight capability for the mission and payload fairing (PLF) selected and specific mission design constraints.”

h. Replace 2.5 with:

“Section 4.0, Verification. This section shall identify and define the following:

a. Philosophy of Verification to include Do No Harm for Fully Integrated Propulsive Evolved Expendable Launch Vehicle Secondary Payload Adapter [ESPA] on Launch Vehicle, Integrated Payload Stack and Aft Payload Stack.

b. Verification Methods

c. Verification Matrix” 15. TOTAL

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

(1 Data Item)

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

X002 B TDP X TM OTHER

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

EELV FA8811-18-R-0001

16. REMARKS

i. Replace 2.6 with: “Section 5.0, Notes. This section shall include Definitions, Abbreviations, Acronyms, and Symbols.”

j. Delete Figure 1 Replace 3. with “Appendix A – This appendix shall include the Electrical Interfaces. Appendix B – This appendix shall include the Mechanical Interfaces. Appendix C – This appendix shall include the Requirements Traceability.”

k. Delete 3.1–3.3

2. (BLK 8): Signatures by 4-Party Technical Team

a. For USAF Missions: LV Contractor, LV Government Program Office, SV Contractor/Launch System Integration Contractor (LSIC), and SV Customer Program Office, at a minimum, constitutes Government approval of the Mission Interface Control Document (ICD).

b. For National Reconnaissance Office Missions: LV Contractor, Office of Space Launch (OSL) Mission Manager, OSL Contracting Officer’s Technical Representative, and LSIC constitutes Government approval of the Mission ICD

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

a. Submit first draft of the Baseline Mission ICD no later than (NLT) Authority to Proceed + 3 months (Milestone #3). No Government approval is required.

b. Submit second draft NLT Launch – 12 months for Government approval.

c. Submit Final 30 calendar days after 4-Party technical Team signature to be formalized by bi-lateral contract modification.

d. Submit revisions as necessary, taking into account the number of approved changes to be formalized by bi-lateral contract modification.

(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,…