Attachment No. A

Landsat 10 Statement of Work

(SOW)

RFP 80GSFC26R0015

National Aeronautics and Space Administration Goddard Space Flight Center

Landsat 10 SC SOW L10-SC-SOW-0006 Revision C ii

Landsat 10 Spacecraft Statement of Work (SC SOW) Signature/Approval Page

Prepared by:

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

NASA/GSFC, Code 426

Prepared by:

Stephen McKim Date Landsat 10 Deputy Mission System Engineer NASA/GSFC, Code 533

Approved by:

Ross Henry Date Landsat 10 Project Manager NASA/GSFC, Code 426

Approved by:

Evan Webb Date Landsat 10 Mission Systems Manager NASA/GSFC, Code 533 iii

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

Note: Prior to February 2026, the project name was Landsat Next (LNext).

For the purposes of configuration management, the prefixes “LNEXT” and “L10” are completely interchangeable. For example, LNEXT-MGMT-PLAN-0004 is the same as L10-MGMT-PLAN- 0004.

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 10 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 10 Project Office, Code 426 Attention: Configuration Management Office Greenbelt, Maryland 20771 iv

Change History Log v

Table of Contents SIGNATURE/APPROVAL PAGE ................................................................................................ II CM FOREWORD ..........................................................................................................................III CHANGE HISTORY LOG .......................................................................................................... IV

TABLE OF CONTENTS ................................................................................................................ V

LIST OF FIGURES ..................................................................................................................... VII LIST OF TABLES ....................................................................................................................... VII

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

4.1.1 Spacecraft Development, Integration, and Test

4.2 Landsat 10 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.5.1 Spacecraft Operations Readiness Test

4.2.5.2 Observatory Mission Readiness Test

4.2.6 Government Involvement and Insight

4.2.6.1 Ground System Interaction

4.3 Landsat 10 Observatory and Launch Vehicle

4.3.1 Observatory and Launch Vehicle Development, Integration, and Test

4.4 Landsat 10 Simulators

4.4.1 Launch Vehicle Interface Simulator (LVIS)

4.5 Observatory Shipment to Launch Site

4.6 Launch Support

vi

4.6.1 Launch Site Operations

4.6.2 Launch Site Integration and Test

4.6.3 Launch Simulations

4.7 Mission Readiness and Mission Operations 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 Verification and 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.8 Electrical, Electronic, and Electromechanical (EEE) Parts

4.9.8.1 Master Parts List

4.9.9 Materials and Processes

4.9.10 Alerts and Problem Advisories

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

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

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 Engineering/Impact Analysis – CLIN 002

vii

4.10.10 Flight Spares

4.10.11 Working Groups

4.11 Systems Engineering

4.11.1 Requirements Management and Verification

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 Design Reference Case Validation

4.11.6 Specialty Engineering

4.11.6.1 Micro-Meteoroid and Orbital Debris Assessment

4.11.6.2 Space Environments

4.11.6.3 Software Engineering

4.11.6.4 Instrument Mounted Spacecraft Components (IMSC)

4.11.6.5 Contamination Control

4.12 IT Requirements

4.12.1 IT Purchase Authorization

4.12.2 Section 508 Conformance

4.12.3 Records Management

4.13 Contract Options

4.13.1 Launch Delays

APPENDIX A ABBREVIATIONS AND ACRONYMS

APPENDIX B DEFINITIONS

List of Figures Figure 2.4-1 Landsat 10 Mission Architecture Figure 4.2.6.1-1 Command and Telemetry and Mission Data Exchange Interfaces for the

Spacecraft/Observatory and the Ground System During I&T Figure 4.4-1 Observatory Operational Simulator (OOPS) with Key Internal and External

Interfaces

List of Tables Table 1.2.1-1 Project Requirements Table 1.2.1-2 Institutional Requirements and Standards Table 1.2.2-1 Institutional Reference Requirements and Standards Table 2.4.1-1 Landsat 10 Mission Parameters Table 4.2.2-1 Instrument Functional Tests 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 10 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) Landsat 10 Observatory in support of the Landsat 10 Mission.

1.1 SCOPE

The Scope of Work encompasses all required effort from receipt of the Landsat 10 Spacecraft Contract Award, through the development, integration, test, launch, delivery, on-orbit checkout, and acceptance of the Observatory. 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 10 Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), L10-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 Observatory developed under the Landsat 10 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 10 Spacecraft Government Furnished Equipment/Information (SC GFE/GFI) List, L10-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 Contractor shall comply with the documents listed in this section during the performance of the Contract. These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract.

SCSOW-9 The Contractor shall apply the following order of precedence in the event of a conflict in requirements between this SOW and other documentation:

1. Landsat 10 Spacecraft Statement of Work (SOW), L10-SC-SOW-0006

2. Landsat 10 Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), L10-SC-REQ-0029

3. Landsat 10 Spacecraft Requirements Document (SRD), L10-SC-REQ-0011

4. Landsat 10 Spacecraft Interface Requirements Document (SCIRD), L10-SC-ICD-0002

5. Landsat 10 Spacecraft to Ground Interface Requirements Document (SC-GND IRD), L10-

SC-ICD-0007

6. Landsat 10 Observatory Environmental Requirements Document (ObsERD), L10-OBSV-

REQ-0031

7. Landsat 10 Space Environments Requirements Document (LSERD), L10-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 instances, where the document specified in SCSOW-9 are in apparent conflict, 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 10 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 L10-LS-ICD-0009 Landsat 10 to Launch Services Interface Description Document (L10-LS IDD) L10-LV-ICD-0008 Landsat 10 Launch Vehicle Interface Control Document (LVICD) L10-MGMT-PLAN-0039 Landsat 10 Key Management Plan L10-OBSV-REQ-0031 Landsat 10 Observatory Environmental Requirements Document (ObsERD) L10-SC-ICD-0002 Landsat 10 Spacecraft Interface Requirements Document (SCIRD) L10-SC-ICD-0007 Landsat 10 Spacecraft to Ground Interface Requirements Document (SC-GND

IRD)

L10-SC-LIST-0007 Landsat 10 Spacecraft Government Furnished Equipment/Information (SC

GFE/GFI) List L10-SC-LIST-0008 Landsat 10 Spacecraft Deliverable Items List (SC DIL) L10-SC-REQ-0011 Landsat 10 Spacecraft Requirements Document (SRD) L10-SC-REQ-0012 Landsat 10 Spacecraft Simulator Requirements Document (SC Sim RD) L10-SC-REQ-0029 Landsat 10 Spacecraft Contract Data Requirements List (CDRL) and Data Item

Descriptions (DID) L10-SMA-PLAN-0133 Landsat 10 Spacecraft and Observatory Quality Assurance Surveillance Plan

(QASP)

L10-SYS-ICD-0017 Landsat 10 Simulator and Ground Test Equipment Interface Control Document

(ICD)

L10-SYS-REQ-0009 Landsat 10 Space Environments Requirements Document (LSERD) LSDS-2389 Landsat 10 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 10 Common Reference and Applicable Documents List (L10-MGMT-DESC-0008), DRAFT Rev F.

Table 1.2.1-2 Institutional Requirements and Standards Document Number Title Revision Section Reference NASA-STD-1006 Space System Protection Standard A 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 w/ Change 1 All

NPD 1440.6 NASA Records Management I All NPR 1441.1 NASA Records Management Program

Requirements E w/ CHANGE 3 All

NPR 8715.7 Payload Safety Program B w/ Change 2 All 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

3 All

DS-101 Electronic Key Management System

(EKMS)

N/A All

DS-102 Electronic Key Management System

(EKMS)

N/A All

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

1.2.2 Reference Documents

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

Table 1.2.2-1 Institutional Reference Requirements and Standards

Document Number Title EEE-INST-002 Instructions for EEE Parts Selection, Screening, Qualification, and Derating NASA-STD-8719.9 Lifting Standard NASA-STD-8739.8 Software Assurance and Software Safety NF 1634 Contracting Officer Representative (COR) / Alternate COR

Delegation NPR 7150.2 NASA Software Engineering Requirements NPR 8705.4 Risk Classification for NASA Payloads SS BPG Space Security: Best Practices Guide (BPG) GSFC-STD-1001 Criteria for Flight and Flight Support System Lifecycle

Reviews OnePlace (ServiceNow) NASA Office of the Chief Information Officer (OCIO)

Commercial IT Request (CITR) Application FRA; 44 U.S.C., Chapters 21, 29,31,33 Federal Records Act H.R.1232 Federal Information Technology Acquisition Reform Act 29 U.S.C. §794d Section 508 of the Rehabilitation Act, as amended 36 CFR § 1194.1 Standards for Section 508 of the Rehabilitation Act, Apps. A, C, & D 36 CFR Chapter XII Subchapter B Records Management Cybersecurity Maturity Model Certification (CMMC) Level 2

Department of War (DoW)

Cybersecurity Supply Chain Risk Management Strategy for Information and Communications Technology and Operational Technology Products and Services

Department of the Interior (DOI)

Internet Protocol version 6 (IPv6) Internet Protocol version 6 (IPv6) ISO 14644-1 Cleanrooms and associated controlled environments - Part 1:

Classification of air cleanliness by particle concentration ISO/IEC 27001 Information security, cybersecurity and privacy protection —

Information security management systems — Requirements In this document, citations are assumed to be the latest version unless otherwise noted.

2.0 MISSION OVERVIEW

2.1 MISSION STATEMENT

Landsat 10, consistent with United States (U.S.) law and government policy, will continue the Landsat program's acquisition, archival, and distribution of multi-spectral imagery, thereby 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 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. This investigation 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. Landsat Next subsequently passed its Mission Concept Review (MCR) and Key Decision Point-A (KDP-A) reviews in 2022. In March 2026, the Landsat Next mission was re-architected and re-designated Landsat 10 as a single observatory mission.

The goal of Landsat 10 is to continue the acquisition, archival, and distribution of multi-spectral imagery, thereby 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 10 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 10 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 10 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 10 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 10 data products to the public freely on a nondiscriminatory basis.

2.4 MISSION IMPLEMENTATION

The Landsat 10 mission includes a single observatory in a 653 km sun-synchronous low-earth orbit (LEO). The observatory includes a single integrated suite of sensors called LandIS (the Landsat Instrument Suite) that images the full swath required to achieve global coverage via a repeating ground track every 18 days.

The LandIS improves all spectral and spatial capabilities by approximately twofold when compared with the Operational Land Imager (OLI) and Thermal InfraRed Sensor (TIRS) instruments flown on Landsats 8 and 9, while maintaining the historical Landsat data continuity and similar temporal coverage.

Each Landsat 10 partner agency has specific responsibilities and will deliver major elements to the overall mission. NASA will provide the Space Segment (SS) and the Launch Services Segment (LSS), and the USGS will provide the Ground System (GS) and Mission Operations.

NASA/Goddard Space Flight Center (GSFC) will provide overall Landsat 10 project management, mission system engineering and mission assurance during development and will transition the mission to USGS for science operations following on-orbit commissioning.

Figure 2.4-1 Landsat 10 Mission Architecture

(Generated from Landsat 10 Common Mission Architecture Diagram L10-SYS-DESC-0022 Rev B)

2.4.1 Space Segment

NASA/GSFC provides the Space Segment via competitive procurements for the science instrument suite (LandIS) and the spacecraft bus. The Space Segment will consist of a single observatory flying in a sun-synchronous, near-polar orbit at 653 km altitude. The spacecraft, instrument, and overall Landsat 10 mission are specified as risk class C per NPR 8705.4. The overall mission parameters needed to achieve global coverage are shown below in the Mission Parameters Table.

Table 2.4.1-1 Landsat 10 Mission Parameters

LandIS is a whiskbroom scanner which provides 26 spectral bands covering a swath on the ground of approximately 164 km on a fixed ground track defined by a world-wide reference system known as WRS-3. LandIS acquires raw detector data for all spectral bands within 15 seconds to minimize band-to-band and georegistration errors, reduce classification change detection errors due to clouds, and provide simultaneous acquisitions for science applications.

LandIS then performs data compression prior to packaging the data for transfer to the spacecraft storage and subsequent downlink. LandIS also provides internal calibration sources such as blackbody, a space port, stim lamps and solar diffuser.

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. These simulators will have varying fidelity and capabilities to meet various mission needs.

2.4.2 Ground Segment

The Landsat Ground Segment (GS) 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 10 MOC will be used for command and control, health and status monitoring, orbit and attitude maintenance, performance analysis, onboard memory management, and flight software maintenance. The MOC will support onboard autonomy for mission planning and scheduling. The MOC ingests, processes and archives telemetry data delivered via the GN. The Landsat 10 Flight Operations Team (FOT) located at the MOC performs these functions and is responsible for monitoring the observatory, 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 to and from the observatory and MOC for commanding and housekeeping data via the S-band, and will receive science mission data from the observatory over a Ka-band downlink.

The DPAS ingests, processes, and archives science data returned from the observatory via the GN. LandIS data will be processed into data products with a ground sample distance (GSD) ranging from 10m-60m depending on the particular spectral band. 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 10 data products, via a public-facing web portal for receiving data products.

The USGS will lead overall Landsat 10 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 10 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 observatory-to-LV integration. The Launch Segment will include the LV; all

Launch Vehicle-Ground Support Equipment (LV-GSE), property, and facilities to integrate the observatory to the LV and verify its integration; and perform prelaunch testing with ground-based functions. The launch vehicle and launch site will be specified during late Mission Phase B or early Phase C.

Sections 2.0-2.4.3 were generated using Landsat 10 Common Boilerplate (L10-MGMT-DESC-0005) Rev E

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

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

4.0 WORK TO BE PERFORMED

The following sections, along with the Landsat 10 Spacecraft Contract Requirements Document List (CDRL) and Data Item Descriptions (DID), L10-SC-REQ-0029, describe the specific work to be accomplished by the Spacecraft Contractor.

SCSOW-41 The Contractor shall provide (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 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 the Landsat 10 Spacecraft.

SCSOW-42 The Contractor shall provide the personnel, materials, equipment, and facilities necessary to integrate the LandIS Instrument, test the Landsat 10 Observatory, support mission-level activities, support launch vehicle integration, and on-orbit commissioning of Landsat 10.

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

4.1 LANDSAT 10 SPACECRAFT

4.1.1 Spacecraft Development, Integration, and Test

SCSOW-47 The Contractor shall develop, implement, integrate, and test one Spacecraft that satisfies all Landsat 10 mission requirements.

SCSOW-61 The Contractor shall conduct a successful Comprehensive Performance Test (CPT) after the completion of Spacecraft Integration and Test (I&T) and successfully complete all Spacecraft Operations Readiness Tests (SORTs) to demonstrate readiness for instrument integration and transition to Observatory I&T.

SCSOW-986 The Contractor shall perform a Test Readiness Review (TRR) prior to the SC CPT that includes all the data for a TRR as required per SCSOW-67.

SCSOW-888 The Contractor shall perform the CPT, including a mini-DRC, on the Spacecraft in the flight configuration with the full complement of Spacecraft flight hardware.

SCSOW-62 The Contractor shall include a long duration test as part of the CPT that is 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.

SCSOW-965 The Contractor shall deliver a final and complete Spacecraft End Item Data Package (EIDP) per CDRL L10-SA-10 to demonstrate readiness for instrument integration and transition to Observatory I&T.

SCSOW-1023 The Contractor shall include in the entrance criteria for OIRR, completion of final Spacecraft CPT, the long duration test outlined in SCSOW-62, completion of all SORTs, and approval of the Spacecraft EIDP.

SCSOW-893 The Contractor shall ensure that all parts of the SC will be at TRL-6 or above at the time of Spacecraft PDR. TRL-6 is determined using the following criteria:

Definition: System/sub-system model or prototype demonstration in a Relevant environment.

Hardware Description: A high-fidelity prototype of the system/subsystems that adequately addresses all critical scaling issues is built and tested in a relevant environment to demonstrate performance under critical environmental conditions.

Software Description: Prototype implementations of the software demonstrated on full-scale, realistic problems. Partially integrated with existing hardware/software systems. Limited documentation available. Engineering feasibility fully demonstrated.

Success Criteria: Documented test performance demonstrating agreement with analytical predictions.

4.2 LANDSAT 10 OBSERVATORY

4.2.1 Observatory I&T

SCSOW-83 The Contractor shall mechanically and electrically integrate to the Spacecraft, and verify alignment of, the GFE instrument interface according to the Landsat 10 Spacecraft (SC) to Landsat Instrument Suite (LandIS) Interface Control Document (SC-LandIS ICD), L10-SC-ICD- 0005.

Note: The Government will lead the development and incorporation of inputs into the Interface Control Documents (ICDs) via working groups (WGs) as described in Section 4.8.

SCSOW-1024 The Contractor shall provide all electrical interface harnessing for LandIS flight instrument and the simulators from SC and SC GSE to the associated interface panel(s).

SCSOW-67 The Contractor shall perform a TRR or contractor equivalent in advance of each Observatory-level test that describes the following:

• Testing to be executed

• Test objectives

• Expected results

• Status of flight hardware/software including any open relevant anomalies or other conditions affecting flight hardware/software

• Status of procedures

• Required GSE and certification/calibration status

• Required staff and availability

• Required facilities and status

• Hardware and personnel safety considerations

• Identification of any hazardous operations

SCSOW-1025 The Contractor shall perform Observatory Comprehensive Performance Testing (CPT), Limited Performance Testing (LPT) and Aliveness Testing (AT) that complies with the requirements in Landsat 10 Observatory Environmental Requirements Document (ObsERD), L10-OBSV-REQ-0031.

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 (to enable informed consent before breaking configuration and proceeding) that includes,

• Test configuration

• Status of test objectives

• Anomaly information and resolution (if any)

• Assessment by the instrument team of instrument data (as necessary)

SCSOW-825 The Contractor shall provide mission data and state-of-health (SOH) 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 The Contractor shall monitor and capture (store), on electrical ground support equipment (EGSE), independent of SC telemetry system, a set of hard-line Spacecraft parameters, sufficient to establish Spacecraft health and safety, 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 mini-DRC flight-like test case run in closed-loop Attitude Control System (ACS) mode, based on a selected subset consisting of five (5) orbits adapted from the full Landsat 10 Design Reference Case – 18 Days (DRC-18) Definition, LSDS- 2389, with Government input and concurrence.

SCSOW-1006 The Contractor shall execute a mini-DRC flight-like run in closed-loop ACS mode for the purposes of the Government to generate accompanying data for injection.

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-823 The Contractor shall follow their standard process to capture, archive and make available upon request videos of all critical lifts and mechanism deployments when the Instrument is involved or integrated to the Observatory.

4.2.2 Instrument Accommodation and Integration

SCSOW-966 The Contractor shall provide a Spacecraft interface that complies with the requirements of the Landsat 10 Spacecraft Interface Requirements Document, L10-SC-ICD- 0002.

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

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 the GFE instrument to the Spacecraft in concert with the GFE instrument contractor and the Government.

SCSOW-826 The Contractor shall, with the participation of the Government and the GFE instrument contractor, develop all integration procedures for the integration of the GFE instrument to the Spacecraft, subject to the approval of government.

SCSOW-86 The Contractor shall only perform operations on the GFE instrument and power on or off the GFE instrument only when the GFE instrument personnel are present, and have concurred that it is safe to do so.

SCSOW-87 The Contractor shall be responsible for monitoring and reporting the instrument health and safety at all times the instrument is 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 any possible parallel instrument troubleshooting.

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 Full Functional Test (FFT) 12 hours Instrument Aliveness Tests 2 hours

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.

SCSOW-1026 The contractor shall allocate time for execution of an instrument Full Functional Test (FFT) at the duration specified in the table above as part of each Observatory CPT and Observatory LPT.

SCSOW-1027 The contractor shall allocate time for execution of an instrument Aliveness Test (AT) at the duration specified in the table above as part of each Observatory AT.

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) with SC Contractor supplied EGSE harnesses and deliver test results per CDRL L10-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 DTE, NSN SR/TDRS and/or the commercial SR/TDRS replacement, and supply the interface equipment to the government RF test equipment, including any RF Hats, test couplers, etc.

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-118 The Contractor shall support the Government in devising the test goals and timeline for all End-to-End (E2E) tests, which cover the Contractor-led Spacecraft Operations Readiness Test (SORT) and the Government-led Mission Readiness Test (MRT). All E2E tests are performed with integrated flight hardware, the GSSIR, the CTP, the operational MOC (utilizing Ops Products) for commanding and telemetry, and DPAS (when test objectives require science data processing). The Government will provide access to the MOC (and necessary training), the GSSIR, and the CTP.

