OMB tightens reins on technology contracts

The Office of Management and Budget is tightening the reins on governmentwide information technology contracts.

In a Jan. 25 letter, OMB Director Jacob Lew revealed that OMB has begun a two-year evaluation of the need for government-wide acquisition contracts (GWACs). GWACs allow agencies to issue task and delivery orders against other agencies' multiple-award IT services and equipment contracts, usually for a fee, instead of initiating new contracts. GWACs offer agencies a way to avoid the complicated and lengthy process of open competition and negotiation for contracts.

GWACs have stirred outcry in recent years because some sponsoring agencies have allowed customers to direct task orders to preferred vendors, effectively limiting or eliminating competition. Acquisition law requires that the multiple vendors in GWACs be given a fair opportunity to compete for task orders under most conditions.

In a Jan. 11 memorandum to government procurement chiefs, Deidre Lee, administrator of OMB's Office of Federal Procurement Policy, underscored OMB's opposition to preferred sourcing. "This practice deprives the government of the benefits and efficiencies of continuous, streamlined, commercial-style competition made possible by the fair opportunity process because it discourages other multiple award contract holders from competing," Lee wrote.

In September, OMB issued a proposed amendment to acquisition regulations that would prohibit "methods such as allocation, or designation in any way of any preferred awardees, that would result in less than fair consideration being given to all awardees prior to placing each order." The proposed rule is expected to become final this month.

Meanwhile, Lew took a stab at setting official rules for GWACs, at least those seeking special designation from OMB. In his letter designating the Transportation Department as executive agent for the follow-on to its successful Information Technology Omnibus Procurement GWAC, Lew listed operating principles to which executive agent GWACs must adhere, including:

  • The multiple award contract underlying a GWAC must include a statement of work that reasonably describes the scope, nature and purpose of work to be performed so vendors can decide whether or not to bid on it.
  • Agencies as well as private companies must be able to bid.
  • The contract should include caps on prices for defined tasks, caps on hourly rates and other provisions reflecting the government's buying power.
  • Orders should be for fixed prices and should be performance-based whenever possible.
  • Orders should be based on best value and vendors' past performance.
  • To ensure competition, orders should be for specifically defined, narrow and brief projects aimed at solving part of an overall mission problem and should deliver benefits independent of future tasks or orders.
  • Long-term orders should contain "off ramps" to avoid dependence on a single contractor.
  • The scope of competition for orders should quickly be narrowed to leading contenders so they will be motivated to invest resources in coming up with superior proposals.
  • The ordering process should not make it difficult for agencies to convert work from in-house to vendor performance via OMB Circular A-76 contracting rules.

Agencies can operate GWACs without executive agent designations, but the budget agency clearly hopes the principles will be widely adopted. OMB also intends to issue further GWAC policy guidance as well as a framework for executive agency designations in an effort to more effectively carve up the federal IT market.

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Federal IT Applications: Assessing Government's Core Drivers

    In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


When you download a report, your information may be shared with the underwriters of that document.