Mars Telecommunications Network RFP Shows NASA’s Next Step Toward Mars Infrastructure

Key Takeaways

• NASA’s Mars relay plan turns communications into a contracted infrastructure service.
• The draft PWS covers spacecraft, ground systems, launch support, safety, and verification.
• The Mars Telecommunications Network could reshape future Mars science and operations.

Mars Telecommunications Network RFP Moves Mars Relay From Heritage to Procurement

NASA announced on May 14, 2026, that it had issued the Final RFP – Mars Telecommunications Network (MTN), seeking industry collaboration for high-bandwidth Mars communications. The draft performance work statement for RFP 80GSFC26R0011 defines the Mars Telecommunications Network as a contractor-delivered system covering design, development, integration, testing, delivery, launch operations support, and operational commissioning. That scope places the Mars Telecommunications Network in a different category from earlier Mars relay arrangements, because NASA is asking industry to propose a full contract performance work statement rather than supply a narrowly defined component or subsystem.

NASA’s public announcement states that the network will use high-performance Mars telecommunications orbiters at the Red Planet to support future surface, orbital, and human exploration. The agency also states that the network should be ready to operate at Mars no later than 2030, and that industry responses should address current missions, future operational missions, and a science payload accommodation selected by NASA’s Science Mission Directorate.

The draft performance work statement turns a communications need into a procurement architecture. It tells offerors to incorporate mandatory work statements, either verbatim or with language that meets the intent, and to add the details needed for their own technical and business approach. NASA is leaving room for contractor design choices, but it is retaining control over requirements, acceptance criteria, oversight, data deliverables, safety visibility, and verification.

That balance matters because Mars communications are no longer a background service. Landers and rovers depend on orbiters for data return, command relay, navigation support, and operational continuity. NASA’s existing Mars Relay Network relies on five spacecraft orbiting Mars, with each orbiter relaying rover data alongside its primary science mission. NASA describes the network as an international collaboration with the European Space Agency, using spacecraft such as Mars Odyssey, Mars Reconnaissance Orbiter, MAVEN, Mars Express, and the ExoMars Trace Gas Orbiter.

The Mars Telecommunications Network RFP suggests a more service-oriented model. NASA is still specifying the mission-level responsibilities, but it is asking industry to propose how to deliver the system, manage risk, integrate launch services, support payload hosting, and maintain long-term viability beyond 2035. This framing fits NASA’s broader Space Communications and Navigation direction, which treats communications and navigation as mission infrastructure rather than isolated mission accessories.

What the Draft Performance Work Statement Requires From Contractors

The draft performance work statement uses a spaceflight work breakdown structure built around project management, systems engineering, safety and mission assurance, science and technology, payloads, spacecraft, mission operations, launch vehicle services, ground systems, and systems integration and testing. Each category forces offerors to describe how they will convert a mission concept into a delivered Mars relay system with documented requirements, acceptance evidence, and operational readiness.

The project management content is more than scheduling language. Contractors must deliver a program management plan, integrated master schedule, management review packages, configuration and data management plan, risk management reports, major review documentation, information technology security management plan, and an insight and oversight implementation plan. The records management provisions connect contract execution to federal records law, National Archives and Records Administration regulations, and NASA records policy. NASA is making clear that the project’s information record is part of the deliverable, not an afterthought.

Systems engineering carries the largest documentation load. The contractor must produce system requirements, specifications, interface control documents, hardware deliverable lists, acceptance data packages, environmental requirements, design data books, resource budget reports, assembly and test plans, verification plans, test reports, drawing trees, engineering drawings, structural analyses, thermal analyses, power analyses, electromagnetic compatibility plans, and worst-case analysis. That list reflects the nature of a Mars relay system. A communications orbiter must survive launch, cruise, Mars orbit insertion, long-duration operations, relay duty cycles, radiation exposure, thermal extremes, and software-driven service demands.

