ATT_A_CLPS_SOW_Final_Draft_9.6.18.pdf

PDF 207 KB Posted

Attached to
Commercial Lunar Payload Services Federal contract opportunity
Solicitation number
80HQTR18R0011R
Issued by
National Aeronautics and Space Administration Headquarters

About this file

CLPS RFP Attachment A - Statement of Work

View the file

Other files for this federal contract opportunity

Other files attached to Commercial Lunar Payload Services, newest first.
File Type Posted
CLPS__JOFOC.pdf PDF
CLPS_QA_09262018_Final.pdf PDF
CLPS_Amend_1.pdf PDF
Final_CLPS_Cover_Letter_RFP_9.6.18.pdf PDF
Final_CLPS_1449.pdf PDF
ATT_E_IT_Security_Management_Plan_9.6.18.pdf PDF
Final_CLPS_RFP_9.6.18.pdf PDF
ENC_1_CLPS_QASP_Fixed_Price_Contract_(002)_9.6.18.pdf PDF
ATT_B_Subcontracing_Plan_9.6.18.pdf PDF
ATT_D_IT_Security_Applicable_Documents_List_9.6.18.pdf PDF
ATT_C_OCI_Plan_9.6.18.pdf PDF
Show all 11

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

July 2018

ATTACHMENT A

Commercial Lunar Payload Services

STATEMENT OF WORK

July 9, 2018

1.0 Introduction

1.1 Scope

2.0 Use of IDIQ Task Orders

3.0 Destinations and Scenarios

4.0 Payload Accommodation Services

4.1 Mission Integration

4.2 Analytical Integration

4.3 Physical Integration

4.3.1 Launch Processing

4.3.2 Vehicle Integration

4.4 Transport and Operation

4.4.1 Attached Landed NASA Payloads

4.4.2 Attached Non-landed NASA Payloads

4.4.3 Deployed NASA Payloads

4.4.4 NASA Payload Termination

4.5 Utilities Resources

4.6 Environmental Considerations

4.7 Mission Data Provision

5.0 Purchase of Payload Data and Functions

6.0 Other Mission Services

7.0 Non Mission Services

8.0 Service Readiness

9.0 Capability Updates through Contract effective ordering period

1.0 Introduction

1.1 Scope

The Contractor shall provide all resources and functions to perform the Commercial

Lunar Payload Services identified within this Statement of Work for the National

Aeronautics and Space Administration. The Contractor shall select launch opportunities, determine the overall Mission Architecture, and provide the end-to-end service including operations associated with the Launch Vehicle, Launch Site, Spacecraft, Lander, Mission Design and Analysis, Ground Systems, and Payload

Support. The Contractor shall be responsible for all taxes, licenses, permits, and approvals necessary to perform the mission, including following Export Control and

ITAR regulations when applicable. Payload Support includes: physical and analytical integration of NASA-provided payloads, launch and transport of NASA-provided payloads to specified lunar-related destinations, provision of utility resources to the

NASA-provided payloads, and other related mutually agreed upon services such as the sale of non-NASA payload data to NASA. NASA may provide facilities, functions, equipment, and technologies, as requested by and negotiated with the Contractor, in furtherance of the Commercial Lunar Payload Services. The procedures and timing for handover of payload service responsibilities, or for concurrent coordinated operations, will be negotiated with the Contractor on a case-by-case basis. The Contractor shall provide resolution of critical problem areas to minimize or eliminate schedule impacts.

Prior to execution of lunar payload missions and services under this contract, the

Contractor shall deliver information necessary to enable NASA payload integration planning and complete a Service Readiness review to demonstrate the Contractor’s ability to provide end-to-end payload services.

2.0 Use of IDIQ Task Orders

This is an Indefinite Delivery, Indefinite Quantity (IDIQ) type contract. This SOW defines in general terms the scope of activities to be purchased and specifications for the various services available under this contract. Task orders will be negotiated and issued for any services purchased, in accordance with the Task Ordering Clause of this contract. Task orders will reference this SOW for services to be purchased, with additional details, delivery dates, NASA payload needs, payment milestones and final negotiated prices to be included separately in each task order. Due to the anticipated varied nature of NASA payloads, and myriad scenarios resulting from Contractor’s

Mission Architecture and payload opportunities, NASA Payload requirements will be provided in, and applicable to, individual Task Orders.

