Discussion on:
View:
Show:
Are you in the midst of an ERP planning or implementation effort? What obstacles have you encountered so far?
Sorry I just clicked on the link to find out what ERP stood for. Enterprise (Resource? Recovery?) Plan?
We are getting ready to upgrade our servers to Server 2003. But I haven't finished the whitepaper from MS on that.
Paul
We are getting ready to upgrade our servers to Server 2003. But I haven't finished the whitepaper from MS on that.
Paul
Useful in large organizations or businesses.
http://en.wikipedia.org/wiki/Enterprise_resource_planning
http://en.wikipedia.org/wiki/Enterprise_resource_planning
Thanks a lot for attaching the website it is more usful for me.
actually our company planning to implemment an ERP system and I will be the in-charge for this process.
maybe i need your advice in some subject.
like , selection of database, selction of vendors...
please if u can keep in touch on my E-mail:(gsaleh_2000@yahoo.com)
actually our company planning to implemment an ERP system and I will be the in-charge for this process.
maybe i need your advice in some subject.
like , selection of database, selction of vendors...
please if u can keep in touch on my E-mail:(gsaleh_2000@yahoo.com)
Clients who ask for too much without realizing how far back it will push the deadline.
Clients who ask for one thing, to change their minds again and again and again. Eventually you have to tell them no.
Clients who request customizations that are so complicated that no one can use them but the person who was involved. (I have seen an almost million dollar customization fail because it was beyond what users would understand).
Clients who ask for a change and won't accept the time line because they do not understand the complexities of what they are asking.
Clients who try and combine multiple "screens" into one so that all the information is in one place. They don't realize it further complicates training and makes it harder for the end-users to understand. Screens are usually separated for a reason.
ERP implementations that use EDI.. Oh the woes of EDI and how people like to make up their own EDI standards and name it to some other form of EDI.
Clients not realizing that there method of thinking or business requirements may change with a new ERP implementation. Just because you did it that way before, doesn't necessarily mean it's okay to continue doing it that way. Sometimes your business practices have to change...
It's these type of situations that have lead to client frustration and what I have seen as "failures" on their parts.
I have seen one ERP implementation fail completely. Where we as the ERP package had to take a hard stance and to not continue working with the client.
By the way my list could go on forever I think... :P
Clients who ask for one thing, to change their minds again and again and again. Eventually you have to tell them no.
Clients who request customizations that are so complicated that no one can use them but the person who was involved. (I have seen an almost million dollar customization fail because it was beyond what users would understand).
Clients who ask for a change and won't accept the time line because they do not understand the complexities of what they are asking.
Clients who try and combine multiple "screens" into one so that all the information is in one place. They don't realize it further complicates training and makes it harder for the end-users to understand. Screens are usually separated for a reason.
ERP implementations that use EDI.. Oh the woes of EDI and how people like to make up their own EDI standards and name it to some other form of EDI.
Clients not realizing that there method of thinking or business requirements may change with a new ERP implementation. Just because you did it that way before, doesn't necessarily mean it's okay to continue doing it that way. Sometimes your business practices have to change...
It's these type of situations that have lead to client frustration and what I have seen as "failures" on their parts.
I have seen one ERP implementation fail completely. Where we as the ERP package had to take a hard stance and to not continue working with the client.
By the way my list could go on forever I think... :P
I recently left a company where an ERP implementation was going south. The North American President of the company came to IT and mandated an absorption of a home-grown AS400 based ERP (Canada operations) into a customized and several versions behind JD Edwards World on an AS400 (USA) in 7 months for less than $250k! No documentation exists for the customizations in either location. The Executive micro managed the project and at the same time didn't understand or listen to the technical teams. He then mandated that IT use consulting firms to help. Thankfully my involvement was only on the networking/website side of things. My fondest memory was arguing with same executive that we needed Cisco routers vs. $40 linksys routers (his suggestion was the linksys routers to save money) for the MPLS network between locations. And explaining that AS400 twinax (token ring?) didn't work over the TCP/IP based MPLS network. Kind of like explaining what a calculator is to a caveman.
I got a better job for a company that understands that technology is not a cost center. Last I heard they had big problems finding employees/consultants that knew legacy AS400/JD Edwards world AND knew modern stuff like web-enabled AS400, TCP/IP, SSL, Ansi SQL, change management, java/SOA, it goes on and on. Anyway the ERP project is still going on and it's been over a year now. Poor leadership doomed the project from the beginning.
I got a better job for a company that understands that technology is not a cost center. Last I heard they had big problems finding employees/consultants that knew legacy AS400/JD Edwards world AND knew modern stuff like web-enabled AS400, TCP/IP, SSL, Ansi SQL, change management, java/SOA, it goes on and on. Anyway the ERP project is still going on and it's been over a year now. Poor leadership doomed the project from the beginning.
My co-workers and executive just didn't understand what ERP meant. I work for a wonderful group of people that previously did everything on excel spreadsheets, countless Access applications and had an Accountant that worked from an MS DOS based accounting software that did a cutover to an ERP system. Even in this mid sized environment, the results were devestating. They could not get invoices out the door because there was no training or documentation on the system. The team that implemented the new system did not follow through on planning the processes involved. The finger pointing was out of control!
I was hired at a very critical point and had to turn things around very quickly. Concentrated on cleaning and defining the processes and data related to the core accounting functionality first then worked outward. The company is now profitable and we will be implementing a new module this year.
I was hired at a very critical point and had to turn things around very quickly. Concentrated on cleaning and defining the processes and data related to the core accounting functionality first then worked outward. The company is now profitable and we will be implementing a new module this year.
Technette41,
Most interesting to read your posting to this article. History repeats itself over and over again, to my surprise. I have implemented several ERP systems in my IT life and the story is always the same you told: Lack of knowledge and planing.
Hope all keeps on the right track.
Most interesting to read your posting to this article. History repeats itself over and over again, to my surprise. I have implemented several ERP systems in my IT life and the story is always the same you told: Lack of knowledge and planing.
Hope all keeps on the right track.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
