Republic Polytechnic Case Study Assignment Example | Topics and Well Written Essays - 2750 words

Republic polytechnic institute Case Study - Assignment ExampleImplementation of an ERP in any organization involves a liveness cycle from the decision to adopt it to successful roll step up, with discernible implementation phases as characterized by the mark stakeholders, typical activities, associated challenges and extinctcomes. Four broad phases can be discerned base on this framework. They are planning, configuration, testing and real(a) implementation (Kumar, Maheshwari and Kumar 2003, pp. 795). Other authors present the phases as involving planning, implementation, stabilization and improvement (Markus and Tanis 2000, pp.173-207 Shanks et al. 2000, pp. 2). In the case of Republic engineering schools ERP, the latter framework is seen in action thus forming this papers line of discussion.The outgrowth stage that was undertaken in RPs implementation of the ERP is planning. RP needed an Enterprise System that was able to support twain considerations. These include their p roblem-based learning pedagogy and their commitment to an IT strategy that would render the campus paperless for faster, efficient and cost-effective processes. RP set out on an outsourcing path for the vendor of an enterprise-wide e-learning management system that would provide a package which could suit RPs mission and strategic direction. All relevant stakeholders were involved in finding such a vendor, supple enough to allow for the heavy customization that was necessary for RPs strategy, to be rolled out dubbed LEO (Learning surround Online). This step involved two representatives from RP.... o allow for the heavy customization that was necessary for RPs strategy, finally prima(p) to settling on Wizlearn Pte Limited and their Academic Version 7 package. Post-purchase tailoring was the next step aimed at customizing the vendors product to RPs needs in the system to be rolled out dubbed LEO (Learning Environment Online). This step involved two representatives from RP. These are OAA (Officer of Academic Affairs) and OIS (Officer of Information Systems) and an external IS police squad from the vendor all of whom liaised together and held discussions that finally resulted in a heavily customized product plan put to be rolled out. The next phase after the planning part was actual implementation of the colonized upon system, done a fewer weeks before the opening of the school term. The system that was rolled out provided an optimal system for RP and her staff although it was not exactly like they had envisioned as it had not accommodated all their views. stabilisation was the next phase for the system. Although the roll out had determined that there would be no need for information of RP staff, it was still necessary to provide basic training on the core features of the LEO. In a akin fashion, the students were trained on a basic general IT course and then given a few lessons on the core features of the LEO by the facilitators. The last phase of RPs impl ementation of their ERP was improvement. This involved access of the features that had been suggested in the planning stage but had been left out in implementation. More improvements on the ERP were based on suggestions from three sources the top management, the facilitators and the development team itself, with additional suggestions being drawn from the students. The LEO coach determined which improvements