SCaN-MOCS-0001-Rev _4__Final.pdf

SCaN-MOCS-0001

SPACE COMMUNICATIONS AND NAVIGATION PROGRAM

Space Communications and Navigation (SCaN) Mission Operations and Communications

Services (MOCS)

Revision 4

Effective Date: August 13, 2021

Expiration Date: August 13, 2026

CHECK THE TECHNICAL DATA MANAGEMENT SYSTEM (TDMS) AT: https://ipdtdms.gsfc.nasa.gov/

PRIOR TO USE TO VERIFY THAT THIS IS THE CORRECT VERSION.

Nat ona Aeronaut cs and Space Adm n strat on

NASA Headquarters Washington, D. C.

1-1 SCaN-MOCS-0001

Space Communications and Navigation (SCaN) Mission Operations and Communications Services

(MOCS)

NASA Headquarters Washington, D. C.

1-2 SCaN-MOCS-0001

Preface

This is the SCaN Mission Operations and Communications Services Document.

This document is controlled by the Heaquarters (HQ). SCaN Integrated Network Configuration Control (SINCCB) is delegated by SCaN to manage the configuration of the SINCCB. This document will be updated by Documentation Change Notice (DCN) or complete revision.

Proposed changes to this document must be submitted to SCaN Configuration Management Office along with supportive material justifying the proposed change.

Comments or questions concerning this document and proposed changes shall be addressed to:

John Hudiburg

Mission Commitment Manager, Network Services Division SCaN Program Office

NASA, HQ

John.J.Hudiburg@nasa.gov

Cc: Qiuna.T.Pope@nasa.gov

This document may be downloaded from the Exploration and Space Communications (ESC) Projects Division, Space Communications and Navigation (SCaN) library at https://ipdtdms.gsfc.nasa.gov/. If you do not have direct access to the library, you may obtain the document from the SCaN Configuration Management Office (CMO).

1-4 SCaN-MOCS-0001

Revision 1 March 26, 2018

• Editorial revisions for clarity, verbiage, grammar, and acronyms throughout the document

• Replaced DSN Mission Services Planning & Management Office (DMSP&MO) with CIMO throughout the document

• Updates throughout the document for consistency with other SCaN documentation

• Changes references from Communications Service Office (CSO) to NASCOM in Sections 3.4 and 4.2

• Updated SN Rates in Section 5.3 to match published 2017 SN Rate Letter

• Reconfigured Section 5.3 to create a more balanced presentation of the material between the three SCaN networks

• Moved Costs for using the DSN from Section 5.4 to Appendix F

• Updated contact information for the Points of Contact in Section 6

• Added references to the Customer Service Portal in Section 6.1

• Moved Acronym list to Appendix A

• Updated references in Appendix B

• Updated tables in Appendix D

• Added Points of Contact to Appendix E

• Updated cost algorithms in Appendix F

Revision 2 March 15, 2019 • General updates for 2018-19 information throughout the document

• Updated SN Rates in Section 5.3 to match published 2018 SN Rate Letter

• Updated Points of Contact in Section 6.2

• Updated cost algorithms in Appendix F

1-5 SCaN-MOCS-0001

Revision 3 August 18,

• General updates for 2019-20 information throughout the document

• Added new coverage diagram to section 1.3.2

• Added new section 1.3.2.2 detailing the new Lunar Exploration Ground System

(LEGS)

• Added a new section 2.1.1.1 detailing SCaN’s policy regarding missions’ use of commercial services

• Added new section 4.3 detailing the Mission Cloud Platform

• Removed Section 4.6 JPL Mission Design and Navigation

• Updated SN Rates in Section 5.3 to match published 2020 SN Rate Letter

• Revised section 5.5, on the cost for non- SCaN services, in response to the new policy statement in section 1.2

• Updated POCs in section 6.

1-6 SCaN-MOCS-0001

Revision 4 August 13,

• General updates for 2021 information throughout the document

• Updated document to reflect reorganization of Goddard Space Flight Center’s Exploration Systems Communications (ESC), Code 450, including removing references to Space Network (SN), Near Earth Network (NEN) and Network Integration Management Office (NIMO) and adding references to Near Space Network (NSN), Advanced Communications Capabilities for Exploration and Science Systems (ACCESS), and the Commercialization, Innovation and Synergies (CIS) Office, as appropriate

• Updated section 3.3 to reflect the new Memorandum of Agreement between SCaN and SMD

• Added new Contingency and Emergency Services subsection and description to Section 3.5

• Updated section 4.2 to reflect new Communication Program (CP) descriptions

• Updated rate tables in section 5 to reflect 2021 rates

• Updated section 6 to reflect new points of contact

• Updated Appendix A with new acronyms

• Updated appendix B with updated references

• Retitled Appendix C to the MCO

Questionnaire and replaced the questionnaire itself with an updated version

• Updated POC in Appendix E

• Removed Appendix F and included DSN cost information in Table 5-2

1-7 SCaN-MOCS-0001

Contents

Preface ......................................................................................................................... 1-2

Change Information Page ........................................................................................... 1-3

Section 1 Introduction ................................................................................................ 1-1

1.1 Purpose ................................................................................................... 1-1

1.2 Scope ....................................................................................................... 1-2

1.3 SCaN Network Services Division ............................................................. 1-2

1.3.1. SCaN Mission Commitment Office (MCO) ............................... 1-2

