Attachment 1 - Performance Work Statement (PWS) - Rev3.pdf

OSP-4 PWS – Rev 3 Page 1 of 55

Attachment 1 Orbital Services Program-4 (OSP-4)

Performance-Based Work Statement (PWS)

OSP-4 PWS – Rev 3 Page 2 of 55

PWS REVISION RECORD

Revision Date Description Pages

Basic 29 July 2019 -- 50

Rev 1 31 August 2020 Corrected discrepancies between Annex 2 and CDRLs, updated section 3.0 - Service Summary to better evaluate performance

Rev 2 22 June 2021 Update on page 16 to section 2.1.2.9 Classified Payloads

Rev 3 4 August 2021 Updated Annex 1-2.61 to the original language in the basic PWS.

OSP-4 PWS – Rev 3 Page 3 of 55

Table of Contents

1.0 General Information

1.1 Scope and Objectives:

1.2 Program Overview:

1.3 Management and Communications:

1.4 Associate Contractor Agreements and Non‐Disclosure Agreements:

1.4.1 Associate Contractor Agreements (ACA):

1.4.2 Non‐Disclosure Agreements (NDAs):

1.5 Excess Ballistic Missile Motors:

1.6 Contractor Responsibility Watch List (CRWL):

2.0 Description of Services:

2.1 Design, Integration, & Launch Services (DILS) (CLIN 0001):

2.1.1 LS Formal Reviews:

2.1.2 Launch Campaign:

2.1.3 Integrated Product Team (IPT) Meetings:

2.1.4 Periodic and Technical Interchange Meetings (TIM):

2.1.5 Multi‐SV Missions:

2.2 Mission Assurance (MA) (CLIN 0003):

2.2.1 MA Formal Reviews:

2.2.2 Government Readiness Reviews (Cat 2&3 Missions Only):

2.3 Mission Analysis Study (MAS) (CLIN 0005):

2.4 Concept Analysis Study (CAS) (CLIN 0007):

2.5 GFP Closeout Service (CLIN 0009):

2.5.1 Annual Audit:

2.5.2 GFP Quarterly Report:

2.5.3 Returns:

2.6 Hardware Service (CLIN 0011):

3.0 Service Summary

3.1 Contract Surveillance:

4.0 Documents

4.1 Reference Documents:

4.2 Compliance Documents:

Annex 1: MA Category-Specific Mission Analysis Requirements

OSP-4 PWS – Rev 3 Page 4 of 55

A1‐1 Category 1 Analyses

A1‐2 Category 2 Analyses

A1‐3 Category 3 Analyses

Annex 2: Performance Threshold Entrance and Exit Criteria Annex 3: Definitions

OSP-4 PWS – Rev 3 Page 5 of 55

1.0 General Information

1.1 Scope and Objectives: The Rocket Systems Launch Program (RSLP) delivers innovative, resilient, and affordable launch solutions for the Department of Defense (DoD), the Intelligence Community (IC) and the United States (U.S.) Government, complementing the National Security Space Launch (NSSL), formerly the Evolved Expendable Launch Vehicle (EELV) program, to provide assured access to space and full-spectrum launch capabilities for the warfighter. The U.S. Air Force Space and Missile Systems Center (SMC) Launch Enterprise, Small Launch & Targets Division manages the RSLP. The RSLP provides launch services, mission integration, and support for both operational and research and development (R&D) requirements and to date has flown over 700 missions, using 24 booster types, from 20 different launch sites.

The RSLP employs four primary contract mechanisms to accomplish the full range of payload (PL) delivery services: (1) General Services Administration (GSA) schedules are used to procure rideshare services; (2) The Sounding Rocket Program 4 (SRP-4) is used to procure suborbital launch services; (3) Small Rocket Program – Orbital (SRP-O) contracts are used to procure very small orbital (<400 lb to Low Earth Orbit (LEO)) launch services; and (4) The Orbital Service Program-4 (OSP-4) is used to procure dedicated and primary orbital launch services greater than 400 lb to LEO.

The objective of the OSP-4 program is to provide flexible small launch capability using Spacelift System (SS) designs based on commercial and/or Government Furnished Property (GFP) motors to meet a variety of mission and Space Vehicle (SV) requirements in 12-24 months. Required services also include special studies. OSP-4 delivers PLs ranging between 400 pounds (lb) to LEO through approx. 8,000 lb to Geostationary Transfer Orbit (GTO). Additional orbits of interest within this performance range include, but are not limited to, Medium Earth Orbit (MEO) and Highly Elliptical Orbits (HEO). The program supports both dedicated and primary launch services. In addition, for some missions the launch solution may consist of multiple SSs to support mission requirements.

This Performance Work Statement (PWS) delineates the launch service responsibilities of the Launch Service Contractor (LSC) in support of the OSP-4 contract. The requiring activity is the SMC/Launch Enterprise. Contractual direction is provided by the Procuring Contracting Officer (PCO), SMC/PKT, at Kirtland Air Force Base, New Mexico.

1.2 Program Overview: SMC requires complete launch services where the culmination of work results in the LSC’s Launch Solution (LS) meeting mission requirements and demonstrating compliance, through analysis, with this PWS, the Mission Requirements Document’s (MRD), and the RSLP Small Launch Performance Requirements Document (SLPRD) and Small Launch Interface Specification (SLIS). The MRD defines specific mission objectives for each mission. The system and interface requirements are defined in the RSLP SLPRD and SLIS respectively. The order of precedence is MRD, PWS, and

SLPRD/SLIS.

The scope of the procured LS consists of completion of design activities and developmental efforts for any Spacelift System (SS), and/or subsystem designs not previously qualified to mission levels; fabrication, test, and integration of the systems, OSP-4 PWS – Rev 3 Page 6 of 55 required SS support equipment, integration of the SS with the SV(s), provision of launch facilities, operations, training, logistics, or information supporting Government oversight and insight required for Independent Verification and Validation (IV&V). These activities also include customization of the proposed system, subsystems, or components to meet mission requirements such as guidance and control systems, SS instrumentation systems, trajectory software, SV(s) integration, launch site, facilities, storage and other associated activities.

OSP-4 missions will normally be procured as a dedicated launch service. A dedicated launch service is one in which the Government reserves all capacity of the launch solution.

For some OSP-4 missions (specified in the MRD), the LSC may provide a primary launch service, where the OSP-4 launch service directs the launch date and orbit, with Other Government Agency (OGA) Rideshare SV(s) and/or Commercial Rideshare SV(s) allowed to utilize excess capacity. The launch service shall provide multi-SV services as part of the launch service when multiple SVs are manifested. For more information regarding the multi-SV mission element, refer to the SLIS and the Rideshare User’s Guide (RUG) or its successor document.

For both dedicated and primary launch services, the launch schedule shall be per the OSP-4 requirement.

1.3 Management and Communications: The Government will assign a Contracting Officer's Representative (COR); the COR will act as the primary interface with the LSC and provide contract surveillance (i.e. quality assurance) as described in Section 3 of this PWS, on behalf of the PCO. The COR will also assess the conformance with requirements of each service provided and make a final recommendation to the PCO for determination of the conformance of the service rendered in accordance with Federal Acquisition Regulation (FAR) 52.246-4(e).

The Government will also assign a Mission Manager (MM) for each task order responsible for leading an Integrated Product Team (IPT) to identify and manage the full breadth of mission planning and issues, including interfacing with the LSC to coordinate activities with stakeholders.

1.4 Associate Contractor Agreements and Non-Disclosure Agreements:

1.4.1 Associate Contractor Agreements (ACA): The LSC shall enter into ACAs for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement(s). These agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the conduct of the mission, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Associate contractors are listed in the MRD.

ACAs shall include the following general information:

Identify the associate contractors and their relationships

Identify the program involved and the relevant Government contracts of the associate contractors

OSP-4 PWS – Rev 3 Page 7 of 55

Describe the associate contractor interfaces by general subject matter

Specify the categories of information to be exchanged or support to be provided

Include the expiration date (or event) of the ACA

Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees

A copy of such agreement shall be provided to the PCO for review before execution of the document by the cooperating contractors.

The LSC is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government. All costs associated with the agreements are included in the negotiated prices of applicable orders issued under this contract. The Government will make necessary updates to the agreements when the associate contractor is succeeded by a new contractor.

1.4.2 Non-Disclosure Agreements (NDAs): The LSC shall establish NDAs with other contractors performing related services for the Government such as SV Contractors responsible for SV(s) operations and Mission Assurance Contractor (MAC) who may perform IV&V activities on behalf of the Government.

1.5 Excess Ballistic Missile Motors: The Government will offer excess ballistic missile motors, as well as related handling and test equipment for use, to be furnished as GFP for use at the LSC's discretion. Excess ballistic missile motors are provided in flight worthy condition while all other GFP is furnished as-is. If excess ballistic missile motors are used in the LSC’s solution, excess capacity is reserved for the Government.

Department of Defense (DoD) will not pursue or allow commercial rideshare opportunities on space launch vehicles derived from excess ICBM assets. The LSC shall manage and maintain GFP (if applicable) using documented LSC procedures when Government-provided procedures are unavailable.

For all other GFP items, the contractor shall be responsible for contacting the appropriate GFP owner and arranging for its use in performance of the contract.

1.6 Contractor Responsibility Watch List (CRWL): SMC Instruction (SMCI) 64-101, Air Force Space Contractor Responsibility Watch List (CRWL), applies to this contract. Accordingly, if at any time during the performance of this contract the contractor is placed on the CRWL, before executing a modification resulting from an engineering change proposal or exercising an option on this contract, the Contracting Officer must determine whether to recommend proceeding with the modification or option exercise and if so, obtain approval to proceed from the SMC Commander. To support the Contracting Officer’s determination on whether to proceed with the modification or option, the contractor must submit documentation describing how it has addressed the conditions that resulted in its inclusion on the CRWL and why those

OSP-4 PWS – Rev 3 Page 8 of 55 conditions will not impact performance on this contract. The Contracting Officer will consider this information as well as other available information in making a determination.

In addition, in accordance with either 52.212-4 (if commercial) or the SMC Class Deviation of FAR clause 52.244-2, Subcontracts (if non-commercial) in this contract, the contractor must receive written consent of the Contracting Officer prior to subcontracting with proposed subcontractors included on the CRWL when the subcontracts are valued in excess of $3M or 5% of the prime contract value, whichever is lesser. Before providing this consent the Contracting Officer must determine whether to recommend granting consent and if so, obtain approval to proceed from the SMC Commander. Prime contractors must inform their proposed subcontractors that they must notify the prime contractor if they have been notified by the SMC Commander that they have been included on the CRWL. The prime contractor must submit a written consent to subcontract request to the Contracting Officer, the prime contractor’s determination of subcontractor responsibility in accordance with FAR 9.104-4(a), and documentation describing how the proposed subcontractor has addressed the conditions that resulted in its inclusion on the CRWL and why those conditions will not impact its performance on a subcontract to this contract. The proposed subcontractor may submit information related to its CRWL inclusion through the prime contractor or directly to the Contracting Officer. The Contracting Officer will consider information provided by the prime contractor and the proposed subcontractor as well as other available information in making a determination. The contractor is encouraged to inform the Contracting Officer of any subcontractor concerns or issues that may jeopardize successful contract performance.

