Attachment S CONOPS 410 XO CONOPS 0004 V1.00.pdf

Effective Date: July 20, 2022 410-XO-CONOPS-0004 Expiration Date: Five years from last signature Version 1.0 Responsible Organization: GeoXO Program / Code 410 ii Check the GeoXO Portal at https://goesportal.ndc.nasa.gov to verify correct version prior to use.

GeoXO Program Concept of Operations (CONOPS)

Submitted by

Electronically approved by:

07/05/2022

Alexander Krimchansky GeoXO Program Systems Engineer

Concurred by

Electronically approved by C Wheeler for:

Date

07/15/2022

Candace Carlisle GeoXO Flight Project Manager

Electronically approved by E Corderman for:

07/07/2022

Steven Grippando GEO Ground Segment Project Manager

Approved by

Electronically approved by:

07/20/2022

Pamela C. Sullivan GeoXO System Program Director iii

GeoXO Program

Concept of Operations (CONOPS) Document Change Record

VERSION CCR # DATE PAGES /SECTION

AFFECTED DESCRIPTION

1.0 X00095 07/20/2022 All Baseline

iv

TABLE OF CONTENTS

INTRODUCTION

1.1 GOALS AND OBJECTIVES

1.2 MISSION OVERVIEW

1.3 ORGANIZATIONAL RESPONSIBILITIES

1.4 DOCUMENT SCOPE

REFERENCE DOCUMENTS

GEOXO ADVANCES NOAA’S GEO OBSERVATIONS

GEOXO SYSTEM AND INTERFACE DESCRIPTION

4.1 GEOXO SYSTEM

4.1.1 GeoXO Interfaces

4.1.2 GeoXO Space Segment

4.1.2.1 GeoXO Spacecraft

4.1.2.2 GeoXO Instruments

4.1.2.3 Data Collection System Payload

4.1.2.4 Launch Vehicle (LV)

4.1.3 Ground Segment

4.1.3.1 Mission Management

4.1.3.2 Product Generation (PG)

4.1.3.3 Data Delivery To NCCF

4.1.3.4 Ground Facilities

4.1.4 Data Distribution

4.1.4.1 GeoXO High Rate Data

4.1.4.2 GeoXO Medium / Low Rate Data Services

4.1.4.3 OSPO Data Collection System Data Distribution

GEOXO SYSTEM OPERATIONS

5.1 OPERATIONAL PHILOSOPHY

5.2 OPTIMIZATION AND AUTOMATION

5.3 AVAILABILITY AND TRANSITION FROM THE GOES-R SERIES

5.3.1 Transition Timeline

5.4 OPERATIONAL VALIDATION

5.4.1 Mission Operations Support Team

5.4.2 Ground Functional Validation for L1b implementation

5.4.3 Program Science

5.5 PHASES AND MODES OF OPERATION

5.5.1 Phases

5.5.1.1 Pre-Launch

5.5.1.2 Launch and Orbit Raising

5.5.1.3 Post-Launch Test

5.5.1.4 Operational

5.5.1.5 Deactivation

5.5.2 Satellite Modes

5.5.2.1 Pre-Operational

Responsible Organization: GeoXO Program / Code 410 v Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

5.5.2.2 On-Orbit Storage

5.5.2.3 Normal Mission Operations

5.5.2.4 Degraded Capability

5.5.2.5 Post-Mission Operation

5.6 ORBIT DETERMINATION AND CONTROL

5.7 FREQUENCY UTILIZATION

5.8 DATA DISTRIBUTION VIA NCCF

5.9 MISSION OPERATIONS

5.9.1 Commanding

5.9.2 Telemetry Monitoring and Trending

5.9.3 Routine Operations

5.9.4 Housekeeping Operations

5.9.5 Special Operations

5.9.6 Anomaly Operations

5.9.6.1 Instrument Anomalies

5.9.6.2 Satellite Anomalies

5.9.6.3 Ground Anomalies

5.9.7 Station Relocation

5.9.8 Storage Mode Activation/Reactivation

5.9.9 Eclipse

5.9.10 Flight Software

5.9.11 End-of-Life Decommissioning

5.10 INSTRUMENT OPERATIONS

5.11 SCHEDULING / MISSION PLANNING

5.12 INSTRUMENT TASKING

5.13 FLIGHT/GROUND INTEGRATED TEST PROGRAM

5.13.1 Mission Operations End-To-End Tests

5.13.2 Data Operations Exercises

5.13.3 Special Integrated Tests

5.13.4 Radio Frequency Compatibility (RF Compat)

5.14 CALIBRATION AND VALIDATION

5.14.1 Pre-Launch

5.14.2 Post-Launch Test Calibration

5.14.3 Routine Operations Calibration

5.15 IMAGE NAVIGATION AND REGISTRATION

5.16 ALGORITHM DEVELOPMENT PROCESS

5.17 CONTINGENCY OPERATIONS

5.18 7-DAY AUTONOMY

5.19 CONTINUITY OF OPERATIONS

5.20 GROUND SYSTEM SUSTAINMENT

5.21 CONFIGURATION MANAGEMENT

5.22 OPERATIONS TRAINING

5.23 SECURITY

APPENDIX

6.1 DATA STORAGE AND ARCHIVE SUMMARY

6.2 SYSTEM LEVEL DESCRIPTIONS

GLOSSARY

Responsible Organization: GeoXO Program / Code 410 vi Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

ACRONYM LIST

LIST OF FIGURES

