March 25, 2020 | International, C4ISR
The Pentagon's request to reconsider narrow technical aspects of the award to Microsoft, Amazon argues, ignores a wide range of fundamental flaws.
By SYDNEY J. FREEDBERG JR.
WASHINGTON: Amazon Web Services has publicly denounced the Defense Department's latest legal maneuver in the months-long public battle over the JEDI cloud computing contract, awarded to Microsoft last year. No, Amazon said in a statement this morning, the Pentagon should not get to redo a particular piece of the award process the judge found flawed, because that was just one flaw among many and fixing it is a distraction from the larger issues.
“We're pleased to see the DoD recognize the need to take corrective action,” the Amazon statement began, “but we're concerned that the proposed approach is not designed to provide a complete, fair, and effective re-evaluation.”
“Both earlier in the adjudication process when we submitted 265 questions to the DoD that they refused to answer, and in our protest where we outlined numerous significant flaws in the evaluation, it's been clear that there were many problems with the DoD's initial decision,” the statement continues. “Instead of addressing the breadth of problems in its proposed corrective action, the DoD's proposal focuses only on providing Microsoft a ‘do-over' on its fatally flawed bid while preventing AWS from adjusting its own pricing in response to the DoD's new storage criteria.”
“This attempt to gerrymander the corrective action without fixing all of the serious flaws pointed out in our complaint raises significant questions,” the statement concludes.
The Pentagon's plan to consolidate many — but not all — of its 500-plus cloud contracts into a single Joint Enterprise Defense Infrastructure (JEDI). Note the suggestion that the single “pathfinder” contract for JEDI might evolve into multiple JEDI contracts.
An email circulated by Amazon went further: “DoD's proposed corrective action seeks to resurrect Microsoft's award eligibility and directly and unreasonably benefits Microsoft's deficient approach. DoD's proposed corrective action does not meaningfully address the numerous errors identified in AWS's protest. These errors were pervasive, impacting all six of the technical evaluation factors” — that is, not just the one the Pentagon is asking to redo.
“From the President's order to ‘screw' Amazon out of the contract, to the Secretary halting the award for an 85-day ‘examination,' to the Secretary's bizarre recusal after an award decision had been made, to the numerous inexplicable evaluation errors, to the refusal to substantively address AWS's 265 post-award debriefing questions, to the blatant political interference which impacted the award decision – the history of this procurement casts serious doubt on the rationality and fairness of DoD's proposed correction action,” the email said bluntly.
Some backstory might help in parsing all this. (Click here for more detail). On Feb. 13, the court had granted Amazon a preliminary injunction, saying the company would “likely” be able to prove the Department of Defense had erred in one particular portion of its process – an evaluation of the two companies called Price Scenario 6 – when it awarded the potentially $10 billion contract to Microsoft Azure. On March 12th, DoD responded by asking the judge to “remand” the case back to DoD so it could correct and redo Price Scenario 6, giving Microsoft and Amazon the opportunity to submit updated bids – albeit with very strict limits on those updates.
“During the proposed remand,” DoD's motion said, “the agency potentially could make decisions that would moot this action, in whole or in part, and may obviate the need for further litigation in this Court.”
In other words, the Pentagon is asking the judge: let us fix this one thing, and then there might be nothing left for Amazon to object to, and you can dismiss the case. Today, Amazon replied: We have plenty more to object to – and we think the judge will side with us.
https://breakingdefense.com/2020/03/amazon-denounces-dod-jedi-do-over
March 24, 2021 | International, Naval
Norway will block Rolls-Royce from selling a Norwegian maritime engine maker to a Russian company on national security grounds, its justice minister told parliament on Tuesday.
November 13, 2019 | International, Aerospace
By: Aaron Mehta and Valerie Insinna WASHINGTON — The U.S. Air Force expects to resolve a safety issue with the cargo capability of its KC-46A Pegasus tanker within “months,” the service's top acquisition official said Tuesday. Will Roper said he is “confident” the issue would get fixed and that the problem,— which has led the Air Force to stop the tankers from flying with cargo in their holds — was not his top concern for the Boeing-made plane. “The issue with the locks was identified. We're working options currently with Boeing and their supplier,” Roper said at a breakfast hosted by the Defense Writers Group. “We're looking to our operators to tell us which one of the solutions that have been identified is the one that they prefer." In September, Defense News first reported that the KC-46 was restricted from carrying either cargo or people in the back of the aircraft. The restriction was set after a recent flight where cargo locks on the bottom of the aircraft's floor became unlocked, creating concerns that airmen could be hurt or killed by heavy equipment that suddenly bursts free during a flight. It has been a rough year for the KC-46. The Air Force suspended KC-46 flights at Boeing's production line in Everett, Washington, this February after finding debris. Then it paused all tanker deliveries in March as the service investigated the extent of the problem. The service began accepting tankers again later that month, only for deliveries to stop — and restart — in April due to similar problems. The cargo issue represents the fourth category 1 deficiency for the tanker, and the issues are becoming increasingly expensive for Boeing: The company is locked into a fixed-price contract, which means it is responsible for paying for a expenses beyond the initial $4.9 billion award for development of the aircraft. So far, the company has paid more than $3.5 billion of its own money to fund corrections to ongoing technical issues. The other three issues are: The remote vision system, or RVS — the camera system that allows KC-46 boom operators to steer the boom into a receiver aircraft without having to look out a window and use visual cues — provides imagery in certain lighting conditions that appears warped or misleading. Boeing has agreed to pay for potentially extensive hardware and software fixes, but the Air Force believes it could be up to four years until the system is fully functional. The Air Force has recorded instances of the boom scraping against the airframe of receiver aircraft. Boeing and the Air Force believe this problem is a symptom of the RVS' acuity problems, and that the problem will be eliminated once the camera system is fixed. Boeing must redesign the boom to accommodate the A-10 plane, which currently does not generate the thrust necessary to push into the boom for refueling. This problem is a requirements change by the Air Force, which approved Boeing's design in 2016. Last month, Boeing received a $55.5 million contract to begin work on the new boom actuator. Roper said the cargo issue “goes into the kind of normal deficiency space” and noted that it's the type of issue that is discovered by the normal testing process. The more long-term issues, such as the remote visual system, are “the areas I keep the most focus on,” he said. https://www.defensenews.com/air/2019/11/12/kc-46-cargo-solution-still-months-away/
December 13, 2019 | International, C4ISR
Andrew Eversden There will be 14 early adopters of the Pentagon's controversial new enterprisewide general-purpose cloud, Defense Department CIO Dana Deasy said Dec. 12. Deasy, speaking at the AFCEA NOVA Air Force IT Day, said parties eyeing a move to the Joint Enterprise Defense Infrastructure (JEDI) cloud are U.S. Transportation Command, Special Operations Command, Joint Special Operations Command and the Navy. “What's really unique is the variety of the 14 early adopters allows us to test various principles on JEDI from the tactical edge all the way to the top secret — needing to use the cross-domain,” Deasy said. “So we're going to learn fairly quickly what it takes to actually now go from the strategic vision to the ability to stand it up and to bring it to life.” Federal Times asked the Department of Defense to provide the other 10 components among the first movers. A DoD spokesperson didn't immediately respond. Deasy reiterated what he told Defense News earlier in the week: that the unclassified JEDI environment will be ready in February, with the “secret” environment ready six months after that. There is also no specific timeline for the top-secret environment. He said that there are meetings every two weeks where the JEDI team discusses the “60 to 70 services” that must be ready to go when the unclassified environment kicks off. DoD awarded the JEDI contract to Microsoft over Amazon Web Services, which recently filed a protest in the U.S. Court of Federal Claims that relied heavily on interference allegations against President Donald Trump. The contract is potentially worth $10 billion over 10 years. Throughout the entirety of the JEDI procurement, DoD has struggled to dispel the notion that the Pentagon's only cloud would be JEDI, when in reality the JEDI cloud is just one in a multicloud environment. Deasy took aim at that characterization in his address, highlighting that there are “something like” 10 more cloud contracts out for bids next year. “The whole reason we started JEDI was we were not short on clouds,” Deasy said. “What we were short of was an enterprise capability ... all the way out to the tactical edge. ... There will always be a need for special-purpose clouds." Once the JEDI cloud is set up, Deasy said, the next step is to look across the department at the various siloed cloud and ask “do they serve a unique purpose that is truly distinctly different than JEDI? Or is there overlap?” The Pentagon has signaled that it will move 80 percent of its systems to the JEDI cloud. Consolidation is an option for overlapping clouds, but Deasy said the DoD won't know what to do specifically with the overlaps until the JEDI cloud is stood up. The JEDI cloud environment will allow the DoD to significantly reduce the number of clouds it has, which the Congressional Research Services has estimated sits at more than 500. With the JEDI cloud, Deasy's ready to reduce that number by hundreds. At the end of the day, “we sure in the heck don't need 100 clouds, we probably don't need 50 clouds, but we definitely need more than one or two clouds,” Deasy said. https://www.federaltimes.com/it-networks/cloud/2019/12/12/here-are-some-early-adopters-of-the-controversial-jedi-cloud/