3 Attachment 1 PWS 20 December 2019.pdf

ATTACHMENT 1

NATIONAL SECURITY SPACE LAUNCH (NSSL)

PHASE 2 LAUNCH SERVICE PROCUREMENT

PERFORMANCE WORK STATEMENT (PWS)

FA8811-19-R-0002

3 May 2019

Amendment 1: 23 July 2019

Amendment 2: 20 December 2019

Department of the Air Force

Space and Missile Systems Center

Launch Enterprise Systems Directorate

Los Angeles Air Force Base, California

Table of Contents

1 NATIONAL SECURITY SPACE LAUNCH SERVICES

1.1 DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES

1.2 DEFINITION OF ROLES and Responsibilities

1.2.1 Roles

1.2.2 Responsibilities

2 APPLICABLE DOCUMENTS

2.1 COMPLIANCE DOCUMENTS

2.2 REFERENCE DOCUMENTS

2.3 DOCUMENTATION DE-CONFLICTION

3 SPACE LAUNCH SERVICE

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS

3.1.1 LSS: Risk Management

3.1.2 LSS: Manufacturing Management

3.1.3 LSS: Reliability Program

3.1.4 LSS: Launch System Data

3.1.5 LSS: Launch System IDE Training

3.1.6 LSS: Program Management Data Reporting

3.1.7 LSS: Program Management Reviews

3.1.8 Mission Integration Management Plan (MIMP)

3.1.9 LS/LSS: Launch Manifesting Process

3.1.10 LSS: System Safety Program

3.1.11 LSS: Range Safety

3.1.12 LSS: Autonomous Flight Safety System (AFSS)

3.1.13 LS/LSS: Safety Training

3.1.14 LSS: Launch System Familiarization Course

3.1.15 LSS: Program Protection

3.1.16 LSS: Operations Security

3.1.17 LSS: Anti-Terrorism

3.1.18 LSS: Cyber Security

3.1.19 LSS: Physical Security

3.1.20 LSS: Environmental Requirements (NSS)

3.1.21 LSS: Hazardous Materials

3.1.22 LSS: Incident and Discrepancy Reporting

3.1.23 LS: Public Affairs Activities

3.1.24 LS: Mission Milestone Reviews

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS

3.2.1 LSS: Technical Interchange Meetings

3.2.2 LSS: Contractor Engineering Databases

3.2.3 LSS: Systems Engineering Boards and Processes

3.2.4 LSS: Launch System Configuration Management

3.2.5 LSS: Launch System Verification (component, unit, subsystem, system, launch site)

3.2.6 LS/FS: Launch System Parameters

3.2.7 LSS: Performance Capabilities Guide

3.2.8 LSS: Logistics

3.2.9 LSS: Quality Management

3.3 LAUNCH VEHICLE PRODUCTION

3.3.1 LS/LSS: Launch Vehicle Hardware and Software

3.3.2 LS: Mission-Unique Requirements

3.4 MISSION INTEGRATION

3.4.1 MI: Mission Integration Data

3.4.2 MI: Mission Integration Management

3.4.3 MI: Payload Integration Information

3.4.4 MI: Interface Control Document

3.4.5 MI: Mission Design and Analyses

3.4.6 MI: Integrated Operations Planning

3.4.7 MI: Launch Rehearsal Support

3.4.8 MI: Mission Interface Control Document Requirements Verification

3.4.9 MI: Flight Hardware Interface Checks

3.4.10 MI: Ground Hardware Interface Checks

3.4.11 MI: Launch Range Coordination

3.4.12 MI: Payload Processing

3.4.13 MI: Launch Operations Validation Activities

3.4.14 MI: Reflight Mission Integration

3.5 MISSION OPERATIONS

3.5.1 LS/LSS/FS: Personnel Access

3.5.2 LSS: Launch Site Operations and Support Services (Non-Discrete)

3.5.3 LS/LSS: Launch Site Operations and Support Services (Discrete)

3.5.4 LSS: Launch Infrastructure and GSE

3.5.5 LS: Base and Range Support

3.5.6 LS: Mission Commodities

3.5.7 LSS: Landing and Recovery Operations

3.6 SUPPORT TO GOVERNMENT SPACE FLIGHT WORTHINESS

3.6.1 LSS: Space Flight Worthiness Working Groups

3.6.2 LS/LSS: USG Team Participation in Contractor Production and Engineering Forums

3.6.3 LSS: Contractor Support to SMC/LE Issue Closure for NSS missions

3.6.4 LS: Orbital Debris Mitigation

3.6.5 LS: Launch Safety Collision Avoidance & Radio Frequency Power Impingement Data .. 38

3.6.6 LSS: Government Hardware Review (CDRL A034)

3.6.7 LS: Launch Vehicle Production Cycle Review Support

3.6.8 LS: Post-Flight Data Review

3.6.9 FS: Post-Flight Data Review for Non-NSS Missions

3.7 LEVEL OF EFFORT ACTIVITIES

3.7.1 LOE: Quick Reaction/Anomaly Resolution

3.7.2 LOE: Launch Mishap Investigation

3.7.3 LOE: Special Studies

3.8 MISSION Unique SERVICES

3.8.1 MU: Mission-Unique Hardware and Software

3.8.2 MU: Third Integrated Crew Exercise (ICE 3)

3.8.3 MU: Augmented Ordnance Support Option

3.8.4 MU: Instrument Component Purge Option

3.8.5 MU: Video Coverage Option

3.8.6 MU: Radio Frequency (RF) Links Option

3.8.7 MU: Dipout Maneuver Option

3.8.8 MU: Witness Plates Option

3.8.9 MU: RF Attenuation Option

3.8.10 MU: MSE Accommodations Option

