SOW 110 eLib.pdf

Statement of Work Task: Earth Observing System (EOS) Flight Dynamics

Support Task Order: 110 Task Modification: 6

I. Summary of Changes in this Task Modification

Task modification 6 of Task Order 110 on FDSS-III for CY5. Software and hardware support is being moved into this task as a new subtask.

II. Summary of Work The objective of this task is to provide the Earth Observing System (EOS) Flight Dynamics System (FDS) analysis required by the Earth Sciences Mission Operations (ESMO) Project in the EOS Operations Center (EOC), and the Backup EOC (BEOC) for routine and special flight dynamics operations planning and support. Requirements definition and acceptance testing of each delivery of the mission’s FDS are also required. In addition, the task will provide support for the EOS FDS hardware and software and the EOS Ops Center Information Interactive Display

Task work is divided into subtasks which shall provide the following:

• Subtask 1 - EOS Terra Flight Dynamics Analysis Support

• Subtask 2 - EOS Terra Routine Flight Dynamics Support

• Subtask 3 - TDRSS Onboard Navigation System (TONS) Analysis support for Terra

• Subtask 4 - EOS Aqua Flight Dynamics Analysis Support

• Subtask 5 - EOS Aqua Routine Flight Dynamics Support

• Subtask 6 - EOS Aura Flight Dynamics Analysis Support

• Subtask 7 - EOS Aura Routine Flight Dynamics Support

• Subtask 8 - Flight Dynamics System (FDS) Software Analysis Support

• Subtask 9 – EOS FDS Maintenance and System Administration

NOTE: This task does not include any EOS support provided from the Flight Dynamics Facility (FDF) in building 28.

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 List of meetings contractor is required to attend:

• ESMO Operations Activity

• Top 10 Meetings (Aqua/Aura/Terra)

• High-Interest Event Briefings (Aqua/Aura/Terra)

• Command Authorization Meeting (Aqua/Aura/Terra)

• Weekly Task 110 Status with Task Monitor

• Monthly FDSS-III ESMO Status

• FOT-FDS Working Group

• Maneuver Working Groups (Aqua/Aura/Terra)

• Decommissioning Working Groups (Aqua/Aura/Terra)

• FDS Software milestone reviews

• Bi-Weekly ESMO DRB

• Anomaly Meetings, when applicable

• Science Team or Instrument Team meetings, when requested by Mission Director

• Decommissioning Review (Aqua/Aura/Terra)

• ESMO Annual Review (if requested by ESMO)

• ESMO IT Security Compliance meetings, when applicable

In addition, Specific service elements to be performed under this task include, but are not limited to:

• Operational software maintenance

• Software tools & flight dynamics models upgrade & maintenance

• Configuration management of both operations & analysis software

Subtask 1: EOS Terra Flight Dynamics Analysis Support Task Scope: This subtask provides non-routine analysis and operations support for Terra. Support shall be performed during normal business hours (between 9:00 AM ET and 5:00 PM ET Monday through Friday) except in the event of a mission critical emergency, when off-hours support may be required on a temporary basis.

Technical Requirements: Specific analyses can include, but are not limited to:

• Requirements analysis

• Contingency analysis

• Implementation of routine attitude sensor validation, if prioritized by Mission Director

• Attitude sensor calibration, as needed

• Contingency/Anomaly support, as needed

• Critical operations support

• Simulation support

• Write and present technical paper(s) at aerospace conferences, if required.

• Consultation regarding star tracker performance and updated star catalog use will be provided, as necessary

• Configuration management for all spacecraft parameters, assumptions, and other setup parameters used in unique mission analyses and for periodic mission analysis updates (e.g. – lifetime analysis)

• End of mission planning and design decommissioning plans

Skill Requirements: FreeFlyer scripting, Matlab scripting, ability to present analyses to a wide audience.

Subtask 2: EOS Terra Routine Flight Dynamics Support Task Scope: The contractor shall provide routine operations support for the Terra Flight Dynamics Systems.

Technical Requirements: Specific support can include, but is not limited to:

• Routine daily/weekly/periodic product generation and delivery, including spacecraft computer loads and acquisition data, and other products required by the mission support personnel

• Lifetime studies

