03_draft_attachmnt_1_pws_11_may_(GPS_III).pdf

GPS III PWS

ATTACHMENT 1 4

GPS III 6

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV) 7

COMPETITIVE LAUNCH SERVICES 8

PERFORMANCE WORK STATEMENT (PWS) 9

Document No. PWS-FA8811-15-R-0001 11

11 May 2015 14

Department of the Air Force 17 Space and Missile Systems Center 18

Launch Systems Directorate 19 Los Angeles Air Force Base, California 20

1 EVOLVED EXPENDABLE LAUNCH VEHICLE COMPETITIVE LAUNCH SERVICES ............ 5 1

1.1 DESCRIPTION AND SCOPE OF THE COMPETITIVE LAUNCH SERVICES ...................... 5 2

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY ..................................................... 5 3

1.2.1 Government ........................................................................................................................... 5 4

1.2.2 United States Government Team .......................................................................................... 5 5

1.2.3 Space Vehicle Team .............................................................................................................. 5 6

1.2.4 Electronic Data Access ......................................................................................................... 5 7

2 APPLICABLE DOCUMENTS ............................................................................................................. 6 8

2.1 COMPLIANCE DOCUMENTS ................................................................................................... 6 9

2.2 REFERENCE DOCUMENTS ...................................................................................................... 6 10

3 SPACE LAUNCH SERVICE ............................................................................................................... 6 11

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS ...................................................... 6 12

3.1.1 Launch System Data ............................................................................................................. 7 13

3.1.2 Launch System Electronic Data Access Training ................................................................. 7 14

3.1.3 Data Accession List .............................................................................................................. 7 15

3.1.4 Program Management Data Reporting .................................................................................. 8 16

3.1.5 Program Management Reviews ............................................................................................ 8 17

3.1.6 Launch Manifesting Process ................................................................................................. 8 18

3.1.7 System Safety Program ......................................................................................................... 9 19

3.1.8 Range Safety ......................................................................................................................... 9 20

3.1.9 Safety Training ...................................................................................................................... 9 21

3.1.10 Launch System Familiarization Course ................................................................................ 9 22

3.1.11 Program Protection ............................................................................................................. 10 23

3.1.12 Operations Security ............................................................................................................. 10 24

3.1.13 Anti-Terrorism .................................................................................................................... 10 25

3.1.14 Environmental Requirements .............................................................................................. 11 26

3.1.15 Hazardous Materials ........................................................................................................... 12 27

3.1.16 Incident and Discrepancy Reporting ................................................................................... 12 28

3.1.17 Public Affairs Activities ...................................................................................................... 13 29

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS ........................................................ 13 30

3.2.1 Technical Interchange Meetings ......................................................................................... 14 31

3.2.2 Contractor Engineering Database ....................................................................................... 14 32

3.2.3 Systems Engineering Boards and Processes ....................................................................... 14 33

3.2.4 Launch Vehicle Configuration Change Reporting .............................................................. 14 34

3.2.5 Launch System Testing ....................................................................................................... 16 35

3.2.6 Launch System Parameters ................................................................................................. 16 36

3.2.7 Post-Flight Data Review ..................................................................................................... 16 1

3.2.8 Aging and Surveillance Program ........................................................................................ 16 2

3.2.9 Performance Capabilities Guide ......................................................................................... 17 3

3.2.10 Quality Management ........................................................................................................... 17 4

3.2.11 Non-Recurring Engineering and Processes ......................................................................... 17 5

3.2.12 Support to LSIC and SVC Meetings and Reviews ............................................................. 20 6

3.3 LAUNCH VEHICLE PRODUCTION ....................................................................................... 20 7

3.3.1 Launch Vehicle Hardware and Software ............................................................................ 20 8

3.3.2 Mission-Unique Requirements ........................................................................................... 21 9

3.4 MISSION INTEGRATION ........................................................................................................ 21 10

3.4.1 Principal Mission Manager Interface .................................................................................. 21 11

3.4.2 Mission Integration Activities ............................................................................................. 21 12

3.4.3 Space Vehicle Integration Information ............................................................................... 22 13

3.4.4 Interface Control Document ................................................................................................ 23 14

3.4.5 Mission Design and Analyses ............................................................................................. 23 15

3.4.6 Orbital Debris Mitigation .................................................................................................... 23 16

3.4.7 Integrated (Space Vehicle/Launch Vehicle) Operations Planning ...................................... 23 17

3.4.8 Launch Rehearsal Support .................................................................................................. 24 18

3.4.9 Third Integrated Crew Exercise (ICE 3) ............................................................................. 25 19

3.4.10 Mission Interface Control Document Requirements Verification ...................................... 25 20

3.4.11 Flight Hardware Interface Checks ...................................................................................... 25 21

3.4.12 Ground Hardware Interface Checks .................................................................................... 25 22

3.4.13 Launch Safety Collision Avoidance and Radio Frequency Power Impingement Data ...... 25 23

3.4.14 Launch Range Coordination ............................................................................................... 25 24

3.4.15 Mission-Unique Tests ......................................................................................................... 26 25

3.5 LAUNCH OPERATIONS .......................................................................................................... 26 26

3.5.1 Launch Site Operations and Support Services .................................................................... 27 27

