Attachment 1 - Performance Work Statement.pdf

NASA-AFRC Flight Opportunities Program

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

Version 0.22

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 flight platforms that provide relevant environments required to test technologies (including, but not limited to, reduced gravity, exposure to the space environment, 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).

The Government intends to provide flight opportunities for furthering autonomous/non-autonomous technologies and procedures operating in high altitude, reduced gravity, or other relevant environments. This includes flying technology payloads and NASA spaceflight participants (SFP) on vehicles that are capable of flying to various altitudes and flight conditions. Solicitation of the technology payloads themselves is conducted under separate announcements issued by the Program and is not part of this solicitation.

2. Objective

The Government intends to acquire space on commercial flights for technology payloads (“by the slot”) along with the associated payload integration services with the objective of flying these payloads aboard platforms 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 NASA SFP (“by the seat”) to fly as passengers aboard those platforms capable of supporting human flight. The flights and other services solicited are for NASA internal use or for other Government Agencies (OGAs) only.

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 (including, but not limited to, high-altitude balloons, suborbital rocket-powered vehicles, and orbital vehicles capable of hosting payloads). The Government prefers to contract for one or more single payload positions or SFP (hereafter referred to as a “slot” or “seat”, respectively) and with the vendor to filling the remaining manifest with other customers. This does not preclude the possibility for the Government, at its discretion, to purchase an entire manifest, to require multiple payloads and/or seats be flown together on a single platform, and/or for the Government to procure multiple payload slots and/or seats on a single flight.