2.0 Description of Services: The following sections outline the launch service requirements.

The LSC shall employ a structured Systems Engineering (SE) approach throughout mission execution (e.g., hardware design, software development, configuration management, quality assurance, material review board, change control, requirements flow-down, processes and procedures) to ensure all requirements are met.

2.1 Design, Integration, & Launch Services (DILS) (CLIN 0001): The LSC shall complete all launch activities and support the LS Formal Reviews, Mission Assurance (MA) Formal Reviews, and Government Readiness Reviews depicted in Figure 1 below.

Mission reviews provide insight into the LSC’s structured SE approach and provides the Government an opportunity to conduct contract surveillance as described in Section 3.0

– Service Summary. The timing of formal reviews shall be agreed upon by the COR and the LSC. The COR may waive reviews deemed of low value; the COR may also combine reviews for the sake of efficiency.

OSP-4 PWS – Rev 3 Page 9 of 55

Figure 1 - OSP-4 Mission Reviews (Notional 24 Month Timeline)

For the formal reviews, the LSC shall leverage analyses and/or data previously presented to the Government. As detailed in Annex 2, the LSC shall submit criteria in two groups: (1) Entry Criteria; and (2) Exit Criteria.

(1) Entry Criteria: The entry criteria shall meet the entry criteria specified for the review as detailed in Annex 2. The Government Red Team of subject matter experts (SMEs) will perform a technical evaluation of the criteria submitted and determine whether the criteria demonstrates the LSC is prepared to conduct the formal review. The COR will communicate the determination of the Government no later than seven (7) calendar days prior to the review. In the event of a finding of non-readiness, the specific deficiencies will be communicated to the LSC;

these deficiencies, commonly referred to as “findings”, must be rectified before the LSC will be allowed to continue to the formal review unless otherwise stated in the notification. [CDRL A002 - Design Review Information Package (DRIP)]

(2) Exit Criteria: The COR will communicate any formal review deficiencies, commonly referred to as “liens,” to the LSC at the close of the review. Liens will be validated by the COR and considered by the PCO in the determination that the relevant service has been satisfactorily performed. [CDRL A002 - Design Review Information Package (DRIP)]

The LSC is responsible for collecting, logging, disseminating and assigning resources for responding to each lien, and other action items, identified at the review. The LSC will provide a get-well plan, which includes a burn-down plan and schedule to remedy deficiencies to the COR no later than seven (7) calendar days after the review. Closure dates will be agreed to by the COR and the LSC.

Mission Assurance

S R

R T

-2 m o

Design, Integration, & Launch

M D

R -1

T -1 m o

T R

R T

-1 m o

(C at

/3 o nl y)

ATP ILC

Q T

R T

