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 do the specifications need to go into?
Not too little...
It takes some information to correctly define the requirements for an ERP system. This is the only way to determine the criteria according to which you can select the right 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 cater to the specific needs of your industry. This will enable you to optimise parts of your company. However, the potential of 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 organised. Analyse them - preferably together. The consultant can then respond with suitable options.
... 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 to hold on to, less to suggest solutions. That is the provider's part.
Priorities in 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.
You can also work well with the prioritisation of functions. Firstly, 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 you'll know where it's worth investing. It is easier to make savings on functions that are "nice-to-have" but not absolutely necessary, without jeopardising the success of the project.
Software validation in medical technology
Netting and creditors with debit balances
SAP Business One Partner – the right one is important
Data migration in ERP projects
ERP upgrade – at some point it will be time
