Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

John Foley

John Foley

Editor, InformationWeek

Government Technologist: Vivek Kundra's Data Center Problem

The number of data centers belonging to the U.S. government has more than doubled in the past 10 years. Can Federal CIO Vivek Kundra put a stop to the trend?

The number of data centers belonging to the U.S. government has more than doubled in the past 10 years, an expensive and wasteful trend that Federal CIO Vivek Kundra says he wants to stop. At the same time, however, yet another massive, government-owned data center is going up in Utah.

Kundra's tenure as the United States' first CIO will be judged in part by his success in reversing course. The feds need fewer data centers, not more. Instead of spending billions of taxpayer dollars on huge capital projects, the feds need to turn to virtualization, server consolidation, cloud computing, and shared services, and consider outsourcing to technology vendors that specialize in data center operations.

Kundra has identified the government's love affair with mega IT projects as an outdated approach to today's data management challenges. The government now has 1,200 data centers, compared with 498 a decade ago. "We need to get away from this model of investing heavily in infrastructure," Kundra said at the InformationWeek 500 conference in September, a quote I've used before, but which bears repeating.

The juxtaposition between what needs to happen and what's actually going on came into sharp focus recently when Kundra called the government's data center proliferation "troubling," according to Federal News Radio. "It shows greater investment in infrastructure, yet it's more fragmented," he said.

As Kundra spoke, planning was underway at the National Security Agency for one of the biggest data centers on the planet. The construction project, 26 miles south of Salt Lake City, calls for 1.5 million square feet of building space on 120 acres. Due for completion in 2013, NSA says its new data center will be used to provide intelligence and warnings related to cybersecurity threats.

Without knowing more of the details of NSA's requirements, it's hard for an outside observer to assess whether this particular data center project is absolutely necessary. However, one thing that jumps out is the cost of the project, with estimates ranging from $1.5 billion to $1.6 billion. As a point of comparison, Google budgets about $600 million for one of its state-of-the-art data centers.

Part of the problem with government-owned data centers is that they represent long-term fixed costs. Once the concrete dries and the buildings go up, good luck getting rid of them.

It doesn't have to be this way. U.S. Postal Service CIO Ross Philo told me in a recent interview of tentative plans to build a next-generation data center, in addition to the two that the Postal Service already operates. But Philo admitted that the Postal Service's financial circumstances (losses amid flat revenue) don't make the project feasible right now. Chalk one up for fiscal reality.

And it's possible to stop a data center project even after the bull dozers have cleared ground. In August, I drove out to a data center under construction by Amazon.com in Boardman, Ore., only to find that the project had been put on hold indefinitely (see for yourself). Reason: The economy.

Some federal agencies seem to be leaning in the right direction. Homeland Security, for instance, is looking to consolidate 24 data centers into two.

But putting the brakes on the 10-year trend of data center proliferation will be a test of Kundra's influence and effectiveness. Let's see how many data centers Uncle Sam has a year from now.

John Foley is editor of InformationWeek Government. Follow me on Twitter at @jfoley09 and let me know what you think about the federal government's data center strategy.



InformationWeek Analytics has published a guide to the Open Government Directive and what it means for federal CIOs. Download the report here (registration required).



Related Reading


More Insights




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.