...where expertise opens up new avenues
(Others hide this information; we share it sincerely.)
One of the crucial elements in adopting an ERP system is a proper beginning.
Defining goals and developing a clear and comprehensive vision for the system are of primary importance. For that reason, our methodology requires the client’s serious and complete involvement in the project even during the initial survey.
To develop an ERP system plan requires a survey phase in which procedures and the existing operating methods are thoroughly examined. If necessary, we also study business practices in the industry branch even more deeply.
One of the most significant phases of the survey is the "How would we like it to work" part. This is where a genuine merger between the capabilities of the program as it now exists and the client's unique requirements begins. Simple parameterization will remedy some aspects here, but other elements will require further program development. This is where we strive to achieve consensus. Some procedures will work more efficiently in the system if deregulated.
The documentation in the survey produces a system plan, which can be understood as a musical score, and must be accepted by both parties. It is possible to diverge from this score, but the extent to which one does so is individual and depends on the project. It is not advisable to make major changes in direction after the system plan is in place since this can delay the project as a whole, or in an extreme case, force both parties to start over again.
When both parties have accepted the system plan, the introduction phase begins. At this point, the key corporate users will be involved closely in implementing the system plan. The choice of key users is of strategic importance for the project. They will be the ones in the company who best know the system and they will be responsible for training their co-workers in the specific ways the system works for their company, even beyond the Dyntell basic training.
Successful introduction of this system needs the thoroughgoing and active involvement of both parties. Without this, ERP is a difficult and expensive undertaking for any company.
After determining the necessary adaptations and adjustments covering the demands presented in the system plan and in ongoing consultations, a prototype is created.
After this, as the need for further alterations emerge, we correct the system is set and begin testing. The amount of time needed for this depends on the project, but on average this takes 1-3 months.
The most suitable time for conversion to the new system is in case of accounting, a new calendar year. Our consultants will be available to you on-site for 1-3 months to assist in the implementation and to aid the progress of the project.
Once the system is performing satisfactorily, our employees will be available to support the project by online and telephone assistance.
The above procedure has been implemented by over 250 well-established companies and has been continuously refined. It is in everyone's interest for the system to operate properly. Most importantly, this process always begins with the exact definition of goals.