- The need for user to be committed in attending training by Software Vendor
- Overcoming users resistance on workflow and system changes.
- Integrating with other ERP2 software used by the customer's vendors in diverse industries. KarenSoft's Rosettanet middleware will help to resolve this issue.
- Need to take into account unforeseen operational interruptions which will cause delays in the ERP2 project implementation from time to time.
- Lack of experienced Customer personnel in implementing the system. In this respect, the right ERP2 vendor will be able to provide adequate training and hands-holding.
- Incorrect specifications given during system study by Vendor. This can be resolved if the Software Vendor are principals (like KarenSoft) and not merely representatives.
- Where remote access is needed from areas where bandwidth is an issue, the need to have low bandwidth access via the right system architecture. For example, KarenSoft SCM can be accessed anytime and anywhere through a 22.8 dial-up and still get 'speed of thought' response.
- Need to co-ordinate implementation and ISO procedures
Thursday, April 06, 2006
ERP2 Implementation Tips : During Implementation
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment