Sep
08
2020
--

The $10B JEDI contract is locked, loaded and still completely stuck

The other day I took a moment to count the number of stories we’ve done on TechCrunch on the DoD’s $10 billion, decade-long, winner-take-all, JEDI cloud contract. This marks the 30th time we’ve written about this deal over the last two years, and it comes after a busy week last week in JEDI cloud contract news.

That we’re still writing about this is fairly odd if you consider the winner was announced last October when the DoD chose Microsoft, but there is no end in sight to the on-going drama that is this procurement process.

Government contracts don’t typically catch our attention at TechCrunch, but this one felt different early on. There was the size and scope of the deal of course. There was the cute play on the “Star Wars” theme. There was Oracle acting like a batter complaining to the umpire before the first pitch was thrown. There was the fact that everyone thought Amazon would win until it didn’t.

There was a lot going on. In fact, there’s still a lot going on with this story.

Oracle doth protest too much

Let’s start with Oracle, which dispatched CEO Safra Catz to the White House in April 2018 even before the RFP had been written. She was setting the stage to complain that the deal was going to be set up to favor Amazon, something that Oracle alleged until the day Microsoft was picked the winner.

Catz had been on the Trump transition team and so had the ear of the president. While the president certainly interjected himself in this process, it’s not known how much influence that particular meeting might have had. Suffice to say that it was only the first volley in Oracle’s long war against the JEDI contract procurement process.

It would include official complaints with the Government Accountability Office and a federal lawsuit worth not coincidentally $10 billion. It would claim the contract favored Amazon. It would argue that the one-vendor approach wasn’t proper. It would suggest that because the DoD had some former Amazon employees helping write the RFP, that it somehow favored Amazon. The GAO and two court cases found otherwise, ruling against Oracle every single time.

It’s worth noting that the Court of Appeals ruling last week indicated that Oracle didn’t even meet some of the basic contractual requirements, all the while complaining about the process itself from the start.

Amazon continues to press protests

Nobody was more surprised that Amazon lost the deal than Amazon itself. It still believes to this day that it is technically superior to Microsoft and that it can offer the DoD the best approach. The DoD doesn’t agree. On Friday, it reaffirmed its choice of Microsoft. But that is not the end of this, not by a long shot.

Amazon has maintained since the decision was made last October that the decision-making process had been tainted by presidential interference in the process. They believe that because of the president’s personal dislike of Amazon CEO Jeff Bezos, who also owns the Washington Post, he inserted himself in the process to prevent Bezos’ company from winning that deal.

In January, Amazon filed a motion to stop work on the project until this could all be sorted out. In February, a judge halted work on the project until Amazon’s complaints could be heard by the court. It is September and that order is still in place.

In a blog post on Friday, Amazon reiterated its case, which is based on presidential interference and what it believes is technical superiority. “In February, the Court of Federal Claims stopped performance on JEDI. The Court determined AWS’s protest had merit, and that Microsoft’s proposal likely failed to meet a key solicitation requirement and was likely deficient and ineligible for award. Our protest detailed how pervasive these errors were (impacting all six technical evaluation factors), and the Judge stopped the DoD from moving forward because the very first issue she reviewed demonstrated serious flaws,” Amazon wrote in the post.

Microsoft for the win?

Microsoft on the other hand went quietly about its business throughout this process. It announced Azure Stack, a kind of portable cloud that would work well as a field operations computer system. It beefed up its government security credentials.

Even though Microsoft didn’t agree with the one-vendor approach, indicating that the government would benefit more from the multivendor approach many of its customers were taking, it made clear if those were the rules, it was in it to win it — and win it did, much to the surprise of everyone, especially Amazon.

Yet here we are, almost a year later and in spite of the fact that the DoD found once again, after further review, that Microsoft is still the winner, the contract remains in limbo. Until that pending court case is resolved, we will continue to watch and wait and wonder if this will ever be truly over, and the JEDI cloud contract will actually be implemented.

Sep
04
2020
--

DoD reaffirms Microsoft has won JEDI cloud contract, but Amazon legal complaints still pending

We have seen a lot of action this week as the DoD tries to finally determine the final winner of the $10 billion, decade-long DoD JEDI cloud contract. Today, the DoD released a statement that after reviewing the proposals from finalists Microsoft and Amazon again, it reiterated that Microsoft was the winner of the contract.

“The Department has completed its comprehensive re-evaluation of the JEDI Cloud proposals and determined that Microsoft’s proposal continues to represent the best value to the Government. The JEDI Cloud contract is a firm-fixed-price, indefinite-delivery/indefinite-quantity contract that will make a full range of cloud computing services available to the DoD,” the DoD said in a statement.

This comes on the heels of yesterday’s Court of Appeals decision denying Oracle’s argument that the procurement process was flawed and that there was a conflict of interest because a former Amazon employee helped write the requirements for the RFP.

While the DoD has determined that it believes that Microsoft should still get the contract, after selecting them last October, that doesn’t mean this is the end of the line for this long-running saga. In fact, a federal judge halted work on the project in February pending a hearing on an ongoing protest from Amazon, which believes it should have won based on merit, and the fact it believes the president interfered with the procurement process to prevent Jeff Bezos, who owns The Washington Post, from getting the lucrative contract.

The DoD confirmed that the project could not begin until the legal wrangling was settled. “While contract performance will not begin immediately due to the Preliminary Injunction Order issued by the Court of Federal Claims on February 13, 2020, DoD is eager to begin delivering this capability to our men and women in uniform,” the DoD reported in a statement.

A Microsoft spokesperson said the company was ready to get to work on the project as soon as it got the OK to proceed. “We appreciate that after careful review, the DoD confirmed that we offered the right technology and the best value. We’re ready to get to work and make sure that those who serve our country have access to this much needed technology,” a Microsoft spokesperson told TechCrunch.

Meanwhile, in a blog post published late this afternoon, Amazon made it clear that it was unhappy with today’s outcome and will continue to pursue legal remedy for what they believe to be presidential interference that has threatened the integrity of the procurement process. Here’s how they concluded the blog post:

We strongly disagree with the DoD’s flawed evaluation and believe it’s critical for our country that the government and its elected leaders administer procurements objectively and in a manner that is free from political influence. The question we continue to ask ourselves is whether the President of the United States should be allowed to use the budget of the Department of Defense to pursue his own personal and political ends? Throughout our protest, we’ve been clear that we won’t allow blatant political interference, or inferior technology, to become an acceptable standard. Although these are not easy decisions to make, and we do not take them lightly, we will not back down in the face of targeted political cronyism or illusory corrective actions, and we will continue pursuing a fair, objective, and impartial review.

While today’s statement from DoD appears to take us one step closer to the end of the road for this long-running drama, it won’t be over until the court rules on Amazon’s arguments. It’s clear from today’s blog post that Amazon has no intention of stepping down.

Note: We have  updated this story with content from an Amazon blog post responding to this news.

Sep
03
2020
--

Oracle loses $10B JEDI cloud contract appeal yet again

Oracle was never fond of the JEDI cloud contract process, that massive $10 billion, decade-long Department of Defense cloud contract that went to a single vendor. It was forever arguing to anyone who would listen that that process was faulty and favored Amazon.

Yesterday it lost another round in court when the U.S. Court of Appeals rejected the database giant’s argument that the procurement process was flawed because it went to a single vendor. It also didn’t buy that there was a conflict of interest because a former Amazon employee was involved in writing the DoD’s request for proposal criteria.

On the latter point, the court wrote, “The court addressed the question whether the contracting officer had properly assessed the impact of the conflicts on the procurement and found that she had.”

Further, the court found that Oracle’s case didn’t have merit in some cases because it failed to meet certain basic contractual criteria. In other cases, it didn’t find that the DoD violated any specific procurement rules with this bidding process.

This represents the third time the company has tried to appeal the process in some way, four if you include direct executive intervention with the president. In fact, even before the RFP had been released in April 2018, CEO Safra Catz brought complaints to the president that the bid favored Amazon.

In November 2018, the Government Accountability Office (GAO) denied Oracle’s protest that it favored Amazon or any of the other points in their complaint. The following month, the company filed a $10 billion lawsuit in federal court, which was denied last August. Yesterday’s ruling is on the appeal of that decision.

It’s worth noting that for all its complaints that the deal favored Amazon, Microsoft actually won the bid. Even with that determination, the deal remains tied up in litigation as Amazon has filed multiple complaints, alleging that the president interfered with the deal and that they should have won on merit.

As with all things related to this contract, the drama has never stopped.

May
08
2020
--

Microsoft and AWS exchange poisoned pen blog posts in latest Pentagon JEDI contract spat

Microsoft and Amazon are at it again as the fight for the Defense Department JEDI contract continues. In a recent series of increasingly acerbic pronouncements, the two companies continue their ongoing spat over the $10 billion, decade-long JEDI contract spoils.

