Oracle ERP projects have longest unexpected delays

The survey released by Panorama Consulting in the US, has found nearly two thirds of respondents said their projects involving Oracle, SAP and Microsoft Dynamics software went over schedule.

Panorama's survey found that nearly a third of respondents had yet to realise any financial rewards from their projects, and another 30 percent said it took at least three years to start seeing full ROI.

The survey based on 2,000 responses from 61 countries collected between February 2006 and May of this year, found 28 per cent finished on time and 11 per cent completed the project sooner than expected.

The actual ERP software being used was largely not to blame for problem projects, according to the survey data.

Just 4 per cent of respondents cited vendor functionality issues as a reason for project delays, although technical issues drew 14 percent.

The company said it is "distressingly common" to see ERP (enterprise resource planning) projects running so late.

Related:

A change in the project's initial scope was the top reason for slowdowns, named by 29 per cent of survey respondents. A fifth of respondents cited organisational issues, followed by data issues and resource constraints, both with 17 per cent.

Dynamics led the pack in terms of overall implementation times, averaging 13 months to SAP's 17 months and Oracle's 18 months, according to the survey.

These results should be viewed with some caution, since Dynamics tends to be implemented by smaller companies with less complex environments.

SAP and Dynamics projects ran on average two months past schedule, while Oracle implementations averaged four-month overruns, according to the survey.

Sometimes, ERP projects go so poorly that customers end up suing their vendor, as well as vice versa.

Oracle, for one, is currently embroiled in a high-profile dispute with Montclair State University. Epicor was also the target of a number of recent actions.