Attachment A - LandIS SOW-Rev A.pdf

LNext LandIS SOW LNEXT-LANDIS-SOW-0003 Revision A ii

Landsat Next Landsat Instrument Suite (LandIS) Statement of Work (SOW)

Signature/Approval Page

Prepared by:

Electronic Signature in TDMS Approval Date in TDMS Joy Henegar-Leon Date Landsat Next Payload Technical Manager Org./Code 426

Approved by:

Electronic Signature in TDMS Approval Date in TDMS Wen-Ting Hsieh Date Landsat Next Payload Manager Org./Code 426

Approved by:

Electronic Signature in TDMS Approval Date in TDMS James Pontius Date Landsat Next Project Manager Org./Code 426

Approved by:

Electronic Signature in TDMS Approval Date in TDMS Evan Webb Date Landsat Next Mission System Manager Org./Code 599 iii

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

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

Questions or comments concerning this document should be addressed to:

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

Change History Log v

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

Name/Org.

Due Date

TBx-1 Section 2.4.3

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

ISE Mission

PDR

TBx-2 Section 3.4.5

ISOW-1577 The Contractor shall collect modal frequency data during the model survey and the structural verification testing, to be used to for qualitative verification of structural responses, up to 200 Hz (TBR), for jitter analyses.

ISE Mission

PDR

TBx-3 Section 3.11

ISOW-1301 The Contractor shall design LandIS for a launch from TBD launch facility. ISE Mission

PDR

TBx-4 Section 3.11

ISOW-1304 The Contractor shall provide LandIS to be compatible with the cleanliness specified in the Landsat Next Launch Services Interface Requirements Document (TBR).

ISE Mission

PDR

TBx-5 Section 3.12.11

ISOW-877 The launch-commissioning period will nominally be 100(TBR) days in duration. ISE Mission

PDR

TBx-6 Section 3.12.11.2

ISOW-900 The Contractor shall for planning purposes assume the commissioning phase will take 100 (TBR) days to complete.

ISE Mission

PDR

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

LIST OF TABLES ........................................................................................................................ IX

1.0 INTRODUCTION

1.1 Scope

1.2 Definitions

1.3 Related Documentation

1.3.1 Applicable Documents

1.3.2 Reference Documents

1.3.3 Project Applicable Documents

1.3.4 Project 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 WORK TO BE PERFORMED

3.1 Project Management (PM)

3.1.1 Government Insight and Surveillance

3.1.2 Control of Sensitive Information

3.1.3 Documentation

3.1.4 Reviews and Meetings

3.1.4.1 Major Reviews

3.1.4.2 Engineering Peer Reviews

3.1.4.3 Other Reviews and Meetings

3.1.5 Action Item Tracking

3.1.6 Electronic Access

3.1.7 Internal Technical Memoranda

3.1.8 Access to Controlled Facilities

3.1.9 Risk Management

3.1.10 Problem Tracking

3.1.11 Resource Management

vii

3.1.12 Configuration Management

3.1.13 Subcontractor Management

3.1.14 Government Resident Office Support

3.1.15 Audits

3.1.16 Lessons Learned Reporting

3.1.17 Non-Disclosure Agreements

3.1.18 IT Security/Supply Chain Risk Management

3.1.18.1 Federal Information Systems

3.1.18.2 Connected Information Systems

3.1.18.3 Internal Information Systems

3.1.19 System Security of Space Assets

3.2 Systems Engineering

3.2.1 Requirement Analysis, Derivations, and Allocations

3.2.1.1 Use of DOORS® Tool

3.2.2 Interface Definition, Verification and Control

3.2.3 Design and Performance Verification

3.2.4 Systems Analyses

3.2.5 Trending

3.2.6 Fault Management

3.3 Mission Assurance

3.4 LANDIS Instrument Design

3.4.1 Design Engineering

3.4.2 Focal Plane Assembly Design

3.4.3 Telescope and Optics Design

3.4.3.1 Optical Analytical Model

3.4.3.2 Stray Light and Ghosting Model

3.4.4 Instrument Electronics Design

3.4.5 Instrument Structure Design and Analysis

3.4.6 Mechanisms Design

3.4.7 Instrument Deck Design

3.4.8 Instrument Mounted Spacecraft Components (IMSC)

3.4.9 Calibration System Design

3.4.9.1 Calibration Algorithms and Parameters

3.4.9.2 Radiometric Math Model

3.4.10 Software Engineering

3.4.10.1 Software Definitions