Figure 1. GeoXO Operational View Figure 2. GEO Ground Segment Facilities Location Figure 3. Continuity of NOAA’s Geostationary Satellites Figure 4. GeoXO System Context Figure 5. GeoXO System Interfaces Figure 6. GeoXO Space Segment Interfaces Figure 7. Ground Segment Functions and External Interfaces Figure 8. Notional Data Distribution Concept Figure 9. GOES-R Series to GeoXO Constellation Transition Timeline Figure 10. GeoXO Mission Operations Phases Figure 11. Space - Ground Communications

LIST OF TABLES

Table 1: GeoXO Functions Table 2. Requirements Levels Table 3. Archive Summary Table 4. GeoXO Levels of Assembly

Check the GeoXO Portal at https://goesportal ndc nasa.gov to verify correct version prior to use.

Introduction The National Oceanic and Atmospheric Administration (NOAA) operates a system of Geostationary Operational Environmental Satellites (GOES) to provide continuous weather imagery and monitoring of meteorological and space environment data to protect life and property across the United States. Currently, two NOAA Geostationary Earth Orbit (GEO) satellites will remain operational at all times providing coverage for the eastern United States and most of the Atlantic Ocean and the western United States and Pacific Ocean basin. The Geostationary Extended Observations (GeoXO) Program is the follow-on to the GOES-R series.

The GeoXO launch capability is planned for 2032. GeoXO is a collaborative development and acquisition effort between NOAA and the National Aeronautics and Space Administration (NASA). The acquisition of the end-to-end GeoXO system includes spacecraft, instruments, launch services, and all associated ground system elements. The new NOAA GeoXO satellites will provide critical environmental observations for products supporting weather forecasting and warnings, climatologic analysis and prediction, ocean biochemistry, ecosystems management, and safe and efficient commercial and private air and marine transportation. The GeoXO satellites also provide a platform for data collection platform relay.

Program oversight activities occur at National Environmental Satellite, Data, and Information Service (NESDIS) Headquarters and the NASA Goddard Space Flight Center (GSFC). The GeoXO Program will consist of two projects. The projects are co-located at NASA GSFC. The Flight Project will manage the Space Segment, which consists of the spacecraft, instruments, and interface to launch vehicles. The GEO Ground Project will manage the GeoXO command and control system development, including uplink/downlink RF antennas, plus the implementation of Level 0 (L0) and Level 1b (L1b) science data processing, along with distribution of the L0 and L1b science data to NESDIS Common Cloud Framework (NCCF). Office of Satellite Ground Services (OSGS) manages NCCF. NCCF will provide Level 2+ (L2+) products generation and distribution, and access services, including access to archive.

1.1 GOALS AND OBJECTIVES

The purpose of the Concept of Operations (CONOPS) document is to communicate how the GeoXO system will operate, with special consideration given to user functionality and the external interfaces into which the GeoXO system must be integrated. The current version of the CONOPS is developed during Formulation phase (pre-Mission System Requirements Review (SRR)) and will evolve as the requirements and architecture change. Hence this “to be” CONOPS document (as opposed to “as is”) is intended as a kernel from which the future Ground Segment and Flight Segment Operations Concepts (OPSCONs) may be derived. This document will be updated to reflect current plans after the Flight and Ground Preliminary Design Reviews (PDRs).

This CONOPS is a key architectural document describing the concept of operations from the perspectives of stakeholders such as owners, subject matter experts (SMEs), enterprise architects, system architects, business users, system engineering staff, and others in the program. This CONOPS is not a requirements document, but it provides operational context to the Level 2 requirements defined in the Mission Requirements Document (MRD), and to the Level 3 requirements in the Flight and Ground Segment Functional and Performance Specifications (F&PSs) and Interface Requirements Documents (IRDs). The CONOPS may be modified as a result of analyses and changes occurring throughout the Formulation phase of the GeoXO

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

program.

The GeoXO mission requires the capability to acquire, process, and disseminate environmental data on an extensive spatial range (regional, and local) on a variety of time scales. These data include but are not limited to imagery; cloud and precipitation parameters; atmospheric profiles of temperature, moisture, winds, aerosols, and ozone; surface conditions concerning ice, snow and vegetation; ocean parameters and sea-surface temperature.

The Government is procuring the GeoXO satellites and instruments to continue its mission through new requirements specified in the NESDIS’s GeoXO Program Level Requirements (PLR) and MRD. The NESDIS strategic objectives (as prefaced from the PLR) are to:

• Advance US Earth observational leadership in the geostationary and extended orbits.

• Evolve the US low Earth orbit (LEO) architecture to an enterprise system of systems that exploits and deploys new observational capabilities.

• Advance observational leadership in space weather in LEO, geostationary Earth orbit

(GEO), and extended orbits.

• Develop an agile, scalable ground capability to improve efficiency of service deliverables and to support data from all sources.

• Provide consistent ongoing enterprise-wide user engagement to ensure timely response to user needs.

• Deliver an integrated program development to provide a suite of products and services.

The GeoXO PLR provides the requirements to meet the first strategic objective and provides for accommodation to meet portions of the third strategic objective. The GeoXO MRD, the companion to this document, is derived from the PLR.

GeoXO will improve upon the imagery provided by the GOES-R series and introduce new technologies including hyperspectral sounding, ocean color, and atmospheric composition instruments. These advances will improve the Nation’s ability to monitor and forecast weather and environmental phenomena through 2050.

1.2 MISSION OVERVIEW

