Re: Space Shuttle is the Model T, its time to consider the Model A or reconsider the X-33
There wont be a replacement for this shuttle. They can't build one anymore, there is no pipeline anymore. Most of the vendors and companies that built the different parts have gone on to other projects and the expertise and specialized rigs and equipment are gone.
To restart the shuttle assembly line, while technically possible, would take years and cost nearly as much as starting from scratch. Indeed, it would be starting from scratch.
They have no real choice but to go forward with a new design. However, they haven't shown much gift for managing large projects recently. As Henry Spencers email sig says "Faster, Better, Cheaper requires leadership, not just management."
As far as the older tech. I believe that the onboard systems have all been updated fairly regularly. But many of the systems are still running original system, especially on the ground. The reasons for this are complicated as you might imagine. NASA has been sinking LOTS of money and effort into replacing the original data handling systems but has been completely unable to do this. Much of the work I believe has been trying to replace the custom hardware/embedded software systems with off the shelf PC hardware running linux. But this has been a total failure.
The reason is in the nature of modern systems vs real custom system design. The shuttle systems are a very fast stream of data which has to be processed and run through decision making matrixes and the result has to be guaranteed to be out in a certain amount of time. For example, an over pressure reading at one point necessitates a valve closure in another within 20ms or the pipes burst. Regardless of what else is in the data stream or what else is happening. With the original embedded systems the engineers knew exactly how long it would take the bytes that made up the reading to get into the system, exactly how long it would take to fall through the decision making logic and exactly how long it would take to formulate the control response and send it to the next controller and close the valve. This was possible because these folks designed the hardware and the software that ran on it in a non-multitasking environment in a specialized data handling language that they developed to be able to do this specific task. This is a real time system in the true sense of the word, and that is what's necessary.
No modern computer is a real time environment. They have not been up to the task. No matter how much money and pentium horsepower and extra memory they cannot guarantee 100% when what will happen. Imagine if there is a page fault and the system swaps between that first event above and the second. Don't try to make a computer hardware/software argument of how to do it using a realtime kernel extension or some such, NASA spent hundreds of millions on this and it simply can't be done.
So the original system now runs on new custom hardware, and it continues to run the whole place this way. The readouts and screens are all updated but the backbone of the whole place is still running the same programing language that was developed to get us to the moon.
I would not call this a failure, I would call it a great triumph of the original engineers (one of whom is a great friend of mine which is why I know anything about it) The tragedy is that NASA has lost their mind-share. The great people that developed that original system have all left (or retired) and the younger folks of that caliber are no longer attracted to work there. Speaking with one fellow he commented that the last A should be at the beginning because it was administration that they did the most of. There are still terrific people, some of the best and the brightest, but they are not being given the leadership that they need to make it work. It's a management crisis. But it's also an incredible task. I don't think most people realize the complexity of what they really do to make any of this work at all. When you talk to the people who are really building it and putting it together it's truly staggering. Perhaps blaming managment is too easy, but I've worked in enough large companies to have that be my gut reflex
These things are very hard. Building a new system and getting it to work will be equally difficult. If the higher ups try to apply standard IT buzzwords, more money will go down the pit and more people will die when it goes wrong. The reality is that no managment is trained enough to make the choises. They have to start with the problems and come up with good solutions, whatever they might turn out to be. It is current management thinking everywhere that I've worked to get what they think are the best tools first and then tell the engineers what to do with them. That doesn't work.