4.2.5.1 Spacecraft Operations Readiness Test

SCSOW-914 The Contractor shall execute End-to-End (E2E) Spacecraft Operations Readiness Tests (SORT) to verify all Spacecraft activities and associated ops products.

Spacecraft activities include all on-orbit SC commanding executed during LEOC, which include a demonstration of normal operations and decommissioning.

The Contractor will determine the number of SORT(s) and total duration to meet the SORT objectives, which will be documented as part of CDRL OPS-02 Mission Readiness, Commissioning and Operations Support Plan.

SCSOW-915 The Contractor shall conduct a series of MOC connectivity tests with the MOC or MOC equipment prior to the first Spacecraft Operations Readiness Test (SORT) that demonstrates encrypted commanding from the MOC to the spacecraft hardware and software at the spacecraft contractor’s facility, and telemetry and mission data connectivity exists to the MOC and DPAS.

4.2.5.2 Observatory Mission Readiness Test

SCSOW-117 The Contractor shall support the Government in the coordination and execution of E2E Mission Readiness Test (MRTs) to validate Observatory-level activities and Instrument activities. Test execution and pre-test checkout support includes Contractor personnel in attendance at the MOC and the Contractor facility for the duration of each test.

SCSOW-168 The Contractor shall allocate 176 hours of Observation I&T time after Obs CPT to conduct a series of MRTs. This consists of 144 hours of test time and 32 hours to verify connectivity between the SC and MOC prior to each MRT. This allotment will be broken up into several test blocks, where each test block can be a minimum of 12 hours and maximum of 80 hours; these will be coordinated with the Government at the Mission Readiness Working Group.

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 real-time remote/off-site telemetry monitoring capability during Observatory I&T.

