Slashdot Mirror
US Air Force Scraps ERP Project After $1 Billion Spent
angry tapir writes "The U.S. Air Force has decided to scrap a major ERP (enterprise resource planning) software project after spending $1 billion, concluding that finishing it would cost far too much more money for too little gain. Dubbed the Expeditionary Combat Support System (ECSS), the project has racked up $1.03 billion in costs since 2005, 'and has not yielded any significant military capability,' an Air Force spokesman said in a statement. 'We estimate it would require an additional $1.1B for about a quarter of the original scope to continue and fielding would not be until 2020. The Air Force has concluded the ECSS program is no longer a viable option for meeting the FY17 Financial Improvement and Audit Readiness (FIAR) statutory requirement. Therefore, we are canceling the program and moving forward with other options in order to meet both requirements.'"
I'd like to see them implement a CRM system instead
Never look back at the carnage.
Seems that this is a common theme with ERP rollouts-- scope creep tends to get them all in the end. Granted, most organizations seem to wave off long before the $1 billion mark...
I know lots of programmers who can get the same result for half the price.
From my observations, I've concluded that no organizational group works toward reducing its size, reducing the amount of its discretionary budget, or increasing its accountability for the preceding.
Any exceptions?
Those billions could have put a man on mars, or housed many,many homeless people, or any of a bunch of other uses. When will we realize that most of out debt is crime useless military spending, not social programs?
Silence is a state of mime.
Answered my own question:
http://www.youtube.com/watch?v=PVRgIXLWDHs
ERP is a bunch of disparate functions mashed together then held in place with a metric assload of duck tape. It's only natural that if you try to tacle the whole thing at once the result will be a sort of dynamic paralysis where you run back and forth in a nearly random pattern burning money all the way.
Just as well, if you ever manage to build the thing, you'll create paralysis across the entire company if you suddenly drop this chimera on people's desks.
Note, I am NOT claiming that the individual functions aren't necessary nor am I claiming that they shouldn't support common data formats.I am claiming that trying to build the whole thing at once and as a single 'solution' is wrong headed and doomed to failure.
Perfect application of Hanlon's Razor: Not so much a conspiracy to waste money as the worst combination of both world (defense acquisition and enterprise software development). Both fields are very prone to overruns, scope creep, and repeated waste of funds as manager after manager--or contractor after contractor--throws away work to start over again. Another great example is the FAA's version of enterprise software, which is currently at $63.4 BILLION and counting (though, to be fair, it's quite possible the most complicated software project in the world).
Still, there are worse examples--specifically, when these kinds of overruns, violations, and program restarts are done deliberately to ensure continued funding to entrenched players in a limited field and / or to pursue minor permutations on someone's pet dream of a project. This can occur at the cost of throwing away many years and billions of dollars of decent work while never really getting closer to a functioning system. Space Launch System, anyone? (Not a software example, but the line between software and aerospace engineering is a lot thinner than most people realize.)
If only they'd had a better ERP system, they could've planned this project more carefully, and put all those resources to better use.
Why would anyone engrave "Elbereth"?
Obama is in charge... the buck stops with him; he's the one who brags about his "kill list"... Oh, wait, this is Slashdot... Obama has a GREAT smile and a cool attitude and nobody is to blame for the drone strikes. Move along, nothing to see here. Dick Cheney is retired so there is no evil to be denounced.
I wouldn't be surprised that the DoD is encouraging this. In this way, each branch picks their own solution because they need to satisfy so many domestic "interests". (Yes, SAP America contributes to political campaigns and PACs, just like every other large ERP company in the US). Besides, the only reason that anyone has been successful is probably because they are sipping more Kool-Aid and sitting in a circle "reassuring" one another.
In what sense do you think ERP is dead? The functions are all required and if you buy best of breed individual packages, you still need to integrate them, so either you do it yourself or you buy the ERP package that is already integrated.
I agree that some decisions can be made to break it up into manageable pieces and accept less efficiency, but with an organization of that size you still have a problem of complexity whether using an ERP package or creating point solutions and integrating them.
ERP is dead because word is on the street: Too many failed or seriously delayed implementations.
I have seen (first hand) too many institutions decide to implement ERP, pay a tremendous amount of cash, and watch it fail. If it ever does get fully implemented (in a way that was originally envisioned) the institutions have spent so much time and effort to get it running that the institutions have lost their focus because senior management was distracted or the cost of full implementation has affected the bottom line. In some cases, the institution was irreparably damaged or failed.(often surpassed by their competition).
In theory, ERP is a wonderful thing. In actuality, it can kill.
Bullshit. I have been involved in dozens of ERP implementations over the years. The software works. When implementations fail it is always, in my experience, because of the people (i.e. management) making the decisions on how to implement the product.
Me: "Let me show you how Product X handles Accounts Payable"
Client: "That's not how we do it"
Me: "This might be a good opportunity to take a look at your current business practices and see if they can be done in a more efficient way"
Client: "But we've always done it this way"
Me: "Why?"
Client "Dunno...just always have. And I doubt that the team is willing to change"
Me: "Ok, we can customize the product to make it work the way you want but it's going to take more time and money. And when you do an upgrade later on there will be implications as well"
Client: "Fine. Just make it work the way we do it now"
And so it goes. Time and again I see clients go out and buy an expensive ERP system only to customize the bejezus out of it to make it look exactly like the systems they are retiring. They are not open to better business practices. Too many political headwinds.
What does this say about these clowns in the Air Force? It takes them 10 years and $1.03B to realize that the project is going to fail? On an original budget of $88M? One of the big problems with trying to shoehorn a best practice ERP system into a large government institution is that often they employ worst practices. They won't, or can't, change them so you have to end up rewriting the product to fit their ass backwards ways. The whole purpose of implementing an ERP system is to replace aging, stove-piped systems with modern integrated systems. It can work well if it's implemented properly and the right decisions are made along the way. But it's not a magic pill.
BING! BING! BING!
We have a winner. I am seeing this very poli-drama being played out right now at my institution. The multi-decade tenured staff will not change from business processes implemented to fit a bad system bought 3 decades ago; and will not listen because they don't have to.
Every mans' island needs an ocean; choose your ocean carefully.
While I hear what you're saying, government entities, and especially the military, are also subject to legal requirements that they not do things in certain ways, or have unique requirements not accounted for in a 'best practices' system.