Implementation is crucial in the success of computerization. The effort here involves organizing task force, system mapping, defining procedure and baseline data, data preparation, and project management. An implementation guide is used as the workbook for implementation.
Implementation methodology adopted by ISL generally consists of the following steps:
Initial Preparation: Contract signing, site preparation, hardware installation, software installation Base-Line: Base-line information, system mapping, master file preparation
User-Training: Distribution modules, accounting modules, production modules, system administration module.
Pilot Run: Scenarios definition, conceptual training, pilot run, acceptance of flow
Live Run: System switching and official launch, including system acceptance meeting and after-sales support service
There are three concerns involved in system implementation, namely, quality, time, and cost. In practice, the amount of time and cost are the key factors to the quality. Low cost and quick implementation usually results in poor quality.
Depending on the readiness of user organization, scope of implementation, and the system involved, to get it up and running could take between one and six months. We try to come up with a practical time frame for the implementation according to the computer literary of the users so as to ensure the smooth deployment of the new system.
We provide classroom training for our complete product range which includes training notes for each participant. The training is organized into two parts. The morning session is carried out using a stop-and-go methodology which allows users to go through the training material while practising at the same time. Users will start prototyping in the afternoon session with their own data for the purpose of experimentation as advised. This faciliates them to get familiar with the system in a short period of time.
This involves bringing data across different platforms or different software. It usually requires data to be in ASCII text file format, with delimiters or in spreadsheet columns.
Master files such as item master, customer, supplier, and chart of accounts are portable. Transaction files are different between systems and are not ported because of the huge effort involved in development and verification.
One-to-one correspondence simplifies the process as there is no need for conversion. Most conversions require custom programming and may not be cost effective.
After the data are ported, it is the users' responsibility to verify for completeness and accuracy.
In the case when the standard system does not address the specific needs of your company, you can request for customization. ISL's Research & Development team will assess the impact that the requirement would have on the system and estimate the development time. If the request is a general requirement concerning most users, ISL will adopt it in future release with no additional cost. Otherwise, ISL will provide a quotation on the customization.