3.4.10.2 Software Management

3.4.10.3 Software Engineering Life Cycle Activities

3.4.10.4 Software Design

3.4.10.5 Software Peer Reviews and Inspections

3.4.11 Harnessing Design

3.4.12 Electrical System Design

3.4.13 Thermal System Design

3.4.14 Contamination Control Design

3.4.15 Instrument Integration and Test Planning

3.4.16 Instrument Simulators Design

viii

3.4.17 Engineering Development Unit (EDU) Design

3.4.18 Data Processing Algorithms Design and Support

3.4.19 Data Reduction/Compression

3.5 Implementation, Fabrication, Assembly, and Test

3.5.1 Focal Plane Assembly Fabrication, Assembly and Test

3.5.2 Telescope and Optics Fabrication, Assembly, and Test

3.5.3 Instrument Electronics Fabrication, Assembly, and Test

3.5.4 Instrument Structure Fabrication, Assembly, and Test

3.5.5 Instrument Mechanisms Fabrication, Assembly, and Test

3.5.6 Instrument Deck Fabrication, Assembly, and Test

3.5.7 Instrument Calibration System Fabrication, Assembly, and Test

3.5.8 Software Implementation

3.5.8.1 Implementation and Delivery Life Cycle Activities

3.5.9 Harnessing Fabrication, Assembly, and Test

3.5.10 Electrical System Fabrication, Assembly, and Test

3.5.11 Thermal System Fabrication, Assembly, and Test

3.5.12 Contamination Control Monitoring and Validation

3.5.13 Instrument Integration and Test

3.5.13.1 Integration

3.5.13.2 Environmental and Performance Testing

3.5.13.3 Instrument Calibration and Validation

3.5.13.4 Instrument Special Calibration Test Requirements (SCTR)

3.5.13.5 Instrument Independent Testing

3.5.13.6 Instrument Level of Assembly on Delivery

3.5.14 Instrument Simulators Fabrication, Assembly, Test, and Delivery

3.5.15 Engineering Development Unit Fabrication, Assembly, and Test

3.5.16 Data Processing Algorithms Code and Test

3.5.16.1 Line of Sight Process Algorithms

3.5.16.2 Data Processing Algorithms

3.5.16.3 Support to Operational Algorithm Development

3.5.17 Data Reduction/Compression Implementation

3.6 Instrument Operations Support

3.6.1 Support to Mission Operations Development

3.6.2 Operational Procedures and Documentation

3.6.3 Command and Telemetry Database Support

3.6.4 Training Support

3.6.5 Software Operations, Maintenance, and Retirement

3.6.5.1 Software Development and Verification Facility (SDVF)

3.7 Packaging, Handling, Storage, and Transportation

3.8 Delivery, Checkout, and Acceptance

3.9 Ground Support Equipment

3.9.1 Calibration Test Equipment

3.9.2 Mechanical Ground Support Equipment (MGSE)

3.9.3 Electrical Ground Support Equipment

3.9.4 Shipping, Storage, and Purge Equipment

3.10 Spares

ix

3.11 Launch Site Requirements

3.12 Post-Delivery Support

3.12.1 Observatory Integration and Test

3.12.2 Interface Testing

3.12.3 Observatory Integration

3.12.4 Observatory Testing

3.12.5 Support to Mission Readiness Tests(s)

3.12.6 Support to RF Compatibility Testing

3.12.7 Support to Mission Simulations

3.12.8 Support to Launch Rehearsals and Exercises

3.12.9 Instrument Simulators Checkout, Acceptance, and Support

3.12.9.1 LandIS Operations Simulators

3.12.9.2 LandIS Interface Simulator

3.12.10 Launch and Early Orbit Support

3.12.11 Commissioning, Including On-Orbit Check-Out

3.12.11.1 Instrument Checkout

3.12.11.2 Acceptance

4.0 SPECIAL STUDIES

5.0 OPTION FOR LANDIS#4

5.1 Overview of the Work to be Performed:

5.2 Project Management

5.2.1 LandIS #4 Reviews

5.3 Systems Engineering Section:

5.4 Mission Assurance:

5.5 LandIS Instrument Design:

5.6 Fabrication, Assembly, and Test

5.7 Instrument Operations Support

5.8 Packaging Handling, Storage, and Transportation

5.9 Delivery, Checkout and Acceptance

5.10 Ground Support Equipment

5.11 Spares

5.12 Launch Site Requirements

5.13 Post-Delivery Support Requirements

