{"id":112584,"date":"2020-05-07T21:28:48","date_gmt":"2020-05-07T21:28:48","guid":{"rendered":"https:\/\/news.microsoft.com\/?p=437499"},"modified":"2020-05-07T21:28:48","modified_gmt":"2020-05-07T21:28:48","slug":"bid-high-lose-try-again-amazon-continues-to-push-for-a-jedi-re-do","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2020\/05\/07\/bid-high-lose-try-again-amazon-continues-to-push-for-a-jedi-re-do\/","title":{"rendered":"Bid high, lose, try again. Amazon continues to push for a JEDI re-do"},"content":{"rendered":"
<\/div>\n

Many years ago when I was on active duty as a Marine officer in the 1980s, I went through cold weather training carrying a 1950s-era sleeping bag and \u201cwaterproof\u201d clothing from the 1970s. At the time, I could have gone down to the local store and bought gear that would have kept me warm and dry, but alas that wasn\u2019t yet in the USMC supply system. I was not happy about this. Also, I was cold and wet.<\/p>\n

So when it comes to making sure the U.S. Military has the latest and best technology available, I\u2019m a huge supporter, and the Department of Defense\u2019s (DoD) decision to source a Joint Enterprise Defense Infrastructure (JEDI) contract to deliver the latest advancements in enterprise cloud could be a great step forward. But only if Amazon gets out of the way.<\/p>\n

We received notice on Tuesday that Amazon has filed yet another protest \u2013 this time, out of view of the public and directly with the DoD \u2013 about their losing bid for the JEDI cloud contract. Amazon\u2019s complaint is confidential, so we don\u2019t know what it says. However, if their latest complaint mirrors the arguments Amazon made in court , it\u2019s likely yet another attempt to force a re-do because they bid high and lost the first time.<\/p>\n

The only thing that\u2019s certain about Amazon\u2019s new complaint is that it will force American warfighters to wait even longer for the 21st<\/sup>-century technology they need \u2013 perpetuating Amazon\u2019s record of putting its own interests ahead of theirs.<\/p>\n

This latest roadblock is disappointing but not surprising. As my colleague Jon Palmer made clear in a recent blog<\/a>, Amazon wants a do-over on JEDI . As Jon wrote, \u201cAmazon would have you believe that it lost the award because of bias at the highest levels of government. But Amazon, alone, is responsible for the pricing it offered. As the government explained in its brief: \u2018AWS and Microsoft each had a fair chance to build pricing for the entire procurement, based on their overall business pricing.\u2019 Amazon did build its pricing for the entire procurement, and it wasn\u2019t good enough to win.\u201d<\/p>\n

From the DoD\u2019s independent Inspector General\u2019s report, to the court\u2019s granting of a preliminary injunction, to refusing to even give the DoD a chance to address court\u2019s narrowly scoped concerns, you have to ask, \u201cWhen will enough be enough for Amazon? When will they say that they\u2019ve been heard?\u201d<\/p>\n

This latest filing \u2013 filed with the DoD this time \u2013 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. Think about it: Amazon spent the better part of last month fighting in court to prevent the DoD from taking a 120-day pause to address a concern flagged by the judge and reevaluate the bids. Amazon fought for a complete re-do and more delay. Amazon lost. The judge granted the DoD\u2019s request for a timeout in the litigation to address her concerns.<\/p>\n

And now Amazon is at it again, trying to grind this process to a halt, keeping vital technology from the men and women in uniform \u2013 the very people Amazon says it supports. Why do this? Is it because the DoD won\u2019t completely unwind the JEDI procurement process to the beginning? Again, we don\u2019t know the content of Amazon\u2019s complaint, as it avoids the public scrutiny of a court filing. But we do know that the changes DoD have made based on the judge\u2019s ruling do not allow Amazon to undo its earlier business decision to bid high, which resulted in their loss. It does not allow Amazon to completely re-do its pricing, especially now that it knows Microsoft\u2019s price and has a target to shoot at. And it does not allow Amazon to tilt the playing field in its favor.<\/p>\n

Amazon may make a lot of noise about bias and interference, but the DoD\u2019s independent Inspector General made it clear that the department established and followed a proper procurement process. And no one forced Amazon to bid high in the procurement. Amazon alone made the choice to bid high, but now wants to find a way to avoid the consequences of its own bad business decisions.<\/p>\n

At the end of the day, putting the customer first is a good business strategy and one where Amazon has traditionally excelled. In this case, I think about the customer not as a singular \u201cDoD\u201d but as the individual soldier, sailor, airman or Marine who wants and deserves the very best tools to do their job. And the best way Amazon can put these<\/em> customers first is to stand down on its litigation, stop asking for a do-over and let JEDI proceed.<\/p>\n

Tags: Amazon<\/a>, Defense<\/a>, JEDI<\/a>, Microsoft Azure<\/a>, military<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Many years ago when I was on active duty as a Marine officer in the 1980s, I went through cold weather training carrying a 1950s-era sleeping bag and \u201cwaterproof\u201d clothing from the 1970s. At the time, I could have gone down to the local store and bought gear that would have kept me warm and […]<\/p>\n","protected":false},"author":2,"featured_media":112585,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[49],"tags":[152,50],"class_list":["post-112584","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-news","tag-microsoft-on-the-issues","tag-recent-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/112584","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=112584"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/112584\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/112585"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=112584"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=112584"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=112584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}