SOW 121 eLib.pdf

Statement of Work Task: JPSS Ground Attitude Support Task Order: 121 Task Modification: 4

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 121 thru October 31, 2024.

II. Summary of Work The work under this task is to provide technical support for the development, testing, and operation of the Joint Polar Satellite System (JPSS) Attitude Ground System (AGS). The JPSS AGS is provided to the JPSS project as a Government-Off-The-Shelf (GOTS) component of the multi-mission JPSS Common Ground System (CGS). This task will support the J1, J2, J3, and the Suomi National Polar-orbiting Partnership (S-NPP) missions under the JPSS project, within the JPSS CGS architecture. The task is designed to get the appropriate support from the contractor to help the task monitor (TM) define, develop, and document the requirements, architecture, and software design specifications, continue system development, support testing, perform operations planning, support Launch and Early Orbit (L&EO) operations thru end of commissioning phase prior to handoff to NOAA operations personnel, and to support sustaining engineering during normal operations.

The JPSS 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 sustaining engineering support for J1, J2 and S-NPP AGS, and AGS requirements generation, system development, testing, operational planning. The support will include launch and early orbit support through commissioning for the J2 mission, and AGS requirements generation, system design, software development, and operational planning for the J3 mission. The scope of work will include all interfaces, as necessary, with other JPSS project elements and subsystems. Development and testing of a fully functional software system, including definition of the generic MTASS software modules to meet the JPSS requirements and modifications to the existing MTASS software suitable for the S-NPP, J1, J2, J3 missions, as well as other utilities developed in MATLAB to meet the JPSS ground attitude support requirements will be provided by task personnel with AGS software suitable for implementation on the JPSS Mission Operations Center (MOC) computer systems.

The overall development and management of the AGS is the primary responsibility of the Attitude Control Systems Engineering Branch (ACSEB) at NASA Goddard Space Flight Center.

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: AGS Software Design, Development, and Testing

This subtask will specifically concentrate on the requirements generation and system design, design, coding, and testing of AGS software functionalities to support J1, J2, J3, and S-NPP missions. It will also be the mechanism for preparation and delivery of the AGS software releases compliant with the functional and performance requirements identified to support these JPSS missions, as well as project’s software quality assurance (SQA) requirements and NASA software engineering requirements specified in the NASA Procedural Requirements (NPR)

7150.2. All acceptance testing, including documentation of test results, shall be performed at the factory prior to delivery of major software releases. Regression testing shall be performed for all patches or incremental releases that will ensure updated software items have not adversely affected required functionality of the prior AGS software release. Additional support should be provided to the project during ground system tests that include the AGS in the JPSS CGS testing and operational environments.

i. During the previous task POP under the FDSS II contract, the contractor delivered Release 7.0 of the AGS software. This software release is fully functional post J2 launch release, including the necessary components to support J1, J2, and S-NPP commissioning phase and normal operations.

During this POP, the contractor shall, 1) Complete development and testing of an initial AGS release for J3 mission (AGS Release 8.0) 2) continue development of AGSS requirements and specifications for the J3 mission.

Implementation of AGS functionalities to support activities for J1, J2, J3, or S- NPP outside of these planned releases, necessary to meet the JPSS AGS requirements, shall be discussed with and approved by, the TM and JPSS Project. These may include AGS changes to support any new telemetry data interface formatting, as imposed and implemented by the new ground system contractor. AGS Release 8 is the initial J3 release, and thus is considered a major release.

ii. Comprehensive factory acceptance testing (FAT) is required for all major AGS software releases. Patches releases shall undergo only regression testing to ensure the quality of the release.

iii. The contractor shall provide post AGS software release installation, integration, testing, and support for all ground project required testing.

iv. As part of NPR 7150.2 compliance, or as requested by the Technical Monitor (TM), the contractor shall hold software reviews and/or walkthroughs for updates to the JPSS AGS software and/or configuration files included in all AGS releases.

v. The contractor shall provide all the documentation associated with each AGS software release. This documentation includes, but it is not limited to, the

FAT test plan, procedures and test results, the User’s Guide, the Version Description Document (VDD), and viewgraphs for reviews of the AGS software.

b. Subtask 2: Operational Support

Operational support under this subtask entails operational planning, mission rehearsal planning and participation, documentation of AGS operational procedures, AGS training, AGS operations support from L&EO thru commissioning phase, and AGS sustaining engineering support. The contractor shall work with the TM to provide the operational support to the JPSS project for J1, J2, J3 and S-NPP missions.

