SOW 117 eLib.pdf

Statement of Work Task: Attitude Ground System Sustaining Engineering Task Order: 117 Task Modification: 5

I. Summary of Changes in this Task Modification

This task modification extends the Period of Performance (POP) and specifies the work to be completed on FDSS-3 Task 117 thru October 31, 2024.

II. Summary of Work The objective of this task is to provide sustaining engineering support for the operation of the Attitude Ground System (AGS) for each project listed in separate subtasks below. These include Subtask 1: Global Precipitation Measurement (GPM) support, and Subtask 2: Deep Space Climate Observatory (DSCOVR) support. The AGS utilizes a customized version of the Multi-Mission Three Axis Stabilized Spacecraft System (MTASS) Government off-the-shelf (GOTS) software. This software is referred to as the Attitude Ground System Software (AGSS) and is typically made of two operational systems: 1) Real-Time Attitude Determination System (RTADS) and, 2) Attitude Determination System (ADS) for offline attitude work. The focus of this task is for the contractor to provide AGS support in the following areas, 1) Sustaining engineering and maintenance of the AGSS, to include analysis support and implementations of any additional required functionality and/or fixing problems identified in system testing or operations, 2) Maintain a fully functional and operational AGS software system, 3) Testing support for future MOC releases.

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

The period during which the work for this task modification shall be performed is from November 1, 2023 thru October 31, 2024.

IV. Task Description

a. Subtask 1: GPM Support

i. Under consultation with Technical Monitor (TM), as negotiated with GPM project personnel, task personnel shall provide sustaining engineering support of the operational GPM AGS by developing, testing, and deploying enhancements and/or bug fixes to operational Attitude Ground System Software (AGSS), as identified during the normal operations.

1. This effort will include software design, coding, analysis, and pertinent testing, of GPM mission-specific MTASS utilities required for both real-time and offline AGSS elements, in support of GPM project during normal mission operations.

2. Under consultation with TM, task personnel shall provide algorithm design documentation for any new GPM-specific software functionality. Task personnel shall present this algorithm design documentation to the TM for review prior to completing the development of this item.

3. Under consultation with TM, task personnel shall perform unit testing of any newly developed GPM mission-specific AGS utility required for either the real-time and offline components in a manner agreed upon with the TM, as necessary to ensure AGS will meet GPM requirements.

4. Under consultation with TM, task personnel shall support pre-installation acceptance and regression testing of any modification developed for the operational AGSS, prior to deployment on the operational systems. This testing will be conducted at the vendor site, the GPM ground systems development lab, or emergency mission operations center (eMOC), as appropriate, with guidance from GPM project personnel.

5. Under consultation and negotiation with TM, task personnel shall issue patch releases to the mission operations center (MOC) and TM for all modifications developed for deployment on the operational AGS systems.

6. Under consultation with TM, task personnel shall provide any additional AGS training for operation of AGSS, as necessary for Flight Operations Team (FOT) personnel to maintain competency on GPM AGS operation, as it pertains to software modifications performed by task personnel. This work will also include consultation with FOT in updates necessary to AGS operational procedures as it pertains to any modifications made by task personnel to operational AGSS.

ii. As needed, as negotiated with TM, task personnel shall provide analysis and operational support for AGS-related anomaly resolution to the GPM project.

iii. Under consultation with TM, task personnel shall review and analyze the AGS trending data and reports on a regular basis to monitor performance of Onboard Computer (OBC) attitude determination and sensor residuals. The review interval will nominally be no more often than biweekly. Any anomalies identified that require further investigation will be reported to TM in a timely manner.

1. Monthly trending reports will be sent to TM via email, along with a brief description of task personnel's analysis of the data, per schedule included in section V. Deliverable Items and Schedules.

iv. Provide a brief report summarizing the cost, schedule, and technical activities during the calendar month, submitted by the 15th day of the succeeding month.

v. Provide the documentation, reports, reviews, and analyses on topics and with the delivery dates as negotiated with the TM or included in section V.

Deliverable Items and Schedules.

b. Subtask 2: DSCOVR Support

i. Under consultation with Technical Monitor (TM), as negotiated with DSCOVR project personnel, task personnel shall provide sustaining engineering support of the operational DSCOVR AGS by developing, testing, and deploying enhancements and/or bug fixes to operational Attitude Ground System Software (AGSS), as identified during the normal operations.

1. This effort will include software design, coding, analysis, and pertinent testing, of DSCOVR mission-specific MTASS utilities required for both real-time and offline AGSS elements, in support of DSCOVR project during normal mission operations.

2. Under consultation with TM, task personnel shall provide algorithm design documentation for any new DSCOVR-specific software functionality. Task personnel shall present this algorithm design documentation to the TM for review prior to completing the development of this item.

3. Under consultation with TM, task personnel shall perform unit testing of any newly developed DSCOVR mission-specific AGSS utility required for either the real-time and offline components in a manner agreed upon with the TM, as necessary to ensure AGS will meet DSCOVR requirements.

4. Under consultation with TM, task personnel shall support pre-installation acceptance and regression testing of any modification developed for the operational AGSS, prior to deployment on the operational systems. This testing will be conducted at the vendor site, of a DSCOVR ground systems development lab), as appropriate, with guidance from DSCOVR project personnel.

5. Under consultation and negotiation with TM, task personnel shall issue AGSS patch releases to the mission operations center (MOC) and TM for all modifications developed for deployment on the operational AGSS systems.

6. Under consultation with TM, task personnel shall provide any additional AGS training for operation of AGSS, as necessary for NOAA Mission Engineering Team (MET) personnel to maintain competency on DSCOVR AGS operation. This work will also include consultation with MET in updates necessary to AGS operational procedures as it pertains to any modifications made by task personnel to operational

AGSS.

ii. As needed, as negotiated with TM, task personnel shall provide analysis and operational support for AGS-related performance and/or anomaly resolution to the DSCOVR project.

iii. Under consultation with TM, task personnel shall review and analyze the AGS trending data and reports on a regular basis to monitor performance of Onboard Computer (OBC) attitude determination and sensor residuals. The review interval will nominally be no more often than monthly. Any anomalies identified that require further investigation will be reported to TM in a timely manner.

1. Monthly trending reports will be sent to TM via email, along with a brief description of task personnel's analysis of the data, per schedule included in section V. Deliverable Items and Schedules.

AGSS Patch Releases As requested and negotiated with TM.

AGSS software enhancements incorporated into a patch release

Task Status Reports Monthly, by the 15th day of the succeeding month

Task Status Reports (technical, cost & schedule) verification matrix

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

AGS software and all the required documents mentioned in the previous sections of this SOW will be covered under the FDF, Ground Attitude or Ground System Configuration Management Plans as dictated by the customer and TM.

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 work performed for this task will be evaluated by the Technical Monitor based on the technical merit. The TM’s evaluations will reflect the contractor’s performance in meeting specific mission requirements and/or analyses, deliverables and delivery schedule, and the contractor’s cost. Technical evaluation of the task performance is a subjective combination of, 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

There is no non-local travel for this SOW.

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

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 coordinated with the TM. Spending will be tracked at the subtask level. The contractor shall provide a separate 533 for each Subtask.

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 REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – general (FAR 52.227-14) Alternate II (2007 and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).

XIV. References