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

FA8811-15-R-0001 11

30 September 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 LAUNCH SERVICES ....................................... 5 1

1.1 DESCRIPTION AND SCOPE OF THE 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 .......................................................................................... 6 5

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

1.2.4 Electronic Data Access ......................................................................................................... 6 7

1.3 DOCUMENTATION DE-CONFLICTION ................................................................................. 6 8

2 APPLICABLE DOCUMENTS ............................................................................................................. 6 9

2.1 COMPLIANCE DOCUMENTS ................................................................................................... 6 10

2.2 REFERENCE DOCUMENTS ...................................................................................................... 7 11

3 SPACE LAUNCH SERVICE ............................................................................................................... 7 12

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS ...................................................... 7 13

3.1.1 Launch System Data ............................................................................................................. 8 14

3.1.2 Launch System Electronic Data Access Training ................................................................. 8 15

3.1.3 Data Accession List .............................................................................................................. 8 16

3.1.4 Program Management Data Reporting .................................................................................. 8 17

3.1.5 Program Management Reviews ............................................................................................ 9 18

3.1.6 Launch Manifesting Process ................................................................................................. 9 19

3.1.7 System Safety Program ....................................................................................................... 10 20

3.1.8 Range Safety ....................................................................................................................... 10 21

3.1.9 Safety Training .................................................................................................................... 10 22

3.1.10 Launch System Familiarization Course .............................................................................. 10 23

3.1.11 Program Protection ............................................................................................................. 11 24

3.1.12 Operations Security ............................................................................................................. 11 25

3.1.13 Anti-Terrorism .................................................................................................................... 11 26

3.1.14 Environmental Requirements .............................................................................................. 12 27

3.1.15 Hazardous Materials ........................................................................................................... 13 28

3.1.16 Incident and Discrepancy Reporting ................................................................................... 13 29

3.1.17 Public Affairs Activities ...................................................................................................... 13 30

3.1.18 Program Milestone Reviews ............................................................................................... 14 31

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS ........................................................ 14 32

3.2.1 Technical Interchange Meetings ......................................................................................... 15 33

3.2.2 Contractor Engineering Database ....................................................................................... 15 34

3.2.3 Systems Engineering Boards and Processes ....................................................................... 15 35

3.2.4 Launch Vehicle Configuration Change Reporting .............................................................. 16 36

3.2.5 Non-Recurring Engineering and Processes ......................................................................... 18 1

3.2.6 Launch System Testing (component, unit, subsystem, system, launch site) ....................... 19 2

3.2.7 Launch System Parameters ................................................................................................. 19 3

3.2.8 Post-Flight Data Review ..................................................................................................... 19 4

3.2.9 Aging and Surveillance Program ........................................................................................ 20 5

3.2.10 Performance Capabilities Guide ......................................................................................... 20 6

3.2.11 Quality Management ........................................................................................................... 20 7

3.2.12 Support to LSIC and SVC Meetings and Reviews ............................................................. 21 8

3.3 LAUNCH VEHICLE PRODUCTION ....................................................................................... 21 9

3.3.1 Launch Vehicle Hardware and Software ............................................................................ 21 10

3.3.2 Mission-Unique Requirements ........................................................................................... 22 11

3.4 MISSION INTEGRATION ........................................................................................................ 22 12

3.4.1 Principal Mission Manager Interface .................................................................................. 22 13

3.4.2 Mission Integration Activities ............................................................................................. 22 14

3.4.3 Space Vehicle Integration Information ............................................................................... 23 15

3.4.4 Interface Control Document ................................................................................................ 23 16

3.4.5 Mission Design and Analyses ............................................................................................. 24 17

3.4.6 Orbital Debris Mitigation .................................................................................................... 24 18

3.4.7 Integrated (Space Vehicle/Launch Vehicle) Operations Planning ...................................... 24 19

3.4.8 Launch Rehearsal Support .................................................................................................. 25 20

3.4.9 Third Integrated Crew Exercise (ICE 3) ............................................................................. 26 21

3.4.10 Mission Interface Control Document Requirements Verification ...................................... 26 22

3.4.11 Flight Hardware Interface Checks ...................................................................................... 26 23

