LNEXT-SC-SOW-0004 Rev C Landsat Next Spacecraft Statement of Work (SOW) 20250129.pdf

DOORS EXPORT

National Aeronautics and Space Administration

Goddard Space Flight Center Greenbelt, Maryland

LNEXT-SC-SOW-0004, Revision C

Landsat Next, Code 426

Landsat Next Spacecraft Statement of Work

(SOW)

January 27, 2025

LNext Reviewed – Not Subject to Export Control

1/29/2025

SC SOW LNEXT-SC-SOW-0004 Revision C ii

Landsat Next Spacecraft Statement of Work (SOW)

Signature/Approval Page

Prepared by:

Electronic Signature in TDMS Approval Date in TDMS Joy Henegar-Leon Date Landsat Next Payload Technical Manager NASA/GSFC, Code 426

Prepared by:

Electronic Signature in TDMS Approval Date in TDMS Bryan Mattfeld Date Landsat Next Spacecraft Systems Engineer NASA/GSFC, Code 560

Approved by:

Electronic Signature in TDMS Approval Date in TDMS Cagatay Aymergen Date Acting Landsat Next Project Manager / Landsat Next Deputy Project Manager

NASA/GSFC, Code 426

Approved by:

Electronic Signature in TDMS Approval Date in TDMS Cagatay Aymergen Date Acting Landsat Next Observatory Manager NASA/GSFC, Code 426

Approved by:

Electronic Signature in TDMS Approval Date in TDMS Evan Webb Date Landsat Next Mission System Manager NASA/GSFC, Code 599 iii

CM Foreword This document is a Landsat Next Project Configuration Management (CM)-controlled document.

Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the Landsat Next CM Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.

Questions or comments concerning this document should be addressed to:

NASA/Goddard Space Flight Center Landsat Next Project Office, Code 426 Attention: Configuration Management Office Greenbelt, Maryland 20771 iv

Change History Log Revision Effective Date Description of Changes

- 05/02/2024 LNEXT-CCR-0081 – Initial Release A 11/22/2024 LNEXT-CCR-0098 – Updates to reflect SC cost reduction activities B 01/23/2025 LNEXT-CCR-0112 –Updated to include the latest versions of the Landsat Next Common Boilerplate, LNEXT-MGMT-DESC-0005 Rev D and Landsat Next Common Mission Architecture Diagram, LNEXT-SYS-DESC- 0022 Rev A.

C 01/27/2025 LNEXT-CCR-0116 - Per recent executive order, removed all DEIA language from document. (SC-PM-07) v

List of TBDs/TBRs Hyperlink to TBx Location Summary Ind.

Name/Org. Due Date

TBx-1 Section

3.1.5.4 1 Table contains multiple TBDs. MSE Mission

SRR

TBx-2 Section 3.2.2.5

SCSOW-2073 The Contractor shall review and provide comments to the Government-generated drafts of the Launch Services Interface Requirements Document (LSIRD), TBD in support of the launch service procurement activity.

MSE Mission

CDR

TBx-3 Section 3.4.2

SCSOW-1020 Prior to CDR, the Contractor shall perform all launch vehicle compatibility analyses and structural models such that they address each of the potential vehicles (TBD, list of vehicles).

MSE Spacecraft

PDR

TBx-4 Section 3.4.12.1

SCSOW-1091 The Contractor shall provide a portfolio of twenty (20) (TBR) security keys per spacecraft for the life span of the mission.

vi

Table of Contents SIGNATURE/APPROVAL PAGE ................................................................................................ II

CM FOREWORD ..........................................................................................................................III

CHANGE HISTORY LOG .......................................................................................................... IV

LIST OF TBDS/TBRS .................................................................................................................... V

TABLE OF CONTENTS .............................................................................................................. VI

LIST OF FIGURES ........................................................................................................................ X

LIST OF TABLES .......................................................................................................................... X

1.0 INTRODUCTION

1.1 Scope

1.2 Related Documentation

1.2.1 Applicable Documents

1.2.2 Reference Documents

1.2.3 Project Applicable Documents

2.0 MISSION OVERVIEW

2.1 Mission Statement

2.2 Mission Background

2.3 Mission Objectives

2.4 Mission Implementation

2.4.1 Space Segment

2.4.2 Ground Segment

2.4.3 Launch Segment

3.0 WORK TO BE PERFORMED

3.1 Project Management (PM)

3.1.1 Government Insight and Surveillance

3.1.2 Control of Sensitive Information

3.1.3 Non-Disclosure Agreements

3.1.4 Documentation

3.1.5 Reviews

3.1.5.1 Major Reviews

3.1.5.2 Spacecraft Reviews

3.1.5.3 Additional Required Meetings and Reviews

3.1.5.4 LNext Mission Level and Other LNext Reviews

3.1.6 Anomaly Reporting and Disposition

3.1.7 Electronic Access

3.1.8 Risk Management

3.1.9 Resource Management

3.1.10 Configuration Management

3.1.11 Subcontractor Management

3.1.12 Government Resident Office Support

vii

3.1.13 Audits

3.1.14 Lessons Learned Reporting

3.1.15 Information Technology (IT) Security and Cybersecurity

3.1.15.1 Federal Information Systems

3.1.15.2 Connected Information Systems

3.1.15.3 Internal Information Systems

3.1.16 System Security of Space Assets

3.2 Systems Engineering

3.2.1 Requirement Analysis, Derivations, and Allocations

3.2.1.1 Use of Dynamic Object-Oriented Requirements System (DOORS) Tool 36