1.3.2. The SCaN Networks ................................................................. 1-2

Section 2 SCaN Network Policies and Standards .................................................... 2-1

2.2 SCaN Policy on the Use of the Electromagnetic Spectrum ..................... 2-1

2.3 Bandwidth Efficient Modulation (DSN, NSN GOCO) ............................... 2-2

2.4 Coding Standards .................................................................................... 2-2

2.5 Space Link Extension (DSN, NSN GOCO) .............................................. 2-3

Section 3 Summary of SCaN Networks’ Standard Services ................................... 3-1

3.1 NSN Service Summary ............................................................................ 3-1

3.2 DSN Service Summary ............................................................................ 3-2

3.3 MCO Service Summary ........................................................................... 3-3

3.4 Critical Event Communications ................................................................ 3-7

3.5 Emergency or Contingency Communication Support .............................. 3-7

Section 4 Support from Non-SCaN Network Service Providers ............................. 4-1

4.1 Spectrum Management ........................................................................... 4-1

4.2 Communications Program (CP)/NASA Communication Network

(NASCOM) ............................................................................................... 4-1

4.3 Mission Cloud Platform (MCP) ................................................................ 4-2

4.4 Flight Dynamics Facility (FDF) ................................................................. 4-3

4.5 Advanced Multi-Mission Operations System (AMMOS) .......................... 4-4

Section 5 Network Support Cost Estimation ............................................................ 5-1

5.1 Mission Engineering Support Costs ........................................................ 5-1

5.2 Mission Planning and Integration (MP&I) ................................................ 5-1

5.3 Cost Estimates for Using the SCaN Networks ........................................ 5-2

5.4 Critical or Emergency Event Support Costing ......................................... 5-3

5.5 Non-SCaN Support Costing .................................................................... 5-4

1-8 SCaN-MOCS-0001

Section 6 Requesting Support from the SCaN Networks ........................................ 6-1

6.1 Requesting SCaN Network Services ....................................................... 6-1

6.2 Additional Points of Contact .................................................................... 6-2

Appendix A. Acronym List ........................................................................................ A-1

Appendix B. Reference Documents and Websites ................................................. B-1

Appendix C. Sample Mission Commitment Questionnaire .................................... C-1

Appendix D. Sample DSN Communications System Parameter Tables ............... D-1

Appendix E. Form for Estimating DSN Mission Support Costs ............................. E-1

List of Tables Table 3-1: Ground-Based Direct-to-Earth Service Summary ........................................ 3-2 Table 3-2: Space-Based Relay Service Summary ........................................................ 3-2 Table 3-3: DSN Service Summary ................................................................................ 3-3 Table 3-4: MCO Service Summary - Mission Planning and Integration ........................ 3-3 Table 3-5: MCO Service Summary – Network Services (Operations and Maintenance) 3-

Table 3-6: MCO Service Summary - Network Sustainment .......................................... 3-6 Table 5-1: Pass Length Calculation .............................................................................. 5-2 Table 5-2: Rates for Estimation for Using the SCaN Networks ..................................... 5-3 Table D-1: Telecommunications Parameters and Definitions ...................................... D-1 Table D-2: Sample Table for Inclusion in Proposal ...................................................... D-3 Table D-3: Sample Station Requirements by Mission Phase Table ............................ D-5

1-1 SCaN-MOCS-0001

Section 1 Introduction

1.1 Purpose

This document is intended to assist in the preparation of proposals responding to Announcements of Opportunity (AO), Broad Area Announcements (BAA), and other mission focused Request for Proposals (RFP) that are issued by the National Aeronautics and Space Administration (NASA). In addition, this document may also assist missions and organizations seeking to use NASA’s space communications and navigation (C&N) services.

It is NASA's policy to achieve and maintain consolidated, mission-success oriented, and cost-effective space C&N mission support; to unify the set of processes for the development, utilization, and acquisition of agency space C&N infrastructure; and to enhance this support by facilitating new capabilities for the future. NASA's space C&N infrastructure comprises the ground and space-based communications and navigation networks and infrastructure providing mission support for all planetary orbits, surfaces, and environs. To accommodate this policy, NASA leadership established the Space Communications and Navigation (SCaN) Program Office, organizationally located within the Human Exploration and Operations Mission Directorate (HEOMD), to support agency management of space C&N services, as prescribed by NASA Policy Directive (NPD) 1000.0A, NASA Governance and Strategic Management Handbook, and NPD 1000.3, The NASA Organization.

NASA provides many mission operations and communications services relating to the planning and execution of the transport of voice, video, and data for mission support.

Costs accrue when using these services and estimates, and these costs need to be included in proposals responding to an RFP. Cost numbers and equations supplied in this document are for planning purposes only. The calculated estimate of services provided is required by the SMD to document the full value of the mission and its services, although not all missions will be charged by SCaN for recurring cost for aperture or per-minute fees. Please see Section 5 for details on how to estimate the cost of using the SCaN Networks. To facilitate proposal preparation, proposers are encouraged to read this document and to contact the individuals named in Section 6. Respondents preparing proposals should carefully review this entire document to ensure that the document that they are submitting addresses each applicable item.

