SOW 147 eLib.pdf
PDF 525 KB Posted
- Solicitation number
- FDSSIV23JG-elibrary
About this file
This document is a Statement of Work (SOW) for a task order to provide support for the Deep Atmosphere Venus Investigation of Noble gases, Chemistry, and Imaging (DAVINCI) mission. The work will focus on assisting the DAVINCI Flight Dynamics Lead with managing the mission's flight dynamics, including trajectory design and optimization, as well as providing data products, attending meetings, and supporting mission reviews and milestones. The period of performance is from August 7, 2023 to October 31, 2024, with the potential for follow-on work. The contractor will be evaluated on criteria such as cost, on-time delivery, and technical quality. The government will provide access to relevant software and facilities, and travel may be required, though limited due to budget constraints. Reporting requirements include weekly status updates, quarterly project meetings, and a flight dynamics requirements review.
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: DAVINCI Mission Design Support Task Order: 147 Task Modification: 0
I. Summary of Changes in this Task Modification
• Initiated/submitted task on 7/7/2023
II. Summary of Work NASA Goddard Space Flight Center’s (GSFC’s) Navigation and Mission Design Branch (NMDB) is seeking support for the Deep Atmosphere Venus Investigation of Noble gasses, Chemistry, and Imaging (DAVINCI) mission.
The work for this task will focus on assisting the DAVINCI Flight Dynamics Lead (FDL), Kyle Hughes, with managing the mission’s flight dynamics (FD) as well as conducting mission-design analysis including (but not limited to) trajectory design and optimization.
III. Period of Performance The period during which the work for this task shall be performed is between August 7, 2023 and October 31, 2024.
The availability of follow-on work beyond the listed performance period is very likely.
IV. Task Description The proposed work will include (but is not limited to) the following, or as otherwise negotiated with the TM:
A. Trajectory design and optimization for the baseline launch period and all viable backup opportunities.
B. Management/maintenance of the trajectory as needed by the FDL/project as new aspects of the mission details are discovered and/or various updates are needed as the mission develops.
C. Provide data products to the FDL/project as needed.
D. Attend FD meetings and other relevant project meetings as requested by the TM.
E. Support the FDL and FD team in mission reviews, status updates, and other milestones requiring presentations and/or reports.
F. Developing documentation such as requirements, interface control documents, navigation plan, etc.
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.
b. Configuration Management
Systems and documents will be covered under the Configuration Management Plan specific to each project under which the work is performed.
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.
VII. Performance Metrics
The work performed for this task will be evaluated by the TM based on the technical merit. The TM shall develop detailed performance metrics that shall reflect the contractor’s performance in meeting specific mission requirements, deliverables and delivery schedule, and the contractor’s cost. Technical evaluation of the task performance is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.
The specific performance metrics are:
a. Planned versus actual cost
b. On-time delivery of items and milestones specified in Section V of this SOW and other deliverables as required by the TM.
c. Quality of support to the project and any other customers and stakeholders
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 may be necessary for various reviews and key meetings throughout this work. Due to projected FY24 budget cuts, travel will not be required, but may be accommodated per negotiation with the TM. Funds for a single trip to GSFC’s Greenbelt, MD campus should be assumed for a 3-day meeting/review. Costs are estimated at ~$3000. Unanticipated travel may also be negotiated with the TM. Should the task POP be extended, travel in FY25 and later will be much easier to accommodate.
X. Work Location This work may be performed on site at GSFC, on site at the contractor’s facility, or remotely.
XI. Reporting Requirements
a. Weekly Status Updates
The contractor shall provide verbal weekly updates to the TM/FDL with status of completed work. The update may include a summary of the week’s highlights/accomplishments, milestones/deliverables, schedule changes, and/or risks. This report may be informal, and can be either verbal in a weekly meeting (or other communication with the TM/FDL), a slide package, document, and/or email.
b. Quarterly Updates to DAVINCI Project
Approximately each quarter, the project holds a DAVINCI Quarterly meeting where each mission element (including FD) provides a status update. Status is given in the form of a ppt presentation that is typically presented by the FDL. The contractor shall support the FDL in preparing content for this meeting and may be asked to present the status when the FDL is unavailable. Attendance at these meetings may be virtual or in person.
c. FD L3 Requirements Review The FD team is required to provide the L3 requirements for the FD design. The contractor shall support the FDL and broader FD team in identifying and defining these requirements, as well as help identify corrections needed to mission L2 requirements, and drafting L4 requirements. The contractor shall also support the FDL in preparing the requirements documentation and presentation materials for the FD Requirements Review anticipated in Winter 2024.
d. Data Archiving Archive all analysis data, including scripts, inputs, raw output data. All reports, documents, presentation charts, produced for this work will also be archived, as well as any reference material used to complete the work. Archiving will be done throughout the task and reviewed at the completion of each major task item. A detailed index must also be provided to locate all archived data, and a Technical Memo may be required to summarize, and provide context for, the content of the archived data. The complete data-archive package will be delivered to the TM.
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 RIGHTS IN DATA – general (FAR 52.227-14) Alternate II (2007 and Alternate III (2007), as modified by NFS 1852.227-14 (APR (2015).
File details come from the government source that posted it. Updated .