3.4.12 Ground Hardware Interface Checks .................................................................................... 26 24

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

3.4.14 Launch Range Coordination ............................................................................................... 26 26

3.4.15 Mission-Unique Tests ......................................................................................................... 27 27

3.5 LAUNCH OPERATIONS .......................................................................................................... 27 28

3.5.1 Launch Site Operations and Support Services .................................................................... 28 29

3.5.2 Launch Infrastructure .......................................................................................................... 37 30

3.5.3 Base and Range Support ..................................................................................................... 37 31

3.5.4 Mission Commodities ......................................................................................................... 38 32

3.6 SUPPORT TO GOVERNMENT SPACE FLIGHT WORTHINESS......................................... 38 33

3.6.1 Contractor Support to Government Space Flight Worthiness Meetings ............................. 38 34

3.6.2 USG Team Participation in Contractor Production and Engineering Forums .................... 39 35

3.6.3 Contractor Support to SMC/LR Issue Closure .................................................................... 40 36

3.6.4 Launch Vehicle Parts List (CDRL A009) ........................................................................... 41 1

3.6.5 Government Hardware Review ........................................................................................... 41 2

3.6.6 Launch Vehicle Production Cycle Review Support ............................................................ 43 3

3.6.7 Office of Space Launch Independent Validation and Verification ..................................... 44 4

3.6.8 National Reconnaissance Office/Office of Space Launch Mission Assurance Team ......... 44 5

3.6.9 National Reconnaissance Office Mission Integration Group .............................................. 46 6

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

3.8 MISSION-UNIQUE LAUNCH VEHICLE SERVICES ............................................................ 47 8

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

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

APPENDIX C: COMPLIANCE DOCUMENTS ....................................................................................... 67 11

APPENDIX D: REFERENCE DOCUMENTS .......................................................................................... 71 12

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

APPENDIX F: NON-RECURRING ENGINEERING DATA PRODUCTS ............................................. 80 14

APPENDIX G: GOVERNMENT HARDWARE REVIEW FORMAT ..................................................... 88 15

APPENDIX H: PROGRAM MILESTONE REVIEWS ............................................................................ 92 16

1 EVOLVED EXPENDABLE LAUNCH VEHICLE LAUNCH SERVICES 1

1.1 DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES 3

This Performance Work Statement (PWS) defines the launch services the Contractor will 4 perform for Air Force and National Reconnaissance Office (NRO) missions in order to 5 provide a Launch Vehicle (LV) and deliver a Payload (PL) into its intended orbit managed by 6 Air Force Space Command, Space and Missile Systems Center (AFSPC/SMC). This contract 7 is for the procurement of GPS III missions only; therefore, requirements with specific NRO-8 only references are not applicable. NRO-only references appear in grey text. 9 The Contractor shall perform all launch service tasks necessary to deliver payloads to defined 11 orbital parameters in compliance with mission requirements as described in Section 3. The 12 launch service shall support missions to all orbital parameters, consistent with vehicle 13 configuration capabilities and Range Safety restrictions. The Contractor shall provide launch 14 services, which are in compliance with all Range Safety requirements. The Contractor shall 15 make all arrangements with the responsible authorities for the required Range Safety 16 authorization and support for vehicle processing; integrated payload/vehicle processing, 17 launch; and launch site maintenance and modifications. 18 The requirements in Section 3 of this PWS is divided into functional areas: 3.1 Program 20 Management, 3.2 Systems Engineering, 3.3 Launch Vehicle Production, 3.4 Mission 21 Integration, 3.5 Launch Operations, 3.6 Support to Government Space Flight Worthiness, 3.7 22 Quick Reaction and Anomaly Resolution, and 3.8 Mission-Unique Launch Vehicle Services. 23 The PWS tasks for each launch service effort described in this PWS may be grouped 25 chronologically: 1) establish of the launch vehicle configuration, 2) qualify the flight 26 configuration, 3) produce the flight launch vehicle, and 4) conduct the launch campaign. 27 The chronological flow of the launch service first begins with 1) the Contractor establishing 29 the launch vehicle configuration in accordance with the systems engineering functions and 30 tasks of section 3.2, culminating in submittal of CDRL A009 with the proposed configuration 31 changes against the certified/approved launch vehicle in accordance with paragraph 3.2.4. 32 Second, 2) analysis and qualification is conducted for the proposed launch vehicle 33 configuration while performing the systems engineering functions and tasks of section 3.2. 34 Third, 3) production of the flight vehicle is accomplished by performing tasks of section 3.3. 35 Finally, 4) the launch campaign is conducted with the performance of section 3.4, Mission 36 Integration, and section 3.5, Launch Operations. 37 During post award contract execution, the contractor may request, in writing, Government 39 approval to allow relevant activities, documentation, and information developed under other 40 contract(s)/agreement(s) with the Government for NSS launch services missions, to be used to 41 satisfy requirements of this PWS. 42

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY 44

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