3.8.11 MU: Flight Command and Telemetry Interfaces Option

3.8.12 MU: Supplemental Aft Payload Compartment Gas Conditioning Option

3.8.13 MU: Additional Routine Access Doors

3.8.14 MU: Acoustic Environment (Molniya Category B) Option

3.8.15 MU: Acoustic Environment (GEO 1 Category B) Option

3.8.16 MU: Launch Vehicle-to-Payload Shock (GEO 1 Category B) Option

3.8.17 MU: Multi-Manifest Mission Option

3.8.18 MU: Pathfinder Option

3.8.19 MU: Reserved

3.8.20 MU: Classified SV Option

3.8.21 MU: Wet Dress Rehearsal (WDR)

3.8.22 MU: Reserved

3.8.23 MU: GPS III Kit

3.8.24 MU: Aft End of Upper Stage Ride Share Adapter

3.8.25 MU: Secondary Payload Adapter Procurement and Integration

3.8.26 MU: ESPA Grande Procurement and Integration

3.8.27 MU: Propulsive ESPA Integration

3.8.28 MU: Acoustic Category A Environment in a Category B Payload Envelope

3.8.29 MU: Category C Payload Fairing

3.9 Early Integration Studies (EIS)

3.9.1 Simple EIS

3.9.2 Standard EIS

3.9.3 Complex EIS

3.9.4 Additional EIS tasks

3.10 Other Special Studies

APPENDIX A: GLOSSARY OF TERMS

APPENDIX B: ACRONYMS AND ABBREVIATIONS

APPENDIX C: COMPLIANCE DOCUMENTS

APPENDIX D: REFERENCE DOCUMENTS

APPENDIX E: MEETINGS AND REVIEWS

APPENDIX F: MISSION MILESTONE REVIEWS

APPENDIX G: CHANGE CLASS

LIST OF TABLES

Table 1: Mission Integration Working Groups and Reviews

Table 2: Mission Specific Analyses*

Table 3: Space Flight Worthiness Working Groups

Nom. Start Nom. End Nom. Freq. Nom. Length Format Location Contractor USG Team M

3.1.7 Program Management Reviews ATP+1 Month End PoP Monthly 2 hours In‐Person Various Lead Participate

3.1.9.1 Current Launch Schedule Review Board ATP End PoP Semi‐Annual 2 hours Teleconference Virtual Support Participate

3.1.9.1 Government Integrated Meeting ATP End PoP Semi‐Annual 2 hours Teleconference Virtual Support Lead

3.1.9.1 Senior Management Review ATP+1 Month End PoP Monthly 1 hour Teleconference Virtual Support Lead

3.1.9.1 Launch Manifest Status Teleconference ATP+6 Months End PoP Weekly 1 hour Teleconference Virtual Support Lead

3.1.9.1 Manifest Review ATP+6 Months End PoP Monthly 1 hour Teleconference Virtual Lead Participate

3.1.10.2 System Safety Working Groups ATP+6 Months End PoP Quarterly Contractor‐

Dependent In‐Person

Contactor Site or Launch Site Support Lead

3.1.10.2 System Safety Group ATP End PoP Annually 8 hours In‐Person SMC Support Lead

3.1.13.1 Contractor‐Required Safety Training ATP End PoP

As Needed‐Per

Mission

Contractor‐

Dependent

Contractor‐

Dependent

Contractor‐

Dependent Lead Participate

3.1.13.2 Contractor Facility Training ATP End PoP

As Needed‐

Ongoing

Contractor‐

Dependent

Contractor‐

Dependent

Contractor‐

Dependent Lead Participate

3.1.14 Contractor Launch System Familiarization

Course ATP End PoP 3 Per Year 24 hours In‐Person USG Site Lead Participate

3.1.15.1 NSSL Program Protection Surveys ATP End PoP Annual 4 hours In‐Person Contractor Site Support Lead

3.1.15.2 NSSL System Security Working Group ATP End PoP Quarterly 2 hours In‐Person USG Site Support Lead

3.1.15.2 Security‐Related Meeting ATP End PoP Monthly 1 hour In‐Person Launch Sites Support Lead

3.1.17.1 Anti‐Terrorism Meeting ATP End PoP

Annual per launch site 1 hour In‐Person Launch Sites Support Lead

3.2.1 Technical Interchange Meetings ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Launch System Risk Management Boards ATP End PoP

As Needed‐

Ongoing

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Engineering Review Boards (ERB) ATP End PoP

As Needed‐

Ongoing

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Anomaly Review Boards (ARB) ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Technical Review Boards ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Corrective Action Boards ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Change Control Boards ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Material Review Boards ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Failure Review Boards ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Parts Materials and Processes Control

Boards ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 System Verification Review ATP End PoP

As Needed‐Per

Mission

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Production Readiness Review ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Test Readiness Review ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Shipping Readiness Review ATP End PoP

Contractor‐

Dependent

Contractor‐

Dependent Teleconference Virtual Invite Participate

3.2.3 Pre‐Launch Reviews ATP End PoP

As Needed‐Per

Mission

Contractor‐

Dependent Teleconference Virtual Invite Participate

ResponsibilityForumTime ActivityParagraph

Nom. Start Nom. End Nom. Freq. Nom. Length Format Location Contractor

ResponForumTime ActivityParagraph

This Page Intentionally Left Blank

1 NATIONAL SECURITY SPACE LAUNCH SERVICES

1.1 DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES

This Performance Work Statement (PWS) defines the launch services (LS), mission integration (MI), mission-unique (MU), and level of effort (LOE) work the Contractor will perform for National Security Space (NSS) missions. This PWS also defines Launch Service Support (LSS) work that will be performed annually, and fleet surveillance (FS) work that the Contractor will perform for each non-NSS mission. The PWS includes the Program Management, Systems Engineering, Launch Vehicle (LV) Production, Mission Integration, Mission Operations, and Support to Government Space Flight Worthiness (SFW), LOE Activities, and Mission-Unique Options necessary to deliver healthy Payloads (PL) into their intended orbits managed by Air Force Space Command, Space and Missile Systems Center (AFSPC/SMC).

A National Security Space Launch (NSSL) service includes all tasks necessary to deliver National Security Space (NSS) payloads to defined orbital parameters in compliance with mission requirements as described in Section 3 (Space Launch Service). LS requirements apply to discrete activities for each individual NSS mission, and will be executed in accordance with (IAW) Contract Line Item Number (CLIN) 0001. LSS requirements apply to non-discrete, NSS-driven activities, and will be executed IAW CLIN 0005. Mission Integration (MI) requirements (subsection 3.4) and Mission-Unique (MU) requirements (subsection 3.8) will be executed IAW CLIN 0002 for procurement funded items, or CLIN 0010 for research and development funded items. Early Integration Studies (EIS) for non-NRO missions will be executed IAW CLIN 0003.

LOE requirements (subsection 3.7) will be executed IAW CLIN 0004. FS requirements (for non- NSS launches) will be executed IAW CLIN 0007.

Mission Integration tasks, Mission Unique Services, and additional unique requirements (e.g., enhanced security) for National Reconnaissance Office (NRO) missions will be executed via a separate companion contract managed by the NRO Office of Space Launch (OSL). The NRO will also conduct Leading Edge Integration (LEI) studies on an NRO companion contract.

During post-award contract execution, the Contractor may request, in writing, United States Government (USG) approval to allow relevant activities, documentation, and information developed under other contracts/agreements with the USG, to be used to satisfy the requirements of this PWS. Acceptance on previous activities does not guarantee acceptance on this contract.

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

An Acronyms and Abbreviations list is provided in Appendix B.

1.2 DEFINITION OF ROLES AND RESPONSIBILITIES

1.2.1 Roles

1.2.1.1 Launch Service Provider (LSP)

The term “Launch Service Provider (LSP),” used interchangeably with “The Contractor,” refers to the party responsible for supplying the Launch Service and LSS detailed in this PWS.

1.2.1.2 Government

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

1.2.1.3 United States Government Team

The term “USG Team” refers to the Air Force Space and Missile Systems Center/Launch Enterprise Systems Directorate (SMC/LE) program office and Air Force Program Executive Officer office personnel, but also includes the Aerospace Federally Funded Research and

Development Center (FFRDC), SMC/LE Systems Engineering and Integration (SE&I) contractors, SMC/LE Systems Engineering and Technical Assistance (SETA) support contractors, SMC/LE Advisory & Assistance Service contractors, the NRO/Office of Space Launch (OSL), NRO/OSL SE&I contractors, NRO/OSL SETA support contractors, NRO/OSL Mission Assurance Team (MAT) NRO/OSL Independent Verification and Validation (IV&V) support contractors, the SMC Independent Readiness Review Team, Defense Security Service, Defense Information Systems Agency, Defense Contract Management Agency, Defense Contract Audit Agency, 30th Space Wing (30 SW), 45th Space Wing (45 SW), and other organizations as designated by SMC/LE Procuring Contracting Officer (PCO). Refer to the Model Contract Clause 52.212-04 for Government Program Contracts Requiring Interface with Aerospace Federally Funded Research and Development Center (FFRDC, Prime, and Support contractors).

Estimates of the number of USG Team individuals associated with specific requirements in this PWS are listed in Appendix E (United States Government Team Call-Outs).

Government Hardware Review Team

The Government Hardware Review Team is the team comprised of USAF, civilian, SE&I, and Aerospace FFRDC personnel directly involved with supporting and performing independent hardware reviews. The OSL/MAT will also participate in these reviews.

Launch Mission System Integrator (LMSI)

The Launch Mission System Integrator is the contractor with responsibility, authority, and accountability for delivering an NSSL Integrated Multi-manifest Carrier (IMMC) end-item (including Multi-manifest Space Vehicles [MSVs]) to the LSP.

Government Mission Integration Manager (GMIM)

For USAF missions, the Government Mission Integration Manager (GMIM) is the lead interface between LV and PL (IPS/APS) programs orchestrating launch services, including operations planning, flight certification, and mission rehearsals. The GMIM also manages technical and funding changes between the PL (IPS/APS) and the LV, and coordinates LV/PL (IPS/APS) interface requirements. For NRO missions, the GMIM is the lead interface between SMC/LE and

OSL.

Government Mission Director (GMD)

The Government Mission Director (GMD) is the Senior Air Force (for USAF missions) or NRO/OSL (for NRO missions) official who is assigned responsibility for successfully delivering the integrated LV/PL to the proper orbit(s). The GMD must be involved in issue resolution for both the LV and the PL through the launch service.

Rehearsal Anomaly Team (RAT)

The Rehearsal Anomaly Team (RAT), consisting of representatives from each agency participating in the launch, is responsible for planning rehearsals. The RAT generates launch countdown scenarios, including anomalies that will exercise their teams for Day of Launch (DoL) preparation.

Space Wing

The term Space Wing (SW) includes subordinate units that provide generation and launch execution of space launch systems. 30th SW provides generation and launch execution of space launch systems for Vandenberg Air Force Base (VAFB) missions. 45th SW provides generation and launch execution of space launch systems for Cape Canaveral Air Force Station (CCAFS) and KSC (Kennedy Space Center) missions.

Government Launch Operations Team

The Government Launch Operations Team is the mission team comprised of USAF, OSL, SE&I, and FFRDC personnel directly involved with planning and execution of Government launch operations for a specific mission. This includes personnel at SMC and the respective SW at the launch site.

1.2.1.4 Space Vehicle Team (SV Team)

The term “SV Team” refers to the SV Directorate(s)/Program Office(s) (SPO), Space Vehicle Contractor(s) (SVC), and Launch Services Integration Contractor (LSIC) personnel, but also includes the FFRDC supporting the Systems Program Office (SPO), SE&I and SETA Contractors supporting the SPO, the SV’s Payload Processing Facility (PPF) personnel, and the LMSI representing the Multi-manifest SVs.

1.2.1.5 Space Vehicle Contractor (SVC)

The Space Vehicle Contractor (SVC) is the contractor with responsibility for delivering an SV and necessary data documentation to the respective SPO for non-NRO missions.

1.2.1.6 Launch Services Integration Contractor (LSIC)

The LSIC is the contractor with responsibility for assisting in the integration of the SV to the LV for NRO missions. The LSIC is responsible for defining spacecraft mission requirements, launch base and range support requirements, interface requirements, development and maintenance of integration schedules and plans, and coordination of integration activities with the Launch Vehicle Integration Contractor (LVIC).

1.2.2 Responsibilities

1.2.2.1 Notify

Notification is a Contractor responsibility to officially inform the USG Team about an action, activity, or decision process. The Contractor is not required to deliver data, generate action items to be tracked and closed outside of the relevant event, or attain USG approval, unless otherwise specified in the relevant PWS paragraph. Notification is considered complete when the USG Team acknowledges receipt.

1.2.2.2 Invite

Invitation is a Contractor responsibility to allow USG Team to observe meeting/event. When the Contractor is required to “invite” the USG Team to observe a meeting/event, USG approval of that meeting/event (or data generated therein, unless otherwise required by the contract) is not required. The Contractor is required to answer the USG's clarification questions. The Contractor is not required to generate action items to be tracked and closed outside of the relevant meeting/event. When the Contractor is required to “invite,” the relevant meeting/event can be completed without Government attendance.

1.2.2.3 Support

Support is a Contractor responsibility to actively cooperate with the USG Team in a USG-led meeting/event. When the Contractor is required to “support” a meeting/event, the Contractor may be required to provide data or a recommendation. The Contractor may also be required to generate action items to be closed outside of the relevant meeting/event, and to track the status of those action items throughout the Period of Performance (PoP). For questions on the data products required for a given meeting/event, consult the relevant PWS paragraph.

1.2.2.4 Lead

Leading is a Contractor or Government responsibility consisting of scheduling a meeting/event, facilitating appropriate participation in the meeting/event, and ensuring meeting/event objectives are met. When the Contractor is required to “lead” a meeting/event, the Contractor is required to provide a standard set of data products, unless otherwise indicated in the relevant PWS paragraph.

This standard set of data products includes a meeting agenda, presentation materials, and meeting minutes. The Contractor may also be required to generate action items to be closed outside of the relevant meeting/event, and to track the status of those action items throughout the PoP. For questions on the data products required for a given meeting/event, consult the relevant PWS paragraph.

1.2.2.5 Participate

Participation is a USG Team activity comprised of actively cooperating with the Contractor in a Contractor-led meeting/event. The USG Team may provide data or a recommendation for the Contractor to consider, but USG approval of the meeting/event (or data generated therein, unless otherwise required by the contract) is not required. The Contractor may be required to generate action items to be tracked and closed outside of the relevant meeting/event, so long as those action items are directly related to the fulfillment of a paragraph or multiple paragraphs in this

PWS.

1.2.2.6 Provide

Provide is a Contractor responsibility to make something or someone available for use by the USG Team, through physical or virtual delivery of that which is being provided. The responsibility to provide is accomplished when the Contracting Officer’s Representative (COR) acknowledges receipt, or the PCO approves, the relevant Contract Data Requirements List

(CDRL).

2 APPLICABLE DOCUMENTS

2.1 COMPLIANCE DOCUMENTS

The Contractor shall comply with the applicable documents listed in Appendix C unless tailoring is approved per the instructions listed in CDRL A019.

2.2 REFERENCE DOCUMENTS

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

2.3 DOCUMENTATION DE-CONFLICTION

For each mission, if a conflict exists between the signed mission Interface Control Document (ICD), the Mission Requirements Annex (MRA), the Interface Requirements Document (IRD), and the Standard Interface Specification (SIS), the mission ICD shall be given precedence. Other documents shall be given precedence IAW Federal Acquisition Regulation (FAR) 52.212-04(s).

3 SPACE LAUNCH SERVICE

The Government requires services to meet NSS launch needs. Space Launch Services for NSS missions include LV production and transportation, mission integration, launch operations, support to independent Government mission assurance, base and range support, mission commodities, all associated program management and systems engineering functions and tasks, and special studies.

The Contractor shall provide Space Launch Services for NSS missions IAW the performance requirements stated in the System Performance Requirements Document (SPRD), Standard Interface Specification (SIS), MRA, and relevant mission ICD(s). The Contractor shall control, document, and provide the USG Team continuous access and insight into its processes, assessments of progress and performance of all Space Launch Service requirements as defined in CDRL requirements, provide continuous access to the Contractor’s command media, and support the USG’s Independent Mission Assurance activities, as defined in the paragraphs below and the associated CDRLs.

3.1 PROGRAM MANAGEMENT FUNCTIONS AND TASKS

LSS/LS: The Contractor shall identify a Program Manager (PM) and perform all program management functions and tasks necessary to deliver launch services and to satisfy the requirements for the mission consistent with operational quality, safety, security, and environmental standards. The program management function of this contract shall provide insight to the Government for all technical and programmatic activities performed under this contract.

3.1.1 LSS: Risk Management

