03_PWS_3_Aug_16_as_posted.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-16-R-0006 11

3 August 2016 14

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

Launch Systems Enterprise 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 ............................................................................................................. 7 9

2.1 COMPLIANCE DOCUMENTS ................................................................................................... 7 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.................................................................................. 9 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 .................................................................................................................... 12 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 ...................................................................................................... 14 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 ....................................................................... 16 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 ................................................................................................ 24 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 ...... 27 25

3.4.14 Launch Range Coordination ............................................................................................... 27 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 ..................................................................................................... 38 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/LE 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 .......................................................... 47 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/LE 3 program office and AFPEO/SP office personnel, but also includes the Aerospace 4 Federally Funded Research and Development Center (FFRDC), SMC/LE Systems 5 Engineering and Integration (SE&I) Contractors, SMC/LE Systems Engineering and 6 Technical Assistance (SETA) support Contractors, SMC/LE Advisory & Assistance 7 Services, the National Reconnaissance Office (NRO)/Office of Space Launch (OSL), 8 NRO/OSL SETA support Contractors, NRO/OSL Independent Verification and 9 Validation (IV&V) support Contractors, the SMC Independent Readiness Review 10 Team (IRRT), Defense Security Service (DSS), Defense Information Systems Agency 11 (DISA), Defense Contract Management Agency (DCMA), Defense Contract Audit 12 Agency (DCAA), 30th Space Wing (30 SW), 45th Space Wing (45 SW), and other 13 organizations as designated by SMC/LE Procuring Contracting Officer (PCO). 14 Appropriate Non-Disclosure Agreements with USG Team Members and the Contractor 15 shall be in place per SMC/LR--H002 ENABLING CLAUSE FOR PRIME AND 16 SUPPORT CONTRACTOR RELATIONSHIPS (JUL 2014). Estimates of the number 17 of USG Team individuals associated with specific requirements in this PWS are listed 18 in Appendix E. 19

1.2.3 Space Vehicle Team 21

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

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

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

LSIC. 31

1.2.4 Electronic Data Access 33

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

1.3 DOCUMENTATION DE-CONFLICTION 45

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

2 APPLICABLE DOCUMENTS 1

2.1 COMPLIANCE DOCUMENTS 3

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

2.2 REFERENCE DOCUMENTS 6

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

3 SPACE LAUNCH SERVICE 9

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

3.7. 15

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

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 27

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

CNSSP-22 1

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

AFI 10-701, 8

AFI 10-1202, 9

AFI 20-114, 10

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

AFI 91-204_AFSPCSUP_I, CNSSI-1253, 14

MIL-STD-881C Appendix J, 15

MIL-STD-1367A, 16

MIL-STD-1791A, 17

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

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

3.1.1 Launch System Data 27

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

3.1.2 Launch System Electronic Data Access Training 42

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

3.1.3 Data Accession List 49

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

3.1.4 Program Management Data Reporting 2

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

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

(CDRL A006) 11

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

3.1.5 Program Management Reviews 25

The Contractor shall schedule and conduct monthly Program Management Reviews 26 (PMR) to: report development and production status, ensure schedules support program 27 objectives, review action items, review program schedules, and discuss any issues. The 28 intent of the PMR is to provide a forum for open dialog between the USG Team and 29 the Contractor. The Contractor shall provide the USG Team the PMR briefing slides 30 no later than 3 calendar days prior to the review or as agreed to by the parties. 31 SMC/LE and the Contractor will agree to the PMR agenda no later than 14 calendar 32 days prior to the PMR or as agreed to by the parties. The PMR agenda shall include a 33 status of the following topics at a minimum: Programmatics, Business Operations, 34 Production Operations, Risk Management, Subsystem(s) Status, Launch Operations, 35 and Wrap Up/Action Items. PMRs will be planned for 2 hours but last no more than 1 36 business day. Locations may rotate between Contractor and Government facilities. 37 The USG team shall be invited to major subcontractor PMRs or equivalent reviews. 38 (Electronic Data Access) 39

3.1.6 Launch Manifesting Process 41

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

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

Option Assessments as part of the launch manifesting process. (Electronic 3 Data Access) 4

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

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

H006. (CDRL B001) 9

3.1.7 System Safety Program 11

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

3.1.8 Range Safety 18

The Contractor shall coordinate the tailoring of AFSPCMAN 91-710 for all missions 19 under this contract with SMC/LE and Range Safety prior to formal submittal. The 20 Contractor shall coordinate relief requests (e.g., Equivalent Level of Safety (ELS), or 21 Waivers) for all missions under this contract with SMC/LE and Range Safety prior to 22 formal submittal. (Electronic Data Access) 23