3.2.2 Interface Definition, Verification and Control

3.2.2.1 Spacecraft-Instrument Interface

3.2.2.2 Observatory-to-Ground Interface

3.2.2.3 Flight Operations Interface

3.2.2.4 Government-Furnished Ground System Interface Equipment

3.2.2.5 Observatory/Mission Payload/Launch Vehicle Interface

3.2.3 Design and Performance Verification

3.2.4 Appendix A Assessment

3.2.5 Technical Performance Measures

3.2.6 Orbital Debris Assessment Report Inputs

3.2.7 Space Environment Assessments

3.2.8 Design Reference Case Validation

3.2.9 Trend Data

3.2.10 Systems Analyses

3.2.11 Dynamics Model Validation

3.2.12 Reserved

3.2.13 Fault Management

3.3 Mission Assurance

3.3.1 Flight Heritage/Previously Qualified Inherited Hardware and Software

3.4 LNext Spacecraft Design

3.4.1 Design Engineering

3.4.2 Structure Design and Analysis

3.4.3 Mechanisms Design

3.4.4 Thermal Design

3.4.5 Command and Data Handling Design

3.4.6 Field Programmable Gate Array (FPGA) Design, Development and Verification

3.4.7 Electrical, Harness and Cabling Design

3.4.8 Power Design

3.4.9 Propulsion Design

3.4.10 Guidance, Navigation, and Control (GN&C) Design

3.4.11 Instrument-Mounted Spacecraft Components (IMSC)

3.4.12 Communications Design

3.4.12.1 Communication Security (COMSEC)

3.4.13 Software Engineering

viii

3.4.13.1 Software Definitions

3.4.13.2 Software Management

3.4.13.3 Commercial-Off-The-Shelf (COTS), Government-Off-The-Shelf (GOTS), Modified-Off-The-Shelf (MOTS) and Reused Software Components

3.4.13.4 Automatic Generation of Source Code

3.4.13.5 Software Bidirectional Tracing

3.4.13.6 Software Engineering Life Cycle Requirements

3.4.13.7 Software Requirements

3.4.13.8 Software Design

3.4.13.9 Software Implementation

3.4.13.10 Software Testing

3.4.13.11 Software Operations, Maintenance, and Retirement

3.4.13.12 Supporting Software Life Cycle

3.4.13.13 Software Configuration Management (SCM)

3.4.13.14 Software Risk Management

3.4.13.15 Software Peer Reviews and Inspections

3.4.14 Contamination Control Design

3.4.15 Spacecraft Integration and Test Planning

3.4.16 Observatory Integration and Test Planning

3.5 Spacecraft Implementation, Fabrication, Assembly and Test

3.5.1 Spacecraft Engineering

3.5.2 Spacecraft Safety and Mission Assurance

3.5.3 Structure Fabrication, Assembly, and Test

3.5.4 Mechanisms Fabrication, Assembly, and Test

3.5.5 Thermal Fabrication, Assembly, and Test

3.5.6 Command and Data Handling Fabrication, Assembly, and Test

3.5.7 Electrical, Harnessing, and Cabling Fabrication, Assembly, and Test

3.5.8 Power System Fabrication, Assembly, and Test

3.5.8.1 Solar Array Verification Requirements

3.5.8.2 Solar Array Panel Component-Level Testing

3.5.9 Propulsion System Fabrication, Assembly, and Test

3.5.10 GN&C and IMSC System Fabrication, Assembly, and Test

3.5.11 Communication System Fabrication, Assembly, and Test

3.5.12 Contamination Control Monitoring and Validation

3.5.13 Spacecraft Integration and Test

3.5.13.1 Landsat Next Project, Flight Operations Team, and Instrument Teams Participation in I&T

3.5.14 Observatory Integration and Test

3.5.14.1 Observatory Integration

3.5.14.2 Solar Array Observatory-Level Testing

3.5.14.3 Observatory Testing

3.5.15 Shipping and Handling of the LNext Observatories and GSE

3.5.16 LNext Spacecraft/Observatory Storage

3.6 Dispenser/Mission Payload Design, Fabrication and Testing

3.7 Ground Support Equipment and Test Units

ix

3.8 Simulators Fabrication, Assembly, Test, and Delivery

3.8.1 Spacecraft Simulators for Operations

3.8.2 Observatory Simulators for Operations

3.8.3 Spacecraft Software Simulator (SoftSim)

3.8.4 Instrument Mounted SC Components Simulator (IMSC Sim)

3.8.5 Command and Telemetry Simulation System (CTSS)

3.8.6 Launch Vehicle Interface Simulator (LVIS)

3.8.7 Software Development and Verification Facility (SDVF)

3.8.8 RF Suitcase Simulator

3.9 Flight Spares

3.10 Flight Operations Support

3.10.1 Flight Operations Procedure Support

3.10.2 Observatory Database

3.10.3 Training for Flight Operations Team

3.10.4 Mission Readiness Testing

3.10.4.1 Pre-MRT Testing

3.10.4.2 MRT Descriptions

3.10.4.3 Mission Operations Testing

3.10.4.4 Exercises

3.10.4.5 Mission Simulations

3.11 Launch Site and On-Orbit Support

3.11.1 Launch Site Operations Support

3.11.2 Launch Site Safety

3.11.3 Launch Site Operations Planning and Documentation

3.11.4 Launch Site Integration and Test

3.11.5 Launch Simulations

3.11.6 On-Orbit Performance Verification

3.11.7 On-Orbit Acceptance

3.11.8 Post On-Orbit Acceptance

3.12 Observatory Models

