SOW 138 eLib.pdf

Statement of Work Task: Space Weather Follow On (SWFO) Analysis Task

Task Order: 138

Task Modification: 2

I. Summary of Changes in this task mod

A CY4 mod accounts for multiple additional iterations of analysis required to resolve questions and incorporate updated information from the SWFO project. Task 138 subtask -1 analysis included new and updated information regarding NSN and DSN coverage, which influenced orbit determination results. This analysis was impacted by the need to address a newly imposed post-deployment calibration maneuver placed shortly after deployment and in the middle of NSN or DSN coverage.

A CY5 mod accounts for the continued support and updates required for the SWFO mission leading into the pre-launch phase that consist of final analyses, FDOA development and training, GMAT modifications, NOAA testing support, and NOAA training for maneuver and navigation operations.

II. Summary of Work NASA Goddard Space Flight Center’s (GSFC’s) Navigation and Mission Design Branch (NMDB) is seeking Contractor support for the Space Weather Follow On (SWFO) Mission.

SWFO will establish an operational capability and continuity of space weather observational requirements. SWFO will enable space weather watches, warnings, forecasting, and predictions. SWFO is a rideshare with the NASA Interstellar Mapping and Acceleration Probe (IMAP) mission provided by an ESPA Grande compatible spacecraft bus. SWFO will orbit the Sun-Earth Libration-1 Point in a Lissajous pattern to perform space weather monitoring and solar observations. The current mission instrument design includes a Coronal White Light Images for detection of Coronal Mass Ejections (CMEs) and in situ solar wind measurements using magnetic fields, thermal plasma, and energetic particles.

A new SWFO Antenna Network (SAN) along with the DSN will be used to provide tracking data measurements for orbit determination (OD). SWFO will use Coherent S-band tracking for Range and Doppler measurements with the SAN delivering these data using a TDM format. For SWFO, the current project plan is for the FDF to provide all mission design, maneuver planning, and OD support until post commissioning which occurs approximately six months after Lissajous orbit insertion. Routine OD support will then be transitioned to the NOAA C2 element at the NOAA facility in Suitland.

SWFO is a three-axis stabilized spacecraft that will perform momentum unloads in the sunward direction. This event, along with the SAN implementation may increase the challenges of the OD support and orbit maintenance.

This task is for SWFO Flight Dynamics and Operations Systems Engineering support needed for project requirements definition, validation and verification, and Flight Dynamics Operations Area (FDOA) Release 3 and Phase C/D design and implementation. The work is divided into five Subtasks:

1) Subtask 1: Systems Engineering Task – OD and Mission Analysis

2) Subtask 2: Ground System Task – FDOA Raptor Development and Documentation

3) Subtask 3: Ground System Task –FDOA GMAT Development and Documentation

4) Subtask 4: C2 Testing and operational readiness support

5) Subtask 5: C2 / NSOF Training

Subtask 1 focuses primarily on the analyses needed to prepare for the SWFO Operational Readiness Review (ORR), Flight Operations Review (FOR), general analysis to support launch readiness activites, develop operational plans, determine accuracies and operational tracking needs, and the Integration and Testing (I&T) activities scheduled between November 01, 2023 and October 31, 2024. This includes the SWFO OD requirements using the ODTK (Extended Kalman Filter (EKF) and Batch Least Squares (BLS)) and GMAT BLS, and SAN antenna certification planning and analysis. OD analysis will address each phase of the mission including: Post deployment and Midcourse Correction maneuvers; Transfer trajectory and statistical correction maneuvers; pre and post Lissajous Orbit Insertion (LOI) maneuver support; and the first several stationkeeping maneuvers. Contingency analysis and alternate design analysis for off nominal launch or maneuver performance will be required.

Subtask 2 covers the Raptor software development activities to support the SWFO Mission.

This includes all activities to support the ORR, scheduled for October 2024, FOR, scheduled for July 2024, and the I&T activities scheduled from November 01, 2023 to October 31, 2024. FDOA-Raptor Release 3 is expected to support of ORR, NOAA ground Command and Control (C2) testing schedules, and establishing FDOA-NOAA C2 interfaces to the Customer Interface Layer (CIL) for operational support. FDOA-Raptor Release 3 is expected to provide updates to Release 2 based on the definition of the Operational Concept. The Operational Concept for SWFO Flight Dynamics is led by SWFO Mission Operations Support Team (MOST). Release 3 is expected to contain maneuver reconstruction and GMAT OD processes, scripts, inputs, outputs, and documentation of each delivered product. Raptor Release 3 will incorporate maneuver reconstruction and OD (GMAT using BLS).

Subtask 3 covers the development of the FDOA GMAT scripts for the C2 NOAA operations team. FDOA-C2 Release 3 includes updates to the design, development, validation and verification, and integration support in C2. These GMAT scripts are used for all products including OD and maneuver planning and reconstruction. FDOA-C2 Release 3 is expected to provide updates to Release 2 scripts based on the results of the I&T activities,the definition of the Operational Concept, and improvements made by the FD team. The I&T activities are scheduled between November 01, 2023 and October 31, 2024. The SWFO implementation of GMAT and the associated scripts in the GOES-R MOST scripting automation environment, known as GLADOS, is expected by August 2024. The validation of the Navigation process for SWFO (within NOAA ops system) is expected in the Sept-Oct 2024 timeframe.

Subtask 4 will support establishing the NOAA FDOA-C2 interfaces to the CIL to support the I&T activities scheduled for January 2024 to October 31, 2024. Support will be provided for the major C2 End to End tests that include the Ground Validation Test (GVTs), Mission Rehearsals (MRs), SAN tracking data delivery, and several End to End (E2E) test. These tests include product generation and verification for various phases of the mission, e.g. post deployment and MCCs, LOI, and stationkeeping. Products wil be provided for each test.

Tracking data from SAN via TDMs and from DSN via Trk 2-34 formats will be ingested. The tentative schedule for the tests is given in Table 3.

Subtask 5 will be the definition of a training plan for the NOAA C2 Operations Team. This will include a GMAT tutorial for all procucts and processes including; SWFO OD, maneuver planning, reconstruction, and calibration, viewperiod data, training data for Libration Point Orbits OD, and hands-on training using the FDOA-C2 GMAT OD scripts.

III. Period of Performance The period during which the work for these tasks shall be performed is from November 1, 2023 to October 31, 2024.

IV. Task Description

1. Subtask 1: Analysis

Subtask Scope:

SWFO OD will be provided by the GSFC FDF from deployment (launch plus ~one hour) through Lissajous orbit insertion (LOI) + commissioning (~ LOI plus six months). Post commissioning, routine OD support (Lissajous orbit only) is planned to be performed by NOAA / C2 in the NSOF. Backup FDF OD support and contingency FDF support is to be provided over the duration of the five-year mission. With a Momentum Unload frequency of at least seven days pointed nominally in a sunward direction, the OD will pose a challenge.

This subtask will assume that the Phase C baseline is Ground-based OD.

Tracking data (range and Doppler) is expected to flow from SAN Wallops and Consolidated Backup (CBU) Facility CBU stations and be processed to compute a navigation solution.

These antennas need to go through the certification process. This subtask will also assist on the SAN antenna certification process. Relevant documentation will be provided including updates to the Naviagtion plan, Models and Constants Document, and SAN Certification plan.

The goals of this subtask will be the following:

1a) Perform Analysis to finalize the C2 to Nav/Att ICD, SAN to C2 ICD, FD to SC ICD, FDOA C2 Ops Agreement, Navigation Plan and the FDOA Models and Constant document.

1b) Certify SWFO Antenna Network (SAN) for operational support.

Technical Requirements:

1a) Perform Analysis to finalize the C2 to Nav/Att ICD, SAN to C2 ICD, FD to SC ICD, FDOA C2 Ops Agreement, Navigation Plan, and the FDOA Models and Constant document

Analyses will be completed to address project updates since the MOR (June 2023). The following analyses must be complete prior to the end of the Period of Performance such that there is sufficient time to present updates to the Task Monitor as well as make any subsequent updates to the SWFO Navigation Plan. The Task Monitor along with Ref. [1] will provide inputs for the assumptions to be used for the analyses. The analyses are summarized in tables 1 and 2 below. The mission peofile remains the same for MCC1, MCC2, TCMs, LOI and Stationkeeping maneuevrs. The Momentum unloads (MU) will remain the same candence, e.g. weekly MUs with residual DVs of ~ 5.77 cm/s towards the sun. MU profiles ( frequency and DV residual magnitude) during the transfer trajectory are expected to be update by the project based on operational performance.

Meeting Requirements: It is expected that members on this subtask will meet with the Task Monitor once a week to provide updates to the analysis, documentation, and FDOA development. The contractor team shall document and record in the FDSSIII SWFO Flight Dynamics Confluence page the minutes of all meetings and keep track of actions.

Staffing Requirements: This subtask shall be staffed by engineers with experience in Navigation (both analysis and operations), requirements definition (preferably with a Libration Point mission such as DSCOVR, SOHO, RST, JWST), and a subject matter expert in ODTK and GMAT for consultation. Analysts working on this task will have experience assessing navigation tools and doing navigation analysis designed to address requirements compliance. Also, staff in this task shall have experience in the antenna certification process.

Configuration Management Requirements:

• All analysis under this subtask shall be documented

• All analyses will be tracked using the FDSS III SWFO JIRA system.

• Power point presentations and reports shall be stored on the FDSS III SWFO Flight

Dynamics Confluence page.

• All code and navigation tool scenario files used for analysis shall be stored on

BitBucket or on a similar repository with access by code 595.

2. Subtask 2: Ground Systems Subtask – FDOA Raptor Development and Documentation

Subtask Scope:

This subtask will provide technical evaluation, and assessment of various technical aspects of the mission pertaining to development of ground requirements and implementation concepts (ground design, interfaces, and ops concepts), as well as engineering oversight in the implementation of the SWFO ground operations concept development. The FDF is baselined to generate and provide operational products in operations for the SWFO project, from launch through commissioning, which ends approximately six months after Lissajous orbit insertion (LOI).

This subtask will work to integrate SWFO mission design tools and OD tools. This subtask will coordinate with the Roman Space Telescope (RST) for designing Raptor to support SWFO and will work to finalize all documentation in preparation for the ORR, FOR, and I&T activities.

• This subtask will document the architecture for the SWFO FDOA software around ODTK to support operations before NOAA C2 handover. They will also document the use of GMAT OD for comparison to the NOAA C2 version used for routine operations.

• The Task Monitor will provide updates to the list of products requested by the C2 (e.g.

definitive OD products, predictive OD products, ephemerides, etc.) as listed in the C2 Nav/Att ICD.

• This subtask will develop procedures in Raptor to automate OD simulations that will meet the scope of the C2 integration and testing. This will also support the project ORR scheduled for October 2024 (TBD). Both ODTK and GMAT are requested for OD support.

• The Raptor procedures that need to be complete for Release 3 to be listed in the FDOA Build and Release Plan are as follows o Tracking Data Processing Ingest of tracking data (TDM and TRK 2-34 formats) o Ingest of Definitive Attitude data provided in a txt format via CIL o Ingest of C2 Mission Timeline (tracking pass times) o Orbit Determination (Spherical SRP, with and without maneuvers) o Orbit propagation (Spherical SRP with and without maneuvers o Predictive 7-day and 28-day Ephemeris Generation and delivery to C2 o Predictive 2-year Ephemeris Generation and delivery to DSN o Ground Station View Periods Generation and delivery to C2 o Definitive Ephemeris Generation and delivery to C2 o OEM format for all ephemeris data o Delivery of Maneuver Reconstruction and calibration reports to C2 o Spacecraft Mass and SRP (CsubR) updates after maneuvers, delivery of Fuel

Mass report and SRP estimation report to C2 o Stationkeeping planning and reconstruction (GMAT) o MCC1 and MCC2 planning and reconstruction (GMAT) o TCM planning and reconstruction (GMAT) o LOI planning and reconstruction (GMAT) o MU modeling and implementation into the OD and manuever planning process

• Reports generated for OD and maneuver planning and reconstruction will be required

• System Engineering support will be necessary in order to organize the FDOA

Development, Documentation, and Testing Schedule

• The Task Monitor will be involved in the Procedure Development/Coding, and will be given the opportunity to participate in the Raptor meetings held internal to the FDF and review the updates being made for SWFO

• The Task Monitor also requests separate Raptor meetings to show what progress has been made on Raptor on a bi-weekly basis

• The documentation that will be finalized under this subtask includes the following (documents with an asterisk are responsibility of SWFO FD):

o Updates/inputs to FDOA Level 3-4 Requirements These are the requirements that define the scope and purpose of the

FDOA

o Updates/inputs to FDOA Configuration Management Plan

This will be the FDOA’s internal CM plan to establish best practices/CM methods for FDOA Development o Updates/inputs to C2 Nav/Att ICD This document contains all the products that the FDOA will send to and receive from the C2 o Updates/inputs to FDOA Raptor Design Document o Updates/inputs to FDOA Raptor Acceptance Test Plan capabilities are being developed/included into the Raptor development plan to support

SWFO.

Configuration Management Requirements:

• All analysis under this subtask shall be documented

• All analyses will be tracked using the FDSS III SWFO JIRA system.

• Power point presentations, documents, and reports shall be stored on the FDSS III

SWFO Flight Dynamics Confluence page.

• All code and scripts shall be stored on BitBucket or on a similar repository with access by code 595.

Deploy an infrastructure that ensures that all analyses are using the same system configuration (Virtual Machines, docker containers, etc…).

3. Subtask 3: Ground System Task –FDOA GMAT Development and Documentation

Subtask Scope:

This subtask will provide technical evaluation, and assessment of various technical aspects of the mission pertaining to development of ground requirements and implementation concepts (ground design, interfaces, and ops concepts), as well as engineering oversight in the design and development of the operational GMAT scrips to support SWFO FD operations.

The FDF is expected to handover Flight Dynamics operations to the NOAA-C2 team after commissioning (Lissajous Orbit Insertion (LOI) plus ~6 months). The FDF is expected to develop and update GMAT scripts that perform the following flight dynamics tasks:

• Maneuver planning and the maneuver reconstruction and calibration for all Stationkeeping and routine orbit maintenance o These include maneuver reports for planning and reconstruction that contain calibration data, e.g. mass, SRP data

• Orbit determination

• Antenna view periods

• Predicted and definitive ephemeris generation

This task will work to design, develop, test, and document the above-mentioned flight dynamics operational GMAT scripts.

• The Task Monitor will provide the expected inputs and output of the GMAT operational scripts

• This subtask will document the architecture for the GMAT operational scripts

• The GMAT procedures that need to be complete for Release 3 (planned for January 31, 2024)

Meeting Requirements: This task will support SWFO FDOA-GMAT meetings and technical interchange meetings and teleconferences. It is expected that members on this subtask will meet with the Task Monitor weekly for FDOA-GMAT Development and documentation. The FDOA-GMAT team will also schedule a meeting will the Task Monitor weekly to provide a development status to the team. The contractor team shall document and record in the FDSSIII SWFO Flight Dynamics confluence page the minutes of all meetings and keep track of actions.

Staffing Requirements: This task shall be staffed by engineers with GMAT software development experience and with operational experience delivering OD products. The task will also be staffed with a System Engineer to ensure comprehensive understanding between the GMAT (and Raptor during pre-routine Lissajous Support) and NOAA team on the con-ops, flow of products, requirements, FDOA development, and testing for the necessary Raptor updates.

Configuration Management Requirements:

• All analysis under this subtask shall be documented

• All analyses will be tracked using the FDSS III SWFO JIRA system.

• Power point presentations, documents, and reports shall be stored on the FDSS III

SWFO Flight Dynamics Confluence page.

4. Subtask 4: C2 Testing and operational readiness support

Subtask Scope:

This subtask will provide technical evaluation, and assessment of various technical aspects of the mission pertaining to testing and operational readiness of ground requirements and implementation concepts (ground design, interfaces, and ops concepts).

This subtask shall work to establish and test the CIL interface between the FDF and NOAA- C2. This subtask will support establishing the interfaces to the C2 via the CIL to support the I&T activities scheduled for January-October 2024. Support will be provided for the major C2 End to End tests that include the GVTs, MRs, SAN tracking data delivery, and several E2E test. These tests include product generation and verification for various phases of the mission, e.g. post deployment and MCCs, LOI, and stationkeeping. Products wil be provided for each test. Tracking data from SAN via TDMs and from DSN via Trk 2-34 formats will be ingested. A voice communication link between FDF and NSOF shall be established prior to any C2 test.

Each of the tests shown in the table require support for data product generation (pre-test and during each tests), real-time staffing support during each tests from the FDF, interface with C2 via the CIL for product delivery, voice communication with the NSOF (other other designated facility – TBD). And senior-level technical and management staffing to ensure tests are successfully completed.

A separate tests series will be conducted to certify the SWFO SAN tracking capabilities at WDACS (Wallops), and CBU. These test will incorporate both static (simulated) and real tracking data, potentially from SOHO and DSCOVR. The SAN test schedule is TBD, The current test schedule is as follows, with GVTs, MRs, and SAN test a priority.

Table 3. FD Supported Tests and Draft Schedule

Staffing Requirements: This task shall be staffed by engineers with testing and software development experience and with operational experience delivering OD products. The task will also be staffed with a System Engineer to ensure comprehensive understanding between the GMAT and NOAA team on the con-ops, flow of products, requirements, FDOA development, and testing.

Configuration Management Requirements:

• All analysis under this subtask shall be documented

• All analyses will be tracked using the FDSS III SWFO JIRA system.

• Power point presentations, documents, and reports shall be stored on the FDSS III SWFO Flight Dynamics Confluence page.

5. Subtask 5: C2 / NSOF Training

Subtask scope:

This support includes maneuver planning, and OD training using GMAT and establishing interfaces with the NOAA C2 facility for tracking data reception and product generation and delivery via the FDF Customer Interface Layer (CIL).

With the current plan to transition routine OD support the C2, the subtask shall also support and develop a training plan for the NOAA Maneuver and Navigation staff. This plan assumes the use of GMAT for OD support in the C2 element at NOAA. This plan shall incorporate routine scripts for OD processing, training material (documents and presentations), demonstrations, and hands-on training during the transfer trajectory support.

The SWFO Flight Dynamics GMAT Training package delivery date is March 28, 2023. This includes:

• Session 1: Basics of GMAT

• Session 2: GMAT for SWFO Maneuver Planning and Reconstruction

• Session 3: GMAT BLS for SWFO Orbit Determination

• Session 4: GMAT to generate SWFO reports and products

• OD Hands-on training

The OD Hands-on training is designed to help the trainees to be exposed to a real operational OD experience. The main goal is to help the trainees to build an intuition on how to identify, diagnose, and solve problems that arise during operations. The idea is to have NOAA-C2 personnel be physically at the FDF for two sessions to process real data from an operational Libration Point Orbit (LPO) mission (e.g., DSCOVR) using the FDOA-C2 OD GMAT scripts, and try to reproduce the results obtained by the FDF with the help of a navigator. Other training will be provided at the NSOF facility.

V. Deliverable Items and Schedules

Table of Milestones

Milestone Review Date Description

FDOA demo for C2 personnel at GSFC

January 2024 (TBD) Demo of the FDOA-Raptor functionalities to support SWFO from the FDF

Mission ORR October 2024 We will present a summary of the FDOA status at this review

FOR July 2024 We will present a summary of the FDOA status at this review

FDOA GMAT Release 3 Design Document (Word/PDF) March 31, 2024

FDOA GMAT Release 3 Acceptance Test Plan (Word/PDF) March 31, 2024

FDOA-GMAT Release 3 April 28, 2024

Antenna Certification Plan (Word/PDF) May 1, 2024

FAT Final Report (Word/PDF) August 15, 2024

UAT Final Report (Word/PDF) August 15, 2024

GMAT-Raptor Release 2 August 18, 2024

FDOA C2 Ops Agreement October 01, 2024

GMAT OD focused peer-review (PowerPoint) ORR – 3 months

VI. Management Approach

a. Staff Allocation, Expertise, and Skill Mix

The staffing requirements are placed under each subtask.

b. Configuration Management

Systems and documents will be covered under the SWFO Configuration Management Plan.

c. Facilities

Appropriate IT devices to support the analyses, specification development, and report development are required. It shall be the contractor’s responsibility to provide and set up local workstations and network connections at the contractor’s off-site facilities as required, and to install any required tools and utilities on the contractor’s equipment.

d. Risk Management and Best Practices

The contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the compliance of the TM.

VII. Performance Metrics

N/A

VIII. Government Furnished Facilities, Equipment, Software and Other Resources The Government will provide account and passwords to government-furnished workstations where existing versions of various relevant software packages shall be maintained. It shall be the contractor’s responsibility to complete any GSFC required security-related training courses.

IX. Travel There is no non-local travel for this SOW. There is local travel to NOAA (NSOF) for training summarized in the following table:

Trip Description # of Business Days Destination Dates

NOAA-C2 Training 1 Suitland, MD TBD

X. Work Location This work shall be performed partly at the Contractor’s facilities and at Goddard Space Flight Center.

XI. Reporting Requirements The Contractor shall report status on a weekly basis for Subtask 1, 2, 3, and 4. Reports shall include interim results, status of development activities, current and projected issues, and other action items. The Contractor shall comply with all additional requests for status meetings, reports, and reviews.

XII. Security Requirements This task shall comply with IT security requirements as documented in the FDF IT security plan for all systems located in the FDF. FDF systems shall be maintained under the FDF Sustaining Engineering Task. Systems located outside of the FDF shall be covered under the Code 590 security plan and the Code 590 sustaining engineering support or the contractor sustaining engineering support depending on system location.

XIII. Rights

The Contractor shall adhere to the FAR 52.227-14 RIGHTS IN DATA – General, Alternate II (2007) and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).

XIV. References [1] FDSS-III-138-TBD General Mission Analysis Tool (GMAT) Analysis Definitions

[2] SWFO Program CDR. May 23-25, 2023

[3] SWFO Program MOR. June, 2023