• Fuel budget/bookkeeping analysis

• Orbit parameter trending

• Attitude maneuver planning, as needed

• Contingency/Anomaly support, as needed

• Critical operations support, as needed

• Simulation support, as needed

• Oversight/quality assurance of routine product generation

• Documentation upkeep (ICDs, MOUs, SOPs)

• TONS carryout monitoring for Terra

• TGSS/SOS monthly validation to ensure operational status, when possible

• Attitude maneuver monitoring

• OBC attitude validation (monthly)

• Training of new FOT on-line engineers on the FDS

• Routine conjunction assessment support and risk mitigation maneuver (RMM) planning

• Configuration management for all spacecraft parameters, assumptions, and other setup parameters used in unique mission analyses and for periodic mission analysis updates (e.g. – lifetime analysis)

• Execution of decommissioning plans, including planning and calibration of perigee lowering maneuvers, and expending of all fuel

• Training of new Flight Dynamics analysts

Skill Requirements: FreeFlyer scripting, Matlab scripting, ability to present analyses and maneuver plans to a wide audience.

Subtask 3: Terra TDRSS Onboard Navigation System (TONS) Analysis Support Task Scope: This subtask provides analysis and supporting documentation for the TDRSS Onboard Navigation System (TONS) onboard the Terra spacecraft. The contractor shall be expected to provide timely support of unplanned high-priority actions as circumstances dictate. Support shall be performed during normal business hours (between 9:00 AM ET and 5:00 PM ET Monday through Friday) except in the event of a mission critical emergency, when off-hours support may be required on a temporary basis. This subtask also includes any testing effort required as part of any TGSS/Software Only Simulator (SOS) system upgrades and/or configuration changes.

The TDRS Ground Support System (TGSS) maximum date issue was resolved in FY16 by modifying the input files used and was available for the TONS recovery in FY16 using one of the EOC SUN workstations. Testing and certification of additional SUN workstations in the Backup EOC (BEOC) was completed in FY19. Testing and certification of the tertiary system for failover in the EOC and for contingency support will continue in FY24.

Technical Requirements: Specific analyses may include

• Developing set-ups and making runs on the Terra SOS for such items as a change in the solar flux model onboard the spacecraft, an upgrade in geopotential model, or changes to tuning parameters. Recommendations regarding updating the onboard software shall be made to the Terra Mission Director and FOT.

• Support and testing and maintenance of the TGSS/SOS primary, secondary, and tertiary machines.

• Analyze Harris-Priester (HP) density models on TGSS/SOS for a possible update of the HP density model on-board the Terra spacecraft.

Skill Requirements: Familiarity with SUN workstations and UNIX software from the 1990s, ability to present analyses to a wide audience.

Subtask 4: EOS Aqua Flight Dynamics Analysis Support Task Scope: This subtask provides non-routine analysis and operations support for Aqua. Support shall be performed during normal business hours (between 9:00 AM ET and 5:00 PM ET Monday through Friday) except in the event of a mission critical emergency, when off-hours support may be required on a temporary basis.

Technical Requirements: Specific analyses can include, but are not limited to:

• Requirements analysis

• Contingency analysis

• Attitude analysis, as needed

• Implementation of routine attitude sensor validation, if prioritized by Mission Director

• Attitude sensor calibration, as needed

• Contingency/Anomaly support, as needed

• Critical operations support

• Simulation support

• Write and present technical paper(s) at aerospace conferences, if required

• Configuration management for all spacecraft parameters, assumptions, and other setup parameters used in unique mission analyses and for periodic mission analysis updates (e.g. – lifetime analysis)

• Analysis and reduction of observed Aqua star tracker data may be started and the necessity for an updated Aqua star catalog will be assessed, if requested by the Mission Director o Assumption: necessary observational data will be available from FOT

• Analysis and support of decommissioning maneuver design for maneuvers utilizing slewing on reaction wheels

• Analysis and support of developing and planning retrograde RMM maneuvers

• End of mission planning and decommissioning plans

• Analysis and support of design and plans for fully retrograde maneuvers

Skill Requirements: FreeFlyer scripting, Matlab scripting, ability to present analyses to a wide audience.

