Implementation Enterprise-Level Business Systems

Implementation of Enterprise-Level Business Systems Paper The implementation phase, just before going live, is one of the most critical points in a project’s success. It is the culmination of a number of planned tasks, activities, many resources that have been brought together to implement the system based on the goals of the company and Project team. A product software implementation method is a blueprint to get users and/or organizations running with a specific software product. There are different types of implementation for a system.

One implementation method is a “Vanilla Installation”. This would entail implementing the system without any customizations. You would use the software right out of the box and follow a generic implementation. No changes would be made to your process. This may be good for non complex installations but not a good choice for an ERP System. Businesses with relatively straightforward business practices that are not unique should consider a vanilla implementation. Also businesses that don’t have the resources to handle customizations should also consider this route for an implementation.

The opposite of a vanilla implementation would be one that included customizations. This decision would be made based on the requirements gathering phase of the project. The company may have certain business or government requirements that are not included in a “vanilla” installation. They would then need to proceed carefully with customizations. Adding customizations or changes to the “vanilla” process and add more money, time and resources to the project. The business needs to assure that they are in agreement with this and have allocated the resources and time lines accordingly.

Microsoft Project is an excellent tool to use to plan the implementation of a system. This is generally the responsibility of the Project Manager and is done at the beginning of the project and signed off on by the key stakeholders in the project. It is a scheduling tool that can track each step in the process and it’s dependencies. Each step is marked with a start and completion date and can be assigned to certain functions or inividuals. At any given time a project manager can give updates on the project and alert key individuals if there seems to be an issue with certain tasks not being completed on time.

This process of mapping out all the steps needed in a project is a great way to assure you have a well defined process and ultimately gage your success. You have the ability to track if each task is completing on time. This plan will also ensure you can stay on time and on budget. •An example of an implementation process is as follows: Objective and Scope Setting the objectives and scope of ERP implementation; setting the expectation of the client . Requirement Analysis: The requirements of the client are collected, using the SRS (Software Requirements Specification) form, to further the process study.

GAP Analysis: This stage analyzes differences or gaps that exist between the standard capabilities of the desired system & the expectations of the client. The deliveralble would be a Gap Analysis document BMR (Business Mapping Report): This follow-up of the GAP Analysis should address the identified solution(s) for the gap areas. Data Mapping/ Data Loading Installation Design of Workarounds from the Gap Analysis Setup and Configuration Testing End User Training Go Live To measure the effectiveness of the implementation you can use the project schedule.

You can determine if the tasks were done within the budgeted time or if possibly more resources were need to finish the task. In addition you need to track the time and money spent on the project by the Implementation team of the software company. If they are going over this can cause major issues with the budget and adjustments may need to be made. The best metric would be if you can meet the scheduled Go Live of the project as planned. A good process for the implementation would be to have in place a Change Control System. Even seemingly minor changes could have significant impact on the system so a change-control committee consisting of staff members who are responsible for the major functions of the system (e. g. , technology, financials, operations, payroll, etc. ) can control any changes made that might affect the product and timelines. This committee should review and approve proposed changes to the system and advise policymakers when they seek advice on potential impacts to the system when a policy is being proposed. . ? Bibliography “ERP Implementation” Retrieved August 09, 2011 , http://www. gfoaconsulting. org/downloads/GFR-Jun08-ERPManageRisk. pdf A