Monday 8 December 2014

ERP Implementation - Typical Problems And How To Avoid Them

o          Computer network factor. When you implement ERP, you need to make use of your Windows Domain or Workgroup as a platform with multiple tunings and connectors to make your ERP hosted and implemented in this surroundings: 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)

The fact, that midsize business ERP technique implementation ought to be planned and thought through what-ifs and rollbacks. This is not a recent management science discovery. And, it is also known from the managerial theory that key people and the whole company team involvement is highly recommended, and even necessary. In this small editorial they will concentrate on the generic expertise pitfalls as well as the coordination with several high-tech contractors and you internal IT team. They 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

o          Contractors management. In the event you deploy different companies to build your IT network and implement ERP - both companies may be confident in their core expertise, however in the event that they do not work out shared vision of implementation - it may fail in the interoperability area. This is feasible when IT contractor moves ERP technique to new hardware (new more scalable server) without MRP consultants being involved. Customer relationship management General advise - think about having of your employees or insiders playing project management role to coordinate your contractors

o          Documentation and Control. When you are small, you very certainly have business owner or your trusted worker to keep in her/his mind the technique and support it as needed. However, when you are in the midsize business section, 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, when you pick to change ERP consulting contractor, or in the event you need to replace your IT internal workforce. Specific GP case would be keeping Dexterity source code of your custom piece - DYNAMICS.DIC along with your scripts

o          Traditional ERP Implementation Wisdom. In this editorial they don't repeat it in detail, however, they 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. In the event you need speedy directions, in Google enter "ERP Implementation" and read few articles on the top
IBM Lotus Notes with Domino e mail server is traditional document workflow management solution for huge corporate business, where you need audit trail on approval cycle and decision making. Microsoft Business Solutions CRM is cost efficient solution to automate sales method. It might be surprising, but they see nice strata of clients who are willing to deploy and integrate both systems: MS CRM and Lotus Domino. In our view these clients are balancing ERP platform risks and trying to protect and deploy investments in to Lotus licenses, while deploying new and already leading CRM solution - Microsoft CRM. In this small news story we'll give you the integration example - European division of of the widely known machinery manufacturer dealership network.

o          Custom Lotus Database. In our case client had custom database, which was designed back in the beginning of 1990th. Some dealers had Lotus Notes Domino four.0 and a number of them had 6.0 and 6.5. Technical excurse - in Lotus Notes Domino 6.0 you can use Java two agents, and it appears to be platform independent (Microsoft Windows Server, IBM AS/400). To synch all the dealerships - the decision was made to upgrade across the network to Lotus Notes Domino 6.0 (to be a bit conservative)

o          Domino Messaging. Obviously you need to have e mail server assigned to your url domain, and as historicallyin the past Lotus Domino was the e mail server - the replacement with Microsoft Exchange 2003 (which is natural choice in the event you buy Microsoft CRM) was not an option. With Alba Spectrum Technologies MS CMR Lotus Notes Domino connector you can switch e mail messaging to Lotus Domino

o          Lotus & MS CRM events synchronization. IBM and Microsoft application designers designed CRM & Lotus events differently. Second phase of the project implementation will synchronize appointments, calendar events, etc. between Lotus and MS CRM.

o          MS CRM ODBC lookups to Lotus database. As the second phase they plan to implement lookups from MS CRM Account to cases with custom fields and Lotus notes lookup tab. This tab will be realized as web .net application, integrated in to MS CRM web interface. Enterprise resource planning  This web application will have machine serial number, warranty & service information. As you  certainly know in MS CRM three.0 you can deploy custom table in link it to MS CRM object as one-to-many. The most important is that it will be synchronized by MS Outlook and will permit you as a salesperson to work offline.

No comments:

Post a Comment