J_1_Attachment_-_SOW.pdf

Department of the Interior U.S. Geological Survey

Landsat Next (LNext) Mission Operations Center (MOC) Studies Requirements and Statement of Work (SOW)

Version 1.7

October 2023

140G0124Q0011 - Attachment J.1 - SOW Page 1 of 22

- ii -

Executive Summary

This document provides the requirements and statement of work (SOW) for studies of technology and systems to inform the architecture and acquisition strategy for the Landsat Next (LNext) mission operations center (MOC).

Landsat represents the world’s longest continuously acquired collection of space-based moderate-resolution land remote-sensing data. The program’s imagery provides a unique resource for those who work in agriculture, geology, forestry, regional planning, education, mapping, and global change research. Landsat images are also invaluable for emergency response and disaster relief.

In February 2023, USGS released a Landsat Next MOC Request for Information (RFI) to gather industry input for a future Landsat Next MOC considering 1) Landsat Multi-satellite Mission Operations Center (LMOC) augmentation 2) alternative MOC solutions.

While responses to the RFI significantly helped USGS understand the industry capabilities, the USGS continues to seek additional information on cost effective MOC architectures and design concepts for constellation operations for Landsat Next alternative MOC solutions. In addition, Landsat Next released the Landsat Next Mission Synopsis that provides additional information on the Landsat Next mission operations concept, greater detail about interfaces between the MOC and the observatory, and automation concepts. This funded study is needed by the USGS to obtain additional information necessary to help understand industry capabilities including candidate architectures, design concepts, and associated costs for development and operations phases of the mission.

140G0124Q0011 - Attachment J.1 - SOW Page 2 of 22

- iii -

Document History

Document Number

Document Version

Publication Date

Change Number

N/A 1.7 October 2023 Initial Version

140G0124Q0011 - Attachment J.1 - SOW Page 3 of 22

- iv -

Contents

Executive Summary ...................................................................................................... ii

Document History ........................................................................................................ iii

Contents ........................................................................................................................ iv

List of Figures ............................................................................................................... v

List of Tables ................................................................................................................. v

Section 1 Introduction

1.1 Background

1.2 Purpose

1.3 Scope

1.4 References

1.4.1 Applicable Documents

1.4.2 Reference Documents

Section 2 LNext Mission Overview

2.1 Mission Statement

2.2 Mission Background

2.3 Objectives

2.4 Mission Implementation

2.4.1 Space Segment

2.4.2 Ground Segment

2.4.3 Launch Segment

Section 3 Statement of Work (SOW)

3.1 Study Introduction and Problem Statement

3.2 Study Scope

3.3 Study Deliverables

3.4 Option 1: Candidate MOC Architecture concept for the LNext constellation ... 10

3.5 Option 2: Candidate Technology Infusion and Functionality Enhancements .. 10

Option 2A – Messaging Architecture

Option 2B – Containerization & Modular Design for Sustainability

Option 2C – Cloud Hosting and Commanding from a Cloud-Based Architecture .. 12

Option 2D – Highly Capable & Efficient Realtime Telemetry and Command Processing System

Option 2E – Automated Constellation Mission Planning

Option 2F – Highly Capable & Efficient Telemetry Trending and Analysis System 14

Option 2G – Other Relevant Technology

Appendix A Acronyms

140G0124Q0011 - Attachment J.1 - SOW Page 4 of 22

- v -

List of Figures

Figure 2-1. Landsat Next Operations Concept (Generated from Landsat Next Common Mission Architecture Diagram LNEXT-SYS-DESC-0022 Rev -)

List of Tables

Table 1-1. Applicable Documents

Table 1-2. Reference Documents

140G0124Q0011 - Attachment J.1 - SOW Page 5 of 22

- 1 -

Section 1 Introduction

1.1 Background

The Landsat Next (LNext) mission is a component of the Sustainable Land Imaging (SLI) Program conducted jointly by the National Aeronautics and Space Administration (NASA) and U.S. Geological Survey (USGS) of the Department of the Interior (DOI).

LNext was conceived as a follow-on mission to the highly successful Landsat series of missions that have provided satellite coverage of Earth’s continental surfaces since the launch of the Earth Resources Technology Satellite (ERTS, later renamed Landsat 1) in 1972. The Landsat data archive constitutes the longest continuous moderate-resolution record of the global land surface as viewed from space. LNext is intended to ensure that Landsat-like data be provided to the USGS National Satellite Land Remote Sensing Data Archive (NSLRSDA) for a period of not less than five years.

1.2 Purpose

This document provides the requirements and statement of work (SOW) for studies of technology and systems to inform the architecture and acquisition strategy for the LNext mission operations center (MOC).

1.3 Scope