i. The contractor shall work with the TM and project personnel to provide operational planning and to support any mission simulations or ground readiness tests for J3 mission.

ii. The contractor shall provide training of the AGS team, and/or NOAA FOT necessary to support all AGS operations for J1, J2, J3, S-NPP missions.

iii. The contractor shall develop, document, and maintain AGS procedures in mission-specific operations handbooks for conducting all required AGS functions for each JPSS mission (i.e. for J1, J2, J3 and S-NPP).

iv. The contractor shall provide AGS sustaining engineering support after handover to NOAA operations team for J1, J2, and S-NPP missions. This work will include consultation with NOAA operations team on AGS related matters, AGS trending, AGS software maintenance (i.e. enhancements and bug fixes), and attitude-related anomaly resolution.

v. The contractor shall, as part of AGS sustaining engineering support for J1 and J2, assist JPSS project personnel to deploy, integrate, checkout, initiate operation, and sustain the AGS trending automation functionality for J1 and J2.

c. Subtask 3: Documentation, Reviews, Task Meetings, and Reporting

This subtask focuses on all documentation and reviews required by JPSS project that are not part of the other subtasks. Documentation for each of the AGS software releases, including for algorithm reviews and code walkthroughs, and operational procedures, etc., will not be included in this subtask. Task personal shall perform the following activities during the POP:

i. Provide comments or update the AGS Interface Design Document (ICD) for all external and internal interfaces identified in the JPSS CGS to AGS Interface Requirement Document (IRD).

ii. Develop or review any type of required documentation related to the JPSS AGS or any other documentation relevant to the overall Ground System, as requested by the TM or their delegated representatives.

iii. Participate in meetings that require the presence or attendance of the AGS team as scheduled by the JPSS Project or requested by the TM.

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 specified above in Section IV, Task Description, and to provide the deliverables on schedule and budget.

b. Configuration Management

Configuration Management (CM) will be covered in the JPSS AGS Software Development and Test, CM, and Quality Assurance (QA) Plan. This plan consists of the MTASS Software Development, Management and Assurance (DMA) plan with JPSS mission specific appendixes. These appendixes shall address NPR 7150.2 compliance, security requirement compliance, and other mission software specific related information. The entire AGS software and all the documents mentioned in the previous sections of this SOW will adhere to the internal AGS plan, as well as any other JPSS Ground System Configuration Management Plans as dictated by the customer and task monitor.

c. Facilities

Appropriate IT devices to support the analyses and development of specifications and reports 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 progress monitoring and reporting, as well as performance metrics. The contractor shall identify issues well in advance of negative consequences, and shall recommend and implement corrective actions with concurrence 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 Local travel is expected during this performance period between contractor’s facility and NASA Goddard Space Flight Center in Greenbelt, MD, and NOAA Satellite Operations Facility

(NSOF) in Suitland, MD, and Raytheon Facility at Riverdale, Md. Non-local travel is not foreseen during this performance period. In addition, the technical representative may specify travel for presentation of professional papers or other technical meetings deemed to be of broad enough interest to the aerospace community. In the event new travel not specified in this SOW is required, a mod will be provided.

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, as well as the NOAA Satellite Operations Facility (NSOF) in Suitland, MD, and Raytheon Facility at Riverdale, Md.

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 and to the TM and members of the JPSS project, as directed by 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 sustaining engineering support, the Project’s security plan, or the contractor sustaining engineering support depending on system location. Specifically, the AGS shall comply with the IT security requirements deemed to be applicable to the system from the JPSS Common Ground System (CGS) IT requirements.

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

a. JPSS Software Development, Management and Assurance (SDMA) plan with mission-specific annex for JPSS. This document will also be referred to as the JPSS AGS Software Development and Test, Configuration Management (CM), and Quality Assurance (QA) Plan.

b. JPSS AGS Level 3 Requirements, JPSS MIS document number 474-00585.

c. JPSS AGS Level 4 Requirements, JPSS MIS document number 474-00549.

d. JPSS CGS to AGS Interface Requirement Document (IRD), JPSS MIS document number 474-00316.

e. JPSS CGS to AGS Interface Control Document (ICD), JPSS MIS document number 474- 00428-B0200.

f. JPSS Ground System Concept of Operations, JPSS MIS document number 474-00054.

g. JPSS AGS Security Compliance Matrix, JPSS MIS document number 474-00586.

h. JPSS AGS NPR 7150.2 Compliance Matrix provided by the JPSS project.