SOW 112 eLib.pdf
PDF 2 MB Posted
- Solicitation number
- FDSSIV23JG-elibrary
About this file
This document is a Statement of Work (SOW) for a task order under the Flight Dynamics Support Services (FDSS) IV contract vehicle. The SOW outlines 12 subtasks for providing product management, development, testing, and sustaining engineering support for the GMAT software product, which supports various NASA projects and provides open-source releases to the public.
The key details include a new contractor role called the "System Architect" to support the overall vision and day-to-day technical management of the GMAT product. The period of performance is extended through September 27, 2024. The SOW covers a range of GMAT support activities, including software testing, engineering, navigation and mission design, API development, and project-specific support for GOES, CAPSTONE, NGA, FDF, Space Force, SWFO, RST, and SpaceX/HLS. Reporting requirements, security, and rights in data are also specified.
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
Statement of Work Task: GMAT Development and Support Task Order: 112 Task Modification: 12
I. Summary of Changes in this Task Modification
This task modification adds and extends deliverables for the active GMAT sub-tasks. The POP for this mod is extended through Sept 27, 2024.
This modification will also outline the expectations of a new contractor role supporting GMAT called the System Architect.
II. Summary of Work The Contractor shall provide product management and development/test/sustaining engineering for the GMAT Product which currently supports numerous projects and provides an Open-Source Release to the public periodically; currently the next public release is scheduled for the end of 2024.
This SOW contains 12 subtasks all related to GMAT development and support:
o 112.01 (SW Testing) – multi-mission funded o 112.02 (SW Engineering) – multi-mission funded o 112.03 (NAV and Mission Design) – multi-mission funded, inactive o 112.04 (API Support) – multi-mission funded o 112.05 (GOES Support) – project-specific funded o 112.06 (CAPSTONE Support) – project-specific funded o 112.07 (NGA/LGS Support) – project-specific funded o 112.08 (FDF Support) – project-specific funded o 112.09 (Space Force Support) – project-specific funded, inactive o 112.10 (SWFO Support) – project-specific funded o 112.11 (RST Support) – project-specific funded o 112.12 (SpaceX/HLS Support) – project-specific funded
A new contractor role, the System Architect, is being added as a level-of-effort for this task to support the overall vision for the product as well as day-to-day management of technical work within the team.
III. Period of Performance The period during which the work for this task shall be performed is from March 01, 2024 through September 27, 2024.
V. Deliverable Items and Schedules The deliverables and milestones have been provided at the sub-task level above.
VI. Management Approach
a. Staff Allocation, Expertise, and Skill Mix
Staffing requirements for each subtask are provided in the sub-task sections above. The contractor shall designate one individual as the single point of contact for coordination of the contractor's efforts on the task with the Government's Task Monitor (TM). With concurrence from the TM, the contractor may augment its skill mix with journeyman and apprentice-level staff as appropriate to accomplish certain specific objectives of particular work items, and/or to assist with overall task coordination and management activities.
As directed by the TM, the contractor shall maintain separate cost accounts for subtasks and/or subtask work items funded from different Government accounting codes.
b. Configuration Management
The contractor shall use existing processes documented in the GMAT Software Development Plan (Configuration Management section) and commit source code and documents accordingly.
c. Facilities
Appropriate Information Technology 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
There are no specific metrics.
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 Travel to GSFC, as requested.
X. Work Location This work shall be performed in a combination of on-site at the Goddard Space Flight Center, telework, or at the contractor’s facility, based on work requirements and in accordance with NASA’s work policy.
XI. Reporting Requirements The contractor shall report status on a weekly basis via updating appropriate JIRA tickets and in GMAT weekly meeting minutes. Reports shall include informal presentation of interim results, status of development activities, and status of risks, issues, and other action items. 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 by committing them to the appropriate location in either the mesa-jade or Jazz SVN repositories. All bugs and software defects found during testing will be reported in the project’s JIRA database.
The 533 financial reports will be generated at both the overall task level and for each individual task.
• Overall Task 112
• Task 112 subtask 1 - Software Testing
• Task 112 subtask 2 - Software Engineering
• Task 112 subtask 3 - Navigation and Mission Design
• Task 112 subtask 4 - API Development and Support
• Task 112 subtask 5 - GOES Support
• Task 112 subtask 6 - CAPSTONE Support
• Task 112 subtask 7 - NGA Support
• Task 112 subtask 8 - FDF Support
• Task 112 subtask 9 - Space Force Support
• Task 112 subtask 10 - SWFO Support
• Task 112 subtask 11 - RST Support
• Task 112 subtask 12 – SpaceX HLS Support
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 The Contractor shall adhere to the FAR 52.227-17 RIGHTS IN DATA – SPECIAL WORKS and GSFC 52.227-93 APPLICABILITY OF RIGHTS IN DATA - SPECIAL WORKS.
XIV. References
1. Milner, B. “GMAT Software Development Plan”.
File details come from the government source that posted it. Updated .