1.2.1 Government 48

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

1.2.2 United States Government Team 2

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

1.2.3 Space Vehicle Team 16

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

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

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

LSIC. 26

1.2.4 Electronic Data Access 28

The term “(Electronic Data Access)” refers to the ability of the USG Team to remotely 29 access the data via the Contractor’s electronic data repository host systems for the 30 purpose of reviewing, uploading, or downloading specific, identified program-related 31 data on Contractor host systems. The Contractor shall be responsible for providing 32 access to the data, administering user accounts, and ensuring the integrity of the data. 33 The Contractor shall provide server/folder location of data and confirm appropriate 34 permissions have been provided. Data identified in this PWS shall be provided via 35 electronic access unless otherwise specified in the Contract Data Requirements List 36 (CDRL) descriptions. All data accessed is considered delivered to the Government for 37 the purposes of Defense Federal Acquisition Regulation Supplement 252.227-7015. 38

1.3 DOCUMENTATION DE-CONFLICTION 40

If any conflict or inconsistency exists between the signed mission Interface Control Document, 41 the Standard Interface Specification, or this Performance Work Statement, the mission 42 Interface Control Document shall be given precedence. 43

2 APPLICABLE DOCUMENTS 45

2.1 COMPLIANCE DOCUMENTS 47

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

2.2 REFERENCE DOCUMENTS 1

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

3 SPACE LAUNCH SERVICE 4

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

3.7. 10

The Contractor shall provide Space Launch Services for NSS missions in accordance with the 12 performance requirements stated in the Evolved Expendable Launch Vehicle (EELV) System 13 Performance Requirements Document (SPRD), EELV Standard Interface Specification (SIS), 14 Mission Requirements Annex (MRA) (for USAF only), Interface Requirements Document (IRD) 15 (for NRO only), and mission Interface Control Document (ICD). The Contractor shall control, 16 document, and provide the USG Team continuous access and insight into its processes and 17 assessments of progress and performance of all Space Launch Service requirements. The Contractor 18 shall control, document, and provide the USG Team continuous access to the Contractor’s command 19 media and support the USG’s Independent Mission Assurance activities. 20

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 22

The Contractor shall identify a lead Program Manager and perform all program management 23 functions and tasks necessary to deliver launch services and to satisfy the mission 24 requirements for the mission consistent with operational quality, safety, security, and 25 environmental standards. The program management function of this contract shall provide 26 insight to the Government for all technical and programmatic activities performed under this 27 contract. 28 The following compliance documents are applicable to program management execution: DoD 30 5000.04-M-1 31 Military Standard (MIL-STD)-882E (T) 32 MIL-STD 1528A (see CDRL B005) 33 Range Commander’s Council (RCC) 324-11 (for Global Positioning System [GPS] Metric 34 Tracking) 35 DoD 5220.22-M, 36 EELV Operations Security (OPSEC) Plan, 37 EELV Security Classification Guide, 38 EELV Program Protection Plan (PPP) 39 DoD Instruction (DoDI) 8581.01 Enclosure 3, paragraph a.4.e. 40 NRO Launch (NROL) Information Protection Guide (IPG) (for NRO missions) 41 Air Force Space Command Manual (AFSPCMAN) 91-710 (T) 42 Committee on National Security Systems Directive (CNSSD)-505 (see CDRL B005) 43 Committee on National Security Systems Instruction (CNSSI)-1200 (see CDRL B005) 44 Committee on National Security Systems Policy (CNSSP)-12, and 45