3.0 Destinations and Scenarios

This contract is for payload services to lunar surface destinations. Other destinations may include lunar orbital and flyby space, lunar Lagrangian points and other destinations that may result from the Contractor’s Mission Architecture. NASA payloads and/or obtained services may utilize any location or feature that the Contractor makes available including on:

a) Launching Vehicle stages

b) Spacecraft

c) Landers

d) Rovers or other mobility systems

e) Sample or payload returns

f) Supporting systems

Many NASA payload/obtained service scenarios may result, including: intact landing on the Moon, operation on the lunar surface, impactor delivery, launch vehicle rideshare, lunar orbit insertion and operations and lunar flyby operations.

4.0 Payload Accommodation Services

Payload accommodation services are those services described below. These payload accommodation services are applicable to NASA payloads on the Contractor’s spacecraft mission to the Moon.

4.1 Mission Integration

The Contractor shall perform mission integration for the NASA payload into the

Contractor’s Mission Architecture. This includes: providing Contractor point of contact for each payload, providing Contractor Vehicle-to-Payload interface definitions, providing

Contractor operational details pertinent to the NASA Payload, holding meetings with

NASA Payload representatives, identifying when NASA test support is required, planning and communicating Vehicle-to-Payload integration activities and milestones, performing analyses and assessments of Contractor’s systems with NASA Payloads to confirm compatibility.

4.2 Analytical Integration

The Contractor shall perform analysis of Contractor’s Mission Architecture and its systems to confirm that the requirements specified in the Task Order are satisfied for the

NASA Payload. This includes assessing and satisfying agreed-upon: Contractor Vehicle resources provided to NASA Payload, resulting NASA Payload environments, non-interference of non-NASA Payloads with NASA Payloads, and NASA Payload operational timelines within overall Contractor Mission operations. NASA will provide relevant analytical models and data for its payloads when needed as part of the task execution process.

4.3 Physical Integration

4.3.1 Launch Processing

The Contractor shall receive, handle, and process the NASA payload as specified in the

Task Order. This includes all ground processing scenarios such as: standard installation, non-standard installation (e.g., installed at launch pad), and launch scrub turnaround.

Processing could include receipt of NASA payload, cleaning of NASA payload, checkout of NASA payload, fueling of NASA payload, and other launch preparation processes for a NASA payload.

4.3.2 Vehicle Integration

The Contractor shall integrate the NASA payload with the Contractor’s vehicle(s) as specified in the Task Order. This includes: physical installation, establishment and integration of interfacing resources (e.g., electrical, transmission of vehicle commands and data, cooling, cleanliness), performing post-installation pre-flight checkouts as well as any post integration access requirements .

4.4 Transport and Operation

The Contractor shall launch, transport, land, deploy, and possibly operate the NASA

Payload according to the Task Order. Responsibilities for Orbital Debris and Planetary

Protection, as applicable, resulting from NASA Payload content and operations will be specified in the Task Order. The Contractor shall be accountable for the NASA payload from the time of NASA delivery through ignition. After ignition, the Contractor will be responsible for operations of the NASA payload through the end of mission operations

(e.g., successful mission completion, launch failure, or loss of payload), or as designated in each task order. The Contractor shall also be responsible for ensuring application of

Export Control/ITAR regulations when in possession of NASA Payloads.

4.4.1 Attached Landed NASA Payloads

Contractor responsibilities for landed NASA payloads shall end after the Contractor’s system ceases transport operations, unless NASA payload is dependent upon

Contractor’s system (e.g., communications, data relay) or as otherwise specified in the

Task Order. The NASA payload may independently operate after the Contractor’s system ceases operations. In the event that Contractor decides to terminate Contactor’s system, Contractor will inform NASA of said decision and will negotiate with NASA system-termination-scenarios favorable to the continued operations of NASA payload.

Should NASA decide to terminate NASA payload operations in tandem with Contractor’s system, the Contractor will be relieved of this obligation.

4.4.2 Attached Non-landed NASA Payloads

Contractor responsibilities for non-landed NASA payloads shall end upon the permanent cessation of the Contractor’s system operations, unless otherwise specified in the Task

Order. Specifics such as mission duration, payload services, etc. will be defined in the

Task order.

4.4.3 Deployed NASA Payloads

Contractor responsibilities for deployed NASA payloads shall end upon separation from the Contractor’s systems unless NASA payload is dependent upon Contractor’s system after deployment (e.g., communications, data relay) as specified in the Task Order.

