International ERP rollout: Strategies for corporate groups

An ERP rollout is not just an ERP rollout - every experience we have had with often International ERP projects taught. Especially when a new system is to be introduced at several locations, it is important to find out about the various options for a rollout strategy and adapt it to the project. There is no standardised procedure. Nevertheless, you can take different directions with rollouts. Here are a few suggestions:

Versino Financial Suite for SAP Business One Finance

The "all at once" strategy for the ERP rollout

As the name suggests, this rollout strategy is all about the big picture. The new system is "rolled out" at all locations simultaneously. The load is equalised, but also equally high everywhere. An ERP rollout in this variant must therefore be well planned - because if something goes wrong, it has a direct impact on the entire group of companies. This strategy is particularly suitable for groups of companies that are already very closely linked and are looking for a standardised solution. The "all at once" variant has the advantage that the ERP solution can be easily developed by the various locations together and there is no "forerunner". Instead, processes can be standardised and thus grow together. If the locations differ in their working methods and this is perhaps even reflected in the system, a different strategy for the rollout may be more suitable.

The "step-by-step" strategy for the ERP rollout

As the exact opposite of the first strategy, this variant primarily offers one advantage. Instead of sending all locations into the often chaotic daily project routine at once, the ERP rollout is first implemented. The project approach can develop and improve each time. This takes the pressure off the individual locations and the project team only works on one "construction site". With this strategy, however, care should be taken to ensure that the individual projects do not become too far apart. The basic idea behind the introduction of a new ERP system is often that the company processes should also be standardised across locations. If this is not the case in the end, the project will have failed. Here at least it helps to Project planning and, above all, not to lose sight of the objectives. It is also a good help to ensure that the rollout does not turn into a long-term project.

The "stage" strategy for the ERP rollout

This variant of a rollout is a hybrid of the last two strategies. Although the rollout takes place in several steps, it is carried out across multiple locations. This variant is suitable for groups of companies that are not too widely dispersed and are working towards standardised processes and has the advantage that the implementation can be designed quite clearly, but is still carried out in one go. This is particularly useful for larger groups of companies in order to maintain an overview.

The "tester" strategy for the ERP rollout

This variant is also based on the previous strategies. Here, however, the company deliberately "tests" the ERP rollout at a smaller location. This strategy is then applied to all locations. The advantage: the project team can gain experience and test their strategy on a manageable project. However, the question arises as to whether to test at the location that needs it most urgently or at a location that needs the most. processes of all locations is best presented in a standardised way. The disadvantage is that you have to assume that the tested project strategy also works for all others, which is not necessarily the case. Again, it is important to consider how standardised the processes in the ERP system should ultimately be.

Ultimately, there is no predetermined "how-to-do-it" strategy for the rollout of ERP systems at multiple locations. The basis for the decision is the number of companies, their similarities, but also their differences and the capacities of the project team. Each group of companies can and should design this for itself.

Here a contribution on what you should definitely consider in an ERP project.

SAP B1 blog