Attachment 1_PWS_18Jul2023.pdf

NASA Flight Opportunities Program

Performance Work Statement (PWS) for Suborbital/ Hosted Orbital Flight and Payload Integration Services

July 18, 2023

1. Background

The Flight Opportunities Program (hereafter FO or “the Program”), part of NASA’s Space Technology Mission Directorate (STMD), rapidly demonstrates promising technologies for space exploration, discovery, and the expansion of space commerce through suborbital testing with industry flight providers. The program matures capabilities needed for NASA missions and commercial applications while strategically investing in the growth of the U.S. commercial spaceflight industry. FO has provided opportunities to fly technology payloads on Qualified Vehicles (QVs) that provide relevant environments required to test technologies (including, but not limited to, reduced gravity, exposure to the space environment, and free fall) in order to advance their technology readiness.

Flight Opportunities also partners with STMD’s Small Spacecraft Technology (SST) program, which expands the ability to execute unique missions through rapid development and demonstration of capabilities for small spacecraft applicable to exploration, science, and the commercial space sector. Similar to FO, SST works with industry providers to advance technologies through flight testing in relevant environments (including, but not limited to orbital flight).

2. Objective

The Government has a requirement to advance technologies and procedures for operating in space, including testing in high altitude, reduced gravity, or other relevant environments. To fulfill this requirement, the Government intends to acquire space on commercial flights for technology payloads along with the associated payload integration services with the objective of flying these payloads aboard QVs that provide high altitude, reduced gravity, or other relevant environments required to test the technologies and advance their readiness. Additionally, the Government intends to acquire space for Government Suborbital Research Specialists to fly as passengers aboard those QVs capable of supporting human flight. The flights and other services provided are for NASA and other Government Agencies (OGAs) use.

3. Scope

The Provider Pool (“Pool”) shall be capable of providing flight opportunities to a variety of Government-sponsored payloads on various platforms (including, but not limited to, high-altitude balloons, suborbital rocket-powered vehicles, and orbital vehicles capable of hosting payloads). The Government may require individual payloads or Government

Suborbital Research Specialist accommodations (hereafter referred to as a “slot” or “seat”, respectively), multiple payloads/multiple seats, and partial or full manifests. The contracts will be for comprehensive services inclusive of flight, payload integration services, and in some instances, human accommodations.

The Government may periodically provide opportunities for additional contractors and/or Qualified Vehicles to be added to the Provider Pool (On-Ramp). The Government may also consider future Expansion of Performance Capabilities covered by this contract.

4. Ordering Requirements Each successful vendor (hereafter “Contractor”) will receive an indefinite delivery/indefinite quantity (IDIQ) contract, with the opportunity to propose on Task Orders issued by the Government to fly payloads or Government Suborbital Research Specialists.

The Manifest Requirements Document (MRD) is defined as the document that establishes the payload operational requirements, requirements for a potential Suborbital Research Specialist(s), mission performance requirements, data delivery requirements, payload access requirements, and the mission exit criteria. The MRD is developed by the Government based on information furnished by the Payload Provider or seat requestor. The MRD will be issued to the Provider Pool as part of a Task Order solicitation. A Task Order solicitation may contain requirements for flying one or more payloads and/or seats on one or more flights.

5. General Requirements

5.1. Qualified Vehicles and Qualified Vehicle Families

Contractors shall utilize only those vehicles or family of vehicles that have been accepted by the Government as Qualified (Qualified Vehicles - “QVs” or Qualified Vehicle Families – “QVF”) to provide services under this contract. A QVF shall be a group of closely related vehicles (similar in characteristics with different performance or payload capacities) that fly similar flight profile(s). The Government will be the sole authority for determining if a Vehicle or Vehicle Family is Qualified.

For Profile 6, the orbital launch vehicle used to place the orbital platform in orbit is not considered to be a component of the QV / QVF, unless it is the exclusive U.S.

commercial option for launching the particular orbital QV / QVF.

All QV / QVF and orbital launch vehicles must be owned and operated by a U.S.

commercial provider, as defined by 51 U.S.C. § 50101(7). In addition, the QV / QVF or orbital launch vehicle shall be majority (51% or more by value) manufactured or assembled in the United States.