SCSOW-1029 The Contractor shall provide Government and LandIS personnel with remote/off-site access to all archived telemetry during Observatory I&T.

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

4.2.6.1 Ground System Interaction

SCSOW-174 The Contractor shall accommodate ground system GSE that will be used to interface between the SC and the ground system as depicted in Figure 4.2.6.1-1.

This includes the Ground System to Spacecraft Integration Test Racks (GSSIR) and the MOC Command and Telemetry Processor (MOC CTP).

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-1030 The Contractor shall supply the output of each Ka-band RF signal polarization (RHCP and LHCP) as down-converted inputs to the 2.4 GHz IF GISSR receiver.

SCSOW-1031 The Contractor shall feed the Telemetry and Command (T&C) S-band output of the observatory into the CTP via S-band RF over fiber connection.

The MOC CTP is used to interface between the Spacecraft GSE and the ground system to support the SC command and telemetry traffic with the MOC during I&T.

The details of the interface definitions and facilities needs for the government provided GSE will be worked with the contractor and documented in the Landsat 10 Simulator and Ground Test Equipment Interface Control Document (ICD), L10-SYS-ICD-0017. For estimating purposes, the contractor can assume 4 equipment racks and workspaces/desks for up to 3 persons at a time.

Figure 4.2.6.1-1 Command and Telemetry and Mission Data Exchange Interfaces for the

Spacecraft/Observatory and the Ground System During I&T

SCSOW-828 The Contractor shall establish and verify a connection from the SC GSE to the

GSSIR.

SCSOW-897 The Contractor shall establish an external connection from the GSSIR to a Government-provided Wide Area Network (WAN) to the Ground System.

SCSOW-912 The Contractor shall establish and verify a connection to/from the SC GSE from/to the MOC CTP.

SCSOW-913 The Contractor shall establish an external connection to/from the MOC CTP from/to a Government-provided WAN to the Ground System.

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-175 The Contractor shall provide accommodations and voice loop communications for two GSSIR operators to the SC I&T voice communication loops and enable voice loop communication to the L10 MOC through a Government-provided WAN.

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

SCSOW-177 The Contractor shall provide real time telemetry from the SC to the MOC Command and Telemetry Processor (MOC CTP) at all times, when the Spacecraft is powered at the Contractors facility and at the Launch site facility. This will provide a real-time “listen line” flowing telemetry to the MOC to support MOC development.

4.3 LANDSAT 10 OBSERVATORY AND LAUNCH VEHICLE

4.3.1 Observatory and Launch Vehicle Development, Integration, and Test SCSOW-181 The Contractor shall provide the structure, electrical, purge and harnessing to interface the Observatory to a single launch vehicle, compliant with the requirements as defined in the Landsat 10 Spacecraft Requirements Document (SRD), L10-SC-REQ-0011 and Landsat 10 Observatory to Launch Services Interface Description Document (L10-LS IDD), L10-LS-

ICD-0009.

SCSOW-183 The Contractor shall provide all Spacecraft and Observatory modeling and analyses and provide test data and safety data information as needed for required CDRLs.

SCSOW-184 The Contractor shall provide for distribution of the T-0 GN2 purges and electrical services from the mechanical interface to the LV to the Observatory.

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

