Government Procurement Process Needs an Overhaul

Ann All

I've written a couple of times about the federal government's efforts to improve its poor technology track record. Much of the focus appears to be on project management, with initiatives like the Department of Veterans Affairs' Program Management Accountability System (PMAS) vetting process, which it used to identify and either rework or cancel IT projects that were behind schedule and/or over budget. It sounds like a similar approach is being extended to other agencies, based on a Wall Street Journal article that says the Obama administration is considering overhauling 26 troubled federal IT projects that are over budget, haven't met expectations or both.


Among the targeted projects:

  • A $2.8 billion Treasury Department project to update the agency's computer network and telecommunications, which has resulted in 45 data centers that can't support newer Internet technologies, according to Office of Management and Budget officials.
  • A $2 billion Air Force logistics project that has already cost $650 million and is still years away from deployment.
  • The Federal Bureau of Investigation's $557 million Sentinel case-management system, which was halted because of poor performance.
  • A $7.6 billion Interior Department project to consolidate technology systems, which has spent $3.25 billion thus far on 200 data centers and 9,000 servers, yet has failed to reach even such basic goals as getting employees on the same e-mail system.


Federal CIO Vivek Kundra stresses the importance of splitting such projects into more manageable chunks. He's right, of course, but I can't help but think there's a pretty big problem even before these projects make it to the scoping stage. I think part of the problem is a convoluted and arcane procurement process that favors incumbent IT vendors and contractors that are experienced in jumping through all of the necessary hoops, mostly giants like AT&T, Lockheed Martin, Accenture, IBM and Oracle, all companies involved with problematic projects, according to the article.


I am not saying there is anything wrong with any of those companies. But by making the process so complicated, the government is discouraging many other companies from even trying, which means agencies aren't getting a full picture of the possibilities.


Government procurement appears to be a broken process, one in which agencies hamstring even their usual vendors from suggesting different ways of solving problems or achieving goals. Writing on UK, Gary Bettis of Compass Management Consulting opines that government procurement focuses too much on the technical aspects of service delivery and not enough on desired business outcomes. He writes:

... Instead of simply defining the need for desktop clerical tools such as word processing and e-mail, a procurer might insist on a certain PC specification, operating system and versions of the word processing tools rather than letting the vendor come up with the most cost-effective solution to deliver the same outputs.

The result? Bettis says he and his Compass colleagues estimate the public sector pays at least (emphasis mine) 40 percent above the market rate for outsourced IT services. (The figure is based on an analysis of central government contracts in the UK over the last five years. I suspect the figure would be pretty similar here in the United States.)


To be fair, Bettis also mentions government agencies' frequent demands for customized technology, an issue that is also touched upon the Journal article, which says, "technology companies and federal contractors have privately raised concerns about the Obama administration's broader review of technology spending, arguing that delays and cost overruns often occur because federal officials change their requirements for the projects."


If they really want to cut costs and boost efficiences, government agencies will use standardized platforms, Bettis says. Standardization "allows service providers to do what they have done so successfully in the private sector -- provide utility IT services to a range of clients at a competitive price, having achieved economies of scale through use of the same delivery infrastructure."


There are certainly hints that at least some agency officials in the United States realize this. For instance, Kundra has been pushing government agencies to consolidate data centers and consider cloud computing. Problem is, just as with tweaking the procurement process, a move to the cloud will entail some major changes to government culture.

Add Comment      Leave a comment on this blog post
Aug 26, 2010 2:00 AM Jenny Sutton Jenny Sutton  says:

The mind boggles at the size of these individual projects. It is hard to imagine any multinational private sector company spending this type of money on a single project. Makes me wonder whether it the problem extends beyond the procurement process to the definition of the problem itself, and the process of defining it.

Governments, just like private sector enterprises, should be careful about allowing external consultants to define the problem to be solved with each of these technologies.

Too often clients pay for expensive solutions because they simply accepted the consultants definition of the problem in the first place.

Letting a consultant define the problem allows them to define it terms of a solution that they are best positioned to deliver - rather than the simplest solution to meet the clients need.

So the only way to significantly reduce government purchase of consulting and major IT projects is to significantly improve the process for defining the need in the first place.

Nov 14, 2011 10:07 AM Ben Benjabutr Ben Benjabutr  says:

I think identifying specifications of products properly is a good thing to do. The real problem is how to do it quickly.


Post a comment





(Maximum characters: 1200). You have 1200 characters left.



Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.