In order to appropriately assess SCaN’s ability to support candidate missions, it is in the interest of the selected investigation teams to provide information on the communication parameters when submitting a proposal. To that end, while this document provides an initial set of information, additional detail is often referenced. Appendix B contains references and links to websites where further information can be found. Appendix C, Appendix D and Appendix E provide samples of the information that should be submitted with the proposal. For more details on the requested information, proposers are encouraged to contact the points of contact listed in Section 6.

1-2 SCaN-MOCS-0001

1.2 Scope

Services and support offered by NASA’s SCaN networks are available to all NASA sponsored flight projects and science investigators; the SCaN networks provide standard services to NASA missions—from Hubble Space Telescope to SmallSat missions. Other Government agencies and commercial flight projects may become eligible for services offered by the SCaN networks through negotiation with NASA Headquarters.

The scope of this document covers the SCaN networks’ services that are current at the time of publication. This document will be updated over time as new services and rates are made available to the public.

1.3 SCaN Network Services Division

The Network Services Division (NSD), a part of NASA’s SCaN Program, is responsible for managing the day-to-day operations and maintenance of the networks; directing activities related to network sustainment and development; and capturing and assessing user mission requirements. NSD is also the customer-facing division, interacting regularly with stakeholders and the user community to assess changes that are needed to continue to support users. The Network Services Division performs these activities under the direction of NPD 8074.1 Management and Utilization of NASA's Space Communication and Navigation Infrastructure.

1.3.1. SCaN Mission Commitment Office (MCO)

SCaN implements a well-established process to capture and assess user requirements in order to determine how to best support those requirements. The process is collaborative and relies on continuous communication and exchange of information between the customer and SCaN throughout all phases of mission development. It is the responsibility of SCaN’s Mission Commitment Office (MCO), along with the Commercialization, Innovation and Synergies (CIS) Office, the Near Space Network (NSN) mission integration group, and the Deep Space Network’s (DSN) Customer Interface Management Office (CIMO), to facilitate this process on behalf of the SCaN networks.

1.3.2. The SCaN Networks

The SCaN networks are comprised of the Near Space Network (NSN) and the Deep Space Network (DSN). These networks provide communications and navigation services over the full operational life cycle of a mission from launch to end of life and/or deorbit.

SCaN oversees the Operations and Maintenance of these networks ensuring reliability and robustness to meet mission objectives. While missions may have a desire to use specific resources in accordance with NPD 8074.1, the SCaN networks ultimately decide the utilization of its network assets.

1.3.2.1. Deep Space Network (DSN)

The DSN, which has been in operation for more than 50 years, provides reliable, high-performance, and cost-effective communication and tracking services to NASA and non- NASA missions beyond geosynchronous orbit (more than 22,000 miles above the Earth’s surface). It is a worldwide network of 34-meter and 70-meter antennas that supports interplanetary spacecraft missions and radio and radar astronomy observations for the

1-3 SCaN-MOCS-0001 exploration of the solar system and the universe. The DSN currently consists of three deep-space communications facilities located approximately 120 degrees of longitude apart around the world: at Goldstone in California's Mojave Desert; near Madrid, Spain;

and near Canberra, Australia. The site separation ensures that any spacecraft in deep space can communicate with at least one DSN facility at all times as the Earth rotates and the spacecraft continues to move along its trajectory. Additionally, NASA uses the Goldstone Solar System Radar (GSSR) capability to track and characterize near-Earth objects that pass within nine million miles of Earth. The orbits of the near-Earth objects are determined and utilized by the Science Mission Directorate’s (SMD) Planetary Science Division to assess the probability of a conjunction between the object and the Earth.

1.3.2.2. Near Space Network (NSN)

NSN provides near-continuous communication services to users via commercial and government assets and providers from ground level through low earth orbit (LEO) and up to cis-lunar distances. NSN provides These space-based relay and ground-based, direct-to-Earth services are provided to the missions customers through a blend of Government Owned, Contractor Operated (GOCO) assets—managed by the Advanced Communications Capabilities for Exploration and Science Systems (ACCESS) Project— and Commercial Services Providers. Both NSN and ACCESS are managed out of Goddard Space Flight Center (GSFC). The NSN ground-based “direct-to-Earth” assets, consisting of a combination of NASA, partner, and commercial ground stations with antennas up to 18 meters in diameter, is focused on supporting launch and operational activities in the Low Earth Orbit (LEO) range as well as GEO, Lunar, and Earth-Sun Lagrange points.

NSN is working to deploy a set of new 18-meter class antennas to provide direct-to-Earth communication and navigation services for missions operating in the cisLunar and Earth

- Sun Lagrangian regimes.

NSN’s space-based assets (i.e., NASA’s Tracking and Data Relay Satellites (TDRS)) are a system of government-owned/contractor-operated communications satellites in geosynchronous orbit matched with a set of space-to-ground link terminals located at NASA’s White Sands Complex in New Mexico, in Guam, and in Blossom Point, MD. The constellation, enables continuous communications services to missions operating in Medium Earth Orbit (MEO) and below with support provided to Highly Elliptical Orbit (HEO) when the orbit brings the spacecraft within range. Using this capability, NASA has continuous visibility to missions from Launch through LEO operations.

1.3.2.3. Commercialization of the SCaN Networks

The provision of communications network services is undergoing a transformation; SCaN is pursuing commercialization of services for near-Earth users in the 2020s and beyond.

