Think 2005/6, what options did the AF, Lockheed or Boeing have? As independent companies the overhead costs were much higher than ULA. There was no alternative launch offering. So there was a shotgun wedding. Now 8 years later was that the correct decision? ULA has delivered what was intended, reduced cost, assured access to orbit and reliable launch. Even today there is no viable alternative, a lot of hope, but a lot more broken promises.
Well, with the details of the politics and legalities aside (as I don’t understand it enough to know them all), There were some options.
Jim and you both said the overhead of two independent companies would be higher than ULA, and I’ll take you guys at your word. But how much more? Would it be significant, or more of a drop in the bucked of the huge amount that’s spent on the joint ULA anyway. If we are talking a few million more per year to keep them separate, is it worth it to have this separate entity now that can’t be separated now?
If we are talking tens of millions or hundreds of millions per year, that may be another story.
I mean, I really don’t know, but I have to assume there’s a certain amount of extra costs associated with physically merging Boeing and LM operations into a single entity, especially when their parent companies are often competitors with often opposing interests. Even a shotgun wedding is between two people that like each other enough to get knocked up. It takes a pretty big shotgun to force two people that don’t particularly like each other (or hate each other), and who’ve never liked each other, and who don’t really even have anything in common, into a marriage. And it’s probably a pretty ugly process.
How much cheap is that –really- than keeping the two separate, but splitting the contracts for both for a period of time, and then studying an option to downselect to just one? I’m just looking at it form afar, and that wouldn’t seem to be much more expensive than pushing the two together. And now USAF is married to that new entity with both of their LV’s and all of the legacy liabilities brought in from both sides (the same as they’d have been separately I’d think).
But then, they could have downselected to one and kept Titan as a backup standby while the new EELV proves itself. Then fully retire Titan once the chosen EELV hit an acceptable level of reliability. Both designs were known by USAF and were legitimate, and it should be assumed that any problem that did arise would not be catastrophic or program ending. It would be worked through and fixed. Since humans are not at risk on them like they were After Challenger or Columbia, the criteria for fixing a problem would not be as onerous. A backup would really only be needed temporarily. Maybe they could buy some Titan LV’s and store them somewhere in case they were needed, then retired the production. If not needed by the time the EELV proved itself, they could be fitted with payloads and launched (to get them used so not to go to waste), and then the pads and facilities retired. IF needed, then they could be used while the EELV was being fixed. It’s not like –most- USAF/DoD payloads couldn’t have been delayed 6 months or a year while the EELV issue was getting fixed. And if there was a payload that absolutely –couldn’t- wait as a matter of national security, there’d be an inventory of say 5 Titan IV LV’s which could be tapped.
Would that have been more expensive then supporting two full new LV’s, with new pads, and new infrastructure, full staffs, etc? I dunno, but it seems like there could have been options other than this shotgun wedding that married USAF to two redundant EELV’s forever.