SOW 120 eLib.pdf

Statement of Work Task: PACE Flight Dynamics Design & Analysis Task Order: 120 Task Modification: 8

I. Summary of Changes in this Task Modification

This task modification extends the period of performance and updates deliverables and milestones. It adds Subtask 1 requirement (d) for post-commissioning support.

II. Summary of Work This SOW provides anticipated work and direction for flight dynamics design and analysis for the Plankton, Aerosol, Cloud, Ocean Ecosystem (PACE) mission. The work described consists of flight dynamics-related analyses and development of the flight dynamics system (FDS) within the PACE ground system mission operations center (MOC) as agreed to by the PACE project and the Navigation and Mission Design Branch (NMDB, GSFC Code 595).

III. Period of Performance The period during which the work for this task shall be performed is between November 1, 2019 and September 30, 2024.

IV. Task Description Subtask 1: Ground System Development Task Scope: Development of the PACE flight dynamics system (FDS).

Technical Requirements:

a) Define PACE ground trades and requirements to support project reviews.

b) Support the TM in developing and maintaining the FDS that resides in the PACE MOC. This includes:

• Developing and maintaining scripts for the following subsystems as required to support

FDS Build 1, Build 2, and Build 3, and subsequent maintenance builds:

o Product generation o Maneuver planning o Orbit determination o Ephemeris generation o Maneuver reconstruction and calibration o Acquisition data o Automation o Visualization o FDS infrastructure and utilities

• Collaborating with team on development processes, best practices, and quality improvement.

• Participating in development lifecycle activities, including design development, testing, performing code walkthroughs, and participating in systems testing.

• Performing technical analyses related to establishing the recommended FDS configuration, esp. related to processing of GPS and Galileo point solution and pseudorange telemetry.

c) Attend weekly PACE Flight Dynamics team meetings and PACE Ground Segment reviews and meetings as scheduled.

d) Post-commissioning, defined as after 60 days post-launch:

a. Support the PACE Flight Operations Team (FOT) in operations of the FDS and execution of the associated flight operations procedures (FOPs)

b. Develop and release patch builds of the FDS as needed, including external components, and coordinating with the FOT to test and install builds in the PACE MOC and BMOC.

c. Maintain configuration management of the FDS and FOPs with the PACE project and

NMDB.

d. Support FOT in non-routine operations, including:

i. Planning and evaluation of spacecraft maneuvers, including risk mitigation maneuvers (RMMs)

ii. Transitions between operations strings, and between MOC and BMOC.

iii. Periodic lifetime analyses

iv. Periodic (monthly or quarterly) proficiency exercises with FDF

v. Periodic covariance realism evaluations with SpaceNav

Skill Requirements: Experience with earth science mission operations, especially within the GSFC ESMO organization. Experience with Global Precipitation Measurement (GPM) mission operations.

FreeFlyer mission design and orbit determination, XFDS, MATLAB, Perl, and related computer programming languages.

Subtask 2: Flight Dynamics Analyses Task Scope: Flight dynamics-related analyses for the PACE mission.

Technical Requirements:

• Support the PACE Guidance Navigation and Control (GN&C) Flight Dynamics team in the following analyses and activities leading to project reviews:

a) Delta-V analysis

b) Science requests for calibration and orbit optimization.

c) Lifetime analysis (maneuver statistics, drag acceleration, constraints, etc.…)

d) Thruster and tank modeling

e) Maneuver prediction accuracy

f) Maneuver operations planning

g) Station-keeping analysis

h) Controlled re-entry analysis

i) Navigation analysis

j) GPS multipath and visibility analysis

k) Launch dispersion analysis

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 No travel is planned for this period of performance.

X. Work Location This work shall be performed primarily on-site at the Goddard Space Flight Center, but the contractor may be required to perform some work at the contractor’s facility.

XI. Reporting Requirements The contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the GSFC NMDB online library, as directed by the TM.

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. References None.