CNSSP-22 46

The Contractor shall provide tailoring to or Contractor’s command media which fulfills MIL-47 STD-1528A for Government approval in accordance with CDRL B005. 48

The following reference documents are applicable to program management execution: 1 Air Force Instruction (AFI) 10-245, 2

AFI 10-701, 3

AFI 10-1202, 4

AFI 20-114, 5

Air Force Space Command Instruction (AFSPCI) 10-1208, 6 13-1213, 7 AFI 31-101, AFI 31-101_Air Force Space Command Supplement (AFSPCSUP), 8

AFI 91-204_AFSPCSUP_I, CNSSI-1253, 9

MIL-STD-881C Appendix J, 10

MIL-STD-1367A, 11

MIL-STD-1791A, 12

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

National Aerospace Standard (NAS) 411, 14 DoDI 4140.67, 15 DoDI 5000.02, 16 DoDI 5200.39, 17 DoDI 5200.44, 18 DoDI 8500.01, and 19 DoDI 8510.01 20

3.1.1 Launch System Data 22

The Contractor shall provide and maintain the USG Team access to all Launch System 23 Data supporting this contract residing on the Contractor’s systems throughout the 24 contract period of performance. The Contractor shall communicate with the USG 25 Team any updates to Launch System data as soon as possible but no later than 24 26 hours, or one business day, after the updates. Launch system data includes access to 27 fleet data. Fleet surveillance is essential to the Space Flight Worthiness Certification 28 process which requires identification of hazards, assessments of risks, mitigation 29 measures and acceptance of residual risks. Fleet and mission specific launch system 30 data are elements affecting the risk baseline accepted by the USG for National Security 31 Space missions. The Contractor shall notify the Government of any network outages or 32 system upgrades that could interrupt access to the systems. The Contractor shall 33 cooperate with the USG Team to develop a plan to implement this requirement. 34 (Electronic Data Access) 35

3.1.2 Launch System Electronic Data Access Training 37

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

3.1.3 Data Accession List 44

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

3.1.4 Program Management Data Reporting 48

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

A. Cost Data Summary Report (CDRL A002) 1 B. Functional Cost-Hour Report (CDRL A003) 2 C. Contractor Business Data Report (CDRL A004) 3 D. Contractor Work Breakdown Structure (CDRL A005) 4 E. Integrated Program Management Report – Integrated Master Schedule (IMS) 5

(CDRL A006) 6

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

3.1.5 Program Management Reviews 20