NASA’s payload provisions add another layer. The contractor must describe payload interfaces, define hosted payload constraints, accommodate a NASA science payload on a “do no harm” basis, support integration and testing with either the payload or a representative mass simulator, provide a command interface, and separate payload telemetry on the ground. This makes the Mars Telecommunications Network more than a relay bus. It could carry science capability without allowing that payload to compromise the primary communications mission.

The draft also requires a low-fidelity spacecraft simulator for payload interface testing. That simulator must emulate electrical, power, command, data handling, and flight software interfaces. It must include representative mechanical and thermal interfaces, with deployment mechanism interfaces if a deployable payload is accommodated. This early simulator requirement reduces risk by giving the payload team time to test compatibility before flight hardware arrives.

Contractors also must define interim financing payment milestones and delivery milestones with entrance criteria, acceptance criteria, verification events, deliverables, assumptions, and references to requirements. That language is procurement-oriented, but it has engineering meaning. NASA wants payment progress connected to objective evidence, not informal declarations that design work has advanced.

Why Mars Relay Capacity Shapes Science and Human Exploration

Mars surface missions generate far more data than direct-to-Earth links from a rover can efficiently return. Orbiters solve that problem by passing over a rover, receiving data at shorter range, storing it, and transmitting it to Earth through deep-space antennas. NASA says the Mars Relay Network frees rovers such as Perseverance and Curiosity for more scientific work by routing surface data through orbiters with larger antennas, more electrical power, and more regular contact with Earth.

The draft performance work statement builds on this operating model, but it looks toward a heavier mission mix. A dedicated Mars telecommunications and navigation relay system would support science data, operational telemetry, high-definition imagery, command traffic, and navigation-related services. NASA’s RFP announcement states that high-bandwidth communications are needed to relay science data, imagery, and mission information during Mars missions. A future human Mars architecture would place greater demands on delay-tolerant operations, health data, navigation support, surface systems coordination, and contingency communications.

Mars relay capacity also shapes mission design on the surface. A rover with dependable relay access can send more imagery, more engineering telemetry, and more science data. It can support more frequent planning cycles. It can reduce the burden on direct-to-Earth transmitters that have limited power and antenna constraints. Surface systems can be designed with different communications assumptions when relay passes are dependable and when orbiters offer predictable service windows.

The Mars Telecommunications Network RFP gives industry a chance to propose an architecture that supports both existing robotic missions and future operational missions. That wording matters because NASA is not buying a single-purpose communications spacecraft for one rover. It is asking for infrastructure that can scale across mission classes. The draft also asks contractors to describe extensibility and long-term system viability beyond 2035, which places service life and upgrade paths inside the procurement discussion.

Future Mars exploration will need communications systems that function across different mission phases. Entry, descent, and landing need telemetry visibility. Surface operations need routine data relay. Orbiters need Earth return paths. Future sample return activities would need coordination among surface assets, Mars orbiters, and Earth-based ground systems if NASA proceeds with an architecture requiring Mars relay support. Human exploration would add crew safety, surface mobility, habitat operations, science support, and high-volume media traffic.

The Mars Telecommunications Network does not solve every Mars communications problem by itself. Earth-Mars distance still imposes signal delay. Solar conjunction periods still affect operations. Deep-space antennas on Earth still have limited availability. Even so, a dedicated relay network at Mars would move the bottleneck away from ad hoc use of aging science orbiters and toward planned infrastructure with performance requirements, contractor accountability, and documented service interfaces.

Engineering, Verification, and Safety Demands Behind the Network

Mars communications infrastructure carries the same technical burden as any deep-space spacecraft, with the added pressure that other missions may depend on it. The draft performance work statement assigns responsibilities for systems engineering, safety and mission assurance, software assurance, supply chain risk management, cybersecurity, anomaly reporting, and verification. NASA is giving the contractor flexibility, but not freedom from evidence.