4.0 SPECIAL STUDIES

5.0 OPTIONS

5.1 Option for Spacecraft #4

5.1.1 Overview of the Work to be Performed:

5.1.1.1 Project Management

5.1.1.2 SC #4 Reviews

5.1.2 Systems Engineering Section:

5.1.3 Mission Assurance:

5.1.4 SC#4 Design:

5.1.5 Fabrication, Assembly, and Test

5.1.6 Flight Operations Support

5.1.7 Packaging Handling, Storage, and Transportation

5.1.8 Delivery, Checkout and Acceptance

5.1.9 Ground Support Equipment

5.1.10 Spares

x

5.1.11 Launch Site Requirements

APPENDIX A SC DESIGN RULES

APPENDIX B ABBREVIATIONS AND ACRONYMS

APPENDIX C DEFINITIONS

List of Figures Figure 2.4-1 Triplet Constellation Observatory Spacing On-Orbit Figure 2.4-2 Landsat Next Mission Architecture

List of Tables

Table 2.4.1-1 Mission Parameters Table 3.1.5.2-1 SC Systems Reviews Table 3.1.5.3-1 Additional Required Meetings/Reviews Table 3.1.5.3.4-1 Working Group Meetings Table 3.1.5.4-1 Mission-Level and Other LNext Reviews Table 3.5.14-1 TABLE Instrument Test Durations Table 3.10.4.2-1 MRT Descriptions

1.0 INTRODUCTION

This Statement of Work (SOW) defines the work requirements for the spacecraft (SC) implementation and observatory integration for the Landsat Next (LNext) Mission. This SOW specifies the activities to be performed in producing and delivering, inclusive of launch and on-orbit commissioning, to the National Aeronautics and Space Administration (NASA) three LNext Observatories that are identical in form, fit, and function, and selected options in support of the LNext Mission.

1.1 SCOPE

The Scope of Work encompasses all required effort from receipt of the LNext Spacecraft Contract Award, through the launch, delivery, on-orbit checkout, and acceptance of the observatories. Throughout this SOW, a product or service provided by the Government may be provided by a Civil Servant or a Project Support Contractor. In addition to deliverables listed herein, the Landsat Next Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), LNEXT-SC-PLAN-0055 lists data deliverables labeled as DIDs required to be provided during execution of the contract.

In accordance with the requirements of this document and all attachments to the contract, the Contractor furnishes or performs all necessary coordination, management, engineering, study, analysis, reports, personnel, facilities, services, and materials to design, fabricate, integrate, test, transport, and support launch and activation activities for the observatories developed under the LNext contract and the exercised options.

The Launch Readiness Dates (LRDs) are specified in the contract, with instruments delivered to the Spacecraft Contractor as specified in the Landsat Next Spacecraft Government Furnished Equipment (SC GFE) List, LNEXT-SC-LIST-0007. Instrument delivery is defined as the moment that the instrument and required Ground Support Equipment (GSE) have been received, have successfully completed any post-delivery verification, and are available to the Contractor for integration.

1.2 RELATED DOCUMENTATION

The documents listed in this section shall apply directly to the performance of the Contract.

These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract.

In the event of a conflict in requirements between this SOW and other documentation, the order of precedence shall be the Landsat Next Spacecraft Statement of Work (SOW), LNEXT-SC- SOW-0004, Landsat Next Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), Landsat Next Spacecraft Mission Assurance Requirements (SCMAR), LNEXT-SMA-REQ-0015, Landsat Next Spacecraft Requirements Document (SRD), LNEXT- SC-REQ-0011, Landsat Next Spacecraft Interface Requirements Document (SCIRD), LNEXT- SC-ICD-0002, Landsat Next Spacecraft to Ground Interface Requirements Document (SC-GND IRD), LNEXT-SC-ICD-0007, LNEXT-SC-PLAN-0055 and the Landsat Next Environmental Requirements Document (LNERD), LNEXT-SYS-REQ-0005 and any other Applicable Documents. Applicable documents take precedence over Reference documents.

The Contractor shall notify the Contracting Officer of any inconsistency, including all attachments and applicable documents.

Upon notification of an inconsistency, the Contracting Officer will clarify which requirement takes precedence, and may modify the contract as deemed appropriate.

1.2.1 Applicable Documents

These documents apply directly to the required performance of the contract and contain provisions that constitute requirements of this SOW to the degree specified in this document.

Document Number Title Revision Section Reference ITS-HBK-CUI Controlled Unclassified Information

Handbook

2.0.0 ALL

NASA FAR Supplement National Aeronautics and Space Administration Supplement to the Federal Acquisition Regulation (FAR) - NASA FAR Supplement

(NFS)

2015 Part 1846

NASA-STD-1006 Space System Protection Standard A ALL NASA-STD-5005 Standard for the Design and

Fabrication of Ground Support Equipment

D w/ CHANGE

ALL

NASA-STD-5017 Design and Development Requirements for Mechanisms

B ALL

NASA-STD-6030 Additive Manufacturing Requirements for Spaceflight Systems

- ALL

NASA-STD-6033 Additive Manufacturing Requirements for Equipment and Facility Control

- ALL

NASA-STD-8719.14 Process for Limiting Orbital Debris C ALL NASA-STD-8719.24 NASA Expendable Launch Vehicle

Payload Safety Requirements

A ALL

Annex to NASA-STD- 8719.24

Annex to NASA Expendable Launch Vehicle Payload Safety Requirements: Requirements Table

B ALL

NASA-STD-8739.4 Workmanship Standard for Crimping, Interconnecting Cables, Harnesses, and Wiring

