Enclosure DD - Representative Task Orders (RTOs).pdf

ENCLOSURE DD

REPRESENTATIVE TASK ORDER(S) (RTOs)

RFP 80GSFC24R0027

CONTRACT - TBD

FDSS-IV (RTO 1) Statement of Work

Task: Flight Dynamics Facility (FDF) Mission Development and Operations

Task Order: 001

Task Modification: 0

I. Summary of Work

NASA/Goddard Space Flight Center in collaboration with NOAA and Spacegrass University is designing the EarthRock Mission to be launched from the new NASA-owned Clutch Launch Vehicle (CLV) on September 5, 2025. EarthRock will feature a “hub” spacecraft in Low Earth Orbit (LEO) and eight cubesats deployed from it. Together, the fleet will measure fluctuations in the Earth’s atmosphere and how they contribute to catastrophic weather events. The eight cubesats, called “Pebbles” 1-8, each contain gravimeters to collect multipoint observations, with the hub satellite communicating with deployed ground assets.

The Pebbles will utilize Two Line Elements (TLEs) for navigation while the hub spacecraft will utilize S-band for ground-based tracking and commanding.

The scope of this task includes working with the Task Monitor (TM) to assess the mission and launch vehicle requirements in order to: 1) develop the FDF ground system required, 2) analyze and document mission readiness, and 3) execute the flight dynamics operations support for the CLV as well as launch and early orbit phase (LEOP) operations for the EarthRock Mission.

II. Period of Performance

The period during which the work for this task shall be performed is between November 1, 2024 and October 31, 2025.

III. Task Description

The focus of this task is working with the Task Monitor in identifying the navigation needs of the EarthRock mission and the proper FDF Ground System Development and Operations Concept to support EarthRock and the CLV through LEOP, and continued science mission operations. The task contains the following work items:

• Assess the use of TLEs for meeting the navigation requirements of the Pebbles cubesats and develop a Navigation and Communications Requirements Plan for meeting these requirements if TLEs are insufficient.

• Develop requirements and procedures pertaining to tracking and telemetry data processing as needed for EarthRock and the CLV, as well as acquisition data transmission also documented in the Navigation and Communication Requirements Plan.

• Assess the ground system (hardware, software, interfaces, etc.) needed to support the CLV’s maiden flight to ensure all products, operational configurations, agreements and interfaces are within the capabilities of the FDF Operations Facility.

Milestone Due Date

Description

Operations Readiness Review

August 4-6, 2025

Launch September 5, 2025

V. Management Approach

The contractor is free to propose a skill mix and staffing level (i.e., a phasing plan) based on their understanding of the work involved. The contractor shall justify this phasing plan by addressing the following points:

1. Why the phasing plan offers the best balance between lowering risk, increasing quality, and controlling cost and schedule

2. The degree to which the phasing plan offers flexibility should redirection be required (including depth of contractor bench strength)

In addition, the contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the compliance of the TM.

VI. Performance Metrics

The work performed for this task will be evaluated by the Technical Monitor based on the technical merit. Specific performance metrics for this task are: 1) timely delivery of all deliverables (including clearly supported and negotiated rationales where delivery is delayed), 2) technical quality based on appropriate depth and scope of analysis, rigor of methods, and quality of documented results, and 3) open and honest communication with the TM including personnel constraints, gaps in skills and/or technology and similar considerations.

VII. Travel

There is no non-local travel for this SOW.

VIII. Work Location

This work shall be performed in a combination of on-site at the Goddard Space Flight Center, or at the contractor’s facility, based on work requirements and in accordance with NASA's work policy.

IX. Reporting Requirements

At a minimum, the contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the GSFC NMDB online library, as directed by the TM. The contractor shall also track all changes to analyses approach and schedule as negotiated with the TM in a location accessible to all stakeholders, including the rationale for the change.

X. Security Requirements

