Chapter 7 E R P Implementation Lifecycle Alexis Leon

LifecycleCHAPTER 8ERP IMPLEMENTATION LIFECYCLESonali C.UDIT -T.Y.B.Sc (IT) 2008-09Sonali C. (UDIT TYBSc-IT)1Company Pre-Selection ScreeningERP VendorsManagementPackage EvaluationProject PlanningGap AnalysisReengineeringConfigurationImplementation Team TrainingTestingEnd-user TraningPre-Selection ScreeningPhases of ERP ImplementationPre-Selection ScreeningSonali C. (UDIT TYBSc-IT)2Pre-Selection Screening There are many Vendors and all packages are not same Study strong points and week points of each packages Short list according to the requirement of organization Check the years of existence of the vendor and past experience Search for a perfect packet. Compare the cost Compare the time requiredSonali C. (UDIT TYBSc-IT)3Sonali C. (UDIT-TYBSc-IT)1LifecyclePackage Evaluation Most important phases because it will decide failure and success of project. Require huge investment so switching to another ERP package is not easy.“DO IT RIGHT THE FIRST TME” No package is perfect - (keep in mind before analysis). Do not require prefect fit ,Should be flexible enough for the company needs. Develop selection criteriaSonali C. (UDIT TYBSc-IT)4Cont…Package EvaluationPoints to be kept in mind while evaluating ERP:1. Functional fit with the 7. Ability to support multi-company‟s business site planning and controlprocess.8. Technology 2. Degree of Integration 9. Availability of regular between the various upgradescomponents of the ERP system.10. Amount of customization required3. Flexibility and scalability11. Local support 4. Complexityinfrastructure5. User friendliness 12.Availability of reference 6. Quick implementationsites13.Total cost Sonali C. (UDIT TYBSc-IT)5Cont…Package EvaluationBetter to form evaluation/selection committee for evaluation processThis is not a one-man-decision.All the departments are involved. Thus it should have company wise acceptanceDiscuss the pro & consSonali C. (UDIT TYBSc-IT)6Sonali C. (UDIT-TYBSc-IT)2LifecycleProject Planning Phase Designs implementation processdetermine-“How to go about” – time schedule, deadline, etc – PROJECT PLAN IS DEVELOPED  Roles are identified and Responsibilities are assigned Everyone's scope of work defined and Heads of implementations identified Team members are selected and task allocation. How- When- What to DO??? Phase is controlled by committee and meets periodicallySonali C. (UDIT TYBSc-IT)7Gap AnalysisCrucial phase Create complete model of where they are now and in which direction they will head in future.Even the best ERP package can only cover 80% of the companies functional requirement.The remaining 20% of these requirements present a problematic issue for the company‟s BPR.One of the most painful solution is to change the business process to fit the ERP packageSonali C. (UDIT TYBSc-IT)8Cont…Gap Analysis Other solutions: Updation at low cost Identifying a third party product that might fill the gap. Design a custom program. Altering the ERP source code (most expensive) used only for mission criticalSonali C. (UDIT TYBSc-IT)9Sonali C. (UDIT-TYBSc-IT)3LifecycleReengineeringHuman factors are taken into account.Two different connotations: Downsizing efforts (controversial) Reduce significant no of employeesBusiness Process Re-Engineering ( Two separate but closely linked implementations are:)Technical implementationBusiness process integration.Sonali C. (UDIT TYBSc-IT)10Configuration Business should be mapped according to goal of company Prototype is created before implementing it Live. Testing is done on prototype Configuring not only reveals strength but also weakness. Explains what wont fit and whr the gap isSonali C. (UDIT TYBSc-IT)11Implementation team Training Implementation team is trained i.e. connotations how to implement  Later employees are also trained to run the system Vendors and consultant will leave after implementation is over. Good in-houses must be there to handle system. So there should be right selection of employee. Willing to change ,Learn new thing andNot afraid of technologies – and good functional knowledgeSonali C. (UDIT TYBSc-IT)12Sonali C. (UDIT-TYBSc-IT)4LifecycleTesting Try to beak system Testing real case scenarios While testing- come up with extreme case scenarios- System overload Multiple users logging at same time User entering invalid data Hacker and so on… Test case must be designed to find weak links and bugs should be fixed before going liveSonali C. (UDIT TYBSc-IT)13Going live“Lights On, Switches Thrown, Gloves Off” Technical side, Work is almost completed Functional side, prototype is fully configures and tested ready to go operational Once system is „live’ old system is removed and new system is useSonali C. (UDIT TYBSc-IT)14End-User Training Actual user is given training on how to use system. Starts much before system goes liveSonali C. (UDIT TYBSc-IT)15Sonali C. (UDIT-TYBSc-IT)5LifecyclePost-Implementation This is very crucial phase as there are no vendors and consultant at this stage. So employees must be trained thoroughly to handle problem is system. There should be employed who must have knowledge to enhance the system in future. System should be upgraded and ne technologies are introduced.Sonali C. (UDIT TYBSc-IT)16Any Questions????THANK YOUSonali C. (UDIT TYBSc-IT)17Sonali C. (UDIT-TYBSc-IT)6