This document covers the work defined for the studies, not the full LNext MOC development effort. A subset of the mission, draft ground system, and draft MOC requirements are included to provide context and requirements for the LNext MOC effort. Depending upon the content of the study efforts, some, or all of the MOC and system requirements subset will be addressed.

The following definitions are used in this document:

• Shall: Compliance by the vendor is mandatory. Any deviations from these contractually imposed mandatory requirements require the approval of the contracting officer. The vendor shall flow all contractual requirements to any and all subcontractors employed.

• May: At the discretion of the vendor or Government.

• Will: Designates the intent of the Government. Unless required by other contract provisions, noncompliance with a will statement does not require approval of the contracting officer and does not require documented technical substantiation.

1.4 References

1.4.1 Applicable Documents

The documents in Table 1-1 are considered to form a part of this document.

140G0124Q0011 - Attachment J.1 - SOW Page 6 of 22

- 2 -

Document Number Document Title

N/A Landsat Next Mission Synopsis - July 2023 Update for Release

140G0123R0004 LNext MOC Request for Information (RFI)

LNEXT-SYS-DESC-

0018 Revision A

Landsat WRS-3 Definition

LSDS-2389 Version 1.0

Landsat Next Design Reference Case – 18 Days (DRC-18) Definition

Table 1-1. Applicable Documents

1.4.2 Reference Documents

The documents in Table 1-2 provide additional background and context for this document.

Document Number Document Title

GSFC-STD-1000H

Rules for the Design, Development, Verification, and Operations of Flight Systems (GOLD Rules)

GSFC-STD-1001A

Criteria for Flight and Flight Support System Lifecycle Reviews

NASA/SP-2014-3705

NASA Space Flight Program and Project Management Handbook

NPR 7120.5F

NASA Space Flight Program and Project Management Requirements

NASA/SP-2014-3706B Standing Review Board Handbook

NPR 7123.1D

NASA Systems Engineering Processes and Requirements

NASA/SP-2016-6102 Rev2 NASA Systems Engineering Handbook, February 2017, Rev 2

NPR 7150.2D NASA Software Engineering Requirements

Table 1-2. Reference Documents

140G0124Q0011 - Attachment J.1 - SOW Page 7 of 22 https://sam.gov/api/prod/opps/v3/opportunities/resources/files/09690c8d5f6e468e9d3bcbe208ea04bd/download?&token= https://sam.gov/opp/5eb146434f774d1aab2968843d2be47a/view https://sam.gov/api/prod/opps/v3/opportunities/resources/files/cdc4ac3ed595477f99f4ebd2a6294640/download?&token= https://sam.gov/api/prod/opps/v3/opportunities/resources/files/cdc4ac3ed595477f99f4ebd2a6294640/download?&token= https://sam.gov/api/prod/opps/v3/opportunities/resources/files/ecf54fa941a34eb5ae8116a5e09065be/download?&token= https://sam.gov/api/prod/opps/v3/opportunities/resources/files/ecf54fa941a34eb5ae8116a5e09065be/download?&token= https://standards.nasa.gov/standard/GSFC/GSFC-STD-1000 https://standards.nasa.gov/sites/default/files/standards/GSFC/A/0/gsfc-std-1001-a_extension_04-01-2020.pdf https://ntrs.nasa.gov/citations/20220009501 https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=7120&s=5E https://ntrs.nasa.gov/citations/20230001306 https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7123_001D_/N_PR_7123_001D_.pdf https://www.nasa.gov/seh/index.html https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_002D_&page_name=main

- 3 -

Section 2 LNext Mission Overview

2.1 Mission Statement

Landsat Next, consistent with United States (U.S.) law and Government policy, will continue the Landsat program's acquisition, archival, and distribution of multi-spectral imagery affording global, synoptic, and repetitive coverage of the Earth's land surfaces at a scale where natural and human-induced changes can be detected, differentiated, characterized, and monitored over time.

2.2 Mission Background

Following the successful launch of Landsat 8 (L8, formally named the Landsat Data Continuity Mission, LDCM) in February 2013, and during the development of Landsat 9 (L9), the United States Geological Survey (USGS) and National Aeronautics and Space Administration (NASA) recognized the need to assemble a team of experts from within both agencies to evaluate how to inform an acquisition strategy for the Landsat mission to follow Landsat 9. The NASA-USGS Joint Agency Sustainable Land Imaging (SLI) Architecture Study Team (AST) was formed in September 2018 and was tasked with investigating how to best satisfy the diverse set of user needs collected in the USGS “User Needs for the Sustainable Land Imaging Program – Release 2.0.” These investigations resulted in a set of recommendations to the headquarters of both agencies, delivered in December 2019. The highest-recommended “Roadmap 1” architecture described a small constellation of “superspectral” space-based sensors that would substantially improve the spectral, spatial, and temporal capabilities of previous Landsat missions, while continuing to satisfy the primary goal of ensuring a highly calibrated data set that maintains compatibility with the legacy data of the Earth’s land mass held in the National Satellite Land Remote Sensing Data Archive (NSLRSDA) at USGS’s Earth Resources and Observation Science (EROS) Center. In April 2020 NASA/Goddard Space Flight Center (GSFC) received authorization to initiate the Landsat Next project consistent with the AST’s Roadmap 1 recommendation.