Work product from this task is anticipated as being performed at the Flight Dynamics Facility (FDF) and at the contractor’s facility. Any access by task personnel of government furnished equipment or computing systems will done in compliance with all applicable IT security requirements (e.g. Satern IT training). Any additional assets (e.g., GSFC’s mission cloud platform) shall be identified and an appropriate rationale for the need and a corresponding assessment of the risk shall also be provided.

XI. Rights

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – special works (FAR

52.227-17) (2007). OR

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – general (FAR 52.227-14) Alternate II (2007 and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).

XII. References

None

FDSS-IV (RTO 2) Statement of Work

Task: Guardian Mission Design

Task Order: 002

NASA/Goddard Space Flight Center in conjunction with the National Oceanic and Atmospheric Administration (NOAA) and the Bureau of Land Management (BLM) is developing infrastructure for the Guardian Mission. Guardian consists of a constellation consisting of a yet-to-be-determined number of spacecraft in low-Earth orbit. The goal of the Guardian Mission is to provide real time situational awareness and context-specific data to assist in catastrophic land change events in the United States. The overall concept of operations consists of a fleet of Guardian Spacecraft in orbit around the Earth that are equipped with a sensor suite and corresponding processing software to detect land change and to promote the raw data to actionable Level 2 (L2) products for supporting first responders with no more than 1 hour latency. Figure 1 shows a possible Guardian-detected land change event in which the spacecraft on the left initially detects the outbreak of a fire in southern California. That spacecraft then alerts nearby members in the constellation and subsequently begins to prioritize data and starts processing raw sensor input into actionable products for first responders.

Figure 1: Guardian Mission responding to a sudden outbreak of a fire in southern California as a prototypical example of a catastrophic land change event.

It is generally expected that no single Guardian Spacecraft will have sufficient time to completely characterize and process an event. So, the fleet as a whole will be tasked to act in concert with the primary means of enabling this being inter-spacecraft communications links supplemented by key deployed ground assets.

The scope of this task includes working with the TM to generate a set of candidate constellation designs and documenting the strengths of these designs (mission metrics, VI. Performance Metrics

The work performed for this task will be evaluated by the Technical Monitor based on the technical merit. Specific performance metrics for this task are: 1) timely delivery of all deliverables (including clearly supported and negotiated rationales where delivery is delayed), 2) technical quality based on appropriate depth and scope of analysis, rigor of methods, and quality of documented results, and 3) open and honest communication with the TM including personnel constraints, gaps in skills and/or technology and similar considerations.

VII. Travel

There is no non-local travel for this SOW.

VIII. Work Location

This work shall be performed primarily at the contractor’s facility, but the contractor may be required to perform some work at the Goddard Space Flight Center.

IX. Reporting Requirements

At a minimum, the contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the GSFC NMDB online library, as directed by the TM. The contractor shall also track all changes to analyses approach and schedule as negotiated with the TM in a location accessible to all stakeholders, including the rationale for the change.

X. Security Requirements

Work product from this task is anticipated as being performed at the contractor’s facility.

Any access by task personnel of government furnished equipment or computing systems will done in compliance with all applicable IT security requirements (e.g. Satern IT training). Any additional assets (e.g., GSFC’s mission cloud platform) shall be identified and an appropriate rationale for the need and an corresponding assessment of the risk shall also be provided.

XI. Rights

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – special works (FAR

52.227-17) (2007). OR

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – general (FAR 52.227-14) Alternate II (2007 and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).

FDSS-IV (RTO 3) Statement of Work

Task: Flight Dynamics Tool Interoperability Task

Task Order: 003

NASA Goddard Space Flight Center’s Navigation and Mission Design Branch along with the Space

Communication and Navigation (SCaN) Program is developing a communication and navigation infrastructure for a sustained lunar presence and, eventually, missions to Mars and beyond. This infrastructure is a constellation of ten communication and navigation satellites in lunar orbit that have intercommunications with one another, with three of these satellites having communication back to Earth ground assets.