The transition to commercial services, particularly the space-based relay and gradual phase-out of TDRS services for new users, will be an evolving and fluid process requiring coordination between SCaN and the mission community. Currently commercial partner ground assets (KSAT and SSC) and services are available through the NSN, but the portfolio of providers is expected to grow. SCaN services and capabilities will be updated periodically as additional commercial services become available.

2-1 SCaN-MOCS-0001

Section 2 SCaN Network Policies and Standards

It is NASA policy that space missions receiving funding from NASA comply with all applicable international and United States regulations, standards, and agreements.

Such regulations and standards include those promulgated by the:

• International Telecommunications Union (ITU);

• National Telecommunications and Information Agency (NTIA);

• Consultative Committee for Space Data Systems (CCSDS);

• Space Frequency Coordination Group (SFCG).

Information about the ITU and NTIA regulations may be obtained from NASA's Spectrum Management Office by consulting the reference documents listed in Appendix B.

Additional information on recommended CCSDS standards applicable to the support that the SCaN networks provide as well as recommendations from the SFCG can also be found by consulting the reference documents listed in Appendix B.

2.1.1.1. SCaN Policy Regarding Use of Commercial Services

It is SCaN’s policy to utilize commercial assets to satisfy mission requirements to the greatest extent possible. Some customer user cases may require a mixture of commercial and GOCO assets, or GOCO only (e.g., TDRS). SCaN utilizes bulk-buy agreements for the use of commercial and/or international service providers and will make every effort to negotiate the most cost-effective rates possible. Rather than purchasing commercial services on the open market, proposers and offerors are encouraged to utilize those agreements whenever possible, as there are a variety of advantages to missions for doing so, including increased cost savings for the Agency and priority scheduling for missions.

To utilize NASA's contracted commercial providers, proposers and offerors are required to contact SCaN. Please see Section 5.5 for additional information on costing non-SCaN services and Section 6 for the appropriate point of contact. These organizations will find a good blend of providers to meet the mission needs.

2.2 SCaN Policy on the Use of the Electromagnetic Spectrum

Per NPD 2570.5E NASA Electromagnetic Spectrum Management, it is NASA policy that all NASA satellite, airborne and other missions, whether directly developed and operated by NASA or those supported through contracts or other financial agreements that require the use of the electromagnetic spectrum, shall follow the United States and international spectrum regulatory rules and processes. All uses of the radio frequency spectrum require an authorization from the NTIA, for Federal Government systems, the ITU, for International Partners, or a license from the Federal Communications Commission (FCC) for Non-Federal Government systems (e.g., commercial, academic).

The design and operation of systems using radio-frequency communications, navigation, and sensors (i.e., any system that involves the use of the radio frequency spectrum for transmission, reception, or both) needs to consider a variety of factors, 2-2 SCaN-MOCS-0001 including spectrum regulations, network services, spaceflight equipment availability, and others depending upon the mission needs. Additional information concerning NASA spectrum policy and processes can be found in NPD 2570.5E and NASA Policy Requirement (NPR) 2570.1C NASA Radio Frequency Spectrum Management Manual.

These requirements and processes apply to electromagnetic spectrum use for radio frequency (<300 GHz) communication, navigation, radio science, active sensing, and passive sensing.

All missions and projects requiring the use of the electromagnetic spectrum should contact the associated Center/Facility Spectrum Manager (SM) as early in the proposal or mission development process as possible to discuss the electromagnetic spectrum operations concept and the necessary system certification and frequency authorization (licensing) requirements. The current NASA Center SMs, NASA National Spectrum Program Manager, and other points of contact are provided on NASA’s spectrum website (www.nasa.gov/directorates/heo/scan/spectrum/index.html).

2.3 Bandwidth Efficient Modulation (DSN, NSN GOCO)

Missions operating in the 2, 8, 2 6 , a n d 3 2 GHz spectral bands should employ bandwidth efficient modulation methods in conformance with SFCG and CCSDS recommendations. Spectral Emission Masks for Category A missions (r < 2 x 106 km, where “r” is the range from the spacecraft to Earth) are found in the SFCG’s Handbook, available on the SFCG web site. Specific modulation methods meeting the SFCG mask are enumerated in CCSDS Recommendations 401 for non-deep space and Earth resources missions, respectively.

As a matter of DSN policy, it is recommended that Category B missions (r ≥ 2 x 106 km) employ bandwidth efficient modulation to comply with SFCG Recommendation 23-1, from CCSDS 413.0-G-2, whenever operating in the 8400 - 8450 MHz band. CCSDS Recommendation 401 (2.4.17B) B-1 lists acceptable modulation schemes. Not all schemes are implemented in the DSN, so there may be additional losses that need to be accounted for due to mismatches between the spacecraft transmission and the ground demodulation.

2.4 Coding Standards

Most missions employ error-detecting/error-correcting codes to substantially improve telemetry link performance. Users are reminded that their encoders should conform to the CCSDS Telemetry Channel Coding Blue Book. Supported codes include but are not limited to:

1) Uncoded

2) Convolutional Rate 1/2

3) Convolutional Rate 1/3 (DSN does not support)

4) Reed-Solomon

5) Convolutional/Reed-Solomon

6) Turbo codes with rates: 1/2, 1/3, 1/4, or 1/6

7) Low Density Parity Check (LDPC) Rate ½ (DSN supports rate 2/3 and 4/5 also)

8) LDPC Rate 7/8 (Note: This service has been partially implemented and is not yet available across the SCaN networks).

