STO2 Space Relay Ops Services.pdf

Enclosure x – STO 2 RFP xx

Near Space Network (NSN) Services (NSNS) Operational Services

Sample Task Order (STO) Contract Number TBD

Task Order Statement of Work

Task Order Number: STO 2 Modification: 0 Task Name: Near Space Relay Operational Services Task Period of Performance: TBD Firm Fixed Price of Order: TBP

1. Overview and Description

1.1. The Near Space Network

NASA’s Near Space Network (NSN) fulfills the essential needs of user missions, empowering them with mission-critical communication and navigation services and enabling the transmission of science and exploration data to and from space. The goal of the Near Space Network Services (NSNS) contract is to provide NASA with a single avenue to procure communication and navigation services that are secure, reliable, and affordable, so that all NSN mission users will receive the services required by their mission within their latency, accuracy, and availability requirements.

1.2. Task Focus

This Sample Task Order (STO) focuses on all Near Space Relay communications and navigation services, defining the required operational services for all three service regions as defined in NSNS Statement of work (SOW).

1.3. Operations Services

The Contractor shall propose the price for the minutes of nominal and critical operational services as outlined in Table 1 of this STO. The government anticipates a breakdown of approximately 80% nominal minutes and 20% critical minutes.

The Contractor shall interoperate with IPv6 networks and components unless a waiver for IPv4 compatibility is requested by the Contractor and granted by the government.

The Contractor shall define and document the network address, port(s), and client/server role of the Contractor endpoint of each interface between NSN and the Contractor.

The Contractor shall provide terrestrial network connections in accordance with the SOW to the demarcation point at the NSN boundary.

The Contractor shall provide terrestrial network connections with a mean time to restore of at most 1 minute to the demarcation point at the NSN boundary.

The Contractor shall provide real-time link layer communications Services that will allow the relaying of data at the frame level in accordance with the SOW.

The Contractor shall provide real-time network layer services to provide end-to-end delivery of data over a series of multiple links in accordance with the SOW.

The Contractor shall provide interoperable store-and-forward communications services using Delay Tolerant Network (DTN) Bundle Protocol (BP) in accordance with the SOW.

The Contractor shall provide Messaging services that will provide a standard way for messages to be transferred directly over a link layer service or a network layer service in accordance with the SOW.

The Contractor shall be responsible for re-establishing dropped connections on any interface in which the Contractor endpoint operates in a network client role.

The Contractor shall configure and operate its network interfaces to NSN in compliance with the applicable NSN-Contractor Information Security Agreement (ISA), which will be consistent with the corresponding provisions of the NSN Security Plan.

The Contractor shall decrypt data provided by NSN in encrypted format as necessary to allow transport and processing of the data.

2.2. Services Management

The Contractor shall execute Service Management activities in accordance with the SOW.

2.2.1. Service Scheduling

The Contractor shall provide resource availability period data to NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of resource availability period data.

The Contractor shall provide updated resource availability period data to NSN no later than 30 minutes after a change to the availability of a Contractor resource.

The Contractor shall receive the deconflicted Tentative Schedule provided by NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of the deconflicted Tentative Schedule.

The Contractor shall receive the service configuration data provided by NSN together with the deconflicted Tentative Schedule.

The Contractor shall provide Tentative Schedule acceptance notifications to NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of Tentative Schedule acceptance/rejection notifications.

The Contractor shall receive the Operational Schedule provided by NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of the Operational Schedule.

The Contractor shall receive the service configuration data provided by NSN together with the Operational Schedule.

2.2.2. Acquisition Support

The Contractor shall receive the spacecraft acquisition data provided by NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of acquisition data.

The Contractor shall receive and respond to requests for in-service reconfiguration provided by NSN.

The Contractor shall define the electronic data interchange format and protocol for delivery of in-service reconfiguration requests.

The Contractor shall respond to the in-service reconfiguration request within 40 seconds of receipt.

2.3. Monitor and Control

The Contractor shall execute Monitor and Control activities in accordance with the SOW.

The Contractor shall provide service execution monitoring data to NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of service execution monitoring data.

The Contractor shall update service execution monitoring data no less than once per second while a service is active.

The Contractor shall provide updated service execution monitoring data no less than once per minute when such data is provided via an Electronic Data Interchange (EDI) format and protocol aggregates multiple data points across a time interval.

The Contractor shall provide updated service execution monitoring data no less than once per second when such data is provided via an EDI format and protocol that does not aggregate multiple data points across a time interval.

The Contractor shall provide forward service performance data to NSN.

The Contractor and the NSN shall agree on the EDI format and protocol for delivery of forward service performance data.

The Contractor shall update forward service performance data no less than once per second while a forward service is active.