Subtask 5: EOS Aqua Routine Flight Dynamics Support Task Scope: The contractor shall provide routine operations support for the Aqua Flight Dynamics Systems.

Technical Requirements: Specific support can include, but is not limited to:

• Routine daily/weekly/periodic product generation and delivery, including spacecraft computer loads and acquisition data, and other products required by the mission support personnel

• Lifetime studies

• Fuel budget/bookkeeping analysis

• Orbit parameter trending

• Attitude maneuver planning, as needed

• Contingency/Anomaly support, as needed

• Critical operations support, as needed

• Simulations support, as needed

• Oversight/quality assurance of routine product generation

• Documentation upkeep (ICDs, MOUs, SOPs)

• Attitude maneuver monitoring

• OBC attitude validation (monthly)

• Training of new FOT on-line engineers on the FDS

• Routine conjunction assessment support and risk mitigation maneuver (RMM) planning

• Configuration management for all spacecraft parameters, assumptions, and other setup parameters used in unique mission analyses and for periodic mission analysis updates (e.g. – lifetime analysis)

• Execution of decommissioning plans, including planning and calibration of perigee lowering maneuvers, and expending of all fuel

• Training of new Flight Dynamics analysts

Skill Requirements: FreeFlyer scripting, Matlab scripting, ability to present analyses to a wide audience.

Subtask 6: EOS Aura Flight Dynamics Analysis Support Task Scope: This subtask provides non-routine analysis and operations support for Aura. Support shall be performed during normal business hours (between 9:00 AM ET and 5:00 PM ET Monday through Friday) except in the event of a mission critical emergency, when off-hours support may be required on a temporary basis.

Technical Requirements: Specific analyses can include, but are not limited to:

• Requirements analysis

• Contingency analysis

• Attitude analysis as needed

• Implementation of routine attitude sensor validation, if prioritized by Mission Director

• Attitude sensor calibration as needed

• Contingency/Anomaly support as needed

• Critical operations support

• Simulation support

• Write and present technical paper(s) at aerospace conferences, if required.

• Configuration management for all spacecraft parameters, assumptions, and other setup parameters used in unique mission analyses and for periodic mission analysis updates (e.g. – lifetime analysis)

• Analysis and reduction of observed Aura star tracker data may be started and the necessity for an updated Aura star catalog will be assessed, if requested by the Mission Director o Assumption: necessary observational data will be available from FOT

• Analysis and support of decommissioning maneuver design for maneuvers utilizing slewing on reaction wheels

• Analysis and support of developing and planning retrograde RMM maneuvers

• Analysis and support of planning for the possibility of spacecraft slew to provide more power and prolong the mission lifetime

• End of mission planning and decommissioning plans

• Analysis and support of design and plans for fully retrograde maneuvers

Skill Requirements: FreeFlyer scripting, Matlab scripting, ability to present analyses to a wide audience.

Subtask 7: EOS Aura Routine Flight Dynamics Support Task Scope: The contractor shall provide routine operations support for the Aura Flight Dynamics Systems.

Technical Requirements: Specific support can include, but is not limited to:

• Routine daily/weekly/periodic product generation and delivery, including spacecraft computer loads and acquisition data, and other products required by the mission support personnel

• Lifetime studies

• Fuel budget/bookkeeping analysis

• Routine drag make-up maneuver planning and calibration

• Orbit parameter trending

• Attitude maneuver planning, as needed

• Contingency/Anomaly support, as needed

• Critical operations support, as needed

• Simulations support, as needed

• Oversight/quality assurance of routine product generation

• Documentation upkeep (ICDs, MOUs, SOPs)

• Attitude maneuver monitoring

• OBC attitude validation (monthly)

• Training of new FOT on-line engineers on the FDS

• Routine conjunction assessment support and risk mitigation maneuver (RMM) planning

• Configuration management for all spacecraft parameters, assumptions, and other setup parameters used in unique mission analyses and for periodic mission analysis updates (e.g. – lifetime analysis)

• Execution of decommissioning plans, including planning and calibration of constellation exit and perigee lowering maneuvers, and expending of all fuel

• Training of new Flight Dynamics analysts

Skill Requirements: FreeFlyer scripting, Matlab scripting, ability to present analyses to a wide audience.