Contractor’s system(s) shall issue the deploy command to deployment interface/mechanism as specified in the Task Order. Deployment interface and/or use of a NASA or Contractor furnished deployment mechanism shall be as specified in the

Task Order.

4.4.3.1 Deployed Non-NASA Payloads

The Contractor shall inform NASA of any Contractor or other non-NASA deployed payloads sharing a mission with a NASA payload, and manage the deployment of these such that they do not interfere with NASA payloads.

4.4.4 NASA Payload Termination

When defined in the Task Order, the Contractor shall terminate NASA Payload operations. The Contractor shall have no Contract responsibilities after NASA Payload termination with exception of providing previously stored data that may still reside on

Contractor’s systems.

4.5 Utilities Resources

The Contractor’s systems, shall provide utility resources to the NASA Payloads as specified in the Task Order. The Contractor shall specify and provide definitions for which utility resources are available from Contractor’s systems on a specific mission.

Typical utilities resources may include, but are not limited to: structural attachment, geometrical volume, mass accommodation, center-of-gravity constraints, electrical power/characteristics, thermal control, telemetry, commanding, physical access, and operational constraints of these.

4.6 Environmental Considerations

The Contractor shall specify and provide definitions for environmental controls or passive protections available from Contractor’s systems on a specific mission. These can include, but are not limited to pressure, thermal, aerothermal, aerodynamic, plasma charging, radiation, magnetic field, lighting, and cleanliness. Payloads will be exposed to a variety of environment conditions that may affect the payload’s ability to operate.

Some of those environmental conditions are inherent to the physical location (e.g.

radiation), some may be a byproduct of the transport vehicles (e.g. vibrations or thermal load). Each Contractor may offer specific mitigations in their lander design to environmental conditions. NASA will be interested in understanding these mitigations

/controls and the Contractor is expected to document them in the User’s Guide. There may also be specific mitigations or controls enabled via mission design that would be elaborated as part of the mission planning process for a specific task order. Specific

NASA payload requirements for environmental control will also be elaborated in the task orders.

4.7 Mission Data Provision

Mission data, including engineering data relevant to NASA payloads, timing of key events, mission trajectory and location information shall be provided to the NASA payload team as documented in the Task Order.

NASA Payload telemetry provided to the Contractor’s spacecraft, including data relayed back to Earth will be delivered to NASA as specified in the Task Order.

5.0 Purchase of Payload Data and Functions

For Contractor or other non-NASA payloads, the Contractor may make available to

NASA, data and/or functions produced by the payload. These data and/or function purchases, and any 3rd party agreements, will be specified in the Task Order.

6.0 Other Mission Services

Other Mission Services, from the Contractor or NASA, that may become available during the Commercial Lunar Payload Services term and within the Commercial Lunar Payload

Services scope, may be offered by the Contractor or NASA. Other Mission Services will be proposed, negotiated and defined in task orders.

Examples include:

The use of radioisotope heater units (RHUs) within NASA-provided payloads

Sample handling and/or return services

Payload services through the lunar night

Precision landing

Synergistic opportunities between NASA payloads and non-NASA payloads; such as a NASA payload provides data to non-NASA payload

7.0 Non Mission Services

NASA may issue task orders that require special services. Examples include:

a) Advance planning and feasibility studies in support of future contemplated missions of projected or existing payloads;

b) Development, fabrication, and test of hardware/software to support planning studies, special tests, and/or flight equipment for NASA Payloads or obtained services

8.0 Service Readiness

The Contractor shall provide evidence of readiness to proceed with performing an initial landed mission under this contract. As primary evidence, each vendor will be asked to prepare a User’s Guide, including documentation of the Contractor’s payload interface requirements and capabilities.

Over the life of the contract, the complexity, size, and risk tolerance for NASA payloads will change. To maximize likelihood of mission success, NASA may require evidence of readiness via the task order process. Evidence such as contractor documentation, formal briefings, designs, processes, facilities, and/or implementation materials may all be requested as part of a readiness assessment.

9.0 Capability Updates through Contract effective ordering period

Over the life of the contract, the Contractors shall provide projections of future missions, potential payload opportunities, and any changes to mission capability.

THIS PAGE INTENTIONALLY LEFT BLANK

File details come from the government source that posted it.