Hacker News Reader

Comment by tssva | Hacker News Reader

The options aren't just give $10B to AWS, Oracle, IBM or Microsoft. The JEDI should have been a multi-award IDIQ (indefinite delivery indefinite quantity) contract. With a multi-award IDIQ the each task order issued under the IDIQ is competed for among the multiple vendors the IDIQ has been awarded to. It is actually fairly unusual that this type of IT services contract was not done as a multi-award IDIQ.

Having to compete for each task order is thought to reduce costs to the government. Of course having to compete each task brings its own additional costs which don't necessarily make the cost saving proposition true. The big benefit I see to this contract is that it helps prevent vendor lock-in. I don't worry about the next 10 years and $10B, but what happens after 10 years when the DoD is now locked in to proprietary AWS cloud features which make migrating to a different vendor technically and fiscally near impossible.

View on HN

You should not do infrastructure as IDIQ, this is an infrastructure contract. The idea that all contracts issued by IT are for "IT Services" is part of the reason digital systems at the DOD and other government agencies are such a nightmare. HAving a single system to build off of is the best way to do it, and not having that system be a customer solution for just the government is way better then not.

Lock in is the only concern, but from my experience doing an IDIQ or multi-vendor won't solve the lock in problem. The best thing to solve that is to make sure your using bland normal things not customer government thigs.

You know, I've been in some data centers and top 50 HPC clusters ... I don't understand why the US government doesn't run it's own cloud systems, except for the appropriations. There are enough computer scientists in the larger org to field a major distributed systems engineering group.

>I don't understand why the US government doesn't run it's own cloud systems, except for the appropriations.

Inability to pay high enough salaries for anyone to maintain it properly AND move it forward with new tech.

Here’s the civilian pay scale – think of how it compares with AWS or Google:

https://www.opm.gov/policy-data-oversight/pay-leave/salaries...

Now, think of the political climate: there’ve been decades trying to “trim waste” by steering money to the private sector, where efficiency is taken as a matter of faith. First you’d need to hire the technical leadership to properly plan something like that and then hire all of the people who’d build it, not to mention procuring all of the hardware & data centers, etc. You’re looking at years before you have a positive return on any of that – and all the while, every big contractor is going to have their lobbyists talking about how it’s a waste of money compared to going with them.

NASA tried this a decade ago with Nebula, which was part of the early OpenStack history. I don’t know exactly what happened with that but the people I know working on NASA projects are all using AWS.

I'm glad you mentioned the caveats with IDIQ contracts. I would say that the IDIQ process rarely, if ever, results in savings. (In fact, if you have some examples where it did I know some people who would be interested in studying those cases.)

The history of IDIQ processes is likely a large part of the reason people were anxious to do something different in this instance. Now that it's all politics, it'll probably cost more and function less when all is said and done.

Some aspects of the military, I don't really miss.

I’ve done IDIQ contracts in state government. You can absolutely save money, but you need to force a limited list of SKUs and renegotiate pricing at different volume-based high water marks.

Winner take all is also important, because it eliminates the room for sales bullshit. The magic is figuring out how to break up the lots of services so that it makes sense. You don’t want to give any one of AWS, Google and Microsoft everything, so you want to design lots that keep it competitive. This also ensures that any one vendor doesn’t subsidize strategic SKUs by discounting something that isn’t meaningful.

Everything fed is more complex, but it’s all doable.

What’s your theory on the justification DoD is giving to go single-award IDIQ?

I doubt their actual justification will ever be public, but I suspect their motivation is that they require a common IaaS platform such that they can have a unified toolset and a single, comprehensive approach to infrastructure security.

Keep in mind also that fewer proprietary features at AWS are available when considering standardizing across all classification types. “East/west” and GovCloud don’t have feature parity.

Reply on news.ycombinator.com