LNEXT-SC-SOW-0006 Landsat Next Spacecraft Statement of Work (SC SOW) Rev - Draft 7 20251203 reqt numbers in paragraph.pdf

DOORS EXPORT

National Aeronautics and Space Administration

Goddard Space Flight Center Greenbelt, Maryland

DRAFT

LNEXT-SC-SOW-0006, Revision - Landsat Next, Code 426

Landsat Next Spacecraft Statement of Work

(SC SOW)

Draft 7: December 3, 2025

SC SOW DRAFT LNEXT-SC-SOW-0006 Revision -ii

Landsat Next Spacecraft Statement of Work (SC SOW) Signature/Approval Page 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 Change History will be provided by CM prior to release v

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

Name/Org.

Due Date 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 .................................................................................................................... VIII

LIST OF TABLES ...................................................................................................................... VIII

1.0 INTRODUCTION

1.1 Scope

1.2 Related Documentation

1.2.1 Applicable Documents

1.2.2 Reference 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 DEFINITIONS

4.0 WORK TO BE PERFORMED

4.1 Landsat Next Spacecraft

4.1.1 Spacecraft Development, Integration, and Test

4.2 Landsat Next Observatory

4.2.1 Observatory I&T

4.2.2 Instrument Accommodation and Integration

4.2.3 Instrument Interface Validation and Instrument Special Tests

4.2.4 RF Compatibility Testing

4.2.5 End to End Mission Readiness Testing

4.2.6 Government Involvement and Insight

4.2.6.1 Ground System Interaction

4.3 Landsat Next Mission Payload

4.3.1 Mission Payload Development, Integration, and Test

4.4 Landsat Next Simulators

4.4.1 Command and Telemetry Simulation System (CTSS)

4.4.2 Spacecraft Software Simulator (Softsim)

4.4.3 Observatory Operational Simulators (OOps)

4.4.4 Launch Vehicle Interface Simulator (LVIS)

vii

4.4.5 RF Suitcase

4.5 Mission Payload Shipment to Launch Site

4.6 Launch Support

4.6.1 Launch Site Operations

4.6.2 Launch Site Integration and Test

4.6.3 Launch Simulations

4.7 Commissioning and On-Orbit Support

4.7.1 Flight Operations Readiness, Databases, and Procedures

4.7.2 Flight Operations Training

4.7.3 Mission Simulations

4.7.4 On-Orbit Performance Validation

4.7.5 On-Orbit Acceptance

4.7.6 Post Acceptance Support

4.8 Critical Interfaces

4.9 Safety and Mission Assurance

4.9.1 Safety and Mission Assurance Program

4.9.2 Surveillance

4.9.3 Non-Conformance & Anomaly Review Board

4.9.4 System Safety

4.9.4.1 General Requirements

4.9.4.2 Lifting Device Safety

4.9.4.3 Mishap Reporting and Investigation

4.9.4.4 System Safety Deliverables

4.9.5 Reliability

4.9.5.1 Reliability Program Plan

4.9.5.2 Fault Tolerance and Protection

4.9.5.3 Reliability Design Margins

4.9.6 Software Assurance

4.9.7 Workmanship

4.9.7.1 Processes and Standards

4.9.7.2 Printed Circuit Boards

4.9.8 EEE Parts

4.9.8.1 Master Parts List

4.9.9 Materials and Processes

4.9.10 Contamination Control

4.9.11 Metrology and Calibration

4.9.12 GIDEP Alerts and Problem Advisoriers

4.10 Project Management

4.10.1 Reporting

4.10.2 Documentation

4.10.3 Risk Management

4.10.4 Resource Management

4.10.5 Configuration Management

4.10.6 Government Residence Office

4.10.7 Reviews

4.10.7.1 Milestone Reviews

viii

4.10.7.2 Spacecraft and Observatory Reviews

4.10.7.3 Engineering Peer Reviews

4.10.8 Security

4.10.8.1 Communications Security (COMSEC)

4.10.9 Special Studies

4.10.10 Flight Spares

4.10.11 Working Groups

4.11 Systems Engineering

4.11.1 Requirements Management

4.11.2 TPMs and Trended Parameters Tracking and Reporting

4.11.3 Analyses and Modeling

4.11.4 Interface Management

4.11.4.1 Launch Services Interface Management & Support

4.11.5 Performance Verification

4.11.6 Design Reference Case Validation

4.11.7 Specialty Engineering

4.11.7.1 Micro-Meteoroid and Orbital Debris Assessment

4.11.7.2 Space Environments

4.11.7.3 Software Engineering

4.11.7.4 Instrument Mounted Spacecraft Components (IMSC)

4.11.7.5 Contamination Control

5.0 APPENDIX A ABBREVIATIONS AND ACRONYMS

6.0 APPENDIX B 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 1.2.1-1 Project Requirements Table 1.2.1-2 Institutional Requirements and Standards Table 1.2.2-1 Project Reference Requirements Table 1.2.2-2 Institutional Reference Requirements and Standards Table 2.4.1-1 Mission Parameters Table 4.2.2-1 Instrument Functional Tests Table 4.2.5-1 MRT Descriptions Table 4.7.3-1 Mission Simulations Table 4.8-1 Mission Critical Interfaces Table 4.10.7.1-1 Mission Milestone Reviews Table 4.10.7.2-1 Spacecraft and Observatory Reviews Table 4.11.4-1 Interface Control Documents

1.0 INTRODUCTION

This Statement of Work (SOW) defines the work and quality assurance 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 development, integration, test, 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-REQ-0029 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

SCSOW-8 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.

SCSOW-9 In the event of a conflict in requirements between this SOW and other documentation, the order of precedence shall be the following:

1. Landsat Next Spacecraft Statement of Work (SOW), LNEXT-SC-SOW-0006

2. Landsat Next Spacecraft Contract Requirements Document List (CDRL) and Data Item

Descriptions (DID), LNEXT-SC-REQ-0029

3. Landsat Next Spacecraft Requirements Document (SRD), LNEXT-SC-REQ-0011

4. Landsat Next Spacecraft Interface Requirements Document (SCIRD), LNEXT-SC-ICD-

5. Landsat Next Spacecraft to Ground Interface Requirements Document (SC-GND IRD), LNEXT-SC-ICD-0007

6. Landsat Next Spacecraft Environmental Requirements Document (SCERD), LNEXT-

SC-REQ-0031,

7. Landsat Next Space Environments Requirements Document (LSERD), LNEXT-SYS- REQ-0009 from SCSOW-587

8. Any other Applicable Documents.

Applicable documents take precedence over Reference documents. Note that reference documents are provided for informational purposes only and contain no requirements.

SCSOW-10 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

Table 1.2.1-1 lists the Landsat Next requirements documents. Table 1.2.1-2 lists NASA institutional requirements and standards that are referenced in this SOW. 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.

Table 1.2.1-1 Project Requirements

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-0039 Landsat Next Key Management Plan LNEXT-SC-ICD-0002 Landsat Next Spacecraft Interface Requirements Document

(SC IRD)

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-REQ-0011 Landsat Next Spacecraft Requirements Document (SRD) LNEXT-SC-REQ-0012 Landsat Next Spacecraft Simulator Requirements Document

(SC Sim RD) LNEXT-SC-REQ-0031 Landsat Next Spacecraft Environmental Requirements

Document (SCERD) LNEXT-SYS-REQ-0009 Landsat Next Space Environments Requirements Document

(LSERD)

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

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

Table 1.2.1-2 Institutional Requirements and Standards

Document Number Title Revision Section Reference EEE-INST-002 Instructions for EEE Parts Selection, Screening, Qualification, and Derating

- TBD

NASA-STD-1006 Space System Protection Standard A ALL NASA-STD-8719.14 Process for Limiting Orbital Debris C ALL Annex to NASA-STD- 8719.24

Annex to NASA Expendable Launch Vehicle Payload Safety Requirements:

Requirements Table

B w/ Change 1 TBD

FIPS PUB 140-3 Security Requirements for Cryptographic Modules

N/A 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

1.2.2 Reference Documents

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

Table 1.2.2-1 Project Reference Requirements

NASA-STD-8719.9 Lifting Standard NASA-STD-8739.8 Software Assurance and Software Safety NPR 7150.2 NASA Software Engineering Requirements GSFC-STD-1001 Criteria for Flight and Flight Support System Lifecycle

Reviews AS9100 Quality Systems - Aerospace - Model for Quality Assurance in

Design, Development, Production, Installation and Servicing 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

