Attachment A - SOW.pdf

DRFP# 80GSFC22R0029

Attachment A

NEAR SPACE NETWORK

SERVICES

STATEMENT OF WORK

DATE: JUNE 2022

Contents

1. Introduction

1.1. Introduction

1.2. Background

1.3. Near Space Network Services (NSNS) Objectives

1.4. NSNS Scope and Structure

1.5. Definitions & Terminology

1.5.1. Near Space Region

1.5.2. Availability

1.5.3. Proficiency

1.5.4. Latency

1.5.5. Mean Time to Restore

1.5.6. Nominal Services

1.5.7. Critical Services

1.5.8. Secure

1.6. Spectrum Management

2. Process

2.1. NSNS Task Order (TO) Structure

2.2. Capability Validation Task Orders

2.3. Operational Services Task Orders

2.4. Mission Integration and Special Studies (MI&SS) Task Orders

2.5. Mission Unique Requirements Task Orders

3. Management Requirements

3.1. Program Management

3.1.1. Reviews

3.1.2. Risk Management

3.1.3. Export Control

3.1.4. Configuration Management

3.1.5. Controlled Unclassified Information (CUI)

3.1.6. Classified Information

3.1.7. Information Technology and Security

3.1.8. Spectrum Management

3.1.9. Safety, Reliability, and Quality Assurance

3.2. Capability Validation

3.2.1. Capability Validation Success Criteria

3.3. Operational Services

3.3.1. Nominal Services

3.3.2. Critical Services

3.3.3. Mission On-boarding

3.3.4. Mission Analysis and Planning

3.3.5. Mission Integration

3.3.6. Operational Services Success Criteria

3.4. Mission Integration and Special Studies Task Orders (MI&SS)

4. Technical Requirements

4.1. Overarching Requirements for All Services (DTE and Space Relay)

4.1.1. Functional Requirements

4.1.2. Performance Requirements

4.2. Category 1 Direct to Earth (DTE) Services

4.2.1. Performance Requirements for all Category 1 DTE Services

4.2.2. Category 1.1. Earth Proximity (EP) DTE Services

4.2.3. Category 1.2: GEO to Cislunar DTE Services

4.2.4. Category 1.3: xCislunar DTE Services

4.3. Category 2 Space Relay Services

4.3.1. Category 2.1: Earth Proximity (EP) Relay Services

4.3.2. Category 2.2: GEO to Cislunar Relay Services

4.3.3. Category 2.3: xCislunar Space Relay Services

Appendix A – NSN Secure Interfaces

Appendix B – Related Documentation

Applicable Documents

Reference Documents

NASA Information Security Policy

Appendix C – Acronyms

Figures Figure 1 NSNS Service Categories Figure 2 NSNS Service Regions Figure 3 Proficiency Example Figure 4 Top Level Task Order Structure Figure 5 Validation Task Order Structure Figure 6 Operational Services Task Order Figure 7 Mission Integration and Special Studies Task Order Figure 8 NSN Interfaces

Tables Table 1 Category 1 NSNS Near Space Direct to Earth (DTE) Services Table 2 Category 2 NSNS Near Space Relay Services Table 3. Summary of Interfaces and Capabilities Table 4 Scheduling Table 5. Monitor and Control – Asset and Service Configuration and Status Table 6. Monitor and Control – Operational Status Notification and Coordination Table 7. Platform Requirements – All Categories Table 8 Performance Requirements for All Categories of Service Table 9 Category 1 DTE, GEO to Cislunar and xCislunar Related Orbits Table 10. Forward Data Service Performance – DTE Table 11. Return Data Service Performance – DTE Table 12. Tracking Performance – DTE Table 13. Mission Service Interfaces and Capabilities – Data Forward – Earth Proximity DTE Table 14. Mission Service Interfaces and Capabilities – Data Return – Earth Proximity DTE Table 15. Mission Service Interfaces and Capabilities – Tracking – Earth Proximity DTE Table 16. Typical Forward RF Signal Performance – Earth Proximity DTE Table 17. Typical Return RF Signal Performance – Earth Proximity DTE Table 18. Mission Service Interfaces and Capabilities – Data Forward – GEO to Cislunar DTE Table 19. Mission Service Interfaces and Capabilities – Data Return – GEO to Cislunar DTE Table 20. Mission Service Interfaces and Capabilities – Tracking – GEO to Cislunar DTE Table 21. Typical Forward RF Signal Performance – GEO to Cislunar DTE Table 22. Typical Return RF Signal Performance – GEO to Cislunar DTE Table 23. Mission Service Interfaces and Capabilities – Data Forward – xCislunar DTE Table 24. Mission Service Interfaces and Capabilities – Data Return – xCislunar DTE Table 25. Mission Service Interfaces and Capabilities – Tracking – xCislunar DTE Table 26. Typical Forward RF Signal Performance – xCislunar DTE Table 27. Typical Return RF Signal Performance – xCislunar DTE Table 28. Mission Service Interfaces and Capabilities – Data Forward Link Bands – GEO to Cislunar Space Relay Table 29 SLP to NSN Interfaces Table 30 Data Service Standards Table 31 Navigation Service Standard Table 32 Scheduling Management Standards Table 33 Acquisition Data Standards Table 34 Service Monitoring and Accounting Standards Table 35. Applicable Documents Table 36. Reference Documents

