03_Attachment_1_PWS_RFP_1A-4.pdf

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

03 Attachment 1 PWS

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

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

COMPETITIVE LAUNCH SERVICES

PERFORMANCE WORK STATEMENT (PWS)

FA8811-17-R-0004

29 June 2017

Department of the Air Force

Space and Missile Systems Center

Launch Systems Enterprise Directorate

Los Angeles Air Force Base, California

Table of Contents 1

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

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

1.2 PERFORMANCE WORK STATEMENT TERMINOLOGY ..................................................... 2 4

1.2.1 Government ........................................................................................................................... 2 5

1.2.2 United States Government Team .......................................................................................... 2 6

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

1.2.4 OSL Mission Management Team ......................................................................................... 2 8

1.2.5 Electronic Data Access ......................................................................................................... 2 9

2 APPLICABLE DOCUMENTS ............................................................................................................. 3 10

2.1 COMPLIANCE DOCUMENTS ................................................................................................... 3 11

2.2 REFERENCE DOCUMENTS ...................................................................................................... 3 12

2.3 DOCUMENTATION DE-CONFLICTION ................................................................................. 3 13

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

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

3.1.1 Launch System Data ............................................................................................................. 4 16

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

3.1.3 Data Accession List .............................................................................................................. 4 18

3.1.4 Program Management Data Reporting.................................................................................. 4 19

3.1.5 Program Management Reviews ............................................................................................ 4 20

3.1.6 Launch Manifesting Process ................................................................................................. 5 21

3.1.7 System Safety Program ......................................................................................................... 5 22

3.1.8 Range Safety ......................................................................................................................... 5 23

3.1.9 Safety Training ...................................................................................................................... 6 24

3.1.10 Launch System Familiarization Course ................................................................................ 6 25

3.1.11 Program Protection ............................................................................................................... 7 26

3.1.12 Operations Security ............................................................................................................... 7 27

3.1.13 Anti-Terrorism ...................................................................................................................... 7 28

3.1.14 Environmental Requirements ................................................................................................ 8 29

3.1.15 Hazardous Materials ............................................................................................................. 9 30

3.1.16 Incident and Discrepancy Reporting ..................................................................................... 9 31

3.1.17 Public Affairs Activities ...................................................................................................... 10 32

3.1.18 Program Milestone Reviews ............................................................................................... 10 33

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

3.2.1 Technical Interchange Meetings ......................................................................................... 10 35

3.2.2 Contractor Engineering Database ....................................................................................... 10 36

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

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

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

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

3.2.7 Launch System Parameters ................................................................................................. 15 5

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

3.2.9 Aging and Surveillance Program ........................................................................................ 16 7

3.2.10 Performance Capabilities Guide ......................................................................................... 16 8

3.2.11 Quality Management ........................................................................................................... 16 9

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

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

3.3 LAUNCH VEHICLE PRODUCTION ....................................................................................... 17 12

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

3.3.2 Mission-Unique Requirements ........................................................................................... 18 14

3.4 MISSION INTEGRATION ........................................................................................................ 20 15

3.4.1 Mission Integration Data ..................................................................................................... 20 16

3.4.2 Principal Mission Manager Interface .................................................................................. 20 17

3.4.3 Mission Integration Activities ............................................................................................. 20 18

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

3.4.5 Interface Control Document ................................................................................................ 26 20

3.4.6 Mission Design and Analyses ............................................................................................. 27 21

3.4.7 Orbital Debris Mitigation .................................................................................................... 28 22

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

3.4.9 Launch Rehearsal Support .................................................................................................. 31 24

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

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

3.4.12 Flight Hardware Interface Checks ...................................................................................... 33 27

3.4.13 Ground Hardware Interface Checks .................................................................................... 33 28

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

3.4.15 Launch Range Coordination ............................................................................................... 33 30

3.4.16 Mission-Unique Tests ......................................................................................................... 34 31

3.5 LAUNCH OPERATIONS .......................................................................................................... 34 32

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

3.5.2 Launch Infrastructure .......................................................................................................... 45 34

3.5.3 Base and Range Support ..................................................................................................... 45 35