The Contractor shall provide updated forward service performance data no less than once per minute when such data is provided via an EDI format and protocol aggregates multiple data points across a time interval.

The Contractor shall provide updated forward service performance data no less than once per second when such data is provided via an EDI format and protocol that does not aggregate multiple data points across a time interval.

The Contractor shall provide return service performance data to NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of return service performance data.

The Contractor shall update return service performance data no less than once per second while a return service is active.

The Contractor shall provide updated return service performance data no less than once per minute when such data is provided via an EDI format and protocol aggregates multiple data points across a time interval.

The Contractor shall provide updated return service performance data no less than once per second when such data is provided via an EDI format and protocol that does not aggregate multiple data points across a time interval.

The Contractor shall provide monitoring data for assets used to support scheduled services to NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of asset monitoring data.

The Contractor shall provide notifications of conditions that affect scheduled services to NSN.

The Contractor and the NSN shall agree on the electronic data interchange format and protocol for delivery of notifications of conditions.

2.4. Service Execution

The Contractor shall perform Service Execution activities in accordance with the SOW.

2.4.1. Forward Data Delivery Service

The Contractor shall receive forward service data provided at the NSN demarcation boundary.

The Contractor shall receive real-time forward service data via a network-based online delivery mechanism.

The Contractor shall receive real-time forward service data at a rate consistent with the typical performance of terrestrial network links.

The Contractor shall receive non-real-time forward service data via a file transfer mechanism.

The Contractor shall be capable of receiving forward service data having the characteristics necessary to support Earth Proximity, GEO-to-Cislunar, and xCislunar Space Relay forward services, including applicable Space Internetworking Services per the SOW.

The Contractor shall deliver forward service echo data to the NSN demarcation boundary.

The Contractor shall deliver real-time forward service echo data via a network-based online delivery mechanism.

2.4.2. Return Data Delivery Service

The Contractor shall deliver return service data to NSN demarcation boundary.

The Contractor shall deliver real-time return service data via a network-based online delivery mechanism.

The Contractor shall deliver non-real-time return service data via a file transfer mechanism.

The Contractor shall provide an Earth Receive Time (ERT) with all return service data.

The Contractor shall provide an ERT for each discrete unit of data delivered by a particular return service, including, but not limited to, an individual frame or packet for services that deliver frames or packets; an individual sample for services that deliver digitized IF samples; and an individual file for services that deliver reconstructed files.

The Contractor shall be capable of delivering return service data having the characteristics necessary to support Earth Proximity, GEO-to-Cislunar, and xCislunar Space Relay return services, including applicable Space Internetworking Services in accordance with the SOW.

The Contractor shall be capable of receiving return service data having the characteristics necessary to support Earth Proximity, GEO-to-Cislunar, and xCislunar Space Relay return services, including applicable Space Internetworking Services in accordance with the SOW.

2.4.3. Position, Navigation, and Timing (PNT) Services

The Contractor shall provide Near Space Relay Position, Navigation and Timing (PNT) services to users in accordance with the SOW.

The Contractor shall deliver tracking service data to NSN demarcation boundary.

The Contractor shall deliver real-time tracking service data via a network-based online delivery mechanism.

The Contractor shall deliver non-real-time tracking service data via a file transfer mechanism.

The Contractor shall be capable of delivering tracking service data having the characteristics necessary to support Earth Proximity, GEO-to-Cislunar, and xCislunar Space Relay return services, including applicable Space Internetworking Services in accordance with the SOW.

The Contractor shall be capable of receiving tracking service data having the characteristics necessary to support Earth Proximity, GEO-to-Cislunar, and xCislunar Space Relay return services, including applicable Space Internetworking Services in accordance with the SOW.

2.5. Operational Support Services

The Contractor shall coordinate service requirements, expectations, and activities with NSN while onboarding NSN user missions.

The Contractor shall provide mission onboarding coordination to include service preparation plans, spectrum licensing, and compatibility testing.

The Contractor shall support the government to perform a link budget analysis for each NASA Mission in operational control.

The Contractor shall support the government to determine network resources have geometric line-of-sight visibility with the customer during the required service times.

The contractor shall support the government to evaluate the effects on the existing and projected network load and the network’s ability to meet customer commitments.

The Contractor shall support the government to assess and document new mission support requirements and identify new or mission unique service capabilities or configurations.

The Contractor shall support the government to integrate, test, verify, validate, and transition to operations configuration changes, upgrades, enhancements, interface changes, and new customer data flows.

The Contractor shall conduct integrated network testing, compatibility testing and technical exchange meetings (TEM) with the government to validate and verify new user service requirements.

The Contractor shall obtain the required frequency authorizations and licenses for the frequencies they will be supporting.

The Contractor shall be responsible for maintaining compliance with appropriate national and local authorization and licensing requirements and regulations for operations outside of the US.