03_Attachment_1_PWS.pdf

ATTACHMENT 1

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

COMPETITIVE LAUNCH SERVICES

PERFORMANCE WORK STATEMENT (PWS)

FA8811-18-R-0001

31 January 2018

Department of the Air Force Space and Missile Systems Center

Launch Systems Enterprise Directorate Los Angeles Air Force Base, California

Table of Contents 1

1 EVOLVED EXPENDABLE LAUNCH VEHICLE LAUNCH SERVICES ....................................... 1 2

1.1 DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES ................................................. 1 3

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY ..................................................... 2 4

1.2.1 Government ........................................................................................................................... 2 5

1.2.2 United States Government Team .......................................................................................... 2 6

1.2.3 Space Vehicle Team .............................................................................................................. 2 7

1.2.4 OSL Mission Management Team ......................................................................................... 2 8

1.2.5 Electronic Data Access ......................................................................................................... 2 9

2 APPLICABLE DOCUMENTS ............................................................................................................. 3 10

2.1 COMPLIANCE DOCUMENTS ................................................................................................... 3 11

2.2 REFERENCE DOCUMENTS ...................................................................................................... 3 12

2.3 DOCUMENTATION DE-CONFLICTION ................................................................................. 3 13

3 SPACE LAUNCH SERVICE ............................................................................................................... 3 14

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS ...................................................... 4 15

3.1.1 Launch System Data ............................................................................................................. 4 16

3.1.2 Launch System Electronic Data Access Training ................................................................. 4 17

3.1.3 Data Accession List .............................................................................................................. 4 18

3.1.4 Program Management Data Reporting .................................................................................. 4 19

3.1.5 Program Management Reviews ............................................................................................ 5 20

3.1.6 Launch Manifesting Process ................................................................................................. 5 21

3.1.7 System Safety Program ......................................................................................................... 6 22

3.1.8 Range Safety ......................................................................................................................... 6 23

3.1.9 Safety Training ...................................................................................................................... 7 24

3.1.10 Launch System Familiarization Course ................................................................................ 7 25

3.1.11 Program Protection ............................................................................................................... 8 26

3.1.12 Operations Security ............................................................................................................... 8 27

3.1.13 Anti-Terrorism ...................................................................................................................... 8 28

3.1.14 Environmental Requirements ................................................................................................ 9 29

3.1.15 Hazardous Materials ............................................................................................................. 9 30

3.1.16 Incident and Discrepancy Reporting ................................................................................... 10 31

3.1.17 Public Affairs Activities ...................................................................................................... 10 32

3.1.18 Program Milestone Reviews ............................................................................................... 11 33

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS ........................................................ 11 34

3.2.1 Technical Interchange Meetings ......................................................................................... 11 35

3.2.2 Contractor Engineering Database ....................................................................................... 11 36

3.2.3 Systems Engineering Boards and Processes ....................................................................... 11 1

3.2.4 Launch Vehicle Configuration Change Reporting .............................................................. 12 2

3.2.5 Non-Recurring Design Validation and Processes ............................................................... 15 3

3.2.6 Launch System Testing (component, unit, subsystem, system, launch site) ....................... 16 4

3.2.7 Launch System Parameters ................................................................................................. 16 5

3.2.8 Post-Flight Data Review ..................................................................................................... 16 6

3.2.9 Aging and Surveillance Program ........................................................................................ 17 7

3.2.10 Performance Capabilities Guide ......................................................................................... 17 8

3.2.11 Quality Management ........................................................................................................... 17 9

3.2.12 Support to LSIC Meetings and Reviews ............................................................................. 18 10

3.2.13 Support to SV Team Meetings and Reviews ........................................................................ 18 11

3.2.14 Reliability Program ............................................................................................................. 18 12

3.3 LAUNCH VEHICLE PRODUCTION ....................................................................................... 18 13

3.3.1 Launch Vehicle Hardware and Software ............................................................................ 19 14

3.3.2 Mission-Unique Requirements ........................................................................................... 19 15

3.4 MISSION INTEGRATION ........................................................................................................ 21 16

3.4.1 Mission Integration Data ..................................................................................................... 21 17

3.4.2 Principal Mission Manager Interface .................................................................................. 22 18

3.4.3 Mission Integration Management ....................................................................................... 22 19

3.4.4 Payload (Integrated Payload Stack) Integration Information ............................................. 26 20

3.4.5 Interface Control Document ................................................................................................ 27 21

3.4.6 Mission Design and Analyses ............................................................................................. 28 22

3.4.7 Orbital Debris Mitigation .................................................................................................... 30 23

3.4.8 Integrated (Payload [Integrated Payload Stack]/Launch Vehicle) Operations Planning ... 30 24

3.4.9 Launch Rehearsal Support .................................................................................................. 33 25

3.4.10 Third Integrated Crew Exercise (ICE 3) ............................................................................. 35 26

3.4.11 Mission Interface Control Document Requirements Verification ...................................... 35 27

3.4.12 Flight Hardware Interface Checks ...................................................................................... 35 28

3.4.13 Ground Hardware Interface Checks .................................................................................... 36 29

3.4.14 Launch Safety Collision Avoidance and Radio Frequency Power Impingement Data ...... 36 30

3.4.15 Launch Range Coordination ............................................................................................... 36 31