The safety and mission assurance section requires NASA access to documents, records, and test data relevant to mission success and safety. Contractors must notify NASA within 24 hours of any major anomaly or test failure that could affect on-orbit performance, mission requirements, or schedule. They also must notify NASA of changes to safety-essential or mission-essential hardware or software before implementation. These provisions preserve NASA visibility into risk, even when the contractor uses its own internal standards and workmanship processes.

Supply chain risk appears explicitly. Contractors must maintain a supply chain risk management process, provide NASA visibility into risks affecting mission-essential components, identify sole-source dependencies and long-lead items, and use counterfeit prevention measures. Those requirements reflect a hard reality of space hardware. A Mars orbiter depends on specialized electronics, propulsion components, radio frequency equipment, thermal systems, software, batteries, and materials that may have limited suppliers and long procurement lead times.

Cybersecurity is part of the mission assurance story. The draft requires controls that protect confidentiality, integrity, and availability of mission information and system resources. That wording fits a relay network that will carry mission commands, spacecraft telemetry, payload data, operational planning products, and potentially sensitive interface information. A compromised communications infrastructure system could threaten mission performance even if the spacecraft hardware remains healthy.

Verification receives its own detailed section. Contractors must define verification methods such as analysis, inspection, demonstration, and test for each requirement. They must establish verification sequence, environments, success criteria, and responsible organizations. The draft asks contractors to address the tension between a rigorous verification program and an aggressive delivery schedule. That is one of the most revealing parts of the document. NASA is not pretending that schedule pressure disappears in a commercial-style procurement. It is asking offerors to explain the trade space directly.

The verification section spans design verification, qualification testing, acceptance testing, integration and test, launch readiness verification, on-orbit checkout, and commissioning. For Mars infrastructure, commissioning matters because a relay orbiter does not become useful at launch. It becomes useful after launch, cruise, arrival, orbital checkout, ground system activation, relay service validation, and operational handover. NASA’s approach links contract acceptance to mission performance rather than physical delivery alone.

Ground Systems, Deep Space Network Choice, and Electra Continuity

The ground systems section gives offerors a consequential choice. The contractor must state whether it will use the Deep Space Network as a government furnished service. If the contractor proposes an alternative to Deep Space Network tracking, telemetry, and command services, the alternative must provide at least 6,750 tracking hours per year at performance levels equal to or better than a Deep Space Network 34-meter beam waveguide station. That threshold sets a high bar.

NASA’s Deep Space Network uses large antennas in California, Spain, and Australia to support deep-space missions. NASA describes the DSN as three antenna complexes spaced about 120 degrees apart on Earth, allowing the network to scan almost any part of the sky at any time. The draft performance work statement’s reference to a 34-meter beam waveguide station gives industry a concrete performance benchmark for any proposed alternative.

That requirement also exposes the economics of Mars communications. A contractor may be able to build or contract alternate ground capacity, but NASA wants evidence of technical capability, maturity, schedules, licenses, availability, and funding. A promised future ground network is not the same as an operational one. For a Mars relay service, ground availability becomes part of mission assurance. An orbiter at Mars that cannot reliably send data to Earth is not an effective service node.

The draft’s Electra provisions connect the new network to past Mars relay architecture. The contractor must state whether it will use Electra UHF Transceiver radio items listed as government furnished property. If proposing an alternative, the contractor must explain how the substitute meets the relevant requirements. Electra matters because it has served as a relay technology bridge across Mars missions. NASA identifies MAVEN’s communications package as an Electra UHF system that provides data relay from rovers and landers on Mars back to Earth.

Electra continuity can reduce interface risk for missions that already understand the relay model. A new system that supports legacy proximity links can help preserve compatibility with existing users and test equipment. The draft includes ground and compatibility test hardware such as advanced proximity link test hardware, legacy proximity link test hardware, payload ground integration unit test hardware, and a low-fidelity spacecraft emulator. These items show that NASA expects a service transition, not a clean break from heritage systems.

Ground software assurance receives attention as well. Contractors must identify and classify safety-essential and mission-essential ground system software, disclose known defects or limitations, and provide NASA with visibility into problem tracking upon request. For a communications network, ground software controls scheduling, telemetry processing, command products, data routing, databases, and service delivery. The spacecraft may be the visible asset, but ground systems decide whether the service works at mission scale.

