SOW 115 eLib.pdf

Statement of Work Task: GOES Flight Dynamics Support Task Order: 115 Task Modification: 5

I. Summary of Changes in this Task Modification

This task modification has been initiated to extend the period of performance (POP) through Contract Year 5 (CY5).

II. Summary of Work This task is designed to provide Flight Dynamics support to the Geostationary Operational Environmental Satellite (GOES) Project for the pre-launch, Launch and Orbit Raising (LOR) and the Post Launch Testing (PLT) phases of the GOES-R series of spacecraft (GOES-R, -S, -T, & -U). Additionally, this task helps to coordinate of the FDF support of operational GOES spacecraft (GOES13-18). Support for this task may require non-disclosure agreements between Lockheed-Martin (GOES-R Flight Program contractor) & Harris (GOES-R Ground System contractor) and the parent companies of the task members. As of this task order modification, the GOES-U launch date is holding steady for April 30, 2024.

III. Period of Performance The period of performance for this task will be from 11/01/2023 through 10/31/2024.

IV. Task Description The Flight Dynamics support for the GOES-R has reverted back to the model for the GOES-I/M series where the maneuver planning for the launch and orbit raising (LOR) period is the responsibility of NASA team (GSFC Code 595) and hence, this task. All task personnel supporting the GOES-R series of spacecraft will comply with non-disclosure agreements between Lockheed-Martin (GOES-R Flight Program contractor) & Harris (GOES-R Ground System contractor) and the parent companies of the task members. Current planning assumes the GOES-U launch date of NET April 30, 2024.

The task support includes, but is not limited to, the following.

Meeting Support

Technical meetings of the GOES Flight Dynamics Team will be biweekly.

• The Task will provide a written monthly report assessing technical, staffing, and budget statuses

• Participate in LOR Working Group meetings with GOES project, Lockheed Martin (GOES-R spacecraft contractor), and Project MOST personnel. These are likely to begin as bi-weekly meetings beginning in this POP.

• Task personnel will be asked to participate in meetings related to operations planning and simulations called by the GOES Project and/or the GOES Mission Operations Support Team (MOST). These meetings will begin roughly 1-2 months before the first mission rehearsal.

• The task will also help to coordinate support from the Flight Dynamics Facility (FDF) for operational GOES spacecraft (GOES-13-18) and for GOES-U flight readiness.

• Provide support for other Project reviews as needed.

Documentation Support

• Continue to support the update of the CAOIA (Conjunction Assessment and Operations Interface Agreement) document between the GOES-U project and the NASA CARA team. A draft has been received and we will work to finalize it before launch

• Continue to support the update of the GOES-U MOU as necessary.

• There is no planned update of the GOES-R Detailed Mission Requirements (DMR) document

FDS Development

• The operating system in the NSOF LCR (NOAA Satellite Operations Facility Launch Control Room) has been updated to Red Hat Enterprise Linux 7.4. GFDS updates will be compliant with this version of Linux.

• GFDS updates will be compliant with FreeFlyer 7.4

• Consistent with current activities, complete and deliver Build 12.1 of the GFDS on

January 15, 2024.

• Support verification of installment at NSOF by February 16, 2024, or within 2 weeks of installation.

• Continue to monitor the development status of subsequent FreeFlyer development on Linux operating system (e.g. inclusion of full GUI and graphics output) and adjust GFDS scripts and procedures accordingly.

• Support activities related to Continuity of Operations (COOP) whereby launch support would transition from the NSOF LCR to the backup Mission Operations Center at Wallops, VA or potentially the backup facility at Fairmont, WV.

• Support installations of FDS at NSOF and backup location.

• Document test plans and results for all updates.

• Maintain Matlab licenses (i.e. costing) needed for mission rehearsals and operations. This includes two network licenses on the Operations Environment (OE), 1 network license on the Integration and Test Environment (ITE), and 1 node-locked license at Wallops for COOP.

• FreeFlyer license renewals are being handled along with the Code 595 branch bulk renewals and are not to be costed on this task.

• Maintain FDS system under configuration control.

• Maintain listing of potential changes to FDS in the event that another update is needed prior to launch.

• Development regarding the future GOES-U Flight Dynamics ground system support will accommodate any changes in the FDF architecture.

Simulation Support

• Update Operations Procedures based on GFDS Build 12.1. Deliver updated version of Operations Handbook by February 16, 2024.

• Continue internal training of operations procedures to be prepared for launch operations starting NET April 30, 2024.

• Simulation support will include preparation of mission planning products prior to the simulation (roughly Rehearsal minus 4-5 weeks), weekly support of 1-day dry runs of mission rehearsal activities, and on-console support during the simulation where procedures are executed, and post-simulation de-briefing. Product updates may be needed as requested by the GOES Mission Operations Support Team

(MOST).

• Use the following Mission Rehearsal (MR) dates for planning. These dates are based on the current launch date of April 30, 2024. There will be dry runs of Mission Rehearsal activities prior to each event. These dry runs can be used for additional training.