The goal of Landsat Next is to continue the acquisition, archival, and distribution of multi-spectral imagery affording global, synoptic, and repetitive coverage of the Earth's land surfaces at a scale where natural and human-induced changes can be detected, differentiated, characterized, and monitored over time. This goal is in keeping with the Landsat programmatic goals stated in both the Commercial Space Act of 1998 (Public Law 105-303) and the Land Remote Sensing Policy Act of 1992 (Public Law 102-555).

This policy requires that the Landsat Program provide data into the future that is sufficiently consistent with previous Landsat data to allow the detection and quantitative characterization of changes in or on the land surface of the globe.

Landsat Next continues the long-running partnership of NASA and USGS, with NASA providing the space and launch segments and USGS providing the ground system, providing the longest continuous global record of the Earth’s surface. The Landsat series of satellites have continuously acquired multispectral images of the global land surface since the launch of the Earth Resources Technology Satellite (ERTS, later

140G0124Q0011 - Attachment J.1 - SOW Page 8 of 22

- 4 -renamed Landsat 1) in 1972. The Landsat data archive constitutes the longest continuous moderate-resolution record of the global land surface as viewed from space.

2.3 Objectives

Landsat Next has these major mission objectives:

• Collect and archive moderate resolution, Visible Through Short Wave Infrared (VSWIR) reflective and Thermal Infrared (TIR) emissive image data affording seasonal coverage of the global landmass for a continuous period of not less than five (5) years

• Ensure that Landsat Next data are sufficiently consistent with data from the earlier Landsat missions in terms of relative acquisition geometry, calibration, coverage characteristics, spectral characteristics, output product quality, and data availability to permit studies and management of land cover along with land and water resource change over multi-decadal time periods

• Ensure Landsat Next is responsive to critical emerging user needs and applications as characterized by periodic assessment, currently the User Needs for the Sustainable Land Imaging Program July 2018, Release 2.0, and identified by the operational requirements for collection, processing, archiving, and distribution of land surface data to the United States Government and other users

• Distribute Landsat Next data products to the public on a nondiscriminatory basis

2.4 Mission Implementation

NASA and USGS each have specific responsibilities for Landsat Next and will deliver the major elements to the overall mission. NASA will provide the Space and Launch Segments of Landsat Next, and USGS will provide the Ground System and mission operations. NASA/GSFC will provide overall Landsat Next project management, mission system engineering, and mission assurance during development and will transition the mission to USGS following on-orbit commissioning.

The Landsat Next post-launch nominal mission operations concept is shown graphically in the following figure 2-1.

140G0124Q0011 - Attachment J.1 - SOW Page 9 of 22

- 5 -

Figure 2-1. Landsat Next Operations Concept (Generated from Landsat Next Common Mission Architecture Diagram LNEXT-SYS-DESC-0022 Rev -)

2.4.1 Space Segment

NASA/GSFC will provide the Space Segment, which will consist of a constellation of three observatories flying in coordinated sun-synchronous orbits at 653 Km altitude, each with nominally identical spacecraft and instrument suites. The observatories will be equally spaced in the orbit, providing in aggregate a six-day ground repeat period at the equator.

The instrument suites will each provide 26 spectral bands with a maximum ground sampling distance of 10m-60m dependent on the spectral band, covering a swath on the ground of approximately 164 Km on a ground track defined by a world-wide reference system known as WRS-3.

2.4.2 Ground Segment

The Landsat Ground Segment currently supports mission operations for Landsats 8 and

9. Landsat Next takes advantage of developments on these missions and will upgrade and expand the current systems to accommodate Landsat Next. The Landsat Ground Segment consists of the Ground System (GS) and its external interfaces, including NASA institutional services. The GS includes the Mission Operations Center (MOC), the Ground Network (GN), and the Data Processing and Archive System (DPAS). External interfaces include NASA's Near Space Network (NSN) and Advanced Communications Capabilities for Exploration and Science Systems (ACCESS), GSFC Conjunction Assessment and Risk Analysis (CARA) and its Flight Dynamics Facility, along with other external interfaces.

140G0124Q0011 - Attachment J.1 - SOW Page 10 of 22

- 6 -

