MGFS PWS.pdf

MICROGRAVITY FLIGHT SERVICES ATTACHMENT A

Version 1.0 dated 04-10-2021 Page 1 of 11

NASA-AFRC Flight Opportunities Program

Performance Work Statement (PWS) for

Microgravity Flight Services (MGFS)

Version 1.0

1. BACKGROUND

The Flight Opportunities Program (hereafter FO or “the Program”), part of NASA’s Space Technology Mission Directorate, has worked towards maturing flight readiness of new crosscutting technologies that advance or enable multiple future space missions. FO has provided opportunities to fly technology payloads on flight platforms that provide relevant environments required to test technologies, including but not limited to, reduced gravity, exposure to the space environment, or free fall in order to advance their technology readiness.

The Government intends to provide frequent flight opportunities for technology payloads on aircraft that are capable of flying reduced gravity flight conditions. Technology payloads, which are solicited under separate announcements issued by the Program, are not part of this solicitation.

Microgravity flights provide a unique "reduced gravity" or "micro-g" environment that allows, among other, for 0-g environments as well as simulated Lunar, Martian, and other gravity levels.

These are used for conducting research in areas such as fluid physics, combustion, material sciences, and life sciences, and engineering development (for the International Space Station and other space hardware programs); for education; and for astronaut flight crew training.

The typical operation involves one or more self-contained payloads that are installed on the platform and activated in flight during the microgravity periods by a human operator. Data is recorded, and experiments are often documented by means of photographs and/or video. Upon completion of each flight series, each payload is removed and can be refurbished and prepared for future flights. The payloads are usually observed and/or tended during flights by one or more human experimenters.

Reduced gravity parabolic trajectories and increased gravity constant-g maneuvers are normally within the design envelope of FAA-certificated transport aircraft; however, the repeated parabolic trajectories may constitute additional duty cycles that manufacturers did not consider in the design of their aircraft and engines.

2. OBJECTIVE

The Government intends to acquire space on commercial flights, including payload integration services, to fly technology payloads and human operators on flight platforms that provide reduced gravity required to test the technology in order to advance its readiness. The flights and other services solicited are for NASA internal use or for other Government Agencies (OGAs) only.

Version 1.0 dated 04-10-2021 Page 2 of 11

NASA intends to obtain microgravity flight services on a purely commercial basis. In such an operation, the provider will operate as a “civil aircraft” and bears full responsibility for airworthiness, flight safety, and mission assurance. These services will not require Public Use Aircraft Operation (PAO – ref. AC 00-1.1B) with commensurate NASA airworthiness approvals.

