SOW 137 eLib.pdf

Statement of Work Task: HSF Network Systems Engineering and Integration Task Order: 137 Task Modification: 08

I. Summary of Changes in this Task Modification Modification 1 – Updating Table 2: WBS Structure to separate SCaN funded activities

Modification 2 – Administrative modification

Modification 3 – Increase task funding for travel

Modification 4 – Add verbiage to replan subtasks 1, 2, 3, 6, and 7 due to launch and mission related delays.

Modification 5 – Removed modification 4 verbiage and adds Network Simulation Plan (NSP) requirement to Statement of Work.

Modification 6 – Update funding for subtask 9 to reflect 3/31/23 period of performance.

Modification 7 – Extend subtask 9 through 6/30/2023.

Modification 8 – Extend the Period of Performance thru October 31, 2024

II. Summary of Work

This task order defines requirements for Near Space Network (NSN) Human Space Flight (HSF) contractor-provided services for management of mission specific network requirements, assessments of network readiness for mission support and the technical integration of the NSN with HSF mission spacecraft and launch vehicles.

III. Period of Performance The period during which the work for this task shall be performed is award date through October 31, 2024.

IV. Task Description The task order is structured into the different HSF programs that NASA works with for all its HSF mission spacecraft and launch vehicles. Table 1 provides all vehicles and missions for the International Space Station (ISS) program, the Commercial Crew Program (CCP), the Artemis program, the Lunar Gateway program, the Human Lander System (lunar lander) program, the HSF demonstration missions, and the HSF commercial missions.

In addition, this task order will contain generalized Low Earth Orbit (LEO) and Lunar systems engineering support and up-front systems engineering efforts on behalf of both the HSF Network Director (ND).

into the M/VIDD mission requirements as applicable.

2.3 The contractor shall maintain legacy SLAs for HSF spacecraft, launch vehicles and missions noted in Table 1 as requested by the HSF ND or TM to do so.

2.4 The Contractor shall maintain legacy NSRDs for HSF spacecraft, launch vehicles and missions noted in Table 1 as requested by the HSF ND or TM to do so. If not requested to develop or maintain this document the contractor shall participate in the development of the document through providing input, review and comments to ensure technical accuracy. The contractor shall ensure adequate and accurate flow from the PRD into the NSRD as applicable.

2.5 With the M/VIDD, the Contractor shall lead the preparation, production and briefing of the Network Requirements Review (NRR) for HSF spacecraft, launch vehicles and missions noted in Table 1 as requested by the HSF ND or TM to do so. If not requested to lead the review the contractor shall attend and participate providing systems engineering support.

2.6 The Contractor shall lead the preparation and development of the Network Test Plan (NTP) for HSF spacecraft, launch vehicles, and missions noted in Table 1 as requested by the HSF ND or TM to do so. The contractor shall coordinate and oversee the execution of the NTP with the implementing and testing contracting team. If not requested to lead the NTP preparation and development, the contractor shall attend and participate providing systems engineering support.

2.7 The Contractor shall lead the preparation and development of the Network Simulation Plan (NSP) for HSF spacecraft, launch vehicles, and missions noted in Table 1 as requested by the HSF ND or TM to do so. The contractor shall coordinate and oversee the execution of the NSP in coordination with the HSF ND and Mission Managers.

2.8 The Contractor shall lead the preparation, production and briefing presentation of the Network Requirements Verification and Integration Status (NRVIS) for all HSF spacecraft, launch vehicles, and missions noted in Table 1.

2.9 The contractor shall develop, produce, and maintain a Concept of Operations (CONOPs) Architecture Design Document (CADD) for all HSF spacecraft, launch vehicles, and missions noted in Table 1.

2.10 The Contractor shall lead the preparation and production Network Operations Readiness Reviews (NORR) and Flight Readiness Reviews (FRR) briefing packages for HSF spacecraft, launch vehicles and missions noted in Table 1 as requested by the HSF ND or TM to do so. If not requested to develop or maintain this document the contractor shall participate in the development of

Table 1, per the request of the HSF ND or TM for all integrated HSF tests.

3.7 The Contractor shall develop, produce, and maintain integrated HSF operational procedures for real-time test and mission support.

3.8 The Contractor shall participate in formal spacecraft/launch vehicles design reviews, operational readiness, integration reviews and test readiness reviews (PDR, CDR, ORR, IRR, TRR etc.), as requested by the HSF ND or TM.