3.4.16 Mission-Unique Tests ......................................................................................................... 36 32

3.5 LAUNCH OPERATIONS .......................................................................................................... 36 33

3.5.1 Launch Site Operations and Support Services .................................................................... 37 34

3.5.2 Launch Infrastructure .......................................................................................................... 48 35

3.5.3 Base and Range Support ..................................................................................................... 49 36

3.5.4 Mission Commodities ......................................................................................................... 49 1

3.6 SUPPORT TO GOVERNMENT SPACE FLIGHT WORTHINESS......................................... 49 2

3.6.1 Contractor Support to Government Space Flight Worthiness Meetings ............................. 50 3

3.6.2 USG Team Participation in Contractor Production and Engineering Forums .................... 52 4

3.6.3 Contractor Support to SMC/LE Issue Closure .................................................................... 52 5

3.6.4 Launch Vehicle As Designed Configuration List (CDRL AX09) ...................................... 53 6

3.6.5 Government Hardware Review (CDRL AX12) .................................................................. 54 7

3.6.6 Launch Vehicle Production Cycle Review Support ............................................................ 56 8

3.6.7 OSL Independent Validation and Verification ................................................................... 56 9

3.6.8 NRO/OSL Launch Mission Assurance Team (MAT) ........................................................ 57 10

3.6.9 National Reconnaissance Office Mission Integration Group (MIG) .................................. 58 11

3.7 QUICK REACTION AND ANOMALY RESOLUTION .......................................................... 59 12

3.8 MISSION-UNIQUE LAUNCH VEHICLE SERVICES ............................................................ 59 13

APPENDIX A: GLOSSARY OF TERMS ................................................................................................. 61 14 APPENDIX B: ACRONYMS AND ABBREVIATIONS .......................................................................... 77 15 APPENDIX C: COMPLIANCE DOCUMENTS ....................................................................................... 83 16 APPENDIX D: REFERENCE DOCUMENTS .......................................................................................... 88 17 APPENDIX E: UNITED STATES GOVERNMENT TEAM CALL-OUTS ............................................ 93 18 APPENDIX F: NON-RECURRING design validation DATA PRODUCTS .......................................... 100 19 APPENDIX G: GOVERNMENT HARDWARE REVIEW FORMAT ................................................... 110 20 APPENDIX H: PROGRAM MILESTONE REVIEWS ........................................................................... 114 21

APPENDIX I: GOVERNMENT PROGRAM CONTRACTS REQUIRING INTERFACE WITH 22

AEROSPACE Federally Funded Research and Development Center (FFRDC), PRIME, and SUPPORT 23 CONTRACTORS ..................................................................................................................................... 121 24

LIST OF TABLES 26

Table 1: Substantial Change Definition ...................................................................................................... 13 27

Table 2: Mission Integration Milestone Reviews ....................................................................................... 23 28

Table 3: Mission Integration Working Groups and Reviews ...................................................................... 24 29

Table 4: Mission Integration Working Group ............................................................................................. 25 30

Table 5: Mission Specific Analyses ............................................................................................................ 29 31

Table 6: Space Flight Worthiness Meetings ............................................................................................... 50 32

This Page Intentionally Left Blank.1

Performance Work Statement FA8811-18-R-0001

1 EVOLVED EXPENDABLE LAUNCH VEHICLE LAUNCH SERVICES 1

1.1 DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES 2

This Performance Work Statement (PWS) defines the launch services the Contractor will 3 perform for United States (U.S.) Air Force (USAF) and National Reconnaissance Office 4 (NRO) missions in order to provide a Launch Vehicle (LV) and deliver a Payload (PL) (aka an 5 Integrated Payload Stack [IPS]) as well as the Aft Multi-Payload Stack (APS) into their 6 intended orbit(s) managed by Air Force Space Command, Space and Missile Systems Center 7 (AFSPC/SMC). This contract is for the procurement of Air Force missions and NRO 8 missions, to include multi-manifest missions. NRO and SILENTBARKER references appear 9 in grey text. Within the grey text, double-underlined references apply to NRO, 10 SILENTBARKER and Space-Based Infrared System (SBIRS) missions. Multi-manifest-only 11 references within this PWS appear in italicized text. Multi-manifest missions are those that 12 include more than one space vehicle (SV). 13

The Contractor shall perform all launch service tasks necessary to deliver payloads to defined 14 orbital parameters in compliance with mission requirements as described in Section 3 (Space 15 Launch Service). The launch service shall support missions to all orbital parameters, 16 consistent with vehicle configuration capabilities and Range Safety restrictions. The 17 Contractor shall provide launch services, which comply with all Range Safety requirements. 18 The Contractor shall make all arrangements with the responsible authorities for the required 19 Range Safety authorization and support for vehicle processing; integrated payload/vehicle 20 processing, launch; and launch site maintenance and modifications. 21

The requirements in Section 3 (Space Launch Service) of this PWS are divided into functional 22 areas: 3.1 (Program Management Functions and Tasks), 3.2 (Systems Engineering Functions 23 and Tasks), 3.3 (Launch Vehicle Production), 3.4 (Mission Integration), 3.5 (Launch 24 Operations), 3.6 (Support to Government Space Flight Worthiness), 3.7 (Quick Reaction and 25 Anomaly Resolution), and 3.8 (Mission-Unique Launch Vehicle Services). 26

