NASA Space Communications and Navigation Embracing Commercial Relay Services
The Story
Welcome to this strategic, technology-driven episode of the NASA Live Video Podcast: "NASA Space Communications and Navigation: Embracing Commercial Relay Services."In this episode, we explore the major paradigm shift transforming how space missions transmit critical data back to Earth. For decades, NASA's Space Communications and Navigation (SCaN) program has relied primarily on government-owned infrastructure like the Tracking and Data Relay Satellite (TDRS) constellation. Today, NASA is actively transitioning toward commercial satellite communications to power the next generation of Earth science, low Earth orbit (LEO) research, and deep space exploration.
We dive into the technical frameworks and public-private partnerships driving NASA's Communications Services Project (CSP). Discover how integrating commercial GEO and LEO relay satellites enhances bandwidth, reduces operational costs, and ensures robust, continuous data links for future scientific satellites and crewed missions. We also analyze the engineering challenges of inter-operability, optical/laser communications standards, and cybersecurity protocols required to build a seamless, commercially supported space communication architecture.
Whether you are a satellite communications engineer, a space policy analyst, a aerospace industry professional, or a space enthusiast eager to learn how commercial space tech is modernizing NASA's orbital network, this episode delivers critical industry insights. Subscribe to the NASA Live Video Podcast to stay at the absolute forefront of space exploration, satellite communications, and cutting-edge space science!
Speaker 1: Welcome to the TDRS CSP Town Hall. I'm Caitlin O'Neill, Director of Strategic Communications, and I think I speak for all of SCAN when I say we're so glad you could join us today for this important conversation on network sustainability. Today's Town Hall will focus on NASA's transition to commercial relay services, where our panelists will discuss the benefits of a commercial-first approach. With us we have Mr. Greg Heckler, SCAN's Deputy Program Manager for Capability Development, Mr. Joseph Downey, Project Lead Engineer supporting SCAN's communication services project, Mr. Steven Creech, Assistant Deputy Associate Administrator for the Moon to Mars Program Office, and Mr. Andrew Maynard, SMD Assistant Deputy Associate Administrator for Programs.
Speaker 1: Reliable space communication and navigation systems are critical to every NASA mission. Spacecraft commands, never-before-seen images, and scientific data are sent and received daily through NASA's network. For over 40 years, the tracking and data relay satellite constellation has provided resilient communications and near-continuous information relay services to a wide range of space missions. This includes the Hubble Space Telescope, the International Space Station, and countless human spaceflight missions.
Speaker 1: Stepping into the next phase of space communication services, industry will work alongside NASA as new missions leverage their network capabilities. Commercial space partners will expand our space infrastructure, driving forward space communication capability, development, and operations, ultimately providing greater opportunities for discovery. Whether you're here today to get answers to your questions or simply listen and learn, We hope you will walk away with a better understanding of NASA's path forward.
Speaker 1: Now, it's my pleasure to introduce Mr. Kevin Coggins, who will be moderating our panel discussion. Kevin is the Deputy Associate Administrator for the SCAN program here at NASA and is responsible for the development, acquisition, and management of reliable and cost-effective communications and navigation services to support NASA and other government agency space requirements. Today, he's working with commercial partners to build a sustainable space ecosystem. one that will accelerate innovation and offer a vibrant market while also ensuring user needs are met.
Speaker 1: Kevin and our panelists will answer questions and share more on how NASA SCAN is transforming space communication networks from a government-centric paradigm to a commercial, collaborative, and interoperable network.
Speaker 2: Kevin?
Speaker 3: All right. Thank you, Caitlin. And thank you to everyone that has joined us here in the room virtually, and thanks to our panelists. I'm looking forward to a very exciting discussion today, a continuation of discussion some of us have been having, and the beginning of a discussion, you know, that's going to include RFIs, draft RFPs, and ultimately a new capability. Many of you are familiar with the TDRS constellation. It's been around for decades. Many of you might not know, it was one of the things that the space shuttle carried up in the shuttle missions.
Speaker 3: They usually had a TDRS satellite in the bay. And once, you know, before the TDRS satellites were up, the astronauts and people in the ISS, they got time off, right? There was time when you couldn't talk to them, and they enjoyed that. I've talked to many astronauts still in NASA, and they really enjoyed that time when they could just have, you know, time on their own and to themselves, not being told what to do every minute. But then we got a lot of TDRSs up there, so we had continuous coverage.
Speaker 3: We've launched science missions that have used TDRS. We depend on it for human spaceflight. We depend on it for launch. It is an amazing capability. However, it is an old capability. It's an aging capability. It's a government-owned, government-operated capability in Earth's orbit. It doesn't make business sense anymore for the government, and it also takes away market share for industry. And so one of the purposes of our CSP program is to help grow this commercial space ecosystem around the Earth so that we can move missions off of TDRS and from these launch needs and from human spaceflight to commercial partners.
Speaker 3: But market forces determined what people built under CSP. So we had a couple things that were left out of that, mainly some of the unique things TDRS provides in S-band and KAKU band. And so we have missions that still need the capability, but TDRS is at the end of its life. We seem to be retiring a TDRS satellite every year. And come 2030, we're only going to have a couple left. And in the 2030s, right, we'll see the Constellation switch off, go away, get completely retired. So by then, we need to have something that can provide some of these capabilities.
Speaker 3: We still want market forces to drive what we do, but... What ties us is S band, KA band, KU band. So what we want to do is work with industry to figure out how do we make these bands available to you in a commercial platform so that you can service us and then bring others, others that like to use those bands or could, into those frequency bands. That's a big move. That's a big move.
Speaker 3: You know, NASA's– in the early days of NASA when– Let's even pick on Apollo, right? We had to build infrastructure all over the world, government-owned, government-operated infrastructure everywhere, direct-to-Earth antennas. We built little towns all over the place around these capabilities. Over time, some of them shut down. Some of them grew into what's the deep space network today and even some near-space network elements. But there's one special case I want to talk about, which is kind of a model for what we like to do at NASA and SCAN with commercial partners.
Speaker 3: It's the KSAT model around the Landsat mission. We built this antenna at Svalbard. And after the Landsat mission, we kind of didn't need the antenna anymore. So we turned to our partners over there and we said, do you want it? And KSAT in Norway said, you know, we're going to scale a business around it. And now they're one of the largest DTE providers in the world.
Speaker 3: We see what we're doing with TDRS here and CSP with this follow-on activity as a similar thing. We have the spectrum, and we have users. Do you want it? Let's work that out. Let's figure that out. We're trying to take a very commercial-first approach. We understand, in this case, though, we have to drive some requirements in it because we need backwards compatibility for our science missions. We need backwards compatibility for certain things. But we're not going to restrict you. to just our requirements and our needs and the ways we use the frequency today.
Speaker 3: So I think it's very important to note. I'm excited for this panel today. We've got all of your questions. I've got a big stack of questions here. And in just a second, I'm going to begin the moderated discussion. I've got a final note. Industry partners, one reason we're being so forthcoming with this information and broadcasting so much and that we're going to share so much in the RFI is because we can't do it alone. We know you can't do it alone. We want to encourage you to work with each other, form partnerships, form a competitive field to come after this competition.
Speaker 3: We want you to have close dialogue with us constantly. Come visit us. Come see us. Talk to some of these leaders on the stage. Submit questions. Submit white papers. Shape this. Before I was at NASA, I was in industry. If you don't shape it, you don't win it. So what I'm encouraging you is shape this. Learn. Ask questions. And this is one of many forums you're going to be able to do that. So thank you for coming today, and let's get into some of these questions. And welcome, panelists. Thanks for taking the time out of your day.
Speaker 3: Welcome, Kevin.
Speaker 2: All right.
Speaker 3: The TDRS constellation is declining faster than anticipated and will no longer support new missions, only existing missions. What is TDRS flyout timeline, and can you share how we mitigate anticipated risks? Greg Heckler. Sure. Thanks, Kevin.
Speaker 4: And let's advance the slides in the next one. I had the privilege and opportunity to be asked by the agency to help lead us through this transition for about four years now. I also had the privilege before I came to NASA headquarters on working a so-called third-generation TDRS project for about six years. Those are some of the dearest experiences I've had and understand the people on the mission make it really, really important, right? It's just not about the things we build. It's about who we do it with.
Speaker 4: TDRS is a long legacy. It started in the 70s, of course, right, coupled with shuttles. Those in the common air business understand there's a connection actually to GPS as well. There's a common community, common technology there. But that legacy is here with us today. Every astronaut conversation from the space station, every picture you see from the Hubble Space Telescope has come through this constellation, this capability.
Speaker 4: I've learned a lot about the agency going through this transition. We've had thoughts about what this forum really is. It's about the future, but it's also about recognizing not just the capabilities, but the people who helped built it, multiple generations. Yeah, I worked on third-generation TDRS. I was really the third generation, third cohort, that first being the people in the 70s who had the dream, the vision, worked to get those initiatives. satellites up, right? Filled out the first ground station at White Sands.
Speaker 4: Worked on the first generation of TDRS, TDRS 1 through 7. Then there was a second cohort. Some of you may know them. Jeff Gramling. Dave Littman, who's no longer with us.
Speaker 3: Paul Buchanan.
Speaker 4: I had the opportunity and privilege to learn from them during my experience on that project. And so today you can think of it, this is a retirement party. And so I'm going to talk a little bit about the teacher's mission, what it's helped us do, and how we're going to approach that retirement. So before I get into that, if this is a retirement speech, let's give a round of applause, not to the capability, but the people that have dedicated their lives and careers to this system over the last, now almost 50 years.
Speaker 3: So let's do that. Thank you. Next slide, please.
Speaker 4: So Kevin talked a little bit about the missions that TDRS enabled. Talked about it being coupled to the shuttle, right? Conceived at the same time in the 70s. Yeah, the TDRS launched, TDRS were launched on the shuttle mission, TDRS 1 through 7. Some of you may not know The payload in the Challenger was actually a TDRS satellite that we lost. So we understand the importance of human spaceflight and safety. So it enabled the shuttle. Of course, the ISS I don't think could have been built without TDRS, the high data rates, the continuous connectivity, allowing us to see those helmet cams in real time.
Speaker 4: We had one of our leadership from the ISS come over yesterday and We had a blip in our Guam ground station, and we lost coverage over that area of space. And the first thing they did was march down to the scan office. When can you recover this capability? We have a spacewalk going on. It's safety of life. We need to see the helmet cam. So we understand that. We have our human spaceflight representative, Steve Creech, here. We want Our user community understand we know those things, and we want our new industry partners to also appreciate what we're asking them to do.
Speaker 4: Of course, ISS evolved, right? As the shuttle was retired, there was COTS and commercial crew. The agency made a decision, right? We always talk about risk. We wanted those industry partners to focus on certain risks, and that's building the spacecraft, not how you communicate with it. And so we made a choice at the time, hey, we're going to offer TDRS. That's your catcher's mitt. That's your safety of life. I had one colleague call, SCAM provides the air to the rest of the agency. And so we wanted to make sure our industry partners didn't have to worry about that at that time.
Speaker 4: And so TDRS was built into several of the COPS and commercial crew vehicles. Artemis itself, right?
Speaker 3: Orion, SLF.
Speaker 4: Maybe even some initial support to help bootstrap some of the human landing systems, their needs in LEO. So it's making contributions there. Launch vehicles. Great dialogue over the last six months with the commercial and international launch vehicle community. In the late 90s, early 2000s, again, we made a national decision with this national asset to help make our commercial launch vehicle community, our industry, more competitive by offering them this unique capability to support their ability to launch anywhere and anytime.
Speaker 4: And of course, science. We talk about Hubble.
Speaker 3: Astrophysics.
Speaker 4: We've had a great dialogue with the astrophysics community. They need that 24 by 7 connectivity to coordinate multiple science missions and ground telescopes to go look at gamma ray bursts.
Speaker 3: We understand astrophysics.
Speaker 4: Maintaining those types of capabilities, maybe not what they know today as we evolve the system in the future. The A-train, right, Aqua, Aura, and Terra built in the 90s. These things would not have happened without this capability, and we're proud to be that third generation to maintain it and shepherd it gracefully into retirement.
Speaker 2: Next slide.
Speaker 3: So how did we get here?
Speaker 4: How did we make this decision? What was the rationale? Obviously, TDRS started, I like to say, before I was born in the 70s. Proud to have been part of that third generation, but we built the system up over time, initially with three satellites. Right now, I think we have nine satellites in orbit, soon to be eight, providing global coverage. Kevin talked about astronauts not wanting to be in contact with FOD all the time or mission control all the time.
Speaker 3: We closed.
Speaker 4: What was called the zone of exclusion in the late 90s, adding in birds over the Indian Ocean region. So we had truly seamless connectivity. I was there for that final teachers launch, Teachers M, which became Teachers 13 once it was commissioned. I was there for that last day, the final staff meeting for the Teachers Project that had been open since roughly 1973. I was there when Boeing, our partners on the second and third generation TDRS, we had our last review, that pre-ship review on TDRS-M.
Speaker 4: There were people in tears.
Speaker 3: They were sobbing.
Speaker 4: They fought to be on the third gen project because they understood the capability and the national importance when they executed the second gen. There's feelings wrapped up in this. And we wanted to acknowledge those feelings through this transition. Ultimately, all good things come to an end. We have legacy missions, FMV missions, ISS. We know those are going to keep flying. We could not continue to add new missions onto the constellation, or we would end up in a situation where we did not have enough supply, enough TDRS in the sky to meet all of those needs.
Speaker 4: And so after the unanticipated failure of TDRS-8 in late 2022, We made a decision in SCAN. We had to work with our mission directorate stakeholders and say, we have to make a heavy-handed decision. We need to move forward. We cannot make new commitments. Even some of the legacy missions, the launch vehicles, we may need to ask them to transition sooner rather than later. And so worked with our stakeholders, had those tough risk-based conversations. It drove open transparency across the agency. talking about when SMD missions will retire, right, because their satellites don't last forever.
Speaker 4: They run out of fuel. They were open and transparent, sharing that information with us. We worked with ISS, right, ISS retirement, also kind of evolving at the same time we made this decision. And ultimately, last November, at the APMC, the highest kind of NASA decision-making forum, We've made a decision to no longer allow so-called new missions, right, onto the legacy TDRS system. New missions will have to be serviced by new Earth Relay capabilities. I look forward to Joe talking about those in a few minutes.
Speaker 4: So as we move forward, individual TDRS are going to be retired eventually in the late 2030s probably. Then we will quietly turn off the lights for the final time. And this part of the agency's history that a lot of people don't know. I hope there's someone out there who's curious and can write that book or chapter.
Speaker 3: Next slide.
Speaker 4: So what does the flyout look like? These are all projections, right? We do the best we can to model how these satellites will decline. Right now, we have eight in orbit. There's actually nine soon to be retired, so we did not put in on this chart, but we anticipate We will be down to a so-called, we call it a three-ball constellation by the end of the 2020.
Speaker 3: Of course, this isn't perfect.
Speaker 4: It could happen as early as 2028, as late as 2033, but we need to manage our demand on the legacy system downwards over the next five to six years. People ask questions. Are you trying to artificially turn off Deidre? No, that is not true. We only turn them off and supersync them when it's unsafe to continue operating them or their payloads have degraded where they're not actually providing utility or services. Teachers 10 will retire this summer, and we're carefully watching each of the legacy satellites and trying to update these projections, and we'll share them with our entire community, both inside and outside NASA, from an annual basis from here onward.
Speaker 4: Big decisions, a lot of risk. I talk about, if you listen to me, touching a third rail. I was asked to touch a third rail. But the entire agency rallied around SCAN, around me as an individual, and I'm really proud and feel privileged on being able to lead.
Speaker 3: NASA through this transition. So that's where we are.
Speaker 4: I hope people who are involved in this see the opportunities that I see and the tremendous capability that industry has to offer the agency.
Speaker 3: We'll learn things. Risks will be taken.
Speaker 4: There will be hiccups, right? We all build satellites. We're in this business. It's not going to go perfectly. But we need to charge into the future. And TDRS, a system that was designed in the 70s, was really holding us back. And so now is the time for change. SCAN is committed to change. And I think our user community is starting to see what we're seeing.
Speaker 3: And I hope they can.
Speaker 4: Talk about some of the opportunities they see in this transition.
Speaker 3: So I think that was it. And we can transition to the next speaker. Thank you, Kevin. Thank you, everyone. All right. Thanks, Greg. A couple things to note. The chart that was just up showed the satellite's decline, but you can imagine the satellites are getting used right now. As they decline, these users need to go somewhere, right? These missions need to go somewhere, and that's a big driver for what we're doing. So instead of building new government-owned satellite relay infrastructure, we decided to leverage our investment in the domestic SATCOM market through CSP.
Speaker 3: and direct new missions to acquire all necessary SATCOM services from commercial service providers. So, Joe, this next question is for you. What does the future of space communications look like under the CSP partnership model? And some might be unfamiliar with the model, and so maybe break that down as well.
Speaker 1: Sure.
Speaker 3: Yeah, we'll get right into all of that. Under the CSP model, we are pioneering a new era of space communication and navigation and features instead of government the specified systems partnering with industry. Commercial industry has invested and is continuing to invest billions of dollars into a thriving SATCOM market. And we are partnering with them to extend those services, which currently service terrestrial, maritime, aviation customers, extending those to cover space-based users. NASA's not alone.
Speaker 3: We are not the only customer in this. There are benefits to enabling this capability for United States space economy, both government and commercial. Under this model, we are creating a portfolio of diverse service offerings. This is reflective of the diversity that's in the service providers today. We have large LEO constellations, constellations in MEO, different altitudes, inclinations, and in GEO as well.
Speaker 3: This portfolio of diverse service offerings is needed to cover all of NASA's use cases, and these different specific orbits are tailored and have key benefits for specific use cases. Next, I'll highlight some of the features that we see in these commercial services that are coming on board that will be revolutionary for our missions. On-demand capabilities. No need for lengthy scheduling cycles. These service providers today can rapidly provision services on demand, machine-to-machine interfaces, enabling our mission operators to communicate with their satellite anytime they need to, wherever they need to.
Speaker 3: High data rates, we're seeing orders of magnitude increase. Many of our upcoming systems that you're all aware of are featuring optical communication systems that's maturing that technology and providing persistent, high-rate connectivity that will open up new avenues for our missions. Not capacity limited. If you take a look at the total NASA data capacity that we could ever use, it is a small, small fraction of the capacity that commercial providers can provide. This means that we won't have to have competition over limited resources for access to our missions.
Speaker 3: to communication resources. And finally, enabling greater autonomy with these on-demand persistent services. This will be a game changer for NASA missions. We strongly believe that new science opportunities will emerge enabled by these new communication capabilities. Next chart. So what is our strategy? SCAN, we are acquiring commercial services a little bit differently per the mission group. For science missions in Artemis, SCAN's role is the acquirer, and we will be acquiring commercial services for the NASA mission community.
Speaker 3: TDRS will continue to provide legacy support for those missions, and we will be establishing these new relay services by 2031. CSP projects role, our role here is to validate and transition these services to the NSN, and the NSN will then manage the operations. For commercial LEO destinations and commercial launch vehicles, SCAN has a different role. Here we're a facilitator. And really what we're trying to do here is to facilitate direct business-to-business relationships between the communities and the providers.
Speaker 3: CSP, we will have an active role in this as well to connect stakeholders to industry partners, share lessons learned, some analysis as well. Finally, for the International Space Station and supporting vehicles, here CSP won't have an active role since we are currently not pursuing backwards-compatible services. Next chart. So this is our three-phase approach for the CSP project, ultimately ending with our commercial service acquisition in phase three. But we'll start phase one. Phase one, this has been completed.
Speaker 3: We extensively studied, going back to a number of studies, number of years. I was part of those. I know Greg was part of those and many others, studying how to do this transition. What was commercial's capabilities? We did a number of RFIs. We engaged industry. And then we did some broad agency announcement studies as well to get their input. Part of it is technical feasibility, seeing if these services would be able to service our missions, taking a look at extending their capabilities to space-based users, but also the business case.
Speaker 3: Very important. We need to have a viable market here for SCAN to be able to use these services. During this time, we also established use cases, took a look at how TDRS was currently being used, the performance goals, to ultimately lead to the funded Space Act agreements. The other outcome of the study was that commercial had capabilities and had the infrastructure, but in order to meet our timeline and to extend those services to space-based users, we did need a little bit of an investment, and that's through the Phase 2 Funded Space Act Agreements.
Speaker 3: In June of 22, we awarded six Funded Space Act Agreements with six commercial SATCOM providers. They're listed right here. Amazon, SpaceX, Telesat, and Fiasat, which has acquired MRSAT, and SES. These demonstrations, we're about halfway through the Funded Space Act agreements, and we're just now entering the demonstration phase. This is the very exciting part where, as these services are being fielded, now we're seeing the demonstrations and see them using operations. These demonstrations, this is not a technology demonstration.
Speaker 3: We are not demonstrating just an optical terminal by itself. These are end-to-end services. That was vital and a huge part of these Funded Space Act agreements. So we are exploring the business side, the operational side, the interfaces, the user terminals, the ICDs, the user guides, everything that we will need to be able to use this as an operational service. I'd like to quickly celebrate some of the accomplishments of our partners. Amazon, if you read Space News, you already know most of these, but Amazon has launched their first round of 27 satellites for their constellation, so very happy to see that first set go up, and there's more along the way.
Speaker 3: SpaceX, we just completed a demonstration with a FRAM-2. It's the, their, it was a crewed private mission on a crewed Dragon capsule. It was outfitted with 100 gigabit per second optical terminal, and for three and a half days did routine optical communications to provide internet to their crew, which was a very successful demonstration, and they'll be sharing more of their detailed analysis with us in the coming months. Telesat, they recently completed a design review for their constellation. Their light-speed constellation will feature SDA-compliant terminals and will set the deploy here in 2026.
Speaker 3: Viasat and Inmarsat already has existing operational services, an L and KA band. These geosatellites are in orbit today, and they will be adding capacity in this year. And then finally, SES has eight of their 13 satellites deployed for M-Power in orbit. The last two just launched recently. And their first demonstration, there's a number of demonstrations that we're doing. The first demonstration spacecraft is with Planet Labs. So we have a company that looks a lot like NASA Science Mission. So this is a very interesting demonstration spacecraft that is doing Earth observation.
Speaker 3: And that spacecraft is launched in January, and we'll begin to do demonstrations with M-Power with them soon. These are our funded Space Act agreements. I'd also like to acknowledge we have non-reimbursable Space Act agreements with a growing number of companies. Kepler is one of them. I think they're here. And that's another good way that we can facilitate conversations between NASA and industry. So where are we heading? The commercial acquisition, this is the next step in our process. We will be performing additional market research be finalizing our acquisition strategy, and then completing the service requirements.
Speaker 3: These service requirements will be with the RFP and define NASA's minimum thresholds for a useful service to NASA. This is an open competition. Although there has been some history with the Fund of Space Act agreements, this is open. We are looking for mature services from any eligible provider that can provide us our, that can meet our needs for our spacecraft. After the RFP, there's the validation activity. And then after we pass our operational writings review, they can enter operations and be entered into the NSN catalog.
Speaker 3: Next chart. So let's talk about the acquisition timeline. Our goal is to deliver these operational services by 2031 and add them into the NSN portfolio. Going back here, the first step I have here is an RFI. I'm happy to announce that there will be an RFI released here in a few weeks. And we're looking for a good response from industry to help with a lot of key items. Tell us about your service capabilities. And it's quite comprehensive. It's about the business side. It's about the information you can provide on your user terminals.
Speaker 3: tell us about any tracking and radiometric services you might have, fill in some gaps that we're seeing. So the other important thing about this RFI is that under the Funded Space Act agreements, we're a little bit limited in what we can share with our mission community. We're hoping through this RFI that we'll be able to share user's guides and information to share that with our user community so they can start thinking about how to use your services.
Speaker 3: Throughout this timeline here, we are engaging with our mission stakeholders.
Speaker 3: So the service requirements review is something we'll be working hand-in-hand with all the mission directorates and with the NSN. There will be opportunities to review those service requirements in a second RFI in Quarter 2, 2026. We will provide a draft of the service requirements for industry to provide us feedback. And then finally, the RFP in 27, and then on to the awards. I think that's my last chart. So, again, I just want to reiterate on the RFI being an excellent opportunity to provide us with more information and also feedback on our validation strategies.
Speaker 3: All right.
Speaker 2: Thank you. All right.
Speaker 3: Hey, thank you so much. All right. The Artemis missions rely on NASA's Near Space Network and Deep Space Network. to communicate critical data to and from the Earth. Steve, this next one's for you, your introductory question. What modifications are being made to incorporate the new partnership model to ensure mission continuity? Yeah, thanks, Kevin. Like you said, really, the capabilities that SCAN brings forward, we could not do our missions without them, right? I kind of see this as transparent, the new model.
Speaker 3: You know, a lot of things that we're doing, we're acquiring in a more commercial model which in my opinion we should do when that ecosystem is out there. And so I see us, you know, what we really need is a seamless transition from TDRS to these new capabilities. Greg kind of touched on it, obviously. Artemis launches with SLS and Orion. We need this capability. Also, you may not think about it, but Orion return, we need it. He also kind of alluded to the landers that are coming on the horizon. You know, Artemis II is just going to be a mission with SLS and Orion.
Speaker 3: But starting with Artemis III, we'll bring in surface missions with our landers. And we have two different providers for the landers on Artemis III and IV is SpaceX with Starship and then Blue Moon with our Blue Origins Blue Moon, which launches on New Glenn. And so those missions are going to expand the need quite a bit because not only launching those landers, but they each do propellant aggregation in low Earth orbit, which will take some number of missions. So from our standpoint, you know, we've got a great partnership with SCAN working with you and your team, and it's critical to our missions.
Speaker 3: And we're just looking forward, as you're moving forward to this new model, we fully support it and and look forward to that continued great partnership. Thank you, Steve. All right, Andrew, your introductory questions next. And after that, I'm going to go through many questions that are from the audience and some that I'm drumming up. Andrew, so we've got a history of RF communications across missions, but optical is something that a lot of partners are bringing to bear. What is the optical communications potential enabled by these emerging CSP partner capabilities?
Speaker 3: Thanks, Kevin.
Speaker 2: I'm going to hijack the mic for just a quick second and double down on some things Greg said. TDRS has been an outstanding asset for science for decades. And I want to send a sincere thank you to everyone here online, people you know that made that happen. Science appreciates your effort. And as Greg said, it's time to look forward into new things. And I'm excited about that. I think one of the roles of science is to ask what if. And here's another opportunity to say what if, specifically with optical communications.
Speaker 2: What can we do with optical communications? I don't think we've even begun to scratch the surface of what this capability could enable for science. I think we're going to find new ways of performing science with the communication capability itself.
Speaker 3: Excuse me.
Speaker 2: Thank you for your patience as I enjoy D.C. 's pollen season. But with the Deep Space Network, RFCOM system, We're using that comm system to make science happen, right? I am eager to see our brilliant scientific community dive into the capabilities that optical comm can do for us, not just in terms of data transfer rates and things like that, which are phenomenal. What science could we even do with that system? One thing that's been abundantly true to me in my 27-year career living in science as a hardware engineer is that scientists want more data all the time faster than ever before.
Speaker 2: We have a voracious appetite for data. Things like optical communications can make that happen for us in deep space, near space, Earth relay.
Speaker 3: Types of situations.
Speaker 2: We've got NISAR launching here hopefully in the next year that's going to be dumping, what, 85 terabits of data down. Unprecedented types of data transfer. We want to do even more than that.
Speaker 3: We're greedy.
Speaker 2: We're hungry, right? We want to explore the what if of optical communication. That's why the DSpace optical communication test platform resides on the Psyche spacecraft, resides on the Psyche spacecraft. And we got to send a fun cat video home. But that's a stepping stone to this unique opportunity that the people in this room, the people online are going to enable for the science community.
Speaker 3: So thank you. Thanks, Andrew. All right, now to the audience questions. And if we could go back one chart, because telepathically I've received some more questions from the audience out here. And if we go back one to 13, there we go. Greg, you're up first. It's a compound question. Are you ready? What drove the agency to make the decision to fly out TDRS and stop other users, formulate CSP, and what are the drivers behind this calendar behind you? Behind the acquisition timeline.
Speaker 2: Okay.
Speaker 3: Yeah.
Speaker 4: So I'll answer the first part of the question. There are multiple drivers, like everything we do, right? The first, we talked about the technical capability, right? TDRS was 20 years ahead of its time when it was conceived in the 70s. I don't know how that first generation of engineers built this unique, exquisite capability out of what I would call Stone Age technology, right? I grew up in the era of digital signal processing, not analog signal processing. It really held us back, right? Andrew talked about the capabilities we're seeing.
Speaker 4: Anywhere, anytime, optical, 100 gigabits, that will turn into terabits per second. We got frozen, right? TDRS was ahead of the game. It was an important part of driving SATCOM industry forward, right? All of the partners I've met, they've had individuals who worked on TDRS in the 80s or 90s or the 2000s. It's been part of not just NASA, but our wider space industry. But it's holding us back at this point, right? It's tough having those conversations with future science missions. I don't know if I have enough to offer you.
Speaker 3: Space policy.
Speaker 4: Space policy drives NASA and all of the federal government to maximize the use of commercial capabilities. And if those requirements aren't there, or there's not a good match to work with commercial partners to go then develop those capabilities that benefit not only NASA, but the wider space industry to enable us competitive advantage. Um, third, um, you know, uh, Funding, right? Let's be open and honest, right? A lot of questions about the NASA budget. Maintaining these old systems is expensive.
Speaker 3: And we at SCAN, we.
Speaker 4: Always talk about that tension about how much are we going to contribute or value our future versus just maintaining what we have, which is in most cases representative of the past. So those three things I think drove us to that transition. Timelines here, right? We have NASA processes, right? We worked with the agency to formalize a life cycle for this project. I worked with the AA before he departed on that. We also wanted to make sure we had time to let this bake. One of the most valuable parts about this phase two opportunity is their two-way dialogue between commercial and NASA.
Speaker 4: So then they can evolve their service capabilities to maximize the benefit and value for the agency. Funded Space Act agreements are magical devices. I'm glad we went through the effort of dusting off that playbook and using those, but we need time to have that two-way dialogue, and that's why phase two.
Speaker 3: Is so important.
Speaker 4: Otherwise, we're going to go proceed as quickly as possible. We need to make sure we nail the acquisition strategy so it meets our needs, but make sure the incentives built into it maximize the return on value investment for our industry partners. We don't want to end up in another situation or potential situation where the business case falls apart. TDRS was a public private partnership, right?
Speaker 3: First gen.
Speaker 4: And in the end, NASA had to innovate the contract and buy out the system because the demand wasn't there. The business case didn't close. We don't want to repeat those mistakes. Validation is going to take as long as it's needed. If there's people ready who have mature capabilities, who can provide artifacts to the government that this service is ready to go, we're going to be as aggressive as we can to push through that validation period and end up in a position where we have an operational service.
Speaker 4: Also say, scan, right? When do we open up the door for mission commitments to really consider these? We can't do that today. I don't have service providers on contract. But as soon as we have the service providers on contract, then we'll be able to answer some of those questions from our user community and open the door for formal mission commitments. So those are some of those aspects of what drove us here and are driving the next few years of activity.
Speaker 3: Thanks, Kevin. Hey, great job. Great job. So I'm sure industry, you have things that incentivize you. We're incentivized by a few things too, right? And we can't control how fast we're going to lose TDRS. And so, you know, to Greg's point, you know, we need to figure out how to bake some speed into this. But I have a next question tied to that for you, Joe. How long of a transition period is planned while we have legacy TDRS available for backup as the new capability comes on board?
Speaker 1: Sure.
Speaker 3: Yes, there will be a transition period as we ramp down TDRS use, ramp into commercial, and there will be a period where those services will be operating concurrently. If we bring these services on, some might have a quick validation, some might be So it can start sooner, absolutely, if we can get through the validation processes. But to answer your question, we anticipate there being a period of time where those are concurrent, and probably about the mid-2030s is when we would like to see a transition to commercial.
Speaker 3: Okay, thank you. All right, Andrew, given that TDRS services are no longer permitted by AOs, When responding to AOs, will teams be able to choose telecommunication relay services that best fit their needs, or will NASA compete telecom services separately from AOs as is done with launch vehicles? Yeah, that's a great question. This is a really tough time for proposers, right?
Speaker 2: We're saying you're not allowed to use TDRS anymore, and we can't hand you a menu yet of what communication services are going to be available to you.
Speaker 3: It's a tough time.
Speaker 2: But what I envision this becoming is SCAN is going to continue working with our proposers in pre-phase A to evaluate the needs of that mission and figure out how they can pair the needs of that mission with this basket of service providers that they have secured, vetted, validated, and ensured are quality providers for the types of services we need in the future. So I don't think that there's going to be a massive change. I don't foresee protracted LSP-type contracts. We're relying on our scan partners to do that work for us, to figure out what capabilities we need and partner us with the providers.
Speaker 3: All right. Thanks, Andrew. Steve, next question is for you. Help us understand how Earth Relays enable the Artemis mission and the different things you do in the mission.
Speaker 2: Yeah, sure.
Speaker 3: And I kind of went there a little bit in my opening. But, yeah, definitely launch with SLS and Orion. We couldn't do our missions without it when we were returning Orion with the crew. Like I mentioned, we get into Artemis III potentially with our landers or in that whole campaign with the landers and propellant aggregation. We also have for each of those landers an uncrewed demo mission. So even before Artemis III, we'll need to be– SpaceX with Starship will need to be doing an uncrewed demo. And so all, you know, every time, not just the Artemis mission itself, but any time we fly, it's critical and enabling to our missions, Earth Relay is.
Speaker 3: Thanks, Steve. All right, next one's for Joe. Given NASA's recent selection of intuitive machines, its Lunar Communication Data Services partner, what opportunities for commercial communications are in planning? The next opportunities for commercial communication, CSP is, of course, the one that's here on the timeline up and coming for near-Earth proximity users. There is also some activity through the Mars Exploration Program looking at commercial next-generation relays for Mars. I know there's some studies that were completed late last year, and that program will continue to look at that.
Speaker 3: commercial approaches for Mars.
Speaker 4: Yeah, if I can follow up, right? Yeah, if you're familiar with SCAN, right, we divide the whole universe into kind of three regions, right? Our LEO region, we're talking about CSP, right? The TDRS flyout and the CSP on-ramp is going to really dominate the evolution of that architecture.
Speaker 3: Lunar, right?
Speaker 4: Intuitive Machines, another partner, right? Building out lunar relays to enable Artemis and science missions. Maybe making a national asset of that someday. We have those plans in place, those contracts, right? We've moved that ball forward. Maybe we need to do more there in the 2030s. But the next place GAN is going is on the future of DSN and Mars Relay. We're going to consider those things together. Right now they're coupled. We have to consider that question at the same time. They're not separate.
Speaker 3: And we will see, right?
Speaker 4: Are there, as I like to call them, big C commercial opportunities there where there's a market where an owner-operator has a business case? Or maybe middle C commercial where there's tremendous industry capability, maybe driven by what's done in LEO today, where we could take advantage of that in establishing the next generation of Mars Relay. So, yeah, we're going there.
Speaker 3: Pay attention.
Speaker 4: We have our outreach arm, CIS. Those are the places SCAN is working. going and will likely look to accelerate over the next one to two years.
Speaker 3: Hey, thanks, Greg. All right, Greg, back to you. When we issued the memo in November saying no more new TDRS users, wow, I learned all the TDRS users I didn't know about. I got letters, phone calls, the A-suite got phone calls, Congress got phone calls, Because this is their business. And they're like, whoa, wait a minute. This is an interrupter to my business, my ability to compete even. And so I want to pick on one segment of that, and that's launch vehicles. Many of them use TDRS to meet NASA or Space Force contract requirements.
Speaker 3: As TDRS has flown out, how are NASA and Space Force managing the requirements and contracts that TDRS supports? Yeah, yeah.
Speaker 4: The last six months after we sent that letter, a lot of good conversations. I think I was called a breakup artist during that time. We want to be good partners, right? And part of that partnership is not cutting people off. It's making sure they have runway to change and transition. So working with the commercial launch vehicle community and even some of our international launch vehicles we support, we said, this isn't a today decision, but the data tells us we need to get you off the system before we end up in what we call five ball, five teachers consolation.
Speaker 4: Supporting launch vehicles, yeah, it's not every day, all day, all year. But those launch supports, that's intense 24-hour activity that puts a lot of the demand on the system. We need to keep getting Hubble data down. We need to keep the ISS astronaut happy. And so we set kind of clear expectations. You need to start moving. We gave them those timelines, and we listened to them. We talked about that facilitator role. I've seen just that strength in us all having open, transparent, sometimes brutally transparent conversations.
Speaker 4: Some of those RFI questions, I think, are posed to the launch vehicle community. Be open with us, and we'll play our facilitator role where we can come together maybe later in the year to talk about those things. There's a need here. LSP is doing the right things contractually. They have their relationship with Space Force on these types of needs and requirements. We understand that. And we want to advance everyone's endeavors moving forward, and we'll do that by just forcing the conversation. But again, I think NASA's not the right solution anymore, especially as demands of launch, responsive launch, anywhere launch, start to grow.
Speaker 4: Maybe there's a better solution than what we have with CEDRIS today.
Speaker 3: So let's go find it together. Okay, thank you. Steve, with respect to cross-functional collaboration, How does exploration and science work together to ensure SCAN meets your joint set of needs? Yeah, I'd say the big thing is communication, Kevin. You know, on Artemis I, that was one of our lessons learned is I think we learned, we had working level and at the integration level, but we really needed more communication at the leadership level. We needed more communication, you know, of priorities.
Speaker 3: And so, We've really, I think, intentionally, collectively ramped up that communication. Andrew and our mission managers and Greg meet every Friday now. We know we have a tag with you at our leadership level. We've tried to do face-to-faces to really understand. A couple of things in my mind that have come out of that that really bared fruit is the first priorities. You know, we learned on Artemis 1, we put everything, we were number one priority. We had nine secondary payloads on that flight that probably should not have been classified as priority over flagship science missions.
Speaker 3: So we're reclassifying and making sure we're clear about when our real priorities are at critical mission events. and critical parts of the mission so that we don't create that conflict with science. And the other thing we're doing is we, another example I'll give and a little lessons learned, I think we, with better communication, we can talk about what our real schedule is and scan can react. One of the things we found was, you know, we were putting blackouts for when we're going to launch. And then our launch date would move, and that time was not, you know, taken advantage of.
Speaker 3: So more integrated communication and more responsiveness so that the assets that SCAN has are not, you know, being idled when we think, you know, when you think we're going to need it. So I think, like I said, Artemis 1 was a big success, but we learned– In my mind, that more communication is needed for the complex job you have and that you're orchestrating with all your users. And then particularly for our missions come in even more than a commercial launch. An Artemis mission comes in highly intense and crew safety is going to be critical now.
Speaker 3: We would start with Artemis 2, but making sure we're communicating what our needs are and what the real priorities are. So we asked that question. I hope it illuminated for you that being a commercial provider and supporting Steve's missions, boy, that's a blip in your system because you may drop other customers. You may have to. He may have rescheduled by a week, and now you're telling everybody last minute you can't do something that's going to impact your SLAs. This is something big to bite off.
Speaker 3: And so if I was you from a risk perspective, I would spend a lot of time understanding that how human spaceflight leverages these capabilities you might want to provide. Because it could be something that you either plan for and you do well at and make profit on, or it could be something amazing you do that's a loss leader because you didn't think about it right and negotiate it right. So that's a very important set of statements. Andrew?
Speaker 2: I'd like to jump on top of that, Steve. You know, from the science perspective, Absolutely.
Speaker 3: We need to be communicating better.
Speaker 2: The three parts of this organization collaborating on this great effort. And I'll take this opportunity to do a little nitpick on the slide. I think we've got a resounding theme here that we've seen in the Agency of Science Enabling Exploration and Exploration Enabling Science. And that speaks really deeply to me that we are hand-in-hand partners with Human Space Flight. They aren't over there and we're over here. We need to be collaborating and in lockstep and coordinating our activities. And it all comes together at SCAN from the communication front.
Speaker 2: I've been designated as SMD's senior SCAN liaison, the SCAN whisperer, et cetera. Science Mission Directorate has realized that this needs to be happening. And in fact, they've tasked two of us from the front office to purposely and proactively engage with SCAN. We meet multiple times a week. to make sure that what we're doing, what we're envisioning for the future, and what's going on are all done in a really well-coordinated way. And I'm excited to be a partner in that.
Speaker 3: Andrew, thank you for calling out the slide mistake. When I first came to NASA, I met Nikki Fox. There were two things that happened in that first interaction. I called her a customer, and she stared at me. And I said, well, you're our customer. And then we changed that on the spot to Science and Exploration Enabled. So that is a mistake. Since then, all of our slides have said Science and Exploration Enabled. So apologies to Nikki. Andrew, this is right back to you, though. We talked about some of the interesting drivers of Artemis on this future relay.
Speaker 3: What are the science drivers?
Speaker 2: Wow. So, you know, when we started looking at TDRS Flyout, we really said, do we need Earth Relay? And it was a resounding, heck, yeah.
Speaker 3: Right.
Speaker 2: And I'll tell you that that was validated by the panic that we heard through the science community when we said, hey, by the way, we're turning off your access to TDRS.
Speaker 3: Right.
Speaker 2: That kind of closed the loop for us that, yeah, we're on to this. You know, most notably, I think space relay or Earth relay, sorry, is really critically necessary in astrophysics. The type of observations that we're doing now. necessitate constant and continuous ability to access our space assets to point them strategically as maybe a once in a lifetime astrophysics event is occurring. That's an easy one right off the top. I think you could see that evolve into new mission paradigms that can be enabled by having constant connectivity to our spacecraft.
Speaker 2: Right now, we've got these little buckets of time slices that we spend a lot of time juggling coordination and scheduling And we bin up all of our science data and we dump it down at these little drips and drabs that we have the opportunity. I can imagine a future state where this new network of communicators allows us so much more flexibility in how and when we can collect our science and command our vehicles that I think that the opportunities really, really are exciting and compelling for.
Speaker 3: Science in the future. Thanks, Andrew. Hey, Steve, NASA is going to demonstrate optical communications with Orion during Artemis II using O2O. Will optical communication be part of the moon-to-Mars architecture? Yeah, I'm not sure that, you know, that's in front of us a little bit, but I would think so. Yeah, on Artemis II, we've partnered with Lincoln Labs in doing that demo. Really exciting. What I would tell you is, I mean, particularly for surface missions, our appetite for data is just almost unquenchable.
Speaker 3: You know, and you think about video and the importance of video for, you know, public affairs and STEM kind of reasons. I mean, the public is used to having high-quality video all of the time. And when we're doing these missions and astronauts are on the surface, of the moon you know I think that is going to be a huge need also our science community represented by Andrea I mean there's a real science need to have data and video real-time as our astronauts are exploring so I see it as a it's a great technology to give us so much more data.
Speaker 3: I can't imagine it's not going to be, right now it's more of a demo phase, but I can't imagine that we're eventually not going to want that and it'll have its place. I think we'll still, we're still going to want S-band for those critical events, you know, with the crew and landing and those kind of things. But I see it as having a real opportunity in the architecture. Thanks, Steve. So, Joe, CSP question. Are any radiometric or tracking data services being demonstrated by any CSP partners? Are tracking observations being considered in the service requirements development process?
Speaker 2: No.
Speaker 3: So, not currently. We don't have any tracking or radiometric services part of our demonstrations. We did ask for industry in 2021, part of the announcement for proposals leading to the Funded Space Act agreement, if there was any interest or capabilities in industry for those services. We did not get a response at that time. But some of our, but tracking conveyor metrics is very important to NASA. Some of our spacecraft are very elaborate and require precision pointing accuracy that is beyond what you can do with just GPS alone.
Speaker 3: So, again, to promote the RFI, we will be asking industry again for if they have any tracking and radiometric services they could offer NASA as part of services, and we encourage you to look at other ALT P & T concepts, anything from optical radio metrics, any other innovative solutions that might help our science with that key problem. So, depending on the RFI response, that might influence if it shows up into our service requirements or not. All right. Hey, thank you. All right, Andrew, you're on the spot next.
Speaker 3: So we developed these commercial tenets of working with commercial space partners. The first one is to get behind their path to profitability, which means I need to do everything I can to drive customers to them. What is SMD doing to communicate to their advisory board and the PI community stakeholders these changes and opportunities and help drive them toward these commercial partners?
Speaker 2: So I'll start off by saying I think we can do more and I think we can do a better job. but that doesn't discredit the efforts we've already taken under. We've invited SCAN to come to federal advisory committees to participate in the, we participate in their CSUGS, their commercial services user groups.
Speaker 3: Those are ways to get out to the community.
Speaker 2: In fact, this forum itself is another one of those opportunities that we're hoping.
Speaker 3: To capitalize on.
Speaker 2: We absolutely want to hear from everyone What are we missing? What are we leaving on the floor? What opportunities are we not capitalizing on? Because the viability of this is vital to our sustainability of being able to continue the science that we're doing. This business model is part of SMD's business model, and we have to lean in and embrace it and make sure that we're feeding it.
Speaker 3: As good custodians of the service. All right. Thanks, Andrew. Steve, Moon to Mars has their own set of commercial service procurements and partnerships, and I'm sure you guys have learned a lot. What kind of lessons would you share with us for this acquisition? Well, I think the first thing that for me personally comes to mind is, you know, if you're going to do this kind of approach, you really want industry to be interested in an ecosystem out there, which I think you clearly have. The next thing I would say, lessons learned from us is, You really need to early get your requirements settled and make sure you're confident in what you're buying and what kind of requirements, particularly performance.
Speaker 3: I would say look at what you really need and what's out there. In the past, like with the lander, we actually set a threshold and goal performance requirements, which I think helped because You don't want to put out something that's going to be overly expensive. The other thing in our world, and I'm not as familiar with your world, is the how-to requirements I think are really important. Design and construction standards and other things that you put in as part of the contract. What we did that I think that's worked really well is adjudicate those in an early phase.
Speaker 3: I think you want to settle... Not just performance requirements, but your how-to, design and construction standards, other standards you're going to put on the provider and give them an opportunity to push back on those and really make sure you buy off on those up front. The bad lesson learned I've had in my history is letting that go on too long. And so you really want to get that buy-off from your user community and your technical authorities. And the other thing I would say is thinking about your kind of management model.
Speaker 3: It's not an oversight. It's more of an insight in making sure you're on the same page with your partners of how you're going to do that. And the last thing I would say is, and I'll stop here. I could go on on this subject for a while, is really look at how you're going to do what I call collaboration or offer up. capabilities the agency has to commercial industry. And how you do that, and make sure you make that, and that might be hardware, it might be expertise, that you have a structure where you can make available and help industry or capabilities at the center and let them work for your provider, not directly for you, but make sure that you offer those up and you have a kind of a structure where you can manage that so industry can leverage the investments that we've made in technology or expertise that might be out there.
Speaker 3: So those are some of my lesson learned that I think have worked well and not worked well in the past. Hey, Steve, that's great. I appreciate that. That kind of feeds in now what I'm going to ask you, Andrew. TDRS has a DAS capability. I want you to tell us in a minute what that is. And, you know, how can that be replicated with commercial providers? Is there a potential to test any commercial solutions with existing platforms? Tell us about those platforms. Why do we even do DAS? Will that continue?
Speaker 3: How important is that to SMD? Help people understand in case they have an opportunity to cling on to this, right?
Speaker 2: Yeah, I touched on it a little bit earlier. You know, DAS is Demand Access Service. It's a capability that TDRS provides to us. to say, we need to talk and we need to talk now. Not the call you want to get from your partner, but it's an exciting call to get in science because that means something's happening, right?
Speaker 3: And we want to respond to it.
Speaker 2: And ensuring that that capability exists in the future paradigm is of critical importance to our astrophysics community. They have been one of the staunchest advocators and interested parties as we're talking to SCAN about what's coming next. And every single time.
Speaker 3: We talk to them, it's DAS. How are we going to do DAS?
Speaker 2: I think that this new commercial service paradigm absolutely is compatible with the tenets of DAS, whether you call it DAS or not. I think that having a 24-7 connected network of providers with redundancy across multiple providers is going to provide, I'll say that again, is going to offer that kind of capability to our community. And in fact, I think there's an opportunity for that to grow beyond just astrophysics. I think as other science communities realize that this capability exists, they're going to want to leverage it.
Speaker 2: They're going to want to talk to their satellites more often. They're going to want to see what they can do with their mission paradigms and their mission designs, their con ops, and say, how can we use this to do our science differently, do our science better? How can we capture those unique opportunities that we're currently missing because we're not engaging in this arena.
Speaker 3: Hey, thanks, Andrew. Greg?
Speaker 2: I missed one point of your question, though.
Speaker 3: Sorry, let me go back to that. Oh, yeah, right, right.
Speaker 2: Opportunities to test this stuff, right?
Speaker 3: So there could be an opportunity to.
Speaker 2: I'm definitely interested in exploring the possible opportunity. I'll put all the Weasel words in there so I don't get in trouble, right? One of our assets, Swift, in astrophysics is a user of DAS in its mission paradigm. And I would love to see an early test run, a trial run, a risk mitigation test, to put it in engineering terms, to try it out. So, hey, does this work?
Speaker 3: Does this meet our needs?
Speaker 2: And what about it doesn't meet our needs? You know, we're a learning organization, and in order to learn, we need to try stuff. And I think I really want to see us leaning in to trying stuff as we move forward together with the commercial community.
Speaker 3: Thanks, Andrew. Greg, we received a few questions on S-band services. Is there a plan to replace current SBAN services with commercial ones?
Speaker 4: So, no, not yet, maybe. That's the concise way of answering it, right? Our approach with CSP was to move as maximally towards the commercial capabilities as we could. We want to be one of many. We want to drive unique government requirements into a commercial SATCOM ecosystem where we're the only user of some bespoke service. But this is a conversation. We talked about the CSP life cycle, making sure we had time to consider some of these questions, make adjustments as we moved along. And in the whole teachers fly out process where we're looking at missions, not just missions today, but concepts, you know, physics is physics.
Speaker 4: And that region of the spectrum around the mobile satellite service bands is pretty unique. It allows you to use some unique things, the DAS thing, right? I have a tumbling spacecraft. I need to try to recover it. And so there's some commercial capabilities that are very similar to DDRS. They're in different bands, L bands. But could we partner with commercial working with the FCC and NTIA and maybe making adjustments to the table of allocations and allowing authorizations for a commercial service to with a business case to be formulated around an S-band relay service.
Speaker 4: We're going to ask some of those questions in the RFI. If we have driving requirements, we have a match of technical capability in a business case, plus the spectrum regulatory regime questions are answered, I think that could all add up to yes. We talked about communication about seven different times, not services, but us all talking together. We're going to ask those questions. We're going to have those conversations over the upcoming year. That may turn into effectively a new requirement for scan that we'd have to execute on in partnership with some of these commercial players in the room today.
Speaker 4: So, yeah, evolving situation. We're gathering that information to make an agency judgment on how to move forward in the best way.
Speaker 2: All right.
Speaker 3: Thanks, Greg. Steve, the next one's for you. The need for Earth Relay support of HLS from both SpaceX and Blue Origin is LEO refueling operations was not known when SCAN defined its transition to commercial relay capabilities. How is this new need being accomplished by the agency? Is it really an HLS contractor responsibility? So, I think the last part, yeah, at the end of the day it is, but of course our approach is try to help our providers all we can. I think, you know, At the end of the day, we want the mission to be successful.
Speaker 3: The other thing when you were asking about this commercial model, the one other piece I would add is part of our government role is to help integrate. We are a big organization. In Moon to Mars, there's a lot of programs working with SCAN. And so part of our job is when our partner, provider, or contractor needs help, even under a commercial model, you know, in my mind, it's one of our big jobs is to help integrate and go help fix that problem. And so I think that's what we've done in this case is while it started out, maybe we don't need that.
Speaker 3: You know, as we've gotten closer, we realize we do. And so I just appreciate the partnership with your organization and working through that and putting the mission, the mission need first and, and understanding that, you know, at the end of the day, we can have, you know, sort of goals and ideas about maybe we don't have S-band or maybe where it's all commercial, but at the end of the day, we need to jump in and solve the problem, you know, and make the mission go at the end. Thanks, Steve. All right, Andrew, you're up next.
Speaker 3: Is there a killer app for commercial space services?
Speaker 2: Killer app.
Speaker 3: Let me rephrase that. The science missions are hard enough. You know, they have this whole, you know, they're all so different, right? They all have different needs. But the one need they have is to get the data down. But, you know, what is the easy button industry can do that makes science start banging on their door?
Speaker 2: As I touched on earlier, more data, faster, feed the science machine. It's a voracious community. If you can find ways of doing that for science.
Speaker 3: They will celebrate you.
Speaker 2: They will come to you begging for more. We will come to you begging for more. I've touched on it a few times, this this opportunity to explore what constant comms with our birds could mean for us is really exciting to me. So if you say a killer application of what this new capability might unfold for science, I don't want to suffer for a lack of imagination.
Speaker 3: But this could.
Speaker 2: Really change the game in how we do science. It could set the stage for the next the next decade or two of fundamental ways in which we capture science, communicate science, bring science back to Earth, and share it with the people. I think there's also a really compelling opportunity to leverage a network of connected space assets to actually do science. What if we could put a sensing instrument on some of your birds?
Speaker 3: What if we could do global.
Speaker 2: Rainfall measurement from hundreds of assets or more and constantly be communicating that down. What if we could explore space weather events on a global scale simultaneously instead of a single asset flying around? You know, these are the kinds of things that excite me about what I see coming in the.
Speaker 3: Future from a science perspective.
Speaker 2: All right.
Speaker 3: Hey, thanks, Andrew. All right, Joe, next is for you. You know, you've been through the CSP journey. You've probably heard a lot of complaints and lessons learned from CSP partners. You've got your own pains and lessons learned. What do you want to share that will help this next phase go smoother? We touched on it earlier about communication, being a communication org. Also, these relationships are built on trust. Like any relationship, they take work to be effective. So what we put in, we get back.
Speaker 3: If we engage with our partners, provide them feedback, which is what they really need is feedback, then the insights that we provide will result in a better service for NASA. It forces us to do our homework and to be engaged with industry, also to be direct and tell them what we need but not how to do it. And other key lessons learned that we've been having is to anytime we've brought facilitated conversations between the mission directorates and the providers, good things have happened. I can think of a number of examples when we get the two together, and then if there are a slight gap or something different than what they're expecting, we can work through those things.
Speaker 3: And the companies are anxious to understand those problems and to start working them. I can think of a number of examples where you know, concerns about a tumbling spacecraft, something in an emergency mode. What about this contingency mode? Hey, your system relies on GPS. What happens if you don't have it? That gets them thinking, and then they can start innovating, and they're anxious to do it, and they're willing to do it. They just want to understand how to make this work. So that's been lessons learned for us and some examples.
Speaker 2: Great.
Speaker 3: Thank you. And, Greg, congratulations. You get one out of left field. Are you ready? Oh, the best question.
Speaker 2: Yeah.
Speaker 3: That's a compound question again. Oh, man. First, what keeps you up at night? But the second one is, what are your known unknowns on this? What keeps me up at night? A lot of things.
Speaker 4: I want our customers, our users, to trust SCAN, our vision, and know, even though we're going to have tough conversation, SCAN's place is to be a means to those greater ends, right? We're not going to build services that no one uses, right? We need that feedback. So I hope I'm in a position today, and that even grows further, where if I show up, a representative scan shows up in a room, whether it's a PI room, a FACA room, a mission science division room, or the A-suite, right? They know we're fighting for our users.
Speaker 4: We all have constraints, externalities, policy, funding, all those things, but we're doing the best we can We're here to enable exploration and science or science and exploration. So, yeah, that's what keeps me up at night. Known unknowns. Well, I think we have a known unknown, and that's what the exact services we're going to have in hand to all of us.
Speaker 3: Our providers, right?
Speaker 4: We cannot do that today. We can tell you about our partners, whether you're a funded Space Act Agreement partner or some of the non-reimbursable ones. We can tell you about our market research. But until we have those services on contract to go validate, I'm in a very uncomfortable position. I can't start a mission commitment.
Speaker 3: Machine.
Speaker 4: I cannot go to a pre-formulation mission and say, here's your seven options.
Speaker 3: What works the best for you?
Speaker 4: So that's something we actually didn't anticipate in this process. We thought the TDRS decline would give us a little bit more runway where we wouldn't have to stop new mission commitments before we had those contracts in hand. And so that's the biggest known unknown. It's been very obvious from our mission community, give me those ICDs, those user guides, We're encouraging our partners to share those openly, even though there's a tension with your competition, right? That's the biggest known unknown.
Speaker 4: We've identified it, and we're trying to work through it in every way possible.
Speaker 3: I'm going to throw one more on there. How do you feel like what we're doing and talking about today is supported and will be supported to development and delivery? I'm going to say by those that give you money, by those that give you requirements, by those that enable this to happen. Well, again, there's that trust aspect. We build a lot of trust. We have mission stakeholders. We have leadership stakeholders. We have congressional stakeholders. We have the Office of Management and Budget. We have policy stakeholders.
Speaker 4: I would say that the tenor of how we're retiring TDRS, the agency fought it for probably five years, and we had lost that schedule opportunity. I've seen support everywhere, but also an acknowledgement that there's risks in these transitions, and it requires resources, whether it's schedule or budget, to go buy down those risks. So there's tremendous support. I see the energy in the industry community. Every one-on-one I have a partner or a non-partner, they're jazzed about this. They see NASA leading not just for NASA, But for the rest of the commercial future space owner operators, the Space Force, the elements of the DOD, let alone international space agencies, NASA doesn't have the dollars, right, to move the entire industry ourselves.
Speaker 4: What we have are two unique things, our leadership ability, and then also we talk to everyone.
Speaker 3: NASA is in.
Speaker 4: The nexus, in the middle of the entire space industry, international. the industrial base, the interagency. And so people are looking for our leadership, and we're using that to help move this entire endeavor forward. Yeah, so the support is good. That can come in many different ways and flavors, and I appreciate everyone seeking out and supporting our leadership in this endeavor.
Speaker 3: All right, Steve, this one's out of the left field for you as well.
Speaker 4: Are you ready?
Speaker 3: All right. What's keeping you up at night about this? And with respect to this, what's the last thing you want to go in and tell Ahmed if it falls apart? In this realm, there's a lot that keeps me up at night. But, you know, I think in this realm, you know, we've got existing systems that are used in TDRS that we've designed to. And so, you know, being able to make this transition on our side with the hardware, actual hardware, um, you know, it'd probably be a bigger, uh, hate to go tell on it, but, um, you know, I, I, I really am encouraged with that.
Speaker 3: You know, we continue to have challenges in, in, in you guys supporting our mission and working together, you know, but we still keep meeting those. And so, um, You know, I know that he knows that your partnership is there, and that's the biggest thing that matters to him. So I don't think any problem I'm going to bring him is going to freak him out because he knows you and your team are there to support the mission. Thanks, Steve. Thanks for letting me throw you that one. All right, Joe, how can everyone learn more about CSP, the FSA partners?
Speaker 3: Is there a forum or event they can participate in? Who do they call?
Speaker 2: Absolutely.
Speaker 3: Absolutely. We run a CSP users group meeting at least once a year. That is an excellent way to get engaged. It brings the mission directorates with CSP and the partners together. That is an excellent way. You can certainly reach out to myself and project manager Tom Kasfura for more information. We'd be happy to facilitate any conversations. between you and the partners. We have a mission analysis group, a mission support group that is there to help you for the missions, to help you understand how these services work, the ones that we're working on right now, and to also engage with us on your requirements.
Speaker 3: We are reaching out, so if we're not talking to you, come talk to me and make sure that we get engaged. All right. Hey, thank you. And if we could go to the next chart. I think there's some POCs up there that were the background for your answer. Next chart. There we go. So these are some folks you guys can reach out to. So this concludes our questions. Any follow-up questions, can you email to the appropriate point of contact on the screen behind me? A recording of this town hall will be available on SCAN's website.
Speaker 3: Before I wrap up, I want to take a moment to thank our panel. and everyone here for attending today's town hall. Your time, attention, and thoughtful engagement made this a very vibrant and insightful conversation. As the agency moves forward and transitions to utilizing commercial relay services, we invite you to continue the discussion. Come see us, engage, submit white papers, questions, respond to RFIs. We are available. Let's work together, forge this new era of space communications following TDRS, That leads to advancements in space exploration and research for many, many decades to come.
Speaker 3: Thank you for coming.
Podbean