SOW 114 eLib.pdf
PDF 187 KB Posted
- Solicitation number
- FDSSIV23JG-elibrary
About this file
This document is a Statement of Work (SOW) for Task 114 under the Flight Dynamics Support Services (FDSS) III contract. The SOW describes the engineering analysis and operational support the contractor shall provide to the Navigation and Mission Design Branch at Goddard Space Flight Center for the Magnetospheric Multiscale (MMS) mission. Key areas include conjunction assessment, ground system design and operations, mission design, navigation, and special requests. The contractor shall use various software tools to support these activities. The SOW also covers maintenance of the Flight Dynamics Ground Support System (FDGSS) and the Attitude Ground System (AGS) for the remainder of the MMS mission operations. The period of performance is from November 1, 2023 to October 31, 2024. The contractor shall provide monthly reports, analysis reports, and participate in required meetings.
View the file
Other files
Show all 47
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FDSS3 TO 114 Page 1
Statement of Work
Task: Magnetospheric Multiscale Mission (MMS) Engineering
Analysis and Support: Flight Dynamics and Attitude Task Order: 114 Task Modification: 4
I. Summary of Changes in this Task Modification
This is a modification of an existing task order to continue providing operations coverage for MMS flight dynamics and attitude as provided under FDSS3 Task 114. This encompasses activities as described below.
II. Summary of Work Under this task, the contractor shall provide engineering analysis and operational support to the Navigation and Mission Design Branch (NAMDB) at GSFC for the Magnetospheric Multiscale (MMS) Mission.
The specific technical areas for engineering and analysis are conjunction assessment, ground system design & operations concept, mission design, navigation, and special requests & associated analysis. In addition, the contractor shall provide the requirements analysis, design, and development of the Flight Dynamics Ground Support System (FDGSS) for the mission. Software tools the contractor shall use to support this effort include, but are not limited to, the Goddard Trajectory Determination System (GTDS), DatSim data simulation tool, Goddard Enhanced Onboard Navigation System (GEONS), FreeFlyer, the Orbit Determination ToolBox (ODTBX), ODTK, and Matlab.
This task also includes operational support of ground attitude determination and sensor calibration activities through the remainder of the Magnetospheric MultiScale (MMS) mission operations phase. Maintenance of the Attitude Ground System (AGS) software is also included in this task as part of operations support, but no releases are scheduled to take place during this period of performance and for the rest of the MMS mission operations. Software bug fixes are implemented as a response to critical errors reported as a problem by the operations team, and/or via MMS Mission Operations Change Requests (MOCRs) at the direction of, or with approval of, the Task Monitor (TM). The resolution of a MOCR or a problem report may only require documentation or operational procedure updates, and does not necessarily require a software fix.
FDSS3 TO 114 Page 2
The contractor shall expect to work with NASA as well as NASA’s partners in other government agencies, industry, academia, and other contractors in the accomplishment of the technical objectives of the task. As work results are evaluated or changes to the mission are traded, priorities may change. The contractor shall be expected to provide timely support of unplanned high-priority actions as circumstances dictate to support the MMS mission.
The phrase TM will be used in this document to denote either the Task Monitor or his designate.
III. Period of Performance Period of Performance: The period of performance for this task is from Nov. 1st, 2023 (11/01/2023) through Oct. 31st, 2024 (10/31/2024).
IV. Task Description
Subtask 1 – Routine Operations
The Contractor shall be responsible for the operation of the MMS fleet, maintenance of the Flight Dynamics Ground Support System (FDGSS), and associated analysis to support changes in the Concept of Operations as mission requirements change. This can be conducted on-site at GSFC, or remotely via VPN and NASA hardware as has been proven throughout the coronavirus pandemic.
FDGSS operations:
The contractor shall provide trained staff that are aware of the MMS Concept of Operations and can operate the FDGSS software according to the LOPs (with proficiency levels “able to perform procedure with guidance”, “able to perform procedure without guidance” or “able to perform and teach procedure”) for operations tasks including, but not limited to, the following. Note that AGS is covered under a different subtask.
• PPFA daily definitive products
• PPFA daily predictive products
• PPFA weekly predictive products
• PPFA acquisition data generation and delivery (to DSN, SN, NEN)
• Contact analysis
• CARA data delivery and receipt of results
• CAFA operation
• GGSS realtime playback
• GGSS command generation
• GEONS maintenance
• Maneuver testing using Chifi
• Realtime maneuver monitoring
• Maneuver reconstruction.
FDGSS maintenance:
The contractor shall provide trained staff for maintenance and software enhancement tasks including, but not limited to, the following:
FDSS3 TO 114 Page 3
• Complete refinement of Wald CA test background collision probability (pco) for formation flight, of particular importance for flight at small formation sizes
• Allow addition of maneuvers within 10-day CAFA forecast window
• Modify CA analysis techniques as required in light of any future changes to CARA operations
• System Manager updates: revise Contact Analysis projects as needed to allow use of new tracking assets
• PPFA training/knowledge-sharing
• Investigate whether modifications to the nominal Formation Maintenance and Resize maneuvers exist that could permit flight at smaller scale sizes
• Investigate possible modifications to the nominal Perigee-Raise/Orbit Stabilization (PR/OS), Dodge and Trim Ops Cons and LOPs for use during the extended mission
• Perform any other FDGSS maintenance as required to support the extended mission.
FDGSS software:
Renewal of the current set of FreeFlyer and Matlab licenses, including toolboxes, that are required for operations in the FDOA, as well as the individual stand-alone licenses that certain members of the team currently use, will be carried out by the government. This allows advantage to be taken of reduced prices for bulk purchases.
Analysis:
Under this work element, the contractor shall perform analysis that arises in connection with improving the MMS FD Con Ops. These topics include, but are not limited to, the following.
• Analysis in support of preparations for future “micro” apogee-adjust campaigns in the extended mission, predominantly to mitigate future long eclipses and for setting up drifts into extended strings
• Analyze the effects on increasing perigee altitude on the performance of the GPS-based GEONS orbit determination system
• Investigate role of formation geometry on Formation Maintenance (FM) maneuver fuel usage and robustness to maneuver execution errors, with the goal of being able to select formation designs that, for instance, have good robustness and fuel consumption properties and keep inter-satellite along-track spacings near perigee high while keeping spacings near apogee low
• Investigate and develop methods for implementing the non-tetrahedron formations that have been determined to be both physically and feasible and scientifically attractive, with the goal of improving science data collection during the later MMS extended mission. One particular example is the various extended strings of pearls that the MMS science team has a desire to fly in starting in mid-2024.
• Investigate a desirable sequence of maneuvers to maintain perigee altitude above the operationally acceptable minimum until end of mission
• Perform preliminary analysis of possible disposal scenarios for the end of mission
FDSS3 TO 114 Page 4
• Investigate possible extended mission maneuvers that can use any excess propellant available to increase the scientific productivity of the MMS mission
Additional analysis shall be carried out by the contractor as initiated by discussion between the TM and the contractor.
The contractor shall provide a brief report summarizing the cost, schedule and technical activities during the calendar month, submitted by the 15th day of the succeeding month.
The contractor shall document analysis results, work plans, and designs resulting from this work on the TPS system and, as coordinated with the TM, at FD internal meetings. In addition, the analysis results deemed by the technical representative to be of broad enough interest to the aerospace community shall be disseminated via technical memoranda and professional papers upon TM’s request.
Under this subtask, the contractor shall produce/update comprehensive Requirements Documents, ICDs, Mathematical Specifications Documents and ancillary documents as needed or agreed-to with external groups (e.g. SN, CARA, etc.).
Subtask 2 – Attitude Ground System (AGS)
This subtask will be the mechanism to receive the required AGS support for the remaining portion of MMS mission operations. The following work shall be performed during this period of performance:
• Generate and QA a week worth of definitive attitude and validation products per the MMS FDOA to MOC ICD, and deliver them to the MOC at least one day per week
• Perform attitude prediction and support maneuver planning for routine operations including any future Apogee-Raising (AR) maneuvers. The end products from these two activities are the predicted attitude and spin adjust plans.
• Calibrate the inertia tensor, center of mass and accelerometer bias once every other week. This group of calibrations is usually necessary after each set of Formation Maintenance (FM) maneuvers
• Per TM’s request or no more than once a year, perform sensor alignment calibrations to improve the accuracy of the onboard attitude solutions
• Per TM’s request, perform occasional analysis, for instance related to spacecraft anomalies or other dynamic events, or to future behavior such as star camera Earth interference
• Respond to MMS Mission Operations Change Requests (MOCRs) and close out any tickets or problem reports existing on the AGS. MOCRs, tickets or problem reports may be closed or resolved with software bug fixes and/or simply documentation and operational procedure updates.
FDSS3 TO 114 Page 5
• The analysis results deemed by the technical representative to be of broad enough interest to the aerospace community shall be disseminated via technical memoranda and professional papers upon TM’s request
• Provide a brief report summarizing the cost, schedule and technical activities during the calendar month, submitted by the 15th day of the succeeding month.
1. Required Task Meetings & Reports
1. Once complete, each analysis shall be delivered as a report, per the MMS-FD memorandum designation system. All memos, code, and data shall be placed on the MMS TPS and linked to the wiki for version control, easy retrieval, and archiving.
2. The contractor shall meet monthly with the Task Monitor to discuss task status with respect to cost, schedule, and technical aspects. These monthly meetings may be held in person or via teleconference as negotiated between the contractor and the Task Monitor.
3. Technical meetings of the MMS Flight Dynamics Team shall be attended by appropriate task personnel as needed.
4. Task personnel shall participate in meetings related to mission design, navigation, operations planning, and reviews called by the MMS Systems Team, GN&C Team, or the MMS Mission Director.
V. Deliverable Items and Schedules
At a minimum, the contractor shall deliver the items specified below.
# Deliverable Due Date
1 Subtasks 1 and 2: Monthly Report (as coordinated with the TM)
Monthly, by COB on the 15th of each month (on TPS and email to TM)
2 Subtask 1: Analysis Reports As negotiated with TM
3 Subtask 2: Analysis Reports As negotiated with TM
VI. Management Approach
1. Staff Allocation, Expertise, and Skill Mix
The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.
2. Configuration Management
Systems and documents will be covered under the MMS Configuration Management Plan.
Configured documents (as determined by the TM) in their latest revised form are posted on the MMSMIS (MMS Mission Information System).
3. Facilities
FDSS3 TO 114 Page 6
Appropriate and adequate IT devices to support the analyses, testing, and report development are required, including support for parametric and Monte Carlo analysis. 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.
4. 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. 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 Travel may be required for this task and shall be negotiated with and pre-approved by the Task Monitor.
This includes conference attendance at venues such as ISSFD, AIAA/AAS Astrodynamics Specialist Conference, IEEE and FD operations support conferences as applicable and available. This is expected to cover up to two contractors to up to two professional conferences to present papers on the results of MMS flight dynamics. Additional travel may be required for this task and shall be negotiated with, and pre-approved by, the Task Monitor.
IX. Work Location This work shall be performed primarily at the Goddard Space Flight Center, but additional work may be performed at the contractor’s facility.
X. Reporting Requirements The contractor shall report status electronically and in person or via teleconference to the TM. Reports shall include informal presentation of interim results, status of development and analysis activities, and action item status. The MMS Flight Dynamics team may include civil servants and other contractors with whom the contractor on this task shall need to work and coordinate analysis and other efforts. The contractor shall also support the TM in the preparation of status, requirements, and design reviews for internal and external funding agencies, and Peer Reviews. The contractor shall periodically compile results from this task into technical papers of archival journal quality for presentation at technical conferences and submission to professional journals in coordination with the TM. 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 MMS Flight Dynamics TPS wiki hosted in the MOC, as coordinated with the TM. Budget estimate input will be prepared annually and updated as necessary.
FDSS3 TO 114 Page 7
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 FAR 52.227-14 RIGHTS IN DATA – General, Alternate II (2007) and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).
XIII. References
Reference No. Document Number Document Title
1 461-SYS-RQMT-0019 Mission Requirements Document
2 461-PROJ-PLAN-0071 Concept of Operations
3 461-GS-SPEC-0049 MMS Project Flight Dynamics Subsystem Specification
4 461-GS-ICD-0013 MMS MOC-FDOA ICD
5 461-GS-ICD-0014 MMS SOC to MOC/FDOA ICD
6 461-GS-RQMT-0087 MMS FDOA Level 3 Requirements Document
7 461-GS-RQMT-0082 MMS Network Requirements Document (NRD)
8 461-PROJ-ICD-0025 RF ICD Between MMS Satellites and the DSN, GN, and SN
9 461-GS-RQMT-0078 MMS FDGSS L4 Requirements Specification Document
10 461-GS-RQMT-0076 MMS AGS L4 Requirements Specification Document
FDSS3 TO 114 Page 8
11 461-GS-PLAN-0317 FDOA Software Development, Management, and Assurance Plan
12 461-GS-SPEC-0171 FDOA Software Description Specification
13 461-GS-AGMT-0044 Operations Agreement Between MOC and FDOA
14 461-GS-ICD-0087 FDOA/FDF MOA
15 461-GS-ICD-0086 FDOA/CARA OA
16 461-GS-PLAN-0321 FDGSS Test Procedures (Rev D)
17 461-GS-PLAN-0258 AGS Acceptance Test Procedures (Rev B)
18 461-GS-HDBK-0109 FDOA Contingency Manual
File details come from the government source that posted it. Updated .