When participating in these reviews, the Contractor shall submit and track disposition of review item discrepancies (RIDs), as required.

3.9 The Contractor shall provide in-depth engineering review/analysis network elements’ upgrades/changes and the corresponding impacts to network operability with HSF spacecraft/launch vehicles/missions. The Contractor shall lead the related formal design, operational readiness, integration readiness, operational readiness, and test readiness reviews (PDR, CDR, ORR, IRR, TRR etc.) for the network elements, as requested by the HSF ND or TM.

When participating in these reviews, the Contractor shall submit and track disposition of review item discrepancies (RIDs), as required.

3.10 The Contractor shall provide integrated (end-to-end) analysis and assessments of network elements performance for new HSF spacecraft, launch vehicles, and missions, as requested by the HSF ND or TM.

3.11 The contractor shall provide surveillance and tracking of all network elements' anomalies and DRs directly impacting, or potentially providing a future impact, to HSF test or mission support.

3.12 The Contractor shall lead integrated analysis of all HSF related DRs, from initiation to closure. These activities include integrated HSF spacecraft, launch vehicles, and/or HSF mission support anomalies, including “fishbone” fault trees and Root Cause Corrective Action (RCCA) reports as requested by the HSF ND or TM.

3.13 The Contractor shall lead test or troubleshooting activities including test script content development. Real-time support shall be provided as requested by the HSF ND or TM.

3.14 The Contractor shall support the Network Support Group meetings at JSC and all ad-hoc technical interchange and working group meetings, per the request of the HSF ND or TM. All travel requirements shall be provided to the HSF ND or TM for review and approval.

3.15 The Contractor shall lead the preparation, production, and presentation of integrated Lessons Learned packages for the HSF spacecraft, launch vehicles, The contractor shall work in accordance with the Configuration Management Plan, as described in 450/ESC - Configuration Management Procedure.

The contractor shall interface directly with the Configuration Management and Documentation Specialist, supporting the HSF ND or TM.

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 HSF ND or TM, and implementing corrective actions with the compliance of the HSF ND or TM.

The contractor shall support the Human Space Flight Mission Manager team in the generation and content of risks, to be submitted to the Risk Management Board.

VI. Performance Metrics

Not applicable

VII. Government Furnished Facilities, Equipment, Software and Other Resources The Government shall provide a 4-seat office space at Goddard Space Flight Center for Contractor use.

The Government shall provide access to the NSOCC in Bldg. 13 at the Goddard Space Flight Center.

The Government shall provide access to NASA provided workstations for Contractor use.

The Government shall provide access to websites and portals, such as MCC-H Gateway, TDMS, and SharePoint, behind the NASA firewall.

VIII. Travel The Contractor shall propose travel that they identify as necessary to perform the work associated with this Task Order. All travel requirements shall be provided to the HSF ND or TM for review and approval. The proposed travel should include:

• Network Support Group meetings at JSC, twice per year

• Ad-hoc technical interchange and working group meetings, per the request of the Task Monitor

IX. Work Location The contractor work shall be performed at either the contractor’s facility or NASA locations around the United States that support the needs of the task order, development activities, engineering, and testing support. At a minimum, the work shall be performed at the following NASA locations:

• Goddard Space Flight Center (GSFC)

• Johnson Space Center (JSC)

X. Reporting Requirements

a. The contractor shall report status in person or via teleconference to the HSF ND or TM on a monthly basis.

b. Reports shall include informal presentation of interim results, status of development activities, and action item status.

c. The contractor shall provide all reports at least one day in advance of the monthly meeting via email and maintain an email distribution list with the concurrence of the T HSF ND or TM.

d. The contractor shall comply with any and all additional requests for status meetings and reports.

XI. Material Procurement The Contractor shall propose material that they identify as necessary to perform the work associated with this Task Order.

XII. Security Requirements

The contactor shall maintain security clearances for essential designated personnel up to TS/SCI level. Determination of personnel requiring clearances and required the clearance level shall be made in collaboration with the HSF ND or TM.

XIII. Rights

REQUIRED: In the execution of this Task Order, the Contractor shall utilize NASA Systems Engineering Processes and Requirements, via NPR 7123.1B, and the Networks Integration Process, via NASA 450-PG-1310.1.1 and relevant associated Work Instructions, as a framework for the Contractor’s processes at a minimum.

XIV. References The following applicable and reference documents shall be used for execution of this Task Order.