Sass? We're too busy making ERP work

TalkBack 5 of 5:

« Previous

• Thread View
• Flat View

RE: Sass? We're too busy making ERP work

Quote: "
* Making the wrong software choices and force
fitting solutions
* Setting unrealistic implementation targets
* Failure to manage scope and duration"

Let us focus on the cause of these points of failure:

* Ownership of the Requirement Document
* Technical inhouse customer expertise
* Low level Software Supplier Sales Reps
* Undefined scope of work.

Let's now try to analyse each factor.

*Ownership of the Requirement Document:
1) You cannot make the wrong software choice if you have the tools to document your requirements.

2) Do not fire your FD whilst implementing an ERP system. Why? Simply because the new FD will have his/her own views on the internal processes and might have them changed to a level which wasnt scoped or cannot be met by the ERP Software.

3) Consider the duty of your employees during an implementation and choose the targeted go-live date wisely. Many a fool wants an ERP system within shortest delays, to impress the directors. Imagine the pressure on your accounting & Sales team to answer 100's of questions whilst on peak period/ month or year end.

* Technical inhouse customer expertise
Do your employees have the technical expertise and role to decide upon processes? Will they be able to test a new system and provide clear information on failed scenarios?

* Low level Software Supplier Sales Reps
Can you trust what the sales rep says the system can do? Remember that you are dealing with someone who has for single objective to sell. Not to implement or to understand your needs. If sales reps understood ERP, they would be consultants.

* Undefined scope of work.
An 'open' scope of work may comfort you in the short term but when you hit specific ERP requirements, you may realise that what matters most to your business cannot be acheived. There is no ground for law case since the supplier never promised anything specific but to attend to your needs, if acheivable, during implementation phase.
Some companies, who have the budget, pay for development, which delays the go-live. Others simply look for another ERP system, sour of their experience.

Currently no one has the audacity of creating a tool which helps customers in determining their ERP needs, inhouse, as a team, since these needs can never quite fit any template.

Those interested in contributing their knowledge to such a tool should review sites which, like Mr Howlett's article, aspire the world of IT to a new approach to ERP Implementation.

Posted by: wawadewa   Posted on: 07/27/09 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• The Impact of Virtualization Software on Operating Environments VMware Today's use of virtualization technology allows IT professionals to ... Download Now
• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now