A w/Change 2 ALL

NASA-STD-8739.8 Software Assurance and Software Safety Standard

A ALL

NASA-STD-8739.8 Software Assurance and Software Safety

B ALL

NF 533M NASA Monthly Contractor Financial Management Report

N/A ALL

NPD 1440.6 NASA Records Management I ALL NPR 1040.1 NASA Continuity of Operations

(COOP) Planning Procedural Requirements

- w/ CHANGE 3 ALL

NPR 1600.1 NASA Security Program Procedural Requirements

A ALL

Document Number Title Revision Section Reference NPR 1600.6 Communications Security

(COMSEC)

A ALL

NPR 1620.3 Physical Security Requirements for NASA Facilities and Property

B ALL

NPR 2190.1 NASA Export Control Program C ALL NPR 2180.7 Controlled Unclassified Information - ALL NPR 2810.1 Security of Information and

Information Systems

F ALL

NPR 7120.5 NASA Space Flight Program and Project Management Requirements

F w/Change 2 ALL

NPR 7150.2 NASA Software Engineering Requirements

D ALL

NPR 8621.1 NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping

D ALL

NPR 8715.6 NASA Procedural Requirements for Orbital Debris Mitigation

E TBD

400-PG-1410.2.1 Configuration Control F ALL 500-PG-8700.2.7 Design of Space Flight Field

Programmable Gate Arrays

B ALL

500-PG-8700.2.8 Field Programmable Gate Array (FPGA) Development Methodology

A ALL

GPR 5340.2 Documentation and Control of Process Nonconformances

L ALL

GPR 7123.1 Systems Engineering C TBD GPR 8621.4 GSFC Mishap/Close Call Preparation and Response

C ALL

GSFC-STD-1001 Criteria for Flight and Flight Support System Lifecycle Reviews

A ALL

48 CFR § 9.5 Code of Federal Regulations (CFR), Federal Acquisition Regulations (FAR), Organizational and Consultant Conflicts of Interest

N/A Part 12 and 46

ANSI/ESD S20.20 Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)

2021 ALL

AIAA S-111A-2014 Qualification and Quality Requirements for Space Solar Cells

2014 ALL

AIAA S-11A-2014/A1-

Qualification and Quality Requirements for Space Solar Cells – Amendment 1

2019 ALL

AIAA S112A-2013 Qualification and Quality Requirements for Electrical Components on Space Solar Panels

2013 ALL

AIAA S-112A-2013/A1-

Qualification and Quality Requirements for Electrical Components on Space Solar Panels – Amendment 1

2019 ALL

MIL-STD-461 Requirements for the Control of Electromagnetic Interference

G ALL

Document Number Title Revision Section Reference Characteristics of Subsystems and Equipment

FIPS PUB 140-3 Security Requirements for Cryptographic Modules

N/A ALL

NIST SP 800-37 Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy

2 Appendix B and Appendix G

NIST SP 800-53 Security and Privacy Controls for Information Systems and Organizations

5 ALL

NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

2 ALL

In this document, citations are assumed to be the latest version unless otherwise noted.

This document table was generated from the Landsat Next Common Reference and Applicable Documents List (LNEXT-MGMT-DESC-0008) Rev E.

1.2.2 Reference Documents

These documents contain information relating to the work required by this SOW.

Document Number Title NASA/TM-20210018053 Avionics Radiation Hardness Assurance (RHA) Guideline, R.F. Hodson, J.A. Pellish, R.A. Austin, M.J. Campola, R.L.

Landbury, K.A. LaBel, G.R. Allen, R. Gaza and E.M. Willis

NPD 7120.4 NASA Engineering and Program/Project Management Policy GSFC-STD-8012 Bulk Security Standard For Spacecraft Communication In this document, citations are assumed to be the latest version unless otherwise noted.

This document table was generated from the Landsat Next Common Reference and Applicable Documents List (LNEXT-MGMT-DESC-0008) Rev E.

1.2.3 Project Applicable Documents

Document Number Title LNEXT-LS-ICD-0008 Landsat Next Launch Services Interface Control Document

(LSICD)

LNEXT-LS-ICD-0009 Landsat Next Mission Payload to Launch Services Interface

Description Document (LNext-LS IDD) LNEXT-MGMT-PLAN-0004 Landsat Next Configuration Management Procedures and

Guidelines LNEXT-MGMT-PLAN-0039 Landsat Next Key Management Plan LNEXT-MGMT-SPEC-0001 Landsat Next Key Specification (KS) LNEXT-SC-ICD-0002 Landsat Next Spacecraft Interface Requirements Document

(SCIRD)

LNEXT-SC-ICD-0004 Landsat Next Spacecraft to Ground Interface Control

Document (SC-GND ICD) LNEXT-SC-ICD-0005 Landsat Next Spacecraft to Landsat Next Instrument Suite

(LandIS) Interface Control Document (SC-LandIS ICD) LNEXT-SC-ICD-0007 Landsat Next Spacecraft to Ground Interface Requirements

Document (SC-GND IRD) LNEXT-SC-LIST-0008 Landsat Next Spacecraft Deliverable Items List (SC DIL) LNEXT-SC-PLAN-0055 Landsat Next Spacecraft Contract Data Requirements List

(CDRL) and Data Item Descriptions (DID)

Document Number Title LNEXT-SC-REQ-0011 Landsat Next Spacecraft Requirements Document (SRD) LNEXT-SC-REQ-0012 Landsat Next Spacecraft Simulator Requirements Document

