Each party to a GSA Schedule Contractor Teaming Arrangement must hold the Federal Supply Schedule contract in question.
As demonstrated by a recent GAO bid protest decision, if one of the parties to the GSA CTA doesn’t hold the relevant FSS contract, the CTA may be found ineligible for award of an order under that contract.
It’s hard to top last week’s government contracting news, which included the major SDVOSB Supreme Court victory in Kingdomware. But with the Fourth of July just a week and a half away, there is still plenty going on in the world of government contracts law.
In this week’s SmallGovCon Week in Review, an SDVOSB’s owner speaks out about his important GAO bid protest win, suspensions and debarments of government contractors dropped in 2015, major changes are coming to the GSA Schedule, HUBZone contract awards decline, and much more.
It’s been a wild week in the world of federal government contracting. Yesterday the Supreme Court issued two major decisions affecting contractors: Kingdomware Technologies, Inc. v. United States and Universal Health Services v. United States ex rel. Escobar. If you’re a regular SmallGovCon reader, you know that I’ve been following Kingdomware closely for years, and we will have a separate post later today with reaction to Kingdomware from around the country. But Escobar is an important decision too, so don’t miss out on the coverage of that case.
In addition to coverage of Escobar, this week’s SmallGovCon Week In Review features a major new rule prohibiting contractors from discriminating on the basis of sex, GSA adding a new category on IT Schedule 70, the indictment of a former GSA director and many more.
SDVOSBs and VOSBs are big winners today, as the Supreme Court unanimously ruled that the VA’s “rule of two” is mandatory, and applies to all VA procurements–including GSA Schedule orders.
The Supreme Court’s decision in Kingdomware Technologies, Inc. v. United States, No. 14-916 (2016) means that the VA will be required to truly put “Veterans First” in all of its procurement actions–which is what Kingdomware, and many veterans’ advocates, have fought for all along.
While it may be April Fools’ Day, we promise not to play any pranks on you–not that I didn’t think about a headline trumpeting a major change in the 8(a) program, linked to a video of Rick Astley.
Instead of pranks, it’s time for our weekly dose of government contracting news and notes from around the country. In this edition of SmallGovCon Week In Review, you will find articles covering a potential shift in GSA schedules, the State Department’s audit findings on procurement waste, a billion dollar award is split between 21 vendors to tackle the short and long term needs of the VA’s IT department, the second part of my interview with GovBizConnect, and much more.
The VA and Kingdomware Technologies Inc. haven’t agreed on much in recent years, but in briefs filed with the Supreme Court on November 20, 2015, they agree on one thing: the pending Kingdomware Supreme Court case is not moot.
Hopefully, the fact that neither party wants the case dismissed on a technicality will help convince the Court to decide Kingdomware on the merits.
An agency may not procure new services under an existing GSA Schedule delivery order if the new services exceed scope of the original delivery order.
In a recent decision, Onix Networking Corp., B-411841 (Nov. 9, 2015), the GAO sustained a protest where the agency acquired a new type of software by modifying an existing delivery order for software license extensions because the acquisition exceeded the scope of the initial delivery order. According to the GAO, the out-of-scope modification amounted to an improper sole source contract.