The GeoXO mission is the follow-on to the GOES-R series geosynchronous satellites. When operational, GeoXO will consist of three satellites operating in geostationary orbit. The nominal locations are near 75 degrees West, 137 degrees West and 105 degrees West longitude; however, the exact locations are dependent on NOAA user needs, GeoXO satellite radio frequency assignments, and orbital conjunction assessment and risk analysis. Satellite locations may be as far east as 65 degrees West or as far west as 147 degrees West longitude. A general overview of the GeoXO system is given in Figure 1.

The GeoXO Space Segment consists of the spacecraft, instruments, and auxiliary communications payloads (on East and West orbital locations only). The GeoXO baseline includes the following five Earth-pointed instruments that are detailed in Section 3:

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

• Imager – The GeoXO Imager (GXI) will provide hemispheric, synoptic, and mesoscale environmental data and imagery for weather and hazard forecasting, including severe weather warning, and providing continuity for GEO imagery data and products.

• Infrared (IR) Hyperspectral Sounder – The GeoXO Sounder (GXS) will provide radiance data as input to Numerical Weather Prediction (NWP) and as input to retrievals of vertical and horizontal temperature and moisture information that will be used to produce routine meteorological analyses and forecasts of temperature, moisture, and winds for severe weather events. Radiance data will also be made available for monitoring longer-term climate change.

• Ocean Color Instrument – The GeoXO Ocean Color Instrument (OCX) is a hyperspectral imaging spectrometer spanning the ultraviolet (UV) through near IR spectrum that will provide new daytime coverage of U.S. Exclusive Economic Zone (EEZ East) plus Great Lakes and EEZ West plus southern Alaska, with commandability to Ocean Color Regions of Interest outside of the primary regions. The OCX remotely collects imagery of the Earth’s coastal waters for harmful algal blooms, water turbidity, and general water quality, fisheries management, habitat quality/assessment/mapping, pollution tracking, biogeochemical processing in coastal regions, warnings, and predictions. OCX will expand knowledge of coastal waters and ocean processes in these regions.

• Lightning Mapper– The GeoXO Lightning Mapper (LMX) is a single-channel, near-IR optical detector, used to provide continuous full-disk detection, location and measurement of the optical pulses associated with lightning to allow tracking of each lightning flash within a specific storm cell and calculation of its optical center over time to improve lightning hazards information, storm warning and nowcasting. Data from LMX will also be made available for long-term tracking of decadal changes in lightning activity.

• Atmospheric Composition Instrument – The GeoXO Atmospheric Composition (ACX) Instrument is a UV-visible spectrometer that will collect measurements of ozone, nitrogen dioxide, and other pollutants used to determine and product forecasts and warnings of national air quality, hazard, and fire smoke.

• Partner Payload – The GeoS satellite has space to accommodate a potential Partner payload, should it be provided.

No space weather instruments will be accommodated on the GeoXO mission.

Each GeoXO satellite can accommodate up to 3 instruments on the Earth pointing platform. The GeoXO pre-baseline includes the GXI, LMX, and OCX instruments on the GeoXO East and West satellites. The GeoXO Central satellite includes the GXS and ACX instruments as well as a potential partner payload (TBD).

The naming convention for the East/West versus Central satellites is:

• East/West satellites: GeoXO-Imager/LM/OC, or GeoI.

o Pre-launch these will be GeoI-1, 2, 3, and 4.

o On-orbit these will be re-named GOES-20, 21, 22, and 23.

• Central satellites: GeoXO-Sounder/AC, or GeoS.

o Pre-launch: GeoS-1, 2.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

o On-orbit these central satellite names will not change.

The GeoXO satellites will also provide a communication relay service in support of the Data Collection System (DCS) on East and West satellites. In GeoXO documentation, the DCS service is part of the User Facing Communication (UFC) service.

Figure 1. GeoXO Operational View.

The GeoXO system will also interface with the launch segment, which will provide launch services. The NASA Kennedy Space Center (KSC) Launch Services Program (LSP) will procure the launch vehicle (LV) and manage the launch contract for the GeoXO satellites. Pre-launch and launch operations will be conducted by the spacecraft contractor, KSC LSP and LV contractor (LVC). The spacecraft contractor will perform satellite pre-launch checkout with the assistance of each of the instrument contractors at the payload processing facility (PPF) and the LV integration facility. The LVC will perform satellite encapsulation into the payload fairing (PLF) and integration onto the LV. Final pre-launch checkout will be a joint effort by the LVC, the spacecraft and instrument contractors, and the Ground Segment contractor to ensure that all systems are fully functional end-to-end. The LV will place the GeoXO satellites into a predetermined geosynchronous transfer orbit (GTO) or potentially a direct injection orbit. Upon satellite separation from the LV, the satellite will perform a series of propulsion maneuvers intended to place the satellite in a geostationary checkout orbit for post-launch testing (PLT).

When satellite PLT is completed, the satellite will be relocated into a final geostationary orbit, either operational or storage.

The Ground Segment of GeoXO, part of the GEO Ground Segment, will be implemented as an evolution of the GOES-R Ground Segment (GS) that will also include heritage GEO Ground Segment capabilities of providing L0 data from CCOR to SWPC for the L1 SWFO Program. It is envisioned that GEO Ground Segment will reuse portions of the GOES-R GS and evolve to include cloud data processing, for improved efficiencies over the lifecycle. Unlike GOES-R, the Level 2+ processing will be disaggregated from the L0 and L1b processing, where L0/L1b processing will remain the responsibility of the GEO Ground. This products disaggregation

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