Subtask 8: FDS Software Analysis Support

Task Scope: This subtask provides requirements analysis, requirements generation, and test plans for the FDS software builds for Aqua, Aura, and Terra. The requirements generation also includes getting feedback from the various mission support teams regarding enhancements to the FDS software. This subtask also includes assistance with FOT acceptance testing of FDS upgrades/changes and Requirements testing and User Acceptance Testing of FDS software builds.

Requirements analysis and test plan development will be scheduled, as necessary. Support shall be performed during normal business hours (between 9:00 AM ET and 5:00 PM ET Monday through Friday) except in the event of a mission critical emergency, when off-hours support may be required on a temporary basis.

Technical Requirements: All SW releases must be delivered with build instructions, to include all material necessary to rebuild the latest version of the FDS software in the case of Continuity of Operations (COOP).

Specific support can include, but is not limited to:

• Performing acceptance testing and parallel operations for each software release and patch

• Updates to flight dynamics software and scripts to prepare for constellation exit and decommissioning maneuvers

• Updates to flight dynamics software and scripts to support conjunction assessment including automation, devolution of the Conjunction Analysis Risk Assessment (CARA) operations capability, or other as needed

Skill Requirements: FreeFlyer scripting, Matlab scripting, knowledge of NASA software development cycle and best practices

Subtask 9: EOS FDS Maintenance and System Administration

This subtask describes the Earth Observing Systems (EOS) Flight Dynamics System (FDS) Software Maintenance Support in support of the Terra, Aqua and Aura missions, as well as FDS System Administration. This work requires technology development, ground system integration, and mission support. The high-level requirements and goals that shall be met for these tasks are:

1. Provide software maintenance and integration support for all FDS subsystems (COTS and GOTS) in both the EOC and the Back-up EOC.

2. Provide computational and mission product development support.

3. Provide planning and implementation support to maintain product development software.

4. Increase the multi-mission capabilities of the EOS FDS as needed. Capabilities may include, but are not limited to:

a. Common COTS software versions (i.e., FreeFlyer and MATLAB) to support Terra, Aqua, and

Aura missions

b. Common utility versions for all missions (e.g. WinSCP, Secure SSH, node.js, etc.)

c. Multi-mission reference data (e.g., reference files, TDRS ephemeris) in a common area to support all missions

d. Common desktop interface to support all missions

Details of the work provided herein are to be considered the baseline. However, as products are evaluated and work priorities change, the contractor may be directed to adjust resources across this task.

This subtask provides the software maintenance and integration support for all FDS sub-systems, including, Maneuver Planning, Planning and Scheduling, Automation, Attitude, and Visualization.

These subsystems are maintained to support the mission daily and weekly activities. Maintenance activities include analysis, software development, integration of FDS tools and mission procedures, and serving as maintenance team lead in support of all FDS users, including flight dynamics analysts and the flight operations team. Maintenance activities do not include error fixes to the COTS tools, which is the sole responsibility of the COTS vendor. As such it is the responsibility of the TM to obtain maintenance contracts with the COTS vendors to provide such support. Problems, resolutions, and delivery of custom software issues will be tracked using the Mission Information & Issue Tracking System (MIITS). MIITS is a web-enabled tracking system used to document software and system problems encountered during the course of FDS operations. The MIITS is also occasionally used to request enhancements to the system, such as COTS upgrades, and minor improvements to the FDS application. All DRs are assigned a severity level, based on their impact to FDS operations, as users enter them into the tool. Waivers for all operational software changes will be submitted via an ESMO Configuration Modification Request (CMR).

Specific work items include, but are not limited to:

1. Designate on-call support staff for problems as they arise. This point of contact is the owner of the issue and is responsible for ensuring all necessary work is performed and reporting status through issue resolution. All contractual issues remain the responsibility of the TM.

2. Support the continued updating of technology used to operate FDS systems in both the EOC and

BEOC.

3. Review, evaluate the impact and test the FDS software components to support IT security patch cadence per the ESMO patch management plan.

4. Provide FDS development support for any required OS/COTS upgrades to ensure the ESMO patching cadence is met.