Table 1.2.2-2 Institutional Reference Requirements and Standards

NASA-STD-8719.9 Lifting Standard NASA-STD-8739.8 Software Assurance and Software Safety NPR 7150.2 NASA Software Engineering Requirements GSFC-STD-1001 Criteria for Flight and Flight Support System Lifecycle

Reviews AS9100 Quality Systems - Aerospace - Model for Quality Assurance in

Design, Development, Production, Installation and Servicing 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

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 DEFINITIONS

Available Upon Request:

• Not required to be delivered, unless requested by the Government

• Used to provide the Government with insight Information (I):

• Submitted for government information only

• No formal review or approval required

• No expectation that contractor will address any feedback provided

• Used for routine documentation or reference materials Review (R):

• Government reviews and may provide comments

• The contractor may continue to proceed while the delivery is being reviewed by the Government

• Contractor should consider comments but formal approval is not required Document be finalized after addressing the Government identified significant concerns.

• Used for important but less critical documents Approve (A):

• Government formally reviews and approves the deliverable

• Contractor must address all government comments/concerns

• Formal acceptance is required Often used for critical documents that affect safety, performance, contract requirements, or critical interfaces

• Government approval required before proceeding with dependent activities

• The Contractor may continue to proceed if they do not receive comments from the Government within 10 business days.

Spacecraft: The integrated assembly of all subsystems that form the platform which interfaces with and enables the functionality of a specific complement of instruments to meet their performance requirements and objectives. Synonymous with “spacecraft bus” or “bus”.

Observatory: The integrated assembly of the spacecraft and the instrument(s). Synonymous with “satellite”.

Mission Payload: The integrated assembly of all three LNext Observatories and the Dispenser.

4.0 WORK TO BE PERFORMED

SCSOW-41 The following sections, along with the Landsat Next Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), LNEXT-SC-REQ- 0029, describe the specific work to be accomplished by the Spacecraft Contractor. In accordance with the requirements of this document, 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.

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

SCSOW-43 The Contractor shall deliver to the Government three (3) observatories, dispenser and all other items per the Landsat Next Spacecraft Deliverable Items List (SC DIL), LNEXT- SC-LIST-0008 that are fully flight qualified and have demonstrated compliant operation in accordance with the requirements of this contract.

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

4.1 LANDSAT NEXT SPACECRAFT

4.1.1 Spacecraft Development, Integration, and Test

SCSOW-47 The Contractor shall develop, implement, integrate, and test three spacecraft that satisfy all Landsat Next mission requirements.

SCSOW-61 The Contractor shall conduct a successful Comprehensive Performance Test (CPT) after the completion of spacecraft I&T to demonstrate readiness for instrument integration and transition to observatory I&T.

SCSOW-888 The final CPT shall be executed on each spacecraft in the flight configuration with the full compliment of spacecraft flight hardware.

SCSOW-62 The final spacecraft CPT shall include a long duration test, approximately three days in duration, using the LOpS instrument simulator to demonstrate successful Observatory data flow, bit error rate and data loss allocations to the Government developed Ground System.

4.2 LANDSAT NEXT OBSERVATORY

4.2.1 Observatory I&T

SCSOW-83 The Contractor shall mechanically and electrically integrate to the spacecraft, and verify alignment of, each GFE instrument interface according to the Spacecraft to Instrument

ICD.

Note: The government will lead the development and incorporation of inputs into the ICDs via WGs as described in Section 4.8

SCSOW-67 The Contractor shall perform a Test Readiness Review (TRR) in advance of each observatory-level test.

SCSOW-68 The Contractor shall incorporate consent to proceed and consent to break points in test procedures for observatory level activities and launch site activities, providing sufficient data with adequate notice to enable informed consent before breaking configuration and proceeding.

‘Sufficient data’ should include salient information about the test configuration, confirmation that test objectives were met, and anomaly information and resolution (if any). The instrument team will provide assessment of instrument data as necessary to enable consent to proceed.

SCSOW-825 The Contractor shall provide mission data to the instrument vendor in near real time to facilitate instrument vendor review of data during all Observatory level activities.

Timeliness of data delivery to the instrument team is critical to support instrument team authorization for consent to proceed and/or consent to break during observatory testing.

SCSOW-887 A minimal set of hard-line spacecraft parameters, sufficient to establish spacecraft health and safety, shall be monitored and captured (stored), independent of the spacecraft telemetry system, by the EGSE whenever the spacecraft is powered with the GFE instrument mated. This data should be sampled at a rate sufficiently high to aid in diagnosis of abnormal power events.

SCSOW-69 The Contractor shall develop the MiniDRC flight-like test case, based on a selected subset of the full Landsat Next Design Reference Case – 18 Days (DRC-18) Definition, LSDS-2389, with Government input.

SCSOW-70 The Contractor shall incorporate the Mini-Design Reference Case (mini-DRC) into all Observatory CPTs that can be executed with either instrument simulators or the flight instrument.

SCSOW-72 The Contractor shall follow their standard processes to capture, archive, and make available upon request photos during observatory I&T activities.

SCSOW-823 The Contractor shall capture, archive and make available upon request videos of all critical lifts and mechanism deployments.

4.2.2 Instrument Accommodation and Integration

SCSOW-74 The Contractor shall develop an observatory I&T plan that begins with GFE instrument and related GSE arrival at the Contractor’s facility through LV encapsulation.

SCSOW-75 The Contractor shall accommodate LandIS hardware and provide support facilities for instrument personnel to use for flight delivery, unpacking, lifting and handling, and checkout activities.

SCSOW-78 The Contractor shall perform all necessary test script conversions of the instrument test scripts to facilitate observatory test activities and maintain configuration management of the converted test scripts for the duration of observatory I&T.

SCSOW-79 The Contractor shall develop and document the mechanical integration procedure for the mechanical integration of each GFE instrument to the spacecraft in concert with the GFE instrument contractor and the Government.

SCSOW-826 The Contractor shall develop and document the electrical integration procedure for the electrical integration of each GFE instrument to the spacecraft in concert with the GFE instrument contractor and the Government.

SCSOW-86 The Contractor shall not power on or off the instruments unless instrument personnel are present and notified.

SCSOW-87 The Contractor shall be responsible for monitoring and reporting the instrument health and safety at all times the instruments are powered after they are transferred to the Contractor’s control for observatory I&T.

SCSOW-88 The Contractor shall plan for the nominal schedule durations defined in the table below for GFE instrument functional testing. These durations do not include tear down or set up time for the spacecraft nor do they include parallel instrument troubleshooting that does not impact the spacecraft or observatory schedule. These GFE instrument functional tests will be executed as part of each associated Observatory performance test activity.

Table 4.2.2-1 Instrument Functional Tests

Instrument Functional Test Requirements Description

Hours

Instrument Comprehensive Performance Test (CPT) 24 hours (each CPT) Instrument Limited Performance Tests (LPT) 4 hours (each LPT) Instrument Aliveness Tests 2 hours (each Aliveness Test)

SCSOW-102 The Contractor shall provide testing periods prior to, during, and after each environmental test for instrument functional testing at the durations defined in the table above.

Note: Instrument functional testing will be executed as part of each Observatory performance test that occurs as part of the Observatory environmental test flow.

4.2.3 Instrument Interface Validation and Instrument Special Tests SCSOW-105 The Contractor shall plan and execute an early spacecraft to instrument interface verification test using the GFE LandIS Interface Simulator (LIS) and deliver test results per

CDRL IT-04.

4.2.4 RF Compatibility Testing

SCSOW-590 The Contractor shall participate with the Government in the planning and execution of RF Compatibility Testing to characterize performance of all RF communication link interfaces with the LGN, NSN, SN/TDRRS and/or the commercial SN replacement.

SCSOW-591 The Contractor shall provide the facilities for the Government-provided and operated RF compatibility test equipment and personnel.

SCSOW-592 The Contractor shall support the Government in development and review of the GSFC Code 450 Mission Interface Definition Document, which will be generated to capture all Government-led Radio Frequency (RF) Compatibility Testing.

4.2.5 End to End Mission Readiness Testing

SCSOW-117 The Contractor shall support the Government in the coordination and execution of a set of End-to-End (E2E) Mission Readiness Test (MRTs). The Government will facilitate the test working group sessions in preparation for test execution. E2E MRTs are performed to certify the ability of the observatory and ground system to operate as required to meet mission performance requirements by assessing their performance and their interfaces in various operational environments. MRTs are performed with flight hardware in conjunction with the operational MOC sending commands and receiving telemetry from the Observatory.

