03_Attachment_1_PWS_RFP_1.pdf

PDF 6 MB Posted

Attached to
EELV Phase 1A GPS III Contract Award / AFSPC-8 and AFSPC-12 Contract Award
Solicitation number
FA8811-17-R-0004
Issued by

About this file

Attachment 1: Performance Work Statement

View the file

Other files

Show all 26

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ATTACHMENT 1 4

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV) 6

COMPETITIVE LAUNCH SERVICES 7

PERFORMANCE WORK STATEMENT (PWS) 8

FA8811-17-R-0004 10

03 May 2017 13

Department of the Air Force 16

Space and Missile Systems Center 17

Launch Systems Enterprise Directorate 18

Los Angeles Air Force Base, California 19

Table of Contents 1

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

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

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY ..................................................... 7 4

1.2.1 Government ........................................................................................................................... 7 5

1.2.2 United States Government Team .......................................................................................... 7 6

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

1.2.4 OSL Mission Management Team ......................................................................................... 7 8

1.2.5 Electronic Data Access ......................................................................................................... 7 9

2 APPLICABLE DOCUMENTS ............................................................................................................. 8 10

2.1 COMPLIANCE DOCUMENTS ................................................................................................... 8 11

2.2 REFERENCE DOCUMENTS ...................................................................................................... 8 12

2.3 DOCUMENTATION DE-CONFLICTION ................................................................................. 8 13

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

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

3.1.1 Launch System Data ............................................................................................................. 8 16

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

3.1.3 Data Accession List .............................................................................................................. 9 18

3.1.4 Program Management Data Reporting.................................................................................. 9 19

3.1.5 Program Management Reviews ............................................................................................ 9 20

3.1.6 Launch Manifesting Process ............................................................................................... 10 21

3.1.7 System Safety Program ....................................................................................................... 10 22

3.1.8 Range Safety ....................................................................................................................... 10 23

3.1.9 Safety Training .................................................................................................................... 11 24

3.1.10 Launch System Familiarization Course .............................................................................. 11 25

3.1.11 Program Protection ............................................................................................................. 11 26

3.1.12 Operations Security ............................................................................................................. 12 27

3.1.13 Anti-Terrorism .................................................................................................................... 12 28

3.1.14 Environmental Requirements .............................................................................................. 13 29

3.1.15 Hazardous Materials ........................................................................................................... 13 30

3.1.16 Incident and Discrepancy Reporting ................................................................................... 13 31

3.1.17 Public Affairs Activities ...................................................................................................... 14 32

3.1.18 Program Milestone Reviews ............................................................................................... 14 33

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

3.2.1 Technical Interchange Meetings ......................................................................................... 15 35

3.2.2 Contractor Engineering Database ....................................................................................... 15 36

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

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

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

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

3.2.7 Launch System Parameters ................................................................................................. 19 5

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

3.2.9 Aging and Surveillance Program ........................................................................................ 20 7

3.2.10 Performance Capabilities Guide ......................................................................................... 20 8

3.2.11 Quality Management ........................................................................................................... 20 9

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

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

3.3 LAUNCH VEHICLE PRODUCTION ....................................................................................... 21 12

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

3.3.2 Mission-Unique Requirements ........................................................................................... 22 14

3.4 MISSION INTEGRATION ........................................................................................................ 24 15

3.4.1 Mission Integration Data ..................................................................................................... 24 16

3.4.2 Principal Mission Manager Interface .................................................................................. 24 17

3.4.3 Mission Integration Activities ............................................................................................. 24 18

3.4.4 Payload (Integrated Payload Stack) Integration Information ............................................. 28 19

3.4.5 Interface Control Document ................................................................................................ 29 20

3.4.6 Mission Design and Analyses ............................................................................................. 30 21

3.4.7 Orbital Debris Mitigation .................................................................................................... 32 22

3.4.8 Integrated (Payload [Integrated Payload Stack]/Launch Vehicle) Operations Planning ... 32 23

3.4.9 Launch Rehearsal Support .................................................................................................. 35 24

3.4.10 Third Integrated Crew Exercise (ICE 3) ............................................................................. 36 25

3.4.11 Mission Interface Control Document Requirements Verification ...................................... 36 26

3.4.12 Flight Hardware Interface Checks ...................................................................................... 36 27

3.4.13 Ground Hardware Interface Checks .................................................................................... 37 28

3.4.14 Launch Safety Collision Avoidance and Radio Frequency Power Impingement Data ...... 37 29

3.4.15 Launch Range Coordination ............................................................................................... 37 30

3.4.16 Mission-Unique Tests ......................................................................................................... 37 31

3.5 LAUNCH OPERATIONS .......................................................................................................... 38 32