The PWS tasks for each launch service effort described in this PWS may be grouped 27 chronologically: (1) establish the launch vehicle configuration, (2) qualify the flight 28 configuration, (3) produce the flight launch vehicle, and (4) conduct the launch campaign. 29

The chronological flow of the launch service first begins with (1) the Contractor establishing 30 the launch vehicle configuration in accordance with the systems engineering functions and 31 tasks of Section 3.2 (Systems Engineering Functions and Tasks), culminating in submittal of 32 Contract Data Requirements List (CDRL) AX09 with the proposed configuration changes 33 against the certified/approved launch vehicle in accordance with paragraph 3.2.4 (Launch 34 Vehicle Configuration Change Reporting). Second, (2) analysis and qualification is conducted 35 for the proposed launch vehicle configuration while performing the systems engineering 36 functions and tasks of Section 3.2 (Systems Engineering Functions and Tasks). Third, 37

(3) production of the flight vehicle is accomplished by performing tasks of Section 3.3 38 (Launch Vehicle Production). Finally, (4) the launch campaign is conducted with the 39 performance of Section 3.4 (Mission Integration) and Section 3.5 (Launch Operations). 40

During post-award contract execution, the contractor may request, in writing, Government 41 approval to allow relevant activities, documentation, and information developed under other 42 contract(s)/agreement(s) with the Government for National Security Space (NSS) launch 43 services missions, to be used to satisfy requirements of this PWS. 44

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY 1

A glossary of definitions for terms used in and applicable to this PWS is provided in Appendix 2 A. An Acronyms and Abbreviations list is provided in Appendix B. 3

1.2.1 Government 4

The term “Government” refers to Department of Defense (DoD) personnel, including 5 military and Government civilians. 6

1.2.2 United States Government Team 7

The term “United States Government [USG] Team” refers to the Air Force Space and 8 Missile Systems Center/Launch Systems Directorate (SMC/LE) program office and Air 9 Force Program Executive Officer/Space office personnel, but also includes the 10 Aerospace Federally Funded Research and Development Center (FFRDC), SMC/LE 11 Systems Engineering and Integration (SE&I) Contractors, SMC/LE Systems 12 Engineering and Technical Assistance (SETA) support Contractors, SMC/LE Advisory 13 & Assistance Services, the NRO/Office of Space Launch (OSL), NRO/OSL SETA 14 support Contractors, NRO/OSL Independent Verification and Validation (IV&V) 15 support Contractors, the SMC Independent Readiness Review Team, Defense Security 16 Service, Defense Information Systems Agency, Defense Contract Management 17 Agency, Defense Contract Audit Agency, 30th Space Wing (30 SW), 45th Space Wing 18 (45 SW), and other organizations as designated by SMC/LE Procuring Contracting 19 Officer (PCO). Refer to Appendix I for Government Program Contracts Requiring 20 Interface with Aerospace Federally Funded Research and Development Center 21 (FFRDC), Prime, and Support Contractors. Estimates of the number of USG Team 22 individuals associated with specific requirements in this PWS are listed in Appendix E 23 (United States Government Team Call-Outs). 24

1.2.3 Space Vehicle Team 25

For USAF missions, the term “SV Team” refers to the SV 26

Directorate(s)/Program Office(s) and Space Vehicle Contractor(s) (SVC) 27 personnel, but also includes the Aerospace FFRDC, the SV’s SE&I 28 Contractor and SETA support Contractors, Launch System Integration 29 Contractor (LSIC) (if applicable), the SV’s Payload Processing Facility (PPF) 30 personnel, and Multi-Manifest Systems Integrating Contractor(s) (MMSICs) 31 (if applicable) 32

For NRO missions, the term “SV Team” refers to the SV System Program 33 Office (SPO), LSIC, SVC and Multi-Manifest Integrating Contractor 34 (MMSIC) (if applicable). The interface with the SV Team is the NRO/OSL 35 and the LSIC. 36

1.2.4 OSL Mission Management Team 37

For NRO missions, the term “OSL MMT” refers to the OSL Government Mission 38 Manager and respective team, which includes OSL SETA support Contractors, and 39 Aerospace FFRDC. 40

1.2.5 Electronic Data Access 41

The term “(Electronic Data Access)” refers to the ability of the USG Team and SV 42 Government Teams to remotely access the data via the Contractor’s electronic data 43 repository host systems for the purpose of reviewing, uploading, or downloading 44 specific, identified program-related data on Contractor host systems. The Contractor 45 shall be responsible for providing access to the data, administering user accounts, and 46 ensuring the integrity of the data. The Contractor shall provide the capabilities for the 1 USG Team to subscribe to be notified of any updates to delivered data products on the 2 Contractor’s electronic data repositories. The Contractor shall provide the server/folder 3 location of data and a file/folder directory and confirm appropriate permissions have 4 been provided. If the USG Team is unable to remotely access electronic data through 5 the Contractor’s systems, the Contractor shall deliver the data upon the USG Team’s 6 request. Data identified in this PWS shall be provided via electronic access unless 7 otherwise specified in the CDRL descriptions. All data accessed is considered 8 delivered to the Government for the purposes of Defense Federal Acquisition 9 Regulation Supplement 252.227-7015. 10

2 APPLICABLE DOCUMENTS 11

2.1 COMPLIANCE DOCUMENTS 12