SCSOW-118 The Contractor shall participate with the Government in devising MRT test goals, requirements, procedures, and success criteria.

SCSOW-119 The Contractor shall support test execution with engineering support personnel in attendance at the MOC and at the Contractor facility for the duration of each test described in Table 4.2.5-1.

SCSOW-169 Beginning No Later Than (NLT) six months prior to the first scheduled MRT for the first observatory, the Contractor shall support up to five, 8-hour pre-MRT interface tests with the MOC to demonstrate that commands and telemetry flow successfully between the MOC and the Contractor’s facility and spacecraft hardware and software.

SCSOW-120 The Contractor shall support all test activities and pre-test checkouts to ensure readiness and successful execution of the MRTs. MRTs are described in Table 4.2.5-1, MRT Descriptions.

SCSOW-168 The MRT durations shown in Table 4.2.5-1 do not include spacecraft/observatory setup time or spacecraft/observatory-to-MOC interface verifications. MRTs may be executed in any order, except MRT 1 shall be first.

Table 4.2.5-1 MRT Descriptions

Test Brief Description Duration Configuration MRT1 Single spacecraft: Basic spacecraft command & telemetry checkout

1 day, 24 hours/day

Spacecraft I&T complete; prior to instrument integration

MRT2 Single spacecraft: Flight/Ground Interface Checkout and spacecraft operations

2 days, 24 hours/day

Spacecraft I&T complete; prior to instrument integration

MRT3.1 Single observatory: Spacecraft & Instrument Interface Checkout, Instrument Command & Telemetry Checkout, Basic Autonomy Operations

1 day, 24 hours/day

After Observatory CPT

MRT3.2

MRT3.3

Single observatory: Instrument interface and data flow checkout

2 days, 24 hours/day per observatory

After Observatory CPT

MRT4 Single observatory: Full observatory checkout and instrument operations

3 days, 24 hours/day

After Observatory CPT

MRT5 3 observatories: Constellation operations

1 day, 12 hours/day

After all 3 Observatory CPTs

MRT6 Single observatory: Instrument data flow during TVAC

1 day, 12 hours/day per observatory

TVAC

MRT7 Single observatory: Contingency operations and regression testing

3 days, 24 hours/day

Post TVAC

4.2.6 Government Involvement and Insight

SCSOW-171 The Contractor shall accommodate Government and LandIS engineering representatives on-site in preparation for and during observatory I&T activities.

SCSOW-172 The Contractor shall provide Government and LandIS personnel with remote/off-site access to real-time telemetry during observatory I&T.

SCSOW-177 The Contractor shall provide telemetry connectivity with the observatory at all times the observatory is powered to provide a real-time “listen line” flowing data to the MOC so that MOC personnel can monitor I&T activities throughout the observatory I&T. The Contractor may continue testing if the “listen-line” malfunctions and stops transmitting data. Monitoring at the MOC will be done using the GFE telemetry system.

SCSOW-178 The Contractor shall provide and implement the necessary network equipment within their facility to connect to the Government provided voice connection(s) to the MOC.

SCSOW-827 The Contractor shall implement necessary network equipment and stand up the "listen line" no less than one month prior to the first MOC connectivity test.

4.2.6.1 Ground System Interaction

The Government will provide up to three (3) Ground System to Spacecraft Integration Test Racks (GSSIRs) to interface between the spacecraft GSE and the ground system. The GSSIR is used by the Government to capture, process, store, and analyze mission data from the observatory, as transmitted via the spacecraft Ka-band interface, in support of monitoring the instrument health and performance while at the Contractors facility during I&T.

SCSOW-828 The Contractor shall provide an external network connection from the GSSIR to EROS to facilitate access and delivery of data during testing.

The three GSSIRs consist of a minimum of a full-height rack and three half racks of ground station S- and Ka-band equipment, in addition to two desktop workstations and data storage arrays. The mission data will be sent electronically to portions of the ground segment for further processing.

The GSSIR S-band testing will only be done for RF I&T purposes; the GSSIR does not flow telemetry or command data externally. The Government will be responsible for operation and maintenance of the GSSIR and the GSSIR will remain exclusively on a Government-managed network. The GSSIR is used by the Government for independent validation and is not available for the Contractor to use for critical flight testing operations.