Note that Section 907 of the NASA Authorization Act of 2010 (Public Law 111–267) and subsequent appropriations language directs the Flight Opportunities program to focus on the commercial spaceflight industry and reusable spacecraft. As such, platforms with a propulsion system that does not operate in a vacuum (e.g., drones, helicopters, airplanes) are not included in this PWS. A special exemption is made for high altitude balloons due to their ability to act as long duration surrogates for orbital satellites.

5.1.1. Suborbital Rockets

The category of suborbital rockets includes both crewed (i.e., vehicles with crew and/or Government Suborbital Research Specialist) and uncrewed rocket-powered vehicles capable of achieving a minimum altitude of 80 km above Mean Sea Level [MSL]. This may include suborbital stages of orbital launch vehicles that are capable of hosting payloads. Crewed suborbital rockets must be licensed in accordance with 14 CFR Chapter III to operate commercial flights for compensation or hire in the U.S., or possess applicable FAA documentation to fly as part of the process of being licensed to operate commercial flights for compensation or hire in the U.S. Uncrewed suborbital rockets must be licensed in accordance with 14 CFR Chapter III to operate commercial flights for compensation or hire in the U.S., or the Contractor must possess applicable FAA documentation to fly from the FAA as part of the process of being licensed to operate commercial flights for compensation or hire in the U.S. or otherwise hold the appropriate waiver or written authorization from the FAA in accordance with 14 CFR § 101 Subpart C.

5.1.2. Rocket-Powered Lander Vehicles

Rocket-powered lander vehicles shall be capable of performing a controlled descent and controlled vertical landing of a free-flying vehicle using a propulsion system of a class that can operate in a vacuum. Rocket-powered lander vehicles are required to meet the same licensing, waiver, or written authorization requirements as suborbital rockets. Tethered rocket-powered lander vehicles are also eligible, so long as they meet the definitions of a “tethered launch vehicle” specified in 14 CFR § 400.2 (c) or hold the appropriate waiver or written authorization from the FAA. Tethered service is allowable only in addition to the requirement to be a free-flying rocket powered landing vehicle.

5.1.3. High-Altitude Balloons

High-altitude balloon vehicles must be capable of operating at a minimum altitude of 18.3km (60,000ft) and may include both crewed and uncrewed vehicles.

Crewed high-altitude balloons must be licensed to operate commercial flights for compensation or hire in the U.S. or possess applicable FAA documentation to fly as part of the process of being licensed to operate commercial flights for compensation or hire in the U.S.

Uncrewed high-altitude balloons must comply with 14 CFR § 101 Subpart D or must otherwise hold the appropriate waiver or written authorization from the

FAA. In addition, it is recommended that all high-altitude balloons consider the inclusion of ADS-B systems to provide enhanced air traffic control situational awareness.

5.1.4. Orbital Platforms

Orbital platforms hosting payloads must be able to provide power and communications to the payload (e.g., payload telemetry, payload command and control), as well as perform at least one orbit around the Earth. Payloads may remain attached to the orbital stage(s) of a launch vehicle or be hosted on a satellite. Orbital platforms must be owned and operated by a U.S. commercial entity and must use FAA-licensed U.S. commercial launch services. There shall be a plan for safe end-of-mission disposal at the end of the orbital platform’s operational lifetime, such as defined in NASA STD-8719.14 or equivalent documents. For orbital platforms with propulsive capability, a plan to protect the command uplink shall be submitted for Government approval. Plan submittal deadline will be specified in the MRD.

5.2. Operating Requirements

5.2.1. Independent Operations

The Contractor shall operate independently from the Government, except that payloads may be Government-owned or Government-provided and Government Suborbital Research Specialists, if any, will be authorized by the applicable government agency.

1. The Contractor may propose the use of unique Government-owned ground and range facilities on a fully reimbursable basis, but in no way shall that release the Contractor from full responsibility for all aspects of flight and ground operations. All such arrangements shall be the sole responsibility of the Contractor.

2. All end items and services provided through this contract, including (but not limited to) payload slots and seats on QVs, QV components, subsystems, ground support equipment and facilities, and contracted services shall not be Government provided, owned, or operated.