The MOC provides the primary means to control and monitor the Landsat Next constellation. The Landsat Next Flight Operations Team (FOT) at the MOC performs mission planning and scheduling, command and control, health and status monitoring, orbit and attitude maintenance, performance analysis, onboard memory management, and flight and ground software maintenance. The FOT utilizes MOC functionality to detect, investigate and resolve spacecraft anomalies and monitor the instrument image collections from the onboard constellation and generate special image collections. The MOC ingests, processes and archives data via the GN.

The GN includes geographically dispersed ground station resources for mission execution and includes both the Landsat Ground Network (LGN) and a wideband data routing capability, which transfers mission data to DPAS across wide area networks.

The LGN provides communication capability for each observatory of the constellation for commanding and housekeeping data via the S-Band and will receive mission data from each observatory over a Ka-band downlink.

The DPAS ingests mission data from the GN, processes the mission data to form data products, and archives the data products (Level 0, Level 1R, Level 1Gs, Level 1T). The DPAS also provides a long-term archive capability for raw data and allows the user community to query, download, and directly interact in the cloud with Landsat Next data products, via a public-facing web portal for receiving data products. The DPAS is located at USGS Earth Resources Observation and Science (EROS) near Sioux Falls, South Dakota.

The USGS will lead overall Landsat Next GS development. The USGS will also lead integration of the GS and ensure timely completion of ground readiness testing in preparation for NASA-led mission readiness activities. The MOC will perform planning, scheduling, and observatory operations activities during Landsat Next mission readiness testing.

2.4.3 Launch Segment

The Launch Segment will provide the assets and services associated with the Launch Vehicle (LV) and the constellation-to-LV integration. This will include the LV; all Launch Vehicle-Ground Support Equipment (LV-GSE), property, and facilities to integrate the constellation to the LV and verify their integration; and prelaunch testing with ground-based functions. The launch vehicle and launch site are TBD. The three observatories comprising the Landsat Next constellation will be launched together on the same launch vehicle.

Sections 2.0-2.4.3 were generated using Landsat Next Common Boilerplate (LNEXT- MGMT-DESC-0005) Rev C

140G0124Q0011 - Attachment J.1 - SOW Page 11 of 22

- 7 -

Section 3 Statement of Work (SOW)

3.1 Study Introduction and Problem Statement

The Government seeks to better understand the cost basis for development and implementation (Phases B-D) and long-term operations and sustainment (Phase E) predicated on an LNext MOC constellation architecture concept recommended by vendors at the conclusion of this study. The Government also seeks to better understand application of industry innovations, technologies, and enhancements relevant to constellation MOCs and flight operations that enable reliability, automation, optimization, and use of artificial intelligence (AI) and machine learning (ML).

For cost basis analyses, the Landsat series of satellites have traditionally operated much longer than the design life of 5-years. Accordingly, the LNext triplet constellation is expected to operate into the early 2040s. Therefore, an LNext MOC architecture solution must enable reliable, cost-effective, automated operations for long-term health and safety and science imaging acquisition and be efficient to maintain. The synopsis update (listed in the applicable documents table) provides an overview of functionality and performance expected for the LNext MOC.

The USGS is seeking architecture, design, and cost basis information for the full LNext MOC (Option 1) that meets the objectives for the MOC as described within the documentation provided. A key element of the cost basis will be grounding of the estimate in relevant work and experience, through the design and demonstration process.

Alternatively, vendors may propose against one or more (up to three) specific technologies or subsystems relevant to the LNext MOC (Option 2). Areas of interest and possible investigations are described in Section 3.5. Note that architecture context and full cost basis analyses are required regardless of the option selected.

• Option 1: Candidate MOC Architecture concept for the LNext constellation

• Option 2: Candidate Technology Infusion and Functionality Enhancements o A – Messaging Architecture o B – Modularity o C – Cloud Hosting Approaches o D – Real-time Telemetry & Command Processing o E – Mission Planning o F – Telemetry Trending & Analysis o G – Other relevant technology

As defined in the request for quotation (RFQ) documentation and associated preparation instructions, the size of awards for Option 2 will be less than the values for Option 1 awards based on the scope of work. For work done under Option 1 or Option 2, refer to Section 3.2 and 3.3 for more details.

140G0124Q0011 - Attachment J.1 - SOW Page 12 of 22

- 8 -

3.2 Study Scope

1. Develop a Work Plan that defines the scope of work and schedule for the candidate area(s) studied

2. Develop a candidate LNext MOC architecture solution (white paper or slides) and its relevance/potential benefits to the LNext MOC (MOC performance, efficiency, and/or operations costs). Include corresponding conceptual design, diagram(s), interface definitions and operations concept narratives that apply the technologies and functions depicted (end-to-end for Option 1 or targeted areas for Option 2).

i. The Government has not yet determined the location of the LNext MOC.

