Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Future of Government Data Centers
- The Future of IT: How CIOs Can Enable the Service-Oriented Enterprise
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Mitigating Insider Threats in Virtual & Cloud Environments
- Modern Mission Critical Series
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
- Air Traffic Management Transformation Report
- Cloud First Report
- General Dynamics IT Enterprise Center
- Gov Cloud Minute
- Government in Technology Series
- Homeland Security Cybersecurity Market Report
- National Cybersecurity Awareness Month
- Technology Insights
- The Cyber Security Report
- The Next Generation Cyber Security Experts
Shows & Panels
At Pentagon, lessons learned on data center consolidation
Wednesday - 9/28/2011, 4:47pm EDT
At the Pentagon, however, the latest Office of Management and Budget-directed effort is round-two in a long process of IT consolidation that began in the mid 1990s. The Defense Department began its consolidation under the auspices of a massive and lengthy remodeling of the building that stretched on until this year.
A data center (Photo courtesy of Army Information Technology Agency)
What's now called data center consolidation started for the Pentagon as an effort to use its precious office space more wisely. Before the remodeling began, Adcock said, servers were scattered throughout the building in an ad-hoc fashion-tucked under desks and stashed away in closets with telephone equipment.
Then came the Sept. 11 attacks. At that point, he said, the server reorganization changed from an effort focused around remodeling to one centered on survivability.
Donald Adcock, Director of the Army Information Technology Agency (Photo courtesy of the Army ITA)
In all, ITA has taken 30,000 square feet of floor space that used to be occupied by redundant, inefficient computers and returned it to productive office use.
Today, the Pentagon has what ITA refers to as a single data center taking up about 15,000 square feet of floor space, though it occupies more than one room. In order to maintain continuity of operations and deliver computing services wherever they're needed in the building, the "center" is spread out through 14 different physical rooms. If one room is damaged in an attack, mission-critical data and services can fail-over to other rooms.
Additionally, the Pentagon data center has fail-over capacity to backup data sites outside the building in the event the entire building is compromised. Citing security concerns, ITA officials declined to say how many such sites exist or where they are located, but said they are in multiple locations outside of the National Capital Region.
Despite years of work that predated the modern Federal Data Center Consolidation Initiative, Adcock said the Pentagon's work in the area is far from finished.
Consolidating computer systems into server rooms is one thing; the next steps are the same as they are with other agencies: rationalizing the number of active software applications, doing smarter enterprise licensing of software, and virtualizing systems so that one server can do the job of many. ITA says it has made progress toward those goals. Since 2006, the agency has increased virtualization capacity by 30 percent, reduced software licensing costs by 10 percent and increased processor performance by 40 percent.
Also, unlike during the Pentagon's first round of consolidations, ITA will have to scrupulously track its cost savings as it pushes toward OMB's IT efficiency targets.
"I've tasked an organization within ITA to start tracking those efficiencies, because we've got to be able to answer the question of how many dollars did we save," Adcock said. "As far as the savings from the past, every time we would make an investment or we would find something, it would be reabsorbed to the tenant. As I took something out of your closet, I had to invest money to build the infrastructure to put you in a new space. If you didn't provide me with what it cost you, I didn't have the data. People didn't keep good records and a lot of things got lost. So it's very hard to figure out what was saved in the first round of consolidations." And quantifying the savings going forward won't be easy, he said.
"The savings is so second and third order effect," Adcock said. "By changing the way you do electric supplies or air flow in the building, you have to start asking much did we pay for electric before, and were we tracking that? In a building like a Pentagon where you have so many tenants that control those things, it's very hard to pull that thread and come up with a dollar amount. It's doable, and we're working really hard to get our hands around those costs."
Adcock said he would offer several pieces of advice for federal IT managers who are moving forward with data center consolidation for the first time.
"You need to understand what's in your environment," he said. "Inventory it well and get a good understanding of what it is, because you're going to need to provide for it in your future environment. You need to have robust policy throughout the organization that others can use, and say either 'this is the mission, you have to move to it,' or defer to and ask, 'how do I get there?' You have to have strong policy. You have to have a strong understanding of what it is you're trying to do for your customer and make sure you can deliver on it. That means strong service level agreements. And you've got to understand the requirements. Consolidating into an environment is one thing, but it's another thing to know how you're going to it and how you're going to put it in place. Proper planning up front can help drive some of that."