The Contractor shall comply with the compliance documents listed in Appendix C as approved 13

IAW CDRL BX05.. 14

2.2 REFERENCE DOCUMENTS 15

The reference documents that are applicable to this PWS are listed in Appendix D. 16

2.3 DOCUMENTATION DE-CONFLICTION 17

If any conflict or inconsistency exists between the signed mission Interface Control Document 18 (ICD), the MRA or Interface Requirements Document (IRD) (for NRO missions), the 19 Standard Interface Specification (SIS), or this PWS, the mission ICD shall be given 20 precedence. Other documents shall be given precedence in accordance with Federal 21 Acquisition Regulation (FAR) 52.215-08 or FAR 52.212-04(s), as applicable. 22

3 SPACE LAUNCH SERVICE 23

The Government requires the services of an integrated Launch System to meet NSS launch needs. 24 Space Launch Services for NSS missions include LV production and transportation, mission 25 integration, launch operations, support to independent Government mission assurance, base and 26 range support, mission commodities, all associated program management and systems engineering 27 functions and tasks, and any required special studies as defined in PWS Section 3.7 (Quick Reaction 28 and Anomaly Resolution). 29

The Contractor shall provide Space Launch Services for NSS missions in accordance with the 30 performance requirements stated in the Evolved Expendable Launch Vehicle (EELV) System 31 Performance Requirements Document (SPRD), EELV Standard Interface Specification (SIS), MRA 32 (for USAF only), IRD (for NRO only), and mission ICD. The Contractor shall control, document, 33 and provide the USG Team continuous access and insight into its processes and assessments of 34 progress and performance of all Space Launch Service requirements, provide continuous access to 35 the Contractor’s command media, and support the USG’s Independent Mission Assurance activities. 36

For each launch service provided under this contract, the Contractor shall provide the required 37 payload mass-to-orbit performance margin in accordance with the SPRD, the MRA or IRD (for 38 NRO missions), and the mission ICD. The Government shall own any excess performance margin 39 beyond that required to meet the mission requirements unless the Government approves the release 40 of such margin. Any release of margin shall be documented in the applicable mission ICD and in 41 FAR 52.212-4(y). The Contractor shall facilitate Government risk assessment of any secondary 42 objective by delivering CDRL BX26. Any excess performance margin released by the Government 43 for use by the Contractor can be revoked per conditions stated in FAR 52.212-4(y). 44

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 1

The Contractor shall identify a lead Program Manager and perform all program management 2 functions and tasks necessary to deliver launch services and to satisfy the requirements for the 3 mission consistent with operational quality, safety, security, and environmental standards. The 4 program management function of this contract shall provide insight to the Government for all 5 technical and programmatic activities performed under this contract. 6

3.1.1 Launch System Data 7

The Contractor shall provide and maintain the USG Team access to all Launch System 8 Data supporting this contract residing on the Contractor’s systems throughout the 9 contract period of performance. The Contractor shall communicate with the USG 10 Team any updates (to include manufacturing, testing, operational, or process changes) 11 to delivered Launch System data products as soon as possible but no later than 24 12 hours, or 1 business day, after the updates. Launch system data includes access to fleet 13 data at all sites. Fleet surveillance is essential to the Space Flight Worthiness 14 Certification process, which requires identification of hazards, assessments of risks, 15 mitigation measures, and acceptance of residual risks. Fleet- and mission-specific 16 launch system data are elements affecting the risk baseline accepted by the USG for 17 NSS missions. The Contractor shall notify the Government of any network outages or 18 system upgrades that could interrupt access to the systems. The Contractor shall 19 cooperate with the USG Team to develop a plan to implement this requirement. 20 (Electronic Data Access) 21

3.1.2 Launch System Electronic Data Access Training 22

The Contractor shall provide the USG Team Launch System Electronic Data Access 23 computer-based training as needed. Such training shall include, but is not limited to: 24 Work Authorizing Documents (WAD) access and feedback, anomaly/non-conformance 25 system, launch console data system, specification and engineering file management 26 system, and Contractor employee online training database. (Electronic Data Access) 27

3.1.3 Data Accession List 28

The Contractor shall maintain a list of data supporting this contract on a Data 29 Accession List (DAL). (CDRL AX01) 30

3.1.4 Program Management Data Reporting 31

The Contractor shall collect and report program data to SMC/LE by providing the 32 following: 33

A. Cost Data Summary Report (CDRL AX02) 34 B. Functional Cost-Hour Report (CDRL AX03) 35 C. Contractor Business Data Report (CDRL AX04) 36 D. Contractor Work Breakdown Structure (CDRL AX05) 37 E. Integrated Program Management Report – Integrated Master Schedule (IMS) 38

(CDRL AX06) 39

F. Small Business Utilization Report (CDRL AX14) 40

The Contractor shall report all Contractor labor hours (including subcontractor 42 labor hours) required for performance of services provided under this contract 43 via the secure data collection site (i.e., Enterprise-wide Contractor Manpower 44 Reporting Application [ECMRA]). The Contractor is required to completely 45 fill in all required data fields using the following Web address: 46 http://www.ecmra.mil. Reporting inputs will be for the labor executed during 1 the period of performance during each Government fiscal year (FY), which 2 runs from October 1 through September 30. While inputs may be reported 3 any time during the FY, all data shall be reported no later than (NLT) October 4 31 of each calendar year. Contractors may direct questions to the ECMRA 5 help desk. 6