Launch, Payload Hosting, and Commercial Supply Chain Effects

The launch vehicle services section requires the contractor to identify and justify the selected launch vehicle and launch service provider using mission requirements, schedule constraints, and cost considerations. NASA is not dictating a launch provider inside the draft performance work statement, but it is asking the contractor to prove that the launch choice fits the mission. That includes payload mass capacity, trajectory performance, orbital insertion accuracy, interface capabilities, margins, and compliance with Mars Telecommunications Network mission requirements.

Launch integration creates a chain of obligations among the contractor, NASA, and the launch service provider. The contractor must define mechanical, electrical, thermal, and functional interfaces between the spacecraft and launch vehicle. Interface control documents must capture physical, functional, and procedural details. The contractor must coordinate spacecraft compatibility with launch vehicle capabilities and constraints, support launch site integration, and manage adapter design and verification.

Transportation and launch site operations create another business and operations layer. The contractor must plan safe transport from its facility to the launch site, including packaging, handling, environmental monitoring, and security. It must coordinate spacecraft processing, propellant loading, pre-launch checkout, and final closeouts. These responsibilities pull the Mars Telecommunications Network into the broader space economy through logistics providers, environmental control equipment, contamination control services, ground support equipment, launch site labor, and range safety compliance.

Payload hosting expands the supplier picture. A hosted NASA science payload may require payload interface hardware, data handling accommodations, thermal control support, telemetry separation, test facilities, simulator delivery, and payload operations coordination. This can create work for instrument builders, test service providers, software teams, interface engineers, and mission operations groups. The draft’s “do no harm” framing makes the payload secondary to the relay mission, but it still gives NASA a way to extract science value from a telecommunications platform.

The supply chain provisions reinforce the commercial impact. Contractors must track sole-source dependencies, long-lead items, counterfeit prevention, and disruptions that could affect mission success or schedule. A Mars orbiter procurement can ripple through suppliers of radiation-tolerant electronics, radio frequency components, propulsion systems, batteries, solar arrays, thermal hardware, structures, software tools, and test services. That ripple matters because suppliers that can meet deep-space reliability standards occupy a narrower market than suppliers for lower-risk terrestrial systems.

Commercial participation does not make the program simple. Mars telecommunications requires deep-space navigation, reliable power, thermal survival, long-duration flight software, radiation-aware design, launch vehicle integration, planetary protection planning, relay protocol compatibility, ground system maturity, and operational commissioning. The draft performance work statement suggests NASA wants commercial execution with agency-level discipline, not a consumer-style service purchase.

Space Economy Meaning for Mars Infrastructure

The Mars Telecommunications Network RFP is an infrastructure procurement, and that makes it relevant beyond NASA’s Mars program. Space economy discussions often focus on launch vehicles, satellites, or downstream data markets. Mars communications adds another category: deep-space service infrastructure. It links spacecraft manufacturing, launch procurement, radio frequency systems, software, ground networks, cybersecurity, operations, science payload hosting, and long-duration service management.

The procurement also shows how government demand can shape a market before a fully commercial customer base exists. Mars relay services do not yet have many non-government customers. NASA is the anchor buyer, and its requirements set the standards that contractors must meet. That dynamic resembles earlier phases of Commercial Resupply Services and the Commercial Crew Program, but Mars adds distance, limited traffic volume, higher communications delay, greater autonomy demands, and a smaller near-term customer pool.

Defense and security relevance sits in the architecture rather than in the stated mission. Deep-space communications technologies, secure command paths, resilient ground systems, supply chain risk control, and high-assurance software practices overlap with broader national space capability. The draft performance work statement does not describe a defense program, yet the same industrial base that builds reliable deep-space communications can support national missions requiring secure long-distance links, resilient operations, and high-confidence verification.