The Government, or Launch Services Contractor (LSC), 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 LSC will provide access to the necessary LV test and flight hardware, as well as the associated technical support, for the Observatory electrical testing and flight fit check with the LV interface.

SCSOW-190 The Contractor shall support electrical interface verification testing between the LV umbilical interfaces and the Contractor-supplied Launch Vehicle Interface Simulator (LVIS) at the launch site consistent with the LV processing flow.

SCSOW-193 The Contractor shall support electrical interface verification testing between the Observatory and the LV at the launch site.

SCSOW-195 The Contractor shall verify acceptable mechanical clearances and margins, including potentially reduced clearances after blanket expansion, on the final as-built Observatory.

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

4.4 LANDSAT 10 SIMULATORS

SCSOW-199 The Contractor shall develop, integrate, test, verify, and deliver all simulators as defined in the Landsat 10 Spacecraft Simulator Requirements Document (SC SIM RD), L10-SC-

REQ-0012.

SCSOW-987 All simulator deliveries shall include all required licenses and software environments, libraries, and executables necessary to operate and maintain the simulator.

SCSOW-1036 The contractor shall deliver 4 fully verified Softsims to the government that meet all SoftSim-tagged simulator requirements.

SCSOW-1037 The contractor shall integrate one of the four spacecraft Softsim to the GFE LOPS and deliver to the government as an early product development tool with the following minimum set of functionalities per the Landsat 10 Spacecraft Simulator Requirements Document

(SC SIM RD), L10-SC-REQ-0012:

• Interface

• CMD

• Telemetry

• Time of Day

• Operations Note: The initial Softsim + LOPS delivery will only meet the requirements outlined in SCSOW- 1037 and will be updated by the vendor to satisfy all simulator requirements by the final delivery date.

SCSOW-599 The Contractor shall integrate the Observatory Operational Simulator (OOpS), which consists of the Spacecraft Operational Simulator (SOpS), LandIS Operations Simulator (LOpS), Wideband Data Capture (WDC), and OOpS Command and Telemetry Processor (OOpS CTP). The LOpS, WDC, and OOpS CTP will be provided to the Contractor as listed in the Landsat 10 Spacecraft Government Furnished Equipment/Information (SC GFE/GFI) List, L10-

SC-LIST-0007.

SCSOW-1038 The contractor shall deliver 2 fully verified OOPS to the government that meet all OOpS-tagged simulator requirements.

SCSOW-1039 The contractor shall provide one of the two OOPS to the government as an early product development tool that with the following minimum set of functionalities per the Landsat 10 Spacecraft Simulator Requirements Document (SC SIM RD), L10-SC-REQ-0012:

• Interface

• CMD

• Telemetry

• Time of Day

• Imaging Sensor Data

• Ancillary Data

• Operations Note: The initial OOPS delivery will only meet the requirements outlined in SCSOW-1039 and will be updated by the vendor to satisfy all simulator requirements by the final delivery date.

Figure 4.4-1 Observatory Operational Simulator (OOPS) with Key Internal and External

Interfaces

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

SCSOW-898 The Contractor shall conduct a pre-delivery meeting with the Government before each simulator delivery that contains the following:

• Simulator capabilities

• Simulator requirements verification status and artifacts

• Status of outstanding issues and resolution plan

• Necessary licenses

• Delivery and site integration plans

• Post-delivery maintenance and update plans.

SCSOW-218 The Contractor shall provide facilities for the instrument provider and ground provider to deliver, unpack, checkout, and operate the instrument simulators and Ground test equipment.

SCSOW-210 The Contractor shall conduct a post-delivery/post-integration Simulator Acceptance Test (SAT) per CDRL SIM-02 on each simulator listed in the Landsat 10 Spacecraft Deliverable Items List (SC DIL), L10-SC-LIST-0008.

SCSOW-900 The Contractor shall verify all simulator requirements prior to simulator delivery.

SCSOW-221 The Contractor shall perform a long-duration test of at least 24 hours for one OOpS in closed-loop ACS mode as part of the simulator verification that includes the following:

• Injected mini-DRC (Earth-like injected data)

• High entropy (not highly compressible images)

• Low entropy (highly compressible images)

• A high duty cycle test (as close to continuous imaging as possible for 6 hours).

SCSOW-901 The Contractor shall conduct a training session following the delivery and integration of each simulator that includes hands-on training with Government representatives…