3.1.5 Program Management Reviews 7

The Contractor shall schedule and conduct monthly Program Management Reviews 8 (PMRs) to: report development and production status, ensure schedules support 9 program objectives, review action items, review program schedules, and discuss any 10 issues. The intent of the PMR is to provide a forum for open dialog between the USG 11 Team and the Contractor. The Contractor shall provide the USG Team the PMR 12 briefing slides no later than 5 calendar days prior to the review or as agreed to by the 13 parties. SMC/LE and the Contractor will agree to the PMR agenda no later than 14 14 calendar days prior to the PMR or as agreed to by the parties. The PMR agenda shall 15 include a status of the following topics at a minimum: Programmatics, Business 16 Operations, Flight Manifest Status, Production Operations, Quality Metrics, 17 Configuration Management, Risk Management, Subsystem(s) Status, Mission 18 Integration Status, Non-Recurring Work Status (as applicable), Launch Operations, 19 Major Subcontractor(s) Performance (as applicable), and Wrap Up/Action Items. 20 PMRs will be planned for 3 hours but last no more than 1 business day. Locations may 21 rotate between Contractor and Government facilities. The USG team shall be invited to 22 major subcontractor PMRs or equivalent reviews. (Electronic Data Access) 23

On a quarterly basis in conjunction with a PMR, the Contractor shall brief the 24 USG team (including on-site residents) on the Contractor’s manufacturing and 25 production capabilities to include existing capabilities, ramp-up plans, rate 26 outputs, site overview, facility layouts, facility updates, production flow, and 27 production readiness status. 28

3.1.6 Launch Manifesting Process 29

The Contractor shall participate in the Government-led launch scheduling and 30 manifesting process to include the following reviews and meetings: a semi-annual 31 Current Launch Schedule Review Board, a semi-annual Government Integrated 32 Meeting, a monthly Senior Management Review, weekly launch manifest status 33 teleconferences, and a Contractor-led monthly manifest review. The Contractor should 34 assume a meeting length of 4 hours each. (Ref. Air Force Space Command Instruction 35

[AFSPCI] 13-1213) 36

The Contractor shall develop and provide the USG Team Launch Schedule 1 Option Assessments as part of the launch manifesting process. (Electronic 2 Data Access) 3

The Contractor shall provide the USG Team a Launch Slot Recommendation 4 and Launch Date Recommendation within the assigned launch period for 5 each launch mission in accordance with contract clause SMC—H006. 6

(CDRL BX01) 7

3.1.7 System Safety Program 8

The Contractor shall establish, implement, and maintain a System Safety Program in 9 accordance with Military Standard (MIL-STD)-882E (tailored consistent with 10 SMC-T-004). The Contractor shall provide a System Safety Program Plan and Safety 11 Assessment Report in accordance with MIL-STD-882E (tailored consistent with 12 SMC-T-004). (Electronic Data Access) (CDRLs BX02, BX03, and BX05) 13

The Government shall have access to the Contractor's Hazard Tracking 14 System (HTS) with appropriate controls on data management. The 15 Government shall receive and retain (at a minimum) “government purpose 16 rights” of all the data recorded in the HTS and any other items (i.e., studies, 17 analyses, test data, notes or similar data) generated in the performance of the 18 contract with respect to the HTS. 19

3.1.8 Range Safety 20

The Contractor shall coordinate the tailoring of Air Force Space Command Manual 21 (AFSPCMAN) 91-710 for all missions under this contract with SMC/LE, NRO/OSL, 22 and Range Safety prior to formal submittal. The Contractor shall coordinate relief 23 requests (e.g., Equivalent Level of Safety, or Waivers) for all missions under this 24 contract with SMC/LE, NRO/OSL, and Range Safety prior to formal submittal. 25 (Electronic Data Access) (CDRL BX05) 26

The launch system shall utilize Global Positioning System (GPS) as one of the 1 two mandatory Range Safety tracking data sources. The launch system’s 2 on-board GPS shall comply with the requirements documented in the 3 approved Range Commander’s Council (RCC) 324-11. The Contractor shall 4 coordinate RCC 324-11 tailoring requests, equivalent level of safety 5 certifications, and non-compliance waiver relief requests for all missions 6 under this contract with SMC/LE, NRO/OSL, and Range Safety prior to 7 formal submittal. 8

The launch system’s Autonomous Flight Safety System, or flight safety 9 system using a secure command system employing National Security 10 Agency-approved cryptography in accordance with DoD Instruction (DoDI) 11

8581.01 Enclosure 3, paragraph a.4.e., shall comply with the requirements 12 documented in the approved RCC 319-10 (T). The Contractor shall 13 coordinate RCC 319-10 (T) tailoring requests, equivalent level of safety 14 certifications, and non-compliance waiver relief requests for all missions 15 under this contract with SMC/LE, NRO/OSL, and Range Safety prior to 16 formal submittal. (CDRL BX05) 17

3.1.9 Safety Training 18

The Contractor shall provide any Contractor-required safety training to USG Team and 19 SV Team personnel for Contractor facilities used in performance of this contract to 20 ensure USG Team access to those facilities. 21

3.1.10 Launch System Familiarization Course 22