3.5.4 Mission Commodities ......................................................................................................... 45 36

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

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

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

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

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

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

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

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

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

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

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

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

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

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

APPENDIX C: COMPLIANCE DOCUMENTS ....................................................................................... 78 15

APPENDIX D: REFERENCE DOCUMENTS ............................................................................................ 0 16

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

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

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

APPENDIX H: PROGRAM MILESTONE REVIEWS ............................................................................. 26 20

LIST OF TABLES 22

Table 1: Substantial Change Definition ...................................................................................................... 12 23

Table 2: Mission Integration Milestone Reviews ....................................................................................... 22 24

Table 3: Mission Integration Working Groups and Reviews ...................................................................... 23 25

Table 4: Mission Integration Working Group ............................................................................................. 24 26

Table 5: Mission Specific Analyses ............................................................................................................ 27 27

Table 6: Space Flight Worthiness Meetings ............................................................................................... 46 28

This Page Intentionally Left Blank.1

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 10 in 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, 16 consistent with vehicle configuration capabilities and Range Safety restrictions. The 17

Contractor shall provide launch services, which comply with all Range Safety requirements. 18

The Contractor shall make all arrangements with the responsible authorities for the required 19

Range Safety authorization and support for vehicle processing; integrated payload/vehicle 20 processing, 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 38

(Launch Vehicle Production). Finally, (4) the launch campaign is conducted with the 39 performance of 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). Refer to Appendix I for Government Program Contracts Requiring 20

Interface with Aerospace Federally Funded Research and Development Center 21

(FFRDC), Prime, and Support Contractors. Estimates of the number of USG Team 22 individuals associated with specific requirements in this PWS are listed in Appendix E 23

(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), the SV’s Payload 30

Processing Facility (PPF) personnel, and Multi-Manifest Integrating 31

Contractor(s) (MMICs) (if applicable) 32

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

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

1.2.4 OSL Mission Management Team 36

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

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

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

1.2.5 Electronic Data Access 40

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

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

Contractor’s systems, the Contractor shall deliver the data upon the USG Team’s 4 request. Data identified in this PWS shall be provided via electronic access unless 5 otherwise specified in the CDRL descriptions. All data accessed is considered 6 delivered to the Government for the purposes of Defense Federal Acquisition 7

Regulation Supplement 252.227-7015. 8

2 APPLICABLE DOCUMENTS 9

2.1 COMPLIANCE DOCUMENTS 10

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

2.2 REFERENCE DOCUMENTS 12

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

2.3 DOCUMENTATION DE-CONFLICTION 14

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

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

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

3 SPACE LAUNCH SERVICE 19

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

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

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

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

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

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

Independent Mission Assurance activities. 33

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

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

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS 39

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

3.1.1 Launch System Data 1

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

Data supporting this contract residing on the Contractor’s systems throughout the 3 contract period of performance. The Contractor shall communicate with the USG 4

Team any updates (to include manufacturing, testing, operational, or process changes) 5 to delivered Launch System data products as soon as possible but no later than 24 6 hours, or 1 business day, after the updates. Launch system data includes access to fleet 7 data at all sites. Fleet surveillance is essential to the Space Flight Worthiness 8

Certification process, which requires identification of hazards, assessments of risks, 9 mitigation measures, and acceptance of residual risks. Fleet- and mission-specific 10 launch system data are elements affecting the risk baseline accepted by the USG for 11

NSS missions. The Contractor shall notify the Government of any network outages or 12 system upgrades that could interrupt access to the systems. The Contractor shall 13 cooperate with the USG Team to develop a plan to implement this requirement. 14

(Electronic Data Access) 15

3.1.2 Launch System Electronic Data Access Training 16

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

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

3.1.3 Data Accession List 22

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

Accession List (DAL). (CDRL A001) 24

3.1.4 Program Management Data Reporting 25

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

A. Cost Data Summary Report (CDRL A002) 28

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

C. Contractor Business Data Report (CDRL A004) 30

D. Contractor Work Breakdown Structure (CDRL A005) 31

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

(CDRL A006) 33

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

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