SCSOW-174 The Contractor shall provide facilities and subject matter expert support for the Government to deliver, unpack, checkout, and perform basic power off/on/resets of the GSSIR, including setup and checkout of Government network interfaces connectivity and necessary GSSIR/network equipment moves during I&T. The Government will provide the rack and all GSSIR equipment. Government staff will also set up laptop computers while operating the

GSSIR.

SCSOW-175 The Contractor shall provide accommodations and voice loop communications for two GSSIR operators for each observatory.

SCSOW-176 The Contractor shall support GSSIR communication with the Observatory at all times the science data downlink is powered.

4.3 LANDSAT NEXT MISSION PAYLOAD

4.3.1 Mission Payload Development, Integration, and Test

SCSOW-181 The Contractor shall provide the structure, electrical, purge and harnessing to interface the three observatories to a single launch vehicle, including the multi-vehicle launch dispenser assembly compliant with the requirements as defined in the SRD and LSIDD.

SCSOW-182 The Contractor shall provide all hardware necessary to safely deploy the three Observatories from the Dispenser assembly.

SCSOW-183 The Contractor shall provide all dispenser and mission payload modeling and analyses and provide test data and safety data information as needed.

SCSOW-596 The Contractor shall provide verification of the environments imparted by each of the Observatories onto the LV during separation from the Dispenser.

SCSOW-184 The Contractor Dispenser design shall include distribution of T-0 purge to each of the observatories and all EGSE and LV avionics electrical interfaces from the LV to Mission Payload interface.

SCSOW-194 The Contractor shall conduct a mechanical fit check, electrical interface verification test, and separation system shock test involving the spacecraft (or observatories) with the dispenser at the Contractor’s location prior to shipment of the Mission Payload components to the launch site.

The Government, or launch service provider, will supply the necessary LV test and flight hardware, as well as the associated technical support, for the Observatory mechanical testing, separation shock test, and flight fit check with the LV hardware per the GFE List.

The Government-selected Launch Services Provider will provide access to the necessary LV test and flight hardware, as well as the associated technical support, for the dispenser electrical testing and flight fit check with the LV interface.

SCSOW-190 The Contractor shall support electrical interface verification testing between the LV avionics and the Contractor-supplied Launch Vehicle Interface Simulator (LVIS) at:

i. LV avionics test facility

ii. At the launch complex prior to Mission Payload to LV mate

SCSOW-193 The Contractor shall support electrical interface verification testing following Mission Payload mate to the LV at the launch site.

SCSOW-195 Verification of mechanical clearances and margins including potential reduced clearances after blanket expansion shall be performed on the final as-built 3 observatory stack with dispenser.

SCSOW-197 The Contractor shall provide appropriate ground storage for the dispenser prior to shipment to the launch site.

4.4 LANDSAT NEXT SIMULATORS

SCSOW-199 The Contractor shall develop, deliver, integrate, test, verify and maintain all GSE simulators as defined in the Landsat Next Spacecraft Simulator Requirements Document

(LNEXT-SC-REQ-0012).

SCSOW-599 The Contractor shall integrate and maintain the GSE instrument simulators as defined in the Landsat Next Landsat Instrument Suite (LandIS) Deliverable Items List (DIL), LNEXT-LANDIS-LIST-0004.

SCSOW-200 The Contractor shall implement and manage simulator utilization schedules for both Contractor internal use and for instrument and Flight Operations Team (FOT) use as necessary.

4.4.1 Command and Telemetry Simulation System (CTSS)

SCSOW-203 The Contractor shall develop, integrate, test, and deliver four (4) copies of the Command and Telemetry Simulation System (CTSS) in accordance with the Landsat Next Spacecraft Simulator Requirements Document (SC Sim RD), LNEXT-SC-REQ-0012.

SCSOW-205 After shipment of each CTSS, the Contractor shall assemble and perform a post-shipment Site Acceptance Test (SAT) to verify the function against the pre-ship baseline. The CTSS will be officially accepted after successful completion of the post-ship test and resolution of any anomalies as agreed to by the Government.

SCSOW-206 The Contractor shall maintain the CTSS through the life of the contract. This includes providing all FSW and database updates and patches, including corresponding installation and checkout instructions in order to maintain consistency with the observatory configuration.

4.4.2 Spacecraft Software Simulator (Softsim)