3. The Contractor, or their subcontractor(s) as applicable, shall be solely responsible for obtaining all appropriate permits, licenses, waivers, and/or flight approvals.

4. The Contractor, or their subcontractor(s) as applicable, shall be solely responsible for Ground and Flight Safety, Mission Assurance, and Environmental compliance in accordance with local, state, and Federal regulations.

5. The Contractor, or their subcontractor(s) as applicable, shall provide all QV systems engineering, payload integration, and any other services required for a successful launch.

6. The Contractor, or their subcontractor(s) as applicable, shall be responsible for timely communications of detailed information about the flight and other services to the Government, Payload Provider, including, but not limited to, changes in vehicle readiness and other changes that affect the flight schedule.

5.2.2. Government Observers

The Contractor shall provide Government observers access to Contractor facilities on a non-interference, ad hoc basis.

5.2.3. Commercial Operations

The Contractor shall be capable of providing payload slots and/or Suborbital Research Specialist seats on QVs with commercial flight operations.

5.3. Payload Requirements

5.3.1. Security and Recoverability

The following requirements shall apply to all flight operations. Note, however, that for orbital platforms, the Government has no expectation that the payload is recovered post-flight, except where the contractor provides intact recovery of payloads as part of the service delivery.

1. Unless specified in the task order, payloads shall be considered expendable test articles with no NASA or OGA mission purpose other than the demonstration of various technologies in relevant environments.

2. Notwithstanding Paragraph 1 above, Contractor shall assume complete responsibility for physical security of payloads upon receiving payloads from the Payload Provider, until payloads are released back into provider’s custody.

3. Payloads have value to the Payload Providers. Notwithstanding Paragraph 1 above, the Contractor shall make reasonable effort to return payloads to the Payload Provider within 10 working days or as specified in the MRD from completion of final flight operation, and with no damage exceeding normal wear-and-tear and exhaustion of expendable items.

5.3.2. Accessibility

Unless modified within the governing Task Order, the following requirements apply to all flight operations.

1. For suborbital vehicles, the Contractor shall coordinate with and provide access for Payload Providers to their payloads both before and after flights as needed. Detailed requirements for access will be specified as part of the Manifest Requirements Document (MRD)/Mission Implementation Document (MID) process.

2. For orbital platforms, it is understood that access pre-flight after integration of the payload may be limited and access post flight may be unavailable if the payload is not recoverable or is otherwise inaccessible. For flights on orbital platforms where the payload is not recovered post-flight, accessibility requirements do not apply.

Detailed requirements for access will be specified as part of the MRD/MID process.

3. In a multi-flight campaign, the Contractor shall allow the Payload

Provider access to payloads between flights for servicing and data recovery. Detailed requirements for access will be specified as part of the MRD/MID process.

5.3.3. Manifesting/De-Manifesting

The Contractor shall be responsible for communicating and coordinating with the Government in regard to the proposed payload manifest for each flight that incorporates Government payloads. Similarly, in the event that circumstances require any Government payload(s) to be de-manifested from a flight, the Contractor shall directly communicate and coordinate with the Government prior to proposing or executing any manifest changes of Government-contracted payloads.

5.4. Overview of Operations with Government Suborbital Research Specialist(s)

A Government Suborbital Research Specialist may undertake tasks such as tending a technology payload (i.e., payload mounted to the vehicle or in a locker or other rack) or conducting procedural or operational tests and/or observations that may include handheld or on-person tools/equipment.

5.4.1. Flightworthiness & Flight Safety Approvals for Operations with Government

Suborbital Research Specialist

Task Orders that include Government Suborbital Research Specialists will be limited to those providers that have demonstrated that they meet all NASA Safety Objectives as determined by the NASA Suborbital Crew Program and have received written approval from NASA that they are eligible to fly Government Suborbital Research Specialists.

5.4.2. Manifesting/De-Manifesting

The Contractor shall be responsible for communicating and coordinating with the Government in regard to the proposed manifest for each flight that incorporates Government Suborbital Research Specialists. Similarly, in the event that circumstances require any Government Suborbital Research Specialist to be de-manifested from a flight, the Contractor shall directly communicate and coordinate with the Government prior to executing any manifest changes of the Government Suborbital Research Specialist.

