Presentation on theme: "Class 9 – April 27, 2012 An Abbreviated but Typical System Conversion Plan for a Medium-Sized Enterprise."— Presentation transcript:
Class 9 – April 27, 2012 An Abbreviated but Typical System Conversion Plan for a Medium-Sized Enterprise
Pre-Project Analysis Perform internal needs analysis Use needs analysis to preview system options Perform business process analysis Study workflows Identify and prioritize problems Identify needed variations from the normal way of doing things Identify potential software solutions Identify vendors Touch base with stakeholders and management to make sure they are updated and involved – keep them involved from this point forward Interview vendors and set up demonstrations
Pre-Project Analysis (cont) Supply vendors with demonstration data and needs requirements Arrange to have appropriate personnel attend demonstrations Gather feedback from attendees Determine legacy system maintenance needs and who will provide for these needs Evaluate hardware and software upgrades required Negotiate with top 3 vendors Select vendor and finalize contract
Preparation for Conversion Maintain legacy system with minimal updates/upgrades during conversion Upgrade hardware and software per plan Leave old hardware and software in place if legacy system will not run on new platform Convert legacy system to new platform if possible and desireable Begin export of data from legacy system Evaluate options for conversion of data to new system File formats, tools to use for conversion, etc.
Preparation for Conversion (cont) Determine customizations and data file modifications needed on new system Create testing implementation of new system Implement all customizations on test system Begin importing data into new system data files for system testing Write all required reports and test Print reports and reconcile to legacy system Test customizations and overall implementation with test transactions Refine and revise customizations, data file structures, and import routines as needed
Initial Training Begin training power users of the system Involve supervisors from all affected areas Allow power users to stress and test the system Refine and revise customizations, data file structures, and import routines as required Enlist power users to help train other employees before conversion Importance of power user buy-in Importance of adequate training before conversion
Conversion Develop tentative conversion schedule by location and area Prepare for final data export from legacy system Print all reports Shut down use of legacy system after final exports Should be maintained in this final condition with no updates allowed Export final conversion data Import data into production system Run reports on new system and compare to legacy Tune and test all hardware and software settings to prepare for volume Arrange for support teams in all locations where conversion is taking place Parallel processing!!!!! Very time consuming but worth the effort