1. Introduction

1.1. Introduction

This Statement of Work (SOW) describes the scope of work to be performed by the Contractor for Contractor-provided communication and navigation services in support of the National Aeronautics and Space Administration (NASA) under the Near Space Network Services (NSNS) Contract. Services are defined as communication and navigation services required to provide NASA the capability to support mission users with contractor-provided communication and navigation assets. This SOW requires the Contractor to develop and conduct validation activities for communications and navigation capabilities and services for Near Space Network (NSN) to support multiple missions, and upon completion of the services validation transition the service to operations. The Contractor will provide data deliverables and insight to support capability validation, operational services, and mission integration to NSN.

1.2. Background

The Exploration and Space Communications (ESC) projects division at NASA’s Goddard Space Flight Center (GSFC) provides full-coverage communications and navigation services, as well as cross-cutting technical expertise to move NASA forward into the future. These services are critical to operating NASA’s many robotic spacecraft and human exploration missions, as well as returning ground-breaking scientific data to Earth where it can be used for the benefit of humanity. To execute its mission, ESC supports the Space Communications and Navigation (SCaN) program office at NASA Headquarters to effectively implement their vision. SCaN is a part of the Space Operations Mission Directorate (SOMD) and provides programmatic oversight of NASA’s networks, advanced communication technologies, and other space communications requirements. These capabilities support missions that are funded, sponsored, or operated in conjunction with NASA, providing critical connectivity from spacecraft to the ground.

NASA’s NSN is positioned within the ESC organization and fulfills the essential needs of user missions, empowering them with mission-critical communications and navigation services and enabling the transmission of science and exploration data to and from space. As a single point of service for missions in the near space region — out to two million kilometers (km) from Earth — the network currently connects users using either government or commercial service providers.

As a single, end-to-end network, the NSN orchestrates communications and navigation services, space links, and data transport for users. Additionally, NSN serves missions throughout their entire lifecycle, providing requirements analysis, spectrum management, communications analysis, service agreements, mission design, mission planning, and support for launch, operations, and post-mission activities. As a result, NSN ensures its users have robust and reliable communications and navigation services that fully support their mission objectives.

1.3. Near Space Network Services (NSNS) Objectives

The goal of the NSNS procurement 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. Secure is defined as having integrity, confidentiality, and availability.

The objectives of the NSNS contract are to:

• Provide affordable, accurate, secure, and timely delivery of communication and navigation services from multiple vendors for existing and future NASA scientific, technology and human spaceflight missions from the Earth’s surface up to 2 million km, including those on the lunar surface or in lunar orbit.

• Deliver communication and navigation services that ensure astronaut safety and meet performance and mission assurance objectives for both human and robotic missions.

• Solicit commercial vendors to validate their ability to provide communication and navigation services such that all users receive the services required by their mission within latency and accuracy requirements.

• Offer opportunities for commercial vendors, after capability validation, to be considered for follow-on operational services.

• Provide a mechanism to regularly incorporate new communication and navigation services, technology upgrades, and improved processes and products through an on-ramp feature that allows for additional awards and further competition as industry develops additional capabilities.

• Encourage development of commercial capabilities that provide services to a diverse range of mission customers, of which NASA will be only one.

• Foster competition and create opportunities for new, emerging communication and navigation service providers.

1.4. NSNS Scope and Structure

Paramount to the success of NASA missions, procured communication and navigation services must provide quality connectivity between and among user spacecrafts, relay satellites, surface networks, and ground stations capable of meeting mission requirements. The NSNS SOW separates the procurement of the desired Near Space communication and navigation capabilities into two categories as shown in Figure 1:

• Category 1: Near Space Direct to Earth (DTE) Services: Secure services for orbital and sub-orbital scientific, technology and human spaceflight missions – ground assets that provide line of sight communications and tracking services to missions ranging from the Earth surface and extending out to 2 million km from Earth.

• Category 2: Near Space Relay Services: Secure Space-based asset services for customer missions, spacecraft, or payloads up to 2 million km from Earth which relay critical mission data between spacecrafts/satellites and ground stations to support scientific, technology and human spaceflight missions.

Figure 1 NSNS Service Categories

The NSNS SOW further divides the two Near-Space communication and navigation services categories into three Service Regions as shown in Figure 2. The three Service Regions are:

• Region 1: Earth Proximity: Altitudes from the Earth’s surface to Geosynchronous Earth Orbit

(GEO).

• Region 2: GEO to Cislunar: Altitudes from GEO to 500,000 km. This region includes users on the lunar surface, and users in the Earth-Moon Lagrange points (EML labels).

• Region 3: xCislunar: Includes the remainder of Near Space altitudes from 500,000 km to 2 million km. This region includes the Earth-Sun L1 and L2 points (SEL labels).