The RFP also suggests an industrial transition from bespoke mission support toward planned service continuity. Earlier Mars orbiters often gained relay duties because they were already present and technically capable. The Mars Telecommunications Network would be planned from the start as a relay and navigation asset. That change can make interfaces cleaner, accountability clearer, and service planning more predictable. It can also create new dependencies if future Mars missions assume the network will be available.

The long-term viability requirement beyond 2035 points toward lifecycle economics. Contractors must think about system aging, software maintenance, ground system refresh, compatibility with future users, staffing, supplier obsolescence, and operations funding. A Mars relay orbiter launched late in this decade could serve missions through the 2030s if it performs as expected. That service life pushes procurement analysis beyond acquisition cost and into sustainment.

Mars infrastructure will remain capital-intensive and government-led for the foreseeable future. The customer base is too small, the distances too large, and the operational risk too high for a purely commercial Mars communications market to emerge quickly. Even so, the Mars Telecommunications Network could establish contract models, interface standards, and supplier experience that later missions can use. It gives industry a route into deep-space infrastructure without waiting for a self-sustaining Mars economy.

Summary

NASA’s Mars Telecommunications Network RFP turns a long-standing operational need into a structured infrastructure procurement. The draft performance work statement covers far more than a spacecraft bus and radio payload. It defines a contractor role spanning project management, records control, systems engineering, safety, software, cybersecurity, payload hosting, launch support, ground systems, verification, and commissioning.

The document’s most significant message is that Mars communications have become a mission architecture issue. Rovers, landers, orbiters, science payloads, and possible future human systems need more dependable relay services than aging heritage orbiters can guarantee indefinitely. NASA’s 2030 operational target, long-term viability language, and Deep Space Network alternative threshold show that the agency is trying to buy a service capability with measured performance, documented interfaces, and objective acceptance evidence.

For the space economy, the Mars Telecommunications Network creates a template for deep-space infrastructure contracting. It gives commercial suppliers a defined role in Mars operations, but it also shows the limits of commercial shorthand. Deep-space services still demand agency oversight, strong verification, supply chain discipline, cybersecurity controls, launch integration, and long-duration operations planning. The result is a procurement that could shape the next phase of Mars exploration before the first dedicated network spacecraft begins service.

Appendix: Useful Books Available on Amazon

• Packing for Mars
• The Design and Engineering of Curiosity
• Mars Rover Curiosity
• Curiosity
• Missions to Mars

Appendix: Top Questions Answered in This Article

What Is the Mars Telecommunications Network?

The Mars Telecommunications Network is NASA’s planned relay and navigation communications infrastructure for Mars missions. It is intended to support surface assets, orbiters, science payloads, and future exploration needs through high-performance telecommunications orbiters and associated ground systems. The 2026 RFP asks industry to propose how to deliver, launch, commission, and support that system.

Why Does Mars Need Dedicated Telecommunications Orbiters?

Mars surface missions return far more data through orbiters than they can efficiently send directly to Earth. Relay orbiters reduce the burden on rover transmitters, improve data return, and support more flexible mission planning. A dedicated network would reduce dependence on older science orbiters that were not all launched primarily as communications infrastructure.

What Does the Draft Performance Work Statement Require?

The draft requires contractor responsibilities across project management, systems engineering, safety, payload hosting, spacecraft development, mission operations, launch services, ground systems, and verification. It asks offerors to include mandatory work statements and add the details needed for their proposed approach. It connects contract milestones to acceptance criteria and verification evidence.

Why Is the Deep Space Network Mentioned in the Draft?

The Deep Space Network is NASA’s main Earth-based communications system for deep-space missions. The draft asks contractors to state whether they will use it as a government furnished service. If they propose an alternative, that alternative must meet a high performance and availability threshold measured against a 34-meter beam waveguide station.

What Is the Role of Electra in Mars Relay Communications?

Electra is a software-defined ultra-high frequency relay radio used in Mars missions. It supports communications between surface assets and orbiters, helping return data from rovers and landers. The draft asks contractors to state whether they will use government furnished Electra radio items or propose an alternative that meets the relevant requirements.