The Contractor shall provide the USG Team an instructor-led Launch System 23 Familiarization (FAM) Course up to three times a calendar year to provide training to 24 the Government team supporting NSS missions with the launch service provider: twice 25 at the SMC/LE’s facility, and once at the launch base for this contract. The FAM 26 Course shall be conducted in two parts: a 1-day overview for non-technical personnel 27 and a 2-day in-depth engineering system familiarization. The level of detail covered by 28 the FAM course training materials shall be provided by the Contractor in the initial 29 CDRL submittal and approved by the Government for the final CDRL submittal prior 30 to conducting the FAM course. At a minimum, the FAM Course shall include 31 familiarization on the following: LV configurations; propulsion, avionics, and 32 structures systems; manufacturing capabilities; manufacturing facility and processes; 33 launch site facilities, critical ground mechanical, structural, and fluid/gas systems; 34 facility systems and capabilities; launch site/ground command, control, and 35 communications; power systems; flight controls; guidance, navigation, ground and 36 airborne ordnance systems; ground electrical systems; control/telemetry; launch 37 process flow; contractor organizational structure; flight safety systems; launch commit 38 sequence; performance capabilities, personnel roles and responsibilities, and types of 39 Contractor engineering and launch documentation; system-level testing; integrated 40 testing; flight heritage; launch vehicle evolution; basic performance parameters; mass-41 to-orbit capabilities; flight and ground software; quality management; supply chain 42 management; and systems engineering including issue tracking, requirements 43 management, change management, and risk management. The Contractor shall provide 44 a self-study guide report to accompany the training course consisting of the training 45 materials, test questions, and answers. (CDRL AX07). 46

3.1.11 Program Protection 1

The Contractor shall develop, provide, implement, and maintain, a Program Protection 2 Implementation Plan in accordance with the EELV Program Protection Plan (PPP) and 3 DoDI 8582.01. (CDRL AX08) 4

The Contractor shall provide support to the USG Team in annual EELV 5 Program Protection Surveys at all Contractor facilities in accordance with the 6

EELV PPP. 7

The Contractor shall attend and support the quarterly EELV System Security 8 Working Group and one security-related meeting per month in accordance 9 with the EELV PPP (e.g., Information Technology [IT] Security Breach or 10 Unauthorized Information Distribution resolutions). 11

The Contractor shall provide support to the USG Team in the development of 12 the EELV PPP Contractor-specific Annex. The Contractor’s support to the 13 USG Team in the development of the EELV PPP shall include providing the 14 LV-specific and supporting Ground system architecture specific information 15 necessary to document, identify, assess, and mitigate security related 16 vulnerabilities and risks. 17

The Contractor shall protect Information Systems (IS) processing classified 18 data in accordance with DoD 5220.22-M and applicable supplements. 19

The Contractor shall obtain or maintain International Organization for 20 Standardization/International Electrotechnical Commission (ISO/IEC) 21 27000/02 (T) certification. 22

3.1.12 Operations Security 23

The Contractor shall develop, implement, and maintain an Operations Security 24 (OPSEC) program in accordance with contract Attachment 2, DoD Contract Security 25 Classification Specification (DD254). (Ref. Air Force Instruction [AFI] 10-701 and the 26 EELV OPSEC Plan). 27

3.1.13 Anti-Terrorism 28

The Contractor shall implement and maintain an Anti-terrorism (AT) program for 29 activities at Cape Canaveral Air Force Station (CCAFS), Kennedy Space Center 30 (KSC), and Vandenberg Air Force Base (VAFB) as appropriate. (Ref. AFI 10-245) 31 The Contractor shall ensure SMC/LE, NRO/OSL, and approval prior to taking any 32 action regarding anti-terrorism requirements requested by the 30 SW Operations 33 Security Office or 45 SW/Anti-Terrorism Office (ATO) that change or add any 34 additional anti-terrorism requirements to this PWS paragraph and subparagraphs. 35

Meeting Support: The Contractor shall identify site security leads to support 36 one meeting per year. 37

Program Reviews: The Contractor shall perform an in-house Annual Review 38 of its AT program, which shall be documented in accordance with the host 39 Wing ATO checklist. 40

Training: The Contractor shall perform annual training utilizing SMC/LE AT 41 training materials as a guideline. The Contractor shall create a Corporate 42

Annual Training Letter stating that all site personnel have completed their 1 individual Anti-Terrorism training. 2

Force Protection Condition (FPCON) Checklists: The Contractor shall utilize 3 site-specific FPCON checklists provided by SMC/LE at each launch site. 4

Random AT Measures (RAMs): The Contractor shall perform prescribed 5 RAMs or alternate RAMs that are preapproved by SMC/LE (up to five per 6 month). Completed RAMs shall be documented in a format prescribed by 7 SMC/LE and reported quarterly to the Host Wing ATO. 8

Mission Essential Personnel: The Contractor shall create and maintain a 9 “Mission Essential Personnel” list and an “Emergency Essential Personnel” 10 list for higher FPCON levels (Charlie and Delta) and other emergency 11 situations at each launch site. The Contractor shall provide these lists to the 12 appropriate launch site personnel in advance of any emergency situation and 13 in the event of any changes. 14

3.1.14 Environmental Requirements 15