5. Maintain the automations of analysis FreeFlyer scripts that are provided by the customer through ESMO FDS Analyst Team.

6. Maintain and act as the primary vendor interface for the COTS FreeFlyer software.

7. Maintain and act as the primary vendor interface for the COTS MATLAB software

a. Maintain the MATLAB source and configuration files.

b. Maintain any additional custom MATLAB software.

8. Maintain custom AutoProducts software source code, user configuration files and action files

a. Analyze user requirements to develop actions that produce the daily and weekly products.

b. As this software was developed by GSFC, the sole responsibility falls to this sub-task.

9. Maintain custom TDRSS Onboard Navigation System (TONS) Ground Support System (TGSS) software to assist in accurate TONS performance, monitoring, and product development.

a. This work may include, but is not limited to, such tasks as upgrading scripts for or modifying algorithms in the TGSS software.

b. As this software was developed by GSFC, the sole responsibility falls to this task.

10. Maintain custom EOS Automated Task Operations Manager (ATOM) software - Maintain the EOS ATOM source and configuration files.

11. Maintain all additional FDS utilities, (e.g., used to convert ephemeris for the various FDS sub-systems).

12. Work with the ESMO Discrepancy Review Board (DRB) and users to review and prioritize the DRs, develop an implementation schedule, and to assign the DRs to FDS maintenance team engineers for analysis, and problem resolution.

13. Support the EOS FDS Analyst Team in the generation and update of requirements for each FDS release

14. Support all meetings as deemed necessary by the Task Monitor, including conducting System Requirements Reviews, Preliminary/Critical Design Reviews, Test Readiness Reviews, Pre-Ship Reviews, System Acceptance Reviews, and Operational Readiness Reviews.

FDS System Enhancements

The customer will decide, based on the determined levels of effort supported by funding, importance of features and other criteria, which of the enhancements, if any, should be incorporated into FDS and in what order they should be developed and deployed.

The contractor shall provide analysis and recommendations of how the functionality might be implemented and estimates for the effort required for implementation of the chosen enhancements.

Sets of functionality shall be grouped into releases as defined by the customer over the period of performance. Potential system enhancements that may be incorporated into the FDS baseline application are listed below. Additional enhancements not listed in this document discovered by users of the FDS system may also be considered as candidates for inclusion in the FDS application.

NOTE: The items listed below are only representative items that MAY be included into the FDS application. The actual contents and delivery dates shall be determined through analysis of customer priority (TM and ESMO), effort required, and time available to implement each specific enhancement or feature.

Specific work items include, but are not limited to:

1. Fix, test, and implement resolutions for open DRs.

2. Add, update, and support product fetching, generation, and delivering.

3. Continue migration of older AutoProduct services into the EOS ATOM ecosystem.

4. Continue integrating QA processes into the ATOM dashboard display on FDS workstations.

5. Add additional automation to the FDS system, specifically in the maneuver planning functionality.

6. Support the upgrade of COTS software in the case where manufacture support ends.

7. Update EOS ATOM, AutoProducts, and AutoRMM with more robust logging, diagnostic, configuration, and recovery services.

8. Create or implement scripts, utilities, and processes that reduce manual steps in the software deployments.

EOS FDS System Administration

This section describes the EOS FDS Systems Administration Support required by the ESMO Project.

The high-level requirements that must be met for these tasks are:

1. Provide design and hardware, firmware, and software integration services for new and existing operational support processes.

2. Provide configuration and administration of all FDS user laptops to maintain their capability of providing on-call support, off-site analysis, and regular operational support.

3. Research and implement improvements to the system administration of FDS systems to provide improved efficiency, simplicity, and security.

4. Provide IT maintenance support for existing operational support processes (e.g., system failover and failback, backup/recovery, archival/retrieval, routine system administration activities)

5. Provide hardware maintenance (either in-house or through a 3rd party) for all Terra FDS and EOS FDS equipment that is not covered by a manufacturer support contract.

6. Provide support for FY24 tech refresh, which may include migration of FDS workstations to virtual environment.

7. Provide support for the FDS systems in the Building 13 BEOC and Building 32 EOC environments.

8. Provide configuration management (CM) support for hardware, COTS, GOTS, and custom software, and CM documentation necessary to maintain these systems operationally.