5.5. Flight Schedule

To provide flexibility to both the Contractor and the Government, while also providing a level of schedule certainty required for the success of Government-provided payloads, a Flight Operations Window will be established for each launch / flight within a Task Order.

Within the MRD, the Government will specify the desired dates for flight, including a no-earlier than date, indicating when the payload will be ready to fly, and a no-later than date, indicating the date by which the flight must be completed. As applicable, the MRD will also include any additional constraints on the flight window or adjustment of the flight window.

Within the MID, the Contractor will provide an initial Flight Operations Window based on the Government’s desired flight dates as well as the Contractor’s flight availability.

Thereafter, unless otherwise specified in the MRD, as the target flight date approaches, the Flight Operations Window will be refined as needed via PWS Attachment 1:

Documentation of Flight Operations Window Refinement, which will document mutual agreement between the Contractor and the Government.

If either the Government or Contractor desires a change to the Flight Operations Window date, the Government or the Contractor will give prompt written notice of the desired change via PWS Attachment 1 to begin the negotiation process. If at any point the refined Flight Operations Window moves beyond the no-later than date specified in the MID or as mutually agreed upon within PWS Attachment 1, a modification to the Task Order may be required.

For requests by the Government to change the Flight Operations Window on flights that are other than a full manifest, potential range availability or commitments to other customers may prevent the Contractor from being able to accommodate a Government requested change to the Flight Operations Window. In such cases, options for the government to request a delay to the Flight Operations Window will be defined as part of the MRD/MID process.

5.6. Mishap-Related Requirements

Unless otherwise stated in a Task Order, payloads flown under this Contract are considered expendable and damage to or loss of a payload is not considered a NASA mishap. The Contractor may be subject to FAA and NTSB mishap investigation requirements based on the portion of the U.S. Code of Federal Regulations relevant to their flight operations or other Memoranda of Understanding. If not the subject of an FAA or NTSB investigation, NASA may require the Contractor to conduct an investigation into a mishap or close call involving government personnel, including Government Suborbital Research Specialists.

5.6.1. The Contractor shall notify and promptly report to the contracting officer, or designee, any of the following associated with any work performed under this Contract:

1. Close calls involving NASA personnel that could have resulted in a mishap;

fatality; lost-time occupational injury; or occupational disease.

2. Mishaps involving NASA personnel that result in fatality; lost-time occupational injury; or occupational disease.

5.6.2. The Contractor shall conduct an investigation for any event that meets the requirements of paragraph 5.6.1. The Contractor shall allow NASA participation in the investigation and make all data and resulting reports available to NASA. The Contractor is not required to include in any report an expression of opinion as to the fault or negligence of any employee.

5.6.3. The Contractor shall maintain the data of any investigation referenced above for the term of this Contract plus three (3) years.

5.7. ITAR/Export Control Restrictions and Payload/Suborbital Research Specialist Conflicts

There may be instances where the government will need to fly payload(s) and/or Suborbital Research Specialist(s) conducting activities/experiments with potential ITAR/Export Control considerations. To prevent any conflicts, the Contractor shall promptly evaluate, identify, and notify the Government of any potential ITAR/Export Control issues in relation to onboard experiments and/or Suborbital Research Specialists.

Unless otherwise specified in the Task Order, the Contractor shall obtain any required export licenses. Under all circumstances the Contractor shall comply with the ITAR/Export Control process and provide any required data in timely manner to support export licensing.

6. Flight Profile Requirements

Flight profile requirements will vary greatly for any given payload. The proposed profile performance of the vehicle will be evaluated during the Task Order evaluation process based on the requirements in the Manifest Requirements Document (MRD) for each specific payload. Typical flight profile requirements are listed below.

Contractors shall provide one or more of the listed profiles for each QV or QV family. In some cases, a QV may be qualified for more than one profile.

