SOW 118 eLib.pdf

Statement of Work Task: PACE Attitude Ground System Task Order: 118 Task Modification: 6

I. Summary of Changes in this Task Modification

This task modification specifies the work to be completed on FDSS-3 Task 118 thru October 31, 2024. It includes request for additional support during PACE Phase E.

II. Summary of Work The objective of this task is to provide technical support for the development of the Plankton, Aerosol, Cloud, ocean Ecosystem observatory (PACE) Attitude Ground System (AGS). The task is designed to get the appropriate support from the contractor to help the technical/task monitor ™ define, develop and document the requirements, architecture, and software design specifications, and operation of the system. The PACE AGS will utilize 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: real-time attitude determination system (RTADS) and the attitude determination system (ADS) for offline attitude work. The focus of this task performance period will be to support the TM in design and development of the overall PACE AGS, including interfaces with other PACE project elements and subsystems. Specific AGS work will include development and testing of a functional software system, including definition of the generic MTASS software modules to meet the PACE requirements and modifications to the existing MTASS software suitable for the PACE mission. The work performance will include development and testing of software modules for a post-launch AGSS delivery suitable for integration and deployment on the PACE Mission Operations Center (MOC) computer systems to support PACE operations during Phase E (AGS Release 3.0). The AGS launch-ready release (AGS Release 2.2.2.3) has been delivered to the MOC to support launch and early orbit (L&EO) operations. During this POP, the AGS Release 3.0 will be developed, including all post-launch AGSS patches used to support L&EO. It will be integrated, tested, and deployed to MOC as a fully-functional release. Any bug fixes and enhancements, as required by project personnel, will be incorporated into the post-launch AGS release (AGS Release 3.0), used to support normal operations after the end of the commissioning phase. The work during this period also includes mission operations planning, AGS training for the FOT, and support for execution of all AGS functions from launch though normal mission operations until the Flight Operations Team (FOT) can be fully trained to take over all necessary AGS functions for PACE. AGS team will also provide sustaining engineering during project phase E, starting April 2024.

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 .

III. Task Description

a. Subtask 1: Requirements, Design Definition, and Analysis

i. The task personnel shall assist the TM in refining the requirements, design specifications, test plan, and internal/external interfaces of the AGS as part of the PACE Ground System.

ii. Provide technical support to the TM in the detailed design development of the AGS. The support shall include definition of all generic AGS MTASS, as well as PACE mission-specific, modules and system architecture required to meet PACE AGS requirements. This technical support will help the TM properly allocate or map the AGS requirements to the generic and PACE mission-specific MTASS software modules.

iii. In consultation with the TM, the task personnel shall perform AGS analyses, as negotiated with TM, to support the PACE AGS development.

b. Subtask 2: System Development and Software Support

i. In consultation with the TM, task personnel shall configure and support the deployment and setup of the AGSS. This includes appropriate generic MTASS utilities, which when integrated with the PACE mission-specific utilities, will comprise a fully functional post-launch release of the PACE AGS software system to be delivered as “AGS Release 3.0”. This release will incorporate all patch and analysi files used to support L&EO, and incorporate all required PACE AGS functionality necessary to meet the all AGS requirements.

ii. In consultation with the TM, task personnel shall provide assistance in the overall AGS software design, which will include coding, analysis, and pertinent testing, of PACE mission-specific utilities of the MTASS required for both real-time and offline ground attitude work. The work under this task shall focus on the AGSS development items, as listed below:

1. RTADS data interface unit (DIU) and ADS telemetry processor (TP) functionalities of the MTASS for processing of real-time and offline/playback telemetry data from the PACE spacecraft, respectively.

2. RTADS utility to perform attitude determination and related attitude performance monitoring functions in real time using telemetry acquired through a real-time DIU. RTADS shall provide a set of real-time updated graphical and tabular data displays of attitude estimates, attitude residuals, and attitude sensor parameter data sufficient to facilitate rapid assessment of the PACE attitude system performance.

