University offers investigation into Oracle finance disaster
theregister.com
theregister.com
The orgs themselves are not always blameless. ERP is expensive because the orgs are complex, and usually don’t understand themselves. The kind of end-to-end processes that ERP implements cross organizational boundaries, which is to say departments that don’t have good communication behaviors between themselves and therefore don’t fully understand why they do things. This is the seed of disaster for any project.
And then Oracle specifically make this difficult situation worse by having supremely opaque product documentation, names, versioning, licensing, and a constellation of internal support teams (which are no different to the client orgs in that they don’t communicate well with each other either).
All these big failures are fundamentally failures to communicate the right information throughout the project. Nobody is willing to do the hard yards of understanding and mapping out end-to-end processes and integration points, and fitting them to technology components. They all think they can shortcut the process by starting with the technology and working backwards from there, because that’s what Oracle sales told them they could do.
I’m not trying to excuse Oracle’s actions here, but ERP failure is normally a two-player game.
that's because the ERP has been sold as the solution to the domain complexity of the organization. It's been sold as a way to make your org's business processes work in "industry standard" ways, following "best practice", because the ERP vendor has "experience" with other orgs in similar businesses, which you can leverage the expertise/knowledge off. They'll customize the process a bit, to make it suite your "unique" circumstances.
Unfortunately, it's all hogwash.
https://oversight.house.gov/sites/democrats.oversight.house....
Gives me extra reason to dislike Oracle
[0] https://www.oracle.com/database/technologies/roracle-downloa...