-5 m o (C at

/3 o

P F

R T d (C at

/3 o

F R

R T

-1 4d

LR

T -2 d

P ed ig re e R ev ie w T

-8 1d

C at

/3 o

M

R

P

S R

T -6

0d eI

R T

-3 0d

M D

R -2

T -1 m o

OSP-4 PWS – Rev 3 Page 10 of 55

2.1.1 LS Formal Reviews: The LSC shall host the following LS formal reviews at their facility in order to provide the Government insight into the processes, methodology and progress being made by the LSC [CDRL A001 - Report, Record of Meeting Minutes]:

Service Requirements Review (SRR)

Mission Design Review 1 (MDR-1)

Mission Design Review 2 (MDR-2)

Pre-ship Readiness Review (PSR)

Post-Flight Review (PFR) (Cat 2&3 Missions Only)

2.1.1.1 Requirements Analysis and SRR: The LSC shall perform requirements analysis for the specific mission; including decomposition, allocation, tracing, and validation of all SLPRD, SLIS, and MRD requirements. At the conclusion of the requirements analysis, the LSC shall hold a SRR NLT 60 calendar days after award or as directed by the COR, in coordination with the LSC. [CDRL A002 -

DRIP]

2.1.1.1.1 Requirements Decomposition, Traceability & Validation:

Requirements shall be decomposed and traced in a hierarchical structure starting with the highest level requirements. These high-level requirements shall be decomposed into functional and performance requirements and allocated across the major elements of the proposed LS, with any new design elements or design changes to meet requirements identified accordingly. The launch service shall flow down and trace all numbered SLPRD, SLIS, and MRD requirements to launch service requirements and interface documents. These shall be further decomposed and allocated among lower level elements until a complete set of requirements is achieved. [CDRL A016 - System Performance Specification; A015 - Documentation/Specification Tree;

A018 - SS/Payload Interface Control Document (ICD)]

The launch service shall verify each numbered SLPRD, SLIS, and MRD requirement through a combination of demonstration, test, analysis, and inspection and provide verification evidence to SMC/Small Launch & Targets Division, with artifacts of verification cited. Both traceability and verification shall be documented in the Requirements Traceability and Verification Matrix (RTVM). The use of an automated requirements management system (e.g., DOORS or JAMA) is encouraged but not required. [CDRL A021 - RTVM]

2.1.1.2 Mission Planning: The LSC shall develop and maintain an Integrated Master Schedule (IMS) and IMS Dictionary for the mission. The IS and IS Dictionary shall use a common numbering system. The LSC shall develop a Program Management Plan (PMP) that references and is consistent with the IS. [CDRL A025 - Integrated Master Schedule; A031 Program Management Plan]

OSP-4 PWS – Rev 3 Page 11 of 55

2.1.1.2.1 The IS shall reflect all the LSC’s overall view of the effort and serve as the framework for organizing activities involving the LSC and their subcontractors, Government, Range and Associated Contractors. The LSC shall include all applicable PWS tasks. Tasks/activities shall be logically linked together and show predecessor/successor relationships and establish the logical flow of dates provided by calculating the duration of all tasks using typical schedule networking tools. The IS shall display the critical path as well as schedule margin and deviation.

The IS shall be maintained and updated no less than monthly. The IS shall be presented at formal reviews at a detailed level to display milestones and primary processes of interest. The IS shall reflect all planned mission activities, including external dependencies. [CDRL A025 – Integrated Master Schedule]

2.1.1.2.2 The IS Dictionary shall define the tasks to be performed in each IS task.

This task definition shall include a complete definition of the task to be accomplished, the key processes, procedures and specifications to be used when performing the task and the CDRL item(s) to be delivered.

[CDRL A025 – Integrated Master Schedule]

2.1.1.3 Mission Design: The LSC shall perform mission design for the specific mission. In this activity the LSC designs the complete mission LS. The LSC shall address reusability of the LS booster and potential consideration to the Government if reusability is a part of the LS.

2.1.1.3.1 Interface Control Documents (ICD): The LSC shall maintain configuration control and coordinate the ICD change process throughout the life of the mission. The ICD(s) shall be generated to document the interfaces between the SS and the SV(s), and the Launch Site/Range. If GFP motors are used, a separate ICD shall be created and maintained for the interface(s) between the GFP motor(s) and the LSC’s hardware. [CDRL A018 - SS/Payload ICD; SS-to-(GFP) Booster ICD]

Each ICD shall contain a RTVM that shall be maintained throughout the life of the ICD. The RTVM documents how requirements are derived and specifies artifacts required to demonstrate interface verification. [CDRL A021 – RTVM]

2.1.1.3.2 Mission Design Review (MDR-1): Prior to conducting a detailed LS design, the LSC shall have a preliminary design that meets (or is converging on meeting) the requirements generated in the requirements analysis. The LSC shall ensure the concepts and preliminary designs are adequate to meet mission requirements. The objective of the MDR- 1 is to demonstrate a preliminary design that satisfies the mission design concept, and presents preliminary designs of design items, interfaces, and design modifications that must be implemented to meet mission requirements.

OSP-4 PWS – Rev 3 Page 12 of 55

The LSC shall conduct the MDR-1 NLT 135 days after SRR or as directed by the COR, in coordination with the LSC. After a successful MDR-1 the LSC shall be prepared to execute the detailed design for its LS. [CDRL A002 – DRIP; A001 - Report, Record of Meeting Minutes]

2.1.1.3.3 Mission Design Review (MDR-2): At the conclusion of the mission design phase, the LSC shall hold MDR-2, NLT 135 days after MDR-1.

The objective of the MDR-2 is to demonstrate critical design that satisfies the full mission design concept, and presents complete designs of any design items that were previously only developed to the preliminary design level.

If mission design changes after MDR-2, then a delta review may be required, as directed by the COR, in coordination with the LSC.

[CDRL A002 - DRIP; A001, Report, Record of Meeting Minutes]

2.1.1.4 Mission Development: The LSC shall fabricate and test hardware and software to ensure the Government is provided a LS design capable of meeting all the requirements of the SLPRD, SLIS, MRD and this PWS.

2.1.1.4.1 Space Debris Assessment Report (SDAR): The LSC shall perform analysis and produce a SDAR to demonstrate compliance with AFI 91- 202, para. 13.11, for the SS (the SV will not be included in this report/analysis). [CDRL A004 - SDAR]

2.1.1.4.2 Predicted Environments: The LSC shall generate predicted launch environments based upon mission development activities. [CDRL A004 - Predicted Launch Environments Analysis Report]

2.1.1.4.3 Coupled Loads Analyses (CLA): CLA shall be performed by the LSC to predict the maximum loads that can be expected by the SV(s) during the launch event. The CLA shall address key loading events (e.g. lift-off, maximum dynamic pressure, transonic, staging/ignition events, engine cut-offs and restarts, and steady state conditions, as applicable).

The preliminary CLA shall be performed based upon preliminary SV(s)-provided models to support SV(s) design and test programs. A final CLA shall be performed with test verified models. [CDRL A004 - CLA Report]

2.1.1.4.4 Fabricate & Test: The LSC shall develop, fabricate and test flight hardware and flight software, necessary to conduct the mission. The LSC shall conduct hardware and software system level testing to meet qualification requirements. Flight hardware and software shall be fabricated and developed under configuration control. All work performed under this effort shall be performed in accordance with the LSC’s processes, procedures and SS specifications

2.1.1.4.5 Design Verification Tests: Design verification tests of items crossing the Payload Interface Plan shall be conducted to establish confidence in compatibility between the LSC hardware and any other contractor or

OSP-4 PWS – Rev 3 Page 13 of 55 stakeholder hardware, or to verify complex SS functions. The LSC shall prepare a test report summarizing the test set up, the results, and any anomalies. [CDRL A027 - Design Verification Test Procedure;

A012 - Design Verification Test Report].

2.1.1.4.5.1 Integrated Mechanical / Structural Analysis and Verification Tests: A series of mechanical/structural tests shall be conducted at the LSC facilities to verify the SS mechanical and structural characteristics. The LSC shall conduct the testing with agreed upon SV(s) participation. The LSC and SV Contractor(s) (SVC(s)) shall provide flight representative hardware to support conduct of the testing.

2.1.1.4.5.2 SS/SV(s) Mechanical Interface Verification: A mechanical fit check shall be performed to verify the mechanical compatibility between the SS and the SV(s) separation system as documented in the SS/PL ICD, including cable routing and connections and any areas where there are potential interference issues. The flight representative separation system will be provided by the SV contractor(s).

The LSC shall provide flight representative hardware to support the fit check. The fit check shall be performed at the LSC facility or the agreed upon alternate facility.

2.1.1.4.5.3 Non Destructive Testing (NDT): The LSC shall conduct NDT on all flight structures fabricated with composite materials. For structures that do have other hardware mounted on them, NDT shall be performed to the maximum extent possible.

2.1.1.4.6 Electrical Verification Tests: End-to-end testing shall be conducted to verify the electrical interface between the SS and SV(s). The testing shall use flight-representative hardware furnished by the LSC as well as applicable SV(s) components furnished by the SV(s) and/or separation system contractor. The test(s) shall include the complete exercise of all electrical interfaces between the SS, separation system and the SV(s).

Integrated test procedures shall be reviewed and approved by participating agencies. The location of the test will be proposed by the LSC. [CDRL A027 - SS/Payload Electrical Test Procedure; A012 - SS/Payload Electrical Test Report]

2.1.1.4.7 The LSC shall identify, design, test, qualify and approve all Ground Support Equipment (GSE) and LSE required for flight operations prior to the PSR. This equipment shall include lifting slings, transportation fixtures and equipment, umbilical electrical harnesses, electrical test equipment (including electrical GSE) and temperature control systems.

The LSC shall ensure that all required support equipment for assembly, integration, encapsulation and launch at the launch site has been calibrated, safety-qualified and is in working order and available when

OSP-4 PWS – Rev 3 Page 14 of 55 needed. [CDRL A027 - Test Procedures; A012 - Test Report; A013 - Qualification Test Anomaly/Failure Report]

2.1.1.5 Pre-Ship Readiness Reviews (PSRs) and Shipping: A PSR must be completed prior to processing any major SS components or support equipment for shipment to the launch site so that the Government and other launch campaign stakeholders may assess LSC launch campaign readiness and schedule risk prior to committing resources to the campaign. The final PSR shall be held at approximately T-60 days to launch or as directed by the COR, in coordination with the LSC. The LSC is responsible for shipment and/or transportation of all SS hardware, Air/Ground Support Equipment (A/GSE), Launch Support Equipment (LSE) and other necessary LSC items to the Launch Site. [CDRL

A002 - DRIP]

2.1.1.5.1 Readiness: At the PSR, the LSC shall provide an overview demonstrating completion of the Range Safety/cognizant safety authority preparations and tailoring (if required), an acceptable approach to Flight Safety and Flight Termination, and readiness of the launch site and support facilities. The LSC shall also demonstrate that system level testing has been completed and the SS hardware is prepared for shipment to the launch site. [CDRL A012 - PSR and Shipping Readiness Report; A002 - DRIP]

2.1.2 Launch Campaign: The LSC shall execute the launch campaign, coordinate all safety operations with the Range/Cognizant Authority, and ensure that critical skills and qualified personnel are available when required for integration, testing, and on-console operations. The LSC shall also provide calibrated, certified and qualified LSE and GSE as required for the completion of range/spaceport/airfield integration tasks to process, prepare and launch the SS with the integrated SV(s). This activity requires close cooperation between the Government, LSC, SVC(s), and the Range/Cognizant authority.

2.1.2.1 Launch Site and Services: The Government will provide Government services at Government ranges (e.g., Flight Safety, Telemetry, and Radar). The LSC shall specify all required Government range services/support. All spaceport services, non-Government range services, and launch site services shall be provided by the LSC unless otherwise stated in the MRD. [CDRL A003 - Range/License Related Documentation]

2.1.2.2 Range Requirements Coordination and Documentation: The LSC shall comply with all Range processes to ensure that the requirements specified in the SS to Range ICD and other range interfaces (e.g. range facilities requirements document) are safely executed and coordinated with the Range. The LSC is responsible for obtaining, producing and/or coordinating all items required by the Range. The LSC shall develop and provide Universal Documentation System (UDS) or other range-required documentation inputs for submittal by the program office to the Range as required by the launch site. The LSC shall participate in Range working groups as required. [CDRL A003 - Range/License Related Documentation]

OSP-4 PWS – Rev 3 Page 15 of 55

2.1.2.3 System Safety: The LSC shall comply with AFSPCMAN 91-710 (or equivalent, when specified by the cognizant authority) for all applicable launch site activities. These safety requirements may be tailored or a commercial equivalent used when approved by the MM, but the LSC is responsible for obtaining approval for any range safety tailoring from the cognizant authority.

The LSC shall plan system safety activities for the entire system lifecycle (from development through disposal) as executed under this Task Order in accordance with MIL-STD-882E Task 102 or commercial equivalent when approved by the COR. The LSC shall coordinate scheduling all activities and/or operations with the Range Safety Office/Cognizant authority, as applicable. [CDRL A003 - Range/License Related Documentation; A020 – Lifecycle System Safety Program Plan]

2.1.2.4 Ground and Flight Safety Hazard Analyses: Ground and flight safety hazard analyses shall be performed in accordance with AFSPCMAN 91-710 (or equivalent when specified by the cognizant authority) and MIL-STD-882E Task 106, Task 202 and Task 205 or commercial equivalent when approved by the

MM.

The LSC shall work with the cognizant range safety office in coordination with program office to tailor (if required) the applicable flight safety requirements for the SS, complete development of a compliant flight safety system and gain range safety approval for the implementation of its flight safety system. The LSC shall make prompt waiver requests to the COR if unable to meet range safety requirements due to technical issues with the design or flight hardware.

Failure to obtain approval for the desired tailoring shall not relieve the LSC of its responsibilities under this contract. [CDRL A003 - Range/License Related Documentation; A020 - Preliminary Hazard Analysis, System Hazard Analysis]

2.1.2.4.1 Safety and Environmental Documentation: The LSC shall support the Government safety and environmental documentation required for safety, hazards, debris, and environmental analysis in accordance with MIL-STD-882E Task 301. Documentation includes System Safety Program Plan, Safety Assessment Report, Failure Modes Effects and Criticality Analysis (FMECA), Reliability reports, and AF Form 813 Environmental Impact Analysis inputs. [CDRL A020 - Safety Assessment Report; A028 - Reliability Reports; A029 - FMECA]

2.1.2.5 Facilities and Services: The LSC shall provide the required facilities and services at the launch site, which meet all mission requirements defined in the SLPRD, SLIS, and MRD. These requirements shall include, but are not limited to, safety, contamination control, SV(s) integration, flight control facilities, transportation, lifting/stacking and fueling infrastructure, unless otherwise specified. The SV(s) Processing Facility (capable of accommodating LSC encapsulation activities) will be provided by the SV(s) contractor unless otherwise stated in the MRD. [CDRL A003 - Range/License related Documentation]

OSP-4 PWS – Rev 3 Page 16 of 55

2.1.2.6 Approvals and Waivers: The LSC shall obtain any necessary coordination or approval from the cognizant range for activities taking place at the cognizant range. The LSC shall obtain appropriate documentation, approvals, and perform other necessary actions to secure access to GFP, equipment, facilities, etc. If waivers are required, the LSC shall obtain them prior to initiating facility activation or modification. The LSC shall brief equivalent levels of safety requests at range working groups and formal reviews. The LSC's failure to gain a required approval or waiver shall not relieve the LSC of any responsibilities under this contract. If the LSC identifies any work outside the scope of this contract that is required to meet range requirements, the LSC shall immediately notify the PCO. The LSC shall provide the Government with the necessary information to support approval processes for the launch (i.e. SS RF Frequency approval, Indemnification). [CDRL A003 - Range/License Related Documentarian]

2.1.2.7 New Strategic Arms Reduction Treaty (START) Requirements: If the SS uses GFP motors subject to New START treaty considerations (e.g. Minuteman III ICBM first stage motors), the LSC shall provide “interpretive data” on all telemetry that is transmitted prior to the SS achieving burnout for incorporation into documents required by the New START Treaty. Encryption of telemetry data may not be permitted when launch is subject to the New START Treaty.

[CDRL A017 - New START Treaty Interpretive Data]

2.1.2.8 Cybersecurity: Classification requirements for the mission will be specified in the MRD.

2.1.2.8.1 Unclassified Information: The LSC shall obtain cognizant range authority to connect approval(s) for all commercial information systems planned to support the launch.

2.1.2.8.2 Classified Information: All nonfederal computer systems and software packages that will be used for processing, transmitting, and/or storing Government classified information shall be accredited following the Defense Security Service (DSS) Office of the Designated Approving Authority (ODAA) certification and accreditation process. This is the standard process under which commercial information systems handling DoD classified information achieve and maintain Authority To Operate. [CDRL A023 – Cyber Security Implementation Plan]

2.1.2.9 Classified Payloads: SV(s) may be classified to varying levels and the LSC shall be able to accept delivery and process all SV(s) in accordance with the MRD and DD254. In order to receive an award of a classified SV mission LSC should be able to obtain at a minimum “SECRET” facility clearance. When classified SV(s) are processed the LSC shall provide trained people with the proper clearance to perform the required work in compliance with the applicable Security Classification Guide. Classification requirements for each mission will be specified in the MRD.

2.1.2.9.1 Communication Security (COMSEC):Contractors may require access to COMSEC information. The DD254 will give further instructions on

OSP-4 PWS – Rev 3 Page 17 of 55 safeguarding and managing COMSEC material. Access will be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances.

2.1.2.9.2 Operations Security (OPSEC):The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. Critical Information is defined as information about USAF missions or activities the adversary needs to achieve their goals. The LSC shall ensure compliance with DoDD 5205.02, DoDM 5205.02-M, and/or other applicable Government security regulations including procedures to protect classified and/or controlled classified Government projects and/or programs.

2.1.2.9.3 Restricted/Formerly Restricted Data:Obtain a final U.S. Government clearance at the appropriate level before obtaining access to RESTRICTED DATA and FORMERLY RESTRICTED DATA.

2.1.2.9.4 Controlled Unclassified Information (CUI): The LSC may be required to receive or transmit classified documents. Specific security requirements will be defined in the DD254. The LSC shall comply with DoDI 5200.48 for identification, protection and training requirements of CUI. The LSC shall be responsible for training their personnel and accomplishment of the out-processing procedures identified in DoDI 5200.48. The LSC shall comply with DoDM

5400.07 and AFMAN 33-302 FOIA requirements. Protection of unclassified DoD information not approved for public release on non- DoD Information Systems will be protected IAW DoDI 8582.01.

2.1.2.10 SS/SV(s) Operations: The LSC shall integrate the SV(s) with the SS and perform end-to-end testing with the SV(s); this will occur in a clean room environment as specified in the MRD. End-to-end verifications tests are tests of the hardware/software to obtain or validate engineering data on the performance of the system prior to the execution of the launch operation. The LSC shall perform integrated operations using procedures approved by participating agencies. [CDRL A027 - Integration Test Procedure]

2.1.2.10.1 Launch Verification Testing: An integrated field processing procedure shall be prepared by the LSC test conductor in each test. All anomalies shall be documented by the LSC. [CDRL A027 - Payload Integration Test Procedure]

2.1.2.10.2 SS/SV(s) Mating: Unless otherwise specified in the MRD, the SV(s) contractor will be responsible for all SV(s) integration activities prior to SV(s) mating. During SV(s) mating, the SV Contractor(s) will furnish certified handling/GSE required to interface from the crane hook (or other GSE) to the SV(s), as required during the integration process.

The SV(s) contractor will transfer responsibility for the SV(s) to the LSC when the SV(s) is prepared for immediate mating with the SS and

OSP-4 PWS – Rev 3 Page 18 of 55 is approximately three inches (3”) away from the SS mating surfaces.

The LSC shall conduct mechanical mating, spurious voltage, and electrical connection checks in concert with the SV(s) contractor. The LSC’s responsibility for the SV(s) will end at SV(s) separation(s).

2.1.2.10.3 SS/SV(s) Integrated Processing: Integrated SS/SV(s) processing shall be performed in preparation for SV(s) emplacement on the SS at the launch site. During integrated processing the LSC shall accommodate the SV(s) GSE at the launch site. The LSC shall assist the SV(s) contractor in conducting post-mate checks that may include the SV(s) operational assurance tests and a compatibility test of the SS and SV(s) systems, and the GSE interfaces. Following the post-mate checks, the LSC shall encapsulate the mated SV(s).

2.1.2.10.4 SS/ SV(s) Flight Integration Tests: The flight integration test shall be performed using the flight hardware to verify electrical compatibility and system performance between the SV(s) and the SS upper section(s) prior to movement to the launch site (typically performed within a processing facility at the launch range). The LSC shall provide hardware for any SS-required tests and the SV(s) contractor will provide hardware for any SV(s)-required tests.

2.1.2.10.5 SV(s) Support Equipment and Ground System Checkout: The SV(s) contractor will install the required SV(s) Support Equipment at the launch site in locations to be defined in the SS/PL ICD. A design compatibility test to establish high confidence in electrical compatibility of the SV(s) and SV(s) GSE with the launch complex will be performed at the launch site. The SVC(s) will prepare the test procedure and conduct the test. The LSC shall provide support personnel, facilities access, and the SV(s) contractor will supply all SV(s)-related GSE. The LSC shall provide support to the SV(s) contractor to test the installed equipment. [CDRL A027]

2.1.2.11 Simulations & Rehearsals: For all category missions: The LSC shall coordinate and conduct one tailored mission dress rehearsal and one tailored wet dress rehearsal (for liquid propulsion SSs only). The mission dress rehearsal is a simulated countdown, exercising range interfaces to verify the operational readiness of the entire Aerospace Vehicle Equipment (AVE) and ground system with all launch team members participating. The wet dress rehearsal is a simulated countdown, exercising range interfaces to verify the operational readiness of the entire AVE and ground system, including SS propellant loading, with all launch team members participating. (The term AVE refers to the entire SS). The mission dress rehearsal and wet dress rehearsal may be combined into one rehearsal, contingent upon approval by the COR. These simulations shall include all launch day participants (e.g., Range, LSC, SV(s) contractor, Government, and others as applicable) unless otherwise specified.

For Cat 2 and Cat 3 missions: The LSC shall coordinate and conduct, at a minimum, one Tabletop (countdown review) rehearsal and one green card

OSP-4 PWS – Rev 3 Page 19 of 55

(simulated countdown with simulated anomalies) dress rehearsal. The Tabletop rehearsal is a review of the countdown notebook to help the day-of-launch team identify mission partner countdown scripts. The green card dress rehearsal is a communication-only rehearsal, performing the simulated countdown and exercises anomaly handling and resolution, conducted by key members of the launch team and utilizes the day-of-launch communication process.

2.1.2.11.1 The LSC shall develop a countdown procedure to include launch countdowns, mission constraints and mission overviews/timelines.

2.1.2.11.2 The LSC shall coordinate and conduct "Day of Launch Academics" to provide countdown procedure awareness training to the Government launch team on the day of launch activities.

2.1.2.11.3 The LSC shall provide delta academics to cover any emerging changes with the launch countdown procedure driven by observations from the Green card and/or Mission Dress and table top exercises. Day of Launch Academics should specifically cover integration activities for the space vehicle, and launch vehicle DOL timelines and mission constraints.

2.1.2.11.4 The LSC shall provide corrections over the net before launch rehearsals/operations commence, unless the corrections have already been delivered to the Government as change pages to the countdown notebook.

2.1.2.11.5 The LSC shall compile mission launch notebook data and identify corrections. [CDRL A011 - Launch Notebook]

2.1.2.12 Mission Constraints: The LSC shall compile all SV(s) and SS launch constraints, and coordinate these with the MM prior to inclusion in the mission launch notebook data. [CDRL A011 - Mission Constraints Document]

2.1.2.13 Launch Activities: The LSC shall prepare the SS for launch, conduct prelaunch checkout, conduct launch operations, ensure the collection and recording of telemetry during the launch, support post launch mission activities, perform post-flight analysis, and conduct site shutdown. During the launch campaign, the LSC shall create and maintain a daily activity schedule and coordinate with the MM [CDRL A030 – Daily Activity Schedule].

2.1.2.13.1 Nets and Telemetry: The LSC shall provide the Government with access to all voice (transmit and receive), video, and data networks used for launch support. The LSC shall provide for instrumentation at the launch site, downrange, and on the SS in order to measure the predicted (modeled) launch and flight performance and environments. At Government ranges, the LSC shall provide requirements for range and downrange telemetry collection via the UDS process. Telemetry from this instrumentation shall be provided real-time to a demarcation point defined in the ICD, in order to support telemetry monitoring with an independent Government system. The LSC shall provide all conversions (engineering unit conversion file) necessary to convert the

OSP-4 PWS – Rev 3 Page 20 of 55 raw data to engineering units as well as definition of telemetry format for independent Government processing. [CDRL A011 - Telemetry Document]

2.1.2.13.2 Day of Launch: For MA Category 1 missions, the LSC shall be responsible for Day of Launch operations and the final readiness decision for the combined SS/SV(s) system. The LSC shall accommodate a small contingent (2-3 persons) of Government personnel to monitor launch operations for Government insight. The Government will not have a Mission Director (MD) for these launches or have an approval role in the launch decision. The LSC shall accommodate a small contingent of 2-3 SV(s) personnel as observers.

The LSC shall not launch if the SV(s) lead informs the LSC of non-readiness to launch during the final poll for launch readiness. In addition, if GFP motors are involved in a MA Category 1 launch, the LSC shall accommodate a small Government team on console to monitor the status of the GFP motors. The LSC shall not launch if the Government team informs the LSC of non-readiness to launch, based solely upon GFP motor status, during the final poll for launch readiness.

For MA Category 2/3 missions, the Government will provide the Mission Director, who has a Go/No-Go launch decision during final polling. The LSC shall provide real time vehicle telemetry data displays to Government personnel for all testing and launch operations conducted at the launch site. Specific data requirements shall be coordinated with the COR.

The LSC shall provide trajectory and covariance data to support Collision Avoidance Calculations. [CDRL A004 - Trajectory and Covariance Data Analysis Report]

The LSC shall define an SS instrumentation approach (type and model, function, location, orientation (if applicable), and data archiving.

[CDRL A011 - Instrumentation Document].

2.1.2.14 Post-Flight Activities: The LSC shall conduct an analysis and participate in a review of all launch operations, flight telemetry, and other data to determine SS performance.

2.1.2.14.1 Quicklook Analysis: The LSC shall develop the T+4 hours (Quicklook) analysis and T+4-day post-flight analysis report. Analyses shall include characterization of trajectory parameters, mission timeline/events, environments, telemetry performance, observations and anomalies. [CDRL A017 - T+4 Quicklook Report; A017 - T+4 Postflight Report]

2.1.2.14.2 Lessons Learned: The LSC shall collect lessons learned throughout the performance of the mission and support the Government Integrated

OSP-4 PWS – Rev 3 Page 21 of 55

Product Team (IPT) lesson learned process. [CDRL A017 - Lessons Learned Report]

2.1.2.14.3 Post-Flight Analysis and Post-Flight Review (MA Cat 2/3 only): The LSC shall complete the post-flight analysis by T+30 days, regardless of MA category. The LSC shall attend and support a Government post flight review at SMC (Los Angeles, CA) at approximately T+60 days.

[CDRL A017 – Post-Flight Report]

2.1.2.14.4 Failure Review: In the event of a complete or partial mission failure, the LSC shall participate in a Government-led evaluation of the root cause of the failure event to identify remedial actions required to prevent recurrence. Mission failure reviews will be conducted in accordance with appropriate licensing procedures as indicated by MA Category. The LSC shall enable Government access to all internal investigations of anomalies and failures. [CDRL A013 - Launch Failure Analysis and Corrective Action Report]

2.1.3 Integrated Product Team (IPT) Meetings: The LSC shall structure its program coordination to provide clear, direct points of contact with the Government and shall support weekly Government IPT meetings led by the Government COR and/or MM.

During this meeting, the LSC shall communicate and coordinate program status, discussion of technical information, and resolution of contract/financial issues.

2.1.4 Periodic and Technical Interchange Meetings (TIM): The LSC shall support any IPT working groups designated by the IPT and MM to address specific mission issues of concern that require the combined attention of the Government, supporting contractors, and LSC. The LSC shall organize TIM minutes and capture new concerns and updated status of prior concerns with a consolidated action item list. The LSC shall support daily telecons during the launch campaign. [CDRL A001 - Report, Record of Meeting Minutes]

2.1.5 Multi-SV Missions: When stated in the MRD, the LSC may provide the launch service as a multi-SV mission.

2.1.5.1 Payload Integration Service

2.1.5.1.1 The LSC shall integrate all SV(s) into an Integrated Payload Stack (IPS), also known as the PL. The LSC shall ensure that SV(s) do not harm or damage other SV(s) on the IPS or the SS.

2.1.5.1.2 The LSC shall coordinate…