Spending bill questions JEDI cloud acquisition strategy
As Congress moved forward with an omnibus spending bill, it added language that challenges DOD's approach to the massive JEDI cloud contract.
What a roller coaster the Defense Department’s massive cloud infrastructure initiative has been on.
When it was first out of the gate, most of the private sector cried foul because DOD was shaping the Joint Enterprise Defense Initiative to be a single-award contract that could have a value of $10 billion over 10 years.
Folks went to the media and they went to Capitol Hill with complaints that a single award wouldn’t give DOD the innovation they were looking for.
Then it seemed like DOD listened and the language coming from members of the Cloud Executive Steering Group seemed to soften. The parts of industry opposed to a single award were heartened. “Cooler heads prevailed,” one person told me at the time.
Then came the JEDI industry day and it looked like nothing had changed from DOD’s original plan. It would be a single award. A hybrid cloud with cloud infrastructure services from multiple providers just wouldn’t solve their problems, they said.
The draft RFP was out and final solicitation would come in early May. An award to a single provider would come by September.
But now there’s been a new twist in this ride.
On Wednesday night, the House Appropriations Committee released a $1.3 trillion "omnibus" spending bill for fiscal 2018. It must pass by Friday night for the government to remain open.
In a legislative report that accompanied the bill, Congress questions DOD’s JEDI strategy.
“There are concerns about the proposed duration of a single contract, questions about the best value for the taxpayer, and how to ensure the highest security is maintained,” the report states.
To address those concerns, Congress is asking for several things:
- A report to the defense committees within 60 days of the bill’s passage. The report should justify the single-award strategy. They also want to know all the parts of DOD that will use the contract and what the exit strategy will be.
- Within 45 days of passage, DOD needs to provide the RFP to the defense committees. They also need to provide the amounts request for 2018 and 2019 as well as future years.
- Other items Congress wants in their reports include standards, best practices, and contract types. It also wants information on data migration and middleware costs.
Congress is telling DOD to provide information on how it identifies and justifies acquisitions where other transaction authority is used.
They also want DOD to provide certification from the DOD Chief Information Officer, each military service, combatant command, DISA, and the CIO of each service that they have been consulted on the drafting of the RFP.
Congress is sending a clear signal to DOD -- prove a single award is the right strategy.
DOD has some work to do. Comments on the draft RFP were due March 21. As I said, the final RFP is supposed to come in early May and award by late September. That was a tough schedule to start with. It looks impossible now.
The report isn’t part of the 2,000-plus page omnibus bill that will fund the government for the rest of the year.
So the requests in the report aren’t technically part of the law. But a colleague who has more Hill experience than me said that the report has the force of an order from Congress.
“The people who put it in there will be angry [if DOD ignored the report] and you wouldn’t like to see appropriators when they’re angry,” he said.
NEXT STORY: How KeyW plans to break the $750M milestone