2-3 SCaN-MOCS-0001

DSN has implemented LDPC for all frequency bands except Near Earth Ka-band (26 GHz) and will implement Near Earth Ka-band in the future. The NSN GOCO assets also support LDPC.

Proposers are encouraged to contact the representatives listed in Section 6.1, Requesting MCO Support, for the most recent list of supported codes.

2.5 Space Link Extension (DSN, NSN GOCO)

Missions using SCaN’s space-based relay services may utilize a standard Space Link Extension (SLE) Services Interface for transferring data to and from DSN or space-based relay service sites to control centers on the ground (e.g., Project Operations Control Center [POCC], Mission Operations Center [MOC], etc.). As of December 2020, all DSN missions must utilize the SLE Services Interface, unless otherwise coordinated with SCaN MCO. SCaN’s direct-to-earth SLE services are limited to certain antennas including, but not limited to, the White Sands 1 (WS1) ground system, the Wallops Ground Station (WG-1) and McMurdo Ground Station (MG-1).

Nine international space agencies have agreed to implement the SLE Services Interface to achieve full international interoperability. These agencies include Agenzia Spaziale Italiana (ASI), Centre Nationale d’Etudes Spatiales (CNES), Deutsche Zentrum fur Luft- Und Raumfahrt (DLR), European Space Agency (ESA), Indian Space Research Organization (ISRO), Japanese Aerospace Exploration Agency (JAXA), the Korea Aerospace Research Institute (KARI), the United Arab Emirates (UAE) and NASA. The interface architecture conforms to standards adopted by the CCSDS.

3-1 SCaN-MOCS-0001

Section 3 Summary of SCaN Networks’ Standard Services

SCaN has developed a set of Standard Services which are inherent to the current functional capabilities of the SCaN networks without modification. Use of the Standard Services enables more streamlined service evaluation, acquisition, and use. Current Standard Services include end-to-end transport of information between the point of origin (e.g., mission platform[s]) and destination (e.g., mission operations center, university, etc.).

Standard services for Data Transport facilitate the exchange of information between a mission’s platform(s) and locations on the Earth. Typically, minimal processing is applied to the data—only that which is necessary to communicate with the end points (e.g., RF encoding to IP-based transport). Transported data may include voice, video, and/or data.

Note that Command and Telemetry data are critical subsets of Forward and Return data transport functions. As services for this type of data deal particularly with the exchange of information to and from a mission’s platform(s) for the purposes of monitoring and maintaining control of the platform, this information is typically of higher priority than other categories of data to be transported by the SCaN networks.

This section provides a very brief summary of the standard services that the SCaN networks offer their customers. For additional information on these services, please reference the documents listed in Appendix B. Each of the service categories listed in the tables below may contain several services. Some of those individual services may require that special arrangements be made with SCaN before they can be provided. Proposal respondents who are interested in services that are not a part of the standard Tracking, Telemetry & Command (TT&C) set should contact the person(s) named in Section 6 for additional information.

3.1 NSN Service Summary

Table 3-1 and Table 3-2 summarize the NSN ground-based and space-based service categories. More detailed information can be found using the following link:

https://esc.gsfc.nasa.gov/NSN (See Appendix B for additional references).

3-7 SCaN-MOCS-0001

3.4 Critical Event Communications

When requesting mission critical event support, proposers may want to consider an expanded set of communications and navigation services and assets compared to routine operations. The MCO is prepared to discuss common approaches to ensure support during critical events. Critical Events are defined as “spacecraft events that could result in the loss of mission if anomalies occur.” These events include:

• Launch and early orbit operations

• Spacecraft separation

• Powered flight

• Critical Maneuvers (e.g., Deep Space Maneuvers [DSMs], docking/undocking)

• Orbit insertion

• Entry/Descent/Landing

• Flybys

• Re-entry

Either of the networks (NSN or DSN) can provide critical event support—including launch, early orbit, and separation—if the trajectory permits. However, in cases where there are coverage gaps, SCaN may need to use one or more communication assets from an external organization to provide adequate coverage.

3.5 Emergency or Contingency Communication Support

In the event of a spacecraft anomaly—whether it be a partial loss of data or a full spacecraft emergency—the SCaN Networks can provide rapid connectivity to mission during critical times. Either of the networks (NSN or DSN) can provide emergency event support if the mission trajectory permits. However, in cases where there are coverage gaps, SCaN may need to use communication assets from an external organization to provide adequate coverage. Given the unique and fluid nature of these situations, proposers are encouraged to discuss network capabilities with the POCs listed in Section 6, so that in event that immediate support is required, the mission fully understands SCaN’s capabilities and priorities.

4-1 SCaN-MOCS-0001

Section 4 Support from Non-SCaN Network Service Providers

If needed, the SCaN networks will assist user missions with procuring services from other non-SCaN network entities and partners, including but not limited to other SCaN divisions, other NASA organizations, other Government agencies, and international and commercial partners. This section discusses the most common external organizations for whom the SCaN networks assist missions with procuring services. The SCaN networks will facilitate the coordination between the mission and these organizations during the mission integration phases to ensure that mission needs, such as those related to terrestrial communications and data processing in the cloud, are met.

If the mission desires to use communication and navigation assets outside of the SCaN network, the mission needs to consult NPD 8074.1 and work with MCO, NSN or CIMO to obtain the capabilities needed to ensure the most cost-effective method for the agency.