Figure 2 NSNS Service Regions interest within this volume (e.g., Sun-Earth and Earth-moon Lagrange points) utilized to conduct spaceflight missions and/or provide the services (e.g., PNT) needed by the nation’s explorers.

1.5.2. Availability

Availability is defined as the percentage of time service is provided to a nominal or critical scheduled event (excludes emergency services) divided by the requested scheduled service time. Lost service due to automated or manual failover to restore service will be considered as lost service. Scheduled corrective or preventive maintenance will not be factored into the percentage of availability since it is assumed these activities will not impact nominal services, however, unscheduled corrective maintenance that impacts scheduled services will be factored into the availability percentage.

1.5.3. Proficiency

Proficiency will be determined based on the window of scheduled support time and will be calculated by dividing the amount of time good data was received during the scheduled window by the sum of the amount of time good data was received during the window and the amount of time bad data was received during the scheduled window (Good Data /(Good Data + Bad Data)).

Figure 3 Proficiency Example

1.5.4. Latency

Latency is defined as the amount of time (measured in seconds) from when a signal leaves a mission user transmitter antenna to the time it is delivered to the NSN interface or to the satellite mission’s data processing system/control center, whichever is specified in the Mission Data Workbook.

1.5.5. Mean Time to Restore

Mean Time To Restore (MTTR) is defined as the average elapse time required to restore a nominal or critical service back to an operational state. MTTR should be computed based upon the recovery of a service vice and individual component and should include both terrestrial and spaced based assets in the computations.

1.5.6. Nominal Services

Normal Services cover typical and regular mission user activities such as telemetry, command and science/payload data, momentum management, clock maintenance, memory dumps or other onboard processor management, instrument calibration, and subsystem reconfigurations not covered by onboard autonomy.

1.5.7. Critical Services

Critical Services include communication and navigation services that must provide reliable and secure services at all times during mission critical phases without degradation of performance. Any function or group of functions is deemed mission critical if its failure will result in a situation whereby the spacecraft cannot be recovered by ground. Examples of Critical Services include Launch, early orbit ops, human spaceflight, descent, and spacecraft contingency.

Critical services encompass both Contingency and Emergency activities.

Contingency activities will occur when the user mission platform experiences a failure or degradation in function or performance that affects normal data collection, or otherwise compromises the health and safety of the system. Anomalies could be sudden, discrete events, such as the failure of a critical component, or could be a gradual degradation in performance detected by engineering trending that permits action prior to the occurrence of a mission-threatening situation. Contingency Services include all of the activities performed during Normal Services, plus additional items such as configuration management, and other troubleshooting services as needed.

Emergency activities are a response to an unexpected anomaly that if not responded to in a timely manner would result in loss of mission, or in the case of Humans Spaceflight activities, Loss of life. Emergency service requests will be coordinated by the NSN Project directly with Space Link Providers (SLP) to receive immediate communications services to prevent loss of their user mission platform, enable safing, restore normal operations, and preserve life.

1.5.8. Secure

Secure means contractors shall reinforce the need for confidentiality, integrity, and availability of the systems, data and communication pathways that will support the requirements of this contract. These protections shall be ensured using a combination of software and hardware that prevents unauthorized access as well as corruption, interception, and loss of data. The contractor shall ensure the following during the performance of this contact:

• Confidentiality - Defined as preserving authorized restrictions on information access and disclosure, including ensuring the means for protecting personal privacy and proprietary information from access and disclosure.

• Integrity - Defined as guarding against improper information modification or destruction and includes ensuring information non-repudiation and authenticity.

• Availability - Defined as ensuring timely and reliable access to and use of information.

1.6. Spectrum Management

All spacecraft communication links with ground networks must be coordinated, licensed, and internationally registered prior to operation as required in the (ITU) Radio Regulations. International frequency spectrum allocations are decided by World Radio Communication Conferences convened under the auspices of the ITU and resulting allocation decisions are incorporated into the Radio Regulations, a treaty that requires ratification by the United States. Management of the radio frequency spectrum within the US is divided between government and non-government users. The NTIA administers government allocations (including NASA), and the FCC manages non-governmental allocations. NASA is a member of the NTIA’s Interdepartmental Radio Advisory Committee to coordinate US spectrum allocation issues. US allocations relevant to NSN are consistent with international allocations but may also include additional limitations and constraints.

2. Process

2.1. NSNS Task Order (TO) Structure

The NSNS contract will order DTE and Space Relay services through a series of TOs listed below and shown in Figure 4.

• Capability Validation TOs

• Operational Services TOs

• Mission Integration and Special Studies (MI&SS) TOs

Specific mission requirements will be defined in the TO issued for each mission or set of missions. The NSN Services may be tailored, as needed, to meet the unique needs of each mission.

The Government will periodically perform a market analysis as industry develops additional DTE and Space Relay capabilities, technological advancements, and maturation in this space. If warranted, the government will issue requests for proposals to on-ramp additional vendors as industry emerges with new candidates and capabilities, and to accommodate mission specific needs.

Figure 4 Top Level Task Order Structure

