June 13, 2012 By News Staff
A new study has shown that 58 percent of public finance officers have been or expect to be disappointed with their organizations’ enterprise resource planning (ERP) systems. Discontent about large-scale projects isn’t surprising, but those who have had some success revealed a number of best practices to better handle the process.
Conducted jointly by Microsoft and GFOA Consulting, the research arm of the Government Finance Officers Association, the survey collected responses from 268 members of the organization. Those respondents who had modern ERP systems offered these tips to achieve successful ERP implementations:
The study, titled The Real Impact of ERP Systems in the Public Sector, had a number of other keys to ERP implementation success. Some of the recommendations included staying flexible, setting appropriate expectations, partnering inside and outside the organization and keeping employee staffing levels high during the project.
“For too long, public-sector organizations have had to rely on inflexible ERP systems that hinder their ability to support transparency, open government, compliance and fiscal accountability requirements,” said Charlie Johnson, Microsoft Dynamics Government ERP managing director, in a statement. “Just as today’s citizens have higher expectations for the services they receive, so should public-sector organizations from their solution vendors.”
Additional findings in the study included 75 percent of respondents believing their ERP implementation will or did fall short of expectations, 69 percent did or expect to experience project delays and 60 percent felt the functionality of their ERP system was not up to par.
Taken in the aggregate, of the 139 organizations taking part in the survey that had new ERP systems put in place from 2002 to 2011, expectations were met only 42 percent of the time. Eighty-four organizations planned to get a new system within the next five years.
For those entities looking at purchasing a new ERP system, predicting costs is a struggle. The survey reported that respondents “had widely varying ideas about the real-world cost of ERP systems” ranging from $500,000 to $10 million.
You may use or reference this story with attribution and a link to
http://www.govtech.com/policy-management/Experts-Offer-ERP-System-Implementation-Tips.html
These failure statistics are a result of Government having relied for so long on a small number of Legacy ERP systems that cannot support business change. To make any sort of tweaks to these systems requires significant, complex and expensive programming at code level. As such, organisations are finding out too late that they’re completely dependent on their software providers and therefore cannot operate effectively. At UNIT4, a specialst supplier of ERP for public sector, we've had conversations with customers recently who are facing costs in the order of millions just to upgrade their legacy ERP to a supported version. And that’s just a single upgrade. Flexible systems that change as the business changes without code-level programming and intimidating upgrades can provide these organisations with the independence they need while providing flexible delivery options, be that cloud, on-premise or a combination. What this article does not convey is the importance of the on-going cost of change when evaluating ERP systems. In high-change environments like government, this means that the product’s architectural agility to support on-going change may be the single most important buying criterion to minimise change-related costs and inefficiencies.