Obama administration officials say there are too many IT procurement vehicles, and they want agencies to consolidate their buying around existing interagency contracts rather than launch new ones. There is even a strong case to cut back on current contracts, which officials say are often duplicative in what they provide for buyers.
Where does that leave governmentwide acquisition contracts (GWACs)?
In early 2012, the Office of Federal Procurement Policy (OFPP) issued rules requiring agencies that wanted to award their own multi-agency contracts (MACs) to submit a business case arguing why those contracts were necessary — something agencies that wanted to award GWACs have had to do for years.
“Agencies are required to balance the value of creating a new contract against the benefit of using an existing one, and whether the expected return on investment is worth the taxpayer resources,” said Dan Gordon, who was OFPP administrator at the time.
Following the 1996 Clinger-Cohen Act that authorized their creation, GWACs became a poster child of sorts for that kind of contract inflation. Many agencies were looking to create their own contracts as testimony to their procurement mojo in an era of huge growth in government IT acquisition. For vendors, GWACs were seen as a hunting license to pursue lucrative government IT business.
Keep reading this article at: http://fcw.com/articles/2013/06/07/feature-gwac-facts.aspx