Individual tools have been or are being developed to address specific aspects of designing a constellation mission of this type. For example, there competing approaches to optimizing the low-thrust transfers from low-Earth orbit to lunar orbit and a variety of first guess utilities to provide a starting constellation design for evaluation in a full force model (i.e., ephemeris model).

Project systems engineering requires that individual designs, referred to as Detailed Reference

Missions (DRMs), be evaluated based on a set of common DRM metrics that include:

• Transfer orbit duration and delta-V

• Percent coverage and contact times for the constellation

• Constellation maintenance, frequency, and associated delta-V

• Communications latency and the number of required available nodes

• Additional engineering requirements, such as sun angles for thermal, communication link budgets, etc.

The government is looking for a high-level design of an integration framework to facilitate the construction and evaluation of a variety of DRMs, an accurate cost estimate, and a set of corresponding high-level requirements.

II. Period of Performance

EXAMPLE: The period during which the work for this task shall be performed is between November

18, 2024 and October 31, 2025.

III. Task Description

The goal of this task is to design and cost an integration framework that provides wrappers so that the various flight dynamics tools can be integrated together in a coherent way to construct DRMs, evaluate their performance relative to a set of defined metrics, and generate a variety of reports to support the systems engineering analysis.

The generation of a DRM is done using a suite of tools with varying degrees of fidelity and speed.

Some tools function as first-guess utilities defining either the constellation in its operational orbit or the transfer trajectories of individual spacecraft, assumed to be launched separately or in pairs.

Other tools provide a full-ephemeris model needed for detailed mission analysis of items such as maneuver frequency and size, percent coverage of the lunar surface as a function of time, direct-to-earth downlink opportunities, etc. or as a way of evaluating the amount of tracking required for either ground-based or onboard orbit estimation to achieve a certain definitive accuracy.

The high-level notion for what the government is seeking is represented in the following figure:

Our current list of tools to include:

• Mission Analysis Environment (MAnE) – indirect trajectory optimization method

• Evolutionary Mission Trajectory Generator (EMTG) – direct trajectory optimization method

• Goddard Lie (GLie) – constellation modeling tool

• General Mission Analysis Tool (GMAT) – general-purpose, high-fidelity flight dynamics tool

• Orbit Determination Error Analysis System (ODEAS) – linear propagation of error tool for ground-based orbit determination analysis

• Goddard Enhanced Onboard Navigation System (GEONS) – onboard orbit determination system

In order to realize this framework, this task includes the following work items:

• Assess potential options for scripts, ‘glueware’, etc. for the processing of multiple spacecraft navigation solutions using GEONS/ODEAS and GMAT

In addition, the contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the compliance of the TM.

VI. Performance Metrics

The work performed for this task will be evaluated by the TM based on the technical merit.

Specific performance metrics for this task are: 1) timely delivery of all deliverables (including clearly supported and negotiated rationales where delivery is delayed), 2) technical quality based on appropriate depth and scope of analysis, rigor of methods, and quality of documented results, and 3) open and honest communication with the TM including personnel constraints, gaps in skills and/or technology and similar considerations.

VII. Travel

There is no non-local travel for this SOW.

VIII. Work Location

This work shall be performed primarily at the contractor’s facility, but the contractor may be required to perform some work at the Goddard Space Flight Center.

IX. Reporting Requirements

At a minimum outside of weekly status reports, the contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the GSFC NMDB online library, as directed by the TM. The contractor shall also track all changes to analyses approach and schedule as negotiated with the TM in a location accessible to all stakeholders, including the rationale for the change.

X. Security Requirements

Work product from this task is anticipated as being performed at the contractor’s facility.

Any access by task personnel of government furnished equipment or computing systems will be done in compliance with all applicable IT security requirements (e.g. SATERN IT training). Any additional assets (e.g., GSFC’s mission cloud platform) shall be identified and an appropriate rationale for the need and an corresponding assessment of the risk shall also be provided.

XI. Rights

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – special works (FAR

52.227-17) (2007). OR

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – general (FAR 52.227-14) Alternate II (2007 and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).