As you may recall (or not), last fall in a surprise move, the DoD selected Microsoft as the winning vendor in the JEDI winner-take-all cloud infrastructure sweepstakes. The presumed winner was always AWS, but when the answer finally came down, it was not them.

To make a very long story short, AWS took exception to the decision and went to court to fight it. Later it was granted a stay of JEDI activities between Microsoft and the DoD, which as you can imagine did not please Microsoft . Since then, the two companies have been battling in PR pronouncements and blog posts trying to get the upper hand in the war for public opinion.

That fight took a hard turn this week when the two companies really went at it in dueling blog posts after Amazon filed its latest protest.

First there was Microsoft with PR exec Frank Shaw taking exception to AWS’s machinations, claiming the company just wants a do-over:

This latest filing – filed with the DoD this time – is another example of Amazon trying to bog down JEDI in complaints, litigation and other delays designed to force a do-over to rescue its failed bid.

Amazon’s Drew Herdner countered in a blog post published this morning:

Recently, Microsoft has published multiple self-righteous and pontificating blog posts that amount to nothing more than misleading noise intended to distract those following the protest.

The bottom line is that Microsoft believes it won the contract fair and square with a more competitive bid, while Amazon believes it should have won on technical superiority, and that there was political interference from the president because he doesn’t like Amazon CEO Jeff Bezos, who also owns the Washington Post.

If you’ve been following this story from the beginning (as I have), you know it has taken a series of twists and turns. It’s had lawsuits, complaints, drama and intrigue. The president has inserted himself into it, too. There have been accusations of conflicts of interest. There have been investigations, lawsuits and more investigations.

Government procurement tends to be pretty bland, but from the start when the DoD chose to use the cutesy Star Wars-driven acronym for this project, it has been anything but. Now it’s come down to two of the world’s largest tech companies exchanging angry blog posts. Sooner or later this is going to end right?

Apr
15
2020
--

DoD Inspector General report finds everything was basically hunky-dory with JEDI cloud contract bid

While controversy has dogged the $10 billion, decade-long JEDI contract since its earliest days, a report by the DoD’s Inspector General’s Office concluded today that, while there were some funky bits and potential conflicts, overall the contract procurement process was fair and legal and  the president did not unduly influence the process in spite of public comments.

There were a number of issues along the way about whether the single contractor award was fair or reasonable, about whether there were was White House influence on the decision, and whether the president wanted to prevent Amazon founder Jeff Bezos, who also owns the Washington Post, from getting the contract.

There were questions about whether certain personnel, who had been or were about to be Amazon employees, had undue influence on the contents of the RFP or if former Secretary of Defense showed favor to Amazon, which ultimately did not even win the contract, and that one of Mattis’ under secretaries, in fact, owned stock in Microsoft .

It’s worth noting that the report states clearly that it is not looking at the merits of this contract award or whether the correct company won on technical acumen. It was looking at all of these controversial parts that came up throughout the process. As the report stated:

“In this report, we do not draw a conclusion regarding whether the DoD appropriately awarded the JEDI Cloud contract to Microsoft rather than Amazon Web Services. We did not assess the merits of the contractors’ proposals or DoD’s technical or price evaluations; rather we reviewed the source selection process and determined that it was in compliance with applicable statutes, policies, and the evaluation process described in the Request for Proposals.”

Although the report indicates that the White House would not cooperate with the investigation into potential bias, the investigators claim they had enough discussions with parties involved with the decision to conclude that there was no undue influence on the White House’s part:

“However, we believe the evidence we received showed that the DoD personnel who evaluated the contract proposals and awarded Microsoft the JEDI Cloud contract were not pressured regarding their decision on the award of the contract by any DoD leaders more senior to them, who may have communicated with the White House,” the report stated.

The report chose to blame the media instead, at least for partly giving the impression that the White House had influenced the process, stating:

“Yet, these media reports, and the reports of President Trump’s statements about Amazon, ongoing bid protests and “lobbying” by JEDI Cloud competitors, as well as inaccurate media reports about the JEDI Cloud procurement process, may have created the appearance or perception that the contract award process was not fair or unbiased.”

It’s worth noting that we reported that AWS president Andy Jassy made it clear in a press conference at AWS re:Invent in December that the company believed the president’s words had influenced the process.

“I think that we ended up with a situation where there was political interference. When you have a sitting president, who has shared openly his disdain for a company, and the leader of that company, it makes it really difficult for government agencies, including the DoD, to make objective decisions without fear of reprisal.”

