Attachment_E_-_Landsat_Multi-Satellite_Operations_Center_(LMOC)_Requirements_Document_1.pdf

LSDS-1739

Version 9.0

Department of the Interior U.S. Geological Survey

Landsat Multi-Satellite Operations Center (LMOC) Requirements Document

March 2022

- ii - LSDS-1739

Executive Summary

This Landsat Mission Operations (LMO) – Landsat Multi-Satellite Operations Center (LMOC) Requirements Document (LMOCRD) contains the Level 4 requirements to support a Multi-Satellite Operations Center for Landsat 9 (L9) and Landsat 8 (L8).

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

This document is under Landsat Ground System (GS) Configuration Control Board (CCB) control. Please submit changes to this document, as well as supportive material justifying the proposed changes, via a Change Request (CR) to the Process and Change Management Tool.

- iii - LSDS-1739

Contents

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

Document History ............................................................. Error! Bookmark not defined.

Contents ........................................................................................................................ iii

Section 1 Introduction

1.1 Background

1.2 Purpose and Scope

1.3 Document Organization

1.4 Terminology

Section 2 Landsat Multi-Satellite Operations Center (LMOC) Overview

2.1 Telemetry & Command (T&C)

2.2 Data Management (DM)

2.3 Trending & Analysis (T&A)

2.4 Flight Dynamics (FDS)

2.5 Mission Planning (MPS)

2.6 Alerts and Notifications (ANS)

2.7 Analytical Modeler (AM)

2.8 Infrastructure (Inf)

Section 3 LMOC Level 4 Requirements

3.1 General

3.2 Security

3.3 Infrastructure

3.4 Facility

3.5 Mission Planning

3.5.1 General Image Planning and Scheduling Requirements

3.5.2 Collection Requests

3.5.3 Image Data Collection Schedules

3.5.4 Interval Planning

3.5.5 Constraint Checking

3.5.6 Mass Storage Modeling

3.5.7 Contact Scheduling

3.5.8 Activity and Request Scheduling

3.5.9 Mission Data Management

3.6 Flight Dynamics

3.6.1 Orbit Determination and Products

3.6.2 Orbit Maneuver Planning

3.6.3 Attitude Maneuver Planning

3.6.4 Flight Dynamics Performance Monitoring

3.7 Telemetry and Command

3.7.1 Project Database

3.7.2 Command

3.7.3 Telemetry

3.7.4 Displays

3.7.5 Limit Checking

- iv - LSDS-1739

3.7.6 T&C Operations

3.7.7 T&C Simulator

3.8 Test and Launch Support

3.9 bLMOC

3.10 Monitor and Trending

3.11 Controlled Repository

3.12 Analytical Model

Appendix A Acronyms

References

- 1 - LSDS-1739

Section 1 Introduction

The Landsat mission is a joint mission formulated, implemented, and operated by the National Aeronautics and Space Administration (NASA) and the Department of the Interior (DOI) U.S. Geological Survey (USGS). Landsat is a remote sensing satellite mission providing coverage of the Earth’s land surfaces. The Landsat series of satellites continue the 40+ years of global data collection and distribution.

1.1 Background

The goal of Landsat is to continue the collection, archival, and distribution of multispectral 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. The Landsat programmatic goals are stated in the United States Code, Title 15 Chapter 82 “Land Remote Sensing Policy” (derived from the Land Remote Sensing Policy Act of 1992). This policy requires that the Landsat Project provide data into the future that are sufficiently consistent with previous Landsat data to allow the detection and quantitative characterization of changes in or on the surface of the Earth. The highly successful Landsat series of missions have provided satellite coverage of the Earth’s continental surfaces since 1972. The data from these missions constitute the longest continuous record of Earth’s surface as seen from space.

1.2 Purpose and Scope

The Landsat Multi-Satellite Operations Center Requirements Document (LMOCRD) establishes the Level 4 requirement set for the Landsat Mission Operations (LMO) – Landsat Multi-Satellite Operation Center (LMOC) supporting both Landsat 8 (L8) and Landsat 9 (L9). This requirement set encompasses the LMOC functionality, performance specifications, and interfaces required to support both missions and serves to verify both Missions Operations functionality in the LMOC architecture.

1.3 Document Organization

This document contains the following sections:

• Section 1 introduces the Landsat missions

• Section 2 provides a high-level overview of LMOC

• Section 3 provides the Level 4 LMOC requirements

• Appendix A provides an acronyms list

1.4 Terminology

A requirement is a specification of a function, capability, interface, or constraint with which the system design must be compliant, verifiable, and have a proven achievement during the mission.

- 2 - LSDS-1739

A shall statement designates a mandatory requirement the Contractor must comply with. Any deviations from these contractually imposed, mandatory requirements require the approval of the Contracting Officer.

A mission attribute for a requirement states the applicability of that requirement toward the particular mission(s).

A Unique Scene ID is the term used to scope the L8 Orbit & Path/Row and L9 Scene ID values for image scheduling.

Command and Data Handling (C&DH) Memory is the term for the local, non-mass storage space for stored housekeeping telemetry.

Observatory Mass Storage is the term used for the mass storage onboard the observatory such as the Solid State Recorder (SSR).

Observatory On-Board Data Storage is the term used to cover both the Observatory Mass Storage and C&DH Memory.

A Collection Request is the term used to identify either and/or both a Special Collection Request (SCR) and a Calibration Collection Request (CalCR).

An LTAP Collection Request is the term used to identify the Landsat 9 Long-Term Acquisition Plan (LTAP) base image acquisition request, not to be confused with a Collection Request.

- 3 - LSDS-1739

Section 2 Landsat Multi-Satellite Operations Center (LMOC) Overview

The LMOC handles management of image and calibration acquisitions, commands the generation for all Observatory activities, and monitors Observatory health, safety, and performance. The LMOC comprises the facility and systems that include the capabilities identified in the following sections.

2.1 Telemetry & Command (T&C)

Galaxy is used to provide archive and acquisition of real-time S-Band telemetry from the various antenna complexes, generate and encrypt commands for uplink, manage the Solid State Recorder (SSR), and execute time-based automation tasks.

2.2 Data Management (DM)

Mercury manages file distribution and event-based automation within the LMOC. A central agent administers configurations and provides web portal services while various remote agents perform actual automation work.

2.3 Trending & Analysis (T&A)

Stars ingests S-Band real-time, S-Band Stored State of Health (SSOH), and X-Band SSOH data; Stars also generates statistical data. It produces both automated and user interface outputs in plot and various machine-readable formats.

2.4 Flight Dynamics (FDS)

FreeFlyer, FreeFlyer Meridian, and Multi-Mission Three-Axis Stabilized Spacecraft (MTASS) are used to perform orbit determination and propagation, orbit maintenance, attitude prediction, attitude determination, and Onboard Computer (OBC) sanity checks.

2.5 Mission Planning (MPS)

Collection Planning and Analysis Workstation (CPAW) and Systems Toolkit (STK) Scheduler process input from flight dynamics, various collection requests from Data Processing and Archive System (DPAS), and other sources to generate the contact schedules and activity plans for the spacecraft and ground system.

2.6 Alerts and Notifications (ANS)

Graylog and What's Up Gold process log messages in order to generate alert notifications to the Flight Operations Team (FOT) Engineers.

2.7 Analytical Modeler (AM)

The Joint Activity Simulation for Observatories and Networks (JASON) models mission behavior in a multi-satellite system, including expected spacecraft and ground system activities and realistic failure scenarios.

- 4 - LSDS-1739

2.8 Infrastructure (Inf)

An amalgamation of Commercial Off-the-Shelf (COTS) and open source software, which provides services related to network, compute, disk, authentication, remote access, security, backups, video distribution, and other tools.

- 5 - LSDS-1739

Section 3 LMOC Level 4 Requirements

3.1 General

LMOC-2424: The LMOC shall support a mission life of at least 15 years.

Rationale: The Project Mission goal expresses the need for a scalable system since the LMOC will need to support observatory ops through decommissioning.

Mission: Landsat 8 and Landsat 9

LMOC-2413: The LMOC shall have an availability of 99.9% for observatory telemetry and commanding operations.

Rationale: To ensure command and telemetry system along with the networking within the LMOC, is available over the period of a month, to maintain the health and safety of the Observatory.

Mission: Landsat 8 and Landsat 9

LMOC-2416: The LMOC shall ensure protection exists from a single point of failure within the critical telemetry and command functions.

Rationale: The T&C system must have no single point of failures that will preclude observatory health and safety.

Mission: Landsat 8 and Landsat 9

LMOC-2415: The LMOC shall have a mean time to restore telemetry and commanding operations within 1 minute or less.

Rationale: This provides for a timely transfer of command authority and telemetry monitoring from one system to another in the event of a failure.

Mission: Landsat 8 and Landsat 9

LMOC-2417: The LMOC shall have a combined availability of 98.5% for all non-telemetry and commanding subsystems.

Rationale: To ensure all other LMOC subsystems are available without the stringent constraints of the T&C system. Availability is to be calculated as total downtime per month on a per-subsystem basis.

Mission: Landsat 8 and Landsat 9

LMOC-2427: The LMOC shall be able to simultaneously operate the observatory and observatory simulators without impact to mission operations.

Rationale: The lMOC must be able to verify and validate activities with observatory simulators (e.g. LSIMSS, Softsim/Softbench, and SOS) while mission operations are on-going.

Mission: Landsat 8 and Landsat 9

LMOC-5189: The LMOC shall be able to add and remove systems with no loss in data or interruption to operations.

Rationale: The real-time system is expected to be fault-tolerant of the loss of operational, backup or off-line systems. This drives the expectation that all subsystems

- 6 - LSDS-1739

will be modular and scalable in design, with a warm backup plug and play architecture so that the redundant copy of that subsystem is available for user initiation on demand.

Mission: Landsat 8 and Landsat 9

LMOC-3530: The LMOC shall make available to users one orbit's worth of stored housekeeping data within 30 minutes of receipt of the data from GNE.

Rationale: The full end to end transfer, processing, display of stored telemetry needs to be completed in a timely manner for all operations.

Mission: Landsat 8 and Landsat 9

LMOC-3442: The LMOC shall generate a conflict-free stored command load within 2 hours, including user interaction time, starting from the beginning of the scheduling process.

Rationale: Supports fast turnaround for operations efficiency, anomaly response, and short-notice emergency requests.

Mission: Landsat 8 and Landsat 9

LMOC-2422: The LMOC shall support a single 8-hour by 5-day shift (M-F) approach and operate autonomously whenever not staffed.

Rationale: LMOC automation required to support a minimal staffing level for nominal operations.

Mission: Landsat 8 and Landsat 9

LMOC-2423: The LMOC shall have the ability to perform nominal operations autonomously for at least 72 hours.

Rationale: The LMOC needs to support nominal operations autonomously during a 3-day weekend at a minimum.

Mission: Landsat 8 and Landsat 9

LMOC-3448: The LMOC automation functions shall be capable of being enabled or disabled.

Rationale: All automation should be capable of being disabled to support ongoing operations as required. Manual activities are needed during L&EO, commissioning and during anomalous conditions.

Mission: Landsat 8 and Landsat 9

LMOC-2428: The LMOC shall allow execution of operations both autonomously and by user input through a command line interface.