All QVs shall be capable of carrying a minimum total payload mass of 2 kg and accommodating a minimum total payload volume equivalent to a 2U CubeSat. The Government may require more or less mass and volume for a particular payload; actual payload requirements will vary and be dependent upon actual QV capabilities and payload mass and volume requirements as specified in each MRD. If the QV is capable and approved to fly Government personnel as part of any of these flight profiles, a Task Order may reflect a requirement for a Government Suborbital Research Specialist when needed (ref. PWS Sect.

5.4).

These profiles are described from the perspective of the payload, not the vehicle. These profiles represent typical minimum requirements; actual requirements issued in an MRD may vary from those specified here.

6.1. Profile 1 (P1): Reduced gravity with space environment

Payload is typically an experiment requiring a period of continuous microgravity and/or exposure to the space environment. Requirement is to ascend to a minimum of 80km above mean sea level (MSL), (≥ 100km MSL desired), and expose the payload to a reduced gravity environment for at least two (2) minutes with a total gravitational vector of less than +/- 0.05g (RMS) under stable gravitational conditions in all axes.

The ability to achieve a total gravitational vector of less than +/- 0.005g (RMS) under stable gravitational conditions in all axes for at least a portion of this duration is desired. This profile is typically accomplished by use of a sounding rocket or spacecraft. Some payloads may also require the simultaneous exposure of the payload to near-vacuum and external environment. Vehicles that can achieve the required altitude and reduced gravity but cannot expose the payload to the outside environment may also be qualified for this profile.

6.2. Profile 2 (P2): Exposure to high-altitude and long-duration flight

Under this profile, vehicles shall be capable of providing payloads with external views of the Earth below as well as access to the environment for sensing. Payload types will vary, including remote sensing packages or other systems being tested for use on satellites or other spacecraft. These can be tested by use of an untethered balloon with parachute descent that could allow, for example, testing experimental parachutes or similar atmospheric descent systems. Other vehicles could include untethered balloons or untethered airships with guided trajectory capabilities and controlled landings. The aforementioned vehicles may have additional capabilities such as altitude loitering or geolocation station keeping. In all cases, landing characteristics should be sufficient to recover the payload, for example by means of a soft landing or a parachute recovery.

For consideration under this profile, a QV shall meet the requirements listed in either Section 6.2.1 or 6.2.2 below:

6.2.1. Exposure to high altitude

Payload is typically an experiment requiring exposure to the near-space environment at a minimum of 30km MSL with a flight time of 1 hour or greater along a pre-planned guided flight trajectory, followed by a descent to 0m above ground level (AGL).

6.2.2. Exposure to altitude and long-duration flight

Payload is typically an experiment requiring exposure to an altitude of at least

18.3 km MSL (60, 000 feet MSL) with a float time of 7 days or greater along a pre-planned flight trajectory, followed by a descent to 0 AGL.

6.3. Profile 3 (P3): Space environment with free-fall descent

Payload typically involves testing of systems and components such as thermal protection or decelerators for objects reentering a planetary atmosphere. Requirement is to attain a minimum of 80km MSL, typically ≥ 100km MSL, followed by a free-fall descent of the payload to 0 km AGL. This is typically accomplished by use of a sounding rocket or spacecraft with the payload ejected after main engine cutoff.

6.4. Profile 4 (P4): Controlled descent with controlled vertical landing

Payload is typically an experiment to test concepts for planetary landers. Requirement is to descend from a minimum of 250m AGL to 0m AGL, under controlled rocket-powered flight and conduct a controlled vertical landing. Some payloads may require controlled horizontal translation of at least 100m . Some applications may require allowing the payload to actively control portions of the flight profile. This profile is typically accomplished by use of a spacecraft or a vertical flight testbed.

6.5. Profile 5 (P5): Controlled high-altitude ascent and descent

Requirement is to ascend to a minimum of 30km MSL along a pre-planned trajectory, spend 1 or more minutes above 30km MSL, and then descend back to 0 AGL along a controlled trajectory. Payload is typically a remote sensing system for planetary entry, high-altitude atmospheric measurements, or similar applications. Payloads may require access to the external environment to make observations or obtain measurements. It would be desirable to have the capability of accepting pointing control and guidance commands from the payload. It would also be desirable to provide the payload a view of the Earth below. Landing should be sufficient to recover the payload intact, which may entail either a soft landing or a parachute recovery. In some cases, QVs may have different ascent and descent locations as part of a single flight. This profile is typically accomplished by use of a spacecraft or first (primary) stage of a multi-stage rocket-powered vehicle. Some payloads may require short durations of reduced gravity under this flight profile.