3.5.1 Launch Site Operations and Support Services .................................................................... 38 33

3.5.2 Launch Infrastructure .......................................................................................................... 48 34

3.5.3 Base and Range Support ..................................................................................................... 49 35

3.5.4 Mission Commodities ......................................................................................................... 49 36

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

3.6.1 Contractor Support to Government Space Flight Worthiness Meetings ............................. 49 2

3.6.2 USG Team Participation in Contractor Production and Engineering Forums .................... 51 3

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

3.6.4 Launch Vehicle As Designed Configuration List (CDRL A009) ....................................... 53 5

3.6.5 Government Hardware Review (CDRL A012) ................................................................... 53 6

3.6.6 Launch Vehicle Production Cycle Review Support ............................................................ 55 7

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

3.6.8 NRO/OSL Launch Mission Assurance Team (MAT)......................................................... 56 9

3.6.9 National Reconnaissance Office Mission Integration Group (MIG) .................................. 57 10

3.7 QUICK REACTION AND ANOMALY RESOLUTION .......................................................... 58 11

3.8 MISSION-UNIQUE LAUNCH VEHICLE SERVICES ............................................................ 58 12

APPENDIX A: GLOSSARY OF TERMS ................................................................................................. 59 13

APPENDIX B: ACRONYMS AND ABBREVIATIONS .......................................................................... 74 14

APPENDIX C: COMPLIANCE DOCUMENTS ....................................................................................... 80 15

APPENDIX D: REFERENCE DOCUMENTS .......................................................................................... 84 16

APPENDIX E: UNITED STATES GOVERNMENT TEAM CALL-OUTS ............................................ 88 17

APPENDIX F: NON-RECURRING design validation DATA PRODUCTS ............................................ 96 18

APPENDIX G: GOVERNMENT HARDWARE REVIEW FORMAT ................................................... 106 19

LIST OF TABLES 21

Table 1: Substantial Change Definition ...................................................................................................... 16 22

Table 2. Mission Integration Milestone Reviews ....................................................................................... 26 23

Table 3. Mission Integration Working Groups and Reviews ...................................................................... 26 24

Table 4. Mission Integration Working Group ............................................................................................. 27 25

Table 5. Mission Specific Analyses ............................................................................................................ 30 26

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

This page intentionally left blank.

1 EVOLVED EXPENDABLE LAUNCH VEHICLE LAUNCH SERVICES 1

1.1 DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES 2

This Performance Work Statement (PWS) defines the launch services the Contractor will 3 perform for United States (U.S.) Air Force (USAF) and National Reconnaissance Office 4

(NRO) missions in order to provide a Launch Vehicle (LV) and deliver a Payload (PL) (aka an 5

Integrated Payload Stack [IPS]) into its intended orbit managed by Air Force Space 6

Command, Space and Missile Systems Center (AFSPC/SMC). This contract is for the 7 procurement of Air Force missions only, to include multi-manifest missions; therefore, 8 requirements with specific NRO-only references are not applicable. NRO-only references 9 within this PWS appear in grey text. Multi-manifest-only references within this PWS appear in 10 italicized text. Multi-manifest missions are those that include more than one space vehicle 11

(SV). The Mission Requirements Annex (MRA) provides configuration details for the multi-12 manifest missions applicable to this contract. 13

The Contractor shall perform all launch service tasks necessary to deliver payloads to defined 14 orbital parameters in compliance with mission requirements as described in Section 3 (Space 15

Launch Service). The launch service shall support missions to all orbital parameters, consistent 16 with vehicle configuration capabilities and Range Safety restrictions. The Contractor shall 17 provide launch services, which comply with all Range Safety requirements. The Contractor 18 shall make all arrangements with the responsible authorities for the required Range Safety 19 authorization and support for vehicle processing; integrated payload/vehicle processing, 20 launch; and launch site maintenance and modifications. 21

The requirements in Section 3 (Space Launch Service) of this PWS are divided into functional 22 areas: 3.1 (Program Management Functions and Tasks), 3.2 (Systems Engineering Functions 23 and Tasks), 3.3 (Launch Vehicle Production), 3.4 (Mission Integration), 3.5 (Launch 24

Operations), 3.6 (Support to Government Space Flight Worthiness), 3.7 (Quick Reaction and 25

Anomaly Resolution), and 3.8 (Mission-Unique Launch Vehicle Services). 26

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

The chronological flow of the launch service first begins with (1) the Contractor establishing 30 the launch vehicle configuration in accordance with the systems engineering functions and 31 tasks of section 3.2 (Systems Engineering Functions and Tasks), culminating in submittal of 32