(SC Sim RD) LNEXT-SMA-PLAN-0067 Landsat Next Spacecraft Safety and Mission Assurance

Surveillance Plan (SC SMASP) LNEXT-SMA-REQ-0015 Landsat Next Spacecraft Mission Assurance Requirements

(SCMAR)

LNEXT-SYS-PLAN-0007 Landsat Next Mission Operations Concept (Ops Con)

Document LNEXT-SYS-PLAN-0027 Landsat Next Project Protection Plan (PPP) LNEXT-SYS-PLAN-0070 Landsat Next Communications Security (COMSEC) Plan

(CSP)

LNEXT-SYS-REQ-0005 Landsat Next Environmental Requirements Document

(LNERD)

LNEXT-SYS-REQ-0009 Landsat Next Space Environments Requirements Document

(LSERD)

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

Definition TBD Launch Services Interface Requirements Document (LSIRD) In this document, citations are assumed to be the latest version unless otherwise noted.

This document table was generated from the Landsat Next Common Reference and Applicable Documents List (LNEXT-MGMT-DESC-0008) Rev E.

2.0 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 and coastal regions 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 (formally named Landsat Data Continuity Mission, LDCM) in February 2013, and during the development of Landsat 9, the United States Geological Survey (USGS) and the National Aeronautics and Space Administration (NASA) recognized the need to assemble a team of experts from within both agencies to evaluate and 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 July 2018, 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 surfaces and coastal regions held in the National Satellite Land Remote Sensing Data Archive at the 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 and coastal regions 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 the USGS, with NASA providing the space and launch segments and the USGS providing the ground system (GS), providing the longest continuous global record of the Earth’s land surface and coastal regions.

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 renamed Landsat 1) in 1972.

2.3 MISSION OBJECTIVES

Landsat Next has these major mission objectives:

· Collect and archive moderate resolution Visible to Shortwave-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; all of which permit scientific studies, management of land cover and land use change, along with associated inland and coastal water resources, over multi-decadal periods.

· Ensure Landsat Next is responsive to documented emerging user needs and applications as characterized by periodic assessment, currently the User Needs for the SLI Program July 2018, Release 2.0, and identified by the operational requirements for acquisition, processing, archiving, and distribution of Earth’s image data to the United States Government and other users.

· Distribute Landsat Next data products to the public freely on a nondiscriminatory basis.

2.4 MISSION IMPLEMENTATION

The Landsat Next mission is a constellation of three identical Observatories, referred to as “triplets” with equal orbit spacing. Each observatory images the full swath required to achieve global coverage, with the use of three observatories used to reduce revisit time for any scene.

The Figure below illustrates the 120 degree separation of the Observatories.

Figure 2.4-1 Triplet Constellation Observatory Spacing On-Orbit

This selected architecture of three observatories has been endorsed by the Landsat user communities and improves all temporal, spectral, and spatial capabilities by approximately twofold, while maintaining the historical Landsat data continuity. With all three observatories operating, imaging revisit will be every six (6) days, at the equator.

Each agency has specific responsibilities and will deliver major elements to the overall mission.

NASA will provide the Space and Launch Segments of Landsat Next and the USGS will provide the Ground System and Operations. NASA/Goddard Space Flight Center (GSFC) will provide overall Landsat Next project management, mission system engineering and mission assurance during development and will transition the mission to USGS for science operations following on-orbit commissioning. Each agency in addition to specific responsibilities, will deliver the three major segments to the overall mission.

The three segments are the Space Segment (SS), the Ground Segment (GS), and the Launch Services Segment (LSS). They are described in more detail in the following sections and shown in the Landsat Next Operations Concept below.

Figure 2.4-2 Landsat Next Mission Architecture

(Generated from Landsat Next Common Mission Architecture Diagram LNEXT-SYS-DESC-0022 Rev A)

2.4.1 Space Segment

NASA/GSFC will provide the Space Segment via competitive procurements for the science instrument suite and the spacecraft bus. The Space Segment will consist of a constellation of three observatories flying in sun-synchronous, polar orbits at 653km altitude, each with nominally identical spacecraft and instrument suites. The three observatories will be launched on a single launch vehicle with a single dispenser provided by the spacecraft bus provider. The observatories will be transitioned to their final orbit alignments during commissioning. In aggregate, they provide a six-day ground repeat period at the equator. The spacecraft and instrument will be Class C. The Mission Class B is accomplished by providing redundancy at the Observatory level. The overall mission parameters needed to achieve global coverage are shown below in the Mission Parameters Table.

Table 2.4.1-1 Mission Parameters

A single Observatory will consist of the spacecraft and imaging sensors, referred to as the Landsat Next Instrument Suite (LandIS). Each observatory operates independently, and unique coordination is conducted by the ground as the observatories do not communicate with each other directly.

The LandIS instrument suite is a whiskbroom scanner which provides 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 164km on a ground track defined by a world-wide reference system known as WRS-3. The instrument suite will be capable of acquiring raw detector data for all spectral bands within 15 second to minimize the illumination changes within the observations. Data will be generated at a rate no greater than 1.8 Gbps. The LandIS provides internal calibration sources such as blackbody, a space port, stim lamps and solar diffuser. LandIS instrument suite provides compression prior to packaging the data for transfer to the spacecraft storage.

The Space Segment will also provide simulators for mission, ground system and interface testing during the development phase of the mission and in support of long-term maintenance of systems. Space Segment simulator types include spacecraft, instrument suite, spacecraft and the LandIS instrument suite interface, launch vehicle interface and a combination of simulators integrated to be an Observatory. These simulators will have varying fidelity and capabilities to meet the mission needs.