3. ADS ground-based attitude determination, validation, and trending utilities to perform validation of onboard PACE attitude solutions and related parameters using independently computed attitude solutions from available attitude sensor telemetry.

4. Slew planning utility, including attitude constraint checking utilities, slew plans, and slew commands required to produce all PACE AGS attitude products and support the planning and modeling of all PACE attitude commands and slews.

5. Attitude sensor calibration utilities to provide fully functional system for calibration of required PACE attitude sensors. This will include incorporation of a newly developed gyro calibration utility (GCAL).

6. Other software modifications for development of a functional AGS system necessary to meet PACE requirements.

iii. In consultation with the TM, task personnel shall provide unit testing of all PACE mission-specific utilities of the MTASS required for both real-time and offline ground attitude work as part of the AGSS. Each unit test will be documented in the manner agreed upon with the TM.

iv. In consultation with the TM, task personnel shall provide algorithm design documentation for new PACE mission-specific software items. Task personnel shall present this algorithm design documentation to the AGS team for review prior to completing the development of this item.

v. In consultation with the TM, after a particular PACE mission-specific software item development is complete, task personnel shall support Code Walkthroughs in adherence with PACE Ground System requirements, which will include review of unit testing.

vi. In consultation with the TM, as negotiated with PACE project personnel, task personnel shall begin work on any AGS software enhancements and/or bug fixes that may be identified during the PACE AGS development in this POP.

c. Subtask 3: System Testing, Delivery, and Operational Readiness Support

i. In consultation with the TM, task personnel shall define system scenario test plans and procedures for the fully functional AGS software system, in preparation for factory acceptance testing (FAT), MOC FAT, and MOC site acceptance testing (SAT) of the software for AGS Release 3.0.

ii. Task personnel shall perform testing of the AGSS to verify system requirements and functional performance as a part of the pre-release and also FAT of the AGS Release 3.0. Test plans and procedures for each release will be delivered to the TM per the delivery schedule in section V.

iii. The task personnel shall deliver a fully-functional and operational AGS systems (AGS Release 3.0) for integration with the MOC computer systems, per the delivery schedule in section V.

iv. In consultation with TM, task personnel shall support pre-delivery AGS testing for AGS Release 3.0. These tests shall fully verify all AGS Level 5 requirements where verification method has been designed as "test", or by "demonstration" as appropriate. Documentation of test results will be delivered to MOC computer systems per the delivery schedule in section V.

As part of this delivery a test matrix will be included that documents successful test verification and method for all AGS level 5 requirements.

v. In consultation with TM and PACE project personnel, task personnel shall support MOC FAT testing for AGS Release 3.0 on the MOC computer systems after delivery of each AGS Release, respectively. This support will include providing assistance for MOC testing to verify MOC AGS Level 4 requirements

vi. The task personnel shall deliver fully-functional and operational AGS system patch releases for integration with the MOC computer systems, as required and negotiated with the TM. These patch releases would include any bug fixes and enhancements found in testing or otherwise required by project personnel. They will not require formal FAT or associated test and AGS level 5 requirements verification documents.

vii. In consultation with the TM and PACE project personnel, task personnel shall support all AGS functions during MOC ground mission simulations 4 and 5, and launch rehearsals on the MOC computer systems, as required by PACE project (see Table of Milestones section V)

viii. In consultation with the TM, task personnel shall, with input from the TM and the PACE project personnel, support PACE AGS operations planning. The task personnel shall develop and compile a complete and comprehensive set of operational procedures for AGS Release 3.0 into an AGS Operational Handbook. The AGS Operational Handbook shall be delivered to the MOC computer systems per the delivery schedule in section V.

ix. In consultation with the TM, and in close coordination with the Flight Operations Team (FOT) and all pertinent members of the PACE engineering and science teams, shall support the planning and implementation of all S/C operational activities related the AGS requirements and functions from launch thru the end of the commissioning phase