3.1.8.1 The launch system shall utilize GPS as one of the two mandatory Range Safety 25 tracking data sources. The launch system’s on-board GPS shall comply with 26 the requirements documented in the approved RCC 324-11. The Contractor 27 shall coordinate RCC 324-11 tailoring requests, equivalent level of safety 28 certifications, and non-compliance waiver relief requests for all missions 29 under this contract with SMC/LE and Range Safety prior to formal submittal. 30

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

3.1.9 Safety Training 41

The Contractor shall provide any Contractor-required safety training to USG Team and 42 SV Team (for NRO missions) personnel for Contractor facilities used in performance 43 of this contract to ensure USG Team access to those facilities. 44

3.1.10 Launch System Familiarization Course 46

The Contractor shall provide the USG Team an instructor-led Launch System 47 Familiarization (FAM) Course as needed, up to three times a calendar year to provide 48 training to the Government team supporting NSS missions with the launch service 49 provider: twice at the SMC/LE’s facility, and once at the launch base for this mission. 50

The FAM Course shall be conducted in two parts: a one-day overview for non-1 technical personnel and a two-day in-depth engineering system familiarization. The 2 level of detail covered by the FAM course training materials shall be provided by the 3 Contractor in the initial CDRL submittal and approved by the Government for the final 4 CDRL submittal prior to conducting the FAM course. At a minimum, the FAM Course 5 shall include familiarization on the following: LV configurations, propulsion systems, 6 avionics systems, structures systems, manufacturing facility, manufacturing processes, 7 launch site facilities, facility systems and capabilities, launch site critical ground 8 mechanical, structural, and fluid/gas systems, launch site/ground command, control, 9 and communications, power systems, flight controls, guidance, navigation, ground and 10 airborne ordnance systems, ground electrical systems, control/telemetry, launch process 11 flow, Contractor organizational structure, flight safety systems, launch commit 12 sequence, performance capabilities, personnel roles and responsibilities, and types of 13 Contractor engineering and launch documentation. (CDRL A007). 14

3.1.11 Program Protection 17

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

(CDRL A008) 20

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

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

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

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

3.1.11.3 The Contractor shall provide support to the USG Team in the development of 31 the EELV PPP Contractor-specific Annex. The Contractor’s support to the 32 USG Team in the development of the EELV PPP shall include providing the 33 LV-specific and supporting Ground system architecture specific information 34 necessary to document, identify, assess, and mitigate security related 35 vulnerabilities and risks. 36

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

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

3.1.12 Operations Security 45

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

3.1.13 Anti-Terrorism 1

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

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

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

3.1.13.3 Training: The Contractor shall perform annual training utilizing SMC/LE 17

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

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

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

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

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

3.1.14 Environmental Requirements 37

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

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

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

3.1.14.3 The Contractor shall provide data needed to allow SMC/LE to conduct the 11

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

3.1.15 Hazardous Materials 16

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

3.1.16 Incident and Discrepancy Reporting 21

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

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

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

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

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

3.1.17 Public Affairs Activities 4

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

3.1.18 Program Milestone Reviews 14

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

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 19

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

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

3.2.1 Technical Interchange Meetings 44

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

3.2.2 Contractor Engineering Database 49

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

3.2.3 Systems Engineering Boards and Processes 4

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

3.2.4 Launch Vehicle Configuration Change Reporting 23

The Contractor shall provide the USG Team proposed configuration changes to be 24 implemented on the USG certified/approved launch vehicle configuration. The 25 Contractor shall provide the USG certified/approved launch vehicle configuration. 26 (Ref. EELV SEP) Class 1 and 2 changes will be assessed by the USG team however 27 Class 1 changes shall be communicated in accordance with SMC-S-001- AFSPC Space 28 and Missile Systems Center Standard: Systems Engineering Requirements and 29 Products, SMC-S-002- AFSPC Space and Missile Systems Center Standard: 30 Configuration Management, SMC-S-021- AFSPC Space and Missile Systems Center 31 Standard: Technical Reviews and Audits for Systems, Equipment, & Computer 32 Software and paragraph 3.2.4.1.1. The Contractor shall support participation by the 33 USG Team in system engineering boards and qualification tests/analysis per paragraph 34

3.2.3. (Electronic Data Access) 35

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

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

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

Table 1. Substantial Change Definition 7

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 9 otherwise indicated in Table 1, prior to executing any actions to implement a 10 Class 1 change to the USG certified/approved launch vehicle configuration. 11 The contractor shall provide the initial technical rationale for the Class 1A 12 change as available, or upon change identification to the Contractor’s Change 13 Control Board, or equivalent, whichever is earlier. The Contractor shall 14 provide the final technical rationale and obtain SMC/LE approval after final 15 design of any Class 1A change NLT L-12 months, prior to incorporation of the 16 proposed configuration change to the USG certified/approved launch system 17 configuration. The Contractor shall implement all Class 1 changes NLT 6 18 months or otherwise indicated in Table 1 unless mutually agreed upon by both 19 the Contractor and USG for a later date.