The L8/L9 LMOC is located at NASA GSFC and there are benefits of being located in a government facility. Assume a MOC implementation at NASA GSFC but include considerations in your conceptual design for a potential vendor location as well (if applicable), highlighting the areas of efficiency and risk (including vendor location lock-in) to be considered.

Ideally, architectures are flexible enough to be location agnostic, but highlight any location constraints and considerations.

ii. Assume the Government will provide software and hardware spacecraft simulators for testing at the MOC.

3. Provide a demonstration/prototype (where applicable) of option selected (end to end for Option 1 or targeted areas for Option 2) and prepare any associated presentation materials.

i. Optionally, a demonstration / prototype (where applicable) of the technology or application in a notional LNext MOC context as referenced in the LNext Mission Synopsis. This study allows for demonstration of existing capabilities or to include slight modifications or initial developments for capabilities to illustrate potential capabilities and the associated costs for development efforts for use on LNext.

4. Develop a cost estimate for the candidate architecture that includes:

i. Basis of Estimate (BOE) and assumptions including implementation and/or location details where it impacts cost. Vendors are welcome to include multiple versions of cost estimates for different parameters if desired. Prototype/demo work should be used as a basis to develop cost estimates for development and operations

ii. Provide a 5-year Phase E cost estimate for Option 1 OR Option 2 candidate area(s) studied, including initial operations and steady state operations, covering both system maintenance and flight operations.

• For the cost estimate, please consider timeframe and resources needed to achieve steady-state operations. Further assumptions and details to use in developing the estimate will be provided after contract award.

iii. Provide a cost estimate to develop and implement (Phases B-D) for the Option 1 candidate MOC architecture concept OR other candidate areas studied under Option 2.

140G0124Q0011 - Attachment J.1 - SOW Page 13 of 22

- 9 -

• Assume phases B-D cost estimate is based on GSFC-STD-1001a and NPR 7120.5f development lifecycle review milestones.

Further assumptions and details to use in developing the estimate will be provided after contract award.

5. Lead virtual, routine status and clarification meetings with the Government, notionally scheduled biweekly, but could be weekly by mutual agreement

6. Lead two checkpoint reviews to present status, findings, and discuss any clarifications required

i. Checkpoint 1 will be a virtual meeting, notionally two hours in duration, taking place two months after award

ii. Checkpoint 2 will be an in-person (face-to-face) meeting notionally at the vendor’s facility (but may consider virtual at the Governments discretion), and notionally four hours in duration (based on study scope), taking place three months after award

iii. Note: Government staff (civil servants) and federally funded research and development center (FFRDC) team members comprise the USGS and NASA partners

7. Perform a final presentation at the end of the period of performance, notionally four months from award with a duration of approximately four hours

i. The location will notionally be at the vendor’s facility but will be determined later and by mutual agreement.

3.3 Study Deliverables

For each study awarded, the vendor shall deliver the following (see additional details in section 3.2):

1. Study Work Plan describing scope and milestone-based schedule

2. A candidate LNext MOC architecture solution or specific technology (end-to-end for Option 1 or targeted areas for Option 2) and its relevance/potential benefits to the LNext MOC (MOC performance, efficiency, and/or operations costs). This may be delivered as a white paper or a set of slides along with associated artifacts (diagrams, documents) and may be combined with the final report.

3. Optionally, a system demonstration/prototype and associated presentation materials (end-to-end for Option 1 or targeted areas for Option 2).

4. Cost Estimate of candidate architecture that includes:

a. Basis of estimate and assumptions

b. Phase E 5-year cost estimate

c. Phases B-D cost estimate

5. Checkpoint 1 electronic copy of presentation

6. Checkpoint 2 electronic copy of presentation

7. Final Report electronic copy of presentation

8. Any additional materials the vendor choses for delivery

140G0124Q0011 - Attachment J.1 - SOW Page 14 of 22

- 10 -

3.4 Option 1: Candidate MOC Architecture concept for the LNext constellation

To effectively operate the three LNext observatories into the 2040’s, the MOC must provide reliable, efficient, automated operations (as described in the mission synopsis) enabling an optimized Phase-E cost profile. The USGS is seeking an LNext MOC candidate architecture based on capabilities, technologies, and systems that provide efficient constellation operations capabilities for all three observatories with minimal flight operations staff (FOT), enabled through implementation of automation and other techniques. While staff efficiency is a key goal, the system must provide efficient system performance and constellation capabilities in a reliable and automated way, allowing for optimal flight operations management and performance of the constellation and ground systems.

Architecture analysis and candidate solution should consider application of cloud solutions through containerization and system modularity, messaging solutions, along with reliable and highly automated lights out operations, which include flight dynamics, mission planning, telemetry and analysis, and real-time telemetry and command processing.