SCSOW-208 The Contractor shall develop, integrate, test, and deliver the purely software simulator (SoftSim) to be used by the Government in ground system and mission operations product development and testing in accordance with the Landsat Next Spacecraft Simulator Requirements Document (SC Sim RD), LNEXT-SC-REQ-0012.

SCSOW-600 The SoftSim deliveries shall include all required licenses and software environments, libraries, and executables necessary to operate the SoftSim.

SCSOW-210 The Contractor shall provide onsite support for the installation and configuration of the SoftSim.

SCSOW-212 The Contractor shall maintain the SoftSim throughout the life of the contract. This includes providing all FSW and database updates and patches, including corresponding installation and checkout instructions in order to maintain consistency with the observatory configuration.

4.4.3 Observatory Operational Simulators (OOps)

SCSOW-214 The Contractor shall develop, integrate, test, and verify (3) copies of the Spacecraft Operations Simulator (SOpS) in accordance with the Landsat Next Spacecraft Simulator Requirements Document (SC Sim RD), LNEXT-SC-REQ-0012.

SCSOW-215 The Contractor shall verify each SOpS interfaces and functionality prior to each SOpS integration to the OOpS. This verification will be witnessed by Government personnel.

SCSOW-217 The Contractor shall integrate the SC operational simulators (SOpS) to the Government-Furnished instrument simulators. These assemblies will be called the OOpS. An additional LandIS Operations Simulator (LOpS) is provided for use during testing at the spacecraft factory.

SCSOW-601 The Contractor shall design, fabricate, test and integrate all harnessing that connects the LOpS and SOpS.

SCSOW-219 The Contractor shall develop, integrate, test, verify and deliver three (3) copies of the Observatory Operational Simulator (OOpS).

SCSOW-218 For all instrument simulator deliveries, the Contractor shall provide facilities for the instrument providers to deliver, unpack, checkout, and operate the instrument simulators.

SCSOW-220 The Contractor shall develop and execute a Factory Acceptance Test (FAT) to verify each OOpS interfaces and functionality prior to each OOpS delivery. The instrument providers and necessary ground equipment provider will support the integration effort. This test will be witnessed by Government personnel.

SCSOW-221 The Contractor shall perform a long-duration test of at least 24 hours for one OOpS as part of the simulator verificatoin that includes: an injected mini-DRC (Earth-like injected data), a high entropy (not highly compressible images), low entropy (highly compressible images), and high duty cycle test (as close to continuous imaging as possible for 6 hours).

SCSOW-222 After shipment of each OOpS, the Contractor shall assemble and perform a post-shipment Site Acceptance Test (SAT) to verify the OOpS function against the pre-ship. The OOpS will be officially accepted after successful completion of the post-ship test and resolution of any anomalies as agreed to by the Government.

SCSOW-223 The Contractor shall maintain all copies of the OOpS through the life of the Contract.

4.4.4 Launch Vehicle Interface Simulator (LVIS)

SCSOW-225 The Contractor shall develop, integrate, test, deliver, and operate one (1) LNext LVIS for use at the launch services manufacturing facilities and launch site for interface verification of the LV in accordance with the Landsat Next Spacecraft Simulator Requirements Document (SC Sim RD), LNEXT-SC-REQ-0012, and the Landsat Next Mission Payload to Launch Services Interface Description Document (LSIDD), LNEXT-LS-ICD-0009 to be subsequently replaced by the Landsat Next Launch Services Interface Control Document

(LSICD), LNEXT-LS-ICD-0008.

SCSOW-226 The Contractor shall deliver, set up, and make the LVIS available at the launch service provider’s manufacturing facility for two LV interface test event that will occur no earlier than 60 days prior to launch.

SCSOW-227 The Contractor shall operate the LVIS and provide one week of LVIS operations support for the testing at the launch services provider’s facility and one day each of LVIS operations support for the two launch site test events.

4.4.5 RF Suitcase

SCSOW-231 The Contractor shall develop, integrate, test, verify, and deliver one copy of the RF Suitcase in accordance with the Landsat Next Spacecraft Simulator Requirements Document (SC Sim RD), LNEXT-SC-REQ-0012.

SCSOW-232 The Contract shall conduct a FAT for the RF Suitcase simulator.

SCSOW-233 After shipment of the RF Suitcase, the…