The Contractor shall schedule and conduct monthly Program Management Reviews 21 (PMR) to: report development and production status, ensure schedules support program 22 objectives, review action items, review program schedules, and discuss any issues. The 23 intent of the PMR is to provide a forum for open dialog between the USG Team and 24 the Contractor. The Contractor shall provide the USG Team the PMR briefing slides 25 no later than 3 calendar days prior to the review or as agreed to by the parties. 26 SMC/LR and the Contractor will agree to the PMR agenda no later than 14 calendar 27 days prior to the PMR or as agreed to by the parties. The PMR agenda shall include a 28 status of the following topics at a minimum: Programmatics, Business Operations, 29 Production Operations, Risk Management, Subsystem(s) Status, Launch Operations, 30 and Wrap Up/Action Items. PMRs will be planned for 2 hours but last no more than 1 31 business day. Locations may rotate between Contractor and Government facilities. 32 The USG Team shall be invited to major subcontractor PMRs or equivalent reviews. 33 (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 in accordance with contract clause SMC--1

H006. (CDRL B001) 2

3.1.7 System Safety Program 4

The Contractor shall establish, implement, and maintain a System Safety Program in 5 accordance with MIL-STD-882E (tailored consistent with SMC-T-004). The 6 Contractor shall provide a System Safety Program Plan (SSPP) and Safety Assessment 7 Report (SAR) in accordance with MIL-STD-882E (tailored consistent with SMC-T-8 004). (Electronic Data Access) (CDRLs B002 and B003) 9

3.1.8 Range Safety 11

The Contractor shall coordinate the tailoring of AFSPCMAN 91-710 for all missions 12 under this contract with SMC/LR and Range Safety prior to formal submittal. The 13 Contractor shall coordinate relief requests (e.g., Equivalent Level of Safety (ELS), or 14 Waivers) for all missions under this contract with SMC/LR and Range Safety prior to 15 formal submittal. (Electronic Data Access) 16

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

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

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

3.1.9 Safety Training 35

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

3.1.10 Launch System Familiarization Course 46

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

3.1.11 Program Protection 10

The Contractor shall develop, provide, implement, and maintain, a Program Protection 11 Implementation Plan (PPIP) in accordance with the EELV PPP and DoDI 8582.01. 12

(CDRL A008) 13

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

Program Protection Surveys (PPS) at all Contractor facilities in accordance 16 with the EELV PPP. 17

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

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

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

3.1.11.4 The Contractor shall protect Information Systems (IS) processing classified 31 data in accordance with DoD 5220.22-M, and applicable supplements. 32

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

3.1.12 Operations Security 38

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

3.1.13 Anti-Terrorism 43

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

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

3.1.13.2 Program Reviews: The Contractor shall perform an in-house Annual Review 4 of its Anti-Terrorism program, which shall be documented in accordance with 5 the host Wing ATO checklist. 6

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

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

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

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

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

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

3.1.14 Environmental Requirements 28

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

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

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

3.1.14.3 The Contractor shall provide data needed to allow SMC/LR to conduct the 1 Environmental Impact Analysis Process in accordance with National 2 Environmental Policy Act and Executive Order (E.O.) 12114, Environmental 3 Effects Abroad of Major Federal Actions, dated 4 January 1979. 4

3.1.15 Hazardous Materials 6

The Contractor shall develop, provide, maintain and comply with a hazardous materials 7 management plan in accordance with AFSPCMAN 91-710 and Task 108 of MIL-STD 8 882-E. (CDRL B004) (Ref. NAS 411) 9

3.1.16 Incident and Discrepancy Reporting 11

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

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

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

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

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

3.1.17 Public Affairs Activities 45

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

3.1.18 Program Milestone Reviews 4

The Contractor shall conduct and provide USG Team participation in the Program 5 Milestone Reviews as defined in Appendix H. These reviews may be combined with 6 Contractor reviews with USG approval. 7

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 9

In order to ensure the successful completion of this mission and associated tasks required for 10 mission success, the Contractor shall perform systems engineering functions and tasks 11 necessary to deliver launch services consistent with operational safety, suitability, and 12 effectiveness (OSS&E) and Environmental Safety and Occupational Health guidance on 13 EELV systems. In order to ensure the Government can accomplish its mission assurance 14 functions and tasks the Contractor shall maintain and provide the USG Team insight into the 15 systems engineering processes supporting the launch service. In order to facilitate smooth and 16 unimpeded communication between the USG Team and the Contractor the Contractor shall 17 identify a technical Point of Contact (POC) (vehicle Chief Engineer or equivalent) to work 18 with the USG counterpart to manage the activities in this section. 19 The following compliance documents are applicable to systems engineering execution: 21 American Institute of Aeronautics and Astronautics (AIAA) S-080-1998- Standard for Space 22 Systems,- Metallic Pressure Vessels, Pressurized Structures, and Pressure Components, 23 AIAA S-081A-2006- Space Systems- Composite Overwrapped Pressure Vessels, 24 AIAA S-110-2005- Standard for Space Systems- Structures, structural Components, and 25 Structural Assemblies, 26 AIAA S-113-2005- Criteria for Explosive Systems and Devices on Space and Launch 27 Vehicles, 28 AIAA S-114-2005- Moving Mechanical Assemblies for Space and Launch Vehicles, 29 AIAA S-120-2006- Mass Properties Control for Space Systems, 30 MIL-STD-461F-Department of Defense Interface Standard: Requirements for the Control of 31 Electromagnetic Interference Characteristics of Subsystems and Equipment, 32 MIL-STD-882E (T)- Department of Defense Standard Practice: System Safety, 33 MIL-STD-1542B- Military Standard: Electromagnetic Compatibility Requirements for Space 34 Systems, 35 SAE AS9100C- Quality Management Systems- Requirements for Aviation, Space and 36 Defense Organizations, 37 SMC Standard (SMC-S)-001- AFSPC Standard: Systems Engineering Requirements and 38 Products, 39 SMC-S-002- AFSPC Space and Missile Systems Center Standard: Configuration 40 Management, 41 SMC-S-003 (T)- Quality Space and Launch Requirements Addendum to AS9100C, 42 SMC-S-005- AFSPC Space and Missile Systems Center Standard: Space Systems- Flight 43 Pressurized Systems, 44 SMC-S-006- AFSPC Space and Missile Systems Center Standard: Solid Rocket Motor Case 45 Design and Test, 46 SMC-S-008- AFSPC Space and Missile Systems Center Standard: Electromagnetic 47 Compatibility Requirements for Space Equipment & Systems, 48 SMC-S-011- AFSPC Space and Missile Systems Center Standard: Parts, Materials, and 49 Processes (PMP) Control Program for Launch Vehicles, 50

SMC-S-013- AFSPC Space and Missile Systems Center Standard: Reliability Program for 1 Space Systems, 2 SMC-S-016- AFSPC Space and Missile Systems Center Standard: Test Requirements for 3 Launch, Upper-stage, and Space Vehicles, 4 SMC-S-018- AFSPC Space and Missile Systems Center Standard: Lithium-Ion Battery for 5 Spacecraft Applications, 6 SMC-S-020- AFSPC Space and Missile Systems Center Standard: Technical Requirements for 7 Wiring Harness, Space Vehicle, 8 SMC-S-021- AFSPC Space and Missile Systems Center Standard: Technical Reviews and 9 Audits for Systems, Equipment, & Computer Software, and 10 ISO 17666 (CDRL B005)- Space Systems- Risk Management. 11 The following reference documents are applicable to systems engineering execution: 13 JANNAF-GL-2012-01-R0- Test and Evaluation Guidelines for Liquid Rocket, 14 SMC-S-004- AFSPC Space and Missile Systems Center Standard: Independent Structural 15 Loads Analysis, 16 SMC-S-012- AFSPC Space and Missile Systems Center Standard: Software Development for 17 Space Systems, 18 SMC-S-019- AFSPC Space and Missile Systems Center Standard: Program and Subcontractor 19 Management, 20 ISO 17666- Space Systems- Risk Management, 21 SMC/LR Risk Management Plan (RMP), 22 Technical Operating Report (TOR)-2005(8583)-4019- Risk Management Plan Guide for 23 Space Acquisition Programs, 24 SMC Guide (SMC-G)-1202- Space Flight Worthiness Criteria (SFWC), 25 SMC-G-1203- Independent Readiness Review Team (IRRT), 26 SMC-G-1204- SMC Space Launch Readiness Review, 27 EELV Systems Engineering Plan (SEP), 28 SAE AS9003- Inspection and Test Quality System, 29 SAE AS9120- Quality Management Systems: Aerospace Requirements for Stockist 30 Distributors, and 31 National Aerospace and Defense Contractors Accreditation Program [Nadcap] AC7004 32 SMC/LR TIRP - SMC/LR Technical Issue Resolution Process 33

3.2.1 Technical Interchange Meetings 35

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

3.2.2 Contractor Engineering Database 40

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

3.2.3 Systems Engineering Boards and Processes 46

The Contractor shall conduct and support USG Team participation in Launch System: 47 Risk Management Boards (RMB); Engineering Review Boards (ERB); Anomaly 48 Review Boards (ARB); Technical Review Boards (TRB); Corrective Action Boards 49 (CAB); Change Control Boards (CCB) for technical issues; Material Review Boards 50 (MRB); Failure Review Boards (FRB); Parts, Materials, and Processes (PMP) Control 51

Boards; Systems Safety Groups; Preliminary Design Review (PDR); Critical Design 1 Review (CDR); Functional and Physical Configuration Audits (FCA/PCA), System 2 Verification Review (SVR); Production Readiness Review (PRR); Test Readiness 3 Review (TRR); Shipping Readiness Reviews; Post-Flight Reviews; or Contractor 4 equivalent boards and/or Contractor-equivalent processes. For recurring review 5 boards, the Contractor shall provide electronic invitations to the USG Team no later 6 than 10 calendar days in advance of the board. For all other review boards the 7 Contractor shall provide electronic invitations to the USG Team as soon as possible 8 after the board is scheduled. The Contractor shall provide the USG Team entrance and 9 exit criteria for System Engineering boards, as required by their command media. The 10 Contractor shall provide virtual participation capability for System Engineering boards. 11 (Electronic Data Access) 12

3.2.4 Launch Vehicle Configuration Change Reporting 14

The Contractor shall provide the USG Team proposed configuration changes to be 15 implemented on the USG certified/approved launch vehicle configuration. The 16 Contractor shall provide the USG certified/approved launch vehicle configuration in 17 accordance with CDRL A009. (Ref. EELV SEP) Class 1 and 2 changes will be 18 assessed by the USG Team however Class 1 changes shall be communicated in 19 accordance with SMC-S-001- AFSPC Space and Missile Systems Center Standard: 20 Systems Engineering Requirements and Products, SMC-S-002- AFSPC Space and 21 Missile Systems Center Standard: Configuration Management, SMC-S-021- AFSPC 22 Space and Missile Systems Center Standard: Technical Reviews and Audits for 23 Systems, Equipment, & Computer Software and paragraph 3.2.4.1.1. The Contractor 24 shall support participation by the USG Team in system engineering boards and 25 qualification tests/analysis per paragraph 3.2.3. (Electronic Data Access) 26

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

A Class 1B change for the purpose of this document is defined as a change that 32 drives assessments across multiple technical disciplines/systems, any redesign 33 that has been assessed by the Contractor or USG Team as driving any 34 qualification, a form/fit/function change or any changes to flight critical items 35 listed in the Flight Critical Items List. The Government Product Line Chief 36 Engineer will work with the Contractor Product Line Chief Engineer (or 37 equivalent) to mutually establish the appropriate level of reporting for Class 1B 38 changes (a subset of the items listed for Class 1A in paragraph 3.2.4.1.1) after 39 contract award. 40

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

Table 1. Substantial Change Definition 2

Factor Increase

Decrease

Communicate Changes*

Approval Deadlines**

Implementation Deadlines***

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

months

NLT L-6 months

Length of vehicle +1% -1% NLT L-15 months

NLT L-12

months

NLT L-6 months

Propellant Tank Diameter (each stage)

+1% -1% NLT L-15

months

NLT L-12

months

NLT L-6 months

Structural safety factor -- -5% NLT L-15 months

NLT L-12

months

NLT L-6 months

Design Fatigue Life Margins

-- -10% NLT L-15

months

NLT L-12

months

NLT L-6 months

^ Increase/Decrease from design specification assessed as part of baseline certification configuration *Communicate changes means the Contractor notifies their intent to include change on NSS mission ** Approval is USG approval or disapproval to the Contractor for the incorporation of the change or USG approved schedule provided *** Implementation means engineering drawings complete, hardware produced and incorporated and all qualification/acceptance testing complete unless mutually agreed by both parties for a later date

3.2.4.1 The Contractor shall communicate with the USG Team NLT L-15 months or 4 otherwise indicated in Table 1, prior to executing any actions to implement a 5 Class 1 change to the USG certified/approved launch vehicle configuration and 6 the initial technical rationale for the Class 1A change as available, or upon 7 change identification to the Contractor’s Change Control Board, or equivalent, 8 whichever is earlier. The Contractor shall provide the final technical rationale 9 and obtain SMC/LR approval after final design of any Class 1A change NLT 10 L-12 months, prior to incorporation of the proposed configuration change to 11 the USG certified/approved launch system configuration. The Contractor shall 12 implement all Class 1 changes NLT 6 months or otherwise indicated in Table 1 13 unless mutually agreed upon by both the Contractor and USG for a later date. 14 (Electronic Data Access) 15

3.2.4.1.1 For Class 1A changes, the technical rationale (Change Assessment 17 package) shall include: Design Evolution Narrative, Design 18 Requirements and Interfaces, Design Environments, As-built Design, 19 Software Design, Supporting Design Analyses,…