As defined in the deliverables, the USGS is seeking an end-to-end architecture, corresponding conceptual design, diagram, interface definitions, and associated operations concept for the LNext MOC that implements the functionality and performance described in the mission synopsis. This would be done to a level of maturity, similar to that available at a system definition review (SDR) or preliminary design review (PDR) and include both subsystem and interface definitions to allow assessment of signal flow and workflow.

3.5 Option 2: Candidate Technology Infusion and Functionality Enhancements

Each of the following subsections describe candidate study areas for Landsat Next.

Sections 3.2 and 3.3 above describe the study scope and deliverables which apply to each of the following candidate study areas. These candidate study areas describe specific areas of interest and concern by the Government. Vendors may propose to study up to three candidate areas (one to three). Regardless of the number of studies awarded, the vendor must provide the deliverables defined in section 3.3 but may combine deliverables for multiple study areas.

Option 2A – Messaging Architecture

MOC architectures are composed of several subsystems and some type of communications framework between them. The existing Landsat 8 and 9 MOC uses a file-based communication framework to enable subsystems to pass data between each other.

The USGS is interested in exploring options for use of a standards-based messaging system for communication and data transfers between subsystems and applications

140G0124Q0011 - Attachment J.1 - SOW Page 15 of 22

- 11 -within the LNext MOC. USGS is interested in understanding potential benefits from this type of communication framework and how it might improve efficiency, scalability, and enable better automation and easier monitoring and troubleshooting of the system and also where it may add cost, risk, or complexity. The USGS is interested in better understanding what communication framework and standards that are applicable for LNext, how widely used those standards are, and the amount of effort and potential return on investment of implementing such an architecture that includes use of standard interfaces. The study should include use of the standard messaging architecture with common COTS/GOTS applications to determine level of support already provided as well as any security concerns that may exist.

A white paper that describes a messaging architecture for the Landsat Next MOC will help the government determine what standards are being used and the maturity of those standards. The government also needs to understand the costs associated to implement the standards using the messaging architecture proposed. The white paper should include:

• Which messaging supports modularity (how critical is it to sustainability of the system)

• Examples of missions using this system

• Outline standards adopted

• Risks and suggested mitigations

Option 2B – Modular Design for Sustainability

The USGS would like to explore the feasibility and complexity of implementing modularity for sustainability in the LNext MOC. The Government is interested in better understanding the benefits of a more loosely coupled architecture based on standards.

The Government must adopt a framework that allows for a cost-effective sustainment of the MOC, enabling subsystems and applications to be easily replaced as needed when they become obsolete or when replacement offers greater advantages. Efficient sustainment assumes the ability to replace a subsystem with minimal reengineering or modifications to other subsystems or applications and without unpacking layers of scripts and/or glue-ware.

The Government needs to better understand the benefits, risks, as well as development effort and complexity of this type of architecture to better assess potential return on investment. USGS is also interested in understanding how widely adopted this architecture is within similar MOC systems and what limitations and constraints exist with this architecture, including security concerns, in particular, any which could create challenges in selecting subsystem capabilities for LNext.

A white paper that describes a modular design / framework for the Landsat Next MOC will help the government determine what capabilities are available and maturity of those capabilities along with costs to implement and sustain them. The white paper should include:

• Methods for replacing/swapping out subsystems (goal to require minimal engineering intervention)

140G0124Q0011 - Attachment J.1 - SOW Page 16 of 22

- 12 -

• Which messaging supports modularity (how critical is it to sustainability of the system)

• Examples of missions using this system

• Outline standards adopted

• Risks and suggested mitigations

Option 2C – Cloud Hosting and Commanding from a Cloud-Based Architecture

The USGS is considering the use of a cloud-based architecture for improved resilience, scalability, and flexibility for operations. The Government is looking for information that will help determine if cloud hosting for Constellation MOC applications is reliable and cost effective over on prem solutions. The Government is concerned about IT security aspects of commanding in the cloud as well as costs associated with accessing and processing large amounts of data in the cloud and its impact on long-term operations.

The USGS is highly concerned with cost efficiency in a cloud environment and the method used to deploy applications in the environment to ensure efficient long-term operations (lift and shift vs cloud-native engineered solutions).

The current L8/9 LMOC is implemented using virtual machines running on an on-premises cluster of COTS LINUX and Windows servers with associated networking and hardware command encryption appliances. The USGS would like to explore the feasibility and complexity of implementing the LNext MOC system using a cloud-based/cloud-native architecture. Areas of interest include understanding the information technology (IT) and network security considerations for such an implementation, estimating the staff required to support such an implementation, and implementation of cloud-based encrypted commanding, as well as whether a mission-specific or hosted environment will be a better approach considering both development and long-term Phase-E operations costs and complexities.