Rationale: Provides capability to execute scripts to perform LMOC activities.

Mission: Landsat 8 and Landsat 9

LMOC-5122: The LMOC shall have a test environment to allow for verification of changes before they are operationally implemented.

Rationale: The Test Environment is needed to test software, hardware, operating system, drivers, application, scripts, procs and operational concept changes for each sub-system so they don' t impact operational systems.

- 7 - LSDS-1739

Mission: Landsat 8 and Landsat 9

LMOC-2426: The LMOC shall support training, testing, and system maintenance while meeting all requirements.

Rationale: LMOC training, testing and systems maintenance activities shall not impact on-going operations.

Mission: Landsat 8 and Landsat 9

LMOC-5142: The LMOC shall tag all operational products by Spacecraft ID.

Rationale: Allows LMOC personnel and subsystems to correlate simulated and spacecraft data by Spacecraft ID to delineate between Missions.

Mission: Landsat 8 and Landsat 9

LMOC-2418: The LMOC shall time tag all observatory and ground system data.

Rationale: Allows operator to correlate ground system and spacecraft data output displays & reports.

Mission: Landsat 8 and Landsat 9

LMOC-2410: The LMOC shall use Universal Time Coordinated (UTC) for all systems, displays and products.

Rationale: Utilize standard time reference across all LMOC systems.

Mission: Landsat 8 and Landsat 9

LMOC-2430: The LMOC shall utilize common time formats across LMOC systems.

Rationale: The LMOC needs to utilize a common time format for all operations products generated in the LMOC. Additionally the LMOC systems and displays also need to maintain a consistent time zone and time format's where possible.

Mission: Landsat 8 and Landsat 9

LMOC-2425: The LMOC shall employ a time stamp resolution of at least one millisecond for all operational products used and stored within the LMOC.

Rationale: Define time stamp precision within the LMOC for all operational products.

Mission: Landsat 8 and Landsat 9

LMOC-2421: The LMOC shall generate and locally retain logs from all LMOC systems.

Rationale: Maintaining the record of all system interactions, events is useful for both troubleshooting and supporting operational activities and for IT Security incidents.

Mission: Landsat 8 and Landsat 9

LMOC-5109: The LMOC shall distinguish between system and user actions in the system logs.

Rationale: Distinguishing between system and operator actions is an important part of tracking and optimizing operational activities and for IT Security incidents.

Mission: Landsat 8 and Landsat 9

- 8 - LSDS-1739

LMOC-2431: The LMOC shall provide users the ability to print documents, displays, logs, schedules and operational products.

Rationale: Provides the capability to generate hard copies vs. soft copies of various products.

3.2 Security

LMOC-2433: The LMOC shall employ security controls of NIST PUB 800-53 moderate level system in accordance with corresponding USGS guidance within the LMOC IT Security Control Matrix.

Rationale: The LMOC IT security posture must meet NIST PUB 800-53 for a moderate threat level system. The USGS IT Control Matrix adheres to as part of compliance with

NIST PUB 800-53.

Mission: Landsat 8 and Landsat 9

LMOC-5140: The LMOC shall restrict access to LMOC systems to only authorized personnel.

Rationale: The LMOC needs the ability to provide users with individual and group policy based access to LMOC Systems, Websites and Applications by using an authentication mechanism (e.g. Active Directory, OpenLDAP).

Mission: Landsat 8 and Landsat 9

LMOC-5199: The LMOC shall support multifactor authentication for user authentication to LMOC systems.

Rationale: LMOC users need multifactor authentication to access consoles, systems, remote access. (e.g. Smart Card, RSA).

Mission: Landsat 8 and Landsat 9

LMOC-2437: The LMOC shall support the Government-furnished system configuration monitoring tool without impacting mission operations.

Rationale: The Government is providing a software tool to consolidate LMOC system configuration information for security oversight. LMOC systems will need to be configured in a way that allows the tool to receive information (e.g. OS version).

Mission: Landsat 8 and Landsat 9

LMOC-2435: The LMOC shall support system patches and updates without impacting mission operations.

Rationale: Security policies require timely patching and updates of systems. The LMOC must be able to handle IT Security activities and ongoing operations simultaneously.

Mission: Landsat 8 and Landsat 9

LMOC-2434: The LMOC shall support credentialed scans without impacting mission operations.

- 9 - LSDS-1739

Rationale: Security policies enforce the need to periodically execute scans on operational systems. The LMOC needs to be able to support these while supporting operations and the availability constraints.

Mission: Landsat 8 and Landsat 9

LMOC-2436: The LMOC shall forward all system logs to the Government-furnished log monitoring system.

Rationale: The Government is providing a centralized system for consolidation of LMOC system logs for security oversight for the life of the mission. Therefore LMOC systems will need to interface to it by sending logs.

Mission: Landsat 8 and Landsat 9

LMOC-38943: The LMOC shall employ security controls of the Department of Homeland Security (DHS) High Value Asset (HVA) Control Overlay in accordance with corresponding USGS guidance within the LMOC IT Security Control Matrix.

Rationale: The LMOC IT Security Control Matrix also meet the control enhancements listed in the DHS HVA Control Overlay.

3.3 Infrastructure

LMOC-2442: The LMOC shall receive a master time reference from the Government provided source.

Rationale: Synchronize LMOC system time to common source.

Mission: Landsat 8 and Landsat 9

LMOC-2443: The LMOC shall synchronize to the Government provided master time reference.

Rationale: Maintain time consistency across all LMOC workstations.

Mission: Landsat 8 and Landsat 9

LMOC-5188: The LMOC shall provide a centralized Domain Name System (DNS) to resolve system host names and IP addresses for all systems and devices connected to the LMOC network.

