When a company is in search of a new employee, the ERP-system, sooner or later it faces the decision of standard software or specialised solution. There are many reasons in favour of a standard system - not least the fact that ERP solutions are so flexible that they can be adapted to the individual needs of a company. adapt can. Nevertheless, the perception of what is meant by standard software is not as clear-cut as one might think.
In order to avoid unpleasant surprises, it helps to check the ERP selection define for yourself as a company exactly what you want to achieve with the use of a new system. Helpful in this case is a clean process analysis. The results can then be compared with the possibilities of a standard system.
What does "standard software" mean?
But what do these options entail and what is actually "standard"?
Today, it is almost no longer the case that companies operate entirely without Accounting software or other systems that accompany the work of the company. These are the same processes that are used in a ERP standard system are covered as a basis. This is why we also speak of "basic factors". Many people expect these to be implicit in an ERP system and only the absence of these functions usually indicates their indispensability.
What follows are the "performance factors", i.e. functions that are specifically expected by the future user of the system. These can only be surpassed by so-called "excitement factors", i.e. functions with a surprise effect that the user would not have expected.
The demands grow
However, it is often the case with ERP systems that performance factors quickly become basic factors and enthusiasm factors become performance factors. Especially since many of the basic and performance factors were also mapped in other systems - which were previously used in the respective company - and thus the demands on the new standard software grow. One could almost speak of an expectation of the enthusiasm factors.
Shaping standards first and meeting them later
It is difficult with standards that are shaped by trends and sometimes by the marketing departments of the manufacturers. Some megatrends literally force functions that are not very mature. At the same time, everyone who wants to serve the hype reinforces the effect. The competition feels compelled to follow suit and another pseudo-solution is established. Much later, and often enough through user feedback, really rounded standards are developed.
Unaccustomed standard
Many users find it difficult to leave their familiar processes (which is not always necessary). However, the idea of a standard software always includes standard processes that are better followed. Sometimes a restructuring of the processes to those available in the new software is also a real benefit for the company. The mapped functions have been tested for their success and therefore mean a Optimisation. On the other hand, manufacturers often work with feedback from customers. The standard of the newer version of a software is then a new but modified standard. In the end, however, the results in the standard solution are correspondingly different.
The flexible standard
Standard software and best practice are welcomed and demanded by many companies. When the time comes to swear an oath, i.e. to introduce the software, the call for customisation quickly follows. And that means customising the software, not the company. At first glance, this seems illogical. But bear in mind that a medium-sized company in particular often only differs from its competitors in how it does things, but not what it does. And this different "how" should also be mapped by the company software, standard or not. Many manufacturers respond to this dilemma with a promise: Flexibility. And yes, you can do an incredible amount.
But one must not be under the illusion that one can have both without limitation: Best and personal practice.
With every adjustment you give up a piece of standard.