Big Data. Big Decisions
InformationWeek
Special Coverage Series


GAO: Redundant Federal IT Systems Waste Money

The GAO identified four key areas for IT process improvement -- Department of Defense business systems, enterprise architecture, data centers, and e-health records -- and gave recommendations for how the government could eliminate overlap in these efforts.

Government Innovators
Slideshow: Government Innovators
(click image for larger view and for full slideshow)

The federal government could save billions of tax dollars annually by addressing duplications in programs, agencies, offices, and initiatives that are adversely affecting the government's financial and operational effectiveness, according to a federal watchdog agency.

Some of the areas of overlap identified in a new 345-page report (PDF) from the Government Accountability Office (GAO) -- the first it's delivered after Congress directed it to report on this area -- are within single departments or agencies, while others span multiple organizations.

The agency identified 81 areas of duplication in hundreds of federal programs that are diverse in their scope and missions, ranging from agriculture to homeland security to social services to international affairs.

Not surprisingly, several key aspects of the government's implementation of IT were identified in the report as areas where overlap could be eliminated to help the government provide more efficient and effective services.

The GAO in particular identified four key areas for IT process improvement -- Department of Defense (DoD) business systems, enterprise architecture, data centers, and e-health records -- and gave recommendations for how the government could eliminate overlap in these efforts.

At the DoD, 2,300 investments in its business-system environment are fraught with overlap, including lack of standardization; multiple systems performing the same tasks; and instances where the same data is stored in multiple systems and in which the same data is entered manually into multiple systems.

Among the recommendations the GAO made to improve these areas include defining DoD business-system investments that can be implemented within the context of its federated business enterprise architecture, and a more evolved investment process that is institutionalized at all levels of the organization.

The GAO also recommended that the DoD manage its business system programs and projects with integrated institutional controls to ensure they consistently deliver benefits and capabilities on time and within budget.

While the DoD duplication problem is internal to the department, the GAO found that enterprise-architecture overlap is a cross-organizational problem, according to the report.

Maintaining legacy systems is a costly proposition for the federal government, and enterprise architectures are blueprints used by organizations for modernizing their IT environments. The GAO found that the architectures agencies are currently developing are "duplicative, poorly integrated, unnecessarily costly to maintain and interface, and unable to respond quickly to shifting environmental factors," according to the report.

Moreover, a 2006 GAO report found that agencies and departments were at different stages of enterprise architecture development and implementation, with most not "where they needed to be," according to the report.

To remedy this situation, agencies should use the GAO's enterprise architecture management maturity framework, which it recently issued as a guideline for enterprise-architecture creation, but which so far agencies have not leveraged to their fullest advantage, according to the GAO.

Duplication in data centers also is a cross-organizational duplication problem, one the government is already well aware of and currently trying to address by a broad, White House-mandated consolidation effort, according to the GAO.

 1 | 2  | Next Page »


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.