APPENDIX A SPECIAL CALIBRATION TEST REQUIREMENTS

APPENDIX B ABBREVIATIONS AND ACRONYMS

APPENDIX C DEFINITIONS

List of Figures

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

List of Tables x

No table of contents entries found.

1.0 INTRODUCTION

1.1 SCOPE

This Statement of Work (SOW) defines the effort required of the Contractor that includes but is not limited to the design, engineering analyses, development, fabrication, integration, algorithm development, test, evaluation, delivery, and support for the Landsat Next Instrument Suite (LandIS), a portion of the Landsat Next (LNext) Mission. The Government is responsible for integration of the LNext mission. The Contractor provides support for the instruments related portions of the Government’s mission system integration effort.

This Statement of Work requires delivery of all contract deliverables and documents associated with the LandIS development.

The interface design of the instrument to the spacecraft will be refined after the instrument contract award. After a spacecraft bus contractor is selected, the Government will assume primary responsibility for leading development of the instrument-to-spacecraft interface control documentation in coordination with the instrument contractor.

1.2 DEFINITIONS

The following definitions apply to this document:

Project - The term Project refers to the Landsat Next Project Office Landsat Next Instrument Suite (LandIS) – The term LandIS refers to the multi-band sensors and associated electronics, software, and harnessing that meets the performance requirements in the LandIS Requirements Document (LaRD) (LNEXT-LANDIS-REQ-0007) and the LandIS Interface Requirements Document (LIRD) (LNEXT-LANDIS-ICD-0001). The Contractor will deliver 3 copies of LandIS as part of this contract.

Contractor – The developer of the item of reference. If the term contractor is used in this document without specific reference to an item (e.g., LandIS, spacecraft bus, etc.), then the term shall be interpreted to imply the LandIS contractor. In all cases, the term contractor also implies any and all associated suppliers and subcontractors.

Shall – Compliance by the Contractor is mandatory. Any deviations from these contractually imposed mandatory requirements require the approval of the contracting officer.

May – At the discretion of the Contractor or Government.

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

Should – Gives guidance to the Contractor for the performance of this contract.

Must – Notifies the Contractor of important relevant conditions that may be outside the context of this contract.

Engineering Peer Review (EPR) – a meeting between approximately 2 to 5 Government representatives and Contractor technical representatives to provide focused, in-depth technical reviews that support the evolving design and development of a product subsystem or engineering discipline area, such as the thermal system. The purpose of an EPR is to reduce risk through expert knowledge infusion, confirmation of approach, and specific recommendations. An EPR provides an examination of design, analysis, manufacturing, integration, test and operational details, drawings, processes and data.

Technical Interchange Meeting (TIM) – an informal meeting, between the Contractor and approximately 5 to 10 Government representatives, and/or the spacecraft and MOC contractor personnel to discuss a system process or feature. For example, to reach understanding of an operation or analysis, presentation of test results, discuss planned interface changes, plan for an upcoming test, etc. TIMs typically are held at the contractor’s facility and typically run no more than two days. TIMs involving the LandIS contractor may also be conducted at the spacecraft or MOC contractors’ facilities. Actions are informally tracked by the TIM organizer.

Major Review – Major reviews are major milestones in the implementation where information is formally presented to a panel of Government experts and external reviewers. Major Reviews can involve up to approximately 30 Government representatives and typically run up to four days.

Formal action items are logged and tracked by the Project Office.

1.3 RELATED DOCUMENTATION

The documents listed in this section shall apply directly to the performance of the LandIS Contract. These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract. In case of conflicting requirements, the order of precedence of documents not specifically called out in the Contract is: this Statement of Work, the Instrument Mission Assurance Requirements (IMAR) document (LNEXT-SMA- REQ-0013), the LandIS Requirements Document (LNEXT-LANDIS-REQ-0007), the LandIS Interface Requirements Document (LNEXT-LANDIS-ICD-0001), the Contract Data Requirements List (CDRL) (LNEXT-LANDIS-PLAN-0052), and the Landsat Next Environmental Requirements Document (LNERD) (LNEXT-SYS-REQ-0005). In the event of conflict between the LandIS Interface Requirements Document and the Interface Control Documents (ICDs), the ICDs take precedence.

1.3.1 Applicable Documents

Document Number Title Revision Section Reference

GPR 7120.4 Risk Management D All GSFC-STD-1001 Criteria for Flight and Flight Support

System Lifecycle Reviews A All

ITS-HBK-CUI Controlled Unclassified Information Handbook

1.1.0 All

NASA-STD-1006 Space System Protection Standard A All NASA-STD-5002 Load Analyses of Spacecraft and

Payloads A All

NASA-STD-5005 Standard for the Design and Fabrication of Ground Support Equipment

D w/ CHANGE 1 All

NASA-STD-5017 DESIGN AND DEVELOPMENT

REQUIREMENTS FOR

MECHANISMS

B All

NASA-STD-5020 Requirements for Threaded Fastening Systems in Spaceflight Hardware

B All

NASA-STD-6030 Additive Manufacturing Requirements for Spaceflight Systems

- All

Document Number Title Revision Section Reference

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

- All

NASA-STD-8719.24 NASA Expendable Launch Vehicle Payload Safety Requirements

A All

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

A w/Change 2 All

NASA-STD-8739.8 NASA Standard for Software Assurance

A All

NASA-STD-8739.8 Software Assurance and Software Safety Standard

A All

NPD 1440.6 NASA Records Management I All NPD 2810.1 NASA Information Security Policy F All NPR 1040.1 NASA Continuity of Operations

(COOP) Planning Procedural Requirements

- w/ CHANGE 3 All

NPR 1600.1 NASA Security Program Procedural Requirements

A All

NPR 2180.7 Controlled Unclassified Information - All NPR 2810.1 Security of Information and Information

Systems F All

NPR 7150.2 NASA Software Engineering Requirements

D All

48 CFR § 27.4 Code of Federal Regulations (CFR), Federal Acquisition Regulations (FAR), Rights in Data and Copyrights

2023-02 All

NIST SP 800-37 Risk Management Framework for Information Systems and Organizations:

A System Life Cycle Approach for Security and Privacy

2 Appendix B and Appendix G

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

5 All

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

2 All

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

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

1.3.2 Reference Documents

Document Number Title Revision GSFC-STD-1000 Rules for the Design, Development, Verification, and Operation of Flight Systems

H

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

1.3.3 Project Applicable Documents

Document Number Title LNEXT-LANDIS-ICD-0001 Landsat Next Instrument Suite (LandIS) Interface

Requirements Document (IRD) LNEXT-LANDIS-PLAN-0052 Landsat Next Landsat Instrument Suite (LandIS) Contract Data

Requirements List (CDRL) and Data Item Descriptions (DID) LNEXT-LANDIS-REQ-0007 Landsat Next Landsat Instrument Suite (LandIS) Requirements

Document (LaRD) LNEXT-LANDIS-REQ-0010 Landsat Next Landsat Instrument Suite (LandIS) Simulator

Requirements Document (LandIS Sim RD) LNEXT-LANDIS-REQ-0016 Landsat Next Instrument Suite (LandIS) GSFC-STD-1000, Goddard Open Learning Design (GOLD) Rules, Applicability Matrix

LNEXT-MGMT-DESC-0005 Landsat Next Common Boilerplate LNEXT-SMA-PLAN-0019 Landsat Next Safety and Mission Surveillance Plan (SMASP) LNEXT-SMA-REQ-0013 Landsat Next (LNext) Instrument Mission Assurance

Requirements (IMAR) LNEXT-SYS-DESC-0003 Landsat Next Analytical Math Model Definitions (LAMMD) LNEXT-SYS-REQ-0005 Landsat Next Environmental Requirements Document

(LNERD)

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

(LSERD)

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

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

1.3.4 Project Reference Documents

Document Number Title LNEXT-SYS-DESC-0016 Landsat Next Geometric Error Budget (GEB) 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 C.

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 at a scale where natural and human-induced changes can be detected, differentiated, characterized, and monitored over time.

2.2 MISSION BACKGROUND

The President’s FY 2014 Budget Submittal to Congress directed NASA, in coordination with the United States Geological Survey (USGS), to initiate the definition of a sustainable, space-based, global land imaging capability for the Nation, ensuring continuity and to extend Landsat-class observations into the future while maintaining continuity record of the Earth’s land mass held in the National Satellite Land Remote Sensing Data Archive (NSLRSDA) at the USGS’ Earth Resources and Observation Science (EROS) Center.

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

The goal of Landsat Next is to continue the acquisition, archival, and distribution of multi-spectral imagery affording global, synoptic, and repetitive coverage of the Earth's land surfaces at a scale where natural and human-induced changes can be detected, differentiated, characterized, and monitored over time. This goal is in keeping with the Landsat programmatic goals stated in both the Commercial Space Act of 1998 (Public Law 105-303) and the Land Remote Sensing Policy Act of 1992 (Public Law 102-555). This policy requires that the Landsat Program provide data into the future that is sufficiently consistent with previous Landsat data to allow the detection and quantitative characterization of changes in or on the land surface of the globe.

Landsat Next continues the long-running partnership of NASA and USGS, with NASA providing the space and launch segments and USGS providing the ground system, providing the longest continuous global record of the Earth’s surface. The Landsat series of satellites have continuously acquired multispectral images of the global land surface since the launch of the Earth Resources Technology Satellite (ERTS, later renamed Landsat 1) in 1972. The Landsat data archive constitutes the longest continuous moderate-resolution record of the global land surface as viewed from space.

2.3 MISSION OBJECTIVES

Landsat Next has these major mission objectives:

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

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

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

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

2.4 MISSION IMPLEMENTATION

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

The Landsat Next post-launch nominal mission operations concept is shown graphically in the Figure below.

Figure 2.4-1 Landsat Next Operations Concept (Generated from Landsat Next Common

Mission Architecture Diagram LNEXT-SYS-DESC-0022 Rev -)

2.4.1 Space Segment

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

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

WRS-3.

2.4.2 Ground Segment

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

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

The MOC provides the primary means to control and monitor the Landsat Next constellation.

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

The GN includes geographically dispersed ground station resources for mission execution and includes both the Landsat Ground Network (LGN) and a wideband data routing capability, which transfers mission data to DPAS across wide area networks. The LGN provides communication capability for each observatory of the constellation for commanding and housekeeping data via the S-Band and will receive mission data from each observatory over a Ka-band downlink.

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

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

2.4.3 Launch Segment

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

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

3.0 WORK TO BE PERFORMED

The following sections, along with the LandIS Contract Data Requirements List (LNEXT- LANDIS-PLAN-0052), describe the specific work to be accomplished by the LandIS 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 LandIS(s).

The Contractor shall also provide the personnel, materials, equipment, and facilities necessary for support to Observatory Integration and Test (I&T), support to mission level activities such as Observatory environmental test, launch vehicle integration and on-orbit commissioning for the LNext Launch and special studies of the LandIS.

The Contractor shall deliver to the Government three (3) LandIS that are fully qualified, calibrated, and have demonstrated compliant and reliable operation in accordance with the requirements of this contract. The requirements stated within this document shall apply to each copy or instantiation of the LandIS as appropriate.

If the Government requests the Contractor to store the instrument suite after the LandIS Instrument Pre-Ship Review (IPSR), the Contractor shall provide personnel, materials, equipment, and facilities necessary to perform LandIS storage in accordance with the requirements of this contract.

3.1 PROJECT MANAGEMENT (PM)

The Contractor shall maintain a project office to manage the technical activities, mission assurance and resources of the LandIS project.

The Contractor shall appoint a dedicated Project Manager to direct and manage the LandIS project.

The Contractor’s Project Manager shall have responsibility for the overall technical performance, resource management, and schedule management of the contractual effort and all subcontracts.

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

For costing purposes, the duration of Project Management shall be until on-orbit acceptance.

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

The Contractor shall prepare a Project Management Plan that shall be maintained over the life of the Contract and a Final Report in accordance with Contract Deliverable Requirements List (CDRL) LandIS-PM-11 and LandIS-PM-4, respectively.

The Contractor shall prepare a Work Breakdown Structure Dictionary in accordance with CDRL LandIS-PM-13 in which the Contractor shall define how the Contractor plans to organize, plan, and report on the work being conducted.

The Contractor shall prepare an Organization Conflict of Interest (OCI) Avoidance Plan in accordance with CDRL LandIS-PM-15.

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

The Contractor shall prepare a Diversity, Equity, Inclusion and Accessibility (DEI&A) Plan in accordance with CDRL LandIS-PM-17.

The contractor shall review the DEI&A Plan annually and update as necessary.

The Contractor shall also perform all work necessary to successfully implement and complete the following program functions: Program Security, Property Management, Environmental Program Compliance, Export and International Traffic In Arms Regulation (ITAR) compliance, and Operation Security (OPSEC) custodianship.

3.1.1 Government Insight and Surveillance

The Contractor’s PM function shall provide to the Government, reporting and real-time insight into program status, as well as, technical and programmatic performance information on all of the Contractor’s responsibilities and activities performed under the contract. Insight is defined as the understanding necessary to knowledgeably concur with the Contractor’s actions through watchful observation, inspection, or review of program events, documents, meetings, tests, audits, hardware, etc., without approval/disapproval authority.

The Contractor shall open to Government attendance all Contractor and subcontractor internal data, reviews, audits, meetings and other activities within the scope of the contract. For access and insight activity, “Government” includes Government personnel and Government contractor personnel.

The Contractor shall notify the Contracting Officer (CO), the Government Resident Office and the Contracting Officer’s Representative (COR) of meetings, reviews or tests in sufficient time (nominally 10 working days) to permit meaningful Government participation.

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

The Contractor shall grant access for NASA mission assurance and other representatives to conduct audits, assessments, surveys and Government Mandated Inspection Points (GMIPs) as outlined in the Landsat Next Surveillance Plan, upon notice or as otherwise requested by the Government.

The Contractor shall supply documents, records, equipment, and a work area within the Contractor’s facilities for Government personnel.

The Contractor’s Project Management function shall provide to the Government reporting and at least weekly insight into program status, as well as technical and programmatic performance of all of the Contractor’s responsibilities performed.

The Contractor shall prepare and lead weekly teleconferences with the Government to discuss status, risks, issues, schedule and other business related activities.

The Contractor shall prepare and submit monthly status reports in accordance with CDRL LandIS-PM-1.

3.1.2 Control of Sensitive Information

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

3.1.3 Documentation

The Contractor shall develop, produce, deliver, and maintain all documentation required by the LandIS Contract Data Requirements List (CDRL).

CDRL items shall be delivered in accordance with LandIS CDRL table.

All CDRLs shall be delivered to the NASA CDRL delivery portal (Box is being utilized at this time).

All CDRLs shall include a standard coversheet. The coversheet shall include CDRL number, due date and maturity. If a CDRL is being redelivered, the coversheet shall indicate redelivery.

All efforts, including the performance of tests and analyses not otherwise explicitly stated in other parts of the SOW, but determined jointly by the Contractor and the Government to be mission critical, shall be performed and documented by the Contractor.

All documentation, data, and analyses generated for or applicable to, the LandIS design, fabrication and test, whether formal or informal, deliverable or non-deliverable shall be made available to the Government and Government support Contractor’s with appropriate Non- Disclosure Agreements (NDAs) in place upon request.

This information shall be provided electronically through a Contractor provided web portal.

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

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

Any artifact to be used for verification shall be submitted as a deliverable item. No informal or engineering releases will be accepted for verification purposes. All verification artifacts must be under the Contractor configuration management control.

PDFs of all drawing and models (SE-4, SE-5, SE-15, SE-16), along with the native formats, shall be submitted to the NASA CDRL portal.

The Contractor shall provide a drawing list that includes the hierarchy/structure of drawings and models.

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

All photo and media shall be submitted as a deliverable item. This includes press photos and photos that may have been informally requested by the project. All photos/media used in public places must be vetted by NASA export control.

The Contractor shall provide redlines with all deliverable document updates after the final/baselined version has been submitted. For requirements documentation, the redline process must be reviewed by NASA requirements management.

NASA will provide comments to deliverable items in an EXCEL format. The Contractor shall respond to the comments according to the CO direction.

When response to requirements is required by the CO, the Contractor shall provide a summary response in the excel file and include the excel file with the deliverable item.

3.1.4 Reviews and Meetings

The reviews listed in this section should not be considered a comprehensive set of reviews for the Contractor’s program. Additional reviews that the Contractor deems necessary to successfully execute the program may be conducted at the Contractor’s discretion. The Contractor shall notify the Government at least 10 working days in advance of lower level Contractor subsystem reviews to allow the Government time to attend the review as part of its oversight activities.

3.1.4.1 Major Reviews

All major reviews will be convened and review boards appointed and chaired by the Government. The Contractor shall demonstrate compliance with the review success criteria of, Criteria for Project Flight Critical Milestone Reviews (GSFC-STD-1001), as applicable to spaceflight instruments.

The Contractor shall respond as required to action items assigned by the Government.

The Contractor shall prepare and present their portion of these reviews, as appropriate, ensuring that content is complete and accurate.

3.1.4.1.1 Instrument Reviews

The Contractor shall host, prepare and present instrument reviews and provide review packages in accordance with the stated CDRL.

If multiple imaging sensors are developed to meet the requirements of this contract, then the Contractor shall conduct the following reviews for each sensor.

• Instrument System Requirements Review (ISRR), CDRL LandIS-RE-1

• Instrument Integrated Baseline Review (IIBR), CDRL LandIS-RE-8

• Instrument Preliminary Design Review (IPDR), CDRL LandIS-RE-2

• Instrument Critical Design Review (ICDR), CDRL LandIS-RE-3

• Instrument Integration Readiness Review, CDRL LandIS-RE-10

• Instrument Pre-Environmental Review (IPER), CDRL LandIS-RE-4

• Instrument Pre-Ship Review (IPSR), CDRL LandIS-RE-5

The Goddard Space Flight Center (GSFC) Project Office, the GSFC System Review Office (SRO), and the Instrument Contractor will agree on what level of detail is appropriate for each review.

The Contractor shall assume that each review requires four days to complete.

No later than six weeks prior to each review, the Contractor shall in concert with the project, develop a review agenda.

The Contractor shall conduct dry runs of all reviews with the Government no later than two weeks prior to the formal reviews.

The Contractor shall host and work with the Government project and review team an additional day following all instrument reviews to discuss and address issues raised and actions assigned at the reviews.

The Government will convene a delta review if the success criteria for a review are not met to the Government’s satisfaction.

The Contractor shall host these delta reviews and prepare and present these reviews.

Each review shall be considered complete when: (1) the Government chairperson for the review provides notice that the criteria for successful completion have been satisfactorily met; (2) all RFAs deemed ‘critical’ by the chairperson have been closed to the Government’s satisfaction and (3) all CDRLs required at or prior to that review have been delivered and found to be acceptable by the Government.

Acceptance by the Government may require that all CDRL item modification recommendations resulting from Government “Review” or required for Government “Approval” have been incorporated by the Contractor. The criticality of RFA’s will be determined and documented by the review chairperson when submitted to the Contractor.

3.1.4.1.2 Spacecraft Reviews

The Contractor shall participate in person and support the spacecraft contractor in preparation for the following spacecraft reviews:

• Spacecraft System Requirements Review (SSRR)

• Spacecraft Preliminary Design Review (SPDR)

• Spacecraft Critical Design Review (SCDR)

• Spacecraft-Instrument Integration Readiness Review The LandIS Contractor shall take direction from the Government regarding material inputs for the spacecraft reviews.

The Contractor shall assume three days of attendance for three people at the spacecraft contractor’s facility for each review.

The Contractor shall assume the location of spacecraft reviews to be at the yet to be selected spacecraft bus provider’s facility somewhere within the continental United States (U.S.).

3.1.4.1.3 Ground System Reviews

The Contractor shall participate in and support the Government in preparation for the following Ground System reviews:

• Data Processing and Archive System (DPAS) System Requirements Review

• DPAS Preliminary Design Review

• DPAS Critical Design Review (CDR)

• Landsat Mission Operations Center (MOC) Requirements Review

• MOC Preliminary Design Review

• MOC Critical Design Review

• Ground Preliminary Design Review

• Ground Critical Design Review The Contractor shall present instrument command and telemetry information and data processing algorithm information and other material as appropriate.

The Contractor should assume three days of attendance for two people at each Ground System review at the U.S. Geological Survey Earth Resources Observation and Science (EROS) center in Sioux Falls, South Dakota (SD).

3.1.4.1.4 LNext Mission Level Reviews

The Contractor shall prepare and present in person material at each of the following Mission Level reviews:

• System Requirements Review(SRR)/Mission Definition Review (MDR)

• Preliminary Design Review (PDR)

• Critical Design Review (CDR)

• System Integration Review (SIR)

• Pre-Environmental Review (PER)

• Pre-Ship Review (PSR)

• On-Orbit Acceptance Review (OAR) (CDRL LandIS-RE-9) The Contractor shall prepare their portion of the above Mission Level reviews in accordance with CDRL LandIS-RE-6 and LandIS-RE-9.

The Government leads these Mission Level reviews and will also be presenting material.

The Contractor shall respond to action items as requested by the Government.

The Contractor shall participate in dry runs of all Mission-Level Reviews with the Government approximately two weeks in advance of the reviews.

The Contractor shall assume that the Mission-level SRR/MDR, PDR, CDR, SIR, PER, PSR, and OAR will take four days and that dry runs will take two days of Contractor support.

The Contractor shall assume Mission-level SRR/MDR, PDR, CDR, and OAR will take place in Greenbelt, Maryland (MD) and that the SIR, PER, and PSR will take place at the yet to be selected spacecraft Contractor’s facility somewhere within the continental U.S.

The Contractor may support Mission-level SRR/MDR, PDR, CDR, and OAR dry runs in person or by teleconference and electronic web interface for presentation materials, assuming that the Contractor has electronic services compatible with those of the Government. For estimating purposes, the Contractor should assume three people attending each Mission Level review.

The Contractor shall also attend and support as necessary the following additional Mission-Level Reviews:

• Mission Operations Review (MOR)

• Flight Operations Review (FOR)

• Operational Readiness Review (ORR)

• Post-Launch Assessment Review (PLAR) The Contractor shall assume their participation in the Mission-level MOR, FOR, ORR, and PLAR will require three days of support and that dry runs will require a half-day of support.

The Contractor shall assume the location of the MOR, FOR, and ORR will be Greenbelt, MD and the location of the PLAR will be Sioux Falls, SD.

The Contractor shall support Mission-level MOR, FOR, ORR, and PLAR dry runs by teleconference.

3.1.4.2 Engineering Peer Reviews

The Contractor shall define and implement a set of robust and comprehensive EPRs for the hardware and software subsystems of the LandIS commensurate with the scope, complexity and acceptable risk of the product.

The Contractor shall submit the Engineering Peer Review Plan in accordance with CDRL LandIS-PM-5.

The Contractor shall chair and host EPRs at the Contractor’s facilities with Government participation on the review panels.

The Contractor shall document EPRs in accordance with CDRL LandIS-RE-7, Engineering Peer Review Data Packages.

The Contractor shall track action items from EPRs and report on status at each Instrument Level review.

The Contractor shall maintain EPR presentation and action closure documentation for the duration of the contract and provide electronic access to the Government.

The Contractor shall systematically and comprehensively peer review the product at the individual subsystem level, software module level, and at component (“box”) and lower levels of assembly, as appropriate.

In addition, packaging reviews shall be conducted on electrical and electromechanical components in the flight system. Subsystem and component level design and acceptance reviews

(e.g., Telescope CDR, Calibration Assembly CDR, Flight Software (FSW) CDR, sub-system acceptance reviews, etc.) are considered to be EPRs and subject to this procedure.

The Contractor shall conduct multiple peer reviews, as appropriate, over the lifecycle of each subsystem and component, with content consistent with the evolving design and development.

As a minimum, the Contractor shall complete a comprehensive set of subsystem or lower-level peer reviews prior to instrument PDR and again prior to instrument CDR.

Successful completion of these Pre-IPDR and Pre-ICDR EPRs and resolution of associated technical issues and actions is considered to be an important aspect of entry criteria in the formal review process.

The Contractor shall also use EPRs for the focused evaluation of concepts, designs, plans and processes associated with combinations of subsystems and system functions and performance that cross traditional subsystem or discipline boundaries. Examples include fault detection and correction; or solutions to address, for example, pointing, thermal or contamination constraints.

Requirements for additional Software Peer Reviews are covered in section 3.4.10.5 of this SOW.

In addition to other standard discipline EPRs, the Contractor shall, as a minimum conduct EPRs to cover the following specific items:

1. Sensor Focal Plane Assembly (FPA)

2. LandIS data system, including the data preprocessing and compression as well as interface to the spacecraft

3. Algorithm development

4. Mechanism design and test procedures

5. Opto-mechanical design and alignment processes

6. Sensor calibration design and test

7. Instrument Integration & Test

8. Observatory-Level Integration & Test

9. Fault detection and correction

10. Flight Software development

11. Command and control procedures

12. System engineering and interfaces

13. Single Event Effect Criticality Analysis (SEECA)

3.1.4.2.1 Field Programmable Gate Array (FPGA) Peer Review

In addition to the above peer reviews the Contractor shall support the GSFC review of all FPGAs.

The Contractor shall flow the FPGA requirements to subcontractors.

The Contractor shall deliver an FPGA Development Plan per CDRL LandIS-SE-45.

The Contractor shall complete a Government provided FPGA Checklist.

The Contractor shall generate Verification Cross Reference Matrix (VCRM), FPGA Specification and Block diagrams per internal standards, shall generate design and development details per internal standards and shall generate timing analysis internal to the FPGA functions and including the Analog-to-Digital (ADC) and Digital-to-Analog (DAC) interfaces external to the FPGA.

The Contractor shall deliver a FPGA Design Data Package for each FPGA design used for the LandIS per CDRL LandIS-SE-46.

The Contractor shall for each FPGA/Application-Specific Integrated Circuit (ASIC) generate a synthesesis (including timing violation…