2.2. Capability Validation Task Orders

Contractor-owned and operated communication and navigation ground systems and space relays must be validated to ensure that the quality of service is consistent with user needs for operational support.

After receiving a Capability Validation TO award, Capability Validation activities culminate in a System Validation Review that validates the Contractor’s hardware, software, personnel, and procedures are ready to provide operational communication and navigation services to NASA. The Contractor presents results of validation analyses and tests for Government approval. The Contractor is responsible for planning, scheduling and conducting design and milestone reviews in support of the NSNS contract.

Capability Validation Milestone (CVM) success reviews are conducted for the purpose of assessing programmatic and technical progress. The reviews, to be conducted by the Contractor, will be attended by NASA. The milestones, as shown in Figure 5, use a stepwise approach to validation and provide the Government with insight into Contractor activities on the path towards capability validation, as well as serving as Government approval points on the path to final capability validation. Upon successful completion of all seven CVM success reviews, the Contractor is eligible to compete for Operational Services and MI&SS TOs which are described below.

Figure 5 Validation Task Order Structure

2.3. Operational Services Task Orders

Operational Services are activities that provide operational communication and tracking services to user missions. Operational Services TOs will be released periodically, defining the current Government need for ongoing operational services. Once the Contractor validates their services meet all NASA requirements through completion of a Capability Validation TO, the Contactor is eligible to compete for Operational Services TOs.

Figure 6 below shows the nominal flow of activities for the Operational Services TO.

Figure 6 Operational Services Task Order

2.4. Mission Integration and Special Studies (MI&SS) Task Orders Mission Integration and Special Studies (MI&SS) task orders are Indefinite delivery, indefinite quantity (IDIQ) tasks identified by the Government to address a specific need that requires Contractor support.

This category of TO is used when the Government requires the Contractor to perform special studies, mission analysis for new missions, dedicated testing, or other requested Contractor activities. When the Government identifies a specific need, the Government will issue a Mission Integration and Special Studies (MI&SS) TO describing the scope of work to be performed. Mission Integration and Special Studies ensure assets configurations meet missions support requirements and are available for end-to-end testing prior to launches. Example MI&SS activities include Communication Link analysis, coverage and feasibility analysis, compatibility analysis, and integration activities.

Figure 7 below shows the nominal flow of activities for the Operational Services TO.

Figure 7 Mission Integration and Special Studies Task Order

2.5. Mission Unique Requirements Task Orders

For Controlled Unclassified Information Unique Requirements, and when specifically requested by the Government, Contractors that have successfully completed validation shall provide unique unclassified specific requirements as described in the Task Order (TO) SOW. The TO SOW with the specific unique requirements will be issued by the Government in accordance with the ordering procedures contained in the contract. Only when requested and approved by the Government for Unclassified requirements, the Contractor may use the NTE per minute rates captured under Attachment B for the specified subcategory, as a baseline for the pricing of the individual task orders.

For Classified Requirements (3.1.6 of this statement of work), only Contractors that have successfully completed validation and are in possession of a valid Facility Clearance in accordance with the Security Requirements of the contract and Attachment G, shall provide unique classified specific requirements as described in the TO SOW. Classified unique requirements are not subject to the limitations of Attachment B, rather shall be used as a baseline to meet the unique classified mission requirements.

3. Management Requirements The requirements captured in Section 3, and all its subsections, apply to all task orders issued under this contract.

3.1. Program Management

The Contractor shall perform all Program Management functions required to deliver the full scope of each awarded service. The Contractor shall ensure all contract and TO terms, conditions, and requirements are met.

The Contractor shall perform all the necessary program management functions in order to plan, implement, execute, track, and report progress of work tasked, and manage risks.

The Contractor shall monitor, and status performance summarizes at the Contract level, including objective measures of technical, schedule, and cost performance.

The Contractor shall provide TO processing and status performance as specified in TOs.

During the period of performance, the Contractor shall provide services for changing parameters and missions as specified in TOs.

3.1.1. Reviews

The Contractor shall conduct milestone reviews for Capability Validation in accordance with Section

3.2.1 of this SOW.

3.1.2. Risk Management

The Contractor shall execute a continuous risk management process to be able to identify any risk associated with providing NSN services in a timely manner and contribute to risk mitigations.

The Contractor shall provide inputs to the NSN risk management process and proactively identify any risk to providing DTE or Relay services and any associated mitigations.

3.1.7. Information Technology and Security

The contractor shall perform an annual assessment in accordance with NIST SP 800-171 or ISO 27002 and provide it to the Government for review and concurrence

Evidence of compliance shall be presented by the Contractor at specific milestones during the program lifecycle, and on an annual basis outside of these milestones.

The contractor shall complete an Interconnection Security Agreement (ISA) with any information system that is authorized by a different organization or Authorizing Official (AO).

The Contractor shall notify the NSOCC personnel of cybersecurity incidents within 30 minutes of discovery and provide remediation timelines and on-going daily reporting on all required incident response activities involving NASA data or information systems.

The contractor shall use Fedramp approved Cloud services for all systems that are processing and or transporting data associated with NSN services.

