SOW 142 eLib.pdf

Statement of Work Task: Flight Dynamics Facility Cloud Migration

Task Order: 142

Task Modification: 2

I. Summary of Changes in this Task Modification

• Extends Period of Performance until October 31, 2024 for Contract Year 5

II. Summary of Work This statement-of-work describes the cloud migration requirements for the Flight Dynamics Facility (FDF), in support of the Navigation and Mission Design Branch (NMDB).

As detailed below, the contractor shall provide support for the build-out and migration of the FDF infrastructure into the Cloud, in coordination with Goddard’s Mission Cloud Program (MCP).

The contractor shall accept direction from the FDF Operations Director, the FDF Deputy Operations Director, and/or the Task Monitor (TM) in bi-weekly meetings, ad-hoc discussions, or other methods as necessary. Task personnel are expected to be proactive in reporting project status, risks, and assessments to the appropriate parties and to prepare and support project reviews as needed or requested. Costs associated with the project shall be tracked in detail by each skillset and/or team.

As this Task represents strategic investment in FDF’s ability to support, there are times in which staff are reallocated to critical mission operations and this task is thus not prioritized. The contractor shall report and obtain permission for variations of the project schedule from the Task Monitor, the FDF Operations Director, or their Deputy, as required.

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

IV. Task Description The work on this task shall be broken into two primary areas: Robotics Navigation (known as “Navigation Operations”), and Human Spaceflight & Launch Vehicle Operations (known as “Flight Operations”) and work shall be directed into each area as resources permit.

Each area will include the following work items:

• Support development and exploration of Mission Cloud Program (MCP) Cloud capability, as specified by the TM

• Explore, prototype, test and start implementing a Cloud-based solution for the software development environment such that a refresh of the current development environment is not necessary

• Explore, prototype, test and start transition of operational support to MCP-Supported cloud environment.

• Follow the FDF Facility Review Boards (FRB) process for any operational deployment.

• Costs for official certifications shall be discussed with the TM for each instance and approved as needed.

• Track direct cloud costs by different expenditure category and present such data, including estimates at completion, to the TM at the bi-weekly task meeting.

• Present Cloud Design Reviews which will include:

o Requirements Review o Action Items Resolutions Reports o Trade Study Results o Overall Progress o Official Documentation Status o Design Results o Operations Concepts o Costs Projections o Schedule o Risks

• Prior to any operational promotion, at a minimum, the following processes, procedures, and training specified in the Cloud Design Reviews shall be updated:

o Sustainment team materials:

Deployment of the Cloud infrastructure Monitoring of the infrastructure Training to provide maintenance of the entire system Security updates required by the MCP Testing of the infrastructure Operations procedures Could SA Certification User/New User management o Software team materials:

Updating micro-services Deployment of software infrastructure Jenkins pipeline maintenance SW Cloud Certification User/New User management o Operations team materials:

Operations analyst certification Bug creation management

Automated regression testing Operations procedures

V. Deliverable Items and Schedules The Task deliverable items, and schedule are provided in Table 1.

Deliverable Schedule

Task Status Report Monthly

Cloud Design Review Quarterly (At the direction of TM’s)

Analysis reports As required

Test Reports Test completion + 1 week

Trip Reports 2 weeks after return

Table 1. Deliverable Items and Schedule

Management Approach

a. Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.

b. Configuration Management

Systems and documents will be covered under the FDF 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 equipment 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.

VI. Performance Metrics

Performance of the task will be based on timeliness and completeness of deliverables. The work performed for this task will be evaluated by the TM based on the technical merit. Technical evaluation of the task performed is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.

VII. Government Furnished Facilities, Equipment, Software and Other Resources The Government will provide account and passwords to government-furnished equipment 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 The contractor shall provide support for 2 persons to travel to the AWS Conference “re; Invent” taking place 11/27/2023-12/1/2023 in Las Vegas, Nevada.

IX. Work Location This work shall be performed in a combination of on-site at the Goddard Space Flight Center, telework, or at the contractor’s facility, as based on work requirements and in accordance with NASA's work policy.

X. Reporting Requirements

The contractor shall report task status in person or via teleconference to the TM or designated alternate (e.g. FDF Deputy Operations Director) on a bi-weekly basis. Brief written analysis summaries, action item status, and/or status reports may be requested. The contractor shall provide a report of action item status on a monthly basis or at the direction of the TM, FDF Operations Director, Deputy Operations Director. Additional status meetings and reports may be requested as deemed necessary.

XI. Security Requirements This task shall comply with IT security requirements through coordination with the MCP Team, as the Cloud account is held under the MCP Security Plan. Any instances located outside of the MCP shall be covered under the Code 590 security plan for items on the Corporate Network, or the FDF’s System Security Plan if within the FDF’s IONet.

XII. 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).

XIII. References Not applicable.