2.4.2 Ground Segment

The Landsat Ground Segment consists of the Ground System 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), GSFC Conjunction Assessment and Risk Analysis (CARA) and its Flight Dynamics Facility, along with other external interfaces.

The Landsat Next MOC functionality will be used for command and control, health and status monitoring, orbit and attitude maintenance, performance analysis, onboard memory management, and flight and ground software maintenance. The MOC will support onboard autonomy for mission planning and scheduling. The MOC ingests, processes and archives data delivered via the GN. The Landsat Next Flight Operations Team (FOT) located at the MOC performs these functions and is responsible for monitoring the Observatories, detecting, investigating and resolving spacecraft anomalies and monitoring the instrument image collections and special image collections.

The GN provides geographically dispersed ground station resources for mission execution; it includes the Landsat Ground Network (LGN) and a wideband data routing capability to the Landsat Cloud. The LGN provides communication capability for each observatory of the constellation for commanding and housekeeping data via the S-Band and will receive science mission data from each observatory over a Ka-band downlink. The LGN is used to transfer commands and receive telemetry from each Observatory within the constellation and deliver it to the MOC.

The DPAS ingests, processes, and archives science data returned from each satellite via the GN.

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 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 support Landsat Next mission readiness activities.

2.4.3 Launch Segment

The Launch Segment will provide the assets and services associated with the Launch Vehicle (LV) and the Mission Payload-to-LV integration. The Launch Segment will include the LV; all Launch Vehicle-Ground Support Equipment (LV-GSE), property, and facilities to integrate the Mission Payload to the LV and verify its integration; and perform prelaunch testing with ground-based functions. The launch vehicle and launch site have not been specified and will not be until closer to Mission Phase C. The three observatories comprising the Landsat Next Mission Payload, including the Observatory dispenser, will be launched together on the same launch vehicle.

The candidate launch vehicles for the launch of the Landsat Next Mission Payload are the Falcon 9 Full Thrust, the United Launch Alliance Vulcan Centaur and the Blue Origin New Glenn. This list will be updated in the future to reflect additions and deletions to the candidate launch vehicles presently available under the NASA Launch Services II Contract.

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

3.0 WORK TO BE PERFORMED

The following sections, along with the Landsat Next Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), LNEXT-SC-PLAN-0055, describe the specific work to be accomplished by the Spacecraft Contractor. In accordance with the requirements of this document including Appendix A, the contract, all associated requirements documents, and the other attachments and applicable documents to this contract, the Contractor shall provide the effort and resources that include, but are not limited to, personnel, subject matter expertise, materials, equipment, and facilities necessary for the successful and on-time implementation of the design, analysis, development, fabrication, assembly, integration, test, engineering data analyses, verification, calibration, qualification, and delivery of three LNext spacecraft.

The Contractor shall also provide the personnel, materials, equipment, and facilities necessary to integrate the LandIS instruments, test the LNext Observatories, support mission-level activities, support launch vehicle integration and on-orbit commissioning of the LNext Constellation.

The Contractor shall also perform special studies.

The Contractor shall deliver to the Government three (3) observatories and a dispenser that are fully qualified and have demonstrated compliant and reliable operation in accordance with the requirements of this contract.

The requirements stated within this document shall apply to each copy or instantiation of the LNext spacecraft and observatory as appropriate.

3.1 PROJECT MANAGEMENT (PM)

The Contractor shall provide a Project Management (PM) function that is responsible for control and coordination of all activities on the LNext Contract including the design, study, trade, and analyses tasks relating to the development, implementation, fabrication, integration, characterization, test, qualification, and operation of the observatories.

The Contractor’s project management shall report to a level of company management appropriate to ensure prompt resolution of all problems.

The Contractor shall provide for, and facilitate the use of, this Project Management function to provide to NASA periodic reporting (within 10 business days of period closing), timely (within 24 hours) insight into issues, a program of formal and informal reviews, and on-going insight into the technical, quality, safety, security, and programmatic performance and status of all of the Contractor's responsibilities and activities performed under the Contract.

The Contractor shall prepare and deliver a comprehensive Program Management Plan in accordance with CDRL LNext-PM-02.

The Contractor shall prepare and deliver an Organization Conflict of Interest (OCI) Plan in accordance with CDRL LNext-PM-06.

The Contractor shall review the OCI Avoidance Plan annually and update as necessary.

The Contractor shall provide a Work Breakdown Structure in accordance with CDRL LNext-

PM-11.

The Contractor shall also perform all work necessary to successfully implement and complete the following project functions: Project Security, Property Management, Environmental Project Compliance, Export Administration Regulations (EAR), Controlled Unclassified Information (CUI), and International Traffic In Arms Regulation (ITAR) compliance.

The Contractor shall document security requirements and Export Control requirements in accordance with CDRL LNext-PM-04, Program Security Plan and in compliance with NASA Space Flight Program and Project Management Requirements, NPR 7120.5 and NASA Export Control Program, NPR 2190.1.

The Contractor shall comply with NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping, NPR 8621.1, Documentation and Control of Process Nonconformances, GPR 5340.2, GSFC Mishap/Close Call Preparation and Response, GPR 8621.4 and Anomaly Notification System for Code 400 Programs and Projects, 400 PG

8621.1.1 for mishaps, close calls and non-conformances.

The Contractor shall establish and implement a system to control, protect, preserve, and maintain all Government property.

3.1.1 Government Insight and Surveillance

The Contractor shall provide to the Government reporting and real-time insight into project status, as well as technical and programmatic performance information on all the Contractor’s responsibilities and activities performed under the Contract.

The Contractor shall adhere to the surveillance plan for LNext as defined in the Landsat Next Spacecraft Safety and Mission Assurance Surveillance Plan (SC SMASP), LNEXT-SMA- PLAN-0067. Should the Government identify non-compliance with requirements, a difference in interpretation of test results or in requirements, the Government will take action to ensure compliance.

The Contractor shall notify the Government Contracting Officer, the Government resident office or the appropriate Government operations organization or personnel of meetings, reviews, operations or tests at least 48 hours in advance to permit meaningful Government participation for activities that do not require travel.

The Contractor shall provide at least one week notice for activities which require Government travel.

The Contractor shall grant access for NASA mission assurance and other representatives to conduct audits, assessments, surveys and Government Mandatory Inspection Points (GMIPs) as outlined in the Landsat Next Spacecraft Safety and Mission Assurance Surveillance Plan (SC SMASP), LNEXT-SMA-PLAN-0067, upon notice or as otherwise requested by the Government.

3.1.2 Control of Sensitive Information

The Contractor’s information management systems and processes shall be compliant with the latest versions of Minimum Security Requirements for Federal Information and Information Systems, FIPS 200, NASA Records Management, NPD 1440.6, and Controlled Unclassified Information, NPR 2180.7.

3.1.3 Non-Disclosure Agreements

The Contractor is responsible for executing any Non-Disclosure Agreements the Contractor deems necessary to enable information sharing among the Landsat Next participating product and support Contractors and Subcontractors. Any other formal agreements between the Contractor and other Landsat Next participating Contractors relevant to this, as it pertains to this contract, will be subject to Government review.

The Contractor is responsible for establishing Technical Assistance Agreements (TAAs) as required to implement the SC and instrument integration and verification.

3.1.4 Documentation

The Contractor shall develop, produce, deliver, and maintain all documentation required in accordance with Landsat Next Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), LNEXT-SC-PLAN-0055.

All documentation, data, and analyses generated for or applicable to, the SC and dispenser design, fabrication, and test, whether formal or informal, deliverable or non-deliverable shall be made available to the Government and Government support Contractors with appropriate Non- Disclosure Agreements (NDAs) in place upon request. Formats for data exchange will be coordinated in the appropriate working groups.

This information shall be provided electronically, if possible, through a Contractor-provided web portal which complies with ITAR, EAR and CUI requirements. Formats for data exchange and other guidance will be coordinated in the appropriate working groups.

The Contractor shall mark all data items containing Controlled Unclassified Information (CUI) in compliance with the latest version of the Controlled Unclassified Information Handbook, ITS-

HBK-CUI.

The Contractor shall ensure that Export control markings are specific and identifies what category of export-controlled information is in the document/deliverable. The Landsat Next project will provide guidance on what Export Control categories apply.

The Contractor shall provide Engineering Drawings, the Drawings Tree, the Subsystem Functional Block Diagram, the System Schematics and the System Grounding diagram in accordance with CDRL LNEXT-SE-26.

The Contractor shall clearly indicate which drawings and models are as-designed and as-built.

The latest revisions of all documents cited within this document will be provided by the Government.

3.1.5 Reviews

The Contractor shall conduct reviews and provide for timely reporting of project status to the Government.

This shall include discussions on problem areas and timely transfer of technical information to the Government, including progress and status on achieving major project milestones and materials required by the Government for systems review and evaluation.

The Contractor shall conduct major reviews as outlined in the following sections. A Major Review is a meeting held at each major implementation milestone, where information is formally presented to a panel of Government experts and external independent reviewers. These experts and reviewers have the responsibility and authority to recommend next steps such as continuing as planned, revising the plan, taking corrective actions, providing more information, etc. All SC and Observatory Reviews in Section 3.1.5.2 and the Mission Reviews in Section 3.1.5.4 are Major Reviews. Major Reviews can involve up to 40 Government representatives and run for up to four days. Formal action items are logged and tracked by the Project Office. Technical direction may be forthcoming from a Major Review.

If any deficiencies are found at the reviews, the Contractor shall be required to develop a corrective action plan. The Contractor may proceed prior to approval of the action plan at its own risk.

3.1.5.1 Major Reviews

All major reviews will be convened, and review boards appointed and chaired, by the Government.

The Contractor shall demonstrate compliance with the review success criteria document in, Criteria for Flight and Flight Support System Lifecycle Reviews, GSFC-STD-1001, as applicable to spaceflight.

3.1.5.2 Spacecraft Reviews

The Contractor shall provide technical and management support at the baseline set of SC Systems Reviews shown in Table 3.1.5.2-1.

The Contractor shall coordinate an agenda for each Spacecraft/Observatory Review with the Government no later than six weeks prior to the review.

The Contractor shall support a dry run, no later than two weeks prior to the review, of the System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Spacecraft Instrument Integration Readiness Review (SIIRR), Pre-Environmental Review (PER) and On-Orbit Acceptance Review (OAR) at the Contractor’s facility.

The Contractor shall conduct an assessment prior to the beginning of the second and the beginning of the third spacecraft builds to identify any design changes from the previous spacecraft build(s).

If there has been a design change, the contractor shall conduct a design review with the Government that covers the changes and their impacts including at the system level.

Table 3.1.5.2-1 SC Systems Reviews

SC Systems Reviews* When Length (Days)

Location CDRL Deliverable

SC System Requirements Review

(SRR)

Award + TBP mos

3 Contractor’s Facility