Contract Data Requirements List (CDRL) A009 with the proposed configuration changes 33 against the certified/approved launch vehicle in accordance with paragraph 3.2.4 (Launch 34

Vehicle Configuration Change Reporting). Second, (2) analysis and qualification is conducted 35 for the proposed launch vehicle configuration while performing the systems engineering 36 functions and tasks of section 3.2 (Systems Engineering Functions and Tasks). Third, 37

(3) production of the flight vehicle is accomplished by performing tasks of section 3.3 (Launch 38

Vehicle Production). Finally, (4) the launch campaign is conducted with the performance of 39 section 3.4 (Mission Integration) and section 3.5 (Launch Operations). 40

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

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY 1

A glossary of definitions for terms used in and applicable to this PWS is provided in Appendix 2

A. An Acronyms and Abbreviations list is provided in Appendix B. 3

1.2.1 Government 4

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

1.2.2 United States Government Team 7

The term “United States Government [USG] Team” refers to the Air Force Space and 8

Missile Systems Center/Launch Systems Directorate (SMC/LE) program office and Air 9

Force Program Executive Officer/Space office personnel, but also includes the 10

Aerospace Federally Funded Research and Development Center (FFRDC), SMC/LE 11

Systems Engineering and Integration (SE&I) Contractors, SMC/LE Systems 12

Engineering and Technical Assistance (SETA) support Contractors, SMC/LE Advisory 13

& Assistance Services, the NRO/Office of Space Launch (OSL), NRO/OSL SETA 14 support Contractors, NRO/OSL Independent Verification and Validation (IV&V) 15 support Contractors, the SMC Independent Readiness Review Team, Defense Security 16

Service, Defense Information Systems Agency, Defense Contract Management 17

Agency, Defense Contract Audit Agency, 30th Space Wing (30 SW), 45th Space Wing 18

(45 SW), and other organizations as designated by SMC/LE Procuring Contracting 19

Officer (PCO). Appropriate Non-Disclosure Agreements with USG Team Members 20 and the Contractor shall be in place per SMC/LR—H002 ENABLING CLAUSE FOR 21

PRIME AND SUPPORT CONTRACTOR RELATIONSHIPS (July 2014). Estimates 22 of the number of USG Team individuals associated with specific requirements in this 23

PWS are listed in Appendix E (United States Government Team Call-Outs). 24

1.2.3 Space Vehicle Team 25

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

Directorate(s)/Program Office(s) and Space Vehicle Contractor(s) (SVC) 27 personnel, but also includes the Aerospace FFRDC, the SV’s SE&I 28

Contractor and SETA support Contractors, the SVC’s designated Launch 29

System Integration Contractor (LSIC) (if applicable), and Multi-Manifest 30

Integrating Contractor(s) (MMICs) (if applicable) 31

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

Office (SPO), SVC and Multi-Manifest Integrating Contractor (MMIC) (if 33 applicable). The interface with the SV Team is the NRO/OSL and the LSIC. 34

1.2.4 OSL Mission Management Team 35

For NRO missions, the term “OSL MMT” refers to the OSL Government Mission 36

Manager and respective team, which includes OSL SETA support Contractors, 37

Aerospace FFRDC, as well as the SV SPO SETA and Aerospace FFRDC. 38

1.2.5 Electronic Data Access 39

The term “(Electronic Data Access)” refers to the ability of the USG Team and SV 40

Teams to remotely access the data via the Contractor’s electronic data repository host 41 systems for the purpose of reviewing, uploading, or downloading specific, identified 42 program-related data on Contractor host systems. The Contractor shall be responsible 43 for providing access to the data, administering user accounts, and ensuring the integrity 44 of the data. The Contractor shall provide the capabilities for the USG Team to 45 subscribe to be notified of any new information on the Contractor’s electronic data 46 repositories. The Contractor shall provide the server/folder location of data and a 47 file/folder directory and confirm appropriate permissions have been provided. If the 48

USG Team is unable to remotely access electronic data through the Contractor’s 1 systems, the Contractor shall deliver the data upon the USG Team’s request. Data 2 identified in this PWS shall be provided via electronic access unless otherwise 3 specified in the CDRL descriptions. All data accessed is considered delivered to the 4

Government for the purposes of Defense Federal Acquisition Regulation Supplement 5

252.227-7015. 6

2 APPLICABLE DOCUMENTS 7

2.1 COMPLIANCE DOCUMENTS 8

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

2.2 REFERENCE DOCUMENTS 10

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

2.3 DOCUMENTATION DE-CONFLICTION 12

If any conflict or inconsistency exists between the signed mission Interface Control Document 13

(ICD), the MRA, the Standard Interface Specification (SIS), or this PWS, the mission ICD 14 shall be given precedence. Other documents shall be given precedence in accordance with 15