approach will keep L0/L1b product generation and distribution tightly coupled with Flight elements which will minimize the number of interfaces with external entities. On the other hand, the L2+ product generation and distribution will be migrated to NCCF to be developed and managed by NESDIS’s Office of Satellite Ground Services (OSGS). Furthermore, the GS project will apply lessons learned from GOES-R Series operations including outsourcing auxiliary communication services ad incorporating GeoXO functionality into existing GOES-R Series IT security boundaries. The L2+ product generation and distribution will be migrated to NCCF to be developed and managed by OSGS. As depicted in Figure 2, it is also envisioned that GeoXO system operations will be performed from three facilities: NOAA Satellite Operations Facility (NSOF) in Suitland, MD; the Wallops Command and Data Acquisition station (WCDAS) in Wallops Island, VA; and at Consolidated BackUp site (CBU) in Fairmont, WV. Together, the NSOF and WCDAS comprise the “primary” sites for GeoXO operations and may be considered in certain respects as a single system, with WCDAS providing the Earth-Space communications functions and most high-level functions provided by NSOF. The CBU consolidates the functionality of the NSOF and WCDAS into a single “backup” site that can operate completely independently. The antenna suite at WCDAS and CBU will be operated independent of each facility, and their antennas.

Figure 2. GEO Ground Segment Facilities Location

1.3 ORGANIZATIONAL RESPONSIBILITIES

The GeoXO Program is responsible to meet the requirements defined in GeoXO PLR document and to secure funding to accomplish those requirements. In addition, the GeoXO Program budget covers the following functions in Table 1 to ensure that the end-to-end mission need is met, though these items are not included in the GeoXO program technical scope (as discussed below in section 1.4), where the following acronyms are used: Office of Satellite Ground

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

Services (OSGS), Office of Satellite and Product Operations (OSPO), National Centers for Environmental Information (NCEI).

Table 1: GeoXO Functions

The GeoXO Program will work with the Responsible Organizations to provide necessary funding for these functions within the Program budget plan. The Responsible Organization will receive appropriate funding and technical support from the GeoXO Program and will be fully responsible for meeting those functional requirements.

1.4 DOCUMENT SCOPE

This CONOPS document is intended as a kernel from which the spacecraft or ground systems contractor may derive their respective Operations Concepts (OPSCONs). The Flight and Ground OPSCONs will be utilized by the GeoXO Program Office to evolve the CONOPS into a comprehensive end-to-end system operational concept.

To reiterate, this CONOPS is not a requirements document, but it provides operational context to the Level 2 requirements defined in the MRD, and to the Level 3 requirements in the Flight and Ground (F&PSs and IRDs. Table 2 provides context. Detailed operations plans and procedures, operations handbooks, staffing plans, and maintenance plans and procedures will be developed based on the detailed system designs of each of the segments.

The CONOPS and OPSCONs may be modified as a result of analyses and changes occurring throughout the Formulation and Implementation phases of the GeoXO program. Concepts may be added or modified as functional and performance parameters of these components mature.

During Formulation phase, the government will maintain the CONOPS while the Spacecraft and Instrument development contractors will maintain the respective OPSCONs.

Section 2 of the CONOPS lists reference documents. Section 3 provides background of the legacy GOES systems. Section 4 describes the GeoXO Space and Ground Segments. Section 5 gives an overview of GeoXO operations. An Appendix contains a summary of the various data archives in the system.

REFERENCE DOCUMENTS

• Geostationary Extended Observation (GeoXO) Program Level Requirements (PLR)

Document, NESDIS-REQ-4300.1

• Geostationary Extended Observations (GeoXO) Mission Requirements Document, 410-XO-

MRD-0008

• GeoXO Program Verification and Validation Plan, 410-XO-PLN-0014

• GeoXO Calibration/Validation Plan: Level 1b Data, 410-XO-PLN-0105

• GeoXO Algorithm Development Management Plan for Ground Segment Product Generation, 418-X-PLN-0285

• NASA Procedural Requirements (NPR) for Limiting Orbital Debris and Evaluating the Meteoroid and Orbital Debris Environments, NPR-8715.6

• NOAA IT Security Handbook

• GeoXO Data Book

Check the GeoXO Portal at https://goesportal ndc nasa.gov to verify correct version prior to use.

GEOXO ADVANCES NOAA’S GEO OBSERVATIONS

The legacy GOES-R series provided geostationary meteorological observation to meet forecasting and environmental monitoring over the 2016-2038 timeframe. As depicted in Figure 3 below, GeoXO will provide continuity of meteorological observations in the 20323-2050 timeframe while extending observations via improvements in spatial and spectral resolution over the GOES-R series. Additional observation capability will be provided through the Infrared (IR) Hyperspectral Sounder, Ocean Color (OC), and Atmospheric Composition (AC) Instruments.

Figure 3. Continuity of NOAA’s Geostationary Satellites.

Space Segment The key improvements realized by GeoXO are related to the instrument payloads. The advanced instruments drive improvements in the overall system, such as the processing, generation, and distribution of data products. The advances in the instruments provide improved spatial and spectral resolution and allow for additional observational data, including Atmospheric Composition and Ocean Color measurements.

The GeoXO Imager (GXI) is a multi-channel, visible through infrared, passive imaging radiometer used to measure environmental data. The GXI baseline includes 18 spectral channels. The GXI baseline improves upon the GOES-R Series Advanced Baseline Imager (ABI) capabilities with the addition of a 0.91 μm “Low level water (Total Precipitable Water)” near-IR channel at 1 km, a 5.15 μm band “Low level water for turbulence” MWIR channel at 1 km, and improving the resolution of a number of bands: 0.47 um band to 0.5 km, 0.64 um band to 0.25 km, 0.865 um band to 0.5 km, 2.25 um band to 1.0 km, 3.9 um band to 1 km, 6.95 um band to 1 km, and 10.35 um to 1 km. The higher spatial resolution is intended to improve the daytime land/cloud imaging.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

The GXI will have a flexible imaging pattern that can be programmed on orbit for needed observations.

Although additional scan modes may be defined, GXI can concurrently image in Mode A for a 10-minute Full Disk, a 5-minute Super-Regional and a 30-second Mesoscale, along with any images that may be needed to meet radiometric and INR requirements. GXI can also image in Mode B for a 5-minute Full Disk, along with any images that may be needed to meet radiometric and INR requirements, with 5-minute Super-Regional images pulled out of the Full Disk by ground processing. User-defined intervals and user-defined image regions for additional efficient modes would employ ground modifiable parameters, activate with single command, and be consistent with observing rates used in predefined imaging modes.

The GeoXO Sounder (GXS) is a hyperspectral infrared passive radiometric sounder used to collect radiance observations of the Earth’s atmosphere with both vertical and horizontal resolution. The GXS data will be used to retrieve vertical and horizontal temperature and moisture information and will provide improved spectral, spatial, and temporal operational sounding data of the western hemisphere.

GXS data will enhance nowcasting as well as improve numerical weather production (NWP) in short range weather forecasting and longer-range weather prediction. Like GXI, GXS will also have a flexible observing pattern that can be programmed on orbit for needed observations. The GXS will acquire data at the coverage rate of at least a 62-degree Local Zenith Angle (LZA) sounding disk (SD) in 60 minutes, including performing all necessary housekeeping and calibration functions. The GXS will be commandable into custom tasks at the same rate with various regions interspersed in any order, including needed other acquisitions (as summarized in the MRD.)

The GeoXO Lightning Mapper (LMX) is a single-channel, near-IR optical detector, used to detect, locate and measure the optical pulses associated with lightning over the full-disk to allow tracking of each lightning flash within a specific storm cell and calculation of its optical center over time. The LMX instrument will not directly produce images, but will provide event data to the ground system, which will use spacecraft telemetry, orbit and attitude information and other data to generate calibrated and navigated products mapping optical transients produced by lightning over the full disk. As LMX observes the full disk at all times, the LMX does not need to have multiple observational modes or tasks.

The GeoXO Ocean Color Instrument (OCX) is a hyperspectral imaging radiometer spectrometer that will provide daytime coverage of the U.S. Exclusive Economic Zone (EEZ) and Great Lakes in the ultraviolet (UV) through near infrared spectrum, with commandable coverage for regions of interest within the Western Hemisphere. The OCX will be commanded to provide a minimum daylight temporal coverage refresh of 3.5 hours for the entire coverage area, with a faster refresh rate being studied.

Commanded areas of 800 km x 400 km within the sufficiently-daylit Western Hemisphere will be observed instead of the primary regions, at the same instrument coverage rate. Any user-defined intervals and user-defined image regions for additional efficient modes would employ ground modifiable parameters, activate by a single command, and be consistent with observing rates used in predefined observing modes.

The GeoXO Atmospheric Composition Instrument (ACX) is a hyperspectral, UV through visible imaging spectrometer that will collect daytime measurements of ozone, nitrogen dioxide, and other pollutants used to determine national air quality, hazard, and fire smoke forecasts and warnings. The ACX instrument will provide hourly coverage of a Super-Regional (baseline) with a performance goal of commandable smaller regions. ACX will provide (5 km)2 equivalent spatial resolution at nadir. The ACX instrument will be accommodated on the GeoXO Central satellite near 105W longitude. Any user-

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

defined intervals and user-defined observing regions within Super-Regional for additional efficient observations would employ ground modifiable parameters, activate by a single command, and be consistent with observing rates for Super-Regional coverage and all needed observations within an hour.

Note that all the GXI, GXS, OCX and ACX coverage requirements define a capability and not a definitive operational scenario. NOAA anticipates operating these instruments in an asynchronous manner that uses information from other on-orbit assets and models to identify potential regions for scanning or stepping GXI, GXS, OCX or ACX. To perform their tasks, commanding of these instruments for targeted observations will be based on priorities and availability.

The GeoXO communication system will utilize the X-band communication link to support the higher volume of observation data. Auxiliary communication services on GeoXO will be reduced to minimize satellite development, launch, and operations costs. To address legacy users’ requirements, the notional architecture is envisioned with a GeoXO High Rate data (see Figure 4) that is a legacy subset of data corresponding to GOES-R ABI data. The GeoXO High Rate data subset of GeoXO Mission Data (GMD) will be selected by the GeoXO program and implemented by OSPO via the Configurable User Facing Communication (UFC) Services). Both the GeoXO High Rate data and the GeoXO Medium / Low Rate data, which carries the High Rate Information Transmission (HRIT) and Emergency Managers Weather Information Network (EMWIN) functionalities, will be via NCCF (primary path being explored now) and also via commercial communication providers (secondary path) for users who need an operational RF link. The DCS service will be retained and will be accommodated on GeoXO East and West satellites.

GeoXO Spacecraft The GeoXO spacecraft will provide the same level of precision pointing and “operate-through” performance for routine housekeeping and station-keeping activities as the GOES-R series. This level of performance may necessitate on-board orbit determination (OD) utilizing data from GPS constellation as currently implemented on GOES-R series. However, improvements to on-board navigation and housekeeping planning will allow for automated maneuver planning and execution and minimize ground-based mission planning and scheduling requirements. The GeoXO spacecraft will provide for a minimum 15-year mission life.

Ground Segment The Ground Segment for GeoXO will be implemented as an evolution of the GOES-R Ground Segment (GS) that may also include heritage ground segment elements. It is envisioned that the Ground segment for GeoXO will maximize the reuse of GOES-R GS including on premise satellite command and control (C2), L0 and L1b product generation and distribution. Unlike GOES-R, the Level 2+ processing will be disaggregated from the L0 and L1b processing, where L0/L1b processing will remain the responsibility of the GEO Ground. This products disaggregation approach keeps L0/L1b product generation and distribution tightly coupled with Flight elements which will minimize the number of interfaces with external entities. Furthermore, the GS project will apply lessons learned from GOES-R operations including outsourcing auxiliary communication services ad incorporating GeoXO functionality into existing GOES-R IT security boundaries. On the other hand, the L2+ product generation and distribution will be migrated to NCCF to be developed and managed by OSGS.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

Operational Roles NESDIS operational organizations will retain their legacy operational roles for the GeoXO Program.

The Office of Satellite and Product Operations (OSPO) will provide mission and product operations.

OSGS will develop systems to process L2+ data and will distribute Level 1b and higher products.

National Centers for Environmental Information (NCEI) will archive and provide stewardship for the GeoXO data. L0 and L1b algorithm development and maintenance and instrument calibration will be supported by the Center for Satellite Applications and Research (STAR) with oversight by the GeoXO Program Office, while L2+ algorithm development will be supported by STAR with oversight by OSGS. Organizational roles and responsibilities are further defined in the GeoXO Program Management Plan.

GeoXO Interdependencies and Synergies:

The earth-pointing instruments will also be used more synergistically to optimize observations for the user community. Specifically, the GXI data generates a clear sky mask that can be used in tasking other instruments like GXS and OCX to regions of clear air for improved L1b data. GXI data will provide finer spatial resolution data to improve navigation for ACX L1b data. GXI will also provide additional SWIR band coverage to help ACX. A Night Band (NB) capability will add to the spectral coverage of GXS or OCX for detecting low cloud and storms at night.

L2+ products will also benefit from L1b inputs from multiple instruments, when used synergistically, as planned for GeoXO. For example, improvements in cloud top height, winds, land surface temperature, sea surface temperature, tropical cyclone characteristics, and atmospheric temperature and water vapor are expected with synergies from the L1 radiances produced by ABI and GXS. Improved storm damage and flood assessment are expected from use of GXI, OCX, and NB. Improved trace gases, aerosols and dust detection, and volcanic eruption information for atmospheric composition and air quality are expected from using ACX, GXS, and GXI L1b radiances synergistically for higher level product algorithms. Improved fire hazard and fire weather products are expected from using GXI, NB, LMX, and ACX L1b radiances synergistically. Improved cloud and fog cover at night will result from GXI and NB. Improved severe storm forecasting will result from GXI and LMX. Improved sea ice detection will be afforded from GXI and OCX inputs. Using ACX and GXI L1b outputs to OCX L1b outputs will result in improved ocean biochemistry. Other product improvements are anticipated from future synergistic combinations.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

GEOXO System and Interface Description

4.1 GEOXO SYSTEM

To provide a better understanding of how the GeoXO mission will be operated, it is important to define the GeoXO System in a way that clearly defines what is in and what is out of GeoXO development scope. Thus, it provides a focus on what “system” is to be built and operated. The diagram of notional GeoXO system is presented in Figure 4 below. The space segment and ground segment functions listed within the GeoXO System diagram is within the technical scope of GeoXO system development. All other boxes shown outside of the System are considered to be an external to GeoXO system. The boxes connected with dashed lines are not directly interfaced with the GeoXO system but illustrated here only for context and to show a notional data distribution (subject to change) to the GeoXO user community (also described in Section 4.1.3.4). Note that the partner payload data processing is only shown notionally below.

Figure 4. GeoXO System Context

This System context diagram was derived from the GeoXO PLR and GeoXO MRD, the results of architectural trades, and GeoXO programmatic decisions and may evolve as the program matures. The details of elements constituting the GeoXO system, external entities and interactions are described in Section 4 of this document.

It must be noted that GeoXO program has responsibility to fund not only the GeoXO technical scope of work (described above), but also for the development of new and existing capabilities (as described in Section 1.3) that are considered out of GeoXO technical scope.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

4.1.1 GeoXO Interfaces

GeoXO Mission notional interfaces are as shown in Figure 5. The diagram captures major interfaces, which are both internal and external to the system. Brief descriptions of each interface are provided here, with more detailed interface functions provided in the appropriate IRDs.

Figure 5. GeoXO System Interfaces

The GeoXO Mission Data Interfaces are for:

1. General Interface between spacecraft and Instruments – covered in the General Interface Requirements Document (GIRD). There is a physical interface (mechanical and electrical) as well as a data and commanding interface for the instruments.

2. Commands (Cmds), Telemetry (TLM), and Science Data (SD) – received from the GeoXO series satellites and instruments during nominal operations via direct RF communications from antennas at the WCDAS or the CBU. Commands and telemetry are also sent to the GeoXO spacecraft and instruments at the factories via ground network during integration and testing.

During launch and orbit raising (LOR), telemetry from the GeoXO satellites is received primarily through the Launch Segment network. SD is received via RF link (X-band) from satellite to ground segment to be converted to Intermediate Frequency (IF) by Antenna element and routed to Mission Management element (MM) for processing and distribution. The SD includes raw data from all instruments accommodated on GeoI or GeoS satellite.

3. Data Collection Platform (DCP) – autonomous data collection platforms (DCS users’ equipment) for monitoring of weather data. This data from the DCS platforms is uplinked to the GeoXO East and West satellites (UHF band), transmitted to the ground segment (L-band) and sent to the OSPO’s DCS ingest system located at WCDAS, NSOF and CBU. It is envisioned that most DCS users will receive DCS data via terrestrial lines and/or via other legacy services (ex. HRIT).

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

The GeoXO series does not support the DCS command and interrogate function.

4. Near Earth Network (NEN) - During GeoXO LOR, commands are routed through the NASA

Launch Services, Direct To Earth (DTE), and Deep Space Network (DSN).

5. Launch Segment and Launch Vehicle – Provides pre-launch processing and communication to the GeoXO satellites during LOR raising before the satellites have reached an orbital position where the Geo Ground System can communicate with them continuously. This interface also provides the data interface during pre-launch mission operations testing when command and telemetry data is terrestrially routed to/from the Satellite Operations Control Center (SOCC) and spacecraft factory. Provides hard line communication interface between GeoXO satellite and launch vehicle starting from a launch vehicle integration (at LV integration facility) and until GeoXO satellite separation leading to transfer orbit insertion.

6. GXI – the unique instrument interface between spacecraft and GXI is covered in the Unique Instrument Interface Document (UIID). This includes the instrument specific physical interface (mechanical and electrical) as well as a data and commanding interface for the instrument.

7. LMX - the unique instrument interface between spacecraft and LMX is covered in the Unique Instrument Interface Document (UIID). This includes the instrument specific physical interface (mechanical and electrical) as well as a data and commanding interface for the instrument.

8. OCX - the unique instrument interface between spacecraft and OCX is covered in the Unique Instrument Interface Document (UIID). This includes the instrument specific physical interface (mechanical and electrical) as well as a data and commanding interface for the instrument.

9. GXS - the unique instrument interface between spacecraft and GXS is covered in the Unique Instrument Interface Document (UIID). This includes the instrument specific physical interface (mechanical and electrical) as well as a data and commanding interface for the instrument.

10. ACX - the unique instrument interface between spacecraft and ACX is covered in the Unique Instrument Interface Document (UIID). This includes the instrument specific physical interface (mechanical and electrical) as well as a data and commanding interface for the instrument.

11. NCCF – L0 and L1b GeoXO Mission Data as well as L0 Space Weather Program Office (SWO) data will be made available from GEO Ground segment to NCCF. NCCF will be responsible for GeoXO L2+ product generation. NCCF will perform product distribution to GeoXO users.

12. OSPO’s DCS Ingest System - the GEO Ground segment antenna system will receive DCS data from the GeoXO satellite (GeoI-West or East only) and down convert from L-band to an IF. The DCS IF signal will be sent to the OSPO DCS ingest system located at WCDAS, NSOF and CBU. It is envisioned that most DCS users will receive DCS data via medium/low rate commercial services. The GeoXO series does not support the DCS command and interrogate function.

13. Commercial RF Communications - it is envisioned that most DCS users will receive DCS data via medium/low rate commercial services.

As noted in Figure 5, OSPO supplies spacecraft and product operations which includes OSPO operators on consoles supporting GEO Ground mission management. As Figure 5 depicts nominal operations, spacecraft and instrument simulations are not shown. Simulations are a suite of Hardware In the Loop (HWIL) and all-software simulators for the use by the GeoXO system users. Both types are utilized for validation of the space and ground segments’ functions, operational products (commands, scripts, page

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

displays), as well as for on-orbit anomaly resolutions. Additionally, spacecraft on-board orbit determination (OD) may utilize data from GPS constellation as currently implemented on GOES-R series.

4.1.2 GeoXO Space Segment

The GeoXO Space Segment comprises the spacecraft, instruments, and auxiliary communication payload, as shown in Figure 6. The GeoXO spacecraft bus supports numerous subsystems. The instruments consist of Earth sensing payloads and a potential partner payload. The auxiliary communications payload (on East and West satellites) contains the DCS transponder to relay the data (in UHF band) from Data Collection Platforms (DCP) to Antenna element of GEO Ground segment. In addition, the DCS onboard transponder also receives UFH Pilot signal from OSPO DCS antenna transmitted from WCDAS (pilot) and CBU. The DCS pilot signal provides amplitude and frequency reference for DCS ingest system and hence is an integral part of the DCS system operation.

Figure 6. GeoXO Space Segment Interfaces

4.1.2.1 GeoXO Spacecraft

The GeoXO series spacecraft bus will be 3-axis stabilized and designed for an on-orbit lifetime of 15 years: up to 5 years of on-orbit storage, 10 years of operational life and additionally, may be stored on the ground for up to five years. The spacecraft bus provides mechanical support and alignment of the various instrument payloads, communication payloads and other bus components.

The GeoXO spacecraft bus will have autonomous fault detection and correction capability, enabling it to survive the occurrence of any credible single component failure or processor upset. On-board autonomy will drive many aspects of the operational procedures. The spacecraft will be capable of executing stored command sequences and table loads that permit up to seven days of autonomous operation without ground interaction. The spacecraft will have autonomous station-keeping capability and will

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

perform uninterrupted image data collection during station-keeping. The spacecraft will have a power-positive safehold mode. The spacecraft flight software will allow modification of telemetry points downlinking on-orbit. The flight software will be able to be uploaded without disrupting normal processor or spacecraft operations.

The GeoXO satellite will be capable of performing a semi-annual “yaw flip” maneuver (180 deg rotation about the nadir axis) but only if instruments require such a maneuver to achieve a seasonal radiometric performance.

With an emphasis on maximizing operational availability, the GeoXO series will continue to perform instrument imaging or data collection without degradation during all spacecraft housekeeping or maneuvers. Consistent with previous GOES series, the GeoXO series will not perform imaging during yaw flip maneuvers (if required by instruments) and will recover and commence imaging within a prescribed period. The cumulative time that imaging is interrupted due to all housekeeping and yaw flip maneuvers will be under 180 minutes/year.

4.1.2.2 GeoXO Instruments

For description of the GeoXO instruments, refer to Section 3.

4.1.2.3 Data Collection System Payload

The Data Collection System (DCS) is the only auxiliary communication payload of the GeoXO system.

The DCS is a relay system used to collect information from a large number of Earth-based platforms that transmit in-situ environmental sensor data on predefined frequencies and schedules or in response to thresholds in sensed conditions. The data from each earth-based Data Collection Platforms (DCP) is transmitted via UHF link to the GeoXO East and West satellites. The GeoXO East and West satellites act as a “bent-pipe” transponder where UHF received signals are converted to an L-band signal and transmitted to the ground segment (DCS system at WCDAS and potentially CBU). Figure 5 above references the DCS system interfaces and the DCS system as a whole. The management of the DCS ground system resources is outside the responsibility of the GeoXO Program and will be the responsibility of OSPO.

4.1.2.4 Launch Vehicle (LV)

The LV will be procured through NASA Kennedy Space Center (KSC). Upon arrival at the Payload Processing Facility (PPF), the spacecraft and instrument contractors will perform final mechanical launch configuration operations, electrical testing, and propulsion/fueling operations. The LVC will then encapsulate the spacecraft into the PLF and transport the spacecraft/PLF to the LV integration facility. The LVC will then integrate the spacecraft/PLF onto the LV. Final closeout operations and electrical testing with the LV will then be performed by the LV, instrument, and spacecraft contractors.

Once the LVC performs final flight closeouts on the PLF, the LV will roll to the pad to begin launch countdown operations.

During the launch and ascent phase, the satellite communications will be through the LV RF systems with details procured by GSFC Code 450. During the GTO phase, the satellite communications will be through the Near Space Network (NSN), Swedish Space Corporation (SSC) network, or Deep Space Network (DSN) dependent on needs and availability of services during the launch period. Once the satellite is placed into the checkout location and Post Launch Testing (PLT) begins, the satellite communications will be through the GEO Ground Segment.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

4.1.3 Ground Segment

The GEO Ground Segment will be implemented as an evolution of the GOES-R Ground Segment (GS) that may also include heritage ground segment elements (TBR). It is envisioned that the GEO Ground segment will reuse portions of the GOES-R GS and evolve to include cloud data processing, for improved efficiencies over the lifecycle. Furthermore, the GS project will apply lessons learned from GOES-R operations including: outsourcing auxiliary communication services (to simplify RF implementation for space and ground projects); incorporating GeoXO functionality into existing GOES- R IT security boundaries (to reduce IT start-up cost, recurring IT overhead); disaggregating L0/L1b and L2+ science data functionality and disaggregating mission management from science data processing.

This approach will keep L0/L1b product generation and distribution tightly coupled with Flight elements which will minimize number of interfaces with external entities. To this end, the L2+ product generation and distribution will be migrated to NCCF to be developed and managed by OSGS (as depicted in Figure 7). Given this architecture of removing L2+ processing from GEO Ground, all user data distribution falls under NCCF to be managed by the OSGS organization.

There are three major functions of the ground segment: Mission Management (MM), Product Generation (PG), and Product Distribution (PD) as depicted in Figure 7. For GeoXO, product distribution consists of product delivery to NCCF only and product processing is to L1b, not higher product levels.

Figure 7. Ground Segment Functions and External Interfaces

The following sections will describe GS functions in more details; however, descriptions are meant to be a notional representation of a desired functionality for the system yet to be designed. To this end, many desired functionalities and GS features described herein are modeled after current GOES-R GS functions.

Responsible Organization: GeoXO Program / Code 410

Check the GeoXO portal at https://camportal.ndc.nasa.gov to verify correct version prior to use.

4.1.3.1 Mission Management

Mission Management (MM) will encompass all operational functions of the spacecraft and instruments.

These functions include:

• Space-Ground communications (uplink & downlink) to all GeoXO satellites (GeoI and GeoS)

• Command generation and telemetry data processing

• Raw (instrument) data processing through Level 0

• Mission operations (includes real-time console operations, offline engineering and trending, bus and instrument health and safety and performance monitoring, anomaly detection & resolution),

• Procedure development, spacecraft resource accounting, special…