The contractor shall participate in NSN end to end threat assessments.

The contractor shall conduct network administration, system administration, IT (Information Technology) support services, system maintenance, IT security functions, and other ancillary IT tasks to support contractual requirements and ensure the security of systems.

The Contractor shall have systems capable of connecting to NASA’s mission network, including services provider systems that comply with:

• Internet Protocol Operational Network (IONet) Access Protection Policy and Requirements, 290-

• Internet Protocol Operational Network (IONet) Access Control Compliance Checklist, CHECKLIST

3.1.8. Spectrum Management

The Contractor shall ensure compliance with International Telecommunications Union (ITU), Federal Communications Commission (FCC), and National Telecommunications and Information Administration (NTIA) spectrum regulations as applicable.

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.

3.1.9. Safety, Reliability, and Quality Assurance

The contractor shall maintain OSHA certification for facilities and activities within the United States.

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

3.2. Capability Validation

The Contractor shall validate their ability to provide services in each of the subcategories as described in Section 1.4, Table 1 and Table 2, via a Capability Validation TO.

The Contractor shall perform a set of activities associated with distinct milestones that culminate in a Service Validation Review that validates the Contractor’s hardware, software, personnel, and procedures are ready to provide operational communication and navigation services to NASA.

The Contractor shall progress through the seven Capability Validation TO milestones illustrated in Figure

5. Nominally each milestone must be completed before work can begin on the next milestone, however, a contractor may propose to combine milestones.

The Contractor shall perform all tasks necessary to provide end-to-end communication and navigation services between NASA’s NSN (see Appendix A – NSN Interfaces) and user platforms. In this context, “user platform” refers to a platform owned and/or controlled by a user mission, see the Mission Data Workbook (MDWB), that utilizes NSN services.

The Contractor shall be responsible for planning, scheduling, and conducting design and milestone reviews in support of the NSNS contract.

3.2.1. Capability Validation Success Criteria

Capability Validation Milestone (CVM) success reviews shall be conducted for the purpose of assessing programmatic and technical progress and contract performance at key decision points and phases in the lifecycle.

The Contractor shall complete all Capability Validation activities in accordance with the awarded Capabilities Validation TO.

The Contractor shall meet the following Capability Validation Success Criteria for each milestone and complete all seven milestones within the period of performance for a given service identified in the applicable TO. Contractors are encouraged to complete the Capability Validation TOs earlier than the Not to Exceed (NTE) Period of Performance listed in the TO and can satisfy multiple milestones concurrently with government approval.

Between milestones, the Contractor shall host periodic Technical Exchange Meetings (TEMs) with the Government to discuss status, progress, and risks.

Data items to be reviewed at the various CVMs may be in the Contractor format and, unless specified otherwise, may be provided to NASA via access to an online system.

Sections 3.2.1.1. through 3.2.1.7 provide general milestone requirements the Contractor is expected to meet during capability validation. However, awarded TOs will provide the detail requirements the Contractor shall accomplish to successfully complete each milestone and the Capability Validation TO.

3.2.1.1. Capability Validation Milestone-01 – Service Concept To complete the Service Concept Milestone (CVM-01) the Contractor shall describe how their operations concept, system architecture, and other support functions required for secure Communications and Navigations services will operate.

3.2.1.2. Capability Validation Milestone-02– Service Requirements To complete the Service Requirements Milestone (CVM-02) the Contractor shall specify how the NSN requirements for each of the sub-category of secure services under consideration will be met.

The Contractor shall provide a Service Requirements definition as part of completing CVM-02. The Services Requirements definition shall define the boundaries of the commercial system including the demarcation points between the Contractor service infrastructure and the Government’s external interface.

3.2.1.3. Capability Validation Milestone-03 – Service Design

To complete the Service Design Milestone (CVM-03) the Contractor shall document the status of the design and accomplishing activities such as functional allocation of system requirements to services and identifying verification methods for interface requirements to validate that the maturity and ability of the service is sufficient to support secure operational services.

3.2.1.4. Capability Validation Milestone-04 – Service Integration To complete the Service Integration Milestone (CVM-04) the Contractor shall validate that the contractor provided systems are on schedule to be integrated and technical plans and procedures are on schedule to support secure integration.

3.2.1.5. Capability Validation Milestone -05 – Service Test

To complete the Service Test Milestone (CVM-05) the Contractor shall validate their system is sufficiently mature to safely conduct integrated tests between their system and the Government NSN resources and to ensure that the secure service is ready to enter verification testing.

3.2.1.6. Capability Validation Milestone-06 – Service Verification To complete the Service Verification Milestone (CVM-06) the Contractor shall conduct a Verification test to verify their systems and secure services are compliant with the NSN service requirements.

Verification tests are the official “for the record” testing performed on a system to show that it meets its allocated requirements or specifications including physical and functional interfaces.

3.2.1.7. Capability Validation Milestone-07 – Service Validation To complete the Service Validation Milestone (CVM-07) the Contractor shall validate the effectiveness and suitability of their secure service for use in mission operations and the service is operating as expected.

