Thursday, June 25, 2009

Why aren't standards working?

One of the things that is ailing our federal budget is unnecessary spending to 'reinvent the wheel.' Unfortunately, doing so has been a practice. The government has taken bureacratic steps to prevent this reoccurence but the various DoD components seem obstinate and are wasting taxpayers' money, states one contributor to the AFCEA publication, "SIGNAL." [citing]. I am talking about each component of the DoD - army, navy, AF - all spending money from their own budgets to develop systems that support their equipment that could be developed only once with any different source of money and applied to each branches' equipment. Perhaps two of the most notable cases are radio systems and just about all IT concepts. ..But you may also say, wait, what about the embrace of all the web 2.0 stuff? You've probably heard about GovLoop already and you may even know that the DON CIO is behind all the web 2.0 stuff, in theory (note especially the comment by erica kraft "alt+F" to find that). Although, there are some cool initiatives underway to enhance communications between the components, we have a long ways to go.

You'll have to wait on my next post until I have more comment on the nature of affairs with DoD collaboration, but I welcome your comments. Is the status of NMCI in relation to Navy's SOA Strategic Initiatives analagous to the big picture of adopting standardization and modular architecture service-wide?