3.5.2 Launch Infrastructure .......................................................................................................... 35 28

3.5.3 Base and Range Support ..................................................................................................... 35 29

3.5.4 Mission Commodities ......................................................................................................... 35 30

3.6 SUPPORT TO GOVERNMENT SPACE FLIGHT WORTHINESS......................................... 36 31

3.6.1 Contractor Support to Government Space Flight Worthiness Meetings ............................. 36 32

3.6.2 USG Team Participation in Contractor Production and Engineering Forums .................... 36 33

3.6.3 Contractor Support to SMC/LR Issue Closure .................................................................... 38 34

3.6.4 Launch Vehicle Parts List ................................................................................................... 38 35

3.6.5 Hardware Acceptance Reviews........................................................................................... 39 36

3.6.6 Independent Hardware Reviews ......................................................................................... 39 1

3.6.7 Launch Vehicle Production Cycle Review Support ............................................................ 43 2

3.6.8 Office of Space Launch Independent Validation and Verification ..................................... 43 3

3.6.9 National Reconnaissance Office/Office of Space Launch Mission Assurance Team ......... 44 4

3.6.10 National Reconnaissance Office Mission Integration Group .............................................. 45 5

3.7 QUICK REACTION AND ANOMALY RESOLUTION .......................................................... 46 6

3.8 MISSION-UNIQUE LAUNCH VEHICLE SERVICES ............................................................ 46 7

APPENDIX A: GLOSSARY OF TERMS ................................................................................................. 48 8

APPENDIX B: ACRONYMS AND ABBREVIATIONS .......................................................................... 62 9

APPENDIX C: COMPLIANCE DOCUMENTS ....................................................................................... 67 10

APPENDIX D: REFERENCE DOCUMENTS .......................................................................................... 71 11

APPENDIX E: UNITED STATES GOVERNMENT TEAM CALL-OUTS ............................................ 74 12

1 EVOLVED EXPENDABLE LAUNCH VEHICLE COMPETITIVE LAUNCH 1

SERVICES 2

1.1 DESCRIPTION AND SCOPE OF THE COMPETITIVE LAUNCH SERVICES 4

This Performance Work Statement (PWS) defines the launch services the Contractor will 5 perform for Air Force and National Reconnaissance Office (NRO) missions in order to 6 provide a Launch Vehicle (LV) and deliver a Payload (PL) into its intended orbit managed by 7 Air Force Space Command, Space and Missile Systems Center (AFSPC/SMC). This contract 8 is for the procurement of GPS III missions only; therefore, requirements with specific NRO-9 only references are not applicable. NRO-only references appear in grey text. 10

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY 12

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

1.2.1 Government 16

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

1.2.2 United States Government Team 20

The term “United States Government [USG] Team” refers to the Air Force SMC/LR 21 program office and AFPEO/SP office personnel, but also includes the Aerospace 22 Federally Funded Research and Development Center (FFRDC), SMC/LR Systems 23 Engineering and Integration (SE&I) Contractors, SMC/LR Systems Engineering and 24 Technical Assistance (SETA) support Contractors, SMC/LR Advisory & Assistance 25 Services, the National Reconnaissance Office (NRO)/Office of Space Launch (OSL), 26 the SMC Independent Readiness Review Team (IRRT), Defense Security Service 27 (DSS), Defense Information Systems Agency (DISA), Defense Contract Management 28 Agency (DCMA), Defense Contract Audit Agency (DCAA), 30th Space Wing (30 29 SW), 45th Space Wing (45 SW), and other organizations as designated by SMC/LR 30 Procuring Contracting Officer (PCO). Estimates of the number of USG Team 31 individuals associated with specific requirements in this PWS are listed in Appendix E. 32

1.2.3 Space Vehicle Team 34

1.2.3.1 For United States Air Force (USAF) missions, the term “SV Team” refers to 36 the SV Directorate/Program Office and Space Vehicle Contractor (SVC) 37 personnel, but also includes the Aerospace FFRDC, the SV’s SE&I Contractor 38 and SETA support Contractors, and the SVC’s designated Launch System 39 Integration Contractor (LSIC) (if applicable). 40

1.2.3.2 For NRO missions, the term “SV Team” refers to the SV System Program 42

Office and SVC. The interface with the SV Team is the NRO/OSL and the 43

LSIC. 44

1.2.4 Electronic Data Access 46

The term “(Electronic Data Access)” refers to the ability of the USG Team to remotely 47 access the data via the Contractor’s host systems for the purpose of reviewing, 48 uploading, or downloading specific, identified program-related data on Contractor host 49 systems. The Contractor shall be responsible for providing access to the data, 1 administering user accounts, and ensuring the integrity of the data. The Contractor shall 2 provide location of data. Data identified in this PWS shall be provided via electronic 3 access unless otherwise specified in the Contract Data Requirements List (CDRL) 4 descriptions. All data accessed is considered delivered to the Government for the 5 purposes of Defense Federal Acquisition Regulation Supplement 252.227-7015. 6

2 APPLICABLE DOCUMENTS 8

2.1 COMPLIANCE DOCUMENTS 10

The Contractor shall comply with the compliance documents listed in Appendix C. 11