Federal Acquisition Regulation (FAR) 52.215-08 or FAR 52.212-04(s), as applicable. 16

3 SPACE LAUNCH SERVICE 17

The Government requires the services of an integrated Launch System to meet NSS launch needs. 18

Space Launch Services for NSS missions include LV production and transportation, mission 19 integration, launch operations, support to independent Government mission assurance, base and 20 range support, mission commodities, all associated program management and systems engineering 21 functions and tasks, and any required special studies as defined in PWS Section 3.7 (Quick Reaction 22 and Anomaly Resolution). 23

The Contractor shall provide Space Launch Services for NSS missions in accordance with the 24 performance requirements stated in the Evolved Expendable Launch Vehicle (EELV) System 25

Performance Requirements Document (SPRD), EELV Standard Interface Specification (SIS), MRA 26

(for USAF only), Interface Requirements Document (IRD) (for NRO only), and mission ICD. The 27

Contractor shall control, document, and provide the USG Team continuous access and insight into 28 its processes and assessments of progress and performance of all Space Launch Service 29 requirements, provide continuous access to the Contractor’s command media, and support the USG’s 30

Independent Mission Assurance activities. 31

For each launch service provided under this contract, the Contractor shall provide the required 32 payload mass-to-orbit performance margin in accordance with the SPRD, the MRA, and the mission 33

ICD. The Government shall own any excess performance margin beyond that required to meet the 34 mission requirements unless the Government approves the release of such margin. Any release of 35 margin shall be documented in the applicable mission ICD. 36

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 37

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

3.1.1 Launch System Data 43

The Contractor shall provide and maintain the USG Team access to all Launch System 44

Data supporting this contract residing on the Contractor’s systems throughout the 45 contract period of performance. The Contractor shall communicate with the USG Team 1 any updates (to include manufacturing, testing, operational, or process changes) to 2

Launch System data as soon as possible but no later than 24 hours, or 1 business day, 3 after the updates. Launch system data includes access to fleet data at all sites. Fleet 4 surveillance is essential to the Space Flight Worthiness Certification process, which 5 requires identification of hazards, assessments of risks, mitigation measures, and 6 acceptance of residual risks. Fleet- and mission-specific launch system data are 7 elements affecting the risk baseline accepted by the USG for NSS missions. The 8

Contractor shall notify the Government of any network outages or system upgrades that 9 could interrupt access to the systems. The Contractor shall cooperate with the USG 10

Team to develop a plan to implement this requirement. (Electronic Data Access) 11

3.1.2 Launch System Electronic Data Access Training 12

The Contractor shall provide the USG Team Launch System Electronic Data Access 13 computer-based training as needed. Such training shall include, but is not limited to: 14

Work Authorizing Documents (WAD) access and feedback, anomaly/non-conformance 15 system, launch console data system, specification and engineering file management 16 system, and Contractor employee online training database. (Electronic Data Access) 17

3.1.3 Data Accession List 18

The Contractor shall maintain a list of data supporting this contract on a Data 19

Accession List (DAL). (CDRL A001) 20

3.1.4 Program Management Data Reporting 21

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

A. Cost Data Summary Report (CDRL A002) 24

B. Functional Cost-Hour Report (CDRL A003) 25

C. Contractor Business Data Report (CDRL A004) 26

D. Contractor Work Breakdown Structure (CDRL A005) 27

E. Integrated Program Management Report – Integrated Master Schedule (IMS) 28

(CDRL A006) 29

The Contractor shall report all Contractor labor hours (including subcontractor 30 labor hours) required for performance of services provided under this contract 31 via the secure data collection site (i.e., Enterprise-wide Contractor Manpower 32

Reporting Application [ECMRA]). The Contractor is required to completely 33 fill in all required data fields using the following Web address: 34 http://www.ecmra.mil. Reporting inputs will be for the labor executed during 35 the period of performance during each Government fiscal year (FY), which 36 runs from October 1 through September 30. While inputs may be reported any 37 time during the FY, all data shall be reported no later than (NLT) October 31 38 of each calendar year. Contractors may direct questions to the ECMRA help 39 desk. 40

3.1.5 Program Management Reviews 41

The Contractor shall schedule and conduct monthly Program Management Reviews 42

(PMRs) to: report development and production status, ensure schedules support 43 program objectives, review action items, review program schedules, and discuss any 44 issues. The intent of the PMR is to provide a forum for open dialog between the USG 45

Team and the Contractor. The Contractor shall provide the USG Team the PMR 46 briefing slides no later than 3 calendar days prior to the review or as agreed to by the 47 parties. SMC/LE and the Contractor will agree to the PMR agenda no later than 14 48 calendar days prior to the PMR or as agreed to by the parties. The PMR agenda shall 1 include a status of the following topics at a minimum: Programmatics, Business 2

