Implementation of an ERP
CIOREVIEW >> Enterprise Resource Planning >> NEWS

Villa Group Resorts & Spas

Moisés Juárez Sánchez, ERP & POS Application Manager

Implementation of an ERP

Moisés Juárez Sánchez, ERP & POS Application Manager
Moisés Juárez Sánchez, ERP & POS Application Manager, Villa Group Resorts & Spas

When a company decides to strengthen control over its administrative processes and resources, implementing an ERP becomes an indispensable strategy. However, since this change impacts most areas of the business, it is crucial to follow a series of steps to ensure a smooth and successful implementation.

1. Business Analysis: Before making any changes, it is fundamental to understand the current business situation. Therefore, it is necessary to identify all areas that will be involved and document their daily processes in detail. This will help us understand the needs and identify areas of opportunity required to streamline processes and reduce resource waste.

2. ERP Selection: Given the variety of options in the market, understanding our needs will facilitate the selection of the best ERP for our business. The most expensive or widely marketed solution may not always be the best fit for our requirements. Therefore, it is important to consider factors such as our business sector, company size and budget allocated for the project, taking into account implementation and licensing costs.

  
​We must never forget that the success of any project depends
largely on communication
   

3. Provider Selection: Even if the company has highly qualified IT personnel, including the consulting services of a selected ERP provider is advisable. Their experience will be invaluable in saving time, avoiding wasting financial resources, and extracting all necessary technical information from operational users. When choosing a provider, it is crucial to consider their experience with the system, working methodology, and the support they will offer before, during, and after implementation.

4. Change Management: Once this point is reached, the company must implement a change management policy to ensure a smooth transition. All members, from top management to operational staff, who will be affected directly or indirectly by the change must be aware and focused on this process. Users of the system are the most critical part of adapting new technologies in the company. Therefore, it is fundamental to provide constant information about the planned change and its status, generate descriptive documentation on how to carry out processes, and offer constant training on the operation of the new system.

5. Acceptance Testing: No system should go into production without undergoing QA and testing phases by the IT department and users. The IT team will validate that the requirements made to the provider were actually delivered correctly and meet the requested functionality. Meanwhile, since there is no better expert in each area than the users themselves, they will ultimately determine if the new system meets their needs and is functional. In case there are requirements for any of the system's functionalities, the IT department must properly document them and report them to the provider.

6. Implementation: Undoubtedly, this is one of the most complicated phases of the project because it involves shutting down the legacy system to start operations with the new solution. Therefore, it is necessary to load all necessary information so that all areas can work. This information includes initial accounting balances, as well as catalogs of suppliers, customers, and products. It will be crucial to validate at least one week before going live that all hardware and software configurations are working properly to avoid setbacks.

7. Daily ERP Support: Once the stabilization phase of the system after going live is completed, it is necessary to follow up and record each incident that occurs through a ticketing tool. The IT staff must define the escalation level and the SLA for each ticket according to its complexity. Additionally, users must be trained on the correct way to request support, including a brief but descriptive title of the error and a detailed explanation of it. A periodic analysis of recurring errors must be carried out to determine if they are due to user expertise or system problems, which must be documented and reported to the provider for correction.

We must never forget that the success of any project depends largely on communication. Therefore, we must maintain constant communication with top management, users and the provider. We must also keep in mind and remind the business that any system is always in a process of continuous improvement, so over time, we will need to mature the system to adapt it to our daily processes.

The articles from these contributors are based on their personal expertise and viewpoints, and do not necessarily reflect the opinions of their employers or affiliated organizations.