LNEXT-RE-01

SC Preliminary Design Review (PDR) Award + TBP mos

4 Contractor’s Facility

LNEXT-RE-02

SC Critical Design Review (CDR) Award + TBP mos

4 Contractor’s Facility

LNEXT-RE-03

SC Bus Integration Readiness Review SC Bus I&T Start – 1 mo

1 Contractor’s Facility

LNEXT-RE-10

SC - Instrument Integration Readiness Review (SIIRR)* (for each observatory and dispenser)

TBP 2 Contractor’s Facility

LNEXT-RE-04

Observatory Pre-Environmental Review (PER)** (for each observatory and dispenser)

Test – 1 mo 3 Contractor’s Facility

LNEXT-RE-05

Observatory Pre-Shipment Review (PSR) (for each observatory)

Launch -90 days

3 Contractor’s Facility

LNEXT-RE-06

On-orbit Acceptance Review (OAR) Launch + 100 days

2 GSFC LNEXT-RE-07

Integrated Baseline Review (IBR) Award + 180 days

1 GSFC LNEXT-RE-09

* The SIIRR shall be held no later than two months prior to each instrument integration on the corresponding spacecraft.

** The PER shall be held no later than one month prior to planned exposure to the first environment, but after completion of comprehensive observatory ambient testing for each observatory.

The Contractor shall host and provide data for these reviews according to the CDRL delivery schedule. The Government will chair these reviews and provide Requests for Action (RFAs) and Advisories to the Contractor for response. The PDR, CDR, PER and PSR will be additionally attended by a Government Standing Review Board (SRB) and/or the Goddard System Review Team (GSRT).

The Contractor shall provide to the Government, for approval, formal responses to all assigned RFAs and Advisories.

Each review shall be considered complete when:

1. The Government chairperson for the review provides notice that the criteria for successful completion have been satisfactorily met.

2. All RFAs deemed "critical" by the chairperson have been closed to the Government’s satisfaction.

3. All CDRLs required at or prior to that review have been delivered and found to be acceptable by the Government. Acceptance by the Government may require that all

CDRL item modification recommendations resulting from Government “Review” or required for Government “Approval” have been incorporated by the Contractor. The criticality of RFAs will be determined and documented by the review chairperson when submitted to the Contractor.

3.1.5.3 Additional Required Meetings and Reviews

In addition to the baseline set of SC Systems Reviews shown in Table 3.1.5.2-1, the Contractor shall support the meetings shown in Table 3.1.5.3-1.

Table 3.1.5.3-1 Additional Required Meetings/Reviews

Review Name When Length

(Days) Location CDRL

Deliverable SC Kick-Off Award + 1 month, determined at Award 2 Contractor

Facility/Online N/A

Weekly Status Telecon Weekly 0.2 Online N/A Working Group Meetings

As defined in Table 3.1.5.3.2-1

As defined in Table

3.1.5.3.2-1

As defined in Table 3.1.5.3.2-1

N/A

Monthly Program Status Reviews

Monthly 1 Contractor Facility LNext-PM-01

Technical Interchange Meetings

12 per year 2 Contractor Facility or GSFC/Online

N/A

Peer Reviews As required per Section 3.1.5.3.4

1 Contractor Facility/Online

N/A

SC Test Readiness Reviews

1 week before test 0.5 Contractor facility/Online N/A

Observatory Test Readiness Reviews

1 week before test 1 Contractor Facility/Online

N/A

3.1.5.3.1 Spacecraft Kickoff Meeting

The Contractor shall host a SC Kickoff meeting to present the concept overview, plans, schedules, and activities required to meet the contract.

The agenda and information to be presented shall be coordinated with the Government no less than 14 days prior to the meeting and will largely be based on the Contractor’s offer and updated to reflect any changes since the offer submission, including any directed changes.

The SC Kickoff shall also include the functional overview of the proposed bus, overview of the Mission Data Management concept, overview of flight software tables (description of each, anticipated types, number, and size), database format description.

The SC Kickoff shall also include compliance matrices for the Landsat Next Spacecraft Statement of Work (SC SOW), LNEXT-SC-SOW-0004, Landsat Next Spacecraft Requirements Document (SRD), LNEXT-SC-REQ-0011, Landsat Next Spacecraft Mission Assurance Requirements (SCMAR), LNEXT-SMA-REQ-0015, the Landsat Next Spacecraft Interface Requirements Document (SCIRD), LNEXT-SC-ICD-0002, and Landsat Next Environmental Requirements Document (LNERD), LNEXT-SYS-REQ-0005 reflecting the planned compliance and a discussion of any requirements questions/issues.

3.1.5.3.2 Weekly Status Teleconference Requirements

The Contractor shall support Weekly Status virtual meeting throughout the performance of the contract.

If agreed to by the Government, a Weekly Status will not be required during the week that a Monthly Project Status Review (MPSR) is held. The Contractor shall address the following topics as a minimum in the weekly teleconferences:

1. Activities, plans, and the progress against those plans

2. Review of planned upcoming meetings and events

3. Up-to date (working-level) rolling wave mission schedule

4. Up-to date rolling wave subsystem schedule on critical paths

5. Any communications and correspondence related to the implementation, including Engineering Review Board activities

6. Descriptions and status of technical problems and the resolutions

7. Any anomalies and problem reports generated since the last teleconference

8. Issues and action items

The Government has identified several Working Groups to address specific aspects of LNext. A Working Group is a cross-organizational team that meets periodically to address specific mission functions or implementation processes. No technical direction is given at a Working Group meeting.