SOW 135 eLib.pdf

Statement of Work Task: Planetary Defense Support Task Order: 135 Task Modification: 4

I. Summary of Changes in this Task Modification

• Initiating task on 8/16/2020

• Mod1 – Administrative: Changed Project RA to Rickicia Cheatham on 1/10/2022

• Mod2 – Technical: Added tool development for planetary science to scope of work, added labor to planetary science work, and extended POP to September 30, 2023.

• Mod3 – Administrative: Changed Project RA to Merim Karailo on 6/7/2022

• Mod4 – Technical: Extended POP to September 30, 2024 with funding for continued support at same level of effort.

II. Summary of Work This task provides experienced Flight Dynamics support for mission design, concept studies, and tool development in support of planetary science and planetary defense (PD) projects.

III. Period of Performance The period during which the work for this task shall be performed is between August 16, 2021 and September 30, 2024.

IV. Task Description I. The contractor shall perform analysis to design missions and their trajectories for mission studies and proposals. This will include mission feasibility studies, detailed trade studies, and other analyses to determine the impact of various mission designs on mission elements and requirements (and vice versa). Specific work items and deliverables will be negotiated with the project and the TM.

II. The contractor shall develop mission-design tools to enable new analyses as deemed necessary by the project. Specific work items and deliverables will be negotiated with the project and the TM.

III. The contractor shall attend regular meetings as specified by the project or the TM.

Skill Requirements:

This position requires expertise in flight dynamics, mission-concept design, and software development. The position requires the ability to develop a planetary-class, flight-dynamics design from scratch that meets mission requirements. This assignment requires extensive interplanetary mission-design experience; as well as knowledge of mission systems and their coupling with the flight-dynamics design. Personnel assigned to this task must have at

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 or any other customers as determined by the TM.

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 There is no non-local travel anticipated for this SOW. Unanticipated travel may be negotiated with TM.

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. Biweekly Status Report

The contractor shall generate Performance Reports every two weeks to the TM. The report shall include, as a minimum, a summary of the two-week highlights/accomplishments, milestones/schedule/deliverables, risks and customer meetings. The report may be a document, slide package, and/or email to the TM.

b. Analysis Technical Memo

Detailed documentation of all analyses and work done, with sufficient details for work to be reproduced. Memo must also provide information to find any relevant archived data. Details may include: descriptions of analyses, inputs, methods used, tools used.

c. Data Archiving

Archive all analysis data, including scripts, inputs, raw output data. Reports, documents, presentation charts. Detailed index of what data is archived. All data will be delivered to 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).