Feedback on federal contracting

By | March 9, 2009, 12:07pm PDT

Summary: Readers respond. Reforming IT acquisition and purchasing will be hugely difficult.

Writing over the weekend about Vivek Kundra, I said that if Obama planned to seriously make government more efficient, he would need to reform contracting:

[Without reform], government IT will never match the private sector’s and more importantly we will continue to waste taxpayer money at a time when we can least afford to do so. If reform succeeds it will benefit government and taxpayers for decades to come.

I received two interesting comments that pushed back on that sentiment.

As a former USAF acquisition person — currently teaching government contracting — my response is “good luck.” The Federal Acquisition Regulations are passed by Congress (not the Executive). They drive average acquisition lead times to almost two years in order to get through all the hoops. Unless Congress is willing to step to the plate and reduce some of the requirements for small business and other set-asides; to shorten the time for competitive responses; and lots more — we are not going to get anywhere. By the way, no-bid contracts are a thing of war as far as DOD is concerned. A no-bid contract is almost unheard of except in emergencies.

I don’t really have an opinion on whether Congress will be able to do this. I admit it seems unlikely but I would suggest that the ONLY way it could happen would be for the Administration to make the push and to push hard for Congress to reform the rules. I think this is an area that will fit under the “a crisis is a terrible thing to waste” umbrella. The financial crisis is obligating the government to spend huge amounts of money, Republicans are asking for fiscal discipline (which is of course the worst possible thing to do in a deep recession but Obama is promising line-by-line scrutiny to cut unnecessary costs). I have no doubt that billions can be saved by allowing the government to operate more freely, by contracting with less red tape and more accountability — that is, as any rational business would act.

Unfortunately, another commenter wrote, it’s not that simple.

I think it’s important to recognize that Government is (and should be) held to a different set of standards than private business. Government is required by regulation to deal equitably with all willing contractors. Private business, on the other hand, is under no obligation to offer equal opportunities to all interested offerors and can work within existing business relationships, even if the contract cost is greater. This probably accounts for business’s greater agility.

Well … in business, you are always trying to cut costs, to get vendors to compete with one another. But you also realize that the cost of a purchase is not just the amount on the bottom line, it’s also the cost of maintenance contracts, the associated internal costs, the training costs. Most importantly, it has to work and you have to calculate the lost productivity, the lost hours when something doesn’t work as advertised. You build relationships with trusted vendors and you don’t risk big projects on unproven vendors because they bid 10 percent cheaper.

The problem with government IT is that there is a tendency, even a need to build huge, mammoth systems that are so complex they are inherently primed for failure. Everyone knows the projects will fail but neither the vendor nor the government employees are able or interested in stopping them. What I think Kundra can offer is a completely transformed mindset away from giant projects and towards breaking IT into smaller bits that can talk seamlessly and securely with one another. I don’t know exactly what that looks like but I think that’s going to be how you get the right level of data- and knowledge-sharing.

Since the big vendors have failed so spectacularly, I think the door is wide-open for agencies to put real programmers on its payroll to create projects like the ones Kundra has created, doing it with open interfaces so that the open source community can create new applications, and letting small fast-moving developers into the bidding process.

Perhaps this is all blue sky and the realistic response is Good Luck. Or perhaps something hugely better is within our grasp. Government IT is not the problem. Bad IT (and in general terms, IT contractors) is the problem.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Disclosure

Richard Koman

http://government.zdnet.com/?page_id=3731

Biography

Richard Koman

Richard Koman is an attorney admitted to practice in California. As a technology writer since the mid-1980s, Richard Koman has documented the role of computing in the transformation of the graphic arts, the growth of the Web and the birth of the peer-to-peer phenomenon. He worked as a book and web editor for O'Reilly Media throughout the 1990s, editing several influential websites and numerous best-sellers. As a lawyer, as well as a tech writer, he brings a unique perspective to the blog's intersection of law, government and technology.

Related Discussions on TechRepublic

Did you know you can take part in these discussions with your ZDNet membership?
5
Comments

Join the conversation!

Just In

Point being...
John L. Ries 11th Mar 2009
...the law itself may be overly cumbersome and in need of review.
0 Votes
+ -
Nixon in China
John L. Ries 9th Mar 2009
A Democratic president may actually have an easier time reforming procurement practices than a Republican one would, simply because most of the federal procurement statutes were enacted by Democratic Congresses in response to scandals back when Ronald Reagan was president.

George W. Bush could have tried it (had he been interested) but it would have been seen as part of a broader effort to restore presidential supremacy and possibly to funnel additional money to loyal Republican defense contractors. Besides, it was more his style to simply ignore statutes he found inconvenient, even if he had the votes in Congress to repeal them.
0 Votes
+ -
RE: Feedback on federal contracting
dhays Updated - 10th Mar 2009
I work for the Federal government in OKC, I am not involved in contracting, IT or otherwise. I believe, though, that we are trying to streamline as much as possible, under the law, the contracting process. We have contract employees working alongside the full time employee (FTE).
In many cases a Contracting Officer is working alonside the people who write the contracts or order from them, this speeds the process as the CO knows what is needed on the contract and can identify where the writer needs to update his language and the the writer knows what equipment is needed, eliminating back and forth emails, meetings, etc. at one or the other's convenience.
Sorry to be so blunt, but it sounds like there are more supervising than doing. It sounds a lot like the extra precautions in the nuclear industry where you have someone tightening bolt with someone reading out of a book the specs to tighten the bolt and someone else making sure that the book is followed and that the instructions are followed by the reader and the person doing the physical work. For safety, this does make sense but for efficiency it does not.

The real question is "where does innovation come in, from the top or the bottom or somewhere else?"
0 Votes
+ -
Point being...
John L. Ries 11th Mar 2009
...the law itself may be overly cumbersome and in need of review.
0 Votes
+ -
Gore Already Tried
MichP 10th Mar 2009
During the Clinton years, Gore had a program (I don't remember the name) for collecting suggestions from anyone who had ideas about how to improve the way government and contractors worked. But I never noticed any changes.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix