SOW 103 eLib.pdf

Statement of Work Task: Flight Dynamics Software Development and Maintenance Task Order: 103 Task Modification: 7

I. Summary of Changes Since Last Modification

• Extends period of performance to October 31, 2024

• Removed deliverables that are no longer applicable to CY5

• Added language that directs the contractor to prioritize on-going maintenance efforts as required vs. desired due to budgetary constraints.

II. Summary of Work This statement of work (SOW) describes software development and maintenance services to support flight dynamics engineers and technology initiatives within the MESA Navigation & Mission Design Branch. Details of the work by subtask are provided below, and should be considered as a baseline. As work results are evaluated, work priorities may change.

This task shall be responsible for the development and maintenance of the Flight Dynamics software in support of the Flight Dynamics Facility (FDF) institutional space mission operations activities and maintenance of the NMDB R&D software tools, to ensure consistency with the broader aerospace community practices. The flight dynamics software supports the following activities: mission analysis, trajectory design and analysis and maneuver planning; navigation, orbit prediction and determination, and error analysis. Also, software used for planning products and application software.

This task is also responsible for the research, analysis, and engineering support necessary to provide solar flux and earth geomagnetic index prediction updates to the Flight Dynamics Facility, required to support accurate, long-term prediction of satellite orbits and orbit decay rates in low altitude orbits.

The related work items described in this SOW provide the NMDB with continued prediction of the monthly mean smoothed estimate of future solar radio flux and weighted planetary geomagnetic index, ap, with predictions for early, nominal, and late solar max timing as well as “plus two sigma”, and “minus two sigma” solar flux error bounds.

This task shall provide daily prime shift support, to develop and maintain all Flight Dynamics Facility (FDF) software. The staffing schedule shall provide for as needed for defined critical support periods such as launches and maneuvers. Coverage on the evening (swing) shift and midnight shift will be provided by request or in response to emergencies. The task shall interface directly with the spacecraft support and hardware tasks to ensure coordination of support services. Special/emergency support to be provided as required and approved by the Task Monitor (TM) or authorized NMDB personnel.

Under this task order, the contractor shall provide technical assistance on navigation-related CCSDS support as directed by the government technical representative. The contractors will need extensive analysis and operations experience in navigation-related areas including trajectory design, maneuver support, tracking data evaluation and use, and orbit determination.

The contractor shall have expertise in the use of GOTS and COTS tools for attitude determination and prediction, sensor analysis, tools to generate trajectory designs, perform orbit determination and prediction, as well as tools to generate tracking station acquisition data, simulated tracking data, and to process and evaluate tracking data.

In performance of this task order, the contractor shall show proof that adequate Nondisclosure Statements have been executed prior to the handling of any proprietary data.

Software processes followed under this task shall be compliant with the NPR 7150.2 standard.

III. Period of Performance The period of performance of this task is from November 1, 2023 to October 31, 2024.

IV. Task Description Specific service elements to be performed under the Flight Dynamics Software Development and Maintenance Task include, but are not limited to:

• Operational software maintenance

• Software created and maintained as part of FDF re-engineering circa 2010

• Software tools & flight dynamics models development & maintenance

• Configuration management of both operations & analysis software

• FDF Web applications

• Attend the task status meetings, FDF Review Board (FRB) meetings, project planning meetings, and all software reviews.

Software Support of Mission Operations

Under this subtask, the contractor shall provide support for Flight Dynamics Facility (FDF) Operations for both routine operations and critical operations such as launches and maneuvers.

Support to routine operations mainly include Incidence Response, where “incidents” will include troubleshooting of FDF software applications interfering with the FDF’s ability to produce customer deliverables for a current mission.

The contractor shall provide on-call support for operations on a 24x7 basis to respond to any software issue that may arise. The nature of the response will be dictated in FDF Local Operating Procedures (LOP). In addition, when requested by the FDF operations teams, the contractor shall provide on-console support.

Items to be done

• Provide point of contact for Mission Support prior to FDF Review Board (FRB) review.

• Provide on-call roster for upcoming month on OmEGa, or equivalent.

• Report Missions supported in monthly report.

• Maintain a log of incidents in OmEGa.

Software Maintenance (Bug Fixes, Non-Critical/Urgent)

Under this subtask, the contractor shall provide the support necessary to develop, maintain and enhance the suite of flight dynamics mission analysis, trajectory design and analysis, and maneuver planning software tools and databases, consistent with the Software Maintenance Plan. This software is Government Furnished Information (GFI).

Items to be done

• Change requests for software processes, efforts and development shall be managed by the contractor team and presented for incorporation into a government-approved prioritized list of efforts along with analysis of the impacts and recommendations for implementation.

• The contractor shall develop software updates, upgrades and new applications, per the government-approved prioritized list of software efforts.

• The task shall comply with IT security requirements as documented in the FDF IT security plan for all systems located in the FDF.

• Solar Flux & Earth Geomagnetic Index Predictions. The contractor shall incorporate physical phenomena of the sun and known characteristics of solar activity to predict the mean solar flux. Updates shall be provided every six months of the Schatten mean solar flux prediction files. The contractor shall maintain and update the documented Schatten prediction procedures to generate the solar flux data and ensure backup personnel are capable of producing the Schatten predictions.