2.2 REFERENCE DOCUMENTS 13

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

3 SPACE LAUNCH SERVICE 16

The Government requires the services of an integrated Launch System to meet National Security 17 Space (NSS) launch needs. Space Launch Services for NSS missions include LV production and 18 transportation, mission integration, launch operations, support to independent Government mission 19 assurance, base and range support, mission commodities, all associated program management and 20 systems engineering functions and tasks, and any required special studies as defined in PWS Section 21

3.7. 22

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

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 34

The Contractor shall identify a lead Program Manager and perform the program management 35 functions and tasks necessary to deliver launch services consistent with operational quality, 36 safety, security, and environmental standards. 37 The following compliance documents are applicable to program management execution: DoD 39 5000.04-M-1 40 Military Standard (MIL-STD)-882E (T) 41 MIL-STD 1528A (see CDRL A014) 42 Range Commander’s Council (RCC) 324-11 (for Global Positioning System [GPS] Metric 43 Tracking) 44 DoD 5220.22-M 45 EELV Security Classification Guide 46 the EELV Program Protection Plan (PPP) 47 DoD Instruction (DoDI) 8581.01 Enclosure 3, paragraph a.4.e. 48 the NRO Launch (NROL) Information Protection Guide (IPG) (for NRO missions) 49 Air Force Space Command Manual (AFSPCMAN) 91-710 (T) 50

Committee on National Security Systems Directive (CNSSD)-505 (see CDRL A014) 1 Committee on National Security Systems Instruction (CNSSI)-1200 (see CDRL A014) 2 Committee on National Security Systems Policy (CNSSP)-12, and 3

CNSSP-22 4

The Contractor shall provide tailoring to or Contractor’s command media which fulfills MIL-6 STD-1528A for Government approval IAW CDRL A014. 7 The following reference documents are applicable to program management execution: 9 Air Force Instruction (AFI) 10-245, 10

AFI 10-701, 11

AFI 20-114, 12

Air Force Space Command Instruction (AFSPCI) 13-1213, 13 AFI 31-101, AFI 31-101_Air Force Space Command Supplement (AFSPCSUP), 14

AFI 91-204_AFSPCSUP_I, CNSSI-1253, 15

EELV Operations Security (OPSEC) Plan, 16 MIL-STD-881C Appendix J, 17

MIL-STD-1367A, 18

MIL-STD-1791A, 19

MIL-STD-2073-1E(1), 20

National Aerospace Standard (NAS) 411, 21 DoDI 4140.67, 22 DoDI 5000.02, 23 DoDI 5200.39, 24 DoDI 5200.44, 25 DoDI 8500.01, and 26 DoDI 8510.01 27

3.1.1 Launch System Data 29

The Contractor shall provide and maintain the USG Team access to all Launch System 30 data supporting this contract residing on the Contractor’s systems throughout the 31 contract period of performance and shall not interfere with Government access. The 32 Contractor shall communicate with the USG Team any updates to Launch System data 33 as soon as possible but NLT 24 hours after the updates. The Contractor shall notify the 34 Government of any network outages or system upgrades that could interrupt access to 35 the systems. (Electronic Data Access) 36

3.1.2 Launch System Electronic Data Access Training 38

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

3.1.3 Data Accession List 45

The Contractor shall maintain a list of data supporting this contract on a Data 46 Accession List (DAL). (CDRL A001) 47

3.1.4 Program Management Data Reporting 1

The Contractor shall collect and report program data to SMC/LR by providing the 2 following: 3

A. Cost Data Summary Report (CDRL A002) 5 B. Functional Cost-Hour Report (CDRL A003) 6 C. Progress Curve Report (CDRL A004) 7 D. Contractor Business Data Report (CDRL A005) 8 E. Contractor Work Breakdown Structure (CDRL A006) 9 F. Integrated Program Management Report – Integrated Master Schedule (IMS) 10

(CDRL A007) 11

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

3.1.5 Program Management Reviews 25

The Contractor shall schedule and conduct quarterly Program Management Reviews 26 (PMR) and provide the USG Team the PMR briefing slides NLT 3 calendar days prior 27 to the review or as agreed to by the parties. SMC/LR and the Contractor will agree to 28 the PMR agenda NLT 14 calendar days prior to the PMR or as agreed to by the parties. 29 The PMR agenda shall include a status of the following topics at a minimum: 30 Programmatics, Business Operations, Production Operations, Risk Management, 31 Subsystem(s) Status, Launch Operations, and Wrap Up/Action Items. PMRs will last 32 no more than 1 business day. Locations may rotate between Contractor and 33 Government facilities. (Electronic Data Access) 34

3.1.6 Launch Manifesting Process 36

The Contractor shall participate in the Government’s launch scheduling and 37 manifesting process to include the following reviews and meetings: a semi-annual 38 Current Launch Schedule Review Board (CLSRB), a semi-annual Government 39 Integrated Meeting (GIM), a Contractor-led monthly manifest review, a monthly Senior 40 Management Review (SMR), and weekly launch manifest status teleconferences. The 41 Contractor should assume a meeting length of 4 hours each. (Ref. AFSPCI 13-1213) 42

3.1.6.1 The Contractor shall develop and provide the USG Team Launch Schedule 44