4.1 Spectrum Management

Although the Spectrum Management Office falls under the responsibility of the SCaN Program Office, it is not part of the SCaN networks or MCO. It is NASA policy that any satellite mission supported by the Agency, whether directly developed and operated by NASA or those supported through contracts or other financial agreements that require the use of the electromagnetic spectrum for transmission, reception, or both, shall follow the United States spectrum regulatory rules and processes as well as all applicable international spectrum regulations. NASA missions are encouraged to engage with the SCaN Networks for Spectrum Management needs.

The Center/Facility Spectrum Manager or NASA National Spectrum Program Manager will provide assistance during all phases of a mission or project from conceptual, preproposal efforts through formulation and implementation. The Spectrum Manager will support the project at each review in the project life cycle and assist with design and spectrum considerations such as frequency selection, conformance to regulatory constraints, and compliance with any other electromagnetic spectrum constraints. A key element of this support is assisting with or preparing inputs for spectrum certification as early in the acquisition and procurement cycles as possible.

If support from the Spectrum office is required, proposal respondents may either contact their local center Spectrum Manager or the National Spectrum Program Manager directly or request assistance in coordinating Spectrum support from the SCaN networks by consulting one of the Points of Contact listed in Section 6.

4.2 Communications Program (CP)/NASA Communication Network

(NASCOM)

The Communications Program (CP) is responsible for the enterprise-wide delivery of Wide Area Network voice, video, and data services in support of the agency, including the following:

• Agency WAN Services

4-2 SCaN-MOCS-0001

• Agency LAN Services

• Russian Communication Services

• Network Security Services

• Agency Network Architecture

• Agency Video Services

• Center Unique Communications Services

• Communications and Network Innovation

• Communications Service Integration

CP staffing is primarily drawn from the three Host Centers – ARC, GSFC, and MSFC:

• Ames Research Center (ARC) provides cross-cutting integration and leadership in the areas of IT security, research networking, emerging network technology and innovation, enterprise architecture, and project management governance

• Goddard Space Flight Center (GSFC) provides leadership for the overall management of the mission communications services

• Marshall Space Flight Center (MSFC) provides leadership for the overall program management, administrative and financial management, and management of the corporate communications services

The corporate communications services include NASA-wide voice and video teleconferencing, corporate network routed data services, as well as Layer 2 Virtual Private Network service. The fundamental function of these services is to provide enterprise-level communications services across the Agency.

The mission communications services include mission routed data services (including IONet), dedicated mission data services, and mission voice services. The fundamental purpose of these services is to support spacecraft operations. These include terrestrial transport of spacecraft command, telemetry, and tracking data as well as delivery of science data products. The mission network must also address risks to the health and safety of human life as well as serious damage or loss of spacecraft. The mission voice services provide order wire and other voice service in support of spacecraft operations.

4.3 Mission Cloud Platform (MCP)

The GSFC Cloud Computing Program Office established the MCP to provide consolidated cloud computing services for mission customers, giving them a streamlined process for implementing and using those resources. The MCP captures detailed requirements from each customer in the Cloud Architecture Requirements Document (CARD) and uses this information to form the basis of the cloud architecture.

In support of the networks, MCP provides missions with the following cloud computing capabilities:

• Virtual private cloud (VPC)

• Server-less computing

• Compute

• Storage

• Database

4-3 SCaN-MOCS-0001

• Application development

• Science data processing

• Artificial intelligence/machine learning

• External collaboration and/or file sharing

Additional information regarding MCP networks and mission services and their timetables will be defined in the Service Level Agreement (SLA). More details regarding requested services and products can be obtained from the MCP Project Manager.

4.4 Flight Dynamics Facility (FDF)

The GSFC FDF, which is not part of SCaN but works closely with the NSN, provides expertise in navigation analysis and system design, operations planning, trajectory design, orbit determination, network operations support, and critical real-time mission operations. This expertise spans the technical areas of orbit determination and trajectory design for low-Earth, geosynchronous, highly elliptical, lunar, libration-point, heliocentric orbits, other celestial-body centered orbits ELV and human spaceflight operations, and support of over 25 on-orbit spacecraft.

FDF evaluates tracking data from commercial providers, NSN/SR, DSN, and both NASA and DoD C-band radar sites and certifies tracking capability for new stations needed for mission support. FDF also participates in end-to-end verification and validation to ensure that FDF products, such as pointing data for the NSN/SR assets, are received in the proper format. Mission integration is a part of FDF’s support of the SCaN networks and its flight project customers. FDF can interface with any of the SCaN networks to support a mission’s flight dynamics needs. Products generated by FDF include ephemerides;

acquisition data, which is used to establish two-way communication with space vehicles;

maneuver planning and execution for spacecraft; on-console support for testing and real-time operations; and evaluation of Expendable Launch Vehicle (ELV) performance during ascent utilizing guidance data. FDF also generates other navigation sources, such as local oscillator frequency analysis for Tracking Data Relay Satellite (TDRS) transponders, orbit event predictions, and calibration of sensors used for tracking spacecraft.

The capabilities of the Goddard FDF include the following:

1) Orbit determination in multiple regimes

2) Launch vehicle support, including but not limited to Atlas V, Delta II, Delta IV, and

Sea Launch

3) Launch and early-orbit support utilizing a diversity of networks

