Adoption of IT

There are 3 main steps under adoption 1. Configuration 2. Training 3. Testing

The new IT system that is implemented need to be configured with proper parameters and rules that is required by the company. For e.g.:- Date and Time, currency, exchange rates, tax factors etc:The business analysts or domain experts need to develop clear, precise and complete business rules that represent real life business process logics and these processes need to be logically robust so that the rules can be configured easily by consultants or implementers without any confusion. Keeping this in mind a task force was created and business rules were documented .These rules were rechecked and wetted by internal audit team. This document was later sent to configuration team. Configuration team configured the rules in the new system. The implementation Project Team members had received application software training in the Design and CRP phase. Shortly after the project team training and a full cycle regression test of the ERP application during the Pilot phase, the person in charge of training (often the software vendor) designed a user oriented training curriculum and delivered end user training in the form of classroom training or a train-the-trainer program. End-user training curriculums differ from the initial project team training as they put much greater emphasis in the day-to-day user tasks and activities and do not include the software set up, application configuration or process alternatives exhausted during the pilot phase. End user training permits users to focus on only the activities that they need to be concerned with and leaves the configuration and business process alternatives to the project team. Implementation experience clearly shows that user retention is the most challenging training obstacle faced by users. It is therefore advisable to schedule the user training just before the go-live event. It is also very important that management provide the uninterrupted availability of those users scheduled to receive training so that training can be both efficient and effective. User training is frequently performed as a Train-the-Trainer program. All users responsible for using the application in everyday tasks must be trained in at least the processes necessary for their routine activities. When it comes to user software training, the strategy used was KISS (keep it simple stupid) principal. Stay focused on the primary and core responsibilities and do not try to make your users technology experts - it will not work and ultimately produce frustration that then challenges user adoption. Instead, empower your users with the screens, information and knowledge to become better in their positions, not technology gurus. Some other training recommendations are listed below.

Allocate your limited implementation time in the most optimal areas with a significant concentration in user training programs. ERP applications and

accounting software systems should have less of a focus on software technology and more of a focus on people, processes and training. A thorough training curriculum and post-production user support are directly correlated to the adoption and use of the new business software system and the achievement of the company's objectives. Be sure you have finished all of your software configuration, pilot Q.A.,and system testing before you begin the user training programs. It is a mistake to knowingly or unknowingly make the users the testers or Beta site which results in the unintended result of losing their confidence in the new system just before the go-live cut-over. Develop a solid agenda, training curriculum, classroom facility and supporting hand-out materials and integrate cross reference materials where they add value. Develop a rock solid, user based, real-world training curriculum. It is usually a mistake to use the software manufacturer's generic training materials. Instead use a tailored curriculum that more closely aligns with the users daily activities and responsibilities. Depending upon your user base computer literacy, you may want to consider skill-set assessments which measure PC skills and can then introduce precursor courses or append the training program as needed. Provide multiple types of user help resources such as a support desk, printed collaterals, role aides, reference sources, Queue Cards, a knowledge-base and online documentation. You may also want to consider provisioning a separate training company application so that users have a location to experiment without the risk of corrupting the system. If you're using internal help desk resources, make sure they are thoroughly trained, tested and ready for incoming user requests. It is generally a good idea to have these resources involved in the user training delivery.

Accordingly the users were given adequate training on the new system. The trained users were given access to the new system. They got the feel of the system and started testing various screens and data. Now new system was running parallel to the old system. Users could feel the ease and simplicity of the new system. They tested the data and report outputs of new system with the old system and confirmed the accuracy of configurations and data. Internal Audit team wetted the final results and the new system was adopted.