While some analysis has predicted a simple, low-cost, and straightforward migration to a cloud-based architecture, the USGS would like to understand practical considerations in such an approach, including exploration of a cloud-native solutions as compared to “lift and shift” of current virtualized architecture to systems hosted in the cloud. Security considerations with implementation of satellite commanding is also a concern, and the USGS would like to explore the practical implementation of a system that can address these concerns and constraints without adding undue complexity or performance restrictions. This effort could include conversion of an application or product to operate in cloud-native environment with a demonstration of the product as a result of the study effort.

USGS requires cost information to help determine if hosting the MOC in the cloud is feasible. USGS must understand the effort and complexity of containerizing or modularizing systems that do not have this capability already. If there are costs associated with porting current capabilities to the cloud native solutions, the government needs to understand them. Vendors may choose to migrate an application, demonstrate that application and explain how this will scale to a fully implemented LNext MOC solution. Vendors must take into consideration the full MOC architecture

140G0124Q0011 - Attachment J.1 - SOW Page 17 of 22

- 13 -solution to determine what functions may be feasibly migrated to the cloud and what functions must remain on-prem along with associated interfaces between them.

A white paper that describes an efficient cloud or hybrid-cloud enabled framework for the LNext MOC will help the government determine what capabilities are available and maturity of those capabilities along with costs to implement and sustain them. The white paper should include:

• Cloud native functions; use of containerization and emerging cloud technologies

• What functions must remain on-prem?

• Associated technology readiness level (TRL) of proposed MOC functions in the cloud including missions where the functions are being used

• Security Approaches and Risks

• Outline standards adopted

• Risks and suggested mitigations; For example, how does the government mitigate risk of cloud vendor lock-in and escalating costs?

• Lessons from other missions and their cloud implementations

Option 2D – Highly Capable & Efficient Realtime Telemetry and Command Processing System

The L8/9 LMOC uses a commercial version on the NASA GOTS Integrated Test and Operations System (ITOS) real-time command and TLM (T&C) processing system called Galaxy. The USGS is interested in learning more about the feasibility and benefits of using other real-time T&C processing systems for LNext. These could include GOTS, open-source, or commercial (COTS) applications. Ideally, solution sets are based on an existing application with minor modifications to accommodate the new LNext observatory T&C database.

Additionally, the Landsat Next project is interested in advanced visualization tools to enable more effective flight operations of both individual observatories and the complete constellation. This would provide both FOT operations staff and mission managers with the ability to easily gain insight into the health, safety, and performance of the mission and constituent observatories. Both console visualization tools and (associated) report-generation tools are of interest.

Other capabilities and features of these tools would be explored, such as predicted performance gains in the LNext MOC application and associated relevance to stated objectives, complexity for and end-to-end development implementation, ability for system/application to automate FOT functions for increased operational efficiency, suitability for use in a cloud-based environment (containerized, cloud-native application, or only support for a VM implementation, etc.), and plans for future growth/expansion of the application, and how those future plans will be managed for LNext (e.g. will be included as part of standard maintenance/product line, or would require re-engineering and integration, or would be tied into CI/CD along with the Government maintained baseline, etc.).

140G0124Q0011 - Attachment J.1 - SOW Page 18 of 22

- 14 -

Option 2E – Automated Constellation Mission Planning

LNext will use onboard automation for local observatory (spacecraft) control of routine imaging operations. The long-term acquisition plan (LTAP) defines the WRS-3 path/row-based image acquisitions for each day of the 18-day repeat cycle. The LTAP will be used to generate an LTAP collection request (LCR) that is uplinked to the observatory to guide autonomous onboard imaging acquisition. The LCR will form the basis for routine imaging with infrequent updates. Short-term changes to accommodate perturbations to the baseline will be implemented via special collection requests (SCRs) and special command requests (spCRs) to make changes in planned imaging and/or suspend imaging to accommodate other spacecraft operations (such as maneuvers).

Each observatory in the constellation will run a similar LCR implementing the LTAP for LNext as a constellation, in combination yielding six-day global revisit.

The USGS is seeking systems or technologies for efficient, automated mission planning that considers wholistic operations of the constellation (“fleet operations”) and works in conjunction with onboard automation to execute routine imaging, special requests, and other activities. For the purpose of this study, the mission planning function needs to include the traditional scheduling and planning functions, such as contact planning and scheduling, contact resource management, image collection planning and scheduling, activity planning, deconfliction, and scheduling, constraint checking and management, and load planning and coordination. Depending on the overall MOC architecture and functional distribution, it could also include other functions such as maneuver planning and constraint management, onboard image and command plan validation, mission data management, command load generation, and observatory configuration tracking.

Highly configurable automation capabilities are also needed and may be included in mission planning functions or separate, based on the overall automation architecture.

