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 set out in the specifications, the ERP system. This can lead to a „wrong“ result due to missing information, and too much information just as easily... This raises the question: How much detail does the requirements specification need to go into?

Not too little...

It takes quite a bit of information to properly define the requirements for an ERP system. Only then can the criteria be established for selecting the right software. Without this, you will still 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. While this will allow you to see an optimisation in parts of your company, the potential of new ERP software will not be fully exploited.

Therefore, go into detail! Even an expert ERP consultant don't know how the processes in your company are organised. Analyse them - preferably together. The consultant can then respond with suitable options.

Versino Financial Suite for SAP Business One Finance

... and not too much

However, you should remain focussed. If you start to detail every process down to the smallest detail and endlessly formulate every desired application option, this will increase the workload enormously and you will quickly get lost in the details and lose focus on the essentials. In addition, in a specification sheet you should above all consider the problem of processes hold on to, rather than suggest solutions. That's the provider's job.

Prioritise the specifications!

But where is the line between too little and too much information? Firstly, you can leave out everything that is already included in the standard ERP software. This includes classic accounting or order creation functions. An overview of standard ERP functions You can ask your ERP consultant (or another expert in the field of ERP projects) for more information.

Furthermore, you can work well with prioritising features. First, list the requirements that are most important for your business. Feel free to go into detail here – it's worth it. This way, you won't lose focus during the project and will know where it's worth investing. For features that are „nice-to-have“ but not absolutely necessary, it's easier to make savings without jeopardising the project's success.

SAP B1 blog