How Does the RFP Affect Mars Science Payloads?

The draft requires the contractor to accommodate a NASA science payload on a “do no harm” basis. That means the payload can gain access to the spacecraft platform, but it cannot compromise the relay mission. The contractor must support interfaces, simulator testing, command access, telemetry collection, and ground delivery of payload data.

What Makes Verification So Important for This Procurement?

Verification proves that each requirement has been satisfied through analysis, inspection, demonstration, or test. A Mars relay system must work through launch, cruise, Mars arrival, checkout, and operations. The draft requires contractors to define verification sequence, environments, success criteria, responsible organizations, and NASA visibility into verification events.

Why Does the Draft Discuss Supply Chain Risk?

A Mars telecommunications orbiter depends on specialized hardware, software, materials, and test services. Some components may have limited suppliers or long lead times. The draft requires contractors to identify sole-source dependencies, track long-lead items, prevent counterfeit parts, and notify NASA about disruptions that could affect schedule or mission success.

How Could the Mars Telecommunications Network Affect the Space Economy?

The network could create demand for spacecraft manufacturing, communications payloads, launch services, ground systems, cybersecurity, mission operations, payload integration, and test services. It gives industry a defined role in deep-space infrastructure. NASA remains the anchor customer because Mars communications does not yet have a broad commercial customer base.

Does This RFP Mean Mars Communications Are Becoming Commercial?

The RFP shows commercial execution inside a NASA-defined mission framework. Contractors can propose architecture, implementation approach, launch integration, and service delivery methods. NASA still controls requirements, oversight, safety visibility, verification, and acceptance. The result is a hybrid model where industry delivers infrastructure under government mission standards.

Appendix: Glossary of Key Terms

Mars Telecommunications Network

A planned NASA communications and navigation relay system for Mars missions. It is intended to support surface assets, orbiters, science payloads, and future exploration needs through high-performance telecommunications orbiters and associated ground systems.

Performance Work Statement

A contract document that defines work a contractor must perform. In this case, the draft performance work statement gives offerors mandatory language and structural guidance for proposing a contract-ready work statement.

Request for Proposal

A formal procurement document asking industry to submit offers for a defined requirement. NASA’s Mars Telecommunications Network RFP asks companies to propose how they would deliver the relay system and related services.

Deep Space Network

NASA’s global network of large antennas used to communicate with spacecraft beyond Earth orbit. It supports command, tracking, telemetry, science data return, and navigation for many deep-space missions.

Electra UHF Transceiver

A software-defined Mars relay radio used to support ultra-high frequency communication between Mars surface assets and orbiters. It helps rovers and landers send more data than direct surface-to-Earth links can usually support.

Government Furnished Service

A service supplied by the government for contractor use during contract performance. In the draft, the Deep Space Network may serve as a government furnished service if the contractor elects to use it.

Government Furnished Property

Government-owned equipment provided for contractor use. The draft references Electra radio items as possible government furnished property that contractors may use or replace with an approved alternative.

Interface Control Document

A technical document that defines how systems connect and interact. It may cover physical, electrical, thermal, software, data, and procedural interfaces among spacecraft, payloads, launch vehicles, and ground systems.

Verification

The process of proving that a requirement has been satisfied. Verification can use analysis, inspection, demonstration, or test, depending on the requirement and the evidence needed for acceptance.

Commissioning

The phase after launch and arrival when a spacecraft system is checked, configured, tested, and accepted for operational use. For a Mars relay network, commissioning confirms that the service can support mission users.

Hosted Payload

A payload carried on a spacecraft whose main mission is something else. The Mars Telecommunications Network draft allows for a NASA science payload, provided it does not harm the primary relay mission.

Supply Chain Risk Management

The process of identifying and controlling risks in suppliers, components, materials, software, and delivery schedules. For deep-space missions, supply chain risk can affect reliability, schedule, cost, and mission readiness.