October 31 of each calendar year. Contractors may direct questions to the 43

ECMRA help desk. 44

3.1.5 Program Management Reviews 45

The Contractor shall schedule and conduct monthly Program Management Reviews 46

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

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

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

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

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

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

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

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

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

3.1.6 Launch Manifesting Process 19

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

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

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

[AFSPCI] 13-1213) 26

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

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

Data Access) 29

The Contractor shall provide the USG Team a Launch Slot Recommendation 30 and Launch Date Recommendation within the assigned launch period for 31 each launch mission in accordance with contract clause SMC—H006. 32

(CDRL B001) 33

3.1.7 System Safety Program 34

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

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

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

SMC-T-004). (Electronic Data Access) (CDRLs B002, B003, and B005) 39

3.1.8 Range Safety 40

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

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

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

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

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

B005) 46

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

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

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

8581.01 Enclosure 3, paragraph a.4.e., shall comply with the requirements 11 documented in the approved RCC 319-10 (T). The Contractor shall 12 coordinate RCC 319-10 (T) tailoring requests, equivalent level of safety 13 certifications, and non-compliance waiver relief requests for all missions 14 under this contract with SMC/LE and Range Safety prior to formal submittal. 15

(CDRL B005) 16

3.1.9 Safety Training 17

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

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

3.1.10 Launch System Familiarization Course 21

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

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

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

CDRL submittal and approved by the Government for the final CDRL submittal prior 29 to conducting the FAM course. At a minimum, the FAM Course shall include 30 familiarization on the following: LV configurations; propulsion, avionics, and 31 structures systems; manufacturing capabilities; manufacturing facility and processes; 32 launch site facilities, critical ground mechanical, structural, and fluid/gas systems; 33 facility systems and capabilities; launch site/ground command, control, and 34 communications; power systems; flight controls; guidance, navigation, ground and 35 airborne ordnance systems; ground electrical systems; control/telemetry; launch 36 process flow; contractor organizational structure; flight safety systems; launch commit 37 sequence; performance capabilities, personnel roles and responsibilities, and types of 38

Contractor engineering and launch documentation; system-level testing; integrated 39 testing; flight heritage; launch vehicle evolution; basic performance parameters; mass-40 to-orbit capabilities; flight and ground software; quality management; supply chain 41 management; and systems engineering including issue tracking, requirements 42 management, change management, and risk management. The Contractor shall provide 43 a self-study guide report to accompany the training course consisting of the training 44 materials, test questions, and answers. (CDRL A007). 45

3.1.11 Program Protection 1

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

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

DoDI 8582.01. (CDRL A008) 4

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

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

EELV PPP. 7

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

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

Unauthorized Information Distribution resolutions). 11

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

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

LV-specific and supporting Ground system architecture specific information 15 necessary to document, identify, assess, and mitigate security related 16 vulnerabilities and risks. 17

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

The Contractor shall obtain or maintain International Organization for 20

Standardization/International Electrotechnical Commission (ISO/IEC) 21

27000/02 (T) certification. 22

3.1.12 Operations Security 23

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

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

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

EELV OPSEC Plan). 27

3.1.13 Anti-Terrorism 28

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

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

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

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

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

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

Wing ATO checklist. 5

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

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

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

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

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

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

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

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

3.1.14 Environmental Requirements 22

The Contractor shall comply with environmental requirements in accordance with 23

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

Agreements (CSOSA), and CSOSA annexes. 27

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

The Contractor shall include SMC/LE in the coordination process with the 7 host Wing and the environmental regulatory agencies relating to the 8 application, development, or modification of permits or required 9 environmental compliance plans, environmental cleanup actions, or other 10 major efforts subject to environmental laws and regulations. The Contractor 11 shall provide information to the on-site USG Team environmental 12 representatives, during the coordination process, to ensure that the USG 13

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

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

Environmental Impact Analysis Process in accordance with National 17

Environmental Policy Act and Executive Order 12114, Environmental Effects 18

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

3.1.15 Hazardous Materials 20

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

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