6.6. Profile 6 (P6): Hosting on Orbital Platform

Payloads typically are intended to operate in an orbital environment, either in a non-pressurized (exposed to the space environment) or pressurized environment. Qualified orbital platforms must perform a minimum of one complete orbit around the Earth, with a perigee typically > 160 km. The orbital platforms shall be capable of providing power and communications services to the payload. Some payloads may require pointing capabilities. Examples of orbital platforms include satellites or orbital stages of launch vehicles.

7. Other Requirements

Unless modified within the governing Task Order, the following requirements shall apply to all contractors.

7.1. Data Collection

The Contractor shall allow Payload Providers and/or Suborbital Research Specialists to collect, publish, and/or distribute any non-proprietary data that was collected during the flight. At its discretion, the Contractor may accept or refuse any data requests from Payload Providers involving the release of proprietary flight data for supplementing any non-proprietary experimental data collected during the flight.

Additionally, the Contractor shall provide the Government a Flight Data Report at the conclusion of each flight campaign (ref. PWS Section 9.3).

7.2. Reviews and Documents

7.2.1. Payload User Guide (PUG)

For each QV or QV family (as necessary), the Contractor shall submit to the Government a Payload User Guide (PUG; see definition in PWS Section 9) for review and approval by the Government no later than thirty (30) days after contract award and upon any updates/revisions. Note that information published in the PUG does not supersede contractual requirements. The Contractor shall also make the most updated PUG available to the Payload Provider. In addition, the Contractor shall provide a publicly releasable PUG to the general public via the Contractor’s website.

This can be a full PUG or a redacted version that includes at a minimum the following information: overview of QV profile capabilities, overview of the QV, outline of services provided (power, data services, etc.), typical mission integration timelines from contract to flight, general dimension requirements/limitations, high-level interface descriptions, and applicable environments that the payload must meet.

ITAR/EAR information should be redacted from the public version as appropriate.

7.2.2. Mission Implementation Document (MID)

The Contractor shall develop a Mission Implementation Document (MID; see definition in PWS Section 9) in response to Task Order solicitations.

7.2.3. Payload Readiness Review (PRR)

The Contractor shall conduct a Payload Readiness Review (PRR) with the Payload Provider prior to delivery of the payload. The Contractor shall work with the Payload Provider to ensure payloads meet all flight provider requirements (including safety) and shall be responsible for accepting or refusing the payloads for integration and flight. For the latter, the Contractor may refuse to accept any payloads for integration that do not meet the requirements of the MID, do not meet the safety requirements included in the Contractor’s Payload User’s Guide (PUG), or are otherwise considered unsafe. The Contractor shall allow the Government to observe and ask questions during the PRR and approval process for Government payloads and will provide any associated documentation. Upon written request, the Contractor shall allow the Government to observe the Flight Readiness Review or equivalent activity on a non-interference basis.

7.2.4. Flight Readiness Review (FRR) for Flight with Government Suborbital Research Specialists

The Contractor shall conduct a Flight Readiness Review (FRR) following their internal process. The Contractor shall allow the Government to observe and ask questions during the FRR for flights with Government Suborbital Research Specialists and will provide any associated documentation to ensure that NASA representatives have an appropriate level of insight into any changes or previous flight anomalies that might affect the risk of any given mission and qualified vehicle.

7.3. Flight Service Requirements

The Contractor shall provide flight service on a QV that meets the requirements of the

MID.

7.3.1. Flight / Mission Approvals

The Contractor, or their subcontractor(s) as applicable, shall obtain and provide to the Government upon request written evidence of all required flight / mission approvals, including (but not limited to) permits, licenses, export licenses, or waivers for operation, as applicable, from the Federal Aviation Administration (FAA) or other appropriate governing authority for the flight activity.

7.3.2. Flight / Mission Operations Responsibility