Rationale: Use of local, centralized DNS is intended to eliminate dependency on external DNS services, allow simple name resolution and access of LMOC systems and relevant external hosts, and provide a single point of update for operational changes (i.e. allow updates to be resolved quickly in the event of a host failure or other local or remote system name/IP address change).

Mission: Landsat 8 and Landsat 9

LMOC-5206: The LMOC shall provide a centralized location for the management of LMOC documentation.

Rationale: The LMOC needs a central location that can be utilized for archiving and retrieval of approved SOP's, COP's and any additional LMOC and bLMOC specific documentation.

- 10 - LSDS-1739

Mission: Landsat 8 and Landsat 9

LMOC-5111: The LMOC shall provide web based access to the centralized location for LMOC documentation.

Rationale: The LMOC needs the ability to access the documentation system remotely via a web based interface, allow the creation of LOP's, COP's (ie. Wiki) and to access any other additional LMOC and bLMOC specific documentation.

Mission: Landsat 8 and Landsat 9

LMOC-5139: The LMOC shall provide authorized users with policy based access to all LMOC documentation.

Rationale: The LMOC needs the ability to provide users with individual or group policy based access to read and write LMOC specific documentation that is stored at the centralized location.

Mission: Landsat 8 and Landsat 9

LMOC-3647: The LMOC shall provide configuration management of LMOC systems and software.

Rationale: Configuration management is needed to prevent unauthorized changes from being applied and affecting the LMOC systems and software. This includes the management of software, documentation and scripts used by operations that handled on a system level which require CM control.

Mission: Landsat 8 and Landsat 9

LMOC-5110: The LMOC shall provide the ability to rapidly deploy new systems using a pre-existing base image within 30 minutes.

Rationale: Operations needs the ability to have pre-configured operating system images with any applicable FOT or Infrastructure subsystem software deployed in a timely fashion, this excludes any rapid deployment of large archives or other hardware specific items.

Mission: Landsat 8 and Landsat 9

LMOC-2444: The LMOC shall provide an web based event countdown clock that displays upcoming mission events.

Rationale: All spacecraft and ground activities need to be displayed, in reference to UTC, in a highly accessible manner for use by operations.

Mission: Landsat 8 and Landsat 9

LMOC-3627: The LMOC shall provide authorized users with policy based remote access to the LMOC systems, websites and applications.

Rationale: Remote access for authorized users is needed for operations and development. (ex. Engineers and other authorized users (e.g. FOT, CVT, Spacecraft Vendors) need access to real-time and stored observatory telemetry, trending and analysis, engineering data and operational products outside of the LMOC.)

- 11 - LSDS-1739

LMOC-2420: The LMOC shall support up to 30 concurrent remote users.

Rationale: Remote access capabilities for real-time and stored observatory telemetry, trending and analysis, engineering data and operational products access by FOT, spacecraft, instrument, government and support personnel must be robust enough to handle multiple users simultaneously.

Mission: Landsat 8 and Landsat 9

LMOC-5186: The LMOC shall perform automated backups of all critical systems.

Rationale: Critical LMOC systems need to be backed up frequently to ensure no impact to operations occurs if any fault happens to those critical systems.

Mission: Landsat 8 and Landsat 9

LMOC-5187: The LMOC shall retain all system backups for at least 30 days.

Rationale: LMOC backups only need to be kept 30 days as system images older than 30 days may no longer be relevant to operations.

Mission: Landsat 8 and Landsat 9

LMOC-6107: The LMOC shall be able to restore data from all critical system backups.

Rationale: LMOC backups need to be utilized during operations to recover whole systems along with individual files within a backup to the imaged system.

3.4 Facility

LMOC-5200: The LMOC shall be able to accommodate simultaneous activities for both Landsat 8 and Landsat 9 observatories.

Rationale: The LMOC facility needs to allow for multiple spacecraft operations to occur at the same time without negatively impacting either mission.

Mission: Landsat 8 and Landsat 9

LMOC-2449: The LMOC shall support combined Landsat 8 and Landsat 9 operations within an area not to exceed 1200 sq. ft.

Rationale: Define LMOC operations room space allocations; this does not include space for production systems. This square footage includes the space lost due to furniture and facilities equipment (ex. 800 sq. ft. usable space).

Mission: Landsat 8 and Landsat 9

LMOC-2450: The LMOC servers and network equipment for both Landsat 8 and Landsat 9 shall reside within 6, 48-U racks.

Rationale: Constrain space needs within the LMOC Equipment Room.

Mission: Landsat 8 and Landsat 9

LMOC-2448: The LMOC shall utilize redundant uninterruptible power for all LMOC systems.

Rationale: Provide power redundancy to prevent localized power interruptions from affecting operations by using different facility feeds and facility Uninterruptable Power

- 12 - LSDS-1739

Supplies (UPS). This includes the use of Automatic Transfer Switch (ATS) for suppling power to single Power Supply Units (PSU) devices like workstations and direct redundant Power Distribution Units (PDU) feeds to dual PSU devices like servers.

Facility power outages and maintenance occur infrequently which can cause interruptions to LMOC Operations.

Mission: Landsat 8 and Landsat 9

LMOC-2439: The LMOC shall operate in a temperature range from 10 degrees C to 29 degrees C.

Rationale: Equipment within LMOC to operate within temperature range for LMOC facility Mission: Landsat 8 and Landsat 9

LMOC-2440: The LMOC shall operate in a relative humidity range from 40% to 60%.

Rationale: Equipment within LMOC to operate within humidity range for LMOC facility.

Mission: Landsat 8 and Landsat 9

LMOC-2441: The LMOC shall monitor the environmental conditions of the Spacecraft Observatory Simulator's (S/OS) and notify LMOC users if any conditions exceed a user-defined threshold.

Rationale: Notify personnel of potential environmental issues such as when temperature, humidity or water within the facility that houses the Landsat 9 and Landsat 8 S/OS's exceed an acceptable threshold. Equipment could be at risk if conditions rise to dangerous levels.

Mission: Landsat 8 and Landsat 9

LMOC-2451: The LMOC shall provide dual displays for all user accessible workstations.

Rationale: Provide display space for LMOC operations Mission: Landsat 8 and Landsat 9

LMOC-2445: The LMOC shall provide wall mounted screen displays viewable from any workstation within the LMOC.

Rationale: The mounted displays will show the heads-up status such as upcoming passes, trending data, telemetry displays which may be best displayed to the entire

LMOC.

Mission: Landsat 8 and Landsat 9

LMOC-2446: The LMOC shall provide users the ability to configure the information routed to wall mounted displays.

Rationale: This includes the use of a multi-in/out matrix switch, wireless keyboards & mice or thin clients to facilitate the mounted displays. Personnel within the LMOC should have the ability to control any computer attached to a wall-mounted display.

Mission: Landsat 8 and Landsat 9

LMOC-5146: The LMOC shall be able to output a single display of each LMOC subsystem on the wall mounted displays.

- 13 - LSDS-1739

Rationale: The FOT uses this functionality to share system displays with a large group during key activities, such as during post-launch deployments.

Mission: Landsat 8 and Landsat 9

LMOC-2447: The LMOC shall provide a black/white and color printing capability within the LMOC.

Rationale: Printers are required since hard copy of some items will be necessary.

3.5 Mission Planning

3.5.1 General Image Planning and Scheduling Requirements

LMOC-5124: The LMOC shall support a planning period of 1 to 72 hours.

Rationale: The planning period covers all planned activities for all operational concepts (e.g. planning, scheduling and command load generation). By default Landsat 8 uses a 72 hour load, but certain operational constraints such as early testing could result in single-orbit loads Mission: Landsat 8

LMOC-5232: The LMOC shall support a planning period of 1 to 96 hours.

Rationale: The planning period covers all planned activities for all operational concepts (e.g. planning, scheduling and command load generation). By default Landsat 9 uses a 96 hour load, but certain operational constraints such as early testing could result in single-orbit loads Mission: Landsat 9

LMOC-6110: The LMOC shall have the ability to schedule image data collections consisting of any instrument combination.

Rationale: Nominally, image data collections include both instruments, but single-instrument collection must not be precluded. For Landsat 9 this means the ability to schedule OLI-2 only, TIRS-2 only, and OLI-2 + TIRS-2 collections; for Landsat 8 it encompasses OLI only, TIRS only, and OLI + TIRS collections.

Mission: Landsat 8 and Landsat 9

LMOC-2457: The LMOC shall incorporate the WRS-2 model as defined in GSFC 429- 02-07 LDCM Worldwide Reference System-2 Memorandum (WRS-2) for image collection planning.

Rationale: The LMOC uses the WRS-2 memorandum as the definition and model of the WRS-2 grid, and must build the WRS-2 grid specification into LMOC systems as appropriate in order to maintain orbit and precisely execute imaging acquisition for processing requests and generating operational products (e.g. WRS2TTT).

Mission: Landsat 8 and Landsat 9

LMOC-2458: The LMOC shall generate and maintain a WRS-2 path/row to time translation table (WRS2TTT) per the DPAS-MOC ICD.

- 14 - LSDS-1739

Rationale: The WRS2TTT product associates WRS-2 grid traversal with predicted collection time, and as such is pivotal for image collection planning and scheduling activities, and also for later use in reporting across the ground system. The WRS2TTT contains the time at which each path/row in the WRS-2 grid traversed over the reported planning cycle will be at the observatory nadir position, the solar angle for each path/row, and the cross-track error for each path/row (quantifies the deviation, perpendicular to nadir point flight direction, from the WRS-2 compliant position).

Mission: Landsat 8 and Landsat 9

LMOC-2459: The LMOC shall provide the WRS2TTT to DPAS per the DPAS-MOC

ICD.

Rationale: The LMOC generates and sends the WRS2TT to the DPAS for input to ground system reporting functions. As an example this can be used to generate maps of capture success rate vs position.

Mission: Landsat 8 and Landsat 9

LMOC-2455: The LMOC shall generate and display a graphical report of all scheduled collection activities occurring within a user-selectable time period.

Rationale: A graphical report enables a fast and intuitive check for certain activities or activity constraints, which are often related to positions within an orbit or an area such as the SAA.

Mission: Landsat 8 and Landsat 9

LMOC-2456: The LMOC shall provide users the ability to display scheduled collection activities in tabular formats.

Rationale: Due to the volume of individual scenes, these reports can get quite large.

Tabular formats like CSV or XML make it easier for staff to ingest the data into other tools for assessment, producing maps, matching to database records, etc.

Mission: Landsat 8 and Landsat 9

LMOC-5204: The LMOC shall provide users the ability to generate human readable reports on all mission planning products.

Rationale: A human readable format enables quality assurance, quality control, and troubleshooting.

Mission: Landsat 8 and Landsat 9

LMOC-2466: The LMOC shall provide mission planning products to the controlled repository.

Rationale: Needed for a controlled source where mission planning products are available and may be retrieved.

3.5.2 Collection Requests

LMOC-2469: The LMOC shall receive Special Collection Requests (SCR) from DPAS per the DPAS-LMOC ICD.

- 15 - LSDS-1739

Rationale: The LMOC planning & scheduling function receives special collection requests for imaging acquisitions other than LTAP Collection Requests (e.g. coastal scene requests, non-standing night scene requests, and ascending daylight scenes) from DPAS.

Mission: Landsat 8 and Landsat 9

LMOC-2468: The LMOC shall provide users the ability to generate collection requests, on demand, per the DPAS-LMOC ICD.

Rationale: Though not expected to be a nominal use case, this capability is needed to generate local, ad-hoc image data collections (e.g. nominal earth imagery in the absence of LTAP Collection Request input from DPAS, off-nadir imagery, night imaging, ascending daylight scenes, calibration intervals) used primarily for testing, pre-launch, and LEO operations when the DPAS-LMOC interface for collection requests and LTAP Collection Request transfer is either not used or not available.

Mission: Landsat 8 and Landsat 9

LMOC-35452: The LMOC shall be capable of scheduling selective scene collection and down-link for IC stations.

Rationale: Some IC stations do not request all scenes which could potentially be downlinked during a Landsat 8/9 overfly. Therefore, the LMOC needs to be able to specify which scene can be scheduled for real-time downlink and reported on a per-IC station basis. These scenes may not be a contiguous interval.

Mission: Landsat 8 and Landsat 9

LMOC-33874: The LMOC shall track and report images not specified by a collection request with unique identifier.

Rationale: In order to avoid data loss, the LMOC sometimes commands the spacecraft to continue recording when there is a short gap between intervals. DPAS would like to receive status of these images in the database as "flywheel" collects, as well as make them available to the science community. As such, the LMOC must create unique IDs and include them in the IDSR.

Mission: Landsat 8 and Landsat 9

LMOC-5246: The LMOC shall reference the WRS-2 coordinate system for all scene collection requests and reporting when the observatory is not flying in a WRS-2-compliant orbit.

Rationale: All calibration sites, field work, underflights, and other planning activities during Landsat 9 commissioning will reference the long-established WRS-2 grid. The LMOC needs to be capable of translating between WRS-2 grid references and the current projected observatory orbit.

Mission: Landsat 9

LMOC-2470: The LMOC shall process collection requests into the image collection schedule.

Rationale: The collection requests need to be scheduled for execution by the LMOC.

- 16 - LSDS-1739

LMOC-32446: The LMOC shall receive collection request modifications from DPAS per the DPAS-LMOC ICD.

Rationale: SCRs may need to be updated or canceled for any image acquisitions that fall outside of the planning period.

Mission: Landsat 8 and Landsat 9

LMOC-2472: The LMOC shall process collection requests that modify or cancel existing collection requests.

Rationale: Collection requests submitted to the LMOC may need to be changed or deleted.

Mission: Landsat 8 and Landsat 9

LMOC-5325: The LMOC shall include collection requests received at least 24 hours prior to observatory over-flight of the requested scene(s) for consideration within the image collection schedule during LEO and commissioning.

Rationale: LMOC will plan to acquire special requests and non-routine calibration activities within a reasonable time frame that don't violate constraints outside of emergency requests.

Mission: Landsat 9

LMOC-5137: The LMOC shall include collection requests received at least 72 hours prior to observatory over-flight of the requested scene(s) for consideration within the image collection schedule.

Rationale: LMOC will plan to acquire special requests and non-routine calibration activities within a reasonable time frame that don't violate constraints outside of emergency requests.

Mission: Landsat 8 and Landsat 9

LMOC-2471: The LMOC shall manage up to one year of active collection requests.

Rationale: Landsat data coverage is seasonal, so requests may span up to a year into the future. This requirement is intended to help scope the size of relevant data storage (table sizes, etc.)

Mission: Landsat 8 and Landsat 9

LMOC-2473: The LMOC shall maintain past collection requests in the system for DPAS-LMOC interface use for no less than 3 weeks.

Rationale: The DPAS-LMOC interface includes the ability to status past collection requests. Because of the large potential number of collection requests and to prevent this information from becoming an operational burden on the LMOC, the long term archival of collection request status information is allocated to the DPAS. This requirement represents the constraints on related LMOC information storage so that the system can be properly sized.

- 17 - LSDS-1739

LMOC-2475: The LMOC shall generate and maintain collection request receipt confirmation per the DPAS-LMOC ICD.

Rationale: When activities such as generating new stored command loads change the status of requests, that status change needs to be communicated to DPAS per the

DPAS-LMOC ICD.

Mission: Landsat 8 and Landsat 9

LMOC-2474: The LMOC shall provide collection request receipt confirmation to DPAS per the DPAS-LMOC ICD.

Rationale: The LMOC provides persistent collection request status to the DPAS for user confirmation (status may include Success or Failure) to indicate successful ingest of the file or failure that need further action such as resend of the file.

3.5.3 Image Data Collection Schedules

LMOC-3354: The LMOC shall receive the LTAP Collection Request from DPAS per the

DPAS-LMOC ICD.

Rationale: The DPAS sends the LTAP Collection Request to the LMOC for use in image collection planning activities.

Mission: Landsat 8 and Landsat 9

LMOC-3355: The LMOC shall verify the contents and format of the LTAP Collection Request per the DPAS-LMOC ICD.

Rationale: The LMOC needs to ensure the delivered content is valid prior to ingesting the data into the mission planning and scheduling function.

Mission: Landsat 8 and Landsat 9

LMOC-3356: The LMOC shall plan the acquisition of all scenes within the LTAP Collection Request and all collection requests that occur within the planning period.

Rationale: The LMOC will plan to acquire all land (Descending Daylight Land), collection requests (Ascending Daylight, Night, Ocean scenes, requested calibrations), and nominal calibration activities for each planning period. For reference, utilizing the DRC-16 analysis, the average number of imagery scenes per day over the 16 day cycle is 738. During constraint checking some scenes may be removed to accommodate higher priority observatory activities.

Mission: Landsat 8 and Landsat 9

LMOC-5115: The LMOC shall plan routine instrument calibrations within each planning period.

Rationale: The LMOC generates plans and schedules for nominal instrument calibrations internally; for calibrations managed by the Cal/Val Team and Mission operations management personnel, the collection request function is utilized.

- 18 - LSDS-1739

LMOC-3357: The LMOC shall provide the ability to ignore the LTAP Collection Request during image planning.

Rationale: The LMOC needs to allow the FOT to enable/disable the LTAP Collection Request within the planning function (i.e. use collection requests only) during L&EO, commissioning, and during anomalous conditions.

Mission: Landsat 8 and Landsat 9

LMOC-3358: The LMOC shall schedule all planned collection activities that do not violate constraints.

Rationale: The LMOC will only eliminate scenes or intervals that violate constraints.

Planned collection activities include LTAP Collection Request, collection requests (WRS-2 scene requests and calibration requests), and routine calibration activities.

Mission: Landsat 8 and Landsat 9

LMOC-3361: The LMOC shall provide a graphical display of activities, both scheduled and not scheduled, within the planning period.

Rationale: Provide a quick reference display for activities being performed, rejected or special events for projection onto a LMOC display.

Mission: Landsat 8 and Landsat 9

LMOC-3362: The LMOC shall generate the Image Data Status Report (IDSR) per the

DPAS-LMOC ICD.

Rationale: The IDSR contains the consolidated list of all scheduled scene UIDs, their collection request identifiers, interval UID, and related metadata (includes all LTAP Collection Request earth imaging scenes, scene collection requests, requested and routine calibrations, and any other imaging activities with concrete start/stop times and resources (ex. OLI-2 only, TIRS-2 only, OLI-2 + TIRS-2 for Landsat 9 or OLI only, TIRS only, OLI + TIRS for Landsat 8). In addition, it includes the status of the collection requests that are new or updated or cancelled within the past 24 hours. This information is needed to provide status of the requests to the user community.

Mission: Landsat 8 and Landsat 9

LMOC-3363: The LMOC shall generate a unique scene ID (scene UID) for each collection activity scheduled per the DPAS-LMOC ICD.

Rationale: These scene ID values apply to individual scenes within the LTAP Collection Request and collection requests, but also individual calibration activities (i.e. activities in the IDSR); these IDs will be used to associate records across the ground system, so they must be unique for the life of the mission.

Mission: Landsat 8 and Landsat 9

LMOC-3364: The LMOC shall provide users the ability to request and display any Image Data Status Report (IDSR).

Rationale: All schedules and reports should be viewable for reviews, comparisons, or analyses.

- 19 - LSDS-1739

LMOC-3366: The LMOC shall provide users the ability to generate a Image Data Status Report (IDSR) for a user-specified time interval of up to 16 days.

Rationale: Provide the capability to create IDSR for an entire WRS-2 16 day cycle.

Mission: Landsat 8 and Landsat 9

LMOC-3367: The LMOC shall provide Image Data Status Report (IDSR) to DPAS per the DPAS-LMOC ICD.

Rationale: The LMOC provides the IDSR to DPAS for image collection accounting and reporting. These metrics include the complete list of scenes which were scheduled to be collected and a distinct notification of failure to schedule scenes along with a reason / justification. In addition, it includes the status of the collection requests that are new or updated or cancelled within the past 24 hours. This information is needed to provide status of the requests to the user community.

Mission: Landsat 8 and Landsat 9

LMOC-3371: The LMOC shall generate the IC Scene Transmit Schedule per the DPAS-

LMOC ICD.

Rationale: The IC Scene Transmit Schedule (STS) identifies the planned acquisitions and downlinks of science data. The LMOC passes the IC Scene Transmit Schedule to the DPAS for distribution to the ICs.

Mission: Landsat 8 and Landsat 9

LMOC-3370: The LMOC shall provide the IC Scene Transmit Schedule to DPAS per the DPAS-LMOC ICD.

Rationale: The IC Scene Transmit Schedule (STS) identifies the planned acquisitions and downlinks of science data. The LMOC passes the station specific IC Scene Transmit Schedule to the DPAS for distribution to the ICs.

3.5.4 Interval Planning

LMOC-3374: The LMOC shall plan and schedule the observatory imaging intervals.

Rationale: LMOC to perform mission image collection activities by combining individual scene collections into continuous imaging intervals.

Mission: Landsat 8 and Landsat 9

LMOC-3376: The LMOC shall generate and assign a unique identifier for each imaging interval (interval UID) based on an identifier scheme defined in conjunction with the Government.

Rationale: Unique identifier used to track imaging intervals throughout the ground system; the interval UIDs are unique for the life of the mission.

Mission: Landsat 8 and Landsat 9

LMOC-3375: The LMOC shall map image data collection activities to image data collections requests, scene UIDs and interval UIDs.

- 20 - LSDS-1739

Rationale: This entire mapping will be resolved in the IDSR; the SIFMT will also reference relevant identifiers. This mapping includes all image acquisition activities (including LTAP Collection Request scenes, collection request activities, routine calibrations), regardless if an individual collection request identifier exists for the activity.

Mission: Landsat 8 and Landsat 9

LMOC-5121: The LMOC shall define and maintain direct mapping between interval UIDs and Root File Names generated for use on the spacecraft.

Rationale: This is key mission data management functionality; since root file names generated and uploaded to the spacecraft won't support mission-long uniqueness, the LMOC needs to maintain a tight coupling between interval UIDs and root file names; the SIFMT report will contain the interval UID field along with the root file name field in order to make this important relationship clear to the rest of the Ground System.

Mission: Landsat 9

LMOC-5250: The LMOC shall define and maintain direct mapping between interval UIDs and Root File IDs generated for use on the spacecraft.

Rationale: This is key mission data management functionality; since Root File IDs generated and uploaded to the spacecraft won't support mission-long uniqueness, the LMOC needs to maintain a tight coupling between interval UIDs and Root File IDs; the SIFMT report will contain the interval UID field along with the Root File ID field in order to make this important relationship clear to the rest of the Ground System.

Mission: Landsat 8

LMOC-3377: The LMOC shall generate and maintain the Scene to Interval File identifier Mapping Table (SIFMT) per the GNE-LMOC ICD.

Rationale: The LMOC needs to create the SIFMT to track each scene to the interval and file it is being captured within. This file is used as the basis for tracking image processing through the rest of the Ground System.

Mission: Landsat 8 and Landsat 9

LMOC-3378: The LMOC shall provide the SIFMT to the GNE per the GNE-LMOC ICD.

Rationale: The SIFMT is needed by the GNE for interval assembly. It matches downlinked data with the appropriate sensors and path/row combination. The LMOC passes the SIFMT to the GNE.

Mission: Landsat 8 and Landsat 9

LMOC-3379: The LMOC shall maintain the collection and downlink status of all scene UIDs and Interval UIDs.

Rationale: Need to track status of each scene planned, scheduled, executed, and downlinked.

Mission: Landsat 8 and Landsat 9

LMOC-3380: The LMOC shall predict instrument calibration opportunities for four weeks in the future.

- 21 - LSDS-1739

Rationale: This capability is needed to support sensor calibration plans for Lunar and Solar calibration events.

3.5.5 Constraint Checking

LMOC-5114: The LMOC shall apply solar angle constraints embedded in the LTAP Collection Request and collection requests per the DPAS-LMOC ICD.

Rationale: The DAM provides the solar angle at which WRS-2 scenes are collected;

the LMOC receives this information from DPAS and applies it as part of the schedule generation process. The generic LTAP Collection Request will have a solar angle constraint which applies to all scenes within the LTAP Collection Request; additional collection requests will be accompanied by a solar angle constraint which is specific to each request.

Mission: Landsat 8 and Landsat 9

LMOC-3398: The LMOC shall detect when the spacecraft star trackers are occulted by the Earth, Moon, or Sun over the duration of the attitude predict file.

Rationale: Report any interference events with the star tracker that may cause potential problems.

Mission: Landsat 8 and Landsat 9

LMOC-3393: The LMOC shall generate image data collection schedules based on configurable engineering constraints.

Rationale: Image collections need to be planned within configurable constraints like boresight to sun angles, duty-cycle of components.

Mission: Landsat 8 and Landsat 9

LMOC-3394: The LMOC shall provide users the ability to manage resource definitions.

Rationale: Resources are used to ensure that activities are not scheduled in conflict with the availability of resources.

Mission: Landsat 8 and Landsat 9

LMOC-3395: The LMOC shall provide users the ability to manage resource availability data.

Rationale: The capability to manage the information regarding the availability of each resource. The instruments (OLI-2 or TIRS-2) and individual Ground Stations, are examples of a resource.

Mission: Landsat 8 and Landsat 9

LMOC-3396: The LMOC shall provide users the ability to manage mission resource constraint data.

Rationale: Have the ability to add/update/modify various resource constraints in the system.

- 22 - LSDS-1739

LMOC-3397: The LMOC shall provide users the ability to modify resource constraint thresholds.

Rationale: In cases where a resource constraint is specified with maximum and/or minimum values, these values must be changeable using The LMOC software.

Mission: Landsat 8 and Landsat 9

LMOC-3390: The LMOC shall implement a user-configurable constraint against the maximum data volume allowed in observatory mass storage.

Rationale: Observatory mass storage volume constraints may vary depending on phase of mission and other operations-determined factors. The LMOC must always plan image acquisitions and housekeeping data storage within this constraint.

Mission: Landsat 8 and Landsat 9

LMOC-36990: The LMOC shall perform constraint checking on a command load planning period which overlaps a previous plan.

Rationale: Whenever building a load, the mission planning system shall be capable of recalling the previous plan in order to ensure constraints are applied correctly across the entire load, including the transition from one load to the next. The OPSCON is that there will be at least 24 hours of overlap between successful load builds.

Mission: Landsat 8 and Landsat 9

LMOC-5141: The LMOC shall restrict mission data flow to observatory mass storage as necessary to enforce the constraint against the maximum data volume.

Rationale: In order to avoid potential anomalies on-board the observatory, the LMOC must ensure that image acquisition schedules and housekeeping data transfers to observatory mass storage do not violate the constraint on observatory mass storage data volume.

Mission: Landsat 8 and Landsat 9

LMOC-22659: The LMOC shall apply individual WRS-2 scene priority values when it is necessary to reduce image collection volume due to constraints in accordance to LTAP-

9 (TBR).

Rationale: The DAM provides a priority value for each individual WRS-2 scene requested for acquisition; the LMOC receives this information from DPAS and applies it as part of the schedule generation process when absolutely necessary; this capability is generally only used during non-nominal operations to avoid violating observatory mass storage constraints. Note that priority values are individual to each scene and exist within both LTAP Collection Request and collection request inputs.

Mission: Landsat 8

LMOC-5194: The LMOC shall apply individual WRS-2 scene priority values when it is necessary to reduce image collection volume due to constraints in accordance to LTAP- 9.

Rationale: The DAM provides a priority value for each individual WRS-2 scene requested for acquisition; the LMOC receives this information from DPAS and applies it as part of the schedule generation process when absolutely necessary; this capability is

- 23 - LSDS-1739

generally only used during non-nominal…