Given the complexity of managing imaging operations of three observatories simultaneously, an efficient and automated mission planning architecture is required to minimize flight operations staffing to a level comparable to operations of a single observatory (or lower if possible). Scheduling and planning must also include deconfliction of ground station contacts and optimal allocation of ground station resources between observatories in the constellation based on criteria defined by the mission and FOT (i.e. – preference for lower cost station use). The USGS is also interested in understanding the development cost or complexity drivers associated with efficient mission constellation planning approaches that yield lower Phase-E ops costs, to make an assessment on return on investment (ROI) for development-phase actions.

Option 2F – Highly Capable & Efficient Telemetry Trending and Analysis System

The L8/9 observatories generate substantially more telemetry (TLM) than prior missions, and the LNext observatories are expected to generate a similar or somewhat larger volume (per observatory), leading to a potential tripling or more of telemetry data volume to process. The USGS is looking for systems and technologies to process, analyze, and visualize this larger volume of TLM, including limit checking, state checking, configuration checking, and trend analysis very efficiently. The USGS is also interested in predictive trending to assess potential issues before they exceed a warning

140G0124Q0011 - Attachment J.1 - SOW Page 19 of 22

- 15 -threshold (both for a single spacecraft and for a complete constellation perspective), which could include monitoring predictive performance trends against requirements, margins, life limited items, and key performance mission goals. Automated analysis and trending techniques, such as machine learning (ML) are of interest due to the ability of such systems to analyze trends in large volumes of data and “learn” patterns that may indicate current issues or portend future issues. This must include both historical analysis and forward-looking predictive analysis, assessing data for individual observatories and across the constellation. The Government is interested in capabilities that would allow for reliable and repeatable use of machine learning and would like to understand better any risks and/or constraints to proposed implementations to achieving these goals.

Other capabilities and features of these tools would be explored, such as comparison with other candidate systems/applications, complexity for and end-to-end development implementation, ability for system/application to automate FOT functions for increased operational efficiency, suitability for use in a cloud-based environment (containerized, cloud-native application, or only support for a VM implementation, etc.), and plans for future growth/expansion of the application.

Option 2G – Other Relevant Technology

Vendors are also invited to suggest studies for other relevant areas of technology that would serve to address the USGS MOC objectives defined. Studies proposed via this section should clearly describe the proposed technology or application, the relevance to improving the LNext MOC performance, efficiency, or cost-effectiveness, and capability improvements the technology or application could provide.

The USGS will assess the proposed technology or application and relevance to the LNext MOC development and operations, as well as relative priority and need when determining whether a study will be funded.

140G0124Q0011 - Attachment J.1 - SOW Page 20 of 22

- 16 -

Appendix A Acronyms

ACCESS

(NASA) Advanced Communications Capabilities for Exploration and Science Systems

AI Artificial Intelligence

AMMOS (NASA) Advanced Multi-Mission Operations System

AST Architecture Study Team

CARA (NASA/GSFC) Conjunction Assessment and Risk Analysis

CCB Configuration Control Board

CM Configuration Management

COTS Commercial Off-the-Shelf

CR Change Request

DOI Department of the Interior

DPAS Data Processing and Archive System

EROS (USGS Center for) Earth Resources Observation and Science

ERTS Earth Resources Technology Satellite

FFRDC Federally Funded Research and Development Center

FOT Flight Operations Team

GN Ground Network

GOTS Government Off-the-Shelf

GS Ground System

GSD Ground Sample Distance

GSFC NASA/Goddard Space Flight Center

IT Information Technology

ITOS Integrated Test and Operations System

L7 Landsat 7

L8 Landsat 8

L9 Landsat 9

LCR Long Term Acquisition Plan (LTAP) Collection Request

LDCM Landsat Data Continuity Mission

LGN Landsat Ground Network

LMOC Landsat 8/9 (L8/9) Multi-Satellite Operations Center

LNext Landsat Next

LSDS Land Satellites Data System

LTAP Long Term Acquisition Plan

LV Launch Vehicle

LV-GSE Launch Vehicle-Ground Support Equipment

MCR Mission Concept Review

ML Machine Learning

MOC Mission Operations Center

NASA National Aeronautics and Space Administration

NSLRSDA National Satellite Land Remote Sensing Data Archive

NSN (NASA) Near Space Network

140G0124Q0011 - Attachment J.1 - SOW Page 21 of 22

- 17 -

PDR Preliminary Design Review

SCR Special Collection Request

SLI Sustainable Land Imaging

SOO Statement of Objectives

SOW Statement of Work

T&C Telemetry and Command

TIR Thermal Infrared

TLM Telemetry

USGS United States (U.S.) Geological Survey

VSWIR Visible through Short Wave Infrared

WRS Worldwide Reference System

140G0124Q0011 - Attachment J.1 - SOW Page 22 of 22