SOW 130 eLib.pdf

Statement of Work Task: Flight Dynamics Facility Launch Vehicle Operations Support

Task Order: 130

Task Modification: 4

I. Summary of Changes in this Task Modification

• Extends Period of Performance until October 31, 2024

II. Summary of Work This statement-of-work describes the Launch Vehicle (LV) Operations Support requirements, which includes mission preparation and real-time operations support, within the Flight Dynamics Facility (FDF), in support of the Navigation and Mission Design Branch (NMDB).

As detailed below, the contractor shall provide support for LV missions as needed within the FDF, in the technical areas of mission analysis & planning, integrated networks testing, documentation, mission readiness reviews, and operations support.

As an operations task within the FDF, this task is required to work closely with other Flight Dynamics Support Services (FDSS) III tasks and the NMDB. Task personnel shall interface directly with project personnel, operations team members, other contractors, tracking networks, and others, as needed. The contractor shall accept direction from the FDF Operations Director, the FDF Deputy Operations Director, and/or the Task Monitor (TM) in bi-weekly meetings, ad-hoc discussions, or other methods as necessary. Task personnel are expected to be proactive in reporting anomalies and other errors to the appropriate parties and to prepare and support project reviews as needed or requested. Costs associated with each mission and/or effort shall be tracked as a separate line item. The contractor shall prepare conference papers or other documentation as appropriate to promote and demonstrate the capabilities of the FDF. Task personnel shall prepare and maintain databases, reports, and/or other mechanisms as needed to support FDF customers.

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 The work on this task is divided into the following areas:

a. LV Mission Support

The contractor shall work with internal and external mission support elements in preparation for and support of LV mission requirements definition, testing, and flight operations, including but not limited to Atlas V, Delta IV, Vulcan, JAXA HIII, JAXA H-IIA, Vettore Europeo di Generazione Avanzata (Vega), Ariane 6, Blue Origin, Falcon-9, and Minotaur. These external support elements include, but are not limited to, integrated networks, private industry, Code 457, and other NASA field centers.

1. Mission Analysis, Planning, and Integration

The contractor shall perform the required analysis of trajectory information provided by the LV provider, and develop trajectory data interface and acquisition data generation and delivery procedures. The contractor shall develop and maintain a support plan that includes sections addressing mission specific support requirements and procedures for all FDF mission support elements. When required, the contractor shall perform analysis of LV provider’s telemetry formats to ensure FDF readiness for receiving and processing of on-board navigation data for acquisition data support, and provide products specified by the LV Team/Manufacturer for flight planning purposes.

The contractor shall develop communications requirements and procedures pertaining to voice and video circuit configurations, facsimile, telephone, tracking and telemetry data processing and storage, and acquisition data transmission. The contractor shall coordinate changes to hardware and software configuration within the FDF with the Facility Review Board (FRB) and fully comply with the established policies and procedures. In addition, the contractor shall comply with established network schedules and policies with regard to hardware and software configuration changes prior to and during critical testing and operations periods.

The contractor shall establish and maintain an action item database for the purpose of identifying problems, response dates, and the disposition of action items. The contractor shall generate, quality assure, and coordinate the transmission of pre-launch nominal and contingency acquisition data to the supporting Advanced Communications Capabilities for Exploration and Science Systems (ACCESS) and the Near Space Network (NSN), and provide mission planning and scheduling products for the integrated networks consistent with developed and approved procedures.

2. Real-Time Mission Support

The contractor shall provide support for LV mission operations in accordance with the support plan, which consists of pertinent local operating procedures (LOPs) and checklists, and mission requirements. This support includes staffing of communications consoles, flight dynamics mission management and coordination, acquisition data generation and transmission, planning and scheduling product generation, telemetry data monitoring and processing, and mission status reporting and briefings as required. A Post-Mission Report (PMR) for each mission shall be provided to the TM at launch plus 3 weeks. A courtesy copy of the PMR shall also be delivered to the Code 457 Network Director (ND) or their designee.

The contractor shall support all mission phases including launch and powered-flight, post-maneuver real-time analysis based on guidance telemetry and pre-defined network assets, and special requests as required for each unique mission.

The contractor shall perform the generation of navigation products (nominal or contingency trajectory, or tracking-related), acquisition data generation, radiometric tracking data evaluation, and the delivery of the actual payload orbit insertion state vector (if required), as specified for each unique mission.

The contractor shall provide a postflight mission operations report to the TM, FDF Operations Director, and LV ND, and postflight mission analysis as requested.

b. LV Network Support

As needed, the contractor shall support other LV activities related to FDF functionality. This support may include, but isn’t limited to, evaluation and/or development of FDF support requirements, resolution of Network related problems or issues, participation in discussions or forums about FDF support, creation and/or review of documentation and procedures, and general technical expertise.

The contractor shall provide support for required integrated networks testing of LV ground support hardware and software. The contractor shall develop test plans and procedures and generate the required data for SN Vector Verification testing, and GN testing as required. The contractor shall also execute the procedures, evaluate the results, and provide written reports to the TM, FDF Operations Director, and LV ND and Mission Manager (MM), as required.

