ERP Implementation Methodologies
ERP Implementation Methodologies
ERP Implementation Methodologies
AGENDA
Need of Methodologies ERP Implementation Strategies ERP Implementation Methodologies
Examples
References
NEED OF METHODOLOGY
A good implementation methodology provides structure and control, and allows for a degree of flexibility to meet the operational requirements of the business. The methodology will include tools and templates to help with planning, decision making, data mapping, meetings, project reporting and cost control. A good implementation methodology means a supplier will deliver an ERP solution on time and within budget, and be able to deal with external factors that may arise that affect the progress of the project.
PREPARATION OF PLAN
CUSTOMISATION
DATA UPLOADING
TEST RUNS
METHODOLOGIES
USER TRAINING
PARALLEL RUN
METHODOLOGIES
2 4 6 8
3 5 7
It is of great importance to form an implementation team consisting of knowledge users from all functions along with IT personnel and personnel from implementation consultant. From the people chosen , the project manager and project leaders and the module leaders should be identified and also a steering committee should be formed .
Formation of implementation team
2 4 6 8
3
5
An important task is preparation of detailed implementation plan that covers the total implementation process.
Here various project management techniques like CPM, PERT charts can be used
2 4 6 8
This is a crucial stage where the reengineering processes are mapped on to the software .
3
5
In mapping the implementation team tries to fulfill the user requirements by making use of standard functionality available in the software .
However if the requirement are not covered by software fully , then next step of implementation i.e. gap analysis comes into picture.
Mapping business processes
2 4 6 8
3
5
2 4 6 8
3
5
Once the process mapping and gap analysis is done , the actual customizing starts. In this step first the customizing needs are chalked out and then the actual job is handed over to the respective functional teams.
CUSTOMIZATION
2 4 6 8
3
5
As mentioned under gap analysis any user requirements not covered by standard systems need to be provided by extra programming efforts. In this step the required reports and transactions are created.
2 4 6 8
With customizing in place , the system is now ready to receive the master and transaction data from the existing system.
3
5
In this step programmed transfer of data takes place from the existing system to new system.
To avoid wrong tabulation of master data transfer process needs to be thoroughly checked in the trial runs at times it to involves a lot of programming efforts.
DATA UPLOADING FROM EXISTING SYSTEMS
1
3 5 7
2 4 6 8
The test runs on the system are started . Sample transactions are tried to see whether the customizing and the master data uploading is error free.
The result of sample transaction is evaluated and any changes required in setting to get the desired results are incorporated
TEST RUNS
9 10
11 12
13 14
Normally user training includes: Logging in and logging out, Getting to know the system, Navigating through the various menu paths & Trying sample transaction in respective function
USER TRAINING
9 10 11 12 13 14
With the successful test runs and user training in place , the parallel run of the system can now started. In the parallel run , the business transactions are carried out in both through the existing as well as through the new system.
The implementation team then takes care of problems which comes to light during the parallel run.
PARALLEL RUN
9 10 11 12 13 14
If the parallel run is the satisfactory and error free , error that have come up have resolved , the user may be asked for their final approval.
USER CONCURRENCE
9 10
11 12
13 14
When the parallel run has been successfully tried for reasonable length of time and when the user and the implementation team fell absolutely confident , it is time to go live.
9 10 11 12 13 14
User Documentation includes the details on how to carry out the various transactions .
It is different from regular ERP package documentation in the sense that it is more specific in nature than general documentation.
It only covers alternatives that are being used in particular business so as to make it easy for the user to understand and use them.
USER DOCUMENTATION
9 10
11 12
Post implementation Support usually involves queries from user, minor changes in the report formats , as well as small changes in layout of various printed formats like purchase orders etc. In this phase the IT people monitor the system closely to see the performance aspects and fine tune the database and other administrative aspect of the system so that the user can derive the best performance from it.
OPERATIONS,SUPPORT & MONITORING
13 14
EXAMPLES
Sage ERP X3 from The Sage Group SAP Business All-in-One from SAP SAP Business ByDesign from SAP Baan ERP from Infor Global Solutions Oracle E-Business Suite from Oracle Oracle Fusion from Oracle
REFERENCES
http://blog.softwareadvice.com/articles/manuf acturing/erp-implementation-strategies1031101/ http://www.aptean.com/en/Solutions/ByApplication-Area/Enterprise-Resource-PlanningERP/Resources-Folder/ERP-System-Examples http://en.wikipedia.org/wiki/List_of_ERP_softw are_packages#Proprietary_ERP_software