4) Tracking performance evaluation of a multitude of ground-based and space-borne assets

5) Certification of new tracking equipment

6) Mission integration that combines engineering knowledge of the SCaN networks and the analytical and operational aspects of our flight project customers

7) Backup navigation support to the Human Spaceflight Program

8) International Space Station orbit determination and support to all Visiting

Vehicles.

4-4 SCaN-MOCS-0001

4.5 Advanced Multi-Mission Operations System (AMMOS)

AMMOS is the responsibility of the Multi-Mission Ground System and Services (MGSS) Program located at the JPL. While not inherently part of SCaN, AMMOS works closely with the SCaN Network to achieve mission needs. AMMOS consists of a core set of products that can be readily customized to accommodate the specific needs of individual missions. AMMOS provides the elements of a Mission Operations System (MOS) that are common to multiple missions, eliminating the need for duplication of development and maintenance of the MOS. Using AMMOS may lower mission cost and risk by providing a mature base for a MOS.

AMMOS is comprised of multi-mission hardware, software, processes, procedures, and facilities used to implement and operate the MOS. Components of the AMMOS include:

• Planning and Sequencing

• Telemetry Processing

• Data Archive

• Navigation, Mission Design, and Solar System Dynamics

• Operations Configuration Management

• Mission Support Facilities

• Ground Data System (GDS) Integration, Test, Deployment and Support

• Operations Engineering

• Data Relay Coordination for Landed Assets who do not have the direct-to-earth bandwidth needed to execute the mission’

• Multimission Resource Scheduling Service (MRSS) used to schedule DSN apertures.

AMMOS supports the entire life cycle of a flight project or experimental investigation.

5-1 SCaN-MOCS-0001

Section 5 Network Support Cost Estimation

As a matter of policy, NASA includes estimated costs for mission operations and communications services as well as an assessment of key parameters for mission operations in the evaluation and selection processes of all near-space and deep-space missions. The purpose of this policy is to:

• Enable evaluation of the reasonableness and cost effectiveness of the proposed communications and navigation approach

• Implement formal NASA-wide, full-cost accounting

• Better manage NASA’s heavily subscribed communications resources

• Promote trade-offs between space and ground, including parameters such as data volume, data latency, data rate, contact time, aperture size, and cost of associated systems

• Encourage hardware and operations system designs minimizing life-cycle costs while accomplishing the highest-priority science objectives.

Generally, mission proposals must include nonrecurring (e.g., Mission Planning & Integration [MP&I]) and recurring estimates as well as those for services during routine operations and critical event support.

Cost numbers and equations supplied in this section are for planning purposes only. The calculated estimate of services provided is required by the SMD to document the full value of the mission and its services. NASA missions that use standard services will not be charged by SCaN for recurring cost for aperture or per-minute fees.

This section explains how to estimate costs for the DSN and NSN. To ensure accuracy and to validate cost estimates, proposal respondents should contact the appropriate representatives listed in Section 6.

5.1 Mission Engineering Support Costs

Nonrecurring engineering (NRE) costs (e.g., TT&C services, ground communications, MIM support) are those associated with unique equipment that a mission customer provides at NASA facilities, including installation and sustainment engineering. NRE costs also include any unique equipment that a mission requires as well as its installation and the sustaining engineering of that equipment as well as modifications that the networks must make to their systems in order to recognize a new mission. Proposal respondents are advised to contact the point of contacts listed in Section 6 to determine a cost estimate for their missions.

5.2 Mission Planning and Integration (MP&I)

MP&I is the set of activities performed and coordinated by the SCaN MCO, NSN, and CIMO to facilitate the successful provision of NASA’s space communications services to evaluate and address mission needs. MP&I includes those tasks that must be executed prior to the operational use of the SCaN networks as well as actual cost estimates for the

5-4 SCaN-MOCS-0001

Because mission requirements vary over such a broad range, it is not possible to provide a simple means to calculate the cost of telemetry support in the early mission phase.

Please see Section 6 for the point of contact who can assist in establishing alternative solutions and/or in costing the required support.

5.5 Non-SCaN Support Costing

Cost for support from non-SCaN networks resources and entities is dependent on the mission needs and the supporting entity to be used. As stated in Section 2.1.1.1, SCaN negotiates bulk-buy agreements for the use of commercial service providers and makes every effort to negotiate the most cost-effective rates possible. These agreements are negotiated on a periodic basis and, as such, the actual costs for using such providers cannot be included in this document.

SCaN negotiates the costs for using non-NASA, non-SCaN, non-commercial (i.e., international, academic) assets on a case-by-case basis and therefore cannot include that information in this document. However, if requested, SCaN will integrate the requested support into the overall network plan.

If support is required from outside the SCaN networks, proposal respondents should contact SCaN MCO (per NPD 8074.1) for assistance in assessing the need, capabilities, and cost of those services. Please see Section 6 for the appropriate point of contact.

6-1 SCaN-MOCS-0001

Section 6 Requesting Support from the SCaN Networks

Early planning and coordination between SCaN and its customers are critical to ensuring quality service with minimal complications. Proposers are encouraged to contact SCaN as early in their development process as possible to begin pre-mission planning and analysis activities and to ensure that the network(s) have both the capability and capacity to satisfy the mission requirements.

