

- #Nasa sewp 5 awarded task orders full
- #Nasa sewp 5 awarded task orders software
- #Nasa sewp 5 awarded task orders license
And because C3.ai is not on SEWP, game over. Well, apparently there's this rule? "A protester is not an interested party where it does not possess the IDIQ contract under which the protested order will be or has been issued". So, how did GAO reach the conclusion that C3.ai was not an interested party?

That conclusion at first surprised me! After all, the regulations define an interested party as "an actual or prospective bidder or offeror whose direct economic interest would be affected by the award of a contract or the failure to award a contract." C3.ai sure seems like a prospective offerer, with a direct economic interest, by the award (or failure to award). and lost.īut, here, GAO never reached the question of whether CDC was justified in using Palantir because GAO concluded that C3.ai was not "an interested party" in the award decision. After all, Palantir famously made a similar argument in 2016.
#Nasa sewp 5 awarded task orders full
The protester argues that, “under the Federal Acquisition Regulation, ‘brand-name specifications shall not be used unless market research indicates other companies’ similar products, or products lacking the particular feature, do not meet, or cannot be modified to meet, the agency’s needs.’” C3.ai contends that if the CDC had conducted the required market research, the agency would have found that the protester-and not Palantir alone-can provide a full solution for the agency’s requirements.
#Nasa sewp 5 awarded task orders license
So, C3.ai protested the SEWP award and argued that CDC should not have required a SDVOSB to use Palantir: C3.ai asserts that CDC’s brand-name justification in support of its decision to limit the SaaS solution license to Palantir Foundry products is improper. And it basically argues that anything it can do anything Palantir can do. It, like Palantir, is an enterprise data platform. All very standard, federal contracting 101 type stuff.Įnter C3.ai. And because these contracts all used Palantir, the government wrote up a brand-name justification for Palantir. So, HHS decided to combine these contracts together and bid the opportunity as a task order under the NASA SEWP GWAC as an SDVOSB set-aside. Compounding the situation, all 3 of these systems were all contracted through a single "value added reseller" called i3 Federal LLC, and HHS even had a separate contract with Palantir. Under the hood, though, they were all Palantir. You see, over the course of 12+ years, HHS had built 3 different systems with 3 different fun and clever names, and each of them sort of related to data things. Since then, it has expanded to include information regarding therapeutics and at-home test kits (over 500 terabytes of data managed across a few thousand users). Tiberius was created in the summer of 2020 and was tasked with managing the production, delivery, and administration of COVID-19 vaccines to the American public. The current HHS Protect Contract (NNG15SD31B / 75D30122F 13684) was transferred from HHS to CDC in 2022. HHS has since served as the common operating picture where most COVID-19 data (approximately 1 petabyte of data managed across a few thousand users) is generated from and shared to partners, the White House, and the public. HHS Protect was created in March 2020 by HHS in collaboration with CDC as a data integration, analytics, and situational awareness platform for the whole of Government response to COVID-19-inclusive of information regarding cases, deaths, hospitalizations, diagnostics, and resource planning.
#Nasa sewp 5 awarded task orders software
A recent award in 2021 enabled CDC to migrate the DCIPHER solution from a CDC on-premises solution to the Palantir Foundry cloud software as a service platform. which all appear to be sort of the same thing? CDC awarded an estimated $19 Million between 20 via contracts to develop, operate, and maintain the DCIPHER solution that today is a configuration of commercial software called the Palantir Foundry. and then continues with another product in 2020 called Tiberius. and then in picks up dramatically at the beginning of the COVID-19 pandemic in 2020 with a product called HHS Protect. Our story begins in 2010 with the creation of a product called DCIPHER. Today, however, we will stay focused on a more narrowly funny thing. Maybe one day I will write about those things. I thought I might write about the strangeness of setting evaluation criteria for SaaS that is not primarily based on price.īut, no.

I thought I might write broadly about GWACs and strategic sourcing and set-aside pools. When I sat down to start writing, I figured I would write primarily about the government-facilitated cottage industry that is value-added resellers. Last week, I announced that I would be writing about the GAO's decision in C3.ai.