As for other points of controversy, such as those previously referenced biases, all were found lacking by the Inspector General. While the earliest complaints from Oracle and others were that Deap Ubhi and Victor Gavin, two individuals involved in drafting the RFP, failed to disclose they were offered jobs by Amazon during that time.

The report concluded that while Ubhi violated ethics rules, his involvement wasn’t substantial enough to influence the RFP (which again, Amazon didn’t win). “However, we concluded that Mr. Ubhi’s brief early involvement in the JEDI Cloud Initiative was not substantial and did not provide any advantage to his prospective employer, Amazon…,” the report stated.

The report found Gavin did not violate any ethics rules in spite of taking a job with Amazon because he had disqualified himself from the process, nor did the report find that former Secretary Mattis had any ethical violations in its investigation.

One final note: Stacy Cummings, Principal Deputy Assistant Secretary of Defense for Acquisition and Deputy Assistant Secretary of Defense for Acquisition Enablers, who worked for Mattis, owned some stock in Microsoft and did not disclose this. While the report found that was a violation of ethics guidelines, it ultimately concluded this did not unduly influence the award to Microsoft.

While the report is a substantial, 313 pages, it basically concludes that as far as the purview of the Inspector General is concerned, the process was basically conducted in a fair way. The court case, however involving Amazon’s protest of the award to Microsoft continues. And the project remains on hold until that is concluded.

Note: Microsoft and Amazon did not respond to requests from TechCrunch for comments before we published this article. If that changes, we will update accordingly.

Report on the Joint Enterprise Defense Infrastructure (Jedi) Cloud Procurement Dodig-2020-079 by TechCrunch on Scribd

Mar
13
2020
--

Pentagon asks court for time to reconsider JEDI award to Microsoft

The JEDI contract award process might never be done. Following legal challenges from Amazon after the Pentagon’s massive, $10 billion cloud contract was awarded to Microsoft in October, the Pentagon indicated in court documents last night that it wishes to reconsider the award.

It’s just the latest plot twist in an epic government procurement saga.

Here’s what we know. The Pentagon filing is based on Amazon’s complaints about the technical part of the deal only. Amazon has said that it believes political interference influenced the awarding of the contract. However, the cloud computing giant also believes it beat Microsoft on the technical merits in a majority of instances required in the request for proposals issued by the Pentagon.

In fact, sources told TechCrunch, “AWS’s protest identified evaluation errors, clear deficiencies and unmistakable bias in six of the eight evaluation factors.”

Obviously Amazon was happy to hear this news. “We are pleased that the DoD has acknowledged ‘substantial and legitimate’ issues that affected the JEDI award decision, and that corrective action is necessary,” a spokesperson stated.

“We look forward to complete, fair, and effective corrective action that fully insulates the re-evaluation from political influence and corrects the many issues affecting the initial flawed award.”

As would expect, Microsoft thinks that the DoD made the correct choice, and believes the review will bear that out. “Over two years, the DoD reviewed dozens of factors and sub factors and found Microsoft equal or superior to AWS on every factor. We remain confident that Microsoft’s proposal was technologically superior, continues to offer the best value, and is the right choice for the DoD,” Microsoft VP of communications Frank Shaw said.

The court granted the Pentagon 120 days to review the results again, but indicated it could take longer. In the meantime, the project is at a standstill.

On Friday, the court issued a ruling that Amazon was likely to succeed on its complaint on merit, and that could have been the impetus of this latest action by the Pentagon.

While the political influence piece might not be overtly part of this filing, it does lurk in the background. The president has made it clear that he doesn’t like Amazon founder and CEO Jeff Bezos, who also owns The Washington Post. As we wrote last year:

Amazon, for instance, could point to Jim Mattis’ book where he wrote that the president told the then Defense Secretary to “screw Bezos out of that $10 billion contract.” Mattis says he refused, saying he would go by the book, but it certainly leaves the door open to a conflict question.

As we previously reported, AWS CEO Andy Jassy stated at a press event at AWS re:Invent in December that the company believed there was political bias at play in the decision-making process.

“What I would say is that it’s fairly obvious that we feel pretty strongly that it was not adjudicated fairly,” he said. He added, “I think that we ended up with a situation where there was political interference. When you have a sitting president, who has shared openly his disdain for a company, and the leader of that company, it makes it really difficult for government agencies, including the DoD, to make objective decisions without fear of reprisal.”

The story has been updated with a comment from Microsoft. We have requested comment from DoD and will update the story should they respond.

Feb
13
2020
--

Judge temporarily halts work on JEDI contract until court can hear AWS protest

A sealed order from a judge today has halted the $10 billion, decade-long JEDI project in its tracks until AWS’s protest of the contract award to Microsoft can be heard by the court.

The order signed by Judge Patricia E. Campbell-Smith of the U.S. Court Federal Claims stated:

The United States, by and through the Department of Defense, its officers, agents, and employees, is hereby PRELIMINARILY ENJOINED from proceeding with contract activities under Contract No. HQ0034-20-D-0001, which was awarded under Solicitation No. HQ0034-18-R-0077, until further order of the court.

The judge was not taking this lightly, adding that Amazon would have to put up $42 million bond to cover costs should it prove that the motion was filed wrongfully. Given Amazon’s value as of today is $1.08 trillion, they can probably afford to put up the money, but they must provide it by February 20th, and the court gets to hold the funds until a final determination has been made.

At the end of last month, Amazon filed a motion to stop work on the project until the court could rule on its protest. It is worth noting that in protests of this sort, it is not unusual to stop work until a final decision on the award can be made.

This is all part of an ongoing drama that has gone on for a couple of years since the DoD put this out to bid. After much wrangling, the DoD awarded the contract to Microsoft at the end of October. Amazon filed suit in November, claiming that the president had unduly influenced the process.

As we reported in December, at a press conference at AWS re:Invent, the cloud arm’s annual customer conference, AWS CEO Andy Jassy made clear the company thought the president had unfairly influenced the procurement process:

“I would say is that it’s fairly obvious that we feel pretty strongly that it was not adjudicated fairly,” he said. He added, “I think that we ended up with a situation where there was political interference. When you have a sitting president, who has shared openly his disdain for a company, and the leader of that company, it makes it really difficult for government agencies, including the DoD, to make objective decisions without fear of reprisal.”

Earlier this week, the company filed paperwork to depose the president and Secretary of Defense Mark Esper.

The entire statement from the court today halting the JEDI project:

**SEALED**OPINION AND ORDER granting [130] Motion for Preliminary Injunction, filed by plaintiff. The United States, by and through the Department of Defense, its officers, agents, and employees, is hereby PRELIMINARILY ENJOINED from proceeding with contract activities under Contract No. HQ0034-20-D-0001, which was awarded under Solicitation No. HQ0034-18-R-0077, until further order of the court.

Pursuant to RCFC 65(c), plaintiff is directed to PROVIDE security in the amount of $42 million for the payment of such costs and damages as may be incurred or suffered in the event that future proceedings prove that this injunction was issued wrongfully.

As such, on or before 2/20/2020, plaintiff is directed to FILE a notice of filing on the docket in this matter indicating the form of security obtained, and plaintiff shall PROVIDE the original certification of security to the clerk of court. The clerk shall HOLD the security until this case is closed.

On or before 2/27/2020, the parties are directed to CONFER and FILE a notice of filing attaching a proposed redacted version of this opinion, with any competition-sensitive or otherwise protectable information blacked out. Signed by Judge Patricia E. Campbell-Smith.

Feb
10
2020
--

Amazon wants to depose president and secretary of Defense as part of JEDI protest

Today, AWS made public its Motion to Supplement the Record in its protest of the JEDI contract decision. As part of that process, the company has announced it wants to depose President Trump and Secretary of Defense Mark Esper.

When Amazon announced at the end of last year that it was protesting the DoD’s decision to award the $10 billion, decade-long JEDI contract to Microsoft, the company made clear that it was not happy with the decision. The company believes that the president steered the contract away from Amazon because of personal political differences with Amazon CEO Jeff Bezos, who also owns The Washington Post.

“President Trump has repeatedly demonstrated his willingness to use his position as President and Commander in Chief to interfere with government functions – including federal procurements – to advance his personal agenda. The preservation of public confidence in the nation’s procurement process requires discovery and supplementation of the administrative record, particularly in light of President Trump’s order to ‘screw Amazon.’ The question is whether the President of the United States should be allowed to use the budget of the DoD to pursue his own personal and political ends,” an AWS spokesperson said in a statement.

This is consistent with public statements the company has been making since the DoD made the surprise decision in October to go with Microsoft. It had been widely believed that Amazon would win the contract, and there was much wrangling and complaining throughout the procurement process that the contract had been designed to favor Amazon, something that the DoD repeatedly denied.