The contracts will be for comprehensive services inclusive of flight, payload integration services, and in some instances, human accommodations. Each vendor may propose providing these comprehensive services through in-house or subcontracted means. 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 NASA SFP. The Manifest Requirements Document (MRD) is defined as the document that establishes the payload operational requirements, requirements for a potential SFP(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. 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 will 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 (“flight profiles”) covered by this contract, by soliciting proposals from all qualified sources capable of meeting the requirements in the expanded flight profiles.

4. General Requirements

4.1. Qualified Vehicles and Qualified Vehicle Families

Contractors shall utilize only those flight vehicles or family of flight vehicles that were proposed in response to this solicitation and 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 flight vehicles (closely 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. All QV and QVF must be owned and operated by a U.S. commercial entity.

4.1.1. Suborbital Rockets

Suborbital rockets shall include both crewed (i.e., vehicles with crew and/or SFP) 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 be in the process of being licensed to operate commercial flights for compensation or hire in the U.S. at the time of proposal submission. 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 be in the process of being licensed to operate commercial flights for compensation or hire in the U.S. at the time of proposal submission or must otherwise hold the appropriate waiver or written authorization from the FAA in accordance with 14 CFR § 101 Subpart C.

4.1.2 Rocket-Powered Lander Vehicles

Rocket-powered lander vehicles shall include those vehicles that are 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; however, there is no minimum altitude required for a rocket-powered lander vehicle to be eligible under this solicitation. 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.

4.1.3 High-Altitude Balloons

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

Crewed high-altitude balloons must be licensed to operate commercial flights for compensation or hire in the U.S. or be in the process of being licensed to operate commercial flights for compensation or hire in the U.S. at the time of proposal submission. 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.

4.1.4 Orbital Platforms

Orbital platforms hosting payloads must be able to provide power and communications to the payload, 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. The orbital platform hosting the payload shall have plans 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.

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, and SFP, if any, will be authorized by NASA.

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 shall be solely responsible for obtaining appropriate permits, licenses, waivers, and/or flight approvals.

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.

5. The Contractor shall provide all QV systems engineering, payload integration, and any other required services.

6. Once a task order has been accepted by the Contractor, the Contractor shall be responsible for timely communications of detailed information about the flight and other services to the Government, Payload Provider, and seat requestor, including, but not limited to, changes in vehicle readiness and other changes that affect the flight schedule.

4.2.2 Government Observers

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

4.2.3 Commercial Operations

The Contractor shall be capable of providing payload slots and/or SFP seats on QVs with commercial flight operations, offered to the general public for pay.

4.3 Payload Requirements

4.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. 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. Notwithstanding Paragraph 1 above, payloads have value to the Payload Providers. 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.

4.3.2 Accessibility

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

1. For suborbital vehicles, Payload Providers shall be permitted access to their payloads both before and after flights as needed and in coordination with the Contractor. 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 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 and requests for waivers will be determined on a case-by-case basis.

3. The Contractor shall allow the Payload Provider access to payloads between flights for servicing and data recovery in a multi-flight campaign. Detailed requirements for access will be specified as part of the MRD/MID process.

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

4.4 NASA Spaceflight Participant (SFP) Capability Requirements for Suborbital Profiles

4.4.1 Roles

The Government envisions capabilities for flying SFP on suborbital flight profiles only (ref. Sect. 5). During these flights, SFP(s) would assume one or more of the following roles:

1. Payload Operator: tending a technology payload

2. Research Specialist: conducting procedural or operational tests or observations that may or may not include hand-held or on-person tools/equipment. This role would not interact with a technology payload.

4.4.2 Flightworthiness & Flight Safety Approvals for Operations with SFP

If the Contractor can support NASA SFP, the Contractor shall be responsible for obtaining all corresponding flight/mission approvals from NASA and upon request shall provide written evidence and documentation related to those approvals.

4.4.3 Accessibility

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

1. NASA SFP shall be permitted access to their seat locations both before and after a flight as needed and in coordination with the Contractor. Detailed requirements for access will be specified as part

2. The Contractor shall allow the NASA SFP access to their seat(s) between flights for pre-flight preparations during a multi-flight campaign. Detailed requirements for access will be specified as part

4.4.4 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 SFP. Similarly, in the event that circumstances require any Government SFP to be de-manifested from a flight, the Contractor shall directly communicate and coordinate with the Government prior to executing any manifest changes.

4.5 Flight Schedule

The MRD/MID process will be used to determine the flight schedule. Unless otherwise specified in the Task Order, the contractor will identify a nominal window for the flight, as outlined in the Terms and Conditions of the Contract. During execution of the Task Order, the Contractor will further specify other elements of flight schedule per these terms. Postponements and launch delays impacting the flight schedule, as well as associated fees and consideration, will also be handled per the terms of the Contract.

4.6 Mishap-Related Requirements

4.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, NASA property, or NASA equipment that could have resulted in a mishap

2. Exposures involving NASA personnel, NASA property, or NASA equipment, which could result in fatality; lost-time occupational injury; or occupational disease

3. Mishaps involving NASA personnel, NASA property, or NASA equipment, which result in serious injury; fatality; lost-time occupational injury;

occupational disease; any environmental damage; any mission failure; or substantial damage to or loss of equipment or property damage of at least $50,000

4.6.2 The Contractor shall conduct an investigation for any event that meets the requirements of paragraph 4.5.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.

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

4.7 ITAR/Export Control Restrictions and Payload/SFP Conflicts

There may be instances where the government will need to fly payload(s) and/or SFP 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 SFP. Unless otherwise specified in the Task Order, the Contractor is responsible for obtaining any required export licenses. Under all circumstances the Contractor required to comply with the ITAR/Export Control process and provide any required data in timely manner to support export licensing.

5. Flight Profile Requirements

Flight profile requirements will vary greatly for any given payload. The proposed profile performance of the flight 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. The Government may include additional profiles within the general scope of this effort at a future date by use of the Technology Expansion Provision.

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 flight vehicles 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 SFP when needed (ref. PWS Sect. 4.4).

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

5.1 Profile 1 (P1): Reduced gravity with space environment

Payload is typically an experiment requiring two (2) or more minutes 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 total gravitational vector of less than +/- 0.005g (RMS) under stable gravitational conditions in all axes for at least two (2) minutes. Some payloads may also require the simultaneous exposure of the payload to near-vacuum and low temperature. This is typically accomplished by use of a sounding rocket or spacecraft.

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.

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

Under this profile, platforms 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 qualified 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, for testing experimental parachutes or similar atmospheric descent systems. Other platforms could include untethered balloons or untethered airships with guided trajectory capabilities and controlled landings. The aforementioned platforms 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 5.2.1 or 5.2.2 below:

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

5.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 with a float time of 7 days or greater along a pre-planned flight trajectory, followed by a descent to 0 AGL.

5.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 rapid 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 at apogee. In some cases, it may be desired to have a landing sufficient to recover the payload intact, which may entail either a soft landing or a parachute recovery.

5.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 up to 1 km. Some applications may require allowing the payload to actively control portions of the flight profile. This is typically accomplished by use of a spacecraft or a vertical flight testbed.

5.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 control inputs 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, platforms may have different ascent and descent locations as part of a single flight. This 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.

5.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. Orbital platforms hosting payloads are required to have plans for safe end-of-mission disposal at the end of the vehicle operational lifetime, such as defined in NASA STD-8719.14 and in accordance with applicable U.S. laws or regulations.

6. Other Requirements

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

6.1 Data Collection

The Contractor shall allow Payload Providers and/or SFP 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 8.3).

6.2 Reviews and Documents

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

6.2.1 Payload User Guide (PUG)

For each QV or QV family (as necessary), the Contractor shall provide the Government a Payload User Guide (PUG; see definition in PWS Section 9) on an annual basis and upon any updates/revisions. The most updated PUG shall also be made 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 flight vehicle profile capabilities, overview of the vehicle, 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.

6.2.2 Mission Implementation Document (MID)

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

6.2.3 Payload Acceptance and 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, or do not meet the safety requirements included in the Contractor’s Payload User’s Guide (PUG). Upon written request, the Contractor shall allow the Government to participate in the approval process for payloads and will provide any associated documentation.

6.2.4 Flight Readiness Review (FRR) for Flight with Space Flight Participants (SFP)

The Contractor shall conduct a Flight Readiness Review (FRR) no less than L-1 week prior to the scheduled launch date. The Contractor shall use their internal process to examine data from tests, demonstrations, analyses, and audits, as appropriate, to demonstrate the system's readiness for a safe and successful flight and for subsequent flight operations. The FRR also ensures that all flight and ground hardware, software, personnel, and procedures are operationally ready. Upon written request, the Contractor shall allow the Government to participate in the approval process for the flight and will provide any associated documentation.

6.3 Flight Service Requirements

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

MID.

6.3.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, licenses, export licenses, or waivers for operation, as applicable, from the Federal Aviation Administration (FAA) or other appropriate governing authority for the flight activity.

6.3.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 (see Sec 4.4 for specific requirements for operations involving SFP), flight safety and mission assurance, environmental compliance, range safety, and flight and ground personnel safety and health. Upon written request, the Contractor shall allow the Government to observe the Flight Readiness Review or equivalent activity on a non-interference basis (see Section

6.2.4 for additional specific requirements for SFPs). The Contractor will also provide any associated documentation upon written request.

6.4 Payload Integration

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

6.4.1 The Contractor shall integrate the payload into the flight vehicle system(s) and ensure full functionality.

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

6.4.2 The Contractor shall manage an interface control document (ICD) between the payload and the flight vehicle 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. This document shall be provided to the Government upon request.

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

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

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

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 (NSS):

The Contractor shall perform necessary modifications or additions to payload slots, interfaces, or seats to accommodate unique payload or SFP requirements, within the general capabilities of the QV but not within the definition of a Standard Flight Payload Slot. 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. 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).

8.1 Payload User’s Guide (PUG)

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

8.2 Mission Implementation Document (MID)

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

8.3 Flight Data Report

Contractor shall provide a Flight Data Report (see Section 9) for each flight performed under this contract within 7 days after the conclusion of each flight.

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. This report shall contain 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 shall also be included.

Interface Control Document (ICD) shall define 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.

Launch Vehicle (LV or Vehicle) is any means used to fly a payload under this contract, regardless of mode of propulsion (e.g., rocket, spacecraft, balloon).

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 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 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 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 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 launch vehicle that was proposed in response to this solicitation and accepted by the Government as Qualified to provide services under this contract.

QV Family (or “QVF”) is a group of closely related flight vehicles (closely similar in characteristics with different performance or capacities) that fly similar flight profile(s). The Government shall 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 available for purchase.

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

Spaceflight Participant is an individual, who is not crew, carried aboard a launch vehicle or reentry vehicle.

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 and Platform are synonymous.