03_Attachment_1_Draft_PWS_(updated_15_Jul_15).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

14 July 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 .............................................................................................................. 6 6

1.2.4 Electronic Data Access ......................................................................................................... 6 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 ...................................................... 7 12

3.1.1 Launch System Data ............................................................................................................. 8 13

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

3.1.3 Data Accession List .............................................................................................................. 8 15

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

3.1.5 Program Management Reviews ............................................................................................ 9 17

3.1.6 Launch Manifesting Process ................................................................................................. 9 18

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

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

3.1.9 Safety Training .................................................................................................................... 10 21

3.1.10 Launch System Familiarization Course .............................................................................. 10 22

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

3.1.12 Operations Security ............................................................................................................. 11 24

3.1.13 Anti-Terrorism .................................................................................................................... 11 25

3.1.14 Environmental Requirements .............................................................................................. 12 26

3.1.15 Hazardous Materials ........................................................................................................... 13 27

3.1.16 Incident and Discrepancy Reporting ................................................................................... 13 28

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

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

3.2.1 Technical Interchange Meetings ......................................................................................... 15 31

3.2.2 Contractor Engineering Database ....................................................................................... 16 32

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

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

3.2.5 Launch System Testing ....................................................................................................... 18 35

3.2.6 Launch System Parameters ................................................................................................. 19 36

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

3.2.8 Aging and Surveillance Program ........................................................................................ 20 2

3.2.9 Performance Capabilities Guide ......................................................................................... 20 3

3.2.10 Quality Management ........................................................................................................... 20 4

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

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

3.3 LAUNCH VEHICLE PRODUCTION ....................................................................................... 21 7

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

3.3.2 Mission-Unique Requirements ........................................................................................... 22 9

3.4 MISSION INTEGRATION ........................................................................................................ 22 10

3.4.1 Principal Mission Manager Interface .................................................................................. 22 11

3.4.2 Mission Integration Activities ............................................................................................. 22 12

3.4.3 Space Vehicle Integration Information ............................................................................... 23 13

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

3.4.5 Mission Design and Analyses ............................................................................................. 24 15

3.4.6 Orbital Debris Mitigation .................................................................................................... 24 16

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

3.4.8 Launch Rehearsal Support .................................................................................................. 25 18

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

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

3.4.11 Flight Hardware Interface Checks ...................................................................................... 26 21

3.4.12 Ground Hardware Interface Checks .................................................................................... 26 22

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

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

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

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

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

3.5.2 Launch Infrastructure .......................................................................................................... 37 28

3.5.3 Base and Range Support ..................................................................................................... 37 29

3.5.4 Mission Commodities ......................................................................................................... 37 30

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

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

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

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

3.6.4 Launch Vehicle Parts List ................................................................................................... 40 35

3.6.5 Hardware Acceptance Reviews........................................................................................... 41 36

3.6.6 Independent Hardware Reviews

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

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

APPENDIX C: COMPLIANCE DOCUMENTS ....................................................................................... 66 10

APPENDIX D: REFERENCE DOCUMENTS .......................................................................................... 70 11

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

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

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY 39

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

1.2.1 Government 43

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

1.2.2 United States Government Team 47

The term “United States Government [USG] Team” refers to the Air Force SMC/LR 48 program office and AFPEO/SP office personnel, but also includes the Aerospace 49 Federally Funded Research and Development Center (FFRDC), SMC/LR Systems 50

Engineering and Integration (SE&I) Contractors, SMC/LR Systems Engineering and 1 Technical Assistance (SETA) support Contractors, SMC/LR Advisory & Assistance 2 Services, the National Reconnaissance Office (NRO)/Office of Space Launch (OSL), 3 the SMC Independent Readiness Review Team (IRRT), Defense Security Service 4 (DSS), Defense Information Systems Agency (DISA), Defense Contract Management 5 Agency (DCMA), Defense Contract Audit Agency (DCAA), 30th Space Wing (30 6 SW), 45th Space Wing (45 SW), and other organizations as designated by SMC/LR 7 Procuring Contracting Officer (PCO). Estimates of the number of USG Team 8 individuals associated with specific requirements in this PWS are listed in Appendix E. 9

1.2.3 Space Vehicle Team 11

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

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

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

LSIC. 21

1.2.4 Electronic Data Access 23

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

2 APPLICABLE DOCUMENTS 36

2.1 COMPLIANCE DOCUMENTS 38

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

2.2 REFERENCE DOCUMENTS 41

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

3 SPACE LAUNCH SERVICE 44

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

3.7. 2

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

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 14

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

CNSSP-22 38

The Contractor shall provide tailoring to or Contractor’s command media which fulfills MIL-39 STD-1528A for Government approval in accordance with CDRL B005. 40 The following reference documents are applicable to program management execution: 42 Air Force Instruction (AFI) 10-245, 43

AFI 10-701, 44

AFI 20-114, 45

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

AFI 91-204_AFSPCSUP_I, CNSSI-1253, 48

EELV Operations Security (OPSEC) Plan, 49 MIL-STD-881C Appendix J, 50

MIL-STD-1367A, 1

MIL-STD-1791A, 2

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

National Aerospace Standard (NAS) 411, 4 DoDI 4140.67, 5 DoDI 5000.02, 6 DoDI 5200.39, 7 DoDI 5200.44, 8 DoDI 8500.01, and 9 DoDI 8510.01 10

3.1.1 Launch System Data 12

The Contractor shall provide and maintain the USG Team access to all Launch System 13 Data supporting this contract residing on the Contractor’s systems throughout the 14 contract period of performance and shall not interfere with Government access. The 15 Contractor shall communicate with the USG Team any updates to Launch System data 16 as soon as possible but no later than 24 hours, or one business day, after the updates. 17 Launch system data includes access to fleet data. Fleet surveillance is essential to the 18 Space Flight Worthiness Certification process which requires identification of hazards, 19 assessments of risks, mitigation measures and acceptance of residual risks. Fleet and 20 mission specific launch system data are elements affecting the risk baseline accepted by 21 the USG for National Security Space missions. The Contractor shall notify the 22 Government of any network outages or system upgrades that could interrupt access to 23 the systems. (Electronic Data Access) 24

3.1.2 Launch System Electronic Data Access Training 26

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

3.1.3 Data Accession List 33

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

3.1.4 Program Management Data Reporting 37

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

A. Cost Data Summary Report (CDRL A002) 41 B. Functional Cost-Hour Report (CDRL A003) 42 C. Contractor Business Data Report (CDRL A004) 43 D. Contractor Work Breakdown Structure (CDRL A005) 44 E. Integrated Program Management Report – Integrated Master Schedule (IMS) 45

(CDRL A006) 46

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

3.1.5 Program Management Reviews 9

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

3.1.6 Launch Manifesting Process 25

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

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

Option Assessments as part of the launch manifesting process. (Electronic 34 Data Access) 35

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

(LSR) and Launch Date Recommendation (LDR) within the assigned launch 38 period for each launch mission in accordance with contract clause SMC--39

H006. (CDRL B001) 40

3.1.7 System Safety Program 42

The Contractor shall establish, implement, and maintain a System Safety Program in 43 accordance with MIL-STD-882E (tailored consistent with SMC-T-004). The 44 Contractor shall provide a Safety Assessment Report (SAR) in accordance with MIL-45 STD-882E (tailored consistent with SMC-T-004). (CDRLs B002 and B003) 46

3.1.8 Range Safety 48

The Contractor shall coordinate the tailoring of AFSPCMAN 91-710 for SMC/LR 49 procured missions with SMC/LR and Range Safety prior to formal submittal. The 50

Contractor shall coordinate relief requests (i.e., Equivalent Level of Safety (ELS), or 1 Waivers) for SMC/LR procured missions with SMC/LR and Range Safety prior to 2 formal submittal. (Electronic Data Access) 3

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

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

3.1.8.2 The launch system’s Autonomous Flight Safety System (AFSS) or flight 12 safety system using a secure command system employing National Security 13 Agency approved cryptography in accordance with DoDI 8581.01 Enclosure 14 3, paragraph a.4.e. shall comply with the requirements documented in the 15 approved RCC 319-10 (T). The Contractor shall coordinate RCC 319-10 (T) 16 tailoring requests, equivalent level of safety certifications, and non-17 compliance waiver relief requests for SMC/LR procured missions with 18 SMC/LR and Range Safety prior to formal submittal. 19

3.1.9 Safety Training 21

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

3.1.10 Launch System Familiarization Course 32

The Contractor shall provide the USG Team an instructor-led Launch System 33 Familiarization Course as needed or up to twice a year: once at the SMC/LR’s facility, 34 and once at the launch base for this mission. At a minimum, the Launch System 35 Familiarization Course shall include familiarization on the following: LV 36 configurations, propulsion systems, avionics systems, structures systems, 37 manufacturing facility, manufacturing processes, launch site facilities, facility systems 38 and capabilities, launch site critical ground mechanical, structural, and fluid/gas 39 systems, launch site/ground command, control, and communications, power systems, 40 and flight controls, guidance, navigation, ground and airborne ordnance systems, 41 ground electrical systems, control/telemetry, launch process flow, Contractor 42 organizational structure, personnel roles and responsibilities, and types of Contractor 43 engineering and launch documentation. (CDRL A007) 44