Option Assessments as part of the launch manifesting process. (Electronic 45 Data Access) 46

3.1.6.2 The Contractor shall provide the USG Team a Launch Slot Recommendation 48

(LSR) and Launch Date Recommendation (LDR) within the assigned launch 49 period for each launch mission IAW contract clause SMC--H006. (CDRL 1 A008) 2

3.1.7 System Safety Program 4

The Contractor shall establish, implement, and maintain a System Safety Program IAW 5 MIL-STD-882E (tailored consistent with SMC-T-004). The Contractor shall provide a 6 Safety Assessment Report (SAR) IAW MIL-STD-882E (tailored consistent with SMC-7 T-004). (CDRLs A009 and A010) 8

3.1.8 Range Safety 10

The Contractor shall coordinate the tailoring of AFSPCMAN 91-710 for SMC/LR 11 procured missions with SMC/LR and Range Safety prior to formal submittal. The 12 Contractor shall coordinate Equivalent Level of Safety (ELS) certifications, waivers, 13 and relief requests for SMC/LR procured missions with SMC/LR and Range Safety 14 prior to formal submittal. (Electronic Data Access) 15

3.1.8.1 The launch system shall utilize GPS as one of the two mandatory Range 17

Safety tracking data sources. The launch system’s on-board GPS shall 18 comply with the requirements documented in the approved RCC 324-11. The 19 Contractor shall coordinate RCC 324-11 tailoring requests, equivalent level of 20 safety certifications, and non-compliance waiver relief requests for SMC/LR 21 procured missions with SMC/LR and Range Safety prior to formal submittal. 22

3.1.8.2 The launch system’s Autonomous Flight Safety System (AFSS) or flight 24 safety system using a secure command system employing National Security 25 Agency approved cryptography IAW DoDI 8581.01 Enclosure 3, paragraph 26 a.4.e. shall comply with the requirements documented in the approved RCC 27 319-10 (T). The Contractor shall coordinate RCC 319-10 (T) tailoring 28 requests, equivalent level of safety certifications, and non-compliance waiver 29 relief requests for SMC/LR procured missions with SMC/LR and Range 30 Safety prior to formal submittal. 31

3.1.9 Safety Training 33

The Contractor shall provide any Contractor-required safety training to USG Team and 34 SV Team (for NRO missions) personnel for Contractor facilities used in performance 35 of this contract to ensure USG Team access to those facilities. Such training shall 36 include, but is not limited to: launch pad/facility safety training, introduction to 37 Contractor's site safety plan, Emergency Life Support Apparatus/Hooded Demand 38 Valve (ELSA/HDV) and other Personal Protective Equipment (PPE) Training, as 39 required, Contractor general maintenance/processing practices impacting safety (e.g., 40 foreign object damage [FOD], drop mitigation, and hard hats), and facility restriction 41 and limitations (e.g., personnel restrictions on platforms/areas). 42

3.1.10 Launch System Familiarization Course 44

The Contractor shall provide the USG Team an instructor-led Launch System 45 Familiarization Course twice a year: once at the SMC/LR’s facility, and once at the 46 launch base for this mission. At a minimum, the Launch System Familiarization 47 Course shall include familiarization on the following: LV configurations, propulsion 48 systems, avionics systems, structures systems, manufacturing facility, manufacturing 49 processes, launch site facilities, facility systems and capabilities, launch site critical 1 ground mechanical, structural, and fluid/gas systems, launch site/ground command, 2 control, and communications, power systems, and flight controls, guidance, navigation, 3 ground and airborne ordnance systems, ground electrical systems, control/telemetry, 4 launch process flow, Contractor organizational structure, personnel roles and 5 responsibilities, and types of Contractor engineering and launch documentation. 6

(CDRL A011) 7

3.1.11 Program Protection 9

The Contractor shall develop, provide, implement, and maintain, a Program Protection 10 Implementation Plan (PPIP) IAWthe EELV PPP and DoDI 8582.01. (CDRL A012) 11

3.1.11.1 The Contractor shall provide support to the USG Team in annual EELV 13

Program Protection Surveys (PPS) at all Contractor facilities IAW the EELV 14

PPP. 15

3.1.11.2 The Contractor shall attend and support the quarterly EELV System Security 17

Working Group (SSWG) and one security-related meeting per month IAW the 18 EELV PPP (e.g., Information Technology [IT] Security Breach or 19 Unauthorized Information Distribution resolutions). 20

3.1.11.3 The Contractor shall provide support to the USG Team in the development of 22 the EELV PPP Contractor-specific Annex. The Contractor’s support to the 23 USG Team in the development of the EELV PPP shall include providing the 24 LV-specific and supporting Ground system architecture specific information 25 necessary to document, identify, assess, and mitigate security related 26 vulnerabilities and risks. 27

3.1.11.4 The Contractor shall protect Information Systems (IS) processing classified 29 data IAW DoD 5220.22-M, and applicable supplements. 30

3.1.11.5 The Contractor shall obtain and/or maintain International Organization for 32 Standardization/International Electrotechnical Commission (ISO/IEC) 33 27000/02 (T) certification. 34

3.1.12 Operations Security 36

