This year’s decision to increase and extend use of the initial “Block 1” operating configuration of NASA’s Space Launch System (SLS) booster also impacts the space agency’s near-term plans for evolution of the launch vehicle’s design.
The Congressional commitment to a second Mobile Launcher for SLS, along with the ability of SLS Block 1 to carry out early Orion lunar test flights and send a six-ton spacecraft to Jupiter has engineers back at the proverbial drawing board to look at re-assigned missions and preliminary vehicle configurations.
The design and analysis work that comes with the latest change in direction is above and beyond work that was well underway for the second generation SLS vehicle called Block 1B, and the SLS Program is looking at how to juggle schedules to finish all the new Block 1 work so it can fly before Block 1B.
Iterative design process
Currently forecast to fly in 2020, the first SLS launch will begin Exploration Mission-1 (EM-1), sending NASA’s Orion spacecraft uncrewed to the Moon for a multi-week Lunar orbit mission. SLS will fly EM-1 in its initial Block 1 configuration which has the Interim Cryogenic Propulsion Stage (ICPS), a modified United Launch Alliance (ULA) Delta 4 upper stage, stacked on top of its foundational elements of two five-segment Solid Rocket Boosters (SRB) and a liquid-propellant Core Stage using four RS-25 engines.
Already receiving funding, longer-term plans are to develop the Block 1B vehicle which replaces Block 1’s ICPS upper stage with a more capable one called the Exploration Upper Stage (EUS). EUS has four RL-10 engines instead of one in the ICPS, and also has higher capacity liquid hydrogen and liquid oxygen tanks sized to the 8.4-meter/27.6-foot diameter of the SLS Core Stage.
Design and development of SLS vehicles is being done in phases or configuration “blocks.” An iterative design process is used by the program to take a vehicle configuration from a preliminary concept to hardware that is certified for flight.
“I think the key is the design analysis cycle, the DAC,” David Alan Smith, SLS Utilization and Payload Integration Manager with the Spacecraft Payload Integration and Evolution (SPIE) Office, said. “That’s the period of time where we perform, with increasingly mature data, analysis cycles on the performance of the vehicle, the accommodations, the interfaces, the operations. That’s really what the DAC means.”
“Now there’s a whole bunch of DACs, because [as] a vehicle configuration matures we have additional DACs. They go off into infinity potentially, [but] we have one to maybe even three DACs depending on what we do.”
“The design analysis cycles are intended to mature the vehicle from pre-PDR (Preliminary Design Review) through CDR (Critical Design Review) and after which you get into your verification analysis cycles (VAC) which feed into your design certification,” Rob Stough, SLS Utilization Manager with SPIE, explained.
Outside of that, other people look at future payload utilization for SLS. “[That] was developed as a way to more quickly with a different set of people and resources look at how can we best utilize the vehicle, how can we look at how the performance can best be used or optimized,” Smith said.
“The vehicle configurations have kind of been defined, but there are still kind of crazy trade studies that we do looking at performance, accommodations, [and] interfaces.”
“[That] analysis lives more in the conceptual realm that feeds requirement generation that starts the initial DACs,” Stough added.
The Block 1 Crew vehicle configuration, which will fly with the Orion crewed spacecraft, is currently into Verification Analysis Cycles. The first mission it will fly is EM-1.
“There’s certifying the vehicle for a capability, you can consider that what you do at DCR, Design Certification Review, then after that you have to get ready for flight, so you would then perform a FRAC, Flight Readiness Analysis Cycle,” Stough said. “That generates all the flight products that you would feed your I-loads (initialization loads), everything for flight.”
“One (DCR) is certification of the configuration called Block 1 and another (FRAC) would be the readiness of a mission called EM-1 using the Block 1, two different flavors,” Smith added. “If you went to Boeing and bought a 737 that would be like a Block 1,” he explained.
“Well no one in history has ever flown a 737 — they’ve flown a Delta 737 or an American Airlines 737. It’s a configuration that gets customized out of the factory for whoever buys it. So Block 1 in its pure state is a capability like Rob said, but it’s going to be fiddled with a little bit for a particular mission.”
“Europa (Clipper) is going to take the Block 1 and go to Jupiter, EM-2 (Exploration Mission-2) is going to take the Block 1 to do a test flight with humans,” Smith continued. “And then going to Block 1B, we’re going to do the same thing.”
The EM-1 vehicle will have a number of customizations, some because it’s the first SLS flight vehicle. Most visible are the photogrammetry markings on the SRB cases on the +Z side of the vehicle, but a significant amount of one-time Development Flight Instrumentation (DFI) sensors are also being placed on the EM-1 vehicle.
Data from pressure transducers, accelerometers, and other types of sensors embedded on the skin of the Core Stage and other parts of the vehicle will be collected during the EM-1 launch and downlinked in real-time along with operational data.
FRAC-0 for the EM-1 mission is currently being timed to start after completion of integration of the first Core Stage’s engine section. That critical production milestone for the first vehicle is forecast for somewhere in the first quarter of 2019.
History: three decisions
Prior to the initial definition of SLS Block 1 in September, 2011, and in all appropriations bills passed by Congress since then, the vehicle was expected to evolve from Block 1 to its required full capability, which continues to be defined as being able to lift 130 metric tons to low Earth orbit (LEO).
While detailed design analysis on the Block 1 configuration was going on, the SLS Program was also evaluating evolution strategies that would upgrade upper stages and/or boosters. The first evolution, Path A, looked at putting multiple upper stages on top of the Core Stage and Boosters in a Block 1A configuration.
“There was a trade that looked at what if you didn’t do the upper stage you just did the Advanced Boosters, but essentially Block 1A delayed an Advanced Boosters still to Block 2,” Smith said. “There were trades that looked at the booster first but the stages were too important, the upper stages were key to our success.”
“What happened was coming off of Ares we had these J-2X engines and we were kind of looking at an upper stage based on J-2X and it was really a great performer, it looked great,” he added. “However to meet its full potential it had to have a third stage.”
“We called it the CPS, Cryogenic Propulsion Stage, but essentially it was the third stage. That was a great performer but there were two issues.”
“One is it took up a lot of fairing space that the payload needed,” he continued. “You had this big third stage and it was cryogenic and it had to be fueled on the pad and so forth. But the other one that was really the kicker was that we had to develop a third stage and that’s a lot of money.”
“When you think we’re developing the Exploration Upper Stage right now, that’s a costly endeavor this giant stage, the biggest ever made of an upper stage,” Smith added. “Think about having to do that for a second time for a little brother version that goes on top of it.”
“So we traded that performance and that development path to all of sudden we came up with a path that said we’ll use four RL-10s and now we’ve got a stage that really does both functions of what the original J-2X upper stage was going to do and its potential third stage CPS.” That second evolution path, Path B, put a single large upper stage on top of the Core and Boosters in a Block 1B configuration.
The first decision was to choose the evolution path to Block 1B, setting aside the Block 1A possibilities. “When you look at it, as you’re seeing our DAC, VAC, and FRAC cycles that we’re talking about, every time you develop one of these guys you’ve got to do all that over again,” Smith explained.
“There’s a lot of money and a lot of people and so it ended up being a pretty easy trade to say we’re almost getting our performance with a Block 1B configuration using the EUS that we could have gotten with that original Block 1A at a smaller cost and a shorter time frame and less risk.”
“That trade worked out well, we got rid of a stage in a sense going Block 1B,” he added. “The complexity, the cost, the staging, the manufacturing, we were able to eliminate that from the path.”
Current public estimates say the Block 1B configuration can place 105 metric tons in LEO; in order to reach the 130 metric ton mandate, SLS has been studying a future evolution of the vehicle called Block 2. The assumption is that along with improved boosters replacing the Shuttle-derived SRBs, a major redesign of the vehicle would be necessary to get the required performance.
Both efforts would be expensive and with Block 1 and Block 1B still yet to fly, development of Block 2 is not currently funded.
Although the Block 1B configuration had become favored over Block 1A by 2014 to follow Block 1, NASA still needed to get the authority and funding to begin development. Originally, the Block 1 vehicle was the only configuration authorized and funded and initial launches were studied using ICPS.
NASA finally got the go-ahead with the decision by the 114th Congress to develop EUS and the Block 1B vehicle beginning with enactment of the Fiscal Year (FY) 2016 budget in late 2015.
Shortly thereafter in late January, 2016 a formal directive was issued by Exploration Systems Development (ESD), which integrates the Exploration Ground Systems, Orion, and SLS Programs, to stop all work on Block 1 after the single EM-1 launch. All subsequent SLS launches would use the EUS and Block 1B.
The directive to concentrate on EUS and Block 1B after EM-1 stopped detailed design work on Block 1 concepts, including Europa Clipper studies. With that, not only was ICPS human rating work for EM-2 (the first crewed Orion flight) suspended but studies of launching Europa Clipper on SLS then focused solely on using the more capable Block 1B, which also provided more performance margin for a launch on a direct trajectory to Jupiter.
“NASA has always wanted the Block 1B because it’s a great performing vehicle and so when we went to Block 1B formally…all of sudden we started looking at a cargo version of Europa on a Block 1B,” Smith said.
At the time, a single Mobile Launcher (ML) was enough to satisfy the long-term goal of one flight per year for SLS and Orion; however, ML was going to require a significant teardown/disassembly and reconstruction to support the longer, EUS-based Block 1B vehicle, along with structural reinforcements to handle the higher weight of both the vehicle and the modified umbilical tower.
It was expected that the program’s only Mobile Launcher would be out of service for nearly three years, a 33-month long period that came to be referred to as an “iron-bar” stuck between EM-1 and the next launch that could not be shortened.
The desire to shorten the time between initial Orion and SLS flights and the availability of additional top-line funding for NASA led to the decision to fund a second Mobile Launcher in the FY 2018 budget.
With funding of the second ML, the first Mobile Launcher, now called Mobile Launcher-1 (ML-1), will remain largely as-is. ML-1 recently completed major construction and after EM-1 it will essentially be ready for additional Block 1 launches.
Another formal directive from ESD was issued in late April moving the EM-2 and Europa Clipper missions from Block 1B back to Block 1.
Change in direction leads to further changes
In order to launch Europa Clipper on Block 1, an additional SLS vehicle configuration is necessary. Early in the SLS Program before EUS was funded, preliminary studies looked at using a cargo configuration of the Block 1 vehicle.
“We did a DAC-0 on that Block 1 Cargo version with Europa,” Smith said. “So that was the first design cycle that said it would work, it could work with a number of different fairings, it didn’t have to be a specific fairing, it was feasible.”
After the change in 2016 to go “all EUS,” the SLS Program was developing three vehicle configurations: Block 1 Crew, Block 1B Crew, and Block 1B Cargo. The SLS crew vehicle configurations fly with the Orion spacecraft launch system on top, which includes the Orion, its Launch Abort System, and aerodynamic fairings and adapters. Cargo configurations use an aerodynamic fairing on top of the upper stage to completely cover a payload package during the early phase of launch.
With Europa Clipper moved back to Block 1, development work on the Block 1 Cargo configuration has resumed. The ICPS is derived from the Delta Cryogenic Second Stage (DCSS) that is used as a Delta IV upper stage, and NASA has also decided to use the Boeing’s payload fairing system for Delta IV in this configuration for Europa Clipper.
EM-2 has also moved back to Block 1 and ICPS, and NASA is planning on leveraging independent development efforts by ULA to human rate the stage. The launch provider is certifying an emergency detection system (EDS) that will fly on the Atlas V launch vehicle for Boeing’s CST-100 Starliner spacecraft.
That avionics, along with the move to Common Avionics between ULA’s Atlas and Delta vehicles will help with human rating, since ICPS uses the same Common Avionics. Some additional modifications such as increased Micro-Meteoroid and Orbital Debris (MMOD) protection are also being looked at for crewed Orion missions that fly on ICPS.
Development work on EUS and Block 1B is continuing with Smith noting they recently finished the DAC-2 analysis cycle for Block 1B, but all the additional Block 1 work and mission design now has to be completed in front of their first launch.
“The timing is a little bit changed since the Spring when Block 1 came back into the mix, so we’ve got to focus on a few more Block 1 missions before Block 1B,” Smith noted. “We have one set of resources that have to do both configurations.”
The EUS PDR was completed in early 2017 and prior to the change in plans the CDR was expected some time this year. With all the changes inserted in the manifest, that timing will also change.
“The Space Launch System Program is assessing the manifest and mission requirements to determine the optimum time to schedule the Exploration Upper Stage critical design review,” said Kent Chojnacki, NASA’s EUS manager for SLS said in an email. “We are examining all the requirements, especially in ensuring SLS Block 1B can send 10 metric tons along with the Orion crew vehicle on a single mission. In the meantime, we are continuing to work on EUS components.”