The procurement and development budget Department of Defense is under fire; this is no secret. The incoming administration wants to increase that amount of fire; this is also no secret. Experts are expecting several projects, such as the F-22, the Army's Future Combat Systems (FCS), and most of the Navy's new surface combatant programs to be cut heavily or, worse, canceled outright.
This would be, in my opinion, as stupid as stupid gets.
To be fair, however, DoD brought this on itself as much as any external force of pressure. Since the heyday of World War II, DoD's ability to procure and develop systems, while remaining impressive, has endured a severe loss of quality and effectiveness. Simply put: we don't do it like we used to.
More and more of DoD's design and development happens out-of-house. That is, not under the direct control of the Department of Defense. While this is very much an American capitalist ideal, it is not necessarily the best way to run things. In fact, the DoD should almost inarguably be the one department of our government that is 100% self-sufficient. Defense should not rely on anyone other than the defenders. That being stated, external input should always be welcomed.
There is also the American propensity to want to make "leaps and bounds" in technology before implementing improvements. In other words, we like waiting for the next big thing, rather than enduring the purchases of several stages of "little things." Economists might tell you this is the reason the Japanese overtook us in electronics and automobiles, and they would be right. This attitude of "bigger, better, now" is also what's hurting our military. And, again, we can point to the heyday of World War II.
You see, in the 1930s, 40s, and even the 50s, weapons systems obsolesced insanely quickly. Some within a year of being fielded. While most of us find that an incomprehensible concept, we would only have to look at modern computer development to find a contemporary example of such a phenomenon. While the WWII-era system of procurement and development was by no means cheap, it was wholly effective, and set the stage for our rapid advancement through the 1970s, the last great era for design and development until now.
Yes, systems were purchased and then "thrown away" quickly. But those throw-aways had benefit. They provided us with ample material to recycle, an excess of quality training tools, and, in their most important roles, served as test-beds for countless technological innovations (some major, some minor). We no longer have that capability today.
And why not? Well, bureacracy and politics. Every politician and general or admiral wants to be able to put their "stamp" on a particular system. Which means every politician and general or admiral naturally avoids the "small scale" innovations that could keep our procurement process cheap, yet continuously evolving in the field, and not just in the lab.
Take, for instance, the new rail gun system the Navy wants to field by 2025. The truth of the matter is that the Navy could field one tomorrow. But they would have to combine an old technology with a new one, and relegate their ultimate goal of "a new gun on a new ship" to a secondary goal.
The current rail guns can feasibly be mounted on a battleship. No, they're not as powerful as the Navy wants, but they're as powerful or more powerful than most of the other gun systems found in the world today. And we could test them in the field.
Instead, the Navy seems content with lab-testing a rail gun, waiting 10-years until the system is small and efficient enough to be mounted on a destroyer (of probably a new build or design), and then send it out into the world... without the data we could be accumulating by putting one of these bad boys on a battleship.
Mark my words: implementing the so-called "final design" of these rail guns will become far, far more expensive than currently expected because of our indirect policy of waiting. Just look at the Navy's Littoral Combat Ship (LCS). Bloated design and development; horrendously overbudget. Look at the Joint Strike Fighter (JSF). Bloated design and development; horrendously overbudget. Hell, our Air Force can't even procure a new mid-air refueler with any semblance of an efficient process. And, yet, in World War II, we had weapons systems go from idea, to drawing board, to construction, to deployment in less than a year.
But we don't like looking to the past, and we certainly don't like making small, seemingly insignificant improvements. It takes too long. The end result seems less important. Nobody can try to take all of the credit. And Al Gore invented the Internet.
Seriously, we have weapons systems still in use today that were in service 30, or even 40, years ago. And why? Because those weapons systems are constantly upgraded at a consistent pace. But nobody notices. Even the services themselves seem less interested in fixing up older systems. It's not "sexy." The new shit is.
Well, sexier don't mean better.
* This is the first part of what will hopefully be a nine-part entry in the River of Mnemosyne challenge that's happening over at The ...
I would have to admit that it takes a long time for a writer to truly be able to become objective with his or her own work. Or, at least, r...
31 is far too young.