The Contractor, or their subcontractor(s) as applicable, shall assume total responsibility for all flight / mission operations, which includes provision of the flight range, operational facilities, and all required personnel. This also includes responsibility for mission security, airworthiness (see Sec 5.4 for specific requirements for operations involving Government Suborbital Research Specialists), flight safety and mission assurance, environmental compliance, range safety, and flight and ground personnel safety and health.

7.4. Payload Integration

The Contractor shall provide payload integration service on the QV.

7.4.1. The Contractor shall integrate the payload into the QV system(s) and verify full functionality according to the terms of the MID and the Task Order.

7.4.2. The Contractor shall perform a PRR prior to payload arrival as well as onsite payload operational readiness and safety check.

7.4.3. The Contractor shall manage an interface control document (ICD) between the payload and the QV that captures the payload/flight specific interface requirements and associated verification requirements. In the event the PUG satisfies this intent and reflects the specific requirements for the payload/flight, then it will be considered the ICD. The Contractor shall provide this document to the Government upon request.

7.4.4. The Contractor shall ensure that the payload meets the interface requirements of the Payload User’s Guide (PUG) and/or the interface control document (ICD).

7.4.5. Pre/Post-Flight Payload Support Facilities: The Contractor shall offer payload providers appropriate facilities for preparing/analyzing samples, as well as inspecting, preparing, and testing their payloads and/or instruments prior to and after each flight, where applicable. Facilities and resources shall include but are not limited to electrical power, adequate lighting, payload servicing space, sample processing space, and internet connectivity.

7.4.6. The Contractor shall ensure that the payload, as integrated and while operating, does not interfere in any way (including EMI, physically, structurally, etc.) with the vehicle systems and other payloads.

8. Special Projects

8.1. Special Projects:

Occasionally, the Government will have requirements that are not specific to flight or payload integration efforts, but that instead may fall within related deliverables such as reports, plans, studies, or other similar deliverables within the general scope of this contract. The requirements for Special Projects shall be further delineated by the issuance of Task Orders.

8.2. Non-Standard Services (NSS):

The Contractor shall perform necessary modifications or additions to payload slots, interfaces, or seats to accommodate unique payload or Suborbital Research Specialist requirements, within the general capabilities of the QV but not within the definition of a Standard Flight Payload Slot or Seat. There are some NSS that are frequently requested (termed “common”) and others that are infrequent or unusual in nature (termed “uncommon”). Uncommon NSS cannot be anticipated prior to assignment of payloads or Suborbital Research Specialists. The requirements for NSS shall be further delineated by the MRD/MID process.

9. General Deliverables

The following items shall be general deliverables applicable to services under this contract.

There will also be specific deliverables as required by each Task Order. These deliverables are not applicable to Special Projects (Section 8.1).

9.1. Payload User’s Guide (PUG)

As stated in 7.2.1, the Contractor shall provide a Payload User’s Guide (see Section 10) for each Qualified Vehicle or QVF, as well as a publicly releasable PUG available via the Contractor’s website.

9.2. Mission Implementation Document (MID)

Contractor shall provide a Mission Implementation Document (MID) for each Task Order (see Section 10).

9.3. Flight Data Report

Contractor shall provide a preliminary Flight Data Report (see Section 10) for each flight/ orbital test performed under this contract within 3 business days after the conclusion of each flight, and a final Flight Data Report within 30 business days.

10. Definitions

Above Ground Level (AGL) is defined as a measured distance above the launch site altitude.

Flight is defined as any contracted suborbital flight / orbital mission operation performed under this contract, regardless of type of vehicle or mode of propulsion.

Flight Data Report is defined as a summary of the flight operation as related to the requirements of the MID and the Task Order. This report contains detailed information regarding the flight profiles flown, including the type of profile(s); reduced gravity duration, level, and quality (if applicable); and formatted data item deliverables as specified in the Task Order. A summary of any unexpected issues encountered as well as lessons learned from each flight will also be included.

Government Suborbital Research Specialist is an individual, who is not crew, carried aboard a QV/QVF.

Interface Control Document (ICD) defines all physical and functional interfaces between the payload and the flight provider’s vehicle, along with verification requirements that define how and what evidence will be provided to show an ICD requirement is met.