Operations, Flight Manifest Status, Production Operations, Quality Metrics, 3

Configuration Management, Risk Management, Subsystem(s) Status, Mission 4

Integration Status, Non-Recurring Work Status (as applicable), Launch Operations, 5

Major Subcontractor(s) Performance (as applicable), and Wrap Up/Action Items. 6

PMRs will be planned for 3 hours but last no more than 1 business day. Locations may 7 rotate between Contractor and Government facilities. The USG team shall be invited to 8 major subcontractor PMRs or equivalent reviews. (Electronic Data Access) 9

On a quarterly basis in conjunction with a PMR, the Contractor shall brief the 10

USG team (including on-site residents) on the Contractor’s manufacturing and 11 production capabilities to include existing capabilities, ramp-up plans, rate 12 outputs, site overview, facility layouts, facility updates, production flow, and 13 production readiness status. 14

3.1.6 Launch Manifesting Process 15

The Contractor shall participate in the Government-led launch scheduling and 16 manifesting process to include the following reviews and meetings: a semi-annual 17

Current Launch Schedule Review Board, a semi-annual Government Integrated 18

Meeting, a monthly Senior Management Review, weekly launch manifest status 19 teleconferences, and a Contractor-led monthly manifest review. The Contractor should 20 assume a meeting length of 4 hours each. (Ref. Air Force Space Command Instruction 21

[AFSPCI] 13-1213) 22

The Contractor shall develop and provide the USG Team Launch Schedule 23

Option Assessments as part of the launch manifesting process. (Electronic 24

Data Access) 25

The Contractor shall provide the USG Team a Launch Slot Recommendation 26 and Launch Date Recommendation within the assigned launch period for 27 each launch mission in accordance with contract clause SMC—H006. (CDRL 28

B001) 29

3.1.7 System Safety Program 30

The Contractor shall establish, implement, and maintain a System Safety Program in 31 accordance with Military Standard (MIL-STD)-882E (tailored consistent with 32

SMC-T-004). The Contractor shall provide a System Safety Program Plan and Safety 33

Assessment Report in accordance with MIL-STD-882E (tailored consistent with 34

SMC-T-004). (Electronic Data Access) (CDRLs B002 and B003) 35

3.1.8 Range Safety 36

The Contractor shall coordinate the tailoring of Air Force Space Command Manual 37

(AFSPCMAN) 91-710 for all missions under this contract with SMC/LE and Range 38

Safety prior to formal submittal. The Contractor shall coordinate relief requests (e.g., 39

Equivalent Level of Safety, or Waivers) for all missions under this contract with 40

SMC/LE and Range Safety prior to formal submittal. (Electronic Data Access) 41

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

The launch system’s Autonomous Flight Safety System, or flight safety 3 system using a secure command system employing National Security 4

Agency-approved cryptography in accordance with DoD Instruction (DoDI) 5

8581.01 Enclosure 3, paragraph a.4.e., shall comply with the requirements 6 documented in the approved RCC 319-10 (T). The Contractor shall coordinate 7

RCC 319-10 (T) tailoring requests, equivalent level of safety certifications, 8 and non-compliance waiver relief requests for all missions under this contract 9 with SMC/LE and Range Safety prior to formal submittal. 10

3.1.9 Safety Training 11

The Contractor shall provide any Contractor-required safety training to USG Team and 12

SV Team personnel for Contractor facilities used in performance of this contract to 13 ensure USG Team access to those facilities. 14

3.1.10 Launch System Familiarization Course 15

The Contractor shall provide the USG Team an instructor-led Launch System 16

Familiarization (FAM) Course up to three times a calendar year to provide training to 17 the Government team supporting NSS missions with the launch service provider: twice 18 at the SMC/LE’s facility, and once at the launch base for this contract. The FAM 19

Course shall be conducted in two parts: a 1-day overview for non-technical personnel 20 and a 2-day in-depth engineering system familiarization. The level of detail covered by 21 the FAM course training materials shall be provided by the Contractor in the initial 22