To complete the CVM-07 the Contractor shall pass a review which validates that the Contractor’s hardware, software, personnel, and procedures are ready to provide operational communication and navigation services to NASA spacecraft and payloads. The CVM-07 review will validate readiness using the Mission Data Workbook as a reference.

At this milestone, the Contractor shall provide evidence that they have performed all tasks necessary to validate their ability to provide communication and radiometric tracking services for all mission users.

3.3. Operational Services

Upon award of an Operational Services TO, the Contractor shall provide secure DTE or Relay communications services along with either Radiometric tracking data or a Position, Navigation and Timing (PNT) signal for awarded missions as defined in the TO. Before the contractor can be awarded a

TO for Operational Services for a given subcategory described in Section 1.4, Table 1 and Table 2, the Contractor shall complete a Capability Validation TO for the same subcategory validating they can successfully deliver secure services meeting all mission requirements.

Under an Operations Services TO, the contractor shall provide both Nominal and Critical services as described in Sections 1.5.6 and 1.5.7 and per the requirements in Sections 3.3.1 and 3.3.2.

3.3.1. Nominal Services

The Contractor shall allocate resources to Nominal Service request based on awarded contract language.

The Contractor shall propose pricing for nominal operations services for each subcategory.

3.3.2. Critical Services

During Critical Services, the Contractor shall respond within 30 minutes to service request and coordinate directly with NASA personnel to minimize mission impact.

Critical Service request shall be treated by contractors as having priority over any nominal service request by other users of the requested asset.

If the Critical Service request is to respond to an emergency, the Contractor shall respond in real-time.

Additionally, the Critical Service request shall be given absolute priority for the requested resource by the contractor regardless of any other contractual requirement they may have.

The Contractor shall provide engineering support when NASA declares a spacecraft emergency or contingency on a mission user spacecraft or payload.

The Contractor shall propose pricing for critical operations services for each subcategory.

3.3.3. Mission On-boarding

When on-boarding a new mission, the Contractor shall coordinate requirements, expectations, and activities with the government. This coordination includes the interface control document, Interconnection Security Agreement (ISA) service preparation plan, test plans, and licensing, among other support activities.

The contractor shall successfully perform RF compatibility testing with the onboarding spacecraft.

3.3.4. Mission Analysis and Planning

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

The contractor shall perform modeling analysis that determines what network resources have geometric line-of-sight visibility with the customer during the required service times.

The contractor shall perform a modeling analysis to determine if their network has the ability to provide services to the specific mission being on-boarded.

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

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

The Contractor shall conduct integrated network testing to validate and verify new user requirements for services.

3.3.5. Mission Integration

Mission Integration activities may occur under either an Operational Services TO or a MI&SS TO depending on the mission’s requirements at the discretion of the government.

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

The Contractor shall conduct interface compatibility analysis and testing to verify and validate that the user’s mission interfaces are compatible with the configurations of the Contractor’s hardware, software, and firmware.

The Contractor shall conduct integrated networks testing to validate and verify new customer requirements for services from the integrated networks.

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

3.3.6. Operational Services Success Criteria

The Contractor shall provide secure operational services in accordance with section 4, and all its relevant subsections, below.

3.4. Mission Integration and Special Studies Task Orders (MI&SS) TOs for MI&SS will be released when the Government identifies a specific need that requires Contractor support. Once the Contractor validates their services meet all NASA requirements through completion of a Validation TO, the Contactor is eligible to compete for MI&SS TOs for that subcategory.

The Contractor shall perform special studies, mission analysis for new missions, dedicated testing, or other requested Contractor activities as specified in the MI&SS Task Order.

The government expects it will only award MI&SS TOs for mission integration activities when the new mission has unique requirements that the Contractor has not previously validated.

In accordance with the task ordering procedures in this contract, the Contractor shall perform NSNS-related tasks such as special studies, analysis, and/or support tasks as initiated by written direction from the Contracting Officer. Details of each task will be fully defined in the MI&SS TO when it is issued.

4. Technical Requirements

4.1. Overarching Requirements for All Services (DTE and Space Relay)

4.1.1. Functional Requirements

The Contractor shall validate their services can meet the following functional requirements to successfully complete a Capability Validation TO and/or perform an Operational Services TO for any of the requested secure services in Table 1 and Table 2.

4.1.1.1. Management Functions and Interfaces

The Contractor shall provide the following mission management support functions identified in Table 3.

Table 3. Summary of Interfaces and Capabilities

Mission Service Interfaces and Capabilities

Mission Data Forward Mission Data Return Tracking (Category 1, DTE services only) PNT (Category 2, Relay services only)

Management Interfaces and Capabilities

Scheduling – Resource Availability Scheduling – Resource Request and Confirmation Scheduling – Spacecraft Acquisition Data Monitor and Control – Asset and Service Configuration Monitor and Control – Asset and Service Status Monitor and Control – Operational Status Notification Monitor and Control – Operational Coordination

4.1.1.2. Scheduling

