NOAA GEO GS SE RFI Attachment 7 SRR Requirements Briefing.pdf

GEO Ground Project Requirements (Level III) X-SRR Aug 2022

GeoXO System Requirements Review

GEO Ground Project Requirements (Level III)

Kevin McMahon

GEO Ground Chief Engineer

GSFC Obenschain Conference Center (B36)

August 23-25, 2022

19-1

Agenda

• Requirements Hierarchy & Traceability

• Key & Driving Requirements

• Architecture Overview

• Studies & Prototypes

• Path to MDR

19-2

Key & Driving Requirements – Deltas from GOES-R

• Auxiliary Comm

• No GOES ReBroadcast (GRB) requirements for GeoXO ground - transferred to NESDIS

• Three operational satellites (East/West/Central)

• Product Generation (PG) / Product Distribution (PD)

• No Level 2 (L2) PG or PD

• No direct interface to the National Weather Service (NWS)

• Level 0 (L0) and Level 1b (L1b) PD to NCCF only

• Primary and backup site remaining operational during maintenance

• Generation of L1b products for satellites located anywhere in the range from 65°W to 147°W

• Backwards compatibility and evolution to a multi-mission ground system

• Common ground system (GS) flying GOES-R Series, Space Weather Follow On (SWFO)-L1 and GeoXO missions

• New data flow for Cloud Cover Mask (developed from GeoXO Imager (GXI) data) and uplinked associated optimized scan pattern back to instruments

• No space weather instruments

19-3

Driving Requirements – System Sizing/Extensibility

19-4

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD148 The GeoXO System shall operate the following instruments and auxiliary communication payloads at the following geosynchronous orbital locations:

East/West (GeoI) GeoXO Imager (GXI) GeoXO Lightning Mapper (LMX) GeoXO Ocean Color Imager (OCX) Auxiliary Communication Services Data Collection System (DCS) Center (GeoS) GeoXO Hyperspectral IR Sounder (GXS) GeoXO Atmospheric Composition (ACX) Partner Payload

The Operational Satellites will require additional resources (antenna, SGC, computing, storage) over current GOES-R system.

MRD391 The GEO Ground Segment shall scale to 2x capacity over the lifetime for all functionalities and interfaces supporting product generation and distribution to

NCCF.

Drives Easily Extensible Architecture

MRD392 The GEO Ground Segment shall provide reserve capacity of 1.25x nominal for growth during the mission for all functionalities and interfaces supporting product generation and distribution to NCCF.

Rationale: Nominal here refers to the full configuration of the GeoXO System (GeoI West, GeoI East, GeoS Central, Storage (including Annual Checkout) and Initial Checkout)

Drives Easily Extensible Architecture

Driving Requirements – Availability (1/2)

19-5

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD63 The GeoXO System shall have an availability of 0.90 each month for HAP at the East and West geosynchronous orbital locations, over System lifetime.

Will drive Architectural Redundancy and selection of Component parts

MRD70 When operational, the GeoXO System shall provide continuous sensor data for ground generation of non-HAP L0 data with outages less than 70 hours per year and no single outage exceeding 24 hours.

Rationale: This is the acceptable downtime for non-HAP L0 data.

Will drive Architectural Redundancy and selection of Component parts

Driving Requirements – Availability (2/2)

19-6

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD356 The GEO Ground Segment monthly availability shall be at least 0.989 over the system lifetime.

Rationale: This availability covers non-HAP functions, as HAP functions must be restored more rapidly.

Will drive Architectural Redundancy and selection of Component parts

MRD359 The GEO Ground Segment Maximum Time To Restore Service (MaxTTRS) functionality related to HAP generation shall be no greater than 10 minutes.

Will drive Architectural Redundancy and operations/failover approaches

GeoXO GS to NCCF IRD ID GeoXO GS to NCCF IRD Text Design Implications

TBD XXX Availability, defined by the ratio Uptime / (Uptime+Downtime) of the GS to NCCF interface shall be 0.9999 (TBR) computed on a monthly basis.

Will Drive Interface Design

Driving Requirements – Maintenance Availability

19-7

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD396 The GeoXO System, including both primary and backup ground sites, shall remain operational during all planned system maintenance activities.

Rationale: The requirement is intended to prevent an entire site shutting down during planned system maintenance. Exceptions to this would include events like site power outages.

Will drive Architectural and Maintenance Approaches

Driving Requirements – NCCF Interface

19-8

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD388 The GeoXO System shall provide earth-observing L0 and Level 1b data and associated metadata to the NESDIS Common Cloud Framework (NCCF) users as defined in the “GS to NESDIS Common Cloud Framework (NCCF) Interface Requirement Document” 416-GEO-IRD-0102 [Applicable Document 15].

Rationale: The NCCF will be used to compute the L2+ products for GeoXO using the L1b radiances inputs.

Drives a new interface and changes to PG/PD responsibilities

MRD364 The GEO Ground Segment shall make available L1b software algorithm versions to NCCF for NOAA archiving.

Drives scope of new interface

MRD365 The GEO Ground Segment shall make available data supporting product performance evaluation to NCCF for NOAA archiving.

Drives scope of new interface

Driving Requirements – L1b Generation

19-9

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD50 The GeoXO System shall generate Level 1b products for any GeoXO satellite located between 65° West and 147° West.

Rationale: Both the GeoXO Space Segment and Ground Segment must be capable of generating satellite data products regardless of the satellite's operational location in the range of orbital locations identified.

Architect simple system configurability to manage changes in orbital positions

No ancillary or ADRS data necessary

Driving Requirements – Automation

19-10

GeoXO MRD ID GeoXO MRD Text Design Implication

MRD464 The GEO Ground Segment shall autonomously provide L1b data without operator intervention for a period of 7 days.

Rationale: This implies autonomous operations without operator intervention.

Enable capability to implement increasing levels of mission operations and data production automation.

Product Differences Driving Ground Design Summary

• New Instruments

• Hyperspectral Data Processing

• Atmospheric Radiances

• Partner Payload

• Throughput

• Finer resolution of Earth Imaging Radiances

• Hyperspectral data processing

• Product Latency (final data collection to NCCF availability)

• Imaging Radiances

• Full Disk and Super Regional: 60 seconds

• Mesoscale: 30 seconds

• Lightning Detection: 20 seconds

• Hyperspectral Infrared Radiances: 240 Seconds

• Atmospheric Composition Radiances

• Super-Regional: 660 seconds

• Water-Leaving: 600 seconds

• Cloud Cover Mask computation and uplink

• Architect to minimize dependencies between Mission Management (MM) and PG

19-11

Driving Requirements – New Instruments

19-12

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD113 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for the SFD region within a Mission Product Data Latency of 240 sec.

Latency, new instrument. Hyperspectral data processing

MRD114 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for the Super- Regional region within a Mission Product Data Latency of 240 sec.

Latency, new instrument. Hyperspectral data processing

MRD115 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for a Mesoscale region within a Mission Product Data Latency of 240 sec.

Latency, new instrument. Hyperspectral data processing

MRD120 The GeoXO System shall make available Level 1b Atmospheric Composition Radiances for the Super-Regional region within a Mission Product Data Latency of 660 seconds.

Latency, new instrument

MRD126 The GeoXO System shall make available Level 1b Top of the Atmosphere Radiances for Water- Leaving Radiances within a Mission Product Data Latency of 600 seconds.

Latency, new instrument

MRD368 The GEO Ground Segment shall monitor the quality of all products. New instruments may generate products that are challenging to monitor.

MRD371 The GEO Ground Segment shall produce Level 0 and L1b data from a Partner Payload instrument, if provided.

Rationale: At minimum if instrument provided, we would do Level 0 processing and the potential exists for providing L1b processing as well.

Unknown impacts, including monitoring the products

Driving Requirements – Product Latency

19-13

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD94 The GeoXO System shall make available Level 1b Imaging Radiances for the Full Disk region within a Mission Product Data Latency of 60 sec. Note: See definition of Mission Product Data Latency in section 3.3.3.5

Latency

MRD95 The GeoXO System shall make available Level 1b Imaging Radiances for the Super-Regional region within a Mission Product Data Latency of 60 sec.

Latency

MRD96 The GeoXO System shall make available Level 1b Imaging Radiances for a Mesoscale region within a Mission Product Data Latency of 30 sec.

Latency

MRD101 The GeoXO System shall make available Level 1b Lightning Detection Events within a Mission Product Data Latency of 20 sec.

Latency

MRD113 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for the SFD region within a Mission Product Data Latency of 240 sec.

Latency, new instrument. Hyperspectral data processing

MRD114 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for the Super-Regional region within a Mission Product Data Latency of 240 sec.

Latency, new instrument. Hyperspectral data processing

MRD115 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for a Mesoscale region within a Mission Product Data Latency of 240 sec.

Latency, new instrument. Hyperspectral data processing

MRD120 The GeoXO System shall make available Level 1b Atmospheric Composition Radiances for the Super-Regional region within a Mission Product Data Latency of 660 seconds.

Latency, new instrument

MRD126 The GeoXO System shall make available Level 1b Top of the Atmosphere Radiances for Water-Leaving Radiances within a Mission Product Data Latency of 600 seconds.

Latency

Driving Requirements – Throughput

19-14

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD182 The GeoXO System shall observe earth Imaging Radiances with a minimum nadir spatial resolution of 2 km, except for 1 km for each of the 0.91, 1.61, 2.25, 3.9, 5.15, 6.95, and 10.35 um bands, 0.5 km for the

0.47 and 0.86 um band, and 0.25 km for the 0.64 um band.

Finer resolution of multiple bands drive increase in data rate and computational load. In particular, 0.25 km for the 0.64 um band will quadruple the size of ABI band 2, which is our current KPP throughput driver.

MRD113 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for the SFD region within a Mission Product Data Latency of 240 sec.

Latency, new instrument.

Hyperspectral data processing

MRD114 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for the Super-Regional region within a Mission Product Data Latency of 240 sec.

Latency, new instrument.

Hyperspectral data processing

MRD115 The GeoXO System shall make available Level 1b Hyperspectral Infrared Radiances for a Mesoscale region within a Mission Product Data Latency of 240 sec.

Latency, new instrument.

Hyperspectral data processing

Driving Requirements – Cloud Cover Mask

19-15

GeoXO MRD ID GeoXO MRD Text Design Implications

MRD465 The GEO Ground Segment shall generate a simplified cloud cover mask resulting from GXI processing.

Rationale: A simplified cloud cover mask needs to be accessible for commanding for other instruments.

New data flow between MM and DO

– need to carefully architect to minimize dependencies and security implications

MRD466 The GEO Ground Segment shall uplink to the instruments a simplified cloud cover mask resulting from GXI processing.

Rationale: A simplified cloud cover mask will be used by instruments to optimize scanning due to cloud cover. Specifically, information from PG must be shared with MM to enable this periodic uplinking.

New data flow between MM and DO

– need to carefully architect to minimize dependencies and security implications

GEO GS Functional Elements

• MM: All operational functions of the spacecraft and instruments including but not limited to:

• Space-to-Ground Communications (SGC)

• Command generation and telemetry processing

• Mission scheduling and planning

• Orbit determination and maneuver planning

• Raw data processing through L0

• Data Operations (PG/PD): Generation of the L1b data products and transmission of data products to NCCF

• Enterprise Management (EM): Underlying computing and network infrastructure, including monitoring and reporting performance

• Antenna: Reflector and all associated transmit/receive equipment necessary to establish RF uplink/downlink path to satellites

19-16

GEO GS Functional Architecture and Interfaces

19-17

S-Band

Cmd,Tlm, & Ranging, DCPC

L/S-Band

Tlm

X-Band

Science

Data

GeoXO East/West Spacecraft (GeoI)

Mission Management (MM)

Data Ops (DO)

(PG/PD)

Antennas L0/L1b Data

S-Band

Cmd,Tlm, & Ranging

L/S-Band

Tlm

X-Band

Science

Data

GeoXO Center Spacecraft (GeoS)

GEO Ground

GeoXO Program

Spacecraft & Product Ops

Office of Satellite & Product Ops

Data Collection System (DCS) Ops

Non-NOAA Data Secure Ingest

Office of Satellite Ground Services (w/Center for Sat. Apps & Research)

Product Gen./Data Distribution/Archive

DCPR (I/F)

Enterprise Management (EM)

2 2 2 3

2 2 2

DCPR (L)

Updated

DCPC (IF)

GEO GS External Interfaces

19-18

I/F No.

Description Governing Document

Level 0 and Level 1b+ data products to NCCF for distribution

416-GEO-IRD-102: GS to NESDIS Common Cloud Framework IRD

Spacecraft to Ground L- and S-band Interfaces for C&T, Ranging, as well as X- Band Science Data

418-XO-IRD-0043: SS to Ground Located Command, Control & Communications (SS-C3S) IRD

Space Segment L- and S-Band Interface from Data Collection System transponder to GS antennas

418-XO-IRD-0044: SS to Data Collection System (SS-DCS) IRD

Terrestrial transmission of Intermediate Frequency DCS Data to OSPO, DCPC from

OSPO

416-GEO-IRD-0131: GS to Data Collection System (DCS) Data Collection Platform Receive (DCPR) IRD (update this document)

Updated

Ongoing Studies & Pathfinders

• Executing an antenna resource study to determine the required number and locations of GEO Ground antennas

• Current GS has three tri-band X/S/L antennas at Wallops Command and Data Acquisition

Station (WCDAS) and three at the Consolidated Backup (CBU)

• GEO Ground will need to support existing GOES-R constellation until retirement while supporting GeoXO satellite launch schedule

• GeoXO adds a third operational data flow with the central spacecraft

• Study will determine the maximum required antennas and durations depending on expected launches and projected satellite lifetime

• Define and recommend number of steady state antennas required and how to meet peak load with potential surge capacity

• Close coordination with Space Weather Follow On (SWFO)-L1 program as a GEO GS mission integration pathfinder

• Defining processes to support multiple missions

• Extending ground capabilities, especially infrastructure

• Capturing lessons learned on architectural pinch points that can be re-worked for GeoXO

• Completion of SWFO Ground integration, and SWFO-L1 launch, occurs prior to procurement phase for GEO Ground updates to support GeoXO

19-19

Ongoing Cloud Efforts – Establishing the GeoCloud

• Prototyping with cloud-based technologies since 2020

• Leveraging Amazon Web Services (AWS) as the Cloud Service Provider, using an Infrastructure as a

Service (IaaS) model

• Exploring infrastructure and security services

• Prototypes include numerous data access mechanisms as well as enabling mission partner tools to be co-located in the cloud

• Currently establishing operational GeoCloud

• Subsystem within NOAA5050

• Interim Authority to Test (IATT) has been granted. Authority to Operate (ATO) planned for

September/October 2022

• Migrating three services for mission data access (LZSSc, eGRESc, GL0ASc)

• Providing environment for mission partner tools to integrate with GeoCloud services

• GeoCloud capabilities

• All product data from all satellites, including Sectorized Cloud and Moisture Imagery (sCMI), is available in the cloud in near-real time

• Filterable subscriptions to support asynchronous transactions for authorized users

• Support of flow to National Centers for Environmental Information (NCEI) for archiving

19-20

Ongoing Cloud Efforts

• GeoCloud enabling Mission Partner participation/collaboration

• Mission Partner Tools VPC allow co-located tools within the GeoCloud environment

• Simplifies mission partner access and lowers egress cost

• Allows partners to leverage cloud resources

• Currently four tools in prototyping: geoTOWRS, MOA, proGHOST, ABIPLTc

• geoStream service

• Streaming GOES-16 GRB to GeoXO exploration prototype

• Exploring alternative formats, protocols and content

• Including customizable streams

• DCS proof of concept

• Working with DCS team to integrate digital DCS stream in GeoCloud (prototype)

• Explore, evaluate, and measure DCS access mechanisms with targeted users

• Purpose is to gather experience and lessons learned for future decisions

• L3Harris Special Studies

• Completed Special Study 25 to explore use of cloud technologies as a GS Development Environment (DE)

• Kicked off Special Study 26 to develop a proof of concept for GOES-R data product generation in the cloud.

This will provide technical and management experience to inform future product generation decisions

19-21

Future Planned Efforts

• High Rate Information Transmission/Emergency Managers Weather Information Network (HRIT/EMWIN) data distribution via cloud

• Will provide information and lessons for future NCCF user facing services

• Studies for major functional areas: DO, Antenna, EM

• Weigh the pros/cons, risks, opportunities, and cost comparisons

• Capability migrated to cloud vs continued execution on-premises at WCDAS/CBU

• If recommended for cloud then continued analysis of execution on Government vs

Contractor-owned cloud (IaaS vs Software as a Service (SaaS))

• Will leverage results of all prototype activities to define costs and technical capabilities/risks

• Study advancements in automated operations

• GeoXO CONOPS communicates a goal of automating operations in support of an eventual

8x5 staffing model

• Will explore opportunities to take advantage of existing system capabilities and/or emerging technologies

19-22