Too much or too little? How much information can be included in the specifications?

Especially the entry into a ERP project often determines its success. We have already discussed the essential role of the specifications in this process here. On the basis of the requirements laid down in the specifications, the design grows and takes shape. ERP system. Missing information can lead to a "wrong" result, as can too much information... This raises the question: how much detail does the specification need to go into?

Not too little...

It takes some information to properly define the requirements for an ERP system. This is the only way to determine the criteria according to which you can select the appropriate software. Without this, you will also be offered "suitable" solutions. However, these will always be ERP systems that cover the necessary standard but do not address the specific needs of your industry. This means that you will be able to optimise parts of your company. However, the potential of a new ERP software is not exhausted.

Therefore, go into detail! Even an expert ERP consultant don't know how the processes in your company are set up. Analyse them - together if you like. Then the consultant can react with suitable options.

... and not too much

However, you should stay focused. If you start to execute every process down to the smallest detail and endlessly formulate every desired application possibility, this will increase the workload enormously and you will quickly get lost in details and thereby lose focus on the essentials. In addition, in a specification you should above all address the problem of the processes to hold on to, less to suggest solutions. That is the provider's part.

Priorities in the specifications!

But where is the border between too little and too much information? First of all, you can leave out everything that is already included in the standard ERP software. Classic accounting or functions for order creation belong here. An overview of standard ERP functions you can ask your ERP consultant (or another person with expertise in ERP projects).

Further, you can work well with prioritising functions. First list the requirements that are most important for your company. You can also go into detail here - it's worth it. This way you won't lose focus during the project and know where it's worth investing. It is easier to save money on functions that are "nice-to-have" but not absolutely necessary, without jeopardising the success of the project.

Not too little...

... and not too much

Priorities in the specifications!

Get more out of your SAP Business One

Leave a Reply Cancel reply

site lock

We will call you back!