Examples include but are not limited to mechanical interface drawings, electrical pinouts, loads, and thermal environments. Providers that do not utilize a single ICD document shall provide a listing of all relevant documents, drawings, and manuals that make up the requirements set between the payload and flight provider vehicle. In the event the Payload Users Guide (PUG) acts as a configuration controlled, payload / flight specific requirements document that meets the intent of the ICD, then it may be substituted in place of a standalone ICD.

Manifest Requirements Document (MRD) is defined as the document that establishes the payload operational requirements, mission performance requirements, data delivery requirements, payload access requirements, and the mission exit criteria; the MRD is developed by the Government based on information furnished by the Payload Provider.

The MRD will be issued to the Contractor(s) as part of a Task Order solicitation.

Mean Seal Level (MSL) is defined as a measured distance above the industry standard datum of globally averaged ocean surface height.

Microgravity (for the purposes of this acquisition) is defined as extremely low values of acceleration in all axes of the payload.

Mission Implementation Document (MID) is defined as the proposal provided by the Contractor in response to the requirements (MRD) presented by the Government.

Non-standard Services (NSS) are those services that are not provided as part of the standard priced payload slot. “Common” NSS are those that may be routinely requested by Payload Providers, and “Uncommon” NSS are those that are unique to an individual payload and are not easily anticipated prior to the assignment of the manifest.

Payloads are expendable test articles with no Government mission purpose other than the demonstration of various technologies in relevant environments.

Payload Integration is defined as integration of a payload to the QV, while ensuring that the interfaces to other payloads and to the QV are compatible and that the mission requirements of the Payload Provider are met.

Payload Provider is defined as the entity that provides a Program-sponsored payload.

Payload User’s Guide (PUG) is the Contractor-provided documentation that defines the payload interfaces of the QV or QVF, including, but not limited to mechanical (including fluid), electrical, communication, information/data, and environmental (e.g., thermal, vibration, acceleration) interfaces. The documentation also defines processing and operations requirements imposed on the payload. The PUG should also list the common NSS that are routinely available.

Provider Pool is the list of vendors with QVs accepted by the Government for providing services under this contract.

Qualified Vehicle (or QV) is a vehicle that has been accepted by the Government as Qualified to provide services under this contract.

QV Family (or QVF) is a group of closely related vehicles (closely similar in characteristics with different performance or capacities) that fly similar flight profile(s). The Government will be the sole authority for determining if a Vehicle Family is Qualified.

Seat is defined as a single seat accommodation for a human passenger. Vehicles may have one or more seats or types of seats available for purchase.

Slot is defined as a single payload space. Vehicles may have one or more slots or types of slots available for purchase.

Standard Flight Payload Slot is the payload space and interfaces on a QV offered as a standard commercial product by the flight services provider.

Successful Flight is defined as a flight that has successfully and safely met all of the requirements of the Task Order.

Vehicle is any means used to fly a payload under this contract, regardless of mode of propulsion (e.g., rocket, spacecraft, balloon). For Profile 6, this is the orbital platform but does not include the launch vehicle used to place that platform in orbit.

NASA Flight Opportunities Program

Performance Work Statement (PWS) for Suborbital/ Hosted Orbital Flight and Payload Integration Services

PWS Attachment 1: Documentation of Flight Operations Window Refinement

July 18, 2023

As stated in the PWS Section 5.5, an initial Flight Operations Window will be agreed upon during the MRD/MID process. This Attachment will be used to initiate the process of refining the Flight Operations Window and document mutual agreement between the Contractor and the Government.

Note: Refinements made via this Attachment may be subject to the requirements/constraints specified in the Task Order.

The party requesting the refinement should complete the table below with all applicable information.

Proposed Refinement to Flight Operations Window

Today’s Date Original MRD no-earlier than date Original MRD no-later than date Original MID no-earlier than date Original MID no-later than Current no-earlier than date (if different than MID) Current no-later than date (if different than MID) New proposed no-earlier than date New proposed no-later than date Total days of new proposed Flight Operations Window

Contractor Information (Requestor / Concurrer )

Name Company Signature Date

Government Representative Information (Requestor / Concurrer )

Name Company Signature Date