Under the non-PAO concept, NASA will perform an initial airworthiness review including a physical inspection of the proposed aircraft and detailed review of its maintenance records in accordance with its policy NPR 7900.3 Chapter 10 “Aircraft Operations Management - Commercial Aviation Services (CAS), Including UAS Operations” (http://go.usa.gov/sWt9). In addition, NASA will provide limited airworthiness oversight for payload design and payload integration for NASA payloads only. In situations where there will be a human tended experiment, there will be additional requirements for flight safety and mission assurance reviews and approvals.

The Contractor shall provide an aircraft capable of safely providing periods of zero and partial gravity to support the NASA research and development mission. The aircraft shall provide specialized services required by NASA experiments.

3. SCOPE

The Government intends to establish a Provider Pool (“Pool”) by awarding contracts to multiple vendors who are capable of providing flight opportunities to a variety of Program-sponsored payloads on various platforms. The Government prefers to contract for a single payload position (hereafter referred to as a “slot”) and require the vendor to fill the remaining manifest and set the schedule for flights. This does not preclude the possibility for the Government, at its discretion, to purchase an entire manifest, to require multiple payloads be flown together on a single platform, or for the Government to procure multiple payload slots on a single flight.

The contracts shall be for comprehensive services inclusive of flight and payload integration services. Each vendor may propose providing these comprehensive services through in-house or subcontracted means. Contracts shall include flying 1 or more payloads of varying dimensions, volumes and mass by means of multiple pre-planned parabolic flight trajectories with the primary objective of simulating different gravity conditions (1 g = 9.8 m/s^2 at MSL), including:

microgravity (nominally 0 g), Lunar (nominally 0.17 g), Martian (nominally 0.38 g), asteroid (nominally 0.03 g), or other (between 0.00 and 0.5 g) gravity conditions. The vendor will be expected to complete 10 or more parabolas during a single flight.

Each successful vendor will receive an indefinite delivery/indefinite quantity (IDIQ) contract, with the opportunity to propose on Task Orders issued by the Government to fly payloads. A Task Order is defined as a request from the Government to the vendor (hereafter the “Contractor”) to fulfill the requirements of a Manifest Requirements Document (MRD) for a given payload or payloads. The 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

Version 1.0 dated 04-10-2021 Page 3 of 11 to the Provider Pool as part of a Task Order solicitation. A Task Order solicitation may contain requirements for flying one or more payloads on one or more flights. It is anticipated that the Government will issue multiple Task Orders to the Contractors in the Provider Pool during the period of performance of the contract. Each Contractor awarded a Task Order shall supply comprehensive flight and payload integration services in accordance with the requirements identified in the Task Order. It is anticipated that Task Orders will be issued on a competitive basis in those cases where more than one vendor in the Pool is capable of providing the required services.

The Government intends to periodically provide opportunities for additional contractors and/or Qualified Vehicles to be added to the Provider Pool (“Ramp-On”). The requirements for Ramp- On shall be identical to those used for initially establishing the Provider Pool of Qualified Vehicles, as outlined below. The Government may also consider future expansion of the performance capabilities covered by this contract, by soliciting proposals from all qualified sources capable of meeting the requirements.

4. GENERAL REQUIREMENTS

4.1. Qualified Vehicles

Contractors shall utilize only those flight vehicles that were proposed in response to this solicitation and accepted by NASA under this contract as Qualified (Qualified Vehicles - “QVs”). NASA shall be the sole authority for determining vehicle qualification.

4.2. Operating Requirements

4.2.1. Independent Operations

The Contractor shall operate independently from the Government, except that payloads may be Government-owned or provided.

4.2.1.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.

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

4.2.1.3. The Contractor shall be solely responsible for obtaining appropriate permits, licenses, waivers, and/or flight approvals.

4.2.1.4. The Contractor shall be solely responsible for Ground and Flight Safety, Mission Assurance, and Environmental compliance in accordance with local, state, and Federal regulations.

Version 1.0 dated 04-10-2021 Page 5 of 11

4.2.5.2. The Contractor shall allow the Payload Provider access to payloads between flights for servicing and data recovery in a multi-flight campaign.

5. MISSION REQUIREMENTS

5.1. Payloads

Payloads may include gases, fluids, biologicals, mechanical devices, and may have hazardous and/or combustible materials, including cryogens. Some payloads will require overboard venting of gaseous materials. Payloads may have RF transmitters and Bluetooth or WiFi network connections. Size of payloads may vary considerably; some payloads may be as small as a 1U CubeSat (10x10x10cm), while others may be as large as the aircraft’s maximum allowable experiment bay dimensions (with allowance for sufficient room for safe installation, access and egress considerations). Payloads may be fully autonomous, semi-autonomous, or human-tended. Some payloads will have stationary cameras, strapped on cameras, or both. On occasion additional personnel may be flying with the payload, including a photographer, NASA FOP personnel and/or program guest.

All flight vehicles shall be capable of carrying a minimum payload mass per slot of 30 kg and accommodating a minimum combined payload volume equivalent to 6U CubeSat, in addition to any space required for human operators. 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.

5.2. Human-Tended Payloads

5.2.1. NASA expects some (if not most) payloads to have a human-tended requirement.

5.2.2. Human-tended payloads will require interaction with at least 1 personnel, including a payload specialist, crew member and/or principal investigator.

Occasionally, payloads shall require additional personnel to operate the payload, and the Contractor shall inform the Government how many personnel can be accommodated by the QV(s).

5.2.3. Contractor shall ensure that for those portions of the flight considered as transit to/from the reduced gravity profile, the level of cabin safety for all personnel flying to support and/or operate payloads shall be equivalent to that of commercial carriers.

5.3. Power Requirements

Payloads may require power to be supplied from the aircraft. Power requirements will vary with payload, but include 28VDC, 110VAC 60 Hz single phase, 110VAC 400 Hz three phase, and/or 230VAC single phase. Provider shall include circuit protection to each individual payload.

Version 1.0 dated 04-10-2021 Page 6 of 11

5.4. Gravity Level Requirements

Reduced gravity requirements will vary greatly for any given mission, and may include any of the reduced gravity maneuvers listed below. The proposed reduced gravity profile performance of the flight vehicle will be evaluated during the Task Order evaluation process based on the requirements in the Mission Requirements Document (MRD) for each specific payload. The Government may include additional profiles within the general scope of this effort at a future date by use of the Technology Expansion Provision. Profiles are described from the perspective of the payload, not the flight vehicle. These profiles represent minimum requirements for payloads. Actual requirements issued in an MRD may vary from those specified here.

The aircraft shall be capable of providing various gravity levels and durations for each by means of pre-planned parabolic flight trajectories for simulating different stable and sustained gravity conditions (1 g = 9.8 m/s^2 at MSL) including:

• 10 seconds (30 seconds or longer duration preferred) of microgravity (nominally 0 g)

• 10 seconds (longer duration preferred) of Lunar gravity (nominally 0.17 g)

• 10 seconds (longer duration preferred) of Martian (nominally 0.38 g)

• 10 seconds (longer duration preferred) of Asteroid (nominally 0.03 g)

• 10 seconds (longer duration preferred) of Other gravity levels (between 0.00 and

0.5 g)

The aircraft shall be capable of providing 2 or more maneuver types (Microgravity, Lunar, Martian, etc.) per flight, which include parabolic trajectories. For all maneuvers, the vendor shall attain and maintain high levels of parabola accuracy and stability (preferably within +/-0.02 g), as well as minimum longitudinal and lateral gravitational deviations (preferably not to exceed +/- 0.01 g).

NASA microgravity profile requirements will vary for any given group of payloads and/or flight participants. In some cases, the objective may be to maximize the duration of low gravity exposure with less emphasis on accuracy and stability. This would be most likely with a non-critical payload where the objective is to give the flight participant a micro-gravity experience. In other cases, the accuracy and stability of the gravity level may be critical and duration less important. As a result, for each flight the vendor shall group multiple compatible payloads with similar and non-conflicting parabola requirements and g-limits (e.g.: compatible G-level requirements, parabola durations, parabola entry and completion g excursion limits etc.) in order to maximize microgravity experimental time while simultaneously minimizing adverse effects on payloads due to parabola entry and completion maneuvers.

5.5. Free-Floating/Non-Free Floating Payloads

There may be some instances in which a payload(s) may require a free-floating configuration during the reduced gravity portions of the flight(s), in which cases the vendor will coordinate with the payload provider for conducting a feasibility & safety evaluation. In these cases, the Contractor shall provide for payload stowage or restraint during take-off, transit & landing.

Version 1.0 dated 04-10-2021 Page 7 of 11

5.6. Data Collection

The Contractor shall allow payload providers to collect, publish and/or distribute any data that was collected during the flight as part of the payload experiment. Additionally, the Contractor shall provide a Flight Data Report at the conclusion of each flight campaign (ref. PWS Section 8.3).

6. OTHER REQUIREMENTS

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

6.1. Review and Documents

6.1.1. Payload User Guide (PUG)

For each QV the Contractor shall provide to the Government a Payload User Guide (PUG), to be made available to the Payload Provider. The PUG is the Contractor-provided documentation that defines the payload interfaces of the QV, including, but not limited to, the mechanical, electrical, communication, information/data, and environmental interface requirements.

6.1.2. Mission Implementation Document (MID)

The Contractor shall develop a Mission Implementation Document (MID) in response to Task Order solicitations to which the Contractor chooses to respond.

The MID is defined as the document that establishes the agreement between the Contractor and the Government, and documents how the MRD will be implemented, including deviations from the MRD.

6.1.3. Payload Acceptance and Readiness Review (PRR)

The Contractor shall be responsible for accepting or refusing the payloads for integration and flight. The Payload Provider will conduct a Payload Readiness Review (PRR) with the Contractor prior to delivery of the payload. The Contractor will allow the Government to participate in the approval process for payloads. The Contractor shall work with the payload provider to ensure payloads meet all flight provider requirements (including safety) and can also refuse to accept any payloads that do not meet the requirements of the MID, or do not meet the safety requirements included in the Contractor’s Payload User’s Guide (PUG).

6.2. Flight Service Requirements

The Contractor shall provide flight service on a vehicle that meets the requirements of the MID.

6.2.1. Flight Approvals

The Contractor shall obtain and provide to the Government upon request written evidence of all required flight approvals, including (but not limited to) permits, Version 1.0 dated 04-10-2021 Page 8 of 11 licenses, or waivers for operation, as applicable, from the Federal Aviation Administration (FAA) or other governing authority for the flight activity.

6.2.2. Flight Operations Responsibility

The Contractor shall assume total responsibility for all flight operations, which includes provision of the flight range, operational facilities, and all required personnel. This also includes responsibility for mission security, airworthiness, flight safety and mission assurance, environmental compliance, range safety, and flight and ground personnel safety and health.

6.2.3. Commercial Aviation Services

The Contractor shall conduct operations in accordance with the current version of policy NPR 7900.3 Chapter 10 “Aircraft Operations Management - Commercial Aviation Services (CAS), Including UAS Operations” (http://go.usa.gov/sWt9), which will include among other, airworthiness inspections, safety & surveillance inspections, safety & mission assurance reviews, and thorough reviews of aircraft maintenance records. The contractor shall provide, maintain, and make available complete records during the period of performance, including updates related to modifications or repairs to the aircraft and associated FAA approvals & documentation following the initial inspection. Additionally, the Government shall conduct periodic surveillance of the QV and related records. The Government has the right to inspect all services, to the extent practicable at all times and places during the period of performance. Additionally, the Contractor shall allow insight on their airworthiness review & approval process for the aircraft. In the case that the Contractor does not satisfy any of the requirements included in NPR 7900.3, the Government shall have the right to discontinue the execution of any Task(s) issued.

6.3. Payload Integration

The Contractor shall provide payload integration service on the flight vehicle.

6.3.1. The Contractor shall integrate the payload into the flight vehicle system(s).

6.3.2. The Contractor shall perform a payload operational readiness and payload safety review.

6.3.3. The Contractor shall ensure that the payload meets as required the interface specifications of the Payload User’s Guide.

6.3.4. 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 parabolic flight. Facilities and resources shall include but are not limited to electrical power, adequate lighting, payload servicing space, sample processing space, and internet connectivity.

Version 1.0 dated 04-10-2021 Page 9 of 11

6.3.5. The Contractor shall manage the interface control document (ICD) between the payload and the flight vehicle. This document shall be provided to the Government upon request.

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

7. SPECIAL PROJECTS

7.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.

7.2. Non-Standard Services

The Contractor shall perform necessary modifications or additions to payload slots to accommodate unique payload requirements, within the general capabilities of the QV but not within the definition of a Standard Flight Payload Slot. There are some Non-Standard Services (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. The requirements for NSS shall be further delineated by the MRD/MID process.

8. 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 7.1).

DRD No. Title of DRD No. Pages DRD-1 Payload User’s Guide (PUG) 1 DRD-2 Mission Implementation Document (MID) 1 DRD-3 Flight Data Report (FDR) 1

8.1. Payload User’s Guide (PUG)

Contractor shall provide a Payload User’s Guide for each Qualified Vehicle. The PUG is the documentation that defines the payload interfaces of the QV, including, but not limited to, mechanical, electrical, communication, information/data, and environmental interfaces.

8.2. Mission Implementation Document (MID)

Contractor shall provide a Mission Implementation Document (MID) for each Task Order. The MID is the document that establishes the agreement between the Contractor

Version 1.0 dated 04-10-2021 Page 10 of 11 and the Government, and documents how the MRD will be implemented, including any proposed deviations.

8.3. Flight Data Report

Contractor shall provide a Flight Data Report for each flight performed under this contract within 7 days after the conclusion of each flight campaign. The Flight Data Report is the summary of the flight operation as related to the requirements of the MID and the Task Order. The Flight Data Report includes formatted data item deliverables as specified in the Task Order.

9. DEFINITIONS

Above Ground Level or “AGL” is defined as a measured distance above nominal ground level for the local area under consideration.

Contractor is defined as a business entity who has been awarded a contract under this solicitation and provides both flight and payload integration services.

Flight is defined as any contracted flight 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. The Flight Data Report includes formatted data item deliverables as specified in the Task Order.

Gravity or “g” is nominally 9.8 m/sec^2 at 0 MSL

Human-tended refers to payloads that require human interaction during the flight.

Manifest Requirements Document (MRD) is defined as the document that establishes the payload operational requirements, mission performance requirements, data delivery requirements, payload access requirements, payload hazard analysis & evaluation 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 Sea Level or “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 document that establishes the agreement between the Contractor and the Government, and documents how the MRD has been implemented including deviations.

Version 1.0 dated 04-10-2021 Page 11 of 11

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 NASA mission purpose other than the demonstration of various technologies in relevant environments.

Payload Integration is defined as integration of a payload to the Flight Vehicle, while ensuring that the interfaces to other payloads and to the Flight Vehicle 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, including, but not limited to, mechanical, electrical, communication, information/data, and environmental interfaces. 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 the vehicle that was proposed in response to this solicitation and accepted by the Government as Qualified to provide services under this contract.

Slot is defined as a single payload space or seat. Vehicles may have one or more 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.

Task Order is defined as a request from the Government to the Contractor(s) to fulfill the requirements of the MID for a given payload or payloads.

Vehicle is any means used to fly a payload under this contract.

Vendor and Contractor are synonymous.