The Contractor shall provide the following scheduling capabilities for Resource Availability, Resource Request and Confirmation, and Spacecraft Acquisition Data identified in Table 4:

Table 10. Forward Data Service Performance – DTE

Forward Data Delivery Latency

Real-time

Forward Data Delivery Jitter

≤ 0.1% of nominal symbol rate

Table 11. Return Data Service Performance – DTE

Return Data Quality Bit-error rate (BER) no more than 1.0E-5, or equivalent frame error rate

(FER)

Return Data Delivery Latency

Real-time services: SLA threshold varies by mission; performance target is < 6 seconds (best effort) and < 15 seconds (maximum)

Non-real-time services: SLA threshold varies by mission Return Data Delivery Jitter

≤ 0.1% of nominal symbol rate

Return Data ERT Accuracy

No more than 50 microseconds at data rates above 1 ksps

4.2.1.2. DTE Tracking Performance

The Contractor shall provide secure DTE services that meet or exceed the following Tracking Performance requirements as indicated in Table 12.

Table 12. Tracking Performance – DTE

Antenna Travel Range >360 deg azimuth continuous 0-90 deg elevation

Antenna Tracking Rate 0.5 deg/s

Autotrack Accuracy ±0.2 dB of beam peak

Timing Reference Short term stability better than 10E-14

4.2.2. Category 1.1. Earth Proximity (EP) DTE Services

Category 1.1 tasks provide secure DTE services in the EP Service Region for EP DTE missions as described in Section 1.4 of this SOW.

In addition to the requirement of Sections 3, 4.1, and 4.2.1 the Contractor shall provide secure EP DTE services that meet the functional and performance requirements identified in Sections 4.2.2.1 and 4.2.2.2.

For all Category 1.1, EP DTE Services Capability Validation TOs, the Contractor shall validate services can meet the functional and performance requirements in this section, and all subsections, to successfully complete the Capability Validation TO.

For all Category 1.1, EP DTE Services Operational Services TOs, the Contractor shall deliver secure services that satisfy the functional and performance requirements in this section, and all of its subsections.

4.2.2.1. EP DTE Functional Requirements

The Contractor shall validate the ability to provide secure EP DTE communication and radiometric tracking services for mission users up to 36,000 km away from Earth.

The Contractor shall complete all EP DTE Capability Validation milestones within the Period of Performance identified in the awarded TO. Contractors are encouraged to complete the Capability Validation TO earlier than the Not to Exceed (NTE) Period of Performance listed in the TO and can satisfy multiple milestones concurrently with government approval.

The Contractor shall validate services meet the Mission Service Interfaces and Capability requirements for Data Forward (Table 13), Data Return (Table 14), and Tracking (Table 15) to successfully complete a Capability Validation TO for EP DTE services.

The Contractor shall deliver secure operational services in accordance with the functional requirements in Table 13, Table 14, and Table 15 for the missions defined in the Operational Services TO.

Table 13. Mission Service Interfaces and Capabilities – Data Forward – Earth Proximity DTE

Frequency Bands S-band X-band Ka-band

Service Coverage Forward service line of sight coverage for user mission platforms above 5 degrees elevation, subject to antenna horizon masks

Space Service Interface CLTU

ECLTU

File Frame

IP

Bitstream

Space Interface Protocols

CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 231.0 "TC Synchronization and Channel Coding" CCSDS 232.1 "Communications Operation Procedure-1" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)" CCSDS 732.0 "AOS Space Data Link Protocol"

Ground Service Interface

CLTU over TCP/IP

CLTU

Transfer Frame CADU over TCP/IP File with delivery meta-data (time, destination, forwarding) CCSDS frame over TCP/IP IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 912.1 "Space Link Extension--Forward CLTU Service Specification"

CCSDS 912.11 "Space Link Extension--Enhanced Forward CLTU Service"

CCSDS 913.1 "Space Link Extension--Internet Protocol for Transfer Services"

CCSDS 922.3 "Cross Support Transfer Service—Forward Frame Service"

IP

SFTP, HTTP, or CFDP over IP NASCOM 4800 Bit Block over RTP/UDP/IP

Table 14. Mission Service Interfaces and Capabilities – Data Return – Earth Proximity DTE

Frequency Bands S-band X-band X-band (SRS) Ka-band

Service Coverage Return service line of sight coverage for user mission platforms above 5 degrees elevation subject to antenna horizon masks.

Space Service Interface All Frames Channel Frames Beacon Tone File Packet

IP

Bitstream

Space Interface Protocol Stack

CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 231.0 "TC Synchronization and Channel Coding" CCSDS 131.0 "TM Synch & Channel Coding" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.1 "Encapsulation Packet Protocol"

IP

Ground Service Interface

A stream of frames (including fill frames) over TCP/IP A stream of frames per each virtual channel over TCP/IP Tracking support File with delivery meta-data IP packets Bitstream data encapsulated over UDP/IP

Cislunar Service Coverage

Service-capable line of sight to user mission platforms for at least:

1) 87% of every day in NRHO

2) 95% of every day for lunar surface (subject to local terrain mask)