x. In consultation with the TM and PACE project personnel, task personnel shall support and prepare AGS materials for the PACE Operational Readiness Review (ORR)

d. Subtask 4: Operational Support

Operational support under this subtask entails PACE operational planning and support pertinent to all AGS requirements and functions, including participation in operational working groups, documentation of AGS operational procedures, AGS training for AGS team and FOT, AGS operations support from L&EO thru normal mission operations, included also sustaining engineering support during Phase E.

i. The contractor shall support all AGS operations during launch and early orbit through normal mission phase operations, as appropriate to meet AGS requirements and functionality, for the PACE mission. Operational support of all AGS functions shall be provided by the AGS team until the FOT can be trained and ready to take over the AGS operations during Phase E

ii. Under consultation with TM, task personnel shall operate the AGS within the MOC to support successful PACE commissioning during LE&O from launch through the end of the commissioning phase. This support shall include:

1. Operation of AGS software elements, both real-time and off-line components, in support the PACE flight operations during L&EO through commissioning phase.

2. Generation and delivery of all AGS products. These products include slew planning and ATS command file generation, ACS sensor calibration, attitude validation and trending, OCI ST alignment, attitude and constraint predictions, and all other AGS products or special requests, as required by PACE project and negotiated with the TM, for AGS system data and/or assessments requested by TM and/or PACE project personnel during commissioning phase.

3. Analysis of AGS telemetry data, both real-time and off-line, to successfully characterize both nominal and off-nominal behavior of the PACE spacecraft attitude system.

iii. The contractor shall provide training of the FOT as necessary, for the FOT to fully support of all AGS operations during Phase E.

iv. Under consultation with TM, task personnel shall initiate AGS training for the FOT personnel on PACE in preparation for handover of all AGS functions to the FOT for mission operations support. This training shall capture and communicate all AGS lessons learned during the commissioning phase to the FOT prior to handover of AGS operations.

v. Under consultation with TM task personnel shall, with appropriate input from the TM and the PACE project personnel, began gathering artifacts and performing analysis to be included in a AGS Post Launch report providing a detailed account with relevant analyses of AGS functions during LE&O through the end of commissioning phase. The AGS Post Launch Report shall be delivered to the MOC computer systems per the delivery schedule in section V.

vi. The contractor shall develop, document, and maintain AGS procedures in mission-specific operations handbooks for conducting all required AGS functions for the PACE mission.

vii. The contractor shall provide AGS training to the AGS operators, as appropriate, during the commissioning and mission phases.

viii. The contractor shall begin AGS training of the FOT during the 2nd month of commissioning phase. This training will target sufficient detail for FOT to take over the routine operation of AGS during phase E.

ix. The contractor shall provide AGS sustaining engineering support to PACE during the commissioning phase and throughout phase E. This work will include providing consultation to the FOT for all AGS operations, AGS trending, AGS software maintenance (i.e. enhancements and bug fixes), and attitude-related anomaly resolution.

e. Subtask 5: Documentation, Reviews, Task Meetings and Reporting

i. The task personnel shall assist the TM in developing and reviewing any type of required documentation for the PACE AGS and overall Ground System.

The required documentation support for the AGS includes updates to Level 5 AGS requirements and related Level 4 MOC requirements, AGS design specification, Internal MOC ICD, AGS test plan and related sections within PACE ground system test plans, AGS test and operational procedures, etc.

Launch Date February 6, 2024 Launch Date

Commissioning Phase February 6, 2024 thru April6, 2024

Commissioning Phase.

Normal Mission Phase Starting on April 6, Phase E (normal mission)

V. 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 PACE 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.

VI. 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.

VII. 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.

VIII. Travel Local travel is expected during this performance period between contractor’s facility and NASA Goddard Space Flight Center in Greenbelt, MD.

IX. 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.

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

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.

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

XIII. References