The contractor shall prepare for and participate in network and mission simulations, data transmission tests, dataflows, and launch dress rehearsals, as well as contingency simulations.

Internal simulations and exercises shall be performed as required to maintain proficiency and ensure readiness to support. The test reports shall be provided to the TM, FDF Operations Director, and the LV ND and MM within 1 week of completion of the simulation/test if needed or be incorporated into the Network Report.

c. Documentation and Readiness Reviews

The contractor shall review pertinent support documentation including but not limited to:

Network Operations Integration Plan (NOIP); Network Mission Operations Plan (NMOP); Network Requirements Document (NRD) or Network System Requirements Document (NSRD), Interface Control Document (ICD) and associated Operations Concepts; Network Operations Support Plan (NOSP); Project Service Level Agreement (PSLA), Radio Frequency (RF) ICD, etc. The contractor will also participate in the Code 457 Configuration Control Board (CCB) and review documents to the standards of the CCB. The contractor shall perform analysis to determine hardware, software, system configuration, and testing requirements, and implement procedures and methods to satisfy those requirements prior to the LV mission in conformance with network schedules and policies. The contractor shall also prepare and present information concerning Flight Dynamics Facility mission requirements and readiness to support at the FDF Operations Readiness Review (ORR) and the Code 457/Code 300 Mission Operations Readiness Review (MORR) prior to each mission.

V. Deliverable Items and Schedules The Launch Vehicle Operations Support Task deliverable items and schedule are provided in Table 1 with the CY4 work-to baseline for expected mission support schedule in Table 2.

Deliverable LV Analysis & Ops LV Mission Services

Integration

Schedule

Task Status Report X X Monthly

Action Item Resolution Reports X X Action Item due date

Anomaly reports X X Event + 1 day

Mission Ops Readiness Review Presentation Materials

X When delivered to Code 457

Analysis reports X X As required

Ops Concept Studies X X As required

Test Reports X Test completion + 1 week

Post-mission Reports X End of ops + 3 weeks

Trip Reports X End of trip + 3 weeks

LV Training & Cert Plan update X X Yearly

Table 1. Deliverable Items and Schedule

Number Mission Expected Launch Dates LV Supplier

1 Atlas V / USSF-51 Nov-23 ULA

2 Vulcan / Peregrine Dec-23 ULA

3 Atlas V / ViaSat-3 Dec-23 ULA

4 Ariane 6 / Mission 1 Dec-23 ESA

5 Vulcan / DCC-1(Cert-2) Jan-24 ULA

6 JAXA HIII / [Mission 1] Feb-24 JAXA

7 Atlas V / CFT-1 Mar-24 ULA

8 Vulcan / USSF-106 Mar-24 ULA

9 New Glenn / [Mission 1] Jul-24 Blue Origin

10 JAXA HIII / MMX Sep-24 JAXA

Table 2. Baselined Mission Support Schedule

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 FDF Configuration Management Plan.

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 equipment 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. The contractor shall work with the FDF Operations Planning team and TM to establish and maintain accurate Level of Effort (LOE) estimates for all current and development missions and activities, while managing work scope. The contractor shall maintain the Training and Certification process for LV support, which includes identification of Subject Matter Experts (SMEs), development of a skills catalogue, training matrix, in-class instruction, tests, simulations, on-the-job-training (OJT), and the process of certification.

VI. Performance Metrics

Performance of the task will be based on timeliness and completeness of deliverables. The work performed for this task will be evaluated by the TM based on the technical merit. Technical evaluation of the task performed is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.

VII. Government Furnished Facilities, Equipment, Software and Other Resources The Government will provide account and passwords to government-furnished equipment 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

The task shall plan for participation of up to two engineers at four Ascent Operations Working Group (AOWG) meetings at either the Eastern Range (ER) located at Kennedy Space Center (KSC), Florida, or Western Range (WR) located at Vandenberg Air Force Base (VAFB), California. Non-local travel may be required to attend conferences, training, or other related technical meetings.

IX. 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, as based on work requirements and in accordance with NASA's work policy.

X. Reporting Requirements

The contractor shall report task status in person or via teleconference to the TM or designated alternate (e.g. FDF Deputy Operations Director) on a bi-weekly basis. Brief written mission analysis summaries, action item status, and/or mission status reports may be requested. The contractor shall provide a report of action item status on a monthly basis or at the direction of the TM, FDF Operations Director, Deputy Operations Director, or ND and MM. In addition, the contractor shall report mission support status at the direction of the TM, FDF Operations Director, or ND, to include, but not limited to, the following times: pre-launch readiness briefing and post-launch debriefing. Additional status meetings and reports may be requested as deemed necessary.

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. On-site 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, the Goddard Computational Cloud support, or the contractor sustaining engineering support depending on system location.

XII. Rights 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 Not applicable.