[Here’s one last draft I’ve found to polish off–this one only from a year ago. It’s a little bit of a touch subject–I’m not trying to denigrate what the NASA teams mentioned in this post were doing, just trying to suggest another, possibly better way of achieving the same underlying goal–that of giving new NASA engineers hands-on experience working on lean, fast-moving engineering projects.]
I’ve written about the idea of NASA/AFRL externships before, but lately I’ve been thinking about the idea again as an alternative to NASA “training-wheels” intramural R&D. By “training wheels” intramural R&D, I’m talking about internally run NASA R&D projects which have training new engineers as one of their primary purposes. As I’ve pointed out many times in the past, knowledge and experience of how to do things doesn’t reside in documentation or in the walls of an organization, it resides in people. And that knowledge/experience has a “shelf-life.” People who haven’t had recent experience can get rusty, and over time, even those people can disperse, either via retirement, job changes, etc. So having some way of training new teams and giving them solid, hands-on experience early in their careers is really important.
While NASA talks about its expertise in designing and building new launch vehicles, the reality is that many, if not most of the NASA people with actual experience in that area are gone by now (either dead or retired). The last successful new launch vehicle that NASA had a major role in was the Shuttle, and that flew for the first time 35 years ago, and any engineer older than 30 at that point has by now passed retirement age. While NASA won’t admit this problem too publicly, I think it has at least recognized this experience issue internally, which is why they’ve pushed hard on intramural R&D projects like Project Morpheus, Robonaut, Valkyrie and others over the past few years1. When you talk to people at NASA about some of these projects (and similar projects at other centers), you often hear one of the major justifications being that NASA is undergoing a lot of turnover as most of the existing NASA civil servants retire over the next decade or two. The newer hires don’t have experience building and running space projects, so having “training wheels” projects that they can get initial experience with, and even try out new ways of doing things, is a good way of making sure NASA prepares the next generation of engineers to take over as the current generation exits stage right.
Before I go on, I need to say that I find this desire admirable–NASA is taking a proactive approach to make sure their tax-payer-funded people have real hands-on experience, not just book learning. This is in general a very good thing.
These intramural R&D programs are also often sold as being very inexpensive–Morpheus for instance has bragged in the past that they’ve spent less than $5-10M getting to where they’re at. That would seem like a pretty reasonable price compared to commercial VTVL efforts. But then you hear that they’ve had >60 engineers working on the project over the past few years. There’s no way the fully-burdened cost of a NASA engineer is anything less than $100k/yr, more likely it’s in the $200k/yr range. NASA doesn’t count those costs, since they would’ve paid for that labor anyway, but it’s a real part of the cost of the project. When you take fully burdened costs into consideration, Morpheus has probably cost NASA more like $40M+ total, which all of the sudden stops seeming so frugal compared to comparable commercial efforts at companies like Masten and the now-defunct Armadillo Aerospace. Similarly, the Valkyrie robotics project has been called a $2M project, but it has also been reported to have over 50 FTEs working on it for over a year. That means it’s more like a $12-15M project.
The question becomes is this the best way of spending NASA resources to train future civil servants?
Possibly, but I have my doubts for the following three reasons:
- These projects in many cases compete with commercial efforts. While they may potentially create new NASA operational capabilities, they don’t encourage the creation of profitable new commercial space capabilities. By removing a good chunk of the NASA market for things like VTVL test beds or robotics systems, they make it that much harder to create businesses that serve NASA as one customer among many. NASA’s budget is unlikely to grow much over the coming years, so the best way for it to improve its bang for the buck is to encourage commercial companies to provide the services they need, in a way that allows them to get significant non-NASA customers so NASA isn’t having to carry the full burden of the fixed costs of those capabilities. Wouldn’t it be better if NASA found a way to train their engineers that actually encouraged the commercial development of space?
- While these projects teach engineers to do things cheaper than the traditional NASA way, they’re still very inefficient compared to commercial efforts. As one case in point, I had a friend who briefly worked with the Morpheus team. He was familiar with what the NGLLC teams had accomplished, and was surprised to find that for instance, the NASA team had over a dozen engineers working on GN&C and flight controls–a job that most of the smaller companies did just fine with 1 or 2 guys. While this may be a “new way of doing GN&C at NASA”, and may be a step in the right direction, wouldn’t it be better to train engineers in an environment that is as lean as private enterprise? While the NASA environment may not allow all lessons learned from private enterprise to be directly translated into practice, I think it would still help provide a better yardstick for them to compare how efficient they’re really being.
- These projects tend to develop IP that they then lock-up at NASA. While it’s possible to license those technologies, in many cases exclusively, that tends to favor companies with the deepest pockets or best lawyers/connections, not the ones with the best ability to successfully commercialize those technologies. While there are some examples of companies buying their way into a NASA technology and commercializing it well, I think it’s probably more likely to happen when the company already has technical chops of their own. Wouldn’t it be great if NASA could train its engineers in a way that disseminated the IP better into the hands of commercial companies that were well-poised to bring those technologies to market?
If the only way to get new NASA engineers more practical, hands-on experience was via these intramural R&D projects, it might be worth it, in spite of the negative impacts to commercial industry. But what if there was a way to get them experience in a way that actually helped commercial industry instead of competing against it? While the devil is probably in the details, I think “externships” are a potential way of doing this. For those of you who didn’t read the previous post, an “externship” is kind of like an internship, but instead of having a student or recent graduate work for you for a few months, you would get a NASA employee “on loan” for a specified amount of time.
NASA is already doing some potentially innovative public/private partnerships through programs such as the NextSTEP BAA and more recently the Tipping Point and Emerging Space Technologies solicitations that are currently out. In each of these cases, NASA is only putting up a portion of the money, and in some cases is only providing in-kind services through non-reimburseable Space Act Agreements. What if they added to those in-kind services by providing some of their engineers on a loaner basis to teams that can come up with good proposed projects to use them? Not just letting them access NASA personnel and facilities at NASA sites on a no-exchange of funds basis, but basically providing them with on-site externs as well.
You could probably structure the solicitation in a way to require the companies to provide a certain amount of their own people, and their own hardware money in order to access a small number of NASA-funded externs to augment their team. Maybe even throw in a NASA subject-matter expert as part of the team. It’s often the case that small companies can’t afford to have a specialist in some esoteric technical field that they’re only going to use occasionally, but borrowing one from NASA can help a lot. For instance, I remember that NASA Ames lent Dan Rasky to SpaceX back when they were investigating heat shield material, and he helped the SpaceX team develop the Pica-X material they are now using on Dragon.
This solution isn’t perfect, because it could still end up competing with private companies trying to provide contract engineering services, but if more of the “training wheels” experience for new NASA engineers was earned at commercial companies, working on developing new products in a truly lean organization, I think it would likely be a net good for the industry. For one thing, NASA would have a much better idea of what things ought to cost in a truly lean and hungry organization, and how big of a team you really need for various projects. These externs would also get to see the contrast between industry approaches and NASA standard processes, and would likely have a better idea of which NASA standard processes should be kept, which ones should be streamlined, and which ones are just plain baggage. I’m willing to bet that the knowledge would also flow both ways–you’d see industry learning some lessons and processes that actually do improve their effectiveness over time, and these NASA externs would also take their industry-gained experiences back to NASA, which would likely tone down some of the NASA analysis-paralysis over time.
Anyhow, just wanted to throw this out as food for thought.
Latest posts by Jonathan Goff (see all)
- An Updated Propellant Depot Taxonomy Part IV: Smallsat Launcher Refueling Depots - November 14, 2020
- Blog Links Updated - November 2, 2020
- Blog Migration Completed - October 26, 2020