During the concept study phase (Phase-A or Step-2), as the mission’s concept is more clearly defined, proposers should contact the SCaN MCO to obtain a Letter of Acknowledgement (LOA) documenting the fundamentals of the coordination, namely that the exchange of mission needs, and preliminary guidance and direction on network support has been completed. The agreement will identify all mission operations requirements, including those provided by non-SCaN sources, becoming a source of end-to-end operations information and documenting any cost analyses leading to the selection of non-SCaN services. If use of NASA SCaN's network services beyond the capabilities and capacities described in the NASA’s Mission Operations and Communications Services document is proposed, the proposal shall include a Letter of Commitment (LOC) from the SCaN Program Office. Please reference the RFP documentation for a description of Phase A, Step 1, and Step 2 requirements.

The mission commitment process is tailored for each mission and its needs. From the time Mission Commitment personnel are first contacted, the mission commitment process can take anywhere from 2 to 7 weeks, depending on the mission needs and the complexity of the requirements, to develop pre-planning estimate and provide a letter of commitment.

6.1 Requesting SCaN Network Services

Missions desiring use of SCaN services should make contact with the SCaN Mission Commitment Office as early in the concept and design phase process as possible. In order to begin the mission commitment process, missions should send their questions, concerns, or services requests to the following e-mail address:

exploration-enabled@lists.hq.nasa.gov Missions may also contact the SCaN Mission Commitment Manager for questions:

John Hudiburg Mission Integration & Commitment Manager Space Communications and Navigation (SCaN) NASA Headquarters Washington, D.C. 20546 Office: HQ 7Z76 Phone: (202) 358-1202 Email: john.j.hudiburg@nasa.gov

6-2 SCaN-MOCS-0001

For additional information on MCO, its points of contact and the services that it and SCaN provides, proposal respondents may visit the SCaN Customer Service Portal (https://www.nasa.gov/directorates/heo/scan/services/services/index.html). Please note that this is a public website. Access to the restricted section of this portal, which contains the mission-specific information, will only be granted to the selected proposers after award.

6.2 Additional Points of Contact

At the time when initial science operations concepts are being defined, proposers may contact NSN or DSN at the address in this section for information about mission operations services and costs. A representative will assist proposers by providing information concerning services and costs.

The point of contact for NSN is CIS, which can be reached at:

gsfc-missiononboarding@mail.nasa.gov The point of contact for DSN services is CIMO:

Brian J. Giovannoni Manager Jet Propulsion Laboratory Interplanetary Network Directorate Customer Management Interface Office Mobile phone: 626-755-8829 Email: brian.j.giovannoni@jpl.nasa.gov

A-1 SCaN-MOCS-0001

Appendix A. Acronym List ACCESS Advanced Communications Capabilities for Exploration and Science

Systems

AF Aperture Fee

AF' Aperture Fee discounted for Multiple Spacecraft per Aperture applications

AMMOS Advanced Multi-Mission Operations System

AO Announcement of Opportunity

ARC Ames Research Center

ASI Agenzia Spaziale Italiana (Italy)

AW Aperture Weighting (For costing DSN stations) b/s Bits per second

BER Bit Error Rate

BWG Beam Wave Guide (Refers to specific DSN 34M antennas)

C&N Communication and Navigation

CARD Cloud Architecture Requirements Document

Category A Missions whose distance from Earth is < 2 x 10 6 km

Category B Missions whose distance from Earth is ≥ 2 x 10 6 km

CCSDS Consultative Committee for Space Data Systems

CDR Critical Design Review

CIMO Customer Interface Management Office

CIS Commercialization, Innovation and Synergies

CNES Centre National d'Etudes Spatiales (France)

CP Communication Program

CSO Communications Service Office

CSR Concept Study Report dB Decibels

DCN Documentation Change Notice

DDOR Delta Differenced One-way Range

A-2 SCaN-MOCS-0001

DLR Deutsche Zentrum fur Luft- Und Raumfahrt (Germany)

DoD Department of Defense

DOR Differential One-way Range

DSA Deep Space Network Service Agreement

DSM Deep Space Maneuver

DSN Deep Space Network

DTE Direct to Earth

EDL Entry, Departure, and Landing

ELV Expendable Launch Vehicle

ESA European Space Agency

FC Frequency of Contacts (For costing DSN stations)

FCC Federal Communications Commission

FCLTU Forward Communications Link Transmission Unit

FDF Flight Dynamics Facility

FY Fiscal Year

GDS Ground Data System

GEO Geosynchronous Earth Orbit

GHz Gigahertz (1 x 10 9 cycles per second)

GOCO Government Owned, Contractor Operated

GSFC Goddard Space Flight Center

HEO Highly Elliptical Orbit

HEOMD Human Exploration and Operations Mission Directorate

Hz Hertz (cycles per second)

IAD Implementing Arrangement Document

ISRO Indian Space Research Organization

ITA Internal Task Agreement

ITU International Telecommunications Union

JAXA Japanese Aerospace Exploration Agency

JPL Jet Propulsion Laboratory

A-3 SCaN-MOCS-0001

K Kilo (1 x 10 3) or Kelvin

KA-Band Frequency band:

• Deep Space (Category B) 31.8 - 32.3 GHz downlink

• Near-Earth (Category A) 25.5 - 27.0 GHZ downlink

KARI Korea Aerospace Research Institute

Km Kilometers

LAN Local Area Network

LDPC Low Density Parity Check

LEO Low Earth…