The Contractor shall establish and maintain a risk management process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

3.1.2 LSS: Manufacturing Management

The Contractor shall establish and maintain a manufacturing management process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

3.1.3 LSS: Reliability Program

The Contractor shall establish and maintain a reliability program that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

3.1.4 LSS: Launch System Data

3.1.4.1 LSS: Launch System Integrated Data Environment

The Contractor shall implement and maintain continuous USG access to an Integrated Data Environment (IDE) comprised of all Launch System Data used in support of this contract. The Contractor shall enable USG enterprise-level (large-scale) ability to perform bulk and incremental download and synchronization of Launch System Data. The Contractor shall enable the USG Team to access and download both raw and processed (e.g., pdf, csv) Launch System Data. The USG may incorporate this data into a USG Digital Engineering Environment (DEE), in support of the principles outlined in the DoD Digital Engineering Strategy. The USG has rights IAW the contract to all technical data accessed via the IDE, to include technical data that is archived by the USG Team. The Contractor shall notify the USG Team of any updates to delivered Launch System Data products as soon as possible, but no later than 1 CD after the update. The Contractor shall provide the USG Team with access to the Contractor’s Launch System Data collaboration platforms, including collaboration spaces, and ticketing systems, to exchange data and to review launch system data. The Contractor shall enable the USG Team and SV Teams to remotely access the Launch System Data via the Contractor’s electronic data repository host systems for the purpose of reviewing, uploading, and downloading data on Contractor host systems. The Contractor shall be responsible for providing access to the data, administering user IDE accounts, marking the data, and ensuring the integrity of the data. The Contractor shall provide server/folder location of data and confirm appropriate permissions have been provided. The Contractor shall notify the Government at least 24 hours in advance of all planned network outages and system upgrades that could interrupt access to the systems, or as soon as possible in the case of unplanned interruptions.

3.1.4.2 LSS: Software Product Specification

The Contractor shall provide the computer software and licenses needed to instantiate USG Team access to the IDE. For all Contractor modifications to commercial computer software (e.g., Microsoft SharePoint) used to create the IDE, the Contractor shall provide the source code needed for the USG Team to instantiate the IDE on USG systems. (CDRL A002)

3.1.4.3 LSS: Software Version Description

The Contractor shall identify all versions of commercial computer software used to create the IDE, and Contractor modifications made to those software applications that are needed for the USG Team to instantiate the IDE on USG systems. (CDRL A002)

3.1.4.4 LSS: Database Design Description

The Contractor shall provide a Database Design Description to describe the design of the database that comprises the IDE. The Contractor shall provide description of the IDE instantiation, to include the file folder structure/hierarchy, levels of access rights and privileges specified at the user level (e.g., administrator, guest, super-user) and at the data/deliverable level (e.g., ability to allow access to specific data/deliverables to selected users only based upon the classification level and level of license rights associated with that data) into which the data will be deposited, and search functions. (CDRL A002)

3.1.4.5 LSS: Data Accession List

The Contractor shall maintain a list of all data supporting this contract on a Data Accession List

(DAL). (CDRL A001)

3.1.5 LSS: Launch System IDE Training

The Contractor shall provide the USG Team on demand, computer-based training for the Launch System IDE used in support of this contract. USG team users will receive IDE access only after completing the necessary security and data access training. Such training shall include the following subjects: Work Authorizing Documents (WAD) access and feedback, anomaly/non-conformance system, launch console data system, specification and engineering file management system, In the event of changes to the Software Product Specification, Software Version Description, Database Design Description, or user interfaces to the IDE, the Contractor shall update the computer-based IDE training. (IDE)

3.1.6 LSS: Program Management Data Reporting

Note: The Contractor may provide the data items listed in this paragraph outside the IDE.

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

A. Cost Data Summary Report (CDRL A003) B. Functional Cost-Hour Report (CDRL A004) C. Contractor Business Data Report (CDRL A005) D. Contractor Work Breakdown Structure (CDRL A006) E. Small Business Utilization Report (CDRL A007) F. Integrated Program Management Report – Integrated Master Schedule (IMS) (CDRL

A008)

3.1.7 LSS: Program Management Reviews

The Contractor shall lead monthly Program Management Reviews (PMRs) to report development and production status, report CDRL status, ensure schedules support program objectives, review action items, review program data reports, and discuss all issues. The intent of the PMR is to provide a forum for open dialog between the USG Team and the Contractor. The Contractor shall provide the USG Team the PMR briefing slides NLT 5 calendar days (CDs) prior to the review or as agreed to by the COR. The Contractor and the COR will agree to the PMR agenda NLT 14 CDs prior to the PMR, or as agreed to by the COR. The PMR agenda shall include a status of the following topics at a minimum: Programmatic, Business Operations, Flight Manifest Status, Production Operations, Quality Metrics, Configuration Management, Risk Management, Program Protection/Cybersecurity Status, Subsystem(s) Status, Mission Integration Status, Non- Recurring Work Status, Launch Operations, Major Subcontractor(s) Performance, IV&V status, working group status, special topics and Wrap Up/Action Items. PMRs will be planned for 2 hours but last no more than 1 business day. Locations may rotate between Contractor and Government facilities. The Contractor shall invite the USG Team to major subcontractor PMRs or equivalent reviews. (IDE)

3.1.8 Mission Integration Management Plan (MIMP)

3.1.8.1 LSS: The Contractor shall provide a Mission Integration Management Plan (MIMP), which defines the Contractor’s standard process flow for first time and previously flown PL integration with the LV. The MIMP shall include the organizational roles and responsibilities, management approach, documentation products, integration meetings, working groups, reviews, and controls required to implement the integration process for the mission. (CDRL A010)

