Nine steps to the mobile ERP system

Mobile applications are already part of our everyday standard - whether privately or professionally. However, we are still in the early stages of development. Also in the area of ERP systems we have by no means exhausted the possibilities in the mobile field. However, it is slowly becoming necessary for most future-orientated companies to consider the use of mobile applications. The fact that this is often done hastily is due to short-term modernisation measures and an underestimation of the introduction. However, the implementation of mobile applications is just as complex as any other system project and requires good planning. planning. Here are nine steps on how you can approach the introduction of an (additional) mobile ERP system:

Step 1: Define goals and align with company focus

At the beginning of a mobile ERP system project, there is always the objective. This is not only to ensure that a realistic project plan can be drawn up, but also to create motivation for the implementation. This is also necessary when implementing mobile applications. It is hardly worth the effort just to say "we can also do mobile". It is important to consider how the mobile application relates to the company's goals and whether a common objective can be focussed on. It should always be kept in mind that mobile development does not stand still.

Step 2: Communicate with (future) users

It is particularly important to clarify who is using the mobile application and where, due to the rapid pace of development. It quickly becomes clear what requirements are placed on the use of mobile resources. It is important that there is conscious communication about the use and benefits of a mobile ERP solution. Training courses are always a good way to start this communication.

Step 3: Generate processes in a customer-oriented way

In contrast to the "normal" ERP system, customer contact plays a very important role in the mobile version. The mobile applications are often used to create and visualise calculations directly with customers. In addition to secure handling of the system, it is also important here to create an awareness of which processes should be visible to the customer and in which the result takes centre stage.

Step 4: Analyse functionality

In contrast to the previous points, the focus should always be on functionality. Just because certain processes can be implemented on mobile devices does not mean that this makes sense. It is also important that the functions that can be implemented in mobile processes are also supported by the corresponding end devices.

Step 5: Ensure usability in the mobile ERP system

Mobile applications only make sense if they are easy to use. We are used to our everyday "mobile apps" being self-explanatory. This is always synonymous with the success of a mobile application.

Step 6: Match technologies with previous points

The offer determines the question here: Which end devices are used with which OS (Apple, Android, Windows)? The web technology (e.g. as a browser app) is also defined here. This leads to the question of where which access to which company data should be created. There are as many answers as there are possibilities. Therefore, the objective, user definition, usability and the corresponding functionality serve as a benchmark for the corresponding solutions.

Step 7: Set offline functions sensibly

The major drawback of mobility: nothing works without a network. However, many mobile applications also offer the option of using important functions offline. Here it is important to determine which areas must also be available without the Internet. However, these offline functions should be kept to a minimum, as they also harbour risks (see P.9).

Step 8: Decide and plan development

Of course, it is also possible to develop your own mobile ERP application. However, if you don't have an in-house IT department, the chances are slim. And even so, experienced providers who have gained experience with the system and mobile applications are often the better alternative. Especially if the application is to remain update-capable with the system.

Step 9: Emphasise the safety factor

The top discussion factor with mobile applications is of course always the security of the data. From data misuse to errors by employees, there are a number of risks. It is important to create awareness of the security situation and to clarify the consequences for the company. The risk can also be limited to such an extent that, for example, only the data that is actually needed is available on mobile devices and no data is stored offline on the mobile devices.

SAP B1 blog