ERP Implementation: typical problems and how to avoid them
 by: Andrew Karasev


The fact, that midsize business ERP system implementation should be planned and thought through – what-ifs and rollbacks. This is not a recent management science discovery. Plus – it also known from the managerial theory that key people and the whole company team involvement is highly recommended, and even required. In this small article we will concentrate on the generic technology pitfalls as well as the coordination with several high-tech contractors and you internal IT team. We will assume that you are on Microsoft Windows platform and implementing Microsoft Dynamics GP Great Plains, however similar advises are applicable to Navision, Solomon, Axapta and Microsoft CRM implementation scenarios

• Computer network factor. When you implement ERP, you have to use your Windows Domain or Workgroup as a platform with multiple tunings and connectors to make your ERP hosted and implemented in this environment: shared network folders, network printers (preferred printers with their driver for specific GP documents printing), Reporting access and security (in the case of GP you restring access you your FRx sysdata, where reports are stored in metadata, for example)

• Contractors management. If you deploy different companies to build your IT network and implement ERP – both companies may be pretty confident in their core expertise, however if they do not work out shared vision of implementation – it may fail in the interoperability area. This is especially possible when IT contractor moves ERP system to new hardware (new more scalable server) without MRP consultants being involved. General advise – consider having one of your employees or insiders playing project management role to coordinate your contractors

• Documentation and Control. When you are small, you probably just have business owner or your trusted employee to keep in her/his mind the system and support it as needed. However, when you are in the midsize business category, when your IT department has several people, and you don’t have documentation and business processes MRP automation workflow – there is the risk of losing control, especially when you decide to change ERP consulting contractor, or if you have to replace your IT internal workforce. Specific GP case would be keeping Dexterity source code of your custom piece – DYNAMICS.DIC with your scripts

• Traditional ERP Implementation Wisdom. In this article we don’t repeat it in detail, however, we recognize its importance and encourage you to familiarize yourself with traditional ERP implementation success factors. It may orient you and prevent you from repeating common errors. If you need quick directions, in google enter “ERP Implementation” and read few articles on the top

About The Author
Andrew Karasev, Alba Spectrum Group, http://www.albaspectrum.com [email protected] 1-866-528-0577, 1-630-961-5918, serving Microsoft Dynamics GP USA and Canada nationwide: Toronto, Montreal, Vancouver, Calgary, Windsor, New York, San Francisco, Los Angeles, Miami, Orlando, Pittsburg, Toledo, Indianapolis, Detroit, Philadelphia, Boston, Washington, Seattle, San Diego, Phoenix, Austin. Local service is available in Chicago and Houston metros: Rosenberg, Katy, Richmond, Dallas, Galveston, Sugar Land, Naperville, Wheaton, Plainfield, Aurora, Wheaton, Downers Grove, Lisle, Oakbrook, Morris, Marseilles, Joliet, Montgomery, Oswego, DeKalb. With reasonable travel we serve Springfield, Bloomington, Normal, Peoria, LaSalle, Ottawa, Dixon