The Contractor shall develop, implement and maintain an Operations Security 37 (OPSEC) program IAW contract Attachment 2, DoD Contract Security Classification 38 Specification (DD254). (Ref. AFI 10-701 and the EELV OPSEC Plan) 39

3.1.13 Anti-Terrorism 41

The Contractor shall implement and maintain an Anti-terrorism (AT) program for 42 activities at Cape Canaveral Air Force Station (CCAFS) and Vandenberg Air Force 43 Base (VAFB). (Ref. AFI 10-245) The Contractor shall ensure SMC/LR approval prior 44 to taking any action regarding anti-terrorism requirements requested by the 30 SW 45 Operations Security Office (30 SW/CCH) or 45 SW/Anti-Terrorism Office (ATO) that 46 change or add any additional anti-terrorism requirements to this PWS paragraph and 47 subparagraphs. 48

3.1.13.1 Meeting Support: The Contractor shall identify site security leads to support 2 one meeting per year. 3

3.1.13.2 Program Reviews: The Contractor shall perform an in-house Annual Review 5 of its Anti-Terrorism program and this shall be documented IAW the host 6 Wing ATO checklist. 7

3.1.13.3 Training: The Contractor shall perform annual training utilizing SMC/LR 9

Anti-Terrorism training materials as a guideline. The Contractor shall create a 10 Corporate Annual Training Letter stating that all site personnel have 11 completed their individual Anti-Terrorism training. 12

3.1.13.4 Force Protection Condition (FPCON) Checklists: The Contractor shall utilize 14 site specific FPCON checklists provided by SMC/LR at each launch site. 15

3.1.13.5 Random Anti-Terrorism Measures (RAMs): The Contractor shall perform 17 prescribed RAMs or alternate RAMs that are preapproved by SMC/LR (up to 18 5 per month). Completed RAMs shall be documented in a format prescribed 19 by SMC/LR and reported quarterly to the Host Wing ATO. 20

3.1.13.6 Mission Essential Personnel: The Contractor shall create and maintain a 22

“Mission Essential Personnel” list and an “Emergency Essential Personnel” 23 list for higher FPCON levels (Charlie and Delta) and other emergency 24 situations at each launch site. The Contractor shall provide these lists to the 25 appropriate launch site personnel in advance of any emergency situation and 26 in the event of any changes 27

3.1.14 Environmental Requirements 29

The Contractor shall comply with environmental requirements IAW AFSPCMAN 30 91-710 and all relevant and applicable Federal, State, and local environmental laws, 31 regulations, and executive orders, and base regulations as documented in the 32 appropriate license, lease, Commercial Space Operations Support Agreements 33 (CSOSA), and CSOSA annexes. 34

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

3.1.14.2 The Contractor shall include SMC/LR in the coordination process with the 43 host Wing and the environmental regulatory agencies relating to the 44 application, development, or modification of permits or required 45 environmental compliance plans, environmental cleanup actions, or other 46 major efforts subject to environmental laws and regulations. The Contractor 47 shall provide information to the on-site USG Team environmental 1 representatives, during the coordination process, to ensure that the USG Team 2 is aware of the risks and alternatives that are evaluated or accepted during this 3 process. (Electronic Data Access) 4

3.1.14.3 The Contractor shall provide data needed to allow SMC/LR to conduct the 6

Environmental Impact Analysis Process IAW National Environmental Policy 7 Act and Executive Order (E.O.) 12114, Environmental Effects Abroad of 8 Major Federal Actions, dated 4 January 1979. 9

3.1.15 Hazardous Materials 11

The Contractor shall develop, provide, maintain and comply with a hazardous materials 12 management plan IAW AFSPCMAN 91-710. (CDRL A013) (Ref. NAS 411) 13

3.1.16 Incident and Discrepancy Reporting 15

The Contractor shall maintain an incident and discrepancy reporting system. The 16 Contractor shall notify the USG Team, via Contractor-identified internal reporting 17 systems, of incidents and discrepancies. 18

3.1.16.1 The Contractor shall notify the USG Team of incidents and discrepancies 20 occurring during the execution of this contract that involve: (1) loss of life or 21 severe personal injury as defined per Occupational Safety and Health 22 Administration reporting requirements; (2) damage to any flight hardware or 23 Critical Ground Support Equipment (GSE); or (3) damage to Critical GSE 24 occurring during vehicle build, test, transportation, processing, or facility 25 readiness operations. The notification shall be provided as soon as 26 operationally possible, but NLT 48 hours (post-emergency response and 27 safety hazard securing) and IAW already-established Contractor reporting 28 procedures. The Contractor shall provide the status of ongoing investigations, 29 Contractor incident root cause data, and determination and associated 30 corrective actions. (Electronic Data Access) 31

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

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

(c) changes to the IMS, (d) waivers or exceptions to test or verification 41 requirements, or (e) impact a scheduled launch date. The Contractor shall 42 provide the status of ongoing investigations, Contractor incident root cause 43 data, and determination and associated corrective actions. For all other minor 44 incidents and discrepancies, notification shall be NLT 14 calendar days of an 45 event’s occurrence and status reporting will be determined by SMC/LR on a 46 case-by-case basis. 47

3.1.17 Public Affairs Activities 1