3.1.9 LS/LSS: Launch Manifesting Process

3.1.9.1 LSS: The Contractor shall support the Government-led launch scheduling and manifesting process to include the following reviews and meetings: a semi-annual Current Launch Schedule Review Board, a semi-annual Government Integrated Meeting, a monthly Senior Management Review, weekly launch manifest status teleconferences. The Contractor shall also lead a monthly manifest review. (Ref. Air Force Space Command Instruction [AFSPCI] 13-613)

3.1.9.2 LSS: The Contractor shall develop and provide the Applicable USG Team member(s) Launch Schedule Option Assessments as part of the launch manifesting process. (IDE)

3.1.9.3 LS: The Contractor shall provide the Applicable USG Team member(s) a Launch Slot Recommendation and Launch Date Recommendation within the assigned launch period for each launch mission. (CDRL A022)

3.1.10 LSS: System Safety Program

3.1.10.1 LSS: Per SPRD360, the Contractor shall provide a System Safety Program Plan and Safety Assessment Report IAW MIL-STD-882E (T), per the instructions listed in CDRL A019.

(CDRLs A012, A029)

3.1.10.2 LSS: The Contractor shall support the quarterly NSSL System Safety Working Group (SSWG) and annual System Safety Group (SSG) meetings IAW the SMC-G-012 Space and Missile Systems Center System Safety Program Guide

3.1.11 LSS: Range Safety

The Contractor shall coordinate requests for relief from the tailored Air Force Space Command Manual (AFSPCMAN) 91-710 for all missions under this contract with SMC/LE and NRO/OSL, and Range Safety in parallel with formal submittal. The final approval determination will be made by Range Safety. (CDRL A019)

3.1.11.1 LSS: Per SPRD400, the Contractor shall coordinate RCC 324-11 tailoring requests, equivalent level of safety certifications, and non-compliance waiver relief requests for all missions under this contract with SMC/LE in parallel with formal submittal to Range Safety, and per the instructions in CDRL A019. The final approval determination will be made by Range Safety.

(CDRL A019)

3.1.11.2 LSS: Per SPRD410, the Contractor shall coordinate RCC 319-10 (T) tailoring requests, equivalent level of safety certifications, and non-compliance waiver relief requests for all missions under this contract with SMC/LE in parallel with formal submittal to Range Safety, and per the instructions in CDRL A019. The final approval determination will be made by Range Safety. (CDRL A019)

3.1.12 LSS: Autonomous Flight Safety System (AFSS)

Per SPRD420, the Contractor shall equip its launch system with an AFSS. Per AFSPC AFSS Implementation memo, dated 13 November 2019, AFSS implementation is required by 1 October 2025.

3.1.13 LS/LSS: Safety Training

3.1.13.1 LS: The Contractor shall provide all Contractor-required safety training to applicable USG Team member(s) and SV Team personnel for Contractor facilities and flight hardware used in performance of individual launch service task orders on this contract to ensure Applicable USG Team member(s) access to those facilities and flight hardware. (Ref. paragraph 3.6.2.5)

3.1.13.2 LSS: The Contractor shall provide applicable USG Team member(s) all training required to enter Contractor facilities or the LV at all stages of production for LVs used in performance of fleet processing (including launch sites) and non-discrete, NSS-driven activities on this contract to ensure applicable USG Team member(s) access to those facilities and flight hardware (Ref.

paragraph 3.6.2.5). The USG Team will follow all guidelines and rules for access to Contractor facilities. Failure to do so may result in lost access.

3.1.14 LSS: Launch System Familiarization Course

The Contractor shall provide the USG Team an instructor-led Launch System Familiarization (FAM) Course three times per calendar year to provide training to the Government team supporting NSS missions with the LSP, at locations to be determined and provided by SMC/LE.

The FAM Course shall be conducted in two parts: a 1-day overview for non-technical personnel and a 2-day in-depth engineering system familiarization. The Course shall cover all training material, and the Contractor shall provide a self-study guide to accompany the training course consisting of the training materials, test questions, and answers. (CDRL A018)

3.1.15 LSS: Program Protection

The Contractor shall develop, provide, implement, and maintain a Program Protection Implementation Plan IAW the Program Protection Plan (PPP). (CDRL A011)

3.1.15.1 LSS: The Contractor shall support the applicable USG Team member(s) in annual NSSL Program Protection Surveys at all Contractor facilities IAW the PPP.

3.1.15.2 LSS: The Contractor shall support the quarterly NSSL System Security Working Group and one security-related meeting per month IAW the PPP (e.g., Information Technology [IT] Security Breach or Unauthorized Information Distribution resolutions).

3.1.15.3 LSS: The Contractor shall provide support to the Applicable USG Team member(s) in the development of the PPP Contractor-specific Annex. The Contractor shall provide the LV-specific and support ground system architecture specific information necessary to document, identify, assess, and mitigate security related vulnerabilities and risks.

3.1.16 LSS: Operations Security

3.1.16.1 The Contractor shall develop, implement, and maintain an Operations Security (OPSEC) program IAW contract Attachment 2, DoD Contract Security Classification Specification (DD254). (Ref. Air Force Instruction [AFI] 10-701 and the EELV OPSEC Plan). Contractor personnel will require TS/SCI level clearance to conduct work on some systems, as determined by the relevant COR. The Contractor shall be able to receive, store and generate Special Access Program (SAP) documentation in an approved Special Access Program Facility (SAPF) to conduct the Launch Mission Integration function with the spacecraft payload.

3.1.17 LSS: Anti-Terrorism