9. Maintain and CM operational documentation and systems administration procedures.

10. Provide operating system (OS) maintenance support for all operational systems and install the latest OS security patches.

11. Provide System Administration to support IT Security Patch cadence per ESMO patch management plan.

12. Provide enhanced IT Security Compliance Quality Assurance, Scanning, and Monitoring of ESMO system to support increased IT Security Patching.

13. Run NASA approved vulnerability-assessment tools periodically to identify security vulnerabilities or risks.

14. Review security notification E-mails for any related security vulnerabilities.

15. Follow the ESMO Security implementation, in coordination with other contractors working for

ESMO.

16. Support IT Security Patch Management with functions such as:

a. Develop, manage, and execute schedule working closely with developers, System Administrators, the EOS FDS Analyst Team, and other ESMO contractors to meet OS/COTS patching cadence

b. Develop year-long optimal schedule for Patch Management working with lead IT Security Manager to ensure alignment with reported guidance agreed with Center IT Security Organization

c. Complete ESMO reports as requested by ESMO Ground System Manager

d. Complete and submit Change Management Requests documenting the patch content with confirmation from IT Security and deployment workflow in coordination with the EOS FDS Analyst Team

e. Coordinate and execute expedited deployments based on relevant NASA SOC communications or DHS Emergency Directives

17. Support the security team with system scans and collection of logs, and implementation of security controls to address POA&M items

18. Perform routine administration activities (e.g., backup, archival, user account administration, etc.) for all equipment to ensure proper operation

19. Monitor all systems for security issues including unauthorized access, maintaining OS security updates and support for security scans.

20. Track and obtain quotes for all COTS software licenses, hardware maintenance agreements, and product upgrades.

21. Perform contingency procedures when necessary to continue operations.

22. Provide after hours and weekend on-call technical support

This effort is comprised of two areas of expertise: EOS FDS Operational Services Support and EOS FDS Systems Administration Support. Each of these areas is described in more detail below.

EOS FDS Operational Services Support

This work includes providing general support for the maintenance of the operating environment, including user and system environments for the Terra FDS and EOS FDS. The effort includes systems maintenance activities associated with operational support processes (e.g., backup/recovery, archival/retrieval, fail-over/fail-back), procedure development, configuration management, and hardware and operating system maintenance.

Specific work items include, but are not limited to:

1. Maintain software, processes and procedures for the user environment that produce operational products.

2. Maintain backup and archival plans, processes and procedures.

3. Maintain continuity of operations processes and procedures that address fail-over and recovery between the production and backup systems

4. Document, and maintain software, processes and procedures that support NASA Procedural

Requirements (NPR) 2810.1 Security of Information and Information Systems.

5. Maintain processes and procedures for the configuration management of FDS custom software.

6. Implement new FDS operational support processes (i.e., backup/recovery, archive/retrieval)

7. Provide software maintenance support for existing FDS operational support processes (e.g., system fail-over and fail-back, system administration activities)

8. Attend weekly status meetings, as needed, in support of the Task Monitor.

EOS FDS Systems Administration Support

This subtask provides systems administration support for the Terra FDS and EOS FDS, located in the EOS Operations Center (EOC), in Building 32, and the Backup EOS Operations Center (BEOC), in Building 13, on the GSFC campus. . The work includes the implementation of all processes and procedures necessary to maintain the hardware, COTS software, and operating systems assigned to these systems. It involves providing weekday on-site system administration support and after hours on-call support during evening hours and weekends to ensure successful system operation.

Key Responsibilities

1. Provide Systems Administration Support, Monday-Friday, between the hours of 8:00 AM and

5:00 PM ET

2. Provide after hours on call support via customer provided cellular phones, Monday – Thursday, between the hours of 5:00 PM and 8:00AM ET

3. Provide weekend on call support via customer provided cellular phones beginning Friday evening at 5:00 PM through Monday morning at 8:00 AM ET

4. Provide 30 minute telephone response to all after-hours and weekend on-call requests, 2 hours for email based requests.

5. Provide 2 hour on-site arrival to all after-hours and weekend on site requests

Specific work items can include, but are not limited to:

1. Maintain all operating systems for the Terra FDS and EOS FDS systems. This includes monitoring NASA incident response center security recommendations, installing operating system patches, and performing other services to be in compliance with NPR 2810.1 Security of Information and Information Systems.

2. Maintain all computer hardware and associated peripherals for the Terra TGSS/ Software Only Simulator (SOS), EOS FDS, and Constellation Visualization Tool (CVT) systems. This includes the tracking and renewal of all hardware service level agreements.

3. Track and renew all COTS software licenses for the Terra TGSS/SOS, EOS FDS, and CVT systems.

This includes the installation of new COTS software licenses, as well as installation of any new or COTS upgrade packages that may be required.

4. Schedule and perform daily and weekly system backups and data archival for the Terra FDS and EOS FDS systems.

5. Schedule and perform semi-yearly failover and failback tests to ensure the operational readiness of all backup system capabilities for the Terra FDS and EOS FDS.

6. Monitor and manage system resources on a daily basis to ensure optimum system performance (e.g., storage usage, CPU utilization, network traffic, etc.)

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. NASA will provide office space in Building 32 for task personnel. NASA will provide the required space to house operational FDS hardware and software in Building 32 and 13.

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. Specific performance metrics for this task include, but are not limited to,

• On-time delivery of flight dynamics operations products to end users

• Meeting deliverables and delivery schedules

• Tracking attitude and maneuver performance of the missions

• Tracking thruster performance and fuel use

• Minimal to no operations errors

• Up-to-date and non-expired documentation (ICDs, SOPs, etc.)

• Readiness for constellation exit and retrograde maneuvers in the form of appropriate software, SOPs, training, etc.

The Technical Monitor will provide feedback of technical performance as it relates to 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 and to meet all required security restrictions imposed by ESMO for their Mission Operations Centers.

IX. Travel No travel for this task is anticipated.

X. Work Location This work shall be performed on-site 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 weekly basis. The report shall include accomplishments for the past week and plans for the following week. Weekly status meetings will be held with the TMs, with additional meetings to be supported as requested. The contractor shall maintain meeting minutes and action items.

Detailed schedules shall be provided to the TMs as required. 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 weekly 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 meet with the TM and/or the lead FD analyst on a weekly basis to review progress, discuss, prioritize, and schedule new and outstanding Discrepancy Reports for correction and implementation. 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, or as directly by the TM.

Cost data shall be provided monthly on a subtask basis, as well as in monthly and quarterly reports.

Specific subtask charge numbers will be provided for each mission to track all FD team activities related to RMM support/cost on an individual mission basis by month. Budget input will be prepared yearly and updated as necessary. Budget will be maintained at the subtask level. If additional funds are needed beyond the approved budget levels for unanticipated work or other reasons, this issue must be worked through the TMs and CO well in advance of the expected need date.

XII. Security Requirements This task shall comply with IT security requirements as defined by the Earth Sciences Mission Operations (ESMO) Division and by GSFC, and as documented in the EOS FDS IT security plan, NPR 2810, and ESMO security policies for all systems located in the EOC and BEOC.

XIII. Rights The Contractor shall adhere to the FAR 52.227-17 RIGHTS IN DATA – Special Works(2007), – General, Alternate II (2007) and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015)

XIV. References 552-FDD-96/010R0UD0 ICD between ECS and AM-1 FDS FDS-EMOS-Aqua ICD between FDS and EMOS for Aqua FDS-EMOS-Aura ICD between FDS and EMOS for Aura FDS/FDF ICD - Aqua

428 ICD-015

ICD between FDS and FDF for Aqua updated version in COMET for review

FDS/FDF ICD - Aura

428-ICD-021

ICD between FDS and FDF for Aura initial draft in COMET for review

FDS/FDF ICD -Terra 428-

ICD-022

ICD between FDS and FDF for Terra initial draft in COMET for review

FDS-FOT-Aqua ICD between FDS and FOT for Aqua FDS-FOT-Aura ICD between FDS and FOT for Aura FDS-GDAAC-Aqua ICD between FDS and GDAAC for Aqua FDS-GDAAC-Aura ICD between FDS and GDAAC for Aura FDS-EOSDIS-Terra ICD between FDS and EOSDIS for Terra