The Contractor shall support Public Affairs activities by coordinating with SMC/LR 2 and SMC/PA. The Contractor shall coordinate press statements, press releases, or any 3 related public affairs items with SMC/PA prior to release to the general public. 4 For NRO missions, the Contractor shall support Public Affairs activities to include 6 Launch External Affairs Forum (LEAF) coordination. The Contractor shall submit all 7 launch memorabilia; press statements, press releases, or any related public affairs items 8 to the NRO LEAF for approval prior to production or release to the general public. 9

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 11

The Contractor shall perform systems engineering functions and tasks necessary to deliver 12 launch services consistent with operational safety, suitability, and effectiveness (OSS&E) and 13 Environmental Safety and Occupational Health guidance on EELV systems. The Contractor 14 shall maintain and provide the USG Team insight into the systems engineering processes 15 supporting the launch service. The Contractor shall identify a technical Point of Contact 16 (POC) (vehicle chief engineer or equivalent) to work with the USG counterpart to manage the 17 activities in this section. 18 The following compliance documents are applicable to systems engineering execution: 20 American Institute of Aeronautics and Astronautics (AIAA) S-080-1998, 21

AIAA S-081A-2006, 22

AIAA S-110-2005, 23

AIAA S-113-2005, 24

AIAA S-114-2005, 25

AIAA S-120-2006, 26

MIL-STD-461F, 27

MIL-STD-882E (T), 28

MIL-STD-1542B, 29

SAE AS9100C, 30

SMC Standard (SMC-S)-001, 31

SMC-S-002, 32

SMC-S-003(T), 33

SMC-S-005, 34

SMC-S-006, 35

SMC-S-008, 36

SMC-S-011, 37

SMC-S-013, 38

SMC-S-016, 39

SMC-S-018, 40

SMC-S-020, and 41

ISO 17666 (CDRL A014). 42

The following reference documents are applicable to systems engineering execution: 43

SMC-S-004, 44

SMC-S-012, 45

SMC-S-019, 46

SMC-S-021, 47

ISO 17666, 48

SMC/LR Risk Management Plan (RMP), 49 Technical Operating Report (TOR)-2005(8583)-4019, 50 SMC Guide (SMC-G)-1202, 51

SMC-G-1203, 1

SMC-G-1204, 2

EELV Systems Engineering Plan (SEP), 3 SAE AS9003, SAE AS9120, and 4 National Aerospace and Defense Contractors Accreditation Program [Nadcap] AC7004 5

3.2.1 Technical Interchange Meetings 8

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

3.2.2 Contractor Engineering Database 13

The Contractor shall provide the USG Team access to the Contractor’s non-14 conformance, drawings, configuration control, risk, hazard tracking system, production, 15 launch operations and other similar engineering databases necessary to support space 16 flight worthiness (SFW) certification by the USG Team. (Electronic Data Access) 17

3.2.3 Systems Engineering Boards and Processes 19

The Contractor shall support USG Team participation in Risk Management Boards 20 (RMB); Engineering Review Boards (ERB); Anomaly Review Boards (ARB); 21 Technical Review Boards (TRB); Corrective Action Boards (CAB); Change Control 22 Boards (CCB) for technical issues; Material Review Boards (MRB); Failure Review 23 Boards (FRB); Parts, Materials, and Processes (PMP) Control Boards; Systems Safety 24 Groups; Preliminary Design Review (PDR); Critical Design Review (CDR); 25 Production Readiness Review (PRR); Test Readiness Review (TRR); Shipping 26 Readiness Reviews; or Contractor equivalent boards and/or Contractor-equivalent 27 processes. For recurring review boards, the Contractor shall provide electronic 28 invitations to the USG Team NLT 14 calendar days in advance of the board. For all 29 other review boards the Contractor shall provide electronic invitations to the USG 30 Team as soon as possible after the board is scheduled. The Contractor shall provide the 31 USG Team entrance and exit criteria for System Engineering boards. The Contractor 32 shall provide virtual participation capability for System Engineering boards. (Electronic 33 Data Access) 34

3.2.4 Launch Vehicle Configuration Change Reporting 36

The Contractor shall provide the USG Team proposed configuration changes to be 37 implemented on the USG certified/approved launch vehicle configuration. The 38 Contractor shall provide the USG certified/approved launch vehicle configuration IAW 39 CDRL A015. (Ref. EELV SEP) (Electronic Data Access) 40

A Class 1 change for the purpose of this document is defined as a substantial 42 change from the USG certified/approved launch system configuration as 43 indicated in the table below. 44

A Class 2 change is defined as any change which does not meet the definition 46 of a Class 1 change as described herein. 47

Table 1. Substantial Change Definition 1 Factor Increase Decrease Communicate

Changes* Approval Deadlines

Implementation Deadlines

Maximum thrust (each engine) TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Specific impulse (each engine) TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Engine weight TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Engine thrust-to-weight ratio TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Total impulse (each stage) TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Thrust structure weight TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Dry weight (each stage) excluding fairing

TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days

Length (each stage) excluding fairing

TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days

Length of vehicle excluding fairing TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Diameter (each stage) excluding fairing

TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days

Combined structural safety factor TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days Environment levels TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days TBD TBD TBD NLT TBD days NLT L-TBD days NLT L-TBD days

