At at time when federal (and local) government spending is under an electron microscope, an examination of the government's worst tech purchases seems in order. If the news that the U.S. Navy may have paid $400 for ashtrays deployed to submarines, or the apocryphal tale that NASA once spent $10,000 on a space toilet got you hopping mad, well, you may want to sit down, because the money that the feds have wasted on failed or substandard technology projects has, over the years, cost taxpayers the equivalent of the GNP of several small nations. Here are some choice examples of goofy federal and state government tech buys in recent history.
The IRS's Customer Account Data Engine (CADE)
Final cost: $400 million
Who's responsible: IRS, Vendor Computer Science Corporation.
The IRS made a $400 million blunder with the Customer Account Data Engine (CADE) in 2004.
If any federal agency should know how to handle massive amounts of paperwork and data, it's the IRS. In the late 1990s, the agency had been struggled for decades with a cobbled-together technology called the Master File System.
In 1998, work began on its successor; and in 2004, when the IRS announced the Customer Account Data Engine (CADE), it was hailed as a revolution in tax-form processing. Of course, it arrived three years late: The original plans for CADE had projected that the system would be up and running by 2001.
In 2007, CADE processed only about 11.2 million tax returns. But by March of the next year, CADE had ramped up significantly, and it processed more than 15 million returns in just the first three months of 2008. Briefly, things looked bright for the system, but in 2009 CADE was processing forms at a rate of about 40 million returns a year--far less than expected. The system suffered from problems with data security, too. The IRS pulled the plug on CADE development in June 2009.
"After over 5 years and $400 million, CADE is only processing about 15 percent of the functionality originally planned for completion by 2012," read a later GAO report, which noted "unexpected complexities" in the system. The IRS continues to use CADE while it works on plans for its successor, CADE 2; but the agency no longer updates the system.
Secure Border Initiative-Network (SBInet)
Final cost: at least $620 million (as of 2008)
Who's responsible: Boeing, Customs & Border Protection division of Homeland Security
When the Customs & Border Protection (a division of the Department of Homeland Security) announced in 2006 that it would develop a "virtual fence" along 53 miles of the Arizona-Mexico border, some observers hailed the plan as a perfect application of established, off-the-shelf technology to solve a serious problem, though others questioned the ultimate cost of the project. Too bad it didn't work out quite the way DHS expected.
The electronic border surveillance system accounted for more than half of a $1.1 billion government contract with Boeing, but by 2009 members of the House of Representatives were taking CBP officials to task for repeated delays and cost overruns that forced the program's administrators to ask for $50 million in economic stimulus money (which they received). A 28-mile prototype was completed in 2008, but continued delays may result in cancellation of the program before the end of 2010, with none of the permanent installations completed.
In a 2009 hearing before the House Homeland Security Committee's Border, Maritime and Global Counterterrorism Subcommittee, the Secure Border Initiative's executive director Mark Borkowski explained "What we bet on, which was probably not a good bet, was that this was like buying a new printer for your computer." Maybe if they'd just bought $620 million worth of printers, and stacked the boxes end to end along the border, they'd have had more success.
Denver International Airport's Automated Baggage Handling System
Final cost: $193 million
Who's responsible: New World Airport Commission, United Airlines, BAE Systems
Touted as a revolutionary technological marvel in 1992, during the airport's construction, Denver International's automated baggage-handling system ranks as one of the worst technology failures the federal government has ever funded. The system, designed to move tens of thousands of bags a day between the airport's terminals and planes, never worked right. It was an unmitigated disaster.
(Click the thumbnail above for a better look at DIA's DOA baggage handling system.)
According to plans, the system was to use Destination-Coded Vehicles ( DCVs)--essentially, suitcase-size barcoded similar to the ones you put your laptop, shoes, and belt in so airport security can scan the items with an x-ray machine--to transport bags through a computer-controlled network of conveyor belts at a rate of 1000 bags per minute.
The specs included 300 computers (with 486 chips--woo) as well as dozens of barcode readers, ethernet cabling, more than 17 miles of tracks, and more than 6 miles of conveyor belts.
But the result was hilariously bad. When invited to check out the system in 1993, members of the press witnessed bags flying out of the DCVs, and clothes and other suitcase contents strewn about as DCVs crashed into one another, flew off the tracks, and caused the system to jam repeatedly. United Airlines, one of the airport's largest customers, stopped using the system after just a few months. It has not been used since.