CDRL submittal and approved by the Government for the final CDRL submittal prior 23 to conducting the FAM course. At a minimum, the FAM Course shall include 24 familiarization on the following: LV configurations; propulsion, avionics, and 25 structures systems; manufacturing capabilities; manufacturing facility and processes; 26 launch site facilities, critical ground mechanical, structural, and fluid/gas systems; 27 facility systems and capabilities; launch site/ground command, control, and 28 communications; power systems; flight controls; guidance, navigation, ground and 29 airborne ordnance systems; ground electrical systems; control/telemetry; launch 30 process flow; contractor organizational structure; flight safety systems; launch commit 31 sequence; and performance capabilities, personnel roles and responsibilities, and types 32 of Contractor engineering and launch documentation; system-level testing; integrated 33 testing; flight heritage; launch vehicle evolution; basic performance parameters; mass-34 to-orbit capabilities; flight and ground software; quality management; supply chain 35 management; systems engineering including issue tracking, requirements management, 36 change management, and risk management. The Contractor shall provide a self-study 37 guide report to accompany the training course consisting of the training materials, test 38 questions, and answers. (CDRL A007). 39

3.1.11 Program Protection 40

The Contractor shall develop, provide, implement, and maintain, a Program Protection 41

Implementation Plan in accordance with the EELV Program Protection Plan (PPP) and 42

DoDI 8582.01. (CDRL A008) 43

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

Program Protection Surveys at all Contractor facilities in accordance with the 2

EELV PPP. 3

The Contractor shall attend and support the quarterly EELV System Security 4

Working Group and one security-related meeting per month in accordance 5 with the EELV PPP (e.g., Information Technology [IT] Security Breach or 6

Unauthorized Information Distribution resolutions). 7

The Contractor shall provide support to the USG Team in the development of 8 the EELV PPP Contractor-specific Annex. The Contractor’s support to the 9

USG Team in the development of the EELV PPP shall include providing the 10

LV-specific and supporting Ground system architecture specific information 11 necessary to document, identify, assess, and mitigate security related 12 vulnerabilities and risks. 13

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

The Contractor shall obtain or maintain International Organization for 16

Standardization/International Electrotechnical Commission (ISO/IEC) 17

27000/02 (T) certification. 18

3.1.12 Operations Security 19

The Contractor shall develop, implement, and maintain an Operations Security 20

(OPSEC) program in accordance with contract Attachment 2, DoD Contract Security 21

Classification Specification (DD254). (Ref. Air Force Instruction [AFI] 10-701 and the 22

EELV OPSEC Plan). 23

3.1.13 Anti-Terrorism 24

The Contractor shall implement and maintain an Anti-terrorism (AT) program for 25 activities at Cape Canaveral Air Force Station (CCAFS), Kennedy Space Center 26

(KSC), and Vandenberg Air Force Base (VAFB) as appropriate. (Ref. AFI 10-245) The 27

Contractor shall ensure SMC/LE approval prior to taking any action regarding anti-28 terrorism requirements requested by the 30 SW Operations Security Office or 45 29

SW/Anti-Terrorism Office (ATO) that change or add any additional anti-terrorism 30 requirements to this PWS paragraph and subparagraphs. 31

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

Program Reviews: The Contractor shall perform an in-house Annual Review 34 of its AT program, which shall be documented in accordance with the host 35

Wing ATO checklist. 36

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

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

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

Random AT Measures (RAMs): The Contractor shall perform prescribed 43

RAMs or alternate RAMs that are preapproved by SMC/LE (up to five per 44 month). Completed RAMs shall be documented in a format prescribed by 1

SMC/LE and reported quarterly to the Host Wing ATO. 2

Mission Essential Personnel: The Contractor shall create and maintain a 3

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

3.1.14 Environmental Requirements 9

The Contractor shall comply with environmental requirements in accordance with 10

AFSPCMAN 91-710 as applicable and all relevant and applicable Federal, State, and 11 local environmental laws, regulations, and executive orders, and base regulations as 12 documented in the appropriate license, lease, Commercial Space Operations Support 13

Agreements (CSOSA), and CSOSA annexes. 14

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

The Contractor shall include SMC/LE in the coordination process with the 21 host Wing and the environmental regulatory agencies relating to the 22 application, development, or modification of permits or required 23 environmental compliance plans, environmental cleanup actions, or other 24 major efforts subject to environmental laws and regulations. The Contractor 25 shall provide information to the on-site USG Team environmental 26 representatives, during the coordination process, to ensure that the USG 27

Team is aware of the risks and alternatives that are evaluated or accepted 28 during this process. (Electronic Data Access) 29

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

Environmental Impact Analysis Process in accordance with National 31

Environmental Policy Act and Executive Order 12114, Environmental Effects 32

Abroad of Major Federal Actions, dated 4 January 1979. 33

3.1.15 Hazardous Materials 34

The Contractor shall develop, provide, maintain, and comply with a hazardous 35 materials management plan in accordance with AFSPCMAN 91-710 and Task 108 of 36

MIL-STD 882-E. (CDRL B004) (Ref. National Aerospace Standard 411) 37

3.1.16 Incident and Discrepancy Reporting 38

The Contractor shall maintain an incident and discrepancy reporting system. The 39

Contractor shall notify the USG Team, via Contractor-identified internal reporting 40 systems, of all incidents and discrepancies. 41

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

(1) loss of life or severe personal injury as defined per Occupational Safety 44 and Health Administration reporting requirements; (2) damage to any flight 45 hardware or Critical Ground Support Equipment (GSE); or (3) damage to 46

Critical GSE occurring during vehicle build, test, transportation, processing, 1 or facility readiness operations. The notification shall be provided as soon as 2 operationally possible, but no later than 48 hours (post-emergency response 3 and safety hazard securing) and in accordance with already-established 4

Contractor reporting procedures. The Contractor shall provide the status of 5 ongoing investigations, Contractor incident root cause data, and 6 determination and associated corrective actions. (Electronic Data Access) 7

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

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

(c) changes to the IMS, (d) waivers or exceptions to test or verification 15 requirements, or (e) impact a scheduled launch date. The Contractor shall 16 provide the status of ongoing investigations, Contractor incident root cause 17 data, and determination and associated corrective actions. For all other minor 18 incidents and discrepancies, notification shall be no later than 14 calendar 19 days of an event’s occurrence and status reporting will be determined by 20

SMC/LE on a case-by-case basis. 21

3.1.17 Public Affairs Activities 22

The Contractor shall support Public Affairs activities by coordinating with SMC/LE 23 and the Space and Missile Systems Center Public Affairs office (SMC/PA). The 24

Contractor shall coordinate press statements, press releases, or any related public affairs 25 items with SMC/PA prior to release to the general public. 26

For NRO missions, the Contractor shall support Public Affairs activities to include 27

Launch External Affairs Forum (LEAF) coordination. The Contractor shall submit all 28 launch memorabilia; press statements, press releases, or any related public affairs items 29 to the NRO LEAF for approval prior to production or release to the general public. 30

3.1.18 Program Milestone Reviews 31

The Contractor shall conduct and provide USG Team participation in the Program 32

Milestone Reviews as defined in Appendix H. These reviews may be combined with 33

Contractor reviews with USG approval. The Contractor shall provide the USG Team 34 the briefing slides for each Program Milestone Reviews no later than 5 calendar days 35 prior to the review or as agreed to by the parties. 36

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 37

In order to ensure the successful completion of this mission and associated tasks required for 38 mission success, the Contractor shall perform systems engineering functions and tasks 39 necessary to deliver launch services consistent with operational safety, suitability, and 40 effectiveness and Environmental Safety and Occupational Health guidance on EELV systems. 41

In order to ensure the Government can accomplish its mission assurance functions and tasks, 42 the Contractor shall maintain and provide the USG Team insight into the systems engineering 43 processes supporting the launch service. In order to facilitate smooth and unimpeded 44 communication between the USG Team and the Contractor, the Contractor shall identify a 45 technical Point of Contact (POC) (vehicle Chief Engineer or equivalent) to work with the USG 1 counterpart to manage the activities in this section. 2

3.2.1 Technical Interchange Meetings 3

The Contractor shall invite the USG Team to Technical Interchange Meetings or any 4

Contractor-equivalent boards and make available any meeting documentation materials. 5

(Electronic Data Access) 6

3.2.2 Contractor Engineering Database 7

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

3.2.3 Systems Engineering Boards and Processes 14

The Contractor shall conduct and support USG Team participation in Launch System: 15

Risk Management Boards; Engineering Review Boards (ERB); Anomaly Review 16

Boards (ARB); Technical Review Boards; Corrective Action Boards; Change Control 17

Boards for technical issues; Material Review Boards; Failure Review Boards; Parts, 18

Materials, and Processes Control Boards; Systems Safety Groups (SSGs); Preliminary 19

Design Review; Critical Design Review; Functional and Physical Configuration 20

Audits, System Verification Review; Production Readiness Review; Test Readiness 21

Review; Shipping Readiness Reviews; or Contractor equivalent boards or Contractor-22 equivalent processes. For recurring review boards, the Contractor shall provide 23 electronic invitations to the USG Team no later than 10 calendar days in advance of the 24 board. For all other review boards the Contractor shall provide electronic invitations to 25 the USG Team as soon as possible after the board is scheduled. The Contractor shall 26 provide the USG Team entrance and exit criteria for System Engineering boards, as 27 required by their command media. The Contractor shall provide virtual participation 28 capability for Systems Engineering boards. (Electronic Data Access) 29

3.2.4 Launch Vehicle Configuration Change Reporting 30

The Contractor shall provide the USG Team proposed configuration changes to be 31 implemented on the USG certified/approved launch vehicle configuration. The 32

