Best listening experience is on Chrome, Firefox or Safari. Subscribe to Federal Drive’s daily audio interviews on Apple Podcasts or PodcastOne.
The Defense Department’s high-profile and controversial cloud procurement known as JEDI overcame a major hurdle, but is far from out of the woods.
An internal DoD investigation found the Joint Enterprise Defense Initiative has not been prejudiced by at least two former employees, who previously had worked at or had ties to Amazon Web Services, the Pentagon announced Wednesday.
“The department’s investigation has determined that there is no adverse impact on the integrity of the acquisition process,” DoD spokeswoman Elissa Smith said in a statement. “However, the investigation also uncovered potential ethical violations, which have been further referred to DoD inspector general. There are two different components of the investigation. First, DoD investigated potential conflicts of interest as they relate to the acquisition process. This portion of the investigation determined that there are no conflicts of interest that affected the integrity of the acquisition process. However, there may be potential ethical violations, which have been referred to DoD IG for further investigation.”
DoD initiated the investigation, which presumably focused at least in part on Deap Ubhi, a former member of the Defense Digital Service, after Oracle filed a bid protest with the Court of Federal Claims.
As part of initiating the investigation, DoD asked the judge for a stay in the protest and procurement process.
Smith said DoD will be asking the court to lift the stay so it can move forward with the investigation.
In the meantime, the Pentagon took two more steps to move JEDI closer to the award stage.
First, it downselected bids from four companies to come up with a final two. Sources confirmed AWS and Microsoft remain in contention for the contract, which some estimate to be worth $10 billion over 10 years.
Sources said DoD told IBM and Oracle, the other two bidders, that both companies were out of the competitive range. IBM also initially submitted a bid protest to the Government Accountability Office, which was dismissed when Oracle filed with the federal court.
Second, DoD’s Washington Headquarters Services office released a sources sought notice for cloud computing support services on behalf of the Office of the Chief Information Officer.
“The Cloud Computing Program Office (CCPO) has been stood up under the Department of Defense (DoD) Chief Information Office (CIO) to act as the centralized program office for delivery of the JEDI Cloud capability. The CCPO will be responsible for overarching operations of the JEDI program to include: business operations and leadership support, engineering and security, strategic communications, user engagement and program execution,” a notice in FedBizOpps.gov states. “To accomplish the operations of the JEDI contract, the CCPO requires highly skilled services to support program office operations and delivery of a modern enterprise cloud services solution, to include end user engagement and supporting migration of early adopter applications. The vendor shall support the execution of business operations and leadership support, engineering and security support, office automation and desktop support, risk management framework activities for assessment and authorization, strategic communication support, program execution support, budget and financial management. ”
Responses to the sources sought notice are due April 23.
Bloomberg first reported DoD’s decision about the investigation and downselect.
In the meantime, the JEDI program’s road forward is far from smooth. In fact, DoD may have created more challenges for itself with its decision to complete the downselect before the court ruled on Oracle’s protest.
The potential conflict of interest was only one of seven parts of Oracle’s complaint. The downselect decision could potentially give Oracle better standing with the court given one of its complaints is that DoD’s criteria was problematic.
Oracle claims JEDI’s prerequisites have more to do with reducing the number of potential bidders than actual performance on the JEDI program, since the contract will use its own cybersecurity plan rather than FedRAMP. Another “gate criteria” Oracle criticizes as irrelevant is the requirement that the winning firm’s JEDI revenue not be larger than the commercial cloud business it had as of January 2018.
“The gate criteria served their improper purpose,” attorneys wrote. “When first announced, JEDI sparked intense interest in the contracting community: Hundreds of companies attended the industry day, and more than 60 companies submitted detailed RFI responses identifying extensive, sometimes unique capabilities. But following the issuance of the final RFP and its restrictive gate criteria, only four companies attended DoD’s in-person question and answer session and ultimately submitted proposals.”
DoD’s spokeswoman Smith said the internal investigation and protests have pushed back the timeline and now the Pentagon expects to award JEDI no sooner than mid-July.
“The two companies within the competitive range will participate further in the procurement process,” she said. “DoD remains committed to adopting the best enterprise cloud solution that fits its unique and critical needs. The scope and complexity of DoD’s mission requires multiple clouds from multiple vendors. JEDI is one element of DoD’s overall multi-cloud strategy and part of larger efforts to modernize information technology across the DoD enterprise.”