The Contractor shall implement and maintain an Anti-Terrorism Program for activities at CCAFS, KSC, and VAFB as appropriate. The Contractor shall ensure SMC/LE and NRO/OSL approval prior to taking action regarding anti-terrorism requirements requested by the 30th SW Operations Security Office or 45th SW/Anti-Terrorism Office that change or add additional anti-terrorism requirements to this PWS paragraph and subparagraphs. (CDRL A015)

3.1.17.1 LSS: Meeting Support: The Contractor shall provide site security leads and support one meeting per year, per launch site.

3.1.17.2 LSS: Program Reviews: The Contractor shall perform an in-house Annual Review of its Anti- Terrorism program, which shall be documented IAW the host Wing Anti-Terrorism Office checklist. (CDRL A015)

3.1.17.3 LSS: Training: The Contractor shall ensure all applicable Contractor personnel perform annual training utilizing the host SW’s Anti-Terrorism training materials as a guideline. The Contractor shall create a Corporate Annual Training Letter stating that all site personnel have completed their individual Anti-Terrorism training.

3.1.17.4 LSS: Force Protection Condition (FPCON) Checklists: The Contractor shall utilize site-specific FPCON checklists provided by the COR at each launch site.

3.1.17.5 LSS: Random Anti-Terrorism Measures (RAMs): The Contractor shall perform prescribed RAMs or alternate RAMs that are preapproved by host Space Wing (up to five per month).

Completed RAMs shall be documented in a format prescribed by SMC/LE and reported quarterly to the Host Wing Anti-Terrorism Office. (CDRL A015)

3.1.17.6 LSS: Mission Essential Personnel: The Contractor shall create and maintain a “Mission Essential Personnel” list and an “Emergency Essential Personnel” list for higher FPCON levels (Charlie and Delta) and other emergency situations at each launch site. The Contractor shall provide continuous access to updated versions of these lists to the appropriate launch site personnel. (IDE)

3.1.18 LSS: Cyber Security

The Contractor shall provide evidence of compliance with International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 27001 and National Institute of Standards and Technology (NIST) 800-171 derived from activities performed to establish and maintain compliance upon Government request. This shall include initial and annual audit reports, Contractor-developed compliance documentation, such as plans, procedures, and reports, plan of action and milestones (POA&Ms), and requests for waivers. The Contractor shall notify the Government of cyber security audits and coordinate schedules to ensure Government participation. (CDRL A011)

3.1.19 LSS: Physical Security

Contractor shall permit physical access to NSSL restricted areas to the host Wing DoD security forces to maintain compliance with AFI 31-101, Integrated Defense, and the Air Force Space Command supplement to AFI 31-101 operations and physical security requirements. Contractor-developed structures within NSSL Restricted Areas shall comply the PPP and PPIP physical security requirements and not degrade AFI 31-101 physical security requirements. Contractor facilities outside of NSSL restricted areas housing NSSL Critical Program Information (CPI) and critical components (CC) shall comply with physical security requirements identified in the Program Protection Plan, and use Contractor-specific Program Protection Implementation Plan (PPIP) derived protection and countermeasures. (CDRL A011)

3.1.20 LSS: Environmental Requirements (NSS)

3.1.20.1 LSS: The Contractor shall provide to the applicable USG Team member(s) each environmental impact analysis document, environmental report, and applicable meeting notices related to or that impact the launch system. This includes associated correspondence sent to or received from environmental regulatory agencies and the host Wing but does not include informal telephone and e-mail communication. (IDE)

3.1.20.2 LSS: The Contractor shall include SMC/LE in the coordination process with the host Wing and the environmental regulatory agencies relating to the application, development, or modification of permits or required environmental compliance plans, environmental cleanup actions, or other major efforts subject to environmental laws and regulations. During the coordination process, the Contractor shall provide information to the on-site USG Team environmental representatives to ensure that the applicable USG Team member(s) are aware of the risks and alternatives that are evaluated or accepted. (IDE)

3.1.20.3 LSS: The Contractor shall provide data needed to allow SMC/LE to monitor, in coordination with the SWs, the Environmental Impact Analysis Process IAW National Environmental Policy Act and Executive Order 12114, Environmental Effects Abroad of Major Federal Actions, dated 4 January 1979. (CDRL A016)

3.1.20.4 LSS: The contracted shall be prepared to submit the listed items on the VAFB Description of Proposed Action and Alternatives (DOPAA) checklist in preparation for the requirements needed to complete AF Form 813 submittal for launch services and work at the 30th SW.

DOPPA is a checklist for reference only and should be used as a guide for EIA preparations.

This document is included in APP. C and in the Bidders Library.

3.1.21 LSS: Hazardous Materials

The Contractor shall provide a hazardous materials management plan IAW AFSPCMAN 91-710 and Task 108 of MIL-STD 882-E (Ref: NAS 411 Hazardous Materials Management Program for guidance). (CDRL A013)

3.1.22 LSS: Incident and Discrepancy Reporting

The Contractor shall maintain an incident and discrepancy reporting system. The Contractor shall notify the applicable USG Team member(s) of all incidents and discrepancies. (IDE)

3.1.22.1 LSS: The Contractor shall notify the applicable USG Team member(s) of incidents and discrepancies during the execution of this contract that involve (1) loss of life or severe personal injury as defined per Occupational Safety and Health Administration reporting requirements;

(2) damage to flight hardware or launch infrastructure critical ground systems; or (3) damage to launch infrastructure critical ground systems occurring during vehicle build, test, transportation, processing, or facility readiness operations. The notification shall be provided as soon as operationally possible, but NLT 48 hours (post-emergency response and safety hazard securing) and IAW already-established Contractor reporting procedures. The Contractor shall provide the status of ongoing investigations, Contractor incident root cause data, and determination and associated corrective actions. (IDE)

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