At AWS re:Invent at the end last year, AWS CEO Andy Jassy made it clear he was unhappy with the decision and that he believed the president showed bias. “I think that we ended up with a situation where there was political interference. When you have a sitting president, who has shared openly his disdain for a company, and the leader of that company, it makes it really difficult for government agencies, including the DoD, to make objective decisions without fear of reprisal,” Jassy said last year.

Sources say that the DoD gave Amazon a written debriefing after the decision to award the contract to Microsoft, but the company is particularly upset that the department has failed to respond in a timely fashion to requests for additional information and questions, as required by law.

Jan
23
2020
--

In latest JEDI contract drama, AWS files motion to stop work on project

When the Department of Defense finally made a decision in October on the decade-long, $10 billion JEDI cloud contract, it seemed that Microsoft had won. But nothing has been simple about this deal from the earliest days, so it shouldn’t come as a surprise that last night Amazon filed a motion to stop work on the project until the court decides on its protest of the DoD’s decision.

The company announced on November 22nd that it had filed suit in the U.S. Court of Federal Claims protesting the DoD’s decision to select Microsoft. Last night’s motion is an extension of that move to put the project on hold until the court decides on the merits of the case.

Sources tell us that AWS decided not protest the start of initial JEDI activities at the time of the court filing in November as an accommodation made at DoD’s request. DoD declined to comment on that.

As for why they are doing it now, an Amazon spokesperson had this to say in a statement last night: “It is common practice to stay contract performance while a protest is pending and it’s important that the numerous evaluation errors and blatant political interference that impacted the JEDI award decision be reviewed. AWS is absolutely committed to supporting the DoD’s modernization efforts and to an expeditious legal process that resolves this matter as quickly as possible.”

As we previously reported, the statement echoes sentiments AWS CEO Andy Jassy made at a press event during AWS re:Invent in December:

“I would say is that it’s fairly obvious that we feel pretty strongly that it was not adjudicated fairly,” he said. He added, “I think that we ended up with a situation where there was political interference. When you have a sitting president, who has shared openly his disdain for a company, and the leader of that company, it makes it really difficult for government agencies, including the DoD, to make objective decisions without fear of reprisal.”

This is just the latest turn in a contract procurement process for the ages. It will now be up to the court to decide if the project should stop or not, and beyond that if the decision process was carried out fairly.

Nov
14
2019
--

AWS confirms reports it will challenge JEDI contract award to Microsoft

Surely just about everyone was surprised when the Department of Defense last month named Microsoft as the winner of the decade-long, $10 billion JEDI cloud contract — none more so than Amazon, the company everyone assumed all along would be the winner. Today the company confirmed earlier reports that it was challenging the contract award in the Court of Federal Claims.

The Federal Times broke this story.

In a statement, an Amazon spokesperson suggested that there was possible bias and issues in the selection process. “AWS is uniquely experienced and qualified to provide the critical technology the U.S. military needs, and remains committed to supporting the DoD’s modernization efforts. We also believe it’s critical for our country that the government and its elected leaders administer procurements objectively and in a manner that is free from political influence.

“Numerous aspects of the JEDI evaluation process contained clear deficiencies, errors, and unmistakable bias — and it’s important that these matters be examined and rectified,” an Amazon spokesperson told TechCrunch.

It’s certainly worth noting that the president has not hidden his disdain for Amazon CEO and founder Jeff Bezos, who also is owner of The Washington Post newspaper. As I wrote in Even after Microsoft wins, JEDI saga could drag on:

Amazon, for instance, could point to Jim Mattis’ book where he wrote that the president told the then Defense Secretary to “screw Bezos out of that $10 billion contract.” Mattis says he refused, saying he would go by the book, but it certainly leaves the door open to a conflict question.

Oracle also filed a number of protests throughout the process, including one with the Government Accountability Office that was later rejected. It also went to court and the case was dismissed. All of the protests claimed that the process favored Amazon. The end result proved it didn’t.

The president interjected himself in the decision process in August, asking the defense secretary, Mark T. Esper, to investigate once again if the procurement process somehow favored Amazon, and the week the contract was awarded, the White House canceled its subscription to The Washington Post.

In October, the decision finally came and the DOD chose Microsoft . Now Amazon is filing a challenge in federal Court, and the JEDI saga really ain’t over until it’s over.

 

Powered by WordPress | Theme: Aeros 2.0 by TheBuckmaker.com