Contractor shall provide the USG certified/approved launch vehicle configuration at the 33

Mission Kickoff Review. If any changes are proposed, the Contractor shall identify the 34 impacted As-Designed Configuration List (ADCL) (CDRL A009) items and identify 35 the class of change (e.g., Class 1A, 1B, 2) being proposed (classification defined 36 below). (Ref. EELV Systems Engineering Plan) Class 1 and 2 changes will be assessed 37 by the USG team; however, Class 1 changes shall be communicated in accordance with 38

Space and Missile Systems Center Standard (SMC-S)-001- AFSPC Space and Missile 39

Systems Center Standard: Systems Engineering Requirements and Products, SMC-S-40

002- AFSPC Space and Missile Systems Center Standard: Configuration Management, 41

SMC-S-021- AFSPC Space and Missile Systems Center Standard: Technical Reviews 42 and Audits for Systems, Equipment, & Computer Software and paragraph 3.2.4.1.1. 43

The Contractor shall support participation by the USG Team in system engineering 44 boards and qualification tests/analysis per paragraph 3.2.3 (Systems Engineering 45

Boards and Processes). (Electronic Data Access) 46

Contractor Product Line Chief Engineer (or equivalent) to mutually establish the appropriate level of reporting for Class 1B changes (a subset of the items listed for

Class 1A in paragraph 3.2.4.1.1) after contract award.

A Class 2 change is defined as any change that does not meet the definition of a Class

1 change as described herein.

The Contractor shall communicate with the USG Team No Later Than (NLT) 1 launch minus fifteen (L-15) months or otherwise indicated in Table 1, prior to 2 executing any actions to implement a Class 1 change to the USG 3 certified/approved launch vehicle configuration. The contractor shall provide 4 the initial technical rationale (initial set of data as defined in section 3.2.4.1.1) 5 for the Class 1A change as available, or upon change identification to the 6

Contractor’s Change Control Board, or equivalent, whichever is earlier. The 7

Contractor shall submit a Government-approved Non-Recurring Design 8

Validation Work Closure plan (CDRL B020) that demonstrates Government 9 approval of all open Non-Recurring Design Validation (NRDV) work in 10 accordance with paragraph 3.2.4 Table 1. The Contractor shall assume that 11

Government approval and verification/validation will be obtained 4 months 12 following completion of final contractor NRDV efforts. The Contractor shall 13 provide the final technical rationale and obtain SMC/LE approval after final 14 design of any Class 1A change NLT L-12 months, prior to incorporation of 15 the proposed configuration change to the USG certified/approved launch 16 system configuration. The Contractor shall implement all Class 1 changes 17

NLT L-6 months or otherwise indicated in Table 1 unless mutually agreed 18 upon by both the Contractor and USG for a later date. (Electronic Data 19

Access) 20

For Class 1A changes, the technical rationale (Change Assessment 21 package) shall include Design Evolution Narrative, Design 22

Requirements and Interfaces, Design Environments, As-built 23

Design, Software Design, Supporting Design Analyses, Principles 24 of Operation, Limited Operating Life Items Tracked, Summary of 25

Required Manufacturing Processes, Summary of Logistics, 26

Summary of Failure Modes and Effects Analysis and Reliability 27

Assessment, Summary of Identified Risks, 28

Acceptance/Qualification Test Plan/Procedures, Test-Like-You-Fly 29

Exceptions and Deviations, Qualification Rationale, Qualification 30

Test Results, List of Test Nonconformances, Summary of Flight 31

Data, and Configuration Differences Between Unit Under Test 32

(UUT) and Qualification Unit (For example UUT includes Flight 33 and Proto Qualification Units), unless mutually agreed by both 34 parties to be non-applicable. 35

The Contractor shall communicate with the USG Team of any proposed 36

Class 2 configuration change to the USG certified/approved launch vehicle 37 configuration and the initial technical rationale as available for the change as 38 soon as possible but no later than 10 calendar days after identifying the 39 change. Any Class 2 change after L-60 requires Government Product Line 40

Chief Engineer approval. The Contractor shall provide the final technical 41 rationale NLT 30 days prior to coordinating the Government Hardware 42

Reviews as defined in section 3.6.5 (Government Hardware Review [CDRL 1

A012). (Electronic Data Access) 2

The Contractor shall communicate changes to the launch system’s interface 3 with Engineering Launch Support System (ELSS) or a change to the 4

Operational Surveillance Requirements as defined in Section 3.5.1.14 5

(Operational Surveillance Requirements) as soon as possible but no later than 6

14 days prior to testing operations or launch. The Contractor shall obtain 7

SMC/LE approval after final design of changes to the launch system…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .