SOW 124 eLib.pdf

Statement of Work Task: Roman Analysis Task Task Order: 124 Task Modification: 4

I. Summary of Changes in this Task Modification

This SOW reflects the work that shall be done for the Roman Flight Dynamics Project to Support Flight Dynamics Operations Area (FDOA) Release 2 and Phase C/D design and implementation. The work has been broken up into three Subtasks:

1) Subtask 1: Systems Engineering Task – Analysis

2) Subtask 2: Ground System Task – Flight Dynamics Operations Area (FDOA) Development and Documentation

3. Subtask 3: Support for Operations System Engineering

Subtask 1 will continue analysis to address Ops Con and contingency-type cases, as well as any additional analysis to support FDOA development.

Subtask 2 will be the FDOA software development task supporting FDOA Release 2.

Subtask 3 covers staffing directly supporting the Roman Systems Engineering Team in the area of 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 Roman Space Telescope (RST) Project, previously known as the Wide Field Infrared Survey Telescope (WFIRST). Roman is a telescope planning to orbit at Sun-Earth Libration Point 2 to perform wide-field imaging and surveys of the near infrared (NIR) sky. The current design of the mission makes use of an existing 2.4 meter telescope, which is the same size as the Hubble Space Telescope.

Roman is the top-ranked large space mission in the New Worlds, New Horizon Decadal Survey of Astronomy and Astrophysics.

This task is for Roman Flight Dynamics and Operations Systems Engineering support for Phase C/D design and implementation.

III. Period of Performance The period during which the work for these tasks shall be performed is between January 25, 2023 and May 31, 2024.

IV. Task Description

1. Subtask 1: Analysis

Task Summary: Subtask 1 will continue navigation and maneuver calibration analysis supporting the development of the Roman FDOA. Tasks will include analyses aimed at addressing any Ops Con questions, performing additional contingency analyses as needed, and documenting updated analyses in the Roman Navigation Plan. Continuation of the integration of the mission design tools and the OD analysis for the launch and early orbit phase of the mission. This will include re-running OD analyses for MCC1, MCC2, LOI, and SK planning with updated assumptions as needed in order to generate OD errors to be incorporated into the maneuver planning analysis scripts.

Costing Requirements: Work on this subtask will be charged only to the Flight Dynamics Systems Engineering WBS (131480.02.05)

Meeting Requirements: It is expected that members on this subtask will meet with the Task Monitor as needed (nominally once every two weeks) to provide updates to the analysis and supporting analysis documentation.

Staffing Requirements: This task shall be staffed by engineers with Navigation and Ops experience (preferably with a Libration Point mission), and Orbit Determination analysis experience using ODTK. Analysts working on this task will have experience doing navigation analysis that answers the questions of whether or not requirements are met, and should have experience tuning a sequential filter.

2. Subtask 2: Flight Dynamics Operations Area (FDOA) Development and Documentation

Task Summary: Subtask 2 is the task supporting software development and testing for FDOA Release 2. This task covers Raptor procedure development, Factory Acceptance Testing (FAT), User Acceptance Testing (UAT), and supporting documentation. The FDOA development will be integrated with the Raptor software development cycles.

The FDOA Release 2 development will be broken down into 4 interim releases. Software “sprints” will be one month long activities aligned with the Raptor project “sprints” with some subset of the work to be done for the interim release assigned to various team members. For each interim release, an informal demonstration of the functionality implemented will be performed. For the formal release, full regression testing and functional testing will be performed as well as requirements verification.

Systems and documents will be covered under the Roman 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 routine non-local travel for this SOW. However, if travel is necessary for current remote workers to support FAT/UAT testing this will be covered by the RST Flight Dynamics budget.

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 bi-weekly basis for Subtask 1, and on a weekly basis for Subtask 2. Reports shall include interim results, status of development activities, current and projected issues, and other action items. The Contractor shall comply with any and all additional requests for status meetings, reports, and reviews.

o Subtask 1: Analysis o Bi-weekly report status will be delivered via email or in person in bi-weekly meeting o Status can be in document or Power Point format o Analysis results and code will be saved to Confluence for reference o Subtask 2: Flight Dynamics Operational Area (FDOA) Development and Documentation o Weekly report status will be delivered via email or in person in weekly meeting o Status and meeting minutes will be captured on Confluence o Subtask 3: Operations Systems Engineering o Monthly report

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