Uncertainty reigns in warfare, and it is impossible to fully understand the intentions of a capable, thinking adversary in the midst of conflict. Yet, the best counter to this is to have equally adept and creative personnel able to recognize that warfare does not merely consist of armed clashes, but the combination of moral, psychological, economic and political forces.
The next step in the transformation of the U.S. Defense Department systems architecture will be networks defined by software instead of by hardware. Software-based network controls will extend the scope of what currently is limited only to data center operations.
The benefits of virtualization can be extended to thrifty end-users either through public clouds or via private clouds. The time has come to reach out to the millions of user devices that operate in thousands of separately programmable silos that require spending money on labor-intensive overhead. U.S.
Defense Department projects can be brought into a consolidated cloud environment where much lower costs and increased security can deliver immediate benefits.
The May 21, 2012, issue of Forbes magazine describes how start-up firms acquire information technologies without spending much money. These firms use commercial cloud services instead of setting up their own data centers.
In last month’s column, I reported that there were 2,904 separately funded fiscal year 2012 information technology budgets. Many of these would be set up to operate their own and incompatible networking, storage, server, operating systems, middleware or control commands.
Among many definitions, the Oxford dictionary defines a silo as a process that operates in isolation. In the U.S. Defense Department, everyone works in separate components. Computer silos have proliferated with the availability of a huge number of customized information technology solutions.
In March, the Government Accountability Office (GAO) delivered to the House Armed Services Committee a report on enterprise resource planning (ERP) systems. These ERPs would be replacing legacy systems costing $890 million per year. Replacing such systems would take anywhere from seven to 14 years. However, when the ERPs finally are installed, they would cost up to $207,561 per user and have a payback time frame as high as 168 years.
Any aggregation of computers, software and networks can be viewed as a “cloud.” The U.S. Defense Department is actually a cloud consisting of thousands of networks, tens of thousands of servers and millions of access points. The department’s fiscal year 2012 spending for information technologies is $38.4 billion. This includes the costs of civilian and military payroll as well as most information technology spending on intelligence.
We now have the U.S. Defense Department information technology enterprise strategy and roadmap. The new direction calls for an overhaul of policies that guide the department’s information systems. Yet, implementation is a challenge, and several issues require the reorientation of how the Defense Department manages information technologies.
The adoption of platform-as-a-service (PaaS) has opened up new opportunities for reducing information technology costs. Now, the U.S. Defense Department must enter this option into its planning.
A smartphone that engages in conversations is the next perturbation that will dictate how the U.S. Defense Department needs to revise its information management practices. The effects of this new technology will reverberate from individual communications protocols all the way to data architectures.
You may remember that old New Orleans house I mentioned in a previous column and its ongoing renovation that so closely matches the process of upgrading legacy federal information technology systems.
The word transparency is used in many different places but with different results. Transparency is what we want in Congress, friendships, relationships and processes, as well as in city council meetings, school board decisions, neighborhood association rules and acquisition strategies. However, in today’s world, very few things are opaque—particularly when it comes to the process of government procurement.
This is as simple as a tale of two airports.
Last year, as the April 15 tax deadline approached, I realized that I did not have my W-2 statement from the Navy Reserve. I knew it was no problem because all of that information was “easily” available at MY-PAY online. That was simple—“simple” being a very relative term—when I had a Common Access Card (CAC) and reader. However, as a retired 0-6 without a CAC, there was no “simple” button available to make this process work.
We want partners—not vendors.” All of the government-industry days, procurement updates or program reviews offer the constant call for industry to “be our partner, bring us innovation; work with us to enhance the capability for the warfighter or the ultimate end user.” Yet, partnership is a two-way street.
A week ago, I spent three nights in the hospital with my 17-year-old son, who was suffering from severe headaches and uncontrolled nausea.
With our military stretched among three fronts, our volunteer force is bearing a tremendous burden of OPTEMPO, reduced budgets and political posturing. A recent experience I had with our disabled veterans highlighted the reasons why we do what we do. It may be a good reminder to us all.
In the late 1990s, the U.S. Navy decided it needed to change the way it handled information technology. So, it created the Navy/Marine Corps Intranet, or NMCI. Yes, for many, it was seen as a four-letter word. With the NMCI, the Navy elected to outsource the entire program to industry—the company EDS. The process took many years of study and analysis, as well as dealing with policy, procedure, culture wars and a host of other common barriers to any new concept.
For the past 15 years, my family has been in an ongoing love-hate relationship with our 110-year-old historic New Orleans home, and we recently decided it finally was time to do “the big one” and renovate it. Do we move out or do we live with the mess? Can we still operate with some sanity and functionality in the house while we’re making the changes? What about our budget, managing the architecture and requirements of historic preservation?