3.1.16 Incident and Discrepancy Reporting 24

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

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

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

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

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

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

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

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 1 requirements, or (e) impact a scheduled launch date. The Contractor shall 2 provide the status of ongoing investigations, Contractor incident root cause 3 data, and determination and associated corrective actions. For all other minor 4 incidents and discrepancies, notification shall be no later than 14 calendar 5 days of an event’s occurrence and status reporting will be determined by 6

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

3.1.17 Public Affairs Activities 8

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

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

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

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

3.1.18 Program Milestone Reviews 17

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

Milestone Reviews as defined in Appendix H (Program Milestone Reviews). These 19 reviews may be combined with Contractor reviews with USG approval. The 20

Contractor shall provide the USG Team the briefing slides for each Program Milestone 21

Reviews no later than 5 calendar days prior to the review or as agreed to by the parties. 22

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS 23

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

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

3.2.1 Technical Interchange Meetings 34

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

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

(Electronic Data Access) 37

3.2.2 Contractor Engineering Database 38

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

3.2.3 Systems Engineering Boards and Processes 1

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

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

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

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

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

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

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

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

3.2.4 Launch Vehicle Configuration Change Reporting 17

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

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

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

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

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

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

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

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

Boards and Processes). (Electronic Data Access) 33

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

A Class 1B change for the purpose of this document is defined as a change that drives 37 assessments across multiple technical disciplines/systems, any redesign that has been 38 assessed by the Contractor or USG Team as driving any qualification by test, a 39 form/fit/function change, or any changes to flight-critical items listed in the Flight 40

Critical Items List. The Government Product Line Chief Engineer will work with the 41

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

Class 1A in paragraph 3.2.4.1.1) after contract award. 44

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

Table 1: Substantial Change Definition

Factor Increase A Decrease Communicate Approval Implementatio I\ Changes* Deadlines** n Deadlines***

Minimum qualified +1.5% -1.5% NLT L-15 NLT L-12 NLT L-6 chamber pressure at months months months engine cutoff command (Stage 2 engine)

Minimum qualified +1.5% -1.5% NLT L-15 NLT L-12 NLT L-6 chamber pressure months months months (Stage 2 engine)

Maximum thrnst +3% -1.5% NLT L-15 NLT L-12 NLT L-6 (each engine) months months months

Specific impulse +1% -0.5% NLT L-15 NLT L-12 NLT L-6 (each engine) months months months

Total impulse +1% -0.5% NLT L-15 NLT L-12 NLT L-6 (each stage) months months months

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

Propellant Tan1c +1% -1% NLT L-15 NLT L-12 NLT L-6 Diameter (each stage) months months months

Strnctural safety - -5% NLT L-15 NLT L-12 NLT L-6 factor months months months

Design Fatigue Life - -10% NLT L-15 NLT L-12 NLT L-6 Margins months months months

" Increase/Decrease from design specification assessed as part of baseline ce1tification configuration *Communicate changes means the Contractor shall notify their intent to implement the change to the USG ce1tified/approved launch vehicle configuration and include the impacts to ADCL, change classifications for each change (e.g., Class lA, lB, 2), initial technical rationale (such as Design Evolution Nairntive, Design Requirements and Interfaces, Principles of Operation, impacts to SPRD, and Fonn/Fit/Function), qualification testing schedule, and schedule of when final technical rationale (per 3 .2.4.1.1) will be ready for approval.

** Approval is USG approval or disapproval to the Contractor for the incorporation of the change or USG approved schedule provided (including the final technical rationale per 3 .2.4.1.1 and the completion of all qualification/acceptance testing), unless mutually agreed by both pa1ties for a later date *** Implementation means engineering drawings released, hardwai·e produced and incorporated unless mutually agreed by both pa1ties for a later date.

Note: NLT = No Later Than

3.2.4.1 The Contractor shall communicate with the USG Team No Later Than (NLT) launch minus fifteen (L-15) months or othe1wise indicated in Table 1, p1ior to executing any actions to implement a Class 1 change to the USG ce1tified/approved launch vehicle configuration. The contractor shall provide the initial technical rationale (such as Design Evolution Narrative, Design

Requirements and Interfaces, and Principles of Operation) for the Class 1A 1…

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 .