MR3: Week of December 04, 2023 MR4: Week of February 26, 2024 MR5: Week of March 25, 2024

Analysis Support

• Provide mission analysis support for GOES-U in the areas of Launch Window Analysis Review, Validation of GEO Transfer Orbit, Nominal Ascent Planning, Contingency Ascent Planning, and End of Mission Planning.

• Provide verification of orbit raising plan based on orbit state received from SpaceX and NASA’s Launch Services Project (LSP). Data from PGAA-2 (Performance and Guidance Accuracy Analysis). Data is expected around March 2023. Provide analysis within 2 weeks.

• Provide evaluation of launch sigma cases (± 1, 2, 3 σ) at L-1 month by developing alternate ascent plans based on different launch vehicle dispersion errors. Deliver report by L – 5 weeks.

• Provide evaluation of Station Acquisition plan to compensate for errors in the REA Fuel Management maneuvers, the HBT bubble clearing maneuvers, and potential missed REA/HBT drift stop maneuvers. Deliver report by L-3 weeks.

• If requested, provide orbit determination analysis support for GOES-U based on lessons learned from GOES-T.

Launch Support

• There is launch support during this period. Operations will cover roughly 4 weeks based on the nominal 14-burn orbit raising sequence. Ops personnel need to maintain their access credentials for support at NSOF. Personnel will follow all NSOF (NOAA Satellite Operations Facility) requirements as they relate to COVID- 19 virus protocols.

• Provide draft of staffing schedule at L-2 months and final at L-2 weeks. Launch support will be similar to GOES-T support with 3, 8-hour shifts (with overlap) providing continuous 24 x 7 support throughout LOR. Shifts will be released when detailed planning investigates opportunities for rest.

• Provide draft of product delivery schedule at L-2 months and final at L-2 weeks

• Deliver post-launch archive of products/data at end of LOR (Launch and Orbit

Raising) + 3 months

In-Orbit Support

• There may be infrequent support of the on-orbit, legacy spacecraft – GOES-13, - 14, & -15 and GOES-16, -17, & 18 (-R, -S, & -T). This will involve coordination of FDF resources for orbit determination activities in support of normal operations at NOAA.

GOES-R Series Archive

• Develop archive of GOES-R series data by compiling data for each satellite (GOES- R, -S, -T, & -U).

• The data will include for each satellite – pre-launch memos, final operations procedures document, GFDS build used for operations, products (inputs/outputs) generated during LOR support, review materials, etc.

• Archive will be delivered by October 18, 2024, or L+6 months, whichever is later.

V. Deliverable Items and Schedules At a minimum, the contractor shall deliver the items specified below.

Deliverable Due Date

Report of all materials reviewed for GOES Project including, but not limited to, MOU, test plans, etc.

Within 2 weeks of event

Mission Analysis Reports (as needed) As negotiated with TM

Flight Dynamics Systems and documents will be reviewed and signed-off by GOES Project Management

Facilities

Appropriate IT devices to support the analyses, testing, 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.

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.

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.

VII. Government Furnished Facilities, Equipment, Software and Other Resources EXAMPLE: 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.

VIII. Travel Include budget for non-local travel to/from NOAA’s NSOF facility in Suitland, MD for meetings, mission simulations, and launch support.

IX. Work Location This work shall be performed at the contractor’s facility, in GSFC’s Flight Dynamics Facility (Building 28), and at the NOAA Satellite Operations Facility (NSOF) in Suitland, MD.

X. 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 testing 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.

XI. 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. Any task members required to support at NOAA’s NSOF facility (in Suitland, MD) will be required to be badged (including NACI Clearance) under NOAA guidelines. These task members must also comply with IT security guidelines set by

NOAA.

XII. Rights REQUIRED: The Contractor shall adhere to the FAR 52.227-17 RIGHTS IN DATA – Special Works (2007).

XIII. References

1. “GOES-R Series Memorandum of Understanding (MOU) between GSFC Flight

Dynamics (FD) and the GOES-R Flight Project”, March, 2018, 417-R-MOU-0266.

2. “Conjunction Assessment Risk Analysis (CARA) to Geostationary Operational

Environmental Satellite-T (GOES-T) Mission Conjunction Assessment Operations Implementation Agreement (CAOIA) Interface Control Document”, 417-R-ICD- 0428.

3. “Flight Dynamics Support Services-II Operational Agreement between the Navigation and Mission Design Branch (NMDB) Flight Dynamics Facility (FDF) at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) and the Satellite Operations Control Center (SOCC) of the National Oceanic and Atmospheric Administration (NOAA) National Environmental Satellite Data and Information Services (NESDIS) in providing Acquisition Data Support for the Near-Earth Network (NEN) and the United Space Network (USN) Network and Radiometric Orbit Determination Support for GOES-(13-15) and GOES-(16-19)”, March 06, 2018, 417-R-OA-0389