3.1.22.3 LSS: The Contractor shall report within 48 hours of an event’s occurrence all incidents and all discrepancies that may be or are a major non-conformance or that may lead to one or more of the following: (a) delay to the ship date of flight hardware for NSS missions, (b) out-of-position (OOP) work transferred to the launch site, (c) changes to the IMS (including applicable Mission Integration Schedules), (d) waivers or exceptions to test or verification requirements, or (e) impact a scheduled launch date. The Contractor shall provide the status of ongoing investigations, Contractor incident root cause data, and determination and associated corrective actions. For all other incidents and discrepancies, notification shall be NLT 14 CDs of an event’s occurrence and status reporting will be determined by SMC/LE on a case-by-case basis.

3.1.23 LS: Public Affairs Activities

3.1.23.1 LS: For AF missions, the Contractor shall support Public Affairs activities related to this contract by coordinating with SMC/LE and the Space and Missile Systems Center Public Affairs Office (SMC/PA). The Contractor shall notify SMC/PA and the COR NLT 1 hour prior to public release of press statements, press releases, and all related public affairs items related to missions executed under this contract.

3.1.23.2 LS: For NRO missions, the Contractor shall support Public Affairs activities by coordinating with the NRO Office of Public Affairs (OPA). The Contractor shall submit all press statements, press releases, broadcast material, videos, podcasts, photographs, social media plans/posts, or any related public affairs items to the NRO OPA for approval prior to release to the press or general public. The Contractor shall follow NRO OPA guidance regarding timing of public and media releases. The design for memorabilia (i.e., coins, patches, logos) must be approved by the Director, NRO. The Contractor shall submit proposed designs to NRO OPA and receive written prior approval prior to production of any material.

3.1.24 LS: Mission Milestone Reviews

The Contractor shall lead or support the Mission Milestone Reviews, as defined in Appendix F (Mission Milestone Reviews). The Contractor shall provide the applicable USG Team member(s) the briefing slides for each Mission Milestone Reviews NLT 5 CDs prior to the review or as agreed to by the parties. Support to USG Team readiness reviews includes attendance, presentation of requested information, and providing answers to questions posed during reviews or as follow-up questions related to material presented. For the milestone reviews, the Contractor shall attest to the review Chairman whether the Launch System is ready to proceed with continued processing, assess the margin to the planned schedule, and discuss issues and risks as appropriate. For the Government’s FRR and LRR, the Contractor shall attest to the review Chairman whether the Launch System is ready to proceed with launch.

3.2 SYSTEMS ENGINEERING FUNCTIONS AND TASKS

LSS/LS: In order to ensure the successful completion of the missions on this contract, the Contractor shall perform systems engineering functions and tasks necessary to provide launch services consistent with operational safety, suitability, and effectiveness (OSS&E) and Environmental Safety and Occupational Health guidance on NSSL systems. In order to ensure the Government can accomplish its mission assurance functions and tasks, the Contractor shall maintain and provide the applicable USG Team member(s) insight into the systems engineering processes supporting the launch service. In order to facilitate smooth and unimpeded communication between the USG Team and the Contractor, the Contractor shall identify a Product Line Chief Engineer (or equivalent) to work with the USG Product Line Chief Engineer to manage and control the activities in this subsection.

3.2.1 LSS: Technical Interchange Meetings

The Contractor shall invite the applicable USG Team member(s) to Technical Interchange Meetings (TIMs) or all Contractor-equivalent boards 48 hours in advance (or as soon as possible, if scheduled less than 48 hours in advance.) and make available all meeting documentation materials. (IDE)

3.2.2 LSS: Contractor Engineering Databases

The Contractor shall provide the applicable USG Team member(s) virtual access to the Contractor’s non-recurring, recurring, manufacturing, and engineering databases, to include, but not be limited to non-conformances, drawings, configuration control, risk, production, refurbishment, launch operations, risk management, change management, quality management, test database, design repositories, systems engineering models, requirements tracking, closeout photos, flight observations, anomalies, and other similar engineering databases that meet both of the following criteria: (1) are used by the Contractor to assess the launch system, and (2) are used to support USG space flight worthiness (SFW) process, crossover assessments, and in-plant technical surveillance by the USG Team. (IDE)

3.2.3 LSS: Systems Engineering Boards and Processes

The Contractor shall obtain COR approval of a plan to meet the intent of requirements in this paragraph and its subparagraphs. The plan shall include a comprehensive list of the Contractor’s equivalent systems engineering boards (with the nominal meeting date and time) and processes.

The Contractor shall invite the applicable USG Team member(s) to all Launch System: Risk Management Boards (RMB); Engineering Review Boards (ERB); Anomaly Review Boards (ARB); Technical Review Boards (TRB); Corrective Action Boards; Change Control Boards for technical issues; Material Review Boards (MRB); Failure Review Boards (FRB); Parts, Materials, and Processes Control Boards (PMPCB); System Verification Review; Production Readiness Review (PRR); Test Readiness Review; Shipping Readiness Reviews (SRR); Pre- Launch Reviews; or Contractor-equivalent boards or processes. (IDE)

3.2.3.1 LSS: The Contractor shall establish and maintain a life cycle systems engineering process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

3.2.3.2 LSS: The Contractor shall lead and facilitate applicable USG Team member(s) participation in Launch System Preliminary Design Review (PDR); Critical Design Review (CDR); Functional and Physical Configuration Audits (FCA/PCA), or Contractor-equivalent boards or processes.

The Contractor shall establish and maintain a process for technical reviews (TRs) and audits that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

3.2.3.3 LSS: The Contractor shall establish and maintain processes for design, analysis, test, and operations that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

3.2.3.4 LSS: For recurring review boards, the Contractor shall invite the applicable USG Team member(s) NLT 10 CDs in advance of the board (or shorter timeline, as approved by the COR).

For…