3.1.11 Program Protection 46

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

(CDRL A008) 49

3.1.11.1 The Contractor shall provide support to the USG Team in annual EELV 1 Program Protection Surveys (PPS) at all Contractor facilities in accordance 2 with the EELV PPP. 3

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

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

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

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

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

3.1.12 Operations Security 24

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

3.1.13 Anti-Terrorism 29

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

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

3.1.13.2 Program Reviews: The Contractor shall perform an in-house Annual Review 41 of its Anti-Terrorism program and this shall be documented in accordance 42 with the host Wing ATO checklist. 43

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

Anti-Terrorism training materials as a guideline. The Contractor shall create a 46

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

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

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

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

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

3.1.14 Environmental Requirements 19

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

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

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

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

Environmental Impact Analysis Process in accordance with National 44 Environmental Policy Act and Executive Order (E.O.) 12114, Environmental 45 Effects Abroad of Major Federal Actions, dated 4 January 1979. 46

3.1.15 Hazardous Materials 1

The Contractor shall develop, provide, maintain and comply with a hazardous materials 2 management plan in accordance with AFSPCMAN 91-710. (CDRL B004) (Ref. NAS 3

411) 4

3.1.16 Incident and Discrepancy Reporting 6

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

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

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

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

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

3.1.17 Public Affairs Activities 40

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

3.1.18 Program Milestone Reviews 1

The Contractor shall conduct and provide USG Team participation in the Program 2 Milestone Reviews as defined in Appendix F. 3

Nominal Timeline Program Milestone Reviews L-23 mo Mission Kickoff L-12 mo Mission Design Review L-10 mo Component and Subsystem Readiness Review (CSRR 1) L-6 mo Mission Verification Review L-3 mo Ground Operations Readiness Review (GORR) L-2.5 mo Component and Subsystem Readiness Review (CSRR) 2 L-6 weeks Pre-Launch Vehicle On Stand Review L-7 to 14 days Flight Readiness Review (FRR) L-4 to 5 days Pre-LRR L-2 days Launch Readiness Review (LRR)

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 7

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

SMC-S-003(T)- AFSC Space and Missile Systems Center Standard: Quality Assurance for 1 Space and Launch Requirements, 2 SMC-S-005- AFSC Space and Missile Systems Center Standard: Space Systems- Flight 3 Pressurized Systems, 4 SMC-S-006- AFSC Space and Missile Systems Center Standard: Solid Rocket Motor Case 5 Design and Test, 6 SMC-S-008- AFSC Space and Missile Systems Center Standard: Electromagnetic 7 Compatibility Requirements for Space Equipment & Systems, 8 SMC-S-011- AFSC Space and Missile Systems Center Standard: Parts, Materials, and 9 Processes (PMP) Control Program for Launch Vehicles, 10 SMC-S-013- AFSC Space and Missile Systems Center Standard: Reliability Program for 11 Space Systems, 12 SMC-S-016- AFSC Space and Missile Systems Center Standard: Test Requirements for 13 Launch, Upper-stage, and Space Vehicles, 14 SMC-S-018- AFSC Space and Missile Systems Center Standard: Lithium-Ion Battery for 15 Spacecraft Applications, 16 SMC-S-020- AFSC Space and Missile Systems Center Standard: Technical Requirements for 17 Wiring Harness, Space Vehicle, 18 SMC-S-021- AFSC Space and Missile Systems Center Standard: Technical Reviews and 19 Audits for Systems, Equipment, & Computer Software, and 20 ISO 17666 (CDRL B005)- Space Systems- Risk Management. 21

The following reference documents are applicable to systems engineering execution: 23 JANNAF-GL-2012-01-R0- Test and Evaluation Guidelines for Liquid Rocket, 24 SMC-S-004- AFSC Space and Missile Systems Center Standard: Independent Structural 25 Loads Analysis, 26 SMC-S-012- AFSC Space and Missile Systems Center Standard: Software Development for 27 Space Systems, 28 SMC-S-019- AFSC Space and Missile Systems Center Standard: Program and Subcontractor 29 Management, 30 ISO 17666- Space Systems- Risk Management, 31 SMC/LR Risk Management Plan (RMP), 32 Technical Operating Report (TOR)-2005(8583)-4019- Risk Management Plan Guide for 33 Space Acquisition Programs, 34 SMC Guide (SMC-G)-1202- Space Flight Worthiness Criteria (SFWC), 35 SMC-G-1203- Independent Readiness Review Team (IRRT), 36 SMC-G-1204- SMC Readiness Review Process, 37 EELV Systems Engineering Plan (SEP), 38 SAE AS9003- Inspection and Test Quality System, 39 SAE AS9120- Quality Management Systems: Aerospace Requirements for Stockist 40 Distributors, and 41 National Aerospace and Defense Contractors Accreditation Program [Nadcap] AC7004 42

3.2.1 Technical Interchange Meetings 45

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

3.2.2 Contractor Engineering Database 1

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

3.2.3 Systems Engineering Boards and Processes 7

The Contractor shall conduct and support USG Team participation in Launch System: 8 Risk Management Boards (RMB); Engineering Review Boards (ERB); Anomaly 9 Review Boards (ARB); Technical Review Boards (TRB); Corrective Action Boards 10 (CAB); Change Control Boards (CCB) for technical issues; Material Review Boards 11 (MRB); Failure Review Boards (FRB); Parts, Materials, and Processes (PMP) Control 12 Boards; Systems Safety Groups; Preliminary Design Review (PDR); Critical Design 13 Review (CDR); Functional and Physical Configuration Audits (FCA/PCA), System 14 Verification Review (SVR); Production Readiness Review (PRR); Test Readiness 15 Review (TRR); Shipping Readiness Reviews; or Contractor equivalent boards and/or 16 Contractor-equivalent processes. For recurring review boards, the Contractor shall 17 provide electronic invitations to the USG Team no later than 10 calendar days in 18 advance of the board. For all other review boards the Contractor shall provide 19 electronic invitations to the USG Team as soon as possible after the board is scheduled. 20 The Contractor shall provide the USG Team entrance and exit criteria for System 21 Engineering boards. The Contractor shall provide virtual participation capability for 22 System Engineering boards. (Electronic Data Access) 23

3.2.4 Launch Vehicle Configuration Change Reporting 25

The Contractor shall provide the USG Team proposed configuration changes to be 26 implemented on the USG certified/approved launch vehicle configuration. The 27 Contractor shall provide the USG certified/approved launch vehicle configuration in 28 accordance with CDRL A009. (Ref. EELV SEP) Class 1 & 2 changes will be assessed 29 by the USG team however Class 1 changes shall be communicated in phases consistent 30 with SMC-S-001- AFSC Space and Missile Systems Center Standard: Systems 31 Engineering Requirements and Products, SMC-S-002- AFSC Space and Missile 32 Systems Center Standard: Configuration Management, SMC-S-021- AFSC Space and 33 Missile Systems Center Standard: Technical Reviews and Audits for Systems, 34 Equipment, & Computer Software and paragraph 3.2.4.1.1. (Electronic Data Access) 35

A Class 1 change for the purpose of this document is defined as a change that 37 affects the SPRD, SIS, or ICD requirements, drives assessments across 38 multiple technical disciplines/systems, a redesign driving a qualification, a 39 form/fit/function change or any changes to flight critical items listed in the 40 Flight Critical Items List. Within Class 1 design changes, USG has approval 41 authority for changes that affect the SPRD, SIS, ICD, or substantial changes as 42 specified in Table 1. The Contractor shall support participation by the USG 43 Team in system engineering boards and qualification tests/analysis per 44 paragraph 3.2.3. 45

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

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

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

*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 *** Implementation means engineer drawings complete, hardware produced and incorporated and all qualification/acceptance testing complete or USG approved schedule provided

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 initial technical rationale for the Class 1 8 change as available, or upon change identification to the Contractor’s Change 9 Control Board, or equivalent, whichever is earlier. The Contractor shall 10 provide the final technical rationale and obtain SMC/LR approval after final 11 design of any Class 1 change prior to incorporation of the proposed 12 configuration change to the USG certified/approved launch system 13 configuration. (Electronic Data Access) 14

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

3.2.4.2 The Contractor shall communicate with the USG Team of any proposed Class 27 2 configuration change to the USG certified/approved launch vehicle 28 configuration and the initial technical rationale as available for the change as 29 soon as possible but no later than 10 calendar days after identifying the change. 30

Any Class 2 change after L-60 requires USG approval. The Contractor shall 1 provide the final technical rationale NLT 30 days prior to coordinating the 2 Independent Hardware Reviews as defined in section 3.6.6. (Electronic Data 3 Access) 4

3.2.4.3 The Contractor shall communicate changes to the launch system’s interface 5 with Engineering Launch Support System (ELSS) or a change to the 6 Operational Surveillance Requirements as defined in Section 3.5.1.14 as soon 7 as possible but no later than 14 days prior to launch. The Contractor shall 8 obtain SMC/LR approval after final design of changes to the launch system 9 interface with ELSS or a change to the Operational Surveillance Requirements 10 prior to implementation no later than 7 days prior to launch. (Electronic Data 11 Access) 12

3.2.5 Non-Recurring Engineering and Processes 14

3.2.5.1 The Contractor shall provide the USG Team access to the launch system 16 design, systems…