* NLT days prior to implementation 2

3.2.4.1 The Contractor shall only implement Class 1 changes in accordance with the 4 defined deadlines in Table 1. The Contractor shall communicate with the USG 5 Team in accordance with the defined deadlines in Table 1 prior to executing 6 any actions to implement a Class 1 change to the USG certified/approved 7 launch vehicle configuration and the technical rationale for the Class 1 change, 8 or upon change identification to the Contractor’s Change Control Board, or 9 equivalent, whichever is earlier. The Contractor shall obtain SMC/LR 10 approval after final design of any Class 1 change prior to incorporation of the 11 proposed configuration change to the USG certified/approved launch system 12 configuration. (Electronic Data Access) 13

3.2.4.1.1 The technical rationale (Change Assessment package) shall include: Design 14 Evolution Narrative, Design Requirements and Interfaces, Design 15 Environments, As-built Design, Software Design, Supporting Design Analyses, 16 Principles of Operation, Limited Operating Life Items Tracked, Summary of 17 Required Manufacturing Processes, Summary of Logistics, Summary of FMEA 18 and Reliability Assessment, Summary of Identified Risks, 19 Acceptance/Qualification Test Plan/Procedures, Test-Like-You-Fly Exceptions 20 and Deviations, Qualification Rationale, Qualification Test Results, List of 21 Test Nonconformances, Summary of Flight Data, and Configuration 22 Differences Between Unit Under Test and Qualification Unit. 23

3.2.4.2 The Contractor shall communicate with the USG Team of any proposed Class 24 2 configuration change to the USG certified/approved launch vehicle 25 configuration and the technical rationale for the change as soon as possible but 26 NLT 10 calendar days after identifying the change. (Electronic Data Access) 27

3.2.4.3 The Contractor shall communicate changes to the launch system’s interface 28 with Engineering Launch Support System (ELSS) or a change to the 29 Operational Surveillance Requirements as defined in Section 3.5.1.14 as soon 30 as possible but NLT 14 days prior to launch. The Contractor shall obtain 31 SMC/LR approval after final design of changes to the launch system interface 32 with ELSS or a change to the Operational Surveillance Requirements prior to 33 implementation NLT 7 days prior to launch. (Electronic Data Access) 34

3.2.5 Launch System Testing 1

The Contractor shall maintain and provide the USG Team test requirements, 2 summaries, and test results for any qualification, acceptance, and test and checkout at 3 the component, subsystem, and Launch System levels IAW SMC-S-016. The 4 Contractor shall provide documentation on test-like-you-fly exceptions and test 5 anomalies along with mitigation or acceptance rationale. (Electronic Data Access) 6

3.2.6 Launch System Parameters 8

The Contractor shall make available in a configuration controlled system to the USG 9 Team launch countdown parameters; operational redline limits; and the data, rationale, 10 source, and justification for selecting or changing the specific limits on parameters that 11 affected continued processing from initiation of launch countdown until completion of 12 the launch countdown. (NSS missions and non-NSS missions) (Electronic Data 13 Access) 14

3.2.6.1 For NSS missions, the Contractor shall provide the baseline for items listed in 16

3.2.6 from the USG certified/approved launch vehicle configuration at launch 17 minus six (L-6) months. From L-6 until launch, the Contractor shall maintain 18 the baseline and push-notify the USG Team of any changes to this electronic 19 baseline along with the information requested in paragraph 3.2.6. (Electronic 20 Data Access) 21

3.2.7 Post-Flight Data Review 23

The Contractor shall perform post-flight data reduction, anomaly resolution, lessons 24 learned determinations, and observation disposition in support of the post-flight 25 products identified in paragraphs 3.2.7.2 and 3.2.7.3. The Contractor shall provide the 26 USG Team corrective action plans for anomalies. (Electronic Data Access) 27

3.2.7.1 The Contractor shall conduct a Quick-Look Assessment meeting at the launch 29 site within 2 hours after SV separation that includes USG Team personnel and 30 covers system and sub-system performance. For long coast missions, the 31 Contractor shall conduct the Quick-Look Assessment meeting within 2 hours 32 of transfer orbit insertion. System and sub-system performance shall address 33 initial observations and any anomalies recorded during the minus/plus count. 34

3.2.7.2 The Contractor shall provide an initial and final Post-Flight Assessment 36

Report. (CDRL A016) 37

3.2.7.3 The Contractor shall conduct a Post-Flight Review, which summarizes the 39

Post-Flight Assessment Report, for the USG Team NLT 45 calendar days 40 following Contractor’s receipt of LV telemetry data. 41

3.2.8 Aging and Surveillance Program 43

The Contractor shall maintain and provide to the USG Team an aging and surveillance 44 program to ensure that the LV meets all Contractor specifications and flight safety 45 standards. (Electronic Data Access) 46

3.2.9 Performance Capabilities Guide 1

The Contractor shall provide and maintain a Performance Capabilities Guide. (CDRL 2 A017) 3

3.2.10 Quality Management 5

The Contractor shall perform quality management IAW the following: 6

3.2.10.1 The Contractor shall attain AS 9100C certification from a Certification Body 8 recognized by the International Aerospace Quality Group (IAQG), and 9 maintain the certification throughout the duration of the contract. The 10 AS9100C certification shall cover all Contractor sites, including subsidiaries 11 and partners, performing LV manufacturing, management, integration, testing, 12 and launch. 13

3.2.10.2 The Contractor shall require each supplier of a flight critical item to maintain 15 a quality management system to an aerospace industry standard (AS9100C, 16 AS9003, AS9120, or Nadcap AC7004, as appropriate to the supplier) for 17 procuring Launch System hardware and services. Evidence of supplier 18 quality management system approval shall be based on accredited third-party 19 certification or Contractor second-party audit. 20

3.2.10.3 The Contractor shall provide a current audit plan and schedule for internal and 22 external quality audits and invite the USG Team to observe these audits. The 23 Contractor shall provide the USG Team with access to audit reports (e.g., 24 findings, observations, opportunities for improvement, and corrective action 25 requests) and implementation status of corrective actions resulting from these 26 internal and external quality audits. (Electronic Data Access) 27

3.2.10.4 The Contractor shall provide the USG Team quality metrics for processes 29 comprising the Contractor’s quality management system. Consistent with the 30 requirements in AS9100C, these metrics shall address monitoring and 31 measurement of processes and product including hardware non-conformances, 32 internal escapements, external and supplier escapements, supplier quality 33 ratings, and corrective action effectiveness. (Electronic Data Access) 34

3.2.10.5 The Contractor shall allow the USG Team participation in Contractor’s 36 meetings with its suppliers (e.g., Quality Councils, Supplier Corrective Action 37 Request [SCAR] reviews, management reviews, supplier conferences, and 38 other forums) relating to delivery performance and product quality. 39

3.2.10.6 The Contractor shall comply with SMC-S-003 (T) 40

3.2.11 Non-Recurring Engineering and Processes 42

3.2.11.1 The Contractor shall provide the USG Team access to the launch system 44 design, systems analyses and methodologies, component qualification data, 45 and performance capabilities for the contracted LV configuration to support 46 the USG’s SFW certification process. Any relevant activities and information 47 developed under another contract/agreement with the Government can be used 48 to satisfy this requirement. The Contractor shall document (an electronic 1 interoffice memorandum is acceptable) and notify the USG Team when 2 delivery occurs identifying the location of the data NLT 30 days after contract 3 award and upon implementing subsequent changes in the data. The Non-4 Recurring Engineering and Process data shall contain the following 5 information, or Contractor equivalent, as applicable to the Contractor’s USG 6 certified/approved launch vehicle configuration: (Electronic Data Access) 7

1. Avionics Critical Design Review (CDR) Package 8

2. Hydraulic CDR Package 9

3. Propulsion CDR Package 10

4. Booster CDR Package including engine(s) 11

5. Ground System CDR Package 12

6. Launch Facility CDR Package 13

7. Second Stage CDR Package 14

8. Strap on Rocket CDR Package 15

9. Strongback CDR Package 16

10. Transport Trailer CDR Package 17

11. Site Erector CDR Package 18

12. Interstage CDR Package, Interstage Finite Element Models, Structural 19

Analysis Reports, Qualification Test Results, Engineering Drawings and 20 Test Procedures 21

13. Payload Fairing CDR Package, Payload Fairing Finite Element Models, 22 Structural Analysis Reports, Qualification Test Results, Engineering 23 Drawings and Test Procedures 24

14. Nose Cone CDR Package, Nose Cone Finite Element Models, Structural 25 Analysis Reports, Qualification Test Results, Engineering Drawings and 26 Test Procedures 27

15. Booster Structures Finite Element Models, Structural Analysis Reports, 28 Qualification Test Results, Engineering Drawings and Test Procedures 29

16. Tanks and Domes Finite Element Models, Structural Analysis Reports, 30 Qualification Test Results, Engineering Drawings and Test Procedures 31

17. First Stage Finite Element Models, Structural Analysis Reports, 32 Qualification Test Results, Engineering Drawings and Test Procedures 33

18. Engine Finite Element Models, Structural Analysis Reports, 34 Qualification Test Results, Engineering Drawings and Test Procedures 35

19. Heavy Attach Hardware Finite Element Models, Structural Analysis 36 Reports, Qualification Test Results, Engineering Drawings and Test 37 Procedures 38

20. Launch Vehicle Adapter Finite Element Models, Structural Analysis 39 Reports, Qualification Test Results, Engineering Drawings and Test 40 Procedures 41

21. Transfer Tube Finite Element Models, Structural Analysis Reports, 42 Qualification Test Results, Engineering Drawings and Test Procedures 43

22. Second Stage Finite Element Models, Structural Analysis Reports, 44 Qualification Test Results, Engineering Drawings and Test Procedures 45

23. Stage 1/2 Dynamic Model and Finite Element Models 1

24. Payload Fairing Dynamic Model and Finite Element Models 2

25. Maximum G Dynamic Model and Finite Element Models 3

26. Launch Vehicle/Space Vehicle Separation Dynamic Model and Finite 4

Element Models 5

27. Booster Dynamic Model and Finite Element Models 6

28. Booster/Space Vehicle Loads Models 7

29. Documentation of Maneuvering Loads Forces 8

30. Qualification Test Results for Critical…