The Contractor shall comply with environmental requirements in accordance with 16 AFSPCMAN 91-710 as applicable and all relevant and applicable Federal, State, and 17 local environmental laws, regulations, and executive orders, and base regulations as 18 documented in the appropriate license, lease, Commercial Space Operations Support 19 Agreements (CSOSA), and CSOSA annexes. 20

The Contractor shall provide to the USG Team each environmental impact 21 analysis document, environmental report, and applicable meeting notices 22 related to or that impact the approved/certified EELV launch system. This 23 includes associated correspondence sent to or received from environmental 24 regulatory agencies and the host Wing but does not include informal 25 telephone and e-mail communication. (Electronic Data Access) 26

The Contractor shall include SMC/LE in the coordination process with the 27 host Wing and the environmental regulatory agencies relating to the 28 application, development, or modification of permits or required 29 environmental compliance plans, environmental cleanup actions, or other 30 major efforts subject to environmental laws and regulations. The Contractor 31 shall provide information to the on-site USG Team environmental 32 representatives, during the coordination process, to ensure that the USG 33 Team is aware of the risks and alternatives that are evaluated or accepted 34 during this process. (Electronic Data Access) 35

The Contractor shall provide data needed to allow SMC/LE to conduct the 36 Environmental Impact Analysis Process in accordance with National 37 Environmental Policy Act and Executive Order 12114, Environmental Effects 38 Abroad of Major Federal Actions, dated 4 January 1979. 39

3.1.15 Hazardous Materials 40

The Contractor shall develop, provide, maintain, and comply with a hazardous 41 materials management plan in accordance with AFSPCMAN 91-710 and Task 108 of 42 MIL-STD 882-E. (CDRL BX04) (Ref. National Aerospace Standard 411) 43

3.1.16 Incident and Discrepancy Reporting 1

The Contractor shall maintain an incident and discrepancy reporting system. The 2 Contractor shall notify the USG Team, via Contractor-identified internal reporting 3 systems, of all incidents and discrepancies. 4

The Contractor shall notify the USG Team of incidents and discrepancies 5 related to this mission during the execution of this contract that involve 6

(1) loss of life or severe personal injury as defined per Occupational Safety 7 and Health Administration reporting requirements; (2) damage to any flight 8 hardware or Critical Ground Support Equipment (GSE); or (3) damage to 9 Critical GSE occurring during vehicle build, test, transportation, processing, 10 or facility readiness operations. The notification shall be provided as soon as 11 operationally possible, but no later than 48 hours (post-emergency response 12 and safety hazard securing) and in accordance with already-established 13 Contractor reporting procedures. The Contractor shall provide the status of 14 ongoing investigations, Contractor incident root cause data, and 15 determination and associated corrective actions. (Electronic Data Access) 16

The Contractor shall notify the onsite USG Team as soon as operationally 17 possible (post emergency response) of hazardous materials and waste releases 18 that require coordination with Governmental regulatory agencies. 19

The Contractor shall report within 48 hours of an event’s occurrence any 20 incidents and any discrepancies that may be or are a major non-conformance 21 or lead to any of the following: (a) actual or potential delay to the ship date of 22 flight hardware, (b) out-of-position (OOP) work transferred to the launch site, 23

(c) changes to the IMS, (d) waivers or exceptions to test or verification 24 requirements, or (e) impact a scheduled launch date. The Contractor shall 25 provide the status of ongoing investigations, Contractor incident root cause 26 data, and determination and associated corrective actions. For all other minor 27 incidents and discrepancies, notification shall be no later than 14 calendar 28 days of an event’s occurrence and status reporting will be determined by 29 SMC/LE on a case-by-case basis. 30

3.1.17 Public Affairs Activities 31

The Contractor shall support Public Affairs activities by coordinating with SMC/LE 32 and the Space and Missile Systems Center Public Affairs office (SMC/PA). The 33 Contractor shall coordinate press statements, press releases, or any related public affairs 34 items with SMC/PA prior to release to the general public. 35

For NRO missions, the Contractor shall support Public Affairs activities by 36 coordinating with the NRO Office of Public Affairs (OPA). The Contractor shall 37 submit all press statements, press releases, broadcast material, videos, podcasts, 38 photographs, social media plans/posts, or any related public affairs items to the NRO 39 OPA for approval prior to release to the press or general public. The Contractor shall 40 follow NRO OPA guidance regarding timing of public and media releases. The design 41 for memorabilia (i.e., coins, patches, logos) must be approved by the Director, NRO. 42 The Contractor shall submit proposed designs to NRO OPA and receive written prior 43 approval prior to production of any material. 44

3.1.18 Program Milestone Reviews 1

The Contractor shall conduct and provide USG Team participation in the Program 2 Milestone Reviews as defined in Appendix H (Program Milestone Reviews). These 3 reviews may be combined with Contractor reviews with USG approval. The 4 Contractor shall provide the USG Team the briefing slides for each Program Milestone 5 Reviews no later than 5 calendar days prior to the review or as agreed to by the parties. 6

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 7