• The contractor shall maintain web applications/presence for the FDF, including software supporting the informational web site (fdf.gsfc.nasa.gov) and other web presences.

Delivery Dates

• Shall provide a prioritized high-level list of efforts for government approval. This may be delivered in conjunction with the FDF 5-Year Plan (5YP) under Task 134.

• This prioritized list may be updated within 14 days of a request from the TM or FDF Director along with recommendations for implementation of any changes and analysis of the impacts.

• The solar flux prediction files shall be delivered every April and October.

o Solar Activity Forecast Report (Dr. Schatten source files, ASCII text) o Schatten Predicted Jacchia-Roberts Files (IEEE little-endian, PC)

New Requirements (Missions, Capabilities, etc.)

Under this subtask, the contractor shall identify the support requested and implement tools and/or updates to meet FDF customer missions, upgrades, new capabilities, etc. This support is defined in the requirements levied on and agreed to by the FDF in support agreements with each of new missions and may be in the form of analysis, system architecture and design, and implementation.

Risks/Issues Mitigation

Under this subtask, the contractor shall support the prioritized mitigation of risks that pose a likely impact to the FDF operations or resources.

Items to be done (in order of priority)

• Single Point of Failure for major database design work

• Dependency on Fortran applications

• Any other Risks/Issues being tracked on the open list on OmEGa that are mission critical.

Enhancements

Under this subtask, the contractor shall perform enhancements to improve the FDF software tools, architecture and processes for generating FDF products and interacting with FDF customers.

Examples include but not limited to:

• Interface development with strategic NASA partners who are undergoing upgrades (e.g. ACCESS, NSN)

• Raptor, Fox, and Sentinel development in order to complete the modernization of all flight dynamics front end tools.

o Prioritization of work items will be assessed for each tool at every development cycle in order to determine what work is truly required to meet FDF strategic initiatives and provide required service to customers.

o The prioritized listed will be presented to the TM at each tag-up and made available upon request.

Strategic Directives

Under this subtask, the contractor shall be responsible for developing strategies, draft plans and begin to implement portions of the FDF Strategic Plan approved by the Task Monitor and/or FDF Director. This subtask serves to develop the implementation plan, but not to implement the plans, which would fall under enhancements.

Other strategic directives can be coordinated with and approved by the TM.

Training

Training is essential for software developers to maintain their skills with NASA GSFC tools and changing methodologies. This subtask allows the contractor team to maintain its skills by various methods such as courses taught by a teacher, self-learning, and training by other FDF personnel.

The contractor shall:

• Develop a training plan for software developers to learn and maintain their understanding of how to troubleshoot FDF software in operations during mission support activities.

• Research training opportunities for User Interface (UX) development and present a plan of action to the TM for consideration.

Configuration Management

The contractor shall be responsible for configuration management of all FDF operations and analysis software. Systems shall be covered under the FDF Configuration Management Plan.

The contractor shall maintain a current inventory of institutional software, maintain a current Software Maintenance Plan, maintain a current Risk Management and Best Practices Plan, and support the gathering of performance metrics.

The software inventory shall include information identifying the Configured Item (CI) name and version number. Source code for CIs on the inventory list shall be stored in a Configuration Management (CM) archive using CM software such as GIT. The inventory shall be made available online to NMDB members.

In addition to the above, the following items are to be done:

• Analyze and provide recommendations for implementing Accreditation & Authorization (A&A) Audit finding dispositions. These efforts shall be incorporated into the prioritized software efforts for government approval.

• Create and maintain a catalog of tools created across the NMDB to encourage collaboration and reuse. Recommend a process for development of future tools.

Delivery Dates:

The contractor shall provide the following updated documentation and routine reports.

Deliverable Items Delivery Date Inventory of NMDB & FDF software tools First week of April 2024

First week of October 2024 Performance Metrics records Within 30 days of request Status Report Monthly

V. Deliverable Items and Schedules Deliverable Schedule

Provide Software point of contact for Mission Support

Applicable FRB

Provide on-call roster for upcoming month 30 days prior

Report Missions supported Monthly Report

Maintain an incidents log realtime on OmEGa

Prioritized list of FDF Software efforts as needed

Updates to the Prioritized list of FDF Software efforts, along with recommendations for implementation of any changes and analysis of the impacts

14 Days after request

Solar Activity Forecast Report (Dr. Schatten source files, ASCII text) Schatten Predicted Jacchia-Roberts Files (IEEE little-endian, PC)

End of April & Oct 2024

Inventory of NMDB & FDF Software Tools First week of April 2024

First week of Oct. 2024

Monthly Status Report Monthly

VI. 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 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 The TM shall develop additional detailed performance metrics that shall reflect the contractor’s performance in meeting research analysis, specific mission requirements, deliverables and delivery schedule, and the contractor’s cost. Technical evaluation of the task performance is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.

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 Some travel is required for this SOW when papers are being presented and to attend conferences related to flight dynamics and related flight and software/hardware/ground and flight systems technologies. In the event that the need for travel does arise, this task order will be modified accordingly.

X. 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, based on work requirements and in accordance with NASA’s work policy.

XI. Reporting Requirements The contractor shall report status in person or via teleconference to the TM or designated alternates on a bi-weekly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. 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 directly 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. 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