Space Service Interface

CLTU

ECLTU

File Frame

IP

Bitstream

Space Interface Protocol

CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 231.0 "TC Synch & Channel Coding" CCSDS 232.1 "Communications Operations Procedure-1 (COP-1)" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)" CCSDS 732.0 "AOS Space Data Link Protocol"

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

CLTU over TCP/IP

CLTU

Transfer Frame CADU over TCP/IP File with delivery meta-data (time, destination, forwarding) CCSDS frame over TCP/IP IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 913.1 "Space Link Extension--Internet Protocol for Transfer Services"

CCSDS 912.1 "Space Link Extension--Forward CLTU Service Specification"

CCSDS 912.11 "Space Link Extension--Enhanced Forward CLTU Service, Internet Protocol"

CCSDS 922.3 "Cross Support Transfer Service—Forward Frame Service"

Table 19. Mission Service Interfaces and Capabilities – Data Return – GEO to Cislunar DTE

Frequency Bands S-band X-band X-band (SRS) Ka-band

Service Coverage Receive a signal from a user mission platform in at least:

S-Band: 88% of the sky within 45 degrees of the ecliptic X-Band: 83% of the sky within 45 degrees of the ecliptic Ka-Band: 70% of the sky within 45 degrees of the ecliptic

Cislunar Service Coverage

Service-capable line of sight to user mission platforms for at least:

1) 87% of every day in NRHO

2) 95% of every day for lunar surface (subject to local terrain mask)

Multiple Spacecraft per Antenna (MSPA) Capability

Four or more simultaneous ground links configurable among the three bands (S, X, and Ka)

Acquire signals from up to four user mission platforms using a single antenna.

Space Service Interface All Frames Channel Frames Beacon Tone File Packet

IP

Bitstream

Space Interface Protocol Stack

CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 231.0 "TC Synchronization and Channel Coding" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.1 "Encapsulation Packet Protocol"

IP

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

Stream of frames (including fill frames) over TCP/IP Stream of frames per each virtual channel over TCP/IP Tracking support File with delivery meta-data IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 911.1 "Space Link Extension--Return All Frames Service Specification"

CCSDS 911.2 "Space Link Extension--Return Channel Frames Service Specification"

CCSDS 911.5 “Space Link Extension—Return Operational Control Fields Service Specification”

CCSDS 913.1 " Space Link Extension--Internet Protocol for Transfer Services", SFTP, HTTP, or CFDP over IP

Implementation Loss 2 dB max 2 dB max 2 dB max

Maximum Signal Rate 20 Msps 150 Msps 500 Msps

4.2.4. Category 1.3: xCislunar DTE Services

Category 1.3 tasks provide secure DTE services in the xCislunar Service Region for xCislunar DTE missions as described in Section 1.4 of this SOW.

For all Category 1.3, xCislunar DTE Services Validation TOs, the Contractor shall validate services meet the functional and performance requirements in this section, and all subsections, to successfully complete the Capability Validation TO.

For all Category 1.3, xCislunar DTE Services Operational Services TOs, the Contractor shall deliver secure services that satisfy the functional and performance requirements in this section, and all sub-sections.

In addition to the requirements of Sections 3, 4.1, and 4.2.1, the Contractor shall provide secure xCislunar DTE services that meet the functional and performance requirements identified in Sections

4.2.4.1 and 4.2.4.2.

The Contractor shall complete all xCislunar Capability Validation milestones within the Period of Performance identified in the awarded TO. Contractors are encouraged to complete the Capability Validation TOs earlier than the Not to Exceed (NTE) Period of Performance listed in the TO and can satisfy multiple milestones concurrently with government approval.

4.2.4.1. xCislunar DTE Functional Requirements The Contractor shall validate services meet the functional requirements for xCislunar DTE services and successfully complete a xCislunar DTE Capability Validation TO.

The Contractor shall validate services meet the Mission Service Interfaces and Capability requirements for Data Forward (Table 23), Data Return (Table 24), and Tracking (Table 25) to successfully complete a Capability Validation TO for xCislunar DTE services.

Table 23. Mission Service Interfaces and Capabilities – Data Forward – xCislunar DTE

Frequency Bands S-band X-band Ka-band

Service Coverage S-Band: at least 83% of the sky within 45 degrees of the ecliptic X-Band: at least 83% of the sky within 45 degrees of the ecliptic Ka-Band: at least 70% of the sky within 45 degrees of the ecliptic at Ka-band Sun-Earth Lagrange Service Coverage

Non-Continuous line of sight service coverage for user mission platforms at all azimuth angles and at elevation angles from 10 deg to 89.5 deg subject to antenna horizon masks

Space Service Interface CLTU, ECLTU, File Frame, IP, Bitstream

Space Interface Protocol

CCSDS 231.0 "TC Synch & Channel Coding" CCSDS 131.0 "TM Synch & Channel Coding" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 232.1 "Communications Operations Procedure-1 (COP-1)" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 133.0 "Space Packet Protocol"

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

CLTU over TCP/IP, CLTU, Transfer Frame, CADU…