In order to ensure the successful completion of this mission and associated tasks required for 8 mission success, the Contractor shall perform systems engineering functions and tasks 9 necessary to deliver launch services consistent with operational safety, suitability, and 10 effectiveness and Environmental Safety and Occupational Health guidance on EELV systems. 11 In order to ensure the Government can accomplish its mission assurance functions and system 12 engineering tasks, the Contractor shall maintain and provide the USG Team insight into the 13 systems engineering processes supporting the launch service which are consistent with the 14 EELV System Engineering Plan referenced in Appendix D. In order to facilitate smooth and 15 unimpeded communication between the USG Team and the Contractor, the Contractor shall 16 identify a technical Point of Contact (POC) (vehicle Chief Engineer or equivalent) to work 17 with the USG counterpart to manage the activities in this section. 18

3.2.1 Technical Interchange Meetings 19

The Contractor shall invite the USG Team to Technical Interchange Meetings or any 20 Contractor-equivalent boards and make available any meeting documentation materials. 21 (Electronic Data Access) 22

3.2.2 Contractor Engineering Database 23

The Contractor shall provide the USG Team access to the Contractor’s non-24 conformance, drawings, configuration control, risk, hazard tracking system, production, 25 launch operations, risk management, change management, quality management, test 26 database, design repositories, and other similar engineering databases necessary to 27 support space flight worthiness (SFW) certification and in plant technical surveillance 28 by the USG Team. (Electronic Data Access) 29

3.2.3 Systems Engineering Boards and Processes 30

The Contractor shall conduct and support USG Team participation in Launch System: 31 Risk Management Boards; Engineering Review Boards (ERB); Anomaly Review 32 Boards (ARB); Technical Review Boards; Corrective Action Boards; Change Control 33 Boards for technical issues; Material Review Boards; Failure Review Boards; Parts, 34 Materials, and Processes Control Boards; Systems Safety Groups (SSGs); Preliminary 35 Design Review; Critical Design Review; Functional and Physical Configuration 36 Audits, System Verification Review; Production Readiness Review; Test Readiness 37 Review; Shipping Readiness Reviews; or Contractor equivalent boards or Contractor-38 equivalent processes. For recurring review boards, the Contractor shall provide 39 electronic invitations to the USG Team no later than 10 calendar days in advance of the 40 board. For all other review boards the Contractor shall provide electronic invitations to 41 the USG Team as soon as possible after the board is scheduled. The Contractor shall 42 provide the USG Team entrance and exit criteria for System Engineering boards, as 43 required by their command media. The Contractor shall provide virtual participation 1 capability for Systems Engineering boards. (Electronic Data Access) 2

3.2.4 Launch Vehicle Configuration Change Reporting 3

The Contractor shall provide the USG Team proposed configuration changes to be 4 implemented on the USG certified/approved launch vehicle configuration. The 5 Contractor shall provide the USG certified/approved launch vehicle configuration at the 6 Mission Kickoff Review. If any changes are proposed, the Contractor shall identify the 7 impacted As-Designed Configuration List (ADCL) (CDRL AX09) item(s) and identify 8 the class of change (e.g., Class 1A, 1B, 2) being proposed (classification defined 9 below). (Ref. EELV Systems Engineering Plan) Class 1 and 2 changes will be 10 assessed by the USG team; however, Class 1 changes shall be communicated in 11 accordance with Space and Missile Systems Center Standard (SMC-S)-001- AFSPC 12 Space and Missile Systems Center Standard: Systems Engineering Requirements and 13 Products, SMC-S-002- AFSPC Space and Missile Systems Center Standard: 14 Configuration Management, SMC-S-021- AFSPC Space and Missile Systems Center 15 Standard: Technical Reviews and Audits for Systems, Equipment, & Computer 16 Software and paragraph 3.2.4.1.1. The Contractor shall support participation by the 17 USG Team in system engineering boards and qualification tests/analysis per paragraph 18

3.2.3 (Systems Engineering Boards and Processes). (Electronic Data Access) 19

A Class 1A change for the purpose of this document is defined as a change that affects 20 the SPRD, SIS, ICD, or substantial changes as specified in Table 1: Class 1A changes 21 require USG approval. 22

A Class 1B change for the purpose of this document is defined as a change that drives 23 assessments across multiple technical disciplines/systems, any redesign that has been 24 assessed by the Contractor or USG Team as driving any qualification by test, a 25 form/fit/function change, or any changes to flight-critical items listed in the Flight 26 Critical Items List. The Government Product Line Chief Engineer will work with the 27 Contractor Product Line Chief Engineer (or equivalent) to mutually establish the 28 appropriate level of reporting for Class 1B changes (a subset of the items listed for 29 Class 1A in paragraph 3.2.4.1.1) after contract award. 30

A Class 2 change is defined as any change that does not meet the definition of a Class 1 31 change as described herein. 32

Table 1: Substantial Change Definition 1

Factor Increase ^ Decrease

Communicate Changes*

Approval Deadlines**

Implementatio n Deadlines***

Minimum qualified chamber pressure at engine cutoff command (Stage 2 engine)

+1.5% -1.5% NLT L-15

months

NLT L-12

months

NLT L-6

months

Minimum qualified chamber pressure (Stage 2 engine)

+1.5% -1.5% NLT L-15

months

NLT L-12

months

NLT L-6

months

Maximum thrust (each engine)

+3% -1.5% NLT L-15

months

NLT L-12

months

NLT L-6

months

Specific impulse (each engine)

+1% -0.5% NLT L-15

months

NLT L-12

months

NLT L-6

months

Total impulse (each stage)

+1% -0.5% NLT L-15

months

NLT L-12

mo…